Results for “css_def_audit_history_b”

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

Overview

The table CSS_DEF_AUDIT_HISTORY_B belongs to the CSS – Support product family in Oracle E-Business Suite. In both Release 12.1.1 and 12.2.2, this module is classified as obsolete, meaning it is retained for backward compatibility and historical reference rather than active functional use. The object functions as an audit trail repository for defect records maintained by the legacy CSS defect tracking subsystem. Its purpose is to capture the sequence of state changes applied to a defect header record, recording who performed each change, when it occurred, and which attribute values were applied at that point in time.

The ETRM metadata indicates that this table is not implemented in the reference database, which is consistent with its obsolete status. The primary key is CSS_DEF_AUDIT_HISTORY_B_PK, defined on the AUDIT_HISTORY_ID column. Based on the foreign key topology, the Data Vault classification mined from the metadata leans toward a satellite pattern: the table carries a surrogate key, references a parent defect entity, and records descriptive change context rather than acting as an independent hub or associative link. This classification is a modeling suggestion derived from FK structure alone.

Key Information Stored

The most significant columns documented for this table are the following:

• AUDIT_HISTORY_ID — surrogate primary key that uniquely identifies each audit history row.
• DEFECT_ID — reference to the parent defect in CSS_DEF_DEFECTS_B; this is the principal business-key candidate, since audit rows are meaningful only in the context of their defect.
• ORIGINATING_CUSTOMER_ID — the customer party associated with the defect, referencing HZ_PARTIES.
• FILER_ID — the FND user who originally filed the defect.
• UPDATED_BY_ID — the FND user responsible for the change captured by the row.
• PROBLEM_TYPE_ID, PHASE_ID, STATUS_ID, SEVERITY_ID, PRIORITY_ID — classification attributes whose values at the time of the audit event are preserved via their respective _B lookup tables.
• TERRITORY_ID — the sales or support territory associated with the defect, referencing JTF_TERR_ALL.

The surrogate key distinguishes each audit event, while the combination of DEFECT_ID and related descriptive columns forms the effective business context for reporting change history.

Common Use Cases and Queries

Typical usage centers on historical analysis of defect lifecycle transitions. A representative query retrieves the complete audit trail for a defect:

• SELECT h.audit_history_id, h.defect_id, h.status_id, h.severity_id, h.updated_by_id FROM css_def_audit_history_b h WHERE h.defect_id = :defect_id ORDER BY h.audit_history_id;
• Join to CSS_DEF_STATUSES_B, CSS_DEF_SEVERITIES_B, and CSS_DEF_PRIORITIES_B to translate lookup IDs into user-readable values.
• Join to FND_USER on UPDATED_BY_ID to attribute changes to named users for audit reporting.
• Join to HZ_PARTIES on ORIGINATING_CUSTOMER_ID to report defects by customer account.

Because the module is obsolete and the table is not implemented in the reference database, these patterns apply primarily to legacy data migration, archival extraction, or historical reconciliation efforts.

Related Objects

• CSS_DEF_DEFECTS_B — parent defect entity, joined on DEFECT_ID.
• CSS_DEF_AUDIT_COLUMNS_B — child table referencing this object via AUDIT_HISTORY_ID; holds column-level audit detail.
• HZ_PARTIES — customer party lookup, joined on ORIGINATING_CUSTOMER_ID.
• FND_USER — joined on FILER_ID and UPDATED_BY_ID for user attribution.
• CSS_DEF_STATUSES_B, CSS_DEF_SEVERITIES_B, CSS_DEF_PRIORITIES_B, CSS_DEF_PHASES_B, CSS_DEF_PROB_TYPES_B — lookup tables referenced by the corresponding ID columns.
• JTF_TERR_ALL — territory reference, joined on TERRITORY_ID.