Search Results cs_sr_res_code_mapping_v

Overview

CS_SR_RES_CODE_MAPPING_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CS (Service) product family. Its stated purpose is to present the mapping of resolution codes to service request types and to inventory items. In practice, the view denormalizes the configuration held in CS_SR_RES_CODE_MAPPING_DETAIL and joins it to lookup meanings, incident type names, item concatenated segments, and category concatenated segments, so that a single query returns human-readable values rather than raw identifiers.

The view is defined in both Oracle EBS 12.1.1 and 12.2.2, and is marked VALID in the ETRM 12.2.2 repository. Because it consolidates several lookups and key flexfield views, it is commonly used in service request analytics, agent-facing resolution selection logic, and inbound or outbound integrations that need to translate between internal resolution code identifiers and descriptive text. It is a read-only construct; no DML should be issued against it.

Underlying Base Objects

The documented base objects referenced by this view are:

• CS_SR_RES_CODE_MAPPING_DETAIL (synonym) — the driving table, aliased RESMAP, holding the mapping rows themselves.
• CS_LOOKUPS (view) — joined twice, aliased CSLKP for the resolution code and CSLKP_1 for the problem code, to retrieve the MEANING and DESCRIPTION text.
• CS_INCIDENT_TYPES_VL (view) — the incident/service request type name, aliased INTYP.
• MTL_SYSTEM_ITEMS_KFV (synonym) — the item key flexfield view supplying CONCATENATED_SEGMENTS for the inventory item.
• MTL_CATEGORIES_KFV (synonym) — the category key flexfield view supplying the category concatenated segments.
• FND_GLOBAL (package) — referenced in the documented dependency list, typically for session context resolution.

The joins to INCIDENT_TYPE_ID, INVENTORY_ITEM_ID/ORGANIZATION_ID, and CATEGORY_ID are all outer joins, so a mapping row is still returned even when the related item, category, or incident type is absent. By contrast, the joins to the two CS_LOOKUPS instances are inner joins with an ENABLED_FLAG = 'Y' filter and a date-activity filter against SYSDATE, which means a mapping row is only surfaced when its resolution and problem codes are currently valid, enabled lookups.

Key Columns

• ROW_ID — the ROWID of the underlying mapping detail row, exposed as the first column.
• RESOLUTION_MAP_ID / RESOLUTION_MAP_DETAIL_ID — primary and detail identifiers for the mapping definition.
• RESOLUTION_CODE, PROBLEM_CODE — the coded values stored on the mapping row, translated by the lookups.
• RESOLUTION_MEANING, PROBLEM_MEANING — the lookup MEANING for the resolution code and the problem code respectively; CSLKP.DESCRIPTION is also selected.
• INCIDENT_TYPE_ID / INCIDENT_TYPE — the service request type identifier and its display name.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, INVENTORY_ITEM — item identity and the concatenated item flexfield segments.
• CATEGORY_ID, CATEGORY_NAME — category identity and concatenated category segments.
• MAP_START_DATE_ACTIVE, MAP_END_DATE_ACTIVE, START_DATE_ACTIVE, END_DATE_ACTIVE — the effective dating windows for the mapping and for the underlying record.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and concurrency columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield columns carried through from the mapping detail table.

Common Use Cases and Queries

The view is typically used to validate resolution codes during service request closure, to populate LOVs and resolution picklists conditioned by incident type and item, and to feed reporting layers that require readable resolution and problem descriptions. A representative query retrieving the active mapping for a given service request type is:

• SELECT resolution_code, resolution_meaning, problem_code, problem_meaning, incident_type, inventory_item, category_name FROM cs_sr_res_code_mapping_v WHERE incident_type_id = :p_incident_type_id AND TRUNC(SYSDATE) BETWEEN TRUNC(NVL(map_start_date_active, SYSDATE)) AND TRUNC(NVL(map_end_date_active, SYSDATE));

To list all resolutions configured for a specific item and organization:

• SELECT resolution_code, resolution_meaning, problem_meaning FROM cs_sr_res_code_mapping_v WHERE inventory_item_id = :p_item_id AND organization_id = :p_org_id ORDER BY resolution_meaning;

Because the lookup joins enforce ENABLED_FLAG = 'Y' and current activity dates, consumers should be aware that disabled or date-expired resolution codes will not appear, and that re-enabling or extending activity dates is required before a mapping becomes visible again. Queries intending to inspect historically expired mappings must therefore be directed at the base CS_SR_RES_CODE_MAPPING_DETAIL table rather than this view. All access should be performed as the APPS schema or through a responsibility whose grants include SELECT on APPS.CS_SR_RES_CODE_MAPPING_V.