This topic describes a number of general issues regarding the conversion from TRITON 3.0/3.1 to BAAN IV.
1.1 Scope
This document provides information regarding the procedures to convert TRITON 3.0/3.1 to BAAN IV. It does not explain the concept of VRC structures and does not provide extensive help information on how to upgrade general or in-house customizations (C- and O-VRC’s, respectively).
1.2 Target Group
This document can be used both by Baan conversion teams and by Baan customers. For a flawless conversion from TRITON 3.0/3.1 to BAAN IV, extensive knowledge of both TRITON and BAAN is required.
1.3 Remarks and Recommendations
Prior to the actual conversion, a number of considerations must be taken into account.
1.3.1 Conversion to BAAN IV: two possible scenarios
BAAN IV can be installed as an update across TRITON 3.0X/3.1X, or as a stand-alone environment (fresh install), in which the 3.0/3.1 data can be converted to BAAN IV.
The correction program is suitable for converting data from the the following TRITON versions to BAAN IV:
n 3.0b, 3.0b1, 3.1a, 3.1a1 and 3.1b.
Be aware of the fact that BAAN IVa is a restricted release, and that only the conversion to BAAN IVb has been tested on application-level.
Both scenarios have their pros and cons. The most important are the following:
Pros and cons of the two scenarios |
||
Conversion Scenario |
Pros |
Cons |
Single environment
|
wnot too much extra disk-space required wmore simple conversion wless strain on the server (one server – one environ-ment) |
wusers have to leave the environment during update (software) wsome development actions are not possible anymore in the 3.0/3.1 Package Combinations after update |
Two environments
|
woperational environment remains operational during installation/testconversion wall actions are possible in the 3.0/3.1 (operational) environment during the whole procedure woperational environment remains unchanged (reliable) during instal-lation/testconversion |
wa lot more space is required (since two complete environments exist for a period of time) wthe conversion has more steps, which are also more complex win case of a one server – two environments situation, more strain is put on the server |
The two conversion scenarios are referred to as the Single Environment Scenario or the Two Environments Scenario, respectively.
Both scenarios are depicted in a schematic way in a set of flowcharts, which are included in this document.
It is advisable to determine beforehand which of these two conversion methods is the best for the specific situation, and to study the steps of the corresponding flowchart(s). The charts are not totally self-explanatory, so turn to the corresponding texts in this document for more detail.
It is important to understand the impact of all the choices, presented in the flowchart(s), especially those concerning customized table definitions (in case of a not standard DataModel; see also the section Customizations).
For more information on the installation of BAAN IV and the conversion of the TRITON 3.0/3.1 data, see the BAAN Tools Installation Manual (5574US) and the Installation Concepts (7783US).
1.3.2 Customizations
In case of a standard TRITON 3.0/3.1 version, assuming that the BAANIV version will also be standard, the standard conversion program can be run. If the TRITON 3.0/3.1 version includes customized table definitions, and therefore the BAANIV environment is assumed to also, the standard conversion program must be modified to fit the customer’s specific configuration.
NOTE |
In the case of a not standard DataModel, the test conversion can only be carried out after the customizations have been redefined under BAAN IV, and the conversion program has been adjusted to the BAAN IV table definitions.
It is advisable to check the derived-from structure for all possible types of not standard software. That is: all types of localizations (L-VRC’s), line-of-business-specific software (B-VRC’s), general customizations (C-VRC’s) and in-house customizations (O-VRC’s). If any of these are present, check whether these contain customized table definitions, and make sure the correction program is adjusted to these, if necessary.
Do not attempt a data conversion before this issue is resolved.
For more information on the tables which must be converted, see the on-line help information of the Conversion to BAAN IV (tccov0000m000) session.
1.3.3 Localizations
For the conversion of global localizations, version 3.1b is required which means that TRITON 3.1a users must first be converted to 3.1b. For the conversion of other localizations, see Chapter 1.3.2.
1.3.4 Disk Space
Two Environments Scenario
After BAAN IV has been installed, two different environments exist, namely the operational 3.0X/3.1X environment and the new BAAN IV environment. The data in the old environment must be copied to the new environment.
During the conversion, a file is created containing all company data. Importing the file(s) in BAAN IV and rebuilding and converting the data in these files to fit the new database will require more disk space than was required in TRITON 3.0/3.1. This is because a number of tables and fields were added to BAAN IV.
|
Figure 1-1 Conversion to BAAN IV
During the conversion in BAAN IV, temporary files are used to store the conversion data of each separate table.
1.3.5 Straight Migration
In case of a straight migration, the business functions which are used in TRITON 3.0/3.1 are migrated to BAAN IV in which they will be used in the same way (if possible). Consequently, a straight migration offers maximum security while the complexity of the project is reduced since new functionality is not implemented until later.
1.3.6 Test conversion
The application tables (data) in TRITON 3.0/3.1 are converted to
BAAN IV by one of the conversion specialists of Baan or the customer’s own conversion specialists.
The test conversion simulates the final conversion, with the following objectives:
Attune the conversion environment to customizations (if any)
In case the TRITON 3.0/3.1 version includes customized table definitions, the standard conversion program must be modified to fit the customer’s specific configuration. In this case, the test conversion can only be carried out after the customizations have been redefined under BAAN IV.
Provide information about the run time of the actual conversion
The planning of the final conversion is based on the run time of the test conversion. After the final conversion has been started, no new transactions must be created in TRITON 3.0/3.1 since these transactions will not be included in the conversion.
Provide certainty about the progress of the conversion run
The final conversion must take place without errors. If any error occurs during the test conversion, its causes must be traced and cleared so that the test conversion can be repeated without the error blocking the final conversion.
Provide certainty about the results of the conversion run
The results of the test conversion are assessed based on the data and procedure tests. Since all functions and procedures in the new BAAN IV application can be used based on the data of the user’s own company, maximum certainty is achieved regarding the continuity of business processes after the final conversion has taken place.
1.3.7 Integration of Implementation and Data Conversion
Data conversion must be an integral part of the installation and is, therefore, included in the plan of action.
This plan of action includes the following aspects:
n Upgrade or installation of hardware
n Installation of BAAN IV (if applicable)
n Training of end users (BAAN IV tools and applications)
n Development of customizations
n Implementation of BAAN IV Tools
n Preparation of test conversion
n Test conversion
n Data test
n Procedure test
n Go/No Go decisions
n Final conversion
1.4 Terms and Abbreviations
Term/Abbreviation |
Description |
BSE/$BSE |
BSE refers to the BAAN Shell Environment. By means of the BSE variable, a short link is established which refers to the directory in which all BAAN programs and directories are located. |
Environment |
The technical area which consists of the directories on a system used by the programs. |
Data Conversion |
The conversion of all company data to a new format. |
Software Conversion |
The conversion and upgrade of general or in-house customized software components to a new version. |
1.5 References
For more information on the tools and utilities that can be used in the conversion procedure of customized software, see the following documents:
n New Functions in BAAN IV 5972US
n BAAN Utilities User Manual 5569US
n Component Merge Tool (CMT) module
Module Description 7795US
n BAAN Tools User Manual 5564US
2 Preparing TRITON 3.0/3.1 for Conversion
|
This chapter describes the steps needed to prepare TRITON 3.0/3.1 for the conversion to BAAN IV.
2.1 Steps in the Procedure
The following steps can be distinguished to prepare software components for conversion:
1 General
2 Software export
3 Data export
Each of these main steps may comprise a number of additional steps.
2.2 General
2.2.1 Create a Backup of the TRITON Software and Data
A backup must be created of the operational TRITON software and data.
2.2.2 Export Users/Authorizations/Devices/Currencies/Logical Tables (ottcon61export)
At this point, the data regarding the current users, authorizations, currencies, and devices is exported by means of the following steps:
Copy the ocon61export program from the BAAN IV environment
The ocon61export program must be copied from the new BAAN IV $BSE/tools/ttB40_a/ottcon environment to the TRITON environment. For TRITON 3.1 to the $BSE/tools/tt6.1_*/ottcon directory, and for TRITON 3.0 to the $BSE/tools/tt6.0_*/ottcon directory. This program is referred to as an object and does not have to be patched.
For example:
cp/baan4/bse/tools/ttB40_a/ottcon/ocon61export/triton31/bse/tools/tt6.1_a/ottcon/ocon61export¿
The permissions and the owner of the ottcon61export program must be set to bsp.
Execute the ottcon61export program
The ottcon6.1export program in TRITON 3.0/3.1 is used to export all users, authorizations, currencies, devices, and logical databases to an ASCII file. This program can be started from the command line of a menu by typingp followed by ottcon61export.
Export Users Data y/n: y
Export Authorizations y/n: y
Export Currencies y/n: y
Export Device Data y/n: y
Export Logical Tables y/n: y
Output File :/usr8/bse/tmp/baaniv
Continue y/n: y
2.3 Software Export
This step only applies to customized software components.
2.3.1 Export Data Dictionary (ttiex1280m000)
This session is used to export the customized VRCs from TRITON 3.0/3.1 to an ASCII file. For each VRC, a separate export directory must be created.
ttiex1280m000 alphanum single occ (4) Form 1-4 >
Export Data Dictionary
Package : tc TRITON Common
VRC : 3.10 a cv02 Challenge 3.0
Update : Yes
Compared with VRC : 3.11 a
Export Based on Sessions : No
Only components of package itself : Yes
Session (from/to) : – zzzzzzzzzzz
Languages : 1 2 3
Deliver Session from Status : Developing
Create Components List : Yes
Errors to Printer : Yes
Path Dumps : /usr1/triton6/bse/export/tc
Choice: ..
2.4 Data Export
There are two ways in which the company data can be exported or transferred to the new BAAN IV environment, namely by means of a general data export or by means of a database-specific data transfer.
2.4.1 General Data Export
The Create Sequential Dump of Table (ttaad4226m000) session can be used independent of any database to create a sequential dump of the database tables.
ttaad4226m000 single occ (4) Form 1-1
Create Sequential Dump of Table
From To
Company : 100 – 100
Package : – zz
Table : – zzz999
Suppress Error Messages : No
Recover Isam File : No
Drop Table after Dump : No
Create Backup before Dropping : No
Specify Database Driver : No
Create Fixed Length Records : No
Specify Field Separators : No
Directory for Table Files : No
Basic Name for Dump File(s) : /tmp/dump
Name of the Error File : 100.error
Name of the dumpfile(s) will be:
/tmp/dump.<company> Choice: .
The advantage of this approach is that the company data remain operational. The disadvantages are the amount of disk space which is needed for the export file and the new database as well as the amount of time needed to export and import the company data.
2.4.2 Database-Specific Data Transfer
A database-specific data transfer is a faster conversion method than the general export option. There are different types of database-specific data transfers, depending on the database type.
TBASE or TBASE_TP
For this method the database tables for TBASE and TBASE_TP must be copied to the BAAN IV environment and registered in BAAN IV (this second part is described in the import-section of the next chapter). For TRITON 3.0 an additional step is necessary in the import (conversion of the tables).
Make sure that nobody uses the companies when you are copying them.
The advantage of this approach is that there is a faster conversion which mainly results from the fact that two procedure steps are omitted, namely the Create Sequential Dump of Table (ttaad4226m000) session and the Create Table from Sequential Dump (ttaad4227m000) session (see Chapter 3).
Informix or Oracle
The approach for these RDBMS highly depends on the customer’s specific situation and is, therefore, too complex to be discussed in the context of this document. For more information, contact the local BAAN supplier who may contact the ISC for assistance. Partners and dealers in the EMEA area may contact the department of Technical Services of BAAN Netherlands.
3 Converting to BAAN IV – Two environments scenario |
This chapter describes the steps needed to convert the prepared software components and data from TRITON 3.0/3.1 to BAAN IV.
3.1 Steps in the Procedure
The following steps can be distinguished in converting the TRITON 3.0/3.1 data and software to BAAN IV:
1 General
2 Software Conversion
3 Data Conversion
Each of these main steps may comprise a number of additional steps.
3.2 General
This step is executed from within the Data Conversion menu of BAAN IV:
mttcon2130m000 Menu 1-1
B A A N IV T o o l s Date: 20-05-96
Company: 000
Data Conversion 6.1/3.1 -> BAAN 4
1 Copy Package Combination
2 Copy datadef files from 3.1 to Temporary Package Combination
3 Maintain Companies
4 Assign Tables to Databases
5 Maintain Table Directories (BAAN Base (TP))
6 Maintain Logical Tables
7 Maintain User Data
8 Create Table from Sequential Dump
9 Check Tables
10 Convert 3.1 b tables to BAAN IV
11 Import Users/Authorizations/Devices etc. from 6.1
Choice: 11
3.2.1 Import Users/Authorizations/Devices/Currencies/Logical Tables (ttcon61import)
At this point, the file which was saved in TRITON Tools 6.1 is imported. Instead of importing the old definitions, it is also possible to define new users, authorizations, devices, currencies, and logical tables.
ttcon61impor alphanum single-occ (4) Form 1-1
Import Users/Authorizations/Devices etc. from 6.1
Path 6.1 Data :
/usr8/bse/tmp/baaniv
Choice:
3.3 Software Conversion
3.3.1 Import Data Dictionary (ttiex1285m000)
This session is mandatory for customized software components and is used to import the customized VRCs which originate from TRITON 3.0/3.1 in the proper B40 VRCs.
ttiex1285m000 single-occ (4) Form 1-1
Import Data Dictionary : /usr1/TRITON6/bse/export/tc
Path Sequential Dumps : /tmp
Path Runtime Dictionary : ${BSE}/application
Overwrite : Yes
Delete dumps
after installation : No
Write software components : Yes
in other Package VRC
Package VRC : tc TRITON Common B400 a cv01
Choice: .
For example:
tc3.1O_a_cu02 –> tcB40O_a_cu02
3.3.2 Maintain Packages by Package Combination (ttaad1121m000)
This session is mandatory for customized software components and is used to create an operational package combination in BAAN IV which is referred to as OPER_001. Prior to converting the data tables, the datamodel must be assessed as being the correct datamodel. In addition, the derived structure of the VRCs must be determined.
For more information on how to upgrade customized VRCs, see Chapter 5.
3.4 Data Conversion
3.4.1 Copy Package Combination (ttaad1220m000)
This session is used to copy the standard or customized package combination of BAAN IV which is referred to as OPER_001 to a new temporary package combination which is referred to as TMP_001. These package combinations must have the same VRC structure and the same data model (data definitions).
3.4.2 Copy Data Definition Files
The data definition files are located in the directory which was specified by means of the Maintain Package Combinations (ttaad1120m000) session in the TRITON 3.0/3.1 environment. The target directory of the TMP_001 package combination can be determined by means of the same session in the BAAN IV environment.
If the TRITON 3.0/3.1 and BAAN IV environments are located on the same system, the copy datadef files from 3.1 to Temporary Package Combination (ttcon2140m000) session must be used to copy the data definition files of the OPER_001 operational package of TRITON 3.0/3.1 to the TMP_001 temporary package combination in BAAN IV.
ttcon2140m000 single-occ (4) Form 1-1
Copy datadef files from 3.1 to Temporary Package Combination
BSE-environment 3.1 : /usr1/TRITON6/bse
Package Comb. 3.1 environment : OPER_001
Temporary Package Combination : TMP_001
Choice: .
If the TRITON 3.0/3.1 and BAAN IV environments are located on different systems, there are two options to copy the data definition files.
The first option is to manually transfer the data definitions to the new system. This means that the existing data definitions in the temporary TMP_001 BAAN IV package combination is removed, after which the TRITON 3.0/3.1 data definition files are transferred or copied to the BAAN IV system.
In the example below, a tape is used to transfer this data to the BAAN IV system:
System I TRITON 3.0/3.1 installed in /TRITON/bse
Dictionary installed in /TRITON/dict
Operational Package Combination OPER_001
System II BAAN IV installed in /baaniv/bse
Dictionary installed in /baaniv/dict
Operational Package Combination TMP_001
Step 1
Copy the data dictionary files to tape:
Login as root on system I
# cd /TRITON/dict/ddOPER_001
# find * -print | cpio -ocvudB > /dev/<device> # device of your own system
# for AIX rmt0 or rmt1
# for HP rmt/0m
Step 2
Login as root on system II
Put the tape from system I into the tapestreamer of system II
# cd /baaniv/dict/ddTMP_001
# rm -r d* # remove all existing data
# in this directory
# cpio -icvudB </dev/<device> # device of your own system
# for AIX rmt0 or rmt1
# for HP rmt/0m
# chown -R bsp:bsp d* # setting permissions
The other option is to mount the system with the TRITON 3.0/3.1 environment on the BAAN IV system, after which the procedure which is to be followed is the same as the procedure which is to be followed for two environments on the same system.
3.4.3 Maintain Companies (ttaad1100m000)
This session is used to define the companies which must be converted, without creating the tables. These companies are linked to the temporary package combination by means of the Package Combination field.
3.4.4 Assign Tables to Databases (ttaad4111m000)
This session is used to check the data definitions. Any changes which were made in this session must be converted to runtime prior to exiting the session.
3.4.5 Maintain Table Directories (BAAN Base (TP)) (ttaad4115m000)
This session is used to check the table directories. These table directories must refer to the new path for the BAAN IV tables which must be converted from TRITON 3.0/3.1. Any changes which were made in this session must be converted to runtime prior to exiting the session.
This is an optional session which is used for the BAAN Base database program (tbase or tbase_tp). Consequently, this session must not be used for Oracle or Informix databases.
3.4.6 Maintain Logical Tables (ttaad4120m000)
This session is used to define the logical companies. This data can also be exported and imported by means of the Export Users/Authorizations/Devices/Currencies/Logical Tables (ottcon61export) session and the Import Users/Authorizations/Devices/Currencies/Logical Tables (ttcon61import) session.
3.4.7 Maintain User Data (ttaad2100m000)
This session is used to link the login name of the user who executes the conversion to the TMP_001 temporary package combination.
Any changes which were made in this session must be converted to runtime prior to exiting the session. In addition, the bshell must be restarted.
3.4.8 Data Import
There are two ways in which the company data can be imported in or transferred to the new BAAN IV environment, namely by means of a general data import or by means of a database-specific data transfer.
General Data Import
The Create Table from Sequential Dump (ttaad4227m000) session can be used independent of any database to import the TRITON 3.0/3.1 tables from the old environment in the BAAN IV environment. This import must be executed in the TMP_001 temporary package combination.
For this type of import, the All Parameters field must be set to No, while the Ignore Referential Integrity Constraints field must be set to Yes.
On the second form of this session, the filename for the error log file must be specified.
Database-Specific Data Transfer
A database-specific data transfer is a faster conversion method than the general export option. There are different types of database-specific data transfers, depending on the database type.
TBASE or TBASE_TP
The database tables for TBASE and TBASE_TP must be copied to the BAAN IV environment and registered in BAAN IV.
For TRITON 3.0 and TRITON 3.1 different steps are necessary.
TRITON 3.1
The database tables for TBASE and TBASE_TP must be registered in BAAN IV. This is done by means of the register6.1 script which must be run under the tables directory. This script must be located in the $BSE/bin directory while its permissions must be set by means of the chmod 755 $BSE/bin/register6.1 command.
for i in ` find * -name *.bdt -print `
do
tbase6.1 R r ${I} # Use tbase_tp6.1 for TBASE_TP database !
done
TRITON 3.0
For TRITON 3.0 an additional step is necessary. Make sure all TRITON 3.0 tables are registered correctly at the beginning of this step.
Set $BSE to the TRITON 3.0 environment and make a list of all the existing tables, but not the dictionary tables:
$ tbase6.0 R d | awk ‘{print $1″.bid”}’|grep -v “dict” > /usr/tmp/conv_list
$ tbase6.0 R d | awk ‘{print $1″.bid”}’|grep -v “dict” > /usr/tmp/regr_list
Set $BSE to the BAAN IV environment now and convert all tbase tables into the new tbase format (conv2tbase6.1 is located in $BSE/bin of the BAAN IV environment):
$ conv2tbase6.1 bsp /usr/tmp/conv_list
Now register all tbase tables for BAAN IV. This is done by means of the register6.1 script which must be run under the tables directory. This script must be located in the $BSE/bin directory while its permissions must be set by means of the chmod 755 $BSE/bin/register6.1 command.
for i in ` find * -name *.bdt -print `
do
tbase6.1 R r ${I} # Use tbase_tp6.1 for TBASE_TP database !
done
Informix or Oracle
The approach for these RDBMS highly depends on the customer’s specific situation and is, therefore, too complex to be discussed in the context of this document. For more information, contact the local BAAN supplier who may contact the ISC for assistance. Partners and dealers in the EMEA area may contact the department of Technical Services of BAAN Netherlands.
3.4.9 Check Tables (ttaad4232m000)
This session is used to check the tables which must be converted for consistency in relation to table definitions. If there are no inconsistencies, no error messages will occur other than the Table Does Not Exist message related to error 506 which is prompted by the new tables in BAAN IV. These tables can be created after the conversion.
Since the tables are locked after this session has been used, the bshell must be restarted after this session has been closed.
3.4.10 Convert 3.0/3.1 Tables to BAAN IV (ttaad1202m000)
This session is used to convert the table format from the temporary package combination to the operational package combination.
3.4.11 Check Tables (ttaad4232m000)
After the tables have been converted, this session is used to check the tables for consistency in relation to table definitions. If there are no inconsistencies, no error messages will occur. Since the tables are locked after this session has been used, the bshell must be restarted after this session has been closed.
3.4.12 Change Package Combination for Users (ttaad2200m000)
This session is used to link the users to the new, operational BAAN IV package combination which is referred to as OPER_001.
3.4.13 Convert User Data to Runtime Data Dictionary (ttaad4200m000)
This session is used to convert the modified user data to the runtime data dictionary.
After this session has been used, the bshell must be restarted using a user name which is linked to the OPER_001 operational package combination.
3.4.14 Maintain Package Combinations (ttaad1120m000)
This session is used to delete the TMP_001 temporary package combination. This is done by means of the Delete option.
3.4.15 Create Tables (ttaad4230m000)
This session is used to create the new BAAN IV tables for specific companies and tables.
3.4.16 Reorganize Tables (ttaad4225m000)
This session is used to repair the reference counters of the imported tables. This is done for all involved companies by setting the All Parameters field to No, the Data and Indices field to No, the Reference Integrity field to Yes, and the Repair Reference Counters field to Yes.
In addition, the errors in the $BSE/log/log.aad4225 logfile must be checked. Since the approximately 200 tables which were added to BAAN IV are not yet available, the No DD Found For… message will occur several times.
4 Single Environment Scenario |
4.1 Preparation
4.1.1 Backup
The customer must have a good, recent backup of the software and the tables.
4.1.2 TRITON
While the installation script is running, the customer cannot use TRITON. Furthermore, correction programs have to be run before companies migrated to BAAN IV can be used for testing.
4.1.3 Time frame
The time frame of the update very much depends on the system and database types. Assuming the installation script is started on the evening of the first day, allow 4 to 8 hours on the second day to complete the job. This may be considerably more -to the point of having to allow a third day- where Informix or Oracle installations and/or the conversion of many or large test companies are involved.
The time frame on the first day is 1 to 5 hours to read out the tape(s); a master tape takes longer than a normal installation tape. Allow an additional half hour to prepare the update and to discuss the procedure with the customer. Try to take into account that the customer may want to run a backup at the last moment. The installation script takes between 3 hours and several days (in case of logged databases on a relatively small system) to run.
4.1.4 Prerequisites
Reserve 300 Mb to 400 Mb for reading the tape. A full update requires 350 to over 450 Mb (for one language, excluding customization, under bisam). Allow an extra 200 Mb per additional language.
4.1.5 Disk space
Determine if there is sufficient disk space on the system at the proper places (see previous section).
Check the derived-from structure, the package combinations and associated companies.
After installation, the existing 3.0/3.1 structure (that will continue to be used) must be copied (so to speak) under BAAN IV. This requires the creation of at least one new BAAN IV package combination for testing.
This test package combination is referred to in this document as TMP_001, and is a ‘copy’ of the operational package combination under 3.0/3.1 known as OPER_001.
The environment must be set up for testing; this implies that you should not at this stage migrate all existing package combinations (and associated company numbers) to BAAN IV! When the testconversion is satisfactory, later on only those BAAN IV equivalents of the package combinations have to be created that have companies attached to them (but do not create an equivalent of the standard [31Sa or 31Sb] package combination).
NOTE 1 |
Make sure that for the conversion of ‘own’ software, all that software is included in the process. Take into account possible other customizations as well (C-VRCs and B-VRCs). If there is customized software in 3.0/3.1, the customization supplier must migrate this to BAAN IV. The upgrade cannot take place before that migrated software has been delivered (on tape).
NOTE 2 |
Be aware of the fact that the correction program (otccov0000m000) has to be adapted if there are changes to the Data Model in these customizations (that is O-VRCs, C-VRCs, B-VRCs and possibly L-VRCs), before it can be run for the test company and the test company can be used! See Chapter 1 section 1.3.2.
In essence, one single testcompany and a number of users are migrated to the new test package combination, for testing purposes (and, possibly, for changes in ‘own’ software by the customer). In this phase the correction program (tccov0000m000) has to be adapted to the customizations (if necessary) so that the operational conversion can be without problems.
After testing and acceptance (and possibly adaptation and a second testconversion), the operational companies can be converted to BAAN IV.
Discuss everything with the customer: the backup, TRITON downtime/time frame, the need to adapt tccov0000m000 to changes in the Data Model, and configuration after the update (test package combination, user(s) and testcompany/companies to be migrated).
Remarks |
n During installation a new porting set is installed. This implies that all adjustments in directory $BSE/bin in their current versions will be lost after the update. The old scripts will still be available (in $BSE/bin, under their original name followed by a ‘-‘).
Make sure that, after the update, non-standard scripts or scripts subject to change are properly restored or adjusted.
n Because of the fact that the entire environment (3.0/3.1 and BAAN IV) is upgraded to Tools version B40_release, there will be the following restrictions for the 3.0/3.1 environment after update:
– When using a graphical user interface (bx or bw) it is not possible to use the zoom (<Ctrl>[Z]) options in an application session to a tools subsession
– It is not possible to dump run time 3.0/3.1 forms with BAAN IV tools or to compile 3.0/3.1 program/reportscripts with BAAN IV tools ! This implies that after the (software) conversion, the operational 3.0/3.1 environment will be frozen.
4.2 Installation Procedure
4.2.1 Step 1 – Reading out tapes
Read (each of) the tape(s) into a (new) empty directory.
On a suitable file system, create a temporary, empty directory (baan, for instance) to read the installation tape into. This directory mayNOT be below $BSE.
Read the tape for C-VRCs (if available) into another directory and the tape for B-VRCs (if available) in yet another
A. Regular tape
Go to the empty directory and read the tape using the cpio command or the bstape utility.
B. Master tape
Go to the empty directory and read the first block of the tape (see also the TRITON Tools 6.1 Installation Manual (5966US), chapter 4 [pp. 12 to 32]).
When the first block is read, a script called masread6.1 is copied to disk. Start this script. Select the package VRCs and languages to be installed. The script takes care of reading these from tape.
4.2.2 Step 2 – Start installation script
User must be “root”!
While the installation is running, the customer cannot use this environment. Check if everyone has left the bshell and has been advised (through the system manager) that TRITON cannot be used during the update.
It is advisable to check the tables for at least company 000 and also the testcompany/companies before you start the conversion. You can do this using session ttaad4225m000.
Use is made of the (path) data in$BSE/lib/install/install.data. It is advisable to check them before installation.
First run the rc.stop, then the rc.start script to remove any hanging processes and database locks. If rc.stop fails, bring down the environment manually.
Log in as root (do not use the su command). Check your TERM variable (echo $TERM). The vt220 emulation cannot be used: preferably use vt100 instead.
Go to the installation directory and start the install6.1 script (via ./install6.1). The script only prompts for the $BSE directory (enter the $BSE of the 3.0/3.1 environment to be updated).
Answer the question “Full update?” with “Yes” (MANDATORY!).
The installation script first calls ottiex1287, then starts reconfiguring the tools tables, and then calls ottiex1288. Under bisam, it takes approx. 30 minutes to reach this point.
Once the installation script has reached ottiex1288, the rest of the installation will probably run smoothly.
4.2.3 Step 3 – Check installation logs
After installation, the installation directory should be empty.
When a regular tape is used, the directoryextraremains.
The log files are in directory $BSE/log. Check the most recent ones (type ls -ltr $BSE/log to find them). Create a file called setbse in $BSE that sets the BSE, BSE_TMP, PATH and TERM(=vt100) variables, if it doesn’t exist already.
If the installation has been completed successfully, at this point the customer can start using TRITON again.
4.2.4 Step 4 – B/C – Import customization (ttiex1285m000)
From here on user must be “bsp”!
If available, import the customization dumps (B and/or C VRCs) with this session (do not rename them, by importing them into an other VRC, because of maintance reasons). Import the B VRCs first (if available).
4.2.5 Step 5 – Create new VRCs (ttadv1111m000)
From here on user must be “bsp”!
For general rules on the derived-from structure, see document 1034US, page 7.
Create the O- and U-VRCs using the session:
13 Application Development
3 Packages and Modules
3 Maintain Package VRCs
At least create U-VRCs, derived from the standard B40, for all packages in the format: package code/B40U/release/stnd/Updatespackage name B40_release
(example: tc/B40U/b/stnd/Updates Common B40_b).
Use the OPER_001 derived-from structure as a model for TMP_001.
For instace, if the localization (B40L_b_nl10) is available, then for tf and tp derive the U from the L instead of from the standard.
Do not include the ti (Business Organizer – B40L_b_org1) localization in the derived-from structure.
In the business organizer, items, for instance, are renamed as business objects. Therefore do not incorporate them in an operational/design/testing package combination. For those who want to use this localization, a separate package combination can be created.
Create customer-specific O-VRCs for all packages (exept tt). Basically, copy the existing structure of ‘own’ VRCs to BAAN IV. Retain the existing customer extension(s) as much as possible.
Example: |
OPER_001 contains 3.1O_a_kl01, derived from 3.1_a1.
DSGN_001 contains 3.1O_a_dsg1, derived from 3.1O_a_kl01.
Now create two new series of ‘own’ VRCs:
B40O_b_kl01 (derived from B40U_b_stnd, as no customization is involved) and:
B40O_b_dsg1 (derived from B40O_b_kl01).
4.2.6 Step 6 – Create directories for new VRCs (ttadv1115m000)
Create directories for all new (U and O) VRCs:
13 Application Development
3 Packages and Modules
4 Maintain Software Component Directories
Press [S] and enter the name of the VRC, press [I] to enter the six software component types. Do this for all VRCs. If the components are entered in the order of the ‘enum’ (press the spacebar), you can use the TRITON copying facility: Enter the six components for the first VRC. Press <Esc> to go to the choice field, press <Ctrl>[W], [Y], [B], [Y], enter the name of the next VRC, press [Y] and repeat these steps (from <Ctrl>[W] on) for all VRCs.
4.2.7 Step 7 – O – Copying ‘own’ work to new ‘own’ VRCs (ttadv6265m000)
This session has only have to be run if there are own developments (mostly menus, forms or reports). Start the copying session:
13 Application Development
16 Utilities
1 Copy Software Components to New Package VRC
For all own VRCs, copy everything from the old to the proper new
O-VRCs.
Also run this session for VRCs that are empty at UNIX level. There may be domains attached to these, or recent developments that are already present in tools may not have been converted to run time.
After this session the new O-VRCs at UNIX level are still (largely) empty; copying is currently only done at tools level .
4.2.8 Step 8 – Create New Package combination(s) (ttaad1120m000)
Check the derived-from structure via the session ttadv1411m000 before using this session.
Call the following session:
2 Application Configuration
8 Maintain Package Combinations
Create atleast one new package combination with the name TMP_001 for testing purposes (do not put this in shared memory).
4.2.9 Step 9 – Fill package combination(s) with VRCs (ttaad1221m000)
Start the session:
13 Application Development
3 Packages and modules
6 Maintain Packages by package combination
Fill the new TMP_001 package combination with the right O VRCs (corresponding with the VRCs in OPER_001 in the 3.0/3.1 environment). Again: keep to the original structure, but leave out ge (General) and tb (TRITON Support) if available.
End with [Y], to dump the package combination. In BAAN IV run time help is created automatically when you use this session to dump a package combination. Therefore, it may take up to an hour before the session is finished.
4.2.10 Step 10 – Migrate company/companies (ttaad1101m000)
Convert at least one test company to the new package combination via:
2 Application Configuration
Press [®] twice, to reach the ‘Miscellaneous’ menu.
2 Change Package Combination by Company
This session may result in a list of warnings (of the type ‘Warning: No DD for tcedi472 found’). They relate to new tables (for which there is no DD in 3.0/3.1 but there is one in BAAN IV) and can be ignored.
Run the session Check Tables (ttaad4232m000) now for the test company/companies to make sure that all tables are in the correct format.
4.2.11 Step 11 – Migrate user(s) (ttaad2200m000)
Migrate at least one user to the test package combination via:
3 User Management
1 General User Data
2 Change Package Combination by User
4.2.12 Step 12 – O – Dump forms and menus (ttadv5214m000)
Use this session to convert the forms and menus associated with the migrated ‘own’ work (if available) to run time:
13 Application Development
15 Run time Data-Dictionary
4 Create Run time Data Dictionary (forms and menus)
Set the field ‘Dump’ to 1 (default).
4.2.13 Step 13 – O – Compile reports (ttadv3240m000)
Use this session to compile the reports associated with the migrated ‘own’ work (if available):
13 Application Development
10 Reports
2 Compile Reports
Set the field ‘Compile’ to 1 (default). During compilation an error report is generated. Check this report. All warnings can be ignored.
If there are any errors, the normal procedure is to check if they also occurred in the old version (by compiling the ‘old’ own work via the old package combination, using the same session). If the errors are identical in both versions, there is a problem with the original functionality.
However, this is not possible now because of the fact that the 3.0/3.1 environment’s tools are now of the version B40_release (see the Remarks section of this chapter).
4.2.14 Step 14 – Validate the system
Get a printout of the commercial (tools) functions the customer has bought. Validation of the toolset can only take place when logging on to the customer system as root (or using the su command). Do not forget to set the environment variable by running . ./setbse. After the validation process, log on as bsp again and start the bshell.
NOTE |
Never give the Baan default password to customers.
Choose menu options:
6 Maintain Security Code/Validation Key (ttiex3102m000)
Enter the customer’s data from the printout of commercial information for this customer . For Baan NL customers, place a 2 before the customer number. All the other information can be found on the customer data printout.
2 Maintain Requested System Configuration (Tools) (ttiex3101m000)
Type [S] to enter the correct date. Then type [C] to edit the screen. Enter the data provided in the commercial printout. Do not make any changes.
1 Maintain Requested System Configuration (ttiex3100m000)
For BAAN IVa enter Yes for all entries, for all packages. Press [N] to go to the next page; <Ctrl>[N] to go to the next package.
For BAAN IVb only special items (t102 Foundation Tools and t103 Development Tools) have to be set to Yes when they are bought and not the entire software configuration (as in BAAN IVa).
3 Print Requested System Configuration ()
Press [Y]. Enter: [D] (Display) or ASCIF (ascii file; by default this file will be placed in the current directory). In the latter case, choose a logical file name.
If applicable, read-in the file via a subshell ([<]).
Provide this printout to Baan. This will be used to create the validation key. When you receive this key in a printout from Baan, proceed with the validation.
Choose menu options:
1 Software Installation
6 Maintain Security Code/Validation Key (ttiex3102m000)
Press [C] to edit the screen; enter the Validation Key (Tools) and the Validation Key Software (Standard). Make sure the Security Key on the Baan printout is exactly the same as the one in this session. Press [E] to exit.
NOTE |
To run the next session, user has to be root. Change back to bsp after completing Validate Toolset and starting the license-daemon.
7 Validate Toolset (ttiex3220m000)
On the question to start the license server, answer Yes. At this point an error message may appear. If a message appears, check if the license daemon is running.
You may have to start the license daemon manually. The license daemon must be running in order to complete the next step (otherwise another error message appears).
Check the license daemon by leaving the bshell (via [<] on the Choice prompt) and by entering ps -ef | grep licd. The license daemon is a process with the name licd6.1. If necessary, start the license daemon by entering the licd6.1 command. Return to your bshell (type exit) and perform the following action.
8 Configure Application (ttiex3225m000)
This is also known as patching the software. Enter: Yes (; the next field, No, is skipped), Yes. Press [Y] to confirm. If you see ‘Sorting…’, the process has been started correctly.
4.2.15 Step 15 – Create tables (ttaad4230m000)
For all test company numbers migrated to BAAN IV, create new empty tables using the session:
6 Database Management
Press [®] twice, to reach the ‘Miscellaneous’ menu.
3 Maintain Logical Tables
4.2.16 Step 16 – Parameters (tcmcs0295m000)
Run this session for all testcompany numbers that were migrated to BAAN IV.
4.2.17 Step 17 – Checking and finalizing
Make sure the scripts in $BSE/bin are restored to their old state (see the section ‘Remarks’ in the chapter “Preparation”).
Now turn to the next chapter for performing the final step – running the correction program for the test company/companies.
5 Correction Program and Checking the Conversion – both scenarios |
The first section of this chapter describes the running of the correction program that has to be run (for both scenarios) for the testcompanies.
Bear in mind that the tccov0000m000 has to be adapted to the DataModel of BAANIV, in case this is not standard (see section 1.3.2).
The second section describes the sessions needed by package to perform a general and a specific data check after the conversion has taken place.
5.1 Conversion of TRITON 3.x => BAAN IV (tccov0000m000)
Basically, this session is a shell around a number of correction and conversion sessions which are used to convert the data of an older TRITON 3.* version to BAAN IV.
First, the right TRITON version must be selected as the original version. Next the packages which must be converted to BAAN IVa must be selected since this session will only convert and correct the data of selected packages. On the second form of this session, the current status of each correction or conversion part is displayed. Next, the Real Conversion field, which is the most important parameter in this session, must be set to No to run a test conversion which will result in a report of all changes which will occur as a result of a conversion. Test conversions should be run until the conversion is executed correctly. This is done to ensure that the real conversion is successful.
At the bottom of the form, information regarding the version which is converted, the user who performed the conversion, and the number of times the conversion has been started is displayed.
For the different packages, the following sessions are executed to correct or convert the tables to BAAN IV (if applicable):
BAAN Distribution
n Conversion of Distribution 3.X => 3.1B (tccov1001m000)
By means of this session, the following tables are converted:
– Selections
– Selection Lines
– Letters
– Layouts by Letter
– Planned INV Purchase Orders
– Statuses
– Messages to be Generated
– Generated Messages
– Generated Batch Numbers
– Purchase Orders
– Receipts
– Sales Orders
– Customers
n Conversion of Distribution 3.1B => BAAN IV (tccov1002m000)
By means of this session, the following tables are converted:
– Parameter Tables
– Purchase Statistics
– Purchase Price List
– Purchase Inquiries
– Sales Statistics
– Sales Price List
– Currency Rates
In addition, a number of fields and enums are added to BAAN IV by means of this session, namely:
– Distribution Order Types
– Sales (Success Percentage)
– Inventory (Planner/Buyer)
BAAN Manufacturing
n Conversion of Manufacturing 3.1A => BAAN IV (tccov3001m000)
By means of this session, a number of fields and tables are modified, namely:
– The surcharge history is created
– The value of the Drawing field in the Engineering Item Revisions table is deleted
– The Eco Lines table is set to the initial value of the data definition
– The Device for Messages in Generate MPS parameter is set to the initial value of the data definition
– The Only Reschedule Messages for Total Order Quantity parameter is set to the initial value in the data definition
– The value of the Finance Company field in the Planned MPS Interplant Orders, Planned MPS Purchase Orders, and Planned MRP Purchase Orders tables is entered
– The value of the Financial Supplier Group field in the Financial Project Transactions table is deleted
n Conversion Units to Units by Unit Sets (tccov3002m000)
Because of the new way in which (alternative) units are handled, the following tables are converted and modified by means of this session:
– Engineering Items
– Items
– Alternative Units
– Item Default Data
– Calculation Parts
– Customized Items
n Conversion Unit Conversion Factors (tccov3003m000)
Because of the new way in which (alternative) units are handled, the following conversion factors are converted and modified by means of this session:
– Tables Units
– Alternative Units
– Customized Items
n Fill Auxiliary Item Table (tiitm100) tccov3004m000)
Because of the introduction of item containers in BAAN IV, this session is used to ensure that the number of records in the tiitm100 table is the same as in the tiitm001 table.
BAAN Finance
n Change Sign in Open Item Table (tfacp200) (tccov2001m000)
By means of this session, the symbol for all currency differences of anticipated payments is modified.
n Change Step for Antic. Unalloc/Adv Payments (tccov2002m000)
n Check Standing Order (tfcmg114) (Posting Data) (tccov2003m000)
By means of this session, the Standing Order Number field is added to the Posting Data for Anticipated Payments without Invoice table.
n Check Anticipated Document (tfacp200/tfacr200) (tccov2004m000)
By means of this session, the tables for unallocated/advance receipts/payments are checked to ensure that the anticipated document number is not specified. If the anticipated document number is specified, this is corrected after which the selected records are saved in a file.
n Change Enumerated Field (tfcmg108) (tccov2005m000)
By means of this session, the number of enum values of a field in the One Time Supplier Addresses table is extended from 2 to 8.
n Update Payment Differences from Anticipated Payment (tccov2006m000)
BAAN Transportation
n Conversion of Transportation 3.x => BAAN IV (TCO) (tccov5001m000)
By means of this sessions, the value of the Match Status cost line field is set to All Approved if there is a link with Finance and a cost line with status Posted.
Each of these sessions has an indicator which displays the conversion status. The following statuses can be distinguished:
n Status not defined
This means that the initial value is displayed.
n Execution not necessary
This means that the conversion does not apply to the original version and packages which were selected.
n Not executed
This means that the conversion must still be executed.
n Execution aborted
This means that the conversion was aborted due to an error which occurred during the conversion.
n In process
This means that the session is running.
n Execution completed
This means that the conversion was successful.
For each session, a logfile is created in which data regarding the events, the converted components, and the errors which occurred during each conversion. These logfiles are located in the $BSE/log directory. For example: $BSE/log/log.cov1001.
5.2 General Data Check
Although there are no extensive changes in the data structure, it is necessary to check whether or not the data has been converted. This can be done by drawing a number of samples from a number of tables in the different packages.
5.2.1 TRITON Common
TRITON 3.1b |
BAAN IV |
Description |
tccom1401m000 |
tccom1401m000 |
Print Customers |
tccom2401m000 |
tccom2401m000 |
Print Suppliers |
5.2.2 TRITON Distribution
TRITON 3.1b |
BAAN IV |
Description |
tdilc1414m000 |
tdilc1414m000 |
Print Inventories by Warehouse and Item |
tdinv6220m000 |
tdinv6220m000 |
Perform Slow-Moving Analysis by Item |
tdinv6230m000 |
tdinv6230m000 |
Perform Inventory Valuation by Item |
tdinv7410m000 |
tdinv7410m000 |
Print Stock Transactions by Item |
tdinv8450m000 |
tdinv8450m000 |
Print Chart of Accounts for Stock and WIP Transactions |
tdpst0401m000 |
tdpst0401m000 |
Print Purchase Statistics |
tdpur4404m000 |
tdpur4404m000 |
Print Purchase Invoices |
tdpur4407m000 |
tdpur4407m000 |
Print Purchase Orders by Order Number |
tdpur4431m000 |
tdpur4431m000 |
Print Receipts |
tdpur5401m000 |
tdpur5401m000 |
Print Purchase Order History by Supplier and Item |
tdsls1403m000 |
tdsls1403m000 |
Print Quotations by Item |
tdsls4404m000 |
tdsls4404m000 |
Print Sales Invoices |
tdsls4410m000 |
tdsls4410m000 |
Print Sales Orders by Order Number |
tdsls4431m000 |
tdsls4431m000 |
Print Sales Order Deliveries |
tdsls5401m000 |
tdsls5401m000 |
Print Sales Order History by Customer and Item |
tdsls6401m000 |
tdsls6401m000 |
Print Chart of Accounts – Invoice Analysis |
tdsls6402m000 |
tdsls6402m000 |
Print Chart of Accounts – Invoice Analysis by VAT Code |
tdsls6403m000 |
tdsls6403m000 |
Print Chart of Accounts – Invoice Details |
tdsst0401m000 |
tdsst0401m000 |
Print Sales Statistics |
5.2.3 TRITON Manufacturing
TRITON 3.1b |
BAAN IV |
Description |
tibom1214m000 |
tibom1214m000 |
Detect Loops in Production BOMs |
tibom1411m000 |
tibom1411m000 |
Print Production Bills of Material (Multi-Level) |
ticpr0410m000 |
ticpr0410m000 |
Print Cost Price Components |
ticpr2410m000 |
ticpr2410m000 |
Print Surcharges by Item Group |
ticpr2410m000 |
ticpr2410m000 |
Print Cost Price Calculation by Item |
ticst0401m000 |
ticst0401m000 |
Print Actual Costs by Production Order |
ticst2401m000 |
ticst2401m000 |
Print Costing History by Order |
tiedm1470m000 |
tiedm1470m000 |
Print EBOM and PBOM Consistency |
tigrt0441m000 |
tigrt0441m000 |
Print Classified Items by Family |
tihra1401m000 |
tihra1401m000 |
Print Hours Accounting by Employee |
tihra3460m000 |
tihra3460m000 |
Print Hours History by Employee |
tiitm0401m000 |
tiitm0401m000 |
Print Item Data |
tipcf0450m000 |
tipcf0450m000 |
Print Product Features |
tipcf2401m000 |
tipcf2401m000 |
Print Constraint IDs by Generic Item |
tipcf3411m000 |
tipcf3411m000 |
Print Generic Bill of Material (Multi-Level) |
tipcf4401m000 |
tipcf4401m000 |
Print Generic Price Lists |
tipcf6410m000 |
tipcf6410m000 |
Print Product Variant Statistics |
tipcs1460m000 |
tipcs1460m000 |
Print Cost Price by Budget |
tipcs1462m000 |
tipcs1462m000 |
Print Cost Price Calculation by Budget |
tipcs2451m000 |
tipcs2451m000 |
Print Customized Bills of Material (Multi-Level) |
tipcs3460m000 |
tipcs3460m000 |
Print Cost Price by Project |
tipcs3462m000 |
tipcs3462m000 |
Print Actual Cost Price by Project |
tipcs8410m000 |
tipcs8410m000 |
Print Financial Project Transactions |
tipcs8450m000 |
tipcs8450m000 |
Print Chart of Accounts for Financial Project Transactions. |
tisfc0401m000 |
tisfc0401m000 |
Print Production Order Report |
tisfc0450m000 |
tisfc0450m000 |
Print Work-in-Process |
tisfc2401m000 |
tisfc2401m000 |
Print Subcontracted Operations by Supplier |
5.2.4 TRITON Finance
TRITON 3.1b |
BAAN IV |
Description |
tfacp2420m000 |
tfacp2420m000 |
Print Aging Analysis by Supplier |
tfacp2415m000 |
tfacp2415m000 |
Print Control Account Checklist |
tfacr2420m000 |
tfacr2420m000 |
Print Aging Analysis by Customer |
tfacr2415m000 |
tfacr2415m000 |
Print Control Account Checklist |
tffst1404m000 |
tffst1404m000 |
Print Financial Statements |
tfgld0411m000 |
tfgld0411m000 |
Print Transaction Type Master |
tfgld0408m000 |
tfgld0408m000 |
Print Chart of Accounts |
tfgld1406m000 |
tfgld1406m000 |
Print Finalized Transactions by Ledger Account |
tfgld3402m000 |
tfgld3402m000 |
Print Trial Balance |
tfgld3409m000 |
tfgld3409m000 |
Print Column Balance |
tfgld3405m000 |
tfgld3405m000 |
Print Trial Balance with Dimensions |
5.3 Specific Data Check
During the final step in the conversion, a number of sessions are automatically activated (if required) to convert specific data. The lists of sessions below can be used to check the modifications. Read also the session help of the conversion sessions for more information about the modifications.
5.3.1 BAAN Distribution
Conversion of Distribution 3.X => 3.1B (tccov1001m000)
BAAN IV |
Description |
tdsmi0470m000 |
Print Selections |
tdsmi1450m000 |
Print Letters |
tdinv3420m000 |
Print Planned INV Purchase Orders |
tcedi7401m000 |
Print History of Generated Messages |
tdpur4401m000 |
Print Purchase Orders |
tdpur4431m000 |
Print Receipts |
tdsls4405m000 |
Print Sales Orders by Customer |
tccom1401m000 |
Print Customers |
5.3.2 BAAN Manufacturing
Conversion of Manufacturing 3.1A => BAAN IV (tccov1002m000)
BAAN IV |
Description |
tdpst0401m000 |
Print Purchase Statistics |
tdpur0404m000 |
Print Prices by Price List and Item |
tdpur1401m000 |
Print Inquiries |
tdsst0401m000 |
Print Sales Statistics |
tdsls0404m000 |
Print Prices by Price List and Item |
tcmcs0408m000 |
Print Currency Rates |
5.3.3 BAAN Finance
n Change Sign in Open Item Table (tfacp200) (tccov2001m000)
n Change Step for Antic. Unalloc /Adv Payments (tccov2002m000)
n Check Standing Order (tfcmg114) (Posting Data) (tccov2003m000)
n Check Anticipated Document (tfacp200/tfacr200) (tccov2004m000)
n Change Enumerated Field (tfcmg108) (tccov2005m000)
n Update Payment Differences from Anticipated Payment (tccov2006m000)
BAAN IV |
Description |
tfacp2421m000 |
Print Purchase Invoices |
tfacr2421m000 |
Print Sales Invoices |
5.3.4 BAAN Manufacturing
Conversion of Manufacturing 3.1 A => BAAN IV (tccov3001m000)
BAAN IV |
Description |
timps5410m000 |
Print Planned MPS Interplant Orders |
timps5430m000 |
Print Planned MPS Purchase Orders |
timrp1421m000 |
Print Planned MRP Purchase Orders |
Conversion Units to Units by Unit Sets (tccov3002m000)
Conversion Unit Conversion Factors (tccov3003m000)
BAAN IV |
Description |
tiitm0401m000 |
Print Item Data |
tiitm0410m000 |
Print Item Default Data |
tiedm0410m000 |
Print Engineering Items |
tipcs2421m000 |
Print Customized Item Data |
6 Appendix A – Upgrading Customizations |
This chapter describes the steps needed to upgrade both external and in-house customizations.
6.1 Recommendations
After a new version / release has been installed by means of the installation program, this new software is not yet active. To activate this software, a new package combination can be created to which a company can be linked to test the software while the remaining companies continue using the old TRITON 3.1 software. After the software has been tested and approved, these remaining companies are also migrated to the new software.
A distinction is made between migrating customizations developed by Baan or a Baan dealer and customizations developed by the customer (so-called in-house customizations). In this context, customizations are modifications to the standard software.
6.2 Upgrade of In-House Customizations
To upgrade in-house customizations, the following steps must be taken:
1 The tdB40O_a_cu01 and tdB40O_a_cu02 PVRCs must be created.
2 The directories for software components must be set for both PVRCs.
3 The software components must be exported from the TRITON 3.1 environment by means of the Export Data Dictionary (ttiex1280m000) session and imported in the BAAN IV environment by means of the Import Data Dictionary (ttiex1285m000) session, namely:
– from td3.1O_b_cu01 to tdB40O_a_cu01
– from td3.1O_b_cu02 to tdB40O_a_cu02
4 The VRC tree must be defined.
Figure 6-1 – Start position
Figure 6-2 – Testing the new version
Figure 6-3 – Testing the in-house customization
Figure 6-4 – Released update
6.3 Upgrading Customized Software and In-House Customizations
To upgrade both customized software and in-house customizations, the same procedure can be followed as for in-house customizations only. The only difference is that this procedure is extended with a step in which the external customizations are tested.
An update of the standard involves an update of the customization which is derived from that standard. This is shown in Figures 6-5 through 6-9.
Figure 6-5 – Start position
Figure 6-6 – Testing the standard installation of BAAN IV Figure 6-7 – Testing the external customization
Figure 6-8 – Testing the in-house customization
Figure 6-9 – Released software
Prior to converting the data, the data model in BAAN IV must be assessed as being the correct data model and the correction program (tccov0000m000) has to be adapted to this.