cancel
Showing results for 
Search instead for 
Did you mean: 

Problem when porting a transport request.RDDIMPDP could not be started.

Former Member
0 Kudos

Hi,

I am facing a problem when porting a transport request.It just hangs.

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

ERROR: Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

When I execute the report RDDNEWPP in SE38,it shows me to choose either with normal priority or high priority(for transports).

Later it displays the message"Background job RDDIMPDP_CLIENT_300 successfully scheduled in client xxx(job class A)" for high priority.

But when I check it in SM37,the job is not shown.Can anyone help me overcome this issue.

When I check in the tp System Log,it shows the following

***************************************************************

START TRANSMIT BUFFER ENTR XQ1 g 20090414130408 90001501 INBDQ-S-XQ1

STOP TRANSMIT BUFFER ENTR XQ1 g 0000 20090414130408 90001501 INBDQ-S-XQ1

START TRANSMIT BUFFER ENTR XQ1 g 20090414130419 90001501 INBDQ-S-XQ1

STOP TRANSMIT BUFFER ENTR XQ1 g 0000 20090414130419 90001501 INBDQ-S-XQ1

START imp single XQ1 20090414144843 90001886 INBDQ-S-XQ1 2009041414484

INFO TBATG CONVERSION OF XQ1 N not needed 90001886 INBDQ-S-XQ1 2009041414484

START MOVE NAMETABS XQ1 6 20090414144845 90001886 INBDQ-S-XQ1 2009041414484

START tp_getprots XQ1 P 20090414144845 90001886 INBDQ-S-XQ1 2009041414484

WARNING: System XQ1. Warning. 20090414145251 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System XQ1. Warning. 20090414145751 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System XQ1. Warning. 20090414150251 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System XQ1. Warning. 20090414150751 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System XQ1. Warning. 20090414151252 :

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System XQ1. Warning. 20090414163258 :

ERROR: Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

ERROR: I'm waiting 100 sec (Count: 21).

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System XQ1. Warning. 20090414163306 :

***************************************************************

Please help.

Regards,

Sudheer.

Accepted Solutions (1)

Accepted Solutions (1)

debasissahoo
Active Contributor
0 Kudos

Hi Sudheer,

This job is a event driven job. so check in SM37 accordingly. If you still don't see the job scheduled, run RDDNEWPP in 000 client with DDIC user id preferably. the following notes should help you.

https://service.sap.com/sap/support/notes/11677

https://service.sap.com/sap/support/notes/71353

The new procedure (from Maintenance Level 2.1G onwards):
Background job RDDIMPDP is no longer started automatically every 5 minutes; instead, it only runs when the transport control program, tp, triggers a specific SAP event.
To schedule the event-controlled background job RDDIMPDP, log on to the source/target system as user DDIC in client 000 and execute report RDDNEWPP (using Transaction SE38).

Regards,

Debasis.

Edited by: Debasis Sahoo on Apr 14, 2009 10:39 PM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Sudheer,

run this report in client 000 with ddic user,it should be fine

Rohit