How To Fix >U136 - Payment lot transfer is running; generation not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: >U -

• Message number: 136

• Message text: Payment lot transfer is running; generation not possible

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 >U136 - Payment lot transfer is running; generation not possible ?

  The SAP error message "U136 Payment lot transfer is running; generation not possible" typically occurs in the context of payment processing within the SAP system. This error indicates that a payment lot transfer is currently in progress, which prevents the generation of new payment lots or the execution of certain payment-related functions.
  Cause:
  
  Concurrent Processing: The error usually arises when a payment lot transfer is already being processed in the background. This can happen if multiple users or processes are trying to execute payment runs simultaneously.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If a payment lot is locked for processing, other transactions that require access to that lot will be blocked until the current process is completed.
  Long-running Processes: If the payment lot transfer is taking longer than expected due to system performance issues or large volumes of data, it can lead to this error.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the current payment lot transfer to complete. You can check the status of the payment lot transfer in the relevant transaction (e.g., F110 for automatic payment transactions).
  Check Background Jobs: Use transaction code SM37 to monitor background jobs. Look for any jobs related to payment processing that might be running and causing the lock.
  Identify and Terminate Long-Running Jobs: If you identify a job that is taking too long and is causing the issue, you may need to terminate it (if appropriate) and then retry the payment generation.
  System Performance: If this issue occurs frequently, consider reviewing system performance and optimizing the payment processing jobs. This may involve adjusting job scheduling or increasing system resources.
  Consult with Basis Team: If the issue persists, it may be necessary to involve your SAP Basis team to investigate any underlying system issues or to check for any locks that may not be releasing properly.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), SM37 (Job Monitoring), and SM21 (System Log) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to payment processing and the specific error message.
  Documentation: Review SAP documentation for payment processing to understand the workflow and any potential configurations that may affect payment lot transfers.
  
  By following these steps, you should be able to resolve the error and continue with your payment processing tasks in SAP.