Results for “pobv_receiving_subledgers”

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

Overview

POBV_RECEIVING_SUBLEDGERS is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. Its ETRM documentation categorizes it as "Retrofitted," indicating that the object was carried forward or reconstructed during an upgrade or a product-line consolidation effort rather than being newly authored for the current release. It remains a VALID object in both Oracle EBS 12.1.1 and 12.2.2, where it functions as a reporting and integration surface over receiving subledger accounting data.

The view exposes receiving subledger journal information — accounting date, period, entered and accounted debit/credit amounts, currency conversion detail, journal header and batch attributes, and source document quantities — in a flattened, read-consistent form. Because the definition includes the clause WITH READ ONLY, the view is strictly a query object; no DML may be issued against it. This makes it suitable for extraction, reconciliation, and downstream reporting workloads that must not perturb subledger data.

The view also embeds descriptive flexfield display tokens. Columns such as ACTUAL_FLAG, REVERSE_JOURNAL_FLAG, and ACCRUAL_METHOD_FLAG are surfaced through lookup-based expressions (for example, mapping the YES/NO coded values against PO_LOOKUP_CODES), allowing a consumer to read decoded flag values alongside the underlying transactional columns.

Underlying Base Objects

The documented reference for POBV_RECEIVING_SUBLEDGERS is a single base object: RCV_RECEIVING_SUB_LEDGER, accessed through a synonym. The view is defined as a projection over that object, aliased SL in the view text, without joins to additional tables in the documented definition. All column mappings are direct or lightly transformed references to RCV_RECEIVING_SUB_LEDGER, including the flexfield lookup expressions that annotate coded columns. Because the relationship is a one-to-one projection, row cardinality and the view's filter characteristics are inherited from the subledger table itself.

Key Columns

• ACCOUNTING_DATE / ACCOUNTING_PERIOD_NAME — the GL accounting date and period to which the subledger entry belongs.
• ENTERED_DR / ENTERED_CR and ACCOUNTED_DR / ACCOUNTED_CR — transaction-currency and functional/base-currency debit and credit amounts respectively; the underlying view text maps these to ENTERED_DEBIT_AMOUNT, ENTERED_CREDIT_AMOUNT, BASE_CURRENCY_DEBIT_AMOUNT, and BASE_CURRENCY_CREDIT_AMOUNT.
• CURRENCY_CODE, FUNCTIONAL_CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE, USER_CURRENCY_CONVERSION_TYPE — currency and conversion metadata for the transaction.
• JE_CATEGORY_NAME, JE_SOURCE_NAME, JE_BATCH_NAME, JE_HEADER_NAME, JE_LINE_DESCRIPTION — journal identity attributes for tracing a subledger line back to its GL journal entry.
• GL_ACCOUNT_ID (CODE_COMBINATION_ID), CHART_OF_ACCOUNTS_ID, SET_OF_BOOKS_ID — accounting flexfield and ledger identification.
• BUDGET_VERSION_ID and ENCUMBRANCE_TYPE_ID — supporting attributes for budgetary and encumbrance reporting where applicable.
• SOURCE_DOCUMENT_QUANTITY — the quantity tied to the source receiving transaction.
• RECEIVING_TRANSACTION_ID (RCV_TRANSACTION_ID) — the link back to the originating receiving transaction.
• ENTERED_REC_TAX, ENTERED_NR_TAX, ACCOUNTED_REC_TAX, ACCOUNTED_NR_TAX — recoverable and non-recoverable tax amounts in entered and accounted currency.
• REVERSAL_PERIOD_NAME — the period into which a reversal was posted, where applicable.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical uses include reconciliation of receiving accruals to the general ledger, currency analysis of subledger activity, and extraction of journal detail for audit or data-warehouse loading. A basic period-scoped query is:

SELECT accounting_date, period_name, rcv_transaction_id, entered_dr, entered_cr, accounted_dr, accounted_cr, currency_code
FROM apps.pobv_receiving_subleggers
WHERE period_name = :period;


A reconciliation-oriented query aggregates by journal source and category:

SELECT je_source_name, je_category_name, SUM(accounted_dr) dr, SUM(accounted_cr) cr
FROM apps.pobv_receiving_subleggers
WHERE set_of_books_id = :sob
GROUP BY je_source_name, je_category_name;


Because the view is read-only, it can be queried safely from concurrent programs, BI Publisher data templates, and ad-hoc SQL sessions without risk of modifying subledger records.