Search Results mrp_ap_rcv_shdrs_sn

Overview

MRP_AP_PO_RCV_SUPPLY_V is a Master Scheduling/MRP (MRP) application view that exposes receiving-related supply records for planning purposes. It consolidates purchase order, receipt, and supply snapshot information into a single denormalized structure, allowing MRP and reporting logic to treat expected and confirmed receipts as a uniform supply source alongside other supply types. Because the view's defining predicate is MS.SUPPLY_TYPE_CODE = 'RECEIVING', every row it returns represents a supply event tied to a receiving transaction.

The view is a reporting and integration artifact rather than a transactional entry point. It is well suited to reconciliation, supplier performance analysis, and integration feeds that need receipt-level supply detail joined to PO header, release, line, line location, and distribution context. Its column list is broad, spanning transaction identifiers, quantity and UOM pairs, destination routing, and PO revision data.

Underlying Base Objects

The view is defined over a mix of standard EBS base tables and MRP-specific snapshot tables. The documented base tables include PO_HEADERS_ALL, RCV_TRANSACTIONS, and several MRP_AP_* snapshot objects: MRP_AP_MRP_PARAS_SN, MRP_AP_SYS_ITEMS_SN, MRP_AP_PO_LINE_SN, MRP_AP_PO_LLOCS_SN, MRP_AP_PO_DISTS_SN, MRP_AP_PO_RELEASE_SN, MRP_AP_RCV_SHDRS_SN, and MRP_AP_SUPPLY_SN.

• PO_HEADERS_ALL supplies header-level vendor, segment, and revision information.
• RCV_TRANSACTIONS supplies the actual receiving transaction and its transaction date.
• The MRP_AP_* snapshot tables provide planning-oriented supply, item, line, location, distribution, release, and receipt header detail.

Joins are largely equijoins keyed on organization, item, PO header, PO line, line location, distribution, shipment header, and transaction identifiers. The PO release join is an outer join (PR.PO_RELEASE_ID(+) = MS.PO_RELEASE_ID), which permits rows for orders without releases. The ETRM metadata notes the view is not implemented in the documented database, meaning it exists as definitional metadata rather than a populated object in that instance.

Key Columns

Among the exposed columns, PO_REVISION_NUM is directly relevant to the search term. It is derived through a DECODE: when PO_RELEASE_ID is null, the view returns PH.REVISION_NUM from the PO header; otherwise it returns PR.REVISION_NUM from the release snapshot. This means PO_REVISION_NUM reflects the applicable revision at the level at which the supply was created. Related descriptive columns include PO_NUMBER (which concatenates the header segment with the release number when a release exists), LINE_NUM, RECEIVING_DOCUMENT_DESIGNATOR, and RECEIPT_NUM.

• TRANSACTION_ID, PO_HEADER_ID, ITEM_ID, VENDOR_ID — primary identifiers.
• RCV_TRX_QUANTITY, PRIMARY_UOM_QUANTITY and PRIMARY_UOM — quantity and unit context.
• MRP_EXPECTED_DELIVERY_DATE and EXPECTED_DELIVERY_DATE — planning dates.
• MRP_PRIMARY_QUANTITY, MRP_PRIMARY_UOM, MRP_DESTINATION_TYPE_CODE — planning supply attributes.
• DESTINATION_TYPE_CODE, TO_ORGANIZATION_ID, TO_SUBINVENTORY — routing and destination.

Common Use Cases and Queries

Typical usage includes reconciling expected receipts to planning supply, tracking revision levels on receipted orders, and feeding external systems with receipt-level detail. A representative query filtering on revision might be:

• SELECT PO_NUMBER, PO_REVISION_NUM, LINE_NUM, RCV_TRX_QUANTITY, MRP_EXPECTED_DELIVERY_DATE FROM MRP_AP_PO_RCV_SUPPLY_V WHERE PO_REVISION_NUM IS NOT NULL;
• Aggregating received quantity by vendor and destination: SELECT VENDOR_ID, TO_ORGANIZATION_ID, SUM(RCV_TRX_QUANTITY) FROM MRP_AP_PO_RCV_SUPPLY_V GROUP BY VENDOR_ID, TO_ORGANIZATION_ID;

Because the view is documented as not implemented in the reference database, availability should be verified in each target environment before use in production queries or integrations.