Results for “css_def_audit_columns_b”

10 results




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

Overview

CSS_DEF_AUDIT_COLUMNS_B is a table historically associated with the CSS - Support module in Oracle E-Business Suite. The CSS (Customer Support) product family was widely deployed in earlier EBS releases, and the "_B" suffix on this table name denotes a base (non-translated) entity table, as opposed to its "_T" translation counterpart. In Oracle EBS 12.1.1 and 12.2.2, however, the ETRM metadata explicitly records this object as obsolete and not implemented in the database. The table therefore does not physically exist in a standard, current installation of either release, and any reference to it in custom code, interfaces, or legacy scripts should be treated as a dead link that requires remediation.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This suggests the object functioned as an associative entity connecting two parent entities — audit history and defects — rather than storing descriptive attributes of its own. In Data Vault terms, its identity is composed of the surrogate key together with the two foreign key references, which is characteristic of a relationship or bridge table.

Key Information Stored

Because the object is documented as obsolete and unimplemented, detailed column inventories are not available in current ETRM metadata. The following points are the documented structural facts:

No unique business-key index is documented beyond the primary key constraint, which is consistent with the link-table classification. Additional descriptive columns, such as audit column name, data type, or change flags, are not listed in the supplied metadata and should not be assumed without verification against the historical CSS schema definition.

Common Use Cases and Queries

In a release where this table existed, it would have supported audit trail reporting — associating specific defect records with the columns of an audit history entry. That pattern is typical for change-tracking and compliance reporting in support modules. On 12.1.1 and 12.2.2, however, the practical use case is different: identifying and removing references to an obsolete object. Queries against the data dictionary confirm its absence:

  • SELECT table_name, status FROM dba_tables WHERE table_name = 'CSS_DEF_AUDIT_COLUMNS_B'; — expected to return no rows.
  • SELECT object_name, object_type, status FROM dba_objects WHERE object_name LIKE 'CSS_DEF_AUDIT%'; — useful for confirming whether remnants or synonyms exist.

Legacy reports or custom concurrent programs that join this table to CSS_DEF_AUDIT_HISTORY_B or CSS_DEF_DEFECTS_B will fail at runtime with an ORA-00942 error. Remediation normally involves retiring the report or replacing the join with a supported audit-trail view. There is no supported reporting use case for the object itself in current releases.

Related Objects

The documented foreign key relationships define the object's immediate dependencies. The most significant related objects are:

  • CSS_DEF_AUDIT_HISTORY_B — parent of the AUDIT_HISTORY_ID foreign key; holds audit history base records.
  • CSS_DEF_DEFECTS_B — parent of the DEFECT_ID foreign key; holds defect base records.
  • CSS_DEF_AUDIT_COLUMNS_B_PK — the primary key constraint on AUDIT_COLUMN_ID.
  • CSS_DEF_AUDIT_HISTORY_B_T and CSS_DEF_DEFECTS_B_T — the corresponding translation tables, where the base tables carry "_B" naming.
  • CSS_DEF_AUDIT_COLUMNS_T — the presumed translation counterpart, listed here as a naming-convention reference rather than a confirmed object.

Each of these related objects shares the same obsolete status and limitation: they are documented as not implemented in current 12.1.1 and 12.2.2 databases. Any integration touching this cluster of tables should be reviewed as part of CSS module decommissioning or upgrade remediation.