How To Fix /ACCGO/UIS_MSG340 - Incorrect vendor split information

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 340

• Message text: Incorrect vendor split information

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 /ACCGO/UIS_MSG340 - Incorrect vendor split information ?

  The SAP error message /ACCGO/UIS_MSG340 Incorrect vendor split information typically occurs in the context of the SAP system when there is an issue with how vendor split information is configured or processed in the system. This error is often related to the handling of vendor invoices, particularly when multiple vendors are involved in a single transaction.
  Causes:
  
  Incorrect Vendor Configuration: The vendor master data may not be set up correctly, leading to inconsistencies in how vendor splits are processed.
  Missing or Incorrect Split Criteria: The criteria used to determine how the invoice should be split among vendors may be missing or incorrectly defined.
  Inconsistent Data: There may be inconsistencies in the data entered for the transaction, such as mismatched amounts or incorrect vendor assignments.
  Custom Logic or Enhancements: If there are custom developments or enhancements in the system, they may not be handling vendor splits correctly.
  Document Type Restrictions: Certain document types may have restrictions on how vendor splits can be processed.
  
  Solutions:
  
  Check Vendor Master Data: Verify that the vendor master data is correctly configured. Ensure that all necessary fields are filled out and that the vendor is active.
  Review Split Configuration: Check the configuration for vendor splits in the system. Ensure that the split criteria are correctly defined and that they match the requirements of the transaction.
  Validate Transaction Data: Review the transaction data for any inconsistencies. Ensure that the amounts and vendor assignments are correct and that they align with the expected split.
  Debug Custom Logic: If there are custom developments, debug the logic to identify any issues that may be causing the error. Ensure that the custom code adheres to the standard processing rules for vendor splits.
  Consult Documentation: Refer to SAP documentation or notes related to vendor splits for any specific guidelines or known issues that may apply to your situation.
  Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB60 (Enter Vendor Invoice) or MIRO (Enter Incoming Invoice) where vendor splits may be processed.
  SAP Notes: Search for SAP Notes related to vendor splits and the specific error message for any patches or updates that may address the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.