This chapter contains the following topics:
You can use report interconnects to launch reports and batch applications from:
Another batch application
An interactive application
How the system processes the batch application information depends upon the type of processing selected:
Synchronous
Synchronous is the default processing method. If you select synchronous processing of the report interconnect, the initiating process waits until the batch application has finished before it continues running the original application.
Asynchronous
If you select asynchronous processing, the initiating process starts another process and continues to run the original application. The two processes run separately but at the same time.
This section provides an overview of report interconnects in batch applications, lists the prerequisites, and discusses how to create report interconnects.
You can use report interconnects to automatically run a batch application from another batch application or an interactive application when certain criteria are met. You can use a report data structure along with the report interconnect to pass values between the batch applications.
The batch application that is doing the calling is the primary batch application. The batch application that is being called is the secondary batch application.
Define the report interconnect in the primary batch application. Use the After Last Object Printed event if you want the secondary batch application to be processed after the primary batch application is complete.
You must map parameters as part of the report interconnect. These parameters map data from the primary batch application to data in the secondary batch application. As part of the parameter mapping, you must also indicate the direction that the data should flow.
Define the data structure in the secondary batch application. The secondary batch application might not have a business view attached. It can receive its data from the primary batch application based on the criteria that you define. Select data items to include in the data structure, and then assign these fields to the data items that are included in the secondary batch application.
Report interconnects are beneficial when the secondary batch application provides further detail for the records that are included in the primary batch application or when different data in the primary batch application is required for different audiences.
The user runs the primary batch application, and when the stated criteria are met, the system processes the secondary batch application automatically.
Before you begin creating report interconnects, ensure that you:
Create two batch application objects.
Complete the design of the first report template to serve as the primary batch application.
Complete the design of the secondary report template and define a report data structure.
Open the primary report template in Oracle's JD Edwards EnterpriseOne Report Design Aid.
From the detail section of the report, access Event Rules Design, and select an event.
Click the Report Interconnection option on the toolbar.
On the Work with Applications form, select the batch application that you want to process.
On the Work with Versions form, select the appropriate version of the batch application that you want to process.
In the Available Objects column, select the object that you want to pass, and move it to the Data Structure-Value Column.
Indicate the direction of data flow between Value and Data Items.
To run the report as a separate process, select the Asynchronously option.
To include the report interconnect for transaction processing, select the Include in Transaction option.
Click one of these buttons to add notes, and then click OK:
Structure Notes
Parameter Notes
Note:
Event Rules Design displays the Report Interconnection with the Call (UBE <name> Version <name>) statement.