A Migration Job fails to start with 'Unit code does not exist or is not enabled for use in the application' — the mandatory fields in the template all appear to have values or defaults set. What's a commonly overlooked cause?

All FAQ questions / Data migration

Answer

Check specifically whether the CONTRACT (Site) column has been defined in the migration job template — even when every other mandatory (flagged 'M') field has a template mapping or default value, a missing CONTRACT/Site mapping specifically produces this 'Unit code does not exist' error, since the site context is what the framework uses to resolve and validate the unit code against. Reviewing the full list of mandatory fields (marked with 'M' in the Flag column) and ensuring each has either a template column mapping or a default value — with particular attention to CONTRACT — resolves this.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Data migration questions