Results for “okl_fe_crit_cat_def_v”

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

Overview

OKL_FE_CRIT_CAT_DEF_V is a reporting and integration view owned by the APPS schema in Oracle Lease and Finance Management (OKL), one of the Oracle E-Business Suite (EBS) modules available in 12.1.1 and 12.2.2. The view is described in the ETRM documentation as the "Criteria Categories View." It exposes the definition of criteria categories used by the OKL rules and criteria engine, which evaluates conditions against lease and finance data during contract processing, pricing, and rule execution.

The view is a translation-aware, denormalized presentation of the underlying criteria category definition tables. Because it joins the base table to its translation table, it returns the description appropriate to the runtime language of the session. The view status is documented as VALID, and it is commonly used as a lookup source for validation and value-set queries, list-of-values abstractions, and custom report builders that need to resolve criteria category metadata in a single SELECT statement.

Underlying Base Objects

OKL_FE_CRIT_CAT_DEF_V is defined over two base objects, both referenced through synonyms in the APPS schema:

• OKL_FE_CRIT_CAT_DEF_B — the base (non-translated) table holding the primary criteria category definition rows.
• OKL_FE_CRIT_CAT_DEF_TL — the translation table holding language-specific descriptive attributes.

The view text joins the two objects on CRIT_CAT_DEF_ID and restricts the translation rows to the session language using the condition ECCT.LANGUAGE = USERENV('LANG'). This means that for each base definition row, only the description row matching the current language environment is returned. Consequently, queries that do not set NLS_LANG or the session language explicitly may return descriptions in an unexpected language or, if no matching translation row exists, may omit rows from the result set.

Key Columns

• CRIT_CAT_DEF_ID — Primary identifier of the criteria category definition; the join key between the base and translation tables.
• OBJECT_VERSION_NUMBER — Standard EBS optimistic locking column, incremented on each update of the base row.
• ECC_AC_FLAG — Flag indicating the associated criteria category control or applicability attribute.
• ORIG_CRIT_CAT_DEF_ID — Reference to the original definition, used when a category is copied or derived.
• CRIT_CAT_NAME and CRIT_CAT_DESC — The category name from the base table and the language-translated description from the translation table.
• VALUE_TYPE_CODE — The column the user searched for. It indicates the type of value accepted by the criteria category, distinguishing among such forms as a constant value, a column reference, or a SQL-derived source, and it pairs semantically with DATA_TYPE_CODE.
• DATA_TYPE_CODE — The data type expected for the category value, such as character, number, or date.
• SFWT_FLAG — A seeded/functional flag from the translation table affecting display or behavior.
• ENABLED_YN — Indicates whether the category definition is currently active and can be used by rules processing.
• SEEDED_YN — Distinguishes Oracle-seeded system categories from user-defined categories, an important consideration when customizing.
• FUNCTION_ID — Foreign key to the function or menu context associated with the definition.
• SOURCE_YN — Indicates whether the category definition supplies a source value.
• SQL_STATEMENT — Optional SQL text associated with the definition when the category derives its value dynamically.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

This view is typically queried to enumerate available criteria categories for configuration screens, to validate the VALUE_TYPE_CODE and DATA_TYPE_CODE associated with a category before writing rule logic, and to join definitions back to usage tables when diagnosing rule behavior in OKL.

List active, user-defined categories with their value and data type codes:

SELECT crit_cat_def_id, crit_cat_name, crit_cat_desc,
       value_type_code, data_type_code, source_yn
FROM   apps.okl_fe_crit_cat_def_v
WHERE  enabled_yn = 'Y'
AND    seeded_yn = 'N'
ORDER  BY crit_cat_name;

Filter by value type code, for example to find constant-valued categories:

SELECT crit_cat_name, value_type_code, data_type_code
FROM   apps.okl_fe_crit_cat_def_v
WHERE  value_type_code = :value_type_code;

Retrieve definitions that use a SQL statement as their source, useful during migration or performance review:

SELECT crit_cat_name, sql_statement
FROM   apps.okl_fe_crit_cat_def_v
WHERE  sql_statement IS NOT NULL;

Because the view forces a language join, integration code should rely on it primarily within an initialized EBS session rather than in external extracts where the language environment cannot be guaranteed. Where full language coverage is required, querying OKL_FE_CRIT_CAT_DEF_B and OKL_FE_CRIT_CAT_DEF_TL directly and applying an explicit LANGUAGE predicate is the safer pattern.