Results for “gmi_xfer_mst_v”

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

Overview

GMI_XFER_MST_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMI – Process Manufacturing Inventory product family. Its stated purpose in the ETRM metadata is to populate the Inventory Transfer form; the view supplies the row source that the form's block queries when displaying and maintaining transfer records. The primary base table is IC_XFER_MST, the Process Manufacturing inventory transfer master, and the view enriches that transactional spine with descriptive attributes drawn from item master, lot master, lot status, warehouse, grade, reason code, and FND_USER tables.

Because it is a view rather than a table, GMI_XFER_MST_V holds no data of its own; it exposes a denormalized, read-oriented projection over OLTP tables. This makes it equally useful as a reporting and integration surface — for custom concurrent programs, BI Publisher data templates, OAF/Forms extensions, or interface extracts that need transfer header detail without joining the underlying tables manually. The view status is documented as VALID in the ETRM repository at 12.2.2, and the same object exists in the 12.1.1 code line since the Process Manufacturing data model is consistent across those releases.

Underlying Base Objects

The documented base objects behind the view are all referenced through APPS synonyms, and comprise:

• IC_XFER_MST – the transfer master; every row returned by the view originates here, aliased XFER.
• IC_ITEM_MST – supplies ITEM_NO, ITEM_DESC1, ITEM_UM, ITEM_UM2, LOT_CTL, LOT_INDIVISIBLE, SUBLOT_CTL, LOCT_CTL, DUALUM_IND, DEVIATION_LO, DEVIATION_HI.
• IC_LOTS_MST – supplies LOT_NO, SUBLOT_NO and QC_GRADE for the transferred lot.
• IC_LOTS_STS – supplies STATUS_DESC, the lot status description.
• IC_WHSE_MST – joined twice (aliases such as FWAREHOUSE and TWAREHOUSE) for the from-warehouse and to-warehouse names and their location-control flags.
• QC_GRAD_MST – supplies QC_GRADE_DESC.
• SY_REAS_CDS – joined multiple times for release, receive and cancel reason descriptions.
• FND_USER – supplies user names for the release, receive and cancel actors.

The relationships are all keyed from IC_XFER_MST: item_id to IC_ITEM_MST, lot_id to IC_LOTS_MST, orgn_code/warehouse codes to IC_WHSE_MST, reason codes to SY_REAS_CDS, and the ID columns to FND_USER.

Key Columns

The view exposes roughly eighty columns. The identifying and transactional columns are ROW_ID (the IC_XFER_MST ROWID), TRANSFER_ID, TRANSFER_NO, TRANSFER_BATCH, ORGN_CODE, TRANSFER_STATUS, ITEM_ID and LOT_ID. Location and quantity columns include FROM_WAREHOUSE, FROM_LOCATION, TO_WAREHOUSE, TO_LOCATION, RELEASE_QUANTITY1/2 and RECEIVE_QUANTITY1/2. Date columns cover SCHEDULED_RELEASE_DATE, ACTUAL_RELEASE_DATE, SCHEDULED_RECEIVE_DATE, ACTUAL_RECEIVE_DATE and CANCEL_DATE.

The audit and workflow columns are directly relevant to the user's search term received_by: RECEIVED_BY stores the FND_USER user_id of the person who received the transfer, while RELEASED_BY and CANCELED_BY capture the release and cancellation actors. The view also surfaces the WHO columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE and LAST_UPDATE_LOGIN, the DELETE_MARK flag, the ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 descriptive flexfield columns, TEXT_CODE and COMMENTS. Descriptive output includes ITEM_NO, ITEM_DESC1, LOT_NO, SUBLOT_NO, STATUS_DESC, QC_GRADE_DESC, WHSE_NAME and the three REASON_DESC1 values. Note that RECEIVED_BY holds an ID; resolve it against FND_USER for a user_name, since the view only surfaces textual user names for the release, receive and cancel aliases shown in the view text.

Common Use Cases and Queries

Typical uses include transfer status reporting, audit of who released and received inventory, lot and grade analysis across movements, and building interface extracts. Sample queries:

• Received transfers by user: SELECT transfer_no, item_no, received_by, actual_receive_date FROM apps.gmi_xfer_mst_v WHERE received_by = :user_id;
• Open transfers by organization: SELECT transfer_id, transfer_no, transfer_status, scheduled_release_date FROM apps.gmi_xfer_mst_v WHERE orgn_code = :orgn AND transfer_status <> 'CLOSED';
• Describing the view: SELECT column_name, data_type FROM dba_tab_columns WHERE table_name = 'GMI_XFER_MST_V';
• Join to FND_USER for a name: SELECT v.transfer_no, u.user_name FROM apps.gmi_xfer_mst_v v, fnd_user u WHERE u.user_id = v.received_by;