How To Fix SO810 - Substitute <&> was created

SAP Error Message - Details

• Message type: E = Error

• Message class: SO - SAPoffice: message texts

• Message number: 810

• Message text: Substitute <&> was created

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 SO810 - Substitute <&> was created ?

  The SAP error message SO810, which states "Substitute <&> was created," typically occurs in the context of SAP's Sales and Distribution (SD) module, particularly when dealing with substitutions in sales orders or during the sales process. This message indicates that a substitute product has been created for a particular item in a sales order.
  Cause:
  The error message SO810 is not necessarily an error in the traditional sense; rather, it is an informational message indicating that a substitute item has been successfully created for a product that may not be available or is being replaced. This can happen due to:
  
  Product Unavailability: The original product is out of stock or not available for the requested delivery date.
  Substitution Rules: There are predefined substitution rules in the system that automatically suggest or create substitutes for certain products based on business logic.
  Manual Intervention: A user may have manually created a substitute for a product in the sales order.
  
  Solution:
  To address the SO810 message, consider the following steps:
  
  
  Review the Sales Order: Check the sales order to see which item has been substituted and what the substitute item is. This can usually be done in the sales order display (transaction code VA03).
  
  
  Check Substitution Settings: If the substitution was automatic, review the substitution settings in the system. This can be done in the configuration settings under Sales and Distribution (SD) to ensure that the rules are set up correctly.
  
  
  Communicate with Stakeholders: If the substitution affects customer orders, communicate with relevant stakeholders (e.g., sales team, inventory management) to ensure they are aware of the changes and can manage customer expectations.
  
  
  Adjust Inventory: If the original product is out of stock, consider adjusting inventory levels or procurement plans to avoid future substitutions.
  
  
  Training and Documentation: Ensure that users are trained on how to handle substitutions and that there is documentation available for reference.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VA01 (Create Sales Order), VA02 (Change Sales Order), and VA03 (Display Sales Order) to manage sales orders effectively.
  Substitution Configuration: The configuration for substitutions can be found in the SAP IMG under Sales and Distribution > Basic Functions > Substitutions.
  User Exits and BAdIs: If custom logic is required for substitutions, consider using user exits or Business Add-Ins (BAdIs) to implement specific business rules.
  
  If you continue to experience issues or if the message is causing operational problems, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP SD for further assistance.