Search Results third_discount_date
Overview
APFV_PAYMENT_SCHEDULES is a business view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Payables (AP) product family and is classified as a business view rather than a pure technical or security view. Its purpose is to present invoice payment schedule information in a denormalized, reporting-friendly form by joining payment schedule records to their parent invoices and vendors. This makes it suitable for operational reporting, integration extracts, and inquiry pages that need to display scheduled payment amounts, discount eligibility, due dates, and vendor context without requiring the caller to reconstruct the underlying three-table join.
The view is defined with a WITH READ ONLY clause, so it cannot be used for DML. It is a query-only construct intended for selection, reporting, and downstream consumption.
Underlying Base Objects
ETRM metadata documents three referenced base objects: AP_PAYMENT_SCHEDULES (synonym), AP_INVOICES_ALL (synonym), and PO_VENDORS (view). The view text confirms the join logic:
- AP_PAYMENT_SCHEDULES APS is the driving table, supplying payment numbers, status, amounts, discounts, and due dates.
- AP_INVOICES_ALL AI is joined on
APS.INVOICE_ID = AI.INVOICE_ID, supplying invoice number, invoice date, currency codes, pay group, and vendor identifiers. - PO_VENDORS POV is joined on
AI.VENDOR_ID = POV.VENDOR_ID, supplying vendor number and vendor name.
The view also carries descriptive flexfield context references (_DF:SQLAP:AP_PAYMENT_SCHEDULES:APS and _DF:JG:JG_AP_PAYMENT_SCHEDULES:APS) that allow the reporting layer to resolve DFF segments defined against AP_PAYMENT_SCHEDULES.
Key Columns
- INVOICE_NUMBER / INVOICE_DATE — Identifying attributes of the parent invoice.
- "_LA:INVOICE_TYPE" — A lookup-derived column resolving INVOICE_TYPE_LOOKUP_CODE through AP_LOOKUP_CODES.
- PAYMENT_NUMBER and "_LA:PAYMENT_STATUS" — Payment identifier and a lookup-resolved status flag.
- VENDOR_NUMBER / VENDOR_NAME / VENDOR_SITE_ID — Supplier identification and site context.
- INVOICE_CURRENCY / PAYMENT_CURRENCY / PAYMENT_GROUP — Currency and pay group attributes used in payment processing.
- AMOUNT_REMAINING — Outstanding amount left on the schedule.
- DISCOUNT_AMOUNT_AVAILABLE — The discount amount currently available on the schedule, directly relevant to the user's search term.
- DISCOUNT_AMOUNT_REMAINING — Portion of the discount still unclaimed.
- DISCOUNT_DATE, SECOND_DISCOUNT_DATE, THIRD_DISCOUNT_DATE — Tiered discount dates.
- SECOND_DISC_AMT_AVAILABLE, THIRD_DISC_AMT_AVAILABLE — Tiered discount amounts.
- DUE_DATE / FUTURE_PAY_DUE_DATE — Scheduled and future-pay due dates.
- GROSS_AMOUNT — Gross amount on the payment schedule.
- HOLD_FLAG — Indicates whether the schedule is on hold.
- CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard audit columns.
- INVOICE_ID / EXTERNAL_BANK_ACCOUNT_ID — Surrogate keys useful for joins and integrations.
Common Use Cases and Queries
This view is typically used to report upcoming payments, quantify available discounts, and expose payment schedules to external systems. The DISCOUNT_AMOUNT_AVAILABLE column is commonly queried to identify invoices with unclaimed early-payment discounts before expiry.
Example: list scheduled payments with available discounts by due date:
SELECT invoice_number, invoice_date, vendor_name,
payment_number, due_date, discount_date,
gross_amount, amount_remaining,
discount_amount_available, discount_amount_remaining
FROM apps.apfv_payment_schedules
WHERE discount_amount_available > 0
AND hold_flag IS NULL
ORDER BY discount_date, vendor_name;
Example: summarize outstanding amounts and discounts per vendor:
SELECT vendor_name,
SUM(amount_remaining) total_remaining,
SUM(discount_amount_available) total_discount_avail
FROM apps.apfv_payment_schedules
GROUP BY vendor_name;
Because the view is read-only and pre-joined, it is well suited to ad hoc reporting, discoverer-style queries, and integration extracts that need invoice-to-vendor context in a single select.
-
View: APFV_PAYMENT_SCHEDULES
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APFV_PAYMENT_SCHEDULES, object_name:APFV_PAYMENT_SCHEDULES, status:VALID, product: AP - Payables , description: Business view , implementation_dba_data: APPS.APFV_PAYMENT_SCHEDULES ,
-
View: APFV_PAYMENT_SCHEDULES
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.APFV_PAYMENT_SCHEDULES, object_name:APFV_PAYMENT_SCHEDULES, status:VALID, product: AP - Payables , description: Business view , implementation_dba_data: APPS.APFV_PAYMENT_SCHEDULES ,
-
View: AP_PAYMENT_SCHEDULES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:AR.AP_PAYMENT_SCHEDULES_V SQLAP.AP_PAYMENT_SCHEDULES_V, object_name:AP_PAYMENT_SCHEDULES_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_PAYMENT_SCHEDULES_V ,
-
View: AP_INVOICES_READY_TO_PAY_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_INVOICES_READY_TO_PAY_V, object_name:AP_INVOICES_READY_TO_PAY_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_INVOICES_READY_TO_PAY_V ,
-
View: AP_INVOICES_READY_TO_PAY_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:SQLAP.AP_INVOICES_READY_TO_PAY_V, object_name:AP_INVOICES_READY_TO_PAY_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_INVOICES_READY_TO_PAY_V ,
-
View: AP_PAYMENT_SCHEDULES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:AR.AP_PAYMENT_SCHEDULES_V SQLAP.AP_PAYMENT_SCHEDULES_V, object_name:AP_PAYMENT_SCHEDULES_V, status:VALID, product: AP - Payables , implementation_dba_data: APPS.AP_PAYMENT_SCHEDULES_V ,