Results for “cst_pac_receiving_values_v”

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

Overview

CST_PAC_RECEIVING_VALUES_V is an APPS-owned database view that consolidates receiving transaction data with Period Average Costing (PAC) acquisition cost information. It is a foundational reporting object for the Oracle E-Business Suite Cost Management and Bills of Material modules, and it is referenced by the standard receiving valuation and period-close reports associated with the PAC cost method. The view answers a specific business question: what did a given receiving transaction cost, in which cost group, in which accounting period, and against which source document did it originate.

The view joins purchasing, receiving, inventory, and costing tables so that each row represents a non-consigned receiving transaction enriched with its PAC acquisition cost. Because the definition is fixed in the APPS schema and status is VALID, it can be referenced by custom concurrent programs, Oracle Discoverer workbooks, Business Intelligence Publisher data models, and ad-hoc SQL without recreating the underlying join logic.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms: CST_COST_GROUPS, CST_COST_GROUP_ASSIGNMENTS, CST_PAC_PERIODS, CST_RCV_ACQ_COSTS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS, PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_SUPPLY, and RCV_TRANSACTIONS.

The central fact table is CST_RCV_ACQ_COSTS, which stores the acquisition cost and the PAC period identifier for each receiving transaction. RCV_SUPPLY, RCV_SHIPMENT_HEADERS, and RCV_SHIPMENT_LINES supply the physical receipt detail—item, revision, quantities, UOM, packing slip, and destination type. RCV_TRANSACTIONS provides the transaction ID, date, and organization, and the view filters out consigned inventory via NVL(RCT.CONSIGNED_FLAG,'N') = 'N'. The purchasing tables (PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL) and requisition tables (PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL) are outer-joined so that the source document can be resolved for PO, requisition, or inter-org inventory transfers. CST_COST_GROUPS and CST_COST_GROUP_ASSIGNMENTS map the receiving organization to a legal entity and cost group, while MTL_SYSTEM_ITEMS supplies the primary UOM and item master context.

Key Columns

• TRANSACTION_ID / RCV_TRANSACTION_ID — Identifier of the receiving transaction and its link to RCV_TRANSACTIONS.
• TRANSACTION_DATE / RECEIPT_DATE — Date the transaction was processed and the physical receipt date.
• ORGANIZATION_ID — Receiving inventory organization; used to join to cost group and item definitions.
• LEGAL_ENTITY / COST_GROUP_ID — Legal entity and cost group that own the PAC cost.
• ITEM_ID / ITEM_REVISION / ITEM_DESCRIPTION / PRIMARY_UOM_CODE / UNIT_OF_MEASURE — Item and unit-of-measure context.
• RECEIPT_NUM / SHIPMENT_NUM / PACKING_SLIP / FREIGHT_CARRIER_CODE — Shipping and receipt identifiers.
• QUANTITY_SHIPPED / TO_ORG_PRIMARY_QUANTITY / TO_ORG_PRIMARY_UOM — Quantities received and expressed in the destination organization's primary UOM.
• SOURCE_DOCUMENT_CODE — Indicates whether the source is INVENTORY, PO, or REQ.
• SOURCE_DOCUMENT — The resolved document number: shipment number for inventory transfers, PO number (SEGMENT1) for purchase orders, or requisition number for requisitions.
• DOCUMENT_LINE_NUM — The line number on the source document, decoded from RSL.LINE_NUM for inventory, PL.LINE_NUM for PO, and PRL.LINE_NUM for requisition. This is the column most often queried by users searching for document_line_num, since it identifies the specific PO or requisition line that generated the receipt.
• DELIVER_TO_LOCATION_ID — Destination location, decoded by source document type.
• ACQUISITION_COST / PERIOD_ID — The PAC acquisition cost amount and the costing period it belongs to.
• VENDOR_ID — Supplier associated with the shipment.

Common Use Cases and Queries

Typical uses include reconciling PAC acquisition costs to the general ledger, tracing a receipt back to its originating PO or requisition line, and analyzing receiving activity by cost group or period.

To retrieve document line details for receipts in a period:

SELECT receipt_num, source_document, document_line_num,
       item_description, to_org_primary_quantity, acquisition_cost
FROM   apps.cst_pac_receiving_values_v
WHERE  period_id = :p_period_id
AND    source_document_code = 'PO';

To trace a single PO line back to its receipts:

SELECT receipt_num, receipt_date, quantity_shipped,
       acquisition_cost, cost_group_id
FROM   apps.cst_pac_receiving_values_v
WHERE  source_document_code = 'PO'
AND    source_document = :p_po_number
AND    document_line_num = :p_line_num
ORDER BY receipt_date;

Because the view does not expose a period name or organization name, these are typically joined from CST_PAC_PERIODS and MTL_PARAMETERS respectively, or from the organization and period dimensions available in the reporting layer. Queries should always filter on ORGANIZATION_ID and PERIOD_ID or TRANSACTION_DATE to keep execution plans efficient, as the view joins more than fifteen base tables.