Search Results withheld_amount_currency_code

Overview

AP_INVOICES_WWW_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Payables (AP). The ETRM metadata explicitly flags this object as "(Release 10SC Only)," indicating it was introduced during the Oracle Applications 10SC release cycle to support web-based (WWW) or self-service invoice inquiry functionality. It has been carried forward as a valid object in the 12.1.1 and 12.2.2 data models, but its design lineage reflects the simplified, self-service-oriented HTML interfaces of that era.

The view presents a flattened, human-readable projection of invoice header data joined with payment schedule details, lookup-code descriptions, and vendor site information. Its primary role is to expose invoice amounts in a display-ready format — most notably by concatenating numeric amounts with their currency codes, and by resolving lookup codes into descriptive text for invoice type and payment status. Because it references read-only base objects and packaged APIs, it is intended strictly for querying and reporting, never for DML. The presence of the DISCOUNT_DATE column makes the view relevant to users and developers investigating early-payment discount eligibility and discount-date questioning, a recurring search topic in AP reporting.

Underlying Base Objects

The view text joins five primary sources and invokes two Payables PL/SQL packages. Its documented referenced objects are AP_INVOICES (SYNONYM), AP_PAYMENT_SCHEDULES (SYNONYM), AP_LOOKUP_CODES (VIEW), PO_VENDOR_SITES (VIEW), AP_INVOICES_PKG (PACKAGE), AP_INVOICE_PAYMENTS_PKG (PACKAGE), and FND_GLOBAL (PACKAGE).

• AP_INVOICES — supplies invoice header attributes: description, amount, currency code, invoice date, invoice number, vendor and vendor site identifiers, and the invoice type and payment status lookup codes.
• AP_PAYMENT_SCHEDULES — supplies scheduled payment data including due date, gross amount, amount remaining, discount date, and discount amount available.
• AP_LOOKUP_CODES — joined with outer-join syntax for the 'INVOICE TYPE' and 'INVOICE PAYMENT STATUS' lookup types to translate codes into displayed field text.
• PO_VENDOR_SITES — provides the vendor site code for the invoice's vendor site.
• AP_INVOICES_PKG — its GET_AMOUNT_WITHHELD and GET_PO_NUMBER_LIST functions populate the withheld amount and purchase order number columns.
• AP_INVOICE_PAYMENTS_PKG — its GET_PAID_BY_LIST function supplies the payment number / paid-by list, keyed by invoice and payment number.
• FND_GLOBAL — referenced for session context (for example, organization or user context) used by the underlying packages.

The join between AP_INVOICES and AP_PAYMENT_SCHEDULES is on INVOICE_ID, so a single invoice with multiple scheduled payments may produce multiple rows.

Key Columns

• DISCOUNT_DATE — the date by which payment must be made to qualify for a supplier discount; sourced from AP_PAYMENT_SCHEDULES and central to early-payment analysis.
• DISCOUNT_AMOUNT_AVAILABLE — the discount amount still available on the scheduled payment.
• INVOICE_AMOUNT / INVOICE_AMOUNT_CURRENCY_CODE — the raw invoice amount and its concatenated display form (amount plus currency code).
• WITHHELD_AMOUNT_CURRENCY_CODE — the withheld amount, resolved via AP_INVOICES_PKG, formatted with the currency code.
• DUE_DATE, GROSS_AMOUNT, AMOUNT_REMAINING — payment schedule terms.
• INVOICE_TYPE / PAYMENT_STATUS — descriptive lookup text rather than raw codes.
• PO_NUMBER, PAYMENT_NUMBER — derived via package functions for display.
• VENDOR_SITE_CODE, VENDOR_SITE_ID, VENDOR_ID — vendor identification attributes.
• INVOICE_ID, INVOICE_NUM, INVOICE_DATE, DESCRIPTION — core invoice header identifiers.

Common Use Cases and Queries

Typical uses include web-style invoice inquiry, supplier-facing discount-date reporting, and quick invoice status listings that require formatted amounts and descriptive lookup text. A representative query listing invoices approaching their discount date is:

SELECT invoice_num, vendor_site_code, invoice_amount_currency_code, discount_date, discount_amount_available, due_date, payment_status FROM apps.ap_invoices_www_v WHERE discount_date BETWEEN SYSDATE AND SYSDATE + 7 ORDER BY discount_date;

For a single invoice with its payment schedule detail:

SELECT invoice_num, due_date, gross_amount, amount_remaining, discount_date, po_number, payment_number FROM apps.ap_invoices_www_v WHERE invoice_id = :p_invoice_id;

Because the view calls PL/SQL functions per row, queries against large invoice populations can be resource-intensive; filtering by invoice_id, vendor_id, or a narrow discount_date range is recommended. Note also the outer joins on AP_LOOKUP_CODES: descriptions may be null where no lookup row exists.