How To Fix 06735 - Source list for material & and plant & already being processed

SAP Error Message - Details

• Message type: E = Error

• Message class: 06 -

• Message number: 735

• Message text: Source list for material & and plant & already being processed

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 06735 - Source list for material & and plant & already being processed ?

  The SAP error message "06735: Source list for material & and plant & already being processed" typically occurs when there is an attempt to create or modify a source list entry for a material and plant combination that is already being processed in another session or transaction. This can happen in various scenarios, such as when multiple users are trying to update the same source list simultaneously.
  Cause:
  
  Concurrent Access: Another user or session is currently editing the source list for the same material and plant.
  Lock Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If a source list is locked by one user, other users will receive this error when trying to access it.
  Background Jobs: A background job might be processing the source list, causing it to be locked.
  
  Solution:
  
  Wait and Retry: If you encounter this error, wait for a few moments and then try to access the source list again. The lock may be released once the other user or process completes its task.
  Check Active Sessions: Use transaction code SM12 to check for any active locks on the source list. You can identify the user or session that is holding the lock.
  Contact the User: If you find that another user is holding the lock, you may want to contact them to see if they can complete their task or release the lock.
  Release Locks: If necessary and if you have the appropriate authorizations, you can manually delete the lock entries in SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still processing the data.
  Check Background Jobs: Use transaction code SM37 to check if there are any background jobs that might be processing the source list. If you find any, you may need to wait for them to complete or consult with your basis team.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM37: To monitor background jobs.
  
  
  Source List Maintenance: The source list can be maintained using transaction codes like ME01 (Create), ME02 (Change), and ME03 (Display).
  User Training: Ensure that users are trained on how to manage source lists and understand the implications of concurrent access.
  
  By following these steps, you should be able to resolve the error and continue working with the source list in SAP.