Results for “condition_name”

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

Overview

The HZ_WORD_RPL_CONDS_VL view is a seeded Oracle E-Business Suite database object owned by the APPS schema and registered under the Receivables (AR) product family. It is a "VL" (view with language join) construct, a naming convention Oracle uses when a base table partitioned into a language-independent ("_B") table and a translation ("_TL") table must be surfaced as a single, linguistically resolved record set. This view presents the replacement condition definitions used by Oracle's word replacement and correspondence-generation framework, exposing condition names and the condition description text in the session's currently active language, as determined by USERENV('LANG').

Because it is a VL view, it is the appropriate source for reporting, forms, and integration interfaces that need human-readable descriptions rather than the raw language-neutral keys. It is not a transactional table; it functions as a read-only presentation layer over the underlying condition configuration, and it is frequently referenced by Oracle Correspondence, document generation, and letter/attachment tooling that performs conditional text substitution.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two referenced base objects, exposed to the APPS schema as synonyms:

• HZ_WORD_RPL_CONDS_B — the base (language-independent) table holding the condition's structural definition, aliased as B in the view text.
• HZ_WORD_RPL_CONDS_TL — the translation table holding the language-specific name and description, aliased as T.

The two are joined on the common key CONDITION_ID, with the translation side additionally filtered by T.LANGUAGE = USERENV('LANG'). This guarantees that exactly one localized description row is returned per condition for the caller's session language. Both source objects are documented as SYNONYM-referenced under APPS. The view text additionally selects the base-table ROWID as ROW_ID, providing a pseudo-key for tools that expect a row identifier.

Key Columns

• ROW_ID — the ROWID of the _B row, exposed under an alias.
• CONDITION_ID — the primary join key linking base and translation records.
• CONDITION_NAME — the short identifier for the replacement condition (from _TL).
• CONDITION_DESCRIPTION — the descriptive text for the condition; this is the column the user searched for and is the primary reason to query this view rather than the base table.
• ENTITY — identifies the entity the condition applies to.
• CONDITION_FUNCTION — the function or rule associated with evaluating the condition.
• CONDITION_VAL_FMT_FLAG — a formatting flag governing how the condition value is rendered.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns supporting auditing and concurrency control.

Common Use Cases and Queries

The view is typically queried to enumerate replacement conditions alongside their readable descriptions, for example when auditing correspondence configuration or debugging why a particular conditional substitution fired or did not fire.

Listing all conditions for the session language:

SELECT condition_id, condition_name, condition_description, entity, condition_function FROM hz_word_rpl_conds_vl ORDER BY condition_name;

Resolving a single condition by identifier:

SELECT condition_name, condition_description FROM hz_word_rpl_conds_vl WHERE condition_id = :p_condition_id;

Searching for conditions by description text:

SELECT condition_id, condition_name, condition_description FROM hz_word_rpl_conds_vl WHERE UPPER(condition_description) LIKE '%' || UPPER(:p_search) || '%';

Because the view already constrains LANGUAGE to USERENV('LANG'), no additional language filter is required; callers needing a translation other than the session language must query the _TL table directly.