Search Results wms_repl_demand_gtmp

Overview

WMS_REPL_DEMAND_GTMP is a global temporary table (GTMP) owned by the WMS schema in Oracle E-Business Suite, introduced and documented for releases 12.1.1 and 12.2.2. It serves as a transient staging structure within the Warehouse Management replenishment flow, holding the demand rows that the replenishment engine evaluates when generating suggestions and movement recommendations for warehouse subinventories. Because the object type is a global temporary table, its contents are session-scoped: rows persist only for the duration of the transaction or session that populated them, after which Oracle purges the data automatically. This design makes the object unsuitable for permanent storage or historical reporting, and appropriate for high-volume, in-flight computation during replenishment planning.

Under a heuristic Data Vault classification derived from the documented foreign-key structure, the table behaves as a link candidate. It records a transient association between demand documents and the items, organizations, and inventory locations for which replenishment is being considered. It is catalogued as standalone in the Data Vault classification heuristic, and it is not treated as a durable hub or satellite.

Key Information Stored

The documented physical schema contains 18 columns. The most significant include:

• REPL_SEQUENCE_ID — the surrogate sequence controlling processing order, and the sole documented unique index column (WMS_REPL_DEMAND_GTMP_U1), which functions as the business-key candidate in the absence of a declared primary key.
• ORGANIZATION_ID, INVENTORY_ITEM_ID — the inventory organization and item being replenished; the primary dimensional keys for any query against this table.
• DEMAND_HEADER_ID and DEMAND_LINE_ID — foreign keys to RLA_DEMAND_HEADERS_ALL and RLA_DEMAND_LINES_ALL, tying each staged replenishment row to the originating demand document and line.
• DEMAND_LINE_DETAIL_ID, DEMAND_TYPE_ID — finer-grained demand attribution and demand classification.
• QUANTITY_IN_REPL_UOM, REPL_UOM_CODE, QUANTITY, UOM_CODE — the required quantity expressed in both the replenishment unit of measure and the primary unit of measure.
• EXPECTED_SHIP_DATE — the date constraint driving scheduling and prioritization.
• REPL_TO_SUBINVENTORY_CODE — the destination subinventory receiving the replenishment.
• REPL_LEVEL, REPL_TYPE, REPL_STATUS, RELEASED_STATUS, FILTER_ITEM_FLAG — planning attributes that indicate the replenishment level, processing type, current status, release state, and whether the item passed filtering criteria.

Common Use Cases and Queries

Typical usage involves populating the table from the demand tables, executing the replenishment algorithm, and reading the results within the same session. Common query patterns include grouping demand by item and organization within a session, or joining back to the demand line tables to attribute quantities to their source documents:

• Aggregating staged demand: SELECT organization_id, inventory_item_id, SUM(quantity) FROM wms.wms_repl_demand_gtmp GROUP BY organization_id, inventory_item_id;
• Joining to source demand: SELECT g.repl_sequence_id, l.demand_line_id, g.quantity FROM wms.wms_repl_demand_gtmp g, rla.rla_demand_lines_all l WHERE g.demand_line_id = l.demand_line_id;
• Reporting release status by destination subinventory, and ordering processing by REPL_SEQUENCE_ID.

Because the table is temporary and session-scoped, it should not be used as a reporting source outside the replenishment program's execution. Debugging and diagnostic queries must be run from the same session that populated the table.

Related Objects

• RLA_DEMAND_HEADERS_ALL — joined on DEMAND_HEADER_ID.
• RLA_DEMAND_LINES_ALL — joined on DEMAND_LINE_ID.
• WMS_REPL_DEMAND_GTMP_U1 — unique index on REPL_SEQUENCE_ID.
• MTL_SYSTEM_ITEMS_B — item validation for INVENTORY_ITEM_ID.
• MTL_PARAMETERS — organization context for ORGANIZATION_ID.
• INV_SUBINVENTORIES — destination resolution for REPL_TO_SUBINVENTORY_CODE.
• WMS_REPLENISHMENT APIs and the replenishment concurrent programs that populate and consume this temporary structure.