Search Results print_lead_days




Overview
Explore in AI Chat

Overview

APPS.ARFV_AR_TERMS is a reporting and inquiry view in the Oracle E-Business Suite Receivables (AR) module, registered under the FND Design Data application short name AR and owned by the APPS schema. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents payment terms configuration data stored in the Receivables terms setup, exposing the identifier, the descriptive name and description of each terms record, and the various control flags and schedule attributes that govern how due dates, discounts, and installments are calculated for transactions.

The view is not a base table and carries no transactional data of its own; it is a projection over the underlying terms entity. Oracle's metadata explicitly marks this object as "Oracle Internal Use Only," noting that Oracle Corporation does not support direct access to Oracle applications data through this object except from standard Oracle Applications programs. Consequently, ARFV_AR_TERMS should be treated as an internal dictionary/reporting view rather than a public interface. Developers who need the payment term name for a transaction or customer record are expected to reach it through supported APIs, concurrent programs, or the supported views rather than by querying this object directly.

The user search term "payment_term_name" maps directly to the PAYMENT_TERM_NAME column, which is the user-facing short name of the terms record and the most commonly referenced descriptive field in this view.

Underlying Base Objects

ARFV_AR_TERMS is defined over a single documented base object: APPS.RA_TERMS, accessed through a synonym. RA_TERMS is the Receivables base table that stores payment terms definitions, including the line-level and installment-level discount and due-date rules. The view selects a subset of the columns from that table and exposes them with the same or trimmed naming. Because the view is a straightforward projection, no aggregation, join, or derivation logic is applied beyond what the base table provides; the row count and cardinality of the view match the qualifying rows in RA_TERMS.

Per the dependency information, ARFV_AR_TERMS references RA_TERMS, and the view itself is not referenced by any other database object. This confirms that the view is a leaf-level object in the dependency chain — it depends on RA_TERMS but nothing downstream depends on it. Any change to RA_TERMS column definitions or semantics therefore flows directly into this view, and there is no intermediate object to insulate consumers.

Key Columns

The view exposes the following documented columns:

  • TERM_ID (NUMBER(15)) — The unique identifier of the payment terms record; primary correlation key to RA_TERMS and to foreign keys such as customer or transaction term references.
  • PAYMENT_TERM_NAME (VARCHAR2(15)) — The short, user-facing name of the terms, for example "30 NET" or "2/10 NET 30," and the field most frequently searched and displayed.
  • PAYMENT_TERM_DESCRIPTION (VARCHAR2(240)) — Free-text description providing additional detail about the terms.
  • CREDIT_CHECK_FLAG (CHAR(50)) — Indicates whether credit checking applies to transactions using these terms.
  • CUTOFF_DAY (NUMBER) — The day of the month used for cutoff-based terms calculations.
  • PARTIAL_DISCOUNT_FLAG (CHAR(54)) — Controls whether partial discounts are permitted for these terms.
  • START_EFFECTIVE_DATE and END_EFFECTIVE_DATE (DATE) — The active date range during which the terms are effective, supporting date-effective terms setup.
  • FIRST_INSTALLMENT_OPTION (CHAR(67)) — Determines how the first installment of a multi-installment terms schedule is calculated.
  • PRINT_LEAD_DAYS (NUMBER) — Number of days of lead time used when printing invoices or statements associated with these terms.
  • DISCOUNT_BASIS (CHAR(68)) — Defines the basis on which discounts are computed.
  • Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY — Standard Oracle audit trail columns.

Common Use Cases and Queries

Typical uses include resolving a TERM_ID from a customer or transaction record to its display name, validating terms setup for a given effective period, and building reporting extracts of terms configuration for implementation or audit purposes. A simple lookup by name is commonly used during data validation:

  • SELECT term_id, payment_term_name, payment_term_description FROM apps.arfv_ar_terms WHERE payment_term_name = :p_name;
  • SELECT term_id, payment_term_name, start_effective_date, end_effective_date FROM apps.arfv_ar_terms WHERE TRUNC(SYSDATE) BETWEEN start_effective_date AND end_effective_date;
  • SELECT t.term_id, t.payment_term_name, t.print_lead_days FROM apps.arfv_ar_terms t ORDER BY t.payment_term_name;

Because the object is flagged Oracle Internal Use Only, these queries should be confined to read-only reporting and ad-hoc diagnostics. For production integrations, the supported alternative is to retrieve terms information through the Receivables open interfaces or standard concurrent programs. Where direct SQL is unavoidable, join ARFV_AR_TERMS to RA_TERMS on TERM_ID when additional base-table columns are required, and restrict results by the effective date range to avoid returning inactive terms.