Search Results selected_for_payment_flag

Overview

AP_INVOICES_V is a VALID view owned by the APPS schema in Oracle E-Business Suite, listed under the FND – Application Object Library product grouping. It presents a denormalized, reporting-friendly projection of supplier invoice data drawn primarily from AP_INVOICES_ALL, enriched with lookups, descriptive flexfields, and derived attributes resolved through PL/SQL package calls. The view exhibits a ROWID-based ROW_ID column, which is the signature of an OAF/BC4J "entity view" — a view constructed so that Oracle Application Framework pages and other EBS UI layers can address individual invoice rows for update and navigation. Because it joins human-readable values (currency names, payment terms, vendor names, approval descriptions, payment method text) onto core invoice columns, AP_INVOICES_V is widely used in reports, form LOVs, and integration extracts rather than in transactional write paths.

Underlying Base Objects

The documented ETRM metadata lists an extensive base object dependency set. The central table is AP_INVOICES_ALL (SYNONYM), which supplies the invoice header columns; supporting AP objects include AP_BATCHES_ALL, AP_AWT_GROUPS, AP_DISTRIBUTION_SETS, AP_OTHER_PERIOD_TYPES, AP_RECURRING_PAYMENTS_ALL, AP_SYSTEM_PARAMETERS, and AP_TERMS. Lookup decoding comes through AP_LOOKUP_CODES (VIEW) and FND_LOOKUPS (VIEW), while FND_CURRENCIES, GL_DAILY_CONVERSION_TYPES, and GL_SETS_OF_BOOKS supply currency, rate type, and ledger context. Vendor and party data arrive via PO_VENDORS, PO_VENDOR_SITES_ALL, HZ_PARTIES, and PO_HEADERS; payment attributes come from IBY_PAYMENT_METHODS_VL, IBY_PAYMENT_REASONS_VL, IBY_DELIVERY_CHANNELS_VL, and IBY_EXT_BANK_ACCOUNTS. Payables and Oracle Projects logic is invoked through AP_INVOICES_PKG, AP_INVOICES_UTILITY_PKG, AP_PREPAY_UTILS_PKG, FND_USER_AP_PKG, HR_GENERAL, HR_SECURITY, FND_GLOBAL, and FND_PROFILE, plus PA_PROJECTS_ALL, PA_TASKS_EXPEND_V, PA_TASK_UTILS, and PA_UTILS4. Because the view calls these packages, many derived columns are computed at query time rather than stored.

Key Columns

• INVOICE_ID / INVOICE_NUM / INVOICE_DATE — Primary identifier, supplier-facing invoice number, and invoice date.
• APPROVAL_DESCRIPTION — The approval-status description text exposed on invoice headers; this is the column most commonly sought when troubleshooting approval workflow state.
• APPROVED_AMOUNT / INVOICE_AMOUNT / BASE_AMOUNT — Entered invoice amount, functional (base) amount, and amount released through approval.
• AMOUNT_PAID / AMOUNT_APPLICABLE_TO_DISCOUNT / DISCOUNT_AMOUNT_TAKEN / CANCELLED_AMOUNT — Payment, discount, and cancellation monetary attributes.
• AUTHORIZED_BY, CANCELLED_BY, CANCELLED_DATE — Workflow authorization and cancellation audit columns, resolved to user names.
• DOC_CATEGORY_CODE, DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE — Document sequencing attributes for statutory voucher numbering.
• EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, INVOICE_CURRENCY_CODE — Currency conversion context.
• BATCH_ID, AWT_FLAG, AWT_GROUP_ID, EARLIEST_SETTLEMENT_DATE, EXCLUSIVE_PAYMENT_FLAG — Batch grouping and withholding-tax attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns surfaced on the view.
• EXPENDITURE_ITEM_DATE, EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, GOODS_RECEIVED_DATE — Projects and receiving context.

Common Use Cases and Queries

Typical scenarios include invoice approval-status reporting, open-item and outstanding-payables extracts, and descriptive flexfield analysis. Because the view resolves user IDs to names and calls AP/HR/PA packages, queries can be slower than direct AP_INVOICES_ALL reads, so filtering by INVOICE_ID, INVOICE_NUM, or date range is recommended.

Find invoices in a given approval state:

• SELECT invoice_id, invoice_num, invoice_date, approval_description, approved_amount, invoice_amount FROM ap_invoices_v WHERE approval_description = :p_status AND invoice_date BETWEEN :p_from AND :p_to;

Retrieve a single invoice header for a form or interface, including payment and currency context:

• SELECT invoice_num, approval_description, invoice_currency_code, exchange_rate, exchange_rate_type, payment_method_lookup_code, terms_name FROM ap_invoices_v WHERE invoice_id = :p_invoice_id;

Read descriptive flexfield segments alongside approval information for reporting:

• SELECT invoice_num, attribute_category, attribute1, attribute2, approval_description FROM ap_invoices_v WHERE attribute_category IS NOT NULL AND org_id = :p_org_id;