How To Fix CMX_XS109 - Destination types do not match; see long text

CMX_XS109 - Overview

• Message type: E = Error

• Message class: CMX_XS - XSteps: Messages

• Message number: 109

• Message text: Destination types do not match; see long text

What causes this issue?

Once a <DS:GLOS.3526C517AFAB52B9E10000009B38F974>control recipe
destination</> has been assigned, this is inherited from top to bottom
along the XStep tree hierarchy until the next control recipe destination
is reached. The control recipe destination types must be identical
within this section of the hierarchy.
The control recipe destination type &V1& does not, however, match the
higher-level control recipe destination type &V2&.

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?

Carry out one of the following activities:
Use the control recipe destination type &V2& or do not define a
destination.
Define a specific control recipe destination.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

CMX_XS109 - Details

• The SAP error message CMX_XS109, which states "Destination types do not match; see long text," typically occurs in the context of SAP Cloud Platform or SAP HANA when there is a mismatch between the expected and actual types of destinations being used in a connection or service call.
  
  Cause:
  
  Mismatched Destination Types: This error usually arises when the destination you are trying to use in your application does not match the expected type. For example, if a service expects an HTTP destination but receives a JDBC destination, this error will be triggered.
  
  Configuration Issues: Incorrect configuration of the destination in the SAP Cloud Platform cockpit or in the application settings can lead to this error.
  Service Binding Issues: If the service you are trying to access is bound to a different type of destination than what your application is configured to use, this can also cause the error.
  
  
  Solution:
  
  
  Check Destination Configuration:
  
  Go to the SAP Cloud