Search Results css_def_audit_columns_b

Overview

The CSS_DEF_AUDIT_COLUMNS_B table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the CSS (Support) module, which is documented as obsolete. This table functions as a child table in a data audit trail system, designed to track granular, column-level changes made to records within the support defect management system. Its primary role is to store a historical log of which specific columns were modified during a given audit event, linking each column change to a parent audit history record and the associated defect. The metadata explicitly states this table was "Not implemented in this database," indicating it may exist as a defined schema object but was not actively populated or utilized in standard deployments, a common occurrence for features that were planned but never fully activated.

Key Information Stored

The table's structure centers on identifiers that link it to related audit and defect entities. The primary key, AUDIT_COLUMN_ID, uniquely identifies each recorded column modification. The foreign key column AUDIT_HISTORY_ID is critical, as it joins to the CSS_DEF_AUDIT_HISTORY_B table, connecting the column change to a specific audit transaction or event. Similarly, the DEFECT_ID column joins to the CSS_DEF_DEFECTS_B table, anchoring the audit detail to the master defect record that was altered. While the specific column metadata (e.g., COLUMN_NAME, OLD_VALUE, NEW_VALUE) is not detailed in the provided excerpt, the table's name and purpose imply it would store the name of the altered database column and potentially the before-and-after values of that change.

Common Use Cases and Queries

In an active implementation, this table would enable detailed forensic reporting on defect data modifications. Common use cases would include compliance audits to demonstrate a complete change history, troubleshooting data integrity issues by reconstructing the sequence of edits to a defect, and analyzing support patterns based on which defect fields are most frequently updated. A typical analytical query would join this table to its parent history and defect tables to produce a comprehensive audit report. For example:

• Identifying all columns modified for a specific defect: SELECT aud_col.COLUMN_NAME, aud_hist.CREATION_DATE FROM CSS_DEF_AUDIT_COLUMNS_B aud_col JOIN CSS_DEF_AUDIT_HISTORY_B aud_hist ON aud_col.AUDIT_HISTORY_ID = aud_hist.AUDIT_HISTORY_ID WHERE aud_col.DEFECT_ID = :defect_id ORDER BY aud_hist.CREATION_DATE;
• Reporting on the frequency of changes to particular columns across the system for process analysis.

Related Objects

The table exists within a defined audit schema and has documented foreign key relationships with two key tables, as per the provided metadata. These relationships are essential for any query involving this table.

• CSS_DEF_AUDIT_HISTORY_B: This is the direct parent table. The join is performed on the column CSS_DEF_AUDIT_COLUMNS_B.AUDIT_HISTORY_ID, which references the primary key in CSS_DEF_AUDIT_HISTORY_B. This relationship provides the context for the audit event, such as who made the change and when.
• CSS_DEF_DEFECTS_B: This is the master defects table. The join is performed on the column CSS_DEF_AUDIT_COLUMNS_B.DEFECT_ID, which references the primary key in CSS_DEF_DEFECTS_B. This relationship ties the column-level audit detail back to the specific business object (defect) that was modified.