Analyzing Oracle E-Business Suite Metrics

The Latest Requests subtab shows a breakdown of the statuses assigned to the processes that execute the requests, as well as all the batch job executions in order of execution for the selected environment, as explained in the following sections:

• EBS Status Breakdown Table

• Top Longest Batch Requests Run by <environment name> Table

EBS Status Breakdown Table

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment. The Run By tab is displayed by default, showing the Latest Requests sub tab, with the EBS Status Breakdown table at the top of the tab.

The EBS Status Breakdown table shows a breakdown of the statuses assigned to the processes that execute the requests.

Each record in the EBS Status Breakdown table provides the following information:

• Process Name: Specifies the name of each batch process in each process scheduler domain supporting the selected environment.

• Status: Specifies the state of the process executing jobs the selected environment. Available options include:

  • Up

  • Down

Top Longest Batch Requests Run by <environment name> Table

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view option is displayed by default. Click any EBS batch job transaction record associated with an environment. The Run By tab is displayed by default. Scroll down the Latest Requests sub tab to see the Top Longest Batch Requests Run by <environment name> table.

The Top Longest Batch Requests Run by <environment name> table shows all the batch job executions in order of execution for the selected environment.

Each record in the Top Longest Batch Requests Run by <environment name> table provides the following information:

• Program Name: Specifies the name of the program required to run the concurrent request.

• Program Short Name: Specifies the short name of the program required to run the concurrent request.

• Request ID: Specifies the concurrent request ID.

• Manager Name: Specifies the name of the concurrent manager running the request.

• EBS Request Start Date: Specifies the date and time when the concurrent request's start message was received.

• Running Time: Specifies for how long the request has been running, in days, hours, minutes, and seconds, as applicable.

• Phase: Specifies the Oracle Applications transaction phase. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.

• Status: Specifies the Oracle Applications transaction status. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.

• Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.

The Historical Requests sub tab shows the top concurrent programs for the batch job, listed by runtime, during the period between the specified dates and times. Use the drop-down list in the upper left corner of the page to see only specific batch job programs, as explained in the following sections:

• Top Concurrent Programs by Runtime Table

• Top Concurrent Programs by Count Table

Top Concurrent Programs by Runtime Table

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Historical Requests. The Top Concurrent Programs by Runtime table is displayed by default.

The Top Concurrent Programs by Runtime table shows the batch job programs with the highest runtime, allowing you to easily identify batch jobs with the longest execution time. By default, this report shows data for 24 hours before the current date. To define a custom reporting period, click the widget time selector above the chart, as explained in the Generating Reports for Different Time Periods section in Working with Oracle Pulse.

Each record in the Top Concurrent Programs by Runtime table provides the following information:

• Program Short Name: Specifies the short name of the program required to run the concurrent request.

• Program Name: Specifies the name of the program required to run the concurrent request.

• Successful Executions (%): Shows the percentage of concurrent requests that completed successfully - that is, without warnings or errors.

• Total Executions: Shows the total number of concurrent requests run for the batch job.

• Total Runtime: Shows the total runtime for all concurrent requests run for the batch job.

• Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.

Top Concurrent Programs by Count Table

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Historical Requests and select Top Concurrent Programs by Count from the list.

The Top Concurrent Programs by Count table shows the batch jobs with the greatest number of concurrent requests during the report interval. By default, this report shows data for 24 hours before the current date. To define a custom reporting period, click the widget time selector above the chart, as explained in the Generating Reports for Different Time Periods section in Working with Oracle Pulse.

Each record in the Top Concurrent Programs by Count table provides the following information:

• Program Name: Specifies the name of the program required to run the concurrent request.

• Program Short Name: Specifies the short name of the program required to run the concurrent request.

• Total Executions: Shows the total number of concurrent requests run for the batch job.

• Successful Executions (%): Shows the percentage of concurrent requests that completed successfully.

• Error Executions (%): Shows the percentage of concurrent requests that did not complete successfully.

• Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status. The Current View tab is displayed by default, with the Last 1 Hour Status table at the top of the tab.

The Current View tab shows the number of concurrent programs that have completed with a Success status and those that have completed within the median, 75th percentile, and 95th percentile of the runtime of the jobs completed successfully in the last hour.

Each record in the Last 1 Hour Status table provides the following information:

• Collection Date: Specifies the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.

• Inactive No Manager: Shows the number of requests that could not be run in the last hour and for which no concurrent manager has been defined.

• Inactive On Hold: Shows the number of pending requests that could not be run in the last hour.

• Pending Normal: Shows the number of requests run in the last hour that are waiting for the next available concurrent manager.

• Pending Standby: Shows the number of requests run in the last hour for which the required program is incompatible with other program(s) currently running.

• Running: Shows the number of requests that have been running in the last hour.

• Completed Warnings: Shows the number of requests run in the last hour that completed with warnings.

• Completed Errors: Shows the number of requests run in the last hour that failed to complete successfully.

• Completed Success: Shows the number of requests run in the last hour that completed successfully.

• Total Requests: Shows the total number of requests run in the last hour.

• Normal Runtime: Shows the number of requests run in the last hour that completed successfully and whose runtime is below the 75th percentile of the runtime of the jobs completed successfully in the last 31 days.

• Above Average Runtime: Shows the number of requests run in the last hour that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the runtime of the jobs completed successfully in the last 31 days.

• High Runtime: Shows the number of requests run in the last hour that completed successfully, whose runtime is greater than or equal to the 95th percentile of the runtime of the jobs completed successfully in the last 31 days.

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status and go to the Last 24 Hours sub tab. The 24 Hours Summary chart is displayed at the top of the tab.

The Last 24 Hours sub tab shows the number of concurrent programs that have completed with a Success status and those that have completed within the median, 75th percentile, and 95th percentile of historical runtime.

Chart View: The chart view shows the number of concurrent programs of each status for each hour in the previous 24 hours.

Click Open Table View in the lower right corner of the chart to open the 24 Hours Summary table view in expanded mode.

Table View: The table view shows the number of concurrent programs of each status for each hour in the previous 24 hours.

Each record in the 24 Hours Summary table provides the following information:

• Collection Date: Shows the date and time when these metrics were collected from Oracle Enterprise Manager and Oracle E-Business Suite.

• Inactive No Manager: Shows the number of requests that could not be run in the last 24 hours and for which no concurrent manager has been defined.

• Inactive On Hold: Shows the number of pending requests that could not be run in the last 24 hours.

• Pending Normal: Shows the number of requests run in the last 24 hours that are waiting for the next available concurrent manager.

• Pending Standby: Shows the number of requests run in the last 24 hours for which the required program is incompatible with other program(s) currently running.

• Running: Shows the number of requests that have been running in the last 24 hours.

• Completed Warnings: Shows the number of requests run in the last 24 hours that completed with warnings.

• Completed Errors: Shows the number of requests run in the last 24 hours that failed to complete successfully.

• Completed Success: Shows the number of requests run in the last 24 hours that completed successfully.

• Total Requests: Shows the total number of requests run in the last 24 hours.

• Normal Runtime: Shows the number of requests run in the last 24 hours that completed successfully and whose runtime is below the 75th percentile of the historical runtime.

• Above Average Runtime: Shows the number of requests run in the last 24 hours that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the historical runtime.

• High Runtime: Shows the number of requests run in the last 24 hours that completed successfully, whose runtime is greater than or equal to the 95th percentile of the historical runtime.

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status and go to the Last 31 Days sub tab. The 31 Days Summary chart is displayed at the top of the tab.

The Last 31 Days subtab shows the number of concurrent programs that have completed with a Success status and those that have completed within the median, 75th percentile, and 95th percentile of historical runtime in the previous 31 days.

Chart View: The chart view shows the number of concurrent programs of each status for each of the last 31 days.

Click Open Table View option in the lower right corner of the chart to open the 31 Days Summary table view in expanded mode.

Table View: The table view shows the number of concurrent programs of each status for each of the last 31 days.

Each record in the 31 Days Summary table provides the following information:

• Calendar Date: Indicates the date when the requests were run.

• Inactive No Manager: Shows the number of requests that could not be run in the last 31 days and for which no concurrent manager has been defined.

• Inactive On Hold: Shows the number of pending requests that could not be run in the last 31 days.

• Pending Normal: Shows the number of requests run in the last 31 days that are waiting for the next available concurrent manager.

• Pending Standby: Shows the number of requests run in the last 31 days for which the required program is incompatible with other program(s) currently running.

• Running: Shows the number of requests that have been running in the last 31 days.

• Completed Warnings: Shows the number of requests run in the last 31 days that completed with warnings.

• Completed Errors: Shows the number of requests run in the last 31 days that failed to complete successfully.

• Completed Success: Shows the number of requests run in the last 31 days that completed successfully.

• Total Requests: Shows the total number of requests run in the last 31 days.

• Normal Runtime: Shows the number of requests run in the last 31 days that completed successfully and whose runtime is below the 75th percentile of the historical runtime.

• Above Average Runtime: Shows the number of requests run in the last 31 days that completed successfully, whose runtime is greater than or equal to the 75th and less than the 95th percentile of the historical runtime.

• High Runtime: Shows the number of requests run in the last 31 days that completed successfully, whose runtime is greater than or equal to the 95th percentile of the historical runtime.

Location: On the Transactions dashboard at Customer and Service Level. The Transactions List view is displayed by default. Click any EBS batch job transaction record associated with an environment, then click Status and go to the Historical Request sub tab.

The Historical Request sub tab shows the requests that completed with error, the long pending requests, the pending requests, the requests that completed with warning, as well as the requests that completed with success over the 24 hours before the specified date. You can see table data for each of the aforementioned reports using the ALL category, which facilitates comparison across the categories, and may help you determine the conditions under which specific jobs can be more successful.

By default, this report shows data for 24 hours before the current date. To define a custom reporting period, click the widget time selector above the chart, as explained in the Generating Reports for Different Time Periods section in Working with Oracle Pulse.

Use the drop-down list in the upper left corner of the page to see only specific requests for the selected batch job:

• ALL: Shows all requests that were run over the 24 hours before the specified date. This is the default selection.

• Requests Completed with Error: Shows concurrent requests that were completed with error over the 24 hours before the specified date. Oracle recommends that you investigate any errors.

• Long Pending Requests: Shows concurrent requests with a long Pending phase over the 24 hours before the specified date.

• Pending Requests: Shows concurrent program requests that have been in Pending phase over the 24 hours before the specified date, with any of the associated status values.

• Requests Completed with Warning: Shows concurrent program requests that were completed with one or more warnings over the 24 hours before the specified date. Oracle recommends that you investigate any warnings.

• Requests Completed Successfully: Shows concurrent program requests that were successfully completed over the 24 hours before the specified date.

Each record in the Historical Request report provides the following information:

• Request ID: Specifies the concurrent request identifier.

• Request Manager: Indicates the concurrent manager handling the concurrent request. Depending on how the batch job is configured in Oracle Enterprise Manager and Oracle E-Business Suite, this field may be blank.

• Requested by User: Specifies the identifier of the user who submitted the concurrent request.

• Phase: Specifies the Oracle Applications transaction phase. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.

• Status: Specifies the Oracle Applications transaction status. For more information, see Analyzing Performance for Oracle E-Business Suite Concurrent Managers and Programs.

• Program Name: Specifies the name of the program required to run the concurrent request.

• Program Short Name: Specifies the short name of the program required to run the concurrent request.

• EBS Request Start Date: Specifies the date and time when the concurrent request was started.

• Execution Time: Specifies the date and time when the concurrent request was run.