Results for “css_def_phases_b”

14 results




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

Overview

CSS_DEF_PHASES_B is the base definition table for phases within the CSS (Support) product family in Oracle EBS 12.1.1 and 12.2.2. It stores the master records for phase definitions that are used throughout the support and defect-tracking data model. The table is documented as belonging to the "CSS - Support (Obsolete)" module, meaning that in current releases the feature area is no longer actively implemented. The ETRM metadata explicitly records "Not implemented in this database," indicating that the object may exist only as a residual definition in certain environments or may be absent entirely from a fresh 12.2.2 installation.

From a modeling perspective, the mined Data Vault classification for this table is hub-leaning. This reflects its role as a definition/master table: it holds a single row per phase, identified by a surrogate PHASE_ID, and is referenced by multiple dependent tables through foreign keys. In Data Vault terms it behaves as a hub, with the dependent tables acting as satellites or links capturing status, defect, and problem-type associations. This classification is a heuristic suggestion rather than a documented EBS attribute.

Key Information Stored

The documented metadata identifies the following structural elements as the most significant:

  • PHASE_ID — The surrogate primary key, defined by the constraint CSS_DEF_PHASES_B_PK. It uniquely identifies each phase definition row and is the column referenced by every foreign key from dependent tables.
  • Phase definition attributes — Because the table is the "base table for phases definition," it stores the descriptive and controlling attributes of a phase. In the CSS Support model these typically include a phase name, a phase code or short identifier, a status or enabled flag, sequence or ordering information, and effective-date or audit columns. The ETRM excerpt does not enumerate these non-key columns; only PHASE_ID is explicitly confirmed.

No alternate unique key or business-key candidate is documented in the provided metadata, so PHASE_ID should be treated as the sole confirmed unique identifier. Business-key candidates such as a phase code or name are not evidenced here and should be verified directly against the database dictionary before reliance.

Common Use Cases and Queries

Because the table is obsolete and often "not implemented," the primary practical use is historical analysis, data lineage, and migration assessment rather than day-to-day transaction processing. Typical scenarios include:

  • Identifying orphaned or dependent records during a purge or migration of legacy CSS Support data.
  • Reconstructing phase definitions referenced by defects, audit history, or problem-type mappings.
  • Confirming whether the object exists before running upgrade scripts in 12.2.2.

A representative lookup joins the base table to its dependent defect table:

  • SELECT p.phase_id, d.* FROM css_def_phases_b p, css_def_defects_b d WHERE p.phase_id = d.phase_id;

To enumerate all dependents of a phase, query the child tables by PHASE_ID against CSS_DEF_AUDIT_HISTORY_B, CSS_DEF_DEFECTS_B, CSS_DEF_PHASE_STATUSES, and CSS_DEF_PROB_TYPE_PHASES. If the table reports no rows, verify existence with a dictionary query against ALL_TABLES before assuming a data issue.

Related Objects

The documented foreign key relationships identify the most significant dependent objects, all joined on PHASE_ID:

  • CSS_DEF_AUDIT_HISTORY_B — references CSS_DEF_PHASES_B.PHASE_ID, capturing audit history for phase definitions.
  • CSS_DEF_DEFECTS_B — references PHASE_ID, associating defects with the phase in which they were recorded.
  • CSS_DEF_PHASE_STATUSES — references PHASE_ID, holding status values applicable to each phase.
  • CSS_DEF_PROB_TYPE_PHASES — references PHASE_ID, mapping problem types to phases.
  • CSS_DEF_PHASES_B_PK — the primary key constraint on PHASE_ID that governs all of the above joins.

These four child tables constitute the core dependency set. Because each is joined solely through PHASE_ID, any deletion or renumbering of phase records must account for referential integrity across all four.