Results for “css_def_statuses_b”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSS_DEF_STATUSES_B is a foundational reference table within the Oracle E-Business Suite (EBS) Support module (application short name CSS), historically associated with the defect and enhancement tracking functionality that preceded and underpinned later Oracle Applications support tooling. The physical table is not implemented in a standard EBS 12.1.1 or 12.2.2 environment, as reflected explicitly in the documented metadata; it is catalogued in ETRM (E-Business Suite Tables and Relationships) for completeness and cross-reference purposes. Its business purpose is to store Reasons, also described as Phase Statuses. When a user selects a reason while updating a defect or enhancement, that reason drives attribute-level effects on the parent record — for example, changing an assigned phase, altering classification, or triggering downstream workflow logic.
From a modeling perspective, the mined relationship data suggests a hub-leaning Data Vault classification. The table carries a single documented primary key (STATUS_ID) and is referenced by three dependent tables, which is consistent with a durable business key list rather than a transactional satellite. Practitioners should treat this as a modelling suggestion rather than an authoritative classification; in a classic EBS relational design, CSS_DEF_STATUSES_B functions as a master reference (lookup) table.
Key Information Stored
The documented ETRM metadata for CSS_DEF_STATUSES_B is deliberately sparse. The following attributes are the only ones named in the source and are therefore the only columns that can be asserted with confidence:
- STATUS_ID — The single documented column. It serves as the surrogate primary key defined by the constraint CSS_DEF_STATUSES_B_PK, and simultaneously functions as the business key through which all referencing tables resolve their foreign keys. Because STATUS_ID is the sole identified column, it is both the surrogate identifier and the join anchor: every relationship documented for this object — with CSS_DEF_AUDIT_HISTORY_B, CSS_DEF_DEFECTS_B, and CSS_DEF_PHASE_STATUSES — is established on this one column.
Conventionally, the trailing _B suffix in EBS table naming indicates a base (translation-independent) table, and such tables are typically accompanied by a _TL companion holding translatable text columns (for example a status or reason name and description) keyed by STATUS_ID plus LANGUAGE. The metadata provided here does not document such a companion table, so this should be verified directly against the data dictionary before it is relied upon. The substantive descriptive content — the reason names and descriptions visible to users — would reside in that translation layer, not in _B itself.
Common Use Cases and Queries
The principal analytical and administrative use cases centre on decoding status identifiers into human-readable reasons and on tracing the propagation of status changes through defect and enhancement records.
- Decoding status values. A defect report query joins CSS_DEF_DEFECTS_B to this table on STATUS_ID to render the reason rather than the numeric identifier:
SELECT d.*, s.status_id FROM css_def_defects_b d, css_def_statuses_b s WHERE d.status_id = s.status_id; - Audit reconstruction. Because CSS_DEF_AUDIT_HISTORY_B carries STATUS_ID, audit trails can be resolved to reasons, supporting "who moved this defect, and why" reporting.
- Phase mapping verification. CSS_DEF_PHASE_STATUSES links phases to statuses; querying it alongside this table validates that every reason is associated with an expected process phase, which is useful during configuration review or data migration.
- Population and lineage checks. Since the table is documented as not implemented in a standard database, a validation query across ALL_TABLES / DBA_TABLES should precede any attempt to query it in a given environment.
Reporting use cases are narrow given the obsolete status of the module, but the table remains relevant to historical data analysis, upgrade impact assessment, and environment comparison.
Related Objects
The documented relationships are as follows, all keyed on STATUS_ID:
- CSS_DEF_DEFECTS_B — Defect records; foreign key DEFECTS_B.STATUS_ID references this table. This is the primary transactional consumer of reason values.
- CSS_DEF_AUDIT_HISTORY_B — Historical audit records; AUDIT_HISTORY_B.STATUS_ID references this table, enabling reason resolution across change history.
- CSS_DEF_PHASE_STATUSES — Associative table linking phases to statuses; PHASE_STATUSES.STATUS_ID references this table. This is the object that operationalises the "Phase Statuses" description.
- CSS_DEF_STATUSES_B_PK — The documented primary key constraint on STATUS_ID.
No views or PL/SQL APIs are named in the supplied metadata. Because the CSS Support module is marked obsolete, the most significant "related object" in practice is the ETRM catalogue entry itself, which is frequently the only surviving reference for installations that no longer contain the physical table.
-
Table: CSS_DEF_STATUSES_B 12.2.2
The table store Reasons (Phases Statuses). Attributes of the Defect or Enhancement may be effected by selecting a Reason.
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_STATUSES_B 12.1.1
The table store Reasons (Phases Statuses). Attributes of the Defect or Enhancement may be effected by selecting a Reason.
Not implemented in this database·Explore CSS module →
-
12.2.2 FND Design Data 12.2.2
-
Intersection table between CSS_DEF_PHASES_B and CSS_DEF_REASONS_B. This maps a Reason (Phases Status) to a Phase.
Not implemented in this database·Explore CSS module →
-
Intersection table between CSS_DEF_PHASES_B and CSS_DEF_REASONS_B. This maps a Reason (Phases Status) to a Phase.
Not implemented in this database·Explore CSS module →
-
Not implemented in this database·Explore CSS module →
-
Not implemented in this database·Explore CSS module →
-
12.1.1 FND Design Data 12.1.1
-
Table: CSS_DEF_DEFECTS_B 12.2.2
Not implemented in this database·Explore CSS module →
-
Table: CSS_DEF_DEFECTS_B 12.1.1
Not implemented in this database·Explore CSS module →
-
View: CSS_DEF_STATUSES_VL 12.1.1
Not implemented in this database·Explore CSS module →
-
View: CSS_DEF_STATUSES_VL 12.2.2
Not implemented in this database·Explore CSS module →