Search Results gmdqm_stability_batch




Overview
Explore in AI Chat

Overview

GMD_SS_BATCH_WF_PKG is a Process Manufacturing (OPM) workflow support package in the Oracle E-Business Suite Applications schema (APPS). Its business purpose is to drive the Oracle Workflow notification logic associated with the stability study batch approval process, identified internally by the transaction type constant GMDQM_STABILITY_BATCH. The package acts as the workflow background engine's callback point for the stability batch item type, verifying event conditions and resolving the next approver in an approval chain. It therefore sits at the intersection of Oracle Quality / Process Manufacturing stability study data and the Oracle Workflow / Approvals Management (AME) infrastructure.

The version header (120.4, dated 2006/12/05) indicates this is a long-standing, shipped OPM component rather than a custom or recently introduced object. It is classified in ETRM as API classification OTHER, meaning it is an internal package not intended as a public development API.

Key Procedures and Functions

  • VERIFY_EVENT — The primary documented entry point, invoked by the Workflow engine using the standard workflow callback signature (item type, item key, activity, function mode, and a result-out parameter). It reads the workflow item attributes EVENT_NAME and EVENT_KEY to identify the event being processed, resolves approver information through ame_util.approverRecord, and builds notification content for the stability batch. A significant portion of its body is a cursor (C1) that gathers stability study context — study number and description, organization and plant codes, scheduled start date, item number and description, revision, sample quantity and UOM, recipe number and version, and study owner — for inclusion in the outgoing notification. The procedure also performs the required event verification step that determines whether a notification is actually sent. This package is the object a developer reaches for when tracing the "get_from_role" style approver-resolution behaviour in stability batch notifications.
  • CHECK_NEXT_APPROVER — A helper used to determine the next approver in the stability batch approval routing. It is called during the workflow's approver-determination phase, allowing the approval hierarchy to advance one step at a time as each approver responds.

Tables Accessed

The package reads the following documented APPS-synonym tables, principally from within VERIFY_EVENT's cursor and its supporting logic:

  • GMD_STABILITY_STUDIES_B and GMD_STABILITY_STUDIES_TL — the base and translated stability study definitions, supplying study number and study description.
  • GMD_SS_MATERIAL_SOURCES — the stability study material sources, providing sample quantity, sample quantity UOM, and owner information.
  • GMD_RECIPES — recipe number and recipe version for the studied item.
  • GMD_QC_STATUS — quality status meaning values used in the notification content.
  • MTL_SYSTEM_ITEMS_KFV — the concatenated item key flexfield view, for item number and item description.
  • MTL_PARAMETERS — organization and plant code derivation.
  • FND_USER — resolution of the workflow user or approver identity.
  • FND_APPLICATION — application context lookups.
  • WF_RESOURCES — Oracle Workflow message and resource lookups for building notification text.

Usage Notes

GMD_SS_BATCH_WF_PKG is not called directly from forms, concurrent programs, or general custom code. It is invoked by the Oracle Workflow engine as the function activity implementation for the stability batch item type, and by the notification mailer or Workflow background engine during approval routing. Developers tracing stability batch notifications or the "get_from_role" approver lookup should inspect VERIFY_EVENT's cursor and its calls into AME (ame_util.approverRecord) and WF_ENGINE.GETITEMATTRTEXT, since the role and approver derivation is driven from those workflow item attributes rather than from a parameter supplied by the caller. No other packages in ETRM are documented as referencing this one, confirming its role as a terminal implementation object in the workflow call stack.