Search Results date_created_in_gl




Overview

RCV_MC_REC_SUB_LEDGER is an Oracle E-Business Suite table owned by the PO (Purchasing) schema. It is the Multiple Reporting Currencies (MRC) sub-table of RCV_RECEIVING_SUB_LEDGER, holding the accounting distribution lines — the subledger journal entries — generated from receiving transactions, replicated into each reporting set of books enabled in the MRC configuration. In standard EBS behavior, a base-row set is written to the primary subledger table and one corresponding row per additional reporting ledger is written to the shadow _MC_ table, keyed to the same transaction and identified by SET_OF_BOOKS_ID.

Because receiving distributions ultimately feed General Ledger through the Receiving Accounting program, this table is central to the Purchasing-to-Payables-to-GL accounting flow and to any reconciliation or audit of inventory and accrual postings originating in receiving.

From a Data Vault modeling standpoint, the metadata classifies this table heuristically as standalone. In Data Vault terms, a standalone table of this layout is best modeled as a satellite — a descriptive, attributed record keyed by the transaction/distribution identity — rather than a pure hub or link, since its business identity is inherited from the receiving transaction lineage rather than being a self-contained master entity.

Key Information Stored

The table contains 79 documented columns. The most significant are the following. The transactional and ledger anchors include RCV_TRANSACTION_ID (the receiving transaction that generated the distribution), SET_OF_BOOKS_ID (which reporting ledger this MRC row belongs to), and RCV_SUB_LEDGER_ID, which is the surrogate identifier for the subledger row. Business-key candidates are generally the transaction plus ledger combination, since a single receiving transaction produces one distribution per reporting set of books.

Standard audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the PROGRAM_/REQUEST_ID concurrency fields. ATTRIBUTE1 through ATTRIBUTE15 are the standard descriptive flexfield storage.

Common Use Cases and Queries

Typical uses include reconciling receiving accruals to GL, verifying MRC translation in multi-currency implementations, and investigating discrepancies between inventory and payable postings. A common query joins the base and MRC tables by transaction and ledger:

SELECT m.rcv_transaction_id, m.set_of_books_id, m.accounted_dr, m.accounted_cr FROM rcv_mc_rec_sub_ledger m WHERE m.rcv_transaction_id = :txn AND m.set_of_books_id = :sob;

Reporting patterns frequently aggregate by period and account to compare entered versus accounted amounts, or restrict to ACTUAL_FLAG = 'A'. Reconciliation teams also compare GL_SL_LINK_ID against GL_JE_LINES to confirm each distribution reached the ledger.

Related Objects