How To Fix R5060 - Database inconsistency city &1, notify system administrator

SAP Error Message - Details

• Message type: E = Error

• Message class: R5 - Regional structure

• Message number: 060

• Message text: Database inconsistency city &1, notify system administrator

What causes this issue?

There are already city - postal code assignments (ADRPCITY records) for
the specified city number &V1&, although the city does not yet exist
(should be created now).

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 R5060 - Database inconsistency city &1, notify system administrator ?

  The SAP error message R5060 indicates a database inconsistency related to a city entry in the system. This error typically arises when there is a mismatch or corruption in the data stored in the database, particularly in the address or location-related tables.
  Cause:
  
  Data Corruption: The data for the city entry may have been corrupted due to various reasons, such as system crashes, improper data imports, or manual data entry errors.
  Inconsistent Data: There may be inconsistencies between different tables that reference the city data, leading to conflicts.
  Custom Developments: If there are custom programs or enhancements that manipulate address data, they might inadvertently cause inconsistencies.
  Transport Issues: If data was transported from one system to another (e.g., from development to production), it might not have been transported correctly.
  
  Solution:
  
  Notify System Administrator: As the error message suggests, the first step is to notify your system administrator or SAP Basis team. They will have the necessary access and tools to investigate the issue further.
  Check Database Tables: The administrator should check the relevant database tables (e.g., T005 for countries and cities) for inconsistencies. They can use transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to inspect the data.
  Run Consistency Checks: SAP provides tools to check for data consistency. The administrator can run transaction codes like SARA (Archive Administration) or use specific reports designed to check for inconsistencies in address data.
  Correct Data Manually: If the inconsistency is identified, the administrator may need to correct the data manually or through a data correction program.
  Review Custom Code: If there are custom developments, they should be reviewed to ensure they are not causing the inconsistency.
  Transport Review: If the issue arose after a transport, the transport logs should be reviewed to ensure that all necessary objects were transported correctly.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide guidance on similar issues.
  Transaction Codes: Familiarize yourself with transaction codes like SE11, SE16, and SARA for data inspection and consistency checks.
  Documentation: Review SAP documentation related to address management and data consistency to understand best practices for maintaining data integrity.
  
  If the issue persists after following these steps, it may be necessary to escalate the problem to SAP support for further assistance.