How To Fix RSM1323 - No extractor defined for DS '&' and SS '&' - cannot create InfoPackage

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)

• Message number: 323

• Message text: No extractor defined for DS '&' and SS '&' - cannot create InfoPackage

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 RSM1323 - No extractor defined for DS '&' and SS '&' - cannot create InfoPackage ?

  The SAP error message RSM1323 indicates that there is no extractor defined for the specified DataSource (DS) and the corresponding source system (SS). This error typically occurs when you are trying to create an InfoPackage for a DataSource that has not been properly configured or activated in the SAP system.
  Cause:
  
  Missing Extractor: The DataSource you are trying to use does not have an associated extractor defined in the source system.
  Incorrect Configuration: The DataSource might not be correctly configured in the SAP BW system.
  Deactivated DataSource: The DataSource may have been deactivated or not yet activated in the source system.
  Transport Issues: If the DataSource was recently transported from another system, it may not have been properly activated in the target system.
  
  Solution:
  
  
  Check DataSource Configuration:
  
  Go to the DataSource in the SAP BW system (transaction code RSA1).
  Navigate to the DataSources section and check if the DataSource is active and properly configured.
  
  
  
  Activate the DataSource:
  
  If the DataSource is not active, activate it by selecting the DataSource and choosing the "Activate" option.
  
  
  
  Check Source System:
  
  Ensure that the source system is correctly defined and connected in the SAP BW system.
  Use transaction code RSA1 to check the source system settings.
  
  
  
  Check Extractor in Source System:
  
  If you have access to the source system, check if the extractor is available and functioning correctly.
  Use transaction codes like RSA3 to test the extractor and see if it retrieves data.
  
  
  
  Transport Issues:
  
  If the DataSource was recently transported, ensure that all necessary objects were included in the transport request and that they were activated in the target system.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific DataSource for any additional configuration steps that may be required.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  RSA1: Data Warehousing Workbench
  RSA3: Test DataSource
  RSC1: Create DataSource
  RSC2: Change DataSource
  RSC3: Display DataSource
  
  
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide additional guidance on the specific DataSource you are working with.
  
  
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to resolve the RSM1323 error and successfully create your InfoPackage.