BAAN IV Staged Plan for the Update of BAAN IV to BAAN IVb2baansupport.com/docs/baan/Staged Plan for the Update of... · 2017. 12. 4. · details where they are installed, you must

BAAN IV

Staged Plan for the Update of BAAN IV toBAAN IVb2

Installation Manual U7090A US

Staged Plan for the Update of BAAN IV to BAAN IVb2


Document information

Document

Document code : U7090A USDocument group : User DocumentationDocument title : Staged Plan for the Update of BAAN IV to BAAN IVb2Edition : AMonth modified : November 1997

Check the BaanDoc database to see if this document is still a valid edition.

© Copyright 1997 Baan Development B.V. All rights reserved

The information in this document is subject to change without notice. No part of this document may

be reproduced, stored or transmitted in any form or by any means, electronic or mechanical, for any

purpose, without the express written permission of Baan Development B.V.

Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, from

any errors, omissions or discrepancies between the software and the information contained in this

document.


Staged Plan for the Update of BAAN IV to BAAN IVb2i

Table of contents

1. Preparation 11.1 Backup 11.2 Baan IV 11.3 System manager 11.4 Time frame 21.5 Export DEM models 21.6 Prerequisites 21.7 Disk space 31.8 Validation 4

2. Installation procedure 52.1 Step 1: reading out tapes 52.1.1 Regular tape 52.1.2 Master tape 52.1.3 Tape with customizations 62.2 Step 2: start the installation script 62.3 Step 3: check the installation logs 72.4 Step 4: B/C-VRCs–import customization 72.5 Step 5: create new VRCs 72.6 Step 6: create directories for new VRCs 82.7 Step 7: O-VRCs–copying own work to new own VRCs 92.8 Step 8: create new package combinations 92.9 Step 9: fill package combinations with VRCs 92.10 Step 10: export DEM models 102.11 Step 11: migrate companies 102.12 Step 12: migrate users 102.13 Step 13: import DEM models 112.14 Step 14: check bug fixes in U-VRCs 112.15 Step 15: O-VRCs–dump forms and menus 122.16 Step 16: O-VRCs–compile reports 132.17 Step 17: patching 132.18 Step 18: create tables 132.19 Step 19: parameters 132.20 Step 20: conversion from BAAN IVa(1) to BAAN IVb2 142.21 Step 21: checking and finalizing 14

Staged Plan for the Update of BAAN IV to BAAN IVb2ii

Staged Plan for the Update of BAAN IV to BAAN IVb2iii

About this document

This document describes the update of BAAN IV to BAAN IV b2.

Chapter 1 describes the preconditions for the update.

Chapter 2 describes the steps of the update.

This document can be used by all persons that want to update a BAAN IVenvironment to BAAN IV b2 on a UNIX server. However, users must have anelementary knowledge of UNIX. Users must also have an elementary understanding ofthe way TRITON software is structured: with Package VRCs, Package Combinations,and the derived-from structure.

The person performing the update must also know something about how to movearound in BAAN IV, that is, what keys to use to perform certain actions. A few hintsare given below.

The document describes an installation of BAAN IV on a (single) UNIX server. Theexamples and descriptions of actions on the UNIX prompt presuppose the use of theKorn shell (ksh). In the text, the user is supposed to use an ASCII interface, whichactivates a user session through the ba6.1 command. This of course can also be anX Windows interface if X is configured on the server (bx6.1).

There are four possible types of databases:

1 tbase2 tbase_tp3 Oracle4 Informix

However, the update is (in principle) fully transparent to your database type.

The following points about notation should be noted:

n Keystrokes are placed between brackets.Angle brackets for function keys. Square brackets are used for letters andtypographic characters.

For example:− Press <Ctrl>[C]− Use the <Shift> key− Use [C] to edit the screen

n UNIX keywords, variables, path names, and so on are in bold (case-sensitive).

For example:− The cpio command− Use licmon5.0 -b− Go to $BSE/bin

Staged Plan for the Update of BAAN IV to BAAN IVb2iv

n Variables are in italics.

For example, create the directory path name/baan. This asks you to create asubdirectory baan somewhere in the file system, for example, /usr3/baan or/disk1/temp/baan.

The following hints give some guidance on how to use the interface:

n To exit of a field and return to the Choice prompt, move the cursor to the first left-hand position of the field and press <Esc>.

n The Choice prompt is language-sensitive; pressing [Y] for Yes might well bepressing [J] (for Dutch and German) or pressing [O] (for French) - and so on.

n Use [O] on the Choice prompt to see your options. Use <F6> for a popup-menu(leave the menu without selecting anything by pressing <Esc>).

n Type [E] at the Choice prompt to leave a session while keeping the changes. Type[A] to leave without making changes.

n The Choice prompt is language-sensitive. This means that you press [Y] for Yes inEnglish, [J] for Dutch and German, or [O] for French, and so on.

n Type [O] at the Choice prompt to view your options. Press <F6> to display apopup menu. Press <Esc> to leave the menu without selecting anything.

Preparation


1.1 Backup

You require a good and recent backup of the software and the tables present, inparticular of the tools and company tables that you want to migrate to BAAN IVb2.

1.2 BAAN IV

You cannot use BAAN IV while the installation script is running. Nor can you usecompany numbers that are being reconfigured when they are migrated from onepackage combination to another, or while the operational package combinations thesecompany numbers are associated with are being dumped.

Complications can arise from bug fixes that have been installed in the BAAN IVa(1)or BAAN IVb(1) environment. If these bug fixes have been installed in theB40U_a(1)_stnd or B40U_b(1)_stnd VRCs (which are intended for these bug fixes),they can be screened and copied to the BAAN IVb2 environment, if required. See step12 of the procedure.

This is, of course, impossible, if these B40U_a(1)_stnd or B40U_b(1)_stnd VRCs arenot present, and bug fixes have been installed in the standard VRCs. In this case youmust determine which bug fixes have been installed, and which of these are notincluded in the BAAN IVb2 update. The ones that are not included in the BAAN IVb2update, must then be obtained and later on placed in the B40U_b2_stnd VRCs. Todetermine which objects these are, check your bug fix-administration or call the ISC.

Checking the bug fixes must be done before the update installation script is runbecause this is a full update and the overwrite option is set to Yes. Otherwise, there isa chance some bug fixes will be lost if they are located in BIVa(1) or BIVb(1) VRCs.Please note that in this case, when bug fixes in the BIVa(1) or BIVb(1) VRCs areoverwritten during the update, they will also be lost for the BAAN IVb2 operationalenvironment(s).

If no bug fix administration exists, that includes a registration of the bug fixes and thedetails where they are installed, you must perform the update and obtain the lost bugfixes afterwards –when old errors recur– from the backup (see section 1.1).

1.3 System manager

In some cases the customer’s system manager will have to assist, for instance, byreading out tapes, calling in by modem, and starting the installation script.

1. Preparation

Preparation


1.4 Time frame

The time frame of the update very much depends on the system and the database type.Assuming the installation script is started on the evening of the first day, allow 4 to 8hours on the second day to complete the job. This may be considerably more –to thepoint of having to allow a third day– where Oracle installations and/or the conversionof many or large companies are involved. The time frame on the first day is 1 to 5hours 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 withthe customer. Try to take into account that the customer may want to run a backupfirst. The installation script takes between 3 and 40 hours (updates under Oracle cantake a long time) to run.

1.5 Export DEM models

Where possible it is recommended to export the DEM models per company that youwant to migrate to BAAN IVb2 before you start the update, because it this a verytime-consuming action. See step 10 for more information about how to export themodels.

1.6 Prerequisites

Reserve 300 MB to 500 MB for reading the tape. A full standard update (full update)requires 150 to over 250 MB (for one language, excluding customization, underbisam), distributed as follows:

n Approximately 160 MB for the BIVb2 VRCs ($BSE/application).

n In addition, the BIVa(1) or BIVb(1) VRCs will increase somewhat in size (again,depending on the software installed).

n 50 MB for the new porting set (the old $BSE/bin is copied; may be removed later)

n Some expansion of the tools tables ($BSE/dict; or ORACLE or Informix’s .dat and.idx space. Remember that the ratio between bisam and ORACLE is about 2.5: 50MB in bisam is equivalent to 125 to 150 MB in ORACLE)

Allow an extra 200 MB per additional language.

Preparation


1.7 Disk space

Call into the customer’s system to determine if there is sufficient disk space at theproper places (see previous section).

Check the derived-from structure, the package combinations and associatedcompanies.

After installation, the existing BAAN IVa(1) or BAAN IVb(1) structure that willcontinue to be used must be copied so to speak under BAAN IVb2. This requires thecreation of at least one new (BAAN IVb2) package combination. The BAAN IVb2environment must be set up for testing; this implies that you should not at this stagemigrate all existing package combinations (and associated company numbers) toBAAN IVb2! As a rule, only those BAAN IVb2 equivalents of the packagecombinations that have companies attached to them (but do not create an equivalent ofthe standard [B40S(a)b or B40S(a)b1] package combination) must be created.

Make sure that if the customer wants a (physical) conversion of own customizations(O-VRCs) to BAAN IVb2 all the software is included in the process. Note that theadaptation of forms, menus, reports, and so on themselves is the responsibility of theowner of the customizations.

Take into account any (new) customizations, too. If there is customized software inBAAN IVa(1) or BAAN IVb(1), the customization supplier must update this toBAAN IVb2. This applies to B, C, and possibly L-VRCs, when these are not includedon the (master) tape. The update cannot take place before the updated customizedsoftware has been delivered on tape.

Generally, one single company and a number of users are migrated to each newpackage combination for testing purposes and, possibly, for changes in own softwareby the customer.

Make a list of the package combinations for which a BAAN IVb2 version must becreated (and what each one will be called).

Finally, discuss everything.

This means:

n The backupn BAAN IV downtime/time framen Task assignmentn Configuration after the update (package combination(s), user(s) and

company/companies to be migrated).

You must only deviate from the test scenario if the risks that going live with theupdate involves have been carefully explained to you and if you are prepared to takeon those risks.

Preparation


1.8 Validation

When you do an update from BAAN IVa(1) to BAAN IVb2 an extra action must beperformed. Because there are several additional commercial functions, and the way oflicense-handling is different, a new validation must be done. This action can only bedone by a Baan employee for security reasons. So, the best thing to do is make anappointment for validation when doing an update from BAAN IVa(1) to BAAN IVb2.

Remarks

n During installation a new porting set is installed. This implies that all theadjustments made in their current versions in the directory $BSE/bin, such asdiskbet.pc and telbnk.pc, will be lost after the update. The old scripts will still beavailable in $BSE/bin, under the original name, followed by a dash (-).Make sure that nonstandard scripts (for example, the BAAN IV Reference Modelconfiguration scripts), or scripts that are subject to change (diskbet.pc andtelbnk.pc) are properly restored or adjusted after the update.

n For Motorola and Hewlett Packard with short file names, the mechanism describedabove (when the porting set is replaced, the old bin files are copied to their originalname followed by a dash (-)) does not work: the 15-character limit is exceeded,which causes the installation script to block.

n This can be prevented as follows (instead of rc.stop and rc.start in step 2 of theinstallation procedure):

− Stop BAAN IV.− Move the directory $BSE/bin to, say, $BSE/save/bin.− Copy the bin directory from the tape directory (under ln.0000/bse/bin) to

$BSE/bin.− Move the contents of the bin directory from the tape directory to another

directory (not under the tape directory; for example,usr3/baantape/ln.0000/bse/bin to /usr3/save/bin). The directoryln.0000/bse/bin should be retained, but empty. Copy the new porting set(coming from the tape) to the directory $BSE/bin before the installation scriptis started.

− Restart BAAN IV and continue, beginning at step 2 of the installationprocedure.

Installation procedure


2.1 Step 1: reading out tapes

In a letter accompanying the tape(s), the customer is asked to read (each of) the tape(s)into a (new) empty directory.

Preferably, let the system manager do this. In case of a master tape, be sure to giveaccurate directions.

If this is not possible, and you are using a modem, try to use the maslat utility(developed by the Baan company) or a (nohup) background process.

It is advisable to perform this action as user root.

There will always be at least one tape available for the update on the customer’s site: aregular tape (for Baan company (NL) customers) or a master tape. This tape containsthe standard software and, possibly, localizations (L-VRCs).

Finally, customized software (C-VRCs) or line-of-business specific software(B-VRCs) can be available on another tape.

Make sure all the required tapes, containing standard software and customizations, areavailable.

2.1.1 Regular tape

Create a temporary, empty directory (for example, path name/baan) on a suitable filesystem. Do not include a directory or subdirectory with the name bse5.0 in the pathname.

In this empty directory, read out the tape by typing the cpio command or the bstapeutility.

Use cpio -itcdvB to list the contents, use cpio -icvdB to read (with or without v forverbose). Use the default rewind device (with no hardware compression).

All systems supplied by Simac Services will have bstape available in the/usr/simac/bin directory. Use bstape toc to list the contents, use bstape off to read(no background; verbose).

2.1.2 Master tape

Detailed information about reading out master tapes is provided in the BAAN IV 3.1Installation Manual (5574US) under section 6574-04US, Loading the Software.

Create a temporary, empty directory (for example, pathname/baan) on a suitable filesystem. Do not include bse in the pathname. In this empty directory, read the firstblock from the tape.

Use cpio -itcdvB to list the contents, use cpio -icvdB to read (with or without v forverbose). Use the default no-rewind device (with no hardware compression).

2. Installation procedure

NOTE:



Start the masread6.1 script by entering ./masread6.1, while you are in the directorywhere you read out the master tape.

Select the package VRCs and languages to be installed. Use a listing of the softwarefor the customer to determine what these are.

Subsequently, the script will read these elements from the tape.

2.1.3 Tape with customizations

Read each tape in a new, empty directory using the procedure for a regular tape,unless the instructions with the tape give other directions.

2.2 Step 2: start the installation script

User must be root!

While the installation is running, the customer cannot use this environment. Check ifeveryone has left the bshell and has been advised (by the system manager) thatBAAN IV cannot be started. Log in as root (do not use the su command). Check yourTERM variable (echo $TERM). The vt220 emulation cannot be used: preferably usevt100 instead. First run the rc.stop. Next, run the rc.start script to remove any hungprocesses and database locks. If rc.stop fails, bring down the environment manually.If possible, use maslat to start the installation script. Otherwise, ask the customer tostart it. It cannot run as a background process.

Use is made of the (path) data in $BSE/lib/install/install.data. It is advisable to checkthe data before installation.

Go to the installation directory and start the install6.1 script (via ./install6.1). Thescript only prompts for the $BSE directory. Enter the $BSE of the BIV_a(a1, b, b1)environment to be updated.

Languages or localizations cannot be selected for installation. Nor is a standard(BAAN IVb2) package combination created. Answer the question “Full update?” withYes (this is mandatory!).

The installation script can be interrupted by entering an interrupt (for instance bypressing <Esc> followed by [q]). After interruption, the script can be simply restarted.Press [!] to start a UNIX shell, and return to the installation script via exit. Themessage from the script that says “Please remove all running bshells, pdaemon etc.” ismisleading, in that you are not meant to interrupt the installation script and start killingprocesses manually (least of all the license daemon). The message is only meant toindicate that the installation script is doing this for you. The last question asked by thescript is: “Are you ready for installation?” Only after this is answered with Yes theupdate starts.

The installation script first calls ottiex1287, then starts reconfiguring the tools tables,and then calls ottiex1288. Under bisam, it takes approximately 30 minutes to reachthis point.

Once the installation script has reached ottiex1288, the rest of the installation willprobably run smoothly (unless confronted with disk space problems or power failure).



2.3 Step 3: check the installation logs

After installation, the installation directory should be empty.

When a normal tape is used, the directory extra remains.

Close maslat after using. The log files are in the directory $BSE/log. Check the mostrecent log files (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 theinstallation has been completed successfully, the customer can start using BAAN IVagain.

2.4 Step 4: B/C-VRCs–import customization

From here on user must be logged on as bsp!

Import the customization dumps (when available) with the Import Customization(ttiex1285m000) session. Import the dumps in their original VRCs (so, do not renamethem).

If line-of-business specific software is available, follow the instructions for thatparticular type of software. See the document about Importing Software dumps (for C-VRCs), and for instance, the Installation BAAN IV Branchemodel document (forcertain types of B-VRCs).

2.5 Step 5: create new VRCs

From here on user must be logged on as bsp!

Create the O- and U-VRCs using the Maintain Package VRCs (ttadv1111m000)session:

13 Application Development

3 Packages and Modules

3 Maintain Package VRCs

Create U-VRCs, derived from the standard B40_b2, for all packages in the format:package code/B40U/b2/stnd/Updates package name BIVb2.

For example, tc/B40U/b2/stnd/Updates Common BIVb2.

If the localization B40L_b2_nl10 is included, then for tf and tp derive the U from theL instead of from the standard.

Do not include the ti (Business Organizer – B40L_b2_org1) localization in thederived-from structure.

In the Business Organizer, items, for instance, are renamed as business objects.Therefore, do not incorporate them in an operational, design, or testing packagecombination. For those who want to use this localization, a separate packagecombination can be created.



In case of customizations (C-VRCs), derive the customization from the U-VRCs. If(also) B-VRCs are available, put these in the derived-from structure in the appropriateplace. See the documentation mentioned at the beginning of this step.

Create customer-specific VRCs for all packages. Basically, copy the existing structureof own VRCs to BIVb2. Retain the existing customer extension(s) as much aspossible.

Example:

OPER_001 contains B40O_b_kl01, derived from B40U_b_stnd. DSGN_001 containsB40O_b_dsg1, derived from B40O_b_kl01. Now create two new series of own VRCs:B40O_b2_kl01 (derived from B40U_b2_stnd, as no customization is involved) and:B40O_b2_dsg1 (derived from B40O_b2_kl01).

Check the derived-from structure via the Print Package VRCs (ttadv1411m000)session.

2.6 Step 6: create directories for new VRCs

Create directories for all new (U and O) VRCs using the Maintain SoftwareComponent Directories (ttadv1115m000):



4 Maintain Software Component Directories

Press [S] and enter the name of the VRC. Press [I] to enter the six software componenttypes. Do this for all VRCs.

If the components are entered in the order of the enum (press the spacebar), you canuse the BAAN IV copying facility:

n Enter the six components for the first VRCn Press <Esc> to go to the choice fieldn Press <Ctrl>[W], [Y], [B], [Y]n Enter the name of the next VRCn Press [Y]n Repeat these steps (from <Ctrl>[W] on) for all VRCs



2.7 Step 7: O-VRCs–copying own work to new own VRCs

Start the Copy Software Components to New Package VRC (ttadv6265m000) session:


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.

Run this session for VRCs that are empty at UNIX level. There may be domainsattached, or recent developments that are already present in tools may not have beenconverted to run time.

After this session, the new O-VRCs at UNIX level are still (largely) empty; copying iscurrently only done at the Tools level .

2.8 Step 8: create new package combinations

Start the Maintain Package Combinations (ttaad1120m000) session:

2 Application Configuration

8 Maintain Package Combinations

Create one or more new package combinations under a name agreed with thecustomer. Do not put these in shared memory.

2.9 Step 9: fill package combinations with VRCs

Start the Maintain Packages by Package Combination (ttaad1221m000) session:



6 Maintain Packages by Package Combination

Fill the new package combination(s) with the O-VRCs. Again, keep to the originalstructure. End with [Y] to dump the package combination. Do this step for all newpackage combinations.

NOTE:



2.10 Step 10: export DEM models

Because in BAAN IVa(1) some DEM-components are saved as version-dependent.Therefore, you must export them using the Export Version Dump (tgbrg1235m000)session.

10 BAAN IV Business Organizer

1 Master Data

1 Versions

5 Export Version Dump

Run this session for all models and for all the companies you want to migrate toBAAN IVb2.

2.11 Step 11: migrate companies

Convert at least one company to each new package combination via the ChangePackage Combination by Company (ttaad1101m000) session:

2 Application Configuration

Press [→] twice, to call the Miscellaneous menu.

2 Change Package Combination by Company

This session gives a list of warnings (of the type “Warning: No DD for tcedi472found”) as result. The warnings relate to new tables (for which there is no DD inBAAN IVa(1) or BAAN IVb(1) but there is one in BAAN IVb2) and can be ignored.When in doubt, run the Check Tables session at the end of the procedure (see step 19below).

2.12 Step 12: migrate users

Migrate at least one user (preferably at least bsp) to each new package combinationvia the Change Package Combination by User (ttaad2200m000) session:

3 User Management

1 General User Data

2 Change Package Combination by User

Convert this user data to run time using the Convert user data to a run-time datadictionary (ttaad4200m000) session.

Now stop the bshell (and start it again in step 13, to activate the changes).



2.13 Step 13: import DEM models

Import DEM models using the Import Version Dump (tgbrg1245m000) session:

10 BAAN IV Business Organizer

1 Master Data

1 Versions

5 Import Version Dump

Run this session for all the version dumps that you created using step 10, and for allthe companies that you have migrated to BAAN IVb2. Be sure you perform this actionwhile in the right company.

2.14 Step 14: check bug fixes in U-VRCs

There may already be U-VRCs in the BAAN IVa(1) or BAAN IVb(1) environment. Ifso, these have to be checked. It is possible that there are bug fixes (objects) such asBAAN IVc objects in the B40U_a(1)_stnd VRCs or B40U_b(1)_stnd VRCs that arenot available in the BAAN IVb2 environment. These objects have to be copied to theB40U_b2_stnd VRCs manually.

The procedure for doing this is completely at UNIX level.

First, using the what command, check the compilation dates of the objects in theB40U_a(1)_stnd VRCs or B40U_b(1)_stnd VRCs.

Then, using explode6.1, check in which VRC of the new package combination theseobjects are.

The explode6.1 tool uses the package combination as defined in the user file of theuser (in this case bsp: $BSE/lib/user/ubsp). So, it is important to be attached to the(new) BAAN IVb2 package combination at this point.

Then check, using the what command, the compilation dates of these objects andcompare them to the dates of the objects in the B40U_a(1)_stnd VRCs orB40U_b(1)_stnd. If any objects in the B40U_a(1)_stnd VRCs or B40U_b(1)_stndVRCs are newer, then copy these to the B40U_b2_stnd VRCs.

Keep in mind that, since these objects are newer, they are therefore supposed (!) to beB40_c objects, and not B40_b(1) objects. In most cases this is also visible in the firstline of the result of the what command (which shows the directory in which thesource of the object is located on the development system). When in doubt, call theISC.

NOTE:



The following is an example of a situation in which the oacp1120 object is checked,and the object in the B40_b2 VRC turns out to be newer than the one in the B40U_bVRC (so it does not have to be copied to the new B40U_b2 VRC).

sheliak> pwd/usr5/BaanIV/bse/application/tfB40U_b_stnd/otfacpsheliak> lsoacp1110 oacp1120 oacp1133 oacp2121sheliak> what oacp1120 | head /d5/srcappl/tfB40_b/ptfacp/pacp1120g, 95/11/27 [20:23], From bsp -DREL6_1 bic_global, 05-1993/R1, Copyright (c) Baan International b.v. bic_stdlib, 09-1992/R1, Copyright (c) Baan International b.v. bic_shell, 08-1994/R1, Copyright (c) Baan International b.v. bic_fork, 07-1992/R1, Copyright (c) Baan International b.v. bic_window, 04-1992/R1, Copyright (c) Baan International b.v. bic_process, 05-1992/R1, Copyright (c) Baan International b.v. bic_menu, 04-1992/R1, Copyright (c) Baan International b.v. bic_std, 01-1993/R1, Copyright (c) Baan International b.v.sheliak> explode6.1 otfacp1120/usr5/BaanIV/bse/application/tfB40_b2/otfacp/oacp1120sheliak> what /usr5/BaanIV/bse/application/tfB40_b2/otfacp/oacp1120 | head /d7/srcappl/tfB40_b2/ptfacp/pacp1120g, 96/03/05 [16:07], From bsp -DREL6_1 bic_global 5.7:2/27/96 Copyright (c) Baan International b.v. bic_object 5.2:11/22/95 Copyright (c) Baan International b.v. bic_event, 04-1992/R1, Copyright (c) Baan International b.v. bic_shell, 08-1994/R1, Copyright (c) Baan International b.v. bic_fork 5.1:10/11/95 Copyright (c) Baan International b.v. bic_interface 5.8:2/16/96 Copyright (c) Baan Development b.v. ID 23053, Cor van Dijk, 1994-07-28, 3.0_b ID 23238, Cor van Dijk, 1994-09-22, 3.0_b

2.15 Step 15: O-VRCs–dump forms and menus

Now start the bshell again. Use the Create Run-time Data Dictionary (forms andmenus) (ttadv5214m000) session to convert the forms and menus associated with themigrated own work to runtime:


15 Run-time Data Dictionary

4 Create Run-time Data Dictionary (forms and menus)

Set the Dump field to 1 (default).



2.16 Step 16: O-VRCs–compile reports

Use the Compile Reports (ttadv3240m000) session to compile the reports associatedwith the migrated own work:


10 Reports

2 Compile Reports

Set the Compile field to 1 (default). During compilation an error report is generated.Check this report. All warnings can be ignored.

However, if there are any errors, check if the same errors occurred in the old version(by compiling the old own work via the old package combination, using the samesession). If the errors are identical in both versions, there is a problem with thecustomer’s functionality and the customer must be informed.

If there are no errors in the old environment (which is very unlikely), the problem islikely to lie in the standard software or perhaps in the customization and must besolved.

2.17 Step 17: patching

Check if there are any changes in the customer’s tools/software licenses. For thisupdate alone the key need not be adjusted. If you do have to adjust the key, follow theprocedure laid down for that situation (see work instruction Licenses).

Use the Configure Application (ttiex3225m000) session from the tools menu to patchthe software (provided the key need not be adjusted):

1 Software Installation

8 Configure Application

Fill out the fields as follows: Yes (; No;) Yes. Confirm with [Y]. When the message“Sorting...” appears, the process is running properly.

2.18 Step 18: create tables

For all company numbers migrated to BAAN IVb2, create new empty tables using theCreate Tables (ttaad4230m000) session:

6 Database Management

Press [→] twice, to call the Miscellaneous menu.

3 Create Tables

2.19 Step 19: parameters

Run the Parameters (tcmcs0295m000) session for all company numbers that weremigrated to BAAN IVb2.



2.20 Step 20: conversion from BAAN IVa(1) to BAAN IVb2

After updating from BAAN IVa(1) to BAAN IVb2, some extra actions must beperformed. When you update from BAAN IVb(1) to BAAN IVb2, the followingactions are not necessary:

n Maintain Logical Tables (ttaad4120m000). If required, the next purchase tables,tdpur040, tdpur041, tdpur045 and tdpur046, can be defined as logical tables andstored to a different company.

n Fill the new Logistic Companies by Financial Company (tfgld000) table using thesession tfgld0100m000.

Carry out the following correction objects for all companies that are migrated toBAAN IVb2:

tfcor0300m000.

Check the Only Test Run option to look for any possible problems.

Run the Convert tcmcs097 to tcmcs098 (tccov3005m000) session.

Maintain Logical Tables (ttaad4120m000). Two new tables were introduced:Customer Balances by Company (tccom011) and Supplier Balances by Company(tccom021). These new tables must be logically linked in the same way as the existingtables Customers (tccom010) and Suppliers (tccom020) are logically linked.

Run otfcor0260 and otfcor0261 for all financial companies to automatically fill theinvoice of suppliers and customers.

In addition, run the two sessions tccom2210m000 and tccom2220m000(RebuildCustomer Order Balances, Rebuild Supplier Order Balance) to automatically fill allcustomer order balances.

In some cases you must run the optional utility ttcov1999m000. This utility sets theEDI Message Generated flag on Sales and Purchase Orders.

2.21 Step 21: checking and finalizing

Make sure the scripts in $BSE/bin are restored to their old state (see the Remarkssection in the Chapter 1, Preparation). If required, check the tables using sessionttaad4232m000. Check if the session tiitm0101m000 can be accessed in a companyother than 000. If ti is not implemented or Item Control is conducted via tp, usesession tccom1101m000.

Documents

BAAN IV Staged Plan for the Update of BAAN IV to BAAN IVb2baansupport.com/docs/baan/Staged Plan for the Update of... · 2017. 12. 4. · details where they are installed, you must