Search Results payment_status_flag




Overview
Explore in AI Chat

Overview

The AP_INVOICES_DERIVED_V view in the APPS schema is a Payables module construct that exposes invoice header information alongside a large set of derived, runtime-computed attributes. Unlike a conventional view that is defined purely over base tables, this view projects columns from AP_INVOICES and simultaneously invokes numerous PL/SQL functions resident in the AP_INVOICES_PKG package to derive status, hold, prepayment, and encumbrance indicators on a per-invoice basis. Its documented description in the ETRM metadata is explicitly marked "(Release 10SC Only)," indicating it originated in an early Payables release and has been retained in the 12.1.1 and 12.2.2 environments largely for backward compatibility with forms-based and custom code that referenced the derived-column naming convention.

The view plays a reporting and integration role: it consolidates values that would otherwise require multiple separate queries or function calls into a single, row-level projection. This makes it convenient for inquiry screens, custom reports, and interface programs that need a consolidated invoice status snapshot without directly invoking the underlying package APIs.

Underlying Base Objects

The documented referenced base objects are AP_INVOICES (exposed through a synonym), AP_INVOICES_PKG, AP_INVOICES_UTILITY_PKG, AP_UTILITIES_PKG, and FND_USER_AP_PKG. The view text shows AP_INVOICES as the driving table: columns such as INVOICE_AMOUNT, INVOICE_ID, INVOICE_TYPE_LOOKUP_CODE, PAYMENT_STATUS_FLAG, CANCELLED_BY, GL_DATE, VENDOR_ID, and ORG_ID are selected directly. All remaining columns are computed through function calls against AP_INVOICES_PKG (for example GET_ENCUMBERED_FLAG, GET_POSTING_STATUS, GET_APPROVAL_STATUS, GET_PO_NUMBER, GET_HOLDS_COUNT, GET_AMOUNT_WITHHELD, GET_TOTAL_PREPAYS, GET_AVAILABLE_PREPAYS). Period naming is resolved through AP_UTILITIES_PKG.GET_GL_PERIOD_NAME. Because each derived column invokes a PL/SQL function, the view is not a simple join; its performance profile is dominated by per-row function execution, and it should be queried with selective predicates on AP_INVOICES columns to limit the row set processed.

Key Columns

Common Use Cases and Queries

A frequent scenario is identifying encumbered invoices. Because the ENCUMBERED_FLAG is derived by a function, a predicate directly on it forces evaluation across rows; filtering first on AP_INVOICES columns narrows the workload:

  • SELECT invoice_id, invoice_amount, encumbered_flag FROM ap_invoices_derived_v WHERE gl_date BETWEEN :p_from AND :p_to AND encumbered_flag = 'Y';
  • SELECT invoice_id, approval_status_lookup_code, posting_flag, holds_count FROM ap_invoices_derived_v WHERE invoice_id = :p_invoice_id;
  • SELECT invoice_id, po_number, total_prepays, available_prepays FROM ap_invoices_derived_v WHERE vendor_id = :p_vendor_id;

These patterns support inquiry screens, reconciliation reports, and interface extraction where a consolidated, derived invoice snapshot is required. Given the "(Release 10SC Only)" documentation note, implementers on 12.1.1 and 12.2.2 should treat the view as a compatibility object and validate behavior against the current AP_INVOICES_PKG signatures before relying on it in new customizations.