Search Results oks_contract_upd_dtls_v




Overview
Explore in AI Chat

Overview

OKS_MISC_UTIL_WEB is a utility package in the APPS schema that supports the Oracle E-Business Suite Service Contracts (OKS) and Telecommunications/Contracts (OKC) module set. It consolidates a set of reusable helper routines used by Service Contracts web-based flows, mass update processing, and installed base utilities. Its classification in ETRM is OTHER, indicating it is not a formal public API but an internal utility layer invoked by dependent packages and views rather than by end users directly.

The package is documented as VALID in the APPS schema and depends on FND_API, OKC_API, and the SYS.STANDARD library. FND_API supplies the standard EBS error-handling and message stack conventions (for example, the FND_API.G_RET_STS_SUCCESS / G_RET_STS_ERROR result codes), while OKC_API supplies common contract header and line interrogation logic. This dependency pattern confirms the package functions as a presentation-and-calculations helper for contract data rather than as an owner of contract business rules.

Key Procedures and Functions

The package exposes 17 documented procedures and functions, grouped by purpose:

Parameter lists are not reproduced here; callers should consult the package specification in the database for exact signatures.

Tables Accessed

The package reads and writes through APPS synonyms across three functional areas:

Usage Notes

OKS_MISC_UTIL_WEB is referenced by the view OKS_CONTRACT_UPD_DTLS_V and by the packages OKS_IB_UTIL_PVT and OKS_MASS_UPDATE_PVT, and it references itself. The presence of the view tie-in is significant: the user search term "oks_contract_upd_dtls_v" corresponds to a contract update details view whose column derivations are supplied by this utility package, so the package effectively feeds contract mass-update and detail screens.

Typical invocation paths are therefore Service Contracts forms and web pages, the mass update concurrent programs that drive OKS_MASS_UPDATE_PVT, and installed base utilities. Because the package is not a public API and its dependencies are standard internal components, customizations should call it only through the supported dependent packages where possible, and should validate behavior after patching, since the document contains no formal interface guarantee.