Search Results arfv_ar_terms

Overview

ARFV_AR_TERMS is an Oracle E-Business Suite (EBS) view owned by the APPS schema and registered under the Receivables (AR) product. It exposes payment term definitions used to determine the specific payment conditions applicable to a customer for the sale of goods or services. In practice, a payment term governs when an invoice becomes due, what discount (if any) is offered for early settlement, and how installments are structured across the billing lifecycle.

The object is classified as a VIEW with VALID status in both Oracle EBS 12.1.1 and 12.2.2. The "ARFV" prefix identifies it as a Receivables foundation view, a naming convention Oracle applies to reporting and integration-facing views that present reference or setup data in a stabilized, denormalized form. Because it is a view rather than a base table, it carries no storage of its own; it is a read-only projection over its underlying data source, as indicated by the WITH READ ONLY clause in the view text.

Its principal role is to serve as a reporting and integration surface for payment term setup, including the name, description, active date range, cutoff day, printing lead days, and the various descriptive flexfield-driven business flags. Because the view decodes several lookup values inline using the "_LA" (lookup attribute) annotation mechanism, it delivers human-readable meanings rather than raw lookup codes, which simplifies downstream reporting.

Underlying Base Objects

The view is defined over a single base object: RA_TERMS, accessed in the view text via the alias TE (RA_TERMS TE). In the documented metadata, RA_TERMS is presented as a synonym referenced by the view. RA_TERMS is the core Receivables table that stores payment term header definitions, and the view reads directly from it while enforcing read-only access.

The documented metadata lists only RA_TERMS as a referenced base object. The view text confirms this dependency unambiguously: the SELECT projects columns exclusively from TE (RA_TERMS), and the FROM clause contains no joins, unions, or additional tables. Consequently, ARFV_AR_TERMS is best understood as a controlled, presentation-layer projection over a single Receivables setup table, exposing terminology and lookup-decoded values tailored to reporting consumers. It introduces no independent business logic beyond the column aliasing and lookup translation embedded in the view definition.

Key Columns

The view exposes the following documented columns:

• TERM_ID — Surrogate key for the payment term; maps to TE.TERM_ID and is the unique identifier of the term.
• PAYMENT_TERM_NAME — The term name (TE.NAME), the user-facing label selected on customers, invoices, and agreements.
• PAYMENT_TERM_DESCRIPTION — The term description (TE.DESCRIPTION), providing supplementary detail beyond the name.
• _LA:CREDIT_CHECK_FLAG — Lookup-decoded indicator (AR_LOOKUPS, YES/NO) derived from TE.CREDIT_CHECK_FLAG, indicating whether credit checking applies for this term.
• CUTOFF_DAY — The due cutoff day (TE.DUE_CUTOFF_DAY), the day used to determine invoice due date calculation.
• _LA:PARTIAL_DISCOUNT_FLAG — Lookup-decoded indicator (AR_LOOKUPS, YES/NO) from TE.PARTIAL_DISCOUNT_FLAG, showing whether partial discounts are permitted.
• START_EFFECTIVE_DATE — The active start date (TE.START_DATE_ACTIVE) for the term.
• END_EFFECTIVE_DATE — The active end date (TE.END_DATE_ACTIVE) for the term.
• _LA:FIRST_INSTALLMENT_OPTION — Lookup-decoded value (AR_LOOKUPS, INSTALLMENT_OPTION) from TE.FIRST_INSTALLMENT_CODE, indicating how the first installment is scheduled.
• PRINT_LEAD_DAYS — The number of lead days (TE.PRINTING_LEAD_DAYS) used when printing billing documents in advance of the due date.
• _LA:DISCOUNT_BASIS — Lookup-decoded value (AR_LOOKUPS, DISCOUNT_BASIS) from TE.CALC_DISCOUNT_ON_LINES_FLAG, defining the basis on which discounts are calculated.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY, providing standard audit lineage for the record.

The "_LA" prefixed columns are noteworthy: the prefix signals that the value is resolved through a lookup type (for example AR_LOOKUPS with the YES/NO, INSTALLMENT_OPTION, or DISCOUNT_BASIS lookup codes) and returned as the lookup MEANING rather than the stored code.

Common Use Cases and Queries

ARFV_AR_TERMS is typically used for payment term reporting, reconciliation, and integration extracts. Common scenarios include listing all active terms for a given effective period, validating that a customer's assigned term exists and is active, and feeding term metadata into downstream reporting or data warehouses where a stable, read-only view is preferable to querying RA_TERMS directly.

Representative queries include:

• Retrieve a term by identifier: SELECT term_id, payment_term_name, payment_term_description FROM arfv_ar_terms WHERE term_id = :p_term_id;
• List terms active on a given date: SELECT payment_term_name, start_effective_date, end_effective_date FROM arfv_ar_terms WHERE :p_date BETWEEN start_effective_date AND NVL(end_effective_date, :p_date);
• Report credit-check and discount behavior: SELECT payment_term_name, "_LA:CREDIT_CHECK_FLAG" credit_check, "_LA:DISCOUNT_BASIS" discount_basis FROM arfv_ar_terms ORDER BY payment_term_name;
• Audit recently changed terms: SELECT payment_term_name, last_update_date, last_updated_by FROM arfv_ar_terms WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;

Because the columns carrying the "_LA" prefix require quoted identifiers in SQL, queries should reference them with double quotes exactly as defined. As the view is WITH READ ONLY, it supports query-only workloads; all maintenance must be performed against RA_TERMS through the Receivables application.