Search Results wms_ui_tasks_apis




Overview
Explore in AI Chat

Overview

The APPS.WMS_UI_TASKS_APIS package body is a server-side PL/SQL construct within the Oracle Warehouse Management System (WMS) module of Oracle E-Business Suite. It forms part of the WMS UI (user interface) task layer, providing the backend programmatic logic that supports the warehouse management user interface screens used by warehouse operators, supervisors, and planners. In Oracle EBS 12.1.1 and 12.2.2, WMS relies on a set of API packages to bridge the presentation layer (typically Oracle Forms and mobile/radio-frequency device interfaces) with the underlying task execution and control logic. This package is classified under the ETRM taxonomy as an OTHER API, meaning it is not a standard public business API (such as an Open Interface or PL/SQL business API), but rather an internal support package that initializes and drives UI session behavior. Its status is VALID, confirming it is compiled and active in the APPS schema.

Key Procedures and Functions

ETRM documents exactly one procedure or function within this package body:

  • INIT_UI_STARTUP_VALUES — This procedure is responsible for initializing the startup values required when the WMS user interface is launched or a UI session begins. It prepares the default context, session parameters, and control values that the WMS interface screens depend upon before user interaction or task execution can proceed. Its naming and role indicate that it is invoked during UI initialization to populate the fields and state that drive subsequent WMS task processing. No parameter list is documented in the ETRM metadata, and none should be assumed.

Tables Accessed

The documented ETRM metadata for APPS.WMS_UI_TASKS_APIS does not list any base tables accessed directly via APPS synonyms. This suggests that the package performs its logic primarily through calls to other PL/SQL units rather than through direct DML against warehouse tables. The dependency information confirms this design: the package body references the following objects:

  • APPS.FND_API — the Oracle Application Object Library API package, providing standard API return status handling and error messaging conventions.
  • APPS.INV_CONTROL — the Inventory control package, which supplies inventory organization and control context used during initialization.
  • APPS.WMS_CONTROL — the WMS control package, providing warehouse management control parameters and operational context.
  • APPS.WMS_UI_TASKS_APIS — a self-referential dependency, indicating internal calls within the package body itself.
  • SYS.STANDARD — the standard PL/SQL package, reflecting use of built-in PL/SQL constructs.

Because no base tables are documented as directly referenced, data access is delegated to the dependent WMS_CONTROL and INV_CONTROL packages, which encapsulate the underlying queries and DML against WMS and INV tables.

Usage Notes

APPS.WMS_UI_TASKS_APIS is an internal WMS package and is not intended for direct invocation by end users or external integrations. It is typically called by the WMS user interface layer — Oracle Forms-based WMS screens or mobile/radio-frequency (RF) task screens — during UI startup to seed the values required for task execution. The ETRM metadata notes that this package is not referenced by any database object, which confirms it sits at the top of the call hierarchy for its function rather than being a low-level utility consumed by other packages. Conversely, the package itself references 6 packages (including its own body and shared dependencies such as FND_API, INV_CONTROL, WMS_CONTROL, and SYS.STANDARD).

Because it is classified as an internal API and depends heavily on FND_API error-handling conventions, any custom extension of WMS UI behavior should call it only within the context of the standard WMS UI flow and should expect it to rely on session context established by the calling form. In EBS 12.1.1 and 12.2.2, no public interface is exposed for this package, so customizations that require its logic should reference the equivalent standard UI startup sequence rather than calling the procedure directly, and should verify VALID status after any patch or upgrade applied to the APPS schema.