Search Results accounting_program_batch

Overview

XLA_ACCOUNTING_PUB_PKG is the public accounting engine interface in the Oracle E-Business Suite Subledger Accounting (XLA) module. It belongs to the APPS schema and holds VALID status in both 12.1.1 and 12.2.2. The package exposes the entry points through which subledger applications request creation of accounting entries for events captured in the XLA event model. Rather than embedding accounting logic in each subledger, Oracle centralizes the rule-based creation of journal entries in the XLA engine, and XLA_ACCOUNTING_PUB_PKG is the supported public API surface for driving that engine.

Its core responsibility is to accept a set of events or a batch of documents, determine the applicable accounting method and ledger, evaluate event class precedence and accounting rules, and produce the corresponding subledger journal entries. The package is the recommended call point for third-party and custom subledgers that need to create accounting without directly invoking internal XLA worker procedures.

Key Procedures and Functions

• ACCOUNTING_PROGRAM_BATCH — Initiates accounting for a defined batch of source documents. This is the batch-oriented entry point used when a set of transactions or business documents must be processed together under a single accounting request.
• ACCOUNTING_PROGRAM_DOCUMENT — Requests accounting for a single source document. This is the document-level entry point, typically used when processing must be scoped to one transaction entity rather than a batch.
• ACCOUNTING_PROGRAM_DOC_BATCH — Combines document-level and batch-level processing, allowing a specified set of documents to be submitted together for accounting creation and transfer.
• ACCOUNTING_PROGRAM_EVENTS — Drives accounting directly from previously created events in the XLA event tables, rather than from source documents. This entry point is used when events have already been generated and only accounting rule application remains.
• IS_HISTORIC_UPGRADE_RUNNING — A function that reports whether a historic upgrade process is currently active. Callers use it to suppress or defer accounting requests that would conflict with upgrade processing.

Tables Accessed

• XLA_EVENTS — the transactional event records that drive accounting creation; read to identify events requiring processing and updated with accounting status.
• XLA_TRANSACTION_ENTITIES — the header records for subledger transactions; used to resolve source documents to their owning entities.
• XLA_EVENT_CLASSES_B and XLA_EVENT_CLASS_PREDECS — define event classes and their precedence rules, which determine processing order and accounting applicability.
• XLA_EVT_CLASS_ORDERS_GT — a global temporary table holding the resolved event class ordering for the current run.
• XLA_ACCT_PROG_DOCS_GT and XLA_ACCT_PROG_EVENTS_GT — global temporary tables staging the documents and events passed into the accounting program entry points.
• GL_LEDGER_RELATIONSHIPS — resolves primary-to-secondary ledger relationships when accounting must be generated for related ledgers.
• DUAL — used for single-row queries and status checks.

Usage Notes

The package is invoked by the Create Accounting concurrent program, by subledger-specific accounting programs, and by application code such as XLA_ACCOUNTING_PKG, XLA_JOURNAL_ENTRIES_PKG, and XLA_CREATE_ACCT_RPT_PVT. It is also called from product packages including AP_DRILLDOWN_PUB_PKG, CST_XLA_PVT, CST_RECEIPTACCRUALPEREND_PVT, FV_IPAC, FV_TREASURY_PAYMENTS_PKG, LNS_DISTRIBUTIONS_PUB, and PSA_BC_XLA_PVT. Custom subledgers implementing an XLA integration should call these public entry points rather than internal XLA procedures, because the public signatures are the supported, upgrade-safe API. Callers should verify IS_HISTORIC_UPGRADE_RUNNING before submitting requests to avoid contention with upgrade processing.