Results for “wms_rule_trace_headers”

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

Overview

WMS_RULE_TRACE_HEADERS is a Warehouse Management (WMS) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the WMS schema. It functions as the parent header table that captures the execution trace of the WMS rules engine, recording each invocation of a picking, put-away, or inventory strategy so that the results of rule evaluation can be audited and debugged. Every time the warehouse management engine evaluates a strategy against an order, move order line, or inventory transaction, a row in this table represents the top-level trace record, while the individual rule-by-rule evaluation steps are written to the detail table WMS_RULE_TRACE_LINES, which references the header through HEADER_ID.

From a dimensional modeling perspective, the FK structure mined from the ETRM metadata classifies this table as hub-leaning. The single inbound relationship from WMS_RULE_TRACE_LINES consolidates around the HEADER_ID primary key, which behaves like a hub key for the strategy-evaluation event, with the descriptive attributes carried directly on the header acting as satellite-style context. This classification is a heuristic suggestion rather than a documented Oracle design intent.

Key Information Stored

The physical schema documents 20 columns. The surrogate primary key is HEADER_ID, enforced by the WMS_RULE_TRACE_HEADERS_PK constraint, and is the join key to the trace lines. Business-identifying context is provided by the following columns:

• PICK_HEADER_ID — links the trace to the originating pick wave or pick header being processed.
• MOVE_ORDER_LINE_ID — the move order line for which rules were evaluated.
• STRATEGY_ID — the strategy definition whose rules were applied during evaluation.
• BUSINESS_OBJECT_ID, OBJECT_ID, OBJECT_NAME — identify the business object and instance under evaluation.
• TYPE_CODE — classifies the nature of the rule trace event.
• SIMULATION_MODE — indicates whether the trace was produced by a live transaction or a simulation run.
• TOTAL_QTY and SECONDARY_TOTAL_QTY — the primary and secondary quantities involved in the evaluation.
• SID and SERIAL_NUMBER — inventory locator and serial context for the transaction.
• SO_START_TIME and SO_END_TIME — the start and end timestamps of the strategy evaluation window.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The primary operational use is diagnosing why the WMS rules engine selected or rejected a particular inventory location, subinventory, or lot. Support and implementation teams query the header joined to its lines to reconstruct the decision path. A typical pattern retrieves recent traces for a move order line:

• SELECT h.HEADER_ID, h.STRATEGY_ID, h.TYPE_CODE, h.TOTAL_QTY, h.SO_START_TIME FROM WMS_RULE_TRACE_HEADERS h WHERE h.MOVE_ORDER_LINE_ID = :line_id ORDER BY h.CREATION_DATE DESC;
• Join to WMS_RULE_TRACE_LINES to inspect each rule decision: SELECT h.HEADER_ID, l.* FROM WMS_RULE_TRACE_HEADERS h, WMS_RULE_TRACE_LINES l WHERE h.HEADER_ID = l.HEADER_ID AND h.HEADER_ID = :header_id;
• Filter on SIMULATION_MODE = 'Y' to isolate what-if strategy analysis from production traces.

Reporting use cases include measuring rule evaluation elapsed time using SO_START_TIME and SO_END_TIME, quantifying total evaluated quantities by strategy through STRATEGY_ID and TOTAL_QTY, and auditing pick performance against PICK_HEADER_ID.

Related Objects

The most significant related object is the child detail table, which is the only documented foreign-key relationship:

• WMS_RULE_TRACE_LINES — references WMS_RULE_TRACE_HEADERS via WMS_RULE_TRACE_LINES.HEADER_ID = WMS_RULE_TRACE_HEADERS.HEADER_ID, holding the individual rule evaluation steps.

The columns PICK_HEADER_ID, MOVE_ORDER_LINE_ID, STRATEGY_ID, and BUSINESS_OBJECT_ID implicitly relate this table to the WMS picking headers, move order lines, strategy definitions, and business object registries, which are the natural parent entities for trace reconstruction and reporting joins.