Skip to Content

Inventory Cube 0IC_C03 - marker update for every material movements?

Hello experts,

we have problems with our query performance in SAP BW 7.50 respective Cube 0IC_C03 (inventory cube). We are compressing the cube after every request with marker update. The quantities are correct though, it is just about performance.

I analysed the data more specifically and I realized, that there exists marker records (0RECORDTP = 1 and 0CALDAY = 31.13.9999) for every material movement! That’s not the way it´s supposed to be isn’t it?
I understood it like the markers are just set for the current inventory plus the material movements for calculating inventories from the past?

By the way the material movements exists in the cube as well (0RECORDTP = 0 and 0CALDAY = date of material movement) what seems correct to me.

Also the initial load is correct which set the inventory for every material and plant and stock for the date of the initial load (also as marker record with 0RECORDTP = 1 and 0CALDAY = 31.13.9999). I thought this records would be updated after every compression (as long as marker update is activated --> no tick) or am I wrong?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Nov 08, 2018 at 04:31 AM

    Hi Arnold,

    I think the note 1548125 can answer most of your questions. You may see the example in it to understand the logic of inventory cube from both compression and report perspective.

    Best Regards,

    Sheldon

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 09, 2018 at 12:34 PM

    Hi Sheldon,

    thanks a lot for your advice! :)

    I read note 1548125 already several times.

    Right now I´m pretty sure the marker update is not working correctly in cube 0IC_C03 in our System. The records of the initial load have never been updated instead every material movement creates a new marker and regarding to note 1548125 (and the SAP help sites) that is wrong. And the marker update is activated (no tick).

    What I don´t know is why that is happening. I didn´t find any hint about why every material movement creates its own marker record respectively why the records of the initial load have never been updated.

    Has anyone ever heard about that problem already?

    Thanks in advance for any help !

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 14, 2018 at 07:06 AM

    Hello Arnold,

    While writing the initial stock balances into the fact table, BW converts the date value to 9999-12-31. So for every entry you will be able to see the record for 31/12/9999 for recordtp 1.

    https://assets.cdn.sap.com/sapcom/docs/2016/02/7656180b-617c-0010-82c7-eda71af511fa.pdf

    The above link will help you to understand the marker concepts in BW 7.5.

    Regards

    Gajesh

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 07 at 03:06 PM

    Hello again,

    thanks everyone for your help :)

    Finally we found the problem: because the attribute “material movement” was added to the cube some when, every material movement created its own marker record. That’s the usual behaviour of an inventory cube: one new marker record for every different combination of attributes.

    We solved this issue by creating aggregates.

    Regards

    Arnold

    Add comment
    10|10000 characters needed characters exceeded