Skip to Content
Author's profile photo Former Member

Transport of Transformation failed with RC= 12 and job: RDDEXECL cancelled in Target sytem

We were getting failure while transporting one of Transformation from source to target system.

Error in source system:

Program Terminated (job: RDDEXECL,),

Ended with return code:  ===> 12 <===

Error in Target system:

We found job RDDEXECL is cancelled with reason: Uncaught Exception

Attachment ‘Error details’ which includes scree shot of above error details

Issue analysis:

Using program, RSTRAN_ROUT_RSFO_CHECK we found inconsistency in Rules/mapping of Transformation object in modified version.

Pass Transformation ID and OBJVERS = M and then click on check box ‘SIMULATE’ to get issue for given transformation.

Inconsistency is basically in below transformation tables where entries are not correctly updated for Modified version of transformation

• RSTRANSTEPROUT

• RSTRANROUTMAP

Solution Applied:

There are two ways; we could fix this issue. After following step, transport would go successful to target system.

1->Run the program RSTRAN_ROUT_RSFO_CHECK with following selections:

OBJVERS = M

TRANID = transformation ID

Click on Check box: REPAIR_W

This will fix the problem.  In case, transformation gets inactive after running above program. You can activate back using program: RSDG_TRFN_ACTIVATE

2->Change/delete/adjust entries of Tables according to source system.

• RSTRANSTEPROUT

• RSTRANROUTMAP

You may Change/delete/adjust entries of table with debugging option and then make sure entries of these tables should be same as in source system

Assigned Tags

      7 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Nilesh Jha
      Nilesh Jha

      Nice article Dinesh!!  We were facing the same problem in our project. This is really heplful.

      Author's profile photo Former Member
      Former Member

      Very helpful blog, thanks for sharing with us.

      Author's profile photo Former Member
      Former Member

      OSS note 1801309 has the same fix officially documented.

      But this was very helpful. thanks,

      Author's profile photo Former Member
      Former Member

      Hi  Dinesh,

      Very useful blog..

      Regards,

      Rajesh

      Author's profile photo Chandra Bonthala
      Chandra Bonthala

      Thanks Dinesh.. it resolved my issue

      Author's profile photo Former Member
      Former Member

      This was the perfect solution I was looking for. Solved my error. Thanks Dinesh!!!!

      Author's profile photo Former Member
      Former Member

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

      Then run the job again.

      Regards,

      Anil