How To Fix RSM579 - No IDocs found for this request in the Business Information Warehouse


SAP Error Message - Details

  • Message type: E = Error

  • Message class: RSM -

  • Message number: 579

  • Message text: No IDocs found for this request in the Business Information Warehouse

  • Show details Hide details


  • 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 RSM579 - No IDocs found for this request in the Business Information Warehouse ?

    The SAP error message RSM579: No IDocs found for this request typically occurs in the context of the Business Information Warehouse (BW) when there is an issue with the extraction of data from the source system, particularly when using IDocs (Intermediate Documents) for data transfer.

    Causes:

    1. No IDocs Generated: There may not be any IDocs generated for the specific request you are trying to process. This can happen if the data extraction process did not run successfully or if there were no changes in the source system that would trigger IDoc generation.

    2. IDoc Status Issues: The IDocs that were generated may not be in a status that allows them to be processed. For example, they could be in an error status or not yet processed.

    3. Selection Criteria: The selection criteria used in the data extraction process may be too restrictive, resulting in no IDocs being selected.

    4. Technical Issues: There could be technical issues in the connection between the source system and the BW system, such as network issues or configuration problems.

    5. Data Transfer Process (DTP) Issues: If you are using a DTP to load data, there may be issues with the DTP configuration or execution.

    Solutions:

    1. Check IDoc Generation: Verify if IDocs are being generated in the source system. You can use transaction WE02 or WE05 to check for IDocs related to your request.

    2. Review IDoc Status: If IDocs are generated, check their status. Ensure that they are in a status that allows processing (e.g., status 03 for "completed").

    3. Adjust Selection Criteria: Review and possibly adjust the selection criteria in your data extraction process to ensure that it is not too restrictive.

    4. Monitor Data Transfer Process: If using a DTP, check the DTP settings and monitor its execution. Ensure that it is configured correctly and that there are no errors in the DTP execution logs.

    5. Check for Technical Issues: Investigate any potential technical issues that may be affecting the connection between the source system and BW. This may involve checking network connectivity, RFC connections, and system logs.

    6. Re-run the Extraction: If necessary, re-run the extraction process in the source system to generate new IDocs.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02, WE05 (for IDoc monitoring), RSA1 (for BW modeling), and RSMO (for monitoring data loads).
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to IDoc processing or BW data extraction.
    • Documentation: Review SAP documentation for best practices on IDoc handling and BW data extraction processes.

    By following these steps, you should be able to diagnose and resolve the issue related to the RSM579 error message in SAP BW.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant