APO : consistency check frequency and use

[Former Member]

Hi,

in our system APO, we have dumps during Consistency check because of interactive users connection :

SQL error in the database when accessing a table.

Database error text........: "ORA-00060: deadlock detected while waiting for

  resource"

Internal call code.........: "[RSQL/178//SAPAPO/MATLANE ]"

First we changed parameter on each table /SAPAPO to have more concurrent access ( found in an oss note).

The consistency check are planned in each process chains, not in dedicated job.

When the dump occur, it cancelled the process chain.

What's the best practice about consistency check for SNP ? PPDS ?

Do we have to lock users during these treatments ?

Is it normal that if we have concurrent access in modification in the same time, the 2 requests are cancelled ?

I mean, we've got 2 dumps :

- one for the user in dialog

- one for the PC

in my opinion, the first in modification has a lock and could continue to work...It's not the case here.

Thanks for your feedback.

Regards

[Former Member]

Hi,

For SNP/PPDS we should run the consistency check job for PA (expecially when we have some time series key figures) and OM17 job on daily basis before we start the planning runs.

Regards,

Anil

[Former Member]

Hi Matthieu,

We need to do consistency check on a regular basis. The frequency of this depends on the frequency of planning cycle run and frequency. Also we need to do consistency check whenever we create new master data either through CIF or manual creation of CVCs. It is recommended to lock the users during this period. But if during a manual master data creation if we need to do consistency check we need to first of all find out the master data where inconsistency is there. This we can do by not checking the repair option. Once we found the set of master data having issues we can run fix it and this will not impact whole set of master data.

Regards,

Mukesh Pandey