How To Fix LTR2_UI_OBT_SCN035 - New data sets added

SAP Error Message - Details

• Message type: E = Error

• Message class: LTR2_UI_OBT_SCN - Message Class for OBT-Scenario Editor

• Message number: 035

• Message text: New data sets added

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_UI_OBT_SCN035 - New data sets added ?

  The SAP error message LTR2_UI_OBT_SCN035, which indicates "New data sets added," typically occurs in the context of SAP Landscape Transformation (SLT) or SAP Data Services when there are changes in the data model or when new data sets are introduced that the system is not currently configured to handle.
  Cause:
  
  New Data Sets: The error usually arises when new data sets (tables, views, etc.) are added to the source system that are not yet recognized or configured in the SLT or Data Services environment.
  Configuration Issues: There may be a lack of proper configuration or mapping for the new data sets in the SLT replication setup.
  Change in Source Structure: If the structure of the source data has changed (e.g., new columns added), the target system may not be aware of these changes.
  
  Solution:
  
  
  Refresh the Configuration:
  
  Go to the SLT configuration and refresh the data model to include the new data sets. This can often be done by reloading the configuration or by using the appropriate transaction codes (like LTRC for SLT).
  
  
  
  Add New Data Sets:
  
  If new tables or views have been added, ensure that they are included in the SLT configuration. You may need to manually add these new data sets to the replication configuration.
  
  
  
  Check Replication Settings:
  
  Verify that the replication settings are correctly configured for the new data sets. This includes checking the mapping and ensuring that the target system is set up to receive the new data.
  
  
  
  Monitor Logs:
  
  Check the SLT logs for more detailed error messages or warnings that can provide additional context on what might be causing the issue.
  
  
  
  Reinitialize Replication:
  
  In some cases, it may be necessary to reinitialize the replication for the affected data sets to ensure that they are correctly synchronized.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as LTRC (for SLT configuration), LTR2 (for monitoring), and SLT logs for troubleshooting.
  Documentation: Refer to SAP documentation for SLT and Data Services for detailed steps on how to manage data sets and replication configurations.
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to this error message or provide patches and updates.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance, as they can provide more tailored guidance based on your specific system configuration and version.