Search Results get_fnd_user_name

Overview

GMDQSPEC_APPROVAL_WF_PKG is the Oracle Quality Management (GMD) workflow utility package responsible for driving the specification approval cycle inside Oracle E-Business Suite. It bridges Oracle Workflow and the Approval Management Engine (AME) to determine whether a given specification change transaction requires approval, to route it to the appropriate approvers, and to apply the resulting status transition to the specification record. The package is registered under the APPS schema with the API classification OTHER, and its header indicates a last build of version 120.5 from 2006, placing it squarely in the 12.1.1 and 12.2.2 code lines where the GMD quality modules remain essentially unchanged.

A recurring design point is the local declaration of an APPLICATION_ERROR exception at the top of the package specification body. This mirrors the standard Oracle Forms/Workflow error idiom and is a frequent source of the application_error lookup term: when the workflow engine invokes a package procedure that raises this user-defined exception without a matching handler, the activity ends in error and the runtime surfaces an ORA-20001-class application error to the workflow monitor.

Key Procedures and Functions

The package exposes nine documented program units, grouped by purpose:

• IS_APPROVAL_REQ — the principal entry point. It verifies whether the raised specification business event requires approval, updates the specification status to pending using the next status defined in GMD_QC_STATUS, and populates the workflow item attributes that later activities consume.
• RAISE_SPEC_APPR_EVENT — raises the specification approval business event that starts the workflow, making the package both a consumer and a producer of the approval process.
• ANY_MORE_APPROVERS — evaluates whether additional approvers remain in the AME approval list, directing the loop that continues or completes the approval.
• REQ_APPROVED / REQ_REJECTED — apply the outcome of the approval decision to the specification, advancing or returning its status accordingly.
• NO_RESPONSE — handles the timeout case when an approver does not act within the configured period.
• REMINDAR_CHECK — performs the reminder notification check for outstanding approvals.
• APPEND_COMMENTS — consolidates approval comments and appends them to the specification history for auditability.
• GET_STATUS_MEANING — resolves a status code to its display meaning, typically via GMD_QC_STATUS, so notifications and history rows are human readable.
• GET_FND_USER_NAME (helper in the same body) — returns the FND_USER name for a supplied user ID, used to populate approver and owner attributes.

Tables Accessed

The package reads and writes a defined set of APPS synonyms. FND_USER supplies user names for requester, owner, and approver attributes. GMD_QC_STATUS and its related lookup provide the current and next status codes and their meanings. GMD_SPECIFICATIONS and GMD_SPECIFICATIONS_B hold the specification header and its base definition, where the status transition and comment history are applied. WF_PARAMETER_LIST_T and WF_RESOURCES support item attribute and workflow lookup resolution through the Workflow engine, while PLITBLM is used for the AME dynamic approval list mechanism. HR_ALL_ORGANIZATION_UNITS_TL, MTL_PARAMETERS, and MTL_SYSTEM_ITEMS_KFV are consulted to resolve organizational context and item descriptions presented on the approval notification. The package is referenced by one other package, confirming it is consumed internally by the GMD quality workflow layer rather than by external modules.

Usage Notes

GMDQSPEC_APPROVAL_WF_PKG is not normally called directly from forms or concurrent programs. It is invoked by the Oracle Workflow engine when the GMDQSPAP_ISAPROVAL_REQUIRED workflow is launched and the specification approval business event oracle.apps.gmd.qm.spec.sts is raised. Administrators reviewing a stuck approval should examine the workflow item status; the application_error search term most often indicates that one of these procedures raised the declared APPLICATION_ERROR exception. Diagnosing it requires checking the specification status values in GMD_QC_STATUS and the AME approver setup, since invalid status transitions or an empty approver list are the common triggers. Site-specific extensions should call WF_ENGINE APIs against the same item type rather than invoking these procedures outside the workflow context.