How To Fix RSM668 - Hierarchy loading not possible as hier./attr. is currently running

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 668

• Message text: Hierarchy loading not possible as hier./attr. 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 RSM668 - Hierarchy loading not possible as hier./attr. is currently running ?

  The SAP error message RSM668 indicates that a hierarchy or attribute is currently being processed, which prevents the loading of data into the InfoObject. This typically occurs in the context of SAP BW (Business Warehouse) when you are trying to load data into a hierarchy or attribute that is locked due to an ongoing process.
  Cause:
  
  Concurrent Processing: The most common cause of this error is that another process is currently running that is modifying the hierarchy or attribute. This could be a data load, a hierarchy update, or a similar operation.
  Long-Running Processes: If a previous process is taking longer than expected, it may lock the hierarchy or attribute, leading to this error.
  System Locking Mechanism: SAP uses a locking mechanism to ensure data integrity. If a hierarchy or attribute is locked, other processes cannot access it until the lock is released.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait for the current process to complete. You can monitor the process in the SAP BW system to see if it is still running.
  Check Process Chains: If you are using process chains, check if there are any active processes that might be locking the hierarchy or attribute. You can do this in the process chain monitor.
  Transaction SM37: Use transaction SM37 to check for any background jobs that might be running and causing the lock. If you find a job that is stuck or taking too long, you may need to analyze or terminate it.
  Transaction SM12: You can also check for locks using transaction SM12. This will show you any locks that are currently held in the system. If you find a lock that is no longer needed, you can delete it (be cautious with this approach, as it may lead to data inconsistencies).
  Re-run the Load: Once the current process has completed and the lock is released, you can re-run your data load.
  
  Related Information:
  
  Monitoring Tools: Familiarize yourself with monitoring tools in SAP BW, such as the process chain monitor and job monitoring (SM37).
  Performance Tuning: If you frequently encounter this issue, consider reviewing the performance of your data loads and hierarchy updates to optimize their execution time.
  Documentation: Refer to SAP documentation for more details on hierarchy management and data loading processes in BW.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.