How To Fix 60123 - Collective lease-out &1 currently blocked by &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 123

• Message text: Collective lease-out &1 currently blocked by &2

What causes this issue?

The data for the collective rental agreement is being processed by
another user at present.

System Response

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

How to fix this error?

Select another rental agreement number for processing or try and call
up the blocked agreement at a later date.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 60123 - Collective lease-out &1 currently blocked by &2 ?

  The SAP error message 60123, which states "Collective lease-out &1 currently blocked by &2," typically occurs in the context of asset management, particularly when dealing with collective lease-outs in SAP Asset Accounting (FI-AA). This error indicates that a specific collective lease-out is currently locked or blocked by another process or user, preventing the current transaction from proceeding.
  Cause:
  
  Concurrent Access: Another user or process is currently accessing or modifying the same collective lease-out, leading to a lock.
  Incomplete Transactions: A previous transaction involving the collective lease-out may not have been completed properly, leaving it in a locked state.
  System Configuration: There may be configuration settings that are causing the lease-out to be blocked under certain conditions.
  
  Solution:
  
  Check for Locks: Use transaction code SM12 to check for any locks on the collective lease-out. You can identify the user or process that is holding the lock and take appropriate action.
  Wait and Retry: If the lock is temporary (e.g., another user is processing the lease-out), you may need to wait for the other transaction to complete and then retry your action.
  Contact the User: If you identify a specific user holding the lock, you can reach out to them to see if they can release the lock or complete their transaction.
  System Administration: If the issue persists, it may require intervention from a system administrator to release the lock or investigate further into the system's behavior.
  Review Configuration: Check the configuration settings related to asset management and lease-outs to ensure they are set up correctly.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view locks), SE11 (to check table definitions), and SE80 (to analyze program behavior).
  SAP Notes: Look for SAP Notes related to error message 60123 for any patches or updates that may address known issues.
  Documentation: Review SAP documentation on Asset Accounting and lease management for best practices and troubleshooting steps.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or refer to SAP's official support channels for further assistance.