How To Fix T0729 - Payment history for partner &1 &2 already being edited by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: T0 - General Treasury

• Message number: 729

• Message text: Payment history for partner &1 &2 already being edited 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 T0729 - Payment history for partner &1 &2 already being edited by another user ?

  The SAP error message T0729 indicates that the payment history for a specific partner (customer or vendor) is currently being edited by another user. This can occur in various SAP modules, particularly in Financial Accounting (FI) or Accounts Payable (AP) when multiple users attempt to access or modify the same data simultaneously.
  Cause:
  
  Concurrent Access: Another user is currently editing the payment history for the specified partner, which locks the data to prevent inconsistencies.
  Session Timeout: A previous session may not have been properly closed, leaving the data locked.
  System Configuration: The system may be configured to allow only one user to edit certain records at a time.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish their edits. Once they are done, you should be able to access the payment history.
  Check User Sessions: If you have access, check the user sessions in the system to see if the other user is still active. You can use transaction code SM04 to view active user sessions.
  Contact the User: If you know who the other user is, you can contact them to see if they can finish their work or release the lock.
  System Administrator: If the issue persists and you cannot identify the other user, contact your SAP system administrator. They can release the lock if necessary.
  Review Configuration: If this issue occurs frequently, it may be worth reviewing the system configuration to see if adjustments can be made to allow for better concurrent access.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view and manage locks) and SM04 (to view active user sessions).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Training: Ensure that users are trained on how to properly close sessions and avoid leaving data locked inadvertently.
  
  By following these steps, you should be able to resolve the T0729 error and continue working with the payment history in SAP.