Search Results validate_ct_wt_for_deliverynum

Overview

WMS_CATCH_WEIGHT_PVT is a private (PVT) PL/SQL package body owned by APPS in Oracle E-Business Suite, associated with the Warehouse Management System (WMS) product family. Its purpose is to encapsulate the catch-weight logic used in warehouse execution and outbound shipping: determining whether an item is tracked by a secondary (catch) weight or quantity, retrieving the secondary default quantity and unit of measure, validating the secondary quantity against tolerances, and propagating secondary quantities to LPNs, deliveries, shipping records, and split lines. The package carries the standard EBS private API header (WMSVCWTB.pls, version 120.4.12010000.1) and exposes 21 documented procedures and functions. It follows EBS API conventions — a compatibility check against fnd_api.compatible_api_call, message stack handling through fnd_msg_pub, and debug tracing through inv_log_util.trace gated by the INV_DEBUG_TRACE profile option. The internal constant g_precision is set to 5, reflecting the rounding precision applied to catch-weight arithmetic. The package is referenced by five other packages, indicating it is a shared utility layer rather than an entry-point API.

Key Procedures and Functions

• GET_CATCH_WEIGHT_ATTRIBUTES — The primary attribute resolver, returning the tracking quantity indicator, the Order Management pricing quantity source, the secondary default indicator, secondary quantity and UOM, and the high/low UOM deviation values for an organization and inventory item.
• GET_ONT_PRICING_QTY_SOURCE — Determines the source from which the Order Management pricing quantity is derived for catch-weight items.
• GET_DEFAULT_SECONDARY_QUANTITY — Derives the default secondary quantity for a given item and primary quantity.
• CHECK_SECONDARY_QTY_TOLERANCE — The procedure matched by the user's search term. It validates a supplied secondary quantity against the permissible high/low deviation tolerance defined by the item's UOM attributes, returning a pass/fail outcome used by callers to accept or reject a catch-weight entry.
• UPDATE_SHIPPING_SECONDARY_QTY, UPDATE_PARENT_DELIVERY_SEC_QTY, UPDATE_LPN_SECONDARY_QUANTITY, UPDATE_LPN_PRIMARY_QUANTITY — A coordinated set of update routines that push catch-weight quantities onto shipping records, parent deliveries, and License Plate Numbers, keeping primary and secondary quantities synchronized.
• CHECK_LPN_SECONDARY_QUANTITY, CHECK_DS_LPN, CHECK_WSH_LPN — Validation helpers that test LPN state and secondary quantity consistency for delivery and shipping contexts.
• GET_OUTER_CATCH_WT_LPN, GET_INNER_CATCH_WT_LPN — Retrieve outer and inner catch-weight values associated with LPN hierarchies.
• GET_CATCH_WT_ITEMS — Identifies items flagged as catch-weight within a given context.
• SHOW_CT_WT_FOR_SPLIT, IS_CT_WT_SPLIT_VALID, VALIDATE_CT_WT_FOR_DELIVERYNUM — Govern catch-weight behavior during delivery and line splitting, determining whether a split is valid and validating catch-weight data for a delivery number.
• GET_PRIMARY_UOM_CLASS, GET_UOM_CLASS, WDD_SRC_LINE_ID — Supporting lookups for UOM classification and source line identification.

Tables Accessed

The package reads and writes the core inventory and shipping transaction tables through APPS synonyms. Item and UOM configuration comes from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_KFV, and MTL_UNITS_OF_MEASURE. On-hand and reservation context is drawn from MTL_ONHAND_QUANTITIES_DETAIL and MTL_RESERVATIONS. Location, lot, status, and subinventory data come from MTL_ITEM_LOCATIONS, MTL_LOT_NUMBERS, MTL_MATERIAL_STATUSES, and MTL_SECONDARY_INVENTORIES. Transaction records are read or staged in MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_TRANSACTION_LOTS_TEMP. Organization defaults are taken from MTL_PARAMETERS, and move-order context from MTL_TXN_REQUEST_LINES.

Usage Notes

Because this is a PVT package, it is not intended for direct customer invocation. It is called by the WMS and Shipping Execution (WSH) runtime flows — mobile receiving, packing, LPN management, and delivery/split processing — and by the five dependent packages documented in ETRM. Customizations that need catch-weight validation, particularly tolerance checking via CHECK_SECONDARY_QTY_TOLERANCE, should invoke the corresponding public API rather than this private package, since private APIs carry no compatibility guarantee across releases. Debug output for these routines is controlled by the INV_DEBUG_TRACE profile option.