Search Results insert_wf_processes

Overview

GMS_WORKFLOW_UTILS is a PL/SQL utility package in the Oracle EBS Grants Management (GMS) module. It provides shared helper routines that bridge GMS business entities and the Oracle Workflow engine. The package in the APPS schema is classified as an OTHER API and contains four documented subprograms. Its primary responsibility is to register workflow process instances in the GMS_WF_PROCESSES table on behalf of the various start_approval procedures, and to supply supporting attribute and notification value resolution used when constructing workflow notifications.

The header comment identifies the package as a Grants Management foundation utility (the gmsfutlb.pls source file) and fixes the API version at 1.0. The package begins by capturing session context: G_USER_ID is initialized from FND_GLOBAL.user_id and G_LOGIN_ID from FND_GLOBAL.login_id, so every downstream operation can be attributed to the correct application user and login session.

Key Procedures and Functions

• INSERT_WF_PROCESSES — The core procedure, and the object most commonly associated with the "insert_wf_processes" search term. It inserts rows into GMS_WF_PROCESSES for the start_approval procedures. Its IN parameters describe the entity invoking workflow (p_wf_type_code, such as 'BUDGET' or 'PROJECT'), the workflow name (p_item_type, e.g., 'GMSBUDWF'), the workflow process identifier (p_item_key), and the primary keys of the calling entity (p_entity_key1, with p_entity_key2 as supplemental key, typically holding a baselined budget_version_id). Optional parameters carry a description and a second entity key that defaults to GMS_BUDGET_PUB.G_PA_MISS_CHAR. Standard OUT NOCOPY error parameters return p_err_code, p_err_stage, and p_err_stack. Error code semantics follow the GMS convention: 0 indicates success, a negative value an unexpected error, and a positive value a business rule violation.
• SET_GLOBAL_ATTR — Sets a global workflow attribute value, allowing the caller to populate item-type-level context that workflow activities later read.
• SET_NOTIFICATION_MESSAGES — Resolves and sets notification message text, supporting localization or message-name substitution in workflow notifications.
• GET_APPLICATION_ID — Returns the application identifier, used to qualify workflow item types and notification attributes against the correct Oracle Application Object Library application.

Tables Accessed

• GMS_WF_PROCESSES — The primary writable table. INSERT_WF_PROCESSES writes one row per workflow process launched, recording the item type, item key, and the calling entity keys. This table acts as the correlation register between GMS business records and their workflow instances.
• FND_RESPONSIBILITY — Read to resolve responsibility-level information used in workflow attributes and notification routing, ensuring notifications reach the correct responsibility context.

Usage Notes

GMS_WORKFLOW_UTILS is an internal utility rather than an end-user-facing API. It is invoked indirectly whenever a GMS entity — a project, award, or budget — enters an approval cycle through a start_approval procedure. Those procedures call INSERT_WF_PROCESSES to stamp the workflow instance into GMS_WF_PROCESSES before the item is launched, and call SET_GLOBAL_ATTR and SET_NOTIFICATION_MESSAGES to prepare workflow data and notification content. Because the package is referenced by one other package, its principal dependency is within the GMS approval stack; custom integrations should call the public start_approval APIs rather than this utility directly. Customers extending GMS workflow should preserve the GMS_BUDGET_PUB.G_PA_MISS_CHAR sentinel convention for unspecified optional parameters and honor the documented p_err_code sign convention when handling returned errors. The package is identical in behavior across EBS 12.1.1 and 12.2.2, since its source header predates the 12.2 online-patcher file system.