Configuring a Report Service Request

Use a report service request to invoke a batch version of an EnterpriseOne report from an orchestration. You can configure a report service request to use the settings defined for the report in the Batch Versions program. Or you can configure it to override the processing options, data selection, and data sequencing of a report.

You can also create a report service request to invoke an embedded BI Publisher report, and configure it to use the default settings or override the settings.

A report service request can launch EnterpriseOne reports designed with report interconnects. Report interconnects are inputs added to a report at design time, which enable a report to run automatically without user interaction. Typically, report interconnects are used to launch a report from a button or exit on an EnterpriseOne form.

In the Report design page, the "Fire and Forget" option enables the report to run asynchronously. When the Orchestrator executes the orchestration, this option enables the orchestration to continue to the next action or step without waiting for the report to complete.

At runtime, when the Orchestrator processes the report service request, it respects the EnterpriseOne authorization security for the report. The user initiating the orchestration must be authorized to run the batch version of the report as defined by an administrator in the Security Workbench. If the report service request includes data selection or processing option overrides, the user initiating the orchestration must be authorized in the Security Workbench to perform these overrides as well.

To configure a report service request:

  1. Create and name the report service request as described in Creating a Service Request.

  2. In the Report field, enter the ID of the report that you want the report service request to invoke.

    The Orchestrator Studio loads all versions associated with the report in the Version drop-down list.

  3. Click the Version drop-down list and select a version of the report.

    The Orchestrator Studio loads any settings defined for the version in EnterpriseOne, including data selection, data sequencing, processing options, and output options.

  4. Enable Fire and Forget if you want the report to run asynchronously.

    If you do not enable this setting, if added to an orchestration that has steps following the report service request, the remaining steps will not execute until the report finishes.

  5. Select one of the following options to determine how to run the report:

    • Blind Execution. Select this option if you want the report service request to invoke the batch version using the settings defined in EnterpriseOne for the report version.

      You can review the settings defined for the version by expanding the Data Selection, Data Sequencing, and Processing Options sections.

    • Report Interconnects. If a report is defined with report interconnects, select this option and enter the values you want to pass into the report in the available fields. This option is disabled if no report interconnects were defined for the report.

    • Override Version. Select this option to override the settings in EnterpriseOne for the version of the report, and then perform these steps:

      1. For Data Selection and Data Sequencing, expand the sections to modify existing criteria, or click the Add button to define new criteria.

      2. Expand the Processing Options section and change the settings as desired.

  6. Click the Queue Name drop-down list and select the queue to which the reported is submitted. If you leave this field blank, when this report is invoked, the system uses the default queue defined in the Enterprise Server configuration settings.

  7. To modify the print properties defined for the report, click Output Options and complete the fields as appropriate.

    For more information about report output options, see "Report Output" in the JD Edwards EnterpriseOne Tools Report Printing Administration Technologies Guide.

  8. To enable logging for the report, click Output Options and then enable the JDE Log toggle. Enter a value from 0-6 in the Logging Level field to indicate the level of detail to be captured in the logs.

    Any value greater than 0 will force the system to write both the JDE and JDEDEBUG logs. 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).