BaanEDM 1.3
Release Notes Service Pack 1

Table of contents 

1 Introduction 1-1

Contents 1-1

2 To install the service pack 2-1

Prerequisites before the installation 2-1
You must have BaanEDM1.3 on your system 2-1
Save all customizations 2-1
Close all regular procedures 2-1
How to install the service pack 2-2
How to install the Baan sessions 2-2
How to install the Modeler Templates 2-4
How to install the BaanEDM Utilities 2-5

3 The service pack 3-1

Content of the Service Pack 3-1
Remark/Tips 3-3
Modified components of Service Pack 1 3-4

About this document

This document describes the contents of the Service Pack 1 for BaanEDM1.3 and
shows you how you can install it. These Release Notes are intended for
BaanEDM1.3 installers and system administrators.

This guide consists of the following chapters:

Chapter 1 gives you an introduction to the Service Pack 1 for BaanEDM1.3_Asc

Chapter 2 describes how you can install the Service Pack.

Chapter 3 lists all functionality of the Service Pack. It describes all issues that
are solved within this Service Pack and it lists all components that are
modified.

1 Introduction 

The Service Pack 1 for BaanEDM1.3 is for all BaanEDM1.3 users. Here BaanEDM1.3
is meant for ASCII version of EDM1.3. You can only
use this Service Pack to upgrade an existing BaanEDM1.3 installation. 
The Service Pack contains all patches created up until 31 January 2001.

Contents

The Service Pack 1 for BaanEDM1.3 contains the following components:

•	Baan Export sessions.

•	Broadbase Schemas.

•	Broadbase Scripts.

•	VB applications.

•	Documentation.

These components are used in the following functional areas:

•	Sales.

•	Finance.

•	System Administration.

•	Customization.

2 To install the service pack

Prerequisites before the installation

The Service Pack 1 for BaanEDM1.3 is for all BaanEDM1.3 users.

You must have BaanEDM1.3 on your system

You can only use this Service Pack to upgrade an existing BaanEDM1.3
installation. Therefore, BaanEDM1.3 must be installed. This Service Pack 1 only
contains modified components, not all BaanEDM1.3 components.
Note that components of this Service Pack will overwrite components of the
BaanEDM1.3 installation.

Save all customizations

The Installer will overwrite existing components. Make sure you save
customizations. Take care not to overwrite any customizations to BaanEDM1.3.
You must save these customizations. Components of the standard BaanEDM1.3
will be overwritten by the components of this Service Pack. You must save these
customizations in such a way that after the installation of this Service Pack, you
can customize BaanEDM 1.3. You need at least a back up. You can also print
out the modifications. Broadbase components can be exported to a dump file.
Baan provides guidelines for setting up customizations and these guidelines help
you avoid upgrading problems.

Close all regular procedures

All regular procedures related to BaanEDM1.3 must be closed, for example:

•	No export processes are running.

•	The warehouse data updated.

•	The cubes are processed.

•	The backup procedure is finished.

How to install the service pack

This Service Pack contains three types of components: Baan sessions, Baan
Enterprise Decision Modeler (= Broadbase) Templates, and some System
Management tools.

These three component types must be installed on the relevant computer:

•	The Baan sessions on the Baan computer.

•	The Broadbase components on the Broadbase computer.

•	The System Management tools on the computer on which these applications
are installed for BaanEDM1.3.

You must therefore start the Installation program from the relevant computer.

How to install the Baan sessions

The Baan sessions are dumped in three dump files. The Installer will transfer
these three dump files onto your local computer (Step 1 – 4). If you run Baan on
a UNIX machine, you need to transfer the dumps (FTP) from the local machine
to the UNIX machine (Step 5).
When the dumps are on the Baan machine, you can import them in the Baan
system using standard installation sessions from the Baan system. For Baan4c4
you import the dumps with the PMC module. For Baan4c2/4c3 this process is
described in detail in the BaanEDM1.3 Installation Manual (Doc. No. U7182e US),
chapter 4: “How to install the BaanEDM1.3  components on the Baan server”. This
procedure is described in short, starting with step 6.

1 If Baan runs on NT, start up the Service Pack 1 Installer on the Baan
computer. If Baan runs on UNIX, you can start the Installer on any NT
machine.

2 In the Select Components dialog box select Baan Export Sessions and
Exchange Schemas.

3 Click Next.

4 The Start Copying Files dialog box gives an overview of all selections.
Click Next to start the Installation process.
The system will copy the dump files to the
C:\Program Files\Baan\BaanEDM1.3\Baan Export directory. If necessary, the
system it will create this directory.

The dump file edm1.3sp1_c4 contains the sessions for a Baan4c4
environment. This dump file must be imported in Baan with the PMC-tool.
The dump file edm1.3sp1_c3 contains the sessions for a Baan4c2/4c3
environment.

5 If Baan runs on UNIX transfer the dump files (FTP) to a temporary directory
on the Baan computer.
For Baan4c2/4c3, take step 6.through 12 For Baan4c4, skip step 6, and
continue at step 13.

6 Start the Import patch (ttiex1284m000) session.

7 Fill in the following fields as shown here:
- Path Patch File: the directory and filename of the dump file (result of step 4
or 5) must be: <directory>/spedm_c2_1.
- Path Runtime Dictionary must be: ${BSE}/application.
- Overwrite: must be selected.
- Delete patch file after installation: must be selected.
- Write software components in other package VRC: must be selected.
- VRC: use the <VRC code belonging to the right Package Combination>.

8 Click Continue to start the Import process.

9 Start the Create Runtime Dictionary (ttadv5210m000) session.

10 Fill in the following fields as follows:
- Package Combination From: use the relevant Package Combination.
- Package Combination To: use the relevant Package Combination.
(Make sure you enter the correct package combination, meaning the package
combination of your operational environment.)
- Sessions must be selected.
- Package From: tg.
- Package To: tg.
- Session From: edm.
- Session To: edmzzz.

11 Click Continue to start the process.

12 When this session is completed the import of components in Baan is finished.
You must restart bshell before any new components can be used.
This is the end of the procedure for installing Baan Sessions and Exchange
Schemas for Baan IVc4:

13 Import the edm1.3sp1_c4 dump file with the PMC tool.

14 Continue at step 9

How to install the Modeler Templates

1 Start up the Service Pack 1 Installer on the Broadbase computer.

2 In the Select Components dialog box, select Modeler Templates.
Click Next.
3 In the Data Warehouse Database Server Name dialog box enter the name
of the computer on which the data warehouse B4C13 is located.
Click Next.

4 In the Baan Enterprise Decision Modeler Administrator Password dialog
box enter the password of the Broadbase administrator (twice).
Click Next.
The Start Copying Files dialog box gives an overview of all selections.

5 Click Next. A warning will appear that there already is an ODBC DSN to the
data warehouse B4C13.

6 Select Yes to replace the existing DSN, and No if you do not want to replace
it. It is recommended to choose No.
The system will start copying and importing the files into Broadbase.
When the import is completed, the system will ask you whether you want to
view the logfiles. You have the option to check the results of the import
process.
If you select Yes, several Error Search dialog boxes appear, that show you
where the word Error occurs in the logfile. Dialog boxes will appear for every
imported module, for example, Common, Finance and Project.
The severity of the errors establishes whether you need to take action. (For
instance, if you run the installation twice on the same machine, a lot of errors
will come up, indicating that some components are missing or are already
present.)
The Setup Complete dialog box indicates that the installation process is
completed.

How to install the BaanEDM Utilities

1 Start up the Service Pack 1 Installer on the computer on which the 1
BaanEDM1.3 System Management tool is installed.

2 In the Select Components dialog box, select BaanEDM Utilities.
Click Next.

3 In the Start Copying Files dialog box, click Next.

4 The system will copy the files.

5 The Setup Complete dialog box indicates that the installation process is
completed.

3 The service pack
Content of the Service Pack

This Service Pack 1 contains BaanEDM1.3 components that are modified based
on feedback concerning BaanEDM1.3. It also contains an Installer, to install
these modified components.
The following table lists all patches. The table gives an overview of the defects
(bugs) solved in BaanEDM1.3. The next section will list all modified components per defect. No modifications were carried out on the layout of the warehouse data.

DefectID : 104300
Components : Finance export session (tgedm4220m000)
(Baan Script tgedm4220
Baan form tgedm4220m0001
Baan label tgedm4220.TGEDM_LB
Baan label tgedm4220.TGEDM_BA
Baan label tgedm4220.TGEDM_NF
Baan label tgedm4220.TGEDM_FT
Baan label tgedm4220.TGEDM_IT)

Problem: In Finance export session(tgedm4220m000), there were three options Ledger balances, Budget amounts and Transactions. It didn’t have the flexibility to export only finalized transactions or Non-finalized transactions or Integration transactions.  This took lot of time for exporting unwanted data if customer wants any one type of the transaction.

Solution: Transactions option is split into Finalized transactions, Non-Finalized transactions and Integration transactions. It gives the flexibility to export the transactions separately.

DefectID : 102094
Components : Finance export session (tgedm4220 )

Problem: It was not possible to export the budget information when data warehousing currency  was not equal to USD .

Solution: It is possible to export the budget information for all types of currency properly.

DefectID : 102223
Components : Finance export session (tgedm4220 )

Problem: If all the options are not selected in the export session of finance and exporting first time after installation of the templates, there will not be *.txt files for those options. During the transformation of the data, when Broadbase cannot access the source file, it will give error. Broadbase will give the following error, when tfglg008.txt is not there.

[13880] Error: Sql failure in script: 'java.sql.SQLException: [41020] Error in method Describe: java.sql.SQLException: [29320] OS error opening file C:\Program Files\Baan\BaanDM1.3\Modeler Templates\b4cfin13\TFGLD008.TXT': The system cannot find the file specified. [49010] while starting 'link' execution object, #0  [23000] Error: Statement could not be validated ' 

Solution: Finance export session (tgedm4220m000) creates  *.txt files with space in it, which is handled by Broadbase.

DefectID : 93081
Components : Sales export session (tgedm4200 )
(Baan script tgedm4200)

Problem: When exporting sales data for certain date range in which no data is found, after the export the default range for next run is 31 -12- 9999 to 31-12-9999. 

Solution: Now it shows the range from date of last run  to 31-12-9999.

DefectID : 102640
Components : Extraction job runner (RunBaanJob.exe)

Problem: Extraction job runner is replacing the command option instructions of *.bwc. It is causing the problems if there is any command option instructions.
Ex: -- -set user=username in the command option as shown below. 

It was not taking the user as pvalk. 
Solution : Extraction job runner  is appending the command option instructions( if any) with its instructions.

DefectID : 111163
Components : Export and Import BCD 
(ExportBCD.exe
ImportBCDsp2.exe)

Problem: The BCD file that is written by ExportBCD does have the first line that causes problems with the newest Microsoft XML libraries. The ImportBCD can’t read   first line in the bcd files with newest Microsoft XML libraries. 

Solution: The changes in the ExportBCD and ImportBCD are technical and have to do with the changes in the Microsoft XML libraries. The BCD file that is written by the ExportBCD does not have the first line (which is causing errors with newest Microsoft XML libraries). The ImportBCD can read both old (Who have BCD file with this first line which is causing errors with latest Microsoft XML libraries) and new (Who doesn’t have BCD file with this first line which is causing errors with latest Microsoft XML libraries) export BCD files.

DefectID: 100035
Components: Baan OLAP Client (TextConvert.xla)

Problem: When data is exported to Excel via the BEDN2.0 OLAP Client, then the measures are exported as text and not as numbers. This implies that measures are visible in Excel but can’t be added or used in formulas. 

Solution: The TextConvert.xla, excel add-in, can be used to convert measures from text format to number format. See Appendix A for more information on implementation.

DefectID : 101102
Components : Broadbase (PutSpaceInEmptyFile.exe)

Problem: Broadbase can not handle empty ASCII files. Then it crashes. 

Solution: Visual basic correction program (PutSpaceInEmptyFile.exe) has been made for this. This correction program PutSpaceInEmptyFile.exe delivers a workaround for this problem. It puts one space character in all empty anymore and broadbase will not crash. See Appendix B for more information on implementation.

DefectID : 102374
Components : SQL Server 
(Broadbase script "B4CSST13"."Changed Views")

Problem: The view Sls_Orderlines was containing the data of delivered orders (Status =3). It is requested to have all orders. (Besides delivered orders, rejected orders and non-delivered orders also present in the Sls_Orderlines View). 

Solution:  Now Sls_Orderlines view and Sls_Orderlines_Final table  contain the data of all orders besides delivered orders rejected orders (Status = 2) , Non-delivered orders (Status = 1). If customer wants have only delivered orders  ( Status = 3) just replace the following script.

CREATE OR REPLACE SCRIPT "B4CSST13"."LOAD_FACTS_SLS_ORDERLINES_FINAL"
REMARK ''
AS
sql.setErrorHandlingState(CONTINUE);
// delete the obsolete facts from the DW table
//
execute method RemoteDB.ExecuteSQL('B4CSST13', 'DW_LINK',
'DELETE FROM "SLS_ORDERLINES_FINAL"  WHERE
EXISTS (SELECT * FROM "SLS_ORDERLINES" WHERE
SLS_ORDERLINES.Ordernr = SLS_ORDERLINES_FINAL.Ordernr
AND
SLS_ORDERLINES.Position = SLS_ORDERLINES_FINAL.Position
AND
SLS_ORDERLINES.LogComp = SLS_ORDERLINES_FINAL.LogComp
AND
SLS_ORDERLINES.DateStored <>  SLS_ORDERLINES_FINAL.DateStored)
');
//
// load the new data
execute method RemoteDB.ExecuteSQL('B4CSST13', 'DW_LINK',
'INSERT INTO "SLS_ORDERLINES_FINAL" SELECT * FROM "SLS_ORDERLINES" WHERE NOT  EXISTS( SELECT * FROM "SLS_ORDERLINES_FINAL" WHERE
SLS_ORDERLINES.Ordernr = SLS_ORDERLINES_FINAL.Ordernr
AND
SLS_ORDERLINES.Position = SLS_ORDERLINES_FINAL.Position
AND
SLS_ORDERLINES.LogComp = SLS_ORDERLINES_FINAL.LogComp)');
/

By

CREATE OR REPLACE SCRIPT "B4CSST13"."LOAD_FACTS_SLS_ORDERLINES_FINAL"
REMARK ''
AS
sql.setErrorHandlingState(CONTINUE);
// delete the obsolete facts from the DW table
//
execute method RemoteDB.ExecuteSQL('B4CSST13', 'DW_LINK',
'DELETE FROM "SLS_ORDERLINES_FINAL"  WHERE
EXISTS (SELECT * FROM "SLS_ORDERLINES" WHERE
SLS_ORDERLINES.Ordernr = SLS_ORDERLINES_FINAL.Ordernr
AND
SLS_ORDERLINES.Position = SLS_ORDERLINES_FINAL.Position
AND
SLS_ORDERLINES.LogComp = SLS_ORDERLINES_FINAL.LogComp
AND
SLS_ORDERLINES.DateStored <>  SLS_ORDERLINES_FINAL.DateStored)');
//
// load the new data
execute method RemoteDB.ExecuteSQL('B4CSST13', 'DW_LINK',
'INSERT INTO "SLS_ORDERLINES_FINAL" SELECT * FROM "SLS_ORDERLINES" WHERE Status = 3 and
NOT  EXISTS( SELECT * FROM "SLS_ORDERLINES_FINAL" WHERE
SLS_ORDERLINES.Ordernr = SLS_ORDERLINES_FINAL.Ordernr
AND
SLS_ORDERLINES.Position = SLS_ORDERLINES_FINAL.Position
AND
SLS_ORDERLINES.LogComp = SLS_ORDERLINES_FINAL.LogComp)');

DefectID : 111165
Components: Finance export session (tgedm4220m000 )

Problem: In special circumstances the export of financial ledger balances is slow.

Solution:   This has been solved by adding some database hints ("order by" statement) in 
the sql queries, so that a more optimized index is taken, to read the Baan data from the ledger balances.

Modified components of Service Pack 1

The following table lists an overview of the modified components per defect.
This list is important if you must redo customizations.
The MarkCode column lists the code used to mark the modifications in the Baan
export sessions. (Modifications in Broadbase cannot be marked).

DefectID Modified Components MarkCode

DefectId	Modified Components	MarkCode	
1	Baan Script tgedm4220
Baan form tgedm4220m0001
Baan label tgedm4220.TGEDM_LB
Baan label tgedm4220.TGEDM_BA
Baan label tgedm4220.TGEDM_NF
Baan label tgedm4220.TGEDM_FT
Baan label tgedm4220.TGEDM_IT	SP1 –1	
2	Baan script tgedm4220	SP1 –2	
3	Baan script tgedm4220	SP1 -3	
4	Baan script tgedm4200	SP1 -4	
5	RunBaanJob.exe	SP1 -5	
6	ExportBCD.exe
ImportBCDsp2.exe	SP1 -6	
7	TextConvert.xla	SP1 -7	
8	PutSpaceInEmptyFile.exe	SP1 -8	
9	Broadbase Changed_Views	SP1 -9	
10	Baan script tgedm4220	SP1 - 10	

			

Appendix A

TextConvert Excel add-in Guide

Purpose

This document describes an add-in for Microsoft Excel that Baan has developed for solving the following problem:

When data is exported to Excel via the BEDN 2.0 OLAP Client, then the measures are exported as text and not as numbers. This implies that measures are visible in Excel but cannot be added or used in formulas.

The Excel add-in can be used to convert measures from text format to number format.

Installation

Copy the file to the folder C:\Program Files\Microsoft Office\Office\XLSTART on each client PC where the tool is needed. Most likely, this is each PC that has BEDN 2.0 installed.

Usage

(Re)start Excel. Excel shows a menu option "BaanBIS" with one command "Convert text". This menu options will automatically be available, each time Excel starts.

In order to use the add-in:
1.	Open a .xls file that was created via BEDN 2.0.
2.	Select the range to be converted. Usually the range is a rectangular shaped region of cells on the spreadsheet. It can be selected by clicking the upper-left corner and then dragging the mouse to the lower-right corner of the region. Alternatively, one can click the upper-left corner and then shift-click the lower-right corner of the region.
3.	With the region selected, choose the menu option "Convert text" in the "BaanBIS" menu.
4.	The target region is now converted to number format and the measures can be used in calculations.

Appendix B

          Fill the Empty file add-in Guide

Purpose

This document describes a BaanBIS application 'PutSpaceInEmptyFile' that is developed for solving the following problem: Broadbase crashes when a *.txt-file is empty. 

In BaanBIS the export sessions and Exchange schema's do an export from a fixed set of tables. Some customers do not have all of that tables filled (Example: not all customers use financial budgetting). Exporting from an empty Baan table will result in an empty *.txt file. Broadbase can not handle an empty *.txt file to read from and it will crash. 

This correction program PutSpaceInEmptyFile delivers a workaround on this problem: it puts one space character in all empty *.txt files in a given directory. Then the *.txt files are not empty anymore and Broadbase will not crash.

Installation

Copy the file to the folder C:\ or any other path on PC where Broadbase server is installed.

Description

The program has no graphical user interface, there is just a command line interface. This command line interface makes it possible to add this program to the standard Job Runner (from EDM1.3 and onwards) of BIS and make it run automatically (if that fits into the procedure).

Syntax: 
PutSpaceInEmptyFile.exe -DirName <Directory path> [ ‑LogFile <Logfile name> -StatusFile <Statusfile name> ]

where:

Directory path	The directory that contains the *.txt-files that should be checked.	
Logfile name	Path and name of the logfile to be created.	
Statusfile name	Path and name of the statusfile to be created.	

Logfile and Statusfile are optional but are required for running this program from the Job Runner. 

When started the program will check all *.txt-files in the given directory for being empty. 
When empty (containing zero characters) it will write a space character in and save the file. 
It will write logging info to the logfile (when specified) and its status in the statusfile (when specified).
UI-feedback to the user will only be given when no logfile nor statusfile are specified (otherwise a batchprocess will hang on waiting for pressing OK). 

The process about the *.txt-files is of 3 steps:
1.	Data exported by Baan4c and written on the Baan-server
2.	Transfer (= FTP or copy) the *.txt-files to the Broadbase server
3.	Broadbase reads the *.txt-files and writes to the data warehouse.

This correction program should correct the *.txt-files between step 2 and 3. 

In case you have defined a cluster script (like run_B40c) with Maintain Broadbase parameters from the BIS Console then you have to add a call to this program manually into the cluster script (and do it again when the script is regenerated). 
Reason is that step 2 and 3 are executed subsequently from that one cluster script, where the cluster script itself can be scheduled in Job Runner.

Please see an example below where the call to the program is manually added to the cluster (in bold). 

create or replace script "GENERIC"."RUN_B40C" as 
// Cluster: RUN_B40C
// Generated at: 6/8/00 12:02:39 PM
execute method "GENERIC".PollGetBaanFiles.Log('Info','RUN_B40C starts running.');
// The BB code to run schema B4CSST13 starts here.
execute method "GENERIC".PollGetBaanFiles.PollGetFTP('sabine', 'login','password','UNIX','/home/pvalk/sls','C:\Program Files\Baan\BaanDM1.3\Modeler Templates\b4csst13', 5,300) ;
if(sql.wasError()) {
sql.output("Error: Baan files for B4CSST13 couldn't be loaded");
} else {
execute method "GENERIC".RedirectLink.toDir('B4CSST13', 'SST_LINK','C:\Program Files\Baan\BaanDM1.3\Modeler Templates\b4csst13');
if(sql.wasError()) {
sql.output("Error: Couldn't change B4CSST13.SST_LINK" );
} else {
execute method Run_executable.Do_Exec('C:\PutSpaceInEmptyFile.exe -DirName "C:\Program Files\Baan\BaanDM1.3\Modeler Templates\b4cfin13\" -StatusFile C:\Temp\stat.txt -Logfile C:\Temp\log.txt',0);
execute method "GENERIC".PollGetBaanFiles.Log('Info','B4CSST13 Starts running for C:\Program Files\Baan\BaanDM1.3\Modeler Templates\b4csst13');
execute script "B4CSST13".CONTROL_NOPOLL;
execute method "GENERIC".PollGetBaanFiles.Log('Info','B4CSST13 Finished.');
}
}
execute method "GENERIC".PollGetBaanFiles.Log('Info','RUN_SLS is finished.');
/