Search Results gms_workflow_itemkey_s

Overview

GMS_CLIENT_EXTN_BUDGET_WF is an APPS-owned PL/SQL package body in the Oracle Grants Management (GMS) module. It drives the client extension workflow for grant budget approvals, providing the server-side logic that starts an Oracle Workflow process, resolves approvers, and validates approval rules for a budget version. In Oracle EBS 12.1.1 and 12.2.2 the package is classified as OTHER, meaning it is an internal supporting API rather than a public, multi-call interface. Its procedures are called from the Grants budget client extension (often through the Forms-based budget entry and approval flows) to interact with WF_ENGINE and the Grants workflow structures. The object status is VALID, and the ETRM metadata records seven documented procedures or functions.

Key Procedures and Functions

• IS_BUDGET_WF_USED – Determines whether workflow is enabled/used for the budget process, allowing callers to branch between workflow-driven and non-workflow approval paths.
• START_BUDGET_WF – Initiates the budget workflow for a given budget version, creating the workflow item and routing it to approvers.
• START_BUDGET_WF_NTFY_ONLY – Starts the budget workflow in notification-only mode, issuing approval notifications without requiring a full approval routing cycle.
• SELECT_BUDGET_APPROVER – Resolves and returns the appropriate budget approver, using Grants personnel, HR organization units, and security profile data.
• VERIFY_BUDGET_RULES – Validates that the configured approval rules and conditions are satisfied before a budget workflow is launched.
• CALL_GMS_DEBUG – Wrapper that emits debug/diagnostic information for troubleshooting workflow behaviour.
• CALL_WF_ADDUSERS_TO_ADHOCROLE – Adds users to the ad hoc workflow role so that dynamically determined approvers can act on the budget approval notification.

Because the metadata does not expose parameter lists, callers should reference the package specification for exact signatures.

Tables Accessed

The package references the following tables via APPS synonyms: GMS_AWARDS and GMS_BUDGET_VERSIONS for award and budget version context; GMS_PERSONNEL for approver and personnel data; GMS_WORKFLOW_ITEMKEY_S, which stores workflow item keys and is the object associated with the user's search term; PA_PROJECTS, PA_PROJECT_TYPES, PA_BUDGET_TYPES and PA_RESOURCE_LISTS for Projects-based budget classification and resource information; PER_ALL_PEOPLE_F and PER_PEOPLE_F for person records; HR_ORGANIZATION_UNITS for organization context; FND_USER to map application users to workflow participants; and DUAL for PL/SQL expression evaluation. It also depends on GMS_SECURITY, GMS_WF_PKG, GMS_ERROR_PKG and GMS_NOTIFICATIONS_V, and on FND_API, FND_GLOBAL, FND_MSG_PUB, FND_PROFILE apps APIs together with WF_CORE, WF_DIRECTORY and WF_ENGINE for workflow scheduling and role resolution.

Usage Notes

Typical invocation occurs from the Grants budget approval flow: the UI or a concurrent process first calls IS_BUDGET_WF_USED and VERIFY_BUDGET_RULES, resolves the approver via SELECT_BUDGET_APPROVER, registers participants with CALL_WF_ADDUSERS_TO_ADHOCROLE, and then launches the process using START_BUDGET_WF or START_BUDGET_WF_NTFY_ONLY. The generated item is recorded in GMS_WORKFLOW_ITEMKEY_S, which links the budget version to its workflow item. The package is referenced by one other database object and is not itself referenced by any object, confirming it is a top-level driver rather than a shared utility. Because APIs such as FND_API and WF_ENGINE are used, FND_GLOBAL session context (user, responsibility, application) should be initialised before calling these procedures in custom code. Oracle EBS 12.1.1 and 12.2.2 are functionally equivalent here; the primary 12.2.x consideration is that the online Forms interface is preserved, so the same package body continues to be called from the Grants budget client extension.