How To Fix RSM790 - Hier./attr. change cannot be started again as one is currently running

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 790

• Message text: Hier./attr. change cannot be started again as one is currently running

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 RSM790 - Hier./attr. change cannot be started again as one is currently running ?

  The SAP error message RSM790 indicates that a hierarchical or attribute change process is already running in the system, and therefore, a new change cannot be initiated until the current process is completed. This error typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when dealing with InfoObjects, InfoProviders, or other data modeling elements.
  Cause:
  
  Concurrent Processes: The most common cause of this error is that a previous hierarchical or attribute change process is still in progress. This can happen if a long-running process is taking more time than expected.
  System Lock: The system may have a lock on the object being modified, preventing any new changes from being initiated.
  Background Jobs: There may be background jobs that are executing changes to the same hierarchy or attributes.
  
  Solution:
  
  
  Check Running Processes: 
  
  Use transaction code SM37 to check for any running jobs related to the hierarchy or attribute changes. Look for jobs that are in the "active" state.
  If you find a job that is stuck or taking too long, you may need to analyze it further or terminate it if appropriate.
  
  
  
  Wait for Completion: If you identify that a process is running, the simplest solution is to wait for it to complete. Once the current process finishes, you should be able to start your change.
  
  
  System Monitoring: 
  
  Use transaction RSMO (for monitoring) to check the status of the process.
  If the process is taking too long, you may need to investigate the underlying cause (e.g., performance issues, data volume).
  
  
  
  Terminate Stuck Processes: If you determine that a process is stuck and not progressing, you can terminate it using transaction SM37. Be cautious with this approach, as terminating a process can lead to data inconsistencies.
  
  
  Check for Locks: 
  
  Use transaction SM12 to check for any locks on the objects you are trying to modify. If you find locks that are no longer needed, you can delete them.
  
  
  
  System Restart: In extreme cases, if the system is unresponsive and you cannot identify the cause, a system restart may be necessary. However, this should be done with caution and typically as a last resort.
  
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Job Monitoring
  RSMO: Process Monitoring
  SM12: Lock Entries
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  Performance Tuning: If this error occurs frequently, consider reviewing the performance of your BW system and optimizing data loads and processes.
  
  By following these steps, you should be able to resolve the RSM790 error and successfully initiate your hierarchical or attribute changes in SAP.