Results for “apfv_ap_payment_terms”

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

Overview

APFV_AP_PAYMENT_TERMS is a business view owned by the APPS schema in Oracle E-Business Suite, registered under the Payables (AP) product family. It exposes payment term definition data in a reporting-oriented column layout, presenting the same information as the underlying AP_TERMS table but with friendlier, business-facing column aliases. The view is defined with the WITH READ ONLY clause, meaning it cannot be used as a target for DML operations; it exists purely for query and reporting purposes. Because it is a reporting view rather than a transactional entity, it is safe to reference in custom reports, BI Publisher data templates, Oracle Discoverer workbooks, and third-party integrations that need to read payment term configuration without touching the base table directly. The object is documented as VALID in ETRM for both 12.1.1 and 12.2.2, confirming its availability across the two major release families.

Underlying Base Objects

The view is defined over a single referenced base object: AP_TERMS, accessed through a synonym in the APPS schema. The view text selects from AP_TERMS TERM WITH READ ONLY, projecting columns from the base table and mapping them to the documented view column names. The relationship is strictly one-to-one: every row in APFV_AP_PAYMENT_TERMS corresponds to exactly one row in AP_TERMS. No joins, aggregations, filters, or derived expressions are applied, so the view is a straightforward column-aliasing layer. This is characteristic of Oracle's APFV ("AP Financial View") family, which provides stable, readable interfaces over configuration and transactional tables so that custom code is insulated from changes to the underlying base table definitions.

Key Columns

• PAYMENT_TERM_ID — Surrogate primary key of the payment term, sourced from TERM_ID. This is the value stored on supplier sites, invoices, and other objects that reference a payment term.
• PAYMENT_TERM_NAME — The user-defined name of the term (for example, "Net 30" or "Immediate"), sourced from NAME.
• DUE_CUTOFF_DAY — The day of the month used as the cutoff for determining the due date, applicable to terms with day-of-month based schedules.
• START_EFFECTIVE_DATE and END_EFFECTIVE_DATE — The active date range of the term, mapped from START_DATE_ACTIVE and END_DATE_ACTIVE. These columns determine whether a term is currently usable.
• RANK — The ordering rank used to control the sequence in which payment terms are presented.
• DESCRIPTION — Free-text description of the payment term.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard Oracle WHO columns that capture audit information about row creation and last modification.

Common Use Cases and Queries

The view is most often used to populate payment term selection lists in custom forms and reports, to validate payment term references during data conversion, and to produce configuration extracts for audit or migration projects. A typical query to list all currently active terms follows:

SELECT payment_term_id, payment_term_name, due_cutoff_day
FROM apps.apfv_ap_payment_terms
WHERE TRUNC(SYSDATE) BETWEEN NVL(start_effective_date, TRUNC(SYSDATE))
AND NVL(end_effective_date, TRUNC(SYSDATE))
ORDER BY rank, payment_term_name;

To resolve a term name from an identifier, the view can be joined to AP_SUPPLIER_SITES_ALL or AP_INVOICES_ALL on the payment term ID column. Because the view is read only and mirrors AP_TERMS exactly, it should be preferred over direct queries against the base table when a stable, business-friendly interface is required.