Processing Options

Processing option values are stored in the Versions List (F983051) table for each batch version. This table is centrally located and can be accessed by all JD Edwards EnterpriseOne users within a specific environment. Jobs running on client machines and jobs running on servers all access the same table.

Processing option values that you enter during submission are used at runtime. If prompting is not available, values that exist at submission are used at runtime. Values that you enter during submission are saved in the Versions List table and are displayed the next time that you submit that version. When another user runs the same batch version, the processing option values defined by the previous user display. You can, however, override the processing options for the submission or you can create a new version that includes the processing option values that meet your business requirements. If you define the processing options for a version to execute as a blind execution, the processing option template does not display at submission and other users cannot modify the values.

This table provides some data selection and data sequencing scenarios:

Scenario	Description
Batch versions submitted locally.	During submission of a batch version, you might be prompted for processing option values. The system stores the processing option values that you specify in the Versions List table. When the job is executed, the system retrieves the processing option values from this table.
Batch versions submitted on the server.	The submission process begins in the same way as when a batch version is submitted locally. However, the system sends this job and the associated processing option values to the server. On the server, the system stores the processing option values in the Job Control Status Master (F986110) table. When the job is executed, the system retrieves the processing option values from the Job Control Status Master table instead of the Versions List table.