Results for “ap_encumbrance_lines_v”

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

Overview

The APPS.AP_ENCUMBRANCE_LINES_V view is a Payables reporting object that consolidates encumbrance accounting activity generated against supplier invoices and their distributions. Encumbrance accounting records commitments and obligations against budget resources; within Oracle Payables, encumbrance entries arise when invoices are validated and create accountable pairs of debit and credit lines that reduce available funds. This view joins the transactional encumbrance lines to the source invoice and distribution context, and decorates each row with descriptive encumbrance type and line type information.

The view is a read-only presentation layer. It exposes the internally stored ACCOUNTED_DR and ACCOUNTED_CR amounts under the aliases DEBIT_AMOUNT and CREDIT_AMOUNT, which is the column users most often search for. Because it resolves foreign keys to invoice, distribution, encumbrance type, and lookup descriptions, it is suitable for ad hoc inquiry, reconciliation extracts, custom reports, and interface programs that feed downstream budgeting or audit systems. In EBS 12.1.1 and 12.2.2 the view remains VALID and is owned by APPS; no separate database object replacement was introduced between these releases.

Underlying Base Objects

The documented from-list comprises five referenced objects:

• AP_ENCUMBRANCE_LINES (synonym) — the driving base table, aliased AELA. It supplies the line identifier, code combination, accounted amounts, period, accounting date, reversal flag, encumbrance type, line type, and invoice distribution reference.
• AP_INVOICE_DISTRIBUTIONS (synonym) — aliased AID, joined on INVOICE_DISTRIBUTION_ID, supplying the distribution line number and description.
• AP_INVOICES (synonym) — aliased AI, joined through the distribution on INVOICE_ID, supplying invoice number and invoice identifier.
• GL_ENCUMBRANCE_TYPES (synonym) — aliased GET, joined on ENCUMBRANCE_TYPE_ID, supplying the encumbrance type name.
• AP_LOOKUP_CODES (view) — aliased ALC, joined on LOOKUP_CODE where LOOKUP_TYPE = 'AE LINE TYPE', supplying the displayed line type.

The metadata also lists FND_GLOBAL (package) among referenced objects, consistent with the standard APPS view pattern in which PL/SQL is invoked for multi-org or security context. The view text itself does not reference FND_GLOBAL directly in the excerpt, so its invocation may be indirect or version-dependent.

Key Columns

• DEBIT_AMOUNT (ACCOUNTED_DR) — the accounted debit amount for the encumbrance line; the principal search target for this view.
• CREDIT_AMOUNT (ACCOUNTED_CR) — the corresponding accounted credit amount.
• ENCUMBRANCE_LINE_ID / ROW_ID — unique line identifier and row address, useful for de-duplication or direct table access.
• ENCUMBRANCE_TYPE — descriptive encumbrance type from GL_ENCUMBRANCE_TYPES.
• LINE_TYPE — displayed value of the AE LINE TYPE lookup, distinguishing encumbrance from reversal or relief lines.
• CODE_COMBINATION_ID — the accounting flexfield combination charged by the encumbrance.
• PERIOD / ACCOUNTING_DATE — the accounting period name and the date on which the entry was accounted; essential for period-based reconciliation.
• REVERSAL — flag indicating whether the line represents a reversal.
• INVOICE_ID / INVOICE_NUM / INVOICE_DISTRIBUTION_ID / DIST_LINE_NUM / DIST_DESC — the source invoice and distribution context, enabling drill-down from encumbrance to invoice.

Common Use Cases and Queries

Typical uses include reconciliation of invoice-driven encumbrances by period, audit extracts, and integration feeds. A representative query retrieves debits and credits by invoice:

• SELECT invoice_num, distribution_line_number, debit_amount, credit_amount FROM ap_encumbrance_lines_v WHERE invoice_num = :p_invoice;
• SELECT period, encumbrance_type, SUM(debit_amount - credit_amount) FROM ap_encumbrance_lines_v GROUP BY period, encumbrance_type;

Because the view performs several joins, performance improves when queries filter on indexed keys such as INVOICE_ID, CODE_COMBINATION_ID, or PERIOD. For high-volume extracts, joining directly to the base tables is preferable to scanning the view unfiltered.