Search Results oks_mass_upd_pvt




Overview
Explore in AI Chat

Overview

OKS_MASS_UPD_PVT is a private (PVT-classified) PL/SQL package in the APPS schema that supports Service Contracts mass update processing in Oracle E-Business Suite. It belongs to the Oracle Service (OKS) module and is designed to apply bulk changes to large populations of service contracts, contract lines, and sublines without requiring users to modify each contract individually. The package encapsulates validation logic, temporary table population, cascade selection, concurrent program submission, and the actual update procedures that change price, status, and effectivity values. Because it is classified as a private package, it is not intended as a public integration API; it is invoked internally by the Service Contracts mass update user interface and concurrent processing framework. It appears in both 12.1.1 and 12.2.2 environments with VALID status, and it is not referenced by any other package, confirming its role as a top-level internal driver for the mass update feature rather than a shared library.

Key Procedures and Functions

The package exposes nineteen documented procedures and functions:

Tables Accessed

The package reads and writes the staging tables OKS_HEADERS_TEMP, OKS_LINES_TEMP, and OKS_SUBLINES_TEMP during preparation and execution. Contract data is drawn from OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_LINES_B, OKS_K_HEADERS_B, OKS_K_LINES_B, and OKS_BILL_CONT_LINES, OKS_BILL_SUB_LINES for billing-related lines. Lookups and reference data come from OKC_STATUSES_B, CSI_SYSTEMS_TL, FND_CURRENCIES, HZ_CUST_ACCOUNTS, and HZ_PARTIES. These tables supply the contract, status, currency, customer, and installed base context required for validation and update.

Usage Notes

OKS_MASS_UPD_PVT is normally invoked through the Service Contracts mass update form or the associated concurrent program, not directly by developers. Because the API classification is PVT, Oracle does not guarantee its interface for external callers. Custom code that needs to invoke mass update behavior should call the supported public APIs or the mass update user interface; direct calls to this package's procedures risk breakage during upgrades. The LAUNCH_MASSUPD_CONC_PROG and MASS_UPDATE_SUBMIT routines are the typical entry points when the operation is run concurrently. Performance is influenced by the volume of contracts staged in OKS_HEADERS_TEMP, OKS_LINES_TEMP, and OKS_SUBLINES_TEMP, so large batches should be scheduled during low-activity periods.