When you migrate reference data assets, MDM SaaS uses internal IDs, aliases, and names to identify Reference 360 assets.
Guidelines to migrate Reference 360 assets
Consider the following guidelines when you migrate reference data assets:
•Ensure that you use the same internal IDs for similar source and target assets.
•When you specify an alias for a source asset that has no internal ID, ensure that the alias you specify is the same as the internal ID or the alias of the target asset.
•If the reference data sets of the source and target organizations are matched based on identifiers, such as internal IDs, aliases, and names, then the default code lists of the source and target must also match.
•If the code lists of the source and target organizations are matched based on identifiers, such as internal IDs, aliases, and names, then the source and target reference data sets of these code lists must also match.
•If crosswalks of the source and target organizations are matched based on identifiers, such as internal IDs, aliases, and names, then the source and target code lists of the source and target crosswalks must also match.
Migrating reference data assets
When you migrate reference data assets from one organization to another, Reference 360 uses internal IDs, aliases, and names to identify reference data assets.
When you import an asset, Reference 360 compares the internal ID of the asset with the internal ID of the existing assets.
If the internal ID of the asset doesn't match with that of any of the existing assets, Reference 360 compares the internal ID of the asset with the aliases of the existing assets. If the internal ID of the asset doesn't match with the aliases of any of the existing assets, Reference 360 compares the alias of the asset with the internal IDs of the existing assets. If Reference 360 finds a match but the internal IDs of the source and target assets differ, the import process fails.
If the internal ID doesn't match with any of the existing assets, Reference 360 compares the alias of the asset with the aliases of the existing assets. If Reference 360 finds a match but the internal IDs of the source and target assets differ, the import process fails.
If the alias of the asset doesn't match with that of any of the existing assets, Reference 360 compares the name of the asset with the names of the existing assets.
If an asset doesn't have both internal ID and alias, and an existing asset that Reference 360 compares has either an internal ID or an alias or both the identifiers, then Reference 360 compares the name of the asset with the names of the existing assets.
If the names don't match, Reference 360 creates a new asset. If any of the values match during this process, Reference 360 overwrites the existing asset.
The asset migration fails if the names match but meet the following criteria:
•The assets have different aliases and no internal IDs.
•The assets have different internal IDs.
For example, if the source asset is Cost Center with internal ID int_ccenter and the target asset is Cost Center Category with the same internal ID int_ccenter, Reference 360 compares internal IDs and updates the Alias and Name fields in the target system.
If the source asset is Cost Center with an internal ID int_ccenter and alias ccenter and the target asset is Cost Center Category with no internal ID and alias int_ccenter, Reference 360 compares internal ID and alias and updates the Name field in the target system.
For more information about using the identifiers of assets to import the assets, see Internal IDs and aliases.
You can't migrate job definitions created for Reference 360 assets. All Reference 360 assets aren't published and available in Business 360 Console.