Results for “csc_prof_check_rules_tl”

49 results




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

Overview

CSC_PROF_CHECK_RULES_TL is the translation (language) table associated with the Oracle Customer Care (CSC) profile check rule engine. The base table, CSC_PROF_CHECK_RULES_B, stores the conditions used by the profile check process; the _TL table holds the language-specific and translated content for those rules, allowing expressions and rule text to be presented in the user's preferred language. In Oracle EBS 12.1.1 and 12.2.2, this object resides in the CSC schema and is owned by the CSC - Customer Care product, with a VALID status.

Under a heuristic Data Vault classification mined from the foreign-key structure, this object is satellite-leaning. It aggregates descriptive, language-dependent attributes that hang off the rule entity defined by CSC_PROF_CHECK_RULES_B, which functions as the referenced parent (hub-like) entity. Modeling this as a satellite keyed to its business parent is a reasonable suggestion for warehouse-style designs, though it is a heuristic inference rather than a mandated EBS construct.

Key Information Stored

The table contains 12 documented columns. The most important are summarized below, distinguishing the composite primary key from business-key candidates where documented.

  • CHECK_ID — Identifier of the profile check rule to which the translation belongs; also part of the foreign key to CSC_PROF_CHECK_RULES_B.
  • SEQUENCE — Ordering component identifying a specific rule line or condition within the check; part of the primary key and the parent foreign key.
  • LANGUAGE — The language code for the translated row; a core member of the primary key.
  • SOURCE_LANG — The source language from which the translation originates.
  • EXPRESSION — The language-specific expression or condition text used by the profile check engine.
  • ZD_EDITION_NAME — Editioning column used by EBS 12.2.2 edition-based redefinition; part of the unique index CSC_PROF_CHECK_RULES_TL_U1.
  • SECURITY_GROUP_ID — Multi-tenant/security grouping attribute, with a foreign key to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each row and when.

The documented primary key is CSCPCRTL_PK over (CHECK_ID, SEQUENCE, LANGUAGE). The unique index CSC_PROF_CHECK_RULES_TL_U1 over (CHECK_ID, SEQUENCE, LANGUAGE, ZD_EDITION_NAME) represents the business-key candidate, adding the editioning column to the natural translation key.

Common Use Cases and Queries

Typical use cases center on retrieving translated rule conditions, auditing rule configuration, and joining translations to their base definitions. A common pattern joins the translation table to the base table on the composite key:

  • Reporting translated rule expressions for a given language: SELECT b.check_id, t.expression FROM csc_prof_check_rules_b b, csc_prof_check_rules_tl t WHERE b.check_id = t.check_id AND b.sequence = t.sequence AND t.language = :lang.
  • Auditing recently modified rule translations by filtering on LAST_UPDATE_DATE.
  • Verifying translation completeness by comparing COUNT of _B rows against _TL rows per LANGUAGE.
  • Security-scoped extracts filtered on SECURITY_GROUP_ID.

Because the table is edition-enabled in 12.2.2, queries should account for ZD_EDITION_NAME when running under edition-based redefinition.

Related Objects

The following objects are most significant in relation to CSC_PROF_CHECK_RULES_TL, based on the documented relationships:

  • CSC_PROF_CHECK_RULES_B — Parent base table; joined on CHECK_ID and SEQUENCE. Held the untranslated rule conditions.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, governing access scoping of rules.
  • CSC_PROF_CHECK_RULES_TL_U1 — Unique index providing the business-key candidate for the table.
  • CSCPCRTL_PK — Primary key constraint over (CHECK_ID, SEQUENCE, LANGUAGE).

Additional CSC profile-check configuration and execution objects depend on the rule definitions surfaced through this translation layer at runtime.