Results for “credit_check_flag”

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

Overview

The OKX_RECEIVABLES_TERMS_V view is a read-only database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a component of the OKX product family, which supports Contracts Integration within Oracle Receivables and Oracle Order Management. Its purpose is to expose customer payment term definitions in a form that is directly consumable by the contracts integration layer and by downstream reporting, rather than requiring callers to join the multilingual base tables themselves.

The view returns one row per active payment term accessible to the calling session's language environment. Because it depends on USERENV('LANG'), the NAME and DESCRIPTION values are resolved to the session language, making the view safe for multi-language deployments. Its STATUS attribute is also computed at query time, so callers obtain an up-to-date view of whether a term is currently usable without additional date logic.

Underlying Base Objects

The documented metadata identifies two referenced base objects, both accessed through APPS synonyms:

• RA_TERMS_B — the base table storing payment term header information, including the term identifier, credit check flag, effective date range, and the IN_USE flag.
• RA_TERMS_TL — the translation table storing language-specific NAME and DESCRIPTION values, joined to RA_TERMS_B on TERM_ID.

The join is an equi-join on B.TERM_ID = T.TERM_ID, filtered by T.LANGUAGE = USERENV('LANG'). No outer join is used, so a term lacking a translation row for the current session language will not be returned. The view is therefore a two-table projection over the standard Receivables terms schema, with no aggregation or grouping. It inherits the standard security model of the underlying tables; row-level access is governed by any grants or policies applied to RA_TERMS_B and RA_TERMS_TL rather than by the view itself.

Key Columns

• ID1 — the TERM_ID value from RA_TERMS_B, providing the unique payment term identifier.
• ID2 — a constant literal '#', present to satisfy a fixed two-column identifier contract expected by the consuming integration interface. It carries no business meaning.
• CREDIT_CHECK_FLAG — indicates whether credit checking applies to the payment term.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date window for the term.
• NAME / DESCRIPTION — the translated term name and description drawn from RA_TERMS_TL.
• IN_USE — the Receivables flag recording whether the term is marked for use. This is the column most relevant to searches for "in_use" terminology; it reflects the stored flag, not a computed status.
• STATUS — a derived column returning 'A' (active) when the current date falls within the effective window, and 'I' (inactive) when SYSDATE precedes START_DATE_ACTIVE or exceeds END_DATE_ACTIVE. NULL dates are treated as unbounded via NVL against TRUNC(SYSDATE).

Common Use Cases and Queries

Typical uses include populating payment term lists in contracts integration flows, validating that a term is both flagged IN_USE and currently active before assignment, and building Receivables reference reports.

To list all active, in-use terms:

• SELECT ID1, NAME, DESCRIPTION FROM APPS.OKX_RECEIVABLES_TERMS_V WHERE IN_USE = 'Y' AND STATUS = 'A';

To inspect the effective window for a specific term:

• SELECT NAME, START_DATE_ACTIVE, END_DATE_ACTIVE, STATUS FROM APPS.OKX_RECEIVABLES_TERMS_V WHERE ID1 = :term_id;

Because STATUS is computed per row, a query filtered on STATUS = 'A' will not use a stored index on the date columns; for large result sets, filtering directly on the base date columns may perform better. All queries should be run against the APPS schema or a synonym with appropriate grants.