Results for “ar_payment_schedules_flex_view”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_PAYMENT_SCHEDULES_FLEX_VIEW is a descriptive flexfield (DFF) view owned by the APPS schema within the Oracle E-Business Suite Receivables (AR) module. It exposes payment schedule data together with the context and attribute segments required to present and query descriptive flexfield information for payment schedules in Oracle EBS 12.1.1 and 12.2.2. In the Receivables data model, payment schedules represent the individual installments and due dates derived from a transaction, and they carry amounts due, adjustments, applied cash, discounts, and dispute balances. This view consolidates the core columns of AR_PAYMENT_SCHEDULES and augments them with related identifiers and descriptive flexfield context, allowing reports, forms, and integrations to retrieve payment schedule detail in a single query.

The view is registered under the APPS schema with a status of VALID, and its documented purpose is to expose descriptive flexfields for payment schedules. Because it is a view rather than a table, it performs no physical storage of its own and instead projects columns from the underlying base objects at query time.

Underlying Base Objects

According to the ETRM 12.2.2 documentation, the view is defined over three referenced base objects:

• AR_PAYMENT_SCHEDULES (SYNONYM) — the primary source, aliased as PS in the view text, supplying the payment schedule identifiers, amounts, dates, status, and terms columns.
• AR_CASH_RECEIPTS (SYNONYM) — aliased as CR, contributing receipt-related columns such as DOC_SEQUENCE_VALUE and RECEIPT.
• RA_CUSTOMER_TRX (SYNONYM) — the transaction header table that anchors payment schedules to their originating customer transaction.

The synonym references indicate that the view resolves to the AR product tables through public or product-specific synonyms in the APPS schema, a standard pattern in EBS for cross-module access. The join links payment schedules to cash receipts and to customer transactions, enabling the view to present flexfield and descriptive data in the context of the full receivables lifecycle.

Key Columns

The view exposes a broad set of columns. Notable groupings include:

• Identifiers: PAYMENT_SCHEDULE_ID, CUSTOMER_TRX_ID, CUSTOMER_ID, CUSTOMER_SITE_USE_ID, CUST_TRX_TYPE_ID, TERM_ID, ASSOCIATED_CASH_RECEIPT_ID, CASH_RECEIPT_ID, REVERSED_CASH_RECEIPT_ID, SELECTED_FOR_RECEIPT_BATCH_ID.
• Amounts: AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, ACCTD_AMOUNT_DUE_REMAINING, AMOUNT_APPLIED, AMOUNT_ADJUSTED, AMOUNT_CREDITED, AMOUNT_IN_DISPUTE, FREIGHT_ORIGINAL, FREIGHT_REMAINING, TAX_ORIGINAL, TAX_REMAINING, DISCOUNT_ORIGINAL, DISCOUNT_REMAINING.
• Dates: DUE_DATE, GL_DATE, TRX_DATE, DISCOUNT_DATE, ACTUAL_DATE_CLOSED, GL_DATE_CLOSED, EXCHANGE_DATE, DISPUTE_DATE, LAST_CHARGE_DATE.
• Status and control: CLASS, STATUS, IN_COLLECTION, RECEIPT_CONFIRMED_FLAG, NUMBER_OF_DUE_DATES, TERMS_SEQUENCE_NUMBER.
• Cash application detail: CASH_APPLIED_AMOUNT_LAST, CASH_APPLIED_DATE_LAST, CASH_APPLIED_ID_LAST, CASH_APPLIED_STATUS_LAST, CASH_GL_DATE_LAST, CASH_RECEIPT_AMOUNT_LAST, CASH_RECEIPT_DATE_LAST, CASH_RECEIPT_STATUS_LAST.
• Collections and follow-up: COLLECTOR_LAST, FOLLOW_UP_CODE_LAST, FOLLOW_UP_DATE_LAST, PROMISE_AMOUNT_LAST, PROMISE_DATE_LAST, CALL_DATE_LAST.
• Audit and concurrent program: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• Receipt context: CR.DOC_SEQUENCE_VALUE and CR.RECEIPT, drawn from AR_CASH_RECEIPTS.

Common Use Cases and Queries

Typical uses include open receivables aging reports, collections dashboards, dispute tracking, and integration extracts that require payment schedule flexfield values. A representative query joining the view to transaction data follows:

SELECT ps.payment_schedule_id, ps.trx_number, ps.due_date, ps.amount_due_remaining, ps.status, ps.class
FROM apps.ar_payment_schedules_flex_view ps
WHERE ps.customer_trx_id = :p_trx_id
ORDER BY ps.terms_sequence_number;

For cash receipts reconciliation, filter by associated cash receipt:

SELECT ps.trx_number, ps.cash_receipt_id, ps.amount_applied, ps.cash_applied_date_last, cr.receipt
FROM apps.ar_payment_schedules_flex_view ps, apps.ar_cash_receipts cr
WHERE ps.cash_receipt_id = cr.cash_receipt_id
AND ps.status = 'OP';

Because the view carries the DFF context and attribute columns, it is also used in Flexfield-based reports and in interfaces that must populate or validate descriptive flexfield segments for payment schedules during transaction import and adjustment processing.