Results for “css_def_prob_types_b”

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

Overview

CSS_DEF_PROB_TYPES_B is the base (conceptual) table that stores problem type definitions within the Oracle EBS CSS - Support module. It functions as the primary reference object for categorizing and classifying support problems and defects, allowing the application to differentiate issue types and drive downstream workflow, assignment, and resolution logic. In the EBS 12.1.1 and 12.2.2 release lines, the CSS product family is flagged as obsolete; the ETRM metadata explicitly notes that the object is "Not implemented in this database" for the sampled environment, meaning the table may not exist in every installation. Where it does exist, it retains its original role as a controlled vocabulary of problem types referenced throughout the support schema.

From a Data Vault modeling perspective, the metadata heuristic classifies CSS_DEF_PROB_TYPES_B as hub-leaning. This suggests that the table is best modeled as a hub: a stable, uniquely keyed set of business entities (problem types) identified by a surrogate key, with descriptive attributes potentially distributed to satellite tables. Its relatively small number of inbound foreign keys—four dependent tables—supports treating it as a central, slowly changing reference entity rather than a transactional link.

Key Information Stored

The documented columns for this object are limited, but the structural metadata identifies the following critical elements:

• PROBLEM_TYPE_ID — The surrogate primary key, enforced by the constraint CSS_DEF_PROB_TYPES_B_PK. It uniquely identifies each problem type record and is the column propagated to all four dependent tables.
• PROBLEM_CATEGORY_ID — A foreign key to CSS_DEF_PROB_CATEGORIES_B, establishing the parent-child grouping of problem types within problem categories. This is the primary business-key candidate in terms of classification hierarchy, as it drives categorization logic and reporting rollups.

The base table (_B suffix) typically holds language-independent definition data, with translated descriptions residing in a corresponding _TL table. Descriptive columns such as problem type name, description, and enabled/disabled flags are implied by the design pattern but are not enumerated in the supplied metadata; they should be confirmed against the actual data dictionary in a live instance. The distinction between the surrogate key (PROBLEM_TYPE_ID) and any business-key candidate is important: the surrogate key is stable and referenced by children, while the category assignment (PROBLEM_CATEGORY_ID) carries meaning about the classification hierarchy.

Common Use Cases and Queries

Typical usages center on reference lookups, validation of problem records, and hierarchical reporting by category. A standard lookup joins the type to its category:

• Retrieve all problem types for a given category:
  SELECT pt.problem_type_id, pt.problem_category_id FROM css_def_prob_types_b pt WHERE pt.problem_category_id = :category_id;
• Enumerate defects by problem type to assess issue distribution:
  SELECT d.problem_type_id, COUNT(*) FROM css_def_defects_b d GROUP BY d.problem_type_id;
• Audit configuration changes by joining the audit history table on PROBLEM_TYPE_ID to trace when definitions were amended.
• Report phase coverage by joining CSS_DEF_PROB_TYPE_PHASES to confirm which lifecycle phases are configured per type.

Because the module is marked obsolete, any query should be guarded by checks that the table exists; in most supported 12.1.1/12.2.2 environments, functional equivalents reside in the Service/Depot or other superseding schemas.

Related Objects

The following objects are documented as directly related through primary and foreign key relationships:

• CSS_DEF_PROB_CATEGORIES_B — referenced by CSS_DEF_PROB_TYPES_B via PROBLEM_CATEGORY_ID; parent category definitions.
• CSS_DEF_AUDIT_HISTORY_B — references PROBLEM_TYPE_ID; captures change history for problem type definitions.
• CSS_DEF_DEFECTS_B — references PROBLEM_TYPE_ID; defect records classified by problem type.
• CSS_DEF_PROB_TYPE_PHASES — references PROBLEM_TYPE_ID; maps problem types to workflow phases.
• CSS_DEF_TEMPL_MATRIX — references PROBLEM_TYPE_ID; associates templates with problem types.

These child relationships confirm the table's hub role and its centrality to the CSS support data model, notwithstanding the module's obsolete status.