Results for “jai_rcv_subled_entries”

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

Overview

JAI_RCV_SUBLED_ENTRIES is a localization table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is documented as a localization counterpart to the base Oracle Receiving application table RCV_SUB_LEDGER (referenced in the metadata as rcv_receiving_sub_ledger). Its purpose is to hold subledger accounting entry distributions generated from receiving transactions for the countries and legal requirements covered by the Asia/Pacific localizations, mirroring the structure and semantics of the standard receiving subledger data while isolating localized data in the JA schema.

Records in this table are keyed by SUBLED_ENTRY_ID and are anchored to a source receiving transaction through RCV_TRANSACTION_ID. Each row represents one balanced accounting distribution line — a debit or credit — associated with a receiving transaction, along with the full accounting context: ledger, chart of accounts, period, currency, conversion details, code combination, and journal metadata. This makes the table a source of subledger detail for localized receiving accounting, reporting, and reconciliation.

Under a heuristic Data Vault classification derived from the foreign key structure, the table behaves most like a link: it connects the receiving transaction to the chart of accounts, GL ledger, and code combination, while also carrying descriptive, time-stamped attributes. This is offered as a modeling suggestion only; the table is a normalized third-normal-form Oracle EBS object, not a Data Vault construct.

Key Information Stored

The table contains 69 columns. The most significant are:

• SUBLED_ENTRY_ID — the surrogate primary key (JAI_RCV_SUBLED_ENTRIES_PK) and the documented unique business-key candidate for the table.
• RCV_TRANSACTION_ID — foreign key to RCV_TRANSACTIONS; identifies the originating receiving transaction.
• SET_OF_BOOKS_ID — the ledger (GL_LEDGERS) against which the entry is recorded.
• CODE_COMBINATION_ID — the accounting flexfield combination (GL_CODE_COMBINATIONS) charged or credited.
• CHART_OF_ACCOUNTS_ID — chart of accounts context for the combination.
• ACCOUNTING_DATE and PERIOD_NAME — the accounting date and GL period to which the entry belongs.
• ACTUAL_FLAG — distinguishes actual balances from budget or encumbrance amounts.
• ACCOUNTED_DR / ACCOUNTED_CR — ledger-currency debit and credit amounts.
• ENTERED_DR / ENTERED_CR — transaction-currency debit and credit amounts.
• CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE, and USER_CURRENCY_CONVERSION_TYPE — currency context and conversion parameters.
• JE_SOURCE_NAME, JE_CATEGORY_NAME, JE_BATCH_NAME, and JE_LINE_DESCRIPTION — journal import metadata used to identify the subledger entry in GL.
• ENCUMBRANCE_TYPE_ID and BUDGET_VERSION_ID — encumbrance and budget context (GL_ENCUMBRANCE_TYPES, GL_BUDGET_VERSIONS).
• REFERENCE1 through REFERENCE10 — free-form reference columns, commonly storing source document numbers such as receipt or PO references.
• SOURCE_DOC_QUANTITY and FROM_TYPE — quantity and transaction-type context for the source document.
• REQUEST_ID, PROGRAM_ID, and PROGRAM_LOGIN_ID — concurrency and audit context for the program that created the row.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF/descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include reconciling localized receiving subledger entries to GL, tracing a receipt or PO transaction through to its accounting lines, reviewing currency conversion applied to receiving entries, and extracting period-close data for localized legal entities. The following pattern retrieves entries for a period with their ledger and transaction context:

• SELECT s.SUBLED_ENTRY_ID, s.RCV_TRANSACTION_ID, s.PERIOD_NAME, s.ACCOUNTED_DR, s.ACCOUNTED_CR, s.CURRENCY_CODE FROM JA.JAI_RCV_SUBLED_ENTRIES s WHERE s.PERIOD_NAME = :period AND s.SET_OF_BOOKS_ID = :ledger;
• SELECT s.SUBLED_ENTRY_ID, s.CODE_COMBINATION_ID, s.ACCOUNTED_DR, s.ACCOUNTED_CR FROM JA.JAI_RCV_SUBLED_ENTRIES s WHERE s.RCV_TRANSACTION_ID = :transaction_id;
• SELECT s.JE_SOURCE_NAME, s.JE_CATEGORY_NAME, COUNT(*), SUM(NVL(s.ACCOUNTED_DR,0) - NVL(s.ACCOUNTED_CR,0)) FROM JA.JAI_RCV_SUBLED_ENTRIES s GROUP BY s.JE_SOURCE_NAME, s.JE_CATEGORY_NAME;

Related Objects

The most significant objects linked through the documented foreign keys are:

• RCV_TRANSACTIONS — join on RCV_TRANSACTION_ID to obtain receipt header, item, and quantity context for each subledger entry.
• GL_CODE_COMBINATIONS — join on CODE_COMBINATION_ID to resolve accounting flexfield segment values.
• GL_LEDGERS — join on SET_OF_BOOKS_ID to identify the ledger and its functional currency.
• GL_ENCUMBRANCE_TYPES — join on ENCUMBRANCE_TYPE_ID for encumbrance classification.
• GL_BUDGET_VERSIONS — join on BUDGET_VERSION_ID for budget context.
• FND_CONCURRENT_REQUESTS — join on REQUEST_ID to identify the concurrent request that produced the rows.
• FND_CONCURRENT_PROGRAMS — join on PROGRAM_APPLICATION_ID and PROGRAM_ID to resolve the generating program.
• FND_LOGINS — join on PROGRAM_LOGIN_ID for session-level audit tracing.
• GL_MGT_SEG_UPGRADE_H — referenced via CHART_OF_ACCOUNTS_ID in the documented relationship set.

These relationships make the table a useful bridge between receiving transactions and the general ledger for localized accounting analysis and reconciliation reporting.