Results for “css_def_prob_type_phases”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSS_DEF_PROB_TYPE_PHASES is a Support (CSS) module intersection table in Oracle EBS Release 12.1.1 and 12.2.2. Its documented purpose is to serve as the intersection table between CSS_DEF_PROB_TYPES_B and CSS_DEF_PHASES_B, resolving a many-to-many relationship between defined problem types and defined phases. In the service request and problem-management data model, such intersection tables allow a single problem type to be associated with multiple lifecycle phases, and a single phase to be reused across multiple problem types, without duplicating either definition entity.
The ETRM metadata classifies this object under the CSS - Support product and flags it as obsolete. The metadata further states "Not implemented in this database," indicating the table is not physically present in the environment sampled for the reference documentation. Its heuristic Data Vault classification, mined from the foreign-key structure, is link. This is consistent with its role: it holds no descriptive attributes of its own and exists solely to record associations between two hub-like definition tables.
Key Information Stored
The documented metadata identifies only the key columns of this table; no descriptive or audit columns are enumerated. The essential columns are:
- PROB_TYPE_PHASE_ID — the surrogate primary key, defined by the constraint CSS_DEF_PROB_TYPE_PHASES_PK. It uniquely identifies each association row.
- PHASE_ID — the foreign key to CSS_DEF_PHASES_B (CSS_DEF_PROB_TYPE_PHASES.PHASE_ID → CSS_DEF_PHASES_B). It identifies the phase participating in the association.
- PROBLEM_TYPE_ID — the foreign key to CSS_DEF_PROB_TYPES_B (CSS_DEF_PROB_TYPE_PHASES.PROBLEM_TYPE_ID → CSS_DEF_PROB_TYPES_B). It identifies the problem type participating in the association.
Because the table is a pure intersection (link) entity, its business-key candidate is the composite of PHASE_ID and PROBLEM_TYPE_ID, which the implementing system would typically protect with a unique index to prevent duplicate associations. No unique index is documented in the supplied metadata, so the composite-uniqueness assumption is a modeling expectation rather than a documented constraint. No non-key attribute columns are documented.
Common Use Cases and Queries
The primary use case is resolving which phases apply to a given problem type, and conversely which problem types use a given phase. A typical query joins the intersection to one or both definition tables:
- Listing phases for a problem type: select from CSS_DEF_PROB_TYPE_PHASES ptp joined to CSS_DEF_PHASES_B p on ptp.PHASE_ID = p.PHASE_ID, filtered by ptp.PROBLEM_TYPE_ID.
- Listing problem types for a phase: the same join filtered by ptp.PHASE_ID.
- Detecting orphaned or missing associations when validating the service-request setup configuration.
- Reporting on definition coverage: counting phases per problem type to identify problem types with no phase configuration.
Standard pattern: SELECT ptp.PROBLEM_TYPE_ID, ptp.PHASE_ID FROM CSS_DEF_PROB_TYPE_PHASES ptp WHERE ptp.PROBLEM_TYPE_ID = :problem_type_id;. Because the object is obsolete and not implemented, queries should be validated against the target instance before use, and its columns should not be treated as part of a supported customization surface.
Related Objects
The following objects are most significant to this table, based on the documented foreign-key relationships and its intersection role:
- CSS_DEF_PROB_TYPES_B — parent definition table for problem types; joined via CSS_DEF_PROB_TYPE_PHASES.PROBLEM_TYPE_ID.
- CSS_DEF_PHASES_B — parent definition table for phases; joined via CSS_DEF_PROB_TYPE_PHASES.PHASE_ID.
- CSS_DEF_PROB_TYPE_PHASES_PK — the primary-key constraint on PROB_TYPE_PHASE_ID that governs row uniqueness.
- Translations and dependent definition tables in the same CSS_DEF family, which supply descriptive text for the parent definition rows referenced by the two foreign keys.
Given its obsolete status and the "not implemented" note, integration or reporting solutions should confirm physical presence and current usage before relying on this object.
-
Intersection table between CSS_DEF_PROB_TYPES_B and CSS_DEF_PHASES_B
Not implemented in this database·Explore CSS module →
-
Intersection table between CSS_DEF_PROB_TYPES_B and CSS_DEF_PHASES_B
Not implemented in this database·Explore CSS module →
-
12.2.2 FND Design Data 12.2.2
-
Table: CSS_DEF_PHASES_B 12.1.1
Base table for phases definition
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_PHASES_B 12.2.2
Base table for phases definition
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_PROB_TYPES_B 12.1.1
Base table for problem types
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_PROB_TYPES_B 12.2.2
Base table for problem types
Not implemented in this database·Explore CSS module →
-
12.1.1 FND Design Data 12.1.1
-
Defect information without resource information
Not implemented in this database·Explore CSS module →
-
Defect information without resource information
Not implemented in this database·Explore CSS module →