Results for “cs_sr_allowed_statuses”

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

Overview

CS_SR_ALLOWED_STATUSES is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the set of statuses permitted within a given status rule for service requests. Each row associates a Service Request status with a status group, thereby defining which statuses are legitimately reachable or selectable under a particular rule configuration. This table acts as the authoritative list of "allowable statutes" (statuses) enforced by the Service Request status engine.

From a data modeling perspective, the mined Foreign Key structure classifies CS_SR_ALLOWED_STATUSES as satellite-leaning. The table records descriptive configuration detail that hangs off the primary reference entities CS_SR_STATUS_GROUPS_B and CS_INCIDENT_STATUSES_B, rather than acting as an independent hub or a pure association link. It carries a surrogate primary key and its own effective-dating attributes, consistent with satellite behavior within a Data Vault style model.

Key Information Stored

The table documents 11 columns. The most significant are listed below.

• ALLOWED_STATUS_ID — Surrogate primary key, enforced by the constraint CS_SR_ALLOWED_STATUSES_PK and backed by the unique index CS_SR_ALLOWED_STATUSES_U1. This is the single documented business-key candidate and the column referenced by dependent transition rows.
• STATUS_GROUP_ID — Foreign key to CS_SR_STATUS_GROUPS_B. Identifies the status group (rule grouping) to which the allowed status belongs.
• INCIDENT_STATUS_ID — Foreign key to CS_INCIDENT_STATUSES_B. Identifies the specific Service Request status that is permitted within the status group.
• START_DATE and END_DATE — Effective-dating columns that define the active window of the allowed-status definition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit (WHO) columns tracking record creation and modification.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Object Library to detect concurrent updates.

Common Use Cases and Queries

The primary use case is validating and listing the statuses available within a status rule. Typical reporting queries join the allowed statuses to the status group and to the incident status definition to resolve descriptive names.

• Listing all allowable statuses for a status group:

  SELECT a.ALLOWED_STATUS_ID, a.STATUS_GROUP_ID, a.INCIDENT_STATUS_ID
  FROM   CS.CS_SR_ALLOWED_STATUSES a
  WHERE  a.STATUS_GROUP_ID = :p_status_group_id
  AND    TRUNC(SYSDATE) BETWEEN a.START_DATE AND NVL(a.END_DATE, SYSDATE);

• Determining whether a status transition is permitted, by joining allowed statuses to CS_SR_STATUS_TRANSITIONS on FROM_ALLOWED_STATUS_ID and TO_ALLOWED_STATUS_ID.
• Auditing configuration changes over time using the START_DATE/END_DATE effective window.
• Reporting inactive or expired allowed-status definitions where END_DATE is in the past.

Related Objects

• CS_SR_STATUS_GROUPS_B — Referenced via STATUS_GROUP_ID; parent status group definition.
• CS_INCIDENT_STATUSES_B — Referenced via INCIDENT_STATUS_ID; defines the Service Request status.
• CS_SR_STATUS_TRANSITIONS — Dependent table referencing CS_SR_ALLOWED_STATUSES through FROM_ALLOWED_STATUS_ID and TO_ALLOWED_STATUS_ID; defines permitted movement between allowed statuses.
• CS_INCIDENT_STATUSES_TL and CS_SR_STATUS_GROUPS_TL — Translation tables commonly joined for display names.
• Service Request status validation APIs in the CS module, which enforce the allowed-status rules at transaction time.

Together these objects form the configuration backbone of the Service Request status engine, with CS_SR_ALLOWED_STATUSES providing the central list of permitted statuses.