Skip to Content
Author's profile photo Former Member

Transport Transformations failed in CL_RSO_TLOGO_PERSISTENCY with “UNCAUGHT_EXCEPTION” dump

I have seen recently a lot of problems related to the transport of transformations in program CL_RSO_TLOGO_PERSISTENCY, and I thought, it would be a good idea to give a brief overview of this issue, and how this dump can be avoided. Furthermore, I would like to give you some hints, what should be checked to analyze the problem and finally in the last part of this blog entry, I would like to summarize the release specific properties. 



A versioning of the BW metadata has been implemented in the t-logo framework with BW 7.30. If transformations contain orphaned metadata, this dump occurs as a result. In many cases the issue occurs more specifically because there are some inconsistent entries for affected transformations in tables RSTRANSTEPROUT and RSTRANROUTMAP.

Running report RSTRAN_ROUT_RSFO_CHECK (to check formulas and routines with regards to completeness & consistency of metadata) will return the list of affected TRANIDs & their related errors.

Effects of note 1369395

You should only check the post manual steps from this note, where instructions from report RSTRAN_ROUT_RSFO_CHECK are described.

This report will check the formulas and routines with regard to completeness or consistency of metadata.

You should run this report first on “Check” mode for indentify the inconsistencies, and then in “Repair” mode for correct them.

Caution: You have to perform this manual activity separately in each system into which you transport the Note for implementation.

After that, run the report in check mode again and see the results.

If the error messages still persist, delete the T version via Class CL_RSTRAN_STAT => DELETE_VERSION_FROM_DB. You can see more information about this step on note 1720202.

So in resume the procedure would be:

  1. Run the report in the source and in the target system for ALL affected transformation for both A and M versions and repair them.
  2. Follow the steps provided in the note 1760444 Transport failure: The object name is not allowed to be empty.
  3. Include the code correction from note 1801189 to your system.
  4. Reactivate all affected transformation in the source and target system of the transport.

Please note that, this action cannot be transported and must be executed in all target systems of the transportation landscape.

Another very relevant information is that you must transport the cleaned up transformation using a NEW transport.

The old transport contains incorrect objects and can no longer be used. You should delete the old transport from all import buffers.

When you create a NEW transport request, make sure that all the necessary routines are included, for this flag ON the option “All necessary objects”.

List of referenced notes and documents:

1720202 – Dump ‘ASSERTION_FAILED’ in class CL_RSTRAN_GEN / error message RSTRAN 710 during the activation of a transformation

1760444 – Transport failure: The object name is not allowed to be empty (R7105)

1801309 – Dump in CL_RSO_TLOGO_PERSISTENCY during the transport / RSO663 / RSO252

1880563 – Manual task for DUMP in CL_RSO_TLOGO_PERSISTENCY

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Javier Fernández Mateo
      Javier Fernández Mateo


      Very thankful! I managed to solve my problem following this guidelines.

      thanks, Xevi