Search Results validate_required_numvalue




Overview

OKS_ENTITLEMENTS_PVT is a private PL/SQL package body in the Oracle E-Business Suite Service Contracts (OKS) module. It encapsulates the validation, date computation, and entitlement-processing logic that underpins the Service Contracts entitlement engine in release 12.1.1 and 12.2.2. The package is classified as PVT (private), meaning its program units are not intended for direct external invocation; instead they are consumed by the public APIs and dependent packages that drive contract, coverage, and business-process processing. The header comment identifies the source file as OKSRENTB.pls, with a revision identifier indicating sustained maintenance through the 12.1.3 code line. Because it belongs to the APPS schema and references OKC and CSI entities through APPS synonyms, it operates strictly within the standard EBS data model.

Key Procedures and Functions

The package exposes 99 documented program units, of which the validation and computation routines form the functional core. The user search term validate_required_numvalue maps to the procedure VALIDATE_REQUIRED_NUMVALUE, which is the numeric counterpart of a family of required-value validators.

Package-level constants initialize localized day-of-week names (Bug Fix 5546615) via Get_NLS_Day_Of_Week, supporting multi-language reaction-time calculations.

Tables Accessed

The package reads and writes through APPS synonyms across the contracts, install-base, and trading-partner schemas.

Usage Notes

OKS_ENTITLEMENTS_PVT is invoked indirectly. The Service Contracts forms and the entitlement/reaction-time concurrent programs call the public OKS APIs, which in turn delegate validation and computation to this private package. Because it is marked PVT, custom code should not call it directly; developers should use the supported public OKS API surface. The package is referenced by six other packages, confirming its role as a shared internal library. When troubleshooting entitlement errors, the G_REQUIRED_VALUE and G_UNEXPECTED_ERROR messages raised by VALIDATE_REQUIRED_NUMVALUE and its sibling validators typically surface through OKC_API message handling, so the exception stack or FND message log should be inspected to identify the offending mandatory column.