In Workday Adaptive Planning, a Metric account is the designated account type for displaying calculated Key Performance Indicators and financial ratios on the Income Statement and other financial reports. The profit margin ratio — Operating Income divided by Revenue, expressed as a percentage — is a derived KPI, not a transactional ledger balance. Metric accounts are formula-driven and read-only, meaning they calculate and display a result but cannot receive direct data entry. They support percentage formatting and can be configured to reference any combination of GL accounts, rollup accounts, or Assumption accounts within their formula. Metric accounts appear inline on financial statements alongside GL accounts, providing contextual performance visibility for planners and executives. A Custom account serves structural or supplementary roles not covered by standard account types. A General Ledger account stores transactional financial data such as actual or budgeted monetary amounts and is not appropriate for ratio display. A Calculated account is not a distinct, standard account type in the Adaptive Planning account classification framework for this use case. Metric is the authoritative, purpose-built account type for financial ratios and KPI display. Reference: Workday Adaptive Planning — Metric Accounts, KPI Configuration, Income Statement Design, Financial Ratios.

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 formula syntax, [time=this.year-1] is the correct and officially supported modifier to retrieve the full prior fiscal year value of an account. This modifier navigates to the year period that is one year before the current year context, returning the annual total for the previous fiscal year — which is the precise requirement for incorporating full-year prior year expenses into a formula. Option A uses [time=last.year] , which is not standard Adaptive Planning formula syntax and would result in a formula error. Option C uses [year=previous], which is also not valid Adaptive Planning formula notation. Option D uses [time=this-12] , which shifts back 12 months — for a monthly formula, this returns the same month from the prior year, not the full prior year total. When a formula needs the full prior year annual amount (sum of all 12 prior months), [time=this.year-1] retrieves the aggregated annual value. This is the authoritative time modifier syntax for annual prior year refere nces in Adaptive Planning. Reference: Workday Adaptive Planning — Time Modifiers, Prior Year References, Formula Syntax Guide.

In Workday Adaptive Planning, the 'Change Dimensions' toolbar option on a cube sheet allows end users to interactively modify which elements are displayed on the vertical (row) and horizontal (column) axes. This feature provides analytical flexibility, enabling users to pivot the view of the cube sheet — for example, moving a dimension from rows to columns, adding or removing dimensions from the view, or swapping the axis orientation. This is particularly valuable for ad hoc analysis where users need to explore data from different dimensional perspectives without requiring an administrator to reconfigure the sheet. 'Reset to Default View' returns the sheet to its administrator-defined default layout. 'Sheet Properties' contains configuration settings for the sheet's structural properties, not axis manipulation. 'Dimensions, attributes, and levels' may describe elements within the sheet but is not the specific toolbar option for axis management. 'Change Dimensions' is the dedicated interactive tool for axis manipulation in cube sheets. Reference: Workday Adaptive Planning — Cube Sheets, Change Dimensions, User Interaction, Axis Configuration.

In Workday Adaptive Planning, View mode is the dashboard mode that enables users to interactively engage with dashboard charts by clicking on data points, bars, or other chart elements to drill into underlying data for deeper analysis. In View mode, charts are live and interactive — users can hover over data points to see values, click segments to filter or drill down, and explore data relationships dynamically. This interactivity supports analytical workflows where users need to investigate variances, examine underlying details, or navigate from summary charts to granular data. Presentation mode renders the dashboard in a static, display-oriented format optimized for showing to an audience, with limited interactivity. Grid mode may display data in a tabular format but is not designed for chart interaction. Snapshots capture the current state of a dashboard at a point in time as a static image for archival or comparison purposes. View mode is the standard operational mode for dashboard users who require analytical interactivity with visualized data. Reference: Workday Adaptive Planning — Dashboards, View Mode, Interactive Analytics, Data Exploration.

A modeled sheet is the appropriate design for detailed travel expense planning because it is architected to capture granular, row-level data where each row represents a discrete planning record — in this case, an individual trip. Modeled sheets support custom columns (accounts) such as destination, travel dates, estimated cost, level assignment, and dimension values, enabling planners to build detailed itinerary-level budgets. The data aggregates upward to summary levels for inclusion in corporate reporting. This meets both requirements: detailed planning visibility for Finance and individual planner completion per forecast cycle. A standard sheet captures aggregate monthly amounts by level but lacks the row-level granularity needed for trip-by-trip detail. A standard sheet with a historical formula is a top-down estimation approach, not a detailed planning model. A cube sheet with assumption-based calculation is a statistical model, not a detailed record-level capture. The modeled sheet's row-based architecture is specifically designed for this class of detailed operational planning. Reference: Workday Adaptive Planning — Modeled Sheets, Sheet Design Patterns, Travel Planning Use Case.

In Workday Adaptive Planning, when a sub-account (child account) is created beneath an existing General Ledger account, the system converts the parent account into a rollup account. As part of this structural transformation, all existing data and any formulas that were previously stored in the parent Inventory account are automatically migrated to the newly created child account. The parent then becomes a rollup that aggregates the values of its children. This behavior ensures no data loss during model restructuring. The rationale is that rollup accounts do not hold direct data — only leaf accounts (bottom-level accounts without children) can contain input values or formulas. Therefore, the system must relocate the data to maintain model integrity. Administrators should be aware of this behavior before creating sub-accounts in live environments, as it directly affects reporting and formula references. Existing reports may need to be updated to reflect the new account reference. Reference: Workday Adaptive Planning — Chart of Accounts, Account Hierarchy, Sub-Account Creation Behavior.

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, 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.

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.