Results for “cst_rcv_rae_v”

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

Overview

CST_RCV_RAE_V is a valid, published APPS-owned database view in Oracle E-Business Suite, documented under the BOM (Bills of Material) product family. It is defined over the Receiving Accounting Events tables and exposes a consolidated, denormalized picture of each receiving accounting event together with the context required to interpret it: the receiving transaction, the inventory organization, the purchase order document, the shipment, and the vendor. The view carries the full Receiving Accounting Event (RAE) row along with descriptive attributes resolved from master and transactional tables, which makes it suitable for costing, reconciliation, and audit reporting without requiring the caller to re-implement the many joins in the definition.

Because receiving accounting events are the trigger points at which receipt activity is translated into accounting entries and cost, the view functions as a single reporting surface for questions about what was received, from which supplier and document, into which organization, at what quantity and price, and with what accounting/reconciliation flags. It is frequently referenced in custom reports, extracts, and integration queries where item cost, landed cost, tax, and intercompany indicators for receipts must be evaluated together.

Underlying Base Objects

The ETRM 12.2.2 metadata lists the referenced base objects as CST_ORGANIZATION_DEFINITIONS (view), FND_GLOBAL (package), MTL_SYSTEM_ITEMS_VL (view), MTL_UNITS_OF_MEASURE (synonym), PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), RCV_ACCOUNTING_EVENTS, RCV_ACCOUNTING_EVENT_TYPES, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS. The driving table is RCV_ACCOUNTING_EVENTS (aliased RAE), joined to RCV_TRANSACTIONS for the transaction detail; RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES supply receipt and shipment numbers; PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_REQUISITION_HEADERS, and PO_REQUISITION_LINES provide the procurement document chain; PO_VENDORS and PO_VENDOR_SITES_ALL provide supplier identity; CST_ORGANIZATION_DEFINITIONS supplies organization name, code, and set of books; MTL_SYSTEM_ITEMS_VL supplies item description; MTL_UNITS_OF_MEASURE resolves unit-of-measure codes; and RCV_ACCOUNTING_EVENT_TYPES resolves event type descriptions/names. FND_GLOBAL is referenced for session-level context (for example, responsibility-level org context) used inside the view or its helper views.

Key Columns

The view exposes ROWID plus a broad set of RAE attributes and joined descriptors. Organization and ledger context appear as ORGANIZATION_ID, ORG_ID, ORGANIZATION_NAME, ORGANIZATION_CODE, and SET_OF_BOOKS_ID. Transaction identity is carried by RCV_TRANSACTION_ID, ACCOUNTING_EVENT_ID, EVENT_TYPE_ID, and the decoded EVENT_TYPE_NAME, along with TRANSACTION_DATE, TRANSACTION_QUANTITY, PRIMARY_QUANTITY, and their respective UOM codes.

Procurement and supplier context is provided by PO_HEADER_ID (document number via NVL of CLM_DOCUMENT_NUMBER and SEGMENT1), PO_LINE_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID, RELEASE_NUM, requisition header and line identifiers, VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, and VENDOR_SITE_CODE. Receipt context comes from RECEIPT_NUM, SHIPMENT_NUM, SHIPMENT_HEADER_ID, LINE_NUM, and SHIPMENT_LINE_ID. Cost and accounting columns include UNIT_PRICE, PRIOR_UNIT_PRICE, UNIT_LANDED_COST, TRANSACTION_AMOUNT, NR_TAX, REC_TAX, NR_TAX_AMOUNT, REC_TAX_AMOUNT, PRIOR_NR_TAX, PRIOR_REC_TAX, CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_DATE, together with the flags ACCOUNTED_FLAG, PROCUREMENT_ORG_FLAG, CROSS_OU_FLAG, INVOICED_FLAG, and PA_ADDITION_FLAG and the standard WHO/audit columns. Notably, the location is exposed through RT.LOCATION_ID rather than a distinctly named receiving_location_id column; users searching for "receiving_location_id" should select LOCATION_ID from this view (or RT.LOCATION_ID when querying RCV_TRANSACTIONS directly).

Common Use Cases and Queries

Typical uses include reconciling receipt transactions to accounting events, analyzing landed cost and tax by vendor and item, verifying whether receipts have been accounted or invoiced, and feeding downstream costing or intercompany reporting.

• Receipts by organization, showing location and vendor: SELECT organization_code, receipt_num, transaction_date, transaction_quantity, location_id, vendor_name FROM cst_rcv_rae_v WHERE organization_id = :p_org ORDER BY transaction_date DESC;
• Unaccounted receiving events: SELECT accounting_event_id, receipt_num, event_type_name, transaction_amount, currency_code FROM cst_rcv_rae_v WHERE accounted_flag = 'N';
• Landed cost and tax detail for a PO: SELECT po_header_id, po_line_id, item_description, unit_price, unit_landed_cost, nr_tax_amount, rec_tax_amount, currency_code FROM cst_rcv_rae_v WHERE segment1 = :p_po_number;
• Receipts by location for a given organization: SELECT location_id, receipt_num, shipment_num, transaction_date, transaction_quantity FROM cst_rcv_rae_v WHERE organization_id = :p_org AND location_id IS NOT NULL;

Because the view is a pure SELECT with resolved joins, it can be used directly in reports, BI Publisher data models, and integration extracts. When the LOCATION_ID column is required, it is best sourced directly from this view to retain the joined context rather than re-querying the base receiving tables.