Search Results individual_name

Overview

CS_SR_SERVICE_HISTORY_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, residing in the Service (CS) product family. Its documented purpose is to supply the data set rendered by the Service History tab within the Service Request (CS) application. The view consolidates service request header information, customer and party details, product and serial number attributes, incident type and status lookups, problem and resolution code translations, and owner/group assignment into a single denormalized record per service request. Because it is a view rather than a table, it introduces no storage of its own and reflects the current state of the underlying transactional tables at query time. In both 12.1.1 and 12.2.2 it remains a VALID object, and its column naming — most notably the aliasing of INC.INCIDENT_DATE to DATE_OPENED — makes it convenient for reporting tools, BI Publisher data templates, and custom concurrent programs that need a flattened service history extract without joining the numerous lookup and translation tables manually.

Underlying Base Objects

The view is defined over a combination of synonyms, other views, and a package. Documented base objects include CS_INCIDENTS_B_SEC (a view supplying the core incident attributes), CS_INCIDENTS_ALL_TL, CS_INCIDENT_TYPES_TL and CS_INCIDENT_STATUSES_TL (translation tables filtered by the session language), CSI_ITEM_INSTANCES (customer product instances), HZ_PARTIES (customer names), MTL_SYSTEM_ITEMS_KFV (concatenated product names and descriptions), CS_LOOKUPS (problem and resolution code meanings), JTF_OBJECTS_VL (individual and group owner types), and the CS_STD and FND_GLOBAL packages. Joins to translation tables use USERENV('LANG') to return descriptions in the user's session language, while calls to CS_STD.GET_ITEM_VALDN_ORGZN_ID resolve the item validation organization. Since several joins are outer joins (noted by the (+) operator on MTL_SYSTEM_ITEMS_KFV, CSI_ITEM_INSTANCES, CS_LOOKUPS, JTF_OBJECTS_VL, and related aliases), records are returned even when product, serial number, code meaning, or owning group data is absent.

Key Columns

• INCIDENT_NUMBER / INCIDENT_ID — the service request identifier and its internal primary key.
• DATE_OPENED — the source of the searched term; this is INC.INCIDENT_DATE from CS_INCIDENTS_B_SEC, presented under the service-history label DATE_OPENED.
• DATE_CLOSED — the incident close date, null while the request remains open.
• CUSTOMER_ID / CUSTOMER_NAME — party identifier and resolved party name from HZ_PARTIES.
• PRODUCT_NAME / PRODUCT_DESCRIPTION — concatenated segments and description from MTL_SYSTEM_ITEMS_KFV.
• SERIAL_NUMBER — derived via DECODE from the customer product instance, falling back to the current serial number on the incident.
• STATUS_NAME / TYPE_NAME — translated incident status and type descriptions.
• SUMMARY — the service request summary text.
• PROBLEM_CODE_MEANING / RESOLUTION_CODE_MEANING — lookup meanings for the recorded problem and resolution codes.
• GROUP_TYPE / GROUP_NAME / INDIVIDUAL_TYPE / INDIVIDUAL_NAME — owner classification from JTF_OBJECTS_VL.
• CUSTOMER_PRODUCT_ID, CP_COMPONENT_ID, CP_SUBCOMPONENT_ID, INVENTORY_ITEM_ID — product hierarchy and inventory references supporting drill-down to configuration items.

Common Use Cases and Queries

Typical use is a date-bounded service history report for a customer, product, or serial number. A representative query filtering on the searched column is:

• SELECT incident_number, date_opened, date_closed, customer_name, product_name, serial_number, status_name, summary FROM cs_sr_service_history_v WHERE date_opened >= :p_from_date AND date_opened < :p_to_date ORDER BY date_opened DESC; — supports period-based service activity reporting.
• SELECT incident_number, serial_number, date_opened, problem_code_meaning, resolution_code_meaning FROM cs_sr_service_history_v WHERE serial_number = :p_serial; — retrieves the full repair and problem history for a specific unit.
• SELECT customer_name, COUNT(*) open_requests FROM cs_sr_service_history_v WHERE date_closed IS NULL GROUP BY customer_name; — identifies customers with outstanding, unclosed service requests.

Because translation joins depend on USERENV('LANG'), query results follow the language of the connecting session, so reports intended for multilingual deployment should set the appropriate NLS language context. Users should also be aware that the view is optimized for display rather than mass extraction, and heavy reporting workloads are often better served against the base tables directly.