You execute more than one BPC Data Manager (DM) package concurrently / back to back.
Each DM package starts a job on the server but the job log in transaction code SM37 for the subsequent packages show that after the job starts it remains inactive until the first job completes.
Your BW version is less than the versions listed in SAP Note 2236636 or have applied SAP Note 2193723.
You observe longer DM run times / poor performance / slow performance in your BPC DM packages and see that runtimes are higher if there are several packages running in parallel or if you run the parallel logic (RUNLOGIC_PH) BADI.
You see locks held on table RSPCENQUEUE when DM package is running.
- SAP Business Planning and Consolidation 10.1, version for NetWeaver (standard model)
- SAP Business Planning and Consolidation 10.0, version for NetWeaver
RSPCSYNCLOCK RSPCENQUEUE wait sleep, Standard BPC copy jobs are running for very long durations impacting the month end schedule sleep , KBA , features and functionality , troubleshooting , rspcsynclock rspcenqueue , dm package performance , EPM-BPC-NW , NetWeaver Version , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.