How To Fix 60279 - Building "& &" is being processed by "&"

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 279

• Message text: Building "& &" 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 60279 - Building "& &" is being processed by "&" ?

  The SAP error message 60279 indicates that a building (or object) is currently being processed by another user or session. This typically occurs in scenarios where multiple users or processes are trying to access or modify the same object simultaneously, leading to a lock situation.
  Cause:
  
  Concurrent Access: Another user or process is currently working on the same building or object, which causes a lock.
  Long-running Transactions: A transaction that takes a long time to complete may hold the lock longer than expected.
  System Configuration: Certain configurations in the SAP system may lead to more frequent locking situations.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Lock: Use transaction code SM12 to check for locks. You can see which user or session is holding the lock on the building. If necessary, you can ask the user to release the lock.
  Terminate the Session: If the session holding the lock is no longer active or is stuck, you may need to terminate it using transaction SM50 or SM66 (for global processes).
  Check for Long-running Processes: Investigate if there are any long-running processes that may be causing the lock and address them accordingly.
  System Configuration Review: If this issue occurs frequently, consider reviewing the system configuration and locking mechanisms to optimize performance and reduce locking conflicts.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage locks.
  SM50: Monitor active processes.
  SM66: Monitor global processes.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for best practices on handling locks and concurrent access in your specific module or application.
  
  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.