how to verify data integrity between Live cache and The underlying Infocube

[AA3]

we are getting values doubled up for all the Key figures in planning book when compared to the underlying infocube from which they are loaded.

Is there a way to check if the values between CUBE and PLANNING area are consistent meaning can i directly read the key figs from the LIVE CACHE using browser /sapapo/OM19 or is there any other way to confirm this

[Former Member]

Hi,

If you are using TSCUBE transaction for data loading, then you may be selected "Add Data" button under KeyFigure assignment section. Please check this.

Thanks

[AA3]

no the add ky fig check is not enabled in our case.

[AA3]

in normal case data in planning book should be same as in infocube from which the load happened. in our case the key fig values show doubled up values when compared to the cube. Can any one point out reasons why this can happen

1) key figurs do not have the adding up check box

[Former Member]

Check with your BI consultant, ask them to either delete or inactivate the previous loads(REQUESTS from the infocube), only the latest REQUEST should be active.

[AA3]

you mean that all the previous day requests need to be deleted and then the today's load should happen.

because in our case we have so many requests available from past several months available in the cube and each day we run the INPUT program from CUBE to Planning area. Our Variant for the INPUT program from CUBE to PA has selection date defined for past exactly one year.

Do you think any setting need to be made in grouping conditions of the INPUT program ?

[Former Member]

Run RTSINPUT and update the LC key figures from the cube using a key figure that has all zeros. Do this just as a means to initialize the value in LC. Then do a data access on the cube via LISTCUBE and confirm that you only get back one package request that is active in the cube. If that all looks good, then run RTSINPUT and load the data from IC to LC and it should be fine.

Another sympton that can happen is that you have missed a realignment such that a product exists in the MPOS with duplicate records, such that when you use a selection profile that doesn't consider the duplicated characteristic that you are getting the values doubled. Subtle things like "01" being resent as "1" can cause this to happen, so make sure to check your CVC data via MC62.

[AA3]

and confirm that you only get back one package request that is active in the cube.

Does it mean that we will need to delete the previous day request from the CUBE each day , so that we see only 1 active request each day.

What is Realignment and how can that be configured ?

[AA3]

we are loading historical data with low and high selections for past one year. I dont understand why we will need to delete the requests.

(input program)

FILE source system -

---

> CUBE -

---

> planning area -

---

> Planning book

FILE source system--

---

> DSO---> above cube (deltas)