Results for “cs_incident_types_b_u1”

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

Overview

CS.CS_INCIDENT_TYPES_B is the seeded definition table for Service Request (SR) types within the Oracle E-Business Suite Customer Service (CS) module. Each row defines a distinct incident type—an SR classification such as "Service Request," "Complaint," or a customer-defined type—that controls how service request records are created, routed, and processed. Because it stores the master list of incident types referenced widely across the CS schema, it functions as a foundational setup object in the Service Request lifecycle.

The table resides in the APPS_TS_SEED tablespace with a PCT Free of 10, reflecting its nature as seed/reference data rather than high-volume transactional data. Its physical maintenance is managed under the FND Design Data namespace CS.CS_INCIDENT_TYPES_B, and a secured security view is exposed for custom reporting. From a dimensional modeling perspective, the heuristic Data Vault classification of this object is hub-leaning: it holds a stable business key (INCIDENT_TYPE_ID) that anchors numerous downstream references, making it a natural candidate for a hub entity in a Data Vault design.

Key Information Stored

The table contains 48 documented columns. The most significant are:

• INCIDENT_TYPE_ID (NUMBER, 15) — the surrogate primary key (CS_INCIDENT_TYPES_B_PK) and the value propagated to every dependent table.
• NAME (VARCHAR2, 30) — the user-facing name given to the type.
• DESCRIPTION (VARCHAR2, 240) — textual explanation of the type.
• INCIDENT_SUBTYPE (VARCHAR2, 30) — in 11i always 'INC', confirming the row identifies a service request type.
• SEEDED_FLAG — 'Y' marks pre-defined (Oracle-delivered) types versus customer-defined ones.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date bounds controlling when the type is usable.
• PARENT_INCIDENT_TYPE_ID — self-referencing column (documented as not used in the base excerpt); its presence supports hierarchical type relationships.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — plus OBJECT_VERSION_NUMBER for optimistic locking.
• ATTRIBUTE1–ATTRIBUTE15 and CONTEXT — descriptive flexfield (DFF) segments allowing extensible configuration.
• Behavioral controls such as WORKFLOW, TASK_WORKFLOW, WEB_ENTRY_FLAG, AUTOLAUNCH_WORKFLOW_FLAG, BUSINESS_PROCESS_ID, STATUS_GROUP_ID, and SECURITY_GROUP_ID.

Two unique-index candidates are documented. CS_INCIDENT_TYPES_B_U1 enforces uniqueness on (INCIDENT_TYPE_ID, ZD_EDITION_NAME)—the user's search term refers directly to this index—while CS_INCIDENT_TYPES_B_N1 is a non-unique index on INCIDENT_SUBTYPE. Note that the 12.1.1 metadata lists U1 as unique on INCIDENT_TYPE_ID alone; the 12.2.2 edition adds ZD_EDITION_NAME, reflecting edition-based redefinition support.

Common Use Cases and Queries

Typical reporting resolves an incident to its type name and description, filters active types by date, or distinguishes seeded from custom types. A representative query joining the transaction table to its type definition is:

SELECT i.incident_id, t.name, t.description
FROM cs_incidents_all_b i, cs_incident_types_b t
WHERE i.incident_type_id = t.incident_type_id
AND t.seeded_flag = 'N';

Administrators query the table to list active, customer-defined types (WHERE START_DATE_ACTIVE <= SYSDATE AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= SYSDATE)), and developers interrogate U1 to confirm the full uniqueness key when integrating via APIs or data conversion scripts.

Related Objects

The type ID is a high-fanout foreign key. The most significant referencing objects include:

• CS_INCIDENTS_ALL_B.INCIDENT_TYPE_ID — the primary transactional SR table.
• CS_INCIDENT_CYCLE_STEPS.INCIDENT_TYPE_ID — lifecycle steps per type.
• CS_SR_TYPE_MAPPING and CS_SR_TYPE_CAT_MAPPINGS — mapping types to service categories.
• CS_SR_TSK_TMPL_GP_MAP, XNC_CS_SR_TASK_MAP — task template associations.
• CS_SR_PROB_CODE_MAPPING and CS_SR_RES_CODE_MAPPING — problem and resolution code mapping.
• CUG_SR_TYPE_ATTR_MAPS_B and CUG_SR_TYPE_DUP_CHK_INFO — attribute and duplicate-check configuration.
• This table itself references CS_BUSINESS_PROCESSES, CS_SR_STATUS_GROUPS_B, and FND_SECURITY_GROUPS, and self-references via PARENT_INCIDENT_TYPE_ID.