Standard APO jobs not doing their job
Sometimes, you come across a situation where the version copy is not happening or where the data from the info cube is not coming to the planning area. The sad fact to add to this problem is that these are the standard programs [/SAPAPO/RTSCOPY for version copy, /SAPAPO/RTSINPUT_CUBE for pulling the data from an info cube to a planning area). It becomes a huge task of debugging the entire standard code as to why the behavior is seen this way…
While the fact will be that someone having the access to the system would have executed the program /SAPAPO/OM_NON_LC_RELEVANT_CLT, and made the client you are working on as not relevant for live cache. This is a simple program where you simply need to put your client id, select one option and execute.
The below screen is the output of the program and you can see as well which are the clients which are already made non-relevant to LC. Your client should be one among them!
All you need to do is to select ‘Relevant to live cache’ option, put your client id and execute.