Results for “incident_status”

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

Overview

CS_SR_EVENT_CODES_B is the base table that stores all event definitions within the Service (CS) module of Oracle E-Business Suite. As the foundational repository for service request event metadata, it defines the events that the Service Request workflow engine can recognize, trigger, and act upon. Each row represents a discrete business event — such as a status transition, an incident closure, or a relationship change — that the application uses to drive automated actions and workflow integrations.

From a Data Vault modeling perspective, the mined foreign key structure classifies this table as hub-leaning. This is a heuristic suggestion only: the table functions as a central reference point for a stable business key (EVENT_CODE), with surrounding descriptive attributes that could be separated into satellite structures in a warehouse implementation. In its native EBS form, however, it remains a conventional normalized base table supporting the Service Request event framework.

Key Information Stored

The table contains 16 documented columns. The most significant are described below.

• EVENT_CODE — The business key and sole column of the primary key CS_SR_EVENT_CODES_B_PK. It uniquely identifies each event definition and is the value referenced by dependent tables.
• FROM_TO_STATUS and INCIDENT_STATUS — Define the status context in which the event applies, distinguishing source (from) and target (to) states, or the incident status associated with the event.
• RELATIONSHIP_TYPE — Specifies the type of relationship that the event governs, where applicable.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating columns that control when an event definition is valid and usable.
• WF_BUSINESS_EVENT_ID — Foreign key linking the event to the Oracle Workflow business event in WF_EVENTS, enabling integration with the workflow event system.
• SEEDED_FLAG — Indicates whether the event definition is Oracle-seeded or customer-defined, which matters for upgrade and support behavior.
• APPLICATION_ID — Identifies the owning application, supporting multi-application coexistence.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent updates.
• ZD_EDITION_NAME — Participates with EVENT_CODE in the unique index CS_SR_EVENT_CODES_B_U1, reflecting editioning support. This pair represents the documented business-key candidate, distinct from the surrogate primary key.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns maintained by the EBS framework.

Common Use Cases and Queries

Typical scenarios include reviewing active event definitions, auditing customer-defined versus seeded events, and tracing which events trigger automated actions.

• Listing active events by status context:

SELECT EVENT_CODE, FROM_TO_STATUS, INCIDENT_STATUS, SEEDED_FLAG
FROM   CS.CS_SR_EVENT_CODES_B
WHERE  SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE)
ORDER  BY EVENT_CODE;

• Identifying seeded versus custom events for upgrade impact analysis:

SELECT SEEDED_FLAG, COUNT(*)
FROM   CS.CS_SR_EVENT_CODES_B
GROUP  BY SEEDED_FLAG;

• Mapping events to workflow business events via WF_BUSINESS_EVENT_ID for integration troubleshooting and event-subscription reporting.

Related Objects

The following relationships are documented and are the most significant for dependency analysis and joins.

• WF_EVENTS — Referenced by CS_SR_EVENT_CODES_B.WF_BUSINESS_EVENT_ID, linking service events to workflow business events.
• CS_SR_ACTION_TRIGGERS — References this table through EVENT_CODE; defines triggers that fire on specific events.
• CS_SR_EVENT_ACTIONS — References this table through EVENT_CODE; defines the actions executed when an event occurs.

Together with these dependent objects, CS_SR_EVENT_CODES_B forms the control layer of the Service Request event and automation framework. Reporting and integration efforts should join through EVENT_CODE to associate event definitions with their resulting triggers, actions, and workflow business events.