Search Results xla_events_s




Overview
Explore in AI Chat

Overview

APPS.PA_BILL_REV_XLA_UPGRADE is a PL/SQL package body in the Oracle E-Business Suite Applications schema (APPS). Its name and dependency profile identify it as a one-time upgrade utility used during the transition of Oracle Projects billing and revenue accounting data from the legacy Subledger Accounting (SLA) architecture into the Extensible Accounting (XLA) model. In releases 12.1.1 and 12.2.2, Oracle Projects no longer writes revenue and billing distributions directly to General Ledger; instead, distributions are staged, linked to transaction entities and events, and ultimately posted through the XLA engine, which persists them in the XLA_AE_HEADERS, XLA_AE_LINES, XLA_EVENTS, XLA_DISTRIBUTION_LINKS and XLA_TRANSACTION_ENTITIES tables.

This package performs the bulk conversion of pre-existing Project revenue and billing data into those XLA structures. It reads legacy distribution rows from the Project tables, evaluates the associated events and event types, and inserts the corresponding XLA event, accounting entry header, accounting entry line, and distribution link records. Because the volume of historical transactions is typically very large, the package is built around temporary staging tables and parallel processing utilities rather than row-by-row processing.

Key Procedures and Functions

  • UPGRADE_TRANSACTIONS — the primary driver for converting standard (non-multicurrency) Project billing and revenue transactions into XLA accounting entries. It controls the overall upgrade flow for the primary ledger set.
  • UPGRADE_MC_TRANSACTIONS — the multicurrency counterpart to UPGRADE_TRANSACTIONS, processing transactions associated with reporting or secondary ledgers tracked in the PA_MC_* tables.
  • CON_UPGRADE_TRANSACTIONS — a wrapper or continuation entry point used to orchestrate or resume the upgrade process, typically invoked after staging or parallel batch preparation.
  • REV_UPG_AD_PAR — a parallel-processing procedure that drives revenue upgrade work across requested parallel workers, delegating to the AD_PARALLEL_UPDATES_PKG infrastructure.
  • REV_UPG_MC_AD_PAR — the multicurrency variant of the revenue parallel procedure, applying the same parallel worker mechanism to PA_MC_CUST_EVENT_RDL_ALL and PA_MC_DRAFT_REVS_ALL data.
  • GL_IMP_UPG_AD_PAR — a parallel procedure responsible for upgrading GL import reference information so that the migrated XLA entries retain their linkage back to the corresponding GL journal headers and lines (GL_IMPORT_REFERENCES, GL_JE_HEADERS).

Tables Accessed

The package references Project source tables including PA_DRAFT_REVENUES_ALL, PA_CUST_REV_DIST_LINES_ALL, PA_CUST_EVENT_RDL_ALL, PA_EVENTS, PA_EVENT_TYPES, PA_PROJECTS_ALL, PA_IMPLEMENTATIONS_ALL, and the multicurrency equivalents PA_MC_DRAFT_REVS_ALL, PA_MC_CUST_RDL_ALL and PA_MC_CUST_EVENT_RDL_ALL. It also draws on HR_ORGANIZATION_INFORMATION to resolve organization context.

Staging and control objects include PA_XLA_DRAFT_REV_TMP, PA_XLA_LINES_TMP, PA_REV_AE_LINES_TMP, PA_PRIM_REP_LEGER_TMP and PA_XLA_UPG_CTRL, which track upgrade progress and hold intermediate conversion rows. The target XLA tables written are XLA_EVENTS, XLA_EVENTS_S, XLA_AE_HEADERS, XLA_AE_HEADERS_S, XLA_AE_LINES, XLA_DISTRIBUTION_LINKS, XLA_TRANSACTION_ENTITIES_S, XLA_TRANSACTION_ENTITIES_UPG, XLA_UPG_BATCHES_S and XLA_GL_SL_LINK_ID_S. GL_IMPORT_REFERENCES and GL_JE_HEADERS provide the legacy GL linkage data.

Usage Notes

PA_BILL_REV_XLA_UPGRADE is not intended for routine, online execution. It is a migration utility invoked during the upgrade to Release 12 and, in some cases, when re-running the billing and revenue portion of the SLA upgrade for a set of projects. It is typically launched from the Oracle Projects SLA upgrade concurrent program or from a controlled SQL*Plus session operated by a DBA, using the parallel AD_PARALLEL_UPDATES_PKG framework for scalability.

The presence of XLA_UPG_BATCHES_S and XLA_TRANSACTION_ENTITIES_UPG confirms that processing is batched and restartable. The package is documented as not referenced by any other database object, indicating it is a terminal, standalone upgrade component rather than a runtime dependency of standard Project processing. Customizations should not call these procedures directly; the upgrade should instead be executed through the sanctioned Oracle-supplied upgrade driver to preserve sequencing with PA_XLA_UPG_CTRL and the XLA upgrade control tables.