How To Fix IHC335 - Payment order &1 to be reversed is being edited by the user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: IHC - IHC Messages

• Message number: 335

• Message text: Payment order &1 to be reversed is being edited by the user &2

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 IHC335 - Payment order &1 to be reversed is being edited by the user &2 ?

  The SAP error message IHC335 indicates that a payment order you are trying to reverse is currently being edited by another user. This can happen in scenarios where multiple users are working on the same payment order or if a session is still open with the payment order being processed.
  Cause:
  
  Concurrent Editing: Another user is currently editing the payment order you are trying to reverse.
  Session Lock: The payment order may be locked due to an open session or transaction that has not been completed or closed properly.
  User Lock: The specific user who is editing the payment order has not released the lock on the transaction.
  
  Solution:
  
  Check User Activity: Identify the user who is currently editing the payment order (as indicated in the error message). You may need to communicate with that user to determine if they can complete or cancel their transaction.
  Wait and Retry: If the other user is actively working on the payment order, you may need to wait until they finish and release the lock before attempting to reverse the payment order again.
  Session Management: Ensure that there are no open sessions that are holding locks on the payment order. If you have access, you can check for active sessions in transaction codes like SM04 (User Overview) or SM12 (Lock Entries).
  Lock Entry Release: If necessary, a system administrator can release the lock on the payment order using transaction SM12, but this should be done with caution to avoid data inconsistency.
  Review System Logs: Check system logs for any additional information regarding the lock or the user activity that may help in diagnosing the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM04 (to view user sessions), SM12 (to view and manage lock entries), and SU01 (to manage user profiles).
  User Communication: Establish a protocol for users to communicate when they are working on shared payment orders to avoid such conflicts.
  System Configuration: Review system settings related to locking mechanisms and user access to ensure they align with your organization's workflow.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or technical support for further assistance.