Results for “cs_sr_status_transitions”

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

Overview

CS_SR_STATUS_TRANSITIONS is a Service (CS) module table in Oracle E-Business Suite that stores the permitted status transitions within the allowable statuses associated with a status rule. In service request management, statuses do not move arbitrarily; the application enforces a defined set of legal moves from one status to another. This table is the physical repository of those legal moves, binding a status group, a "from" status, and a "to" status into a single transition record that the runtime UI and validation logic consult before permitting a status change.

The table resides in the CS schema and is marked VALID in the documented ETRM 12.2.2 metadata. It carries 16 documented columns and a single-column primary key, CS_SR_STATUS_TRANSITIONS_PK, defined on STATUS_TRANSITION_ID. A unique index, CS_SR_STATUS_TRANSITIONS_U1, is also defined on STATUS_TRANSITION_ID, confirming that the surrogate identifier is both the primary key and the sole documented business-key candidate.

Heuristic Data Vault classification mined from the foreign-key structure identifies this object as a link. This is a modeling suggestion rather than a physical design statement: the table's purpose is to resolve relationships among status groups, allowed statuses, and incident statuses, which is the classic role of a link entity.

Key Information Stored

The most significant columns fall into three groups: identity, transition endpoints, and auditing/control.

• STATUS_TRANSITION_ID — Surrogate primary key. Uniquely identifies each transition row and is the referenced column for downstream consumers.
• STATUS_GROUP_ID — Foreign key to CS_SR_STATUS_GROUPS_B. Scopes the transition to a particular status group, so transitions are defined per group rather than globally.
• FROM_ALLOWED_STATUS_ID and TO_ALLOWED_STATUS_ID — Foreign keys to CS_SR_ALLOWED_STATUSES. Together they define the allowed-status pair that constitutes the transition.
• FROM_INCIDENT_STATUS_ID and TO_INCIDENT_STATUS_ID — Foreign keys to CS_INCIDENT_STATUSES_B. These capture the incident-level status codes corresponding to the from/to endpoints.
• START_DATE and END_DATE — Effective-dating columns that bound when the transition definition is active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns supporting audit and concurrency.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• TASK_TEMPLATE_ID and WORKFLOW — Configure what task template or workflow is associated with the transition.

Common Use Cases and Queries

The primary use case is validating and rendering legal status moves. A service request screen queries this table to populate the list of statuses a user may select next. A second use case is configuration reporting: administrators audit which transitions exist for a given status group, and whether any pair is missing or duplicated.

A representative query joins the transition to its status group and endpoints:

• SELECT t.status_transition_id, t.status_group_id, t.from_allowed_status_id, t.to_allowed_status_id FROM cs_sr_status_transitions t WHERE t.status_group_id = :group_id;
• SELECT t.* FROM cs_sr_status_transitions t, cs_sr_allowed_statuses f, cs_sr_allowed_statuses o WHERE t.from_allowed_status_id = f.allowed_status_id AND t.to_allowed_status_id = o.allowed_status_id;

Effective-dating filters on START_DATE and END_DATE are common when reporting only currently active transitions.

Related Objects

• CS_SR_STATUS_GROUPS_B — joined on STATUS_GROUP_ID; parent of the transition grouping.
• CS_SR_ALLOWED_STATUSES — referenced twice, via FROM_ALLOWED_STATUS_ID and TO_ALLOWED_STATUS_ID.
• CS_INCIDENT_STATUSES_B — referenced twice, via FROM_INCIDENT_STATUS_ID and TO_INCIDENT_STATUS_ID.
• OZF_SD_STATUS_TRANSITIONS — references this table through STATUS_TRANSITION_ID, extending transition configuration into trade management scenarios.