Results for “csc_condition_line_details_v”
24 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The CSC_CONDITION_LINE_DETAILS_V view is a reporting and integration construct within the Oracle E-Business Suite Customer Care (CSC) product family, owned by the APPS schema. It presents the individual Condition Lines that together define the Boolean logic of a condition. Each Condition Line expresses a Boolean condition, and multiple Condition Lines may be combined using AND or OR operators and nested through the use of parentheses. The view therefore exposes a decomposed, human-readable representation of condition rules used by the Customer Care rule engine and related configuration flows.
The view is particularly relevant to the column CNL_TYPE, which is the discriminator that identifies the kind of condition line being processed. Because the view decodes CNL_TYPE into a friendly CONDITION_TYPE label and derives the appropriate left value, relational operator, and right operand based on that type, it serves as a convenient single source for understanding and reporting on condition definitions without requiring the consumer to interpret raw code values.
Underlying Base Objects
According to the documented view definition, CSC_CONDITION_LINE_DETAILS_V is defined over the following referenced objects:
- OKC_CONDITION_LINES_V (
OCL) — the primary source of condition line records and the origin ofCNL_TYPE. - OKC_ACTION_ATTRIBUTES_V (
OAA) — joined onOAA.ID = OCL.AAE_IDusing an outer join, supplying expression names used as the left value for expression-type lines. - OKC_PROCESS_DEFS_V (
OPD) — joined onOCL.PDF_ID = OPD.IDusing an outer join, supplying function/package names for function-type lines. - CSC_CORE_UTILS_PVT — a package whose function
GET_COUNTER_NAMEis invoked to resolve counter identifiers into meaningful counter names for counter-type lines.
The view is a pure query construct; it stores no data of its own and relies entirely on the underlying OKC condition-related views and the CSC utility package.
Key Columns
- AAE_ID — Identifier of the associated action attribute; used to join expression-type condition lines to their attribute name.
- CNL_TYPE — The raw condition line type code. Documented values include
GEX(expression),FEX(function), andCEX(counter). This is the column most often searched for details. - CONDITION_TYPE — A decoded, human-readable form of
CNL_TYPE, resolving to EXPRESSION, FUNCTION, or COUNTER. - LEFT_VALUE — The resolved left-hand operand. For
GEXit is the attribute name; forCEXit is the counter name; forFEXit is the package-qualified or standalone procedure name. - RELATIONAL_OPERATOR — The comparison operator for the line; null for function-type lines (
FEX). - RIGHT_OPERAND — The right-hand value. For
GEXit is the stored right operand; forCEXit is a resolved counter name. - LEFT_PARENTHESIS / RIGHT_PARENTHESIS — Flags indicating where grouping parentheses are placed, enabling reconstruction of nested logic.
- LOGICAL_OPERATOR — The connective (AND/OR) linking this line to others.
- DESCRIPTION, PDF_ID, CNH_ID, SORTSEQ — Descriptive text, process definition reference, condition header reference, and ordering sequence.
Common Use Cases and Queries
Typical uses include auditing condition configuration, generating rule documentation, and debugging complex nested conditions. To retrieve all condition lines of a given type, a query filtering on CNL_TYPE is the most direct approach:
SELECT CNH_ID, SORTSEQ, CONDITION_TYPE, CNL_TYPE,
LEFT_VALUE, RELATIONAL_OPERATOR, RIGHT_OPERAND,
LEFT_PARENTHESIS, RIGHT_PARENTHESIS, LOGICAL_OPERATOR
FROM APPS.CSC_CONDITION_LINE_DETAILS_V
WHERE CNL_TYPE = 'GEX'
ORDER BY CNH_ID, SORTSEQ;
A summary by condition type supports configuration reporting:
SELECT CONDITION_TYPE, COUNT(*)
FROM APPS.CSC_CONDITION_LINE_DETAILS_V
GROUP BY CONDITION_TYPE;
Reconstructing a full condition requires ordering by CNH_ID and SORTSEQ and applying the parenthesis and logical operator columns to rebuild the nested Boolean expression presented by this view.
-
Each Condition Line expresses a Boolean condition. Multiple Condition Lines may be and'd or or'd together and nested using parenthesis.
APPS.CSC_CONDITION_LINE_DETAILS_V·↳ OKC_ACTION_ATTRIBUTES_V·↳ OKC_CONDITION_LINES_V·↳ OKC_PROCESS_DEFS_V·Explore CSC module →
-
Each Condition Line expresses a Boolean condition. Multiple Condition Lines may be and'd or or'd together and nested using parenthesis.
APPS.CSC_CONDITION_LINE_DETAILS_V·↳ OKC_ACTION_ATTRIBUTES_V·↳ OKC_CONDITION_LINES_V·↳ OKC_PROCESS_DEFS_V·Explore CSC module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - CSC Tables and Views 12.2.2
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - CSC Tables and Views 12.1.1
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - CSC Tables and Views 12.2.2
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - CSC Tables and Views 12.1.1
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.