Search Results upgrade_mc_receipts

Overview

ARP_MRC_XLA_UPGRADE is an Oracle E-Business Suite upgrade utility owned by the APPS schema. It exists to migrate Multiple Reporting Currencies (MRC) accounting data into the Subledger Accounting (XLA) model introduced in the 11i10/12.x lineage. Prior to the introduction of Subledger Accounting, MRC maintained parallel reporting-currency records for each primary-ledger transaction directly within the base Receivables tables. With the transition to XLA, those parallel records are no longer held in the same physical structures; instead, accounting is derived through application accounting definitions and stored against the reporting ledger context.

The package therefore serves a one-time, data-conversion business function: it reads the legacy MRC rows held in the Receivables tables and reconstitutes them as Subledger Accounting events, headers, lines, and distributions for the appropriate reporting ledger. It is a migration instrument rather than a runtime API, and it is meaningful only during an upgrade that carries MRC data forward into an XLA-enabled release.

Key Procedures and Functions

The package exposes three documented procedures, all of which follow the same worker-queue pattern used by the EBS upgrade driver framework. None of the parameter lists are reproduced here; each procedure is described only by name and purpose.

• UPGRADE_MC_TRANSACTIONS — Converts legacy MRC transaction-level records associated with Receivables transactions into Subledger Accounting entries for the reporting ledger. This is the largest of the three conversions, since transactions are the primary driver of Receivables accounting.
• UPGRADE_MC_RECEIPTS — Converts legacy MRC cash-receipt records, including receipt history, into the XLA accounting model for the reporting ledger.
• UPGRADE_MC_ADJUSTMENTS — The procedure most directly associated with the "upgrade_mc_adjustments" search term. It converts legacy MRC adjustment records — both invoice-related adjustments and miscellaneous cash distributions — into XLA accounting entries for the reporting ledger. Adjustments carry their own distribution and accounting significance and must be migrated separately from transactions and receipts because their source rows originate in different base tables.

Each procedure accepts the table owner, table name, script name, worker identification, worker count, batch size, batch identifier, action flag, and an optional entity type. This signature indicates a coordinated, restartable, multi-worker batch process in which individual workers claim disjoint slices of the data and execute in parallel, with the action flag governing whether the worker performs a validation pass, an actual upgrade pass, or a restart.

Tables Accessed

The package reads the primary-ledger and legacy MRC tables and writes XLA accounting records. Documented references include:

• RA_CUSTOMER_TRX_ALL and RA_CUST_TRX_LINE_GL_DIST_ALL — source transactions and their line-level accounting distributions.
• AR_ADJUSTMENTS_ALL, AR_MC_ADJUSTMENTS, and AR_MISC_CASH_DISTRIBUTIONS_ALL / AR_MC_MISC_CASH_DISTS — adjustment and miscellaneous distribution rows, including the MRC shadow copies consumed by UPGRADE_MC_ADJUSTMENTS.
• AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_MC_CASH_RECEIPTS, and AR_MC_CASH_RECEIPT_HIST — receipt and receipt-history data, including MRC duplicates.
• AR_RECEIVABLE_APPLICATIONS_ALL and AR_MC_RECEIVABLE_APPS — application of receipts and adjustments to transactions.
• AR_TRANSACTION_HISTORY_ALL and AR_MC_TRANSACTION_HISTORY — status and activity history, including MRC counterparts.
• AR_MC_DISTRIBUTIONS_ALL — the aggregated legacy MRC distribution data that underpins the conversion.

The "AR_MC_" prefixed tables are the Multiple Reporting Currencies shadow tables. Their presence in this list confirms the package's role as the bridge between the MRC data model and XLA.

Usage Notes

ARP_MRC_XLA_UPGRADE is not intended for direct invocation by end users or by ordinary application code. It is driven by the EBS upgrade infrastructure, typically through a concurrent program or an upgrade driver that supplies the worker, batch, and batching parameters. The package is referenced by one other package in the EBS codebase, which is consistent with a driver or wrapper invoking these procedures rather than direct calls from forms.

In a 12.1.1 or 12.2.2 environment, the package is relevant only during the upgrade window that migrates MRC data into Subledger Accounting. The AUTHID CURRENT_USER declaration means it executes with the privileges of the calling user, so it must be run from a context that has appropriate access to both the AR and XLA schemas. Because all three procedures are restartable by design, a failed run may be resumed at batch granularity. Once the upgrade has completed, the package is dormant and its continued presence in the APPS schema is a legacy artifact.