Search Results g_exception_rollback

Overview

OKS_RENEW_PVT is a private (PVT) PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Knowledge Solutions (OKS) module — the Service Contracts / Contracts Core schema family — specifically to the subscription and service renewal sub-component. The "RENEW" token in the package name indicates its scope: it supports the logic that drives service contract and subscription renewal processing, including the validation, lifecycle transition, and error-handling behavior that underpins renewal workflows invoked from the Service Contracts user interface and from scheduled renewal concurrent programs.

The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema and honors the caller's name-resolution context. Its header references a shared set of global message constants and exception tokens inherited from OKC_API (the Contracts Core API layer), including G_FND_APP, G_RECORD_LOGICALLY_DELETED, G_REQUIRED_VALUE, G_INVALID_VALUE, G_COL_NAME_TOKEN, G_PARENT_TABLE_TOKEN, and G_CHILD_TABLE_TOKEN. These constants are reused across the OKC/OKS contract family to produce consistent, "FND-style" error and message handling. Global exceptions G_EXCEPTION_HALT_VALIDATION, G_EXCEPTION_ROLLBACK, and G_ERROR define the internal control-flow signals the package raises when validation cannot continue, when the current transaction must be rolled back, or when a general error has occurred. The G_PKG_NAME constant ('OKS_RENEW_PVT') and G_APP_NAME constant (OKC_API.G_APP_NAME) provide the standard logging identity used by the debug and error routines.

Key Procedures and Functions

One documented procedure exists in this package:

• DEBUG_LOG — A diagnostic logging procedure. Two overloads are visible in the source excerpt. The first accepts a program name, an optional performance message, an optional error message, and an optional path. The second overload accepts a program name, optional performance message, and an error message. It is intended purely for instrumentation: callers use it to record timing/performance data and error diagnostics to a log destination. Because it references UTL_FILE, output is directed to a server-side file whose location is governed by the database directory and UTL_FILE parameters. DEBUG_LOG is not part of the public renewal business logic; it is a developer/debugging utility retained in the package for troubleshooting renewal execution.

ETRM documents two procedures/functions in total for this package, both resolving to the DEBUG_LOG overloads. No public renewal API procedures are exposed in the documented metadata, which is consistent with the package's PVT classification: the renewal business logic is intended to be called internally by other OKS packages rather than directly by end users or external integrations.

Tables Accessed

The documented referenced objects are system and utility views rather than application tables:

• UTL_FILE — The Oracle-supplied PL/SQL file I/O package. OKS_RENEW_PVT uses it through DEBUG_LOG to write diagnostic lines to an operating-system file on the database server.
• V$PARAMETER — The dynamic performance view exposing current database initialization parameter values. This is typically referenced to read parameters such as UTL_FILE_DIR or related settings, confirming that file-based logging is permitted and where output may be written. No OKS or OKC application tables are documented as directly accessed by name in the available excerpt, which reflects the partial nature of the metadata: renewal logic would ordinarily manipulate subscription and contract tables elsewhere in the OKS/OKC schema.

Usage Notes

OKS_RENEW_PVT is a private package and is not intended for direct invocation by end users, form personalizations, or external applications. It is referenced by four other packages according to the ETRM metadata, meaning it sits inside the internal call graph of the Service Contracts renewal stack. Typical invocation occurs from the Service Contracts renewal forms and from the renewal-oriented concurrent programs that spawn and process subscription renewals, with the calling package supplying program name, performance, and error context into DEBUG_LOG.

Because the header is dated 2005 and carries the "noship" header marker, the package is a long-standing internal component that predates the 12.1.1 and 12.2.2 releases and persists largely unchanged across them. Custom code should not call OKS_RENEW_PVT directly; supported extension points are the public OKS and OKC APIs. When debugging renewal behavior, DBAs and developers rely on DEBUG_LOG output, which requires UTL_FILE directory configuration and appropriate V$PARAMETER visibility granted to the invoking schema. The user search term "gl packets renewals" is a misnomer: this object is not part of the General Ledger schema, and its relationship to "packets" is limited to the concept of a PL/SQL package (a "packet" of procedures) rather than GL accounting packets.