Results for “phase_num”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA.XLA_UPGRADE_REQUESTS is a Subledger Accounting (XLA) operational table within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the parameters for each post-upgrade request executed during the SLA (Subledger Accounting) upgrade process. When an E-Business Suite instance is upgraded to a release that includes Subledger Accounting — most notably the transition to 12.1.1 where SLA becomes the mandatory accounting engine, or the 12.2.2 upgrade path — the upgrade driver creates and tracks work requests that convert historical subledger transactions into SLA entries and repository data. Each row in this table represents one such request, capturing the runtime parameters that govern how the upgrade program decomposes, orders, and parallelizes its work across ledgers, periods, and database objects.

The table functions as a control and checkpoint record rather than a transactional repository. It is written and read primarily by the SLA upgrade concurrent programs and their worker processes. The documented physical schema contains 23 columns, all owned by the XLA schema. From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone (no composite parent-child structure embedded within it), with an outbound foreign key to WSH_ITM_REQUEST_CONTROL via REQUEST_CONTROL_ID. A dimensional modeler could reasonably treat this as a hub or control-satellite construct, since it anchors a request identity and tracks its evolving execution state.

Key Information Stored

The most significant columns fall into identity, scope, execution, and audit groups:

• REQUEST_CONTROL_ID — the primary business identifier for the upgrade request and the column linked to WSH_ITM_REQUEST_CONTROL.
• PARENT_REQUEST_CONTROL_ID — self-referencing pointer that links a worker request back to its parent coordination request, enabling hierarchical tracking of parallel workers.
• APPLICATION_ID — identifies the subledger application (Payables, Receivables, Assets, etc.) whose data is being upgraded.
• LEDGER_ID — the ledger context for which the post-upgrade processing is performed.
• PERIOD_NAME — the accounting period being processed or converted.
• PHASE_NUM, PROGRAM_CODE, SCRIPT_NAME — define the upgrade phase, the executing program, and the specific upgrade script or conversion routine.
• STATUS_CODE — the current state of the request (for example, pending, running, completed, or errored).
• TABLE_NAME, BATCH_SIZE, BATCH_ID, WORKER_ID, WORKERS_NUM, ORDER_NUM — control the batching and parallelization strategy for the underlying data conversions.
• START_DATE, END_DATE — execution timing for performance analysis and progress monitoring.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row.

The surrogate/technical key is not separately documented in the supplied metadata; REQUEST_CONTROL_ID is the strongest business-key candidate and carries the documented foreign key relationship. DBA or implementation-specific unique indexes on that column are typical but are not enumerated in the ETRM extract.

Common Use Cases and Queries

The dominant use case is monitoring and troubleshooting the SLA upgrade. DBAs and upgrade teams query the table to determine which requests are still running, which have failed, and which ledgers, periods, or applications remain incomplete. A representative query lists outstanding work:

• SELECT request_control_id, application_id, ledger_id, period_name, phase_num, program_code, status_code, start_date, end_date FROM xla.xla_upgrade_requests WHERE status_code NOT IN ('COMPLETED') ORDER BY start_date;
• Aggregating progress by ledger and period to estimate remaining runtime.
• Joining to WSH_ITM_REQUEST_CONTROL on REQUEST_CONTROL_ID to correlate the SLA upgrade request with the broader request-control framework and obtain additional status detail.
• Using PARENT_REQUEST_CONTROL_ID to build a hierarchy and identify stalled worker requests under a parent coordinator.

Because the table retains execution history, it also supports post-upgrade auditing and performance retrospection — for example, measuring elapsed time per phase using START_DATE and END_DATE, or analyzing batch throughput via BATCH_SIZE and WORKERS_NUM. Care should be taken to treat the table as read-only during diagnostics; it is maintained by upgrade programs, and manual updates can corrupt upgrade state.

Related Objects

The documented foreign key establishes the principal external relationship. Beyond that, the following objects are most significant in practice:

• WSH_ITM_REQUEST_CONTROL — referenced by XLA_UPGRADE_REQUESTS.REQUEST_CONTROL_ID; the request-control parent record.
• XLA_UPGRADE_REQUESTS (self) — parent/child linkage through PARENT_REQUEST_CONTROL_ID.
• SLA upgrade concurrent programs and worker executables that populate and update the table.
• FND_CONCURRENT_REQUESTS — frequently joined for concurrent program status and output when correlating request timing.
• Subledger application base tables (for example, AP_INVOICES_ALL, AR_TRANSACTIONS) indirectly processed by the requests identified here.
• SLA repository objects such as XLA_AE_HEADERS and XLA_AE_LINES, whose upgraded content depends on successful completion of these requests.

Together these objects complete the operational picture: XLA_UPGRADE_REQUESTS records the work plan, the request-control framework tracks execution, and the SLA repository tables hold the resulting accounting data.