data uploading at the aggregated level

[Former Member]

Hi All,

In our APO-DP project. The final forecast generated by the engine is being sent to a legacy system and the confirmed forecast is coming at an aggregated level not at the detailed level

I have the following confirmation to make in this regard:

1.Can we store the aggregated confirmed forecast data when we don't have the logic for desegregating the data at the detailed level. the disaggregated level which is the level at which we have the CVC in the InfoCube. I am of the understanding that to store the data in the InfoCube we have to first desegregate the data to the detailed so that the data can go with the right CVC.

2. Assuming that the data can be stored at the aggregated level in the inbound infocube would this affect the loading of the data in the planning area and the planning book because we want it to be visible in the planning book for comparing the confirmed forecast with the final forecast.

Please give your suggestions on this .

[somnath_manna · Accepted solution]

Hi APO APO (interesting alias),

You better create a separate infocube with the characteristics at which you are getting aggregated data back from your legacy system. Please note aggregation/ disaggregation does not necessarily take place at the Infocube - better to manage it at the Planning Area.

So if you have the aggregated data in the infocube - while loading to planning area you can manage the disaggregation (assuming you have the diasggregation logic decided).

You may setup your Confirmed Forecast keyfigure to disaggregate based on another keyfigure which in turn you populate using some macro or custom function. Then if you load the data from cube to the Confirmed Forecast keyfigure in the planning area at the aggregated level - the data will automatically disaggregate based on the other disaggregation keyfigure.

Thanks,

Somnath

[Former Member]

Hi

Looks like your requirement is basically to compare confirmed forecast (coming in from legacy and is aggregated) and final forecast (generated in APO and is at a detailed level)... and you want to do it at the same level (ie aggregated)

since you dont have a logic for disaggregation does it really matter what you have

in the detailed view for confirmed forecast??

You can store it at the aggregated level in an infocube. In other words you dont have to have all the charagterisitcs associated (through the POS) to your planning area

You then copy this aggregated forecast into your planinng area. The disaggregation happens in the planning area based on the disaggregation settings. Just dont look at the disaggregated view

Use a separate planning book for the comparison (still based on the same planning area). just make sure the planning book does not have the "detailed" characteristics. Dont give the confirmed forecast KF in any other book

this way you wont even get to see the detailed level of the confirmed forecast. But you get to see the aggregated statisticAl forecast alongside