Frequency of Live Cache consistency check

[former_member188806]

Hi,

I'd like to know with what frequency should the Live Cache consistency check (/SAPAPO/OM17) be run on the production system..

Also is it mandatory that the user's & queues need to be locked while we run this check.

Thanks in advance.

Saba.

[Former Member]

here is a straight copy from the SAP note 425825

Internal consistency check - transaction /SAPAPO/OM17

Internal consistency refers to the consistency between the liveCache data and the APO database.

Inconsistencies may occur if the APO database data or the liveCache data can no longer be completely restored due to system crashes and inappropriate backup strategies.Since there is currently no logging for Demand Planning data, inconsistencies can still occur in this area following a recovery.To check the external consistency between the APO database and the liveCache and to set it up again, if necessary, use transaction /SAPAPO/OM17.

The following data is checked in particular:

Pegging areas, stocks, campaigns and planning versions are checked.

Master data:This data is saved redundantly in the APO database and in the liveCache, this means that data which is only on the APO DB, can be generated in the liveCache.If data still only exists in the liveCache, you can select this for deletion.

No resources are checked.The 'Resources' option is provided in older versions of the /SAPAPO/OM17 report, but you should avoid using this option as the results are inadequate.The results are not satisfactory.

It makes sense not to have activities affecting the DB or LC happening when checking for inconosistencies and this is something common among other non SAP systems as well. A lot of transactions give you block options when checking consistency

[samir_ali]

Hi Saba,

Transaction /SAPAPO/OM17 is the main tool for an overall internal consistency between liveCache and APO-DB. SAP recommends that you perform consistency checks during a posting-free period of time.

It is recommended to execute the program in background. After running the report in background it is possible to use the functionality “Evaluate Last Background Job”.

In principle, a check should be carried out in the following

situations:

•If a recovery is incomplete after a system crash

•If you suspect inconsistencies

For some objects, it is worthwhile to schedule the liveCache consistency check regularly.

Depending on the scale of the data to be analyzed, the liveCache consistency check

can have an effect on performance. See the relevant notes for information.

For more information, see the section on the liveCache consistency check related to objects.

Depending on the object that you want to check, you have to meet the following prerequisites:

•Ensure that no processes are active in the system during the check

•Check other dependent objects, if necessary, before executing the liveCache consistency

check

Preparation

1. Before you execute the liveCache consistency check, ensure that no processes are active in

the system. You can use the following functions for this:

Lock User

Overview of Active Users, Tasks and Jobs

Stop CIF Queue

Consistency Check

After you have made all the necessary preparations, start the liveCache consistency check:

1. First, the system checks all selected planning versions for consistency. Depending on the

object, the system then checks the data belonging to the object starting from the SAP APO

database, SAP liveCache or in both directions.

2. You receive a result overview. In this, the system shows all inconsistencies found, sorted

according to the associated objects. There is a tab page for each object that was selected to

be checked.

3. You can choose to correct all inconsistencies or just selected inconsistencies.

Before actually making the correction, the system makes another consistency check for the

object to ensure that the error still exists.

4. If necessary, you post-process the correction.

Post-Processing

After the liveCache consistency check, you re-release the system by:

Unlocking users

Restarting CIF queues

Release Jobs Again

In the CIF Queue Overview, you can check whether all CIF queues are active.

[Former Member]

Hi,

It is necessary to lock users and CIF Q..

Frequency : Once in a Month and after Livecache crash