How To Fix SOI2371 - Invalid combinations are ignored as correctly handled by application

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI2 - SOI Messages

• Message number: 371

• Message text: Invalid combinations are ignored as correctly handled by application

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 SOI2371 - Invalid combinations are ignored as correctly handled by application ?

  The SAP error message SOI2371, which states "Invalid combinations are ignored as correctly handled by application," typically occurs in the context of SAP's Sales Order Management or similar modules where certain combinations of data inputs do not meet the expected criteria or rules defined in the system.
  Cause:
  
  Data Input Issues: The error often arises when there are invalid combinations of data fields in a transaction. For example, certain product configurations may not be compatible with specific order types or customer requirements.
  Configuration Errors: If the system is not properly configured to handle specific combinations of products, services, or conditions, it may trigger this error.
  Business Rules: The application may have built-in business rules that restrict certain combinations of items, pricing, or conditions that are not allowed.
  
  Solution:
  
  Review Input Data: Check the data being entered for the transaction. Ensure that all combinations of items, pricing, and conditions are valid according to the business rules defined in the system.
  Consult Documentation: Refer to the SAP documentation or configuration guides to understand the valid combinations for the specific transaction you are working with.
  Configuration Check: If you have access, review the configuration settings in the SAP system to ensure that the necessary combinations are allowed. This may involve checking the configuration of product variants, pricing conditions, or other related settings.
  Error Handling: If the application is designed to handle these invalid combinations gracefully, ensure that the system is set up to log these occurrences for further analysis rather than simply ignoring them.
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who can provide insights based on your specific configuration and business processes.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on handling invalid combinations.
  Transaction Codes: Familiarize yourself with transaction codes related to sales order processing, such as VA01 (Create Sales Order), VA02 (Change Sales Order), and VA03 (Display Sales Order), as these may be where the error is encountered.
  User Exits and BAdIs: If your organization has custom developments, check if there are any user exits or Business Add-Ins (BAdIs) that might be affecting the handling of combinations in your specific implementation.
  
  By following these steps, you should be able to identify the cause of the SOI2371 error and implement a solution to address it effectively.