Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 29

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 32

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 138

Strict Standards: Non-static method JRequest::clean() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 33

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 463

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 464

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 465

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 466

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 467

Strict Standards: Non-static method JRequest::_cleanArray() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/environment/request.php on line 468

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 35

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 38

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 39

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::load() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 161

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 138

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 46

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 47

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 50

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 53

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::import() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 54

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/loader.php on line 71

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 57

Strict Standards: Non-static method JLoader::register() should not be called statically in /home/content/19/13966119/html/adivanew/libraries/joomla/import.php on line 58

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/libraries/joomla/session/session.php on line 423

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/libraries/joomla/session/session.php on line 423

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/libraries/joomla/session/session.php on line 426

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/templates/ja_kyanite_ii/libs/ja.template.helper.php on line 119

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/templates/ja_kyanite_ii/libs/mobile_device_detect.php on line 113

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/templates/ja_kyanite_ii/libs/mobile_device_detect.php on line 114

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/templates/ja_kyanite_ii/libs/mobile_device_detect.php on line 113

Warning: Cannot modify header information - headers already sent by (output started at /home/content/19/13966119/html/adivanew/libraries/joomla/import.php:29) in /home/content/19/13966119/html/adivanew/templates/ja_kyanite_ii/libs/mobile_device_detect.php on line 114
BI Publisher for JD Edwards EnterpriseOne : Associating Report Definitions with Batch Versions
You are here: Blog JD Edwards - BI Publisher BI Publisher for JD Edwards EnterpriseOne : Associating Report Definitions with Batch Versions

Warning: Creating default object from empty value in /home/content/19/13966119/html/adivanew/components/com_k2/models/item.php on line 614

BI Publisher for JD Edwards EnterpriseOne : Associating Report Definitions with Batch Versions

Rate this item
(0 votes)

BI Publisher for JD Edwards Enterpriseone - Online Training

Objectives

• After completing this lesson, you will be able to:

– Use Object Management Workbench to associate a report definition with a batch version.

– Use the Batch Versions application to associate a report definition with a batch version.

Report Definitions and Batch Versions

• A report definition can be submitted from the Batch Versions application if it has been associated with a version.

This is an example of the Work With Batch Versions form on the web client.

Associate Report Definitions with Batch Versions

• To associate a report definition with a batch version, the version must first be checked out.

Check Out Version

A version can be checked out from:

• Object Management Workbench.

• Batch Versions on the Microsoft Windows client.

Object Management Workbench

 

Batch Versions

 Default Report Definition Form

• After the version is checked out, use either OMW or Batch Versions to access the Default Report Definition form.

Access Default Report Definition from OMW

• The Revise Version button provides access to the Version Detail form, which has a form exit to the Default Report Definition.

Access Default Report Definition from OMW

1. In an OMW project, select a version and then click the Design button.

2. On the Batch Version Design form, click the Revise Version button. 

Follow these steps to associate a report definition with a checked-out batch version through OMW:

3. On the Version Detail form, select Report Definition from the Form menu.

4. Enter the name of a report definition in the Report Definition field and click OK.

5. Promote the batch version through the OMW project life cycle. 

Access Default Report Definition from Batch Versions

• Batch Versions has a Version Detail row exit. The Version Detail form has a form exit to the Default Report Definition

 Access Default Report Definition from Batch Versions

1. Locate the version in Batch Versions and select Version Detail from the Row menu.

2. On the Version Detail form, select Report Detail from the Form menu.

Follow these steps to associate a report definition with checked-out batch version:

3. On the Default Report Definition form, select Report Definition from the Form menu.

4. Enter the name of a report definition in the Report Definition field and click OK.

5. Promote the batch version through the OMW project life cycle.

Assessment

The following assessment tests your knowledge of associating a report definition with a batch version.

Assessment (1)

• Question: The Default Report Definition form enables users to associate a report definition with a batch version.

Assessment (2)

• Question: The Default Report Definition form can be accessed through either Batch Versions or through the Report Definitions application.

 

Review

• In this lesson, you learned how to:

– Use Object Management Workbench to associate a report definition with a batch version.

– Use the Batch Versions application to associate a report definition with a batch version.

Read 23692 times

Leave a comment

Make sure you enter the (*) required information where indicated.
Basic HTML code is allowed.