Search Results wsh_code_control




Overview
Explore in AI Chat

Overview

The APPS.WSH_CODE_CONTROL package body is a lightweight utility object within the Oracle E-Business Suite Warehouse Management (WSH) module. Its principal business function is to expose the value of the package-level constant CODE_RELEASE_LEVEL to other WSH components, thereby providing a single authoritative source for the code release level at which the WSH schema objects were installed. The package source carries the header identifier WSHCRCNB.pls 120.0, dated 2005/05/26, reflecting its long-standing role as a stable, low-change component of the WSH infrastructure.

The package is classified by the ETRM as an OTHER API rather than a public or private business API, which is consistent with its narrow technical purpose. It performs no business transactions, does not modify data, and does not participate in the shipping or picking workflows directly. Instead, it acts as a metadata accessor that other routines consult when they need to determine compatibility, versioning, or feature-availability information related to the installed WSH code base.

Key Procedures and Functions

The package body documents a single callable function:

  • Get_Code_Release_Level — Returns a VARCHAR2 value representing the current code release level of the WSH module. Internally, the function simply returns the package-level constant WSH_CODE_CONTROL.CODE_RELEASE_LEVEL. The hard-coded debug instrumentation that once wrapped this function (using WSH_DEBUG_INTERFACE.g_debug and WSH_DEBUG_SV.is_debug_enabled, push, and pop) has been commented out per Bug#3772380, so the function executes with minimal overhead and no debug dependency.

No other procedures or functions are documented in this body. The specification exposes the function through the package interface, while the body supplies the implementation shown above.

Tables Accessed

The ETRM metadata lists no tables referenced via APPS synonyms for this package. That is expected: the sole function returns a constant defined within the package itself rather than querying any database object. There are therefore no reads, writes, or locks against WSH or other application tables associated with this package. Any schema-level dependency is limited to the package specification constant, which is resolved at compile time and stored in the compiled body.

Usage Notes

WSH_CODE_CONTROL.Get_Code_Release_Level is referenced by approximately ten other WSH packages, according to ETRM dependency data. These callers typically invoke the function during initialization or setup logic to obtain the release level for conditional behavior, logging, or diagnostic output. Typical invocation contexts include:

  • Server-side PL/SQL routines within the WSH schema that need a deterministic, cached code-release identifier.
  • Internal diagnostics or version-reporting utilities that present the WSH code level to administrators.
  • Custom extensions or integrations that have elected to reuse the standard accessor rather than hard-coding a release string.

Because the function has no parameters and reads only a package constant, it is safe to call from forms, concurrent programs, and custom PL/SQL without side effects. It should be treated as a read-only accessor; custom code should not attempt to alter the underlying constant, which is defined at the package specification level and is not designed to be mutable at runtime.