Search Results wms_control




Overview
Explore in AI Chat

Overview

WMS_CONTROL is a utility package in the Oracle Warehouse Management (WMS) application module of Oracle E-Business Suite. Its primary business function is to expose release-version information for the WMS schema so that dependent code and diagnostic routines can verify that the correct patch level of the Warehouse Management product is installed. In both EBS 12.1.1 and 12.2.2, the package is owned by the APPS schema and is classified as OTHER in the ETRM repository, indicating that it is a supporting infrastructure package rather than a transactional or public business API.

The package was last modified under the header revision WMSCNTRLS.pls 120.1 (2007/12/15), and its source declares a single package-level constant, G_CURRENT_RELEASE_LEVEL, initialized to 120001. This constant encodes the release identifier for the WMS code level that shipped with the 12.0.1 generation of the product and is the anchor value consumed by the package's only documented function.

Key Procedures and Functions

The ETRM metadata documents exactly one callable program unit in this package:

  • GET_CURRENT_RELEASE_LEVEL — a function that returns the numeric release level of the currently installed WMS code. When invoked, it supplies callers with the value held in G_CURRENT_RELEASE_LEVEL (120001 at the documented revision). Because no public parameters are declared in the source, the function is called without arguments. Its purpose is to allow WMS-dependent routines to branch behavior based on the active code release, and to support version-comparison logic during upgrades and patching.

No procedures or additional overloads are documented. The package body, where one exists, is not part of the published metadata; the specification is the sole externally visible interface.

Tables Accessed

The ETRM metadata lists no tables referenced via APPS synonyms for WMS_CONTROL. This is consistent with a lightweight control package whose entire behavior is derived from an in-package constant rather than from database storage. The package therefore performs no reads or writes against WMS base tables such as WMS_* inventory or task tables, and it imposes no DML overhead when invoked. Any persistent release information elsewhere in the WMS schema is not accessed by this package as documented.

Usage Notes

WMS_CONTROL is not exposed through a standard Oracle EBS form or concurrent program. Its documented role is as a programmatic reference point: 18 other packages in the WMS module reference WMS_CONTROL, which confirms that it is invoked internally by Oracle's own PL/SQL code to assert or retrieve the active release level. Typical invocation patterns include:

  • Internal WMS package initialization, where dependent packages call GET_CURRENT_RELEASE_LEVEL to validate that the expected code level is present before executing release-sensitive logic.
  • Upgrade and patching validation routines that compare the running release constant against a target version.
  • Customer or partner extensions that need to detect the WMS code level at runtime without querying product registry tables.

Because the function is read-only and returns a scalar, it is safe to call from custom code, reports, or diagnostic scripts. Developers should note that the returned value reflects the compiled constant, so it only changes when the package is recompiled by a WMS patch; it should not be treated as a runtime-configurable setting. In 12.2.x environments, the same interface is retained, ensuring backward compatibility for the 18 dependent packages across both the 12.1.1 and 12.2.2 releases.