XML and Script Info

Use the XML and Script Info tab of Conversion Build Configuration Settings dialog box to change the build settings for the next conversion build.

Related topics

- Compile Info tab of Conversion Build Configuration Settings dialog box.
- Build Details tab of the Conversion Build Configuration Settings

Fields | Description
Profile | Specify the conversion objects to be considered by the build process. Allowed values Current: If you select this option, only the conversion objects maintained in the selected migration profile are considered for the conversion build process. Current with all parents: The selected profile as well as all its parent profiles are considered for build process. Only the latest conversion objects are selected for build. For example, if you have one conversion object, tccom100, present in profile 6, as well as its parent profile 2 during the build process tccom100 present in profile 6 is considered, the one from profile 2 is ignored.
Drivers | This information is applicable only if your target application is Infor. Here you must specify the database driver type of your target database. Allowed values L1: Select this option, if the target Infor application uses L1 database driver. L2: Select this option if the target Infor application uses L2 database driver. Note SSA ERPLN uses only L2 driver for all the supported databases.
Target Database Specific Optimization | Specify your database. This field is applicable only if the driver selected above is L1. Note For legacy system, this field is not applicable.
Query Optimization | This option is applicable only if your source application is Infor. If you select this check box, then the select * is replaced by select field1, field4 where field1 and field4 are later used in the conversion rules. Field2 and field3 are ignored, since they are not used in the conversion rules.
Consider Checkout Versions for Generations | Select this check box if you want to consider checked out version of the conversion object during conversion build. This can cause problem, since the checked-out version may not be complete. Note This option is useful, when you fix some issue, and before check-in you want to validate by perfoming a conversion run. In this case you can select this flag, and a build for the specific conversion object.
Clear XML and Script Directory for Each Run | DCA Studio creates XML files and conversion scripts locally before copying the script to Infor source environment. Select the option prior to the build process to clear the files. Before performing a complete conversion build you must select the option to ensure that all the scripts are generated afresh and not taken from any previous builds.
Consider History and MultiProcess setup | You must select this option when you perform history or multiple processes per conversion object setup.
Include 2GB Check | This field is applicable if your source application is Infor and it is installed in UNIX OS. In some Unix versions the file size cannot exceed 2GB. You must enable the option so that the conversion script checks whether the size of the data file exceeds 2GB.If the file size exceeds 2 GB the current file is closed and and an additional file is opened.
Is Multibyte Migration | This field is applicable if you uploaded a RDD of a ERP Enterprise target application and the target application was based on unicode. Only use this setting for changed mapping objects which uses the uploaded unicode RDD

Commands | Description
Ok | Saves the build settings and returns to the Build page.
Cancel | Click Cancel to return to the Build page with out saving the changes to build settings.

| Send Us Your Feedback About this Help Page