Glossary for the BC package

A detailed investigation will be initiated to analyze the customer environment related to business and functional aspects, customizations used localization, and technical infrastructure.

Before you start up the actual migration activities, you must carry out an assessment to provide insight into the efforts to be made for the migration, as well as the feasibility and the main risks.

The Oracle and MSSQL Server Database Loader utility creates these files to specify which records were rejected due to data errors. This file contains the records that were rejected due to data errors. These files are created with the name < ERP LN 6.1 table name >.bad.

Conversion package. All the components of the conversion are under the BC package.

The Software Environment: This variable contains a directory path in which all runtime files and programs are located.

This variable contains a directory path in which temporary LN application files will be stored.

BW is a graphical user interface program in the LN software that runs on a PC in a Windows environment.

The CA Engine 2.0 generates objects from the 3GL source code generated by the CA Studio and distributed by means of an CA Logic Pack. Subsequently, the CA Engine starts with the execution of preconversion sessions, followed by the execution of the conversion objects. Finally, the post-conversion sessions start. OTHER: This tool performs the actual data conversion, using the data conversion scripts generated by CA Studio and is also used to execute pre- and post data-conversion activities. This tool was developed in TRITON Tools.

The CA Logic Pack contains source codes of the conversion logic that can be imported by the CA Studio.

The CA Object Pack contains the encrypted 3GL source code files generated by the CA Studio.

The CA Studio enables you to load, compare, and map data dictionaries from a source and target environment. The mapped data dictionaries are converted to conversion rules that can be modelled and validated. The conversion rules can be exported to XML files. Based on these XML files, you can generate 3GL source code . OTHER: This tool enables you to capture the difference between two Infor software releases, based on runtime data dictionaries and generates data conversion scripts and is developed in a thin client architecture.

This phase is the after-migration phase in which the emphasis lies on business performance improvement and new features.

These files are required to load a particular data file into a table. The SQL *Loader utility reads this file for details, such as from where to pick the data file, and which table this data must be loaded into. These files are created with the name < ERP LN 6.1 table name >.ctl.

If you use this option to start loading, the data is loaded record by record and the indices are built simultaneously.

In this document, the terms migration and conversion are synonymous.

The Conversion Adapter is a new generation of flexible conversion tools. With the Conversion Adapter the conversion logic can be generated, modelled, and distributed in a very flexible way, because the conversion logic will be split from the conversion tools.

An object that stores the information about how data is migrated to a target table from a source table. The information is stored as: (a) A set of source tables from which data originates. (b) A precondition in what criteria data is coming from each of these source tables. (c) The main query that specifies what fields must be selected under what condition for each of the source tables. (d) Rules on how these selected fields are mapped to the target fields for each dump in the main query.

Numerous parameter sessions to control the required functional conversion parameters related to the ERP functionality. These sessions are part of the bc package.

An interface between ERP LN 6.1 and the RDBMS that interprets the commands given in ERP LN 6.1 and maps these commands to the underlying RDBMS.

The conversion of all company data to a new format.

These files are the dump files that are created during the dumping process in MANMAN/HP. These files contain the actual data that will populate the ERP LN 6.1 tables. These files are created with the name < ERP LN 6.1 table name > .dat.

This utility compares data fields between the source and target data environments to validate the correctness of the data conversion process. This utility checks that the business processes are correct between the source and target environments after a data conversion process. This mechanism clearly shows the number of records migrated for each source table to what target tables. This mechanism also checks if the total number of records between the source and target are equal. The mechanisms also compares the data itself for most critical data fields, such as open orders, sales orders, stock, items, and so on. Compare data of the most critical data tables/fields. Features to validate if the content of a field in line is with definition in the runtime data dictionary. If all fields are filled correctly, Mandatory /References / Counters and so on

If you start the load with this mode, the tables are not locked. As a result, the loading of data can take place while other users are working. This mode updates indices, performs constraint checking, and evaluates triggers as data is inserted into the table.

If you start loading with this option, the data is loaded and the indices are then built. The checks of the SQL layer are bypassed.

Most business procedures have considerably changed between the MANMAN/HP source and the LN target environment. A DEM conversion tool is available to help the user perform an automatic conversion of the DEM models. Component release conversion tables are the basis for an automatic conversion of the DEM models that a customer uses.

The technical area, which consists of the directories on a system used by the programs.

The process in which data from the MANMAN/HP database table is dumped in an ASCII file in the format of ERP LN 6.1 tables.

If you start loading with this mode, the tables are locked. Therefore, data loading cannot take place if other users are working. This mode disables indices, constraints, and triggers during the loading process. After the load, indices, constraints, and triggers are rebuilt, evaluated, and re-enabled.

Module in the package bc for conversion; all the components of the Conversion Adapter software are available in this module.

The High Performance Loader utility that is a GUI mode provided with Informix and only functions in X-windows.

The High Performance Loader utility provided with Informix.

To develop the proper migration plans for a customer, you must know the technical details of the customer's software environment. The Implementation Scanner provides reports that contain information about the system, companies, DEM, software components, and interfaces.

The process in which data from the dumped ASCII file is loaded in the database table of the target environment.

This variable specifies the full path of the directory in which Informix is installed. If your system has multiple copies or versions of Informix, INFORMIXDIR must contain the directory name for the version that you want to access.

This variable specifies the name of the database server. Informix uses the name of the database server as the index to obtain the connectivity information in the remaining fields from the $INFORMIXDIR/etc/sqlhosts file when client applications connect to database servers. The name of the database server must correspond to an entry in the sqlhosts file.

Level 1 and level 2 database drivers. More information is available in the technical documentation of Infor.

These files are created when a data file is loaded into a table with the database-specific Loader utility. This file contains details, such as how many records were loaded and how many rejected, and so on. These files are created with the name < target table name >.log.

Generate and maintain sessions for generation and maintenance of additional temporary mapping tables. Those tables are required to solve complex mapping problems between the source and target tables. Mapping tables are filled and maintained during the preparation phase of conversion process. The logic of mapping tables is part of the bc package.

The total set of activities that must be carried out in a project to deliver a new version of the Infor software that works properly with data converted from the old Infor software version, and possibly combined with a new or changed technical infrastructure.

The Migration Wizard tool can be used to migrate the data from the source to the target environment without manually invoking the sessions required for the migration. The Migration Wizard tool is created to simplify the process of migration by running the correct sessions sequentially, depending on the environment and your requirements.

The onpload database contains information that the onpload utility requires to perform data loads and unloads. The onpload database can reside on any database server on your network. In addition, any onpload utility can use the onpload database as long as the onpload utility can access the database server that contains the onpload database. In contrast, the onpload utility must run on the same computer as the database server that contains the target database.

Oracle Database HOME is the path on which the database-related executables and files are available, and is a parameter that must be set before the migration tool is run, for data to be migrated to ERP LN 6.1.

Oracle Database Instance ID, a parameter that must be set before the migration tool is run, for data to be migrated to ERP LN 6.1 on Oracle.

Several standard sessions and other specific (bc) sessions in the target environment to fill and correct some target tables, to be run before operational work can be started in the target environment.

Several standard sessions and other specific sessions in the source environment to correct and verify the source database. The specific sessions as required for preconversion are part of the bc package. In addition, a number sessions in the target environment for conversion of some relevant target data to the source environment. Sessions are developed as part of the bc package.

In this migration phase, the entire setup of the customer organization, infrastructure, and software environment takes place.

Relational Database Management System.

After acceptance of the conversion results by the customer, the final cut over will be realized based on the tested infrastructure and tested new LN solution.

The Informix Database Loader utility creates these files to specify which records were rejected due to data errors. This file contains the records that were rejected due to data errors. These files are created with the name < target table name >.rej.

The Software Component Converter supports the upgrade of customized software components based on tools in the source environment to tools in the target environment with mapping features to new or other software components in the target environment.

The conversion and upgrade of general or in-house customized software components to a new version.

The environment in which the earlier ERP LN 6.1 application release is present.

Oracle utility to load data in the ASCII file into a table.

The environment in which the new release of the LN application is present.

Universal Time Constant. A new concept of representing date.

The Version Release Customer (VRC) module in Tools enables you to manage various versions and releases of a package. Four types of VRCs are available: L: Localizations; B: Line of business-specific software; C: General customizations; and O: Customers own customizations.