How To Fix AX148 - Technical lock in company code &1 could not be removed

SAP Error Message - Details

• Message type: E = Error

• Message class: AX - Asset Accounting XPRA messages

• Message number: 148

• Message text: Technical lock in company code &1 could not be removed

What causes this issue?

After successful completion of the conversion, the company code block
could <ZH>not</> be removed for one of the company codes in one of the
clients.
All company codes in a client are blocked before starting with the
conversion. Only when the conversion of the company code-dependent
tables has been executed successfully is the company code block
returned to the state it had before the conversion. This however
requires you to save the configuration data as it stands before the
conversion.
INCLUDE XPRA_1902_SEVERE_ERROR OBJECT DOKU ID TX

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AX148 - Technical lock in company code &1 could not be removed ?

  The SAP error message AX148 indicates that there is a technical lock in a specific company code that could not be removed. This typically occurs when a transaction or process is trying to access or modify data that is currently locked by another user or process. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Technical Lock: A technical lock is usually placed on a company code when a transaction is being processed. If the transaction is interrupted (e.g., due to a system crash, network issue, or user termination), the lock may not be released properly.
  Long-running Transactions: If a transaction takes too long to complete, it may lead to locks that are not released in a timely manner.
  User Sessions: Sometimes, user sessions may remain active even after the user has logged out, causing locks to persist.
  Background Jobs: Background jobs that are running may also hold locks on the company code.
  
  Solution:
  
  Identify the Lock: Use transaction code SM12 to view and manage locks. You can check for locks on the specific company code and identify the user or process that is holding the lock.
  Release the Lock: If you have the necessary authorizations, you can manually delete the lock entries in SM12. Be cautious when doing this, as it may affect ongoing processes.
  Check for Active Sessions: Use transaction code SM04 to check for active user sessions. If you find any sessions that are no longer needed, you can terminate them.
  Review Background Jobs: Use transaction code SM37 to check for any background jobs that may be running and holding locks. If necessary, you can cancel these jobs.
  System Restart: In some cases, a system restart may be required to clear persistent locks, but this should be done with caution and typically as a last resort.
  Consult Basis Team: If the issue persists, it may be necessary to consult your SAP Basis team for further investigation and resolution.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM04: User overview to check active sessions.
  SM37: Monitor background jobs.
  
  
  Authorization: Ensure you have the necessary authorizations to view and delete locks.
  Documentation: Refer to SAP Notes and documentation for specific details related to your version of SAP, as there may be version-specific considerations.
  
  Preventive Measures:
  
  Monitor Long-running Transactions: Regularly monitor transactions that take a long time to complete and optimize them if necessary.
  User Training: Train users to properly log out of sessions to avoid leaving locks behind.
  System Maintenance: Regularly perform system maintenance to ensure that locks are managed effectively.
  
  By following these steps, you should be able to resolve the AX148 error and prevent it from occurring in the future.