Skip to Content
author's profile photo Former Member
Former Member

Infocube Post Update due to price change

Dear Experts,

We have a Infocube contains the following Data.

0Material (Key) 0Plant(Key) 0Calmonth(Key) Material-Average Invoice Price

32009 313 01.2016 1,3

32009 313 02.2016 1,4

The Material Invoice Price is caculated ( sum(monthly Amount) / sum(monthly Quantity) )in end routine though abap look up based on the data of another DSO (invoice document level DSO) which contrains the following data.

Invoice Doc.Nr.(Key) Invoice Doc. Item(Key) Posting Date(Key) Material Invoice Amount Invoice Quantity

4150002938 10 01.01.2016 32009 13 10

4190000293 20 03.02.2016 32009 14 10

But we have noticed that the Invoice Price in the look up DSO can change after some times. For exsample.

In invoice document Level DSO we have a new record in term of Material 32009 after look up the invoice Price in Infocube .

4150002939 10 32009 10 10 15.01.2016

So, the Material (32009) invoice Price at 01.2016 is not 1,3 any more but (10+13)/(10+10)= 1.15

I would like to know how I can change the old invoice Price in Infocube automated wenn we receive new invoice document in Terms of a old date.

Add comment
10|10000 characters needed characters exceeded

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 16, 2017 at 07:10 PM


    I will assume the posting date is part of the DSO key.

    If your level of detail is what you describe (no calday or week or invoice) the delta should manage the 1.15 into that material. But the the DTP it should be better if you use the semantic key for Plant, Material to guarantee the combination is in the same package.


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Ricardo,

      zwischen the invoice DSO and the Infocube there is no DTP. we use look up to caculate the monthly invoice Price and load to Infocube.

  • Posted on Feb 17, 2017 at 11:02 AM

    As a general rules, you'd better not do any calculation on key figure when filling a cube. This will generally generates some delta issue which I'm pretty sure will occur in your case.

    As a general rules too, this kind of calculation should be handled on the query side. Once you have stored the right quantity and amount, this is quite a straight forward calculation. If you can't do this for any reason, you will have to handle this calculation on a lower DSO layer of your data flow (and with the right keys).



    Add comment
    10|10000 characters needed characters exceeded