transport error "Program terminated (job: RDDEXECL, no.: 09264700)"

[Former Member]

Hi,SDNs

when transport a request including process chain , it happened error:

Anyone who can help me ,thanks!!

Program terminated (job: RDDEXECL, no.: 09264700)

Message no. TR012

Diagnosis

Program "RDDEXECL", which was started in the background, was terminated abnormally.

System Response

The system created a job log for the terminated program.

Procedure

Proceed as follows:

1. Log onto the system in which the program was executed. The system is specified at the beginning of the transport log.

2. Then call transaction SM37 to display the job log.

3. Enter "RDDEXECL" as job name and "DDIC" as user name.

4. Restrict the starting date to the starting date specified in the transport log.

5. For the other selection criteria, select only jobs with the status "cancelled". Then press Execute.

A list of the jobs satisfying the selection criteria is displayed.

6. You can display the log by pressing Job log.

If the list contains several jobs, you can select the job with the ID "09264700" with Display -> Job details or define further details for the selection criteria in the initial screen of transaction SM37.

If the ABAP processor reports cancellation, double-clicking on the corresponding message in the job log branches to the display of the corresponding short dump.

[Former Member]

Run SP12 - Temse Consistency check and delete the inconsistent objects.

Then run the job again.

Regards,

Anil

[Former Member]

Hi,

The job should be automatically triggered again with DDIC user. If this dosent happen try scheduling the RDDEXECL job in se36.

I had similar problem and this rescheduling and running the job worked. Hope this will help you.

Regards,

Varun

Edited by: Varun Varma Pinnamaraju on Sep 5, 2009 6:36 PM

[Former Member]

Hi Terry,

I had the same issue with one of my transports - it cancelled my transport with an error '12'. After investigation it appeared it didn't like one of the transformations.

We tried transporting the same request again and it cancelled again.

I then created a new transport with all the same objects and it went in OK.

Thanks

Scott