Architecture & Model Design

Adaptive Planning: Why an Assumption Is Visible but Not Editable at Company Level

Adaptive Planning: Why an Assumption Is Visible but Not Editable at Company Level
Adaptive Planning: Why an Assumption Is Visible but Not Editable at Company Level
Adaptive Planning – EPMLogic

A common Workday Adaptive Planning configuration problem occurs when users can select a company or cost center but cannot enter values into an assumption account.

This often happens when the planning requirement changes from a single corporate assumption to different inputs by entity or department.

Example

Finance wants to maintain holiday assumptions separately:

However, the model currently allows users to enter holidays only at the top level.

Users can select the company, but the cells remain read-only.

What to check

1. Account configuration

Identify the assumption account and review how it is defined.

Check whether the account is designed for input at the required levels or uses a formula that prevents direct input.

2. Sheet level availability

Review the assigned sheet configuration.

A company being visible in the level selector does not necessarily mean that every account on the sheet accepts input at that level.

3. Version and access controls

Confirm that the relevant period and version are available for input.

Also review the user’s level permissions and applicable access restrictions.

4. Formula and inheritance behavior

Determine whether a top-level value is being inherited by child levels.

If the business requires company-specific holiday values, confirm that the account and calculation architecture support those inputs.

5. Test downstream calculations

Use controlled sample values at two different companies.

Verify that holiday pay calculations use the intended company-specific assumptions and that higher-level reporting behaves correctly.

Architecture consideration

Holiday assumptions are usually drivers, not additive financial amounts.

If three companies have 12, 14, and 10 holidays, the corporate reporting value should not automatically be treated as 36 holidays.

The correct aggregation or reporting treatment must follow the business requirement.

Conclusion

When an Adaptive Planning cell is read-only, changing sheet visibility alone may not resolve the issue.

Validate the account, sheet configuration, level availability, formulas, version and security together.

A model should support the level at which the business actually plans.

EPMLogic: https://epmlogic.com

EPMLogicEPMLogic ConsultingWorkdayWorkday Adaptive PlanningWorkday Financials
Related Insights

More from the architecture desk.

Workday Adaptive Planning Workers: Modeled Sheet Accounts and Workforce Calculations
Architecture & Model Design

Workday Adaptive Planning Workers: Modeled Sheet Accounts and Workforce Calculations

Workforce planning starts with understanding the employees already working in the organization. Before we calculate future...

Read more
Workday Adaptive Planning Headcount Supply: Account Structure, Workforce Costs and Calculations
Architecture & Model Design

Workday Adaptive Planning Headcount Supply: Account Structure, Workforce Costs and Calculations

In workforce planning, we need to understand more than the number of employees in the organization....

Read more
Workday Adaptive Planning Headcount Planning: Cube Accounts, Formulas and Workforce Targets
Architecture & Model Design

Workday Adaptive Planning Headcount Planning: Cube Accounts, Formulas and Workforce Targets

Headcount planning is not only about entering the number of employees we need. We also need...

Read more