Search Results rcv_sub_ledger_det_mrc_v

Overview

The RCV_SUB_LEDGER_DET_MRC_V view, owned by the APPS schema, belongs to the Oracle Purchasing (PO) product family and supports the Receiving (RCV) subledger accounting flow. It is a Multi-Reporting-Currency (MRC) view that exposes subledger accounting detail rows across multiple sets of books, allowing users to query accounting distributions associated with receiving transactions without requiring a separate query per ledger. Because it is an MRC-style view, each logical receiving transaction may appear multiple times when more than one set of books is assigned, distinguished primarily by SET_OF_BOOKS_ID and CURRENCY_CODE. In Oracle EBS 12.1.1 and 12.2.2 this view is commonly used in reporting and integration scenarios where receiving accounting entries must be reconciled to the General Ledger, or where the linkage between receiving distributions and their corresponding GL journal lines is required. The presence of the GL_SL_LINK_ID column makes this view particularly relevant for subledger-to-GL reconciliation, since it carries the key that ties a subledger accounting line back to the GL interface and journal entry.

Underlying Base Objects

The view is defined over RCV_MC_SUB_LEDGER_DETAILS, which is documented as a synonym referenced by the view. The select list projects the full set of accounting columns from this underlying source, including amounts, currencies, journal entry attributes, periods, and descriptive flexfields. Because RCV_MC_SUB_LEDGER_DETAILS is exposed as an APPS synonym, the view depends on the underlying receiving subledger detail table that stores the multi-currency accounting distributions generated by the Receiving subledger accounting process. Applications and reports should access the view rather than the synonym directly, since the view enforces the documented column projection and naming used by Oracle's standard reporting components.

Key Columns

The following columns are the most frequently referenced:

• RCV_TRANSACTION_ID and RCV_SL_DETAILS_ID — identify the receiving transaction and the specific subledger detail line.
• SET_OF_BOOKS_ID — the ledger for the accounted row; central to MRC filtering.
• CURRENCY_CODE, FUNCTIONAL_CURRENCY_CODE — transaction and functional currencies.
• CODE_COMBINATION_ID — the accounting flexfield combination for the distribution.
• ACCOUNTED_DR / ACCOUNTED_CR, ENTERED_DR / ENTERED_CR — debits and credits in functional and entered amounts.
• ACCOUNTING_DATE, TRANSACTION_DATE, PERIOD_NAME — key dates and the GL period.
• JE_SOURCE_NAME, JE_CATEGORY_NAME, JE_BATCH_NAME, JE_HEADER_NAME — journal entry classification for reconciliation.
• GL_SL_LINK_ID — the linkage identifier between the subledger line and its corresponding General Ledger journal line; this is the primary column users search for when reconciling receiving accounting with GL.
• SOURCE_DOC_QUANTITY, PO_LINE_LOCATION_ID — document-level context for the distribution.
• Descriptive flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15) and REFERENCE1–REFERENCE10 — additional attribute and reference data.

Common Use Cases and Queries

Typical scenarios include reconciling receiving subledger entries to GL journals, investigating multi-currency accounting entries, and extracting distributions for reporting or data warehouse loading. The GL_SL_LINK_ID is the key column used to join receiving accounting detail to General Ledger balances and journals.

Example 1 — locate lines by GL/SL link identifier:

SELECT rcv_transaction_id,
       set_of_books_id,
       period_name,
       accounted_dr,
       accounted_cr,
       gl_sl_link_id
FROM   apps.rcv_sub_ledger_det_mrc_v
WHERE  gl_sl_link_id IS NOT NULL
ORDER  BY rcv_transaction_id;

Example 2 — summarize accounted amounts by ledger and period:

SELECT set_of_books_id,
       period_name,
       SUM(accounted_dr) AS total_dr,
       SUM(accounted_cr) AS total_cr
FROM   apps.rcv_sub_ledger_det_mrc_v
WHERE  rcv_transaction_id = :p_rcv_transaction_id
GROUP  BY set_of_books_id, period_name;

Example 3 — join to GL for reconciliation using the link identifier:

SELECT r.gl_sl_link_id,
       r.accounted_dr,
       r.accounted_cr,
       r.period_name
FROM   apps.rcv_sub_ledger_det_mrc_v r
WHERE  r.gl_sl_link_id = :p_gl_sl_link_id;

Filtering on SET_OF_BOOKS_ID is advisable when only a specific reporting ledger is required, as the MRC nature of the view may return the same receiving transaction across multiple sets of books.