Search Results cst_xla_rcv_lines_v




Overview
Explore in AI Chat

Overview

CST_XLA_RCV_LINES_V is an APPS-owned database view in Oracle E-Business Suite, catalogued under the BOM (Bills of Material) product family and used primarily within the Cost Management and Subledger Accounting (XLA) accounting generation flow. The view presents receiving accounting line detail in a form suitable for consumption by the XLA Create Accounting program and by downstream reporting, reconciliation, and diagnostic queries. It exposes one row per receiving subledger distribution, keyed to the subledger accounting event that produced it, thereby bridging the receiving subledger (RCV_RECEIVING_SUB_LEDGER) with the in-flight event set held in the XLA_EVENTS_GT global temporary table.

Because the view references XLA_EVENTS_GT, it is meaningful only during the window in which an accounting event set is populated in that global temporary table. Its role is therefore largely internal: it feeds the pipeline that converts receiving subledger rows into subledger accounting lines, and it is reused by reporting or troubleshooting queries that run inside the same accounting session context.

Underlying Base Objects

The documented base objects are RCV_RECEIVING_SUB_LEDGER (referenced as a SYNONYM) and XLA_EVENTS_GT (referenced as a SYNONYM). RCV_RECEIVING_SUB_LEDGER supplies the accounting distributions, amounts, tax figures, code combination, accrual method flag, and accounting line type. XLA_EVENTS_GT supplies the EVENT_ID, LEDGER_ID, ENTITY_CODE, and the SOURCE_ID_INT_n correlation keys used to join the two sources.

The join predicates are specific: XEG.ENTITY_CODE must equal 'RCV_ACCOUNTING_EVENTS', XEG.SOURCE_ID_INT_1 must equal RRS.RCV_TRANSACTION_ID, and XEG.SOURCE_ID_INT_2 must equal RRS.ACCOUNTING_EVENT_ID. Encumbrance reversal lines are handled separately, joining on REFERENCE9 rather than ACCOUNTING_EVENT_ID. A CARDINALITY(XEG, 1) hint tells the optimizer to treat the temporary event set as low cardinality.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling XLA event amounts to receiving subledger distributions and investigating why a receiving transaction produced unexpected accounting lines.

  • Retrieve all distributions for a given event: SELECT event_id, line_number, accounted_amount, code_combination_id FROM cst_xla_rcv_lines_v WHERE event_id = :event_id ORDER BY line_number;
  • Summarise accounted amounts by ledger: SELECT ledger_id, SUM(accounted_amount) FROM cst_xla_rcv_lines_v GROUP BY ledger_id;
  • Trace a distribution back to the subledger: SELECT distribution_identifier, rcv_accounting_line_type, accrual_method_flag FROM cst_xla_rcv_lines_v WHERE event_id = :event_id;

Because XLA_EVENTS_GT is a global temporary table, these queries return data only within the accounting session that populated it; outside that context the view returns no rows.