How To Fix /ACCGO/UIS_API195 - EXTID &1: Customer &2 is not in reference trading contract &3

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_API -

• Message number: 195

• Message text: EXTID &1: Customer &2 is not in reference trading contract &3

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_API195 - EXTID &1: Customer &2 is not in reference trading contract &3 ?

  The SAP error message /ACCGO/UIS_API195 EXTID &1: Customer &2 is not in reference trading contract &3 typically indicates that there is an issue with the customer assignment in a trading contract. This error arises when the system is unable to find the specified customer in the reference trading contract.
  Cause:
  
  Customer Not Assigned: The customer specified in the error message is not assigned to the trading contract referenced.
  Incorrect Trading Contract: The trading contract number provided may be incorrect or does not exist.
  Data Inconsistency: There may be inconsistencies in the data, such as missing or incorrect entries in the customer master data or trading contract.
  Authorization Issues: The user may not have the necessary authorizations to view or access the trading contract or customer data.
  
  Solution:
  
  
  Check Customer Assignment:
  
  Go to the trading contract in question and verify if the customer is indeed assigned to it. You can do this by navigating to the relevant transaction code (e.g., VA42 for changing contracts) and checking the customer details.
  
  
  
  Verify Trading Contract:
  
  Ensure that the trading contract number is correct. If you have the wrong number, correct it and try again.
  
  
  
  Review Customer Master Data:
  
  Check the customer master data to ensure that the customer exists and is active. You can use transaction code XD03 to display customer data.
  
  
  
  Check for Data Consistency:
  
  Run any relevant reports or transactions to check for data consistency issues. This may involve checking for missing entries or discrepancies in the database.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the trading contract and customer data. If not, contact your SAP security team to resolve any authorization issues.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific guidance or patches that may address the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VA42 (Change Contract), XD03 (Display Customer), and VA03 (Display Sales Order) for checking related data.
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with SAP experts for further assistance.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message.