Results for “term_name”

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

Overview

PA_TERMS_LOV_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It is delivered as part of the Projects (PA) product family and functions as a list-of-values (LOV) source rather than a transactional or reporting entity. Its purpose is to expose the set of currently active agreement types that are associated with payment terms defined in Oracle Receivables. In this sense the view bridges master data held in the Projects application (agreement types) with billing terms maintained in Receivables (RA_TERMS).

Because the view filters agreement-type records by their active date range, it presents only those rows whose START_DATE_ACTIVE and END_DATE_ACTIVE bracket the current system date. This makes it well suited to driving LOV poplists, validation queries, and lightweight integration lookups where only live terms should be surfaced to the end user. In the typical Projects flow, agreement types determine whether revenue limits apply to a project or contract, and the associated Receivables term defines the billing schedule used for invoices. Exposing both values together through a single view simplifies the selection experience and reduces the client-side work required to join across the two products.

Underlying Base Objects

The view is defined over two synonyms in the APPS schema, each resolving to a base table:

• PA_AGREEMENT_TYPES — the Projects table holding agreement-type definitions, their active date windows, and their link to a Receivables term.
• RA_TERMS — the Receivables payment-terms table providing the term NAME and other term attributes.

The join is expressed as AT.TERM_ID = RT.TERM_ID(+), an outer join in Oracle syntax. The outer join on RA_TERMS means that agreement types with no matching Receivables term are still returned, with term columns null. This is important for LOV purposes: users can still select an agreement type that lacks an assigned payment term, and downstream processing can flag the missing term. The active-date predicate uses TRUNC(SYSDATE) BETWEEN TRUNC(AT.START_DATE_ACTIVE) AND TRUNC(NVL(AT.END_DATE_ACTIVE, SYSDATE)), so records with an open-ended END_DATE_ACTIVE (null) remain valid indefinitely. Date truncation removes any time component, giving a stable inclusion rule across the working day.

Key Columns

• AGREEMENT_TYPE — the identifier/name of the Projects agreement type returned by the LOV.
• REVENUE_LIMIT_FLAG — indicates whether the agreement type enforces a revenue limit; consumed by billing and revenue-recognition logic.
• TERM_ID — the foreign key linking the agreement type to its Receivables payment term.
• TERM_NAME — the descriptive name of the term sourced from RA_TERMS.NAME; null when no matching term exists, consistent with the outer join.

Although the underlying SQL aliases RT.NAME as NAME, the documented view metadata exposes the column as TERM_NAME, which is the name applications and queries should reference.

Common Use Cases and Queries

The view is most commonly used to populate an LOV in a Projects form or OAF page, and to support custom validation or reporting queries that need active agreement types alongside their payment terms. A simple listing looks like this:

• SELECT agreement_type, term_id, term_name, revenue_limit_flag FROM apps.pa_terms_lov_v ORDER BY agreement_type;

A typical filtered lookup returning only the term name for a given agreement type:

• SELECT term_name FROM apps.pa_terms_lov_v WHERE agreement_type = :p_agreement_type;

To identify agreement types that currently have no Receivables term assigned (relying on the outer join):

• SELECT agreement_type, term_id FROM apps.pa_terms_lov_v WHERE term_name IS NULL;

And to identify which agreement types are subject to revenue limits:

• SELECT agreement_type, term_name FROM apps.pa_terms_lov_v WHERE revenue_limit_flag = 'Y';

Because the view already applies the active-date filter, callers do not need to repeat that logic. Clients should query it in preference to joining PA_AGREEMENT_TYPES and RA_TERMS directly, ensuring consistency with the standard Projects LOV behavior across 12.1.1 and 12.2.2.