Search Results bus_process_cle_id




Overview
Explore in AI Chat

Overview

OKS_COV_ACTION_TIMES_V is an APPS-owned reporting and integration view within the Oracle E-Business Suite Service Contracts (OKS) module. Its declared purpose is to list the action times defined for business processes attached to a coverage, and it is consumed directly by the Coverage user interface. In the context of EBS 12.1.1 and 12.2.2, the view provides a denormalized, read-only projection that joins coverage line information to the reaction-time definitions configured for each business process, freeing the UI and downstream consumers from having to assemble those relationships at runtime.

Because the view is registered as VALID in the APPS schema and exposes standard WHO audit columns plus a full set of DFF attribute columns, it is suitable both for the Coverage UI's internal querying and for ad hoc extraction through tools such as Oracle Reports, BI Publisher, or direct SQL. It is a view, not a table, so no DML should be issued against it; changes must be made to the underlying coverage and action-time records.

Underlying Base Objects

The view is defined over four documented base objects:

  • OKC_K_LINES_B (SYNONYM) — the contractual coverage line table, aliased CLEB, which supplies the primary row identity, line number, coverage (DNZ_CHR_ID), and descriptive flexfield attributes.
  • OKS_K_LINES_V (VIEW) — aliased OKSL, joined on CLE_ID = CLEB.ID, supplying the business process definition (PDF_ID), incident severity, reaction time name, and work-through/active flags.
  • OKS_ACTION_TIME_TYPES (SYNONYM) — aliased ACT, joined on CLE_ID = CLEB.ID, supplying ACTION_TYPE_CODE.
  • OKS_ACTION_TIMES (SYNONYM) — aliased ACY, joined on COV_ACTION_TYPE_ID = ACT.ID, supplying the UOM and the seven per-day duration columns.

The join is constrained by CLEB.LSE_ID IN (4, 17, 22), restricting the view to the coverage line types that carry business-process action times.

Key Columns

Common Use Cases and Queries

Typical scenarios include reviewing the configured action times for a coverage, validating reaction-time setup before contract activation, and feeding integration extracts that populate external ITSM or service-desk systems.

  • Listing all action times for a specific coverage:
SELECT bus_process_cle_id, process_def_id, action_type_code,
       reaction_time_name, uom_code, sun_duration, mon_duration
FROM   apps.oks_cov_action_times_v
WHERE  dnz_chr_id = :p_coverage_id;
  • Resolving the user's search term "bus_process_cle_id" — using it to retrieve the related business process line metadata:
SELECT bus_process_cle_id, line_number, incident_severity_id1,
       work_thru_yn, active_yn
FROM   apps.oks_cov_action_times_v
WHERE  bus_process_cle_id = :p_cle_id;
  • Auditing recently modified reaction-time configurations:
SELECT id, bus_process_cle_id, last_updated_by, last_update_date
FROM   apps.oks_cov_action_times_v
WHERE  last_update_date >= SYSDATE - 7;

All queries should filter on DNZ_CHR_ID or BUS_PROCESS_CLE_ID to keep result sets bounded, and use the view strictly for read operations.