Search Results ap_invoice_distributions_u2

Overview

APPS.AP_XLA_UPGRADE_PKG is an Oracle E-Business Suite upgrade utility package. Its business function is to migrate Subledger Accounting (SLA / XLA) data for Oracle Payables from pre-11i.x legacy distribution tables into the XLA accounting model introduced in Release 11i.10 and carried forward through 12.1.1 and 12.2.2. The package header is identified as apxlaupb.pls (version 120.11.12000000.2), a source file at the 12.0.0 baseline that continues to ship in later releases.

The package is not part of the day-to-day Payables transaction flow. It is an administrative, one-time (or resumable) upgrade engine that converts legacy invoice, prepayment, and payment distribution rows into corresponding XLA distribution and accounting link records, and reconciles the resulting balances against an extracted liability balance target. Because SLA replaced the older Payables distribution tables as the system of record, any customer upgrading from an older accounting model to the XLA model must run this upgrade so that historical distributions are visible to the Create Accounting program and to Subledger Accounting reporting.

Key Procedures and Functions

The ETRM metadata documents six entry points. The two orchestration routines are AP_XLA_UPGRADE_ONDEMAND, the master/on-demand driver that initiates a customer-selected or targeted upgrade run, and AP_XLA_UPGRADE_SUBWORKER, which processes an individual worker slice of the population. The remaining four procedures perform the actual conversion and validation:

• CREATE_INVOICE_DIST_LINKS — builds the accounting links between invoice distributions and their corresponding XLA distributions.
• CREATE_PREPAY_DIST_LINKS — performs the equivalent link creation for prepayment application distributions.
• CREATE_PAYMENT_DIST_LINKS — performs the equivalent link creation for payment-history distributions.
• CREATE_TRIAL_BALANCE — extracts or derives balance information used to verify that the upgraded distributions reconcile to the Payables liability position.

The package body also contains internal helper functions, including a worker-launching function that submits child concurrent requests (via FND_REQUEST.SUBMIT_REQUEST for the SQLAP executable APXLASUB, one request per worker) so the conversion can be parallelized. It declares named exceptions for "no child process," "procedure failure," and "child failed," and writes diagnostics through FND_LOG at the statement and procedure levels. These internal routines are implementation details and are not exposed as supported APIs.

Tables Accessed

The package reads and writes an extensive set of APPS synonyms covering the full Payables distribution and payment footprint. Source-side data is drawn from AP_INVOICE_DISTRIBUTIONS_ALL, AP_INVOICE_LINES_ALL, AP_INVOICES_ALL, AP_PREPAY_APP_DISTS / AP_PREPAY_APP_DISTS_S, AP_PREPAY_HISTORY_ALL / AP_PREPAY_HISTORY_S, AP_PAYMENT_HIST_DISTS / AP_PAYMENT_HIST_DISTS_S, AP_PAYMENT_HISTORY_ALL, AP_INVOICE_PAYMENTS_ALL, and AP_CHECKS_ALL. These provide the legacy distributions and payment/prepayment application rows that must be converted to SLA. Control and reconciliation data is held in AP_INVOICES_UPG_CONTROL, AP_INV_DISTS_SOURCE, and AP_LIABILITY_BALANCE, which track upgrade status, distribution origin, and the target liability balances used by CREATE_TRIAL_BALANCE to confirm completeness of the conversion.

Usage Notes

AP_XLA_UPGRADE_PKG is invoked as an upgrade program, not as a runtime API. It is normally driven by the Payables SLA upgrade concurrent programs supplied with the release, which submit AP_XLA_UPGRADE_ONDEMAND and the parallel AP_XLA_UPGRADE_SUBWORKER child requests through the APXLASUB executable. The subworker pattern and FND_LOG instrumentation mean that large populations can be processed in batches and monitored from the concurrent manager logs and the SLA upgrade control screens. The package is referenced by one other package, reflecting the layered nature of the Payables upgrade chain.

It is not intended for custom development, and its procedures have no published signature contract for extension. Note that the ETRM query term ap_invoice_distributions_u2 corresponds to a unique-key index on AP_INVOICE_DISTRIBUTIONS_ALL; that table is a primary source for CREATE_INVOICE_DIST_LINKS, so the index is exercised heavily during upgrade reads and deletes. If an upgrade fails due to child-request submission errors, the affected distribution rows are rolled back and the corresponding invoice or payment is typically left flagged as unupgraded until the program is rerun.