We are attempting to leverage plan types for different portions of our P&L and I wanted to know how I can share data between plan types. Can anyone help explain how we can accomplish this? Also is the sharing "real time" or is it a process we need to execute to "push" the data between plan types?
Thanks in advance for your assistance
You define the source of the account (one PT) and make it available to others. It automatically gets XREF'd as a dynamic calc. Of course performance can fall right off a cliff if you have lots of these. I often will go through and make them all stored members and then force their valuation through a business rule.
Here's something I wrote long ago and really need to work into a full blog post:
Chop the Accounts
When I build a Planning application with more than one Plan Type, I like to create upper level Account parents that segregate by Plan Type. This makes security and dimension builds as straightforward as possible. Yes, this does require extra dynamic calcs in the target (really, its the master) Plan Type to pull the XREFd data from the source Plan Type(s), but I think its a small performance penalty to pay for clarity. I reserve the right to bin the above approach if it doesnt work for a particular application, dear client(s), so please dont consider the above set in stone.
Mythical application example -- Account
To do this, name and order the Accounts like the below to split security by Plan Type:
NB -- Wrkforce, the source of employee expenses, is ordered before target Income Plan Type so that there are no forward dynamic calcs.
The issue with shared members across PTs is that they can get REALLY mixed and cause a lot of noise in the hierarchies -- remember, what you see in Planning/EPMA isn't what really translates to Essbase but of course that's where everything happens. I like to segregate the shared members as much as possible hierarchically and then move data around as needed. I also try to keep the scope of XREF'd data as small as possible.