Results for “cs_new_incidents_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_NEW_INCIDENTS_V is an Oracle E-Business Suite (EBS) database view owned by the APPS schema and delivered as part of the CS (Service) product family. It is documented in ETRM as a simplified version of the standard incident view, CS_INCIDENTS_V. Its purpose is to present service incident (service request) data in a flattened, denormalized form that is easier to consume for reporting, operational inquiry, and integration than the full transactional model spread across the incident base and translation tables plus numerous lookup views.

The view carries a status of VALID and is available in both the 12.1.1 and 12.2.2 releases. Because it resolves many descriptive attributes — status, type, severity, urgency, owner, company, account and product — through joins to lookup and party views, it effectively acts as a pre-built reporting layer over the Service (CS) incident schema. Query authors can retrieve a single row per incident with human-readable values instead of performing the multi-table joins themselves.

Underlying Base Objects

The documented base objects of this view span the incident tables, the incident lookup views, party and account views, inventory, and a standard package. The core driving table is CS_INCIDENTS_ALL_B, accessed via its synonym, which supplies the incident identifiers, codes and foreign keys. Localized incident text is joined from CS_INCIDENTS_ALL_TL on INCIDENT_ID with LANGUAGE = USERENV('LANG'), producing the incident SUMMARY.

Descriptive lookups are resolved through CS_INCIDENT_STATUSES_VL, CS_INCIDENT_TYPES_VL, CS_INCIDENT_SEVERITIES_VL and CS_INCIDENT_URGENCIES_VL. Ownership information comes from CS_SR_OWNERS_V, while party context is provided by JTF_PARTIES_ALL_V, JTF_CUST_ACCOUNTS_ALL_V, CSC_HZ_PARTIES_SELF_V and the CS_HZ_SR_CONTACT_POINTS synonym. Product information is taken from MTL_SYSTEM_ITEMS_KFV, and the CS_STD package supplies the item validation organization identifier through CS_STD.GET_ITEM_VALDN_ORGZN_ID. Most of the descriptive joins (urgency, item, owner, party, account) are outer joins, so incidents lacking one of these attributes are still returned.

Key Columns

• INCIDENT_ID — Primary identifier of the service incident; the join key across all subordinate tables.
• PROBLEM_CODE / RESOLUTION_CODE — Standardized problem and resolution classifications.
• STATUS_CODE, INCIDENT_TYPE, SEVERITY, URGENCY — Decoded values obtained from the respective _VL lookup views.
• OWNER — Resource name of the incident owner, from CS_SR_OWNERS_V.
• COMPANY_NAME, ACCOUNT, CUSTOMER_ID — Customer and account context from the party and account views.
• PERSON_FIRST_NAME, PERSON_LAST_NAME — Contact person details resolved through the self-service party view and contact points.
• CURRENT_SERIAL_NUMBER_NV — Aliased serial number of the affected item.
• PRODUCT_NAME, PRODUCT_DESCRIPTION — Concatenated inventory segments and item description from MTL_SYSTEM_ITEMS_KFV.
• INCIDENT_DATE, DATE_CLOSED — Key lifecycle dates for aging and closure reporting.
• CUSTOMER_TICKET_NUMBER — External reference supplied by the customer.
• SUMMARY — Incident description text in the session language.

Common Use Cases and Queries

Typical uses include open-incident backlog reporting, aging and severity analysis, owner workload summaries, and integration extracts where a flat incident record is required. All queries should be fully qualified with the APPS schema.

List open incidents by severity:

• SELECT incident_id, summary, severity, urgency, owner, incident_date
• FROM apps.cs_new_incidents_v
• WHERE status_code NOT IN ('Closed','Cancelled');

Count incidents by company and product:

• SELECT company_name, product_name, COUNT(*) incident_count
• FROM apps.cs_new_incidents_v
• GROUP BY company_name, product_name
• ORDER BY incident_count DESC;

Because the view is a read-only simplification, it should not be used for DML; transactional maintenance continues to be performed against the underlying CS_INCIDENTS_ALL_B and related tables.