Results for “ic_xfer_mst”

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

Overview

IC_XFER_MST is the inventory transfer master table in the Oracle EBS Process Manufacturing (GMI) Inventory module. It records the header-level information for inventory transfer transactions, capturing the movement of items between warehouses and locations within a process manufacturing organization. The table resides in the GMI schema at version 12.1.1 and 12.2.2, and is classified as VALID in the ETRM repository.

Each row in IC_XFER_MST represents a single transfer instruction, carrying the batch grouping, organization context, item and lot identification, source and destination warehouses, quantities, unit of measure references, key milestone dates, and status. Because the table stores both the planned and actual release/receive information alongside reason codes and text references, it functions as the authoritative record for transfer lifecycle tracking across the process manufacturing supply chain.

Based on the heuristic Data Vault classification derived from the foreign key structure, IC_XFER_MST is best modeled as a link. Its extensive set of foreign keys to item, lot, warehouse, organization, reason code, and UOM master tables places it at the intersection of multiple reference hubs and their business transactions, which is characteristic of a link construct rather than a hub or satellite.

Key Information Stored

The table contains 68 documented columns. The most operationally significant include:

• TRANSFER_ID — surrogate primary key, enforced by unique index IC_XFER_MST_PK.
• TRANSFER_BATCH, ORGN_CODE, TRANSFER_NO — composite business-key candidate defined by unique index IC_XFER_MST_I1.
• TRANSFER_STATUS — current lifecycle state of the transfer.
• ITEM_ID, LOT_ID, LOT_STATUS — links to item, lot, and lot status master records, identifying what is being moved.
• FROM_WAREHOUSE, FROM_LOCATION, TO_WAREHOUSE, TO_LOCATION — source and destination points for the transfer.
• RELEASE_QUANTITY1, RELEASE_QUANTITY2, RECEIVE_QUANTITY1, RECEIVE_QUANTITY2 — dual-unit quantities released and received.
• RELEASE_UOM1, RELEASE_UOM2 — unit of measure references for released quantities.
• SCHEDULED_RELEASE_DATE, ACTUAL_RELEASE_DATE, SCHEDULED_RECEIVE_DATE, ACTUAL_RECEIVE_DATE, CANCEL_DATE — milestone timestamps.
• RELEASE_REASON_CODE, RECEIVE_REASON_CODE, CANCEL_REASON_CODE — reason code references.
• RELEASED_BY, RECEIVED_BY, CANCELED_BY — personnel audit fields.
• TEXT_CODE — reference to text header for descriptive content.
• CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical reporting scenarios include open transfer tracking, warehouse-to-warehouse movement analysis, and reconciliation between scheduled and actual milestone dates. Example query patterns:

• Listing pending transfers: SELECT transfer_no, item_id, from_warehouse, to_warehouse, transfer_status FROM ic_xfer_mst WHERE transfer_status = ...
• Transfer aging: compare SCHEDULED_RECEIVE_DATE against ACTUAL_RECEIVE_DATE.
• Batch consolidation: group by TRANSFER_BATCH and ORGN_CODE for release-level processing.
• Cancellation audit: filter rows with non-null CANCEL_DATE and CANCEL_REASON_CODE.

These queries support cycle-count reconciliation, logistics dashboards, and month-end inventory movement extracts.

Related Objects

The following tables participate in the most significant FK relationships with IC_XFER_MST:

• IC_ITEM_MST / IC_ITEM_MST_B — joined via ITEM_ID.
• IC_LOTS_MST — joined via ITEM_ID and LOT_ID.
• IC_LOTS_STS — joined via LOT_STATUS.
• IC_WHSE_MST — joined via FROM_WAREHOUSE and TO_WAREHOUSE.
• SY_ORGN_MST / SY_ORGN_MST_B — joined via ORGN_CODE.
• SY_REAS_CDS / SY_REAS_CDS_B — joined via RELEASE_REASON_CODE, RECEIVE_REASON_CODE, and CANCEL_REASON_CODE.
• SY_UOMS_MST — joined via RELEASE_UOM1 and RELEASE_UOM2.
• IC_TEXT_HDR — joined via TEXT_CODE.