Search Results cs_sr_contacts_ext_audit_n1

Overview

CS.CS_SR_CONTACTS_EXT_AUDIT is a technical audit table in the Oracle E-Business Suite Service (CS) schema. It records the complete change history of the extensible attribute values held against party role contacts associated with a service request. When an agent updates a service request contact or associated party, the affected extensible attribute records are captured here, preserving both the new value and the previous value for each attribute. The table is designated as an audit table in the FND design data (CS.CS_SR_CONTACTS_EXT_AUDIT) and stores its data in the APPS_TS_TX_DATA tablespace, with indexes in APPS_TS_TX_IDX. It is registered as VALID in the EBS data dictionary and is present in both 12.1.1 and 12.2.2 releases.

Under a heuristic Data Vault classification, this object is best modelled as a link. It connects an incident (service request) to a contact extension record and to the party/contact role for a given point in the change history, rather than functioning as an independent business hub. This classification is a modelling suggestion derived from the foreign key structure, not a statement about the physical design of the EBS table.

Key Information Stored

The table carries 266 documented columns, reflecting a very wide extensible attribute model. The most significant columns are:

• AUDIT_EXTENSION_ID — a system-generated number that uniquely identifies each audit extension row. This is the surrogate primary key of the table (CS_SR_CONTACTS_EXT_AUDIT_PK) and the column of the unique index CS_SR_CONTACTS_EXT_AUDIT_U1, which the user referenced as cs_sr_contacts_ext_audit_u1.
• EXTENSION_ID — the system-generated identifier of the corresponding extension row in the source (non-audit) table, linking each audit row back to the live record.
• INCIDENT_ID — the service request number from CS_INCIDENTS_ALL_B, the business key that ties the audit record to a specific SR.
• CONTEXT — classification of an external attribute associated with a service request contact or associated party.
• ATTR_GROUP_ID — identifier of the attribute group to which the extensible attributes belong.
• PARTY_ID / OLD_PARTY_ID — the associated party before and after the change.
• CONTACT_TYPE and PARTY_ROLE_CODE — the contact category and the role played by the party on the service request.
• C_EXT_ATTR1–50, N_EXT_ATTR1–25, D_EXT_ATTR1–25, UOM_EXT_ATTR1–25 — character, numeric, date and unit-of-measure extensible attribute columns, each paired with an OLD_ counterpart that stores the prior value.
• EXT_ATTR_MODIFIED_ON and EXT_ATTR_MODIFIED_BY — the timestamp and user responsible for the attribute modification.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The unique key is the surrogate AUDIT_EXTENSION_ID; there is no unique constraint on INCIDENT_ID or EXTENSION_ID. The non-unique index CS_SR_CONTACTS_EXT_AUDIT_N1 on INCIDENT_ID supports retrieval by service request, which is the dominant access path.

Common Use Cases and Queries

The primary use case is historical traceability: determining who changed a contact's extensible attributes on a service request, when, and from what value. Because every change inserts a new row rather than updating in place, the table supports point-in-time reconstruction of contact attribute state.

• Reconstructing the change history for a service request: SELECT audit_extension_id, extension_id, ext_attr_modified_on, ext_attr_modified_by, c_ext_attr1, old_c_ext_attr1 FROM cs.cs_sr_contacts_ext_audit WHERE incident_id = :p_incident_id ORDER BY ext_attr_modified_on;
• Identifying all attribute changes performed by a user in a period, using EXT_ATTR_MODIFIED_BY and EXT_ATTR_MODIFIED_ON.
• Auditing a specific party's role-based contact data via PARTY_ID and PARTY_ROLE_CODE.
• Comparing prior and current values using the OLD_ paired columns for any of the character, numeric, date or UOM attribute sets.

Reporting should always filter on INCIDENT_ID or the audit surrogate key, since the table grows with every modification and a full scan is expensive.

Related Objects

• CS.CS_INCIDENTS_ALL_B — the service request base table; joined on INCIDENT_ID to obtain SR context.
• CS.CS_SR_CONTACTS_EXT — the live extension table whose changes this audit table records, related via EXTENSION_ID.
• CS.CS_SR_CONTACTS_EXT_AUDIT_U1 — the unique index on AUDIT_EXTENSION_ID.
• CS.CS_SR_CONTACTS_EXT_AUDIT_N1 — the non-unique index on INCIDENT_ID.
• HZ_PARTIES — the party master referenced through PARTY_ID and OLD_PARTY_ID.
• CS.CS_SR_CONTACTS — the service request contact/associated party assignment table, providing contact role context.

Application logic that maintains the contact extensible attributes in the Service module is responsible for writing the corresponding audit rows.