Results for “css_def_priorities_b”

10 results




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

Overview

CSS_DEF_PRIORITIES_B is a reference (lookup) table within the Oracle E-Business Suite CSS – Support module, which is now classified as obsolete. Its documented purpose is to hold the set of defect and enhancement priority definitions used by the support organization. Each priority represents an indication of the internal urgency or importance assigned to resolving a defect or enhancement tracked in the system. The table therefore functions as a control list rather than a transactional store: defect records capture their priority by pointing back to a row in this table, giving a stable, enumerated set of priority values that can be reused across many defect and audit records.

In Data Vault modeling terms, the mined relationship structure classifies this object as hub-leaning. That is a modeling suggestion only: the table behaves like a hub because it is keyed by a single surrogate identifier and is referenced by multiple dependent tables, rather than carrying descriptive change history. Priority codes and descriptions associated with the key would, in a strict Data Vault design, be placed on a satellite attached to that hub.

Key Information Stored

The ETRM metadata for this object is deliberately narrow. The documented structural elements are:

  • PRIORITY_ID — the surrogate primary key, enforced by the constraint CSS_DEF_PRIORITIES_B_PK. This is the single documented key column and is the value referenced by dependent defect and audit tables.
  • CSS_DEF_PRIORITIES_B_PK — the primary key constraint defined on PRIORITY_ID. It is the only uniqueness definition documented for this table; no separate unique-index business-key candidate is recorded in the metadata.
  • Referenced-column role — PRIORITY_ID serves both as the table's own key and as the foreign key column in CSS_DEF_DEFECTS_B and CSS_DEF_AUDIT_HISTORY_B, making it the join column for every relationship documented for this table.

No additional descriptive columns (such as priority code, name, rank, or enabled flag) are enumerated in the supplied ETRM excerpt. The metadata notes that the object is "Not implemented in this database," indicating that in the environment documented, this reference table was not deployed. Because the "_B" suffix in EBS convention typically denotes the base (translation-independent) table, any display text for priorities would ordinarily reside on a companion "_TL" table. The supplied metadata does not document such a table, so that pairing is stated here as convention rather than as a recorded fact.

Common Use Cases and Queries

Typical uses center on decoding the priority identifier stored on defects and on auditing priority assignments. A basic lookup joins the defect table to the priority reference on the shared key:

  • Decoding priority on open defects — select defect identifiers and join CSS_DEF_DEFECTS_B to CSS_DEF_PRIORITIES_B on PRIORITY_ID to resolve each defect's priority.
  • Priority distribution reporting — group counts of defects by PRIORITY_ID to show how work is distributed across priority levels.
  • Reassignment and change auditing — join CSS_DEF_AUDIT_HISTORY_B to this table on PRIORITY_ID to reconstruct how priorities changed over time.
  • Validation and orphan detection — identify defects or audit rows whose PRIORITY_ID has no matching row here, indicating a broken reference.

Because the table is documented as obsolete and not implemented, any such reporting should first confirm the table exists and is populated in the target instance; where it is absent, priority lookups may have been replaced by a successor reference object.

Related Objects

The documented foreign-key relationships identify the objects that depend on this table. Both reference PRIORITY_ID as a foreign key column:

  • CSS_DEF_DEFECTS_B — holds defect and enhancement records; CSS_DEF_DEFECTS_B.PRIORITY_ID references CSS_DEF_PRIORITIES_B.
  • CSS_DEF_AUDIT_HISTORY_B — records audit history of defect changes; CSS_DEF_AUDIT_HISTORY_B.PRIORITY_ID references CSS_DEF_PRIORITIES_B.
  • CSS_DEF_PRIORITIES_B_PK — the primary key constraint providing the referenced key for both relationships.

No views, PL/SQL APIs, or additional dependent tables are documented in the supplied metadata. Practically, these two child tables are the significant consumers of this reference data, and they are reached exclusively through the PRIORITY_ID column.