Results for “invoice_due_date”

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

Overview

APPS.POS_PO_SUP_ORDER_INVOICES_V is a Purchasing (PO) module view in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name reflects its purpose: it presents supplier (vendor) invoice information related to purchase orders, drawing invoice data from Payables and linking it back to Purchasing distributions. Rather than exposing raw foreign keys alone, the view assembles a reporting-ready, denormalized projection in which monetary values are pre-formatted and descriptive attributes are resolved through lookup and packaged function calls. It is therefore intended primarily for read-only reporting, inquiry screens, and integration scenarios where a concise, queryable representation of PO-referenced supplier invoices is required. The view is owned by the APPS schema and is documented as VALID.

Underlying Base Objects

The view is defined over several underlying objects, joining Payables and Purchasing data. The documented base objects are:

• AP_INVOICES_ALL (synonym) — the invoice header, aliased AI; supplies amount, currency, date, number, vendor, and status attributes.
• AP_PAYMENT_SCHEDULES_ALL (synonym) — aliased APS; supplies due date, gross amount, amount remaining, discount date, and discount amount available.
• AP_INVOICE_DISTRIBUTIONS_ALL (synonym) — aliased AID; the join bridge to PO distributions via PO_DISTRIBUTION_ID.
• PO_DISTRIBUTIONS_ALL (synonym) — aliased POD; provides the PO_HEADER_ID and PO_RELEASE_ID linkage.
• PO_VENDORS (view, aliased PV) and PO_VENDOR_SITES_ALL (view, aliased PVS) — resolve vendor and vendor site identity, including PVS.VENDOR_SITE_CODE.
• AP_LOOKUP_CODES (view) — joined twice with outer-join syntax (ALC1, ALC2) to translate INVOICE_TYPE_LOOKUP_CODE and PAYMENT_STATUS_FLAG into displayed values.
• FND_CURRENCY and FND_GLOBAL (packages) — used for currency format mask resolution.
• POS_AP_INVOICES_PKG and POS_AP_INVOICE_PAYMENTS_PKG (packages) — supply derived columns through PL/SQL functions.

The joins are inner joins for the core invoice, schedule, distribution, vendor, and site relationships, with the lookup joins expressed as outer joins.

Key Columns

The view projects a focused set of columns, many of which are already formatted as character strings:

• DESCRIPTION — invoice description from AP_INVOICES_ALL.
• INVOICE_AMOUNT — formatted invoice amount, produced via FND_CURRENCY.SAFE_GET_FORMAT_MASK.
• INVOICE_CURRENCY_CODE — the invoice currency.
• WITHHELD_AMOUNT_CURRENCY_CODE — withheld amount concatenated with currency code, returned by POS_AP_INVOICES_PKG.GET_AMOUNT_WITHHELD.
• INVOICE_DATE, INVOICE_ID, INVOICE_NUM — core invoice identifiers and dates.
• INVOICE_DUE_DATE, GROSS_AMOUNT, AMOUNT_REMAINING, DISCOUNT_DATE, DISCOUNT_AMOUNT_AVAILABLE — payment schedule attributes, amounts formatted as strings.
• INVOICE_TYPE, PAYMENT_STATUS — resolved lookup display fields.
• PO_NUMBER — derived via POS_AP_INVOICES_PKG.GET_PO_NUMBER_LIST.
• PAYMENT_NUMBER — derived via POS_AP_INVOICE_PAYMENTS_PKG.GET_PAID_BY_LIST, using APS.PAYMENT_NUM.
• VENDOR_SITE_CODE, VENDOR_SITE_ID, VENDOR_ID, EMPLOYEE_ID — supplier party and site identity.
• PO_HEADER_ID, PO_RELEASE_ID — the Purchasing document references.

Common Use Cases and Queries

The view is typically queried to list supplier invoices tied to purchase orders, showing amounts, payment status, and vendor site. Because amounts are already formatted, it suits inquiry and reporting output. A representative query filters by vendor or PO:

SELECT invoice_num, invoice_date, invoice_currency_code,
       invoice_amount, amount_remaining, payment_status,
       po_number, vendor_site_code
FROM   apps.pos_po_sup_order_invoices_v
WHERE  vendor_id = :p_vendor_id
ORDER  BY invoice_date DESC;

Another common pattern joins the view back to PO headers using PO_HEADER_ID to reconcile invoices against specific purchasing documents. Caution is warranted: the view calls PL/SQL package functions (GET_AMOUNT_WITHHELD, GET_PO_NUMBER_LIST, GET_PAID_BY_LIST) per row, so large unbounded extracts can be costly. Its DISTINCT and function-based columns also mean it is optimized for read-only reporting, not for transactional update or DML.