Results for “oks_bus_processes_hv”

24 results




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

Overview

OKS_BUS_PROCESSES_HV is a Service Contracts (OKS) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as the History View for Coverage Business Process. Its purpose is to expose the versioned, historical relationship between a contract coverage line and the business process associated with it. In the EBS data model, coverage lines are versioned through the OKC_K_LINES_B / OKC_K_LINES_BH table pair, where the _BH table stores prior and current versions. This view joins that history to the contract line item records and to the business process definition, producing a denormalized, date-effective result set suitable for concurrent programs, Oracle Reports, OAF-based inquiries, and external integrations that need to trace which business process applied to a coverage across contract revisions.

Underlying Base Objects

Per documented ETRM metadata, the view is defined over four referenced objects:

The joins are: CITEM.CLE_ID = CLEB.ID and CITEM.MAJOR_VERSION = CLEB.MAJOR_VERSION; CITEM.JTOT_OBJECT1_CODE = JTFOB.OBJECT_CODE with JTFOB.OBJECT_CODE = 'OKX_BUSIPROC'; and BUSPR.ID1 / ID2 = CITEM.OBJECT1_ID1 / OBJECT1_ID2. A hard-coded predicate restricts results to CLEB.LSE_ID IN (3, 16, 21), which corresponds to specific contract line style values reserved for coverage business process records.

Key Columns

  • ROW_ID — the ROWID of the underlying OKC_K_LINES_BH row, useful for direct row access.
  • ID, OBJECT_VERSION_NUMBER, MAJOR_VERSION — the coverage line identity and versioning keys; MAJOR_VERSION is critical for reconstructing history.
  • COVERAGE_CLE_ID, LSE_ID, LINE_NUMBER, DNZ_CHR_ID — the coverage line ID (CLE_ID), line style, line sequence, and the owning contract header ID (DNZ_CHR_ID).
  • BUS_PROCESS_ID1, BUS_PROCESS_ID2, BUS_PROCESS_NAME — the business process identifiers and human-readable name.
  • START_DATE, END_DATE — the effective period of the coverage line version.
  • ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the descriptive flexfield context and segments.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns for change tracking.

Common Use Cases and Queries

Typical scenarios include auditing which business process was attached to a coverage at a point in time, reconciling history versions against the current OKC_K_LINES_B record, and extracting data for downstream entitlement or billing systems. A representative query follows:

  • SELECT id, major_version, coverage_cle_id, dnz_chr_id, bus_process_name, start_date, end_date FROM oks_bus_processes_hv WHERE dnz_chr_id = :contract_id ORDER BY id, major_version;
  • SELECT bus_process_id1, bus_process_id2, COUNT(*) FROM oks_bus_processes_hv GROUP BY bus_process_id1, bus_process_id2;
  • SELECT v.id, v.major_version, v.start_date, v.end_date FROM oks_bus_processes_hv v WHERE v.coverage_cle_id = :cle_id AND TRUNC(SYSDATE) BETWEEN v.start_date AND NVL(v.end_date, TRUNC(SYSDATE)+1);

Because the view is built over history tables and a restricted LSE_ID set, queries should always filter on the contract or coverage line identifiers to benefit from the underlying indexed access paths. Note that the similarly named OKC_K_ITEMS_H is a referenced base object rather than a substitute for this view; callers searching on "okc_k_items_h" should recognize that OKS_BUS_PROCESSES_HV is the join-based presentation built partly upon it.