I want to use Essbase 11.x to create a partition strategy that has several source BSO cubes (all with the same number of dimensions) partitioned to a single ASO target cube, which has the additional dimensions than the BSO source cubes. Is that possible?
Is this a transparent partition? Why is the ASO cube's dimensionality different? Does it contain its own "local" data in addition to the data you are sucking in from the BSO source cubes?
In any case, when you have extra dimensions in your target, you map from 'Void' in the source to a selected member in the target dimension. It's explained in the DBAG section titled 'Mapping Data Cubes with Extra Dimensions': http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dotprtbd.html#dotprtbd1082203
Thanks. The primary reason for the difference in dimensionality between the source BSO and the target ASO cube is that the BSO cubes are from two separate Plan Types in Planning, one plan type is primarily financial data and the other plan type is primarily labor/headcount related data. So we have multiple BSO applications, each with two BSO cubes of different dimensionalities that all need to map to the single large ASO cube. Thanks
Gotcha. The only reason I ask if the ASO cube also contains its "own" data is that there is an issue with "local" data not being displayed if the cube is also the target of a transparent partition. If the ASO cube has no data of its own you won't have that problem.
Just for example, see http://www.network54.com/Forum/58296/thread/1314903542/ASO+transparent+partitioning..