Search Results cslkp_1

Overview

APPS.CS_SR_RES_CODE_MAPPING_V is a reporting view in the Oracle E-Business Suite (EBS) Service / TeleService and Depot Repair schemas. It exposes the resolution code mapping configuration stored in the CS_SR_RES_CODE_MAPPING_DETAIL table, denormalized against lookup meanings, incident types, inventory items, and item categories. In releases 12.1.1 and 12.2.2, this view is the standard interface used by concurrent programs, Oracle Discoverer worksheets, BI Publisher reports, and custom extensions that need human-readable resolution and problem descriptions rather than raw lookup codes. The user search term "resolution_meaning" maps directly to a column produced by this view: it joins CS_LOOKUPS (alias CSLKP) on LOOKUP_TYPE = 'REQUEST_RESOLUTION_CODE' to translate RESOLUTION_CODE into its display name.

This view is read-only and dependent on the APPS schema. It is typically consumed by functional users configuring call center resolution trees, service request closure screens, and field service resolution validation.

Underlying Base Objects

The view SELECT clause lists the documented base objects and their aliases:

• CS_SR_RES_CODE_MAPPING_DETAIL (SYNONYM, alias RESMAP) – the driving table holding resolution_map_id, resolution_map_detail_id, resolution_code, problem_code, incident_type_id, inventory_item_id, organization_id, category_id, and all the date and DFF (attribute1–15, attribute_category) columns.
• CS_LOOKUPS (VIEW, aliases CSLKP and CSLKP_1) – joined on problem_code to lookup_type 'REQUEST_PROBLEM_CODE' and on resolution_code to lookup_type 'REQUEST_RESOLUTION_CODE'. Only rows with enabled_flag = 'Y' and a current date range are retained.
• CS_INCIDENT_TYPES_VL (VIEW, alias INTYP) – outer-joined on incident_type_id to supply the incident_type name.
• MTL_SYSTEM_ITEMS_KFV (SYNONYM, alias MTLKFV) – outer-joined on inventory_item_id and organization_id to return the inventory_item key flexfield concatenated_segments.
• MTL_CATEGORIES_KFV (SYNONYM, alias MTLCSET) – outer-joined on category_id to return the category_name key flexfield concatenated_segments.
• FND_GLOBAL (PACKAGE) – referenced indirectly for environment/user context during runtime.

Key Columns

• resolution_meaning – the meaning of RESOLUTION_CODE from CS_LOOKUPS where lookup_type = 'REQUEST_RESOLUTION_CODE'. This is the primary descriptive column returned for user search "resolution_meaning".
• problem_meaning – the meaning of PROBLEM_CODE from CS_LOOKUPS where lookup_type = 'REQUEST_PROBLEM_CODE'.
• resolution_code / problem_code – the raw lookup codes that drive validation.
• incident_type – descriptive name of the associated incident type (CS_INCIDENT_TYPES_VL.NAME).
• inventory_item – concatenated_segments of the item key flexfield.
• category_name – concatenated_segments of the item category key flexfield.
• resolution_map_id, resolution_map_detail_id – surrogate keys for the mapping and mapping detail records.
• map_start_date_active, map_end_date_active, start_date_active, end_date_active – effective dating for the mapping and its details.
• attribute1 through attribute15, attribute_category – descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include listing valid resolution codes for a given incident type, validating a resolution entered on a service request, and driving LOV queries in custom OAF or Forms pages. Because CS_LOOKUPS is filtered by SYSDATE, only currently effective lookups appear, so historical mappings may be absent from query results.

Sample query — list resolution meanings for a specific incident type:

SELECT resolution_meaning, problem_meaning,
       incident_type, category_name
FROM   apps.cs_sr_res_code_mapping_v
WHERE  incident_type = :p_incident_type
ORDER  BY resolution_meaning;

Sample query — retrieve item-specific mappings:

SELECT resolution_code, resolution_meaning,
       inventory_item, organization_id
FROM   apps.cs_sr_res_code_mapping_v
WHERE  inventory_item_id = :p_item_id
AND    organization_id  = :p_org_id;

Because the view applies TRUNC(SYSDATE) against NVl-ed lookup date ranges and INNER joins to CS_LOOKUPS on problem_code, rows whose lookup codes are disabled or outside their effective window are silently excluded. Users should confirm lookup setup in the REQUEST_RESOLUTION_CODE and REQUEST_PROBLEM_CODE lookup types before diagnosing missing resolution_meaning values.