Search Results repl_status

Overview

WMS.WMS_REPL_DEMAND_GTMP is a global temporary table within the Warehouse Management System (WMS) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a transient staging structure used by the replenishment engine to materialize demand lines prior to processing. The table is defined with a data duration of SYS$SESSION, meaning rows are visible only to the session that inserts them and are purged automatically when that session terminates. This design makes the object suitable for high-concurrency replenishment runs, where multiple sessions can populate demand independently without contention on persistent storage.

The table appears in ETRM as VALID with no subobject name and is registered under FND Design Data as WMS.WMS_REPL_DEMAND_GTMP. From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone; it is best understood as a working set rather than a persistent hub, link, or satellite. Any downstream modeling should treat it as an ephemeral staging construct whose lifecycle is confined to a single session.

Key Information Stored

The table contains eighteen documented columns. The most operationally significant are summarized below.

• REPL_SEQUENCE_ID — Surrogate primary key and the sole unique business-key candidate (index WMS_REPL_DEMAND_GTMP_U1). It orders and identifies each replenishment demand row within the session.
• REPL_LEVEL — Indicates the replenishment hierarchy level, distinguishing parent and child demand rows.
• ORGANIZATION_ID — The inventory organization against which the demand is evaluated; part of the non-unique index WMS_REPL_DEMAND_GTMP_U2.
• INVENTORY_ITEM_ID — The item being replenished.
• DEMAND_HEADER_ID, DEMAND_LINE_ID, DEMAND_LINE_DETAIL_ID — Keys linking the row to the originating demand hierarchy; DEMAND_LINE_DETAIL_ID forms the second component of index WMS_REPL_DEMAND_GTMP_U2.
• DEMAND_TYPE_ID — Classifies the demand source (e.g., sales order, transfer, work in process).
• QUANTITY_IN_REPL_UOM and REPL_UOM_CODE — The demand quantity expressed in the replenishment unit of measure, together with that UOM code. The search term repl_uom_code resolves directly to this column.
• QUANTITY and UOM_CODE — The same quantity expressed in the primary item UOM, enabling conversion-aware comparisons.
• EXPECTED_SHIP_DATE, REPL_TO_SUBINVENTORY_CODE, FILTER_ITEM_FLAG, REPL_TYPE, REPL_STATUS, RELEASED_STATUS — Scheduling, destination, filtering, and lifecycle state attributes consumed by the replenishment process.

Common Use Cases and Queries

Typical usage centers on diagnosing or auditing replenishment runs within the current session. A common pattern aggregates demand by item and organization, converting via the replenishment UOM:

• Demand by item: SELECT ORGANIZATION_ID, INVENTORY_ITEM_ID, SUM(QUANTITY_IN_REPL_UOM) FROM WMS.WMS_REPL_DEMAND_GTMP GROUP BY ORGANIZATION_ID, INVENTORY_ITEM_ID;
• UOM reconciliation: compare QUANTITY_IN_REPL_UOM against QUANTITY to validate conversion factors.
• Unreleased demand review: filter on RELEASED_STATUS or REPL_STATUS to identify rows pending release.
• Subinventory targeting: group by REPL_TO_SUBINVENTORY_CODE to verify put-away destinations.
• Date-driven reporting: compare EXPECTED_SHIP_DATE against the run date.

Because the table is session-scoped, queries must execute from the same session that populated it; external reporting tools cannot see another session's rows.

Related Objects

• RLA_DEMAND_HEADERS_ALL — joined on DEMAND_HEADER_ID.
• RLA_DEMAND_LINES_ALL — joined on DEMAND_LINE_ID.
• APPS.WMS_REPL_DEMAND_GTMP — the APPS-layer synonym referencing this table.
• WMS_REPL_DEMAND_GTMP_U1 / _U2 — supporting unique and non-unique indexes.

No database objects are documented as referencing this table; the dependency chain flows inward from RLA demand tables and outward only through the APPS synonym.