Search Results qty_transfer




Overview
Explore in AI Chat

Overview

POA_EDW_RCV_TXNS_F_IV is a reporting view historically shipped with the Oracle Purchasing Intelligence (POA) product, an obsolete business intelligence application that predates and overlaps with the Oracle Business Intelligence (OBIEE) based procurement analytics now delivered out of the box in EBS 12.1.1 and 12.2.2. The "_IV" suffix denotes an "interface view" whose columns are already conformed to the purchasing star schema, in which natural keys are replaced or supplemented by surrogate foreign key columns (_FK_KEY) that join to EDW dimension tables.

The view exposes the receiving transaction fact set at the grain of a single receiving transaction line — one row per receipt, delivery, correction, return, or transfer transaction recorded in the Receiving module. Because the source POA_EDW_RCV_TXNS_F table physically stores descriptive attributes such as PACKING_SLIP, the interface view passes those attributes through unchanged while adding the surrogate key mappings needed by the Purchasing Intelligence ETL.

The user's search term "packing_slip" corresponds directly to the PACKING_SLIP column of this view, which is the receipt-level packing slip number entered on the receiving form and stored on the underlying RCV_TRANSACTIONS record.

Underlying Base Objects

According to the ETRM metadata, the view is defined over a single documented base object: POA_EDW_RCV_TXNS_F. The SELECT list references the columns of that table directly, with a derived literal column ' ' OPERATION_CODE appended at the end, and ROWID aliased to ROW_ID. No other base tables, synonyms, or views are documented as referenced.

The metadata also records "Not implemented in this database," confirming that in the environment from which the ETRM entry was extracted the POA objects had been dropped or were never installed; the definition survives only as documentation. In installations where POA was deployed, POA_EDW_RCV_TXNS_F was itself populated by the Purchasing Intelligence ETL from Receiving tables such as RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and PO_HEADERS/PO_LINES, but the view does not expose those joins — only the materialized fact table.

Key Columns

Common Use Cases and Queries

Because the view is not implemented in current 12.1.1/12.2.2 instances, it is chiefly of interest for migration analysis, custom reporting that originally targeted POA, or reconstructing equivalent data from the standard RCV_TRANSACTIONS tables. A representative query retrieving packing-slip detail is:

SELECT RCV_TXN_PK, PACKING_SLIP, BILL_OF_LADING, SUPPLIER_SITE_FK_KEY, QTY_RECEIVED, QTY_TXN_NET, TXN_DATE_FK_KEY FROM POA_EDW_RCV_TXNS_F_IV WHERE PACKING_SLIP IS NOT NULL;

Typical scenarios include reconciling packing slip numbers against quantities received for a supplier shipment, tracing receiving transactions to their shipment header for logistics analysis, and aggregating accepted versus rejected quantities by item revision or destination. In a modern EBS deployment the same information is obtained directly from RCV_TRANSACTIONS, joining RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES to recover packing slip, bill of lading, and shipment context.