Creating Batch Versions

This chapter provides an overview of the difference between web client and Microsoft Windows client batch versions, and discusses how to:

• Create batch versions from the Microsoft Windows client.

• Create batch versions from the web client.

• Convert web only batch versions.

Understanding the Difference Between Web Client and Microsoft Windows Client Batch Versions

Batch versions that you create from the web client are defined as Web Only. Web only batch versions cannot be:

• Run from the Microsoft Windows client.

• Copied from the web client.

However, you can define data selection and data sequencing for web only batch versions from the web client. Data selection and data sequencing for web only batch versions are referred to as persistent and remain with the batch version until you change them again.

You cannot change persistent data selection and data sequencing for batch versions created from a Microsoft Windows client while on the web client. However, you can change data selection and data sequencing at runtime. You can copy Microsoft Windows created batch versions from the web client. The copied batch version is defined as web only.

You can convert a web only batch version to a Microsoft Windows batch version, if needed.

See Converting Web Only Batch Versions.

Creating Batch Versions from the Microsoft Windows Client

This section provides overviews of adding batch versions and copying batch versions, lists the prerequisite, and discusses how to:

• Add batch versions in the JD Edwards EnterpriseOne Batch Versions application.

• Copy batch versions in the JD Edwards EnterpriseOne Batch Versions application.

• Add batch versions in JD Edwards EnterpriseOne Object Management Workbench (P98220).

• Copy batch versions in JD Edwards EnterpriseOne Object Management Workbench.

Understanding Adding Batch Versions

You must create at least one batch version for each report template before you can process the report. You can create batch versions automatically in Oracle's JD Edwards EnterpriseOne Report Design Aid (RDA) using the Report Director. You can create additional batch versions from the Oracle's JD Edwards EnterpriseOne Batch Versions application by:

• Adding a new batch version.

  When you add new batch versions, the new versions read the specifications from the associated report template, or master specifications.

• Copying an existing batch version.

  Copying batch versions provides a slightly different result than adding batch versions as explained in the next section.

If the associated report template has a processing option attached to it, the Prompting Options field is active when you create a new batch version. You can define how you want the system to handle processing options at runtime. This table describes the prompting options available:

You should set up security on all new batch versions. Version security enables you to set security differently for each JD Edwards EnterpriseOne version. Batch version security is separate from JD Edwards EnterpriseOne security that is defined in the Oracle's JD Edwards EnterpriseOne Security Workbench (P00950) application. This table describes the batch version security options:

At the time that you create a new batch version, you can define the batch version to print immediately every time that it is submitted for processing. This enables you to define specific batch versions to output directly to the printer rather than sitting in the print queue until someone releases it to the printer. The Print Immediate option can be overridden at runtime.

There is also a setting in the jde.ini for the print immediate feature. This setting, however, affects all batch versions. The print immediate option on the Version Detail form enables you to define the feature for individual batch versions.

Understanding Copying Batch Versions

You can copy existing batch versions from the Microsoft Windows client and tailor the information to fit your needs. The new version inherits all of the master report specifications and any overrides that are defined in the version that is copied.

When you copy batch versions, you should add security to the new version. Version security is separate from the JD Edwards EnterpriseOne security defined in the JD Edwards EnterpriseOne Security Workbench application. Version security enables you to set security for different JD Edwards EnterpriseOne versions.

When you copy batch versions that are defined to print immediately, the copied version is also defined to print immediately. You must modify the version details and clear the Print Immediate option if you do not want the new version to print immediately every time that it is processed. The Print Immediate option can be overridden at runtime.

Prerequisite

Before creating batch versions from the Microsoft Windows Client, ensure that you create a batch application.

Forms Used to Create Batch Versions from the Microsoft Windows Client

Adding Batch Versions in the Batch Versions Application

Access the Version Add form.

Application	The name of the batch application upon which the batch version is created. This information is populated by the system based on the batch application selected on the Work With Batch Versions - Available Versions form.
Version	Enter the name of the batch version.
Version Title	Enter the title of the batch version. The title describes the purpose of the batch version.
Prompting Options	Select the method to be used for process the processing option values. Values are Prompt for Values and Blind Execution. You can also select to disable the processing option.
Security	Select the restriction to be placed on the batch version. Values are 0–3, 0 is no security and 3 is full security.
Job Queue	Select the queue to which the batch version is submitted.
Version Detail	Enter the functionality differences between the batch version and the associated batch application.
Print Cover Page	Select this option if you want a cover page to print with the batch version.
Print Immediate	Select this option if you want the batch version to print immediately every time that it is processed. The Print Immediate option can be overridden at runtime.

Note. The new version must be checked in to make it available to the enterprise.

Copying Batch Versions in the Batch Versions Application

Access the Version Copy form.

Application	The name of the batch application upon which the batch version is created. This information is populated by the system based on the batch application selected on the Work With Batch Versions - Available Versions form.
Version to Copy	The name of the batch version that is being copied. This information is populated by the system based on the batch version selected on the Work With Batch Versions - Available Versions form.
New Version	Enter the name of the batch version.
Security	Select the restriction to be placed on the batch version. Values are 0–3, 0 is no security and 3 is full security.
Version Title	Enter the title of the batch version. The title describes the purpose of the batch version.

Note. The new version must be checked in to make it available to the enterprise.

Adding Batch Versions in Object Management Workbench

In Solution Explorer, from the Tools menu, select Object Management Workbench to access the Object Management Workbench form.

1. Click Find and in the project view, expand the project to which the batch version will be added.

2. Click the Objects node of the project and click Add.

3. On the Add EnterpriseOne Object to the Project form, select Batch Version, and click OK.

4. On the Adding a Version form, enter the name of the report template or batch process for which you want to add a batch version in the Batch Application field and click OK

5. On the Version Add form, enter the name of the version in the Version field.

6. In the Version Title field, enter a title that indicates the specifics of the batch version.

   For example, General Ledger by Batch for Business Unit 1.

7. In the Prompting Options field, indicate how you want the associated processing options to process.

   If the associated report template does not have any processing options attached, JD Edwards EnterpriseOne leaves the Prompting Options field inactive.

8. In the Security field, indicate the level of security for the batch version.

9. In the Job Queue field, indicate the queue to use for processing the batch version.

10. In the Version Detail field, enter a brief description of how the batch version differs from the report template.

    For example, this version displays address book records for employees only and is sequenced by name.

11. Select the Print Cover Page option, if required.

12. Select the Print Immediate option, if required, and click OK.

13. On the Batch Version Design form, select the Tools tab and define data selection and data sequencing for the version.

    On the General tab of this form, you can select Revise Version to edit the version information, Processing Options to modify the processing option values, or Run to run the new version.

14. On the Batch Version Design form, click OK to save the version.

15. Check in the new version to make it available to the enterprise.

See Working with Objects.

Copying Batch Versions in Object Management Workbench

Access the Object Management Workbench form.

1. In the project view, expand the project where the batch version that you want to copy resides.

2. Expand the Objects node, click the batch version, and click Copy.

3. On the Version Copy form, enter the name of the version in the New Version field.

4. In the Security field, indicate the level of security for the batch version.

5. In the Version Title field, enter a title that indicates the specifics of the batch version and click OK..

6. On the Batch Version Design form, select the Tools tab, define data selection and data sequencing for the version and click OK.

7. Check in the new version to make this version available to the enterprise.

Creating Batch Versions from the Web Client

This section provides overviews of adding batch versions from the web client and copying batch versions from the web client, lists the prerequisites, and discusses how to:

• Add batch versions from the web client.

• Copy batch versions from the web client.

Understanding Adding Batch Versions from the Web Client

As with the Microsoft Windows client, report templates must have at least one batch version before you can process the report from the web client. When you create a new batch version from the web client, the new version is identified as web only.

If the associated report template has a processing option attached to it, the Prompting Options field is active when you create a new batch version. As with the Microsoft Windows client, you can define how you want the system to handle processing options at runtime.

As with the Microsoft Windows client, you should set up security on new batch versions.

Understanding Copying Batch Versions from the Web Client

You can copy existing batch versions, if they are not defined as web only, and tailor the information to fit your needs. The new version inherits all of the master report specifications and any overrides that are defined in the version that is copied.

When you copy Microsoft Windows batch versions from the web client, the copied version is identified as web only. From the web client you cannot copy:

• Web only batch versions.

• Table conversion versions.

As with the Microsoft Windows client, when you copy batch versions you should set up security for the new version.

Prerequisites

Before creating batch versions from the web client, ensure that you:

• Create a batch application from the Microsoft Windows client.

• Check in the batch application.

• Ensure that the batch application has been deployed to the server.

• Ensure that the batch application has been generated to HTML.

Forms Used to Create Batch Versions from the Web Client

Adding Batch Versions from the Web Client

Access the Submit Job - Add Version form.

Note. This task does not pertain to table conversion versions; versions for table conversions cannot be added from the web client.

Report	The name of the batch application upon which the batch version is created. This information is populated by the system based on the batch application selected on the Submit Job - Work With Batch Versions - Available Versions form.
Version	Enter the name of the batch version.
Version Title	Enter the title of the batch version. The title describes the purpose of the batch version.
Prompting Options	Select the method to be used for process the processing option values. Values are Prompt for Values and Blind Execution. You can also select to disable the processing option.
Security	Select the restriction to be placed on the batch version. Values are 0–3, 0 is no security and 3 is full security.
Print Immediate	Select this option if you want the batch version to print immediately every time that it is processed. The Print Immediate option can be overridden at runtime.

Note. On the Submit Job - Work With Batch Versions - Available Versions form, the number one is displayed in the Web Only column. This indicates that the batch version is a web only version and cannot be run from the Microsoft Windows client.

Copying Batch Versions from the Web Client

Access the Submit Job - Copy Version form.

Note. This task does not pertain to table conversion versions; versions for table conversions cannot be copied from the web client.

Report	The name of the batch application upon which the batch version is created. This information is populated by the system based on the batch application selected on the Submit Job - Work With Batch Versions - Available Versions form.
Version to Copy	The name of the batch version that is being copied. This information is populated by the system based on the batch version selected on the Submit Job - Work With Batch Versions - Available Versions form.
New Version	Enter the name of the batch version.
Security	Select the restriction to be placed on the batch version.Values are 0–3, 0 is no security and 3 is full security.
Version Title	Enter the title of the batch version. The title describes the purpose of the batch version.

Note. On the Submit Job - Work With Batch Versions - Available Versions form, the number one is displayed in the Web Only column. This indicates that the batch version is a web only version and cannot be run from the Microsoft Windows client.

Converting Web Only Batch Versions

This section provides an overview of converting web only batch versions, lists the prerequisite, and discusses how to convert web only batch versions to Microsoft Windows batch versions.

Understanding Converting Web Only Batch Versions

A batch version created on the web client cannot run on the Microsoft Windows client. The batch version specifications do not reside on the enterprise server.

Convert batch versions to a Microsoft Windows batch version if you need to:

• Override specifications in the batch version.

• Copy the batch version from the web client.

• Ensure that the batch version exists on the deployment server.

Prerequisite

Before converting web only batch versions to Microsoft Windows batch versions, ensure that you create a batch version from the web client.

Converting Web Only Batch Versions to Microsoft Windows Batch Versions

Access the Object Management Workbench form.

1. In the project view, expand the project to which the batch version will be added.

2. Click the Objects node of the project and using the Search tab, locate the web only batch version.

3. Move the web only batch version into the project.

4. Click the web only batch version and click Check Out.

   The system copies the batch version specifications from the central objects of the relational database onto the local workstation. The environment definition in the VRENHV field of the Versions List (F983051) table is modified from the web environment to the Microsoft Windows environment.

5. Click the web only batch version again and click Check In.

   The system copies the batch version specifications from the local workstation back into the central objects relational database.

6. Advance the project through the development cycle.

7. Build a package and deploy it to the enterprise server and appropriate workstations.

   If batch versions are the only JD Edwards EnterpriseOne objects included in the project, you can skip the package build and submit the version specifications to the enterprise server using the Advanced option on the Form menu of the Version Prompting form.

8. Generate the batch version to HTML using the eGenerator.

   This is typically done by a system administrator using a machine defined as a generation machine.

   During generation, the web only flag is updated and the batch version is no longer defined as web only.

See JD Edwards EnterpriseOne Tools 8.97 Package Management Guide

See JD Edwards EnterpriseOne Tools 8.97 HTML Server Installation, Generating EnterpriseOne Serialized Objects