Hi,
Have you followed the recommended precedures for compression and loading according to the HowTo document for Inventory management in BW? If you haven't got this document - give me your email adress - and I send it to you.
Incorrect historical values in stock cube can of course have many possible reasons but one likely reason is some missing material movement documents:
The stock cube 0IC_C03 doesn't save snapshots instead it calculates historical stocks based on current stock for particulat characteristic combination and derives historic stock by "calculating backwards" from current stock based on historical material movements given by 2LIS_03_BF extractor. This means that if you miss one single movement document then this will affect the historical values not only for that month but also for all previous months.
To find the problem track down a single material/plant combination that have incorrect historical stock. Trace the data in the cube by first looking at current stock (select recordtype = 1 in LISTCUBE transaction). Then look at movements with recordtype = 0 for the particular combination of characteristics back to the point in which the data is wrong. Perform the backwards calculation manually (this will be hard if you have many movements for the particular characteristic combination). You can compare this directly in R/3 by looking in table MSEG (material movements) and MBEW (for current total of valuated stock at material/plant level). This will give you the details on which document(s) that are missing and when you know that then you can start to look for the reason. Possible reasons for missing documents are:
The stock initialization might have been done improperly - if you don't perform the initialization during a posting free time in the system these problems can occur. Moreover if you use Queued delta mechanism in R/3 (look at tc LBWE) and forget to stop the delta queue job during initialization this might also lead to some missing documents.
Other things to look out for is the stockrelev flag set in the 2LIS_03_BF extractor this flag is set to 1 if the movement is stock relevant and 2 o.w. Only lines with stockrelev = 1 will be updated in the cube. Due to configuration miss on R/3 side you might miss some documents if they are incorrectly flagged with stockrelev 2. Look in the PSA for BF extractor to determine the value of this flag for a particular material movement document.
If you use an ODS layer before updating to stock cube this might also be a problem if it is setup incorrectly - in that case you could lose documents by postings overwriting each other...
Finally look into OSS - there are several notes on the stock cube and related objects.
Regards,
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.