Unforeseen Issue during SAP BW Data Flow Migration
Purpose: To migrate SAP BW Data Flow from 3.x to 7.x version.
Tool: RSMIGRATE (provided by SAP)
SAP makes our life easy by providing a great tool to migrate the BW 3.x version to 7.x version automatically. It also provides supportive SAP Notes/KBA for the known errors and issues.
However, there were undocumented few issues which we came across during our migration activities.
In this post, we will share 'unforeseen issues' and their resolutions which were mostly manual efforts.
However, there were undocumented few issues which we came across during our migration activities.
In this post, we will share 'unforeseen issues' and their resolutions which were mostly manual efforts.
1. Update Rule - Return Table Logic: In SAP BW 3.x version we have Return Table logic to replicate the source record into multiple record based on key figures as per the requirement. However, in Transformation this return table is unsupported and cannot be converted by RSMIGRATE tool automatically.
We need to correct it manually by writing the split logic in end routine.
Here is the key, which we can use-
We need to correct it manually by writing the split logic in end routine.
Here is the key, which we can use-
2. DTP failed with - GETWA_NOT_ASSIGNED: Sometimes we don't do the homework before we start the work and afterward face the consequences.
This error we face while DTP failure. It is because we have G_S_MINFO, which is used to get the runtime information of the IP, which does not support in Transformation and cannot be converted by migration tool automatically.
Again, we need to correct it manually by using the class p_r_request and call its corresponding methods.
3. Master Data Text - Infopackage: Even SAP has confirmed that Infopackage for Text Master Data cannot be converted by migration tool so we need to manually create a DTP and copy the same selection from Infopackage.
4. Replication of routine in DTP filter: This weird issue occurs when DTP filter routine gets copied from IP filter and replicated many times. It has to be corrected manually.
5. 3rd Step of Migration: Yes, at the 3rd step i.e. "Create DTPs from Infopackages". Sometimes this step fails due to a weird behavior of tool; during migration it will show the update rule and its corresponding transformation which is part of the second step.
This can be corrected by recovering the step and subsequent re-migration but sometimes this does not work and again, we need to fix it manually.
@SAPReaders - Please comment your findings and share it with others.
Thanks for sharing this Information. SAP BW Training in Gurgaon
ReplyDeleteI am really happy to say it’s an interesting post to read. I learn new information from your article, you are doing a great job. Keep it up
ReplyDeleteSAP Data Migration Services