Results for “sunday_react_resolve_time”

8 results




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

Overview

OKS_ENT_REACT_TIME_L_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKS – Service Contracts (Service Contracts / Enterprise Contracts) product family. The view consolidates reaction time and resolution time definitions maintained against coverage action types, exposing them in a denormalized, day-of-week oriented layout. In ETRM 12.1.1 and 12.2.2 the object carries a VALID status, indicating that it compiles cleanly against its referenced base objects.

Functionally, the view answers the question of how quickly a service provider must respond to, or resolve, a service request associated with a given action type. Rather than storing one row per weekday, the view pivots the underlying time definitions into a single row per reaction interval, presenting seven separate duration columns (Sunday through Saturday) alongside a unit of measure column. The REACT_TUOM column — the object of the search term "react_tuom" — carries the unit of measure code in which those durations are expressed. Because the underlying tables are keyed on coverage action types, the view is a natural source for contract entitlement reporting, service level agreement analysis, and integration extracts that feed external dispatch or SLA monitoring systems.

The view is read-only reference data and is not a transactional interface; it is intended for queries, reports, and inbound integration lookups rather than direct DML.

Underlying Base Objects

The documented view text is defined over two synonyms resolving to OKS base tables:

  • OKS_ACTION_TIME_TYPES (aliased ACT) — the action type header, supplying the reaction interval identifier and the action type classification.
  • OKS_ACTION_TIMES (aliased ACM) — the per-action-type time detail rows, supplying the unit of measure code and the individual weekday duration values.

The join predicate is ACT.ID = ACM.COV_ACTION_TYPE_ID, establishing a one-to-many relationship between an action type and its associated time definition rows. The view therefore inherits the security and multi-org behavior of the OKS Service Contracts tables beneath it. Column mappings that are not physically present in the base tables are projected as NULL placeholders, a common technique used to preserve a stable interface for downstream consumers.

Key Columns

  • REACTION_INTERVAL_ID — the action type identifier (ACT.ID); the primary grouping key for the reaction interval definition.
  • TIME_VALUE_ID — the time detail row identifier (ACM.ID) within the action time table.
  • REACT_TUOM — the unit of measure code (ACM.UOM_CODE) in which reaction and resolution durations are expressed, for example minutes, hours, or days. This is the column referenced by the "react_tuom" search term.
  • REACTION_ON and REACT_WITHIN_TIME — projected as NULL in this view version, retained for interface compatibility.
  • SUNDAY_REACT_RESOLVE_TIME through SATURDAY_REACT_RESOLVE_TIME — seven duration columns carrying the day-specific reaction or resolution allowance derived from the underlying *_DURATION columns of OKS_ACTION_TIMES.
  • TIME_TYPE — the action type classification (ACT.ACTION_TYPE_CODE), distinguishing reaction versus resolution semantics.

Common Use Cases and Queries

Typical uses include validating that every active coverage action type has a reaction time defined in a recognized unit of measure, populating SLA reports that show day-by-day response commitments, and exporting reaction interval data to external service management tools.

Listing all reaction time definitions with their unit of measure:

SELECT reaction_interval_id,
       time_value_id,
       react_tuom,
       time_type
FROM   apps.oks_ent_react_time_l_v
ORDER  BY reaction_interval_id;

Displaying the weekday resolution schedule for a specific interval:

SELECT reaction_interval_id,
       monday_react_resolve_time,
       tuesday_react_resolve_time,
       wednesday_react_resolve_time,
       thursday_react_resolve_time,
       friday_react_resolve_time,
       saturday_react_resolve_time,
       sunday_react_resolve_time
FROM   apps.oks_ent_react_time_l_v
WHERE  reaction_interval_id = :action_type_id;

Identifying definitions expressed in unexpected units:

SELECT reaction_interval_id,
       react_tuom,
       COUNT(*)
FROM   apps.oks_ent_react_time_l_v
GROUP  BY reaction_interval_id, react_tuom;

Because the view is a simple projection over two OKS tables with no complex aggregation, performance is governed by indexing on COV_ACTION_TYPE_ID and ID in the base tables. Applications should treat the NULL-projected columns as reserved placeholders and avoid filtering on them.