How To Fix EDI_SD020 - Purchase order &2 of customer &1 is currently being processed

SAP Error Message - Details

• Message type: E = Error

• Message class: EDI_SD - Messages for EDI SD Integration

• Message number: 020

• Message text: Purchase order &2 of customer &1 is currently 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 EDI_SD020 - Purchase order &2 of customer &1 is currently being processed ?

  The SAP error message EDI_SD020 indicates that a purchase order (PO) for a specific customer is currently being processed, which means that the system is unable to handle the request for that particular PO at the moment. This can occur in various scenarios, particularly in the context of Electronic Data Interchange (EDI) processes.
  Cause:
  
  Concurrent Processing: The purchase order is being processed by another transaction or user, which locks the PO for updates.
  System Lock: The system may have a lock on the PO due to ongoing processing, such as an inbound EDI message or a related transaction that has not yet completed.
  Long-running Processes: If there are long-running background jobs or processes that involve the PO, it may lead to this error.
  Data Consistency Checks: The system may be performing data consistency checks or validations that temporarily lock the PO.
  
  Solution:
  
  Wait and Retry: If the error is due to concurrent processing, waiting for a few moments and then retrying the operation may resolve the issue.
  Check for Locks: Use transaction codes like SM12 to check for locks on the purchase order. If you find a lock that is no longer needed, you may need to unlock it (with caution).
  Monitor Background Jobs: Check for any background jobs that may be processing the PO using transaction SM37. If a job is taking too long, you may need to investigate or terminate it if appropriate.
  Review EDI Processing: If the error is related to EDI processing, ensure that the inbound EDI messages are being processed correctly and that there are no issues with the EDI interface.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to your SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to check locks), SM37 (to monitor jobs), and SLG1 (to view application logs).
  EDI Configuration: Ensure that your EDI configuration is set up correctly, including partner profiles and message types.
  User Permissions: Verify that the user attempting to process the PO has the necessary permissions to access and modify the purchase order.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the EDI_SD020 error message in SAP.