Results for “txn_source_id”

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

Overview

WMS_TXN_CONTEXT_TEMP is a temporary detailing context table residing in the WMS (Warehouse Management) schema of Oracle E-Business Suite. Its documented description, "WMS Detailing Context Temporary Table," identifies it as a transient staging structure used during warehouse transaction processing to hold contextual details associated with a transaction line before the information is consumed by downstream fulfillment, shipping, or inventory logic. Within the WMS module, such context tables typically support the transaction detailer by accumulating attribute values — freight carrier, customer, and source document references — that are later resolved into permanent transaction records.

Because the table is temporary in nature, its contents are generally scoped to a single processing session or concurrent request and are not intended for long-term retention. The ETRM metadata documents seven columns and a single primary key, WMS_TXN_CONTEXT_TEMP_PK, defined on LINE_ID. A unique index, WMS_TXN_CONTEXT_TEMP_U1, also exists on LINE_ID, confirming that the transaction request line is the natural business key and enforcing one context row per line. Applying Data Vault modeling heuristics to the documented foreign-key structure classifies this table as satellite-leaning: it hangs off a parent business entity (the transaction request line) and carries descriptive, context-bearing attributes rather than representing an independent hub or an associative link.

Key Information Stored

The documented columns capture the identity of the transaction line and the contextual references required for detailing:

• LINE_ID — Surrogate primary key (WMS_TXN_CONTEXT_TEMP_PK) and sole documented unique key (WMS_TXN_CONTEXT_TEMP_U1). It references MTL_TXN_REQUEST_LINES, tying each context row to a specific move-order line. This is the join column to every related object.
• TXN_SOURCE_ID — Identifier of the originating transaction source, allowing the detailer to trace context back to the source document.
• TXN_SOURCE_LINE_ID — The source document's line identifier, distinguishing individual lines within the same source.
• TXN_SOURCE_NAME — The name of the transaction source, used for display, filtering, and reporting of the originating document type or reference.
• TXN_SOURCE_LINE_DETAIL — Free-form or structured detail describing the source line, supplying supplementary context to the detailing process.
• FREIGHT_CARRIER_CODE — The carrier designated for shipment, supporting freight rating, manifesting, and carrier-specific logic.
• CUSTOMER_ID — The customer associated with the transaction, enabling customer-specific shipping, labeling, or delivery context.

In Data Vault terms, LINE_ID functions as the foreign key to the parent hub (the move-order line), while the remaining columns are descriptive satellite attributes.

Common Use Cases and Queries

Typical scenarios include diagnosing detailing failures, validating freight-carrier assignment, and reconciling customer context during shipping confirmation. Because the table is keyed on LINE_ID, queries commonly join to MTL_TXN_REQUEST_LINES:

• Retrieving context for a specific move-order line: SELECT * FROM wms.wms_txn_context_temp WHERE line_id = :p_line_id;
• Listing all context rows for a batch of lines: SELECT c.line_id, c.txn_source_name, c.freight_carrier_code, c.customer_id FROM wms.wms_txn_context_temp c, mtl_txn_request_lines l WHERE c.line_id = l.line_id AND l.request_number = :p_request;
• Auditing freight carrier usage: SELECT freight_carrier_code, COUNT(*) FROM wms.wms_txn_context_temp GROUP BY freight_carrier_code;
• Verifying orphaned context during integration troubleshooting, since rows should always resolve to an existing move-order line.

Reports typically treat this table as a processing aid rather than a reporting source, so extracts should run while a detailing session is active.

Related Objects

• MTL_TXN_REQUEST_LINES — Parent entity referenced by the documented foreign key WMS_TXN_CONTEXT_TEMP.LINE_ID → MTL_TXN_REQUEST_LINES. This is the primary join relationship.
• WMS_TXN_CONTEXT_TEMP_PK / WMS_TXN_CONTEXT_TEMP_U1 — Primary key and unique index on LINE_ID, both enforcing line-level granularity.
• MTL_TXN_REQUEST_HEADERS — Header-level companion to the referenced lines, used to resolve request numbers and transaction types.
• WMS Dispatcher and Transaction Detailer concurrent programs/APIs — The WMS processes that populate and consume this context table during move-order detailing.
• WMS_SHIPPING / carrier and customer reference tables — Lookup sources for FREIGHT_CARRIER_CODE and CUSTOMER_ID values recorded here.

Together these objects position WMS_TXN_CONTEXT_TEMP as a short-lived satellite of the move-order line, central to warehouse transaction detailing in EBS 12.1.1 and 12.2.2.