Search Results ship_status




Overview
Explore in AI Chat

Overview

APPS.IC_PURG_VW1 is a consolidated inventory and receiving transaction registry view owned by the APPS schema. Its purpose is to present a unified, cross-functional listing of transactional documents that affect inventory positions, purchase receipt processing, and shipping-related staging. Rather than surfacing a single underlying entity, the view aggregates header information from several Oracle EBS operational modules — production batch headers, purchase order headers, receipt headers, completed inventory transactions, order headers, and bill of lading records — into one homogeneous result set. The first column acts as a discriminator, tagging each row with a document type literal such as 'PROD', 'PORD', 'RECV', 'OPSO', or the inventory transaction codes 'ADJI', 'ADJR', 'GRDI', 'GRDR', 'STSI', 'STSR', 'TRNI', and 'TRNR'. This design makes IC_PURG_VW1 useful in reporting and interface contexts where consumers must enumerate a broad set of inventory-affecting documents without querying each module individually.

Underlying Base Objects

The ETRM metadata documents the view as defined over seven referenced base objects, all exposed through APPS synonyms: IC_TRAN_CMP, OP_BILL_LAD, OP_ORDR_DTL, OP_ORDR_HDR, PM_BTCH_HDR, PO_ORDR_HDR, and PO_RECV_HDR. The view's SQL is a set of UNION branches, each selecting from one of these objects. PM_BTCH_HDR contributes production batches filtered by BATCH_STATUS = 4. PO_ORDR_HDR contributes purchase orders filtered by PO_STATUS = 20. PO_RECV_HDR contributes receipt headers where DELETE_MARK = 0. IC_TRAN_CMP contributes completed inventory transactions restricted to the enumerated DOC_TYPE values. OP_ORDR_HDR and OP_BILL_LAD contribute order and bill-of-lading rows; both branches exclude records whose ORDER_ID or BOL_ID appears in OP_ORDR_DTL with a SHIP_STATUS below 20 while COMPLETED_IND = 0, meaning line-level shipping status is used as an exclusion filter. OP_ORDR_DTL therefore functions as a not-exists correlation source rather than a direct projection source.

Key Columns

The view exposes five positional columns. Column one is the document-type discriminator, populated with the literals 'PROD', 'PORD', 'RECV', 'OPSO', or with the DOC_TYPE value from IC_TRAN_CMP. Column two is an organization or plant code: PLANT_CODE for production batches, ORGN_CODE for purchase, receipt, order, and BOL records. Column three is a document number such as BATCH_NO, PO_NO, RECV_NO, ORDER_NO, or BOL_NO; for IC_TRAN_CMP rows this position is returned as an empty string. Column four is the corresponding primary key identifier — BATCH_ID, PO_ID, RECV_ID, DOC_ID, ORDER_ID, or BOL_ID. Column five is a date, sourced variably as LAST_UPDATE_DATE, RECV_DATE, or TRANS_DATE depending on the branch. Because the SQL does not alias these columns, consumers reference them positionally or through the view's stored definition.

Common Use Cases and Queries

Typical usage involves enumerating outstanding or completed documents relevant to shipping status. Notably, the view's own WHERE clause references SHIP_STATUS < 20 on OP_ORDR_DTL, so a search for "ship_status" intersects directly with this view's filtering logic: orders and bills of lading are suppressed when any related detail line remains unshipped (below status 20) and incomplete. A representative query is:

  • SELECT column1, column2, column3, column4, column5 FROM APPS.IC_PURG_VW1 WHERE column1 = 'OPSO';
  • SELECT * FROM APPS.IC_PURG_VW1 WHERE column5 >= SYSDATE - 30;
  • Joining the view to OP_ORDR_DTL on ORDER_ID to inspect the underlying SHIP_STATUS values that drive inclusion or exclusion.

Because column names are not aliased, positional references are standard practice. The view is read-only and intended for reporting; direct DML against it is not supported.