Transport request to all clients in system from STMS

Hello colleagues,
Wich parameters should we activate so that every transport request wich is imported in our test systems updates all available clients in the system?
Kindest Regards

Hi Enrique,
That should be part of extended transport protocol. Check [this|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/1b/9dc2d6e59911d184810000e8a57770/content.htm] URL for ETP. Also have a look at [this|Auto import from one client to another with in same system; thread, where your question is being answered.
Kind regards,
Mark

Similar Messages

Transport Request in All client

Dear All,
In my Quality server there are 4 client (630, 650, 670, 690). When i transport any customized request from DEV to QLT, then in each client I have to transport it. It means i have to do same activity for 4 times. So is there any way by which I can transport the request in all client at same time? How?
Regards,
Nisit

Hi Nisit,
Try scehduling a Background Job (TMS_BCI_START_SERVICE), which run at the same time in all the clients.
Thanks
Ahamed

Prevent import of transport request for certain client

Hello.
I have two clients in TST system.
I would like to delete one client.
How can I prevent import of transport request for certain client?
At hte same time users must transport request into other client in TST system.
Is it possible?
I know next features:
1.
se37-->
SCCR_LOCK_CLIENT
SCCR_UNLOCK_CLIENT
2.
tp locksys SID (from OS level)
but they use for all client (for whole system).
Best regards,
Denis

se37-->
SCCR_LOCK_CLIENT
SCCR_UNLOCK_CLIENT
These are Client Specific not Cross client. So if you want to delete a client just Schedule the Delete Job and lock the client and no body would be able to transport on that client. I hope i understand your question properly.
Regards,
Subhash

How to Delete Transport request for Delete client

Hi guys,
We are going for upgrade from 46C to ECC.
we found client XXX does not exists but Transport request for the client XXX does exists. so we plan to delete it or release it before going to upgrade.
But SAP does not allow me to delete or release it. Is there any special way to deal this issue.
Please suggest me.
Thanks
Jaichan

You could have the lost client XXX recreated again by system administrator using a "minimal" client copy (just users), should take only minutes and not much disk space.
Then you can release or delete the transports, afterwards delete the client again.
I don't know another way of doing it.
Thomas
P.S. all the other replies so far do not take into account that you cannot change transports that were created in a different client.
P.P.S did you ever look at the long text for message TK056? This clearly explains your options here
To transfer the request to the current client, proceed as follows:
1. Go to the request overview.
2. Position the cursor on the request and choose Request/task -> Display/change.
You are asked if you want to copy the request and all tasks belonging to it to the current client.
3. Answer "Yes".
The request is copied to the current client, and can then be edited as normal.
Note
For this procedure, you require the "Change source client" authorization contained in the SAP standard authorization S_CTS_TR_ALL.
You can copy only your own requests to another client.
In order to copy other users' requests, you first have to assign them to you.
You can reassign the request to you in another client only if the original client no longer exists (prerequisite: You want all client-specific entries to be deleted).
I was not aware of this up to right now...

Transport Request copy between clients in the same system

I have one workbench request needs to transported across all our client in the QA system
Development system has 3 clients - D001,D002,D003(client)
I am supposed to do the development works in the D001 client.
Unfortunatel I did in the D002 client.
But our transport route is D001 --->Q001only.
Is their any way I can copy the Transport request from D002 to D001 and then release D001-Q001.
I am able to repeat the same work relevant to D002 client.But there is no transport request is creating for the new
work in D001.
Please advise on this.
Advance Thanks

Hi,
You cannot copy a transport request from one client to another. Try to make a client copy so that the changes you made to D002 client will get effected in D001.
Hope this helps.
Assign points if useful.
Venkat

Inconsistant transport requests after local client copy

Dear experts,
our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
Thanks for your appreciated help
Andreas

Hello,
Transports are NEVER part of a client copy.
In fact all the data of your transports is stored in tables that are client independent (E07* tables).
This means that you can view (not edit) always all transports from all clients in a specific system.
When you want to edit or release a transport the source client is important (in which client was the transport originally created).
This is stored in table E070C for all transports and can not be overruled.
So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
Success.
Wim

Transporting request to two clients

Hi Experts,
We have two clients(100 and 200) in production system.
1. If we transport client-independent request to any client 100 or 200, will it effect entire system?
2. Shall we have to transport client dependent request to production 2 times?( first to 100 and second to 200 via STMS)?
3. Using SCC1 shall we pull the request from client 100 to 200? is it right process in production?
Please advise..Thanks in advance
Regards
Veera

Hi,
We have two clients(100 and 200) in production system.
1. If we transport client-independent request to any client 100 or 200, will it effect entire system? - yes
2. Shall we have to transport client dependent request to production 2 times?
( first to 100 and second to 200 via STMS)? ..... yes
3. Using SCC1 shall we pull the request from client 100 to 200? is it right process in production? -
yes
1. All Workbench requests are Client-Independant
2. Alll Customization requests are known as Client dependant.
Thanks
Siva

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

Re-transport the transport request in Quality 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

No cross posting
Read the "Rules of Engagement"
Regards
Juan

How to install transport request files into the SAP system

Hi Experts,
I want to install transport request files into my SAP source and target system . I am from BW/BI background so can anyone help me out with the step by step procedure for the above installation.
Thanks in advance
Regards
Shiva

Hi,
What I understand is, you want to transport request from one server to another.
for example, Development to Qualtiy or Quality to Production.
For this your transport system must be configured. Please search help.sap.com or google for "How to configure Transport System (STMS)".
If you want to copy transport request from one system to another system which is not in your landscape, you need to physically move/copy transport request (cofile and datafile) to the target system in /usr/sap/trans/cofiles and /usr/sap/trans/data
Then import that request using SCC1.
You can alos perform TEST import for result.
Regards.
Rajesh Narkhede

Copy Transport Request (customizing-workbench) between different systems

Hello guys !
I have a question.
I can copy transport request of customizing and workbench from ECC 6.0 system to another ECC 6.0, with the same levels of support packages and patch realease, but one of the systems in Windows and another in AIX?. The database is the same: oracle.
Thanks guys!!!
dcardena

Hi Dcardena,
You can very well copy the request. Different OS platforms won't make any difference.
Regards
Sourabh Majumdar

Issues with creating transport request for cross client changes???

Hi,
In our ECC 6.0 dev system, functional team makes all their configurations in client 100.But ABAP team is using another client 120 to create /modify ABAP objects.
So all workbench requests getting created in client 120.
I would like to have all customizing/work bench requests created and released from client 100.Is is possible to re-assign all work bench requests created in cleint 120 to client 100?
Thanks
Ram
Message was edited by:
        rama subramaniam

Hi Rama,
             If u r making any workbench changes that means they are repository
             objects it will reflect entire system. I dont think we need to import them
              into the same system once again. Hw ever we can do that by scc1.
Regards,
Vamshi.

Transport Request Information

Dear All,
I have three systems landscape. My quality server having 4 clients. During the transport. I have transported all transport requests to all clients to make them sysnc.
I would like to know that which transport requests have gone to which clients. Please tell me the table name from where I can download the data and make my comparision.
Regards
Vimal

Check tables E070, E071 and E070C,
E070 - Stores transport headers
E071 - The names of the objects of a transport request is stored in table.
E070C - stores information for client specific tarnsports
This will help you out.

Checking Transport requests present in two different clients.

We have around 200 transport requests that have been transported by consultants from D01 to R01-client1/client2 and I need to check that which transport is present in which R01 system client.. i.e. a) how many of them are present in client 1, b) how many are in client 2 and c) how many are in both. We can check the logs of every transoprt through SE10 but Is there any quick/automated way of checking mass Transport Requests status ?

Dear Raichandi,
Please follow the below steps to get the desired information.
1. Login to D01 (Dev client) to find the released transports..
2. Execute transaction SE01
3. Go to "Transport" tab
4. Give User as "*"
5. Select "Request Type" by tick mark as Customizing Requests and Workbench Requests
6 Select "Request Status" by tick mark as "Released" only
7. Click on "Display Button"
8. It would display all the released transports requests.
9. From here you can copy and paste all these requests numbers in the spread sheet
(CTRL + Y) then use Mouse to select the requets, (CTRL +C), and then paste it in exel sheet.
1. Now Login to the R01 (QA client) to find the import status of the release transports from D01.
2. Execute transaction STMS
3. Click on "Import Overview (F5)" or the Truck Symbol.
4. It will take you to the Import Queues for the Import Domain D01.
5. This is the option where you can select the Queue to see the desired information for Quality/Stag/prod system.
6. Now double click on the required "Import Queue" for R01 (Quality system).
7. Now Go to "Import History or (CTRL+ F7)"
8. Change the Filters as required (may be for time interval or remove any filter on client -Clt)
9. The import History will display all the Imported requests in all clients in one system (SID), so for your case it will display requests for R01/client1 and R01/client2
10. Copy the same in the spread sheet...
11. Do the VLOOKUP to find which are not imported in which clients.
Please provide the feedback if it works.
Thanks,
Vinod

How to delete the entries from the transport request

i need to delete the entries programatically from the transport request for all the entries which is exists in the package for the tables e070 and e071.

Hi,
I think you need to have authorization for that thru auth group SA.
One more thing is where ever its created like source client only you can do if u have authorization.
Regds
Sivaparvathi
Please reward points if helpful...

Transport request to all clients in system from STMS

Similar Messages

Maybe you are looking for