Search Results xla_ae_headers_s




Overview

ARP_MRC_XLA_UPGRADE is an Oracle E-Business Suite upgrade utility package owned by the APPS schema. Its purpose is to migrate historical Multi-Reporting Currency (MRC) accounting data into the Subledger Accounting (XLA) model introduced in Release 12. Prior to R12, multi-currency accounting entries in Receivables were stored in the MRC shadow tables (the AR_MC_* and RA_MC_* families). With the introduction of Subledger Accounting, these entries must instead be represented as accounting events, journal entry headers, and journal entry lines in the XLA schema. ARP_MRC_XLA_UPGRADE performs that controlled conversion for Receivables transactions, receipts, and adjustments, ensuring that pre-upgrade MRC balances are visible and reconcilable through the standard XLA inquiry and reporting infrastructure after the upgrade.

The package is part of the broader XLA upgrade framework and depends on APPS.AD_PARALLEL_UPDATES_PKG, indicating that its upgrade routines are designed to be executed in parallel worker processes during the upgrade window. It also references XLA_UPGRADE_DATES, the framework table that records cutoff and processing dates used to determine which source records require conversion. The package is documented as an OTHER classified API rather than a public callable interface, confirming that it is intended for internal upgrade processing rather than routine application or customer invocation. It is not referenced by any other database object, which is consistent with its role as a terminal upgrade process invoked by the upgrade driver.

Key Procedures and Functions

The package body exposes three documented procedures, each targeting a distinct category of Receivables MRC data:

All three procedures write to the XLA_AE_HEADERS and XLA_AE_LINES tables through the header sequence XLA_AE_HEADERS_S, and populate the linking tables XLA_DISTRIBUTION_LINKS and XLA_GL_SL_LINK_ID_S to establish traceability between the new XLA entries and their originating source distributions and General Ledger link identifiers.

Tables Accessed

Source data is read from the standard Receivables base tables and their MRC counterparts through APPS synonyms: AR_ADJUSTMENTS_ALL, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_MISC_CASH_DISTRIBUTIONS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL, AR_TRANSACTION_HISTORY_ALL, RA_CUSTOMER_TRX_ALL, and RA_CUST_TRX_LINE_GL_DIST_ALL, together with the MRC shadow tables AR_MC_ADJUSTMENTS, AR_MC_CASH_RECEIPTS, AR_MC_CASH_RECEIPT_HIST, AR_MC_DISTRIBUTIONS_ALL, AR_MC_MISC_CASH_DISTS, AR_MC_RECEIVABLE_APPS, RA_MC_CUSTOMER_TRX, and RA_MC_TRX_LINE_GL_DIST. GL_SETS_OF_BOOKS supplies reporting ledger context for the conversion.

On the target side, the package inserts into XLA_AE_HEADERS (via sequence XLA_AE_HEADERS_S), XLA_AE_LINES, XLA_DISTRIBUTION_LINKS, and XLA_GL_SL_LINK_ID_S, and reads conversion control dates from XLA_UPGRADE_DATES. Each source distribution is matched to a newly created XLA journal line so that Subledger Accounting balances reconcile to the legacy MRC balances.

Usage Notes

ARP_MRC_XLA_UPGRADE is invoked by the R12 upgrade driver during the transition from Release 11i to Release 12, and by subsequent XLA MRC upgrade processes for environments where MRC data remains to be converted. It is driven programmatically, typically as parallel workers orchestrated through AD_PARALLEL_UPDATES_PKG, and is not exposed through a Receivables form or a customer-facing concurrent program. Because the package performs bulk inserts into the XLA accounting tables, it should only be executed within the sanctioned upgrade sequence, after XLA_UPGRADE_DATES has been populated and before accounting is resumed. Direct invocation in a production runtime environment is not supported; customers requiring MRC-to-XLA conversion outside the standard upgrade path should use Oracle-supplied upgrade or diagnostic concurrent programs rather than calling these procedures directly.