A Task List in Oracle EPM Planning (PBCS/EPBCS) is a predefined, ordered sequence of tasks that guides a planning user through the steps required to complete a specific process — a budget submission, a forecast revision, a close cycle data entry sequence, or an end-of-period review. Each task in the list represents a specific action within the EPM application: opening a data entry form, running a business rule, viewing a report, importing data, or completing an external action (performing a step outside EPM that must be acknowledged as complete before the task list can advance). Task lists provide process governance through the EPM interface — rather than relying on a planner to remember the correct sequence of steps from a Word document or email instruction, the task list surfaces the next required step directly in the EPM application and prevents the user from marking a step complete until the required action is confirmed.
Task List Architecture
| Task Type | What It Does | Planning Use Case |
|---|---|---|
| Form task | Opens a specified data entry form for user input | Headcount input form, driver-based assumptions form |
| Business rule task | Executes a specified business rule (with optional runtime prompt) | Spread annual budget to months, copy budget to working version |
| Report task | Opens a Financial Reporting Studio or OBIEE report | Review prior-year actuals before entering budget; validate submission against guideline |
| Copy data task | Copies data between scenarios, versions, or periods | Copy Working Budget to Submitted Budget |
| URL task | Opens an external URL — external tool, SharePoint, or instruction document | Access external assumptions worksheet; review budget guidance document |
| Composite task | A task that contains sub-tasks — allows grouping of related steps | Group “Revenue Planning” sub-tasks under a “Revenue” parent task |
Task Lists vs Task Manager
EPM Planning Task Lists are specific to the Planning application and govern the individual planning user’s workflow within their budget submission process. Oracle Task Manager is the broader close calendar orchestration application — governing the enterprise-wide close process across Finance, EPM, and external activities with multi-user dependencies and executive-level status visibility. Task Lists are the micro-workflow tool for individual planning users; Task Manager is the macro-workflow tool for the close management team. In Oracle EPBCS deployments, both coexist: Task Manager tracks the overall budget cycle timeline (when regional submissions are due, when the global rollup must complete), while Planning Task Lists guide each regional finance manager through the specific steps of their submission within the Planning application.
GCC Budget Cycle Task List Design
For GCC enterprise budget cycles where the planning process involves entities across Saudi Arabia, UAE, and Egypt — each with their own finance managers performing their submissions in different time zones — task lists provide a self-service guidance mechanism that reduces the volume of process support questions directed at the EPM team. A well-designed task list for the entity budget submission includes the data entry steps in the correct sequence, embedded data validation business rules that run automatically after each entry step, and a final submission step that triggers the Planning Unit advancement — advancing the planning unit from “Under Review (Entity)” to “Submitted” status in the approval workflow. Entity finance managers can complete their submissions following the task list without requiring guidance from the central EPM support team for each step.
What Goes Wrong in Practice
The specific task list failure that most disrupts planning cycle governance is a task list that becomes obsolete between budget cycles — because a form was renamed, a business rule was retired, or a step’s sequence was changed, but the task list was not updated to reflect the change. When a planning user opens a task list that references a deleted form or a retired business rule, the task errors on execution and the user cannot advance past the broken step. Task lists must be tested at the start of every planning cycle — before they are published to the planning user community — to confirm that every referenced form, business rule, and report is current and accessible.
How Loop Wise Solutions Designs Task Lists
We design task lists for every repeating planning and close process delivered through Oracle EPM — building the process governance directly into the application rather than relying on external process documents. Task list maintenance — reviewing and updating after every planning cycle — is included in our EPM managed service engagements as a standard activity.
