How To Fix 60479 - Comparative apartment & & is being processed by &

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 479

• Message text: Comparative apartment & & is being processed by &

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 60479 - Comparative apartment & & is being processed by & ?

  The SAP error message 60479 typically indicates that a comparative apartment (or comparative analysis) is currently being processed by another user or session. This can occur in various SAP modules, particularly in financial or controlling areas where comparative data is analyzed.
  Cause:
  
  Concurrent Processing: The error usually arises when two users or processes attempt to access or modify the same comparative apartment simultaneously.
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If one user is processing a comparative apartment, it locks that apartment for other users until the process is completed.
  Long-Running Processes: If a process is taking longer than expected, it may lead to this error if another user tries to access the same data.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user or process to complete its operation. After some time, try accessing the comparative apartment again.
  Identify the Lock: If you have the necessary authorizations, you can check which user or process is currently holding the lock. This can be done using transaction codes like SM12 (to view locks) or SM21 (to check system logs).
  Contact the User: If you identify the user who is holding the lock, you can reach out to them to see if they can complete their task or release the lock.
  System Administrator Intervention: If the lock persists and you cannot identify the user, you may need to contact your SAP system administrator. They can forcibly release the lock if necessary, but this should be done with caution to avoid data inconsistencies.
  Review Process Design: If this error occurs frequently, it may be worth reviewing the process design to minimize concurrent access to the same comparative apartments.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12, SM21, and SM37 (to check job status) for troubleshooting.
  User Training: Ensure that users are trained on how to properly access and process comparative apartments to minimize conflicts.
  System Performance: Monitor system performance to identify any long-running processes that may be causing locks.
  
  By following these steps, you should be able to resolve the error message 60479 and improve the efficiency of your SAP processes.