Search Results item_serial_number




Overview
Explore in AI Chat

Overview

CS_SR_SEARCH_NO_CONT_V is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a non-contractual variant of the Service Request search view family, designed to satisfy lookups performed from the SR find window as rendered on the Bali spread table, and from the Service History Bali spread table on the Service Request tab. The view exposes a flattened, denormalized projection of service request header data drawn from CS_INCIDENTS_B_SEC and its multilingual translation tables, together with selected customer, item, and party attributes. Its primary role is to feed the searchable grid that service agents use to locate existing service requests by criteria such as incident number, serial number, status, severity, or customer, without requiring the agent to query the transactional tables directly. Because it is a view rather than a table, all filtering, sorting, and display are performed at runtime, ensuring that the underlying service request records remain the single source of truth. The "NO_CONT" suffix conventionally denotes that the query path is optimized for non-contract-related service requests, distinguishing it from contract-aware search views used elsewhere in the SR finder.

Underlying Base Objects

The view is defined over a documented set of base objects, most of which are referenced through APPS synonyms in the standard EBS manner. The core transactional source is CS_INCIDENTS_B_SEC, a view over the secure service request base, which supplies incident identifiers, status, type, urgency, severity, ownership, dates, and the resource and financial attributes. Multilingual names are resolved by correlated subqueries against CS_INCIDENT_TYPES_TL, CS_INCIDENT_SEVERITIES_TL, CS_INCIDENT_STATUSES_TL, and CS_INCIDENT_URGENCIES_TL, each filtered by USERENV('LANG') so that the description returned matches the session language. The summary text is sourced from CS_INCIDENTS_ALL_TL. Customer and location context is gathered from HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_TIMEZONES. Product and serial context is linked through CSI_ITEM_INSTANCES and MTL_SYSTEM_ITEMS_KFV. Resource group assignment and creation-channel lookups are provided by JTF_RS_GROUPS_VL, JTF_RS_GROUP_USAGES, CS_LOOKUPS, and FND_GLOBAL.

Key Columns

Common Use Cases and Queries

The most frequent use case is locating service requests by serial number when the agent does not know the SR number. A representative query is:

SELECT incident_number, summary, current_serial_number_nv, status_code, severity, incident_date FROM apps.cs_sr_search_no_cont_v WHERE current_serial_number_nv = :p_serial_number AND org_id = :p_org_id;

A broader item-and-serial search can join the inventory item description:

SELECT v.incident_number, v.summary, m.concatenated_segments item, v.current_serial_number_nv FROM apps.cs_sr_search_no_cont_v v, apps.mtl_system_items_kfv m WHERE v.inventory_item_id = m.inventory_item_id AND v.current_serial_number_nv LIKE :p_serial || '%' ORDER BY v.incident_date DESC;

Additional scenarios include building open-SR aging reports filtered by status and close date, constructing customer-facing service history extracts, and supporting OBIEE or custom concurrent-program reporting where the Bali spread table is not used but the same flattened SR projection is required. Because the view inherits the security predicates of CS_INCIDENTS_B_SEC, adopters should always constrain queries by ORG_ID and applicable resource-group criteria to avoid unauthorized data exposure.