Understanding Batch Versions

Batch versions follow the same process as other Oracle JD Edwards EnterpriseOne objects for check in, check out, and erasing checkouts. Use JD Edwards EnterpriseOne Object Management Workbench (P98220) to control the movement of versions between the workstation and the server. However, unlike other JD Edwards EnterpriseOne objects, you can submit batch version specifications to the server directly from JD Edwards EnterpriseOne Batch Versions application.

Just like master report specifications, when you create a batch version on the Microsoft Windows client, the specification records for that version exist only on the workstation. To make the version available to other users, you must check in the version. When you check in batch versions, the system copies the version specifications to the central objects data source (server) according to the path code of the current environment. However, when you create batch versions on the web client, you do not have to check them in because they are automatically updated to the central objects for you.

Once a version is in the central objects data source (server), anyone who installs and runs the version is ensured of having the updated version. After you check in the batch version, you can still make certain changes to the version without checking it out. For example, when you make changes to the processing options, these changes are effective immediately, even if you have not checked in the local version. This is because the processing options for versions are stored as a field in the server Versions List (F983051) table.

A version cannot be checked out by more than one user. The Version Detail form identifies the user that has a version checked out.

You can create a new batch version based solely on the associated report template. For example, you might create a new version because you do not want to use the layout or data selection of an existing version.

You can create a batch version based on an existing version. If you copy a version, the copied version inherits the same overrides as the version that is copied, such as data selection and data sequencing.

If you make changes to a report template, the system automatically pushes these changes to all of the associated versions that exist for that report. The exception to this rule is batch versions that contain overrides to the specific section modified in the report template.