Search Results cust_phone_line_code

Overview

CSD_INCIDENTS_NON_SEC_V is an APPS-owned database view within the Oracle E-Business Suite Depot Repair (CSD) module, valid in both 12.1.1 and 12.2.2. It exposes service request (incident) information, resolving the security-restricted CS_INCIDENTS_ALL_VL into a non-secured projection intended for reporting, extracts, and integration interfaces where row-level security predicates would otherwise suppress or complicate results. The view joins incident header data to item master descriptions, customer/product instance references, caller identity, and contact telephony attributes, producing a denormalized row per incident suitable for direct consumption by BI Publisher reports, OBIEE repositories, or custom concurrent programs. Its name includes the "NON_SEC" qualifier to signal that it does not enforce organization or responsibility security on the underlying service request records.

Underlying Base Objects

The documented reference list spans several product schemas. Primary transactional data derives from CS_INCIDENTS_ALL_VL and its extensions in CS Foundation, supplemented by lookup and reference views for status, type, urgency, and severity (CS_INCIDENT_STATUSES_VL, CS_INCIDENT_TYPES_VL, CS_INCIDENT_URGENCIES_B/TL, CS_INCIDENT_SEVERITIES_VL, AR_LOOKUPS, CS_LOOKUPS, HR_LOOKUPS). Customer and contact data is sourced from the TCA/HZ model: HZ_PARTIES, HZ_CONTACT_POINTS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_RELATIONSHIPS, HZ_LOCATIONS, and HZ_TIMEZONES, surfaced through CS_HZ_SR_CONTACT_POINTS and JTF_CUST_ACCOUNTS_ALL_V/JTF_PARTIES_ALL_V. Product/instance detail comes from CSI_ITEM_INSTANCES, CSI_INSTANCE_STATUSES, and MTL_SYSTEM_ITEMS_VL. Person and employee resolution uses PER_ALL_PEOPLE_F, PER_EMPLOYEES_CURRENT_X, PER_PHONES, FND_USER, and supporting APIs (HR_API, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY). Utility logic is invoked through CSD_PROCESS_UTIL, CS_STD, and FND_GLOBAL.

Key Columns

• INCIDENT_ID / INCIDENT_NUMBER — primary identifier and user-facing service request number.
• INCIDENT_STATUS_ID, INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID — foreign keys to the corresponding CS lookup views for decoded meaning.
• ITEM, ITEM_DESC, INV_ITEM_ID, INV_ORGANIZATION_ID, INV_ITEM_REVISION — concatenated item segment, description, and revision derived from MTL_SYSTEM_ITEMS_VL, using NVL of inventory revision against product revision.
• CUST_PHONE — a DECODE-built concatenation of country code, area code, and phone number from HZ_CONTACT_POINTS, branching on CALLER_TYPE (ORGANIZATION or PERSON).
• CUST_PHONE_LINE_TYPE — decoded meaning from AR_LOOKUPS (ARL2.MEANING) resolving the underlying PHONE_LINE_TYPE lookup code; this is the column users search against when filtering by phone line classification (for example, "Mobile" or "Office").
• CUST_PHONE_LINE_CODE — the raw PHONE_LINE_TYPE code from HZ_CONTACT_POINTS, also gated by CALLER_TYPE.
• EXT — phone extension, similarly conditional on caller type.
• CALLER — formatted caller name: first/last name concatenation for person or organization callers, otherwise FND_USER full name.
• INCIDENT_DATE — TRUNC'ed incident creation date.
• CUSTOMER_PRODUCT_ID — CSI instance identifier linking the incident to the installed base record.
• ROW_ID — the incident table ROWID, useful for DML or detokenized updates.

Common Use Cases and Queries

The view is commonly used to build depot repair dashboards, service request extracts, and contact-validation reports, and to reconcile phone line classifications across incidents. A representative query retrieving incidents with caller phone details follows:

SELECT incident_number, item, caller, cust_phone, cust_phone_line_type, incident_date
FROM apps.csd_incidents_non_sec_v
WHERE cust_phone_line_type = 'Mobile';

Filtering on CUST_PHONE_LINE_TYPE supports analyses such as identifying incidents logged via mobile contacts, auditing the completeness of contact telephony data, or joining the result set to CSI_ITEM_INSTANCES for installed-base coverage reporting. Because the view bypasses CS security, it should be restricted to trusted reporting responsibilities or wrapped with an explicit organization filter keyed on INV_ORGANIZATION_ID.