How To Fix LTR2_RN104 - Check between source project and clone project failed

SAP Error Message - Details

• Message type: E = Error

• Message class: LTR2_RN - LTR2 RN: Message class

• Message number: 104

• Message text: Check between source project and clone project failed

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message LTR2_RN104 - Check between source project and clone project failed ?

  The SAP error message LTR2_RN104: Check between source project and clone project failed typically occurs during the process of cloning a project in SAP Landscape Transformation (SLT) or during the replication of data. This error indicates that there is a mismatch or inconsistency between the source project and the clone project, which prevents the cloning process from completing successfully.
  Causes:
  
  Inconsistent Configuration: The source project may have configurations that are not compatible with the clone project.
  Missing Objects: Some objects (like tables, views, or other database objects) that are present in the source project may be missing in the clone project.
  Data Model Differences: Differences in the data model or structure between the source and clone projects can lead to this error.
  Authorization Issues: Lack of proper authorizations for the user executing the cloning process can also trigger this error.
  Technical Settings: Differences in technical settings (like data types, lengths, etc.) between the source and clone projects.
  
  Solutions:
  
  Check Configuration: Review the configurations of both the source and clone projects to ensure they are consistent. Pay attention to any settings that may differ.
  Verify Objects: Ensure that all necessary objects in the source project are also present in the clone project. This includes tables, views, and any other relevant database objects.
  Data Model Alignment: Make sure that the data models of both projects are aligned. If there are changes in the source project, replicate those changes in the clone project.
  Authorization Check: Ensure that the user executing the cloning process has the necessary authorizations to access both the source and clone projects.
  Technical Settings Review: Check the technical settings of the objects in both projects to ensure they match. This includes data types, lengths, and other relevant attributes.
  Logs and Traces: Review the logs and traces for more detailed error messages that can provide insights into what specifically is causing the failure.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to the official SAP documentation for Landscape Transformation (SLT) for guidance on project cloning and replication processes.
  Community Forums: Engage with SAP community forums or support channels where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the steps you have already taken.