How To Fix AX147 - Technical lock in company code &1 could not be set

SAP Error Message - Details

• Message type: E = Error

• Message class: AX - Asset Accounting XPRA messages

• Message number: 147

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

What causes this issue?

It was <ZH>not</> possible to block one of the company codes in one of
the clients before you started the conversion.
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 AX147 - Technical lock in company code &1 could not be set ?

  The SAP error message AX147, which states "Technical lock in company code &1 could not be set," typically occurs when there is an issue with setting a technical lock for a specific company code during a transaction. This can happen in various scenarios, such as during posting, closing periods, or executing certain financial transactions.
  Causes:
  
  Database Lock Issues: The system may be unable to set a lock due to existing locks on the database, possibly from other users or processes.
  Authorization Issues: The user may not have the necessary authorizations to set a lock for the specified company code.
  System Configuration: There may be configuration issues in the system that prevent the lock from being set.
  Technical Errors: There could be underlying technical issues, such as problems with the database or application server.
  
  Solutions:
  
  Check for Existing Locks: Use transaction code SM12 to check for existing locks on the company code. If there are locks that are no longer needed, they can be deleted (if you have the necessary authorizations).
  Review User Authorizations: Ensure that the user has the appropriate authorizations to perform the action that is causing the error. This may involve checking roles and profiles assigned to the user.
  System Configuration Review: Consult with your SAP Basis or technical team to review the system configuration and ensure that everything is set up correctly for locking mechanisms.
  Restart the Transaction: Sometimes, simply restarting the transaction or logging out and back into the system can resolve temporary issues.
  Check for Background Jobs: If there are background jobs running that might be locking the company code, you may need to wait for those jobs to complete or coordinate with the job owners.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (for lock entries), SM21 (for system logs), and ST22 (for dump analysis) to help diagnose the issue.
  SAP Support: If the issue persists, consider reaching out to SAP Support for further assistance, especially if it appears to be a bug or a more complex technical issue.
  Documentation: Review SAP documentation related to locking mechanisms and company code settings for additional insights.
  
  By following these steps, you should be able to identify the cause of the AX147 error and implement a suitable solution.