Search Results explode_wms_lpn

Overview

QA_MQA_MWA_API is the Mobile Warehouse Application (MWA) integration API for Oracle Quality. It provides the server-side PL/SQL entry points that allow warehouse and shop-floor mobile transactions to interact with Oracle Quality collection plans, quality checks, and trigger evaluation logic. The package is most closely associated with the "Quality Check" flow used in WMS-directed and WIP-driven mobile transactions, where a user scanning license plates, containers, or items must be presented with the correct quality collection plan for the context in which the scan occurs.

The package header comment identifies the context elements used for the QA WMS Quality Check: content item (10), item category (11), customer (32), ship-to location (146), and container item (173). The license plate number element (150) is explicitly commented out, indicating that license plate context is handled separately through the LPN explosion path rather than as a standard collection element. This is directly relevant to callers searching for explode_wms_lpn, which is the documented procedure responsible for resolving a WMS license plate into its constituent contents so that quality context can be derived.

Key Procedures and Functions

• APP_INSTALLED — A wrapper around fnd_installation.get_app_info that returns 1 when a named application is installed and 0 otherwise. It exists because the underlying FND function returns a Boolean, which is not compatible with the JDBC versions used by the mobile client. The implementation treats status 'I' and 'S' as installed, a deliberate accommodation documented in the source comments to prevent the Quality button from disappearing during WIP move.
• TRANSACTION_COMPLETED — Signals the completion of a mobile transaction against a Quality collection. It accepts a collection identifier and a commit flag, normalises the commit flag to the FND API Boolean constants, and delegates to qa_result_grp.enable to enable the collection results group. This is the point at which collected quality results become available for processing.
• EXPLODE_WMS_LPN — Resolves a WMS license plate identifier within a given inventory organisation into its constituent contents, supplying the item, container, and quantity context required to select and populate a quality collection plan. This procedure is the documented entry point for LPN-based quality checks in mobile receiving, put-away, and picking flows.
• EVALUATE_TRIGGERS — Evaluates the collection plan triggers configured for the transaction context to determine which collection plans apply.
• TRIGGERS_MATCHED — Reports whether one or more triggers matched during trigger evaluation, allowing the caller to decide whether to launch a quality collection.
• IS_MOBILE_TXN — Identifies whether the current transaction originates from a mobile device, used to gate mobile-specific behaviour such as button visibility and collection invocation.

Tables Accessed

The package reads and writes through APPS synonyms including QA_PLANS, QA_PLAN_TRANSACTIONS, QA_PLAN_COLLECTION_TRIGGERS, and QA_CHARS, which supply plan definitions, character specifications, and the trigger rules evaluated by EVALUATE_TRIGGERS. WMS_LICENSE_PLATE_NUMBERS is the primary source for EXPLODE_WMS_LPN, with WSH_DELIVERY_DETAILS used to resolve delivery and shipping context. MTL_SYSTEM_ITEMS_KFV provides concatenated item descriptions for the context elements, while HZ_LOCATIONS and HR_LOCATIONS_ALL_TL supply customer and ship-to location descriptions. PLITBLM is used for PL/SQL index-by table handling within the API.

Usage Notes

QA_MQA_MWA_API is invoked from the MWA mobile client stack rather than from a standard Oracle Forms window. It is referenced by one other package, which typically acts as the mobile transaction dispatcher. The package is delivered under the APPS schema in both 12.1.1 and 12.2.2. Customisations should call EXPLODE_WMS_LPN before EVALUATE_TRIGGERS when the transaction context includes a license plate, and should respect the APP_INSTALLED guard so that Quality integration is skipped gracefully on installations where Oracle Quality is not licensed.