Search Results pa_wf_client_extn

Overview

PA_CLIENT_EXTN_BUDGET_WF is a client extension package body owned by APPS that governs whether an Oracle Workflow approval process is initiated for a project budget in Oracle E-Business Suite. The package implements the business rules that determine whether a given budget requires workflow-based approval, identifies the appropriate approver, validates budget rules, and, when conditions are satisfied, launches the budget approval workflow. It is classified as an OTHER API with an internal API version constant (G_API_VERSION_NUMBER := 1.0), reflecting its role as a versioned client extension rather than a conventional public API.

A distinguishing characteristic of this extension is that it is invoked directly from the Budgets form and from the public Baseline_Budget API (through a wrapper of the same name), and is explicitly not called from workflow itself. Error conditions raised in the form or public API surface under the error code PA_WF_CLIENT_EXTN, to which two tokens are passed: the name of the client extension and the error code.

Key Procedures and Functions

• BUDGET_WF_IS_USED — Determines whether a workflow should be started for a particular budget, returning a value of "T" or "F". This is the primary gating procedure for the extension and is the entry point called from the Budgets form and the Baseline_Budget API wrapper.
• START_BUDGET_WF — Initiates the budget approval workflow once the decision to require approval has been established.
• SELECT_BUDGET_APPROVER — Resolves the approver to be associated with the budget approval workflow, drawing on user and person data.
• VERIFY_BUDGET_RULES — Validates the budget against the applicable approval rules, ensuring the workflow is only raised when rule conditions are met.

Tables Accessed

The package reads reference and transactional data through APPS synonyms. Project and budget context is drawn from PA_PROJECTS, PA_BUDGET_VERSIONS, PA_BUDGET_TYPES, PA_BUDGET_ENTRY_METHODS, and PA_FIN_PLAN_TYPES_B / PA_FIN_PLAN_TYPES_TL. Enablement flags held on PA_PROJECT_TYPES and PA_BUDGET_TYPES are consulted to decide whether workflow applies, and PA_PROJ_FP_OPTIONS supports the financial plan model logic. Approver identity is resolved from FND_USER and PER_ALL_PEOPLE_F. PA_WORKFLOW_ITEMKEY_S supplies the workflow item key sequence, and DUAL is used for trivial single-row queries.

Usage Notes

Typical invocation occurs interactively when a user submits a budget for approval from the Budgets form, or programmatically when the Baseline_Budget public API is called; the wrapper of the same name ensures consistent behavior across both paths. Because the package is a client extension, customers and implementers may customize the decision logic, but the documented procedure signatures and the "T"/"F" return contract must be preserved to avoid breaking the calling form and API. The package is referenced by three other packages, indicating a degree of internal dependency within the project budgeting and workflow integration layer. When diagnosing approval-related errors, the PA_WF_CLIENT_EXTN error code and its two tokens should be used to trace the failure to the specific extension and rule involved.