Search Results old_ship_to_site_use_id

Overview

CS_INCIDENTS_AUDIT_VL is an APPS-owned multilingual (VL) view in the Oracle E-Business Suite Service (CS) module. It presents audit trail information for service incidents, exposing the history of field-level changes recorded against incident records. In Oracle EBS 12.1.1 and 12.2.2, the view conforms to the standard MLS (Multi-Lingual Support) pattern: it joins a base (_B) table holding language-independent columns with a translation (_TL) table holding language-dependent columns, and presents them through a single queryable interface filtered by the session's language.

Functionally, the view serves reporting and integration consumers who need to determine when and how an incident changed—status, owner, group, severity, urgency, dates, and other tracked attributes. Each row represents one audited change event on an incident, together with both the new and previous values of the affected attribute and a flag indicating the field that changed. Because it is a view rather than a table, it carries no storage of its own and is populated from the underlying audit tables maintained by the Service application.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists two referenced base objects, both exposed to APPS as synonyms:

• CS_INCIDENTS_AUDIT_B — the base table containing non-translatable audit columns, including all identifiers, flags, dates, and the old/new value pairs.
• CS_INCIDENTS_AUDIT_TL — the translation table containing language-dependent descriptive columns, keyed by LANGUAGE_ID and the audit record's primary key.

The view text confirms this structure: it selects from the _B table (aliased B) and joins to the _TL table on INCIDENT_AUDIT_ID and LANGUAGE_ID, returning a ROWID alias (ROW_ID) for the base row. The _VL suffix and the inclusion of LANGUAGE_ID among the selected columns are consistent with the standard MLS view convention used throughout EBS 12.x. The view is owned by APPS and is marked VALID in the ETRM dictionary.

Key Columns

The view exposes a substantial set of audit columns. The most significant include:

• INCIDENT_AUDIT_ID — primary key of the audit record; INCIDENT_ID — the incident to which the audit row belongs.
• INCIDENT_STATUS_ID / OLD_INCIDENT_STATUS_ID / CHANGE_INCIDENT_STATUS_FLAG — the new and prior status values and the change indicator.
• INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID with corresponding OLD_ and CHANGE_ columns — tracked classification attributes.
• RESPONSIBLE_GROUP_ID, INCIDENT_OWNER_ID, GROUP_ID — assignment-related fields with old values and flags.
• SITE_ID / OLD_SITE_ID / CHANGE_SITE_FLAG and BILL_TO_CONTACT_ID / OLD_BILL_TO_CONTACT_ID / CHANGE_BILL_TO_FLAG — party-site and contact changes. The user's search term, old_bill_to_site_use_id, relates conceptually to this family of bill-to and site audit columns, although the documented view text exposes BILL_TO_CONTACT_ID and SITE_ID rather than a literal OLD_BILL_TO_SITE_USE_ID column.
• Date fields such as INCIDENT_DATE, CLOSE_DATE, EXPECTED_RESOLUTION_DATE, OBLIGATION_DATE with their OLD_ counterparts.
• AUDIT_FIELD — identifies the audited attribute; WORKFLOW_PROCESS_NAME / WORKFLOW_PROCESS_ITEMKEY / NEW_WORKFLOW_FLAG — workflow context.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and LANGUAGE_ID.

Common Use Cases and Queries

Typical uses include reconstructing the lifecycle of an incident, auditing reassignments, and feeding downstream reporting or integration extracts.

• Change history for a specific incident:
  SELECT incident_audit_id, audit_field, incident_status_id, old_incident_status_id, last_update_date FROM cs_incidents_audit_vl WHERE incident_id = :p_incident_id ORDER BY last_update_date;
• Status transitions over a period:
  SELECT incident_id, old_incident_status_id, incident_status_id, last_update_date FROM cs_incidents_audit_vl WHERE change_incident_status_flag = 'Y' AND last_update_date BETWEEN :p_from AND :p_to;
• Ownership or group reassignment tracking:
  SELECT incident_id, incident_owner_id, old_incident_owner_id, responsible_group_id FROM cs_incidents_audit_vl WHERE change_incident_owner_flag = 'Y';
• Bill-to/site related changes:
  SELECT incident_id, site_id, old_site_id, bill_to_contact_id, old_bill_to_contact_id FROM cs_incidents_audit_vl WHERE change_bill_to_flag = 'Y' OR change_site_flag = 'Y';

Because the view is multilingual, queries automatically return descriptions in the session language; joins to lookup tables using the *_ID columns resolve the human-readable values.