Search Results oks_ent_react_time_h_v




Overview
Explore in AI Chat

Overview

The OKS_ENT_REACT_TIME_H_V view is an APPS-owned, VALID database view within the Oracle E-Business Suite Service Contracts (OKS) module. Its documented purpose is to list all reaction time header information. Reaction times are the contractual commitments, defined on entitlement or coverage lines, that specify how quickly a service provider must respond to an incident of a given severity. This view therefore surfaces the header-level definition of each reaction time record, including the parent coverage, the transaction group it belongs to, the reaction interval, and the associated incident severity.

Because it exposes a denormalized, business-friendly projection of reaction time data, the view is well suited for reporting, operational dashboards, and integration interfaces that need to evaluate contractual service levels without navigating the underlying normalized service contract tables directly. The presence of the SEVERITY_ID column explains why the view is frequently retrieved when users search for "severity_id": it is one of the principal keys used to map a reaction time to an incident severity definition. The view is available in both Oracle EBS 12.1.1 and 12.2.2, with the metadata provided reflecting the 12.2.2 ETRM documentation.

Underlying Base Objects

The view text demonstrates that OKS_ENT_REACT_TIME_H_V is a join across several service contract entities. The documented base objects are:

The join is constrained by a lineage relationship (BP.ID = RT.CLE_ID), a level-set filter (RT.LSE_ID IN (4, 17, 22)), a language restriction (TL.LANGUAGE = USERENV('LANG')), and equality conditions tying severity, service lines, and action time types back to the reaction time line.

Key Columns

  • COVERAGE_ID — the identifier of the parent coverage line (the entitlement) under which the reaction time is defined.
  • TXN_GROUP_ID — the transaction group identifier for the reaction time contract line.
  • REACTION_TIME_ID — the primary identifier of the reaction time header record.
  • REACTION_INTERVAL_ID — the identifier of the associated reaction interval (the response window).
  • NAME — the language-specific name of the reaction time, sourced from the translated line table.
  • SEVERITY_ID — the incident severity identifier, derived from SV.ID1 in the incident severity view. This is the column most commonly used to filter or group reaction times by severity.
  • SEVERITY_NAME — the human-readable severity description.
  • WORK_THROUGH_YN — indicates whether the reaction applies on a work-through basis.
  • ACTIVE_YN — indicates whether the reaction time is currently active.
  • TIME_TYPE — the action/time type classification, derived from ACTION_TYPE_CODE.

Common Use Cases and Queries

Typical uses include reviewing which reaction times exist per severity per coverage, auditing active versus inactive commitments, and feeding downstream SLA or incident management processes. A representative query joining to the incident severity name might be:

SELECT rt.coverage_id,
       rt.reaction_time_id,
       rt.name,
       rt.severity_id,
       rt.severity_name,
       rt.active_yn,
       rt.time_type
FROM   apps.oks_ent_react_time_h_v rt
WHERE  rt.severity_id = :p_severity_id
AND    rt.active_yn = 'Y'
ORDER BY rt.coverage_id, rt.name;

Because SEVERITY_ID is exposed directly, the view simplifies severity-driven reporting that would otherwise require reconstructing the join between service lines and the incident severity view. Integrations may also consume the view when synchronizing contractual response commitments into external service management systems.