Transport mass addition to the import queue

I have around 500 transports to be added into import queue after refresh. Now if i add once at a time, it will take a lot of time. Is there a way to add multiple transports at the same time. I know about running multiple transports in a single type but not sure about adding them in a queue.
Also we are doing this as a part of refresh, do we hvae a better way rather than to take the transport backup of requests waiting to be imported and manually add than run them again one by one.
Thanks.

Refer to the below link:
http://help.sap.com/saphelp_nw04/helpdata/en/96/8a99386185c064e10000009b38f8cf/content.htm
this might help you.
Thanks,
Rohan

Similar Messages

Transport Request is disappearing from the import queue

Hi everybody,
I am facing a problem with the transport import queue.When I exported a transport request and entered the STMS transaction,initially it is showing the request.But when I double click on the system(like DEV or PRD) it is saying "there are no requests in the import queue".
Please help in resolving this issue.
Thanks in advance,
Sreeharsha Singuru

Goto transaction SE01 and enter the transport number and put the cursor on the Transport number ans click Transport Logs (CtrlShiftF2) and see the structure .
This will give u the details of the Development , Quality , and Production Status for that request.
Like whether this request is moved to quality or production . This you can make out from the Tree Node Structure of that Log .
Check this .
If this is not there in the Quality then it is not imported from queue .
regards,
vijay

STMS: how to hide the Import All Requests button in the import queue view?

Hi All,
I'd like to know how to hide the "Import all requests" button in the import queue view.
Thanks a lot for your answers.
G.

Hi,
about hiding i have a doubt but u can inactivate by following procedure,
As referred in a thread:
On the domain controller, in STMS>overview>systems>(double click the one you want to change)>Select Transport Tool tab and click on change. Add Import_single_only value 1, import_single_strategy value 1 and no_import_all value 1. Save distribute and activate.
or
Refer to OSS NOTE 194000.
Thanks & regards.

How to delete 100+ released requests from the import queue?

Hello
How to delete 100+ released requests from the import queue?
One by one or there is more convinient way?
Thanks

To delete multiple non-imported transport requests, you do the following while in the import queue on STMS:
1) Highlight the status field of the import queue.
2) Sort the import queue by the status.
3) Put your cursor on the first non-imported transport, right-click, and click on Select Block.
4) Scroll down and put your cursor on the last non-imported transport, right-click and click on Select Block. This will highlight all requests from the first one selection to the last one selected.
5) Go to menu option Request > Delete.
If all of the requests in the import queue haven't been imported (no imported, including failed import, requests), you can jump to Steps 3-5.

Who clear the import queue?

Hello,
The import queue at our site was cleared by someone. I recovered the queue from backup but would like to know if there is a way to discover who cleared the list?
TIA,
Yossef

There is more than one way how an import queue might have been deleted.
The file may have been deleted or emptied at OS level, by tp command or other operating system commands. Follow Rishi's advice to investigate further.
All the transports may have been deleted from the queue by means of transaction STMS. In this case you may find out from the transport protocols the time when this happened. Then you may find out who called STMS at that time by transaction STAD.
hope this helps

Need to delete the SPAM requests from the import queue

Dear all,
There were some issues with my QA system SAP patch application and we were forced to do a DB refresh from our production system. Now our QA system ABAP stack is having an issue with the STMS import queue which shows 4 old patches(witch were applied to the system before the refresh) with u201Crequest will not be importedu201D status. When I try to delete these requests from the import queue it shows the following error
u201CThis is tp version 372.04.29 (release 700, unicode enabled)
ERROR: Client 'ALL' is not possible.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0246
standard output from tp and from tools called by tpu201D
When I try to import a new support package it gives the following error,
Error in phase: CHECK_REQUIREMENTS
Reason for error: QUEUE_NOT_EMPTY
Not sure how these requests arew still in the import queue even after the DB refresh. How can I delete these 4 old requests from the import queue?
The System is ECC6.0 ABAP+JAVA stack with Oracle 10g on Win2003 server.
Thank you,
Siju Sam

Dear Ganesh,
I have tried the steps you suggested, but still the import queue is not cleared.
Now I just wanted to remove these entires from the STMS=>queue=>import queue list.
Number   Request      Clt   Owner          Short Text
     1   SAPKB70013   ALL   SAPUSER        Basis Support Package 13 for 7.00
     2   SAPKA70013   ALL   SAPUSER        ABA Support Package 13 for 7.00
     3   SAPKB70014   ALL   SAPUSER        Basis Support Package 14 for 7.00
     4   SAPKA70014   ALL   SAPUSER        ABA Support Package 14 for 7.00
I think these requests(Patches) are not there in the tp buffer/(import queue) but somehow some table entries shows the status that they are still in the queue. So I just wanted to reset the status that These TPs are already applied.
Thank you,
Siju Sam

Adding transports to import queue after System Refresh

Hello All,
Every time we do system refresh from PRD to Sandbox as a part of post refresh activity we need to import all the transports which are in the import queue of PRD(which are not yet imported to PRD) to our Sandbox.
But its a tedious job, as in the import queue many old transports which are still not yet imported to PRD will b there.
So may b around 150+ transport requests in the import queue of PRD, which we need to add those manually from path
Extras---->other requests -
> Add. doing same for 150 times. cant even imagine dat work.
So my question is, Is there any way to get the replica of import queue of PRD to Sandbox.
Some where i read like transport buffer in the path /usr/sap/trans/buffer/<SID> of the system will have list of all transports in the import queue.
So can i copy dat file and replace SID with Sandbox SID and place it in the Sandbox under same path.
Please suggest or give me a correct solution.
Regards,
Ravi

Thanks a lot for your reply.
I had read about using script like tp addtobuffer inorder to add the transports to the import queue some time back.
But forwarding transports is a new method i got to know here which even looks easy too. It would be great if any 1 tell me how forwarding works.
Also it would b fine if who all uses this method of forwarding to add transports to import queue do reply about any problems faced while forwarding requests.
Bcoz in our landscape , transport route is as below
Dev to QA and Sandbox then from QA transports will move to Production.
So after refresh forwarding Transports from PRD to Sandbox, how does this work. Please share your suggestions.
Regards,
Ravi

Request not visible in the production import queue

Hi all.
When importing some requests in the QUA system, these requests do not automatically appear in the PRD import queue: they need to be added manually.
This only happens for some request: there are requests which automatically appear in the import queue of the production system.
There is no approval queue used.
I'm looking for the cause of this behaviour, but without success until now.
Can anybody help?
Thanks a lot,
Dino

Hello Dino,
This might happen when the request is originated from a system which is not inside the same transport domain of the target system (QA/PRD).
So if you've DEV > QAS > PRD landscape and you've somehow imported a transport ABCK9xxxx of system ABC into the DEV, then qas then prd, it won't appear automatically in the next target queue, but you've to manually add it.
Regards,
Debasis.

Systems in same transport domain, but PRD import queue is empty

Hi all!
I have previously set up ERP 2005 development and QAS system, and there has been some development and transporting occuring between these two systems. Now I have installed the production system and added it to the transport landscape in STMS. The three system are in the same transport domain and the same transport group. In STMS I have created the Delivery route to the PRD system.
When I check the import queue for the production system, only transports created AFTER the installation of the production system appear in the import queue. Transports created and released from DEV to QAS before the production system was available is not displayed in the queue.I know that I can add single requests to the import queue easily, but that required a lot of manual work and making sure that the transports are added to the queue in the correct sequence.
How can I get all the transports to appear in the PRD system import queue? In AL11 in PRD, I am able to access the TRANS_DIR and I see all the transport requests in the directory.
Regards,
Thomas

Hi Thomas,
"Only transports created AFTER the installation of the production system appear in the import queue." - <b>This is expected</b>
From table E070, you can get a list of all transport imported into QAS system. Sort that list according to the date imported, and save the transport requests into a text file.
Run this below script from production by logging in as <sid>adm.
Provide the transport text file as an input to the script. It will add the transports to queue automatically one by one.
@echo on
set SID=<Prd SID>
set CL=<Client>
set filename=<drive>:\usr\sap\trans\scripts\transports.txt
FOR /F "tokens=1,2* delims=K" %%i in (%filename%) do (
tp addtobuffer %%iK%%j %SID% client%CL% pf=<drive>:\usr\sap\trans\bin\TP_DOMAIN_%%i.PFL >> )
Before running the script, take a backup of the production buffer at the OS level, incase u need to restore it.
Cheers,
Fahad

Regarding the import

Hello Guru,
I have transported the tranport request using the transaction STMS. So how i can import in the next system.
please give me details.
it is urgent.
Thanks in advance
zubera

Use transaction STMS
Look at Transport Management System (BC-CTS-TMS) and System Administration Assistant
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCTSTMS/BCCTSTMS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCRRR/BCRRRSAA.pdf
Importing Requests
Use
You can use three different methods in the TMS import queue to import requests into the target system. You can choose between performing any of the three methods in dialog, or in the background. The best method for you depends on your system landscape and your transport
strategy [Ext.]. In practice, you will find that a combination of these methods is the most effectiveway of working with the TMS. If you only want to import individual requests or projects into a system, you can change the transport strategy
Prerequisites
Before you import the requests from an import queue into an SAP System, ensure that no users are working in this SAP System. Therefore, inform your users about the import times early on, for example by creating a system message.To prevent change requests from still being placed in the import queue shortly before the mass import, and perhaps being imported unintentionally, we recommend closing the import queue before the import. Also read the notes on Precautionary Measures in the Target System
Functions
Starting the Import of All Requests in an Import Queue (Mass Transport
Strategy)
When you import all the requests from an import queue, they are imported in the order in which they are placed in the queue. Each import step is performed for all requests. First, all the Dictionary objects in the requests are imported, then all the Dictionary objects are activated, and then the main import is performed for all requests. If you use this method to export all your requests from your development system into your quality assurance and production systems, then you are assured of keeping the Customizing and Workbench objects in your systems synchronized. However, this method is less suitable if you develop in different projects at the same time, test them in the QA system, and then import the projects into your production system at different times. This applies especially to the production system.
Starting the Import of All Requests in One or More Projects
If you have assigned your transport requests to projects (see Using Projects to Control Transports [Ext.]), you can import all requests that belong to a single project together. The requests are imported in the order in which they are placed in the import queue. This also applies if you want to import all the requests from multiple projects together. All the requests in one project are not imported first, followed by all the requests in the next project. Instead they are imported in the order in which they are placed in the import queue. Each import step is performedfor all requests, just like when you import all requests from a queue. First, all the Dictionary objects in the requests are imported, then all the Dictionary objects are activated, and then the main import is performed for all requests.
Starting the Import for Individual Requests (Single Transport Strategy)
As well has having the option of importing all requests in the import queue, or all requests in a project, the TMS also allows you to import individual requests from the import queue. The requests you choose are imported in the order in which they are placed in the import queue. The order of the mport steps corresponds to an import of all requests. Importing single requests can either be _ an exception, if you usually use mass transports _ or the rule if you usually use single transports. Examples for using single transports:
_ Every week, you import changes into your production system that you have previously tested in your QA system. To do this, you have scheduled an import that periodically imports all waiting requests. If you want to correct an error in the production system between these
import times, you can import the request into your quality assurance and production system at an earlier time. As standard, the TMS imports a request of this type as a preliminary transport. This means that it stays in the import queue after it has been imported, and is imported again in the next scheduled import of all requests, to avoid inconsistencies. In this scenario you can also use the Transport Workflow [Ext.], as of Release 4.6. Developers make the transports into a test system. Developers have the authorization to import their own requests. Since only individual transports are made into the system in this case, the system administrator sets the system so that the requests do not remain in the import queue after the import (see Starting the Import for Single Requests.To find out about the requirements you need to meet, we recommend that you read the following
information:
_ Transport Strategy in the CTS [Ext.]
_ Transport Strategy for Single Transports [Ext.]
Test Imports
Before you start or schedule any of the import methods discussed above, you can test them with a test import. This lets you recognize any conflicts with original objects and repairs.
Regards

How to clear import queue?

Hi All,
we are using WebAS 6.20 and we have a huge number of transports in our landscape.
The import queue of our systems therefore is quite big (several thousand transports) and slow.
I found an option "Delete Imported Requests".
But most of the transports get a yellow (ready for import again) or green (waiting to be imported) status after import and not an "already imported" status.
So the option above ignores them.
Any ideas welcome.
Thanks in advance,
Martin

Hi Martin,
Generally, you'll want to keep the list of transports shown in the queue short and leave the transport files out on in the transport directory for a longer period of time. But, that of course depends on how much space you have and the policies your company has for keeping files around.
Is this for a large installation of SAP?
Thanks,
J. Haynes

Assets Mass Addition error-APP-OFA-48400

Hi,
We are working on Oracle Applications 11i. The Assets user have run the post mass additions and the Mass Additions post gave no output when it completes successfully (POST MASS ADDITIONS REPORT and two of the MASS ADDITIONS POST resulted in error before the thired one completes successfully) and there is still one item X in the POST queue in the mass additions.
Item X was one of two items in the same PO and same invoice the second item Y was POSTED successfully and now has an asset number.
I have checked the po charge accounts, ap expense account and fa clearing account and they match.
Any clues?
This matter is urgernt please due to the period closing.
Found the following error in one of the logs:
At least one of the child requests failed.
Cause: At least one of the child requests spawned to run Mass Additions Post failed.
Action: Check the Mass Additions Post log files to find out what caused the request to fail.
Error: function famgpi returned failure (called from FAMAPT)
APP-OFA-48400: Error: function famgpi returned failure (called from FAMAPT)
Edited by: AHS on Feb 4, 2010 1:37 AM
Edited by: AHS on Feb 4, 2010 1:48 AM

Thank you for your help.
unfortunately, i have no access to metalink these days.
We had also the following error ; on the attempt to open the assignment form of the item:
APP-OFA-48317: the employee to which this distribution line is assigned is no longer valid.
when the form opens there is no emmploye visible in the assignment line.
and in the table FA_MASSADD_DISTRIBUTIONS an employee_id is there.
So, I chose an employee in the form and saved it, then I cleared the employee from the line and saved again.
Finally the problem is solved.

STMS import queue

HI all,
Think some body deleted TR request (or something happend in the import queue) from the import queue, from that day onwards there was no transports are going on from development to quality systems. is there any chance to rebuild import queues, it was a problem in STMS imports.
pls help me.
cheers,

Did you refresh the list with refresh button?
If yes, check release log of that particular transport.
Hope it helps.
Regards

STMS - transports get hung on tp import

Hi
There are a number of threads regarding this and I've also looked at OSS note 71353 but so far none have fixed my problem.
When I attempt to import to my new development environment, the transports just hang. There are no entries in TRJOB and TRBAT. I delete the files from stms, kill the tp.exe process from the OS (Windows) but when I add the files back to the import queue and attempt to reimport them, the little truck still appears saying that the import is already running.
I should mention that this new development system was previously the QA system. It is a SAP_ALL client copy of Production. Even when I choose the overwrite originals options for the import of the transport, it still fails.
Any assistance is greatly appreaciated.
Thanks
Conor

hello Connor,
You had delete old tp log files. Further you also need to delete any old entires from import monitor inside stms. Make sure all tp processes are killed as well.
Once this done try importing again. If it works out fine. If not then trying importing the request using TP commands at OS level.
If TP import goes successfully then try importing another request to check if it is fine. Also check if any old import job is running.
There are lots of checks and a number of solutions to this issue.
I have faced this issue a dozen times and solved it in atleast 4 or 5 different ways.
Regards.
Ruchit.

Released request are not in import queue

Dear experts,
Released requests are not appearing in the import queue. They are not in the cofiles folder also. Can any one help me to get these requests in import queue.
rgds.....
Art

Hi,
Please go to SE01, select your request(s) and on the next screen click on the request. In the opened screen navigate to the properties tab and see what target system you have defined for the transport. If there is no definition, transport is considered as local and will not be released to cofile/data folders (but stays in E070). You have to define the correct target system as it's defined in TMS to make you request tranportable
Regards,
Mike

Transport mass addition to the import queue

Similar Messages

Maybe you are looking for