Search Results close_flag

Overview

CS_INC_RELATED_STATUSES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered under the Service (CS) product family. Its documented purpose is to expose the related statuses associated with a service request type, derived from the service request lifecycle configuration held in the incident cycle steps. In Oracle EBS 12.1.1 and 12.2.2, service requests (incidents) move through statuses defined by an incident type lifecycle. Each lifecycle is decomposed into ordered cycle steps, and each step is linked to an incident status. This view flattens that relationship, presenting one row per incident cycle step together with its resolved status name.

Because the view joins the cycle-step configuration to the translated status values, it provides a convenient reporting and integration surface for the status-versus-step mapping without requiring callers to reproduce the join themselves. It is commonly consumed by custom concurrent programs, OA Framework extensions, SOA/B2B integrations, and ad-hoc reporting against the Service module. The presence of descriptive flexfield columns (ATTRIBUTE1–15 and CONTEXT), audit columns, and OBJECT_VERSION_NUMBER indicates the view is intended to mirror the concurrency-control and DFF behavior of the underlying entity.

Underlying Base Objects

The view is documented as being defined over two referenced base objects: CS_INCIDENT_CYCLE_STEPS (exposed through a synonym) and CS_INCIDENT_STATUSES_VL (itself a view). The join condition is C.INCIDENT_STATUS_ID = STATUS.INCIDENT_STATUS_ID.

• CS_INCIDENT_CYCLE_STEPS — the primary driver, aliased C. It holds the cycle-step definitions for each incident type, including step level, next step level, status linkage, date ranges, and the VALIDATE_FLAG and CLOSE_FLAG indicators.
• CS_INCIDENT_STATUSES_VL — aliased STATUS. It supplies the translated/MLS-derived STATUS_NAME for each INCIDENT_STATUS_ID, enabling the view to return a human-readable status label rather than only the numeric identifier.
• The view itself is not a base table; it is a non-updatable projection of these two objects and should not be treated as a DML target.

Key Columns

• ROW_ID — the ROWID of the underlying CS_INCIDENT_CYCLE_STEPS row, useful for identity and debugging.
• STATUS_NAME — the translated name of the related status, sourced from CS_INCIDENT_STATUSES_VL.
• INCIDENT_CYCLE_STEPS_ID — primary identifier of the cycle step.
• STEP_LEVEL / NEXT_INCIDENT_STEP_LEVEL — position of the step in the lifecycle and the level of the following step, defining lifecycle ordering.
• INCIDENT_STATUS_ID / INCIDENT_TYPE_ID — the status and the service request type to which the step belongs.
• DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE — descriptive text and effective-dating range for the step.
• VALIDATE_FLAG — indicates whether validation applies to the step.
• CLOSE_FLAG — the column most relevant to a "close_flag" search; it identifies statuses/steps that represent a closed state for the service request, allowing reporting logic to distinguish open from closed statuses.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE1–15 and CONTEXT — descriptive flexfield segments.
• OBJECT_VERSION_NUMBER — optimistic concurrency identifier inherited from the underlying record.

Common Use Cases and Queries

The view is typically used to report the status-to-cycle-step mapping for a service request type, to identify which statuses are terminal/closed via CLOSE_FLAG, or to drive integration logic that maps external states onto EBS service request statuses.

• List all related statuses for a given incident type, ordered by lifecycle position.
• Isolate the statuses that represent a closed service request.
• Resolve a numeric status or step identifier to its display name for reporting.

Sample query — related statuses for an incident type:

SELECT status_name, incident_status_id, step_level, close_flag
FROM cs_inc_related_statuses_v
WHERE incident_type_id = :p_incident_type_id
ORDER BY step_level;

Sample query — closed statuses only (addresses the "close_flag" lookup):

SELECT incident_cycle_steps_id, status_name, incident_status_id, close_flag
FROM cs_inc_related_statuses_v
WHERE close_flag = 'Y'
AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Because the view joins to CS_INCIDENT_STATUSES_VL for the translated STATUS_NAME, results respect the session's language setting, making it suitable for multilingual reporting. Date-range filtering on START_DATE_ACTIVE and END_DATE_ACTIVE should be applied when only currently active steps are required.