This content has been marked as final. Show 3 replies
I can think of a few solutions.
1. Make a dimension for Source have in it the old soruce namd and new soruce name. The parent "Source" can be dynamic. That way you can get old sorce, new source or combined.
2. Have a scenario with Old_Source name actuals, New_Source Name actuals and a parent of Actuals.
3. prefix the account members with somethign to distinguixh them as new or old, then create parents that combine them In your example EPR1_1100 and New_1100 roll up to 1100.
I can think of more ways, but this should get you started
What about exporting data, getting it into a database (or other tool), changing accounts in the exported data to new accounts, import back in to Essbase. If you wanted to differentiate it as being from the old system you could introduce some sort of 'source' member in one of the dimensions or perhaps it is sufficient to know that data prior to (including?) 2013 Jan is from the old system.
This might sound more complex/daunting initially but the end result would be a lot simpler assuming it makes sense to do so.
Thanks for the reply
Old and new account numbers are not the same
EG: old Account Number is 100 and new account number is 1100 so last 3 years worth of data is stored in acct 100 (From 2010 Jan to 2013 Jan) From Feb 2013 data is stored in new account number 1100 and going forward this account would be used. But users want to track old data and new data in the same application. How can we report data with reference to two account numbers.