How To Fix R5517 - City &1 does not exist in country &2

SAP Error Message - Details

• Message type: E = Error

• Message class: R5 - Regional structure

• Message number: 517

• Message text: City &1 does not exist in country &2

What causes this issue?

The specified city could not be found in the city table
(ADRCITY/ADRCITYT), maintained by the transactions SR10 and SR11.
Either the city name was spelt incorrectly or the city has not yet been
created.
This check will only run when the flag 'XREGS' (address check with city
file) is marked in the table T005 (country table).

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message R5517 - City &1 does not exist in country &2 ?

  The SAP error message R5517 indicates that the system cannot find a specified city in the given country. This error typically occurs during processes that involve address validation, such as when creating or updating customer or vendor master data, or during sales order processing.
  Cause:
  
  Missing City Data: The city you are trying to use is not defined in the SAP system for the specified country.
  Incorrect Country Code: The country code provided may be incorrect or not aligned with the city name.
  Data Inconsistency: There may be inconsistencies in the address data, such as typos or incorrect formatting.
  Master Data Issues: The city may not be part of the master data maintained in the system.
  
  Solution:
  
  
  Check City and Country Data:
  
  Verify that the city name is spelled correctly and matches the expected format.
  Ensure that the country code is correct and corresponds to the city.
  
  
  
  Maintain City Data:
  
  If the city is indeed missing, you can add it to the SAP system. This is typically done in the transaction code OVT0 (for maintaining country-specific data) or OBD2 (for maintaining cities).
  You may need to consult with your SAP administrator or someone with the necessary authorizations to add or modify this data.
  
  
  
  Use Standard Address Formats:
  
  Ensure that the address is entered using standard formats recognized by SAP. This includes using the correct naming conventions for cities and countries.
  
  
  
  Check Customizations:
  
  If your organization has custom address validation logic, ensure that it is functioning correctly and that it includes the necessary cities.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this issue. Sometimes, there are known issues or patches that can resolve specific problems.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  OVT0: Maintain country-specific data.
  OBD2: Maintain cities.
  BP: Business Partner transaction for managing customer/vendor data.
  
  
  
  Address Validation: SAP has built-in address validation features that can help ensure that addresses are correctly formatted and valid.
  
  
  User Roles and Authorizations: Ensure that the user attempting to make changes has the necessary permissions to modify address data.
  
  
  If the issue persists after following these steps, it may be beneficial to reach out to SAP support or consult with your internal SAP team for further assistance.