Search Results void_date

Overview

POS_AP_CHECKS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, catalogued under the Purchasing (PO) product family. It presents Accounts Payable payment records — specifically, checks and other payment documents held in AP_CHECKS_ALL — in a format tailored for Purchasing-side inquiry and integration flows. The view combines payment header attributes such as amount, check date, check number, currency, vendor, and vendor site with payment status flags and address information, and it resolves the operating unit name through a join to HR_ALL_ORGANIZATION_UNITS_TL. Its role is primarily read-only reporting: it feeds purchasing inquiry screens, supplier payment review, and downstream integrations that need a denormalized payment picture without navigating the full AP data model. The presence of the columns STOPPED_AT, RELEASED_AT, STOPPED, and CLEARED makes the view particularly relevant when a user searches for "stopped_at," since the payment stop/release lifecycle is exposed both as raw dates and as derived flags.

Underlying Base Objects

The documented base objects for this view are AP_CHECKS_ALL (synonym), AP_LOOKUP_CODES (view), FND_CURRENCY (package), FND_GLOBAL (package), HR_ALL_ORGANIZATION_UNITS_TL (synonym), and PO_VENDORS (view). The primary driver is AP_CHECKS_ALL, which supplies every payment-level column: amounts, dates, vendor and site identifiers, address fields, and the stop/release/clear/void attributes. HR_ALL_ORGANIZATION_UNITS_TL is joined on ORGANIZATION_ID = ORG_ID with the language restricted via USERENV('LANG') to return the operating unit name. The FND_CURRENCY package supplies currency formatting through SAFE_GET_FORMAT_MASK, applied to AC.AMOUNT to produce a locale-aware display value. FND_GLOBAL and the other referenced views provide supporting context used by the packaged function POS_AP_CHECKS_PKG.GET_INVOICES_PAID for the INVOICES column. Because the view reads directly from AP_CHECKS_ALL, its contents reflect the base AP payment table at query time; no materialization or snapshot is involved.

Key Columns

• STOPPED_AT — the date/time a payment was placed on stop, sourced directly from AP_CHECKS_ALL.STOPPED_AT.
• RELEASED_AT — the date/time a stopped payment was released.
• STOPPED — a derived flag. It returns '*' only when STOPPED_AT is populated and RELEASED_AT is empty, meaning the payment remains stopped; a released payment yields a blank.
• CLEARED / CLEARED_DATE — cleared flag and date; VOIDED / VOID_DATE — void flag and date.
• AMOUNT — the payment amount, formatted using the currency code via FND_CURRENCY.
• CHECK_ID, CHECK_NUMBER, CHECK_DATE, CURRENCY_CODE, BANK_ACCOUNT_NAME — core payment identity and cash-management attributes.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_SITE_CODE — supplier and supplier site linkage; PO_VENDORS supports the supplier view.
• ADDRESS and address component columns — CITY, STATE, PROVINCE, ZIP, COUNTRY, plus ADDRESS_URL and ADDRESS_STYLE.
• ORG_ID, ORG_NAME — operating unit identifier and its concatenated display name from HR_ALL_ORGANIZATION_UNITS_TL.
• INVOICES — result of POS_AP_CHECKS_PKG.GET_INVOICES_PAID(CHECK_ID), returning the invoices paid by the payment.

Common Use Cases and Queries

Typical use is to list currently stopped payments for a given operating unit, or to audit payment stop/release activity. The query below returns payments that are stopped and not yet released:

SELECT check_number, check_date, amount, currency_code, vendor_site_code, stopped_at, released_at, org_name
FROM apps.pos_ap_checks_v
WHERE stopped = '*'
AND org_id = :p_org_id
ORDER BY stopped_at DESC;

To review the history of a released stop, filter on RELEASED_AT rather than the derived flag. Because AMOUNT is pre-formatted and the operating unit name is resolved, the view suits concurrent-program extracts and Discoverer or OBIEE reports where downstream formatting logic is undesirable. Integrations that reconcile payment status into purchasing workflows can join on VENDOR_ID or CHECK_ID. When tracing the full payment lifecycle, pair STOPPED_AT and RELEASED_AT with CLEARED_DATE and VOID_DATE to determine the current disposition of each payment.