Errors and Warnings
List of identified errors and warnings
This section lists the errors and warnings identified during migration testing.
Description: Rentable unit does not match Location. MAD is not migrated.
Step: 3
Solution: Change Location values of existing Maintenance Activity definitions (AMM 2.0) to a valid combination of property, rentable unit and asset.
Description: Space does not belong to property. MAD is not migrated.
Step: 3
Solution: Change Space values or add Space to Property.
Description: For activities in the Maintenance planner with the regime Condition Based (CB), weekly schedules are not supported on Planning Details of Activity definitions. Since a worker is created during migration, running it will cause this error on the Background TSI.
Step: 3
Solution: Change the schedule to monthly/yearly (on the MAD before migration) to be able to execute the newly created worker.
Description: Fields are not properly configured.
Step: 1
Solution: check configuration (Preparation and Migration considerations).
Description: A free field should be configured in (Standard) activity definitions for the migration of Worktype, Inspectionregime, Functionalityclass or User definid classification.
Step: 1
Solution: Configure free field picklist on the Standard activity definition and/or Activity definition.
Description: Property and/or Space on Maintenance activity definition do not match Property and/or Space on Asset (that is referenced on the MAD)
Step: 3
Solution: Correct the Property and or Space on either Maintenance activity definition or Asset.
Description: The user does not have the correct license to initiate Migration. An appropriate license is needed. (G00505)
Step: 1
Description: The configuration for field 'xx' in Activity definitions must match the configuration in Maintenance activity definitions.
Step: 1
Solution: Align the configuration of (free) fields.
Description: Migration to the Activity planner is not possible because contract-based maintenance activities exist; CMADs exist in 1 or more migratable Maintenance plans.
Scenario Step: 1
Solution: Close the Maintenance plans that contains CMADs. Migration of Contract based plans will be available in a later release. will be available by end of Q1 2026.
Description: The user who triggered the migration lacks the correct function profile to modify elements. Change the user or their authorizations.
Step: 1
Solution: Change the user or the user authorizations.
Description: Predictive based Maintenance Activity Definition (regime PB) with an empty counter
Scenario Step: 3
Solution: Fill in the counter
Description: A field that is mandatory in a Activity Planner related business object is empty on the Maintenance planner.
Scenario Step: 2.5
Solution: Make field in activity planner related business object not mandatory or give all empty fields in maintenance planner related business object a value
Description: A picklist was configured for which ‘Enforced’ = yes and one of the values does not exist in the picklist.
Scenario Step: 2
Solution: Field should not be marked as enforced or value needs to be changed to an available one.
Description: Unable to migrate a maintenance activity definition, because the asset is disposed or achived.
Scenario Step: 3
Solution: User needs to change the asset status or use a different Asset.
Description: The Maintenance Activity Definition does not overlap with the start/end time of the Maintenance Plan it is linked to. It will be migrated as an Activity Definition, but it will not be linked to any plan.
Step: 3
Solution: add migrated activities to the correct plan after migration or correct the start- and / or end date of the existing plan in the maintenance planner.
Description: A field was used as a cluster criterium in the maintenance planner, but that field is not available for clustering in the activity planner.
Scenario Step: 5
Solution: Use other fields to cluster on.
Description: The quantity of the activity definition is different then the quantity of the location assignement.
Scenario Step: 3
Solution: If this is incorrect, the quantity of the Activity Definition can be changed after migration.