How To Fix EAMS_SP201 - This object is not geo-enabled but has geometry; check the Customizing

EAMS_SP201 - Overview

• Message type: E = Error

• Message class: EAMS_SP - EAMS: Service Provider Layer

• Message number: 201

• Message text: This object is not geo-enabled but has geometry; check the Customizing

What causes this issue?

The business object is not geo-enabled because some field values do not
match the Customizing criteria. However, geometry data already exists
for the business object.

System Response

It is not possible to navigate to the SAP Geographical Enablement
Framework to show or edit the business object on the map.

How to fix this error?

Enter the correct values based on the filter values of your Customizing
settings for each of your business objects.

Procedure for System Administrators

Check your settings in Customizing activity
<DS:SIMG.CONFIGURE THE FRAMEWORK>Configure the Framework</> for the EAM
GEF extension under <ZK>SAP Geographical Enablement Framework</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EAMS_SP201 - This object is not geo-enabled but has geometry; check the Customizing ?

  The SAP error message EAMS_SP201 indicates that there is an issue with a specific object in the SAP system that is expected to have geographic data (geometry) associated with it, but it is not configured to be geo-enabled. This typically occurs in the context of SAP's Enterprise Asset Management (EAM) or similar modules that utilize geographic information systems (GIS).
  
  Cause:
  
  Object Not Geo-Enabled: The object in question (e.g., a functional location, equipment, or asset) is not set up to handle geographic data, even though it has geometry associated with it.
  Customizing Settings: The necessary customizing settings to enable geographic capabilities for the object type may not be properly configured.
  Data Integrity Issues: There may be inconsistencies in the data where geometry is assigned to an object that is not configured to support it.
  
  
  Solution:
  
  
  Check Customizing Settings:
  
  Navigate to the customizing settings in SAP (transaction code SPRO).
  Look for the settings related to the specific object type (e.g.,