Reviewing Batch Version Processing

This chapter provides an overview of resources for reviewing reports and discusses how to:

Click to jump to parent topicUnderstanding 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:

Click to jump to parent topicUsing the Submitted Jobs Application

This section discusses:

Click to jump to top of pageClick to jump to parent topicSubmitted 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:

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.

Click to jump to top of pageClick to jump to parent topicSubmitted Jobs For Other Users

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

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.

Click to jump to top of pageClick to jump to parent topicSubmitted Jobs Options

On the Submitted Job Search form, you can:

Note. For options that apply to JD Edwards XML Publisher functionality, see JD Edwards EnterpriseOne Tools 8.97 XML Publisher Guide.

See Also

Working with Servers

Getting Started with JD Edwards EnterpriseOne XML Publisher

Click to jump to parent topicAccessing 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.

Click to jump to top of pageClick to jump to parent topicAccessing 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

Accessing BrowsER for Report Templates

Click to jump to top of pageClick to jump to parent topicForms 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.

Click to jump to parent topicReviewing the Cover Page

This section discusses the cover page.

Click to jump to top of pageClick to jump to parent topicThe 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:

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

Report Properties

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

System Properties

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

Printer Properties

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

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.

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.

Click to jump to parent topicGenerating 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.

Click to jump to top of pageClick to jump to parent topicUnderstanding 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:

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.

Click to jump to top of pageClick to jump to parent topicForms 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.

Click to jump to parent topicGenerating 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.

Click to jump to top of pageClick to jump to parent topicUnderstanding 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.

Click to jump to top of pageClick to jump to parent topicForms 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.