Search Results csc_prof_checks_b




Overview
Explore in AI Chat

Overview

The CSC_PROF_CHECKS_B table is a core data object within the Oracle E-Business Suite (EBS) Customer Care (CSC) module. It serves as the master repository for profile check definitions, which are fundamental components of the service profiling functionality. Profile checks are configurable rules or conditions used to evaluate service requests, customer accounts, or assets against predefined business criteria. The table's role is to store the structural and control information for each unique check, enabling the system to perform automated assessments that drive service processes, such as entitlement verification, diagnostic routing, and resolution planning. Its "B" suffix indicates it is a base table, primarily holding transactional and seed data that is supplemented by translated descriptive information in its corresponding TL (translation) table.

Key Information Stored

While the provided metadata does not list specific columns, the primary and foreign key relationships define its critical structure. The central column is CHECK_ID, which is the table's primary key and uniquely identifies each profile check definition. Another significant column is SELECT_BLOCK_ID, a foreign key linking the check to a specific profile block defined in CSC_PROF_BLOCKS_B. This relationship suggests that a profile check is often associated with a specific data selection or filtering logic. Other columns in the base table typically store control attributes such as the check's active status, application method, sequencing, creation and last update dates, and the identifier of the last updating user.

Common Use Cases and Queries

This table is central to configuring and executing the service profiling engine. A primary use case involves administrators setting up or modifying the library of checks that the system can apply to service requests. For reporting and analysis, common queries involve listing all active checks or identifying checks associated with a particular service plan. Sample SQL patterns include joining to the translation table to retrieve the check name in a specific language or querying checks linked to a specific profile block.

  • Retrieve active profile checks with descriptions: SELECT b.CHECK_ID, tl.NAME FROM CSC_PROF_CHECKS_B b, CSC_PROF_CHECKS_TL tl WHERE b.CHECK_ID = tl.CHECK_ID AND tl.LANGUAGE = USERENV('LANG') AND b.ENABLED_FLAG = 'Y';
  • Find checks used by a specific service plan: SELECT ph.PLAN_NAME, b.CHECK_ID FROM CSC_PLAN_HEADERS_B ph, CSC_PROF_CHECKS_B b WHERE ph.PROFILE_CHECK_ID = b.CHECK_ID;

Related Objects

The CSC_PROF_CHECKS_B table is a central hub within the profiling schema, with numerous foreign key relationships as documented.

  • CSC_PROF_CHECKS_TL: Stores translated names and descriptions for the check, joined on CHECK_ID.
  • CSC_PROF_BLOCKS_B: Defines the data block a check may use, linked via CSC_PROF_CHECKS_B.SELECT_BLOCK_ID.
  • CSC_PLAN_HEADERS_B: Service plans can reference a specific profile check via CSC_PLAN_HEADERS_B.PROFILE_CHECK_ID.
  • CSC_PROF_CHECK_RATINGS, CSC_PROF_CHECK_RESULTS, CSC_PROF_CHECK_RULES_B, and CSC_PROF_GROUP_CHECKS: These are child tables that store detailed rating logic, execution results, specific rule conditions, and check-group associations, respectively, all linked by the parent CHECK_ID.