Search Results third_discount_date

Overview

AP_PAYMENT_SCHEDULES_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and validated against releases 12.1.1 and 12.2.2. It exposes the payment schedule records of Oracle Payables in a denormalized reporting form, joining each schedule line to its parent invoice and payment batch. Although the ETRM metadata associates the object with the Receivables product grouping, the underlying data and column semantics are those of Oracle Payables (AP); the view is used across both modules wherever invoice payment terms, due dates, and discount opportunities must be evaluated.

The view is intended primarily for read-only reporting and integration rather than for transactional processing. Its role is to present, for each scheduled payment number on an invoice, the gross amount, amount remaining, due date, discount date, and the various discount amounts available, together with descriptive invoice and batch attributes. This makes it a convenient source for discount analysis, cash forecasting, aging reports, and third-party extracts that must reproduce Payables payment-schedule logic without querying the base tables directly.

Underlying Base Objects

Per the documented view text, AP_PAYMENT_SCHEDULES_V is defined over the following base objects:

• AP_PAYMENT_SCHEDULES (synonym) — the primary source, aliased as APS, supplying all schedule-level columns.
• AP_INVOICES_ALL (synonym) — aliased as AI, providing INVOICE_NUM and the invoice identifier used by the helper functions.
• AP_BATCHES_ALL (synonym) — aliased as AB, providing BATCH_NAME.
• AP_INVOICE_PAYMENTS_PKG (package) — invoked through GET_PAID_BY, GET_PAID_DATE, GET_PAYMENT_ID, and GET_PAYMENT_TYPE to derive payment status attributes dynamically.

Simplistically, the view joins each payment schedule row to its invoice and batch, then augments the result with PL/SQL function calls that resolve the paid-by, paid-date, payment-id, and payment-type values associated with a given invoice and payment number. Because the package functions are executed per row, the view carries a higher runtime cost than a plain table join.

Key Columns

• INVOICE_ID / INVOICE_NUM — identifier and number of the parent invoice.
• PAYMENT_NUM — the schedule payment number, the key that links schedules to payments.
• GROSS_AMOUNT, AMOUNT_REMAINING — scheduled amount and unpaid balance.
• DUE_DATE, FUTURE_PAY_DUE_DATE — scheduled due date and any recalculated future-pay date.
• DISCOUNT_DATE, DISCOUNT_AMOUNT_AVAILABLE, DISCOUNT_AMOUNT_REMAINING — first discount window, the discount obtainable, and the discount still available. DISCOUNT_AMOUNT_AVAILABLE is the column most frequently searched in this context.
• SECOND_DISCOUNT_DATE / SECOND_DISC_AMT_AVAILABLE and THIRD_DISCOUNT_DATE / THIRD_DISC_AMT_AVAILABLE — additional discount tiers.
• PAYMENT_STATUS_FLAG, HOLD_FLAG, PAYMENT_METHOD_LOOKUP_CODE, PAYMENT_PRIORITY, PAYMENT_CROSS_RATE — status and control attributes.
• PAID_BY, PAID_DATE, PAYMENT_ID, PAYMENT_TYPE — derived via AP_INVOICE_PAYMENTS_PKG.
• BATCH_ID, BATCH_NAME — payment batch context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical consumers use the view to report discount opportunities before the discount date lapses, to project cash requirements by due date, and to reconcile scheduled versus paid amounts. A representative query selecting discount information follows:

• SELECT invoice_num, payment_num, due_date, discount_date, discount_amount_available, amount_remaining FROM ap_payment_schedules_v WHERE discount_amount_available > 0 AND discount_date >= SYSDATE ORDER BY discount_date;

For cash forecasting, the same view can be grouped by due date:

• SELECT due_date, SUM(amount_remaining) remaining FROM ap_payment_schedules_v WHERE payment_status_flag = 'N' GROUP BY due_date ORDER BY due_date;

Because the paid-by and payment-id values are resolved through AP_INVOICE_PAYMENTS_PKG per row, queries returning large result sets should be filtered by invoice, batch, or date range to keep execution cost predictable.