Search Results costed_txn_for_item

Overview

APPS.WMS_DEPLOY is a public PL/SQL package in Oracle E-Business Suite that exposes the deployment mode of Oracle Warehouse Management (WMS) and provides supporting utilities for Standalone and Logistics Service Provider (LSP) installations. The package is declared with AUTHID CURRENT_USER and carries the ETRM display name "WMS Deploy" under the BUSINESS_ENTITY category WMS_DEPLOY. Its principal service is the function WMS_DEPLOYMENT_MODE, which returns a single-character indicator derived from the profile option WMS_DEPLOYMENT_MODE: I for Integrated Deployment, D for Distributed (Standalone) Deployment, and L for LSP Deployment. Because WMS behavior differs substantially across these three models, downstream code frequently needs to branch on deployment mode, and this package centralizes that determination.

The package also supplies item flexfield metadata and a family of client/LSP resolution utilities. To limit database round trips, the deployment mode and related values are cached in package global variables (for example g_wms_deployment_mode) and reused within the same session.

Key Procedures and Functions

The documented API comprises 19 procedures and functions classified as OTHER:

• WMS_DEPLOYMENT_MODE — returns the deployment mode (I, D, or L) based on the WMS_DEPLOYMENT_MODE profile option.
• GET_ITEM_FLEX_DELIMITER — returns the item flexfield delimiter character.
• GET_ITEM_FLEX_SEGMENT_COUNT — returns the number of item flexfield segments.
• COSTED_TXN and COSTED_TXN_FOR_ITEM — indicate whether a transaction, or a transaction for a specific item, is costed (Y/N).
• GET_CLIENT_INFO and GET_CLIENT_INFO_FOR_ITEM — return client (LSP) information generally and in the context of a specific item.
• GET_CATEGORY_INFO — returns category information; this is the function associated with the user's search term.
• GET_CLIENT_CODE and GET_CLIENT_DETAILS — return a client code and fuller client detail respectively.
• GET_CLIENT_ITEM_NAME and GET_CLIENT_ITEM — relate client identity to item naming.
• GET_CLIENT_PONUM_INFO, GET_CLIENT_PO_NUM, GET_PO_CLIENT_CODE, GET_PO_CLIENT_NAME, and GET_PO_NUMBER — resolve purchase order number and client identity in either direction for LSP transactions.
• GET_ITEM_CLIENT_NAME and GET_ITEM_SUFFIX_FOR_LOV — support item/client name display and list-of-values suffixing.

Record types t_in_txn_rec (inventory_item_id, organization_id) and t_client_rec (client_id, client_name) support these interfaces.

Tables Accessed

The package references the following tables through APPS synonyms:

• HZ_PARTIES — source of party/client names, including the party_name column used by t_client_rec.
• HZ_CUST_ACCOUNTS — customer account data used to resolve client codes and details.
• MTL_CLIENT_PARAMETERS — stores LSP client parameters that drive client-specific behavior.
• MTL_SYSTEM_ITEMS — item master data used for item-level client, category, and costing lookups.
• PO_HEADERS_ALL — purchase order headers used by the PO-number resolution functions.

Usage Notes

WMS_DEPLOY is a runtime utility rather than a transactional API. It is most commonly invoked from WMS-related forms, concurrent programs, and custom PL/SQL that must adapt behavior to the active deployment mode or resolve client and PO context for LSP operations. The cached global variables mean callers benefit from repeated invocation within a session; changes to the underlying profile option require a new session to be observed. Given that the package is referenced by 61 other packages, it should be regarded as a shared dependency, and modifications should be avoided in favor of standard extension mechanisms.