Forum Discussion
Forecast V Actual Comparison Table
Hi Community,
I was looking for the best practice when deciding how to report on Actuals (from an accounting system exported into Excel) and Forecasts (written in excel spreadsheet system).
I have the data in PBI with the same fields in both tables (FORECASTPF and ACTUALPF) except obviously, one with actual $ values and one with forecasts $ values.
I understand creating a calculated table is the best way to join this information for reporting and calculating variances.
Can anyone, advise me of the required steps so i can easily work out the variances for different accounts, jobs and/or periods?
I was able to create a measure in my actuals table to calculate the forecast less actuals as shown below:
1. But is there a better way to do this and create a single table for reporting on both Fact tables?
2. How do I link the Account Numbers, Names, Cashflow Group and Job number between to two? I am not sure how i should join these too tables to create one for analysis and reporting....?
3. Should i create new tables to hold the account numbers, names, jobs etc? to uniform the selection of these criteria?
Here is my table data so far.
Table Structures
Thanks again in advance for your help!
11 Replies
- AnonymousNot applicable
It's a potentially big topic. These links might help:
https://www.sqlbi.com/articles/data-import-best-practices-in-power-bi/
https://www.powerpivotpro.com/2016/02/data-modeling-power-pivot-power-bi/
- v-caliao-msft
Microsoft Employee
Hi TheG,
In your scenario, since FORECASTPF table and ACTUALPF table almost have the same table structure, you needn't to use two tables. You can add then into one table with FORECAST and ACTUAL column. Select Combine > Merge Queries from the Home tab on the ribbon.
Regards,
Charlie Liao
- TheG
Advocate I
Thanks v-caliao-msft
When i merge i dont get the complete matches probably as some account numbers are not in both tables...i guess i need to rework the table layout and split account numbers out, jobs, account names etc..
- AnonymousNot applicable
As noted above and based on the sample data screenshot, merging Actuals and Forecast could be problematic - you have multiple Actual records for July 2014, but only 1 Forecast record that I can see for that month.
- AnonymousNot applicable
In some cases, you might prefer to keep them separate, at least as staging tables - e.g. update scenarios where you're adding new Actuals each month, checking in case Actuals for a new Account Number or Job Number have been added but no Forecast exists for it etc.