Batch Versions at Submission

When you submit batch versions, the batch engine uses a device context to generate a PDF file. This device context includes information such as page size and the printable area of a page. The system generates this information from the printer tables for all platforms.

Within JD Edwards EnterpriseOne, you have the option of viewing the PDF output using Adobe Reader or sending the report directly to a printer. You can also print the report from Adobe Reader. When you send the report to a printer, the system uses a conversion filter to transform the PDF file into a PDL format:

• PCL 5

• PostScript level 3

• Line-printer text

These language formats depend on the type of printer printing the report.

The batch engine uses a logical path to determine to which printer to send reports. If the first method does not return a valid printer name, the batch engine uses the subsequent method.

When you submit batch versions:

1. The batch process triggers the Do Initialize Printer event defined in RDA.

   If this process retrieves a valid printer name, other processes are ignored.

2. You override the default printer name at the time that the report is submitted.

   If you override the default printer with a valid printer name, further processes are ignored.

3. The report specifications pass a printer name to the batch process.

   If this process retrieves a valid printer name, the next process is ignored.

4. The system uses the Printer Definition (F98616) table to determine a valid default printer based on the current user, the environment that the user is signed into, and the host that processes the report.