(Proactive notification) SAPLSENA consuming a lot of time in SM50 and delaying Planning Runs

Recently, I’ve seen quite a few incidents in which, after upgrade to SCM 7.02 or SCM 7.13, a Planning Run executed as a background job via /SAPAPO/CDPSB1 or report /SAPAPO/BACKGROUND_SCHEDULING takes a long time.

If you experience such an issue, execute transaction SM50 while the job is running and verify whether there are Update Tasks stuck for a long time on program SAPLSENA. If that is the case, notes below should be implemented, when applicable:

1998968 Update task hangs in program SAPLSENA

2025948 Long processing times spent by waiting for an enqueue

2107221 – Runtime error TIME_OUT in SAPLSBAL_DB_INTERNAL

When a Planning Run is executed, some planning logs have to be written in an Update Task using this program, which belongs to BC-SRV-BAL area. As the issue is not specific to PP/DS application, it’s quite easy to miss these basis correction notes, thus I’m creating this blog post to increase awareness of the solution.

Edit – also important is note below, which solves a program error where only one planning task is triggered at once, even though Parallel Processing flag has been set for the MRP heuristic (SAP_MRP_001 / SAP_MRP_002):

2047302 Tasks in parallel processing of MRP run are not used and remain blocked