Do you have any question about this error?
Stop Googling SAP errors. Use our Free Essentials plan instead - instant AI help, no credit card needed. Start Now →
Message type: E = Error
Message class: TR - Change and Transport System
Message number: 828
Message text: Caution: & is locked; move the object instead of deleting it
Caution: When you delete this object from the request, the old version
(active before your changes) is not recovered, which means that
Transport Organizer does not record the current state.
If there are dependencies between the changes you have made and the
other objects in the request, you may encounter inconsistencies when you
transport the request into other systems.
The system allows you to delete any superfluous objects.
Make sure that you can transport the request consistently without this
object.
Place the object in another request so that any changes you make to it
can be recorded and transported.
It is advisable, however, to move the object to a different request
instead of deleting it. When to record the object later in a different
request, a new version is written.
This can produce errors, for example when creating correction
instructions.
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.
TR828
- Caution: & is locked; move the object instead of deleting it ?The SAP error message TR828 indicates that a transport request (TR) is locked, and it advises against deleting the object in question. Instead, it suggests moving the object to a different transport request. This error typically arises in the context of transport management within SAP, where objects (like programs, function modules, etc.) are moved between different systems (development, quality assurance, production).
Cause:
Locked Transport Request: The transport request you are trying to modify or delete is currently locked. This can happen if:
- The transport request is being used by another user or process.
- The transport request is in a status that does not allow modifications (e.g., released).
- There are pending changes or dependencies that prevent the deletion.
Object Dependencies: The object you are trying to delete may have dependencies on other objects that are also part of the transport request.
Solution:
Check Lock Status:
- Use transaction code
SE03
(Transport Organizer Tools) to check the status of the transport request and see if it is locked by another user or process.- You can also use transaction
SM12
to check for locks in the system.Release or Unlock the Transport Request:
- If you have the necessary authorizations, you can unlock the transport request or release it if it is in a modifiable state.
- If another user is using the transport request, coordinate with them to resolve the lock.
Move the Object:
- Instead of deleting the object, you can move it to another transport request. This can be done by:
- Using transaction
SE09
orSE10
to manage transport requests.- Selecting the object and choosing the option to move it to a different transport request.
Consult Documentation:
- Review SAP documentation or consult with your SAP Basis team for specific procedures related to transport management in your organization.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis administrator or support team for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
TR827
Request & is protected and belongs to user & (not modifiable)
What causes this issue? Request &V1& has protected status and belongs to user &V2&. This means that you cannot change this request.Sy...
TR825
Request number cannot be changed as there are locked obj. in request/task
What causes this issue? The transport request for your task &V1& cannot be changed because it contains objects with request locks. Different ...
TR829
Save the object list before you delete locked objects
What causes this issue? A locked object cannot be deleted from a (correction/transport/...) request, because the request has status <ZH>not sav...
TR830
Invalid key entry: &1 &2 &3 &4
What causes this issue? In table TADIR, object &V1& is flagged as locked for &V2& but no such correction exists. This means that an i...
Click on this link to search all SAP messages.