Workday Workday-Adaptive-Planning - Workday-Adaptive-Planning

In Workday Adaptive Planning, user management — including creating, editing, deactivating, and assigning permission sets to users — is performed through the Administration area, accessed via the Global Navigation menu. The Administration section contains all system-level configuration options, including Users & Roles, Security Settings, Integrations, and System Preferences. When an administrator selects Administration from the Global Navigation menu, they can navigate to the Users section where new users can be added by providing their email, name, role, and permission set assignment. Processes is used for managing budget workflows and process tasks. Modeling is the area for configuring the financial model, including accounts, versions, and sheets. Workflow manages approval chains and budget submission processes. User creation is exclusively an administrative function gated within the Administration section, consistent with Adaptive Planning's role-based access control architecture. Reference: Workday Adaptive Planning — Administration Menu, User Management, Security and Access Control.

Workday Adaptive Planning supports exactly one top-level hierarchy structure per instance. The level hierarchy is a single-root tree structure, with 'Top Level' serving as the single apex node from which all organizational levels descend. This architectural constraint is by design: a single unified hierarchy ensures that rollup calculations, security access rules, and formula references operate consistently throughout the entire model. All company, department, cost center, and other organizational levels must be organized within this single hierarchy. While Adaptive Planning supports alternate reporting groupings through level attributes and dimensions, these do not constitute separate top-level hierarchy structures — they are metadata overlays on the primary hierarchy. Attempting to create multiple top-level roots is not supported in the standard configuration. Administrators must plan their level hierarchy carefully during implementation to accommodate all reporting and planning needs within this single-root constraint. Reference: Workday Adaptive Planning — Level Hierarchy Structure, Top Level Configuration, Implementation Best Practices.

In Workday Adaptive Planning standard sheets, cell background colors communicate the editability status of each cell to the user. A grey cell background indicates that the cell is read-only — it may contain a calculated value from a formula or display a rolled-up result, but the user cannot directly enter or modify data in that cell. Read-only cells appear grey to clearly differentiate them from white/editable cells, providing instant visual feedback about where data entry is permitted. This applies to cells that contain shared formulas, cells that are restricted by the sheet's Level Availability configuration, and cells that display rollup calculations. A white cell background indicates an editable cell where a user can enter values. Blue or colored cell backgrounds may indicate other states depending on configuration. Errors in cells are typically displayed with error text rather than a grey background. Rollup accounts do appear grey, but the grey color specifically means read-only, which is a broader category. Reference: Workday Adaptive Planning — Standard Sheet Interface, Cell Color Coding, Read-Only vs Editable Cells.

In Workday Adaptive Planning, all level-assigned sheets — including standard sheets, modeled sheets, and cube sheets that have been configured and assigned to specific levels — are accessible through the Sheets section of the application. The Sheets area serves as the central hub for data entry and planning activities, presenting users with the sheets available to them based on their level access and permission settings. Users navigate to Sheets from the main navigation to find all planning input sheets relevant to their assigned levels. The Assumptions area specifically contains Assumption accounts for global rate and constant entry. Reports is for running and viewing financial and management reports. Modeling is the administrative area for building and configuring the model structure, accounts, and sheets — but it is not where end users go to view or access their assigned sheets for data entry. The Sheets navigation area is the correct and official location for users to access and interact with level-assigned planning sheets. Reference: Workday Adaptive Planning — Sheets Navigation, Level-Assigned Sheets, User Interface.

In Workday Adaptive Planning, an (Only) level is automatically created when child levels are added beneath an existing parent level, converting it into a rollup. The (Only) designation refers to a system-generated virtual level that represents the data entered directly at the parent level, independent of its children's data. For example, when child accounts are created under 'Total Marketing,' the system creates a 'Total Marketing (Only)' level to capture any topside adjustments or entries made directly at the parent level. This prevents the double-counting of data that would occur if parent-level entries were included in child rollup totals. The (Only) level is not manually created — it is a structural byproduct of the rollup relationship. Planners who need to enter data at a rollup level must do so through the (Only) level, which requires specific permission settings in the user's permission set. Reference: Workday Adaptive Planning — Level Hierarchy, Rollup Levels, (Only) Level Behavior, Data Entry at Parent Levels.

In the Workday Adaptive Planning implementation sequence, Time and Versions configuration must be completed before importing level structures. This sequencing is mandatory because levels exist within the context of versions and time periods — each level's data, access rules, and planning activity are bound to specific versions and time periods defined in the system. Without established versions and a configured time calendar, the system lacks the structural framework necessary to associate imported levels with planning periods and versions. Importing levels into an instance without Time and Versions configured would result in incomplete or broken level configurations. Users and Security are configured after the organizational structure (levels) is established. Currencies are important but are not a blocking prerequisite for level import. Account Default Formulas are a model configuration step that occurs after both time/versions and levels are established. Time and Versions is the foundational configuration layer that must precede all organizational structure imports. Reference: Workday Adaptive Planning — Implementation Sequence, Level Import Prerequisites, Time and Version Configuration.

When a new Workday Adaptive Planning instance is initialized, the system automatically creates two default exchange rate types: Average and End of Month. The Average rate is typically used for translating income statement accounts (revenues and expenses), where the average exchange rate over a period better represents the economic reality of ongoing transactions. The End of Month rate is used for translating balance sheet accounts (assets, liabilities, equity), where the closing rate at period end reflects the current value of those balances. These two rate types correspond directly to standard financial accounting currency translation methodologies mandated by accounting standards such as ASC 830 and IAS 21. Historical and Budget rates are additional types that can be created manually but are not default system-generated types. Local and Corporate refer to currency designations, not exchange rate types. Actuals and Plan refer to version types. The Average and End of Month defaults align Adaptive Planning with standard multi-currency financial reporting requirements out of the box. Reference: Workday Adaptive Planning — Currency Setup, Exchange Rate Types, Multi-Currency Configuration.

In Workday Adaptive Planning's Workflow (Process Tracker), the Reject action is used by a manager or approver to send a submitted budget back for revision. When a Reject action is performed, the system unlocks the budget data for all child levels beneath the rejected level, returning edit access to the planners at those levels so they can make corrections and resubmit. This is the correct mechanism for sending work back down the approval chain — the Reject action specifically restores editability to the child levels that had been locked when the budget was submitted. Recall is an action that allows a planner to withdraw their own submission before it has been approved, unlocking their own level's data. Submit locks the data at the current level and sends it up the approval chain. Approve finalizes the submission and may lock data at the parent level. The Reject action's specific function of unlocking all child levels is fundamental to the iterative budget revision process in Adaptive Planning's workflow. Reference: Workday Adaptive Planning — Workflow, Process Tracker, Reject Action, Budget Approval Process.

In Workday Adaptive Planning, Breakback is the feature that enables users to enter a value at a higher time stratum (such as a year column) and have the system automatically distribute that value proportionally across the lower-level time periods (months) within that year. When a user enters a value in the annual total column and triggers Breakback, Adaptive Planning allocates the annual amount to the individual months based on a defined distribution method — such as equal distribution, weighted by existing values, or following a seasonal pattern. This is the reverse of the standard bottom-up aggregation (where monthly values roll up to the year). Splits is used to distribute values across dimension values or account line items, not time periods. Copy Forward replicates values from one period to subsequent periods. Adjust applies a percentage or absolute change to existing values. Breakback is the specific, official term for top-down time period allocation in Adaptive Planning. Reference: Workday Adaptive Planning — Breakback, Standard Sheet Data Entry, Time Period Allocation.