Results for “incident_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CS_SR_PROB_CODE_MAPPING_V view is an APPS-owned, VALID database view within the Service (CS) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the mapping that links problem codes to service request incident types and, where applicable, to specific inventory items and item categories. This mapping governs which problem codes are valid selections for a given combination of service request type and product, enabling consistent classification of service requests, defects, and returns.

From a reporting and integration standpoint, the view denormalizes the mapping detail table by resolving foreign keys into human-readable values. Rather than requiring the caller to join to lookup, incident type, item, and category tables, the view presents decoded meanings and concatenated segment values directly. This makes it well suited for concurrent program extracts, Oracle Reports, OAF/ADF data sources, and downstream integrations that need to validate or enumerate valid problem-code-to-item associations. It is a query-only construct; no DML is supported.

Underlying Base Objects

The view is defined over a driving table and several joined objects, documented in the ETRM metadata as follows:

• CS_SR_PROB_CODE_MAPPING_DETAIL (SYNONYM) — the primary source of mapping rows, aliased as PCMAP. This table supplies the problem map identifiers, problem code, incident type, inventory item, organization, category, and the active date ranges.
• CS_LOOKUPS (VIEW) — joined on PROBLEM_CODE = LOOKUP_CODE with LOOKUP_TYPE = 'REQUEST_PROBLEM_CODE' and ENABLED_FLAG = 'Y', supplying the decoded problem meaning and description.
• CS_INCIDENT_TYPES_VL (VIEW) — outer-joined to provide the incident type name.
• MTL_SYSTEM_ITEMS_KFV (SYNONYM) — outer-joined on inventory item and organization to supply the concatenated item segments.
• MTL_CATEGORIES_KFV (SYNONYM) — outer-joined to provide the category name.
• FND_GLOBAL (PACKAGE) — referenced for runtime context such as the current application and responsibility.

The lookup join is effectively inner, since the predicate on lookup code and enabled flag constrains the result set; the incident type, item, and category joins are outer joins, so mappings that are not item- or type-specific remain visible.

Key Columns

• PROBLEM_CODE / PROBLEM_MEANING — the stored problem code and its decoded display meaning from the lookup.
• INCIDENT_TYPE_ID / INCIDENT_TYPE — the service request type identifier and its translated name.
• INVENTORY_ITEM_ID / ORGANIZATION_ID / INVENTORY_ITEM — the item and inventory organization identifiers and the concatenated item segments. These are the columns most relevant to inventory item lookups.
• CATEGORY_ID / CATEGORY_NAME — the item category identifier and its concatenated category name.
• PROBLEM_MAP_ID / PROBLEM_MAP_DETAIL_ID — surrogate keys for the mapping header and detail.
• START_DATE_ACTIVE / END_DATE_ACTIVE and MAP_START_DATE_ACTIVE / MAP_END_DATE_ACTIVE — effective date ranges governing the mapping.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns.

Common Use Cases and Queries

A frequent requirement is to retrieve the valid problem codes for a specific inventory item within an organization:

SELECT problem_code, problem_meaning, incident_type, inventory_item
FROM apps.cs_sr_prob_code_mapping_v
WHERE inventory_item_id = :item_id
AND organization_id = :org_id;

To enumerate all item-specific mappings for an organization, filtering out null items:

SELECT problem_code, inventory_item, category_name
FROM apps.cs_sr_prob_code_mapping_v
WHERE inventory_item_id IS NOT NULL
AND NVL(TRUNC(SYSDATE), SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Additional scenarios include validating user-entered problem codes during service request creation, generating pick lists for LOVs, and building cross-reference extracts between problem codes and item categories. Because date logic uses TRUNC(SYSDATE), callers should apply the same truncation for consistent results.