Search Results amount_currency_code

Overview

AP_CHECKS_WWW_V is a Payables module view that presents payment (check) information in a format suitable for web-based inquiry and reporting. The ETRM metadata identifies this object as a view owned within the AP - Payables product, and the documentation excerpt explicitly notes "(Release 10SC only)." This attribution is significant: the view was introduced to support the self-service, web-facing presentation of payment records and was catalogued during the 10SC release cycle of the E-Business Suite. The ETRM entry further records that the object is "Not implemented in this database," meaning that in the environment from which the metadata was harvested it does not exist as a deployed database object. In Oracle EBS 12.1.1 and 12.2.2, therefore, this view should be treated as a legacy or documentation-only artifact rather than a guaranteed component of the standard AP schema. Where it does exist, it functions as a lightweight, denormalized read layer over AP_CHECKS, tailored for display rather than transactional processing.

Underlying Base Objects

The view text is defined entirely over a single base table, AP_CHECKS, aliased as AC. No other base tables are referenced in the SELECT list; the only additional dependency is a function call to AP_CHECKS_PKG.GET_INVOICES_PAID, which retrieves the concatenated invoice information associated with a given check. The ETRM metadata records "Referenced base objects: none documented," which is consistent with the excerpt's presentation as a view text listing rather than a formal dependency extract. All columns are projected directly from AP_CHECKS, with one derived expression combining amount and currency code, and three DECODE-based flag columns derived from date fields. This single-table lineage distinguishes AP_CHECKS_WWW_V from more complex payment views that join to supplier sites, banks, or invoice distributions. The view is read-only and carries no DML semantics.

Key Columns

• CHECK_ID — Primary identifier of the payment, inherited from AP_CHECKS; used as the key passed to GET_INVOICES_PAID.
• CHECK_NUMBER / CHECK_DATE — The payment document number and its accounting date.
• AMOUNT and AMOUNT_CURRENCY_CODE — The payment amount, plus a concatenated display string of amount and currency for presentation.
• CURRENCY_CODE — The payment currency.
• RELEASED_DATE — The date on which a stopped payment was released; central to the STOPPED flag logic requested by the user.
• CLEARED, VOIDED, STOPPED — Status flags derived via DECODE: CLEARED_DATE and VOID_DATE yield '*' when populated; STOPPED yields '*' when a stop date exists but no release date exists, and is blank once RELEASED_DATE is populated.
• CLEARED_DATE, VOID_DATE, STOPPED_DATE, FUTURE_PAY_DUE_DATE — Raw date columns retained for reporting and sorting.
• BANK_ACCOUNT_NAME, VENDOR_SITE_CODE, VENDOR_SITE_ID, VENDOR_ID — Disbursement and supplier identification attributes.
• ADDRESS, ADDRESS_LINE1–4, CITY, COUNTY, STATE, PROVINCE, ZIP, COUNTRY, ADDRESS_STYLE — Supplier remittance address components, with CITY and STATE concatenated into ADDRESS.
• INVOICES — Function-generated list of invoices paid by the check.

Common Use Cases and Queries

The view supports payment inquiry screens and ad hoc reporting where a flat, display-ready row per check is required. A typical query filtering on payment status and release information is shown below.

SELECT CHECK_NUMBER, CHECK_DATE, AMOUNT_CURRENCY_CODE, STOPPED, STOPPED_DATE, RELEASED_DATE FROM AP_CHECKS_WWW_V WHERE RELEASED_DATE IS NOT NULL;

For voided or cleared payment analysis: SELECT CHECK_ID, VENDOR_SITE_CODE, CLEARED_DATE, VOIDED FROM AP_CHECKS_WWW_V WHERE CLEARED = '*' OR VOIDED = '*';

Because the view is documented as Release 10SC only and not implemented in the referenced database, consumers on 12.1.1 or 12.2.2 should verify its existence in the target schema and, where absent, substitute equivalent queries against AP_CHECKS directly or the supported payment inquiry views.