Diagnose Subledger Accounting Event Data

You can use the diagnostic framework to know why the accounting was created in a particular way or why there are errors.

The diagnostic framework stores data that is used in the creation of a journal entry so you can use the data to analyze accounting issues. It provides the transaction data that is referenced during accounting through accounting rules and ledger setup. Most errors occur because either the source system information or the accounting rules are not as expected.

Here are some ways in which you can use the diagnostic framework.

  • In the implementation phase, you can launch the Accounting Event Diagnostic report to review the source values available in the transaction objects.

  • On a daily basis, you can use the Accounting Event Diagnostic report to troubleshoot exceptions.

Diagnostic Framework Features

The diagnostic framework features are as follows:

  • SLA: Diagnostic Enabled: This option controls whether diagnostic information is gathered by the Create Accounting process. Use with caution. Selecting this option can cause slow performance.

  • Diagnostic Framework Execution: When the SLA: Diagnostic Enabled option is set to Yes, the diagnostic framework is executed simultaneously with the Create Accounting process. The diagnostic framework data is stored in the diagnostic tables.

  • Accounting Event Diagnostic Report: To view the diagnostic framework report, users submit the Accounting Event Diagnostic process with the appropriate report parameters.

  • Purge Accounting Event Diagnostic Data: Purging is useful when accounting is successfully created so that the volume of information in the report does not increase to a point where it becomes unusable.

    Diagnostic framework data purged:

    • When the data collected can be purged by running the process.

    • When the administrator launches the Purge Accounting Event Diagnostic Data process.

Diagnostic Framework Business Process Flow

The following steps describe the diagnostic framework business process flow:

  1. The administrator sets the SLA: Diagnostics Enabled option to Yes for the user or responsibility.

  2. Users submit the Create Accounting process that automatically executes the diagnostic framework to populate the diagnostic tables. The diagnostic framework gathers source values and other information from the transaction objects.

  3. Users submit the Accounting Event Diagnostic process to view the diagnostic report. Based on the information in the diagnostic report, users may determine if additional or resubmission of information from source systems is required. They may also determine if any updates to the accounting rules is required.

  4. Users run the Create Accounting process again to generate subledger journal entries for events that had an error.

  5. The administrator submits the Purge Accounting Event Diagnostic Data process to purge the results of the diagnostic framework.