Search Results rcv_rec_sub_ledger_mrc_v




Overview
Explore in AI Chat

Overview

RCV_REC_SUB_LEDGER_MRC_V is an APPS-owned database view in Oracle E-Business Suite, registered under the Purchasing (PO) product family. Its name indicates that it exposes multiple reporting currencies (MRC) sub-ledger data for receiving transactions. The view is a retrofitted, MRC-aware wrapper over the receiving sub-ledger, and it participates in the flow that carries purchasing receipt accounting entries into the General Ledger interface.

Functionally, the view presents the accounting distributions generated from receiving transactions — receipts, deliveries, returns, and corrections — together with the general ledger accounting attributes required for journal creation, such as journal source, journal category, accounting date, period name, code combination, entered and accounted amounts, and currency conversion details. It also carries MRC-specific tax columns (ACCOUNTED_NR_TAX, ACCOUNTED_REC_TAX, ENTERED_NR_TAX, ENTERED_REC_TAX), which are the non-recoverable and recoverable tax portions used in multiple reporting currency contexts. Because the underlying data is filtered by SET_OF_BOOKS_ID derived from the session's CLIENT_INFO, the view returns sub-ledger lines for the set of books active in the user's session. This makes it a convenient reporting and integration surface without requiring callers to resolve the MRC base table or apply set-of-books logic themselves.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: the synonym RCV_MC_REC_SUB_LEDGER. The "MC" in the base object name denotes the multiple-currency variant of the receiving sub-ledger, and the view text confirms this by selecting directly from RCV_MC_REC_SUB_LEDGER.

The relationship is a one-to-one projection with an additional session-level filter: every column listed in the view is drawn from the base object, and the WHERE clause restricts rows to those matching the current set of books. The expression SET_OF_BOOKS_ID = NVL(TO_NUMBER(SUBSTR(USERENV('CLIENT_INFO'), 45, 10)), -99) extracts the set of books from the CLIENT_INFO session value; when no value is available, the comparison defaults to -99, returning no rows. Consumers should therefore initialize the session context before relying on the view's output. Because RCV_MC_REC_SUB_LEDGER is referenced through a synonym, the physical object may reside in another schema while APPS retains the public interface.

Key Columns

Common Use Cases and Queries

The view is typically used to reconcile receiving sub-ledger accounting to the GL interface, to trace purchasing accrual entries by source and category, and to build MRC reporting extracts. A query filtered by accounting line type is a common starting point:

  • Select all lines for a specific transaction or date range to verify amounts before the Create Accounting process.
  • Filter by JE_SOURCE_NAME and JE_CATEGORY_NAME to isolate Purchasing receipt or accrual entries.
  • Sum ENTERED_DR and ENTERED_CR grouped by ACCOUNTING_LINE_TYPE to analyze the composition of a period's distributions.
  • Join to RCV_TRANSACTIONS or the accounting events interface on RCV_TRANSACTION_ID or ACCOUNTING_EVENT_ID for detail-level tracing.

Example:

SELECT rcv_transaction_id, accounting_line_type, currency_code,
  SUM(entered_dr) AS dr, SUM(entered_cr) AS cr, period_name
FROM apps.rcv_rec_sub_ledger_mrc_v
WHERE accounting_date >= :from_date
  AND accounting_date < :to_date
GROUP BY rcv_transaction_id, accounting_line_type, currency_code, period_name;

Note that the view honors the session's set of books via USERENV('CLIENT_INFO'); in SQL*Plus or external tools, the CLIENT_INFO value must be set to the target operating unit and set of books before querying, otherwise the NVL default of -99 yields an empty result set.