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

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

    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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker