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:
- OKC_K_LINES_B — aliased CLEB, the contracts line/entity base table holding the coverage line record, its DNZ_CHR_ID header reference, line number, LSE_ID, and the DFF attribute columns.
- OKC_RULE_GROUPS_B — aliased RLGRP, the rule-group container; joined on RLGRP.CLE_ID = CLEB.ID and restricted to RGD_CODE = 'SVC_K'.
- OKC_RULES_B — aliased RULES, holding the individual rule rows; joined on RULES.RGP_ID = RLGRP.ID and filtered to RULE_INFORMATION_CATEGORY = 'RCN'. RULES.ID is exposed as REACTION_RULE_ID.
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
- REACTION_RULE_ID — the OKC_RULES_B primary key (RULES.ID). This is the identifier users search for when linking reaction times back to rule definitions.
- ID / BUS_PROCESS_CLE_ID — the coverage line identifier (CLEB.ID) and its CLE reference.
- LSE_ID / LINE_NUMBER / DNZ_CHR_ID — line type, line sequence, and the parent contract header identifier.
- PROCESS_DEF_ID, REACTION_TIME_NAME, WORK_THRU_YN, ACTIVE_YN — decoded from RULE_INFORMATION1 through 4; the workflow process, the display name of the reaction time, whether work-through is permitted, and the active flag.
- INCIDENT_SEVERITY_ID1 / INCIDENT_SEVERITY_ID2 — the severity range (RULES.OBJECT1_ID1/ID2) to which the reaction time applies.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments carried from the coverage line.
- ROW_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO and concurrency 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.
-
View: OKS_REACTION_TIMES_V 12.2.2
View for Reaction Times for Service Coverage
APPS.OKS_REACTION_TIMES_V·↳ OKC_K_LINES_B·↳ OKC_RULES_B·↳ OKC_RULE_GROUPS_B·Explore OKS module →
-
View: OKS_COV_ACTION_TIMES_V 12.1.1
This view lists the action times defined for business processes in a coverage. This will be used by the Coverage UI.
APPS.OKS_COV_ACTION_TIMES_V·↳ OKC_K_LINES_B·↳ OKS_ACTION_TIMES·↳ OKS_ACTION_TIME_TYPES·Explore OKS module →
-
View: OKS_K_LINES_V 12.2.2
Service Contracts Line Attributes
APPS.OKS_K_LINES_V·↳ OKS_K_LINES_B·↳ OKS_K_LINES_TL·Explore OKS module →
-
Service Contracts Line Attributes History
-
View: OKS_AUTH_LINES_HV 12.1.1
APPS.OKS_AUTH_LINES_HV·↳ OKC_K_LINES_BH·↳ OKC_K_LINES_TLH·↳ OKS_K_LINES_BH·Explore OKS module →
-
View: OKS_AUTH_LINES_HV 12.2.2
APPS.OKS_AUTH_LINES_HV·↳ OKC_K_LINES_BH·↳ OKC_K_LINES_TLH·↳ OKS_K_LINES_BH·Explore OKS module →
-
Service Contracts Line Attributes
-
View: OKS_REACTION_TIMES_V 12.1.1
View for Reaction Times for Service Coverage
APPS.OKS_REACTION_TIMES_V·↳ OKC_K_LINES_B·↳ OKC_RULES_B·↳ OKC_RULE_GROUPS_B·Explore OKS module →
-
View: OKS_REACTION_TIMES_HV 12.1.1
History View for Coverage Reaction Times
APPS.OKS_REACTION_TIMES_HV·↳ OKC_K_LINES_BH·↳ OKC_RULES_BH·↳ OKC_RULE_GROUPS_BH·Explore OKS module →
-
View: OKS_REACTION_TIMES_HV 12.2.2
History View for Coverage Reaction Times
APPS.OKS_REACTION_TIMES_HV·↳ OKC_K_LINES_BH·↳ OKC_RULES_BH·↳ OKC_RULE_GROUPS_BH·Explore OKS module →
-
View: OKS_COV_ACTION_TIMES_V 12.2.2
This view lists the action times defined for business processes in a coverage. This will be used by the Coverage UI.
APPS.OKS_COV_ACTION_TIMES_V·↳ OKC_K_LINES_B·↳ OKS_ACTION_TIMES·↳ OKS_ACTION_TIME_TYPES·Explore OKS module →
-
View: OKS_K_LINES_HV 12.1.1
Service Contracts Line Attributes History
APPS.OKS_K_LINES_HV·↳ OKS_K_LINES_BH·↳ OKS_K_LINES_TLH·Explore OKS module →
-
View: OKS_K_LINES_V 12.1.1
Service Contracts Line Attributes
APPS.OKS_K_LINES_V·↳ OKS_K_LINES_B·↳ OKS_K_LINES_TL·Explore OKS module →
-
View: OKS_K_LINES_HV 12.2.2
Service Contracts Line Attributes History
APPS.OKS_K_LINES_HV·↳ OKS_K_LINES_BH·↳ OKS_K_LINES_TLH·Explore OKS module →
-
View: OKS_AUTH_LINES_V 12.2.2
APPS.OKS_AUTH_LINES_V·↳ OKC_K_LINES_B·↳ OKC_K_LINES_TL·↳ OKS_K_LINES_B·Explore OKS module →
-
View: OKS_AUTH_LINES_V 12.1.1
APPS.OKS_AUTH_LINES_V·↳ OKC_K_LINES_B·↳ OKC_K_LINES_TL·↳ OKS_K_LINES_B·Explore OKS module →
-
Service Contracts Line Attributes History
-
Service Contracts Line Attributes
-
VIEW: OKS.OKS_K_LINES_BH# 12.2.2
-
VIEW: OKS.OKS_K_LINES_B# 12.2.2
-
VIEW: OKS.OKS_K_LINES_BH# 12.2.2
-
VIEW: OKS.OKS_K_LINES_B# 12.2.2
-
TABLE: OKS.OKS_K_LINES_BH 12.1.1
-
VIEW: APPS.OKS_K_LINES_HV 12.2.2
-
VIEW: APPS.OKS_K_LINES_HV 12.1.1
-
VIEW: APPS.OKS_K_LINES_HV 12.1.1
-
VIEW: APPS.OKS_K_LINES_V 12.1.1
-
VIEW: APPS.OKS_K_LINES_V 12.1.1
-
VIEW: APPS.OKS_K_LINES_V 12.2.2
-
TABLE: OKS.OKS_K_LINES_BH 12.2.2
-
VIEW: APPS.OKS_K_LINES_HV 12.2.2
-
VIEW: APPS.OKS_RULES_DFF_DFV 12.2.2
-
VIEW: APPS.OKS_RULES_DFF_DFV 12.1.1