Results for “rcv_sub_ledger_details”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RCV_SUB_LEDGER_DETAILS is a subledger accounting table owned by the PO (Purchasing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the detailed accounting distribution lines generated for receiving transactions processed through the Receiving (RCV) module. When goods are received against a purchase order, the receiving transaction must be accounted for in the general ledger. RCV_SUB_LEDGER_DETAILS captures the intermediate subledger journal entries—the debit and credit amounts, the accounts affected, the currency conversions, and the linkage back to the originating receipt transaction—before those entries are transferred to Oracle General Ledger via the Create Accounting process. In this sense it functions as the accounting repository for the PO/RCV subledger, complementing the transactional data held in RCV_TRANSACTIONS.

The ETRM Data Vault heuristic classifies this table as standalone, meaning no strong hub/link/satellite pattern is inferred from its foreign-key density. This should be treated as a modeling suggestion only; in practice the table behaves much like a satellite of receiving transaction events, since each row is anchored to a specific RCV_TRANSACTION_ID and an accounting period.

Key Information Stored

The documented schema contains 75 columns. The most architecturally significant ones are listed below. Note that the surrogate/business key for a row is RCV_SL_DETAILS_ID, which uniquely identifies each subledger accounting detail line.

• RCV_SL_DETAILS_ID — Surrogate primary key identifying each accounting detail row.
• RCV_TRANSACTION_ID — Foreign linkage to the originating receiving transaction; the principal business-key candidate.
• PO_LINE_LOCATION_ID — The purchase order shipment/distribution to which the receipt relates.
• CODE_COMBINATION_ID — The GL account combination charged or credited (a candidate business-key element alongside the transaction).
• ACCOUNTED_DR / ACCOUNTED_CR — Debit and credit amounts in the ledger's functional currency.
• ENTERED_DR / ENTERED_CR — The equivalent amounts in the entered (transaction) currency.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — Currency and conversion information for foreign-currency receipts.
• ACTUAL_FLAG, JE_SOURCE_NAME, JE_CATEGORY_NAME — Accounting class attributes that drive GL journal creation.
• SET_OF_BOOKS_ID, CHART_OF_ACCOUNTS_ID — Ledger and chart-of-accounts context.
• PERIOD_NAME, ACCOUNTING_DATE, TRANSACTION_DATE — Period and date attributes used for period-based reporting and cutoff analysis.
• PERIOD_NAME and GL_SL_LINK_ID — The latter links the subledger line to its generated GL entry after transfer.
• ACCRUAL_METHOD_FLAG — Indicates accrual versus non-accrual accounting treatment.
• SOURCE_DOC_QUANTITY — Quantity associated with the accounting line.
• ENTERED_REC_TAX / ENTERED_NR_TAX / ACCOUNTED_REC_TAX / ACCOUNTED_NR_TAX — Recoverable and non-recoverable tax amounts in entered and accounted currencies.

Common Use Cases and Queries

The table is used primarily for subledger accounting reconciliation, period-close validation, and accrual reporting. Typical queries join RCV_SUB_LEDGER_DETAILS to RCV_TRANSACTIONS to trace an accounting line back to its receipt event.

• Reconciling receiving accruals to the GL by joining on GL_SL_LINK_ID and SET_OF_BOOKS_ID.
• Reviewing debit/credit balances by account: SELECT CODE_COMBINATION_ID, SUM(ACCOUNTED_DR), SUM(ACCOUNTED_CR) FROM RCV_SUB_LEDGER_DETAILS WHERE PERIOD_NAME = :p GROUP BY CODE_COMBINATION_ID;
• Auditing unposted subledger lines by filtering on a NULL GL_SL_LINK_ID or a missing DATE_CREATED_IN_GL.
• Analyzing tax components (ENTERED_REC_TAX, ACCOUNTED_NR_TAX) for tax reporting and recoverability reviews.
• Period-close analysis restricted by PERIOD_NAME to confirm the completeness of receipt accounting before closing.

Related Objects

• GL_ENCUMBRANCE_TYPES — joined via ENCUMBRANCE_TYPE_ID for encumbrance accounting lines.
• GL_MGT_SEG_UPGRADE_H — joined via CHART_OF_ACCOUNTS_ID for chart-of-accounts mapping.
• RCV_TRANSACTIONS — parent receipt transaction table; join on RCV_TRANSACTION_ID.
• RCV_SUB_LEDGER_DETAILS is itself linked to RCV_SL_DETAILS_ID subledger detail records, forming the accounting header/detail relationship.
• GL_JE_LINES / GL_IMPORT_REFERENCES — the GL-side destination for transferred entries, located via GL_SL_LINK_ID.
• PO_LINE_LOCATIONS_ALL — join on PO_LINE_LOCATION_ID to obtain shipment and distribution context.
• GL_CODE_COMBINATIONS — join on CODE_COMBINATION_ID to resolve account descriptions.