Search Results cs_incidents_audit_b




Overview
Explore in AI Chat

Overview

CS_INCIDENTS_AUDIT_B is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores non-translated audit information for service requests. Each row captures a change-history record for a service request (internally an "incident"), recording the new value, the prior value, and a change flag for every auditable attribute on the incident. The table is owned by the CS schema and is documented as VALID in ETRM metadata for release 12.2.2, with a physical schema of 466 columns and a Data Vault classification (heuristic, mined from its foreign-key structure) of satellite-leaning. In Data Vault terms, this suggests modeling CS_INCIDENTS_AUDIT_B as a satellite attached to the CS_INCIDENTS_ALL_B hub: it is descriptive, time-variant, and keyed by an identifier tied to the incident, rather than acting as an independent hub or a pure relationship link.

Key Information Stored

The table is principally an audit trail. The most significant columns fall into three groups.

The extensive set of CHANGE_* flags allows queries to filter only those audit rows where a particular attribute actually changed, rather than returning every historical snapshot.

Common Use Cases and Queries

The primary use case is change-history reporting for service requests: identifying who reassigned a request, when a status or severity changed, or whether resolution and close dates slipped. A typical pattern joins the audit table to its parent incident:

  • SELECT a.incident_id, a.incident_audit_id, a.last_update_date, a.last_updated_by, a.incident_status_id, a.old_incident_status_id FROM cs.cs_incidents_audit_b a WHERE a.incident_id = :p_incident_id AND a.change_incident_status_flag = 'Y' ORDER BY a.last_update_date;
  • Aging and SLA analysis can key on the OLD_ and current SLA_DATE_1 through SLA_DATE_6 columns together with CHANGE_SLA_DATE_*_FLAG, isolating requests whose SLA milestones were renegotiated.
  • Ownership and routing audits commonly filter on CHANGE_INCIDENT_OWNER_FLAG or CHANGE_RESPONSIBLE_GROUP_FLAG to reconstruct reassignment histories for workload or escalation reporting.
  • Because the table carries 466 columns, list specific columns in reporting SQL rather than selecting *, both for performance and to keep result sets readable.

Related Objects

The foreign-key relationships documented for this table identify its principal dependencies.

These relationships confirm that the table functions as an attribute-rich history store hanging off the service request hub, consistent with its satellite-leaning classification.