Search Results first_installment_code

Overview

RA_TERMS_VL is a language-aware (VL) view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It presents payment term definitions—the agreement structures that determine due dates, discount eligibility, installment behavior, and credit handling on customer transactions—by joining the base payment terms table to its translation table and to consolidated billing cycle definitions. Because it is a "_VL" view, it resolves translatable columns (NAME and DESCRIPTION) through the session language, returning the appropriate translated values for the current user environment as determined by USERENV('LANG').

The view is documented for Release 11.5 and Release 12.0 and remains valid in EBS 12.1.1 and 12.2.2. It is a read-only reporting and integration object: it exposes payment term attributes for inquiry, reporting, and interface extraction without requiring callers to join the underlying tables themselves. The CREDIT_CHECK_FLAG column, which the user searched for, is exposed directly by this view and indicates whether credit checking applies to transactions governed by the term.

Underlying Base Objects

The 12.2.2 ETRM metadata documents three referenced base objects, all synonyms in the APPS schema:

• RA_TERMS_B — the base (non-translatable) payment terms table, supplying TERM_ID, credit and discount flags, installment codes, billing cycle, and descriptive flexfield attributes.
• RA_TERMS_TL — the translation table supplying NAME and DESCRIPTION, joined on TERM_ID and filtered by T.LANGUAGE = USERENV('LANG').
• AR_CONS_BILL_CYCLES_TL — the consolidated billing cycles translation table, outer-joined to supply CYCLE_NAME and BILLING_CYCLE_ID.

The join between RA_TERMS_B and RA_TERMS_TL is an inner join on TERM_ID; the join to AR_CONS_BILL_CYCLES_TL is an outer join (BC.BILLING_CYCLE_ID(+) and BC.LANGUAGE(+)), so terms without an assigned billing cycle are still returned.

Key Columns

• TERM_ID — primary key of the payment term, used as the foreign key from invoices, transactions, and customer profiles.
• CREDIT_CHECK_FLAG — indicates whether credit checking is enabled for the term (for example, whether the associated transaction should be subjected to credit limit validation).
• NAME / DESCRIPTION — language-resolved term name and description from RA_TERMS_TL.
• DUE_CUTOFF_DAY, PRINTING_LEAD_DAYS, START_DATE_ACTIVE, END_DATE_ACTIVE — terms scheduling and validity attributes.
• BASE_AMOUNT, CALC_DISCOUNT_ON_LINES_FLAG, PARTIAL_DISCOUNT_FLAG, FIRST_INSTALLMENT_CODE — discount and installment calculation controls.
• PREPAYMENT_FLAG — NVL-normalized to 'N' when null.
• BILLING_CYCLE_ID / CYCLE_NAME — consolidated billing cycle linkage.
• IN_USE, ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — usage indicator and descriptive flexfield context columns.
• ROW_ID — rowid of the RA_TERMS_B row.

Common Use Cases and Queries

Typical scenarios include listing active payment terms, auditing credit-check settings, and extracting term data for interfaces. The following retrieves terms with credit checking enabled:

SELECT term_id, name, due_cutoff_day, credit_check_flag FROM ra_terms_vl WHERE credit_check_flag = 'Y' AND NVL(in_use, 'Y') = 'Y';

To report terms alongside billing cycles, query NAME and CYCLE_NAME directly, since the view already performs the outer join. Because NAME and DESCRIPTION are resolved through USERENV('LANG'), results reflect the session language, and queries should not re-join RA_TERMS_TL. Always filter by TERM_ID or NAME rather than transacting against the view, which is read-only.