Search Results stop_payment_recorded_date




Overview
Explore in AI Chat

Overview

APBV_AP_PAYMENTS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, identified internally by the FND Design Data name SQLAP.APBV_AP_PAYMENTS. Its status is VALID, and it is defined with a View Type A classification, meaning it is purpose-built for business intelligence and reporting consumption rather than for transactional processing. The view presents payment records, described in the documentation as disbursements issued to a supplier. It is one of the APBV (Accounts Payable Business View) family of objects that abstract the underlying Oracle Payables payment tables into a denormalized, read-only presentation layer suitable for ad hoc queries, Discoverer workbooks, and downstream reporting integrations. Because it is a view and not a table, it carries no storage of its own; all data is projected from its referenced base objects, and any change to underlying payment records is immediately reflected.

The user's search term, "stop_payment_recorded_date," maps directly to a column on this view. In Oracle Payables, stopping a payment is the act of instructing the system not to issue a disbursement; when that stop instruction is recorded and later released, the system captures the date and user who performed each action. This view exposes those audit values as STOP_PAYMENT_RECORDED_DATE, STOP_PAYMENT_RECORDED_USER_ID, STOP_PAYMENT_RELEASED_DATE, and STOP_PAYMENT_RELEASED_USER_ID.

Underlying Base Objects

The documented view metadata for 12.2.2 records AP_CHECKS (accessed through a synonym) as the sole referenced base object. This is consistent with the Payables data model, where AP_CHECKS is the principal table storing payment and check records; the APBV_AP_PAYMENTS view selects and projects the relevant payment attributes from that table, joining or resolving user identifiers and lookup meanings where required to produce a business-friendly result set.

No additional base tables are documented in the ETRM metadata. Reporting built against this view should therefore be understood as reflecting the payment header level of AP_CHECKS rather than invoice or distribution detail, which resides in other Payables objects.

Key Columns

Common Use Cases and Queries

Typical use cases include payment register reporting, stop-payment and void tracking, bank clearing analysis, and supplier disbursement audits.

To identify payments with a recorded stop payment in a period:

SELECT payment_document_number, payment_document_date, amount, stop_payment_recorded_date, stop_payment_recorded_user_id FROM apps.apbv_ap_payments WHERE stop_payment_recorded_date IS NOT NULL;

To list outstanding stops that have not been released:

SELECT payment_document_number, payment_status, stop_payment_recorded_date FROM apps.apbv_ap_payments WHERE stop_payment_recorded_date IS NOT NULL AND stop_payment_released_date IS NULL;

Because STOP_PAYMENT_RECORDED_DATE is stored as a character column, date-range filtering requires an explicit conversion, for example WHERE TO_DATE(stop_payment_recorded_date,'YYYY/MM/DD HH24:MI:SS') BETWEEN :from_date AND :to_date. Queries should be run against the APPS schema, and because this is a BIS view, it is intended for query and reporting only, never for direct DML.