How To Fix CRM_MKT_EXTERNAL006 - Server GUID &1 transferred not defined in the Customizing table

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKT_EXTERNAL - CRM MKT: Messages for Interface to External Products

• Message number: 006

• Message text: Server GUID &1 transferred not defined in the Customizing table

What causes this issue?

Using the GUID transferred, the system searched for an entry in the
Customizing table CRMC_EXT_SERVER. This entry was not however found.
The GUID identifies a row in the Customizing table and is automatically
generated by the system when you maintain entries in the table.
This GUID was not found in the table, probably because the entry has
been deleted from the table.

How to fix this error?

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

INCLUDE CRMT_MKT_APIS_LOG OBJECT DOKU ID TX LANGUAGE EN

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_MKT_EXTERNAL006 - Server GUID &1 transferred not defined in the Customizing table ?

  The SAP error message CRM_MKT_EXTERNAL006 indicates that a server GUID (Globally Unique Identifier) that has been transferred is not defined in the Customizing table. This typically occurs in the context of SAP CRM (Customer Relationship Management) when there is an issue with the integration between different systems or components, such as when data is being transferred from an external system to SAP CRM.
  
  Cause:
  
  Missing Configuration: The GUID being referenced is not defined in the relevant Customizing tables. This could happen if the system was not properly configured to recognize the external system or if the GUID was not registered.
  Data Transfer Issues: There may be issues with the data being sent from the external system, such as incorrect or outdated GUIDs.
  System Integration Problems: If there are changes in the external system or if the integration settings have been modified, it may lead to discrepancies in the GUIDs being used.
  
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to