Search Results cs_incidents_ext_b




Overview
Explore in AI Chat

Overview

CS_INCIDENTS_EXT_B is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores Service Request Extensible Attribute records. It is the "B" (base) layer of the extensibility structures that extend the core Service Request (incident) entity with customer-defined attributes. The companion translation layer is CS_INCIDENTS_EXT_TL, and the corresponding key flexfield/multi-org structures follow the industry-standard _B / _TL naming convention used throughout EBS.

The table is owned by the CS schema and holds 134 documented columns in 12.2.2. Its primary key is CS_INCIDENTS_EXT_B_PK, defined on the surrogate column EXTENSION_ID, and a unique index CS_INCIDENTS_EXT_U1 also enforces uniqueness on EXTENSION_ID. The single documented foreign key is INCIDENT_ID referencing CS_INCIDENTS_ALL_B, which anchors each extensible-attribute row to exactly one Service Request.

Under the Data Vault heuristic mined from the FK structure, CS_INCIDENTS_EXT_B is satellite-leaning. It carries descriptive, context-dependent attributes about a single parent business entity rather than defining a hub or resolving a many-to-many link. This classification should be treated as a modeling suggestion: the table behaves as a dependent satellite keyed to the incident hub, with EXTENSION_ID serving as the satellite's own key and INCIDENT_ID as the hub reference.

Key Information Stored

The 134 columns follow a fixed, generated layout rather than one column per logical attribute. The most important columns are:

  • EXTENSION_ID — surrogate primary key; uniquely identifies each extensible-attribute record (CS_INCIDENTS_EXT_B_PK, CS_INCIDENTS_EXT_U1).
  • INCIDENT_ID — foreign key to CS_INCIDENTS_ALL_B; the Service Request to which the attributes belong. This is the true business linkage.
  • CONTEXT — identifies the descriptive flexfield context under which the attribute values are interpreted.
  • ATTR_GROUP_ID — groups related attribute sets, allowing multiple attribute blocks per incident.
  • C_EXT_ATTR1 … C_EXT_ATTR50 — fifty character extensible attribute columns holding text values.
  • N_EXT_ATTR1 … N_EXT_ATTR25 — twenty-five numeric extensible attribute columns.
  • D_EXT_ATTR1 … D_EXT_ATTR25 — twenty-five date extensible attribute columns.
  • UOM_EXT_ATTR1 … UOM_EXT_ATTR25 — twenty-five unit-of-measure companion columns qualifying the numeric attributes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns present on nearly all transactional tables.

Columns are consumed positionally: the flexfield metadata (segments, value sets) maps logical segment names to physical C_/N_/D_/UOM_ positions. Therefore the physical column name alone does not reveal the business meaning — that comes from the context and attribute-group definition.

Common Use Cases and Queries

Typical use cases include reporting on custom Service Request attributes, validating that segment values captured in the UI persisted correctly, migrating incident attributes between environments, and building extracts that combine standard incident columns with extended ones. Because the C_, N_, D_, and UOM_ columns are positional, queries must join to the flexfield definition to resolve logical segment names.

A basic join returning extended attributes for a given incident:

  • SELECT b.INCIDENT_ID, b.CONTEXT, b.ATTR_GROUP_ID, b.C_EXT_ATTR1, b.C_EXT_ATTR2, b.N_EXT_ATTR1, b.D_EXT_ATTR1, b.UOM_EXT_ATTR1 FROM CS.CS_INCIDENTS_EXT_B b WHERE b.INCIDENT_ID = :p_incident_id;
  • SELECT i.INCIDENT_NUMBER, i.SUMMARY, x.C_EXT_ATTR1, x.C_EXT_ATTR2 FROM CS.CS_INCIDENTS_ALL_B i JOIN CS.CS_INCIDENTS_EXT_B x ON x.INCIDENT_ID = i.INCIDENT_ID WHERE i.INCIDENT_NUMBER = :p_number;
  • Auditing recently created extensible records: SELECT EXTENSION_ID, INCIDENT_ID, CREATION_DATE, CREATED_BY FROM CS.CS_INCIDENTS_EXT_B WHERE CREATION_DATE >= TRUNC(SYSDATE);

Because CONTEXT and ATTR_GROUP_ID govern interpretation, reporting logic should filter on them before aggregating attribute values, and should be aware that sparse usage of the C_/N_/D_/UOM_ slots is normal.

Related Objects

The following objects are the most significant for working with this table:

  • CS_INCIDENTS_ALL_B — parent Service Request table; joined via CS_INCIDENTS_EXT_B.INCIDENT_ID = CS_INCIDENTS_ALL_B.INCIDENT_ID (the sole documented FK).
  • CS_INCIDENTS_ALL_TL — translation layer for Service Request text, used when reporting incident descriptions alongside attributes.
  • CS_INCIDENTS_EXT_TL — translation companion to this base table, keyed by EXTENSION_ID.
  • CS_INCIDENTS_EXT_B_PK — the primary-key constraint enforcing surrogate uniqueness on EXTENSION_ID.
  • CS_INCIDENTS_EXT_U1 — the unique index on EXTENSION_ID, the documented business-key candidate.
  • FND_DESCR_FLEX_COLUMN_USAGES / FND_DESCR_FLEX_CONTEXTS — flexfield metadata that maps logical segments to the C_/N_/D_/UOM_ physical columns for a given CONTEXT.
  • CS_INCIDENTS (Service Request) public APIs and the Service Request UI — the maintenance interface that inserts and updates rows in this table when users capture extensible attributes.

In 12.2.2 the 134-column layout and the EXTENSION_ID / INCIDENT_ID relationship are identical in structure to 12.1.1; implementations migrating between releases should verify flexfield context definitions rather than the table definition itself.