How To Fix /ACCGO/UIS_API175 - EXTID &1: In vendor split data, only one entry can be specified as header

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_API -

• Message number: 175

• Message text: EXTID &1: In vendor split data, only one entry can be specified as header

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_API175 - EXTID &1: In vendor split data, only one entry can be specified as header ?

  The SAP error message /ACCGO/UIS_API175 EXTID &1: In vendor split data, only one entry can be specified as header typically occurs in the context of vendor split accounting, particularly when dealing with multiple entries in a vendor split scenario. This error indicates that the system expects only one entry to be designated as the "header" for the vendor split data, but it has detected multiple entries marked as headers.
  Cause:
  
  Multiple Header Entries: The primary cause of this error is that there are multiple entries in the vendor split data that are incorrectly marked as headers. In a vendor split scenario, only one entry should be designated as the header, while the others should be treated as line items or details.
  Data Entry Error: This can happen due to incorrect data entry or configuration in the vendor split settings.
  Configuration Issues: There may be issues in the configuration of the vendor split functionality in the system.
  
  Solution:
  
  Review Vendor Split Data: Check the vendor split data entries for the specific vendor (identified by &1 in the error message). Ensure that only one entry is marked as the header.
  Correct the Entries: If you find multiple entries marked as headers, you need to correct this by:
  
  Changing the designation of the additional header entries to line items.
  Ensuring that only one entry is set as the header.
  
  
  Check Configuration: If the issue persists, review the configuration settings for vendor split accounting in your SAP system. Ensure that the settings align with the expected behavior of the vendor split functionality.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on vendor split configurations and data entry requirements.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like FB60 (Enter Incoming Invoice) or FB70 (Enter Outgoing Invoice) to review and edit vendor invoices.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on vendor split configurations.
  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 assistance based on your specific system configuration and version.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message.