Submitting Report Definitions from Batch Versions (P95305)

This section discusses submitting report definitions from the Batch Versions application and describes how to:

Associate report definitions with batch versions.
Submit batch versions.
Access Batch Version Advanced Option Overrides.

You can associate a report definition with a batch version for user convenience. By doing so, users can submit report definitions from the Batch Versions application by submitting a batch version that is associated with a report definition. To associate a report definition with a batch version, the version must first be checked out. You can check out the version either in Object Management Workbench (OMW) or through the Batch Versions application (P98305) on the Microsoft Windows client.

By associating a report definition with a batch version, if the output is sent to a printer you can choose various print options at runtime, such as portrait, landscape, simplex, duplex, tumble, number of copies, and so on.

See "Selecting a Print Style Option" in the JD Edwards EnterpriseOne Tools Report Printing Administration Technologies Guide.

Some batch versions, such as R42520/XJDE0006, Print Pick Slips - Subsystem, are configured as subsystem jobs. Subsystem jobs offer many advantages, such as the elimination of startup time, one-time initialization of environment and specifications, and better utilization of the processor on the server. You can set up a subsystem report and version to produce BI Publisher output by creating a template and adding a report definition in the Report Definitions application (P95620), with the subsystem report as the source UBE and version.

See Templates

Defining Source of Data, Template Names, and Transformations

After the report definition has been defined, you can associate it with the batch version if you want the version to produce only BI Publisher output.

For information about subsystem jobs, see "Working with Subsystem Jobs" in the JD Edwards EnterpriseOne Tools Report Design Aid Guide.