Online Accounting Engine

The online accounting engine supports online accounting for subledger transactions.

Any user who submits the online accounting for the first time launches this process that stays running in the background. The subsequent user who submits online accounting uses the same process to generate online accounting until this process is terminated. Then the following user who submits online accounting relaunches this background process.

This process generates accounting when you choose to either Account in Draft or Post to Ledger from the Subledger Transaction UI.

If any error/exception is encountered during event processing, the Provide Online Transaction Engine exits, and the system invokes another process to replace it, waiting for another online accounting request. You can always run Create Accounting in batch mode to get more details if you encounter an online engine error or an online accounting request error.

The enhanced Provide Online Transaction Engine Functionality program allows submission of the program by a predefined user FUSION_APPS_FIN_ODI_ESS_APPID with the appropriate privileges to run, create accounting, and post to General Ledger. This prevents users who access a subledger user interface without the appropriate privileges from causing online accounting to fail.

The accounting period status and other setups may be cached if the accounting period is open. If you get an error, terminate the 'Provide Online Transaction Engine Functionality' process and trigger online accounting or submit the Create Accounting process to generate accounting.

Why is Provide Online Transaction Engine Functionality (XLAOTEC) process not completed?

This is the expected behavior of an online accounting engine. By design, you should see four processes running in the background, ready to accept online accounting requests initiated from the UI. You can configure the four running engines based on the environmental needs.

If system or ESS issues require stopping or canceling running processes, these processes can be ended manually. Once a user initiates another online accounting request, the system brings up another set of processes titled 'Provide Online Transaction Engine Functionality.'

How can I provide users access to the output and log files for the Provide Online Transaction Engine Functionality ESS process?

Sign in to the Security Console as a security manager and perform the following steps:

1. Create a job role for the users who require access.
2. Create a data security policy for the ESS_REQUEST_HISTORY object. The Policy page has General Information, Role, Rule, and Action tabs.

   1. Assign the new job role to the policy.

   2. Create a rule and select this value for the condition: ESS requests submitted by the Accounting Automation process.

   3. To allow users to view the log and output files, select these actions: ESS_REQUEST_READ, ESS_REQUEST_OUTPUTREAD.

   4. To allow users to cancel the Accounting Automation job, select the ESS_REQUEST_CANCEL action.