Search Results business_process_migration

Overview

The APPS.OKS_COVERAGE_MIGRATION package is a service-oriented PL/SQL migration utility within the Oracle E-Business Suite Service (OKS) and Contracts (OKC) modules. Its principal business function is to migrate coverage-related configuration data from the legacy "Rules Architecture" to the newer coverage architecture introduced in later EBS releases. The package header carries the version marker $Header: OKSCOVMS.pls 120.0 2005/05/25 18:30:50 appldev noship $, confirming its origin as a server-side migration script rather than an end-user facing API. It is classified in ETRM as an OTHER API under the APPS schema and is not referenced by any other package, indicating that it is typically invoked directly as a standalone migration step rather than as a dependency of downstream code.

Key Procedures and Functions

The package exposes twelve documented procedures, each following a consistent rowid-range driven batch signature (start rowid, end rowid, return status, message data). They fall into two logical groups.

• Architecture migration procedures: COVERAGE_MIGRATION migrates the coverage header from the rules architecture to the new architecture. BILL_TYPES_MIGRATION migrates billing types. BUSINESS_PROCESS_MIGRATION migrates business process definitions. COVERAGE_TIMES_MIGRATION migrates coverage time definitions. REACTION_TIME_MIGRATION migrates reaction time values. REACTION_TIMEVALUES_MIGRATION migrates reaction time-value pairs.
• History migration procedures: COVERAGE_HISTORY_MIGRATION, BUSS_PROC_HISTORY_MIGRATION, COV_TIMES_HISTORY_MIGRATION, REACTION_TIME_HIST_MIGRATION, REACT_TIMEVAL_HIST_MIGRATION, and BILL_TYPE_HIST_MIGRATION migrate the corresponding historical (audit) rows for each entity. The user query react_timeval_hist_migration maps directly to REACT_TIMEVAL_HIST_MIGRATION, which migrates reaction time-value history records.

The header also declares package-level constants such as G_APP_NAME_OKS, G_APP_NAME, G_UNEXPECTED_ERROR, G_SQLERRM_TOKEN, and G_SQLCODE_TOKEN, and typed collection variables (x_ctzv_tbl_in, l_ctzv_tbl_in, x_cvtv_tbl_in, l_cvtv_tbl_in, x_acmv_tbl_in, l_acmv_tbl_in) that buffer coverage timezone, coverage time, and action time records during processing.

Tables Accessed

All table access is performed through APPS synonyms. The migration reads from the legacy rules tables OKC_RULES_B, OKC_RULES_BH, OKC_RULES_TLH, OKC_RULE_GROUPS_B, OKC_RULE_GROUPS_BH, OKC_REACT_INTERVALS, OKC_REACT_INTERVALS_H, OKC_TIMEVALUES_B, OKC_TIMEVALUES_BH, OKC_COVER_TIMES, and OKC_COVER_TIMES_H. It writes to the new-architecture coverage tables OKS_K_LINES_TLH, OKC_K_LINES_B, OKC_K_LINES_BH, and OKS_ACTION_TIMES. The _B/_BH suffixed tables hold base and history rows respectively, which is why each entity has a paired non-history and history migration procedure.

Usage Notes

This package is a one-time or incremental data migration utility, not a runtime business API. It is typically invoked from concurrent programs (range-partitioned by rowid for parallel processing), from SQL*Plus migration scripts, or from custom upgrade harnesses during an EBS upgrade or patch application. The rowid-range parameters make it suitable for committing in batches and re-running after failure. Because it has no inbound references (0 dependent packages), and because it carries the noship header stamp, it is best treated as an internal migration tool. Direct invocation should be restricted to planned downtime or migration windows, with backups taken of the source rules tables before execution.