Search Results is_step

Overview

GMD_QMSMC is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, belonging to the Oracle Process Manufacturing (OPM) Quality Management module. The suffix "QMSMC" identifies it as a Quality Management System workflow-callback package. Its principal business function is to support the Oracle Workflow–driven approval and event-handling logic used by OPM Quality specifications, sampling plans, and batch-related transactions. Whenever a workflow process associated with a quality specification, sampling event, or production batch requires validation of its current state, determination of the next approver, or verification of the triggering business event, the Workflow engine invokes the procedures in this package. In effect, GMD_QMSMC acts as the bridge between the generic Workflow runtime and the OPM Quality domain data model, allowing standard workflow constructs (item types, item keys, activity identifiers, and function modes) to be interpreted against quality-management business rules.

Key Procedures and Functions

The package header declares a small, focused set of public procedures. Each conforms to the Oracle Workflow standard callback signature, accepting an item type, item key, activity identifier, function mode, and an OUT result parameter.

• VERIFY_EVENT — Determines which business event has been raised for the workflow item and returns the outcome through the result parameter, allowing Workflow to branch based on the specific quality event encountered.
• CHECK_NEXT_APPROVER — Evaluates the approval hierarchy to determine whether a next approver exists, supporting multi-level routing of specification, sampling, or batch approvals.
• PRODUCTION — Handles workflow logic relevant to production-related quality transactions, providing the branch decision when a step is executed in a manufacturing or batch context.
• IS_STEP — Added under Bug 5032406 (forward port of 4604305), this procedure checks whether the raised event pertains to a batch step level transaction, allowing step-level and header-level processing to be distinguished.
• GET_DOC_NO — Documented in the source header as retrieving a document number from a document ID and type, but the implementation is commented out and is explicitly marked as unused (Bug 4165704), with the annotation that it was originally introduced under Bug 3361101. It is therefore not part of the active interface.

Tables Accessed

Through APPS synonyms, the package reads OPM Quality, production, and application-setup tables. Quality configuration and specification data are drawn from GMD_QUALITY_CONFIG, GMD_SPECIFICATIONS_B, GMD_INVENTORY_SPEC_VRS, GMD_SUPPLIER_SPEC_VRS, GMD_WIP_SPEC_VRS, and GMD_EVENT_SPEC_DISP, which collectively drive event verification and approver determination. Sampling logic references GMD_SAMPLING_PLANS_B, GMD_SAMPLING_EVENTS, and GMD_SAMPLES. Manufacturing and recipe context comes from GME_BATCH_HEADER, GMD_RECIPES_B, GMD_RECIPE_VALIDITY_RULES, and FM_FORM_MST_B. Workflow and security context is supplied by FND_APPLICATION and FND_USER. These accesses are predominantly read-only lookups performed at workflow decision points.

Usage Notes

GMD_QMSMC is invoked indirectly by the Oracle Workflow engine rather than called directly by end users or concurrent programs. It is registered as the callback package on workflow activities attached to the OPM Quality Management item types that govern specification approval, sampling plan events, and batch step processing. Because it is a Workflow-internal utility, customizations should be limited to extensions of the registered workflow processes; the package itself is not designed as a public API and is not referenced by any other documented package. Note that mobile scanning of workflow item keys or QR-encoded document references does not route through this package — it only resolves the workflow activity outcome once invoked.