Results for “css_def_prob_categories_b”

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

Overview

CSS_DEF_PROB_CATEGORIES_B is the base table that stores problem category definitions within the Oracle EBS Support (CSS) module. Its documented description is simply "Base table for problem category," identifying it as the foundation record that classifies support problems into categories. The table belongs to the CSS — Support product area, which the ETRM metadata flags as obsolete, and the implementation data explicitly notes "Not implemented in this database." This means the object may not exist in every 12.1.1 or 12.2.2 environment; it is present only where the legacy Support/TeleService schema has been deployed. The ETRM metadata marks the object as heuristic Data Vault hub-leaning, which is a modeling suggestion: the table behaves like a hub because it is keyed by a single surrogate identifier (PROBLEM_CATEGORY_ID) and is referenced by multiple downstream tables rather than being a transaction satellite. This positioning makes it a reference/definition table that anchors category identity and drives lookups elsewhere in the CSS data model.

Key Information Stored

The documented metadata identifies the primary key as CSS_DEF_PROB_CATEGORIES_B_PK, built on the column PROBLEM_CATEGORY_ID. This surrogate key uniquely identifies each problem category row and is the key column propagated into dependent tables. The metadata also documents a foreign key relationship from CSS_DEF_PROB_CATEGORIES_B.WORKFLOW to WF_ITEM_TYPES, which implies the table stores a WORKFLOW column linking each category to the workflow item type used to route or process problems assigned to that category. Beyond PROBLEM_CATEGORY_ID and WORKFLOW, the excerpt does not enumerate the descriptive columns (such as category name, description, or enabled flag), so those are not documented in the provided ETRM excerpt. Where business-key candidates exist, they would typically appear on a name or short-code column, but no unique index other than the primary key is documented here. The "_B" suffix convention in Oracle EBS indicates the base (language-independent) table, suggesting that a corresponding translation table holds the language-specific names and descriptions, although that object is not named in the metadata excerpt.

Common Use Cases and Queries

The principal use case is resolving problem categories for support and incident reporting. A standard join retrieves the category identity for dependent records, for example joining CSS_DEF_PROB_TYPES_B to CSS_DEF_PROB_CATEGORIES_B on PROBLEM_CATEGORY_ID to report problem types grouped by category. Because WORKFLOW references WF_ITEM_TYPES, administrators and developers query the workflow associated with each category to understand how problems are routed, using a join from CSS_DEF_PROB_CATEGORIES_B.WORKFLOW to WF_ITEM_TYPES. Reporting scenarios include category-level counts of problem types, resolution-time definitions, and template matrices, all of which resolve through the shared PROBLEM_CATEGORY_ID. A representative pattern is: SELECT c.PROBLEM_CATEGORY_ID, c.WORKFLOW FROM CSS_DEF_PROB_CATEGORIES_B c WHERE EXISTS (SELECT 1 FROM CSS_DEF_PROB_TYPES_B t WHERE t.PROBLEM_CATEGORY_ID = c.PROBLEM_CATEGORY_ID); Given the obsolete status, any query should first confirm the object exists in the target instance, since the metadata states it is not implemented in all databases.

Related Objects

The FK metadata documents one outbound and three inbound relationships, defining the table's neighbors:

• WF_ITEM_TYPES — referenced by CSS_DEF_PROB_CATEGORIES_B.WORKFLOW, providing the workflow definition tied to each category.
• CSS_DEF_PROB_TYPES_B — references this table via PROBLEM_CATEGORY_ID; it holds problem type definitions grouped under each category.
• CSS_DEF_RES_TIMES — references this table via PROBLEM_CATEGORY_ID; it stores resolution-time definitions scoped per category.
• CSS_DEF_TEMPL_MATRIX — references this table via PROBLEM_CATEGORY_ID; it maintains the mapping matrix of templates by category.

Together these objects form the definitional core of the legacy CSS Support data model, with CSS_DEF_PROB_CATEGORIES_B acting as the reference hub anchoring problem categorization across types, resolution times, and template assignments.