Search Results css_def_prob_type_phases




Overview
Explore in AI Chat

Overview

The CSS_DEF_PROB_TYPE_PHASES table is a core intersection entity within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Support (CSS) module, which is documented as obsolete. It functions as a many-to-many resolution table, defining the permissible relationships between defined problem types and defined phases in the support process. Its primary role is to enforce business rules by controlling which phases are valid and available for a given type of service request or problem. This configuration is essential for structuring and standardizing the workflow lifecycle of support cases, ensuring that case progression follows a predefined, type-specific path.

Key Information Stored

The table's structure is designed to manage the association between two key entities. The most critical columns are the foreign keys that create this link. The PROBLEM_TYPE_ID column references a specific record in CSS_DEF_PROB_TYPES_B, identifying the category or classification of a support issue. The PHASE_ID column references a specific record in CSS_DEF_PHASES_B, identifying a stage in the support workflow. The primary key, PROB_TYPE_PHASE_ID, is a unique identifier for each association record. Each row effectively stores a single rule stating that a particular problem type can utilize a particular phase.

Common Use Cases and Queries

The primary use case is the validation and presentation of available phases during case management. When a support agent creates or updates a case of a specific problem type, the application queries this table to determine the next valid phases for the workflow. A common reporting need is to audit the phase configuration for all problem types. A sample query to list all associations would be:

  • SELECT pt.PROBLEM_TYPE_NAME, p.PHASE_NAME
  • FROM CSS_DEF_PROB_TYPE_PHASES ptp,
  • CSS_DEF_PROB_TYPES_B pt,
  • CSS_DEF_PHASES_B p
  • WHERE ptp.PROBLEM_TYPE_ID = pt.PROBLEM_TYPE_ID
  • AND ptp.PHASE_ID = p.PHASE_ID
  • ORDER BY pt.PROBLEM_TYPE_NAME, p.SEQUENCE_NUMBER;

Administrative use cases include seeding reference data for new problem types or modifying the lifecycle by adding or removing phase associations.

Related Objects

This intersection table has direct dependencies on two primary base tables, as defined by its foreign key constraints. The relationship with CSS_DEF_PROB_TYPES_B is established via the PROBLEM_TYPE_ID column, linking to the definition of problem categories. The relationship with CSS_DEF_PHASES_B is established via the PHASE_ID column, linking to the definition of workflow stages. The table is central to any data model or process that requires understanding the configured lifecycle for a support case type. Given the module's obsolete status, direct transactional integration with newer service management functionalities may be limited.