Why does my Structured Planning template open without displaying data (showing the message “Reference and History data downloaded successfully. Click the Display Data button to populate the template”), and how can I make it automatically display and retain data when reopening?
What it means
The template has Enable Expedited Loading turned on.
Expedited Loading is designed for very large templates where data rendering takes time.
With this option:
Data input lines are immediately available, so you can start entering data while reference/history data loads in the background.
You cannot save until the load is complete.
Once the load finishes, you must click Display Data to populate the template.
This feature saves time and improves performance, allowing users to continue planning without waiting for the full template to load.
How to Resolve:
Go to Maintenance > Templates Setup.
Select a scenario and the Template.
Click the Edit button on the header.
in the General Information tab, locate the option Enable Expedited Loading.
Uncheck this option.
Save the template.
Reopen the template (either from Planning Control Panel or Template Setup) — it should now auto-populate data immediately upon opening, and data will persist when saved/closed.
Note: Expedited Loading is available only for Global Template Single Copy and Allocation template types.
Why do I see: “Inserting line(s) is not possible when filters are applied. Remove filters to insert lines”?
What it means
This happens because the Show Data Filter option is enabled in the Grid during template setup.
When filters are active, Planful blocks line insertions to prevent data misalignment.
How to resolve
Go to the Grid menu in your template.
Select Hide Data Filter.
Once the filter is hidden, you can insert lines as needed.
Why does the template show this error message: “Opex' Template definition has been updated by the application administrator. To see the latest changes, open the template in 'Input' mode”?
What it means
This error appears because the version of the template you are trying to open is out of sync with the latest saved definition.
Common causes include:
An administrator modified the template setup (added/removed lines, changed mappings, or updated views).
A snapshot or restore was applied to the template.
The template’s definition was refreshed after workflow changes.
How to resolve
To access the latest version:
Go to Structured Planning > Planning Control Panel.
Select the Scenario and Budget Entity.
Open the Opex template in Input mode (not View mode).
The system will refresh and display the updated definition.
Save and continue working with the updated version.
Best Practice
Administrators should notify budget managers or end users before making structural changes to templates.
If frequent updates are required, consider using the Snapshot feature before changes, so data can be restored if needed.
Always open templates in Input mode after significant updates to ensure you are working with the latest definition.
Use Views in templates for customized layouts instead of structural edits where possible, reducing disruption to end users.
Why isn’t my capital budgeting showing in Forecast?
In a Planful report pulling data from my accounting software, how can I check which accounts are mapped to which group accounts?
For planful report that is drawing data from an accounting software. How can I check which accounts are mapped to which group accounts in the planful report.
What it Means
Planful uses Translations Setup to map source accounts from your accounting system to Planful accounts and groups.
If your report shows accounts under unexpected groups, the mapping in Translations Setup determines where they are assigned.
How to Resolve
Navigate to Maintenance > Data Integration > Translations Setup. To learn more about Translations Setup, click here.
Open the translation rule that applies to your accounting software feed.
Review how each Source GL Account is mapped to the corresponding Target Planful Account or Group.
Confirm mappings are correct. If you need adjustments, update the translations and reprocess the data load.
Re-run your report to verify the corrected mappings are reflected.
Note: Using Translations Setup ensures that external GL accounts align with Planful’s internal reporting hierarchy.
Why are my planned depreciation numbers not moving from my template to my cost centre report?
What it Means
Depreciation in Planful is driven by formulas set up in templates.
If depreciation amounts are not appearing in your cost center report, it usually means the depreciation formulas are missing, incomplete, or not mapped correctly in the template setup.
Reports will only pull calculated values that are generated by these formulas.
How to Resolve
Go to Template Setup for the related template.
Check the formula lines that calculate depreciation expense:
Ensure the formula references the correct accounts (e.g., asset cost, useful life, residual value).
Verify that the destination mapping points to the correct cost center/account combination.
Run the Validation Report for the template to identify any formula or mapping issues.
Re-save the template and refresh the cost center report.
If still missing, confirm that the Process Reporting Area has been run so updated template data is available to reports.
Note: Depreciation in reports will only flow correctly when formulas are set up and mapped properly in the planning template.
Why doesn't making changes to my depreciation template trigger the scenario process?
why aren't my planned depreciation figures not flowing from the template to the scenario
What it means
Edits to templates (such as depreciation or other asset formulas) are not treated as workflow events. Scenario process steps like Forward, Approve, or Final Approve only trigger when actions are taken on budget entities, not when template logic is changed.
How to fix
After updating the depreciation template, reprocess it using the Simulation Engine or by manually opening and saving the template. This ensures your changes are applied and reflected in reports, without requiring a scenario process step. To learn more about the Simulation Engine, click here.
Why do I see error message that says number exceeds allowed size (12,6) when setting up a quarterly spread?
Common Causes in a Quarterly Spread Setup
Large total amounts being spread — e.g., a large annual total being spread quarterly.
Formula or multiplier error — a calculation producing a very large or small (negative/decimal) value.
Data type mismatch — sometimes uploading or copying values from Excel introduces text or formatting issues.
Incorrect driver setup — a driver (like headcount, rates, etc.) might be multiplying unexpectedly large numbers.
How to Fix It
Check your input values:
Make sure the total or quarterly value doesn’t exceed 999,999.999999.
If it’s an annual total, break it down or reduce precision.
Verify drivers and formulas:
If you’re using a calculated spread, confirm each component’s output.
Format numbers correctly:
Avoid commas or special characters.
If you imported from Excel, ensure the column is numeric (not text).
If you’re spreading via a template or model:
Look for fields configured with DECIMAL(12,6) in the model or data load definition — that’s the column imposing the restriction.
Why is the annual column in my template not summing the monthly values?
What causes this?
When an annual column in a template does not sum the monthly periods, it usually means the annual value is not configured as a rollup of the monthly values. This can occur due to template setup, calculation logic, or scenario configuration.
Common causes include:
The annual column is set up as an input field rather than a calculated total
The template line uses a calculation or spread method that does not aggregate monthly data
One or more monthly periods are excluded, locked, or outside the scenario’s time range
The line type is non-additive or calculated, so it does not sum months
The scenario does not include all periods for the year
How to fix it:
Verify that the annual column is intended to be a total/rollup, not an input
Confirm all relevant monthly periods are included and open in the scenario
Review the template line type and calculation logic
Recalculate or refresh the template if required
Once the template and sce
Why did my Report Collection fail with the error “Index was out of range”?
What causes this?
This error occurs when Planful is unable to process one or more reports within a Report Collection due to a mismatch between the report structure and the data being evaluated. It means the system attempted to reference data or report elements that were not available or aligned as expected.
Common causes include:
Changes made to a report (columns, rows, column sets, or filters) after it was added to the Report Collection
Reports referencing dimension members, periods, or scenarios that no longer exist or are not available
Inconsistent report configurations within the same Report Collection
Very large or complex reports that exceed processing limits
Temporary system or processing issues
How to fix it:
Open and run each report in the Report Collection individually to confirm it runs successfully
Verify that all reports use valid and consistent dimensions, periods, and scenarios
Re-save the affected reports and the Report Collection
Reduce report complexity or remove problematic reports from the collection
Retry running the Report Collection after making corrections