Last updated on JULY 24, 2017
Applies to:Oracle Financials Accounting Hub - Version 12.0.0 and later
Information in this document applies to any platform.
In FAH customer receives many events from the feeder system but wants to process them selectively, some should be accounted, some should not be accounted and put up for later.
They do not want to use the standard Create Accounting (CA) process (which works well otherwise) because it picks up all the events eligible for accounting.
So, customer decided to write their own custom process where they insert specific events of a certain class and ledger into the table XLA_ACCT_PROG_EVENTS_GT and then trigger accounting via a call to the public API XLA_ACCOUNTING_PUB_PKG.accounting_program_events.
The issue is that when, for example, they insert 2 events with distinct event_id and ledger_id they can see 4 Create Accounting programs being spawned for processing these events.
The API should not spawn multiple Create Accounting programs or, rather, should not spawn any.
Using the API in custom code.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms