Search Results costed_txn




Overview
Explore in AI Chat

Overview

WMS_DEPLOY is a public PL/SQL package in the APPS schema that governs Oracle Warehouse Management deployment behavior within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to expose the operative WMS deployment mode—Integrated ('I'), Distributed or Standalone ('D'), or Logistics Service Provider ('L')—as determined by the WMS_DEPLOYMENT_MODE profile option, and to supply the supporting utilities that downstream WMS logic requires once that mode is known. The package additionally provides a family of client-facing helper routines used to resolve client, party, and purchase order information for LSP-style processing, together with item flexfield metadata and costing eligibility checks.

The package is declared AUTHID CURRENT_USER and is classified under the BUSINESS_ENTITY category WMS_DEPLOY. It caches key values in session-level global variables (notably g_wms_deployment_mode) to avoid repeated database queries within a single session, an important design characteristic given the frequency with which deployment mode and item flexfield attributes are evaluated by shipping, receiving, and costing logic. The ETRM metadata records that the package is referenced by 61 other packages, confirming its role as a foundational utility rather than an end-user-facing module.

Key Procedures and Functions

  • WMS_DEPLOYMENT_MODE — Returns the active deployment mode by reading the WMS_DEPLOYMENT_MODE profile option: 'I' for Integrated, 'D' for Distributed (Standalone), or 'L' for LSP. This is the package's central function and is cached in the g_wms_deployment_mode global.
  • GET_ITEM_FLEX_DELIMITER — Returns the delimiter character used by the Item flexfield, allowing callers to parse or construct concatenated item key flexfield values.
  • GET_ITEM_FLEX_SEGMENT_COUNT — Returns the number of segments defined for the Item key flexfield, supporting dynamic assembly of item identifiers.
  • COSTED_TXN — Returns whether a transaction can be costed (Y/N). This is the routine most directly associated with the user's search term "costed_txn" and is the transaction-level eligibility gate for costing.
  • COSTED_TXN_FOR_ITEM — Companion check that determines costing eligibility for a specific item, defined by the t_in_txn_rec record type (inventory_item_id, organization_id).
  • GET_CLIENT_INFO and GET_CLIENT_INFO_FOR_ITEM — Retrieve client information generally and for a specific item, based on the t_client_rec record type (client_id, client_name).
  • GET_CLIENT_CODE, GET_CLIENT_DETAILS, GET_CLIENT_ITEM, GET_CLIENT_ITEM_NAME, GET_ITEM_CLIENT_NAME, GET_ITEM_SUFFIX_FOR_LOV — A set of resolution utilities returning client codes, full client details, client-item mappings, client item names, item client names, and LOV-oriented item suffixes.
  • GET_CATEGORY_INFO — Returns category information associated with the client/item context.
  • GET_CLIENT_PONUM_INFO, GET_CLIENT_PO_NUM, GET_PO_CLIENT_CODE, GET_PO_CLIENT_NAME, GET_PO_NUMBER — Routines that resolve purchase order numbers and the associated client code or client name, bridging WMS client processing to purchasing data.

Tables Accessed

  • HZ_PARTIES — Provides party_name for the client record type, substantiating GET_CLIENT_INFO and related client-name resolution routines.
  • HZ_CUST_ACCOUNTS — Supplies customer account context used to link parties to client or PO-related lookups.
  • MTL_CLIENT_PARAMETERS — The core WMS client configuration table, used to resolve client codes, client details, and client-item associations.
  • MTL_SYSTEM_ITEMS — Source of item attributes, including flexfield segment values, for the item-level client and costing routines.
  • PO_HEADERS_ALL — Supplies purchase order header data for GET_PO_NUMBER, GET_PO_CLIENT_CODE, and GET_PO_CLIENT_NAME.

Usage Notes

WMS_DEPLOY is invoked indirectly rather than through a dedicated form or concurrent program. WMS shipping, receiving, and costing code calls WMS_DEPLOYMENT_MODE to branch between integrated and standalone execution paths, and the 61 dependent packages documented in ETRM rely on this and the client-resolution routines. The COSTED_TXN and COSTED_TXN_FOR_ITEM functions are typically referenced from Cost Management and Inventory transaction processing to decide whether a given material transaction is eligible for cost propagation, which explains the association with the "costed_txn" search term. Because deployment mode and flexfield attributes are cached in package globals, session reuse should be considered: a session that changes profile values mid-life will not observe the change through these functions until the session is reinitialized. In custom code, the package is best treated as a read-only facility for deployment-mode detection and client/item resolution, and callers should rely on the documented function names rather than assuming parameter signatures, which the metadata does not expose.