How To Fix RSM2726 - Request &1 (&2) is not available

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM2 - Monitor assistant help texts

• Message number: 726

• Message text: Request &1 (&2) is not available

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 RSM2726 - Request &1 (&2) is not available ?

  The SAP error message RSM2726, which states "Request &1 (&2) is not available," typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with data requests in InfoProviders, such as InfoCubes or DataStore Objects (DSOs). This error indicates that the specific data request you are trying to access is not available for processing.
  Causes:
  
  Request Deletion: The data request may have been deleted or not yet created. This can happen if the data load process was interrupted or if the request was manually deleted.
  Data Load Issues: There may have been issues during the data load process, leading to incomplete or failed requests.
  Request Status: The request might be in a status that does not allow it to be accessed, such as being in a "failed" state.
  Data Archiving: The request may have been archived or removed from the active data set due to data retention policies.
  Incorrect Request ID: The request ID being referenced may be incorrect or not exist in the system.
  
  Solutions:
  
  Check Request Status: Go to the relevant InfoProvider and check the status of the request. Ensure that it is not in a failed state.
  Reprocess the Data Load: If the request was not created due to a failed data load, try reprocessing the data load to generate the request again.
  Verify Request ID: Ensure that the request ID you are using is correct. You can check the list of requests in the relevant InfoProvider.
  Check for Deletion: If the request was deleted, you may need to reload the data to create a new request.
  Review Data Archiving: If the request has been archived, you may need to restore it or adjust your data retention settings.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context on the issue.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to monitor and manage data requests.
  Data Load Monitoring: Use transaction RSMO to monitor the status of data loads and requests.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for RSM2726 in the SAP Support Portal.
  Documentation: Refer to SAP Help documentation for more details on data requests and InfoProviders.
  
  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.