Search Results accounting_program_events

Overview

APPS.XLA_ACCOUNTING_PUB_PKG is the public API package for the Oracle E-Business Suite Subledger Accounting (SLA) engine. Its documented purpose is to expose the accounting creation logic of the XLA schema so that external callers — subledger applications, concurrent programs, and custom code — can submit documents or batches of documents to the Accounting Program for accounting event processing. As stated in the package header, all public routines are thin wrappers over the internal routines in XLA_ACCOUNTING_PKG, which means the package provides a stable, supported calling surface while the underlying implementation remains private and subject to change between releases.

The package is present in both 12.1.1 and 12.2.2 and is classified under ETRM as API classification OTHER. It is referenced by nine other packages, confirming its role as an entry point rather than a terminal consumer of accounting data.

Key Procedures and Functions

The documented interface contains six procedures and functions:

• ACCOUNTING_PROGRAM_BATCH — Accounts for a set of documents in a single invocation. Per the package history, a p_source_application parameter was added to this API in September 2003.
• ACCOUNTING_PROGRAM_DOCUMENT — Accounts for a single document. This is the most heavily revised API in the package history: P_ENTITY_ID and P_ACCOUNTING_FLAG were added to the accounting_program_document signature in August 2003, the internal submit_request call to concurrent program XLAACCPB was corrected in December 2003 (Bug 3290398), and a valuation method workaround for XLA_EVENTS_PKG.get_entity_id was applied and later removed in 2005 (Bug 4323078), with get_accounting_document overloaded instead.
• ACCOUNTING_PROGRAM_DOC_BATCH — Processes documents in batch form, complementing the single-document and batch APIs.
• ACCOUNTING_PROGRAM_EVENTS — Drives accounting for events; this is the routine most directly associated with the "accounting_program_events" search term.
• IS_HISTORIC_UPGRADE_RUNNING — A function that reports whether a historical upgrade is in progress, allowing callers to suppress or defer accounting submission during upgrade windows.

Parameter lists are intentionally not reproduced here, as the documented metadata does not publish them. All OUT parameters received the NOCOPY hint as of July 2003.

Tables Accessed

The package and its wrapped routines operate against the following APPS synonyms:

• XLA_EVENTS — the core subledger event repository read to identify which events require accounting.
• XLA_EVENT_CLASSES_B, XLA_EVENT_CLASS_PREDECS, XLA_EVT_CLASS_ORDERS_GT — event class definitions, precedence rules, and class ordering used to sequence accounting program execution.
• XLA_TRANSACTION_ENTITIES — entity resolution, notably via get_entity_id as referenced in the 2005 bug fix history.
• GL_LEDGER_RELATIONSHIPS — ledger and secondary ledger mapping used during accounting derivation.
• XLA_ACCT_PROG_DOCS_GT and XLA_ACCT_PROG_EVENTS_GT — global temporary tables that carry document and event payloads into and out of the Accounting Program.
• DUAL — used for single-row PL/SQL evaluations and validation checks.

Usage Notes

This package is normally invoked indirectly. Subledger applications call the public APIs to submit accounting for a document, a document batch, or a set of events; the routine then either accounts for the data inline or submits the XLAACCPB concurrent program, as evidenced by the submit_request correction recorded in the package history. Concurrent programs such as the Accounting Program and Create Accounting rely on this interface, and custom integrations should call these APIs rather than the private XLA_ACCOUNTING_PKG routines.

Callers should check IS_HISTORIC_UPGRADE_RUNNING before submitting accounting, particularly during upgrades that re-derive historical entries. Because the package depends on event class precedence and ordering data, callers must ensure event classes are properly configured. Local trace support and FND_LOG messages, added in February and March 2004, allow diagnostic tracing by module when debugging accounting failures.