Message /SAPAPO/SDP_PAR023: "Some CVCs cannot be processed in block..."

[geir_kronkvist1]

Hi,

We are using SAP SCM release 5.1, the component Demand Planning. We are running macros in background jobs, e.g. a macro that populates a key figure by summarizing other key figures etc. We are using parallel processing, configured based on recommendation from SAP. When the number of CVCs to be processed by the macros becomes very high (we are processing ~300.000 CVCs at the moment), we get the following message in the job log in SM37:

"Some CVCs cannot be processed in block 2 ", message number /SAPAPO/SDP_PAR023. Obviously the block number varies, and in our case we have had the above message for up to 19 blocks. Users have spotted CVC's that were not updated by the background job, but we don't have a specific list of the CVCs that were not processed.

OSS notes mentioning this behaviour:

Note 1282811 - Error processing 1 CVC, terminates the Parallel Profile

Note 1501424 - DP Job with parallel processing - job status message

Note 1494099 - DP Job with parallel processing - job status

The question below is only to those who have encountered the same message in a DP background job:

Did you find a log of the CVCs that were not processed, and what did you do to overcome the problem?

Thanks in advance!

Kind regards,

Geir Kronkvist

[rico_frenzel · Accepted solution]

Hi,

this looks like a possible locking issue. Normally you will find more information about what happened in the spool for the corresponding job. What is it saying?

Best regards

Rico Frenzel

[geir_kronkvist1 · Accepted solution]

Hi Rico,

Thanks for your reply! The spool consists of 23.145 pages so I looked for the word "Lock" using the "Find in request" in the "Spool request" menu. The searched found two entries where there was a message stating that a CVC was locked. It must be noted that no users are logged on while our background job is running, and there are no other processes (background or dialog) running in parallel. When checking transaction SM12 prior to running the job, there are no locks in the system.

Our job schedule consists of a nightly process chain transferring data from BI to liveCache, and a monthly job that prepares historical data and calculates the forecast. We are now running the monthly job.

Is it possible that the parallel processing may cause the locking by itself?

Kind regards,

Geir Kronkvist

[rico_frenzel · Accepted solution]

Hi Geir,

it MIGHT be that paralle processing causes the locking issues, but only in case you use aggregates.

small example: Le'ts assume you have an aggregate on Location. The batch job will be executed on aggregationlevel = Product.

So it can be that 2 different products exist in one location. And they will be possibly processed in 2 different parallel tasks. As the aggregate needs to be updated as well during processing, only one parallel task is able to update the aggregate (because both need to lock the one common location).

If this is the case you can enable a reprocessing of the CVC's. For this there are 2 user parameters possible:

/SAPAPO/MAP_REPROCES (check note for details 1311785)

/SAPAPO/MAP_WAIT_SEC (note 1328482)

Best regards

Rico Frenzel