How To Fix /SHCM/EMPLOYEE_BL036 - Transaction for processing tags is already running

SAP Error Message - Details

• Message type: E = Error

• Message class: /SHCM/EMPLOYEE_BL -

• Message number: 036

• Message text: Transaction for processing tags is already running

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 /SHCM/EMPLOYEE_BL036 - Transaction for processing tags is already running ?

  The SAP error message /SHCM/EMPLOYEE_BL036 Transaction for processing tags is already running typically indicates that a background job or transaction related to processing employee tags is already in progress. This can happen in scenarios where multiple users or processes attempt to execute the same transaction simultaneously, leading to a lock situation.
  Cause:
  
  Concurrent Execution: Another user or process is already executing the same transaction, which causes a lock on the resources needed for the transaction.
  Long-Running Process: The previous transaction may be taking longer than expected, causing subsequent attempts to be blocked.
  System Configuration: There may be configuration settings that limit the number of concurrent processes for certain transactions.
  
  Solution:
  
  Wait and Retry: If the transaction is running, wait for it to complete and then try again. You can check the status of the transaction in the job overview (transaction SM37).
  Identify the Lock: Use transaction SM12 to check for locks. You can see which user or process is holding the lock and take appropriate action.
  Terminate the Process: If the transaction is stuck and not progressing, you may need to terminate it. This can be done through SM37 by selecting the job and choosing to cancel it.
  Check for Background Jobs: If the transaction is running as a background job, ensure that it is not scheduled to run multiple times concurrently.
  Review System Configuration: Consult with your SAP Basis team to review the configuration settings related to concurrent processing for this transaction.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM12: Lock Entries
  SM21: System Log
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review the documentation for the specific module or functionality you are working with to understand any limitations or best practices regarding concurrent processing.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.