Search Results oe_ra_terms_v




Overview
Explore in AI Chat

Overview

OE_RA_TERMS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is registered under the Order Management (ONT) product family and, as the ETRM documentation states, is based on the RA_TERMS synonym. The view exposes payment term definitions in a form that is convenient for order management reporting and integration, layering a small number of derived or canonical values on top of the underlying receivables payment term records.

Functionally the view presents one row per payment term defined in Oracle Receivables, retaining the descriptive attributes of the term (name, description, active dates, installment-related flags, and the DFF attribute columns) and additionally surfacing a computed PREPAYMENT_FLAG. Because the object is a view, it is not directly updatable and inherits the security context of the APPS schema and of RA_TERMS.

Underlying Base Objects

The documented base objects are:

  • RA_TERMS (SYNONYM) — the core payment terms table in Oracle Receivables, from which all persistent columns are selected.
  • AR_PUBLIC_UTILS (PACKAGE) — a public Receivables utility package referenced in the view text through the function call AR_PUBLIC_UTILS.CHECK_PREPAY_PAYMENT_TERM(TERM_ID).

The view definition follows the pattern SELECT ... , AR_PUBLIC_UTILS.CHECK_PREPAY_PAYMENT_TERM(TERM_ID) FROM RA_TERMS. All columns except the last are direct projections of RA_TERMS attributes; PREPAYMENT_FLAG is the return value of the package function, evaluated per row using TERM_ID as input. This design centralizes the business rule that determines whether a given payment term represents a prepayment term, so the logic is not duplicated across consumers.

Note that the view text lists an alias CREATE_BY in the column inventory, whereas the projection is CREATED_BY; this is a documentation transcription artifact rather than a difference in the underlying object.

Key Columns

Common Use Cases and Queries

Typical uses include populating order entry LOVs or concurrent report extracts that must exclude prepayment terms, and reconciling OM payment term assignments against Receivables definitions. Because PREPAYMENT_FLAG is computed by a function call, filtering on it forces per-row evaluation; restricting the driving set first with standard predicates improves performance.

  • List active, non-prepayment terms for order entry:

    SELECT term_id, name, prepayment_flag FROM oe_ra_terms_v WHERE prepayment_flag = 'N' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

  • Identify prepayment terms for reconciliation:

    SELECT term_id, name, description FROM oe_ra_terms_v WHERE prepayment_flag = 'Y' ORDER BY name;

  • Extract term attributes for a downstream integration, joining to order data:

    SELECT t.term_id, t.name, t.base_amount, t.first_installment_code FROM oe_ra_terms_v t WHERE t.term_id = :p_term_id;

Consumers should treat the view as read-only and, where only persistent RA_TERMS attributes are required, query RA_TERMS directly to avoid the overhead of the function call. When PREPAYMENT_FLAG is required, OE_RA_TERMS_V is the supported projection.