Skip to Content
Author's profile photo Former Member

RC12 & ABAP Short Dump ASSIGN_TYPE_CONFLICT & SYNTAX_ERROR during DTP Load & Transports

This article is based on SAP BI 7.30 version with support package 5.

Sometimes we would encounter ABAP short dumps during transports or during data load through DTP’s for new developments or for changes in the existing developments.


These errors occur when the Infocube & DSO are changed & without recollecting the related transformations.  There are 2 possibilities which would occur

  1. ) Your transport might fail with RC12  throwing error “Uncaught_Exception” with an exception as “CX_RS_PROGRAM_ERROR” and the program which is terminated as “CL_RSO_TLOGO_PERSISTENCY======CP”.
  2. ) Your transport is successful and data load through DTP fails with the error “Assign_Type_Conflict”.

The reasons for these are that

  1. ) when the Infocube or DSO is changed, the program(new metadata) which is generated get’s updated with the time & date and the logic. The generated program in source is different to the one in target. So when you transport these changes of only the data target’s without the transformations(these transformations does not include the changes done to the Infocube), the program gets updated in the target system. But the transformations in the target system are still pointing to the old generated program (this is orphaned metadata). This is when you would get a data load error “Assign_Type_Conflict” through DTP load.

During Data Load:

During Data Load.jpg

During Transports:

During Transports.jpg

The way to rectify this is using the SAP Note 1627236 which I have given below in a simpler format.

In a gist:

  1. ) Delete the inconsistencies in the transformations using function module in the source system.
  2. ) Re-Collect the transformations in a new transport.
  3. ) Delete the inconsistencies in the transformations using function module in the target system.
  4. ) Transport the newly collected objects to the target system.

In detail:

  1. ) Run the function module “RSTRAN_ROUT_RSFO_CHECK” using SE38 in the source system. SE38a.jpg
  2. ) Copy the technical ID of the transformation which is causing error and paste it in the function module. RSTRAN 1.jpgRSTRAN 2.jpg
  3. ) Run the program for the the transformation  with both “M” & “A” object versions with the option “Simulate” selected.
  4. ) If there is no error then you would get a message  as RSTRAN 3.jpg else it will display the error message.
  5. ) Once running the program with “Simulate” option is complete, run it with “Repair_W” option checked for both “A” & “M” options. Choose option “Yes”. If it asks for a transport then collect it else after this step is done, collect the transports again in a new transport.RSTRAN 4.jpgRSTRAN 5.jpgRSTRAN 6.jpg
  6. Note: The steps given above have to be done exactly the same way in target system before doing the transports
  7. If there are multiple transformations, it’s good to collect each of them in a separate transport along with their DTP’s. This helps in identifying the transformation which is throwing error(if in case you get the error again).
  8. Once the above steps are complete in the target system, transport the requests from source to target system.
  9. So as to cross check, when you re-do the steps above you would get the msg RSTRAN 3.jpg.

Related SAP Notes: 1627236, 18013091913191.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Satendra Mishra
      Satendra Mishra

      Nice information 🙂

      Author's profile photo Former Member
      Former Member
      Blog Post Author


      Author's profile photo Anshu Lilhori
      Anshu Lilhori

      Please post this document in the below forum

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Yes. shifted it today. Thanks.