cancel
Showing results for 
Search instead for 
Did you mean: 

What is Live Cache Anchor

Former Member
0 Kudos

Hi ,

Some times we see errors like "No Live Cache Anchor Found". Can somebody tell me in detail that what is a live cache anchor and why this inconsistency occurs. Is there a link containing detailed documentation?

Best Regards,

Chandan Dubey

Accepted Solutions (1)

Accepted Solutions (1)

tibor_nagy
Contributor
0 Kudos

Dear Chandan,

This error message "No Live Cache Anchor Found" states that for one or even for several characteristics combinations (see Transaction /SAPAPO/MC62) a so-called LiveCache anchor does not exist.In this case, a LiveCache anchor is a pointer to one or several time series in the LiveCache.

There is one LiveCache anchor per planning area, characteristics combination (planning object) and model (model belonging to the planning version, see transaction /SAPAPO/MVM). If for one planning area, time series objects were created for several versions with different models, that means several LiveCache anchors exist for the same planning area and for the same characteristics combination.If you created time series objects for several versions of the same model, that means one LiveCache anchor

points to several time series in the LiveCache.

If there is no LiveCache anchor for a planning area, a model and a characteristics combination, this also means that no respective time series exists in the LiveCache and thus, this characteristics combination cannot be used for the planning with this planning area for all versions of the model.If this state occured for a certain characteristics combination, the above-mentioned error message occurs if either exactly this characteristics combination is selected or if a selection contains this characteristics combination.

Possible causes and solutions:

- Time series objects have not yet been created for the selected version.

Solution: Create time series objects (see documentation)

- You are using a planning session with version assignment.For the version that was acutally selected, the time series objects were created, however, this is not the case for the assigned version.

Solution:Create time series objects for the assigned version.

- New characteristics combinations were created without the 'Create time series ob' option (see Transaction /SAPAPO/MC62).

Solution:Execute the report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC for the basis planning object structure of the planning area.This will create the corresponding LiveCache anchors and LiveCache time series for all planning areas that used these basis planning object structure and for all versions of these planning areas for which time series objects already exist.

If none of these possible solutions is successful, you can use report /SAPAPO/TS_LCM_CONS_CHECK to determine and correct the inconsistencies for a planning area ('Repair' option).

I hope this helps.

Regards,

Tibor

Answers (2)

Answers (2)

Former Member
0 Kudos

Oh your Live Cache isnot activated for this follow the Process...

1. Go to LC10 Transaction

2.Choose the Database cONNECTION - LCA

3.Click on Live Cache monitoring

4.if any error message shows Live Cache isnot installed---solution - Contact to BASIS and install

5.If ok ..Properties screen opens up

6.Click on Administration - Operating and double click

7.Click on start Live Cache -- Live Cache is on

8.Then Create Time Series for Planning area i n Admin Workbench - PA RIGT cLICK

9.aND CHECK THE cONSISTENCY

This will help u..

Regards,

Rajesh Patil

somnath_manna
Active Contributor
0 Kudos

Well it depends when u see the live Cache Anchor not found error message.

Typically it happens when u are trying to update data in a Time Series keyfigure.

in that case u need to reinitialise the Planning Area Time Series.

LiveCache is a blackbox (check under MaxDB for more documentation / explanation) which is essentially main memory (RAM) where almost all Transaction Data and some planning relevant Master Data is stored in APO. For DP the master data is CVC (Characteristic Value Combination) which is just a key. The actual data is stored in keyfigures against each CVC and time bucket.

So technically when u initialise the Time Series for the Planning Area for a given planning version space in RAM is reserved for each CVC, Keyfigure and Time Bucket (based on horizon and Storage Bucket profile) combination. you can consider this CVC - keyfigure - Time Bucket combination as the liveCache Anchor. Later on in Interactive Planning table data entered gets stored in this liveCache reserve.

If anyone has a better explanation would love to hear.

Thanks,

Somnath

Former Member
0 Kudos

Good explanation Somnath.... If anybody like to add something, they are welcome !!