How To Fix RSDTM122 - New InfoPackage could not be generated with reference "&1" ("&2").

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDTM - Data Mining Connection Messages

• Message number: 122

• Message text: New InfoPackage could not be generated with reference "&1" ("&2").

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 RSDTM122 - New InfoPackage could not be generated with reference "&1" ("&2"). ?

  The SAP error message RSDTM122 indicates that a new InfoPackage could not be generated with reference to a specific object. This error typically occurs in the context of data extraction processes in SAP BW (Business Warehouse) when trying to create an InfoPackage for data loading.
  Causes:
  
  Missing or Inactive DataSource: The DataSource referenced in the InfoPackage may not be active or may not exist.
  Incorrect Source System Configuration: The source system from which data is being extracted may not be properly configured or connected.
  Authorization Issues: The user may not have the necessary authorizations to create or modify InfoPackages.
  Technical Issues: There may be underlying technical issues, such as problems with the BW system or the source system.
  Incorrect InfoSource or DataTarget: The InfoSource or DataTarget associated with the InfoPackage may not be correctly defined or may have issues.
  
  Solutions:
  
  Check DataSource Status: Verify that the DataSource referenced in the error message is active. You can do this by navigating to the DataSource in the SAP BW system and checking its status.
  Validate Source System Configuration: Ensure that the source system is correctly configured and that the connection is active. You can check this in the SAP BW system under the source system settings.
  Review Authorizations: Make sure that the user attempting to create the InfoPackage has the necessary authorizations. This may involve checking roles and permissions in the SAP system.
  Check for Technical Issues: Look for any technical issues in the BW system or the source system that may be causing the problem. This could involve checking logs or system messages for errors.
  Inspect InfoSource and DataTarget: Ensure that the InfoSource and DataTarget are correctly defined and that there are no inconsistencies. You may need to check the settings and mappings associated with them.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to manage DataSources and InfoPackages.
  Logs and Traces: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to SAP documentation for BW data extraction processes for more detailed guidance on InfoPackages and DataSources.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation.