Results for “substitute_unordered_code”

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

Overview

The CST_XLA_RCV_REF_V view is a public application view owned by the APPS schema within Oracle E-Business Suite, cataloged under the BOM – Bills of Material product family. In ETRM 12.2.2 the object is reported with a VALID status and is registered against the APPS owner. The view serves as a consolidated reference bridge between Oracle Subledger Accounting (XLA) receiving events and the underlying receiving transaction detail captured in the receiving subledger. Its central purpose is to present a denormalized, accounting-ready picture of each receiving accounting event, joining the event header to the transaction rows that describe what was received, from whom, and under what commercial terms.

Because costing and accounting for receipts, returns, corrections, deliveries, and period-end accruals all require consistent attribution of quantity, unit price, and transaction amounts, CST_XLA_RCV_REF_V is the mechanism by which those attributes are surfaced to the cost and accounting programs. It is commonly consumed by XLA event generation and by extension logic that produces Create Accounting entries for receiving events. Reports and integrations that need to reconcile receiving activity to accounting event lines, or that investigate specific flags such as the receipt exception indicator, also read from this view.

Underlying Base Objects

Per the documented ETRM metadata, CST_XLA_RCV_REF_V is defined over five referenced base objects, all exposed through synonyms in the APPS schema:

• RCV_ACCOUNTING_EVENTS — the driving table in the view text, joined with the LEADING hint, supplying the accounting event identifier, organization, event type, transaction date, quantities, amounts, and pricing attributes.
• RCV_TRANSACTIONS — the receiving transaction detail, supplying transaction type, consigned and user-entered flags, receipt exception flag, inspection and quality attributes, shipment references, and WIP/job context.
• RCV_RECEIVING_SUB_LEDGER — the receiving subledger, providing the linkage between receiving transactions and their accounting event representation.
• PO_HEADERS_ALL — the purchasing document header, contributing vendor and vendor site identifiers.
• XLA_EVENTS_GT — the XLA events global temporary table, used to scope or filter the event population being referenced.

The view text applies a targeted cardinality hint against the XLA events global table and an index-driven access path on RCV_ACCOUNTING_EVENTS, indicating it is tuned for point lookups keyed by accounting event or transaction rather than wholesale scans.

Key Columns

The view exposes a wide attribute set, of which the following are most significant:

• REF_RCV_ACCOUNTING_EVENT_ID — the accounting event identifier that anchors the row to XLA.
• OPERATING_UNIT_ID, ORGANIZATION_ID — the org context for the receipt.
• RCV_TRANSACTION_ID, RCV_TRANSACTION_TYPE — the receiving transaction and its type; the type defaults to PERIOD END ACCRUAL for event type 14 when the transaction type is null.
• RECEIPT_EXCEPTION_FLAG — indicates whether the receiving transaction was created as or associated with a receipt exception, and is frequently queried for exception analysis.
• RCV_CONSIGNED_FLAG, RCV_USER_ENTERED_FLAG — consignment and manual entry indicators.
• PRIMARY_QUANTITY, TRANSACTION_QUANTITY, SOURCE_DOC_QUANTITY and their unit-of-measure counterparts — the quantity basis for costing.
• RAE_UNIT_PRICE, RAE_PRIOR_UNIT_PRICE, RAE_TRANSACTION_AMOUNT — valuation attributes carried from the accounting event.
• VENDOR_ID, VENDOR_SITE_ID — supplier identification sourced from PO_HEADERS_ALL.
• Inspection, quality, project, task, WIP, and shipment columns that support downstream accounting attribution.

Common Use Cases and Queries

Typical usage includes exception investigation, reconciliation of receipts to accounting events, and diagnostics for period-end accrual processing. A representative query retrieving receipt exceptions for a given organization is:

• SELECT ref_rcv_accounting_event_id, rcv_transaction_id, rcv_transaction_type, receipt_exception_flag, inventory_item_id, transaction_quantity FROM cst_xla_rcv_ref_v WHERE organization_id = :org_id AND receipt_exception_flag = 'Y';

A second common pattern reconciles event amounts to vendor and receipt detail:

• SELECT r.ref_rcv_accounting_event_id, r.rcv_transaction_id, r.vendor_id, r.rae_unit_price, r.rae_transaction_amount FROM cst_xla_rcv_ref_v r WHERE r.ref_rcv_accounting_event_id = :event_id;

Because the view is a wrapper rather than a stored table, no DML should ever be issued against it; all access is read-only and governed by the APPS schema privileges and any row-level organization security applied by the calling responsibility.