Results for “xla_tb_work_units”

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

Overview

XLA_TB_WORK_UNITS is a Subledger Accounting (XLA) table in the E-Business Suite database, owned by the XLA schema. Its documented purpose is to act as a work unit table that enables the parallel processing of open account balances data during accounting upgrade or migration activities. Accounting entries are partitioned into multiple discrete work units based on ledger setup, allowing concurrent workers to divide the workload and process balances with greater throughput than a single serial run would permit.

The object carries a heuristic Data Vault classification of standalone, mined from its foreign key structure. Under this modeling suggestion, XLA_TB_WORK_UNITS would be treated as an independent hub-like or work-tracking entity rather than as a link between two business keys or a satellite recording descriptive state changes. This classification reflects the narrow, operational character of the table: it tracks the progress and boundaries of parallel work rather than modeling a business relationship or holding history.

Key Information Stored

The documented physical schema for ETRM 12.2.2 contains nine columns. The most significant are summarized below.

• REQUEST_ID — The concurrent request identifier that spawned this work unit; ties the row back to the parent processing job.
• PARENT_REQUEST_ID — The originating or controlling request when work units are generated by a parent process, enabling parent/child correlation across a parallel run.
• GROUP_ID — Groups a set of work units belonging to the same logical batch, so that completion of all units in a group can be assessed.
• DEFINITION_CODE — Identifies the accounting definition or processing context under which the work unit was created.
• JE_SOURCE_NAME — The journal entry source name whose balances are being processed, providing a business-meaningful partitioning attribute.
• UPG_BATCH_ID — Foreign key to XLA_UPG_BATCHES; identifies the upgrade or migration batch that owns this work unit.
• FROM_HEADER_ID and TO_HEADER_ID — Define the inclusive range of header identifiers (the low and high water marks) assigned to this unit, which is the mechanism by which entries are split into parallel chunks.
• STATUS_CODE — Indicates the processing state of the unit (for example, unprocessed, in progress, or complete), supporting restart and progress monitoring.

No surrogate primary key or unique index column is explicitly documented in the supplied metadata. In practice, the combination of UPG_BATCH_ID, REQUEST_ID, and GROUP_ID, together with the header range, functions as the effective business key for a work unit. The FROM_HEADER_ID/TO_HEADER_ID pair is the principal business-key candidate because it uniquely bounds the data set each unit is responsible for.

Common Use Cases and Queries

Typical uses center on monitoring and troubleshooting parallel balance processing. Administrators query this table to determine whether an upgrade job has completed, which header ranges remain outstanding, and whether any unit has stalled.

A representative progress query counts work units by status for a given batch:

• SELECT STATUS_CODE, COUNT(*) FROM XLA.XLA_TB_WORK_UNITS WHERE UPG_BATCH_ID = :batch_id GROUP BY STATUS_CODE;

To locate incomplete ranges for restart purposes:

• SELECT REQUEST_ID, FROM_HEADER_ID, TO_HEADER_ID FROM XLA.XLA_TB_WORK_UNITS WHERE UPG_BATCH_ID = :batch_id AND STATUS_CODE <> 'COMPLETE' ORDER BY FROM_HEADER_ID;

Reporting scenarios include reconciling the number of units against ledger and journal source setups, verifying that no header range overlap or gap exists, and auditing throughput during large migration windows.

Related Objects

The following objects are most significant in relation to this table.

• XLA_UPG_BATCHES — Referenced through XLA_TB_WORK_UNITS.UPG_BATCH_ID = XLA_UPG_BATCHES.UPG_BATCH_ID; the parent batch that defines the migration scope.
• XLA_UPG_BATCH_STEPS and other XLA_UPG_* tables — Track individual processing steps within the same upgrade batch and are commonly joined for end-to-end status reporting.
• XLA_HEADERS — Supplies the header identifiers bounded by FROM_HEADER_ID and TO_HEADER_ID, linking each work unit to the accounting entries it processes.
• XLA_JE_SOURCES_VL — Provides the descriptive name behind JE_SOURCE_NAME.
• FND_CONCURRENT_REQUESTS — Joins on REQUEST_ID and PARENT_REQUEST_ID to expose concurrent program status and timing.

Together these relationships allow DBAs and technical consultants to trace a parallel balance-processing run from its defining batch through each work unit to the accounting headers and concurrent requests involved.