How To Fix LTR2_ES_CHECK260 - DMC runtime parameter '&1' set to '&2' ('&3' required) - see long text

LTR2_ES_CHECK260 - Overview

• Message type: E = Error

• Message class: LTR2_ES_CHECK - LTR2 Checks on Embedded Specification

• Message number: 260

• Message text: DMC runtime parameter '&1' set to '&2' ('&3' required) - see long text

What causes this issue?

DMC runtime parameter &V1& is set to &V2& but value &V3& is required
for the current object-based transformation project.

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?

This parameter is stored in table DMC_RT_CONFIG. Please use maintanance
view DMC_RT_CONFIG to set the parameters to the required values.
<DS:TRAN.SM30>SM30</>

Procedure for System Administrators

Note that these settings are global and can have side effects to other
solutions that use the Migration Work Bench (MWB), e.g. TDMS or other
SAP LT based solutions.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message LTR2_ES_CHECK260 - DMC runtime parameter '&1' set to '&2' ('&3' required) - see long text ?

  The SAP error message LTR2_ES_CHECK260 typically indicates an issue with the Data Migration Cockpit (DMC) runtime parameters. This error occurs when a specific runtime parameter is set to an incorrect value, which does not meet the requirements for the operation being performed.
  
  Cause:
  The error message indicates that a runtime parameter (denoted as &1) is currently set to a value (&2) that is not acceptable, and a different value (&3) is required for the process to proceed. This usually happens when:
  
  The configuration of the DMC is incorrect.
  The parameters have not been set according to the requirements of the specific migration scenario.
  There may be a mismatch between the expected and actual values for the runtime parameters.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check the Long Text of the Error Message: The long text of the error message will provide specific details about which parameter is causing the issue and what the expected