Results for “detailed_erecord_req_flag”

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

Overview

CS_INCIDENT_TYPES_B is a base configuration table in the Oracle E-Business Suite Service (CS) module that stores non-translated information about Service Request (SR) type codes. In EBS Release 12.1.1 and 12.2.2, this table serves as the master repository of SR categories and subtypes used throughout the Service Request lifecycle. Each row defines a distinct incident type, including its hierarchical relationship to parent types, associated business process, status group, workflow configuration, and enablement window. The table pairs with the translated table CS_INCIDENT_TYPES_TL, which supplies language-specific name and description values; the _B suffix deliberately signals that only translation-independent attributes reside here.

The ETRM data model classifies this object as hub-leaning under the Data Vault heuristic, mined from its foreign key structure. In practice, INCIDENT_TYPE_ID functions as the surrogate primary key (CS_INCIDENT_TYPES_B_PK) and behaves as the natural hub key to which numerous downstream tables attach.

Two unique indexes are documented: CS_INCIDENT_TYPES_B_PK on INCIDENT_TYPE_ID, and the business-key candidate CS_INCIDENT_TYPES_B_UK on INCIDENT_SUBTYPE, along with CS_INCIDENT_TYPES_B_U1 on (INCIDENT_TYPE_ID, ZD_EDITION_NAME) in the 12.2.2 physical schema. The presence of ZD_EDITION_NAME reflects the Edition-Based Redefinition architecture introduced in 12.2.2, enabling online patching.

Key Information Stored

• INCIDENT_TYPE_ID – Surrogate primary key; the identifier referenced by virtually every dependent SR table.
• INCIDENT_SUBTYPE – Business-key candidate (CS_INCIDENT_TYPES_B_UK); the human-readable subtype code.
• NAME – Non-translated internal name of the incident type.
• PARENT_INCIDENT_TYPE_ID – Self-referencing FK supporting hierarchical type/subtype definitions.
• BUSINESS_PROCESS_ID – FK to CS_BUSINESS_PROCESSES, linking the type to its governing process.
• STATUS_GROUP_ID – FK to CS_SR_STATUS_GROUPS_B, defining the status transitions available to the type.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Enablement window controlling when the type may be selected.
• WORKFLOW, TASK_WORKFLOW, WEB_WORKFLOW – Workflow process assignments for the header, tasks, and web entry.
• WEB_ENTRY_FLAG / WEB_IMAGE_FILENAME – Internet-facing behavior and image assets.
• SEEDED_FLAG – Distinguishes Oracle-seeded rows from customer-defined ones.
• SECURITY_GROUP_ID – FK to FND_SECURITY_GROUPS for data-level security.
• OBJECT_VERSION_NUMBER / LAST_UPDATE_DATE – Optimistic locking and audit columns.
• ZD_EDITION_NAME – Edition identifier used in 12.2.2 online patching.

Common Use Cases and Queries

The most frequent use is resolving SR type hierarchies for reporting and LOV definitions:

SELECT t.incident_type_id, t.incident_subtype, t.name, t.start_date_active, t.end_date_active
FROM   cs_incident_types_b t
WHERE  TRUNC(SYSDATE) BETWEEN NVL(t.start_date_active, TRUNC(SYSDATE))
                          AND NVL(t.end_date_active, TRUNC(SYSDATE));

Identifying child types under a parent, exploiting the self-referencing FK:

SELECT child.incident_subtype, child.name
FROM   cs_incident_types_b parent, cs_incident_types_b child
WHERE  child.parent_incident_type_id = parent.incident_type_id
AND    parent.incident_subtype = :p_parent;

Typical reporting scenarios include SR volume by type, workload analysis across business processes, and validation that no active SR references an end-dated type. The table also drives the SR Type Categories setup, task template mapping, and problem/resolution code mapping used by the Service Request Administrator responsibility.

Related Objects

• CS_INCIDENTS_ALL_B – Core SR transaction table; joins on INCIDENT_TYPE_ID.
• CS_INCIDENT_CYCLE_STEPS – Defines status-cycle steps per type via INCIDENT_TYPE_ID.
• CS_BUSINESS_PROCESSES – Parent of BUSINESS_PROCESS_ID.
• CS_SR_STATUS_GROUPS_B – Parent of STATUS_GROUP_ID, governing status transitions.
• CS_SR_TYPE_MAPPING / CS_SR_TYPE_CAT_MAPPINGS / CS_SR_TYPE_ITEMCAT_MAPS – Category and item mappings keyed by INCIDENT_TYPE_ID.
• CS_SR_PROB_CODE_MAPPING / CS_SR_RES_CODE_MAPPING – Problem and resolution code associations.
• CS_SR_TSK_TMPL_GP_MAP – Task template group mapping by type.
• CS_INCIDENT_TYPES_TL – Translated attribute counterpart.
• FND_SECURITY_GROUPS – Parent of SECURITY_GROUP_ID.