Custom reports should be placed under a custom product top. Nonetheless,
creating a custom product top and registering a custom application within
Oracle Applications is beyond the scope of this paper. Please reference the
Oracle Applications Developer's Guide or Coding Standards manual for guidelines
on creating and registering a custom application.
With a custom product top established, copy the postscript report definition
file (RDF) to the appropriate subdirectory under your Oracle Applications:
$CUSTOM_TOP/srw for release 10.7 or $CUSTOM_TOP/reports for release 11.
a. DEFINE A CONCURRENT PROGRAM EXECUTABLE
A concurrent program executable entry associates a source file-like a report
definition file (RDF) with an application and an execution method. When the
execution method is set to Oracle Reports, the ar25run runtime will be called
to process or execute the RDF located under the specified application.
Select a unique Executable name and Short Name for your concurrent program
executables. The executable can be used to define multiple concurrent programs with
different printing styles and reporting option characteristics.
1. Navigate to Concurrent/Program/Executable and create a new concurrent
program executable record for each custom RDF.
2. Below is a general concurrent program executable example:
Executable: MY_PS_RPT
Short Name: MYPSRPT (Release 11 Only)
Application: Custom Apps
Description: My Postscript Report
Execution Method: Oracle Reports
Execution File Name: PS_RPT
Note: In the above example, the report definition file PS_RPT.rdf must be
present under the $CUSTOM_TOP. Oracle Applications will search the base
path of the product/custom_top specified in the Application field.
b. DEFINE A POSTSCRIPT CONCURRENT PROGRAM
This concurrent program record defines which registered Oracle Applications
executable will be called, what options or report parameter will be passed, how
the program request will run, and any output file printing requirements.
For postscript printing, the executable Options field needs the value
VERSION=2.0b and a postscript printer and postscript style needs to be
specified. In Release 11, the format output must be postscript.
Unless a common out directory has been established, the program's output files
will be place under the appropriate product/custom_top specified in the
Application field.
1. Navigate to Concurrent/Program/Define and create a new concurrent program
record for each custom RDF.
2. Below is a general concurrent program example.
Program: My Postscript Report
Short Name: MYPSRPT
Application: Custom Apps
Description: My Postscript Report
Executable Name: MY_PS_RPT
Options: VERSION=2.0b (Must be upper case)
Method: Oracle Reports
Priority: Blank / Unchecked
Request Type: Blank / Null
Use In SRS: Yes / Checked
Allow Disable Values: Blank / Unchecked
Run Alone: Blank / Unchecked
Enable Trace: Unchecked (Release 11 Only)
Restart on System Failure: Unchecked (Release 11 Only)
NLS Compliant: Unchecked (Release 11 Only)
Format: Postscript (Release 11 Only)
Saved: Yes / Checked
Print: Yes / Checked
Columns: 132
Rows: 45
Style: Landscape_PS
Style Required: Yes / Checked
Printer: SitePr3
Note: After adding or making any changes to a defined concurrent program record, the
ICM will recognize the changes after it has been verified on the
Administer Concurrent Manager form.
c. ADD THE CUSTOM REPORT TO A REPORT GROUP
Before a custom report can be selected for printing, the newly defined
concurrent program must be listed within a report group. Select the report
group associated with the responsibility that will be allowed to submit the
custom report and add the newly defined concurrent program.
1. Navigate to Security/Responsibility/Request and query the appropriate
request group and add your postscript program to the request list.
2. Below is a general report group entry example:
Type: Program
Name: My Postscript Report
Application: Custom Apps
d. ASSOCIATE THE CUSTOM APPLICATION WITH A DATA GROUP
Before a custom report can run to a successful completion, any application
schemas associated with the custom report must be listed within a data group.
Select the data group associated with the responsibility that will be allowed
to submit the custom report and add any application schemas.
1. Navigate to Security/ORACLE/Data Group and query the appropriate data
group and add the application associated with you postscript report.
2. Below is a general data group entry example:
Application: Custom Apps
Oracle ID: custapps
Note: Although a concurrent program is listed with a report group, it may not
have the necessary privileges to access the database data referenced
within the custom report. This data access privilege is provided to the
report through the data group associated with a responsibility.
