So here is a scenario for you… Say you have a plan type that pulls half of its data from another plan type. However, depending on which Scenario you choose, the data is either pulled via @XREF or loaded via a text file. How do you do this when Planning will make the member a dynamic calc member in the target cube?
The key item to use is the UDA HSP_NOLINK. This UDA tells Planning to not assign an @XREF in Essbase when the appliation is deployed.
In Workspace, add the UDAs “HSP_NOLINK” and “HSP_UDF” (tells Planning to not overwrite a member formula in Essbase) to the member(s) you would like the data to be dependent on the Scenario (usually an Account member…where the @XREFs are in the Essbase database). Deploy the application.
In Essbase, you see that the member is now a stored member without an @XREF, versus a Dynamic Calc member. Here, you can create a member formula. If we wanted to use an @XREF for Forecast data to the other plan type and have Actuals data loaded, we can.
Voila. You can call this member in a calc script to be run and it will pull Forecast data while leaving Actuals data alone.