I will list the basic steps which you already might know but can be helpful in t imes of urgency and at times when immediate action is needed:To identify the rootcause and solve it accordingly: Go to SE38, execute the report RSTPTEST. It tests the tp status and STMS configu ration check. In STMS_IMPORT transaction -> in menu click on Goto -> tp system log .. this wil l give you if any error is there . Check in SM37 whether RDD* jobs are running or not. If not, schedule them and im port of the transport again. Check in SM13 whether update is active or not as sometimes the update gets into error. If it is not active, activate it Check in SM50 if all background workprocesses are in running status and there ar e zero waiting BGD processes. If so, you will need to wait for the free backgrou nd workprocess to run RDD* jobs to complete the import of the transport. Check if any of the filesystems (like sapmnt, oraarch etc) of the Central Instan ce, Database and application servers is 100% full. If so, please add necessary space. If the above does not helps in solving the issue, try the below things:Move the files from /usr/sap/trans/tmp to some other FS Delete all 'in process' requests from import monitor tab in STMS kill all the work processes from OS level which are running tp make sure that no job is in process named RDDIMPDP Clear entry from TRBAT and TRJOB tables. Also delete any *.LOC file located at / usr/sap/trans/temp location. Reschedule RDDIMPDP Background Job by executing RDDNEWPP report (using SE38) in 000 (under DDIC user) and all the required clients. Try to import the Trans. request(s) again into system using stms_import. The last option would be to restart SAP instance at non-productive time, clear a ny TRBAT/TRJOB entries, reschedule RDDIMPDP Background Job by executing RDDNEWPP report in 000 (under DDIC user) and all the required clients, and then re-impor t the Transport Request Also from OS level, one can kill all the TP processes which are in hang state an d restart the import process.