Printer Selections at Runtime

When you submit batch versions to a printer, the system looks first for the printer defined in RDA. If no printer is defined in RDA, the system uses the default printer defined in the JD Edwards EnterpriseOne Printer Application (P98616.) The system determines a printer based on this hierarchical structure:

1. System function.

   Do_Initialize_Printer called in the Report Event Rule.

2. Printer defined in RDA.

   The printer definition becomes part of the report specifications.

3. Printer defined in the JD Edwards EnterpriseOne Printer Application (P98616) using this hierarchy:

   1. Specific report defined for the user.

   2. Specific report defined for a user role.

   3. Specific report defined for *PUBLIC.

   4. All reports defined for the user.

   5. All reports defined for a user role.

   6. All reports defined for *PUBLIC.

4. User override of defined printer at submission time.

   See Customizing the Location of Report Output.

Depending on the printer that is selected, the system selects the corresponding Printer Definition Language on the Advanced tab of the Printer Selection form at runtime.

When batch jobs are submitted using report interconnects, the child report inherits the printer definitions from the parent report. At print time, once the job has completed processing, you can override the printer for the child report from the JD Edwards EnterpriseOne Work With Servers (P986116) application.

When you submit a job using RUNUBE, if you do not indicate a printer name through the command line parameters, the printer name stored in the specifications is used at print time; otherwise, the default printer is used. At print time, you can override the printer from P986116 when the job has completed processing.

See "Submitting at the Command Line" in the JD Edwards EnterpriseOne Tools Batch Versions Guide.