What is the exact version of Hyperion are you on(including patch level)?(the latest version of FDMEE is 18.104.22.168.200)
Also are you saying your explicit maps have records with the same source values going to two different targets?
If you have the map files for each location in a flat file(e.g source,target) you could simply do a basic excel process to remove the duplicated records and upload that file to the FDMEE location.
Also since it is an upgrade this is the time to really look at the process for map uploads going forward.
We're migrating from FDM 22.214.171.124 to FDMEE 126.96.36.199.200. We're only doing a technical migration and upgrade so business process change isn't in scope but I agree. The difficult thing is that they have users globally updating their mappings; it's not centralized in one place. We can run location analysis reports and artifact change reports but there are a number of changes.
The main challenge is with sequencing with LIKE maps. In FDM, there is a sequencing column, where in FDMEE the rule name takes that role. However, since there are a lot of new maps created and changes in existing maps, when we try and add those maps, it impacts the sequencing of the LIKE maps.
Is there a way to do this efficiently?
If you are doing the migration would not it be more efficient to lock the source system down for a period time(e.g a weekend) then migrate to the new target PROD and then do a validation to make sure everything is working as expected at that point in time? Also you could have had been doing training with users so they know how the new system works so after the validation you all simply have a cut over.
if things are changing things in the source (you have a moving goal so not sure how you could really efficiently validate) after you have created the target then you have to have developed a process in place to update the new environment. (e.g user might have to make the updates in both system)
Also the issue noted in the prior thread was duplicate records with the same source pointing to different targets, not a like map issue so again it goes back to setting up a process for change.
You and your team really need to go back and determine a strategy.
I am sure other expert will chime in with their recommendation too of what you could do at this state.
I like suggestions from @USER1211. Get client to agree on a code freeze for FDMEE and related applications. During freeze, migrate the data load mappings from FDM Classic to FDMEE.
In terms of removing duplicate data load mappings, you can export the data load mappings to Excel, remove duplicates, and create map loaders to get maps in FDMEE. (For those mappings that do not have member mapping scripts, you can use text file map loaders. I find them easier to use than the standard FDMEE Map Loader for Excel.)