Understanding Report Interconnects in Batch Applications
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.