Working with Batch Version Specifications

This chapter provides overviews of batch version specifications and discusses how to:

• Check out and check in batch versions.

• Copy batch version specifications to an enterprise server.

Understanding Batch Version Specifications

Batch versions read their specifications from the associated report template. Typically, any modifications that you make to a report template are read by all of the associated batch versions. The exception to this is a batch version in which you have overridden specifications.

Unlike other JD Edwards EnterpriseOne objects, you can submit the specifications of new and modified batch versions to the server without creating a package. However, the associated batch application must already be checked in.

Checking Out and Checking In Batch Versions

This section provides overviews of checking in and checking out batch versions and erasing the check out record for batch versions, and lists the forms used to check out, check in, and erase the check out of batch versions.

Understanding Checking Out and Checking In Batch Versions

You must check out batch versions before you can:

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

• Set data selection from the Row menu of the Oracle's 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 the Oracle's 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 Oracle's 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.

To convert web only batch versions to run on a Microsoft Windows client, you must check the version out and then check it back in. To permanently remove the Web Only indicator, generate the batch version using the Oracle's JD Edwards EnterpriseOne eGenerator tool after converting the version.

Understanding Erasing the Check Out Record for Batch Versions

Batch versions, as with all JD Edwards EnterpriseOne objects, can be checked out by only one person at a time. Erasing the check-out record allows another user to check out the version and leaves the specifications on the server unchanged. After you have erased the check out of a batch version, you cannot check in the version. However, the report specifications on the workstation remain intact.

When you erase the check out of a batch version, the system updates the checked out status field in the Versions List (F983051) table from Y to N. The system also updates the location field in the Versions List table. This value is changed from the location of the workstation that checked out the version to the machine name of the central object's server.

You can erase the check out of batch versions using JD Edwards EnterpriseOne Object Management Workbench or JD Edwards EnterpriseOne Batch Versions.

Forms Used for Checking Out, Checking In, and Erasing the Check Out of Batch Versions

Copying Batch Version Specifications to an Enterprise Server

This section provides an overview of copying batch version specifications to an enterprise server and lists the forms used to copy batch version specifications.

Understanding Copying Batch Version Specifications to an Enterprise Server

You can copy batch version specifications to an enterprise server without building a package for deployment. You can do this any time the associated report template specifications already reside on the enterprise server. You should use this process when you override the specifications in batch versions.

It is imperative that you copy batch version specifications to an enterprise server when you modify a batch version that is called by another batch version. After you modify the batch version, use this option to copy the version specifications to the same location as the batch version that calls it. This procedure ensures that the batch version calls the updated specifications, rather than obsolete specifications.

Forms Used to Copy Batch Version Specifications