Results for “work_thru_yn”

50+ results




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

Overview

OKS_REACTION_TIMES_V is a VALID APPS-schema view within the Oracle E-Business Suite Service Contracts (OKS) module. It presents reaction times defined for service coverage, exposing the reaction-time commitments that govern how quickly a service provider must respond to an incident once coverage applies. The view is a reporting and integration artifact rather than a transactional entity: it flattens the rule-based configuration held in the OKC contracts foundation tables into a denormalized, easily consumable row set. In Oracle EBS 12.1.1 and 12.2.2 the view remains owned by APPS and is documented under the ETRM reference set for OKS. Because the underlying reaction-time data lives in flexible rule structures (OKC_RULES_B) rather than in dedicated columns, the view performs the decoding of positional RULE_INFORMATION attributes into named, meaningful columns. This makes it the primary supported access path for queries, concurrent programs, and external integrations that need to report reaction times without reimplementing the rule-group and rule-category join logic themselves. Its dependency on service line types (LSE_ID 4, 17, 22) means it returns only reaction times attached to those specific service coverage line configurations.

Underlying Base Objects

The view is defined over three documented base objects, each referenced through an APPS synonym:

The join path is therefore line to rule group to rule, with the rule's positional RULE_INFORMATIONn columns decoded into process definition, reaction time name, work-through flag, active flag, and incident severity identifiers.

Key Columns

Common Use Cases and Queries

Typical uses include reporting all reaction times for a contract, validating active reaction-time rules, and integrating severity-to-reaction-time mappings into external service management systems. A representative query filtering by the searched identifier:

  • Reaction times for a specific contract:
    SELECT reaction_rule_id, reaction_time_name, incident_severity_id1, incident_severity_id2, active_yn
    FROM oks_reaction_times_v
    WHERE dnz_chr_id = :p_contract_id
    AND active_yn = 'Y';
  • Resolving a reaction rule to its coverage line:
    SELECT id, bus_process_cle_id, line_number, process_def_id
    FROM oks_reaction_times_v
    WHERE reaction_rule_id = :p_reaction_rule_id;
  • Listing all defined reaction times with severity ranges for administrative review:
    SELECT reaction_time_name, incident_severity_id1, incident_severity_id2, work_thru_yn, active_yn
    FROM oks_reaction_times_v
    ORDER BY reaction_time_name;

Because the view already decodes the RCN rule category, consumers should not query OKC_RULES_B directly for reaction-time reporting; doing so risks missing the seed-data decode logic embedded in the view definition.