How To Fix RSM613 - Further update of request from PSA started

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 613

• Message text: Further update of request from PSA started

What causes this issue?

The continued processing of requests from PSA into the final data
target is triggered.

System Response

A batch job is scheduled that reads the data from the PSA, and posts it
into the final data target. This target has already been determined
with the data request into the PSA.

How to fix this error?

Regularly refresh the monitor display to keep up-to-date about status
changes.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSM613 - Further update of request from PSA started ?

  The SAP error message RSM613 ("Further update of request from PSA started") typically occurs in the context of data extraction and loading processes in SAP BW (Business Warehouse). This message indicates that a request is currently being processed in the PSA (Persistent Staging Area), and another update attempt is being made for the same request, which is not allowed.
  Cause:
  
  
  Concurrent Processing: The error usually arises when multiple processes are trying to update the same request in the PSA simultaneously. This can happen if:
  
  A data load process is still running.
  A previous request has not yet completed its update to the InfoCube or DataStore Object (DSO).
  
  
  
  Long Running Processes: If a data load takes longer than expected, subsequent attempts to process the same request can trigger this error.
  
  
  Locking Issues: SAP uses locks to manage concurrent access to data. If a request is locked by one process, another process trying to access it will encounter this error.
  
  
  Solution:
  
  
  Check Running Processes: Use transaction codes like SM37 (Job Monitoring) to check if there are any active jobs related to the data load. If a job is still running, you may need to wait for it to complete.
  
  
  Monitor PSA: Use transaction RSA1 to monitor the PSA and see the status of the requests. Ensure that no other processes are trying to update the same request.
  
  
  Cancel or Restart: If a process is stuck or taking too long, you may need to cancel it and restart the data load. Be cautious with this approach, as it may lead to data inconsistencies.
  
  
  Check for Locks: Use transaction SM12 to check for any locks on the request. If you find locks that are no longer needed, you can release them.
  
  
  Batch Processing: If you frequently encounter this issue, consider adjusting your batch processing strategy to avoid overlapping requests.
  
  
  System Performance: If the issue is related to system performance, consider optimizing your data load processes or increasing system resources.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  RSA1: Data Warehousing Workbench
  SM37: Job Monitoring
  SM12: Lock Entries
  RSMO: Monitor Data Load
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  
  
  Documentation: Review SAP BW documentation for best practices on data loading and handling PSA requests.
  
  
  By following these steps, you should be able to resolve the RSM613 error and ensure smoother data loading processes in your SAP BW environment.