How To Fix EI717 - Code number &1 does not exist in import country &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EI - Foreign Trade: Gen. Output

• Message number: 717

• Message text: Code number &1 does not exist in import country &2

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 EI717 - Code number &1 does not exist in import country &2 ?

  The SAP error message EI717, which states "Code number &1 does not exist in import country &2," typically occurs in the context of foreign trade and customs processing within the SAP system. This error indicates that a specific code (such as a customs code, tariff code, or similar identifier) is not recognized or does not exist for the specified import country in the system.
  Cause:
  
  Missing Code: The code number specified in the error message is not defined in the SAP system for the given import country.
  Incorrect Configuration: The configuration for foreign trade settings may be incomplete or incorrect, leading to the system not recognizing the code.
  Data Entry Error: There may be a typographical error in the code number or the import country specified in the transaction.
  Updates or Changes: Changes in regulations or updates to the code lists may not have been reflected in the SAP system.
  
  Solution:
  
  
  Check Code Definition:
  
  Verify if the code number (&1) exists in the system for the specified import country (&2). You can do this by navigating to the relevant configuration or master data areas in SAP.
  Use transaction codes like OBD2 (for customs codes) or OBD1 (for tariff codes) to check the definitions.
  
  
  
  Update Master Data:
  
  If the code does not exist, you may need to create it. This can involve adding the code to the relevant tables or master data records in SAP.
  Ensure that the code is correctly linked to the appropriate import country.
  
  
  
  Review Configuration:
  
  Check the configuration settings for foreign trade in the SAP system. Ensure that all necessary settings are correctly configured for the import process.
  Use transaction SPRO to access the configuration settings and verify the foreign trade settings.
  
  
  
  Consult Documentation:
  
  Review any recent changes in trade regulations or customs requirements that may affect the codes used in your SAP system.
  Ensure that your SAP system is updated with the latest regulatory changes.
  
  
  
  Contact Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting SAP documentation for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing foreign trade data, such as OBD2, OBD1, and ME21N (for creating purchase orders).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles: Ensure that the user has the necessary permissions to access and modify the relevant data in the SAP system.
  
  By following these steps, you should be able to identify the cause of the EI717 error and implement the necessary solutions to resolve it.