Search Results gmd_ss_batch_wf_pkg




Overview

The APPS.GMD_SS_BATCH_WF_PKG package is a workflow integration utility within the Oracle E-Business Suite Process Manufacturing (OPM) module. Its name reflects its role: "GMD" denotes the Process Manufacturing schema family, "SS" refers to Stability Studies, "BATCH" refers to batch or lot processing, and "WF" indicates Oracle Workflow. The package serves as a bridge between the Process Manufacturing stability study and quality control data model and the Oracle Workflow engine, enabling event-driven approvals and routing of stability study and batch-related business transactions.

The package is classified as API classification OTHER under the APPS schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. It exposes a small, focused public interface consisting of two documented procedures, indicating a narrowly scoped integration component rather than a broad business API. The package depends on SYS.STANDARD and is referenced by itself, reflecting an internal call structure. No other packages reference it, which suggests it is invoked directly by forms, workflow definitions, or custom extensions rather than being consumed as a reusable API by other PL/SQL code.

Key Procedures and Functions

  • VERIFY_EVENT — This procedure validates an incoming workflow event associated with a stability study or batch transaction. It confirms that the event corresponds to a legitimate business object in the Process Manufacturing data model, ensuring that workflow subscriptions and approval routing are triggered only against valid records. It typically reads supporting configuration and master data before permitting the workflow to proceed.
  • CHECK_NEXT_APPROVER — This procedure determines the next approver in a stability study or batch approval workflow. It resolves the appropriate user or role assignment based on the workflow context, leveraging user and resource configuration data stored in FND_USER and WF_RESOURCES. This procedure supports multi-step approval routing, allowing the workflow to advance correctly through an approval hierarchy.

Tables Accessed

The package references application and configuration tables to authenticate users and resolve workflow participants. FND_APPLICATION and FND_USER provide application registration and user identity data, while WF_RESOURCES supplies workflow role and resource definitions used by CHECK_NEXT_APPROVER. Master data tables include MTL_PARAMETERS and MTL_SYSTEM_ITEMS_KFV, which furnish the inventory organization defaults and item descriptions relevant to the batch context.

Stability study and quality data are drawn from GMD_STABILITY_STUDIES_B and its translation table GMD_STABILITY_STUDIES_TL, which hold the header records and descriptive text. GMD_RECIPES and GMD_QC_STATUS provide formulation and quality control status information, while GMD_SS_MATERIAL_SOURCES identifies material sourcing records tied to the study. These tables collectively allow VERIFY_EVENT and CHECK_NEXT_APPROVER to validate the transaction and resolve routing without requiring additional external lookups.

Usage Notes

This package is typically invoked from Oracle Workflow event subscriptions, custom form personalizations, or PL/SQL routines that manage stability study and batch approval cycles. It is not designed as a public business API and is not referenced by other packages, so its use should be confined to workflow-driven approval logic. Because it operates within the APPS schema and relies on standard Oracle Workflow and Process Manufacturing master data, any customization should respect existing responsibility and organization security. Administrators reviewing workflow routing issues should examine this package alongside WF_RESOURCES and FND_USER configuration to confirm that approver resolution behaves as intended.