Results for “csc_prof_check_rules_vl”

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

Overview

CSC_PROF_CHECK_RULES_VL is a Multi-Language Support (MLS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a member of the CSC (Customer Care) product family and is reported by ETRM as VALID. The view is defined as the MLS-enabled presentation layer over the base tables CSC_PROF_CHECK_RULES_B and CSC_PROF_CHECK_RULES_TL, and it is the data source for the Profile Checks tab within the Customer Profile Setup form. In EBS terms, the view supplies the translated, user-facing definition of the validation rules that determine whether a customer profile passes or fails a given check.

Because the "_VL" suffix denotes a view that joins the "_B" (base) and "_TL" (translation) tables while filtering the translation by the session language, this view exposes one row per rule per language rather than one row per rule per installation. In reporting and integration scenarios, it provides a stable, joined interface that hides the underlying MLS mechanics from consuming tools such as Oracle Reports, BI Publisher, Discoverer, or custom PL/SQL.

Underlying Base Objects

ETRM documents two referenced base objects, both exposed to the APPS schema as synonyms:

• CSC_PROF_CHECK_RULES_B — the base table holding language-independent rule attributes.
• CSC_PROF_CHECK_RULES_TL — the translation table holding language-dependent text.

The view text is a straight join of these two objects on CHECK_ID and SEQUENCE, with the translation side additionally filtered by T.LANGUAGE = USERENV('LANG'). This constraint is what restricts each logical rule to a single, session-appropriate translation, giving the view its MLS semantics. Columns such as LOGICAL_OPERATOR, LEFT_PAREN, BLOCK_ID, COMPARISON_OPERATOR, and RIGHT_PAREN are drawn from the B table, while the descriptive text column EXPRESSION is drawn from the TL table.

Key Columns

The view exposes sixteen columns. The most significant are:

• ROW_ID — the ROWID of the underlying base table row, emitted as the first projected column.
• CHECK_ID — primary identifier of the profile check; also the join key to the TL table.
• SEQUENCE — ordinal position of the rule within its check and the second join key.
• EXPRESSION — the translated expression text presented to the user (from the TL table).
• LOGICAL_OPERATOR, COMPARISON_OPERATOR — operators used to combine or evaluate rule fragments.
• LEFT_PAREN, RIGHT_PAREN — parenthetical grouping indicators. The user search term "left_paren" maps directly to this column, which records the opening parenthesis (or its absence) in the rule expression.
• BLOCK_ID, EXPR_TO_BLOCK_ID, BLOCK_ID — identifiers linking the rule to the profile block it validates.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical scenarios include extracting the rule set for a profile check, auditing parenthetical grouping logic, and joining rules to blocks for reporting. A representative query is:

SELECT check_id,
       sequence,
       left_paren,
       logical_operator,
       expression,
       comparison_operator,
       right_paren
  FROM apps.csc_prof_check_rules_vl
 WHERE check_id = :p_check_id
 ORDER BY sequence;

To isolate rules that use parentheses (the "left_paren" search intent):

SELECT check_id, sequence, left_paren, right_paren, expression
  FROM apps.csc_prof_check_rules_vl
 WHERE left_paren IS NOT NULL
    OR right_paren IS NOT NULL;

Because the view is MLS-filtered, no explicit language predicate is required; USERENV('LANG') resolves the correct translation automatically. All access should be granted through the APPS schema synonym.