How To Fix RSDTM123 - InfoPackage "&1"("&2") started (with request ID "&3")

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDTM - Data Mining Connection Messages

• Message number: 123

• Message text: InfoPackage "&1"("&2") started (with request ID "&3")

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 RSDTM123 - InfoPackage "&1"("&2") started (with request ID "&3") ?

  The SAP error message RSDTM123 indicates that an InfoPackage has been started, but it may not provide specific details about an error. Instead, it is more of an informational message that indicates the InfoPackage is in the process of being executed. However, if you are encountering issues related to this message, it could be due to several reasons. Here’s a breakdown of potential causes, solutions, and related information:
  Causes:
  
  Long Running Process: The InfoPackage may be taking longer than expected to execute due to large data volumes or performance issues.
  Data Source Issues: There may be issues with the data source from which the InfoPackage is trying to extract data.
  Network Issues: Network latency or connectivity issues could be affecting the execution of the InfoPackage.
  Locking Issues: There may be locks on the data or objects that the InfoPackage is trying to access.
  Configuration Issues: Incorrect settings in the InfoPackage or the data source could lead to problems during execution.
  
  Solutions:
  
  Monitor the Process: Use transaction codes like SM37 to monitor the job status. Check if the job is still running or if it has failed.
  Check Logs: Review the application logs (transaction SLG1) for any error messages or warnings related to the InfoPackage execution.
  Performance Tuning: If the InfoPackage is taking too long, consider optimizing the data extraction process, such as filtering data or adjusting the extraction frequency.
  Data Source Verification: Ensure that the data source is available and functioning correctly. Test the connection to the data source.
  Check for Locks: Use transaction SM12 to check for any locks that might be preventing the InfoPackage from executing properly.
  Reconfigure the InfoPackage: If there are configuration issues, review the settings of the InfoPackage and make necessary adjustments.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SLG1: Application Log
  SM12: Lock Entries
  
  
  Documentation: Refer to SAP Help documentation for detailed information on InfoPackages and data extraction processes.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or bugs related to InfoPackages.
  
  If the problem persists after trying the above solutions, consider reaching out to your SAP Basis or BW support team for further assistance.