Search Results wms_deploy




Overview
Explore in AI Chat

Overview

The APPS.WMS_DEPLOY package body is a deploy-side utility package within Oracle Warehouse Management (WMS), a module that in Oracle E-Business Suite 12.1.1 and 12.2.2 is integrated with Oracle Inventory and Oracle Shipping. Despite the "WMS" prefix, the object's documented dependencies and procedure list indicate that its functional scope is client and deployment metadata resolution in a third-party logistics (3PL) or supplier-managed inventory context: it maps items, customers, purchase orders, and deployment modes to client-facing identifiers. The package is classified as OTHER rather than as a formal FND_API-based public interface, and it carries a status of VALID. The ETRM dependency listing confirms that WMS_DEPLOY references FND_API, FND_MSG_PUB, and FND_PROFILE for error handling and profile option lookups, indicating that its routines raise and translate standard EBS messages rather than returning bare return codes.

Key Procedures and Functions

Nineteen documented procedures and functions are exposed. The deployment-mode and configuration routines are WMS_DEPLOYMENT_MODE, which reports the operational deployment scenario; GET_ITEM_FLEX_DELIMITER, which returns the delimiter used in the item key flexfield; and GET_ITEM_FLEX_SEGMENT_COUNT, which returns the number of concatenated segments in that flexfield. Costing helpers include COSTED_TXN and COSTED_TXN_FOR_ITEM, which evaluate transaction-level and item-level costing applicability.

Client resolution routines form the largest group: GET_CLIENT_INFO, GET_CLIENT_INFO_FOR_ITEM, GET_CLIENT_CODE, GET_CLIENT_DETAILS, GET_CLIENT_ITEM_NAME, GET_CLIENT_ITEM, GET_ITEM_CLIENT_NAME, and GET_CATEGORY_INFO. Purchase-order-oriented routines include GET_CLIENT_PONUM_INFO, GET_CLIENT_PO_NUM, GET_PO_CLIENT_CODE, GET_PO_CLIENT_NAME, and GET_PO_NUMBER. The LOV helper GET_ITEM_SUFFIX_FOR_LOV supplies list-of-values support for item suffixes. No parameter lists are documented, and none should be assumed.

Tables Accessed

The package reads from several registered EBS base tables through APPS synonyms. HZ_PARTIES and HZ_CUST_ACCOUNTS supply customer party and account data used to derive client codes and names. MTL_CLIENT_PARAMETERS holds the 3PL client definition and is central to the client-information routines. MTL_SYSTEM_ITEMS and the key flexfield view MTL_SYSTEM_ITEMS_B_KFV provide item and concatenated item-segment data, while PO_HEADERS_ALL provides purchase order header information for the PO client mapping functions. Flexfield structure and segment metadata are obtained from FND_ID_FLEX_SEGMENTS_VL and FND_ID_FLEX_STRUCTURES_VL, which support the delimiter and segment-count routines.

Usage Notes

WMS_DEPLOY is not a standalone interface; it functions as a shared utility layer. The ETRM metadata records that it is referenced by 61 other database objects, and that it is itself not referenced by any database object, placing it high in the dependency chain. It is therefore typically invoked indirectly from WMS and Inventory forms, concurrent programs, and other PL/SQL packages that require consistent translation between internal item, customer, and PO identifiers and their client-facing equivalents. Because the package relies on FND_PROFILE and FND_MSG_PUB, callers should expect standard EBS profile option governance and message-stack behavior. Recent patches to any of the referenced tables should be evaluated against this package before deployment.