Workday-Adaptive-Planning Workday-Adaptive-Planning Questions and Answers

When importing new levels into Workday Adaptive Planning via the level import process, the 'Rolls up to' field is a required data element. This field specifies the parent level to which the new level reports, defining its position within the organizational hierarchy. Without the 'Rolls up to' value, the system cannot place the level correctly in the hierarchy, making it an essential import requirement. The import file for levels typically requires: the level name, the level code, and the 'Rolls up to' parent reference. While the level Code is also important for identification, among the options listed, 'Rolls up to' is the critical structural requirement that determines hierarchy placement. Short name is optional metadata. Currency can default to the corporate currency if not specified for individual levels. The 'Rolls up to' field is the hierarchical anchor that the system mandates to establish parent-child relationships during bulk level imports. Reference: Workday Adaptive Planning — Level Import, Required Level Fields, Hierarchy Configuration.

In Workday Adaptive Planning, the Append import option is specifically designed to add new time periods (such as prior or future years) to an existing calendar without altering or replacing the current time strata structure, existing period definitions, or data. Append adds new calendar entries to the existing configuration, extending the calendar in either direction while preserving all existing time period configurations, data, and formula references. The 'Reload entire structure' option would replace the entire calendar configuration, potentially destroying existing time strata and any data associated with current periods. 'Overwrite' replaces existing records with the imported values, which could alter existing period definitions. 'Update' modifies existing records but does not specifically address the requirement of adding new periods while protecting existing structure. Append is the safe, non-destructive option for calendar extension during ongoing system maintenance, and is the recommended approach for adding time periods to a live instance. Reference: Workday Adaptive Planning — Calendar Import, Append Option, System Maintenance, Time Configuration.

In Workday Adaptive Planning, a single value lookup table for the Benefit Election dimension is the correct design to drive different calculation rates based on which benefit election a user selects in a modeled sheet. A value lookup table maps each dimension value (e.g., Single, Family, Employee+Spouse) to a corresponding rate value, enabling the modeled sheet formula to dynamically look up the appropriate rate for whichever benefit election is selected on each row. This architecture is efficient, maintainable, and requires only one lookup object rather than separate tables per dimension value. Creating a separate value lookup table for each dimension value (Option C) is unnecessarily complex and duplicates data structures. A cube sheet (Option B) could store rate assumptions but requires a more complex reference architecture than a simple value lookup. A Rate dimension attribute (Option D) stores static metadata on dimension values and cannot drive time-sensitive rate lookups in calculations. The single value lookup table per dimension is the official, recommended pattern in Adaptive Planning's modeled sheet design. Reference: Workday Adaptive Planning — Value Lookup Tables, Modeled Sheets, Dimension-Driven Calculations.

A Metric account in Workday Adaptive Planning is specifically designed to display calculated Key Performance Indicators (KPIs) such as ratios, percentages, and performance measures that are derived from other account values. The profit margin ratio — calculated as Operating Income divided by Revenue — is a classic financial KPI that does not represent a ledger balance but rather a derived performance indicator. Metric accounts are formula-driven, read-only in nature, and are displayed on financial statements and reports alongside GL accounts to provide contextual performance insight. They support percentage formatting and can reference other account types in their formulas. Calculated accounts have a different architectural role in Adaptive Planning and are not the standard type for KPI ratios. General Ledger accounts store transactional financial data. Custom accounts serve structural or supplemental purposes. Metric accounts are the official account type for financial ratios and KPIs in the Adaptive Planning account hierarchy and appear under Model Management > Accounts. Reference: Workday Adaptive Planning — Metric Accounts, KPI Configuration, Financial Statement Display.

In Workday Adaptive Planning, a Default formula is the configuration that enables a formula defined on an account to apply universally across all levels and all versions simultaneously. When a Default formula is set on an account such as Labor (5010), the formula — in this case, 6% of the Income account value — becomes the baseline calculation for every level in the hierarchy and every version in the instance, unless a level-specific or version-specific override is explicitly defined. This is the precise mechanism for ensuring consistent, model-wide formula application without duplicating formula entries across individual levels or versions. A Shared formula also propagates formulas across levels but operates within specific version contexts and requires explicit sharing configuration. A Metric account is used for KPI display and is read-only by nature, not suitable for labor cost planning. A Modeled calculated account applies to row-based modeled sheet structures, not standard GL account formula propagation. The Default formula is the correct and official Adaptive Planning feature for establishing universal cross-level, cross-version formula consistency on GL accounts. Reference: Workday Adaptive Planning — Default Formulas, Account Formula Types, Formula Scope Configuration.

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 Workday Adaptive Planning, modeled sheets offer flexibility in time stratum configuration, allowing administrators to select any time stratum that is defined and available in the instance's calendar — including Month, Quarter, Year, or any custom stratum configured for the instance. This flexibility distinguishes modeled sheets from some other sheet types that may be bound to the default instance time stratum. For example, a Personnel modeled sheet might be set to a monthly stratum for per-pay-period tracking, while a Capital Projects modeled sheet might use an annual or quarterly stratum. The available strata are determined by the time calendar setup in the instance. The time stratum for a modeled sheet is not determined by the version's time stratum (versions inherit the instance default). It is not limited to quarterly only. It is not restricted to the instance default — the key advantage of modeled sheets is the ability to choose from all available strata. Reference: Workday Adaptive Planning — Modeled Sheet Configuration, Time Stratum Selection, Sheet Design.

In Workday Adaptive Planning, the default time stratum is Month > Quarter > Year. To reference the same quarter from one year ago, the correct time modifier is [time=this.qtr-4], which shifts back four quarters (equivalent to one year) from the current quarter. The divf() function performs a floating-point division of the quarterly total by 3 to derive a monthly average. This is correct because a quarter contains 3 months, and dividing the quarterly amount by 3 yields the average monthly value for that quarter. The formula divf(ACCT.Example[time=this.qtr-4] , 3) retrieves the total value for the quarter that is four quarters prior and divides by 3 to return the average monthly value. Option B uses this.year-1, which references the full prior year rather than the same quarter. Option C's syntax [time=this.qtr, this.year-1] is not valid Adaptive Planning formula syntax. Option D uses a month range modifier that does not correctly target a full quarter. Reference: Workday Adaptive Planning — Time Modifiers, Quarter References, divf() Function, Formula Syntax.

Reviewing the access rules table displayed in the scenario, hr@wdayptnrgcf.com is assigned multiple access rules: Full View to 410-01 IT, Full View to 110-03 Manufacturing-Europe, Edit to Total G and A, Edit to Total Manufacturing, and Edit to Total Sales and Mkt. In Workday Adaptive Planning, when a user is granted access to a parent level such as Total Manufacturing with Edit permissions, that access cascades to all descendant levels beneath it — including 110-01 Manufacturing-USA, 110-02 Manufacturing-Canada, and 110-03 Manufacturing-Europe. The question asks what access the HR analyst has, and among the options presented, 'Edit access to the Total Manufacturing level' is the correct characterization of their most significant structural permission. Full View to GCF Inc or Top Level is not listed in the rules. The access configuration demonstrates a deliberately scoped, multi-level permission set typical in departmental HR planning scenarios. Reference: Workday Adaptive Planning — Security Configuration, Level Access Rules, Edit vs. Full View Permissions.

In Workday Adaptive Planning, General Ledger accounts such as Prepaid Advertising are created under Root accounts, which are the primary account categories that form the top-level structure of the Chart of Accounts. Root accounts represent the highest level of the account hierarchy and include categories such as Assets, Liabilities, Equity, Revenue, and Expenses. Prepaid Advertising, being a prepaid asset or operating expense account in standard accounting, would be created as a child of the appropriate Root account category. System accounts are pre-built accounts managed by Adaptive Planning for system-level calculations and cannot be user-created. Assumption accounts are reserved for global planning constants like rates and percentages. Contra accounts are used to offset balances in specific accounts (e.g., Accumulated Depreciation) and are a sub-classification, not a primary creation category. The correct workflow is to navigate to Modeling > Model Management > Accounts and create the new GL account under the appropriate Root. Reference: Workday Adaptive Planning — Chart of Accounts, Root Account Structure, General Ledger Account Creation.

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, when a cube sheet is configured at the Year time stratum, all data stored in that sheet exists at the annual level — not at monthly periods. When formulas on monthly sheets or other sheets reference accounts from this year-stratum Rates cube sheet, the reference must include the [time=this.year] modifier to correctly resolve the time dimension. Without this modifier, a monthly formula attempting to reference a year-stratum account may return zero or an error because the system cannot automatically match a monthly time context to an annual data point. The [time=this.year] modifier explicitly instructs the formula to retrieve the annual value corresponding to the year in which the current period falls. Automatic breakback does not apply to formula references from external sheets. Monthly inputs cannot aggregate to a year-stratum cube sheet — data must be entered at the year level. References across different time strata require explicit time modifiers to ensure correct data retrieval. Reference: Workday Adaptive Planning — Cube Sheet Time Stratum, Cross-Sheet References, [time=this.year] Modifier.

Workday Adaptive Planning enforces specific naming conventions for level names to ensure compatibility with formulas, imports, exports, and API integrations. Level names must not contain special characters such as colons (:), ampersands ( & ), or forward slashes (/), as these are either reserved characters in formula syntax or cause parsing errors during data imports and exports. The colon (:) is used in formula notation as a separator; the ampersand ( & ) can be misinterpreted as a string concatenation operator; the forward slash (/) can be confused with division. The only properly formatted option among those presented is '1000 Sales - France and Germany,' which uses only alphanumeric characters, spaces, a hyphen, and the word 'and' — all of which are safe and compliant with Adaptive Planning's naming standards. Proper level naming is critical during system setup as it prevents downstream issues in reporting, formula references, and data integrations. Reference: Workday Adaptive Planning — Level Setup, Naming Conventions, Level Import Requirements.

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.

In Workday Adaptive Planning, the Formula Assistant is the built-in tool designed specifically to help users construct, validate, and test formulas within the system. The Formula Assistant provides an interactive interface for browsing available functions (such as div, divf, if, sum), selecting valid account references, choosing appropriate time modifiers, and reviewing function syntax — all without requiring the user to memorize formula syntax from scratch. It provides real-time syntax guidance, function descriptions with parameter explanations, and the ability to test formula logic against actual data before committing. This is the primary tool for formula development and validation in Adaptive Planning. Account Details provides metadata about an account's configuration but does not assist in formula construction. Linked Accounts shows accounts that reference each other but is not a formula building tool. Shared Formulas is a method for applying the same formula across multiple levels or accounts but is not an interactive assistance feature. The Formula Assistant is the official, purpose-built formula construction tool in Adaptive Planning. Reference: Workday Adaptive Planning — Formula Assistant, Formula Development, Account Formula Configuration.