Results for “okx_incident_severits_v”

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

Overview

The view OKX_INCIDENT_SEVERITS_V is an APPS-owned database object in Oracle E-Business Suite, registered under the OKX – Contracts Integration product family. It exposes service request and action severity reference data, presenting a denormalized, translation-aware read model over the severity base tables in the Service (CS) module. In EBS 12.1.1 and 12.2.2, the view is documented as VALID in the ETRM repository and serves as the integration and reporting surface through which severity codes, their translated names and descriptions, effective date ranges, and a computed active/inactive status are retrieved. Its principal consumers are concurrent programs, Forms-based lookups, and external integration interfaces that must resolve a service request's severity without querying the multi-language base tables directly.

Underlying Base Objects

The view text defines a two-table join over the following documented base objects, both exposed to APPS as synonyms:

• CS_INCIDENT_SEVERITIES_B — the base table holding the language-independent severity definition, including the primary key INCIDENT_SEVERITY_ID, the INCIDENT_SUBTYPE discriminator, and the START_DATE_ACTIVE / END_DATE_ACTIVE effective dating columns.
• CS_INCIDENT_SEVERITIES_TL — the translation table holding the language-dependent NAME and DESCRIPTION columns, joined on INCIDENT_SEVERITY_ID and filtered to the session language.

The join predicate is B.INCIDENT_SEVERITY_ID = T.INCIDENT_SEVERITY_ID combined with T.LANGUAGE = USERENV('LANG'), ensuring that each row returned reflects the current runtime language of the calling session. Because the view is defined over the _B and _TL pair rather than a _VL view, the language restriction is applied explicitly inside the view text rather than inherited.

Key Columns

• ID1 — the severity identifier, selected from B.INCIDENT_SEVERITY_ID. This is the surrogate key used to reference a severity in downstream records.
• ID2 — a literal placeholder constant ('#') included to satisfy the standard two-column ID convention used by EBS lookup and LOV constructs.
• INCIDENT_SUBTYPE — categorizes the severity by the incident subtype to which it applies, allowing distinct severity sets for different request or action classes.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective dating window governing when the severity is valid for use.
• STATUS — a derived column computed with nested DECODE(SIGN(...)) expressions against TRUNC(SYSDATE) and the effective dates. It returns 'I' for inactive (current date precedes the start date or follows the end date) and 'A' for active. Null effective dates default to TRUNC(SYSDATE), so an open-ended severity evaluates as active.
• NAME — the translated severity name from CS_INCIDENT_SEVERITIES_TL, presented to users and integrations in the session language.
• DESCRIPTION — the translated descriptive text corresponding to the severity.

Common Use Cases and Queries

The view is typically used to populate severity list of values, to validate that a selected severity is currently active before assigning it to a service request, and to feed integration payloads that require a localized severity label. A representative query retrieves only currently active severities for a given subtype:

• SELECT id1, name, description, incident_subtype, start_date_active, end_date_active FROM apps.okx_incident_severits_v WHERE status = 'A' AND incident_subtype = :p_subtype ORDER BY name;
• SELECT id1, name, status FROM apps.okx_incident_severits_v ORDER BY incident_subtype, name;

Because the language filter is bound to USERENV('LANG'), callers must set the session language (for example via FND_GLOBAL initialization in concurrent programs) to obtain the intended translated names. The view is read-only; severity maintenance is performed against the underlying _B and _TL tables using the standard EBS multi-language API conventions.