Search Results qc_tran_vw1




Overview
Explore in AI Chat

Overview

QC_TRAN_VW1 is a documented Oracle E-Business Suite view owned by the APPS schema and classified under the GMD (Process Manufacturing Product Development) product family. The ETRM metadata describes it as a "Lot source view," indicating that its purpose is to expose the origin lot and item context for material transactions generated within process manufacturing and receiving flows. The view is a UNION of three SELECT statements, each drawing from a related but distinct transaction stream: production (DOC_TYPE = 'PROD'), receiving (DOC_TYPE = 'RECV'), and inventory adjustments (DOC_TYPE IN ('ADJI', 'ADJR') with TRANS_QTY > 0). Because it consolidates these streams into a single column-shape, QC_TRAN_VW1 gives downstream reporting, lot genealogy, and quality workflows a uniform way to relate a transaction to its source (ITEM_ID/TARGET_ITEM_ID and LOT_ID/TARGET_LOT_ID) without querying the individual base objects separately. The view also surfaces the COMPLETED_IND flag, which is the column most commonly searched by users of this object.

Underlying Base Objects

The documented base objects referenced by the view are:

  • IC_TRAN_VW1 (VIEW) — the principal lot-transaction basis for each UNION branch; supplies ITEM_ID, LOT_ID, DOC_TYPE, LINE_ID, TRANS_* measure columns, and COMPLETED_IND.
  • IC_TRAN_PND (SYNONYM) — the pending transaction table; joined to IC_TRAN_VW1 on DOC_ID for the production branch.
  • PM_MATL_DTL (SYNONYM) — material detail; joined twice (as C and D) for line-type filtering of the production branch.
  • PM_BTCH_HDR (SYNONYM) — batch header; provides BATCH_NO as DOC_NO and the BATCH_ID join to DOC_ID.
  • PO_RECV_DTL (SYNONYM) and PO_RECV_HDR (SYNONYM) — receiving detail and header tables for the RECV branch, supplying LINE_NO and RECV_NO.

The production branch joins IC_TRAN_VW1 to IC_TRAN_PND, PM_MATL_DTL, and PM_BTCH_HDR; the receiving branch joins IC_TRAN_VW1 to PO_RECV_DTL and PO_RECV_HDR; the adjustment branch selects directly from IC_TRAN_VW1. Because the constituent objects are documented as synonyms, the view resolves under APPS synonyms to the underlying GMD/INV/PO tables.

Key Columns

  • ITEM_ID / LOT_ID — the source item and lot for the transaction.
  • TARGET_ITEM_ID / TARGET_LOT_ID — the destination item and lot; on the adjustment branch these repeat ITEM_ID/LOT_ID.
  • COMPLETED_IND — the completion flag carried from IC_TRAN_VW1/IC_TRAN_PND, commonly used to distinguish completed from pending transactions.
  • DOC_TYPE / DOC_ID / DOC_LINE / DOC_NO — the document classification, surrogate key, line number, and document number (batch number for production, receipt number for receiving).
  • LINE_ID / LINE_TYPE — the transaction line identity and its type (production uses 1/2 on the source and -1 on the target; receiving uses the PO receipt line).
  • TRANS_ID, TRANS_DATE, TRANS_QTY, TRANS_QTY2, TRANS_UM, TRANS_UM2, TRANS_STAT — the transaction identity, date, primary and secondary quantities, units of measure, and status.
  • OP_CODE, ORGN_CODE, LOCATION, WHSE_CODE, REASON_CODE, TEXT_CODE, CREATION_DATE — operation, organization, location, warehouse, reason, text, and creation context.

Common Use Cases and Queries

The view supports lot source/genealogy reporting, quality data collection on production and receipt transactions, and reconciliation of completed versus pending transaction activity. A representative query filtering on the searched column is:

SELECT DOC_NO, DOC_TYPE, ITEM_ID, LOT_ID, TARGET_ITEM_ID, TARGET_LOT_ID, TRANS_QTY, TRANS_DATE
FROM APPS.QC_TRAN_VW1
WHERE COMPLETED_IND = 'Y';

To isolate receiving transactions for a warehouse:

SELECT DOC_NO, ITEM_ID, LOT_ID, TRANS_QTY, TRANS_UM, WHSE_CODE
FROM APPS.QC_TRAN_VW1
WHERE DOC_TYPE = 'RECV' AND WHSE_CODE = :warehouse;

To trace production output against its input lots, join DOC_NO (batch) and compare ITEM_ID/LOT_ID to TARGET_ITEM_ID/TARGET_LOT_ID. Practitioners also use the view as a source in lot attribute queries and in quality results capture where the originating transaction must be resolved.

Oracle Proprietary, Confidential Information — Legal Notices.