Results for “ic_txn_request_headers_u1”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The GMI.IC_TXN_REQUEST_HEADERS table stores move order headers within Oracle Process Manufacturing (OPM), documented in EBS 12.1.1 and 12.2.2. It is registered under the GMI schema with an FND Design Data entry of the same name and holds a VALID status. This table is the transactional header record for inventory move orders — requests to transfer material between subinventories, accounts, or organizations — and functions as the controlling parent for the associated line-level detail in IC_TXN_REQUEST_LINES. In functional terms, it represents the move order document itself: who requested it, from where, to where, when it is required, and its current lifecycle status.
Based on the heuristic Data Vault classification mined from the foreign key structure — a single inbound dependency from IC_TXN_REQUEST_LINES — this object is best modeled as hub-leaning. That is, IC_TXN_REQUEST_HEADERS behaves as a durable business key container for move order identity, with attributes such as status, descriptions, and dates functioning as satellite-style descriptive data attached to that hub. Treating it this way in a warehouse design keeps move order identity stable while allowing status changes to be tracked separately.
Key Information Stored
The physical schema documents 45 columns. The most significant are:
- HEADER_ID — the surrogate primary key (IC_TXN_REQUEST_HEADERS_PK), a system-generated identifier for the move order header.
- REQUEST_NUMBER and ORGANIZATION_ID — together forming the unique business key (IC_TXN_REQUEST_HEADERS_U1), ensuring a move order number is unique within an organization.
- TRANSACTION_TYPE_ID — classifies the transaction type and drives index IC_TXN_REQUEST_HEADERS_N1.
- FROM_SUBINVENTORY_CODE and TO_SUBINVENTORY_CODE — source and destination subinventories, backed by indexes N2 and N3 respectively (each paired with ORGANIZATION_ID).
- TO_ACCOUNT_ID — destination account for accounting-related movements.
- DATE_REQUIRED — the requested completion date.
- HEADER_STATUS and STATUS_DATE — the current workflow status and when it changed.
- MOVE_ORDER_TYPE — categorizes the order and is indexed by IC_TXN_REQUEST_HEADERS_N4.
- DESCRIPTION — free-text description of the move order.
- GROUPING_RULE_ID, SHIP_TO_LOCATION_ID, FREIGHT_CODE, SHIPMENT_METHOD, and AUTO_RECEIPT_FLAG — logistics and receipt-processing attributes.
- The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent WHO columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) plus ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY for extensibility.
Common Use Cases and Queries
The most frequent operation is a join from lines to headers to reconstruct a full move order. A representative pattern:
- Retrieve open move orders by subinventory:
SELECT h.request_number, h.header_status, h.date_required FROM ic_txn_request_headers h WHERE h.organization_id = :org AND h.from_subinventory_code = :subinv AND h.header_status < :completed_status; - Locate orders by transaction type using the N1 index:
SELECT * FROM ic_txn_request_headers WHERE transaction_type_id = :type_id; - Reconstruct order detail:
SELECT h.request_number, l.* FROM ic_txn_request_headers h, ic_txn_request_lines l WHERE h.header_id = l.header_id;
Typical reporting scenarios include pending move order aging by DATE_REQUIRED, move order throughput by TRANSACTION_TYPE_ID, subinventory transfer volume between FROM_ and TO_ subinventories, and audit trails from the WHO columns. Because the N1–N4 indexes are non-unique on frequently filtered columns, queries constrained by transaction type, subinventory, or move order type benefit from index access paths.
Related Objects
- GMI.IC_TXN_REQUEST_LINES — the primary dependent table, joined on HEADER_ID (FK to IC_TXN_REQUEST_HEADERS); holds the line-level item and quantity detail.
- IC_TXN_REQUEST_HEADERS_PK / _U1 — the primary and unique business-key indexes supporting HEADER_ID and (REQUEST_NUMBER, ORGANIZATION_ID).
- IC_TXN_REQUEST_HEADERS_N1–N4 — non-unique performance indexes on TRANSACTION_TYPE_ID, FROM_SUBINVENTORY_CODE, TO_SUBINVENTORY_CODE, and MOVE_ORDER_TYPE.
- Organization-scoped master data referenced via ORGANIZATION_ID, and inventory subinventory definitions implied by FROM_ and TO_ subinventory codes.
Together these objects form the header-line hierarchy underpinning OPM move order processing and inventory transfer reporting.
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
Move Order Headers
-
Move Order Headers
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.2.2
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.
-
eTRM - GMI Tables and Views 12.1.1
Table used to relate Item ID with Roles. If the Item ID is NULL, then Roles will be associated with the warehouse Item ID. This table will be used by the Lot Expiry/Retest Workflow.