Delete modifiable transport with locked objects (SE10)

Dear Forum,
I have a request from a developer who wishes to have a transport deleted from SE10. the transport is in status modifiable, but it has locked objects. So when i try to delete the transport the system warns me that "Request/task XXXK900962 cannot be deleted because it contains locked objects".
What is the "SAP Best Practice" way to get rid of this transport? Please explain in detail.
Any input will be greatly appreciated!
Thanks in advance,
Kind Regards,
Soren

Hello Eric,
I am facing an issue after deleting a repair object in the task.
I could not add this entry in the task as it is not allowing. The object type is as below
R3TR MCIN S901 (Its a change to info structure from SPRO - IMG activity)
Now when I want to change the object, it is giving error.
When I want to add same obj in the repair task manually it is not allowing.
Can you please give me any suggestion.
I believe as you said, when I delete a locked object, the traces that the object has been changed are deleted and hence it is giving the error.
Is there any way to manually restore the object?
Can I add the object using TR_APPEND_TO_COMM_OBJS_KEYS?
Regards,
Pratyusha

Similar Messages

How to delete a transport request easily?

Hi Gurus,
I need to delete a transport request. Unfortunately, I received an error that says
"Request/task BWDK903562 cannot be deleted because it contains locked objects".
So, in order to delete that transport request, I have to first delete all objects contained in that request. However, there are just too many of them if I were to do it manually one-by-one.
Is there any approach where I could delete this transport request easily without first deleting all objects contained in that request?
Thanks you in advance.

Hi Fulham,
A transport request cannot be deleted with locked objects. So you have to first unlock the objects in the request. To do this: SE03 --> Request Task --> Unlock Objects.
The in SE10 select the request you want to delete and expand. Then right click on the sub node of the request and delete. Then Select the main request and delete.
Hope this helps.
Bhargava

Implementing lock object

I've a TCode to modify a report. That TCode picks a doc no. from a table & opens up an editable ALV based on that doc. no .That doc. no. is the only primary key.
I want that if someone is already opened that report, & if someoen else is trying to open that report, it shouldn't open & should show that -"its locked by User XXX". I've made a lock object for that table. Please advise what to do next. How to populate the User name who has locked the report.

used ENQUEUE function and DEQUEUE function
Function Modules for Lock Requests
Activating a lock object in the ABAP Dictionary automatically creates function modules for setting (ENQUEUE_<lock object name>) and releasing (DEQUEUE_<lock object name>) locks.
The generated function modules are automatically assigned to function groups. You should not change these function modules and their assignment to function groups since the function modules are generated again each time the lock object is activated.
Never transport the function groups, which contain the automatically generated function modules. The generated function modules of a lock object could reside in a different function group in the target system. Always transport the lock objects. When a lock object is activated in the target system, the function modules are generated again and correctly assigned to function groups.
Parameters of the Function Modules
Field Names of the Lock Object
The keys to be locked must be passed here.
A further parameter X_<field> that defines the lock behavior when the initial value is passed exists for every lock field <field>. If the initial value is assigned to <field> and X_<field>, then a generic lock is initialized with respect to <field>. If <field> is assigned the initial value and X_<field> is defined as X, the lock is set with exactly the initial value of <field>.
Parameters for Passing Locks to the Update Program
A lock is generally removed at the end of the transaction or when the corresponding DEQUEUE function module is called. However, this is not the case if the transaction has called update routines. In this case, a parameter must check that the lock has been removed.
Parameter _SCOPE controls how the lock or lock release is passed to the update program (see The Owner Concept for Locks). You have the following options:
ｷ        _SCOPE = 1: Locks or lock releases are not passed to the update program. The lock is removed when the transaction is ended.
ｷ        _SCOPE = 2: The lock or lock release is passed to the update program. The update program is responsible for removing the lock. The interactive program with which the lock was requested no longer has an influence on the lock behavior. This is the standard setting for the ENQUEUE function module.
ｷ        _SCOPE = 3: The lock or lock release is also passed to the update program. The lock must be removed in both the interactive program and in the update program. This is the standard setting for the DEQUEUE function module.
Parameters for Lock Mode
A parameter MODE_<TAB> exists for each base table TAB of the lock object. The lock mode for this base table can be set dynamically with this parameter. The values allowed for this parameter are S (read lock), E (write lock), X (extended write lock), and O (optimistic lock).
The lock mode specified when the lock object for the table is created is the default value for this parameter. This default value can, however, be overridden as required when the function module is called.
If a lock set with a lock mode is to be removed by calling the DEQUEUE function module, this call must have the same value for the parameter MODE_<TAB>.
Controlling Lock Transmission
Parameter _COLLECT controls whether the lock request or lock release should be performed directly or whether it should first be written to the local lock container. This parameter can have the following values:
ｷ        Initial Value: The lock request or lock release is sent directly to the lock server.
ｷ        X: The lock request or lock release is placed in the local lock container. The lock requests and lock releases collected in this lock container can then be sent to the lock server at a later time as a group by calling the function module FLUSH_ENQUEUE.
Whenever you have lock mode X (extended write lock), locks should not be written to the local lock container if very many locks refer to the same lock table. In this case, there will be a considerable loss in performance in comparison with direct transmission of locks.
Behavior for Lock Conflicts (ENQUEUE only)
The ENQUEUE function module also has the parameter _WAIT. This parameter determines the lock behavior when there is a lock conflict.
You have the following options:
ｷ        Initial Value: If a lock attempt fails because there is a competing lock, the exception FOREIGN_LOCK is triggered.
ｷ        X: If a lock attempt fails because there is a competing lock, the lock attempt is repeated after waiting for a certain time. The exception FOREIGN_LOCK is triggered only if a certain time limit has elapsed since the first lock attempt. The waiting time and the time limit are defined by profile parameters.
Controlling Deletion of the Lock Entry (DEQUEUE only)
The DEQUEUE function module also has the parameter _SYNCHRON.
If X is passed, the DEQUEUE function waits until the entry has been removed from the lock table. Otherwise it is deleted asynchronously, that is, if the lock table of the system is read directly after the lock is removed, the entry in the lock table may still exist.
Exceptions of the ENQUEUE Function Module
ｷ        FOREIGN_LOCK: A competing lock already exists. You can find out the name of the user holding the lock by looking at system variable SY-MSGV1.
ｷ        SYSTEM_FAILURE: This exception is triggered when the lock server reports that a problem occurred while setting the lock. In this case, the lock could not be set.
If the exceptions are not processed by the calling program itself, appropriate messages are issued for all exceptions.
Reference Fields for RFC-Enabled Lock Objects
The type of an RFC-enabled function module must be completely defined. The parameters of the generated function module therefore have the following reference fields for RFC-enabled lock objects:
Parameters
Reference fields
X_<field name>
DDENQ_LIKE-XPARFLAG
_WAIT
DDENQ_LIKE-WAITFLAG
_SCOPE
DDENQ_LIKE-SCOPE
_SYNCHRON
DDENQ_LIKE-SYNCHRON
See also:
Example for Lock Objects
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eebf446011d189700000e8322d00/content.htm

To delete the transport request.

when i'm trying to delete the transport request by using se09, it responses with " Request/task BWDK916118 cannot be deleted because it contains locked objects." That request is created by me. It showing same name but it will not allow me to delete. Please help to delete how to delete that request.
Thanks
Satish

Hi..
Basically you are getting this messge because first you have to delete all the objects of the underlying sub requests and then the subrequests ......then finally the actual request.................
Secondly, it is better to unlock all the objects first so that you can delete all the objects at a time..............because if you have to delete all the objects one by one.....and if each requests contains 100s objects then it is very tedious to delete all the objects one by one...
Go to SE03 --> There you will get the options "Unlock Objects (Expert Tool) " --> Click over there --> give the subrequest nos and unlock it....
Then go to SE01 --> Click on "Objects" tab --> You will get the change button --> click on it --> Select All and Delete at a time...
Regards,
Debjani..

Error in ACT_UPG (7.0) because of old lock objects E_BAMMAPNG / E_BAMUIBT

I have errors in upgrade phase ACT_UPG because 2 lockobjects could not be activated, because referenced basetables are not there
u2026u2026.
3 DDI806XAktiviere Sperrobjekt "E_BAMMAPNG"
1EDDI751 Basistabelle "BAMMAPFCGR" des Sperrobjektes ist nicht aktiv vorhanden
3 DDI813 Sperrobjekt "E_BAMMAPNG" wurde nicht aktiviert
3 DDI806XAktiviere Sperrobjekt "E_BAMUIBT"
1EDDI751 Basistabelle "BAMUIB" des Sperrobjektes ist nicht aktiv vorhanden
1EDDI751 Basistabelle "BAMUIBT" des Sperrobjektes ist nicht aktiv vorhanden
3 DDI813 Sperrobjekt "E_BAMUIBT" wurde nicht aktiviert
u2026
1 EDO578XFollowing objects not activated/deleted or activated/deleted w. warning:
1EEDO519X"Lock object" *"E_BAMMAPNG"* could not be activated
1EEDO519 "Lock object" *"E_BAMUIBT"* could not be activated
Also in the old release the lock objects were only partly active and gave an error when checking via SE11. Also, the objects are very old sap objects from 2001.So I would think , that these both errors could be ignored.
I have opened an customermessage, but maybe anybody had this error, too ?

answer from sap was:
The two E_BAM* lock objects are related to tables (BAMMAPFCGR, BAMUIB,
BAMUIBT) which are indeed part of the SAP Servicetools.
As mentioned in note 309711, those tools get deleted during the upgrade.However, parts that are regarded as modification get added to the
new repository, like those E_BAM* lock objects. However, they cannot
be activated, as the related tables are missing. You can follow note
309711 in preparation for the upgrade.
In any case, you can ignore activation errors on those E_BAM* tables.
Please check note 309711 for post-upgrade activities.
so, I proceeded like Sunny proposed.

What is the use for lock object and how to use the lock objects

Hi Guru's,
I am new to ABAP .Can you please clarify the that what is the use of lock object and how to use the loct object .what is use of the Deque & Enque function modules .

hi ,
below are some minfo about lock objects :
Lock Objects
These types of objects are used for locking the access to database records in table. This mechanism is used to enforce data integrity that is two users cannot update the same data at the same time. With lock objects you can lock table-field or whole table.
In a system where many users can access the same data, it becomes necessary to control the access to the data. In R/3 system this access control is built-in on database tables. Developers can also lock objects over table records.
To lock an object you need to call standard functions, which are automatically generated while defining the lock object in ABAP/4 dictionary. This locking system is independent of the locking mechanism used by the R/3 system. This mechanism also defines LUW i.e. Logical Unit of Work. Whenever an object is locked, either by in built locking mechanism or by function modules, it creates corresponding entry in global system table i.e. table is locked. The system automatically releases the lock at the end of transaction. The LUW starts when a lock entry is created in the system table and ends when the lock is released.
Creating Lock Objects
Lock object is an aggregated dictionary object and can be defined by using the following steps:
o From initial data dictionary screen, enter the name for the object, Click Lock object radiobutton and then click on Create. The system displays a dialog box for Maintain Lock Objects screen
o Enter short text as usual and the name for primary table.
-Save
-Select Tables option
From this screen you can:
Select secondary tables, if any, linked by foreign key relationship.
Fields for the lock objects. This option allows you to select fields for objects (R/3 system allows locking up to record level). Lock object argument are not selected by user but are imposed by the system and includes all the primary keys for the table.
1) Exclusive lock: The locked data can only be displayed or edited by a single user. A request for another exclusive lock or for a shared lock is rejected.
2) Shared lock: More than one user can access the locked data at the same time in display mode. A request for another shared lock is accepted, even if it comes from another user. An exclusive lock is rejected.
3) Exclusive but not cumulative: Exclusive locks can be requested several times from the same transaction and are processed successively. In contrast, exclusive but not cumulative locks can be called only once from the same transaction. All other lock requests are rejected.
Also, last but not the least, locking the object is logical (locking with any enqueue ) .so, you have to use the lock object while trying to access from second program .
reward if helpful ,
Regards,
Ranjita

Lock objects,Editor lock difference ?

What is the difference between lock object and editor lock

Hi,
Editor Lock : This is to lock a program created by User 1 from editing by any other User. Say for eg. User "XYZ" has created a program and he doesnt want anyone else to edit/modify that program, then he can put Editor Lock so that no one else other than "XYZ" user would be able to edit/modify it.
Lock Object : Consider an example, where two Users say User 1 and User 2 wants to book railway ticket. Only 1 seat is remaining. The ticket information is updated in table ZTICKETS. This table can have tickets only from 1 to 10.
Now User 1 and User 2 approaches two different reservations counters and ask for the same train ticket. Now the table is Locked for User 1 and the ticket information is updated in ZTICKETS table so that the other User should not get the ticket. Otherwise two persons would be alloted the same ticket. So the table locking from simulatneous updates can be achieved through Lock Objects.
Best regards,
Prashant

How to delete unreleased transport request where the objects are locked

Hi Experts,
I was created a transport request, but I am facing some probelms with taht request, now I want to delete transport request. I tried to delete them in SE10, I am getting message that the objects are locked. Please tell me how to delete unreleased transport requests where the objects belong to this transport request are locked.

Hi,
First go to transaction se03 Choose "Unlock Objects (Expert Tool)" option under "Requests/Tasks" and unlock your task,
Than go to se10 and delete what you want.
I hope it helps.
Bulent

Deleting modifiable SE10 request/transport

Dear Forum,
One of our developers made by mistake a transport request (se10) in our Q/A environment /should have been Dev system), and she would like it removed/deleted again. I would say it is ok to delete the modifiable request in Q system (garbage can) as long that it hasnt been released. but i would like your opinion.
Best of my knowledge we wouldnt end up having any locked objects as long the reuqest hasnt been released. It is in status modifiable.
Any replys will be greatly appreciated
thanks in advance!
kind regards,
Soren

Hi,
If any objects are stored in TR first remove them and delete the request.Check the target system of request in properties tab and change if it is Production , make sure it is not released .
Thanks and Regards,
P.Bharadwaj

Unable to delete Transport Request which contain locked objects

Hi all,
I need to delete some unusable transport requests but as they contain locked objects, it's not possible to delete them. Release operation is just allowed. After releasing these transport requests, I can not find them any more in queue. Please help to find these transport requests which are released and also provide a solution to delete instead of releasing them.
Thanks in advance,
Sanaz.

Hi,
Thank you for the reply.
1. What do you mean by transport request , Shipment Request, Shipment Order or Tour.
A. I mean requests which can be transported between SAP Systems using TMS (Transport Management System).
2. What are the objects which has been locked and due to that you are facing this problem.
A. There are diffrent object types. For examle some customizing have booen done or SAP Note correction has been implemented, ... Therefore some objects have been locked due to these operations
3. Let's say if it's an freight Unit, then Pls confirm that System dump / error is not the cause for this.
A. I have no idea about "Freight Unit".
Thanks,
Sanaz.

How to transport Enqueue and Dequeue Objects / Lock Objects / R3

Hi Gurus,
i have created two lock Objects.
I transported those objects in Q system but the table tab has no objects.
But in Dev every thing is correct.
Could you please indicate how i can get the objects correctly transported?
Thanks

Easy and best approach is by getting them re transported by using transport of copy request (Type of request)
1) Get the Transport of copy request created by basis team / urself under your user.
2) Go to SE10 and highlight the request and click on include objects icon
3) Later in the pop up window select the radio button which mentions "Include free objects"
4) Then in the next screen mention the details based on the attributes of the Enque and deque object or else provide the package name and execute and in the next screen choose the concerned enque and deque objects and include them in the request.
5) Transport the Transport of copy to quality.
Also, more easiest is.
Find out the task of the request with with the enque and deque objects were created with (if more than one select all), and then include the tasks in the transport of copy and transport it to next system
If you are not able to do the above two steps then i think the object is $TMP object, kindly cross check.
Cheers

Issue with Info Object Transport after changing Data Type

Hi Experts,
We have a DSO which is running past 5 years. And recently(3 days back) we added new fields into that DSO. Delta loaded for last three days and new info object (Say XXX) data populated into DSO.
Now the problem is, We identified that, info object data type is not correct. We used data type NUMC instead of CHAR.So Character information is missing for that field.
Example:
Data from ECC: ABC123
Data Loaded to DSO: 123 (Missed character ABC)
So we deleted data from DSO and changed the info object data type in Development system.
And also I have deleted only last three days delta records from DSO and transported my info object to Production. But its giving error as: Info object contains data in DSO".
But that info object field is empty in DSO. I have already deleted last three days delta.
Do I need to Delete all 5 years data from DSO to change the data type of recently added new info object ?
Please give me your solutions and ideas to solve this issue.
Thank you,
Best Regards,
Santhosh

Hi Raman,
Thank you for your answer.
When I changed the data type of info object in Dev, I deleted the content of DSO. And same thing transported to QA as well. Before importing changed info object, I just deleted the content of DSO from QA. So transport done successfully QA.
But in Production we have a history of past 5 years. So I cant delete all contents of DSO.
So just deleted only the delta request's which contains data for that info object(3 days back, we moved that info object(NUMC data type) to production,So last 3 days delta only loaded for that info object). And tried to transport it. But it was failed. I am sure we need to drop all data from DSO, if I am interested to go with same info object.
I have some comments on your first approach,
1. If we delete info objects from Dev DSO and transport to Production will give transport failure, Why because, my previous transports errors clearly saying that info object contains data in DSO . So it wont allow to remove that info object from DSO.
2.We are using same info object technical name in BO Data federator also. So if we change add new info objects again we need to make changes with BO as well. I am thinking this point as my last option if i cant find any other solution.
Thank you.
Best Regards.

Locked objects in Transports

Hello All,
I have a bunch of transports around 50 in my system. How do I find out if any of the objects withing all the 50 are locked or not? I want to avoid the manual process of going into SE03 and checking each transport individually. Any other alternative?
Thanks,
Fahad

this is first answer in BPX ,
check in table TLOCK for the locked objects
chk the last but second question in this link
http://www.geocities.com/SiliconValley/Grid/4858/sap/Basis/tpprobs_solutions.htm

Is Lock Object transportable to LIVE from development server?

I had created a customized lock object on a customized table.
I can only managed to save it to $ENQ package. I tried ZSD1 but no use.
Now, since I am working in my development server, I had problem getting it across to my "LIVE" environment.
Can it be transportable?
I tried to change but no avail.
Bye

The lock object transportable is the one created with SE11, not the function modules and group generated.
IdPgr : R3TR
Obj : ENQU
Object : Exxxxx
Regards

Why do we lock objects in a transport ?

hi,
why do we lock objects in a transport in SE09 ? whats the benefit/impact ?
thks

Yes Thomas, today is my TRANSPORTS day
and btw, just to confirm about locking, I have a transport moved from old system to the new one which contains this object say a function group!!.
Now I modify this FG in the new system and include in a different transport.
Due to some reason (errors encountered during transport movement), it is decided that the old transport is going to be moved from old system to new system once again. Will this impact the object that I have modified and included in the new request in the new system ?? Is it bcos of this I am asked to lock and continue my work on that ??
hope i have not confused you

Delete modifiable transport with locked objects (SE10)

Similar Messages

Maybe you are looking for