Results for “csc_condition_expression_v”

20 results




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

Overview

The CSC_CONDITION_EXPRESSION_V view is an APPS-owned, VALID database view within the Oracle E-Business Suite Customer Care (CSC) product family. It exposes the parsed and structured representation of condition expressions that drive the rule, eligibility, and qualification logic maintained by the Oracle Knowledge Center (OKC) sub-module. Rather than presenting conditions as opaque text strings, the view decomposes each condition line into its constituent syntactic elements—left operand, relational operator, right operand, logical connectors, and grouping parentheses—thereby rendering the expression logic queryable and reportable.

In Oracle EBS 12.1.1 and 12.2.2, this view serves as a reporting and integration surface for developers and analysts who need to inspect how service entitlements, warranty terms, and customer care business rules are evaluated. It is not a base table; it is a denormalized projection joining condition-line metadata with action-attribute definitions. Because it is a view, it inherits the security and data visibility of the underlying OKC objects and should be treated as read-only.

Underlying Base Objects

The view is defined over two documented base objects, both of which are themselves views:

  • OKC_CONDITION_LINES_V — Supplies the condition-line payload, including the condition header and footer identifiers, sort sequence, description, parenthesis tokens, the relational operator, the right operand, and the logical operator. Aliased as OCL in the view text.
  • OKC_ACTION_ATTRIBUTES_V — Supplies the action-attribute definition that resolves the left-hand operand's name. Aliased as OAA in the view text.

The join predicate is OAA.ID = OCL.AAE_ID, meaning each condition line is matched to its originating action attribute through the AAE_ID foreign key. This relationship establishes the semantic linkage between a rule's manageable attribute (the left value) and the condition expression applied to it. The RESULTANT columns are drawn from OCL, with the single exception of LEFT_VALUE, which is the NAME column of OAA.

Key Columns

  • AAE_ID — The action-attribute identifier; the join key linking a condition line to its attribute.
  • CONDITION_TYPE — A decoded label derived from CNL_TYPE via DECODE: GEX maps to 'EXPRESSION', FEX to 'FUNCTION', and CEX to 'COUNTER'.
  • CNL_TYPE — The raw condition-line type code underlying CONDITION_TYPE.
  • DESCRIPTION — Free-text description of the condition line.
  • PDF_ID / CNH_ID — Identifiers for the associated document and condition header groupings.
  • SORTSEQ — Ordering sequence used to reassemble the expression in the correct reading order.
  • LEFT_PARENTHESIS / RIGHT_PARENTHESIS — Grouping tokens that preserve operator precedence in the expression.
  • LEFT_VALUE — The name of the action attribute acting as the left-hand operand.
  • RELATIONAL_OPERATOR — The comparison operator (for example, equals, greater than, less than) applied between the left value and right operand.
  • RIGHT_OPERAND — The literal or attribute value compared against the left value.
  • LOGICAL_OPERATOR — The connective (AND/OR) joining this line to the next, enabling multi-clause expressions.

Together, SORTSEQ, the parenthesis columns, RELATIONAL_OPERATOR, and LOGICAL_OPERATOR permit the full Boolean expression to be reconstructed from individual rows. The relational_operator column, the term most commonly searched by developers, is the pivotal comparison token in each clause.

Common Use Cases and Queries

Typical scenarios include auditing which attributes are compared using a given relational operator, exporting rule logic for documentation, and troubleshooting why an entitlement or qualification rule did not fire as expected.

  • Listing all conditions that use a specific operator:
SELECT AAE_ID, LEFT_VALUE, RELATIONAL_OPERATOR, RIGHT_OPERAND
FROM   APPS.CSC_CONDITION_EXPRESSION_V
WHERE  RELATIONAL_OPERATOR = '='
ORDER  BY PDF_ID, SORTSEQ;
  • Reconstructing an expression grouped by condition header:
SELECT CNH_ID, SORTSEQ, LEFT_PARENTHESIS, LEFT_VALUE,
       RELATIONAL_OPERATOR, RIGHT_OPERAND, RIGHT_PARENTHESIS,
       LOGICAL_OPERATOR
FROM   APPS.CSC_CONDITION_EXPRESSION_V
WHERE  CNH_ID = :p_cnh_id
ORDER  BY SORTSEQ;
  • Counting condition types to profile rule complexity:
SELECT CONDITION_TYPE, COUNT(*)
FROM   APPS.CSC_CONDITION_EXPRESSION_V
GROUP  BY CONDITION_TYPE;

Because the view conforms to standard APPS naming and joins documented OKC views, it can be safely referenced in custom reports, concurrent programs, and integration extracts without direct dependency on base-table structures.