Approval workflow in Oracle EPM Planning is the mechanism through which submitted planning data moves through a defined sequence of review, challenge, and approval stages — from the initial data entry by a budget preparer, through intermediate reviewers, to final approval by the process owner. The workflow is governed by the planning unit hierarchy: each planning unit transitions through a defined set of statuses (Not Started, First Pass, Under Review, Approved, Published), and each transition is performed by a user with the appropriate workflow role for the relevant stage. The approval workflow enforces both data review discipline and data access control — a planning unit’s status determines whether data can be written, reviewed, or only read at each stage.
Workflow Mechanics
Each planning unit status transition is triggered by a user action: the preparer promoting from First Pass to Under Review, the reviewer approving or rejecting (sending back to First Pass), the senior reviewer approving or escalating. Each transition is logged with the user’s identity, timestamp, and any annotated comment — creating an audit trail of the planning unit’s lifecycle. Email notifications for workflow transitions require configuration of Planning’s email notification settings and a valid SMTP configuration; without notification, workflow participants must poll the Planning interface to discover that a planning unit has reached a stage requiring their action.
Design Considerations
Workflow stage design must reflect the organisation’s actual review governance — not a theoretical governance ideal. An approval workflow with five stages sounds comprehensive; if the organisation’s actual budget review involves only two substantive review cycles (entity preparer and group finance review), a five-stage workflow creates administrative overhead without adding review value. Unnecessary workflow stages produce planning units that are administratively moved through intermediate stages without genuine review at each stage, undermining the audit value of the workflow log.
What Goes Wrong in Practice
The specific approval workflow failure that most frequently extends the budget cycle beyond its planned duration is planning units that are submitted and then returned to First Pass without a documented reason. When reviewers can reject a planning unit without providing a mandatory comment explaining the reason for rejection, preparers receive a rejection notification without understanding what needs to be corrected — requiring a separate communication channel to determine the review feedback. Mandatory rejection comments are a workflow configuration setting in Planning that should be enabled for every stage where a rejection action is available.
How Loop Wise Solutions Handles This
We design approval workflow stages from the actual review governance process — the number of stages should equal the number of substantive review cycles in the client’s budget governance, not the maximum that Planning can support. We configure mandatory rejection comments for all rejection actions and include workflow action training in the key user programme — ensuring that reviewers understand how to document their review feedback within the Planning workflow rather than through external communication channels.
