Search Results gl_mc_reporting_options

Overview

RCV_AEL_SL_MRC_V is an APPS-owned reporting view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that consolidates the accounting events and sub-ledger distributions generated by receiving activity. In the ETRM product classification it is registered under PO – Purchasing, but its defining SQL draws together receipt, receiving transaction, purchase order, and multi-reporting-currency (MRC) accounting data into a single denormalized row set. The "AEL" and "SL" components of the name refer to the Accounting Events Ledger and Sub-Ledger lineage, while the "MRC_V" suffix indicates the view predates or mirrors the multi-reporting-currency construction used throughout the R12 sub-ledger accounting (SLA) architecture. The view is used principally as a reconciliation and drill-back source, allowing purchasing and payables accounting data to be reported alongside general ledger reporting-currency rules such as those sourced from GL_MC_REPORTING_OPTIONS — the search term associated with this query.

Underlying Base Objects

The documented base objects comprise a mixture of base tables, synonyms, views, and PL/SQL packages. Purchase order sourcing is handled through PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_DISTRIBUTIONS, PO_VENDORS, PO_VENDOR_SITES, and PO_LOOKUP_CODES. Receiving sourcing uses RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS_MRC_V, and RCV_REC_SUB_LEDGER_MRC_V. Accounting and reference data come from GL_DAILY_CONVERSION_TYPES, GL_JE_CATEGORIES, GL_LEDGER_RELATIONSHIPS, and ORG_ORGANIZATION_DEFINITIONS. Supporting utilities include the FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages, the latter two typically used for organization-level security filtering. Notably, the multi-currency MRC variants (PO_HEADERS_MRC_V, PO_DISTRIBUTIONS_MRC_V, RCV_SHIPMENT_HEADERS_MRC_V, RCV_TRANSACTIONS_MRC_V, and RCV_REC_SUB_LEDGER_MRC_V) supply the reporting set-of-books context, and GL_MC_REPORTING_OPTIONS supplies the reporting-currency option metadata used in the join condition.

Key Columns

The view exposes the reporting SET_OF_BOOKS_ID together with the operating ORG_ID and ORGANIZATION_CODE, establishing the ledger and inventory organization context. Receiving data is represented by RECEIPT_NUM, SHIPMENT_HEADER_ID, LINE_NUM, ITEM_ID, ITEM_DESCRIPTION, and ITEM_REVISION. Transaction detail is carried in TRANSACTION_TYPE, TRANSACTION_DATE, COMMENTS, UNIT_OF_MEASURE, SUBINVENTORY, and SOURCE_DOC_QUANTITY. Purchase order attribution includes VENDOR_ID, VENDOR_NAME, VENDOR_SITE_CODE, PO SEGMENT1, DISTRIBUTION_NUM, RELEASE_NUM, and SHIPMENT_NUM, with PRICE_OVERRIDE and UNIT_PRICE providing valuation figures. Accounting columns include CODE_COMBINATION_ID, CURRENCY_CODE, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR, ACCOUNTING_DATE, JE_CATEGORY_NAME, and the currency conversion trio of CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_CONVERSION_RATE. The view also exposes the literal transaction identifiers and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and the request/program columns) that support drill-down.

Common Use Cases and Queries

Typical usage centers on reproducing the accounting entries generated for receipt transactions and reconciling them to the corresponding purchase order distributions or payables events. Reporting by set of books and operating unit is standard, and the multi-currency construction makes the view suitable for reporting-currency analyses where GL_MC_REPORTING_OPTIONS determines the translation behavior.

• Receipt accounting reconciliation: Selecting RECEIPT_NUM, TRANSACTION_TYPE, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, and ACCOUNTED_CR filtered by TRANSACTION_DATE range and SET_OF_BOOKS_ID.
• Vendor and PO drill-back: Joining VENDOR_NAME, SEGMENT1, DISTRIBUTION_NUM, and SHIPMENT_NUM to identify the originating purchasing document for a given sub-ledger entry.
• Currency conversion audit: Returning CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_CONVERSION_RATE for entries where conversion information is required.
• Organization-level reporting: Constraining by ORG_ID and ORGANIZATION_CODE, respecting HR_SECURITY filtering inherited through the underlying views.

Sample query: SELECT SET_OF_BOOKS_ID, ORG_ID, RECEIPT_NUM, TRANSACTION_TYPE, TRANSACTION_DATE, VENDOR_NAME, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR FROM APPS.RCV_AEL_SL_MRC_V WHERE SET_OF_BOOKS_ID = :p_sob AND ORG_ID = :p_org AND TRANSACTION_DATE BETWEEN :p_from AND :p_to; Because the view is a static database object rather than a PL/SQL API, it carries no execution restrictions beyond standard APPS grants and organization security enforced through HR_SECURITY and related packages.