Migration Object Modeler and Custom Migration Objects

Keep this: job aid

Migration object modeling card

• Order of preference: use as delivered, adapt, create; manual entry with evidence for tiny volumes.
• Check release object list and custom field support before opening LTMOM.
• Object parts: source structures, target structures, structure mapping, field mapping and rules.
• Prefer translation objects and fixed values over coded rules.
• After changes: generate, synchronize staging tables, download a new template, log the change.
• Developer-appended fields need a target field, an API path and a mapping; verify values in the target.
• Custom object function module: no COMMIT WORK, BAPIRET2 messages, test-run flag, application checks.
• Targeted tests: valid, missing reference, invalid value, boundary, simulation, repeat load.
• Change only in development; transportable package, not $TMP; ABAP objects with or before the project.
• Mapping values do not travel with definitions: maintain and reconcile them per system.