Search Results owner_old

Overview

CS_INCIDENTS_DIARY_V is an APPS-owned database view within the Oracle E-Business Suite Service (CS) product family. Per the ETRM documentation metadata, the object is marked VALID but is explicitly described as obsolete: "This view is not used anymore. This has been obsoleted. Starting 11.5.6 this view will not be supported and will remain just for backward compatibility." Consequently, it carries no functional role in Oracle EBS 12.1.1 or 12.2.2 reporting or integration activities beyond preserving schema-level compatibility for any legacy custom code that still references it.

The view historically presented a unified incident activity diary, combining incident header information with notes and audit-style change records. Its functional replacement for certain use cases is CS_INCIDENTS_LOG_V, though the metadata notes that the replacement view "has some of the functionality from this view but is not a complete" substitute. The search term "old_description" aligns with the view's legacy "OLD_" prefixed columns, which capture pre-change values for incident attributes such as severity, type, status, urgency, owner, dates, site, contacts, platform, language, and customer product.

Underlying Base Objects

The documented base objects referenced by CS_INCIDENTS_DIARY_V span incident, note, task, and party data. Core incident sources include CS_INCIDENTS_ALL_B, CS_INCIDENTS_AUDIT_VL, and the lookup tables CS_INCIDENT_SEVERITIES, CS_INCIDENT_STATUSES, CS_INCIDENT_TYPES, and CS_INCIDENT_URGENCIES. Notes and text are sourced from JTF_NOTES_VL and the JTF_NOTES_PKG package.

• Customer and reference data: CS_CUSTOMER_PRODUCTS_ALL, MTL_SYSTEM_ITEMS, JTF_PARTIES_ALL_V.
• Owner and task data: CS_SR_OWNERS_V, FND_USER, JTF_TASKS_V, JTF_TASK_UTL, JTF_TASK_WORKFLOW_PKG.
• Utility packages and views: FND_GLOBAL, JTF_COMMON_PVT, JTF_OBJECTS_VL, and CSICUMPI_PUB.

The view text shows a UNION-style construction: a "NOTES" source type selects from the incident and note tables using JTF_NOTE_ID as ACTION_ID and NOTES as DETAILS, while all audit-related columns (SEVERITY_OLD, TYPE_NEW, OWNER_OLD, and similar) are projected as NULL. This indicates the surviving implementation only fully supports the note-diary branch, with the change-tracking branch effectively disabled.

Key Columns

Key columns include SOURCE_TYPE, which identifies the row origin (documented value "NOTES"); INCIDENT_ID, the incident key; INCIDENT_DATE, drawn from the incident LAST_UPDATE_DATE; OWNER, the FND_USER name; ACTION_ID, mapped to JTF_NOTE_ID; DETAILS, the note text; and NOTE_STATUS. A large set of paired OLD/NEW audit columns is exposed but returns NULL in the delivered view text, including SEVERITY_OLD/NEW, TYPE_OLD/NEW, STATUS_OLD/NEW, URGENCY_OLD/NEW, GROUP_OLD/NEW, OWNER_OLD/NEW, DATE_OLD/NEW, and site, contact, platform, language, and customer product variants. Associated flag columns such as INCIDENT_SEVERITY_FLAG and INCIDENT_OWNER_FLAG similarly resolve to NULL. Because of this, the OLD_ and NEW_ name columns are not populated in the obsolete implementation.

Common Use Cases and Queries

Because the view is obsoleted, it should not be used for new development or reporting. Where legacy code must be maintained, the practical query pattern filters on INCIDENT_ID to retrieve note rows:

• Retrieve notes for one incident: SELECT SOURCE_TYPE, INCIDENT_ID, INCIDENT_DATE, OWNER, ACTION_ID, DETAILS FROM APPS.CS_INCIDENTS_DIARY_V WHERE INCIDENT_ID = :incident_id;
• List recent note activity: SELECT INCIDENT_ID, INCIDENT_DATE, OWNER, NOTE_STATUS FROM APPS.CS_INCIDENTS_DIARY_V ORDER BY INCIDENT_DATE DESC;
• Search note text: SELECT INCIDENT_ID, DETAILS FROM APPS.CS_INCIDENTS_DIARY_V WHERE DETAILS LIKE '%text%';

For any new requirement, Oracle recommends converting such queries to supported alternatives such as CS_INCIDENTS_LOG_V or direct queries against CS_INCIDENTS_AUDIT_VL, JTF_NOTES_VL, and CS_INCIDENTS_ALL_B, since CS_INCIDENTS_DIARY_V may be removed in a future release and its audit columns no longer return meaningful data.