Search Results g_k_release_level

Overview

INV_RELEASE is a small, dependency-free PL/SQL package in the Oracle E-Business Suite INV (Inventory) module whose sole purpose is to publish release-level constants and accessor functions. Rather than querying an application table to determine which inventory code features are present, callers invoke INV_RELEASE to obtain a numeric release marker and then branch their logic accordingly. This pattern lets Oracle ship a single set of dependent packages while still allowing legacy and newer code paths to coexist across patch levels. The package is declared with AUTHID CURRENT_USER and, as the header comment ("$Header: INVRELSES.pls 120.0.12020000.6 2013/04/09") indicates, is delivered as a stub-style specification containing nothing but constants and accessor signatures — no business tables, no DML, and no dependencies on other application packages.

Key Procedures and Functions

The specification documents four functions, each of which returns a NUMBER release level and corresponds to a named constant declared in the package body:

• GET_I_RELEASE_LEVEL — returns the constant G_I_Release_Level (110509), identifying Release I feature-set availability.
• GET_J_RELEASE_LEVEL — returns the constant G_J_Release_Level (110510), identifying Release J feature-set availability.
• GET_K_RELEASE_LEVEL — returns the constant G_K_Release_Level (110511), identifying Release K feature-set availability.
• GET_OPTLOTSUPPORT_LEVEL — returns the constant G_OptLotSupport_Release (1222), which flags support for Optional Lot Allocation.

All four are simple, parameterless accessors. Their purpose is to allow calling code to test for the presence of a feature without hard-coding version literals, and to allow Oracle to advance a returned level in a future patch without breaking the call signature.

Tables Accessed

No tables are referenced, directly or through APPS synonyms. The ETRM metadata for this object lists an empty table reference set, consistent with the specification excerpt, which contains only CONSTANT declarations and function signatures. Every value returned by the package is a compile-time literal embedded in the package body. Consequently, INV_RELEASE performs no SQL, holds no cursors, and cannot be blocked by row locks or invalidated by data changes; its only invalidation vector is recompilation of the package itself.

Usage Notes

INV_RELEASE is a utility dependency rather than a business API. It is typically invoked from other PL/SQL packages at the top of a routine — for example, to decide whether to route a transaction through the Optional Lot Allocation logic keyed to the 1222 level, or to enable behavior associated with Release I, J, or K. ETRM records that the package is referenced by 25 other packages, which is consistent with its role as a shared feature flag; those dependents span the Inventory transaction-processing stack. It classifies as API classification OTHER, meaning it is not an application business API and not intended for external integration. Concurrent programs and Oracle Forms do not generally call the accessors directly; forms-based feature gating is handled by the forms layer and profile options. Customer extensions should not treat INV_RELEASE as a supported extension point, and custom code should avoid hard-coding the literal values 110509, 110510, 110511, or 1222, calling the accessor functions instead so that behavior tracks Oracle's shipped release levels across 12.1.1 and 12.2.2 environments.