How To Fix /SCMB/ORDER335 - Purchase order number &1 already exists

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/ORDER -

• Message number: 335

• Message text: Purchase order number &1 already exists

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 /SCMB/ORDER335 - Purchase order number &1 already exists ?

  The SAP error message /SCMB/ORDER335 Purchase order number &1 already exists typically occurs in the context of the Supply Chain Management (SCM) module when there is an attempt to create a purchase order (PO) with a number that already exists in the system. This can happen due to various reasons, such as duplicate entries or issues with the number range configuration.
  Cause:
  
  Duplicate Purchase Order: The most common cause is that a purchase order with the same number has already been created in the system.
  Number Range Configuration: The number range for purchase orders may not be set up correctly, leading to conflicts.
  Data Migration Issues: If data has been migrated from another system, there may be duplicate entries.
  User Error: A user may inadvertently attempt to create a PO with a number that has already been assigned.
  
  Solution:
  
  
  Check Existing Purchase Orders: 
  
  Use transaction codes like ME23N (Display Purchase Order) to check if the purchase order number already exists in the system.
  If it does exist, you may need to use that existing PO instead of creating a new one.
  
  
  
  Adjust Number Range:
  
  If the issue is related to number range configuration, check the number range settings in the customizing settings (transaction code SPRO).
  Ensure that the number range for purchase orders is correctly defined and that there are no overlaps.
  
  
  
  Data Cleanup:
  
  If the error is due to data migration, you may need to clean up the data to remove duplicates or adjust the existing records.
  
  
  
  Use Automatic Number Assignment:
  
  If possible, configure the system to use automatic number assignment for purchase orders to avoid manual entry errors.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  
  Contact SAP Support:
  
  If the problem persists and you cannot identify the cause, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  User Roles and Authorizations: Ensure that users have the appropriate roles and authorizations to create and manage purchase orders.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.