Conversion Parameters (bcgct0100m000)

The target company into which the data must be loaded.

When you use this session for the first time, you must use the New button to enter the details. The current company number then appears in this field automatically. (The current company number must be the same as the source company being converted). This field along with the other fields is displayed if the session was already populated.

• In case of Company Number in Source env details group, please see Company Number(2)
• In case of Company Number in Options group, please see Company Number(3)

Indicates if the data is to be loaded with ERP LN 6.1 inserts.

If this check box is selected, the data is loaded with the ERP inserts. If this check box is selected, other Database-specific detail fields on the form are disabled automatically. They are re-enabled automatically when this checkbox is cleared.

The methodology of migration by this tool is to dump source environment data into ASCII files and load this data from the ASCII files into the target environment tables with database-specific loader utility, such as SQL*Loader for Oracle and High Performance Loader for Informix. Currently target environment supports Informix, Oracle, DB2 and SQL Server databases. If you are using any other RDBMS product, you can load the data into the target environment tables with ERP statements (db.insert). This procedure of loading can be used for any database to which the target environment is linked. Therefore, it is called database-independent loading.

The database to which the current company of the target environment is linked.

This value for this field appears automatically when you start the session. The information is picked up from the baan tools table ttaad410 (Database Definitions) and ttaad411 (Database Table Definitions). The current possibilities for this field are Oracle 7, Oracle 8, and Informix, as the present tool supports loading with database-specific loading utilities for these databases only. The database-independent loader must be used when the target environment database is any other database.

In case of RDBMS in Source env details group, please see RDBMS(2)

This field displays the database-specific information depending on the database to which the current company is linked. If the database is Oracle, this field displays the ORACLE_HOME and ORACLE_SID values. If the database driver for the Oracle database is L1, this information is also displayed with the parameter ORA_LEVEL1. Similarly if the database is Informix, this field displays the INFORMIXDIR and INFORMIXSERVER values. If the database driver for the Informix database is L1, this information is also displayed with the parameter INF_LEVEL1. The information for this field is also picked up from the baan tools table ttaad410 (Database Definitions) and ttaad411 (Database Table Definitions).

The target environment database name.

The target environment server name.

The path where the log files are to be created for tracking the status of data loading process at the target side.

The user name for SQL* Loader for the ORACLE or SQL server database.

The password for the corresponding username for loader.

The number of loaders to be invoked at the start of the conversion run is specified in this field. By default, 3 loaders are invoked if this field is set to 0.

The number of loaders can be changed during the conversion run. Click the + button on the loading window to invoke another loader. If the conversion run is performed as a job, the number of loaders to be invoked must be entered. For DB2, the number of loaders is always one and therefore this field is disabled. The maximum number of loaders that can be invoked at the same time depends upon the power of the CPU and other system resources available on the server.

Current company at the source environment side.

The database to which the current company of the source environment is linked.

Select the source environment for the conversion.

Allowed values

• Triton
• ERP Baan IV
• LN

The value in this field indicates the kind of connectivity available between the source and the target environments.

Allowed values

• Single Machine: The source environment and the target environment reside on the same server. This scenario corresponds to the single machine scenario explained in the Installation Guide.
• Two Machine With Client/Server: If the source environment and the target environment exist on two separate servers, you can perform the conversion with a Client-Server connection between the source and the target server. This scenario corresponds with the two machine with client/server connection scenario explained in the Installation Guide.
• Two Machine Without Client/Server: If the source environment and the target environment exist on two separate servers, you can perform the conversion without a Client-Server connection between the source and the target server (which means dumping is performed separately on the source server, then ASCII files are copied to the target server, and then loaded). This scenario corresponds with the two-machine scenario without client server connection explained in the Installation Guide.

Default value

• Single Machine

If the conversion is a single-step process in which source environment and target environment reside on the same server, you must set the source environment BSE value in this field. If the source environment and the target environment reside on separate servers and are connected through a Client-Server connection, you must set the client source BSE in this field. (In this field, the BSE is the $BSE of the source environment whose data is to be converted). This information is required to start the source environment from the target environment.

If the conversion is a single-step process in which source environment and target environment reside on the same server, you must set the source environment BSE_TEMP value in this field . If the source environment and the target environment reside on separate servers and are connected through a Client-Server connection, you must set the client source BSE_TEMP variables in this field. (In this field, the BSE is the $BSE of the source environment whose data is to be converted). This information is required to start the source environment from the target environment.

This field must be filled with the source environment server name. This field is only enabled for the two-machine scenario (both with and without client server connection).

The path where the data dumps were created on the source server must be specified in this field.

If the source environment and the target environment is present on separate servers and no Client-Server connection is established, then the data dumps are created on the source server and they must be transferred to the target server. The migration tool performs this with the RCP utility of UNIX.

The path on the target server where the sequential data dumps transferred from the source server with the UNIX utility, RCP.

This field is only enabled when source environment and target environment reside on different servers and no client-server connection is established between the two.

The source company number of which you want to convert the data. This must be the same as the current company number in the target environment.

The Enterprise Modelling data for all the companies can be present in a single company at the target side. The company in which this data is stored must be specified in this field. While migrating the source data, the EMM data is loaded into the tables of that company.

Current target environment company.

Alert functionality allows you to receive Migration error messages through an email when you run Migration process as a job. This intimates you in the form of an email about the nature and the source of the problem.

The various types of errors could be the improper run of preconversion activities, disk full condition, incorrect login credentials specified for the user on the source server to connect, and so on.

For the Alert functionality to function following setup is also required:

1. Start the User Data (ttaad2500m000) session.
2. Double-click on a row for the user that will be used during the migration process run as a job. Another session is activated where details for the same row can be modified.
3. Now enter/update the Email Address where you would like to receive emails once the Migration process starts as a job.

In this field, provide an email id where you would like to receive migration error messages in case you are running migration process as a job.

The batch code for which the conversion was carried out last time.

This check box indicates whether the conversion was carried out last time by storing conversion run details such as number of records at every conversion phase, time taken for dumping and loading process.

This check box indicates whether the conversion was carried out last time by maintaining the time taken for dumping and loading process.

This check box indicates whether the conversion was carried out last time by keeping the count of records at every conversion phase.

Displays the run number with the help of which last conversion details are maintained if the conversion was carried out last time by keeping the count of records at every conversion phase.