function BeforeReport return boolean is

begin
-- fnd_client_info.set_org_context('204');
SRW.USER_EXIT('FND SRWINIT');
return (TRUE);
end;
1. The "Unknown User Exit" error will only be when you try to run the report through Reports Builder (including the Live Preview mode). You will be able to
copy it to your machine, open it, make changes, save it, put it back on the server - you just won't be able to run it locally. This is because in the Before
Report trigger there will be a line like "srw.user_exit('FND SRWINIT');" which refers to code that is compiled into the Concurrent Manager's version of the
Reports executable (set's up the Oracle Apps logon), but not your local Reports executable. One option to avoid the error is to put this call to srw.user_exit
in it's own block with an exception handler (this ignores the error, but doesn't set up the Oracle Apps logon, so no Responsibility setup including no Org ID
for the Org specific views), like:
begin
srw.user_exit('FND_SRWINIT');
exception
when srw.unknown_user_exit then null;
end;

2. Yes, it is possible to change the font size through Reports Builder BUT most Report concurrent programs are set up to only generate ascii text. Check the
Output Format field of the Concurrent Program definition - if it is set to Text, then it will only produce ascii text output, with no formatting (except printer
codes).

3. Yes, you can use printer codes to change font formatting, but I have only ever used this for making certain fields bold and even then had issues with
different printer types showing the printer codes as text.

The best way to produce a nicely formatted output from an Oracle concurrent program is to use BI Publisher - with this method, the report itself only
produces XML text output, but you define a template for converting that to PDF (for example) where you do all of your formatting. Note that directly printing
PDF concurrent request output on Unix requires additional setup over standard printing.
Nithin,
You're getting a blank page because the table or views used in the report query are ORG specific. Therefore, when you removed the BeforeReport trigger
call to "SRW.USER_EXIT('FND SRWINIT')" you disabled the code that SETUP the user environment used to filter data in the report. You could modify the
Report Query to use the _ALL version of each table/view (eg: OE_ORDER_HEADERS_ALL instead of OE_ORDER_HEADERS) and this would query the parent
tables, but you might end up with more data than you were looking for as you will be getting everything, not just the data for the ORG the user is logged
into. Also, it's been a while since I've worked with EBS, so you may want to post your question in [EBS General Discussion
|http://forums.oracle.com/forums/forum.jspa?forumID=475] forum. There is another way to set the user environment without calling the FND SRWINIT
function, I just don't remember how to do this. It is the same way if you are running a query in SQL*Plus and you are not using the _ALL tables.

Hope this helps.
Craig...