Results for “sr_type_itemcat_map_id”

10 results




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

Overview

CS_SR_TYPE_ITEMCAT_MAPS is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the mapping information between a service request (incident) type and an item category. Its functional purpose is to constrain which item categories — and optionally which specific inventory items within an inventory organization — are valid for a given service request type, thereby driving item selection, validation, and defaulting on the Service Request form.

The table resides in the CS schema and is classified as VALID. It is a child of CS_INCIDENT_TYPES_B through the INCIDENT_TYPE_ID foreign key, so it functions as configuration or reference data scoped to a service request type. Under the heuristic Data Vault classification derived from its foreign key structure, the object leans toward a satellite: it carries descriptive mapping and effective-dating attributes that describe a parent business entity rather than introducing a new business key or resolving a many-to-many relationship between two independent hubs. This classification should be treated as a modeling suggestion, not a documented fact. The table is effective-dated, allowing mappings to be introduced, retired, and versioned over time without deleting historical rows.

Key Information Stored

The documented physical schema exposes 13 columns. The most significant are:

The business-key candidate is the composite unique index CS_SR_TYPE_ITEMCAT_MAPS_U2 over INCIDENT_TYPE_ID, ITEM_CATEGORY_ID, INVENTORY_ITEM_ID, and INVENTORY_ORG_ID. This confirms that a service request type may be mapped to a given category/item/organization combination only once, while the surrogate key provides the physical uniqueness guarantee.

Common Use Cases and Queries

Typical uses include validating item entry on a service request, driving LOV queries for item categories, and reporting on service request type configuration. A common pattern retrieves all active mappings for a given incident type:

  • SELECT m.item_category_id, m.inventory_item_id, m.inventory_org_id FROM cs.cs_sr_type_itemcat_maps m WHERE m.incident_type_id = :p_incident_type_id AND SYSDATE BETWEEN m.start_date AND NVL(m.end_date, SYSDATE + 1);
  • Joining to CS_INCIDENT_TYPES_B on INCIDENT_TYPE_ID to resolve the service request type name.
  • Joining to MTL_ITEM_CATEGORIES and MTL_SYSTEM_ITEMS_B to resolve category and item descriptions for reporting.
  • Auditing configuration drift by grouping on INCIDENT_TYPE_ID and comparing START_DATE/END_DATE ranges.

Because the table is effective-dated, queries should always filter on the date window and avoid assuming a single row per incident type.

Related Objects

The principal relationships are:

  • CS_INCIDENT_TYPES_B — parent table; joined on CS_SR_TYPE_ITEMCAT_MAPS.INCIDENT_TYPE_ID = CS_INCIDENT_TYPES_B.INCIDENT_TYPE_ID.
  • CS_INCIDENT_TYPES_TL — provides the translated name/description of the service request type.
  • MTL_ITEM_CATEGORIES — resolves ITEM_CATEGORY_ID and INVENTORY_ITEM_ID to category assignments.
  • MTL_SYSTEM_ITEMS_B — resolves INVENTORY_ITEM_ID to item attributes.
  • MTL_PARAMETERS — supplies INVENTORY_ORG_ID organization context.
  • CS_INCIDENTS_ALL — the service request header table whose item lines are validated against these mappings.
  • CS_INCIDENT_TYPE_ITEMCAT_MAP_PKG or equivalent CS setup APIs — the programmatic interface used to maintain these mappings.