The basic meaning: your system won't let you edit certain settings
When you see "locked for adding/changing delivery objects like BSP applications" in SAP, it means your system administrator has restricted who can create or modify certain types of software components. The lock prevents changes to delivery objects — the packages and applications that SAP uses to organize code — without explicit permission or a specific process.
This is a safety feature, not a bug. It stops accidental changes to critical system parts and keeps track of who changed what and when. If you're trying to make a change and hit this message, you either need higher access rights, or you need to follow your organization's change management process.
Key Takeaways
- A delivery object lock prevents anyone without the right permissions from editing SAP packages, applications, or code components.
- BSP applications are web-based programs that run inside SAP; locking them keeps people from accidentally breaking production systems.
- The lock is set by your system administrator and usually requires a formal change request to override.
- You can see which objects are locked and who locked them by checking the transport system or asking your basis team.
What delivery objects are and why they get locked
A delivery object in SAP is any piece of code, configuration, or process that belongs to a package. This includes programs, reports, web pages, database tables, and function modules. When you bundle these together, they form what SAP calls a "delivery unit" — a package you can move from one system to another.
BSP applications are one type of delivery object. BSP stands for Business Server Page, and it's SAP's way of building web interfaces that sit inside the system. A BSP process might be a form for entering data, a dashboard, or a tool for checking inventory. Because these applications run live in your production system and other people depend on them, SAP locks them by default to prevent someone from editing them without going through the proper steps.
The lock applies to the entire object or package, not just one person's changes. Once locked, nobody can add new objects to that package or change existing ones — not even the person who created it — unless they have the right role or submit a change request.
Who sets the lock and how it works
Your basis administrator or system administrator sets delivery object locks. They do this through the SAP transport system, which is the tool SAP uses to move changes between systems (development, testing, production). The transport system tracks every change, who made it, and when.
When an object is locked, the system records it in what's called the "transport layer." If you try to edit a locked object, SAP shows you the error message and stops you. The lock stays in place until someone with the right access removes it or approves your change through the transport request process.
Most organizations lock production objects automatically. Development objects are usually unlocked so developers can work freely. Testing objects might be partially locked depending on the phase of testing. This layered approach keeps people from accidentally breaking live systems while still letting teams develop and test new features.
How to request a change to a locked object
If you need to edit a locked delivery object, the first step is to contact your basis team or system administrator. Tell them which object you want to change and why. They will either unlock it temporarily, or they will create a transport request — a formal record of the change that tracks who did what and when.
A transport request is a container for changes. You make your edits inside the transport request, and then the basis team reviews it, tests it, and moves it to production if it passes. This process protects the system because every change is documented and reversible if something goes wrong.
Some organizations require a change ticket from a separate system (like Jira or ServiceNow) before they will unlock an object. Others have a standing list of people who can request unlocks. Ask your basis team what your organization's process is — it varies widely.
The difference between locked and unlocked objects
An unlocked object can be edited by anyone with developer access. Changes go directly into the system without a transport request. This is fine for development systems where people are still building and testing, but it's dangerous in production because there's no review step and no straightforward way to undo a bad change.
A locked object requires a transport request. You can still edit it, but your edits are captured in a formal change record. The basis team can review the change, test it in a staging system, and then move it to production with confidence. If the change breaks something, they can roll it back using the transport system.
Some objects are locked in production but unlocked in development. This is the standard setup: developers work freely in development, changes get tested in a test system, and then locked changes move to production through the transport system. This separation keeps the live system stable while letting teams innovate.
What happens if you ignore the lock message
You cannot ignore the lock. SAP will not let you save changes to a locked object, period. The system enforces it at the database level, so there's no workaround or backdoor. If you try to edit a locked object, you will get the error message and your changes will not be saved.
This is intentional. The lock is there to protect the system, and SAP makes it impossible to bypass. The only way forward is to go through the proper channel: ask your basis team to unlock it, submit a change request, or wait for the scheduled maintenance window when locks are temporarily removed.
Common reasons the lock appears
You might see this message if you are trying to edit a production object from a development system. Production objects are usually locked to prevent accidental changes. The fix is to make your changes in the development system (where the object is unlocked), test them, and then move them to production through the transport system.
You might also see it if your access role does not include the permission to edit that particular package or object type. This is common if you are new to a team or if you moved to a different project. Ask your basis team to check your roles and add the right one if you need it.
Sometimes the lock appears because the object is in the middle of a transport. If someone else is moving changes to production, the object might be temporarily locked. Wait for the transport to finish and try again.
Frequently Asked Questions
Can I unlock a delivery object myself?
No. Only your basis administrator or someone with the ABAP_EDIT_SYS role can unlock delivery objects. This is a security feature to prevent unauthorized changes. Contact your basis team and explain what you need to change and why.
What is the difference between a locked object and a read-only object?
A locked object prevents you from making changes at all. A read-only object lets you view it but not edit it. Both stop you from saving changes, but the reason is different. A lock is about change control; read-only is about permissions.
Does the lock explore to everyone or just me?
The lock applies to everyone except people with specific roles or explicit permission from the basis team. If one person can edit a locked object, it is usually because they have a higher access level or they submitted a formal change request.
How long does it take to get a locked object unlocked?
It depends on your organization's process. Some teams unlock objects in minutes if you have a valid reason. Others require a change ticket and a review period that can take days. Ask your basis team what the typical timeline is for your system.
Can I make a copy of a locked object and edit the copy instead?
Yes, usually. You can create a new object with a different name and edit that one freely. However, this creates a duplicate that you will have to maintain separately. It is better to go through the proper unlock process so you are editing the original object that other people depend on.