How To Fix RSDRI_DTP055 - New request l_new_sid created

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDRI_DTP - Messages for InfoProvider Extraction in DTP Context

• Message number: 055

• Message text: New request l_new_sid created

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 RSDRI_DTP055 - New request l_new_sid created ?

  The SAP error message RSDRI_DTP055, which states "New request l_new_sid created," typically occurs in the context of Data Transfer Processes (DTP) in SAP BW (Business Warehouse). This message indicates that a new request has been created for the DTP, which is a normal part of the data loading process. However, it can also be associated with issues in the data loading process.
  Cause:
  
  Data Load Issues: The error can occur if there are issues with the data being loaded, such as data inconsistencies, missing data, or problems with the source system.
  DTP Configuration: Incorrect configuration of the DTP can lead to this message. This includes settings related to the source and target InfoProviders, transformation rules, or data filters.
  Request Handling: If the previous request was not processed correctly or if there are multiple requests being processed simultaneously, a new request may be created.
  System Performance: Performance issues in the SAP BW system can also lead to this message, especially if the system is under heavy load.
  
  Solution:
  
  Check DTP Configuration: Review the DTP settings to ensure that they are correctly configured. Pay attention to the source and target InfoProviders, transformation rules, and any filters applied.
  Monitor Data Load: Use transaction codes like RSA1 (Data Warehousing Workbench) to monitor the data load process. Check for any errors or warnings in the process chain that might indicate why the new request was created.
  Review Logs: Check the logs for the DTP execution. You can do this by navigating to the DTP monitor and reviewing the details of the request. Look for any error messages or warnings that could provide more context.
  Data Consistency: Ensure that the data in the source system is consistent and complete. If there are issues with the data, resolve them before attempting to load again.
  Performance Tuning: If system performance is an issue, consider optimizing the BW system. This may involve tuning database performance, adjusting memory settings, or scheduling data loads during off-peak hours.
  Retry the Load: After addressing any identified issues, retry the data load process to see if the problem persists.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 for the Data Warehousing Workbench, RSMO for monitoring data loads, and RSPC for process chains.
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific version of SAP BW you are using. This can provide additional insights or solutions.
  Documentation: Review SAP documentation on DTPs and data loading processes for best practices and troubleshooting tips.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or BW team for further investigation.