Infor-ION-Event-Interoperability
05 Wednesday Sep 2012
Posted Baan ERP
in05 Wednesday Sep 2012
Posted Baan ERP
in03 Monday Sep 2012
Posted Baan ERP
inBaan Project conversion
Due to table changes for the Baan Project package for SP2 you must run a
conversion session. You must run this conversion for each company in Baan.
You are advised to execute this conversion even if you do not use Baan Project
now. Running the conversion now allows conversion to future BaanERP
releases. If you already used this conversion when installing SP2, you can skip
the the actions in this section.
Take the following steps to run the conversion:
1 Start the Create Run time Data Dictionary (ttadv5210m000) session.
Complete the fields as shown below.
2 Click Create Run Time. When the conversion is ready, click OK to
continue.
3 If you have other package combinations which you wish to use with SP3, you
must run the Create Runtime Data Dictionary (ttadv5210m000) session for
each package combination.
4 Change company to the company number for which you want to use Baan
Project. To do so choose Change Company from the Options menu.
Do not choose company number 0.
5 Start the Intitialize Rate . . . (tppdmconv_cy2) session.
6 Choose Continue. When the initialization is ready, the following message
appears.
7 If you click OK the dialog box appears once more. You must click the Close
button in the upper-right corner to close the dialog box.
8 Repeat the steps from step 3 through step 7 , using the tppdmconv_cy2
session for each company for which Baan Project data must be converted. Do
not perform these steps for company 0, because this company contains setup
data.
SLI Conversion
Due to table changes for the SLI module in the Finance package in SP3, you
must run a conversion session. You must run this conversion session for each
company you use in Baan. Even if you do not use Baan Finance you are advised
to run the conversion. Running the conversion now allows conversions to future
BaanERP releases.
Follow these steps to run the conversion.
1 Start the Create Run time Data Dictionary (ttadv5210m000) session.
Complete the fields as shown below.
Once you have just run this session for the Baan Project conversion for the
correct package combinations, you can continue with step 4 of this procedure.
Select the following check boxes:
– Domains
– Tables
– Check before create runt.
– Reconfigure Tables
Enter the Package combination, for example b50sp3.
2 Click Create Run time. When the conversion is ready click OK to continue.
3 Choose Change Company from the Options menu.Change company to the
company number for which you want to use the SLI module.
Do not choose company number 0.
4 Start the Correction Program for Sales Invoicing (cisli9000m000) session.
The following window appears.
5 Click Process. This process initialize the new table fields
– cisli100.dtxd (Date for Sales Invoice Tax)
– cisli205.txdt (Tax Date)
The cisli100.dtxd parameter field is set to invoice date.
The cisli205.txdt field is the date that is used to determine the tax period in
during the posting process. This field receives the same value as the field
cisli205.idat (Invoice Date). After the conversion the package SLI will run as
before, but now you can define the sales invoice tax date as one of the following
dates:
n Invoice date
n Order date
n Delivery date
After choosing one of these options, the field cisli205.txdt will be filled with the
correct date and tax will be calculated according to this setting.
Help
The Windows Help files are linked to a Help group. This help group is associated
with a package combination. You must install new Help files when the package
combination changes, even if there is no new Help information.
n From the BaanERP Tools menu, choose Software InstallationÐ
Installation. Open the Download Help Files (ttadv8245m000) session. This
session has two options:
– Download Help Files
This command installs the Windows Help files on your client. Select the
packages for which you want to see Help and choose Download Help
Files from the Specific menu.
– Edit HTML Help Transfer Script
When you install HTML help on an HTTP server, you must edit the
HTML Help transfer script. This script is used for transferring the HTML
Help files from the application server to the HTTP server. To execute this
script, you need access to the HTTP server.
Installing Detailed Service Requirement
Planning (DSRP)
Before you can use the Installing Detailed SRP (tssoc2266m000) session to
install both Baan Automation Server and Detailed SRP, you must first unzip
these files in their own directories:
n $BSE/c_plus/ts/ba/BAServer.zip
n $BSE/c_plus/ts/srp/SRP.zip
03 Monday Sep 2012
Posted Baan ERP
inCreate package VRC
Please note that the following procedure to create a package VRC, does not cover
all possible details and issues. Screens in the instructions may look different due
to your current setup. For example, you may or may not have installed a previous
service pack.
If you have already created a VRC for a previous service pack, creating a new
package VRC is not mandatory. If you have not created a package VRC for the
service pack you must follow the steps described below. On a UNIX server, you
must execute these steps as user bsp.
Follow these steps to create a package VRC for a service pack.
1 Use the browser to navigate to the Baan Tools.
2 Start the Package Combinations (ttaad1520m000) session.
3 Insert a package combination. You are free to choose a name, for example
b50bU, description: BaanERP_B50b Service Packs and Table Definition Path
: ${BSE}dict.
The Windows Help files are linked to a Help group. This Help group is
associated with a package combination. You must install new Help files when
the package combination changes, even if there is no new Help information.
See the installation manual on how to install new Help files.
4 When asked if you want to create the ${BSE}dict/ddb50bU directory, click
Yes and exit by clicking Close. (the directory name is an example).
5 Use the Package VRCs (ttadv1511m000) session to check the VRC structure.
6 Start the Package by Package Combination (ttaad1121m000) session. From
the Group menu, choose Duplicate.
7 Select the first record to be copied, then select the last record to be copied.
8 Enter the name of the new package combination.
9 Change the values of the columns Version, Control, and Release for each
package as shown in the Package by Package Combination dialog box.
Choose Save from the File menu to save the changes.
10 From the Specific menu, choose Rebuild DD (Data Dictionary).
11 Start the Change Package Combination by Company (ttaad1101m000)
session.
12 Complete the fields as displayed above and select all companies, for example,
from 000 to 820.
13 Click Change.
14 Start the Change Package Combinations for Users (ttaad2200m000) session.
15 Click Change.
16 Click Close. The package VRC has now been set up correctly.
17 Run the Create Tables (ttaad4230m000) session and supply the following
information (be sure that you are in the right package combination, for
example b50bU)
Company: From 000 to 900 (for example)
Package : From to zz
Table : From to zzz999
After a while the message xxx Tables Created appears. Click OK.
03 Monday Sep 2012
Posted Baan ERP
inTo install the service pack on NT
Follow these steps to complete an NT service pack update:
1 For NT insert the service pack CD-ROM. The installation program starts
automatically. The following dialog box appears:
2 Click Next. The following dialog box appears:
3 If you accept the terms, click Yes. The Select environment dialog box
appears.
5 Select the components you wish to update. You must select the application
components. Selecting the porting set components is optional but highly
recommended. Click Next.
6 The Update Type dialog box appears:
7 Select Full Update (recommended). Click Next. The Update configurations
dialog box appears:
8 Select BaanERP B50b. Click Next. The Setup Information dialog box
appears.
9 Click Next to continue or select Back to review your settings.
10 Now the setup process starts copying files. If a read-only file is detected, you
are requested to overwrite it by clicking Yes or otherwise to click No.
11 The following dialog box appears.
12 Now BaanERP is ready for the Baan user logon. Type the password and
select Connect to start BaanERP. The following message appears:
Patch your software
13 Run the Patch Objects After Error Solving (ttiex3226m000) session and
supply the following information:
Package: tt
Objects : from:
to : zzzzz
After the patch process is ready, the message Patch your Software will not appear
again when you start the BaanERP software.
03 Monday Sep 2012
Posted Baan ERP
in5 To install the Service Pack
The installation manuals are available as PDF files on the documentation CDROM
that is part of the service pack for BaanERP.
The UNIX-based installation guides are:
U7071B US INFORMIX Installation Guide for BaanERP on UNIX
U7074B US ORACLE Installation Guide for BaanERP on UNIX
U7079B US DB2/6000 Installation Guide for BaanERP on UNIX
U7081B US SYBASE Installation Guide for BaanERP on UNIX
For Microsoft BackOffice, the installation guides are:
U7077B US Microsoft SQL Server Installation Guide for BaanERP on
Windows NT
U7075B US ORACLE Installation Guide for BaanERP on Windows NT
U7072B US INFORMIX Installation Guide for BaanERP on Windows NT
Open the Welcome.htm file (in the root directory of the documentation CDROM)
by using your Web browser to view a complete list of the BaanERP
documentation.
For a UNIX update read the instructions in this sequence of sections:
n Unix update
n Create Package VRC (optional)
n Baan Project Conversion
n SLI conversion
n Installing Detailed SRP
For an NT update read the instructions in this sequence of sections:
n NT update
n Create Package VRC
n Baan Project Conversion
n SLI conversion
n Installing Detailed SRP
5 To install the Service Pack
To install the Service Pack
Release Notes Service Pack 3
5-2
UNIX update
For all UNIX service pack updates, you must carry out the following steps.
Before you start to update, please note the following:
n BaanERP5.0b cannot be updated with this service pack at run time. You must
log on as Root and use the rc.stop command in /bse/etc to stop the BaanERP
environment for the service pack update.
n You can use the normal installation guides that are listed earlier to install the
service pack. Because some components are already available on your
system, the installation process will skip certain steps that are described in the
installation manual for the initial installation. You can follow the steps
described in the section “Installing the software” later in this chapter. For
your convenience steps 1 through to step 7 are described.
Take the following steps to install the Baan software.
1 Log on as user root (do not use the su command) and set the TERM variable
to vt100 or any other valid value.
2 Change directories to the directory in which the Baan files were read by the
mas.read6.2 script and enter the following command:
# sh install6.2
The selection phase of the installation script (that is, before the last question
Are you ready for installation? is asked) can be stopped at any time by
pressing an interrupt, for instance, CTRL+C. The script can be restarted as
often as desired. From the script, a subshell can be activated by pressing
EXCLAMATION POINT. To end this subshell, type exit at the UNIX prompt.
You then will return to the script at the point where you left.
Never use the tee command to create a log file. The installation script will
start the bshell and if the tee command has been used, a bshell window will
not appear on the screen. During the installation, the log.install6.2 log file is
generated in the directory where the installation was started.
3 After a temporary bse environment is created, you are asked to supply the
path to the already installed BSE (Baan Software Environment) directory. Be
sure to enter the complete path.
4 The default value $BSE/tmp is suggested for the BSE_TMP environment
variable. Accept the default by pressing ENTER. Press ENTER to continue.
5 The process may ask if you want to write the values of the $BSE-related
variables to the systemwide profile /etc/profile. You should not write them to
the systemwide profile, so press ENTER to accept the default answer NO.
NOTE
CAUTION
To install the Service Pack
Release Notes Service Pack 3
5-3
6 The process may ask if you want to write the $BSE variables to the profiles
of the users. If you do not wish to write the variables to the .profile files of
the individual users, press ENTER to accept the default answer NO. Press
ENTER to continue.
7 The process may ask to enter the hostnames of the systems for which a
license is required. The installation procedure displays the name of the local
system as default. Supply the hostname(s) and press ENTER. Then press
ENTER to continue.
The following message appears:
THIS IS AN UPDATE
Do you want to reinstall old components too?
8 Type Yes and press ENTER. A warning appears that all processes that use
shared memory must be removed. If you have not done so, stop these
processes.
9 Type Yes and press ENTER. The following message appears:
Are you ready for installation?
10 Type Yes and press ENTER. An error message Check Fixes may be displayed
indicating that the preinstallation tool preinst encountered errors. If so, you
must check the displayed log.preinst file. Press ENTER to continue.
11 Now the installation process is started. Skip the steps in the installation
manual up to the step where you must install either BI or BW. Continue
following the steps from that point onward.
In case you have installed this service pack before, the installation process
may skip steps that were already performed during the first service pack
installation.
12 After you install the service pack, you must create a package VRC named, for
example, b50bU. To do so, see the section “Create Package VRC” in this
chapter.
13 Due to table changes for the Baan Project package you must run a conversion
session. To do so, see the “Baan Project conversion” section in this chapter. If
you have already run this conversion when you installed SP2, you can skip
this action.
14 Due to table changes for the Baan SLI module you must run a conversion
session. To do so, see the “SLI conversion” section in this chapter.
Even if you do not use Baan Project, or the SLI module, you must run this
conversion to avoid future conversion problems.
NOTE
NOTE
To install the Service Pack
Release Notes Service Pack 3
5-4
NT update
This section describes the installation of the BaanERP5.0b Service Pack 3 for
NT.
To prepare for installation
Follow these steps to prepare for the service pack installation on NT.
1 Before you start the service pack update, you must stop all Baan bshells on
your server. If you have multiple Baan environments on your server, you
must also stop the bshells for the Baan environments which you will not be
updating. You can use the task manger to check if all Baan bshells were
stopped.
2 Do not install the service pack from a mounted CD-ROM drive. The use of a
mounted CD-ROM drive causes NT related authorization problems when you
install the service pack. Always use the CD-ROM drive of the NT server
itself.
3 Before you perform a Service Pack 3 update on an NT system on which
Service pack 1 was not yet installed for a Dutch-language version, you must
remove the files install.info, restart.1288, and installed.dmp in the directory
$BSElibinstall from the BAAN environment. If these files do not exist, no
action needs to be taken. For other languages, removing these files is not
required.
03 Monday Sep 2012
Posted Baan ERP
in4 Solved calls, known defects, and
Limitations
A large number of calls were solved in service pack 3. On the Documentation
CD-ROM for this service pack you can find a Microsoft Word file that contains a
description of all solved calls. This file is named Solved_calls3.doc.
Service pack 3 is an incremental service pack. It also contains the solved calls of
service pack 1 and service pack 2. On the Documentation CD-ROM you can find
a Microsoft Word files that contains a description of all solved calls in service
pack 1. (Solved_calls.doc) and service pack 2 (Solved_calls2.doc).
Tinoway integration
The Tinoway integration of BaanService Remote (version 2.00.000.4
SP1through SP4) does not work with BaanERP5.0b SP2. Tinoway has developed
a new version BaanService Remote 2.1.3 that solved the defect. This solution is
validated for service pack 3 and service pack 2 for BaanERP5.0b.
Defect and solution outbound advice
The Service Pack 3 for BaanERP5.0b contains a defect that is discussed below.
Description of the defect
Assume the following:
n You have a production order.
n In the Bill of Material for the end-item, a material exists with backflushing
switched on.
You issue this material (for example, 50 pieces) for your production order in the
Material to Issue for Production Order (ticst0101m000) session. The Direct
Process Outbound check box is selected. Your warehouse does not hold
sufficient inventory of this material (for example, 30 pieces).
In such a case, the outbound order line in the Outbound Order Lines
(whinh2520m000) session must be split into two lines:
n 30 pieces, status shipped
n 20 pieces, status open
4 Solved calls, known defects, and
limitations
Solved calls, known defects, and limitations
Release Notes Service Pack 3
4-2
However, BaanERP creates three lines:
n 30 pieces, status shipped
n 20 pieces, status open
n 20 pieces, status open.
The creation of the last line is not correct; it should not have been created.
This defect can cause the following problem. If a customer generates and
releases the outbound advice and ships the goods in a batch process (while new
material is arrived in the warehouse), both lines will get the status shipped. In the
Material to Issue for Production Order (ticst0101m000) session, the To issue by
warehousing field will have the value –20, whereas no inbound line is available
with a value of + 20. Because this field should have the value 0, you cannot
close the production order.
Solution of the defect
This problem will be solved in Service Pack 4 for BaanERP5.0b. The Scopus
defect number for this problem is 7784; the solution number that belongs to this
defect is 18835.
An FTP-path is availabe:
If your Current VRC is:
B50_b:
ftp://www.support.baan.com/updates/B50b/18835std.dmp
To keep the dump compatible, more solutions than necessary to solve this
particular defect are available in the dump.
See the Scopus system for additional information.
Solution Defect
18722 75581
18815 75616
18754 76198
18753 76194
03 Monday Sep 2012
Posted Baan ERP
in3 Functional enhancements SP1
Service pack 3 is an incremental service pack. It contains the functional
enhancements of the service packs 1 and 2. The service pack 1 enhancements
are described in this chapter.
Linking order types to transaction types’
In SLI you could not immediately link an order type to a transaction type. This is
still not possible, but with the new functionality you can store billing request
settings that can be reused next time. You can achieve reuse by linking billing
request to billing request sets. You can run the compose/print/post session by
billing request or by billing request set. When you choose the billing request set,
the system copies all billing requests attached to that set to new billing requests
and changes only the cut-off date. This process enables you to establish the link
between, for example, order types and transaction types.
Currency Selection for COGS (Cost of goods
sold)
The distribution package delivers the amount in local home currency. The central
invoicing package however expected the amount to be in reference currency. In
the end the COGS was posted with the reference currency as transaction currency
but with an amount that corresponds with the amount in local home currency.
With the new service pack this problem is solved. The COGS is posted in
reference currency.
Bank format CLIEOP03
The CLIEOP payment method is a Dutch payment method. This payment
method allows companies to send their payment transactions in CLIEOP files to
Dutch banks. These files are in plain ASCII format with a fixed record layout.
The files are processed at the banks to which they are sent. Because of the
introduction of the euro, a new record layout is developed for these CLIEOP
files. This new format is called CLIEOP03 and allows companies to pay in euros
as well as in Dutch guilders.
3 Functional enhancements SP1
Functional enhancements SP1
Release Notes Service Pack 3
3-2
Warning regarding the Currency Rates
(tcmcs0108m000) session
A new parameter, Express in base currency, is introduced in this session. This
parameter can be set each time a currency rate is entered, and it allows the user to
express a currency rate in the base currency as well as in the other currency.
The parameter is introduced because the euro legislation states that the currency
rate between the euro and each participating EMU currency must be expressed in
the participating EMU currency., for example, 1 euro = 2.16 Dutch guilders.
If a new currency rate is entered with an opposite value of the Express in base
currency parameter compared to already existing currency rates, data
inconsistency can occur. This is the case when the effective date of the new
currency rate lies between the effective date of the already existing currency rates
and the currency rate date of already existing documents that make use of the
already existing currency rates.
03 Monday Sep 2012
Posted Baan ERP
inSLI sales invoice taxation
Description of the enhancement
In various countries you must calculate tax based on the delivery date on the
delivery date of the shipped goods. So far the BaanERP5.0b SLI module did not
provide this feature; the tax year and the tax period were always based on the
invoice date. Using the enhancement for Sales invoices tax periods the user can
choose the tax date from:
n Invoice date
n Order date
n Delivery date
This new functionality solves Scopus defect number 75011. The solution number
is 17903.
New or changed software components
Table fields were added to the tables cisli100 and cisli205.
The following scripts were changed:
n cisli210
n cisli225
n cisli235
n cisli245
n cisli255
n cisli265
n cisli.dll2080
n cisli.dll2001
n cisli.dll3001
This form was changed:
n cisli1199s0002
Customer implications/benefits
Is the enhancement new?
Yes, but the previous functionality is still available.
What does the enhancement replace?
It extends the existing functionality.
Functional enhancements SP3
Release Notes Service Pack 3
1-9
Can you still use the previous software?
No, after installing SP3 you must run the conversion program for SLI that is
described in Chapter 5, SLI Conversion.
Do you have to start using the enhancement now?
Yes, but after installing the service pack 3 and running the conversion program,
as default, the software will work as it did before. The (key-)user can decide
when to use the new features. The conversion program is described in Chapter 5,
“SLI conversion.”
Can you start using the enhancement later?
No. After installing service pack 3 you must run the conversion program. The
conversion program takes care of setting the parameter(s) in such a way that you
can use the software as you did before.
What must be done to use the enhancement?
1 You must install the service pack 3 as described in Chapter 5.
2 Run the SLI conversion as described in Chapter 5, “SLI Conversion” in these
release notes.
3 You can select the appropriate Date for Sales Order Tax Determination in the
SLI Parameter (cisli1100s000) session.
4 Start the Compose/Print/Post Invoices (cisli2200m000) session to compose,
print, or post the invoice lines.
Functional enhancements SP3
Release Notes Service Pack 3
1-10
Release Notes Service Pack 3
2-1
Service pack 3 is an incremental service pack, which also includes the
enhancements of service pack 2. This chapter describes the functional
enhancements of the Service Pack 2 for BaanERP5.0b.
The following functional enhancements were included in service pack 2. Each of
the enhancements are described in the following sections in this chapter:
n Integration transactions (Warehousing/Finance)
n DTAUS99 format (Finance)
n Central Mapping scheme (multisite/multifinance)
n Integration Options (multisite/multifinance)
n Deferred emergency service orders (Service)
n Emergency call handling (Service)
n Help desk monitoring (Service)
n Service pack version check
Service pack 2 enables BaanERP for AS/400 (porting). This enhancement is not
described.
Integration transactions
(Warehousing/Finance)
The integration transactions in the Finance package are posted by using the local
currency instead of using the reference currency.
Changed components:
n whinhdll1000
n tfglddll4010
n cislidll2045
n cislidll2055
n cislidll3005
n cislidll3006
2 Functional enhancements SP2
Functional enhancements SP2
Release Notes Service Pack 3
2-2
Service
Changed components to support the new BaanService Remote.
Tables
n tssoc000
n (Newly created. Not present in previous version)
Scripts
n tssoc200
n tssoc2100
n tssoc205
n tssoc210
n tssoc220
n tssoc240
n tssoc250
n tsintdlltino
Forms
n tssoc0100s0003
Session
n Time Stamping for BSR (tsmdm1580m000) It was newly created. Not
present in previous version.
DTAUS99 format
Description of the enhancement
This enhancement allows you to use the new DTAUS99 bank file in the Create
German Bank Order for Diskette (tfcmg1261m000) session and the Create
German Bank Order (Debit) for Diskette (tfcmg4261s000) session.
The format was changed to support payments or receipts in either German Marks
or euros.
New or changed software components
n Create German Bank Order for Diskette (tfcmg1261m000) session.
n Create German Bank Order (Debit) for Diskette (tfcmg4261s000) session.
Functional enhancements SP2
Release Notes Service Pack 3
2-3
Customer implications/benefits
Is the enhancement new?
Yes.
What does the enhancement replace?
It replaces the former bank file created in the previously mentioned sessions.
Can you still use the previous software?
No, the previous bank file is no longer available.
Do you have to start using the enhancement now?
Yes, you have to start using it now.
Can you start using the enhancement later?
No, because the previous option is no longer available it cannot be used.
What must be done to use the enhancement?
Nothing extra has to be done. When a payment method is created that uses one of
the previously mentioned sessions, the new format will be used instead of the old
format.
Central mapping scheme
Description of the enhancement
Having a logistic company is not mandatory anymore in the central mapping
scheme. When you leave it empty, it is used as the base setup in the ledger A/C
mapping for all logistic companies. The integration mapping company
functionality is removed from the Logistic Companies by Financial Companies
(tfgld0100m000) session.
This enhancement solved Scopus defect number 73321. It contains Scopus
solution 16764.
Functional enhancements SP2
Release Notes Service Pack 3
2-4
New or changed software components
There are no new software components.
The following sessions were changed:
n Logistic Companies by Financial Company (tfgld0100m000)
n Post Integration Transactions to Finance Transactions (tfgld4201m000)
n Integration Mapping Scheme (General) (tfgld4500m000)
n Central Mapping Scheme – Detail (tfgld4100s000)
n Integration Mapping Scheme (Manufacturing/Distribution – Overview)
(tfgld4501m000)
n Integration Mapping Scheme (Manufacturing/Distribution ) (tfgld4101s000)
n Integration Mapping Scheme (Project ) (tfgld4502m000)
n Integration Mapping Scheme (Project ) (tfgld4102s000)
n Integration Mapping Scheme (Service ) (tfgld4503m000)
n Integration Mapping Scheme (Service ) (tfgld4103s000)
n Integration Mapping Scheme (Commissions/Rebates ) (tfgld4504m000)
n Integration Mapping Scheme (Commissions/Rebates) (tfgld4104s000)
Customer implications/benefits
In the old situation for all logistic companies in an enterprise, a central mapping
scheme had to be defined. For customers who use a large number of logistic
companies, a central mapping scheme was not feasible. With the current
enhancement, you only need to setup a central mapping scheme once and leave
the Logistic Company field empty. It will be used as a base setup for all logistic
companies. Logistic companies that require a specific mapping onto Finance can
be maintained only for this specific logistic company.
For customers, that already run BaanERP this has no consequences, because it is
easier to share one central mapping scheme across logistic companies. Because
this is an optional enhancement, customers are not forced to change their current
setup.
Functional enhancements SP2
Release Notes Service Pack 3
2-5
Customers that run with service pack 1 (or higher) of BaanERP5.0b are now able
to work with the Integration Mapping Company field in the Logistic
Companies by Financial Company (tfgld0100m000) session. This field was
removed, because it cannot work for all multisite scenearios.
What must be done to use the enhancement?
Customers may need to reconsider the central mapping scheme setup and find
out whether a standard mapping scheme setup can be used, and when they need
to set up a specific scheme for one logistic company.
Are other components influenced?
No
Integration options
Description of the enhancement
When you define options by integration element, you can now define a logistic
company to which the logistic data in the session will refer. You can also leave
this field blank and define a blank setup. Especially in multifinance /
multilogistic company setups, the logistic data had to be shared because database
references and zoom session could not be established otherwise. Now, only when
the Logistic Company field is left blank, we expect your data not be shared.
This enhancement solves Scopus defect number73315. It includes Scopus
solution 16763.
New or changed software components
There are no new software components.
The following components were changed:
Table defintions
n tfgld421
n tfgld422
n tfgld423
n tfgld424
n tfgld425
Functional enhancements SP2
Release Notes Service Pack 3
2-6
Forms
n tfgld4121m0001
n tfgld4122s0000
n tfgld4122s0001
n tfgld4122s0002
n tfgld4123s0000
n tfgld4123s0001
n tfgld4123s0002
n tfgld4123s0005
n tfgld4124s0000
n tfgld4124s0001
n tfgld4124s0002
n tfgld4124s0003
n tfgld4124s0004
n tfgld4124s0005
n tfgld4124s0006
n tfgld4124s0007
n tfgld4124s0008
n tfgld4125s0000
n tfgld4125s0001
n tfgld4125s0002
n tfgld4125s0003
n tfgld4125s0004
n tfgld4125s0005
n tfgld4125s0006
n tfgld4125s0007
n tfgld4125s0008
n tfgld4421m0000
n tfgld4422m0000
Reports
n tfgld442111000
n tfgld442112000
n tfgld442211000
Libraries
n tfgld.dll4000
n tfgld.dll4016
n tfacp.dll0015
Functional enhancements SP2
Release Notes Service Pack 3
2-7
Scripts
n tfgld4121
n tfgld4122
n tfgld4123
n tfgld4124
n tfgld4125
n tfgld4201
n tfgld4421
n tfgld4422
Customer implications/benefits
You can specify integration option relations by logistic company. The logistic
entities of a specific logistic company can now be used for reading
references/establishing zoom sessions and you do not need to share your data.
Only in situations where you always use the same logistic company/financial
company relationship do you need to share tables.
The Logistic Company field is optional. When the field is left blank, the setup is
used as a sort of base setup. When a dimension cannot be found based on logistic
company search, the blank setup will be used.
What must be done to use the enhancement?
When there is a current setup, the customer does not have to create a specific
new setup. Programs that use the Integration Option setup will always determine
the correct setup. If you have problems with the current solution you should
reconsider your setup. If a logistical company does not necessarily use only a
single financial company, and, therefore, you can have many-to many company
relationships, you can use the enhancement immediately to solve your current
reference problems.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-8
Deferred emergency service orders
Description of the enhancement
By using this enhancement, you can mark a service order as emergency, skip the
planning, and release the order to a field engineer. All the released service orders
that are either emergency/created by emergency calls, and that are not responded
to within the given time, are displayed as deferred emergency service orders.
Because these service orders are auto-refreshed, the dispatcher can easily view
orders that have not been responded to.
New or changed software components
Modules
n Service Order Control (SOC)
Sessions
n Service Orders (tssoc2100s000)
n Deferred Emergency Service Orders (tssoc2502m000)
Tables
Tssoc000 (SOC Parameters)
Sno Field Description
1 Oect A provision is provided to indicate the order escalation time on
which the deferred orders will be identified. The time duration
unit is calculated from the MDM (Master Data Management)
Parameters
Tssoc200 (Service Orders )
Sno Field Description
1 Emer Determines whether the service order is emergency or not.
2 Orrt Order release time keeps track of the date on which the service
order is handled to the field engineer.
3 Ract The reaction time is used to keep track of the last changes that
are made to the service order after it is released.
4 Ltdt Last transaction date keeps track of changes with Tinoway.
Functional enhancements SP2
Release Notes Service Pack 3
2-9
Customer implications/benefits
Is the enhancement new?
Yes.
What does the enhancement replace?
It does not replace any of the existing functionality.
Can you still use the previous software?
Yes. There is no problem in skipping this enhancement.
Do you have to start using the enhancement now?
It is not mandatory.
Can you start using the enhancement later?
Yes.
What must be done to use the enhancement?
Conversion of data is not required.
Take the following steps to use the enhancement.
1 Maintain order escalation time in SOC parameters.
2 Get the details of the service orders that are set to emergency and released.
3 Check if the release time plus the order escalation time is greater than the
current time.
4 If the check in step 3 is answered with Yes, the order is considered a deferred
escalation service order.
Is there a change of business processes?
Not applicable.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-10
Emergency call handling
Description of the enhancement
The call center receives a call from the customer who requests an immediate
service from a service engineer. The call center registers the call as an
emergency, assigns the call to a service engineer, and transfers the call to Service
Order Control, which creates a service order with status released. This Service
order is readily available to the service engineer, who can respond to the
customer quickly.
You can now automatically transfer the calls to a service order. If a deferred call
is for a configuration that is covered under a contract or a warranty, the system
automatically transfers the call to a released service order, to make it available to
the field engineer as soon as possible. A new session is provided for this
enhancement, which can be maintained as a repetitive job for performing the
automatic transfer.
New or changed software components
Modules
n Call Management (CLM)
n Service Order Control (SOC)
Sessions
n Calls (tsclm1100s000)
n Escalated / Deferred Calls (tsclm1520m0000)
n Print Calls (tsclm1400m000)
n Call History (tsclm8510s000)
n Calls (tsclm8520m000)
n Call Processing (tsclm1118s000)
n Automatic transfer of Deferred Calls (tsclm1250m000)
n Service Orders (tssoc2500m000)
Functional enhancements SP2
Release Notes Service Pack 3
2-11
Tables
Tsclm100 (Calls)
Sno Field Description
1 Emer A provision is provided in the call to indicate whether the call is
an emergency or not.
2 Oemn Whenever the call taker records the call as an emergency, the
first preferred engineer maintained for the configuration
(tscfg220) should be assigned by default. If the first preferred
engineer is not present, the second preferred engineer should be
assigned by default. If the second preferred engineer is not
present, then the call handler should fill, the service engineer
manually
3 Minu The call handler can mention the page frequency in the call
header. In other words, how many times to page the service
engineer.
Tsclm810 (Call history)
As the data maintained in tsclm100 is also maintained in history, all the fields
(emergency (y/n) , service engineer, and page frequency) will also be replicated
in call history.
Tssoc200 (Service Orders)
Sno Field Description
1 Minu Page frequency for the service engineer
Customer implications/benefits
Is the enhancement new?
It is an enhancement to the existing functionality. In BaanERP5.0b, the call
center can create a call and transfer it to Service Order Control (SOC) where the
order is planned and released to an appropriate service engineer. The new
functionality enables the user to directly create a service order by skipping the
planning part (Detailed Service Requirements Planning and Global Service
Requirements Planning) and automatically transferring calls to service orders.
What does the enhancement replace?
It does not replace any of the existing functionalities.
Can you still use the previous software?
Yes. There is no problem in skipping this enhancement.
Functional enhancements SP2
Release Notes Service Pack 3
2-12
Do you have to start using the enhancement now?
No, it is not mandatory.
Can you start using the enhancement later?
Yes.
What must be done to use the enhancement?
Conversion of data is not required.
Take the following steps to use the new functionality:
1 Mark the call as an emergency.
2 Get the default service engineer from the configuration (either preferred
engineer 1 or preferred engineer 2) of the business partner.
3 If required, check the availability of the engineer based on the calendar linked
to this engineer.
4 Transfer the call to Service Order Control.
5 View the details of the released service order.
Change Business Processes?
Not applicable.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-13
Help desk monitoring
Description of the enhancement
Use this enhancement to view calls that have not been responded to within a
given time after they are registered or assigned . Based on these details, the
Dispatcher can take appropriate action. Auto-refresh updates the call details,
which allow the Dispatcher to view the current deferred calls.
New or changed software components
Modules
Call Management (CLM)
Sessions
n Escalated/Deferred Calls (tsclm1520m0000)
n Call Parameters (tsclm0100s000)
Tables
Tsclm000( Call Parameters)
Sno Field Description
1 Dftm A provision is provided to indicate the deferred call time fence
based on which the deferred calls will be identified. The time
duration unit is taken from the Master Data Management
(MDM) parameters.
Tsclm100 (Calls)
Customer implications/benefits
Is the enhancement new?
It is an enhancement to the existing functionality. In BaanERP5.0b, the user can
view all calls that were escalated based on the priority of the call. The user is
now provided with the following options to view:
n Escalated Calls
n Deferred Calls
n All calls (Escalated and Deferred )
n Deferred Emergency Service Orders
What does the enhancement replace?
It does not replace any of the existing functionality.
Functional enhancements SP2
Release Notes Service Pack 3
2-14
Can you still use the previous software?
Yes. There is no problem in skipping this enhancement.
Do you have to start using the enhancement now?
It is not mandatory.
Can you start using the enhancement later?
Yes.
What must be done to use the enhancement?
Conversion of data is not required.
Take the following steps to use the enhancement;
1 Define the time fence in CLM Parameters. The time duration unit is taken
from the MDM parameters.
2 Check the status of the call.
3 If it is registered, check if the reported time plus the deferred call time fence
is greater than the current time. If yes, display the call as a deferred call.
4 If assigned, check if the assessment time plus the deferred call time fence is
greater than the current time. If yes, display the call as a deferred call.
5 The user can also view the deferred emergency service orders.
Change Business Processes?
Not applicable.
Are other components influenced?
No.
Functional enhancements SP2
Release Notes Service Pack 3
2-15
Paging support
Description of the enhancement
By using this enhancement, the field engineer can be paged whenever an
immediate service is required for an emergency service order.
New or changed software components
Modules
n Master Data Management (MDM)
n Call Management (CLM)
n Service Order Control (SOC)
Sessions
None
Tables
Tsmdm170
Sno Field Description
1 Page Page code
2 Emno Employee to whom the page code belongs
3 Ppno Employee to whom the page code belongs
4 Pager pin code Pager pin code
5 Pager type Type of pager, numeric or alphanumeric
6 Pena Pager enabled (y/n)
7 Page provider Code of the page provider
Tssoc200
Sno Field Description
1 PaMinuge Page frequency
Tsclm100
Sno Field Description
1 Minu Page frequency
Functional enhancements SP2
Release Notes Service Pack 3
2-16
Tscfg220
Sno Field Description
1 Page Page Allowed
Customer implications/benefits
Is the enhancement new?
Yes.
What does the enhancement replace?
It does not replace any of the existing functionality.
Can you still use the previous software?
Yes. There is no problem in skipping this enhancement.
Do you have to start using the enhancement now?
It is not mandatory.
Can you start using the enhancement later?
Yes.
What must be done to use the enhancement?
Conversion of data is not required.
Take the following steps to use the new functionality:
1 Maintain page information for the required field engineers.
2 Indicate whether pager is allowed for the configuration on site.
3 Indicate the page frequency for the call / service order.
4 Release the service order to the field engineer concerned. Based on the
paging information, the field engineer will be paged.
Change Business Processes
Not applicable.
Are other components influenced?
Tinoway’s BaanService Remote software is influenced by this enhancement. It
can access the paging information provided by Baan and proceed using the
paging functionality. See the section Tinoway integration in Chapter 4.
Functional enhancements SP2
Release Notes Service Pack 3
2-17
Service pack version check
In service pack 2 a feature is added which allows you to see which service pack
is active in your current environment. To check the service pack version you
must use the tccomspinfo (ttdsk2080m000) session. Take the following steps to
check the service pack version:
1 Select File/Run Program in your menu browser. The Run Program
(ttdsk2080m000) session appears.
2 Type tccomspinfo in the Program/Session field.
3 Choose OK. The service pack information will be displayed.
03 Monday Sep 2012
Posted Baan ERP
in1 Functional enhancements SP3
This chapter describes the functional enhancements of the Service Pack 3 for
BaanERP5.0b. The following functional enhancements are described.
n Tolerances for automatic matching purchase invoices in Baan Finance
n Euro External Translation
n Uptime calculation in Baan Service
n Product Configurator (PCF) as a beta version
n SLI sales invoice taxation
Tolerances for automatic matching
Description of the enhancement
The enhancement allows you to use tolerances for automatic matching purchase
invoices in Baan Finance. You can use the Automatic Matching Tolerances by
IFBP (invoice-from-business-partner) (tfacp0107m000) session for this purpose.
If the tolerances are not set within this session, the automatic matching procedure
will use the new default parameters from the ACP parameters (tfacp0100s000)
session.
If there is a difference between matched amount and net invoice amount minus
costs, the system checks whether this difference is within the tolerances set for
the invoice-from-business-partner.
If the difference is within the tolerances, this is regarded as a price difference.
The difference will then be booked to the Matched Purchase Invoice Transaction
(tfacp101) table by using the price difference ledger account and dimensions
taken from the financial business partner group of which the Invoice from
Business Partner is part. If the difference is outside the tolerances, matching does
not take place.
This enhancement solves Scopus defect 74260. The Scopus solution number is
18131.
1 Functional enhancements SP3
Functional enhancements SP3
Release Notes Service Pack 3
1-2
New or changed software components
Sessions:
n ACP Parameters (tfacp0100s000) session
n Automatic Matching Tolerances by IFBP (tfacp0107m000) session
n Print tolerances per IFBP for automatic matching (tfacp0407m000) session
The manual match (tfacp2541m000) session has changed substantially regarding the
query extend which is now dramatically faster.
New table:
The acp parameters table (tfacp000) and the Tolerances for automatic match
(tfacp007) both have the same four new fields:
Field Description
ifbp Invoice from business partner
lppd Percentage matched amount lower than invoice amount
hppd Percentage matched amount higher than invoice amount
lapd Matched amount lower than invoice amount
hapd Matched amount higher than invoice amount
DLL:
The automatic match dll (tfacpdll2405) was slightly changed. The DLL now
checks if there is no difference between the total matched amount and the total
net invoice amount.
Customer implications/benefits
Is the enhancement new?
Yes, this is a new feature.
What does the enhancement replace?
It adds new functionality.
Can you still use the previous software?
No. The related program scripts have changed.
Do you have to start using the enhancement now?
Yes, it is used whenever the automatic match functionality is started.
Functional enhancements SP3
Release Notes Service Pack 3
1-3
Can you start using the enhancement later?
Yes, if you do not set tolerances in either the ACP Parameters (tfacp0100s000)
session or the Automatic Matching Tolerances by IFBP (tfacp0107m000)
session, automatic match works as before.
What must be done to use the enhancement?
Set tolerances in the sessions Automatic Matching Tolerances by IFBP
(tfacp0107m000) or use the new default parameters from in the ACP Parameters
(tfacp0100s000) session. The enhancement works whenever automatic matching
is started.
If the tolerances are not set within this session, the automatic matching procedure
will use the new default parameters from the session.
Euro External Translation
Description of the enhancement
This enhancement allows you to:
n Display in the euro currency , Invoice amounts and the Invoice Balance
amounts that are registered in an EMU currency.
n Print in the euro currency, reports related to Open Invoices for the invoices
that are expressed in an EMU currency. You can still print the reports in the
original invoice currencies.
n Create in the euro currency Payment and Direct Debit Advices when the
invoices are in an EMU currency. The software will take care of using the
correct Payment Method. In order to make this work properly, a Euro Related
Payment Method must to be defined. All this makes it possible to pay
invoices using the euro currency.
n Generate Interest Invoices in euro when needed.
n Update the Cash Forecast in such a way that EMU currencies are translated
into the euro. In this way, your Cash Forecast does not show any EMU
currencies anymore. You can still update the cash forecast, without the
translation.
This enhancement solves Scopus defect number 75613. The Scopus solution
number is 18361.
Functional enhancements SP3
Release Notes Service Pack 3
1-4
New or changed software components
n Components in the Finance ACP, ACR, and CMG modules.
n In ACP and ACR sessions and reports with regards to Open Invoices are
modified.
n In ACR the generation of Interest Invoices is modified.
n In CMG the Payment and Direct Debits procedures are modified to allow
payment and direct debits in the euro.
n In CMG the Cash Forecast is modified.
Customer implications/benefits
Is the enhancement new?
Yes, it is new functionality.
What does the enhancement replace?
It does not replace any existing functionality, it adds functionality.
Can you still use the previous software?
Yes, the user can always let the programs work as they did.
Do you have to start using the enhancement now?
No, this is not necessary. Until the EMU currencies are no longer valid
currencies, it is not neccessary to use the functionality. However, in order to get
used to the euro, it is likely that the functionality will be used in an earlier stage.
Can you start using the enhancement later?
Yes, until the EMU currencies are obsolete, because the system still contains
invoices in EMU currencies.
What must be done to use the enhancement?
In order to let the system automatically select the correct Payment Method, for
each Payment Method that does not allow to use Foreign Currencies, and for
which the Payment Method currency is set to an EMU currency, a so called Euro
Related Payment Method must be created. This is in most cases a copy of the
original Payment Method, however, the currency must be the euro currency and
probably some other report(s) have to be chosen.
Further, in order to update the Cash Forecast with translating into the euro, in the
CMG Parameters (tfcmg0100s000) session, the Use Euro Instead of EMU
Currencies checkbox must be selected.
Functional enhancements SP3
Release Notes Service Pack 3
1-5
Uptime calculation
Short description of the enhancement
Service performance is analyzed with respect to the customer’s equipment being
up and available for operation as agreed in the contract.
New or changed software components
Module Contract Management
Modified Sessions
n Quotation Configuration Lines (tsctm2110s000)
n Contract Configuration Lines (tsctm3110s000)
Modified tables
n tsctm210 (Quotation Configuration lines)
n tsctm310 (Contract Configuration lines)
Module History and Statistics
New session
n Uptime Analysis (tshst2400m000) and related Forms and Reports
New tables
n None
Table changes
Tsctm210
Sno Field Description
1 ustm Uptime coverage Start time, goes as input to the contract
2 Uetm Uptime coverage end time, goes as input to the contract
3 Uprc Agreed Uptime Percentage, goes as input to the contract
Functional enhancements SP3
Release Notes Service Pack 3
1-6
Tsctm310
Sno Field Description
1 ustm Uptime coverage Start time
2 Uetm Uptime coverage end time
3 Uprc Agreed Uptime Percentage
Customer implications/benefits
Is the enhancement new?
Yes, the new functionality improves the service performance and the customer
satisfaction, by maximizing the available uptime time of the customer’s
equipment.
What does the enhancement replace?
It does not replace any of the existing functionality.
Can you still use the previous software?
Yes.
Do you have to start using the enhancement now?
It is not mandatory to use the new functionality.
Can you start using the enhancement later?
Yes.
What must be done to use the enhancement?
Conversion of data is not required.
Follow these high level steps to start using the enhancement.
1 Define the uptime agreement values in the Quotation Configuration Lines
(tsctm2110s000)session.
2 Define the uptime agreement values in the Contract Configuration Lines
(tsctm3110s000) session.
3 Proceed with any helpdesk support or rendering field service, as usual.
4 Start the Uptime Analysis (tshst2400m000) session for reporting service
performance.
Functional enhancements SP3
Release Notes Service Pack 3
1-7
Changed Business Processes
There are no changed business processes.
Are other components influenced?
No.
PCF
The Product Configurator (PCF) module was converted from Baan IV to
BaanERP5.0b. The version that is included in Service Pack 3 for BaanERP5.0b
is a beta version. This means that the product did yet not completely pass the
system test.
You must not use the PCF module in a live production environment. Do not
customize the PCF software for your specific purposes because the current beta
version may change.
The beta version intends to demonstrate the customer what the functionality will
be in the final product. For the main part the PCF functionality is the same as in
BaanIVc.
The following functionality is not supported in beta version of PCF:
n Integration with EDI.
n Printing options and features of a product variant when printing a BOM
structure.
n Skipping phantoms from a product structure.
Furthermore, take into consideration that creating a product structure based on a
generic item does not work properly yet.
The software and the online Help is only available in Americsn English. The
online Help was not yet fully reviewed at the time of this beta release and it may
contain errors.
Migration from Baan IV to BaanERP5.0b with SP3 is not possible. Migration
will be possible when the migration tool for BaanERP5.0b is released.
The final version of PCF will be delivered in Service Pack 4 for BaanERP5.0b.
Baan Company whishes to encourage customers and partners to log the remarks
they find while working with this beta product. Baan Company will incorporate
solutions for remarks in the final version which will be included in service
pack 4.
Do not use the SP3 BaanERP5.0b version of PCF in a live BaanERP
environment.
01 Saturday Sep 2012
Posted Baan ERP
inFollow these steps to complete an NT service pack update:
1 For NT insert the service pack CD-ROM. The installation program starts
automatically. The following dialog box is displayed:
2 Click Next. The following dialog box is displayed:
3 If you accept the terms, click Yes. The Select environment dialog box is
displayed.
4 Select the existing environment you want to update. Click Next. The Update
Baan software environment dialog box is displayed.
5 Select the components you wish to update. You must select the application
components. Choosing the porting set components is optional but highly
recommended. Click Next.
7 Select Full Update (recommended). Click Next. The Update configurations
dialog box is displayed:
8 Select BaanERP B50b. Click Next. The Setup Information dialog box is
displayed.
9 Click Next to continue or select Back to review your settings.
10 Now the setup process starts copying files. If a read-only file is detected, you
are requested to overwrite it by clicking Yes or otherwise to click No.
11 The following dialog box is displayed.
12 Now BaanERP is ready for the Baan user logon. Type the password and
select Connect to start BaanERP. The following message is displayed:
Patch your software
13 Run the Patch Objects After Error Solving (ttiex3226m000) session and
supply the following information:
Package: tt
Objects : from:
to : zzzzz
After the patch process is ready, the message Patch your Software will not appear
again when you start the BaanERP software.
Create package VRC
Follow these steps to create a package VRC. Please note that the following
procedure does not cover all possible details and issues. Screens in the
instructions may look different due to your current setup. For example, you may
or may not have installed a previous service pack.
If you have already created a VRC for a previous service pack, creating a new
package VRC is not mandatory. If you have not created a package VRC for the
service pack you must follow the steps described below.
Follow these steps to create a package VRC for a service pack.
1 Use the browser to navigate to the Baan Tools.
2 Start the Package Combinations (ttaad1520m000) session.
3 Insert a package combination. You are free to choose a name, for example
b50bU, description: BaanERP_B50b Service Packs and Table Definition Path
: ${BSE}dict.
4 When asked if you want to create the ${BSE}dict/ddb50bU directory, click
Yes and exit by clicking Close. (The directory name is an example).
5 Use the Package VRCs (ttadv1511m000) session to check the VRC structure.
6 Start the Package by Package Combination (ttaad1121m000) session. From
the Group menu, choose Duplicate.
7 Select the first record to be copied, then select the last record to be copied.
8 Enter the name of the new package combination.
9 Change the values of the columns Version, Control, and Release for each
package as shown in the Package by Package Combination dialog box.
Choose Save from the File menu to save the changes.
10 From the Specific menu, choose Rebuild DD (Data Dictionary).
11 Start the Change Package Combination by Company (ttaad1101m000)
session.
12 Complete the fields as displayed above and select all companies, for example,
from 000 to 820.
13 Click Change.
14 Start the Change Package Combinations for Users (ttaad2200m000) session.
15 Click Change.
16 Click Close. The package VRC has now been set up correctly.
17 Run the Create Tables (ttaad4230m000) session and supply the following
information (be sure that you are in the right package combination, for
example b50bU)
Company: From 000 to 900 (for example)
Package : From to zz
Table : From to zzz999
After a while the message xxx Tables Created appears. Click OK.
If you do not use Baan Project, the service pack update is now complete.
If you use Baan Project you must continue with the next section.
To install the Service Pack
Release Notes Service Pack 2
4-16
Baan Project conversion
Due to table changes for the Baan Project package you must run a conversion
session. You must run this conversion for each company in Baan. If you do not
use Baan Project you can skip the the actions in this section.
Follow these steps to run the conversion.
1 Start the Create Run time Data Dictionary (ttadv5210m000) session.
Complete the fields as shown below.
2 Click Create Run time. When the conversion is ready click OK to continue.
3 Change company to the company number for which you want to use Baan
Project. To do so choose Change Company from the Options menu.
Do not choose company number 0.
4 Start the Intitialize Rate . . . (tppdmconv_cy2) session.
IMPORTANT NOTE
To install the Service Pack
Release Notes Service Pack 2
4-17
5 Choose Continue. When ready, a message is displayed that indicates fields in
the project tables are filled.
6 If you click OK the same dialog box is displayed once more. You must click
the X symbol in the, top right, to close the dialog box.
7 Repeat the steps using the tppdmconv_cy2 session from step 3 through step 6
for each company for which Baan Project data must be converted. Do not
perform these steps for company 0, because this company contains setup
data.