Search Results ic_txn_request_headers_u1

Overview

The IC_TXN_REQUEST_HEADERS table, owned by the GMI schema, is the header-level data object for Move Orders within the Oracle EBS Process Manufacturing Inventory module (GMI). A move order represents an internal inventory transfer request — moving material between subinventories, between organizations, or to a designated location — and IC_TXN_REQUEST_HEADERS acts as the controlling parent record that establishes the identity, type, source, and destination of each request. Each header row anchors a set of line-level detail records in IC_TXN_REQUEST_LINES, which carry the individual item and quantity instructions.

In Data Vault modeling terms, the mined foreign-key structure classifies this table as hub-leaning. This is a modeling suggestion: the two unique indexes on business keys (HEADER_ID and REQUEST_NUMBER/ORGANIZATION_ID) strongly indicate a natural business hub for move order headers, with descriptive attributes (dates, status, shipping attributes) suggesting satellite behavior around that hub. Physical layering depends on the warehouse design chosen.

Key Information Stored

The table carries 45 documented columns. The most operationally significant are:

HEADER_ID — the surrogate primary key (backed by IC_TXN_REQUEST_HEADERS_PK).
REQUEST_NUMBER and ORGANIZATION_ID — together forming the business-key unique index IC_TXN_REQUEST_HEADERS_U1, meaning a move order number is unique within an inventory organization.
TRANSACTION_TYPE_ID and MOVE_ORDER_TYPE — define the nature of the movement (e.g., subinventory transfer, account transfer, requisition-based).
FROM_SUBINVENTORY_CODE and TO_SUBINVENTORY_CODE — the source and destination subinventories for the transfer.
TO_ACCOUNT_ID — the destination account where applicable.
HEADER_STATUS and STATUS_DATE — the workflow state of the request and the timestamp of the last status change.
DATE_REQUIRED — the requested completion date for the movement.
DESCRIPTION — user-entered reference text.
SHIP_TO_LOCATION_ID, FREIGHT_CODE, SHIPMENT_METHOD, and AUTO_RECEIPT_FLAG — shipping and receiving attributes governing how material is handled.
REFERENCE_ID and REFERENCE_DETAIL_ID — pointers to originating documents (such as sales orders or requisitions).
Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and the DFF columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15).

Common Use Cases and Queries

Typical reporting scenarios include tracking open move orders by organization, reconciling completed transfers, and auditing status transitions. A representative query joins headers to lines:

List open move orders awaiting execution: SELECT HEADER_ID, REQUEST_NUMBER, ORGANIZATION_ID, HEADER_STATUS, DATE_REQUIRED FROM IC_TXN_REQUEST_HEADERS WHERE HEADER_STATUS < 'CLOSED'.
Detail a specific request: SELECT h.REQUEST_NUMBER, h.TRANSACTION_TYPE_ID, l.* FROM IC_TXN_REQUEST_HEADERS h JOIN IC_TXN_REQUEST_LINES l ON l.HEADER_ID = h.HEADER_ID WHERE h.REQUEST_NUMBER = :req.
Volume analysis by organization and type groupings.

Related Objects

The primary dependency is the line-level child table IC_TXN_REQUEST_LINES, joined on IC_TXN_REQUEST_LINES.HEADER_ID = IC_TXN_REQUEST_HEADERS.HEADER_ID. Transaction type and organization context reference inventory setup tables (MTL_TRANSACTION_TYPES, ORG_ORGANIZATION_DEFINITIONS). Location and account references link to shipping and GL tables. Move order processing is commonly driven through the inventory move order APIs and the GMI transaction execution programs.

INDEX: GMI.IC_TXN_REQUEST_HEADERS_U1 12.2.2
owner:GMI, object_type:INDEX, object_name:IC_TXN_REQUEST_HEADERS_U1, status:VALID,
Table: IC_TXN_REQUEST_HEADERS 12.2.2
owner:GMI, object_type:TABLE, fnd_design_data:GMI.IC_TXN_REQUEST_HEADERS, object_name:IC_TXN_REQUEST_HEADERS, status:VALID, product: GMI - Process Manufacturing Inventory , description: Move Order Headers , implementation_dba_data: GMI.IC_TXN_REQUEST_HEADERS ,
Table: IC_TXN_REQUEST_HEADERS 12.1.1
owner:GMI, object_type:TABLE, fnd_design_data:GMI.IC_TXN_REQUEST_HEADERS, object_name:IC_TXN_REQUEST_HEADERS, status:VALID, product: GMI - Process Manufacturing Inventory , description: Move Order Headers , implementation_dba_data: GMI.IC_TXN_REQUEST_HEADERS ,
INDEX: GMI.IC_TXN_REQUEST_HEADERS_U1 12.1.1
owner:GMI, object_type:INDEX, object_name:IC_TXN_REQUEST_HEADERS_U1, status:VALID,
TABLE: GMI.IC_TXN_REQUEST_HEADERS 12.1.1
owner:GMI, object_type:TABLE, fnd_design_data:GMI.IC_TXN_REQUEST_HEADERS, object_name:IC_TXN_REQUEST_HEADERS, status:VALID,
TABLE: GMI.IC_TXN_REQUEST_HEADERS 12.2.2
owner:GMI, object_type:TABLE, fnd_design_data:GMI.IC_TXN_REQUEST_HEADERS, object_name:IC_TXN_REQUEST_HEADERS, status:VALID,
12.1.1 DBA Data 12.1.1
12.2.2 DBA Data 12.2.2
eTRM - GMI Tables and Views 12.2.2
description: 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
description: 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
description: 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
description: 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. ,