on 09-24-2010 8:46 PM
I have scheduled the "Import All" job to run periodically in my Sandbox system. After the job runs, the STMS_IMPORT command still shows the transports in the queue with the "clock" for status, meaning that the transport is scheduled to be imported. (Even after Refresh) The transports do not get imported again with each scheduled run of the job, but I would like for the transports to disappear from the queue. This is how it functions in my QAS system (set up by consultants a while back). I can manually delete the transports from the TMS queue after they get imported, but I was wondering how to have this happen automatically. Right now, transports get released from DEV and go into the QAS TMS queue. When that periodic import job runs, the QAS transports get imported and routed to my PROD queue. At that point, the QAS transports no longer appear in the QAS TMS queue. Once the PROD transport is imported (done manually), then the transport gets routed to my Sandbox TMS queue. This is where another periodic import job runs. After the transport is imported, I want it removed from the sandbox TMS queue. Any ideas how I make this happen?
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should be able to import the transport request from any system.
OK, after importing the transport from QAS to PRD can you please go to import monitor (CNTRL+F8) --> Goto --> Display tp System log. go to last and see what messages/errors you get.
also check whether there are free BTC work process.
These are the last set of messages in the tp system log:
START imp all XES 20100926180608 P00039600 SAPXESA 20100926180603934
INFO: event SAP_IMPORT_START triggered successfully
START SET STOPMARK XES 20100926180610 P00039600 SAPXESA 20100926180603934
INFO: Buffer saved as
sapnprd\sapmnt\trans\buffer\XESSAV.
STOP SET STOPMARK XES 20100926180610 P00039600 SAPXESA 20100926180603934
INFO TBATG CONVERSION OF XES N not needed P00039600 SAPXESA 20100926180603934
START MOVE NAMETABS XES 6 20100926180611 P00039600 SAPXESA 20100926180603934
START tp_getprots XES P 20100926180611 P00039600 SAPXESA 20100926180603934
STOP tp_getprots XES P 20100926180614 P00039600 SAPXESA 20100926180603934
STOP MOVE NAMETABS XES 6 20100926180614 P00039600 SAPXESA 20100926180603934
INFO TBATG CREATION OF EN XES n not needed P00039600 SAPXESA 20100926180603934
START REMOVE STOPMARK XES 20100926180616 P00039600 SAPXESA 20100926180603934
STOP REMOVE STOPMARK XES 20100926180616 P00039600 SAPXESA 20100926180603934
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all XES 0000 20100926180616 P00039600 SAPXESA 20100926180603934
START INFORM SAP-SYSTEM OF XES Q 20100926180616 P00039600 SAPXESA 20100926180603934
START tp_getprots XES Q 20100926180616 P00039600 SAPXESA 20100926180603934
STOP tp_getprots XES Q 20100926180619 P00039600 SAPXESA 20100926180603934
STOP INFORM SAP-SYSTEM OF XES Q 20100926180619 P00039600 SAPXESA 20100926180603934
-
There are plenty of BTC processes available.
Please read SAP note 449270 about RDDIMPDP and SAPEVT issues.
Hi Bill,
For mass import, do not check the box "Select All Requests for Later Import". Other than that, please make sure that you have the latest kernel, tp version, etc. According to Note 565574, the imported TRs are automatically deleted from the import queue after the import (although I noticed that they would stay there for a while before disappearing
Regards,
Dao
Hi,
May be you can cross check the variants of Job running in your QAS environment.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.