Search Results raise_spec_appr_event

Overview

GMDQSPEC_APPROVAL_WF_PKG is an Oracle EBS Application Object Library (APPS) package that implements the Oracle Workflow integration logic for the specification approval process in Oracle Process Manufacturing (OPM) Quality Management. In Oracle EBS 12.1.1 and 12.2.2, the package bridges the specification approval business flow and the Workflow Notification System, allowing specification records defined in Oracle Quality / OPM Quality to be routed through an approval hierarchy and acted upon by approvers through standard Workflow notifications.

The package is classified as an OTHER API within ETRM documentation, indicating that it is maintained for internal use by the specification approval workflow rather than as a general-purpose public extension API. It is a validated database object owned by APPS and is dependent upon SYS.STANDARD, confirming it executes as a normal PL/SQL package within the database. Its primary consumers are the Workflow activity functions attached to the specification approval workflow definition and the sibling package GMDQSVRS_APPROVAL_WF_PKG, which references it.

Key Procedures and Functions

The documented interface exposes nine procedures and functions, each supporting a distinct step or decision within the specification approval workflow:

• IS_APPROVAL_REQ — determines whether an approval is required for the specification, allowing the workflow to branch based on the approval setup or the specification's characteristics.
• APPEND_COMMENTS — appends approval-related comments to the notification or to the underlying specification record so that approver feedback is retained.
• ANY_MORE_APPROVERS — evaluates whether additional approvers remain in the approval hierarchy, controlling looping and continuation of the approval process.
• NO_RESPONSE — handles the outcome where an approver does not respond to the notification within the allotted time.
• REQ_REJECTED — processes the rejection path, updating status and initiating any rejection-side workflow activity.
• REQ_APPROVED — processes the approval path, marking the request as approved and advancing the workflow.
• REMINDAR_CHECK — (as named in ETRM metadata) implements reminder checking, determining whether a reminder notification should be sent to a pending approver.
• GET_STATUS_MEANING — returns the display meaning of the current approval status, typically used to render status information in notifications.
• RAISE_SPEC_APPR_EVENT — raises the specification approval workflow event to launch or advance the approval process through the Workflow Business Event System.

Tables Accessed

The package operates against the following documented tables, most accessed through APPS synonyms:

• GMD_SPECIFICATIONS and GMD_SPECIFICATIONS_B — the core specification definition and base tables holding the records under approval.
• GMD_QC_STATUS — supplies the quality status values assigned to specifications as they move through approval.
• FND_USER — identifies approvers, requestors, and notification recipients.
• HR_ALL_ORGANIZATION_UNITS_TL — resolves organization unit names for approval context and hierarchy lookups.
• MTL_PARAMETERS and MTL_SYSTEM_ITEMS_KFV — provide inventory organization and item (concatenated description) information associated with specifications.
• WF_PARAMETER_LIST_T and WF_RESOURCES — supply Workflow parameter lists and resource (message/role) definitions used when constructing notifications and events.
• PLITBLM — the PL/SQL Index-by Table of Long Messages utility, used for building message text such as notification bodies.

Usage Notes

GMDQSPEC_APPROVAL_WF_PKG is invoked indirectly by the Oracle Workflow engine. The activity functions are configured as the runnable/non-runnable activities of the specification approval workflow definition, so the package is executed when the workflow advances through approval, rejection, reminder, and "no response" branches. It is not intended to be called from the OPM Quality forms directly; the forms simply initiate the process, and the workflow item type drives the subsequent calls to this package.

Customizations should avoid modifying the package body. Extension is better achieved by substituting customized workflow activity functions or by wrapping the public functions within a separate custom package. Because the package touches GMD_SPECIFICATIONS and GMD_QC_STATUS, any custom code that alters specification status outside the workflow can cause inconsistencies with the workflow's own state tracking. Customers on both 12.1.1 and 12.2.2 should treat the package as internal infrastructure and validate it after applying Quality or Workflow patches.