Search Results reject_budget
Overview
APPS.PA_BUDGET_WF is the Oracle Projects budget approval workflow integration package within Oracle E-Business Suite 12.1.1 and 12.2.2. It provides the PL/SQL callback layer that the Oracle Workflow engine invokes during the budget approval process for project budgets. The package mediates between the Workflow runtime and the Projects budgeting tables, determining routing (approver selection), validating business rules, applying final disposition (baseline or rejection), and launching the workflow itself. Functionally, it enables the "Budget Approval" workflow used when a draft budget version is submitted for approval, including optional Federal budgetary controls, and it correlates workflow state with budget version state so that the budget lifecycle (draft, submitted, approved/baselined, rejected) remains consistent with the workflow item activity status.
Key Procedures and Functions
- Select_Budget_Approver — Workflow callback used to resolve the approver (or approver list) for the current approval step based on the workflow item context. Called by the Workflow engine using the standard itemtype/itemkey/actid/funcmode signature, returning a result string.
- Verify_Budget_Rules — Evaluates business rules to determine whether the budget may proceed along a given workflow transition. Used to gate branching in the approval process (for example, threshold or rule-based routing decisions).
- Baseline_Budget — Invoked when the approval completes successfully; it performs the baselining action on the associated budget version so the approved budget becomes the new baseline for the project.
- Reject_Budget — The rejection handler. When the workflow is rejected (including the scenario a user triggers by searching "reject_budget"), this procedure updates the affected budget version and related records so the budget is marked rejected rather than approved or baselined, and it clears the workflow-related status.
- Budget_WF_Is_Used — Utility that determines whether the Budget Approval workflow is applicable/active for a given draft version, project, budget type, and product context, optionally with financial plan type and version type. It returns a result flag plus error code, stage, and stack outputs.
- Start_Budget_WF — Entry point that launches the Budget Approval workflow for a specified draft version and project. Accepts flags controlling original-baseline marking, Federal request handling, budget integration, financial plan type, and version type, and returns error code/stage/stack outputs.
- Is_Federal_Enabled — Function that reports whether Federal (budgetary) functionality is enabled, allowing workflow logic to branch for Federal-enabled installations.
Tables Accessed
- PA_BUDGET_VERSIONS — The primary budget entity: version status, baseline indicator, and the draft version being approved or rejected are read and updated here.
- PA_BUDGET_TYPES — Supplies budget type attributes used to determine workflow applicability and rule evaluation.
- PA_PROJECTS / PA_PROJECTS_ALL — Provides project and organization context, including project type linkage needed for approver and rule resolution.
- PA_PROJECT_TYPES — Project type attributes that participate in determining whether the workflow applies and how it routes.
- FND_USER — Resolves workflow/approver identities to application users.
- PA_WF_PROCESSES — Stores the association between Projects documents and their workflow item keys, linking a budget version to its workflow instance.
- WF_ITEM_ACTIVITY_STATUSES — The Workflow runtime status table; read to resolve the current item/activity context used by the callback procedures.
Usage Notes
PA_BUDGET_WF is not typically called directly by end users or custom forms. Its procedures are registered as workflow callbacks on the Budget Approval process, so the Workflow engine invokes them at specific activities: Select_Budget_Approver for routing, Verify_Budget_Rules for transition gating, Baseline_Budget on approval, and Reject_Budget on rejection. Start_Budget_WF and Budget_WF_Is_Used are the programmatic seam used by Oracle Projects concurrent processes and forms when a budget is submitted for approval, while Is_Federal_Enabled supports Federal-specific branching. Because the package is documented as referenced by four other packages, customizations should call Start_Budget_WF/Budget_WF_Is_Used rather than reinventing submission logic, and error handling should check the returned error code, stage, and stack outputs. Any modification to rejection behavior must be validated against PA_WF_PROCESSES and PA_BUDGET_VERSIONS to avoid orphaned workflow items or inconsistent budget status.
-
PACKAGE: APPS.PA_BUDGET_WF
12.1.1
-
PACKAGE: APPS.PA_BUDGET_WF
12.2.2
-
PACKAGE: APPS.GMS_WF_PKG
12.2.2
-
PACKAGE: APPS.GMS_WF_PKG
12.1.1
-
PACKAGE BODY: APPS.PA_BUDGET_WF
12.1.1
-
PACKAGE BODY: APPS.PA_BUDGET_WF
12.2.2
-
PACKAGE BODY: APPS.GMS_WF_PKG
12.2.2
-
PACKAGE BODY: APPS.GMS_WF_PKG
12.1.1
-
APPS.PA_BUDGET_WF dependencies on PA_BUDGET_WF
12.2.2
-
APPS.PA_BUDGET_WF dependencies on WF_CORE
12.2.2
-
APPS.PA_BUDGET_WF dependencies on PA_BUDGET_WF
12.1.1
-
APPS.PA_BUDGET_WF dependencies on WF_CORE
12.1.1
-
APPS.GMS_WF_PKG dependencies on WF_CORE
12.2.2
-
APPS.GMS_WF_PKG dependencies on WF_CORE
12.1.1
-
APPS.PA_BUDGET_WF dependencies on FND_API
12.1.1
-
APPS.GMS_WF_PKG dependencies on GMS_WF_PKG
12.1.1
-
APPS.PA_BUDGET_WF dependencies on FND_API
12.2.2
-
APPS.GMS_WF_PKG dependencies on GMS_WF_PKG
12.2.2
-
APPS.GMS_WF_PKG dependencies on FND_API
12.2.2
-
APPS.GMS_WF_PKG dependencies on FND_API
12.1.1