Search Results start_budget_wf

Overview

GMS_CLIENT_EXTN_BUDGET_WF is an Oracle Grants Management (GMS) PL/SQL package that provides the integration layer between Grants budget maintenance and the Oracle Workflow engine. It is the entry point through which a grant budget version is submitted for approval, routed to the appropriate approver, and validated against the organization's budget business rules before it is committed as the active or original budget. The package is declared AUTHID CURRENT_USER and resides in the APPS schema, meaning it executes with the privileges of the calling user and relies on APPS synonyms for all object references.

In the ETRM 12.2.2 data model, the package is classified as API type OTHER and exposes seven documented program units. Its central role is the initiation and orchestration of the budget approval workflow: callers supply a draft budget version together with its project, award, and budget type context, and the package resolves the correct approval routing, creates the workflow item, and hands control to the Workflow background engine. The package also supports a notification-only variant, allowing budgets to be routed for information or acknowledgement without the standard approval activity.

Key Procedures and Functions

• IS_BUDGET_WF_USED — Determines whether a budget approval workflow is applicable for the supplied project, award, budget type, and product context. Callers typically use the result to decide whether to invoke the approval path or to commit the budget directly.
• START_BUDGET_WF — The primary launcher. Given a draft budget version and its project/award/budget-type keys, plus a flag indicating whether the budget should be marked as the original, it creates and starts the budget approval workflow. It returns the workflow item type and item key so the caller can track the resulting process instance, along with standard error code, stage, and stack outputs.
• START_BUDGET_WF_NTFY_ONLY — A parallel entry point that starts the workflow in notification-only mode, bypassing the full approval cycle while preserving the same context and output parameters.
• SELECT_BUDGET_APPROVER — Resolves the approver for a specific workflow item. It takes the workflow item type and key together with the budget context and the identity of the user who started the workflow, and returns the budget baseliner identifier to whom approval is assigned.
• VERIFY_BUDGET_RULES — Evaluates the budget against configured business rules for a given workflow event. It reports the count of error or warning messages raised and indicates whether only warnings were produced, allowing the workflow to branch between approval, rejection, and advisory paths.
• CALL_GMS_DEBUG — A diagnostic utility that writes debug output, filtered by user role, to support troubleshooting of budget workflow behaviour.
• CALL_WF_ADDUSERS_TO_ADHOCROLE — Adds users to an ad hoc Workflow role, supporting dynamic expansion of the approver pool during the budget approval process.

Tables Accessed

• GMS_BUDGET_VERSIONS — The core budget record; holds the draft version being submitted and its approval state.
• GMS_AWARDS and PA_PROJECTS — Provide the award and project context that drives workflow eligibility and approver determination.
• GMS_PERSONNEL, PER_ALL_PEOPLE_F, and FND_USER — Resolve the person and application user identities used for approver selection and role membership.
• PA_BUDGET_TYPES and PA_PROJECT_TYPES — Supply budget type and project type attributes used by the rule verification and eligibility logic.
• GMS_WORKFLOW_ITEMKEY_S — The sequence generating unique Workflow item keys for launched budget processes.
• DUAL — Used for single-row lookups and PL/SQL expression evaluation.

Usage Notes

The package is normally invoked indirectly. In Oracle Grants Management, budget approval is initiated from the budget entry forms and from budget-related concurrent programs, both of which delegate to START_BUDGET_WF or START_BUDGET_WF_NTFY_ONLY. The ETRM metadata records that the package is referenced by one other package, indicating a further layer of internal reuse. Custom extensions should call the documented procedures rather than manipulating GMS_BUDGET_VERSIONS approval columns directly, because the workflow item key and approver routing must be created consistently. As an AUTHID CURRENT_USER package, grants and synonyms must be in place for the calling schema. Error outputs (code, stage, stack) should always be checked after invocation to detect workflow launch failures.