Search Results payment_term

Overview

SO_PAYMENT_TERMS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Order Entry (OE) product family and exposes the set of payment terms that are currently active, presenting a simplified, filtered projection of payment term data for use in ordering, reporting, and integration contexts. Rather than surfacing the complete terms definition maintained in the Receivables foundation tables, the view returns only those terms whose active date range brackets the current system date (SYSDATE).

Because payment terms govern due dates, discount periods, and installment behavior on orders and invoices, this view provides a convenient, always-current lookup for downstream components that need to attach a valid term to a transaction. Its status is documented as VALID, and it is categorized under the OE - Order Entry module within the ETRM reference set for releases 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a single documented base object: RA_TERMS, referenced through an APPS synonym. RA_TERMS is the Receivables foundation table that stores the master definition of every payment term, including its name, description, active date range, and the related schedule and discount lines. SO_PAYMENT_TERMS_V does not join to any other table; it selects a narrow set of columns from RA_TERMS and applies a row-level filter.

The filter condition is:

WHERE SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE)

This means a term with no start date is treated as active from the current date, and a term with no end date is treated as active through the current date. The practical effect is that only currently effective terms are returned, while expired or not-yet-effective terms are excluded. No DML is possible against the view; it is strictly a query object.

Key Columns

• PAYMENT_TERM — The descriptive name of the payment term, aliased from the RA_TERMS.NAME column. This is the value typically displayed to users and stored on order or invoice headers.
• DESCRIPTION — The free-text description of the term as maintained in RA_TERMS.DESCRIPTION, useful for user-facing labels and reporting.
• PAYMENT_TERM_ID — The unique numeric identifier of the term, aliased from RA_TERMS.TERM_ID. This is the foreign key value used to link transactions to their term definition and is the preferred column for programmatic joins and lookups.

Common Use Cases and Queries

The view is most often used as a validation and selection list for active payment terms. A typical lookup to populate a list of values or to resolve a term ID from a name would be:

SELECT PAYMENT_TERM_ID, PAYMENT_TERM, DESCRIPTION
FROM APPS.SO_PAYMENT_TERMS_V
ORDER BY PAYMENT_TERM;

To confirm whether a specific term is currently active before assigning it to an order:

SELECT PAYMENT_TERM_ID, PAYMENT_TERM
FROM APPS.SO_PAYMENT_TERMS_V
WHERE PAYMENT_TERM = :term_name;

Because the view applies an automatic date filter, reports and integrations that consume it inherit the "currently active" semantics without needing to replicate the START_DATE_ACTIVE and END_DATE_ACTIVE logic. This makes it suitable for concurrent programs, Oracle Reports, OAF pages, and interface staging tables in Order Management that must present only valid terms. Note that historical reporting on terms that are no longer active requires querying RA_TERMS directly, since expired terms are filtered out of this view.