Partition areas question

Question

I have two cubes, one of which is connected to the accounts system and contains the "actual" financial data, the other is a forecasting cube and contains, well, forecasts.I want to link the two via a replicated partition so that actuals can be directly accessed in the Forecasts cube without having to do data export/loads, etc.All the members from all the dimensions in the Actuals cube exist in the Forecasts cube, but they are not neatly divided up. We are a magazine publisher, and each issue is a separate activity, so the activities dimension in the Actuals cube looks like this:Magazine X...........Issue 1...........Issue 2while the same bit of the Forecasts cube looks like this:Magazine X...........Issue 1...........Issue 2...........Issue 3...........Issue 4issues 3 and 4 not having been published yet, no have no actuals data so don't exist in the Actuals cube.Defining the area I want to replicate is easy in the Actuals cube, but I can't see how to define the matching area in the Forecasts cube because of the extra members?Any ideas for a way forward gratefully accepted![email protected]

Answer 1

In my experience, mismatched replicated partitions work fine. It just writes a message to the log file if a match isn't found, (so don't have too many) but the ones that do match tranfer their data fine. Take for example, one cube has one year and the other has seven years. mapping y2003 to @children(years), will not validate, but the transfer of data will always work.