Search Results cnl_type




Overview
Explore in AI Chat

Overview

APPS.CSC_CONDITION_LINE_DETAILS_V is a reporting and integration view within the Oracle EBS Customer Care / Condition Management schema. It consolidates condition line definitions used by the Condition Management Engine, presenting the atomic elements of a rule condition — expressions, functions, and counters — in a denormalized, presentation-ready format. Each row returned by the view represents a single condition line (identified by its cnl_id via the underlying view, though the outer SELECT does not project that column directly) belonging to a condition group header (cnh_id) that participates in a process definition (pdf_id).

The view exists to shield downstream consumers — concurrent programs, Discoverer-style reports, OAF regions, and custom PL/SQL integration — from the raw, type-flavored storage of condition lines. Instead of exposing the raw cnl_type code, the view derives a human-readable CONDITION_TYPE and resolves operands and left-hand values differently depending on the type. It is therefore a convenience layer over the Condition Management data model, not a base table or transactional entity.

Underlying Base Objects

The view is defined over three referenced objects, combined with outer joins and a package function call:

Key Columns

  • CNL_TYPE — the raw discriminator. Documented values are 'GEX' (expression), 'FEX' (function), and 'CEX' (counter). This is the column users search on to classify or filter conditions.
  • CONDITION_TYPE — a DECODE of CNL_TYPE into Expression, Function, or Counter.
  • AAE_ID — the action attribute identifier linking a condition line to an action attribute.
  • LEFT_VALUE — type-dependent. For GEX it is OAA.NAME; for CEX it is the counter name resolved from LEFT_CTR_MASTER_ID or LEFT_COUNTER_ID; for FEX it is PACKAGE_NAME.PROCEDURE_NAME (or just the procedure name when no package exists).
  • RELATIONAL_OPERATOR — returned as NULL for function-type lines via DECODE(CNL_TYPE,'FEX',NULL,...).
  • RIGHT_OPERAND — for GEX the raw right operand; for CEX a counter name derived from RIGHT_OPERAND or RIGHT_CTR_MASTER_ID/RIGHT_COUNTER_ID.
  • LOGICAL_OPERATOR, SORTSEQ, LEFT_PARENTHESIS, RIGHT_PARENTHESIS, DESCRIPTION, PDF_ID, CNH_ID — structural and grouping metadata used to reconstruct the condition expression.

Common Use Cases and Queries

The view is typically queried when diagnosing or reporting on condition rules, for example listing all counter-based lines, or reconstructing the readable form of a condition group. A representative query filtering on the type codes the user searched for:

  • SELECT condition_type, cnl_type, cnh_id, sortseq, left_value, relational_operator, right_operand, logical_operator FROM apps.csc_condition_line_details_v WHERE cnl_type = 'CEX';
  • Join to OKC_CONDITION_HEADERS_V on CNH_ID to obtain the parent condition header context.
  • Filter by PDF_ID to inspect every condition line attached to a specific process definition.

Because the left and right values are resolved by DECODE and by CSC_CORE_UTILS_PVT, consumers should not assume uniformity across types; code that reads LEFT_VALUE or RIGHT_OPERAND must branch on CNL_TYPE. The view is read-only in practical use and carries no update semantics. It is available in both 12.1.1 and 12.2.2 with the structure documented above.