Search Results get_default_secondary_quantity

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WMS_CATCH_WEIGHT_GRP is a public PL/SQL package in the APPS schema that supports catch weight and dual unit of measure (UOM) processing for Oracle Warehouse Management. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling user rather than the package owner, which is significant because it reads from the MTL_SYSTEM_ITEMS and MTL_PARAMETERS tables that are commonly exposed through APPS synonyms and secured by inventory operating unit.

The package header defines two public constants, G_PRICE_PRIMARY and G_PRICE_SECONDARY, which mirror the similarly named constants in WMS_CATCH_WEIGHT_PVT. These constants represent the allowable values of the ONT_PRICING_QTY_SOURCE column on MTL_SYSTEM_ITEMS and indicate whether an item is priced on its primary or its secondary UOM. As its name suggests, this package is a "group" layer: it is designed to be called directly by external consumers, principally Order Management and other pricing-related flows, and it wraps the lower-level private catch weight logic.

Key Procedures and Functions

• GET_DEFAULT_SECONDARY_QUANTITY — The single documented entry point in this package. For a given item and organization, together with a quantity and UOM supplied by the caller, this function returns the ONT_PRICING_QTY_SOURCE value from MTL_SYSTEM_ITEMS and, where the item is set up to be priced on its secondary UOM, also returns the applicable secondary_uom_code and the calculated secondary quantity. The documented inputs are the organization identifier, the inventory item identifier, the source quantity, and optional UOM and secondary UOM codes; when a UOM is not supplied the API defaults to the primary UOM, and when a secondary UOM is not supplied it defaults to the secondary_uom_code defined on the item. The single OUTPUT value is the secondary quantity and the function's return value is the ONT_PRICING_QTY_SOURCE, taking one of the two package constants.

An important behavioral distinction documented in the source is that this group-level API calculates the secondary quantity for secondary-priced items regardless of whether the secondary quantity has been designated as defaultable. The corresponding private API respects the defaultable flag; the public API intentionally does not. Consumers must therefore be aware that a non-null result does not imply that the item profile permits automatic defaulting.

Tables Accessed

• MTL_SYSTEM_ITEMS — The primary source of item attributes. The package reads ONT_PRICING_QTY_SOURCE to determine whether the item is priced on primary or secondary UOM, and reads the item's secondary_uom_code when the caller does not supply one. It also supplies the item-organization context that qualifies the unique item key.
• MTL_PARAMETERS — Read to establish organization-level inventory and warehouse management setup, which governs whether catch weight and dual UOM processing are enabled for the organization in which the item resides.

Usage Notes

WMS_CATCH_WEIGHT_GRP is intended for external invocation by forms, concurrent programs, and custom code that must convert a transaction quantity into its secondary (catch weight) equivalent, most notably pricing and order capture flows that must present the correct quantity source and secondary quantity to the user. Because the package is a documented group API and is referenced by one other package, it should be treated as a supported integration point rather than replaced by direct reads of MTL_SYSTEM_ITEMS.

Callers should note that the header carries an old $Header tag (115.4, dated 2004) and that the package is marked noship, indicating it has shipped under that version lineage for many releases and is stable across both 12.1.1 and 12.2.2. Implementations should pass complete key values — organization and inventory item — on every call, and should validate the returned ONT_PRICING_QTY_SOURCE against the package constants rather than hard-coding literal values such as 'P' or 'S'.