+3As I’m learning Data Migration Manager I have created a few projects. For a couple of them, while Mapping Legacy Tables to Migration Object there has not been any Target Tables available in the Smart Mapping assistant and I have had a hard time figuring out why. Am I missing any setup? What are the requirements for Target Tables to be available for Smart Mapping?
Best answer by Jens
Hi
possibly the creation of the “migration object”, the “mapping legacy tables to migration object”, the connection of the target table to the “migration object”, the creation of the target table definition and setting the scope was not done in the right order.
Without using a DMM project template
I assume you performed the steps without number 2 and/or 3 and these steps you performed afterwards. I’m only thinking loud.
You can try the following now please:
Go to the “Mapping legacy tables to migration object” screen and now press the button “Mapping Detail [Options]”.
Here execute “Resync Mapping Target Fields”.
Is your target table CUSTOMER_INFO now visible and available for the mapping?
This functionality fetches all target tables in scope (with created target table definitions) related to the selected migration object and also perform changes related to the target table definitions (important if you have for example new fields in your target table which didn’t exist in the previous mapping - but then you you also have to perform “Extract Meta Data” in the target table definition to get “new/modified/removed” fields).
So if you would already have one target table for one migration object in the mapping available and now you add a 2nd one then you also have to use this functionality to see your 2nd target table.
/Jens
+5Hi
You need to have any target tables connected with the migration object which you have on your Mapping Legacy Tables to Migration Object.
you need to have the legacy table with lock load here.
If you have these configured on your project setup, then you can be able to do the mapping on the smart mapping
+1And all target tables you want to migrate to must be assigned to the migration object.
Migration Scope - Technical Documentation For IFS Cloud
+3Hi
Thanks for your answer Nirogiri Janstin.
I don’t think so though, as it has not been necessary in other projects to do that. The target table is not possible to select there either.
+3And all target tables you want to migrate to must be assigned to the migration object.
Migration Scope - Technical Documentation For IFS Cloud
Thanks for your answer
It is connected to a Migration Object and still not available to select.
+5And all target tables you want to migrate to must be assigned to the migration object.
Migration Scope - Technical Documentation For IFS Cloud
Thanks for your answer
It is connected to a Migration Object and still not available to select.
Mak sure you have your target table as in scope on your project basic data setup
+3And all target tables you want to migrate to must be assigned to the migration object.
Migration Scope - Technical Documentation For IFS Cloud
Thanks for your answer
It is connected to a Migration Object and still not available to select.
Mak sure you have your target table as in scope on your project basic data setup
Target Table is in scope and Target Table Definition is Created.
The connected Migration Object is also In Scope and Used in Mapping
+10
Hi
I assume you already refreshed the browser cache?
Can you please provide some screenshots of your current setup and the name of the target table which will not be shown?
So e.g.
Within the migraiton object the “Migration Object Details”:
As I have added no “Legacy Tables with locked loads” in the previous screen there will be of course no “Locked Legacy Table Names” as seen in your screenshot but I can select my target table.
/Jens
+3Hi
I had not tried refreshing the cache previously and tried now without any change.
This is my corresponding setup.
In the last image, the table was not to be found in the Target Table drop down either.
+10Hi
possibly the creation of the “migration object”, the “mapping legacy tables to migration object”, the connection of the target table to the “migration object”, the creation of the target table definition and setting the scope was not done in the right order.
Without using a DMM project template
I assume you performed the steps without number 2 and/or 3 and these steps you performed afterwards. I’m only thinking loud.
You can try the following now please:
Go to the “Mapping legacy tables to migration object” screen and now press the button “Mapping Detail [Options]”.
Here execute “Resync Mapping Target Fields”.
Is your target table CUSTOMER_INFO now visible and available for the mapping?
This functionality fetches all target tables in scope (with created target table definitions) related to the selected migration object and also perform changes related to the target table definitions (important if you have for example new fields in your target table which didn’t exist in the previous mapping - but then you you also have to perform “Extract Meta Data” in the target table definition to get “new/modified/removed” fields).
So if you would already have one target table for one migration object in the mapping available and now you add a 2nd one then you also have to use this functionality to see your 2nd target table.
/Jens
+3Go to the “Mapping legacy tables to migration object” screen and now press the button “Mapping Detail [Options]”.
Here execute “Resync Mapping Target Fields”.
This functionality fetches all target tables in scope (with created target table definitions) related to the selected migration object and also perform changes related to the target table definitions (important if you have for example new fields in your target table which didn’t exist in the previous mapping - but then you you also have to perform “Extract Meta Data” in the target table definition to get “new/modified/removed” fields).
So if you would already have one target table for one migration object in the mapping available and now you add a 2nd one then you also have to use this functionality to see your 2nd target table.
This resolved the issue, Thank you
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.