Results for “source_header_id”

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

Overview

WMS_ELS_EXP_RESOURCE_GTEMP is an APPS-owned table within the Oracle Warehouse Management (WMS) module, specifically tied to the Execution Logic System (ELS) subsystem that governs task execution, resource allocation, and labor management in warehouse operations. In Oracle EBS 12.1.1 and 12.2.2, tables bearing the _GTEMP suffix typically function as global temporary staging structures used to hold transient data during concurrent processing, interface runs, or PL/SQL bulk operations. The object has a VALID status in the ETRM 12.2.2 repository and exposes six documented columns.

Under the heuristic Data Vault classification supplied in the metadata, this table is identified as standalone. In Data Vault modeling terms, a standalone classification suggests the object behaves independently rather than as a conventional hub, link, or satellite. Its one documented foreign key relationship — ELS_DATA_ID referencing WMS_ELS_INDIVIDUAL_TASKS_B — indicates that records here are anchored to individual task entities. Rather than a persistent master or transactional hub, the table is best modeled as a transient staging or working set that supports the WMS execution engine.

Key Information Stored

The six documented columns capture the identity and lineage of a warehouse execution record. The most significant columns are:

• ELS_DATA_ID — The foreign key linking each row to a parent record in WMS_ELS_INDIVIDUAL_TASKS_B. This is the principal relationship column and the anchor for joining back to the individual task definition.
• SOURCE_HEADER_ID — Identifier of the originating document header (for example, a sales order, transfer order, or move-order header) that triggered the execution activity.
• SOURCE_LINE_ID — Identifier of the originating document line corresponding to the header above.
• ACTIVITY_ID — Reference to the warehouse activity being executed or planned.
• ACTIVITY_DETAIL_ID — Reference to the finer-grained activity detail record.
• OPERATION_ID — Identifier of the execution operation within the task flow.

Because the metadata does not document a surrogate primary key or unique index, the table should be treated as a non-keyed temporary structure. Where a row must be uniquely identified, the combination of ELS_DATA_ID with the activity or source identifiers serves as the practical business-key candidate. The absence of a documented PK is consistent with global temporary table behavior, where uniqueness is enforced by the populating process rather than by a persistent constraint.

Common Use Cases and Queries

This table is most commonly encountered when diagnosing or extending WMS execution and resource-planning processes. Typical scenarios include tracing which tasks were generated for a given outbound or inbound flow, reconciling planned versus executed activities, and troubleshooting runtime errors in ELS concurrent programs.

A representative query joins the temporary resource data back to its parent task table:

• SELECT t.ELS_DATA_ID, t.SOURCE_HEADER_ID, t.SOURCE_LINE_ID, t.ACTIVITY_ID, t.OPERATION_ID FROM WMS_ELS_EXP_RESOURCE_GTEMP t WHERE t.ELS_DATA_ID = :p_task_id;

Reporting use cases include auditing activity-to-source-document lineage, validating that each individual task carries the expected activity and operation references, and measuring throughput by counting distinct ACTIVITY_ID values per source header. Because the table is temporary by design, queries are meaningful only while the owning session or concurrent request is active; persistent reporting should target the underlying base tables instead.

Related Objects

The principal related objects, derived from the documented FK path and the WMS ELS model, are:

• WMS_ELS_INDIVIDUAL_TASKS_B — referenced via ELS_DATA_ID; the base task entity that anchors each temporary row.
• WMS_ELS_INDIVIDUAL_TASKS_TL — translation companion to the base task table.
• Other WMS execution tables holding SOURCE_HEADER_ID and SOURCE_LINE_ID lineage, such as associated move-order or order-header tables used to resolve the source document.
• Activity and operation master tables referenced by ACTIVITY_ID and OPERATION_ID.
• The WMS ELS concurrent programs and PL/SQL APIs that populate this temporary structure at runtime.

Collectively, these relationships place WMS_ELS_EXP_RESOURCE_GTEMP as a transient processing aid beneath the WMS task execution layer rather than a standalone business entity.