Migration Profiles

The Migration Profiles page is used to maintain migration profile details for various migration runs.

Migration profiles are used to relate a source application to a target application, in other words, to define a data migration scenario. The users are linked to these migration profiles.

Related topics

- Applications page

Fields | Description
Profile Number | A system-generated number that users can change. The DCA uses this number internally to identify the set of conversion rules for a particular data migration scenario. In case you derive this profile from one of the existing profiles, ensure that the number you have entered is greater than the one from which you are going to derive this profile..
Profile Description | A brief description of the migration profile.
Source Application | The application from which you want to migrate data.
Target Application | The application to which you want to migrate data.
Current VRC | Specify the Version Release Customer of the migration profile. The term Version Release Customer means the same as in Infor ERP. The purpose of these three fields is to identify the following: The version of the rules: Major releases receive a new version number Release of the rules in a particular version: Service/Feature Pack upgrades The customer extension, if the rules are customized for a particular customer. Note When you derive this profile from one of the existing profiles, the last letter in the Version part must be U.
Derived from Profile | Select a profile from the list, from which you want to reuse the conversion rules. Example, consider you have Infor4c4 to Infor10 ERP Enterprise, migration rules in profile number 3, and you have created a new profile 4 for a customer from the customized Infor4c4 data model to a customized Infor10 ERP Enterprise data model. In this case you can reuse most of the conversion rules present in profile 3. Therefore, you must derive profile 4 from 3 and in this field you must enter the value 3.
Revision Controlled | Set the field to Yes if you want to revision control the conversion rules for this profile. Otherwise, set the field to No. If you select Yes, you must maintain the Development VRC. Note Revision control is sometimes referred to as Software Configuration Management (SCM).
Development VRC | This field is applicable if this profile is revision controlled. This VRC is internally used by DCA Studio to store the conversion objects, checked out by users for editing. Ensure that this VRC is different from your current VRC.
Lookup Application | This field is applicable if your source application is Non-BaanERP. You can select a Non-BaanERP application that you must refer to, during migration. Note Usually this feature is not used. Instead you can import the lookup database tables also as a part of Source application. An application can store tables from different databases.

Commands | Description
New | Creates a new migration profile. Only user ‘baan’ can create a new profile.
Delete | Deletes a profile. Only user ‘baan’ can delete a profile. When you delete a profile all the conversion objects present in that profile are also deleted. The source and target applications are not deleted.
Users | Use this option to assign/authorize users to this profile. Only user ‘baan’ can assign other users to a profile.
Settings | Use this option to maintain conversion build options. Conversion build is the process by which you create the object pack.
Add Doc | Use this option to specify the comments when some source application tables or tables fields are not migrated. The feature is useful, when you migrate Infor applications. The comments are compiled to web help and published. In other scenarios, the user requires DCA Studio to view these comments.
Modify | Use this option to change an existing profile. Only user ‘baan’ can edit the profile details.
Save | Use this option to save a new or a changed profile.
Cancel | Use this option to cancel the action and return to the previous page.
Check In All | Use this option to check in all the checked out conversion objects in the selected profile. This option is enabled if the profile is revision-controlled. This option allows you to check -in all the checked out objects and conversion objects in use. Using this process can cause problems during conversion or build.
Delete Revisions | Deletes all the revisions of the conversion objects in the profile.
Undo Checkout All | Enables you to undo the changes made to the checked-out conversion objects under this profile. This button is available only if the profile is revision-controlled. This option is a global undo check-out. Hence, the work of the users who have checked-out objects for editing, is lost, when this option is used.

| Send Us Your Feedback About this Help Page