The aim of this issue is get better the query executions in the BCS scenario.
The close periods are saved into a reporting infocube.
We don´t get the infopackage send only data of close periods to the reporting infocube, the request transfer all the data though the period hasn't been closed.
We have followed all the parametrizations steps.
Have anybody implement this scenario? Have you got the same problem?
It is my understanding that regardless of the data in the reporting cube, only the data for closed period are read into the query results with data for the open periods coming from the virtual cube.
You are right Dan. So if you load all data from totals cube via virtual cube to basic cube, you will have double figures for the open period. With the delta scenario the request id is the differentiator. Were the open request from the totals cube is read and the rest is read from the basic cube. With BW load you can't load an open request, therefore no restriction is needed in that scenario.
It is my understanding that as long as the closed periods are maintained in the BCS workbench and the multiprovider settings are correct, the reports will not double count. Only open period data is from virtual cube and only closed periods data is from reporting (datamart) cube. Periods cannot be both open and closed.
That's not correct. The virtual cube will show only open periods, but everything in the basic cube will be shown. Restriction on periods shown is not in multicube.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.