Transport Request Locks on release!!

Hello there,
I am facing one problem; When I create a transport request of a smart form and try releasing it, the request gets locked, thus failing the release.
I unlock the request via transport organizer tool (SE03), but again when I try to release the request, locking repeats.
Any solutions??
Thanks,
Sumit

Hi,
Plz. check client settings via scc4.
And check the owner of that request also via SE01.
Plz. let us know, are u facing this lock issue, only for this smart form only or for all other requests also??
Note: Points will always encourage me to reply!!

Similar Messages

Transport request not getting released

Hello Friends,
I am unable to release a transport request.
While releasing a transport request, it shows the following log in SE10. The export is not taking place.
========================================
Log Overview for DBBK911964
DBBK911964 All cubes
DBB Development (Maintenance Line)
Checks at Operating System Level
20.08.2007 13:30:58 (0) Successfully Completed
Export pre-processing
20.08.2007 13:31:01 (0) Successfully Completed
<b>Export
21.08.2007 07:51:11 In process: Requires update</b>
Import steps not specific to transport request
========================================
Kindly sugest what should be done.
Thanks & regards,
Kunal Patel.

Hi!
Child transport = (transport) task, parent transport = (transport) request.
Releasing the task (child) does not trigger any checks, the locks are just copied from the task to the request (parent).
Only when releasing a request checks are triggered (can be done beforehand via menu in SE09). Also this steps (would) copy the source into files, which are later imported in the target systems.
You have problems in one package (DEVC) and three reports, obviously because of Japanese characters. The possibility to print Japanese seems not to include to name objects in Japanese...
Your objects are ZA11 and 1021-1022 - here no Japanese is include, so it has to be something on lower levels.
Check the code and try English naming.
Regards,
Christian

Transport request main task releasing problem

Hi friends,
Environment is Linux, ECC5.0, Two system landscape,
I have problem with Transport Request task releasing when I am going to release the subtask that willbe released success fully when I am trying to releasing the main task that task is not released and at that time the system wil hang( mesg on the status bar is tp is connected success fully) thats it we wait for long time then also that looks thats only no log will be generating in usr/sap/trans/log there will be a log on this one that log is
WARNING:/usr/sap/trans/tmp/<username.LOS>is already in use (10), I'm waiting 3 sec(20070326124305). My name:pid 7265 on test(sd1adm)
after saw the this mesg I kill the 7265 pid then also same proablem.
I change the ownet of the request then the request is released but not uppeard in the import que. whn i am trying to import in que as manually that will appear in que but not importing when i press the import button the error is tp error 0203.
I check the both users authorizations also bothe authorizations also same then why it wil happening ???
then I check the nfc also that service also running ok the six services are 1.off 2.off 3.on 4. on 5.on 6.off.
I mount the trans dir also the mounting points also ok tms configuration is also ok
wt can i do plz help me with ur valuable suggessions
Thankyou
Ranjith

Hello Ranjith,
This is usually because the tp transport buffer lock file remains locked by the
operating system (OS).
You should be able to move or delete this file from the DIR_TRANS/tmp dir.
After that the tp should run fine after.
Thanks,
George

Transport request in PR release strategy

Hi Experts,
While configuring characteristics and classes for release strategy in PR, system is not giving prompt for transport request.
What could be the reason? Is it standard functionality or something has to be done at our end.
Kindly suggest
Rgda

Hi,
Check the following SAP notes.
10745
45951
86900
Hope it helps,
Regards,

How to find the transport request which was released to Quality

Hi Friends,
Could anyone please let me know, how to find the transport request that was already released from Development to Quality?
there was some change in customization took place. I could find the user (through change log) who made these changes, however I could not find the transport request number he has already released. I did give his user name in SE10 and checked the released checkbox and did click transports to see them, however I found nothing. A message got displayed on the screen: Cross-system information for user xxx. I can't ask the Basis people about it, as its not yet been trasnported to Productive.
Is this the correct way to see the transport request number? Is there any other way to find the number. I can give the tentative dates when the change was released.
This post might already posted before, I did some search, could not find the exact info what I am looking for. Would appreaciate if anyone could give the step by step method to find it.
Thanks in advance.
BR,
Sats.

Ram,
let me tell you the the situation in a better way.
When I see se10 with my user id I could see all the transport requests that I have released. However, now when I enter my colleague user id who did these changes (he is on vacation, otherwise I could simply ask him the transport number), nothing is shown on the page. in simple words the page is completely blank. Initially I thought it is because of some authorizations, but I can get the transport request numbers that are released by another user.
the info what I have right now are:
1. I knew the user name who did these chages
2. I knew the date when it was changed.
I just need the Transport Request number I mean which starts with DEVXXXXXXX.
As per your solution --> If you have any idea when the reques was relase you can select the request and click on goto-transport logs. This way you can find out the request. --> I knew the date when it was released, but didnt understand, the bold and underlined sentense in your answer.. select on which request? as I said, the page was blank after I enter his user id and activate it.. May be I did not understnd your solution properly. Could you please simplify it.
Thanks a bunch in advance
Sats.

Transport request not getting released by se10

Dear all,
I am trying to release transport request of development server via. transaction se10.Now my problem is that the child(DEVELOPMENT/CORRECTION) is getting released while the parent request is not getting released.
I checked everything and its showing 'test call of transport control program ended with return code 0208.' I even checked overview of system,overview of connection type,over view of transport protocol and they are fine.my only doubt is after going to se10 when I click transport proposals its showing "WORK FLOW NOT ACTIVE' .
Is my problem is because of this. Please help its very urgent as due to this I am not even able to transport any request on production server.
Helpful contribution will be duly rewarded.
Thanks & Regards,
VICKY

Are you the owner and in the right client ?
use SWU3 to activate/configure WORKFLOW.

Transport request and task releasing?

Hi all,
I've three systems dev,QA and prod.I'm working on dev client and I've a two reports(say A and B) under the same transport request with different tasks,If I want to release the report 'A',is it necessary that I shud be releasing th ewhoel request number or if I release the task it's enough.why a transport request will have different tasks,when the transportationof ht ese taks associated with the transport request is independent.
I've released the task to QA and the QA sytem had some problem and did nto get he task,what I shud be doing now,release the task again or ?
Can a report be assigned to different tasks(numbers) under the same transport request.can the report be assiged to different transport requests.please let me know.
thanks and regards
Message was edited by: henry

There is a transport route defined by your Basis Team for the transport scenarios. There, the possible ways through which request can be moved( from Dev --> QA & Dev --> Prod ) are defined.
But it does not mean that you can't transport your request to production without transporting it to QAS.
Furher, when you release a transport request, it does not automatically move to QAS or Production but someone from your Basis Team has to run the TP through Xn STMS, which in turn imports the objects from your Dev Request and put it on QAS / Production.
In case of any error encountered while importing to let's say QA, you need to check whether it's a problem with the transport buffer or is it because some objects are missing from the transports or dependent transports are not moved as yet.
Please understand that there is no concept of re-release.
You can only ask your Basis guy to re-import it.
According to the encountered problem, you need to decide whether you should just ask you Basis consultant to re-import the same Transport.
Or create a new request through SE10, and include all the objects from your last request. Release it and ask your Basis guy to import it to QAS.
Or first move the dependent transport and then ask your Basis guy to re-import your current transport.
Or create and group the changed objects, altogether in a new transport by changing all the objects which were contained in the original request.
Further, to your other queries, if two users are modifying the same program ( not exactly at the same time - that's not possible but one after other )then that program will be contained in two separate tasks of the same transport request.
I hope it answers a few of your queries.
Thanks,
Ram

How to retreive Transport request that is released

hi,
I have released few transport requests from R3 Dev system, to R3 QA system.
In Dev system it is showing that requests are released successfully.
But in QA system, under transaction STMS, these requests are not displayed.
Looking for a help..

Hi Saurabh,
You can add these requestes to QA import queue.
Goto STMS -->> QA Import Queue -->> From Menu Extras -->> Other Requests -->> Add -->> Provide Request No.
Hope it Helps
Srini

Object / Transport Requests Lock - TR_LOCK_COMM

Hi to all ABAP gurus,
Is there any substitute Function Module to TR_LOCK_COMM?
It seems that this one has been discontinued since 4.6c
Can anyone tell me if there is another way in ABAP (FUNCs, METHs ...) to Lock objects to a TR as this FM used to do?
Best Regards,
Pedro

quickly debugging the Lock procedure in SE09, I came across FM TRINT_LOCK_OBJECT
<please do not ask for reward>
robert.
Edited by: Thomas Zloch on Mar 2, 2010 10:18 PM

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 could we delete transport request and task(the released one)

Hello
We have a released transport task(not request). Transport request is not released.
How could we delete transport request and task(the released one). Namely we would not like to transport it to production

Hi, never delete directly in table.
There are more tables which depends each other...
Here, you can find nice example how to do it: Help on ABAP: Few Tips for Transport Request Manipulation
Using program: RDDIT076 and changing status.

How can i change transport request description

I need to change transport request description for one table
Note:
Considering this post as Basic and Locking it for futher postings.
Answer: Double click on the Request and using the change option, change it's Description
Edited by: Vijay Babu Dudla on Jun 29, 2009 7:02 AM

Hi,
I know I am a little to late to the party! But for all those who are going to search for this in the future there is a very good blog...i am posting the link below...
Basically run the program RDDIT076...
http://scn.sap.com/community/abap/blog/2015/03/12/program-to-change-transport-request-description-after-release
Regards,
Divaker

Transport request failed; recollected with new TR;what happens to first one

Hi,
I released a transport request and requested that the request be transported to the testing environment.
I received a message from Basis that the transport failed. I suspected that it might fail because I say many duplications in se09.
To fix this problem, I basically recollected the objects carefully and under a new transport request number; and released it.
I have requested that the Basis team move the new request to the testing environment.
1. What is wrong with what I did?
2. If the second request successfully gets moved to the testing environment, what becomes of the first request which was released, therefore no more available in development for me to delete? I tried to delete it under the "Released" section in se09 but got a message that it is not available to delete.
3. Could I have used the same Transport Request number the second time around, although the first number had been previously released?
Thanks

1. What is wrong with what I did?
It depends, did you check the Log.
Log should tell you why it failed or atleast give you some hints.
Ex : Missing objects ..might have been locked in an other request.
2. If the second request successfully gets moved to the testing environment, what becomes of the first request which was released, therefore no more available in development for me to delete? I tried to delete it under the "Released" section in se09 but got a message that it is not available to delete.
If the second request contains similar objects to the ones in first, everything will get overwritten in the target system.
TR1 - 10 Objects
If TR1 returns RC=8 due to one object, 9 objects will be successfully transported. You may only transport the failed one in the next request with its corrections.
3. Could I have used the same Transport Request number the second time around, although the first number had been previously released?
Yes, same released request can still be imported more than once but it may result in the same.
Try to find the reason the request failed, accordingly add objects in the next corrected request.
You can also copy requests into an other.
RClick on the request - Include Objects ( Ctrl + F11 ) - Enter Request Name.

Error while Transporting Request

Hi All,
we have ECC 6.0 on Unix environment.
we had copied a production client with group selection, as we wanted all the three system PRD,DEV,QLT in sync.
the export was succesfully done.i copied Cofiles & Datafiles which are generated in DEV & Quality server,then i add request no in transport queue. the time when i copied transport request was not releasing from development.we checked the destination it was full so we removed the old request. then req is releasing.
after that i deleted the Cofile & datafile from OS level of DEV & QLT & trying to delete the reques from request queue. it is deleted but when im refreshing the queue its coming back in the queue.
while transporting other request its giving me error.
please help out me.

Hi Aasmi Gawas,
Please could you post the error?
We don't have a crystal ball to see the errors in your system...
Best Regards,
Erick ILarraza

Re-transport the transport request to NQA server after system refresh

Hi
Users are moving the transport requests in NQA (quality server) using STMS tcode and Basis team is moving the trasnport requests using TP command in operating system level.
There are some transport requests that are released and are moved only to NQA server but not in Production server.
After the NQA refresh from Production server, we need to re-create the trasnport route for NQA server
in NQA using SE06 and STMS.
Now users want to re-transport the requests again in NQA server that was moved to NQA before the system copy but they are not able to make it. In the transport queue, users are able to see their transport requests but they are not able to re-transport.
When basis team try to move the same transport requests using TP command in operating system level, it failed with error:
- "Transport request is not in buffer".
- x2n0v2:nqaadm 14> transport250_NQAu126 908807
/usr/sap/trans/NDV/cofiles/K908807.NDV
is this the correct cofile ?y
cofile is K908807.NDV
source system is NDV
transport type is K
transport name is NDVK908807
Renamed to K908807.NDV.INTRANSIT on dbcindv
Datafile copied to dbcinqa
Cofile copied to dbcinqa
-rw-rw-r--   1 nqaadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NQA/data/R908807.NDV
-rw-rw-r--   1 ndvadm     sapsys       25606 Oct 29 11:13 /usr/sap/trans/NDV/data/R908807.NDV
-rw-rw-r--   1 nqaadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NQA/cofiles/K908807.NDV
-rw-rw-r--   1 ndvadm     sapsys         678 Dec 1 19:05 /usr/sap/trans/NDV/cofiles/K908807.NDV.INTRANSIT
Please compare the files before proceeding
Do you wish to continue the import?y
tp addtobuffer NDVK908807 NQA pf=TP_DOMAIN_NDV.PFL
This is tp version 305.13.25 (release 46D) for ANY database
Addtobuffer failed for NDVK908807.
Cofile not existent or corrupted (datafile exists).
If source system is available you may try to reconstruct
the cofile using the command "createinfo".
We used the following method to re-transport the requests to NQA server:
"STMS --> Request -->Delete (the request number)" method delete the transport request from transport queue and from the cofiles/data directory of the operating system and then " STMS --> extra-> other request-> add" allow us to put the transport request back to transport queue in NQA server. Once the transport requests are in queue, we can re-transport all of them one by one or in group.
Question: Is it the right way to re-transport the request in NQA (first delete if from transport queue and then add and then re-import in NQA server).
Id there is any other way to re-transport the requests, pls suggest us.
Thanks
Amar

Amar,
Depending on how many tarnsports you have and also if this is one time, what you can do is ask Basis guys to write a small script which adds to the buffer to your NQA system.
Steps:
1) under /usr/sap/trans/buffer rename the NQA buffer file.
2) create a new empty file NQA (make sure permissions are identical)
3) Provide the list of transports and ask Basis team to put it in a file at Unix level
4) Run a script which will add to the buffer from the source file.
5) From STMS refresh the NQA queue and you should see all the transports ready for import.
Hope this helps.
Thanks,
Naveed
Edited by: Naveed Qureshi on Dec 4, 2008 8:52 AM

Transport Request Locks on release!!

Similar Messages

Maybe you are looking for