How To Fix RSM1360 - Too many requests/too much data selected for activation; see long text

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 360

• Message text: Too many requests/too much data selected for activation; see long text

What causes this issue?

You have selected too many requests for activation in the DataStore
object&V1& .
&V2& requests with a total of&V3& records have been selected. This
would result in &V4& activation packages. However a maximum of 100,000
activation packages is allowed.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Select fewer requests for activation in one activation step.

Procedure for System Administrators

The number of activation packages can be calculated using this formula:
<(><<)>Number of Requests> * <(><<)>Sum of All Records for these
Requests> / <(><<)>Package Size for this Activation Step>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM1360 - Too many requests/too much data selected for activation; see long text ?

  The SAP error message RSM1360, which states "Too many requests/too much data selected for activation; see long text," typically occurs during the activation of data in the SAP system, particularly in the context of the SAP BW (Business Warehouse) or SAP BW/4HANA environments. This error indicates that the system is trying to process too many requests or a large volume of data at once, which can lead to performance issues or exceed system limits.
  Causes:
  
  Excessive Data Volume: The activation process is attempting to handle a large amount of data, which can overwhelm the system's resources.
  Too Many Requests: There may be multiple requests queued for activation, leading to a bottleneck.
  System Configuration: The system may not be optimally configured to handle the volume of data being processed.
  Locks or Deadlocks: Other processes may be locking the data or causing deadlocks, preventing the activation from completing successfully.
  
  Solutions:
  
  
  Reduce Data Volume: 
  
  Try to limit the amount of data being activated at one time. This can be done by filtering the data or breaking it into smaller batches.
  If possible, schedule the activation during off-peak hours to reduce the load on the system.
  
  
  
  Check and Manage Requests:
  
  Monitor the requests in the process chain and ensure that there are not too many requests queued for activation.
  If there are multiple requests, consider processing them sequentially rather than in parallel.
  
  
  
  System Configuration:
  
  Review the system settings and parameters related to data processing and activation. Adjusting parameters such as memory allocation or process limits may help.
  Ensure that the system has adequate resources (CPU, memory, etc.) to handle the data load.
  
  
  
  Error Logs and Monitoring:
  
  Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Use transaction RSMO to monitor the status of the data requests and identify any that are stuck or causing issues.
  
  
  
  Reprocess the Data:
  
  If the activation fails, you may need to delete the failed requests and reprocess the data from the source.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes that may address this specific error or provide guidance on best practices for data activation in your version of SAP.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  RSMO: Monitor Data Activation
  SLG1: Display Application Log
  
  
  Performance Tuning: Consider reviewing SAP's best practices for performance tuning in BW environments, which may include optimizing data models, indexes, and queries.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying these solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.