Results for “css_def_phase_statuses”

8 results




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

Overview

CSS_DEF_PHASE_STATUSES is an intersection (cross-reference) table within the Oracle E-Business Suite CSS - Support module. Its documented purpose is to map a "Reason" (described in the metadata as a phase status) to a Phase. Specifically, it sits between CSS_DEF_PHASES_B and CSS_DEF_REASONS_B and, per the documented foreign keys, resolves the many-to-many relationship between phases (CSS_DEF_PHASES_B) and statuses (CSS_DEF_STATUSES_B). Each row represents one valid combination of a phase and a status, allowing the application to enumerate which phase statuses (reasons) are permissible for a given phase.

The module is flagged as obsolete in the ETRM metadata, and the object is explicitly noted as "Not implemented in this database." This indicates that in the referenced 12.1.1 / 12.2.2 environment the table may not exist, may be empty, or may be a legacy artifact retained only for historical or migration purposes. Under the heuristic Data Vault classification supplied in the metadata, this object is best modeled as a link table: its sole structural role is to associate two independent business entities (Phase and Status) through foreign key references, which is the canonical signature of a link (intersection) construct.

Key Information Stored

The documented metadata exposes a deliberately small set of columns, consistent with a pure intersection table. The most important elements are:

  • PHASE_STATUS_ID — The surrogate primary key, defined by the constraint CSS_DEF_PHASE_STATUSES_PK. It uniquely identifies each phase-to-status association and provides the stable internal identifier used by foreign key references from dependent objects.
  • PHASE_ID — A foreign key to CSS_DEF_PHASES_B. This is the business-key candidate on the phase side, anchoring each row to a specific phase definition.
  • STATUS_ID — A foreign key to CSS_DEF_STATUSES_B. This is the business-key candidate on the status side, anchoring each row to a specific status (reason) definition.

Because the metadata documents no additional descriptive columns, the unique combination of PHASE_ID and STATUS_ID functions as the natural (business) unique key, while PHASE_STATUS_ID serves as the surrogate primary key. The absence of date, flag, or attribute columns reinforces the interpretation that this is a link-only structure that carries no satellite attributes of its own.

Common Use Cases and Queries

The primary use case is determining which statuses (reasons) are valid for a given phase, and conversely which phases permit a given status. Reporting typically joins the intersection table to both parent tables to resolve names and descriptions. A representative query pattern is:

  • Statuses for a phase: SELECT s.* FROM css_def_phase_statuses ps, css_def_statuses_b s WHERE ps.status_id = s.status_id AND ps.phase_id = :phase_id;
  • Phases for a status: SELECT p.* FROM css_def_phase_statuses ps, css_def_phases_b p WHERE ps.phase_id = p.phase_id AND ps.status_id = :status_id;
  • Validation of allowable combinations prior to inserting a support event, phase transition, or status change.
  • Data-quality reconciliation to detect orphaned associations whose parent records have been purged.

Given the obsolete status, any extract or integration should treat results defensively and confirm row counts before relying on this table as an authoritative source.

Related Objects

The significant related objects, grounded in the documented foreign keys, are:

  • CSS_DEF_PHASES_B — joined via CSS_DEF_PHASE_STATUSES.PHASE_ID = CSS_DEF_PHASES_B.PHASE_ID.
  • CSS_DEF_STATUSES_B — joined via CSS_DEF_PHASE_STATUSES.STATUS_ID = CSS_DEF_STATUSES_B.STATUS_ID.
  • CSS_DEF_REASONS_B — the reason definition referenced conceptually by the mapping per the object description.
  • CSS_DEF_PHASE_STATUSES_PK — the primary key constraint enforcing uniqueness on PHASE_STATUS_ID.
  • CSS_DEF_PHASES_B and CSS_DEF_STATUSES_B dependent views or APIs that consume this mapping to drive phase transition logic.

Collectively, these objects form the reference-data backbone for phase/status configuration in the legacy CSS - Support schema.