Search Results cs_incidents_ext_audit




Overview
Explore in AI Chat

Overview

CS_INCIDENTS_EXT_AUDIT is an audit table in the Oracle E-Business Suite Service (CS) module, owned by the CS schema. It records the change history of the extensible attribute values attached to service requests (incidents). In Oracle EBS, service request additional information is captured through a set of DFF-style extensible columns — character (C_EXT_ATTR), number (N_EXT_ATTR), date (D_EXT_ATTR) and unit-of-measure (UOM_EXT_ATTR) attribute sets. The operational values for those attributes reside on the service request itself; CS_INCIDENTS_EXT_AUDIT preserves prior values so that changes to those extensible attributes can be traced over time.

Under a heuristic Data Vault classification mined from its foreign key structure, this object models as a link type. It does not hold a natural business entity of its own; instead it associates a service request to an extension record via surrogate keys while capturing an audit snapshot. The table is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2.

Key Information Stored

The table is documented with 262 physical columns. Rather than enumerating them all, the following are the most significant:

The OLD_ prefixed columns are what distinguish this from the live extensible attribute storage; they make before/after comparison possible. The surrogate key is AUDIT_EXTENSION_ID, while INCIDENT_ID and EXTENSION_ID are the referential business-key relationships.

Common Use Cases and Queries

The principal uses are change tracking, compliance reporting, and troubleshooting service request data. A typical query retrieves the change history for a given incident:

SELECT a.audit_extension_id,
       a.incident_id,
       a.attr_group_id,
       a.ext_attr_modified_on,
       a.ext_attr_modified_by,
       a.old_c_ext_attr1,
       a.c_ext_attr1
FROM   cs.cs_incidents_ext_audit a
WHERE  a.incident_id = :incident_id
ORDER BY a.ext_attr_modified_on;

To identify which extensible attributes changed most recently across the service organization, aggregate on attr_group_id and ext_attr_modified_on. For before/after comparisons of a specific attribute, select the OLD_ and non-OLD_ pairs side by side. Reporting use cases include audit trails for regulated service processes, validating that mandatory extensible attributes were populated, and reconstructing the state of a service request at a point in time. Because the table is large and wide, queries should filter on incident_id, extension_id, or the modified-on date to avoid full scans.

Related Objects

  • CS_INCIDENTS_ALL_B — the base service request table; CS_INCIDENTS_EXT_AUDIT.INCIDENT_ID references it. This is the primary parent join.
  • CS_INCIDENTS_EXT_AUDIT_PK / CS_INCIDENTS_EXT_AUDIT_U1 — the primary key constraint and unique index on AUDIT_EXTENSION_ID.
  • CS_INCIDENTS_EXT_AUDIT.extension_id — the second documented foreign key relationship (external reference), linking the audit row to its extension definition.
  • The live extensible attribute storage on the service request (the non-audit counterpart), which supplies the current values against which OLD_ columns are compared.
  • CS Service request DFF / additional information configuration — CONTEXT and ATTR_GROUP_ID correspond to the configured attribute groups and contexts.
  • CS_INCIDENTS_ALL_TL — the translation table for service request descriptive data, commonly joined with CS_INCIDENTS_ALL_B when reporting on incidents alongside their audit history.