How To Fix CRM_ISU_CONSUM135 - Point of delivery is currently blocked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_ISU_CONSUM - IS-U Profile: Error Messages

• Message number: 135

• Message text: Point of delivery is currently blocked by another user

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_ISU_CONSUM135 - Point of delivery is currently blocked by another user ?

  The SAP error message CRM_ISU_CONSUM135 indicates that a point of delivery (POD) is currently blocked by another user. This typically occurs in the context of SAP IS-U (Industry Solution for Utilities) when multiple users attempt to access or modify the same point of delivery simultaneously.
  Cause:
  
  Concurrent Access: Another user is currently editing or processing the same point of delivery, which locks the record to prevent data inconsistencies.
  Session Timeout: A previous session may not have been properly closed, leaving the POD in a locked state.
  System Configuration: Certain configurations in the SAP system may lead to locking issues, especially if the locking mechanism is not properly set up.
  
  Solution:
  
  Wait and Retry: If another user is working on the POD, wait for them to finish and then try again.
  Identify the Lock: Use transaction code SM12 to check for locks on the point of delivery. You can see which user is holding the lock and the details of the lock.
  Release the Lock: If you have the necessary authorizations, you can manually release the lock in transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on the POD.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check if any jobs are running that might be affecting the POD.
  Session Management: Ensure that all sessions are properly closed after use to avoid leaving locks behind.
  Contact Support: If the issue persists and you cannot identify the cause, it may be necessary to contact your SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view and manage locks), SM21 (to check system logs), and ST22 (to check for dumps) for troubleshooting.
  User Training: Ensure that users are trained on proper session management and the implications of concurrent access to shared resources.
  System Configuration: Review the system configuration related to locking mechanisms to ensure they are set up correctly to minimize conflicts.
  
  By following these steps, you should be able to resolve the CRM_ISU_CONSUM135 error and understand the underlying issues related to point of delivery locking in SAP IS-U.