Skip to Content
Author's profile photo Sheetal Maharshi

RSMIGRATE- Migration of dataflows from 3.x to 7.x- Part 3

Hello Again ,

In my previous two blogs , i have discussed about the Migration steps of Master Dataflows and Transactional Dataflows using RSMIGRATE.

In this blog I will be sharing some common errors that you may encounter using SAP tool – RSMIGRATE.

1. Post Migration using RSMIGRATE, the newly created DTPs and transformations are not captured in the Transport Request.

Solution: Capture the objects through Transport Connection in RSA1.

2. Error in transformation during migration when no rule exists.

Solution: This error occurs when there are no mappings present for the newly created transformation. Manually create the mappings in the transformations and add the routines, if any (start routine/field routine/end routine) in RSA1 for that dataflow.

3. Data sources not being activated during Migration, due to missing currency/unit fields during migration.

Solution: Add the Currency and Unit fields to the data source.

4. Process Chains and the relevant info packages and other objects are locked while trying to select the objects to be migrated from the flow, after creating and saving migration project.

Solution: The object gets locked if it is being used in some other migration project. In such cases, first unlock the objects from the existing migration project in which they are already captured and then try to add the same in the new project.

Note: Make sure that the existing migration project is successfully completed and transported to the Quality system, before unlocking it.

5. There might be a situation when we are unable to create transformation for Transfer Rules for any InfoObject while migrating through RSMIGRATE as below :

Solution : Migrate them manually and collect all objects from Transport

6. If two dataflows are sharing same data source / InfoSource, then locking issues may occur.

Solution: In such cases, all objects can be collected in a single Migration project and collected in same Transport request

Hope all my blogs on migration would provide you good insight on RSMIGRATE.

Please do share your feedback.




Assigned Tags

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

      Hi Sheetal


      I am performing migration for the 3.x to 7.x flows. i am stuck at two issues. Could you help

      1. when migrating the hier flow after migration of the data source i am unable to activate it. It is giving error i am attaching the snapshot for the same for the quick reference purpose. I have seen this link of the hierachy migration. But the same i am performing the steps.
      2. When i am trying to migrate the data flow whose data source is myself system only. is creating a problem. which means suppose we have BW1 system which is development and data source is based on this system only.
      Author's profile photo Former Member
      Former Member

      Hi Karan,

      It looks like there is an ABAP code (in the routines) which might be causing this (as per your screenshot saying "Statement concluding with". You might need to use TYPE instead of LIKE in such scenarios in the upgraded platform.



      Author's profile photo Former Member
      Former Member

      Hi Sheetal,

      here is my requirement

      I have a 3.x flow Process Chain and having 37 Master data objects including(30 TEXT,6 ATTRIBUTE AND 1 Hierarchy objects). Now,I would like to migrate all these MD objects to 7x data flow so I choose RSMIGRATE Tool.

      Created one Migration Project

      add all 40 Master data(TXT,ATTR,HIER) flows to this project,save and select until first 5 steps to migrate.

      and start execution the migration button

      after sometime I faced short dump error

      I got a screen like nodenotselected choose Infoarea to assign infoobjects and i choose one custom infoarea and after that I stuck up at below error.

      Please try to help me....much needed.

      Author's profile photo Sudhakar P
      Sudhakar P

      Implement the Note 2442091 (Shortdump during Migration of Transfer Rules). That should work.