Search Results amount_encumbered

Overview

The AP_INVOICE_DISTS_MRC_V view belongs to the Oracle Payables (AP) module and is classified in the ETRM metadata as a "SINGLE-ORG MRC view." MRC, or Multiple Reporting Currencies, is an Oracle E-Business Suite feature that permits an operating unit to maintain and report accounting data in a primary functional currency alongside one or more additional reporting currencies. Views bearing the _MRC_V suffix exist to expose invoice distribution information converted into each reporting set of books, and AP_INVOICE_DISTS_MRC_V performs this role for payables invoice distributions.

The view is not implemented in the reference database recorded by ETRM, meaning it exists as a defined view object within the application schema but carries no materialized rows in that specific environment. It is documented as a single-org view, so its results are scoped to a single operating unit's data rather than returning cross-organization results. Application code, reporting, and integration layers rely on this view to reconcile distribution-level accounting between the primary and reporting sets of books.

Underlying Base Objects

The ETRM metadata records no referenced base objects for this view, and the documented implementation status is "Not implemented in this database." The view text nevertheless reveals a composite construction: the majority of distribution attributes are drawn from the base AP invoice distribution table aliased as B, while converted, reporting-currency-specific amounts are drawn from a set of books view aliased as MC. The MC alias supplies the currency-translated figures such as DISTRIBUTION_LINE_NUMBER, DIST_CODE_COMBINATION_ID, SET_OF_BOOKS_ID, AMOUNT, BASE_AMOUNT, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, AMOUNT_TO_POST, BASE_AMOUNT_TO_POST, POSTED_AMOUNT, and POSTED_BASE_AMOUNT.

Because the base-object list is not documented, practitioners should confirm the definitive dependencies at runtime using ALL_DEPENDENCIES or DBMS_METADATA.GET_DDL rather than assuming a fixed table list from the metadata alone.

Key Columns

• INVOICE_ID, DISTRIBUTION_LINE_NUMBER, LINE_TYPE_LOOKUP_CODE — identify the parent invoice and the individual distribution line and its type.
• ACCOUNTING_DATE, PERIOD_NAME, ACCOUNTING_EVENT_ID — drive accounting-period reporting and event reconciliation.
• SET_OF_BOOKS_ID — distinguishes the primary set of books from each reporting set of books, the defining characteristic of an MRC view.
• AMOUNT, BASE_AMOUNT — the entered and functional-currency distribution amounts.
• AMOUNT_ENCUMBERED, BASE_AMOUNT_ENCUMBERED, ENCUMBERED_FLAG, QUANTITY_UNENCUMBERED — the encumbrance columns directly relevant to the searched term "amount_encumbered," exposing the amount reserved against funds in entered and base currency, whether the line is encumbered, and the quantity still unencumbered.
• POSTED_FLAG, ACCRUAL_POSTED_FLAG, CASH_POSTED_FLAG, POSTED_AMOUNT, POSTED_BASE_AMOUNT — posting status and posted values.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE — currency translation parameters per reporting book.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield context and values.

Common Use Cases and Queries

A frequent requirement is reporting encumbered invoice distribution amounts by set of books to support budgetary controls and funds checking. For example:

• SELECT INVOICE_ID, DISTRIBUTION_LINE_NUMBER, SET_OF_BOOKS_ID, AMOUNT_ENCUMBERED, BASE_AMOUNT_ENCUMBERED FROM AP_INVOICE_DISTS_MRC_V WHERE ENCUMBERED_FLAG = 'Y';
• Comparing primary and reporting book amounts: filter on SET_OF_BOOKS_ID and compare AMOUNT against BASE_AMOUNT for variance analysis.
• Reconciling posted versus unposted distributions using POSTED_FLAG combined with POSTED_AMOUNT.
• Joining the view to AP_INVOICES_ALL on INVOICE_ID for supplier and invoice-level context.

Because the view is single-org and not implemented in all databases, always confirm availability before deployment.