Search Results rule_type_codes

Overview

APPS.CZ_DETAILEDRULETYPES_LKV is a lookup view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, belonging to the ETRM (Enterprise Tax and Rules Management / Configuration Workbench) schema components owned by the APPS database user. The view acts as a filtered, presentation-layer abstraction over the generic lookup values dictionary, restricting its output to two specific lookup list names: RULE_TYPE_CODES and RULE_TYPE_CODES_DETAILED. In EBS reporting and integration contexts, such views are commonly used to drive value sets, flexfield-style LOVs (lists of values), and code-to-meaning conversions where the application needs to resolve rule type identifiers into human-readable labels. The suffix _LKV indicates a "lookup values" view, a convention widely adopted across EBS to expose lookup metadata safely without requiring direct access to the underlying lookup tables.

Underlying Base Objects

The view is defined exclusively over a single documented base object: CZ_LOOKUP_VALUES_VL, itself a view rather than a physical table. CZ_LOOKUP_VALUES_VL is the "view with language" (VL) variant of the lookup values entity, meaning it resolves translated columns such as VALUE_LABEL and VALUE_DESCRIPTION against the current session language, typically via a join to a _TL (translation) table beneath it. Consequently, CZ_DETAILEDRULETYPES_LKV inherits this language-awareness; any query against it returns labels and descriptions in the user's active language setting. The relationship is therefore a simple, one-level projection with a WHERE clause filter — the view does not aggregate, join, or otherwise transform the underlying data, it merely restricts rows by LIST_NAME.

Key Columns

• LIST_NAME — Identifies the lookup list to which a row belongs; in this view restricted to RULE_TYPE_CODES or RULE_TYPE_CODES_DETAILED.
• DATA_VALUE — The stored code value used internally by application logic and by referencing transactions.
• NUMERIC_ID_VALUE — A numeric surrogate identifier associated with the lookup value, useful for joins where numeric keys are preferred.
• VALUE_SEQ — Sort order controlling presentation in LOVs and poplists.
• DATA_TYPE_ID — Indicates the data type classification of the lookup value.
• NULL_VALUE_FLAG — Flags entries representing a null or blank selection option.
• VALUE_LABEL — The translated display text shown to end users.
• VALUE_DESCRIPTION — The translated longer description of the value's meaning.
• VALUE_NOTES — Supplementary internal notes attached to the lookup entry.

Common Use Cases and Queries

The view is principally consumed to populate rule type selections in configuration screens and to decode stored rule type codes in reports. A typical retrieval ordered for LOV display is:

SELECT DATA_VALUE, VALUE_LABEL
FROM   APPS.CZ_DETAILEDRULETYPES_LKV
WHERE  LIST_NAME = 'RULE_TYPE_CODES'
ORDER  BY VALUE_SEQ;

To decode values appearing on a transaction or configuration record, a join against the view on DATA_VALUE provides the descriptive label:

SELECT t.rule_type_code, l.VALUE_LABEL
FROM   some_rule_table t, APPS.CZ_DETAILEDRULETYPES_LKV l
WHERE  l.LIST_NAME = 'RULE_TYPE_CODES_DETAILED'
AND    l.DATA_VALUE = t.rule_type_code;

Because the base object is language-aware, the same query automatically returns labels in the session language, making the view suitable for multi-language deployments without additional translation logic. Integrations that extract lookup metadata for external systems also use the view to obtain a stable, filtered set of rule type definitions limited to the two relevant lists, avoiding the noise of the full lookup dictionary.