1. Batch Versions Guide
  2. Understanding Checking Out and Checking In Batch Versions

Understanding Checking Out and Checking In Batch Versions

You must check out batch versions before you can:

  • Modify batch versions using JD Edwards EnterpriseOne Report Design Aid (RDA).

  • Set data selection from the Row menu of the JD Edwards EnterpriseOne Batch Versions (P98305) application.

  • Set data sequencing from the Row menu of the Oracle's JD Edwards EnterpriseOne Batch Versions application.

When you check out a report object, or any JD Edwards EnterpriseOne object, the system copies the object specifications from the central objects location to the workstation. The set of central objects that the system accesses is defined in JD Edwards EnterpriseOne Object Management Configuration (P98230) application. Only batch versions that reside in that set of central objects are visible. A batch version cannot be checked out by more than one user at a time.

If you check out a batch version and do not make any changes to it, erase the check-out record so that other users can check it out. You need to check out a batch version if you want to make modifications that override the master report template specifications. You do not need to check out a batch version to make these changes at runtime:

  • Data selection

  • Data sequencing

  • Location

  • Processing option values

These runtime changes are not saved with the batch version. However, if you make changes to data selection or data sequencing from the Work With Batch Versions - Available Versions form, you must first check out the batch version. You then check the batch version in to save the changes and make them available to the enterprise. You can check in and check out batch versions either from JD Edwards Object Management Workbench (P98220) or from the Row menu on the Advanced Operations form in JD Edwards EnterpriseOne Batch Versions.

Before you check in batch versions, make sure that you want the changes that you made to be permanent. When you check in batch versions, the system copies the specifications to the central objects location. The new specifications override the previous specifications for the version. The report specifications on the workstation remain intact.

Note: Checking in, checking out, or erasing the checkout of a version only applies when working with batch versions from the Microsoft Windows client. Changes to data selection or data sequencing for batch versions accessed from the web client are updated to central objects automatically, which makes them available to the enterprise without the need to check them out or in. Therefore, make sure that you want your changes to be permanent before making data selection or data sequencing modifications to batch versions accessed from the web client.