Results for “csd_incidents_v”

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

Overview

CSD_INCIDENTS_V is an APPS-owned database view in the Oracle E-Business Suite Depot Repair (CSD) module. It is documented as "the view for getting service request information," which positions it as a denormalized read layer over the depot repair service request (incident) data model. Rather than requiring callers to join the incident entity to item, party, contact point, and lookup tables manually, CSD_INCIDENTS_V pre-assembles those relationships into a single queryable object. The view is marked VALID and appears in both ETRM 12.1.1 and 12.2.2 documentation, making it a stable, cross-release reference for reporting, extensions, and integration.

Because the underlying incident entity is secured and multilingual (the view selects from CS_INCIDENTS_VL_SEC, the security-enabled VL view), CSD_INCIDENTS_V effectively respects Oracle's incident security model while exposing item and caller detail. It is therefore suited to concurrent-program extracts, Oracle Reports, BI Publisher data templates, and custom OAF or forms-based extensions within Depot Repair.

Underlying Base Objects

The documented referenced base objects reveal the view's architecture:

• Incident core: CS_INCIDENTS_VL_SEC (the security-enabled incident entity), with incident status, type, urgency, and severity resolved through CS_INCIDENT_STATUSES_VL, CS_INCIDENT_TYPES_VL, CS_INCIDENT_SEVERITIES_VL, and CS_INCIDENT_URGENCIES_B/TL.
• Product / item: CSI_ITEM_INSTANCES and CSI_INSTANCE_STATUSES (customer product instances), plus MTL_SYSTEM_ITEMS_VL (item flexfield concatenated segments and description).
• Party / contact model: HZ_PARTIES, HZ_CONTACT_POINTS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_RELATIONSHIPS, HZ_LOCATIONS, and HZ_TIMEZONES, exposed through JTF_PARTIES_ALL_V, JTF_CUST_ACCOUNTS_ALL_V, and CS_HZ_SR_CONTACT_POINTS.
• Caller / person: PER_ALL_PEOPLE_F, PER_EMPLOYEES_CURRENT_X, PER_PHONES, FND_USER, and HR packages (HR_API, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY).
• Reference / utility: AR_LOOKUPS, CS_LOOKUPS, HR_LOOKUPS, FND_GLOBAL, CS_STD, and CSD_PROCESS_UTIL.

This breadth explains the "party_cont" search term: the view's phone columns are derived directly from HZ_CONTACT_POINTS aliased as PARTY_CONT1, with DECODE logic on INC.CALLER_TYPE ('ORGANIZATION' vs 'PERSON') governing which contact point values are formatted into the output.

Key Columns

• ROW_ID, INCIDENT_ID, INCIDENT_NUMBER: Unique row locator and incident identifiers.
• INCIDENT_STATUS_ID, INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID: Foreign keys to the incident classification lookups.
• INVENTORY_ITEM_ID, ITEM, ITEM_DESC: Item flexfield concatenated segments and description.
• INV_ITEM_REVISION: NVL of INV_ITEM_REVISION and PRODUCT_REVISION.
• INV_ORGANIZATION_ID: Owning inventory organization.
• CUST_PHONE: Contact-point phone assembled from PARTY_CONT1 (country code, area code, number) with DECODE formatting by caller type.
• CUST_PHONE_LINE_TYPE / CUST_PHONE_LINE_CODE / EXT: Meaning from AR_LOOKUPS and phone line type/extension from the contact point.
• CALLER: Person first/last name concatenation, falling back to FND2.FULL_NAME.
• INCIDENT_DATE, CUSTOMER_PRODUCT_ID (CII.INSTANCE_ID), RECORD_IS_VALID_FLAG, ORG_ID: Date, customer product instance, validity, and multi-org context.

Common Use Cases and Queries

Typical uses include depot repair workbench extracts, service request listings with caller contact detail, and multi-org filtered reports. A minimal query:

SELECT incident_number, caller, cust_phone,
       item, item_desc, incident_date, org_id
  FROM apps.csd_incidents_v
 WHERE org_id = :p_org_id
   AND record_is_valid_flag = 'Y';

To retrieve contact point detail for open incidents:

SELECT i.incident_number, i.caller, i.cust_phone,
       i.cust_phone_line_type, i.ext
  FROM apps.csd_incidents_v i
 WHERE i.incident_status_id IN
       (SELECT lookup_code FROM cs_lookups WHERE lookup_type = 'INCIDENT_STATUS');

Because the view applies security via CS_INCIDENTS_VL_SEC and FND_GLOBAL, queries executed under a user session automatically honor incident access rules. Callers should not assume the underlying phone data is unformatted; CUST_PHONE is presentation-ready and should be treated as a display column rather than a join key.