Map Legacy Data Target Table

Once a migration object of a project is connected to a source, user will be able to start map fields or map concatenated fields of a legacy locked table(s) to the fields in target table definition which are in scope (Required to consider both aspects during concatenation, different target tables and different target fields). In addition to that user will be able to override the default values extracted from its target table definition with his own values or values defined under default definitions. Once the mapping is completed data should be transferred to the input container based on the mapping.

When the same target file is mapped twice to a migration object (E.g. Comm_Methods) it will be post fixed with a # followed by its sequence in migration object (E.g.- Comm_Methods#10, Comm_Methods#20). But when transferring data to the input container all data is transferred to a single target table definition.