How To Fix UGMD130 - Registration made with invalid property of RFC destination &1

UGMD130 - Overview

• Message type: E = Error

• Message class: UGMD - FIN Master Data: Messages

• Message number: 130

• Message text: Registration made with invalid property of RFC destination &1

What causes this issue?

RFC destination &V1& has an invalid property.
RFC destination &V1& previously had property &V2&. The system is now
trying to use the RFC destination with property &V3&. However, it is
not permitted to change the property.

System Response

Registration cannot be performed.

How to fix this error?

If the same target system is to be used in another context, create a
second RFC destination for this system.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UGMD130 - Registration made with invalid property of RFC destination &1 ?

  The SAP error message UGMD130 indicates that there is an issue with the registration of a service or a component due to an invalid property of the RFC (Remote Function Call) destination specified in the system. This error typically arises in scenarios involving the configuration of RFC destinations, especially when dealing with SAP Gateway or other integration scenarios.
  
  Cause:
  
  Invalid RFC Destination: The specified RFC destination does not exist or is incorrectly configured.
  Incorrect Parameters: The parameters set for the RFC destination may be incorrect or incomplete.
  Network Issues: There may be network connectivity issues preventing the system from reaching the specified RFC destination.
  Authorization Issues: The user or service trying to access the RFC destination may not have the necessary authorizations.
  System Configuration: The system may not be properly configured to handle the requested operation.
  
  
  Solution:
  
  
  Check RFC Destination:
  
  Go to transaction code SM59 to check the configuration of the RFC destination.
  Ensure that the destination exists and is