Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TR_AUSL - Software Delivery Composer Messages
Message number: 111
Message text: Delivery &1 is locked by user &2 (no change possible)
Delivery &V1& is currently being edited by user &V2& and is locked.
You cannot change the delivery &V1&. The function terminates.
Contact user &V2&. As soon as the lock on delivery &V1& is lifted you
can repeat the function.
<ZH>Note:</>
Use transaction <DS:TRAN.SM12>SM12</> to display the lock. Select the
user name &V2& to restrict the display.
Error message extract from SAP system. Copyright SAP SE.
TR_AUSL111
- Delivery &1 is locked by user &2 (no change possible) ?The SAP error message TR_AUSL111 indicates that a delivery document (identified by &1) is currently locked by a user (identified by &2), which prevents any changes from being made to that delivery. This is a common issue in SAP systems, particularly in environments where multiple users may be accessing and modifying documents simultaneously.
Cause:
- User Lock: The delivery document is being edited or processed by another user, which results in a lock being placed on the document to prevent conflicting changes.
- Transaction in Progress: A transaction related to the delivery is still in progress, and the system has locked the document until the transaction is completed.
- System Error: Occasionally, a system error or an unexpected termination of a session can leave a document in a locked state.
Solution:
- Wait and Retry: If the lock is due to another user actively working on the document, the simplest solution is to wait until that user has completed their work and released the lock.
- Identify the Locking User: You can use transaction code SM12 to view and manage locks in the system. This transaction allows you to see which user is holding the lock on the delivery document.
- Enter the delivery document number in the appropriate field and execute the transaction.
- Identify the user who has locked the document.
- Contact the Locking User: If possible, contact the user who is holding the lock to determine if they can release it or if they are finished with their changes.
- Release the Lock (if necessary): If the locking user is unavailable and you have the necessary authorizations, you can manually delete the lock using transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on the document.
- Check for Background Jobs: Sometimes, background jobs may also lock documents. Check transaction SM37 to see if any background jobs are running that might be affecting the delivery document.
- System Restart: In rare cases, if the lock persists and cannot be resolved through the above methods, a system restart may be necessary to clear any lingering locks.
Related Information:
By following these steps, you should be able to resolve the TR_AUSL111 error and regain access to the locked delivery document.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR_AUSL110
Exclusion list &1 has not been released
What causes this issue? This function requires an exclusion list whose contents cannot be changed anymore. This occurs when you release exclusion lis...
TR_AUSL109
Change request &1 has already been included: You cannot exclude it
What causes this issue? The change request or piece list &V1& that you want to exclude is already included in the delivery request &V2&am...
TR_AUSL112
Unreleased requests are not flagged (see delivery log)
What causes this issue? You can flag only released change requests (or piece lists) for inclusion in delivery requests. However, you have selected un...
TR_AUSL113
Flag change requests: Not possible for &1
What causes this issue? You cannot <LS>flag change requests</> for delivery requests of type <ZH>&V1&</>.System Respo...
Click on this link to search all SAP messages.