Search Results css_def_phase_statuses_pk

Overview

The CSS_DEF_PHASE_STATUSES table is a core intersection, or mapping, table within the Oracle E-Business Suite (EBS) CSS (Support) module. Its primary role is to define the valid statuses (reasons) that can be applied to a given service request or support phase. It establishes a many-to-many relationship between the phases defined in CSS_DEF_PHASES_B and the status reasons defined in CSS_DEF_STATUSES_B. This mapping is critical for enforcing business rules and maintaining data integrity within the support lifecycle, ensuring that only appropriate status transitions are available for each phase. It is important to note that the ETRM metadata explicitly marks the CSS - Support module as "obsolete" and states the table is "Not implemented in this database," indicating it may be part of a legacy or deprecated data model in versions 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to manage the relationship between phases and statuses. The key columns are its primary key and the two foreign key columns that create the intersection. The PHASE_STATUS_ID column serves as the unique primary key identifier for each specific phase-status mapping record. The PHASE_ID column is a foreign key that references a specific phase record in the CSS_DEF_PHASES_B table. The STATUS_ID column is a foreign key that references a specific status reason record in the CSS_DEF_STATUSES_B table. Together, a row in this table authorizes the use of a particular STATUS_ID for a given PHASE_ID.

Common Use Cases and Queries

The primary use case for this table is to query the list of valid statuses for a support phase, either for application logic or for reporting on phase-status rules. A common operational query would retrieve all allowable statuses for a specific phase name to populate a list of values (LOV) in the application's user interface. For analytical reporting, one might join this table to phase and status descriptions to document the configured support workflow rules. A sample query pattern is:

• SELECT p.PHASE_NAME, s.STATUS_NAME
• FROM CSS_DEF_PHASE_STATUSES ps,
• CSS_DEF_PHASES_B p,
• CSS_DEF_STATUSES_B s
• WHERE ps.PHASE_ID = p.PHASE_ID
• AND ps.STATUS_ID = s.STATUS_ID
• ORDER BY p.PHASE_NAME;

Related Objects

CSS_DEF_PHASE_STATUSES is centrally connected to two key definition tables via foreign key constraints, as documented in the provided ETRM metadata. It directly references the CSS_DEF_PHASES_B table on the column CSS_DEF_PHASE_STATUSES.PHASE_ID. It also directly references the CSS_DEF_STATUSES_B table on the column CSS_DEF_PHASE_STATUSES.STATUS_ID. These relationships are fundamental, as the table has no purpose without these parent entities. The table itself is referenced by its primary key constraint, CSS_DEF_PHASE_STATUSES_PK, on the PHASE_STATUS_ID column. Given its role as a mapping table, it is likely referenced by various application programming interfaces (APIs) and user interfaces within the obsolete Support module to validate status updates.