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

  • Show details Hide details
  • 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

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant