Search Results evaluate_triggers

Overview

QA_MQA_MWA_API is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a public API. Its name reflects its role as the mobile warehouse assistant (MWA) interface for Oracle Quality Management (QA), and it provides the programmatic bridge between warehouse execution operations — particularly License Plate Number (LPN) handling under Warehouse Management — and the Oracle Quality collection plan engine. The package evaluates whether a given material transaction satisfies the collection triggers defined on one or more quality plans, generating the plan context information needed to launch the corresponding quality data collection. It is declared with AUTHID CURRENT_USER, so execution privileges and unqualified name resolution are evaluated against the calling schema rather than the definer, subject to the standard APPS synonym and grant model.

Key Procedures and Functions

• APP_INSTALLED — Returns a numeric flag indicating whether an application, identified by its short name, is installed in the current instance. It wraps FND_INSTALLATION.GET_APP_INFO to avoid the Boolean return type, which is incompatible with certain JDBC versions.
• TRANSACTION_COMPLETED — Signals that a transaction, identified by collection ID, has completed, with a commit flag controlling whether the associated work is committed. It is a wrapper over an enabled API, and callers are encouraged to use the original.
• EXPLODE_WMS_LPN — Decomposes an LPN into its constituent contents and quality elements. It returns the container contents, an array of quality transaction group elements, and the corresponding element identifier table.
• EVALUATE_TRIGGERS — The primary entry point for trigger evaluation. Given an LPN, a transaction number, and an organization, it determines which quality plan triggers are matched and returns three delimited strings: the plan contexts, the plan context identifiers, and the resulting plan transaction identifiers.
• TRIGGERS_MATCHED — Given a plan transaction identifier and an array of transaction group elements, returns a flag indicating whether the associated triggers are satisfied.
• IS_MOBILE_TXN — Returns FND_API.G_TRUE when the supplied transaction number falls in the mobile transaction range (1000–2000), and FND_API.G_FALSE otherwise.

Tables Accessed

The package reads setup and execution data through APPS synonyms. Quality definitions are drawn from QA_PLANS, QA_CHARS, QA_PLAN_COLLECTION_TRIGGERS, and QA_PLAN_TRANSACTIONS, which together define plans, characteristics, trigger rules, and generated plan transactions. Warehouse execution context comes from WMS_LICENSE_PLATE_NUMBERS, MTL_SYSTEM_ITEMS_KFV, and WSH_DELIVERY_DETAILS. Organizational and address data is resolved through HR_LOCATIONS_ALL_TL, HZ_LOCATIONS, and PLITBLM (the PL/SQL integer table type often used for IN-list binding).

Usage Notes

QA_MQA_MWA_API is typically invoked from mobile warehouse assistant flows and from custom code that needs to evaluate quality triggers during LPN-driven transactions. EVALUATE_TRIGGERS is normally called after a transaction is identified, with the returned identifier strings consumed by downstream collection logic; TRIGGERS_MATCHED supports finer-grained confirmation of individual plan transactions. Because the interface returns delimited strings and NOCOPY OUT parameters rather than SQL collections, it is well suited to Java/JDBC and concurrent program callers as well as PL/SQL. Consumers should account for AUTHID CURRENT_USER semantics, confirm that the Quality and Warehouse Management applications are installed via APP_INSTALLED before calling dependent routines, and prefer direct enabled APIs where a wrapper such as TRANSACTION_COMPLETED exists.