In Workday Adaptive Planning modeled sheets, a value lookup for dimensions or text selector columns serves the primary function of associating specific values to dimension or text fields over time, which are then referenced in formula calculations within the modeled sheet. For example, a value lookup might associate a specific benefit election (e.g., 'Family Plan') with a corresponding rate value that changes over time periods — enabling the modeled sheet formula to look up the appropriate rate based on the selected dimension value and time period. This lookup mechanism is what powers time-sensitive, dimension-driven calculations in complex planning models such as HR, benefits, compensation, and sales planning. It is not used for entering global assumption values (which is done directly in Assumption accounts), nor for general data entry into model columns, nor for time-spreading functions (which is handled by Splits/Breakback). The value lookup is a purpose-built mechanism for dynamic, time-aware dimensional rate association. Reference: Workday Adaptive Planning — Modeled Sheets, Value Lookups, Dimension Calculations.

In Workday Adaptive Planning, Accounts are the single required element to create a modeled sheet. A modeled sheet must have at least one account defined to represent the data being planned — accounts serve as the columns in a modeled sheet, capturing the various values for each row (record). Without an account, a modeled sheet has no data structure and cannot be created or saved. Dimensions are commonly used in modeled sheets to enable dimensional data entry and classification, but they are optional — a basic modeled sheet can function with accounts alone. Levels are not a creation requirement for modeled sheets; the sheet applies to levels through its assignment configuration, not as a creation prerequisite. Attributes are metadata elements used for filtering and grouping but are not required for sheet creation. The account is the foundational element of any Adaptive Planning sheet type — it represents what is being measured or planned. In the context of modeled sheets, accounts define the column structure of each planning row. Reference: Workday Adaptive Planning — Modeled Sheet Creation, Required Elements, Sheet Architecture.

In Workday Adaptive Planning, if a matrix report is created without a version explicitly defined in the report design, the system will prompt the user running the report to select a version at runtime. Rather than generating an error or silently applying a default version, Adaptive Planning presents a version selection prompt to ensure the report displays data from the user's intended version context. This behavior provides a safety net for incomplete report configurations while still allowing the report to be run and useful output to be generated. It also introduces a degree of user control over which version is analyzed. The system does not automatically apply a default version or the last viewed version, as this could lead to users inadvertently analyzing incorrect data without awareness. Generating an error would make the report unusable. The prompt behavior ensures the report remains functional while requiring explicit user confirmation of the data context. Reference: Workday Adaptive Planning — Matrix Reports, Version Configuration, Report Runtime Behavior.

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.

When expense results in a linked OPEX model appear under the 'Uncategorized' location dimension value, it indicates that the source personnel sheet data does not carry location dimension information. In Workday Adaptive Planning, when a cube or modeled sheet references data from another sheet via a linked account formula, the dimension values present in the results are determined by the dimension values present in the source data. If the personnel sheet was not planned with the location dimension — meaning location was not used as a planning axis when entering headcount data — then the location dimension has no value assigned to those rows, and the system classifies them as 'Uncategorized' in the OPEX output. The solution is to configure the personnel sheet to include the location dimension as a planning axis, so that headcount entries are tagged with specific location values. Adding formula term modifiers for location in OPEX would not resolve the root cause, which is missing dimensional data at the source. Reference: Workday Adaptive Planning — Dimensional Data Linking, Location Dimension, Cube Sheet Architecture.

In Workday Adaptive Planning, when an account is deleted from the model, all associated formulas and data stored in that account are permanently and irreversibly deleted across all versions and all levels. There is no automatic transfer, reassignment, or archiving mechanism. The system does not migrate data to sibling accounts or parent rollups upon deletion. This is a critical and irreversible action — once the Rent account is removed, its historical actuals, plan data, and any formulas are permanently lost from the model. This behavior underscores the importance of data backup and version control before performing structural changes. Administrators should export or archive data before deleting accounts. The rollup account Total Operating Expenses will continue to function but will now only aggregate the remaining child, Salaries. Any reports or dashboards referencing the deleted Rent account will return errors or blank values. Reference: Workday Adaptive Planning — Account Management, Account Deletion Behavior, Model Maintenance Best Practices.

In Workday Adaptive Planning, a Parameter is the report design feature that enables each user running a report to make interactive selections — such as choosing their specific department (level) — at the time they run the report. Parameters create dynamic input prompts that appear when a report is executed, allowing users to select from available levels, versions, time periods, or other report axes based on their access permissions. This is ideal for a shared matrix report used by multiple departmental managers: each manager opens the same report but selects their own department from the Parameter prompt, receiving a personalized view of their expenses without requiring separate reports per manager. Filters apply static, pre-set conditions that are fixed by the report designer and are not adjustable by end users at runtime. Drill Down Choices enable hierarchical data exploration within a report but do not control the initial selection scope. Manage Hierarchy is not an interactive parameter feature. Parameters are the official mechanism for enabling user-driven, runtime report customization in Adaptive Planning reporting. Reference: Workday Adaptive Planning — Matrix Reports, Parameters, Report Design, Interactive Reporting.

In Workday Adaptive Planning, account deletion is a permanent and irreversible operation. When the Rent account is removed from the model, all formulas and data associated with that account are immediately and permanently deleted across every version (Actuals, Budget, Forecast) and every level in the organizational hierarchy. There is no automatic reassignment mechanism — the system does not migrate data to sibling accounts such as Salaries, nor does it transfer data up to the parent rollup account Total Operating Expenses. There is no archiving or soft-delete function that preserves data in a recoverable state. The rollup account Total Operating Expenses will continue to aggregate data from its remaining children, but the Rent account's contribution is permanently lost. This behavior makes account deletion one of the most consequential structural changes an administrator can perform. Best practice requires administrators to export or document all account data before deletion and to audit any reports, dashboards, or formulas that reference the account being removed, as those references will produce errors post-deletion. Reference: Workday Adaptive Planning — Account Management, Account Deletion Behavior, Model Maintenance, Data Integrity.