Search Results payment_sequence_number

Overview

APBV_AP_PAYMENTS is a business (BV) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Payables (AP) product family and presents payment information maintained in the Oracle Payables module. The view is documented as VALID in the ETRM repository. Its primary design objective is to expose a business-friendly projection of the payment record, mapping internal column names on the underlying payment table to standardized business terminology — for example, CHECK_ID is surfaced as PAYMENT_DOCUMENT_ID, CHECK_NUMBER as PAYMENT_DOCUMENT_NUMBER, CHECK_DATE as PAYMENT_DOCUMENT_DATE, PAYMENT_TYPE_FLAG as PAYMENT_TYPE, and STATUS_LOOKUP_CODE as PAYMENT_STATUS. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying data at query time.

The view is defined with the WITH READ ONLY clause, indicating that it is intended strictly for query and reporting purposes. This makes it suitable for Oracle Reports, BI Publisher data models, Oracle Discoverer/EBS business views, and custom SQL used in reconciliation and audit reporting. The object is not intended for direct DML and should not be treated as a maintenance interface to Payables.

Underlying Base Objects

Per the documented ETRM metadata, APBV_AP_PAYMENTS is defined over a single referenced base object: AP_CHECKS, accessed through its APPS schema synonym. The view text confirms this relationship, selecting exclusively from AP_CHECKS CH with a WITH READ ONLY restriction. No joins to suppliers, invoices, or payment schedules are included in the view definition, so it is a direct one-to-one projection of AP_CHECKS columns rather than an aggregated or joined business entity. Consequently, row counts and key values in the view correspond exactly to those in AP_CHECKS.

Key Columns

• PAYMENT_DOCUMENT_ID — Maps to CHECK_ID; the unique identifier of the payment.
• PAYMENT_DOCUMENT_NUMBER — Maps to CHECK_NUMBER; the printed payment document number.
• PAYMENT_DOCUMENT_DATE — Maps to CHECK_DATE; the date of the payment.
• PAYMENT_TYPE — Maps to PAYMENT_TYPE_FLAG; indicates whether the payment is a check, electronic payment, or wire.
• PAYMENT_STATUS — Maps to STATUS_LOOKUP_CODE; the current lifecycle status of the payment (for example, NEGOTIABLE, CLEARED, VOIDED).
• PAYMENT_SEQUENCE_NUMBER — Maps to DOC_SEQUENCE_ID; the payment sequence number, used for document sequencing and audit numbering.
• AMOUNT and FUNCTIONAL_AMOUNT — The entered and base-currency payment amounts.
• CLEARED_AMOUNT, CLEARED_DATE, CLEARED_FUNCTIONAL_AMOUNT — Clearing details for reconciliation.
• VOID_DATE — The date the payment was voided, if applicable.
• STOP_PAYMENT_RECORDED_DATE / STOP_PAYMENT_RELEASED_DATE and their associated user IDs — Details of stop-payment actions.
• CURRENCY_EXCHANGE_RATE, CURRENCY_EXCHANGE_DATE, CURRENCY_EXCHANGE_RATE_TYPE — Foreign-currency conversion details.
• FUTURE_PAY_DUE_DATE, STAMP_DUTY_AMOUNT, TRANSFER_PRIORITY — Supporting payment attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns.

Common Use Cases and Queries

The view is commonly used for payment register reporting, clearing and reconciliation analysis, and stop-payment auditing. A typical query locating a payment by its sequence number follows:

• SELECT payment_document_id, payment_document_number, payment_document_date, payment_sequence_number, payment_status, amount FROM apbv_ap_payments WHERE payment_sequence_number = :p_seq;
• Reconciliation of cleared versus uncleared payments by status and cleared date.
• Extraction of voided payments within a date range for audit trails.
• Foreign-currency payment analysis using the exchange rate columns.

Because the view is read-only and references only AP_CHECKS, user-supplied WHERE clauses on the columns above are the recommended filtering approach.