Search Results oks_k_lines




Overview

The APPS.OKS_COVERAGE_MIGRATION package body is a Service Contracts (OKS) data migration utility responsible for converting legacy Oracle Contracts (OKC) rule and line structures into the Service Contracts coverage model. Prior to the extended coverage and reaction-time framework, warranty, service, and subscription entitlements were stored as rule-information records attached to contract lines in the OKC schema. The coverage migration package reads these legacy OKC rule groups, rules, and contract lines and creates the corresponding OKS coverage records, bill types, business processes, coverage times, and reaction intervals that the Service Contracts application expects.

The package header carries the identifier $Header: OKSCOVMB.pls 120.0 2005/25/05, indicating it is an older, noship utility file retained for upgrade and internal migration purposes. It is not a public API and is not referenced by any other package in the EBS schema, confirming its role as a standalone one-time conversion program rather than a reusable service component.

Key Procedures and Functions

The package exposes twelve documented procedures, organized into current-data migrations and their corresponding history-table migrations:

Each procedure accepts rowid boundaries where applicable, enabling the caller to partition the conversion into manageable batches.

Tables Accessed

Source data is read from the OKC contract schema: OKC_K_LINES_B (contract lines), OKC_RULE_GROUPS_B (rule group headers), OKC_RULES_B (rule-information details), OKC_COVER_TIMES and OKC_TIMEVALUES_B (coverage timing), and OKC_REACT_INTERVALS (reaction intervals). Historical source rows are drawn from the _BH and _TLH variants, including OKC_K_LINES_BH, OKC_RULES_BH, OKC_RULES_TLH, OKC_RULE_GROUPS_BH, OKC_TIMEVALUES_BH, OKC_REACT_INTERVALS_H, and OKC_COVER_TIMES_H. Target records are inserted into OKS_K_LINES_B, OKS_K_LINES_TLH, and OKS_ACTION_TIMES. The NOT EXISTS predicate against OKS_K_LINES_B prevents duplicate coverage creation on re-run.

Usage Notes

This package is invoked during upgrade or data-conversion projects, typically from a concurrent program or a controlled SQL*Plus script executed by a DBA, rather than from an application form. Because it is neither referenced by other packages nor exposed as a public API, it should not be called from custom application code. Deployments should run the migration in rowid-range batches during a maintenance window, verify row counts between OKC source and OKS target tables, and retain the return status and message output for audit purposes. In Oracle EBS 12.1.1 and 12.2.2 the object remains present in the APPS schema with the same signature set.