Search Results rcv_sl_details_id
Overview
APPS.RCV_SUB_LEDGER_DET_MRC_V is a multi-reporting-currency (MRC) view in Oracle E-Business Suite that exposes receiving subledger accounting distributions across multiple reporting currencies. In the MRC architecture used prior to full Subledger Accounting (SLA) adoption, each reporting currency required its own set of accounting rows. This view presents the rows held in the MRC subledger detail table for a given set of books, giving reporting and reconciliation users a single read-only interface into receiving-related accounting entries for currencies other than the primary ledger currency.
The view contains no procedural or filtering logic of its own; it is a straight projection of the columns from its single underlying object. Its principal value is abstraction and naming stability: applications and reports can reference RCV_SUB_LEDGER_DET_MRC_V regardless of the physical table name, and the columns are aligned to the standard subledger detail convention (accounted and entered amounts, journal source and category, period name, code combination, and so on). For developers searching on rcv_sl_details_id, this view is the MRC counterpart to the primary receiving subledger detail view and is the correct target when the reported amounts belong to a non-primary reporting currency.
Underlying Base Objects
The view is defined over a single base object, RCV_MC_SUB_LEDGER_DETAILS, which is exposed to APPS through a synonym. Every column in the view corresponds one-to-one with a column in that table; no joins, unions, or aggregations are performed. The relationship is therefore direct: the view is a column-level alias of the table, and all row filtering, currency scoping, and set-of-books restriction must be supplied by the calling query through predicates such as SET_OF_BOOKS_ID, CURRENCY_CODE, or PERIOD_NAME.
Because the object is a simple view rather than a materialized view, no refresh or staleness considerations apply; queries always see the current committed contents of RCV_MC_SUB_LEDGER_DETAILS.
Key Columns
RCV_SL_DETAILS_ID— The identifier linking the MRC accounting row back to the originating receiving subledger detail record. This is the column users typically search on when tracing a receiving distribution.RCV_TRANSACTION_ID— The receiving transaction that generated the accounting entry.SET_OF_BOOKS_IDandCHART_OF_ACCOUNTS_ID— Identify the ledger and chart of accounts for which the distribution was created.CURRENCY_CODE,FUNCTIONAL_CURRENCY_CODE— The transaction currency and the functional currency of the set of books.ACCOUNTED_DR,ACCOUNTED_CR— Debit and credit amounts in the ledger's functional currency.ENTERED_DR,ENTERED_CR— Debit and credit amounts in the entered (transaction) currency.CURRENCY_CONVERSION_RATE,CURRENCY_CONVERSION_DATE,USER_CURRENCY_CONVERSION_TYPE— The rate and date used to convert entered amounts to accounted amounts.CODE_COMBINATION_ID— The accounting flexfield combination charged by the distribution.JE_SOURCE_NAME,JE_CATEGORY_NAME,JE_BATCH_NAME,JE_HEADER_NAME,JE_LINE_DESCRIPTION— Journal attributes that govern how the row is transferred to and presented in General Ledger.ACCOUNTING_DATE,TRANSACTION_DATE,PERIOD_NAME— Date and period information used for accounting and reporting cutoffs.GL_SL_LINK_ID,DATE_CREATED_IN_GL— Support reconciliation between the receiving subledger and its GL balances.ATTRIBUTE1throughATTRIBUTE15— Descriptive flexfield segments available for client-specific reporting.
Common Use Cases and Queries
Typical uses include reconciliation of receiving accruals per reporting currency, tracing a receiving transaction's accounting lines to GL, and reporting entered-versus-accounted variances arising from currency conversion.
SELECT rcv_sl_details_id,
rcv_transaction_id,
set_of_books_id,
currency_code,
accounted_dr,
accounted_cre
FROM apps.rcv_sub_ledger_det_mrc_v
WHERE rcv_sl_details_id = :p_rcv_sl_details_id;
SELECT period_name,
SUM(accounted_dr) accounted_dr,
SUM(accounted_cr) accounted_cr
FROM apps.rcv_sub_ledger_det_mrc_v
WHERE set_of_books_id = :p_set_of_books_id
AND period_name = :p_period_name
GROUP BY period_name;
-
VIEW: APPS.RCV_SUB_LEDGER_DET_MRC_V
12.2.2
-
VIEW: PO.RCV_MC_SUB_LEDGER_DETAILS#
12.2.2
-
VIEW: PO.RCV_SUB_LEDGER_DETAILS#
12.2.2
-
View: RCV_SUB_LEDGER_DET_MRC_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.RCV_SUB_LEDGER_DET_MRC_V, object_name:RCV_SUB_LEDGER_DET_MRC_V, status:VALID, product: PO - Purchasing , implementation_dba_data: APPS.RCV_SUB_LEDGER_DET_MRC_V ,
-
View: RCV_SUB_LEDGER_DET_MRC_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.RCV_SUB_LEDGER_DET_MRC_V, object_name:RCV_SUB_LEDGER_DET_MRC_V, status:VALID, product: PO - Purchasing , implementation_dba_data: APPS.RCV_SUB_LEDGER_DET_MRC_V ,
-
VIEW: APPS.RCV_SUB_LEDGER_DET_MRC_V
12.1.1
-
VIEW: PO.RCV_MC_SUB_LEDGER_DETAILS#
12.2.2
owner:PO, object_type:VIEW, object_name:RCV_MC_SUB_LEDGER_DETAILS#, status:VALID,
-
VIEW: PO.RCV_SUB_LEDGER_DETAILS#
12.2.2
owner:PO, object_type:VIEW, object_name:RCV_SUB_LEDGER_DETAILS#, status:VALID,
-
TABLE: PO.RCV_MC_SUB_LEDGER_DETAILS
12.1.1
owner:PO, object_type:TABLE, fnd_design_data:PO.RCV_MC_SUB_LEDGER_DETAILS, object_name:RCV_MC_SUB_LEDGER_DETAILS, status:VALID,
-
TABLE: PO.RCV_MC_SUB_LEDGER_DETAILS
12.2.2
owner:PO, object_type:TABLE, fnd_design_data:PO.RCV_MC_SUB_LEDGER_DETAILS, object_name:RCV_MC_SUB_LEDGER_DETAILS, status:VALID,
-
VIEW: APPS.RCV_SUB_LEDGER_DET_MRC_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PO.RCV_SUB_LEDGER_DET_MRC_V, object_name:RCV_SUB_LEDGER_DET_MRC_V, status:VALID,
-
VIEW: APPS.RCV_SUB_LEDGER_DET_MRC_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PO.RCV_SUB_LEDGER_DET_MRC_V, object_name:RCV_SUB_LEDGER_DET_MRC_V, status:VALID,
-
TABLE: PO.RCV_SUB_LEDGER_DETAILS
12.2.2
owner:PO, object_type:TABLE, fnd_design_data:PO.RCV_SUB_LEDGER_DETAILS, object_name:RCV_SUB_LEDGER_DETAILS, status:VALID,
-
TABLE: PO.RCV_SUB_LEDGER_DETAILS
12.1.1
owner:PO, object_type:TABLE, fnd_design_data:PO.RCV_SUB_LEDGER_DETAILS, object_name:RCV_SUB_LEDGER_DETAILS, status:VALID,
-
eTRM - PO Tables and Views
12.1.1
description: Temporary table for tracking a receiving upgrade from Release 9 to Release 10 ,
-
eTRM - PO Tables and Views
12.2.2
description: Temporary table for tracking a receiving upgrade from Release 9 to Release 10 ,