JD Edwards EnterpriseOne Tools

Development Tools: Batch Versions Guide

Release 8.98 Update 4

E14701-02

March 2011

JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide, Release 8.98 Update 4

E14701-02

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

List of Figures

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction to JD Edwards EnterpriseOne Batch Versions

- 1.1 JD Edwards EnterpriseOne Batch Versions Overview

- 1.2 JD Edwards EnterpriseOne Batch Versions Implementation

- 1.2.1 JD Edwards EnterpriseOne Batch Versions Implementation Steps

2 Understanding Batch Versions

- 2.1 Report Writing

- 2.2 Report Processing

- 2.3 Table Conversion Processing

- 2.4 Output Management

- 2.5 Report Components

- 2.5.1 Report Templates

- 2.5.2 Batch Versions

- 2.6 Batch Versions

- 2.6.1 Characteristics of Batch Versions

- 2.6.2 Batch Versions Created on the Web Client

- 2.7 JD Edwards Naming Conventions

3 Working with Batch Versions

- 3.1 Understanding Batch Versions

- 3.2 Submitting Batch Versions

- 3.2.1 Batch Version Submission

- 3.2.2 Work With Batch Versions Form

- 3.3 Changing Processing Options for the Batch Versions Application

- 3.3.1 Understanding Processing Options for the Batch Versions Application

- 3.3.2 Processing Options for the Batch Versions Application on the Microsoft Windows Client

- 3.3.2.1 Process

- 3.3.2.2 Report Definition

- 3.3.3 Changing Processing Options for the Batch Versions Application on the Microsoft Windows Client

- 3.3.4 Processing Options for the Batch Versions Application on the Web Client (P98305W)

- 3.3.4.1 Report Definition

- 3.3.4.2 Process

- 3.3.5 Changing Processing Options for the Batch Versions Application on the Web Client

4 Creating Batch Versions

- 4.1 Creating Batch Versions from the Microsoft Windows Client

- 4.1.1 Understanding Adding Batch Versions

- 4.1.2 Understanding Copying Batch Versions

- 4.1.3 Prerequisite

- 4.1.4 Forms Used to Create Batch Versions from the Microsoft Windows Client

- 4.1.5 Adding Batch Versions in the Batch Versions Application

- 4.1.6 Copying Batch Versions in the Batch Versions Application

- 4.1.7 Adding Batch Versions in Object Management Workbench

- 4.1.8 Copying Batch Versions in Object Management Workbench

- 4.2 Creating Batch Versions from the Web Client

- 4.2.1 Understanding Adding Batch Versions from the Web Client

- 4.2.2 Understanding Copying Batch Versions from the Web Client

- 4.2.3 Prerequisites

- 4.2.4 Forms Used to Create Batch Versions from the Web Client

- 4.2.5 Adding Batch Versions from the Web Client

- 4.2.6 Copying Batch Versions from the Web Client

5 Modifying Properties of Batch Versions

- 5.1 Understanding Modifying Properties of Batch Versions

- 5.2 Modifying Batch Version Properties from the Microsoft Windows Client

- 5.2.1 Understanding Changing Processing Options

- 5.2.2 Understanding Changing Data Selection and Data Sequencing

- 5.2.3 Prerequisites

- 5.2.4 Forms Used to Modify Properties of Batch Versions from the Microsoft Windows Client

- 5.2.5 Changing Processing Options for Batch Versions from the Microsoft Windows Client

- 5.2.6 Changing Data Selection and Data Sequencing for Batch Versions from the Microsoft Windows Client

- 5.3 Modifying Batch Version Properties from the Web Client

- 5.3.1 Understanding Changing Processing Options from the Web Client

- 5.3.2 Understanding Changing Data Selection and Data Sequencing from the Web Client

- 5.3.3 Prerequisites

- 5.3.4 Forms Used to Modify Properties of Batch Versions from the Web Client

- 5.3.5 Changing Processing Options for Batch Versions from the Web Client

- 5.3.6 Changing Data Selection and Data Sequencing for Batch Versions from the Web Client

- 5.4 Accessing Properties for Versions of Table Conversions

- 5.4.1 Forms Used to Access Properties for Versions of Table Conversions from the Microsoft Windows Client

- 5.4.2 Accessing Properties for Versions of Table Conversions from the Microsoft Windows Client

- 5.4.3 Accessing Data Selection for Versions of Table Conversions from the Web Client

- 5.5 Working with Version Detail

- 5.5.1 Understanding Version Detail

- 5.5.2 Prerequisite

- 5.5.3 Forms Used to Modify the Version Detail for Batch Versions

- 5.5.4 Modifying the Version Detail for Batch Versions

6 Working with Batch Version Specifications

- 6.1 Understanding Batch Version Specifications

- 6.2 Checking Out and Checking In Batch Versions from the Microsoft Windows Client

- 6.2.1 Understanding Checking Out and Checking In Batch Versions

- 6.2.2 Understanding Erasing the Check Out Record for Batch Versions

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

- 6.3 Copying Batch Version Specifications to an Enterprise Server

- 6.3.1 Understanding Copying Batch Version Specifications to an Enterprise Server

- 6.3.2 Forms Used to Copy Batch Version Specifications

7 Changing the Design of Batch Versions

- 7.1 Understanding Overriding Specifications

- 7.2 Overriding Specifications and Properties of Batch Versions

- 7.2.1 Understanding Overriding Specifications in Batch Versions

- 7.2.2 Understanding Overriding Properties for Versions of Table Conversions

- 7.2.3 Prerequisites

- 7.2.4 Overriding Specifications in Batch Versions

- 7.2.5 Changing the Properties of Versions for Table Conversions

8 Submitting Batch Versions

- 8.1 Understanding Batch Version Submission

- 8.1.1 Data Selection and Data Sequencing

- 8.1.2 Processing Options

- 8.1.3 Advanced Option Overrides

- 8.1.4 Printer Selections

- 8.1.5 CSV Files

- 8.1.6 OSA Interface

- 8.2 Submitting Batch Versions from the Microsoft Windows Client

- 8.2.1 Understanding Batch Versions Submitted on the Server from the Microsoft Windows Client

- 8.2.2 Understanding Batch Versions Submitted Locally from the Microsoft Windows Client

- 8.2.3 Forms Used to Submit Batch Versions from the Microsoft Windows Client

- 8.2.4 Running Batch Versions from the Microsoft Windows Client

- 8.2.4.1 Overriding Advanced Options

- 8.2.4.2 Overriding Data Selection and Data Sequencing

- 8.2.4.3 Submitting the Batch Version

- 8.2.4.4 Overriding Printer Selection

- 8.2.4.5 Overriding Print Properties

- 8.2.4.6 Overriding Document Setup

- 8.2.4.7 Overriding Advanced Properties

- 8.3 Submitting Batch Versions from the Web Client

- 8.3.1 Understanding Batch Versions Submitted from the Web Client

- 8.3.2 Forms Used to Submit Batch Versions from the Web Client

- 8.4 Submitting Table Conversions from the Microsoft Windows Client

- 8.4.1 Understanding Table Conversions Submitted from the Microsoft Windows Client

- 8.4.2 Forms Used to Submit Table Conversions from the Microsoft Windows Client

- 8.4.3 Running Table Conversions from the Microsoft Windows Client

- 8.5 Submitting Table Conversions from the Web Client

- 8.5.1 Understanding Table Conversions Submitted from the Web Client

- 8.5.2 Forms Used to Submit Table Conversions from the Web Client

- 8.5.3 Running Table Conversions from the Web Client

- 8.6 Submitting at the Command Line

- 8.6.1 Submitting Batch Versions Using runube

- 8.6.2 Submitting Batch Versions Using runube with Unix and iSeries

- 8.6.2.1 Prompt for User ID and Password

- 8.6.2.2 Create a Text File for User ID and Password

- 8.6.3 Submitting Batch Versions Using runubexml

9 Reviewing Batch Version Processing

- 9.1 Understanding Resources for Reviewing Reports

- 9.2 Using the Submitted Jobs Application

- 9.2.1 Submitted Jobs

- 9.2.2 Submitted Jobs For Other Users

- 9.2.3 Submitted Jobs Options

- 9.3 Using Execution Details (P986114A) Utilities

- 9.3.1 Understanding Batch Processing Utilities

- 9.3.1.1 Dynamic Logging

- 9.3.1.2 Introspection

- 9.3.1.3 Audit Data

- 9.3.1.4 Verifying Statuses

- 9.3.1.5 Report Interconnects

- 9.3.1.6 Troubleshooting Batch Process Utilities

- 9.3.1.7 Accessing Execution Details Utilities

- 9.4 Accessing BrowsER for Batch Versions

- 9.4.1 Accessing BrowsER

- 9.4.2 Forms Used to Access BrowsER

- 9.5 Reviewing the Cover Page

- 9.5.1 The Cover Page

- 9.5.1.1 Report Properties

- 9.5.1.2 System Properties

- 9.5.1.3 Printer Properties

- 9.5.1.4 Processing Options

- 9.5.1.5 Report Interconnects

- 9.6 Generating and Reviewing Logs from the Microsoft Windows Client

- 9.6.1 Understanding Logs for Batch Jobs

- 9.6.2 Forms Used to Generate Logs from the Microsoft Windows Client

- 9.7 Generating and Reviewing Logs from the Web Client

- 9.7.1 Understanding Logs Generated from the Web Client

- 9.7.2 Forms Used to Generate Logs from the Web Client

Glossary

Index

List of Figures

- 4-1 Version Add form

- 4-2 Version Copy form

- 4-3 Submit Job - Add Version form

- 4-4 Submit Job - Copy Version form

- 5-1 Version Detail form

- 8-1 Advanced Version Prompting form

- 8-2 Version Prompting form

- 8-3 Report Output Destination form

- 8-4 Printer Selection form

- 8-5 Table Conversion Prompting form

- 8-6 Submit Job - Table Conversion Prompting form

Preface

Welcome to the JD Edwards EnterpriseOne Tools Development Tools: Batch Versions Guide.

Audience

This guide is intended for report and analytics administrators who are responsible for creating and modifying batch versions.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

You can access related documents from the JD Edwards EnterpriseOne Release Documentation Overview pages on My Oracle Support. Access the main documentation overview page by searching for the document ID, which is 876932.1, or by using this link:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=876932.1

To navigate to this page from the My Oracle Support home page, click the Knowledge tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome Center, Release Information Overview.

This guide contains references to server configuration settings that JD Edwards EnterpriseOne stores in configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, and so on). Beginning with the JD Edwards EnterpriseOne Tools Release 8.97, it is highly recommended that you only access and manage these settings for the supported server types using the Server Manager program. See the Server Manager Guide on My Oracle Support.

Conventions

The following text conventions are used in this document:

Convention

Meaning

Bold

Indicates field values.

Italics

Indicates emphasis and JD Edwards EnterpriseOne or other book-length publication titles.

Monospace

Indicates a JD Edwards EnterpriseOne program, other code example, or URL.

1 Introduction to JD Edwards EnterpriseOne Batch Versions

This chapter contains the following topics:

- Section 1.1, "JD Edwards EnterpriseOne Batch Versions Overview"

- Section 1.2, "JD Edwards EnterpriseOne Batch Versions Implementation"

1.1 JD Edwards EnterpriseOne Batch Versions Overview

Oracle JD Edwards EnterpriseOne Batch Versions is a tool that you use to create and process versions of report templates.

You can use Batch Versions to:

- Create batch versions.

- Define processing options, data selection and data sequencing, and review version detail.

- Check out batch versions, check in batch versions, erase the check out, and copy version specifications to the enterprise server.

- Modify batch versions without changing the report template specifications.

- Submit batch versions for processing and override processing options, data selection, and data sequencing at runtime.

- Review batch version processing by using BrowsER, the report cover page, and logs for reporting.

1.2 JD Edwards EnterpriseOne Batch Versions Implementation

This section provides an overview of the steps that are required to implement Batch Versions.

1.2.1 JD Edwards EnterpriseOne Batch Versions Implementation Steps

In the planning phase of the implementation, take advantage of all JD Edwards sources of information, including the installation guides and troubleshooting information.

This table lists the steps for the Batch Versions implementation.

- Using Oracle's JD Edwards EnterpriseOne Security Workbench, set up permissions to access and use JD Edwards EnterpriseOne Object Management Workbench (OMW) and the JD Edwards EnterpriseOne Batch Versions application.
See "Using Security Workbench," "Managing Application Security" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

- Add yourself to the system in a developer role so that you have permissions to create and modify JD Edwards EnterpriseOne objects.
See "Configuring User Roles and Allowed Actions," "Setting Up User Roles" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

- Set up permissions to create OMW projects.
See "Configuring User Roles and Allowed Actions," "Setting Up Allowed User Actions" in theJD Edwards EnterpriseOne Tools Object Management Workbench Guide.

- Set up activity rules to allow you to promote projects in OMW.
See "Configuring Activity Rules" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

- Set up save locations to enable you to save JD Edwards EnterpriseOne objects that are not ready to be checked in.
See "Configuring Object Save Locations" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

- Set up default locations and printers.
See "Working with Report Printing Administration" in the JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

2 Understanding Batch Versions

This chapter contains the following topics:

- Section 2.1, "Report Writing"

- Section 2.2, "Report Processing"

- Section 2.3, "Table Conversion Processing"

- Section 2.4, "Output Management"

- Section 2.5, "Report Components"

- Section 2.6, "Batch Versions"

- Section 2.7, "JD Edwards Naming Conventions"

2.1 Report Writing

Oracle JD Edwards EnterpriseOne provides reports across many systems to meet your business needs, including:

- JD Edwards EnterpriseOne Financial Management

- JD Edwards EnterpriseOne Human Capital Management

- JD Edwards EnterpriseOne Logistic

- JD Edwards EnterpriseOne Manufacturing

JD Edwards EnterpriseOne reports can be processed and viewed in these formats:

- Online in PDF

- In hardcopy
Report can be sent to a printer.

- In a spreadsheet program
Reports can be exported to a spreadsheet program.

To help you meet all of your business needs, you can create versions of these reports. Using the JD Edwards EnterpriseOne Batch Versions application on either the Microsoft Windows client (P98305) or the web client (P98305W), you can create versions to present specific information that is vital to your business.

2.2 Report Processing

You cannot process a report without a batch version. From the Microsoft Windows client, batch versions are submitted for processing and can be processed either locally or on the server. Typically, servers are faster, so processing on a server is more efficient. From the web client, batch versions are submitted on the server only. Once submitted, a batch version runs without user interaction. You do not interact with the report again until processing is complete.

Once you have submitted a batch version for processing, you have no control over the flow of the attached logic. You must make changes to the flow of logic in Oracle's JD Edwards EnterpriseOne Report Design Aid (RDA) and resubmit the batch version.

2.3 Table Conversion Processing

You run table conversions by submitting batch versions. Table conversions are a type of batch process that enables you to rapidly manipulate the data in tables. Like batch applications, table conversions include a template and associated versions. You can override some of the properties within a version at runtime.

This table describes the conversion types used by the Oracle's JD Edwards EnterpriseOne Table Conversion tool to manipulate data:

Conversion Type

Description

Data Conversion

Enables you to transfer or copy data from an input table or business view into output tables using the logic necessary to perform the transfer.
You can also use Data Conversion to update records in a table or business view.

Data Copy

Enables you to copy tables from one data source or environment to another data source or environment, when the tables are identical.

Data Copy with Table Input

Enables you to copy tables based on information from an input table.
For example, the input table might provide information about which tables are copied, the location to where they are copied, and so on.

Batch Delete

Enables you to delete records from a table or business view.

See "Converting Tables" in the JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

2.4 Output Management

Output management refers to the different output options that you have available for reports, such as:

- File types
You can output reports to different file types such as, PDF, OSA, and CSV.

- Printers
You can output a report to multiple printers, locally or globally. You can send versions of a report to different printer drawers or to printers across the country.

- Forms and paper sizes
You can output reports to forms and define custom paper sizes.

JD Edwards EnterpriseOne accommodates simple output processes such as viewing a report online or sending it to a network printer.

SeeJD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

2.5 Report Components

A report exists as a set of specifications that are read by the JD Edwards EnterpriseOne batch engine for processing. You can create variations of a report template using batch versions. The first step in creating a report is to create a report object within JD Edwards EnterpriseOne. This report is actually a template from which multiple versions can be created.

See JD Edwards EnterpriseOne Tools Development Tools: Report Design Aid Guide.

2.5.1 Report Templates

Report templates are the master specifications created in RDA. These specifications describe the report to the batch engine and define how the data is selected, sorted, displayed, and formatted.

RDA includes a Report Director that you can use to guide you through the report development process. You begin the report development process by selecting:

- Sections to include in the report.

- An appropriate business view.

- Fields for the section layout.

- Records to be included in the report.

2.5.2 Batch Versions

Batch versions read the master specifications from the report template. The sections and fields that you select in the report template appear in the associated batch versions. However, batch versions typically differ slightly from the report template. You can define different data selection, data sequencing, and processing options for each batch version.

There are also several report specifications that can be overwritten at the version level, including:

- Layout

- Data selection

- Event rules

- Database output

- Data sequencing

Batch versions enable you to preserve template integrity while providing custom processing to meet a specific business need. Instead of creating a separate report template to provide multiple variations of a report, you can create one report template with multiple batch versions. For example, you might design a monthly variance report that contains totals for the entire company. If you need to run a quarterly variance report that includes only data for the Western region, you can create a version of the report template and define data selection to meet the requirement.

Batch versions process the specifications read from the report template and any changes that are overwritten in the version. Batch versions first read the master specifications from the report template, then override these specification with the version specifications. You can create additional batch versions by either adding a new version or copying an existing version.

2.6 Batch Versions

In JD Edwards EnterpriseOne, the design for report templates and batch processes are stored in the report template specifications. Batch versions are variations on the report template. They use all of the same report definition information as the template but can also contain changes to the way the report is processed or displayed. Depending on how security is applied to the JD Edwards EnterpriseOne applications, end users can select different batch versions or create new batch versions based on business requirements.

Versions are a powerful and convenient way to modify the behavior of reports. Typically, administrators control the creation, modification, and location of the initial batch version files. When you upgrade JD Edwards EnterpriseOne or a specific application to a new release level, you can apply the existing batch versions without additional modification.

When you process a batch application (that is, when you submit a batch job) you must use a batch version. Depending on how the report was designed, when you submit the batch version you might have the option to override:

- Processing option values

- Data sequencing

- Data selection

- Default locations

For example, you have a report that prints financial information that is required by two different audiences: an American subsidiary and a French subsidiary. For the American subsidiary, you can create a batch version that displays financial information in U.S. dollars for a specific time period and formats the report for American-sized paper. For the French subsidiary, you can create a version that displays financial information in euros for a different time period and formats the report for European-sized paper. You can also display additional information in the report by inserting additional fields into the batch version.

2.6.1 Characteristics of Batch Versions

This table defines the characteristics of batch versions:

Characteristics

Definition

Data sequencing defined at the version level.

For example, you can create multiple batch versions of a single report template: one version might sort checks by date, one by check number, one by address number, and one that sorts checks by amount.

Data selection defined at the version level.

For example, you can specify which records to fetch for each version, such as Business Unit 10-30 and 70, or all address book records where Category 1 is equal to North.

Additions or overrides in the version.

You can modify batch versions to add or override functionality attached to the section of a report template. At the section level, you can override section layout, data selection, data sequencing, event rules, and database output. You cannot delete sections in a version that exist in the report template, however, you can hide unwanted sections.

A specific set of processing option values.

For example, you can set a general ledger post processing option value to print a different account number format on the report.

Change functionality.

For example, you can set processing options to purge records to a history file after a report runs.

Change input parameters.

For example, you can set processing options to specify which category code to use when processing a report and you can define different report interconnect values for different batch versions.

Define data.

For example, you can set a processing option to define the fiscal year for which you want to run a report. You can also define the number of aging days in an accounts receivable aging report.

Additional detail sections.

For example, you can include additional detail sections, each with a different business view attached.

2.6.2 Batch Versions Created on the Web Client

You can create new batch versions of a report on the web client. You can use the Add and Copy options on the Work With Batch Versions - Available Versions form to create a batch version. To change the data selection, data sequencing, or processing options of a version, select Data Selection, Data Sequencing, or Processing Options from the Row menu.

You cannot create a new version, or copy an existing version, of a table conversion on the web client.

2.7 JD Edwards Naming Conventions

To provide consistency for developers and users, all JD Edwards EnterpriseOne objects follow standard naming conventions. The naming conventions require that each object, such as a table, report, interactive application, or menu, has a unique name. The naming conventions help you identify object types and help prevent users from creating objects with duplicate names.

See "Understanding JD Edwards EnterpriseOne Naming Conventions" in the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide.

3 Working with Batch Versions

This chapter contains the following topics:

- Section 3.1, "Understanding Batch Versions"

- Section 3.2, "Submitting Batch Versions"

- Section 3.3, "Changing Processing Options for the Batch Versions Application"

3.1 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.

3.2 Submitting Batch Versions

This section discusses:

- Batch version submission.

- The Work With Batch Versions form.

3.2.1 Batch Version Submission

If batch versions are associated with a form in an interactive application, you can access the versions for viewing and printing from the Reports menu of the form. Batch versions of those reports are available on menus.

In most cases, you submit batch versions to an enterprise server, which can more efficiently handle the processing. The JD Edwards EnterpriseOne environment that you log on to specifies where the batch versions run, although you can override this location when you submit the batch version. When you submit the batch job to the server, you can preview the report and use JD Edwards EnterpriseOne Work With Servers (P986116) application to monitor the progress of the job in the queue.

When you submit a batch version to the enterprise server, if the report specifications do not currently reside on the workstation, the central objects data source (server) performs a Just-In-Time Installation (JITI) to copy the specifications to the workstation. After the JITI, the workstation continues with the submission of the report to the enterprise server.

3.2.2 Work With Batch Versions Form

The Work With Batch Versions - Available Versions form is the entry point to managing batch versions. This table describes the methods of accessing the Work With Batch Versions - Available Versions form:

Access

Description

From any menu that includes a batch application

Select the batch application and then select Prompt for Versions from the Edit menu.
Right-click the batch application and select Prompt for Versions from the pull-down menu. If no versions are associated with the batch application, you must copy or add a version and run that version as explained in this section.

From the Microsoft Windows client

From JD Edwards Solution Explorer, select Report Versions from the Tools menu.

From the web client

From the EnterpriseOne Menu, select Submit Job

3.3 Changing Processing Options for the Batch Versions Application

This section provides an overview of processing options for the JD Edwards EnterpriseOne Batch Versions application on the Microsoft Windows client (P98305) and the Batch Versions application on the web client (P98305W) and discusses how to change processing options for these applications.

3.3.1 Understanding Processing Options for the Batch Versions Application

Not all applications have processing options attached. If an application has processing options, and you have permissions to do so, you can change the processing option values by right-clicking an application task to access the Prompt For menu. If the Values option on the Prompt For menu is not active, either you do not have permissions to modify the processing options, or no processing options exist for the application.

There are different processing options for the Batch Versions application on the Microsoft Windows client (P98305) and the Batch Versions application on the web client (P98305W).

3.3.2 Processing Options for the Batch Versions Application on the Microsoft Windows Client

Processing options for the Batch Versions application on the Microsoft Windows client (P98305) enable you to specify default processing for batch versions and report definitions.

3.3.2.1 Process

1. Confirmation Box

Enter a value to enable or disable the overwrite/delete location specifications confirmation box. If you enable the confirmation box, it appears when JD Edwards EnterpriseOne is about to overwrite or delete specifications on the local machine. For example, when enabled, the confirmation box appears when you check out a batch version.

Y: Enable Confirmation Box

1: Enable Confirmation Box

N: Disable Confirmation Box

0: Disable Confirmation Box

2. Schedule Job

Enter a value (or leave the field blank) to indicate whether users are allowed to schedule their batch version jobs. If users are not allowed to schedule their batch jobs, the jobs run as soon as they submit their batch versions.

0: Do not allow scheduling of Batch Job

1: Schedule Batch Job when submitting

2: Always schedule Batch Job when submitting

Blank: Do not allow scheduling of Batch Job

3. Push Specs

Enter a value (or leave the field blank) to indicate whether the user can push version specifications from the Work With Batch Versions form.

1: Allow for the pushing of version specifications from the Work With Batch Versions form.

Blank: Do not allow the user to push version specifications from the Work With Batch Versions form.

3.3.2.2 Report Definition

1. Report Definition Submission Advanced Options Security

Enter a value (or leave the field blank) to indicate which options on the Advanced Options form are available to users when they submit report definitions.

Blank or 0: Allow users to override the option to submit the version with a report definition.

1: Do not allow users to override the option to submit the version with a report definition.

Blank or 0: Allow users to select the option to choose a report definition from a list of all available report definitions for the version being submitted.

1: Do not allow users to select the option to choose a report definition from a list of all available report definitions for the version being submitted.

3.3.3 Changing Processing Options for the Batch Versions Application on the Microsoft Windows Client

In JD Edwards Solution Explorer, select the Report Management menu (GH9111) and locate Batch Versions.

1. Right-click Batch Versions, select Prompt For, and then select Values.

2. On the Processing Options template, complete the selections on the Process tab.

3. Complete the selections on the Report Definition tab and click OK.

3.3.4 Processing Options for the Batch Versions Application on the Web Client (P98305W)

Processing options for the Batch Versions application on the web client (P98305W) enable you to specify default processing for batch versions and report definitions.

3.3.4.1 Report Definition

1. Report Definition Submission Advanced Options Security

Enter a value (or leave the field blank) to indicate which options on the Advanced Options form are available to users when they submit report definitions.

Blank or 0: Allow users to override the option to submit the version with a report definition.

1: Do not allow users to override the option to submit the version with a report definition.

Blank or 0: Allow users to select the option to choose a report definition from a list of all available report definitions for the version being submitted.

1: Do not allow users to select the option to choose a report definition from a list of all available report definitions for the version being submitted.

3.3.4.2 Process

User Action Tracking using Object Management Workbench (OMW) Logging

1. OMW Tracking Enabled

Blank or 0 : No user action tracking using OMW

1: Enable user action tracking using OMW

2. OMW Project

If Action Tracking through OMW logging selected:

Project Name: Enter the OMW Project to which the Batch Version should be added.

Blank: The Batch Version should be added to the Users Default project.

Note:
OMW integration occurs automatically when using the Batch Versions application on the Microsoft Windows client (P98305). For this reason, processing options for OMW Action Tracking are not necessary for the Microsoft Windows version of the application.

3.3.5 Changing Processing Options for the Batch Versions Application on the Web Client

In JD Edwards EnterpriseOne Menu, select the Report Management menu (GH9111) and locate Batch Versions.

1. Right-click Batch Versions, select Prompt For, and then select Values.

2. On the Processing Options template, complete the selections on the Report Definition tab.

3. Complete the selections on the Process tab and click OK.

4 Creating Batch Versions

This chapter contains the following topics:

- Section 4.1, "Creating Batch Versions from the Microsoft Windows Client"

- Section 4.2, "Creating Batch Versions from the Web Client"

4.1 Creating Batch Versions from the Microsoft Windows Client

This section provides overviews of adding Oracle JD Edwards EnterpriseOne 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.

4.1.1 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 JD Edwards EnterpriseOne Report Design Aid (RDA) using the Report Director. You can create additional batch versions from the 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:

Prompting Options

Description

No Processing Options

This option indicates that the report should run as if all processing option values are NULL or 0.

Blind Execution

The system does not present the processing option template to the user. You define the default values that the system uses at runtime and the user cannot modify these default values.

Prompt for Values

The system presents the processing option template to the user. The user can then enter values in fields included on the processing option template to affect the results of the report.

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 JD Edwards EnterpriseOne Security Workbench (P00950) application. This table describes the batch version security options:

Security Options

Description

No Security

Anyone can design, change processing option values, change detail values, check in, check out, install, transfer, copy, delete, or run the version.

Medium Security

Only the user that last modified the batch version can design, change processing option values, change detail values, check in, check out, or delete the version.
Anyone can install, transfer, copy, or run the version.

Medium to Full Security

Only the user that last modified the batch version can design, change processing option values, change detail values, check in, check out, transfer, delete, or run the version.
Anyone can install or copy the version.

Full Security

Only the user that last modified the batch version can design, change processing option values, change detail values, check in, check out, install, transfer, copy, delete, or run the version.

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.

4.1.2 Understanding Copying Batch Versions

You can copy existing batch versions 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.

4.1.3 Prerequisite

Before creating batch versions, ensure that you create a batch application.

4.1.4 Forms Used to Create Batch Versions from the Microsoft Windows Client

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Version Add

W98305G

Click Add on the Work With Batch Versions - Available Versions form.

Enter the version name, title, prompting options, security, job queue, version detail, and select if you want to print the cover page.

Version Copy

W98305F

Select a batch version and click Copy on the Work With Batch Versions - Available Versions form.

Enter the version name, title, and security.

4.1.5 Adding Batch Versions in the Batch Versions Application

Access the Version Add form.

Figure 4-1 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.

4.1.6 Copying Batch Versions in the Batch Versions Application

Access the Version Copy form.

Figure 4-2 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.

4.1.7 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" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

4.1.8 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.

4.2 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.

4.2.1 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.

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.

4.2.2 Understanding Copying Batch Versions from the Web Client

You can copy existing batch versions 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.

Note:
You cannot copy table conversion versions from the web client.

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

4.2.3 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.

4.2.4 Forms Used to Create Batch Versions from the Web Client

Form Name

FormID

Navigation

Usage

Submit Job - Work With Batch Versions - Available Versions

W98305WA

EnterpriseOne Menu, Submit Job

Enter the name of a batch application and select from available batch versions.

Submit Job - Add Version

W98305WH

Click Add on the Work With Batch Versions - Available Versions form.

Enter the version name, title, prompting options, and security.

Submit Job - Copy Version

W98305WK

Select a batch version and click Copy on the Work With Batch Versions - Available Versions form.

Enter the version name, title, and security.

4.2.5 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.

Figure 4-3 Submit Job - Add Version form

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 processing 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:
Unlike versions that you add from the Microsoft Windows client, you do not have to check in versions that you add from the web client to make them available to the enterprise. Versions added from the web client are checked in for you automatically.

4.2.6 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.

Figure 4-4 Submit Job - Copy Version form

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:
Unlike versions that you add from the Microsoft Windows client, you do not have to check in versions that you add from the web client to make them available to the enterprise. Versions added from the web client are checked in for you automatically.

5 Modifying Properties of Batch Versions

This chapter contains the following topics:

- Section 5.1, "Understanding Modifying Properties of Batch Versions"

- Section 5.2, "Modifying Batch Version Properties from the Microsoft Windows Client"

- Section 5.3, "Modifying Batch Version Properties from the Web Client"

- Section 5.4, "Accessing Properties for Versions of Table Conversions"

- Section 5.5, "Working with Version Detail"

5.1 Understanding Modifying Properties of Batch Versions

All of these properties can be modified from the Oracle JD Edwards EnterpriseOne Work With Batch Versions form and the Batch Version Design form:

- Processing option values.

- Data selection.

- Data sequencing.

- Properties of table conversion versions.

- Version detail.

When you modify these properties, the modifications remain with the batch version until they are modified again.

You can also modify these same properties at runtime. The difference is that properties modified at runtime do not remain with the batch version, these modifications affect the current run only.

5.2 Modifying Batch Version Properties from the Microsoft Windows Client

This section provides overviews of changing processing options and changing data selection and data sequencing, lists the prerequisites, and discusses how to:

- Change processing options for batch versions from the Microsoft Windows client.

- Change data selection and data sequencing for batch versions from the Microsoft Windows client.

5.2.1 Understanding Changing Processing Options

You can change the processing option values for an existing batch version to meet your business needs. You can change the processing option values at runtime or from the Row menu on the Work With Batch Versions-Available Versions form. Use the Row menu when you want to define default values to execute blindly. For example, you can change the processing option values for a batch version of an address book report to select a search type of C for customers. If you also select to execute the processing options blindly, the processing option template does not appear at runtime. Therefore, the user does not have the opportunity to change the search type value; only customer records display in the report.

Not all batch versions have processing options associated with them; for example, a list of addresses might not require special prompting. If processing options do not exist, or if you have been secured from changing processing options, a message box appears when selecting Processing Options from the Row menu on the Work With Batch Versions-Available Versions form. Otherwise, the Processing Options form appears for the application.

Processing option values are stored in the Versions List (F983051) table for each batch version run. Unlike other changes to versions, changes to processing option values do not require you to check in or check out the version. Anyone who uses that version after you make the change is affected by the new processing option values. You can define different processing options values for individual versions and set the processing options to process as a blind execution.

Note:
You should not modify versions that begin with ZJDE or XJDE. These versions are owned by JD Edwards EnterpriseOne and could be modified in future updates and releases. You should either copy these versions or create new versions if you need to change any values, including the version name, description, prompting options, security, and processing options.

5.2.2 Understanding Changing Data Selection and Data Sequencing

You can attach data selection to batch versions to narrow the range of the data. For example, you can define the data selection for a batch version to display only customers from New York. You can define another batch version to display only customers from Paris.

You can also sequence how you want the data presented in the report. For example, you can place the search type field first, followed by the address number and then the employee name.

You can select and sequence the data from one of two places, either from the Work With Batch Versions form, as explained here, or from the Version Prompting form at runtime.

For versions of table conversions, you can change the data selection from the Row exit and at runtime from the web client.

5.2.3 Prerequisites

Before you modify properties of batch versions from the Microsoft Windows client, ensure that you:

- Identify a batch application that has processing options attached.

- Check out the batch version to modify data selection and data sequencing.

5.2.4 Forms Used to Modify Properties of Batch Versions from the Microsoft Windows Client

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

5.2.5 Changing Processing Options for Batch Versions from the Microsoft Windows Client

Access the Work With Batch Versions - Available Versions form.

1. Locate and select a batch version that includes processing options.

2. From the Row menu, select Processing Options.

3. Select each tab to view and change information on that tab.
If multiple tabs exist and you cannot see all of them, left and right arrow buttons appear on the form. Click the arrow buttons to view additional tabs. Use the scroll bar to view additional processing options on a tab.

4. Change the processing option values as appropriate, and click OK.

5.2.6 Changing Data Selection and Data Sequencing for Batch Versions from the Microsoft Windows Client

Access the Work With Batch Versions - Available Versions form.

1. In the detail area, locate and select a batch version that is checked out and with which you want to work.

2. From the Row menu, select either the Data Selection or Data Sequencing option.
When you are working with table conversion batch applications, the Data Selection and Data Sequencing options are unavailable because they do not apply to table conversions.

3. To make the changes available to the enterprise, check in the version.
If you do not check the batch version in, the changes affect only the batch version on the local workstation. If you do not want to check in the version, erase the checkout so that others can check out the version.

5.3 Modifying Batch Version Properties from the Web Client

This section provides overviews of changing processing options from the web client and changing data selection and data sequencing from the web client, lists the prerequisites, and discusses how to:

- Change processing options of batch versions from the web client.

- Change data selection and data sequencing of batch versions from the web client.

5.3.1 Understanding Changing Processing Options from the Web Client

If you are working with batch versions from a web client, you can change the processing options of batch versions from both the Submit Jobs - Work With Batch Versions - Available Versions form and at runtime.

5.3.2 Understanding Changing Data Selection and Data Sequencing from the Web Client

You can select and sequence the data from one of two places, either from the Work With Batch Versions form, as explained here, or from the Version Prompting form at runtime.

5.3.3 Prerequisites

Before you modify properties of batch versions from the web client, ensure that you identify a batch application that has processing options attached.

5.3.4 Forms Used to Modify Properties of Batch Versions from the Web Client

Form Name

FormID

Navigation

Usage

Submit Job - Work With Batch Versions - Available Versions

W98305WA

EnterpriseOne Menu, Submit Job

Enter the name of a batch application and select from available batch versions.

5.3.5 Changing Processing Options for Batch Versions from the Web Client

Access the Submit Job - Work With Batch Versions - Available Versions form.

1. Locate and select a batch version.

2. From the Row menu, select Processing Options.

3. Select each tab to view and change information on that tab.

4. Change the processing option values as appropriate, and click OK.

5.3.6 Changing Data Selection and Data Sequencing for Batch Versions from the Web Client

Access the Submit Job - Work With Batch Versions - Available Versions form.

1. Locate and select a batch version.

2. From the Row menu, select either Data Selection or Data Sequencing.

3. Change the data selection and data sequencing as appropriate, and click OK.
You do not need to check the version in to make these changes available to the enterprise; the changed version is checked in automatically.

Note:
There is one situation when the changed version will not be checked in. In this scenario, an administrator has updated the data selections or data sequencing options (or both) in central objects (such as with an OMW transfer), but has not yet deployed a package to update the users' specifications. Under these circumstances, any modifications that you make to the data selections or data sequencing options will not be updated to central objects. However, your local version will retain your modifications until the new version is deployed.

5.4 Accessing Properties for Versions of Table Conversions

You can access version properties from the Table Conversion Prompting form or from the Work With Batch Versions - Available Versions form. Properties for versions of table conversions cannot be modified from the web client

This section discusses how to:

- Access properties for versions of table conversions from the Microsoft Windows client.

- Access data selection for versions of table conversions from the web client.

See "Converting Tables" in the JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

5.4.1 Forms Used to Access Properties for Versions of Table Conversions from the Microsoft Windows Client

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a table conversion template and select from available batch versions.

5.4.2 Accessing Properties for Versions of Table Conversions from the Microsoft Windows Client

Access the Work With Batch Versions - Available Versions form.

1. In the detail area, locate and select a version that is checked out and with which you want to work.

2. From the Row menu, select Properties.
This menu selection is only enabled for table conversions.

3. To make changes available to the enterprise, check in the version.
The changes that you make affect only the version on the local workstation. If you do not want to check in the version, erase the checkout so that others can check out the version.

5.4.3 Accessing Data Selection for Versions of Table Conversions from the Web Client

Access the Submit Job - Work With Batch Versions - Available Versions form.

1. Enter a table conversion name in the Batch Application field.

2. Click Find to locate the available versions.

3. Select a version and select Data Selection from the Row menu.
This data selection definition remains with the version for the user who changed it until either the user modifies the data selection again or the version is regenerated to HTML.

5.5 Working with Version Detail

This section provides an overview of version detail, lists the prerequisite, and discusses how to modify the version detail for batch versions.

5.5.1 Understanding Version Detail

Use version detail to review information about a version, such as how it differs from the master report template and how processing options are processed. From Version Detail on the Microsoft Windows client you can select to:

- Print a cover page with the report.
The cover page option is not available for versions of table conversions.

- Print the report immediately every time that the batch version is processed.

You can review Version Detail for batch versions from the web client but you cannot modify any of the options.

5.5.2 Prerequisite

Before you modify the version detail of batch versions, ensure that you check out the batch version.

5.5.3 Forms Used to Modify the Version Detail for Batch Versions

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Version Detail

W98305E

Select Version Detail from the Row menu of the Work With Batch Versions - Available Versions form.

Review and modify detail information regarding the batch version.

5.5.4 Modifying the Version Detail for Batch Versions

Access the Version Detail form.

Figure 5-1 Version Detail form

Application

The name of the associated batch application. This information cannot be changed.

Version

The name of the batch version selected. This information cannot be changed.

Version Title

Modify the title of the batch version selected.

Prompting

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. This field is enabled only if processing options are attached to the associated report template. You must have permissions to modify this field.

Security

Select the restriction to be placed on the batch version. Values are 0–3, 0 is no security and 3 is full security. You must have permissions to modify this field.

Version Detail

Enter the functionality differences between the batch version and the associated batch application. This information can be modified.

Print Cover Page

Select this option if you want to print a cover page with the batch version. This option is not available for versions of table conversions.

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.

Job Queue

Select the queue to which the batch version is submitted. When the Job Queue field is left blank, the system reads the setting in the jde.ini on the enterprise server. If the job is submitted to an iSeries, the system looks to the user profile to determine the job queue. You must have permissions to modify this field.

Client Platform

Select the category code associated with the F983051 table.

Application Type

Indicates the type of application. UBE stands for Universal Batch Engine. This field is populated by the system and cannot be changed.

Version Mode

Indicates that the version is associated with a batch application. This field is populated by the system and cannot be changed.

Processing Options

The name of the processing option template attached to the batch application. This field is populated by the system and cannot be changed.

Created By

The ID of the user who created the batch version. This field is populated by the system and cannot be changed.

Path Code

The path code where the batch version was created. This field is populated by the system and cannot be changed.

Location

The machine name where the batch version was created. This field is populated by the system and cannot be changed.

Last Modified By

The ID of the user who last modified the batch version. This field is populated by the system and cannot be changed.

Checked Out

Indicates whether the batch version is checked out. This field is populated by the system and cannot be changed.

On Server

Indicates whether the batch version specifications exist on the server. This field is populated by the system and cannot be changed.

Last Changed

The date that the batch version was last modified. This field is populated by the system and cannot be changed.

Server Update

The date that the batch version was last checked in. This field is populated by the system and cannot be changed.

Last Executed

The date that the batch version was last run. This field is populated by the system and cannot be changed.

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

6 Working with Batch Version Specifications

This chapter contains the following topics:

- Section 6.1, "Understanding Batch Version Specifications"

- Section 6.2, "Checking Out and Checking In Batch Versions from the Microsoft Windows Client"

- Section 6.3, "Copying Batch Version Specifications to an Enterprise Server"

6.1 Understanding Batch Version Specifications

Oracle JD Edwards EnterpriseOne 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.

6.2 Checking Out and Checking In Batch Versions from the Microsoft Windows Client

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.

6.2.1 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.

6.2.2 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.

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

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Advanced Operations

W98305J

Select a batch version and Select Advanced from the Row menu of the Work With Batch Versions - Available Versions form.

Check in, check out, and erase the check out of batch versions.

6.3 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.

6.3.1 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.

6.3.2 Forms Used to Copy Batch Version Specifications

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A
or W98305WA

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Version Prompting

W98305D
or W98305WD

Select a batch version and click Select on the Work With Batch Versions - Available Versions form.

Access advanced options.

Advanced Version Prompting

W98305I
or W98305WI

Click Advanced on the Form menu of the Version Prompting form.

Select the Submit Version Specifications Only option and override the location, if required.

Version Prompting

W98305D
or W98305WD

Click OK on the Advanced Version Prompting form.

Submit batch versions specifications to an enterprise server.

7 Changing the Design of Batch Versions

This chapter contains the following topics:

- Section 7.1, "Understanding Overriding Specifications"

- Section 7.2, "Overriding Specifications and Properties of Batch Versions"

7.1 Understanding Overriding Specifications

You can change Oracle JD Edwards EnterpriseOne batch versions without changing the associated report template or table conversion. When you change the specifications at the version level, you should include a description of the modifications in the Version Detail field on the Version Detail form. The description should include the differences between the report template, or table conversion, and the version specifications.

7.2 Overriding Specifications and Properties of Batch Versions

This section provides overviews of overriding specifications in batch versions and overriding properties for versions of table conversions, lists prerequisites, and discusses how to:

- Override specifications in batch versions.

- Change the properties of versions for table conversions.

7.2.1 Understanding Overriding Specifications in Batch Versions

Override the report specifications at the version level to change the design of a batch version. The changes you make to the specifications of the batch version do not affect the report template or any other batch version associated with the report template. The override specifications feature is a section level option. You must override specifications for each section that requires modification. You can override specifications by type. This table describes the different specification override options:

Specification Type

Description

Section Layout

Enables you to change section properties, delete columns, add columns, move columns, or change column headings on a batch version.

Section Data Selection

Enables you to define specific data selection by version. For example, a version for customer information only and a version for employee information only.

Section Event Rules

Enables you to define specific event rules by version. For example, you can define a version for employee information with a calculated percentage raise amount, date title, or Balance Auditor.

Section Database Output

Enables you to use a different database mapping than the one defined in the report template.

Section Sort Sequence

Enables you to sort data differently than the report template. For example, you can define the data in a version to sort by name rather than by address number.

Once you have selected to override one of the specification types in a batch version, modifications that you make of the same specification type in the report template are not read by the overridden version. For example, if you override the section layout in a section of a batch version, then add a new field to that same section in the report template, the new field is not read by the batch version.

7.2.2 Understanding Overriding Properties for Versions of Table Conversions

When you submit a version to process a table conversion, you can override the conversion properties. This table describes the different conversion properties that can be overridden:

Conversion Properties

Description

Environments

Enables you need to change the location of the input or output data.

Data selection

Enables you need to limit the number of input records.

Table options

Enables you to control how the Oracle's JD Edwards EnterpriseOne Table Conversion system processes records during the conversion.

Logging options

Enables the system to write information to the logs.

Debug logging.

Enables you need to override the setting for debug logging as defined in the jde.ini.

7.2.3 Prerequisites

Before you begin changing the design of batch versions, ensure that you:

- Create a report template.

- Create a batch version of the report template.

- Ensure that JD Edwards EnterpriseOne Report Design Aid (RDA) is not open.

Before you begin changing properties of versions for table conversions, ensure that you set up a table conversion template.

7.2.4 Overriding Specifications in Batch Versions

Access the Work with Batch Versions - Available Versions form.

1. Enter the name of a report or batch process in the Batch Application field and click Find.

2. In the detail area, select a batch version that is checked out and with which you want to work.

3. From the Row menu, select Advanced.

4. On the Advanced Operations form, select Design Version from the Row menu.
RDA opens reading the master specifications from the report template.

5. On the JD Edwards Report Design Aid form, click in a section and select Override Version Specifications from the Section menu.

6. Select the appropriate overrides, and click OK.

7. The changes that you make affect only the version on the local workstation.
To make these changes available to the enterprise, you must check in the version. If you do not want to check in the version, erase the checkout so that other users can check out the version.

7.2.5 Changing the Properties of Versions for Table Conversions

Access the Work With Batch Versions - Available Versions form.

1. Enter the name of the table conversion in the Batch Application field and click Find.

2. Add a new version of the table conversion.

3. On the JD Edwards Table Conversion Version Design form, select the Tools tab and click Properties.

4. On the Properties form, review and override the environments, data selection, table options, and logging options specified in the table conversion.
These forms are similar to the forms in JD Edwards EnterpriseOne Table Conversion Design.

5. To use debug logging, select the Debug Logging tab to perform these steps:

- To use the jde.ini settings for the trace level and row-by-row conversion process, select the Use ini settings for trace level and number of rows to process option. This option ensures that the system uses the settings contained in the jde.ini instead of the values entered in the Trace Level and Number of Rows fields.

- To override the trace level in the jde.ini, clear the Use ini settings for trace level and number of rows to process option. Enter a value from 0 to 10 in the Trace Level field.

- To convert a specific number of records (for example, if you want to test the table conversion), clear the Use ini settings for trace level and number of rows to process option. Enter the number of rows to convert in the Number of Rows field. If you enter 0 in this field, the system processes all rows.
This option corresponds to the StopAfterRow setting in the jde.ini. If you enter a value here, you override any specifications in the jde.ini.

8 Submitting Batch Versions

This chapter contains the following topics:

- Section 8.1, "Understanding Batch Version Submission"

- Section 8.2, "Submitting Batch Versions from the Microsoft Windows Client"

- Section 8.3, "Submitting Batch Versions from the Web Client"

- Section 8.4, "Submitting Table Conversions from the Microsoft Windows Client"

- Section 8.5, "Submitting Table Conversions from the Web Client"

- Section 8.6, "Submitting at the Command Line"

8.1 Understanding Batch Version Submission

You can submit batch versions from the following Oracle JD Edwards EnterpriseOne locations:

- The JD Edwards EnterpriseOne Batch Versions (P98305) Windows client or P98305W web-client application.

- Select Batch Versions from the Report Management (GH9111) menu.

- Select Report Versions from the Tools menu in JD Edwards Solution Explorer.

- The EnterpriseOne Menu.

- From a report located on the Report menu within an application.

- From another batch version using report interconnects.

Before you can process batch versions on the enterprise server, you must ensure that:

- The associated batch applications are checked in and have been deployed to the enterprise server.

- The batch version specifications reside on the enterprise server.

When you use report interconnects, you must ensure that all associated batch applications and batch versions reside on the enterprise server prior to processing. If you need to copy batch version specifications to the enterprise server, ensure that the associated batch application already resides on that server.

See "Understanding Logic and Processing," "Working with Report Interconnects" in the JD Edwards EnterpriseOne Tools Development Tools: Report Design Aid Guide.

When a batch version exists only on the workstation, you must first submit the version specifications to the server where the associated report specifications reside. You can accomplish this by selecting the Submit Version Specifications Only option on the Advanced Version Prompting form.

When you modify a batch version and run the modified version on the workstation, the local modified version specifications run. If you want to run the modified version on the enterprise server, you need to submit the version specifications to the server.

See Copying Batch Version Specifications to an Enterprise Server.

When you submit batch versions, you can modify the data selection and data sequencing, and select from advanced functions. You can also:

- View the report on screen.

- Send the report to a printer.

- Export the report to a CSV file.

- Export the report to another software program using OSA (output stream access).

8.1.1 Data Selection and Data Sequencing

Data selection and data sequencing values are stored in JD Edwards EnterpriseOne Report Design Aid (RDA) specification (RDASPEC) files, which can exist on the client as well as on the server. In Terminal Server environments, multiple users share the same set of client RDASPEC files, so changes made to the specifications by one user are immediately visible to all other users of the same terminal server.

When you submit a batch version, you can modify the data selection and data sequencing from the Version Prompting form. Any modifications that you make to the batch version from this form affect the current submission only. Values that you enter during submission are used for processing, but are not saved and are not seen during the next report submission. If no prompting occurs, the values that exist locally at submission time are used by the system during processing. Values that you enter in Version List or in RDA are saved in the RDASPEC files.

This table provides some data selection and data sequencing scenarios:

Scenario

Description

Batch versions submitted locally from the Microsoft Windows client.

You might be prompted for data selection and data sequencing. The values that you specify during prompting are retained in memory, but are not saved to the local RDASPEC files. The values in memory are then passed along to the job as it processes. If you are not prompted for data selection and data sequencing, the job loads data selection and data sequence values from the local RDASPEC files at runtime.

Batch versions submitted on the server from the Microsoft Windows client.

The system copies the data selection and data sequencing specifications related to the version into packed files and sends them to the server. When the job processes on the server, the system merges the packed files into the specifications on the server, which are then used to run the job.
If you are prompted for data selection and data sequencing during submission, the values retained in memory are copied into the packed files instead of the corresponding RDASPEC information. The system then uses the data selection and data sequencing values that you enter at submission when the job executes.

Batch versions submitted from the web client.

You can override data selection and data sequencing at runtime. You also have the option of defining data selection and data sequencing from the Row menu.

Note:
When you define data selection and data sequencing outside of RDA, either at runtime or from the Work With Batch Versions-Available Versions form, the definition only affects the first level-one section of the report template. If you have other level-one sections in the report template that need to use the same data selection and data sequencing as the first level-one section, you must define these sections to adopt the settings from the first level-one section. You can accomplish this by calling system functions in event rules on the additional level-one sections.

Data selection uses Boolean logic to determine which records to include in the report. Boolean logic uses operators such as And and Or.

Use And to include only the data that two or more fields in a record have in common. For example, suppose you need a list of customers who are located in New York City. You might use the two fields Location and Search Type in the criteria:

Search Type = C (customer)

And

Location = New York

Use Or logic to include all records that meet one of the sets of criteria. For example, if you need to find any New York City record or any customer record, you would indicate the same information for Location and Search Type using these criteria:

Search Type = C (customer)

Or

Location = New York

The Section Data Sequencing form that you see at runtime is slightly different from the one that you see in RDA. You can still see the Columns Available on the left and the Columns Sorted on the right. The form also indicates the sort order of ascending or descending and whether page breaks are set. You can modify both the sort order and the page break options on this form.

8.1.2 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.

8.1.3 Advanced Option Overrides

Advanced options enable you to override the processing location and use a variety of logging features. You can select from these advanced options when submitting batch versions:

- Override Location.

- Logging (JDE.log).

- Tracing (JDEDEBUG.log).

- Override Job Queue.

- UBE Logging Level.

- Submit Version Specifications Only.

Note:
For advanced options that apply to BI Publisher for JD Edwards EnterpriseOne functionality, see JJD Edwards EnterpriseOne Tools BI Publisher For JD Edwards EnterpriseOne Guide.

8.1.4 Printer Selections

Print properties are passed from the report template to the batch version. You can modify print properties from the File menu in RDA. When you modify properties that are located on the File menu, the modifications are not passed to batch versions that existed before launching RDA to make the modification. For existing batch versions, you need to also make the modification in the versions that you want to affect. Any new batch versions that you create after the modification include the update.

When you submit batch versions to a printer, the system looks first for the printer defined in RDA. If no printer is defined in RDA, the system uses the default printer defined in the JD Edwards EnterpriseOne Printers (P98616) application.

The system determines a printer based on this hierarchical structure:

1. Printer defined at runtime.

2. Printer defined in RDA.
The printer definition becomes part of the report specifications.

3. Printer defined in the JD Edwards EnterpriseOne Printers application using this hierarchy:

1. Specific report defined for the user or role.

2. Specific report defined for *PUBLIC.

3. All reports defined for the user or role.

4. All reports defined for *PUBLIC.

When you submit batch versions to a printer, you can use the Printer Selection form to select print options from these tabs:

- Printer Selection

- Print Property

- Document Setup

- Advanced

See "Understanding Print Properties at Runtime" in the JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

8.1.5 CSV Files

In addition to viewing the CSV file, you can manipulate the report data after the report finishes processing.

When you export batch versions to CSV:

- A CSV file is created in the PrintQueue directory.

- A PDF file is created in the PrintQueue directory.

- The CSV file displays in a spreadsheet program such as Microsoft Excel or Lotus 123, which launches automatically if you are running the batch version locally. If you are running the batch version on a server, select View CSV from the Oracle's JD Edwards EnterpriseOne Work With Servers (P986116) application to launch the spreadsheet application and view the file.

You can select to output reports to a CSV file from the following locations:

- RDA for the report template.

- RDA for the batch version.

- Versions List at runtime.

Reports do not always export to other programs perfectly. For example, group sections with several one-character data fields might need some cleanup, such as justifying the data or deleting blank columns.

8.1.6 OSA Interface

You can select to output to third-party software programs using OSA. OSA interfaces enable the third-party program to process and format the report data concurrently.

Benefits of using OSA include:

- The elimination of manually formatting output, as you must do with CSV output.

- Using the processing power of the target software program.

See Also:

- See"Defining Print Properties for Reports", "Modifying Print Properties", "Understanding Exporting to CSV" in the JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

- See "Defining Print Properties for Reports", "Modifying Print Properties", "Understanding OSA Interfaces" in the JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

8.2 Submitting Batch Versions from the Microsoft Windows Client

This section provides overviews of batch versions submitted on the server from the Microsoft Windows client and batch versions submitted locally from the Microsoft Windows client and discusses how to run batch versions from the Microsoft Windows client.

8.2.1 Understanding Batch Versions Submitted on the Server from the Microsoft Windows Client

From the Microsoft Windows client, you can process batch versions:

- On the enterprise server.

- Locally on the workstation.

In most business environments, you submit batch versions to a designated enterprise server that can manage the processing needs more efficiently than the workstation. The system administrator defines whether the system automatically processes and prints the output, or places the job on hold in the queue.

When you submit batch versions to the server for processing, they are sent to a job queue. Version specifications and information required to process the batch version are sent from the workstation to the server.

From the JD Edwards EnterpriseOne Work With Servers application you can:

- Monitor the progress of the job in the queue.

- Change the priority of the job.

- View the report output in the following formats when the processing is complete:

- PDF

- CSV

- OSA

- View logs.

- Print the report.

Additionally, if the batch version is associated with a report definition, you can:

- View report definition jobs.

- View report definition output.

- View report definition source.

- Republish a report definition.

See "Embedded BI Publisher for JD Edwards EnterpriseOne" in the JD Edwards EnterpriseOne Tools BI Publisher For JD Edwards EnterpriseOne Guide

When you select to process batch versions on the enterprise server, you have the following options:

Runtime Options for Processing on the Server

Description

Modify printer selection.

Enables you to change the printer used for the report and select the number of copies to print.

Override the location.

Enables you to override the processing location; when you submit the batch version, the system presents you with a list of available servers from which to choose.

Modify paper type.

Enables you to change the orientation of the report, the paper size, and the paper source.

Define output options.

Enables you to output the report to a CSV file or use OSA interfaces to output to a third-party product.

Modify printer definition language.

Enables you to select a new printer definition language as supported by the printer that is defined for the report.

8.2.2 Understanding Batch Versions Submitted Locally from the Microsoft Windows Client

Sometimes processing batch versions locally is not only beneficial but necessary. If you are processing batch versions where the data selection limits the number of records fetched, processing locally is not a performance concern. Processing locally might be necessary to help narrow down issues that you encounter during processing. When batch versions process locally but do not process successfully on the server, this might indicate that the issue is specific to the server. Processing batch versions locally places the logs on the workstation for ease in reviewing processing concerns.

Since the typical system configuration defines batch versions to process on an enterprise server, you need to override the processing location to process batch versions locally.

When you process batch versions locally, you can select these methods of output:

- On Screen

- To Printer

- Export to CSV

- OSA Interface Name

See Also:

- JD Edwards EnterpriseOne Tools System Administration Guide.

- JD Edwards EnterpriseOne Tools 8.98 HTML Server Reference Guide.

8.2.3 Forms Used to Submit Batch Versions from the Microsoft Windows Client

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Version Prompting

W98305D

Select a batch version and click Select on the Work With Batch Versions - Available Versions form.

Override data selection and data sequencing. Submit batch versions.

Advanced Version Prompting

W98305I

Click Advanced on the Form menu on the Version Prompting form.

Override the processing location for a single batch version submission.

JD Edwards Data Sources

W98305B

Click Submit on the Version Prompting form.

Select a data source for processing a single batch version submission. Select LOCAL to process batch versions locally.

Report Output Destination

W98UBEA

Click Submit on the Version Prompting form.

Select output option for batch version.

Printer Selection

W986162B

Click To Printer on the Report Output Destination form when submitting batch versions locally.
Click Submit on the Version Prompting form when submitting batch versions to an enterprise server.

Select printer options and output the report to a printer.

8.2.4 Running Batch Versions from the Microsoft Windows Client

Select a batch version from the Work With Batch Versions - Available Versions form.

8.2.4.1 Overriding Advanced Options

Access the Advanced Version Prompting form.

Figure 8-1 Advanced Version Prompting form

Override Location

Select this option to define a different location in which the batch version processes. You must have permissions for this option. When you submit the batch version for processing, you can select a new location from a list of available data sources on the JDE Data Source form. Data sources include the enterprise servers available on the network and the local workstation.

Submit Version Specifications Only

Select this option to submit version specifications to the server without processing the batch version locally or on the server. The associated report template specifications must already reside on the server to use this feature.

Logging (JDE.log)

Select this option to enable logging for the execution of the batch job on the server. To enable logging on the workstation, you must modify the output setting in the workstation jde.ini. However, be aware that this output setting affects all JD Edwards EnterpriseOne logging. You can select this option without selecting the Tracing option.

Tracing (JDEDEBUG.log)

Select this option to enable tracing for the execution of the batch job on the server. You cannot select this option without selecting the Logging option. The system selects the Logging option for you when you select the Tracing option.

Override Job Queue

Select this option to submit the batch job to another available queue by overriding the job queue as defined for batch versions in both the jde.ini and the specifications. You must have permissions for this option.

UBE Logging Level

Enter a value from 0–6 to indicate the level of detail to be captured in the logs. This option in used in partnership with the logging options. When you select a high value to receive more technical information, you also receive all the information for the lower values. For example, when you enter a value of 3 (object level messages), you also receive information for 2 (section level messages), 1 (informative messages), and 0 (error messages).

Submit with Report Definition

Select this option to submit the batch version with a report definition. This option is only available if a report definition has been associated with the version.

Prompt for Report Definition

Select this option to prompt the user to select a report definition other than the default to be used for the submission. All batch applications that use this batch version as their source of data and have either no source version specified or this specific version specified will be available for submission.

8.2.4.2 Overriding Data Selection and Data Sequencing

Access the Version Prompting form

Figure 8-2 Version Prompting form

Data Selection

Select this option to override the current data selection. You can append to the current selection, modify the current selection, or delete the current selection and add new criteria.

Data Sequencing

Select this option to override the current data sequencing. You can add to the current sequencing, modify the current sequencing, or delete the current sequencing and add new information.

8.2.4.3 Submitting the Batch Version

The options that you select on this form override settings specified in the report itself, but apply to the current batch process only.

Access the Report Output Destination form.

Figure 8-3 Report Output Destination form

On Screen

Select this option to view the report online in a PDF format. The report is readable with the Adobe Acrobat Reader.

To Printer

Select this option to send the report to the defined printer. The system looks first for a printer defined in Report Design Aid, if no printer is defined, the system uses the default printer defined in the JD Edwards EnterpriseOne Printers application.

Export to CSV

Select this option to create a CSV file. When you select this option, the report can be viewed in a default CSV viewer, such as Microsoft Excel or Lotus 1-2-3.

OSA Interface Name

Select this option to pass data to third-party programs during batch processing, enabling those programs to process and format the data concurrently. An OSA interface must already be defined before you can select this option.

8.2.4.4 Overriding Printer Selection

Access the Printer Selection form.

Figure 8-4 Printer Selection form

Printer Name

The name of the printer that is defined in either RDA or the JD Edwards EnterpriseOne Printers application. You can override the printer from the Form menu.

Printer Location

The location of the printer that is defined in either RDA or the JD Edwards EnterpriseOne Printers application.

Printer Model

The model of the printer that is defined in either RDA or the JD Edwards EnterpriseOne Printers application.

Number of Copies

Enter the number of copies to print. The default value is one. You can enter a value from 1–9999.

8.2.4.5 Overriding Print Properties

Select the Print Property tab.

Portrait

Select this option to print the report on a page that is longer than it is wide.

Landscape

Select this option to print the report on a page that is wider than it is long. This is the default orientation defined for reports.

Number of Copies

Displays the number of copies entered on the Printer Selection tab. Changing the value here changes the value on the Printer Selection tab as well. This option is valid only for PostScript and line printers; it is disabled for PCL printers. If you are printing to an iSeries line printer, you might need to modify the output queue description to enable this feature.

Paper Type

Displays the paper type as it is defined in either RDA or the JD Edwards EnterpriseOne Printers application. You can override this selection.

Paper Source

Displays the name of the output tray to which the report will be sent. The default and maximum values for this option are defined in the JD Edwards EnterpriseOne Printers application. This option is only available for PostScript printers; it is disabled for PCL and line printers. You can override this selection.

8.2.4.6 Overriding Document Setup

Select the Document Setup tab.

PDF (Portable Document Format)

Outputs the report to a PDF file that can be read by Adobe Acrobat Reader. This option cannot be modified.

Printer Definition Language File

Select this option to output the report to a PDL file.

Print Immediate

Select this option to print the report immediately instead of sitting in a queue.

CSV (Comma Delimited)

Select this option to export the report to a CSV file.

OSA Interface Name

Select this option to output the report to a third-party software program.

8.2.4.7 Overriding Advanced Properties

Select the Advanced tab.

Postscript

Displays the type of printer definition language defined. The system selects this option based on the printer that is defined.

PCL

Displays the type of printer definition language defined. The system selects this option based on the printer that is defined.

Line Printer

Displays the type of printer definition language defined. The system selects this option based on the printer that is defined.

Custom

Displays the type of printer definition language defined. Option is selected by the system based on the printer that is defined.

8.3 Submitting Batch Versions from the Web Client

This section discusses batch versions submitted from the web client and lists the forms used to submit batch versions from the web client.

8.3.1 Understanding Batch Versions Submitted from the Web Client

On the web client, you can double-click a report from a menu or access the Submit Jobs application to submit batch versions. All batch versions submitted from the web client are processed on the server.

To make a new report template available from the web client, perform these steps:

1. Check in the report template and all associated batch versions.

2. Include the report template and batch versions in a package.

3. Deploy the package to the enterprise server.

4. Generate the report template and associated batch versions to HTML.

When you create a new batch version from Microsoft Windows for a report template that has already been deployed and generated to HTML, perform these steps to make the new batch version available from the web client:

1. Check in the version specifications.

2. Copy the version specifications to the server.

3. Generate the batch version to HTML.

This table describes runtime options available when you process batch versions from the web client:

Runtime Options from the Web Client

Description

Override the location

Enables you to override the processing location; when you submit the batch version, the system presents you with a list of available servers from which to choose.

Modify printer selection

Enables you to change the printer used for the report and select the number of copies to print.

Modify paper type

Enables you to change the orientation of the report, the paper size, and the paper source.

Define output options

Enables you to output the report to a CSV file or use OSA interfaces to output to a third-party product.

Modify printer definition language

Enables you to select a new printer definition language as supported by the printer defined for the report.

To increase performance for viewing reports on the web client, the system administrator can activate the page-at-a-time functionality. The settings to activate the page-at-a-time functionality are located in the jde.ini and the jas.ini. The page-at-a-time functionality enables you to view portions of the report while the report continues loading.

8.3.2 Forms Used to Submit Batch Versions from the Web Client

Form Name

FormID

Navigation

Usage

Submit Job - Work With Batch Versions - Available Versions

W98305WA

EnterpriseOne Menu, Submit Job

Enter the name of a batch application and select from available batch versions.

Submit Job - Version Prompting

W98305WD

Select a batch version and click Select on the Submit Job - Work With Batch Versions - Available Versions form.
Select an option on the Submit Job - Advanced Version Prompting form and click OK.

Submit batch versions.

Submit Job - Advanced Version Prompting

W98305WI

Click Advanced on the Form menu on the Submit Job - Version Prompting form.

Select Override Location to override the processing location for a single batch version submission.

Submit Job - EnterpriseOne Data Sources

W98305WC

Click Submit on the Submit Job- Version Prompting form.

Select a data source for processing a single batch version submission. LOCAL is not an option on the web client.

Printer Selection

W986162B

Click Submit on the Submit Job - Version Prompting form.

Select printer options and output the report to a printer.

8.4 Submitting Table Conversions from the Microsoft Windows Client

This section provides an overview of table conversions submitted from the Microsoft Windows client and discusses how to submit table conversions from the Microsoft Windows client.

8.4.1 Understanding Table Conversions Submitted from the Microsoft Windows Client

Versions of table conversions use different properties than versions of batch applications. When you submit versions of table conversions from the Microsoft Windows client you can select these options:

- Properties.

- Override Location.

- Submit Version Specifications Only.

- Override Job Queue.

See Also:

- See "Converting Tables", "Running Table Conversions" in the JD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

8.4.2 Forms Used to Submit Table Conversions from the Microsoft Windows Client

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a table conversion template and select from available batch versions.

Table Conversion Prompting

W98305P

Select a version of a table conversion and click Select on the Work With Batch Versions - Available Versions form.

Override properties, processing location and job queue. Copy version specifications to the server and submit versions for processing.

8.4.3 Running Table Conversions from the Microsoft Windows Client

Access the Table Conversion Prompting form.

Figure 8-5 Table Conversion Prompting form

Properties

Select this option to override the tables conversion properties. The system displays the Properties form when you submit the version.

Submit Version Specifications Only

Select this option to copy the version specifications to the server.

Override Location

Select this option to override the location where the version processes. The system displays the JD Edwards Data Sources form when you submit the version.

Override Job Queue

Select this option to override the job queue. The system displays the Job Queue Search form when you submit the version.

8.5 Submitting Table Conversions from the Web Client

This section provides an overview of table conversions submitted from the web client and discusses how to submit table conversions from the web client.

8.5.1 Understanding Table Conversions Submitted from the Web Client

When submitting versions of table conversions from the web client you cannot modify properties. You can select and modify processing options. You can also select these options:

- Override Location.

- Override Job Queue.

- Submit Version Specifications Only.

- Data Selection.

See Also:

- See"Converting Tables," "Running Table Conversions" in theJD Edwards EnterpriseOne Tools Development Tools: Data Access Tools Guide.

8.5.2 Forms Used to Submit Table Conversions from the Web Client

Form Name

FormID

Navigation

Usage

Submit Job - Work With Batch Versions - Available Versions

W98305WA

EnterpriseOne Menu, Submit Job

Enter the name of a table conversion template and select from available batch versions.

Submit Job - Table Conversion Prompting

W98305WO

Select a version of a table conversion and click Select on the Work With Batch Versions - Available Versions form.

Override processing location and job queue. Submit versions for processing.

8.5.3 Running Table Conversions from the Web Client

Access the Submit Job - Table Conversion Prompting form.

Figure 8-6 Submit Job - Table Conversion Prompting form

Override Location

Select this option to override the location where the version processes. The system displays the Submit Job - EnterpriseOne Data Sources form when you submit the version.

Override Job Queue

Select this option to override the job queue. The system displays the Submit Job - Job Queue Search form when you submit the version.

Submit Version Specifications Only

Select this option to copy the version specifications to the server.

Data Selection

Select this option to override the current data selection. You can append to the current selection, modify the current selection, or delete the current selection and add new criterion.

8.6 Submitting at the Command Line

Using the command line on the enterprise server, you can define third-party software applications to submit batch jobs for processing in Oracle's JD Edwards EnterpriseOne.

JD Edwards EnterpriseOne accepts two types of batch submission command lines, rubube and runubexml.

This section discusses how to:

- Submit batch versions using runube.

- Submit batch versions using runube with Unix and iSeries.

- Submit batch versions using runubexml.

8.6.1 Submitting Batch Versions Using runube

The runube command line requires no input files. It is a direct command line that enables you to define:

- Which report and version to run.

- Which job queue to use.

- How the queue is controlled.

- Whether the report is printed or held.

- The location where the report is output.

You cannot enter processing option values or modify data selection and data sequencing using runube from the command line.

This is the format of the runube command line:

runubeUID PWD ENV ROLE REP VER JQB/I P/H S/DPTR

This table describes each of the command line components:

Component

Description

runube

The name of the executable that submits the job.

UID

A JD Edwards EnterpriseOne user ID. You must have permissions to run the report. (If using Unix or iSeries see other options in the Submitting Batch Versions Using runube with Unix and iSeries section.)

PWD

The JD Edwards EnterpriseOne password corresponding to the JD Edwards EnterpriseOne user ID. (If using Unix or iSeries see other options in the Submitting Batch Versions Using runube with Unix and iSeries section.)

ENV

The JD Edwards EnterpriseOne environment.

ROLE

The JD Edwards EnterpriseOne role.

REP

The object name of the report to be processed, such as R014021.

VER

The name of the version of the report to be processed; such as XJDE0001. You must enter a version name; you cannot submit a report template.

JQ

The name of the job queue to which the system should route the batch job, such as QBATCH.

B/I

The processing mode. Enter B to use batch processing. In this case, the system assigns the report a place in the queue.
Enter I for interactive mode, which runs the report immediately outside of the JD Edwards EnterpriseOne queuing mechanism.

P/H

The hold code. Enter P to send the output to a printer immediately after the job completes.
Enter H to hold the processed file without printing. You can print the job later using the Oracle's JD Edwards EnterpriseOne Work With Servers program (P986116) located on the Report Management menu (GH9111).

S/D

The save code. Enter S to save the file after processing is complete. The delete option (D) is reserved for future functionality.

PTR

The printer ID. If you do not enter a printer, the system uses the printer assigned as the default printer based on your JD Edwards EnterpriseOne user ID, role, environment, host name, report name, and version name.

Important:
If you submit this command in a UNIX or iSeries environment, you should be aware of the possible security risk. Any user with access to the UNIX or iSeries system can view this command line, including the password, while the runube command is processing.

8.6.2 Submitting Batch Versions Using runube with Unix and iSeries

When you submit reports in a Unix or iSeries environment using the runube command, users with access to the system can view the command line while it is running. Because the command line contains a password, this password is exposed to any user who accesses the command line while it is running. These solutions address this security concern:

- Define the command to prompt the user for a user ID and password.

- Create a text file that includes the user ID and password.

Note:
Although the command line security concern only applies to Unix and iSeries, the prompting functionality and the password text file functionality can be used on any server platform, including Microsoft Windows.

8.6.2.1 Prompt for User ID and Password

Instead of entering the password in the runube command line, you can modify the command line to prompt the user for a JD Edwards EnterpriseOne user ID and password when the command is submitted. To accomplish this, enter -P as the UID and eliminate the password parameter.

This is the format of the command line when prompting for the JD Edwards EnterpriseOne user ID and password:

runubeUID ENV ROLE REP VER JQB/I P/H S/DPTR

When the user presses enter, the system prompts the user for their JD Edwards EnterpriseOne user ID and password. This table describes the JD Edwards EnterpriseOne user ID and password components:

Component

Description

UID

Enter -P to prompt for a JD Edwards EnterpriseOne user ID and password.

PWD

Do not enter a password parameter.

8.6.2.2 Create a Text File for User ID and Password

Another option to enhance runube security in a Unix or iSeries environment is to create a text file. When the runube command is submitted, the system reads the text file and uses the JD Edwards EnterpriseOne user ID and password as indicated in the text file.

In the text file enter the JD Edwards EnterpriseOne user ID on the first line and the JD Edwards EnterpriseOne password on the second line, as indicated by this example:

UID
PWD

In the runube command line, enter one of these options as the UID:

- -F
The system reads the file where the JD Edwards EnterpriseOne user ID and password reside and closes the file. The file remains intact.

Caution:
This poses its own security risk as the file with the JD Edwards EnterpriseOne user ID and password remain in the system.

- -D
The system reads the file where the JD Edwards EnterpriseOne user ID and password reside and deletes the file. This is the recommended option.

This is the format of the runube command line when using a text file:

runubeUID PWD ENV ROLE REP VER JQB/I P/H S/DPTR

Component

Description

UID

Enter -F or -D so that the system knows to fetch the JD Edwards EnterpriseOne user ID and password from a file.

PWD

Enter the entire path and file name of the text file where the JD Edwards EnterpriseOne user ID and password reside.

8.6.3 Submitting Batch Versions Using runubexml

The runubexml command line requires an XML input file to provide instructions on processing the report. Using this command is nearly as flexible as submitting a batch process directly within JD Edwards EnterpriseOne. This method enables you to override:

- Processing options

- Data selection

- Data sequencing

You must have an XML input file available for each processing variation of each batch version that you want to run.

To use runubexml, you must create an XML input file which provides JD Edwards EnterpriseOne with batch processing instructions. If you are routinely submitting the same reports with the same options for processing, consider creating several XML files for each report.

Create and submit an XML file that provides JD Edwards EnterpriseOne with:

- Your JD Edwards EnterpriseOne user ID.

- Your JD Edwards EnterpriseOne password.

- The JD Edwards EnterpriseOne environment to access.

- The name of the report.

- The name of the batch version to be processed.

The system returns a new XML input file that defines the report version and any associated processing option values. You can modify this input file and create several variations of it.

You can run the XML input file as often as required. Changing the input file does not modify the batch version that is saved in JD Edwards EnterpriseOne. The input file only provides the JD Edwards EnterpriseOne batch processing engine with data; JD Edwards EnterpriseOne does not maintain any connection between the XML input file and the report upon which it is based. If you modify the report template in JD Edwards EnterpriseOne and you want those modifications to be reflected in the output you receive with the XML input file, you must either modify the existing input file or generate a new input file.

You must use a file called jdeRequest.xml to instruct the system to create an XML input file based on a JD Edwards EnterpriseOne report. If you do not have this file available, run this command:

runubexml G CREATE_XML jdeRequest.xml

This command generates the jdeRequest.xml file, which appears as:

<?xml version="1.0" encoding="UTF-8" ?>
<jdeRequest type="ube" user="MYUSERID" pwd="MYPASSWD" environment="MYENV" role=
"MYROLE" session="">
<!--This document is automatically generated by the J.D. Edwards APIs-->
<ACTION TYPE="CREATE_XML" TEMPLATE_TYPE="LAUNCH_JOB">
<REPORT_NAME VALUE="MYREPORT"/>
<REPORT_VERSION VALUE="MYVERSION"/>
<JARGON_SYSTEM_CODE VALUE="1"/>
<COMMENTS VALUE="1"/>
<DATA_TYPING VALUE="1"/>
<BUSINESS_VIEW VALUE="0"/>
<PRINTER_INFORMATION VALUE="0"/>
<POPULATED VALUE="1"/>
</ACTION>
</jdeRequest>

This table describes the modifications required by the jdeRequest.xml file:

Component

Description

user ="MYUSERID"

Substitute MYUSERID with your JD Edwards EnterpriseOne user id.

pwd = "MYPASSWD"

Substitute MYPASSWD with your JD Edwards EnterpriseOne password. The password must be submitted in plain text; therefore, the jdeRequest.xml file should be kept in a secure location on the file system.

environment ="MYENV"

Substitute MYENV with the name of the appropriate JD Edwards EnterpriseOne environment.

role ="'MYROLE"

Substitute MYROLE with your JD Edwards EnterpriseOne role.

REPORT_NAME VALUE ="MYREPORT"

Substitute MYREPORT with the object name of the report, such as R014021, on which to base the parameters for the XML input file.

REPORT_VERSION VALUE = "MYVERSION"

Substitute MYVERSION with the name of the batch version on which to base the parameters for the XML input file, such as XJDE0001. This is a required value; you cannot base the XML input file on a report template.

JARGON_SYSTEM_CODE VALUE

Enter 1 to enable jargon overrides. Enter 0 to disable jargon.

COMMENTS VALUE

Enter 1 to view XML comments in the xml file. Enter 0 to suppress comments.

DATA_TYPING VALUE

Enter 1 to view the data type (numeric, alpha, and so on.) populating the fields. Enter 0 to suppress data type identification.

BUSINESS_VIEW VALUE

Enter 1 to view which business view columns are being used to generate the report. Enter 0 to suppress business view data.

PRINTER INFORMATION VALUE

Enter 1 to view printer information for the printer to be used for the report. Enter 0 to suppress printer information.
Note: Even though print values are displayed in both the jdeRequest.xml and the input XML file, you cannot override printer values with the XML input file.

POPULATED VALUE

Enter 1 to populate the resulting XML input file with the settings and options specified for the batch version. Enter 0 to generate a blank XML input file. Typically, you want to enter 1 in this field.

After you have edited and saved the jdeRequest.xml, run this command:

runubexml S jdeRequest.xmlFilenamexml

Substitute Filename with the name that you want to call this file. JD Edwards EnterpriseOne recommends naming the file after the report and version upon which it is based, such as R014021_XJDE0001. The runubexml command submits the jdeRequest.xml file for processing and returns the input XML file that you require to run the batch job.

At this point, you can edit Filename.xml. For example, you can modify the processing options, data selection, or data sequencing. Create several input files based on the same batch version with slightly different processing option values. This saves you time if you run the variations on a regular basis.

Important:
The input XML file is precisely formatted according to JD Edwards EnterpriseOne input specifications. Altering the format of the file beyond modifying input values might result in errors when the file is run.

After creating, modifying, and saving the XML input file, use this command line to process the batch application that the file defines:

runubexml SFilename.xml jdeResponse.xml

Substitute Filename with the name that you gave the XML input file. This command submits the XML input file for processing and returns the results (including error messages) in a file called jdeResponse.xml.

9 Reviewing Batch Version Processing

This chapter contains the following topics:

- Section 9.1, "Understanding Resources for Reviewing Reports"

- Section 9.2, "Using the Submitted Jobs Application"

- Section 9.3, "Using Execution Details (P986114A) Utilities"

- Section 9.4, "Accessing BrowsER for Batch Versions"

- Section 9.5, "Reviewing the Cover Page"

- Section 9.6, "Generating and Reviewing Logs from the Microsoft Windows Client"

- Section 9.7, "Generating and Reviewing Logs from the Web Client"

9.1 Understanding Resources for Reviewing Reports

When processing batch versions, you might not always get the results that you expect or the job might encounter an error during processing. There are several resources that you can use to troubleshoot reports to understand why you received the results that you did:

- Submitted jobs

- JD Edwards EnterpriseOne BrowsER

- Cover page

- Logs

9.2 Using the Submitted Jobs Application

This section discusses:

- Submitted jobs.

- Submitted jobs for other users.

- Submitted jobs options.

9.2.1 Submitted Jobs

The Oracle's JD Edwards EnterpriseOne Submitted Jobs application displays batch jobs that have been submitted to the enterprise server. After you submit a batch version for processing on the enterprise server, you can access the JD Edwards EnterpriseOne Submitted Jobs application to review the job. The JD Edwards EnterpriseOne Submitted Jobs application does not display jobs that are submitted locally from the Microsoft Windows client.

From the Microsoft Windows client, access JD Edwards EnterpriseOne Submitted Jobs from the Form menu on the Work with Batch Versions - Available Version form. Depending on the configuration of the software, you are presented with one of these forms:

- Work with Servers

- Submitted Jobs Search

The same forms can be accessed from Oracle's JD Edwards Solution Explorer by selecting Work with Servers on the Report Management (GH9111) task.

The Work with Servers form lists all servers available for submitting batch jobs. You want to select the same server on this form that you selected when you submitted the batch version.

From the web client, select Submitted Jobs from the Form menu on the Submit Job - Work with Batch Versions - Available Version form. The same forms can be accessed by selecting View Job Status on JD Edwards EnterpriseOne Menu.

From the Work With Servers form, the system directs you to the Submitted Job Search form. This form displays all of the batch versions submitted to the selected server. This table describes the options that are available for the review from the Submitted Job Search form:

Review Options

Description

Queue

Indicates the job queue to which the job was submitted.

Status

Indicates the status of the job, represented by these codes:
D = Done

E = Error

H = Hold

P = Processing

S = In Queue

W = Waiting

Description

Displays the description of the status code.

Priority

Indicates the priority of the submitted job. The job priority is a value in the range of 0–9, with 0 being the highest priority. The default job priority is hard coded as a 5 on the web client. On the Microsoft Windows client, the default value is also set to 5 but can be modified in the jde.ini:

[NETWORK QUEUE SETTINGS]
UBEPriority=5

Type

Indicates the type of object, represented by these object codes:
001 = Version specifications only— displays when you select Submit Version Specifications Only from Advanced Version Prompting.

PKG = Server package install

UBE = Batch job

User

Indicates the user who submitted the job.

Job Details

Indicates the details of the job, which includes the name of the report and version submitted.

Host

Indicates the name of the server used for processing the job.

Job #

Indicates the number of the job.

Environment

Indicates the location (environment) of the batch version specifications.

Origination Host

Indicates the machine from which the job was submitted.

Process ID

Indicates the process ID that is assigned to the job by the system.

Date Job Submitted

Indicates the date the job was submitted.

Time Job Submitted

Indicates the time the job was submitted.

Date Last Activity

Indicates the last date the job was active.

Time Job Activity

Indicates the last time the job was active.

9.2.2 Submitted Jobs For Other Users

When you access the Submitted Job Search form, the top of the form displays this information:

- The name of the JD Edwards EnterpriseOne server where the jobs were submitted.

- The JD Edwards EnterpriseOne user ID of the person who submitted the jobs.

- The JD Edwards EnterpriseOne job queue where the jobs were submitted.
Typically, the Job Queue field displays an asterisk to display all job queues.

To view jobs submitted by another user, you can enter another user's ID into the User ID field. The option to view jobs submitted by other users must be enabled in the system.

The permissions for viewing another user's job information is defined in the Submitted Jobs processing option. This processing option includes a Security tab. If the Security Flag on the processing option is set to 1, users are allowed to view jobs submitted by other users. If the value is set to 2, users can only view their own jobs.

9.2.3 Submitted Jobs Options

On the Submitted Job Search form, you can:

- Place a job on hold.
The batch job does not process until the job is released. You might want to place a job on hold when the batch job requires a large amount of resources and should not be run during peak business hours.

- Release batch jobs that have been placed on hold.
This enables you to release a job to process during off-peak business hours.

- Change the priority of a batch job.

- Terminate batch jobs.

- View the PDF output.

- View the CSV output.
You must select the option to export to CSV prior to processing the batch job.

- View OSA
You must select the OSA option prior to processing the batch job.

- View logs to troubleshoot processing issues.

- Print the batch job.
Unless you selected the Print Immediate option for the batch job, the report does not print automatically. This option sends the batch job to the printer.

Note:
For options that apply to BI Publisher for JD Edwards EnterpriseOne functionality, see JD Edwards EnterpriseOne Tools BI Publisher For JD Edwards EnterpriseOne Guide.

See Also:

- See "Working with Servers" in the JD Edwards EnterpriseOne Tools System Administration Guide.

- See"Getting Started with BI Publisher for JD Edwards EnterpriseOne" in the JD Edwards EnterpriseOne Tools BI Publisher For JD Edwards EnterpriseOne Guide.

9.3 Using Execution Details (P986114A) Utilities

This section provides an overview of batch processing utilities available in the Execution Details (P986114A) application and discusses how to access Execution Details utilities.

9.3.1 Understanding Batch Processing Utilities

The Execution Details (P986114A) application allows access to additional utilities that help access dynamic runtime information for batch processing. The utilities include:

- Dynamic Logging
This utility enables logging to be turned on or off dynamically at any point during execution.

- Introspection
This utility enables access to dynamic information while a job is processing and gives an interactive display of a subset of current statistics. It gives users more visibility into the runtime information for reports for timing and troubleshooting purposes.

- Audit Data
This utility records information about how a job was submitted and the duration it took to process.

Execution Detail information is only available for jobs with status of Done, Processing, or Error. Use this application to help answer these troubleshooting questions:

- Is the selection criterion not matching output expectations?

- Is the job actively processing?

- What is the job doing?

- Has the database been updated?

- Can the database be rolled back?

- How many records have been processed?

- What was the last business function that executed?

The Execution Details application is available exclusively as a row exit from the Work With Server Jobs application. Audit Data, Dynamic Logging and Introspection are available only from within the Execution Details application.

9.3.1.1 Dynamic Logging

When Dynamic Logging is enabled, a flag is set. This flag is periodically checked by the engine. When it is read, Logging is enabled at the full level 6 UBE logging level. Logging for UBE can still be controlled through .ini settings and submission runtime overrides. This does not replace any current controls, but provides additional points of control. Turning on logging and introspection impacts performance. Be sure to turn off logging when it is no longer needed. (See Accessing Execution Details Utilities.)

You can enable Dynamic Logging by clicking the Turn Logging On button on the Submitted Job Execution Detail form.

9.3.1.2 Introspection

When Introspection is enabled, the system populates the Introspection Data tab. Introspection data is retrieved from the batch process on the server.

You can update Introspection data using the Refresh button within the tab area. If introspection information stops changing when refreshed, then that is the last data to be recorded. In this situation a loop may be occurring. The last set of data may provide a starting point for debugging.

To enable Introspection in error situations, click the Turn Introspection On button on the Submitted Job Execution Detail form.

9.3.1.3 Audit Data

The other selection tabs available on the Submitted Job Execution Detail form are for audit information and include:

- Audit Data

- Processing Options — used to run the batch job.

- Data Selection — used to run the batch job.

- Data Sequencing — used to run the batch job.

- Report Interconnect — used to run the batch job.

- SQL Statement — generated by the batch job.

Audit data is available for every UBE that gets executed. Audit data is useful for analyzing trends in processing time and for troubleshooting batch jobs.

9.3.1.4 Verifying Statuses

The Verifying Statuses button on the Submitted Job Execution Detail form is used to refresh the statuses for:

- Debug Logging Status

- Introspection Status

- Job Status

9.3.1.5 Report Interconnects

If a report has synchronous sub reports invoked through Event Rules or Business Functions, then when you invoke Execution Detail for the parent report, it will present a selection screen for parent and child processes. You can choose which process to view. To select a different report after having selected one, exit the Execution Details form to the Server Jobs form, and then select the Execution Details form and select the process that you want to view.

When a child process finishes and the parent report is still running, the child process is removed from the available details list. You can view the child report by clicking Form, Submitted Jobs from the Batch Versions application to select and display the complete child report. If a report is running a sub-process, Introspection shows the current version and processes, and will update and follow the process. It dynamically follows the process regardless of the entry point.

9.3.1.6 Troubleshooting Batch Process Utilities

If Dynamic Logging or Introspection fails to start, then something is preventing the turn-on flag from being read:

- The process may either be in an unexpected loop or may require extended processing.

- The UBE might be waiting on a locked resource and unable to continue normal processing.

- The server with the IPC mechanism for inter-process communication is not functioning properly.

- The job may have finished processing since the last status refresh.

If failure to start occurs:

1. Look at the logs from the Enterprise Server Kernel processing. This will tell if the network message and inter-process communication is working. (See Server Manager).

2. Using Server Manager, verify the status of the UBE to see if it is active.

9.3.1.7 Accessing Execution Details Utilities

To access Execution Details utilities:

1. On the Batch Versions List application, after you submit a report to the enterprise server, select the Form exit called Submitted Jobs.

2. After choosing a specific report, select Execution Details in the Row menu.

9.4 Accessing BrowsER for Batch Versions

This section provides an overview of accessing Oracle's JD Edwards EnterpriseOne BrowsER and lists the forms used to access JD Edwards EnterpriseOne BrowsER.

9.4.1 Accessing BrowsER

You can use JD Edwards EnterpriseOne BrowsER to view event rules for an entire report or batch version. JD Edwards EnterpriseOne BrowsER displays the sections of the report in a hierarchical structure. When you expand a section, a section node and nodes for each object within the section appear. Event rules attached to the section appear under the section node. All event rules attached to an object display under the appropriate object node.

A plus sign next to a node indicates that there are event rules attached. When you expand a node with a plus sign, a node for the event on which the event rules are attached appears, also with a plus sign. When you expand the event node, you can review the event rules attached to the event. You can disable, and enable, event rules from JD Edwards EnterpriseOne BrowsER. This is useful for troubleshooting event rules for an entire report or batch version.

Since you can override event rule specifications in a batch version, the event rules could be different than the associated report template.

See Also:

- See"Understanding Logic and Processing", "Working with Event Rules", "Accessing BrowsER for Report Templates" in the JD Edwards EnterpriseOne Tools Development Tools: Report Design Aid Guide.

9.4.2 Forms Used to Access BrowsER

Note:
The JD Edwards EnterpriseOne BrowsER options are not available for versions of table conversions.

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Advanced Operations

W98305J

Select Advanced from the Row menu on the Work With Batch Versions - Available Versions form.

Access BrowsER.

Browsing

N/A

Select Report BrowsER or Version BrowsER from the Form menu on the Advanced Operations form.

Review, disable, and enable event rules in a report template or batch version.

9.5 Reviewing the Cover Page

This section discusses the cover page.

9.5.1 The Cover Page

The cover page of a report includes information regarding the report and each section of the report. In Oracle's JD Edwards EnterpriseOne Report Design Aid (RDA), you can select the items to be included in the cover page on the report properties form. From the File menu, select Report Properties and on the Properties form, select the Cover Page Options tab. On the Cover Page Options tab, select the Print Cover Page option to activate the list of items from which you can select.

To print the cover page of a report, you must also select the Print Cover Page option on the Version Detail form for the batch version. The Version Detail form is accessed from the Row menu of the Work with Batch Versions - Available Versions form.

The cover page prints prior to the report. Once you have selected the Print Cover Page option, the cover page prints every time that the batch version is submitted on the Microsoft Windows client. You must return to the Version Detail form to clear the selection if you no longer want the cover page to print.

At the report level, the cover page includes information regarding:

- Report Properties

- System Properties

- Printer Properties

- Processing Options

- Report Interconnects

At the section level, the cover page includes information regarding:

- Section Type

- Section ID

- Business View

- Visible

- Conditional/Custom Section

- Font Override (Y/N)

- Color Override (Y/N)

- Objects Detail
Includes a list of all objects included in the section with information about each, such as whether the object is visible, global, or derived, as well as the object's data type, and alias.

- Data Selection
Indicates the data selection that is defined in the report section. If you do not see the data that you expect in the report, review the defined data selection; the data selection might not be defined correctly. Pay close attention to the operators is equal to and is not equal to.

- Data Sequencing
Indicates the data sequencing that is defined in the report section including the field type, sort order, and whether the field is defined as a level break or a page break.

9.5.1.1 Report Properties

The report properties section of the cover page provides this information on the Report Properties defined in the report template:

- Print Totals Only (Y/N).

- Print Grand Totals (Y/N).

- Limit number of primary table rows.
If the report does not display as many records as you expect, check if a limit has been set for the number of primary rows to be fetched.

- Subsystem (Y/N).

- Data Source.
If the data source has been overridden you might not be accessing the correct database, which could affect the data displayed in the report.

- Data Target.

- Dynamic Positioning.

9.5.1.2 System Properties

The system properties section of the cover page provides this system information:

- The name of the server the report is using.

- The name of the environment being accessed.

- The name of the path code where the report resides.

- The user ID of the person processing the report.

- The role of the user processing the report
Permissions could be another reason that the data in the report does not meet the expectations. Ensure that the user ID and role have the correct permissions to access the required data.

- The currency used in the report.

9.5.1.3 Printer Properties

The printer properties section of the cover page provides this printer information:

- The name of the printer to which the report is defined to output.

- The orientation defined for the report, portrait or landscape.

- The width of the page in inches.

- The height of the page in inches.

9.5.1.4 Processing Options

The processing options section of the cover page provides the name of the processing option template and the number of items listed on the template that is attached to the report template. Each item included on the processing option template are then listed including the description and value of each item.

9.5.1.5 Report Interconnects

The report interconnect section of the cover page provides the number of columns included in the report interconnect. Each column included in the report interconnect is listed with its description, alias, and value.

9.6 Generating and Reviewing Logs from the Microsoft Windows Client

This section provides an overview of logs for batch jobs and lists the forms used to generate logs from the Microsoft Windows client.

9.6.1 Understanding Logs for Batch Jobs

When you submit batch versions, you can specify whether you want to generate logs. The logs available are the JDE.log and the JDEDEBUG.log. These logs enable you to review the processing of the report. You can generate the logs on the server where the report is processed.

You can override the report processing location to process the report locally and generate the logs on the workstation. In this case, the logs are written to the print queue directory on the workstation where the PDF files reside.

The server logs reside in a specific directory on the server. The jde.ini settings determine the location of this directory. Also, depending on the platform that you use, the jde.ini setting differs slightly. This list provides sample jde.ini settings for the directory where the report logs reside:

- iSeries

[INSTALL]
DefaultSystem=E812SYS

Example path: E812SYS\PRINTQUEUE

- UNIX

[INSTALL]
E812=/usr/JDEdwards/output

Example path: /usr/JDEdwards/E812/output/PrintQueue

- Microsoft Windows NT Server

[INSTALL]
E812=d:\JDEdwards\output

Example path: d:\JDEdwards\E812\output\PrintQueue

PrintQueue is the default directory for the UBE log files, which is a subdirectory of the directory that you define in the jde.ini. You can change the location of this directory as necessary.

Note:
These jde.ini settings also determine the location where the report output resides after processing. If you set the jde.ini to save the output for reports, the system saves PDF and CSV files in the PrintQueue folder in the path specified in the jde.ini.

9.6.2 Forms Used to Generate Logs from the Microsoft Windows Client

Form Name

FormID

Navigation

Usage

Work With Batch Versions - Available Versions

W98305A

EnterpriseOne Life Cycle Tools, Report Management (GH9111), Batch Versions

Enter the name of a batch application and select from available batch versions.

Version Prompting

W98305D

Select a batch version and click Select on the Work With Batch Versions - Available Versions form.

Override data selection and data sequencing. Submit batch versions.

Advanced Version Prompting

W98305I

Click Advanced on the Form menu on the Version Prompting form.

Select logs to generate for a single batch version submission.

Printer Selection

W986162B

Click To Printer on the Report Output Destination form when submitting batch versions locally.
Click Submit on the Version Prompting form when submitting batch versions to an enterprise server.

Select printer options and submit the batch version for processing.

Submitted Job Search

W986110BA

Select a batch version and select Submitted Jobs on the Form menu of the Work With Batch Versions - Available Versions form.

Select a batch job.

View Logs

W986110BD

Select View Logs from the Row menu of the Submitted Job Search form.

Select the log to view.

9.7 Generating and Reviewing Logs from the Web Client

This section provides an overview of logs generated from the web client and lists the forms used to generate logs from the web client.

9.7.1 Understanding Logs Generated from the Web Client

When you submit batch versions from the web client, you can specify whether you want to generate logs. The logs available are the JDE.log and the JDEDEBUG.log. These logs enable you to review the processing of the report submitted from the web client.

9.7.2 Forms Used to Generate Logs from the Web Client

Form Name

FormID

Navigation

Usage

Submit Job - Work With Batch Versions - Available Versions

W98305WA

EnterpriseOne Menu, Submit Job

Enter the name of a batch application and select from available batch versions.

Submit Job - Version Prompting

W98305WD

Select a batch version and click Select on the Submit Job - Work With Batch Versions - Available Versions form.

Override data selection and data sequencing. Submit batch versions.

Submit Job - Advanced Version Prompting

W98305I

Click Advanced on the Form menu on the Submit Job - Version Prompting form.

Generate logs for a single batch version submission.

Submit Job - Printer Selection

W986162B

Select Submit on the Submit Job - Version Prompting form.

Select printer options and submit the batch version for processing.

Submit Job - Submitted Job Search

W986110BA

Select a batch version and select Submitted Jobs on the Form menu of the Submit Job - Work With Batch Versions - Available Versions form.

Select a batch job.

View Logs

W986110BD

Select View Logs from the Row menu of the Submitted Job Search form.

Select the log to view.

Glossary

Accessor Methods/Assessors

Java methods to “get” and “set” the elements of a value object or other source file.

activity rule

The criteria by which an object progresses from one given point to the next in a flow.

add mode

A condition of a form that enables users to input data.

Advanced Planning Agent (APAg)

A JD Edwards EnterpriseOne tool that can be used to extract, transform, and load enterprise data. APAg supports access to data sources in the form of rational databases, flat file format, and other data or message encoding, such as XML.

application server

Software that provides the business logic for an application program in a distributed environment. The servers can be Oracle Application Server (OAS) or WebSphere Application Server (WAS).

Auto Commit Transaction

A database connection through which all database operations are immediately written to the database.

batch processing

A process of transferring records from a third-party system to JD Edwards EnterpriseOne.

In JD Edwards EnterpriseOne Financial Management, batch processing enables you to transfer invoices and vouchers that are entered in a system other than JD Edwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable, respectively. In addition, you can transfer address book information, including customer and supplier records, to JD Edwards EnterpriseOne.

batch server

A server that is designated for running batch processing requests. A batch server typically does not contain a database nor does it run interactive applications.

batch-of-one

A transaction method that enables a client application to perform work on a client workstation, then submit the work all at once to a server application for further processing. As a batch process is running on the server, the client application can continue performing other tasks.

best practices

Non-mandatory guidelines that help the developer make better design decisions.

BPEL

Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow.

BPEL PM

Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes.

Build Configuration File

Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services.

build engineer

An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts.

Build Program

A WIN32 executable that reads build configuration files and generates an ANT script for building published business services.

business analyst

An actor that determines if and why an EnterpriseOne business service needs to be developed.

business function

A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability.

business function event rule

See named event rule (NER).

business service

EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service.

business service artifacts

Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process.

business service class method

A method that accesses resources provided by the business service framework.

business service configuration files

Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties.

business service cross reference

A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system.

business service cross-reference utilities

Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data.

business service development environment

A framework needed by an integration developer to develop and manage business services.

business services development tool

Otherwise known as JDeveloper.

business service EnterpriseOne object

A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.

business service framework

Parts of the business service foundation that are specifically for supporting business service development.

business service payload

An object that is passed between an enterprise server and a business services server. The business service payload contains the input to the business service when passed to the business services server. The business service payload contains the results from the business service when passed to the Enterprise Server. In the case of notifications, the return business service payload contains the acknowledgement.

business service property

Key value data pairs used to control the behavior or functionality of business services.

Business Service Property Admin Tool

An EnterpriseOne application for developers and administrators to manage business service property records.

business service property business service group

A classification for business service property at the business service level. This is generally a business service name. A business service level contains one or more business service property groups. Each business service property group may contain zero or more business service property records.

business service property key

A unique name that identifies the business service property globally in the system.

business service property utilities

A utility API used in business service development to access EnterpriseOne business service property data.

business service property value

A value for a business service property.

business service repository

A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network.

business services server

The physical machine where the business services are located. Business services are run on an application server instance.

business services source file or business service class

One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler.

business service value object template

The structural representation of a business service value object used in a C-business function.

Business Service Value Object Template Utility

A utility used to create a business service value object template from a business service value object.

business services server artifact

The object to be deployed to the business services server.

business view

A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data.

central objects merge

A process that blends a customer's modifications to the objects in a current release with objects in a new release.

central server

A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machine—the central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server.

charts

Tables of information in JD Edwards EnterpriseOne that appear on forms in the software.

check-in repository

A repository for developers to check in and check out business service artifacts. There are multiple check-in repositories. Each can be used for a different purpose (for example, development, production, testing, and so on).

checksum

A fixed-size datum computed from an arbitrary block of digital data for the purpose of detecting accidental errors that may have been introduced during its transmission or storage. JD Edwards EnterpriseOne uses the checksum to verify the integrity of packages that have been downloaded by recomputing the checksum of the downloaded package and comparing it with the checksum of the original package. The procedure that yields the checksum from the data is called a checksum function or checksum algorithm. JD Edwards EnterpriseOne uses the MD5 and STA-1 checksum algorithms.

connector

Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors.

Control Table Workbench

An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables.

control tables merge

A process that blends a customer's modifications to the control tables with the data that accompanies a new release.

correlation data

The data used to tie HTTP responses with requests that consist of business service name and method.

credentials

A valid set of JD Edwards EnterpriseOne username/password/environment/role, EnterpriseOne session, or EnterpriseOne token.

cross-reference utility services

Utility services installed in a BPEL/ESB environment that access EnterpriseOne cross-reference data.

database credentials

A valid database username/password.

database server

A server in a local area network that maintains a database and performs searches for client computers.

Data Source Workbench

An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion.

deployment artifacts

Artifacts that are needed for the deployment process, such as servers, ports, and such.

deployment server

A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations.

direct connect

A transaction method in which a client application communicates interactively and directly with a server application.

See also batch-of-one and store-and-forward.

Do Not Translate (DNT)

A type of data source that must exist on the iSeries because of BLOB restrictions.

embedded application server instance

An OC4J instance started by and running wholly within JDeveloper.

edit code

A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information.

edit mode

A condition of a form that enables users to change data.

edit rule

A method used for formatting and validating user entries against a predefined rule or set of rules.

Electronic Data Interchange (EDI)

An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems.

embedded event rule

An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule.

Employee Work Center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages.

enterprise server

A server that contains the database and the logic for JD Edwards EnterpriseOne.

Enterprise Service Bus (ESB)

Middleware infrastructure products or technologies based on web services standards that enable a service-oriented architecture using an event-driven and XML-based messaging framework (the bus).

EnterpriseOne administrator

An actor responsible for the EnterpriseOne administration system.

EnterpriseOne credentials

A user ID, password, environment, and role used to validate a user of EnterpriseOne.

EnterpriseOne development client

Historically called “fat client,” a collection of installed EnterpriseOne components required to develop EnterpriseOne artifacts, including the Microsoft Windows client and design tools.

EnterpriseOne extension

A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizard

is a specific example of an extension.

EnterpriseOne object

A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects.

EnterpriseOne process

A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes don't have to wait if the server is particularly busy.

EnterpriseOne resource

Any EnterpriseOne table, metadata, business function, dictionary information, or other information restricted to authorized users.

Environment Workbench

An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion.

escalation monitor

A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time.

event rule

A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field.

explicit transaction

Transaction used by a business service developer to explicitly control the type (auto or manual) and the scope of transaction boundaries within a business service.

exposed method or value object

Published business service source files or parts of published business service source files that are part of the published interface. These are part of the contract with the customer.

fast path

A command prompt that enables the user to move quickly among menus and applications by using specific commands.

file server

A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files.

final mode

The report processing mode of a processing mode of a program that updates or creates data records.

foundation

A framework that must be accessible for execution of business services at runtime. This includes, but is not limited to, the Java Connector and JDBj.

FTP server

A server that responds to requests for files via file transfer protocol.

HTTP Adapter

A generic set of services that are used to do the basic HTTP operations, such as GET, POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.

instantiate

A Java term meaning “to create.” When a class is instantiated, a new instance

is created.

integration developer

The user of the system who develops, runs, and debugs the EnterpriseOne business services. The integration developer uses the EnterpriseOne business services to develop these components.

integration point (IP)

The business logic in previous implementations of EnterpriseOne that exposes a document level interface. This type of logic used to be called XBPs. In EnterpriseOne 8.11, IPs are implemented in Web Services Gateway powered by webMethods.

integration server

A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.

integrity test

A process used to supplement a company's internal balancing procedures by locating and reporting balancing problems and data inconsistencies.

interface table

See Z table.

internal method or value object

Business service source files or parts of business service source files that are not part of the published interface. These could be private or protected methods. These could be value objects not used in published methods.

interoperability model

A method for third-party systems to connect to or access JD Edwards EnterpriseOne.

in-your-face error

In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form.

jargon

An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of the current object.

Java application server

A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence.

JDBNET

A database driver that enables heterogeneous servers to access each other's data.

JDEBASE Database Middleware

A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access.

JDECallObject

An API used by business functions to invoke other business functions.

jde.ini

A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers.

JDEIPC

Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes.

jde.log

The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne.

JDENET

A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms.

JDeveloper Project

An artifact that JDeveloper uses to categorize and compile source files.

JDeveloper Workspace

An artifact that JDeveloper uses to organize project files. It contains one or more project files.

JMS Queue

A Java Messaging service queue used for point-to-point messaging.

listener service

A listener that listens for XML messages over HTTP.

local repository

A developer's local development environment that is used to store business service artifacts.

Location Workbench

An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source.

logic server

A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs.

MailMerge Workbench

An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment.

Manual Commit transaction

A database connection where all database operations delay writing to the database until a call to commit is made.

master business function (MBF)

An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases.

master table

See published table.

media storage object

Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx.

message center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user.

messaging adapter

An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues.

messaging server

A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions.

Monitoring Application

An EnterpriseOne tool provided for an administrator to get statistical information for various EnterpriseOne servers, reset statistics, and set notifications.

named event rule (NER)

Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work.

Object Configuration Manager (OCM)

In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user.

Object Librarian

A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-incapabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another.

Object Librarian merge

A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release.

Open Data Access (ODA)

An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation.

Output Stream Access (OSA)

An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing.

package

JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server.

package build

A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build.

Consider the following context: “Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions.” The process of creating a package build is often referred to, as it is in this example, simply as “a package build.”

package location

The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored.

Package Workbench

An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion.

Pathcode Directory

The specific portion of the file system on the EnterpriseOne development client where EnterpriseOne development artifacts are stored.

patterns

General repeatable solutions to a commonly occurring problem in software design. For business service development, the focus is on the object relationships and interactions. For orchestrations, the focus is on the integration patterns (for example, synchronous and asynchronous request/response, publish, notify, and receive/reply).

print server

The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself.

pristine environment

A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify.

processing option

A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on.

production environment

A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software.

Production Published Business Services Web Service

Published business services web service deployed to a production application server.

program temporary fix (PTF)

A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks.

project

In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench.

promotion path

The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path):

11>21>26>28>38>01

In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.

proxy server

A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service.

published business service

EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.

published business service identification information

Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.

published business service web service

Published business services components packaged as J2EE Web Service (namely, a J2EE EAR file that contains business service classes, business service foundation, configuration files, and web service artifacts).

published table

Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

publisher

The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

QBE

An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data.

real-time event

A message triggered from EnterpriseOne application logic that is intended for external systems to consume.

refresh

A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level.

replication server

A server that is responsible for replicating central objects to client machines.

rules

Mandatory guidelines that are not enforced by tooling, but must be followed in order to accomplish the desired results and to meet specified standards.

secure by default

A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions.

Secure Socket Layer (SSL)

A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.

selection

Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter.

serialize

The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed.

Server Workbench

An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number data source. The application also updates the Server Plan detail record to reflect completion.

SOA

Abbreviation for Service Oriented Architecture.

softcoding

A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process.

source repository

A repository for HTTP adapter and listener service development environment artifacts.

Specification merge

A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release.

specification

A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is used to build applications.

Specification Table Merge Workbench

An application that, during the Installation Workbench process, runs the batch applications that update the specification tables.

SSL Certificate

A special message signed by a certificate authority that contains the name of a user and that user's public key in such a way that anyone can "verify" that the message was signed by no one other than the certification authority and thereby develop trust in the user's public key.

store-and-forward

The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions.

subscriber table

Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table.

super class

An inheritance concept of the Java language where a class is an instance of something, but is also more specific. “Tree” might be the super class of “Oak” and “Elm,” for example.

table access management (TAM)

The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions.

Table Conversion Workbench

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table conversion

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table event rules

Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level.

terminal server

A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer.

transaction processing (TP) monitor

A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens.

transaction processing method

A method related to the management of a manual commit transaction boundary (for example, start, commit, rollback, and cancel).

transaction set

An electronic business transaction (electronic data interchange standard document) made up of segments.

trigger

One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system processes automatically when the event occurs.

triggering event

A specific workflow event that requires special action or has defined consequences or resulting actions.

user identification information

User ID, role, or *public.

User Overrides merge

Adds new user override records into a customer's user override table.

value object

A specific type of source file that holds input or output data, much like a data structure passes data. Value objects can be exposed (used in a published business service) or internal, and input or output. They are comprised of simple and complex elements and accessories to those elements.

versioning a published business service

Adding additional functionality/interfaces to the published business services without modifying the existing functionality/interfaces.

Versions List merge

The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data.

visual assist

Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control.

vocabulary override

An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report.

web application server

A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions.

web server

A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet.

Web Service Description Language (WSDL)

An XML format for describing network services.

Web Service Inspection Language (WSIL)

An XML format for assisting in the inspection of a site for available services and a set of rules for how inspection-related information should be made.

web service softcoding record

An XML document that contains values that are used to configure a web service proxy. This document identifies the endpoint and conditionally includes security information.

web service softcoding template

An XML document that provides the structure for a soft coded record.

Where clause

The portion of a database operation that specifies which records the database operation will affect.

Windows terminal server

A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device.

wizard

A type of JDeveloper extension used to walk the user through a series of steps.

workbench

A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditor's Workbench (P09E115), and Payroll Cycle Workbench.

workflow

The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules.

workgroup server

A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing.

XAPI events

A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response.

XML CallObject

An interoperability capability that enables you to call business functions.

XML Dispatch

An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses.

XML List

An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks.

XML Service

An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system.

XML Transaction

An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality.

XML Transaction Service (XTS)

Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format.

Z event

A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur.

Z table

A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as interface tables.

Z transaction

Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.

Index
A  B  C  D  E  F  H  I  J  L  M  N  O  P  R  S  T  U  V  W  X

A

Add EnterpriseOne Object to the Project form, 4.1.7

Adding a Version form, 4.1.7

adding batch versions

from the web client, 4.2.1, 4.2.5

in Object Management Workbench, 4.1.7

in the Batch Versions application, 4.1.5

understanding, 4.1.1

Advanced Operations form, 7.2.4 advanced options, overriding, 8.1.3 Advanced Version Prompting form, 8.2.4.1

B

batch delete, deleting data, 2.3

batch processing, overview, 2.2

Batch Version Design form, 4.1.7

batch version specifications

copying to an enterprise server, 6.3.1

location, 3.1

understanding, 6.1

batch versions

accessing BrowsER, 9.4.1

adding, 4.2.1

adding from the web client, 4.2.1, 4.2.5

adding in Object Management Workbench, 4.1.7

benefits of using, 2.5.2

changing data selection and data sequencing, 5.2.2

changing processing options for, 5.2.1

changing the design of, 7.2.4

characteristics of, 2.6.1

checking in and checking out, 6.2.1

copying from the Microsoft Windows client, 4.1.2

copying from the web client, 4.2.2

copying in Object Management Workbench, 4.1.8

copying in the Batch Versions application, 4.1.6

copying specifications to an enterprise server, 6.3

creating from the Microsoft Windows client, 4.1

creating in the Batch Versions application, 4.1.5

defining the Print Immediate option, 4.1.1

erasing the checking out, 6.2.2

making available from the web client, 8.3.1

modifying properties from the Microsoft Windows client, 5.2

overriding specifications, 7.2.1

overview, 2.5.2

submitting and printing, 8.1

submitting from the command line, 8.6

submitting from the web client, 8.1.1

submitting locally from the Microsoft Windows client, 8.2.2

submitting on the server from the Microsoft Windows client, 8.2.1

submitting table conversions, 2.3

understanding, 2.6, 2.6.2, 2.6.2, 3.1

understanding add, 3.1

understanding check in, 3.1

understanding copy, 3.1

understanding how to create from the web client, 2.6.2

understanding security for, 4.1.1

understanding submission, 3.2.1

understanding version detail, 5.5.1

Batch Versions (P98305)

adding batch versions, 4.1.5

copying batch versions, 4.1.6

Batch Versions (P98305) and (P98305W)

changing processing options for, 3.3

boolean logic, 8.1.1 BrowsER

accessing, 9.4.2

understanding, 9.4.1

C

central objects, checking in batch version specifications, 3.1

characteristics of batch versions, 2.6.1

check in, understanding, 6.2.1

check out

erasing the record, 6.2.2

understanding, 6.2.1

checking in batch versions, understanding, 3.1 comma separated valuesCSV, 8.1.5 command line submission

runube, 8.6.1

runubexml, 8.6.3

understanding, 8.6

conversion types, table conversions, 2.3 copying batch versions

from the web client, 4.2.2, 4.2.6

in Object Management Workbench, 4.1.8

in the Batch Versions application, 4.1.6

understanding, 4.1.2

with the Print Immediate option defined, 4.1.2

cover page

ayatem properties information, 9.5.1.2

printer properties information, 9.5.1.3

processing options information, 9.5.1.4

report interconnect information, 9.5.1.5

report level information, 9.5.1

report properties information, 9.5.1.1

section level information, 9.5.1

understanding, 9.5.1

CSV

defining at runtime, 8.1.5

defining in the batch version, 8.1.5

defining in the report template, 8.1.5

exporting at runtime, 8.2.4.6

formatting for exporting to, 8.1.5

location of output, 8.1.5

understanding, 8.1.5

D

data conversion, transferring and copying data, 2.3

data copy with table input, copying tables, 2.3

data copy, copying data, 2.3

data selection

accessing for table conversion versions from the web client, 5.4.3

changing for table conversion versions, 5.2.2

changing from the Microsoft Windows client, 5.2.6

changing from the web client, 5.3.6

defining using boolean logic, 8.1.1

submitting batch versions from the web client, 8.1.1

submitting batch versions locally from the Microsoft Windows client, 8.1.1

submitting batch versions on the server from the Microsoft Windows client, 8.1.1

understanding at runtime, 8.1.1

understanding changing, 5.2.2

data sequencing

changing from the Microsoft Windows client, 5.2.6

changing from the web client, 5.3.6

submitting batch versions from the web client, 8.1.1

submitting batch versions locally from the Microsoft Windows client, 8.1.1

submitting batch versions on the server from the Microsoft Windows client, 8.1.1

understanding at runtime, 8.1.1

understanding changing, 5.2.2

Data Sources form, 8.4.3 data, transferring, copying, and deleting, 2.3

E

enterprise server

copying batch version specifications to an, 6.3.1

overriding location at runtime, 8.2.2

reviewing jobs submitted to, 9.2.1

reviewing the job queue definition in the jde.ini, 5.5.4

specifications residing on, 8.1

submitting batch versions on an, 8.2.1

submitting batch versions to, 3.2.1

environment, checking in batch version specifications, 3.1

F

file types, report output options, 2.4

H

HTML, generating to, 4.2.3

I

iSeries

using runube, 8.6.2

J

JD Edwards Report Design Aid form, 7.2.4

JDE Data Source form, 8.2.4.1

JDEDEBUG.log

defining in advanced options, 8.1.3

enabling, 8.2.4.1

locating on the server, 9.6.1

jde.ini

defining the Print Immediate setting, 4.1.1

enabling logging, 8.2.4.1

enabling page-at-a-time, 8.3.1

reviewing the job queue definition, 5.5.4

reviewing the logging definition, 7.2.2

reviewing the StopAfterRow setting, 7.2.5

reviewing the Trace Level setting, 7.2.5

JDE.log

defining in advanced options, 8.1.3

enabling, 8.2.4.1

locating on the server, 9.6.1

jdeRequest.xml

code sample, 8.6.3

modifications required, 8.6.3

using to create and XML input file, 8.6.3

JITI, copying batch version specifications to the workstation, 3.2.1 job queue

reviewing the definition in the jde.ini, 5.5.4

Job Queue Search form, 8.4.3

L

local submission

exporting to CSV, 8.2.2

modifying data selection and data sequencing, 8.1.1

selecting output destinations, 8.2.2

logs

defining the level of detail to capture, 8.2.4.1

enabling logging, 8.2.4.1

enabling tracing, 8.2.4.1

locating, 9.6.1

selecting options for, 8.1.3

understanding, 9.6.1

understanding Microsoft Windows client generation, 9.6.1

understanding web client generation, 9.7.1

M

Microsoft Windows client

accessing properties for table conversion versions, 5.4.2

adding batch versions, 4.1.1

changing data selection and data sequencing, 5.2.6

changing processing options, 5.2.5

copying batch versions, 4.1.2

modifying properties of batch versions, 5.2

overriding advanced options at runtime, 8.2.4.1

overriding data selection and data sequencing at runtime, 8.2.4.2

submitting batch versions, 8.2.4.3

submitting batch versions locally, 8.2.2

submitting batch versions on the server, 8.2.1

submitting batch versions to a printer, 8.2.4.4

submitting versions of table conversions, 8.4.1

understanding logs, 9.6.1

modifying properties

from the Microsoft Windows client, 5.2

understanding, 5.1

N

naming conventions, 2.7

O

Object Management Configuration (P98230), 6.2.1

Object Management Workbench

adding batch versions, 4.1.7

copying batch versions, 4.1.8

Object Management Workbench form, 4.1.7 OSA

selecting at runtime, 8.2.4.6

understanding, 8.1.6

output

defining paper orientation, 8.2.4.5

defining the number of copies, 8.2.4.4

defining to print report immediately, 8.2.4.6

output destinations, submitting batch versions locally, 8.2.2 output management

modifying batch versions, 2.6.1

output options, 2.4

overriding output at runtime, 8.1.1

overview, 2.4

Output Stream AccessOSA, 8.1.6 override options, available when submitting batch versions, 2.6 overriding specifications

changing the design of batch versions, 7.2.4

changing versions of table conversions, 7.2.5

options available at the version level, 2.5.2

reading report template specifications, 7.2.1

understanding, 7.2.1

P

page-at-a-time, enabling in the jde.ini, 8.3.1

paper orientation, defining at runtime, 8.2.4.5

path code, checking in batch version specifications, 3.1

PDF, location of output, 8.1.5

performance, increasing for viewing reports on the web, 8.3.1

Print Immediate feature

copying batch versions with the Print Immediate option defined, 4.1.2

defining for all batch versions, 4.1.1

defining for individual batch versions, 4.1.1

print properties

overriding at runtime, 8.2.4.4

understanding, 8.1.4

Printer Selection form

Advanced tab, 8.2.4.7

Document Setup tab, 8.2.4.6

Print Property tab, 8.2.4.5

Printer Selection tab, 8.2.4.4

printers

defining options at runtime, 8.2.4.4

determining based on hierarchical structure, 8.1.4

understanding, 2.4

Printers (P98616), 8.1.4 PrintQueue, 8.1.5 processing

reports, 2.2

reviewing reports, 9.1

table conversions, 2.3

processing options

changing for Batch Versions (P98305) and (P98305W), 3.3

changing for Batch Versions on Microsoft Windows client (P98305), 3.3.3

changing for Batch Versions on web client (P98305W), 3.3.5

changing from the Microsoft Windows client, 5.2.5

changing values for batch versions, 5.2.1

changing values from the web client, 5.3.5

defining how to handle at runtime, 4.1.1

for Batch Versions on Microsoft Windows client (P98305), 3.3.2

for Batch Versions on web client (P98305W), 3.3.4

submitting batch versions locally, 8.1.2

submitting batch versions on the server, 8.1.2

understanding submission, 8.1.2

Processing Options form, 5.2.1 properties

accessing for table conversion versions, 5.4

accessing for table conversion versions from the Microsoft Windows client, 5.4.2

modifying from the Microsoft Windows client, 5.2

modifying from the web client, 5.3

overriding for table conversion versions, 7.2.2, 7.2.5

overriding print properties at runtime, 8.2.4.4

understanding print properties, 8.1.4

understanding table conversion properties at runtime, 8.4.1

Properties form, 7.2.5

R

RDASPEC files, 8.1.1

report components, overview, 2.5

report development

process, 2.5.1

Report Output Destination form, 8.2.4.3 report output, formats, 8.2.1 Report Properties form, 9.5.1.1 report templates

overriding specifications in batch versions, 7.2.1

overview, 2.5.1

reading specifications from, 2.5.2, 2.5.2

storing design specifications, 2.6

report templates, making available from the web client, 8.3.1 report versionsbatch versions, 2.5.2 report writing, overview, 2.1 runtime options

available from the web client, 8.3.1

runtime, overriding the Print Immediate option, 4.1.1 runube

command line components, 8.6.1

command line format using a text file, 8.6.2.2

prompting for user ID and password, 8.6.2.1

submitting batch versions from the command line, 8.6.1

submitting on Unix and iSeries, 8.6.2

runubexml

submitting batch versions from the command line, 8.6.3

S

Section Data Sequencing form, 8.1.1

security

defining for viewing jobs submitted by other users, 9.2.2

modifying, 5.5.4

understanding for batch versions, 4.1.1

Security Workbench (P00950), 4.1.1 StopAfterRow, defining in the jde.ini, 7.2.5 Submit Job - Add Version form, 4.2.5 Submit Job - Copy Version form, 4.2.6 Submit Job - EnterpriseOne Data Sources form, 8.5.3 Submit Job - Job Queue Search form, 8.5.3 Submit Job - Table Conversion Prompting form, 8.5.3 Submit Job - Work With Batch Versions - Available Versions form, 4.2.5 Submit Version Specifications Only option, 8.1 Submitted Job Search form, 9.2.1 submitted jobs

options, 9.2.3

reviewing jobs for other users, 9.2.2

understanding, 9.2.1

Submitted Jobs application

review options, 9.2.1

using, 9.2

submitting batch versions

override options available, 2.6

understanding, 3.2.1, 8.1

T

Table Conversion Prompting form, 8.4.3

Table Conversion Version Design form, 7.2.5

table conversion versions

accessing data selection from the web client, 5.4.3

accessing properties, 5.4

accessing properties from the Microsoft Windows client, 5.4.2

changing data selection, 5.2.2

overriding properties, 7.2.2, 7.2.5

submitting, 2.3

submitting from the Microsoft Windows client, 8.4.1

submitting from the web client, 8.5.1

transferring, copying, and deleting data, 2.3

table conversions

conversion types, 2.3

text files

command line format using runube, 8.6.2.2

using with runube, 8.6.2.2

U

Unix

using runube, 8.6.2

user ID and password security

prompting from the command line using runube, 8.6.2.1

using text files with runube, 8.6.2.2

V

Version Add form, 4.1.5, 4.1.7

Version Copy form, 4.1.6, 4.1.8

version detail

creating, 4.1.7

modifying, 5.5.4, 7.1

reviewing the check out of batch versions, 3.1

understanding, 5.5.1

Version Detail form, 3.1, 5.5.4 Version Prompting form, 8.2.4.2 Versions List (F983051) table

location of processing option values, 8.1.2

Versions List table (F983051)

location of processing option values, 5.2.1

server, 3.1

versionsbatch versions, 2.5.2

W

web client

accessing data selection for table conversion versions from the web client, 5.4.3

adding batch versions, 4.2.1, 4.2.5

changing data selection and data sequencing, 5.3.6

changing processing options, 5.3.5

copying batch versions, 4.2.2, 4.2.6

increasing performance for viewing reports, 8.3.1

making batch versions available, 8.3.1

making report templates available, 8.3.1

runtime options available, 8.3.1

submitting batch versions, 8.1.1, 8.3.1

submitting versions of table conversions, 8.5.1

understanding logs, 9.7.1

Work With Batch Versions - Available Versions form, 2.6.2 Work With Batch Versions form, 3.2.2 Work With Servers (P986116), 3.2.1, 8.1.5 Work With Servers form, 9.2.1

X

XML input files

creating, 8.6.3

using with runubexml, 8.6.3

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.