baan ivc functions and featuresbaansupport.com/docs/baan iv c functions and features.pdf · baan...

Functional Release Information P3007B US

Research and Development

BAAN IVc

Functions and Features



Document informationDocument

Number : P3007B USGroup : Product InformationName : Functions and FeaturesEdition : BDate : September 1997

© 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 bereproduced, stored or transmitted in any form or by any means, electronic or mechanical, for anypurpose, 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 anyerrors, omissions or discrepancies between the software and the information contained in thisdocument.


v

Table of contents

1 Application development 1.11.1 Reference designator 1.11.2 Tfgld table split 1.11.3 IRP enhancements 1.1

1.3.1 Work load control 1.11.3.2 Cyclic planning 1.21.3.3 Performance evaluation 1.21.3.4 Forecast time fence 1.31.3.5 Firm planned interplant receipts 1.31.3.6 Net change MPS 1.3

1.4 OLE enhancements 1.41.4.1 Standard methodology 1.41.4.2 Excel Application worksheet standards 1.41.4.3 Excel Input Specification worksheet standards 1.41.4.4 Excel Module standards 1.41.4.5 Coding standards 1.41.4.6 Error handling 1.41.4.7 Validation of data 1.51.4.8 Generation of error report within Excel worksheet or BAAN print session 1.51.4.9 BAAN Applications 1.5

1.5 Performance improvements 1.51.6 Finance enhancements 1.6

1.6.1 New reports 1.61.6.2 Credit control 1.6

1.7 GLO functionality 1.71.7.1 Sales tax enhancements (formerly GLO functionality) 1.81.7.2 EDI 1.111.7.3 Distribution (formerly GLO functionality) 1.121.7.4 Finance (formerly GLO functionality) 1.131.7.5 Transportation (formerly GLO functionality) 1.14

2 BackOffice support 2.12.1 Intel NT support 2.12.2 Alpha NT support 2.12.3 License manager NT 2.12.4 Update facility 2.12.5 Conversion facility 2.12.6 Installation improvements on Informix 2.22.7 Oracle NT support 2.22.8 2.8 SQL Server performance improvements 2.32.9 Auto start mechanism 2.3



vi

3 Tools development 3.13.1 Function Server DLL 3.1

3.1.1 Design approach 3.23.2 Performance improvements 3.23.3 Sybase (Controlled Release, restricted shipment) 3.33.4 Exchange improvements 3.43.5 Distributed Data Collection 3.53.6 Orbix 3.53.7 Multibyte on Unix 3.53.8 Enhancements with Windows clients 3.53.9 Performance improvement refint 3.63.10 Audit improvements 3.63.11 Permissions on outer joins 3.6

4 Internet support 4.14.1 Introduction 4.14.2 HTML 1.0 4.14.3 BAAN IVc Internet applets 4.14.4 Electronic Shopper 4.2

4.4.1 Administration 4.24.4.2 Shopping Experience 4.24.4.3 BAAN sales order generation 4.34.4.4 Sales order status 4.3

5 Orgware development 5.15.1 DEM enhancements 5.15.2 Workflow (demo version) 5.25.3 BAAN Data Navigator 5.2

5.3.1 Scope IVc 5.3

6 Interfaces and partner packages 6.16.1 BAAN PDM 6.16.2 BAAN Synchronization 6.2

6.2.1 Functional specifications 6.26.2.2 6.2.2 The planning and scheduling cycle 6.5

6.3 Hyperion 6.56.3.1 General information about the Hyperion products 6.56.3.2 The interaction between BAAN and Hyperion 6.6

6.4 BAAN Sales 6.66.5 ISSI Safari reporting tool 6.76.6 Tax provider interface (North America, formerly GLO functionality) 6.7

6.6.1 Static data 6.86.6.2 Address jurisdiction checks 6.86.6.3 Product and line-based tax calculations 6.86.6.4 Tax register updates 6.86.6.5 Order balance updates 6.86.6.6 Finance impact 6.96.6.7 Sales installments 6.96.6.8 Service contracts limited to a single location 6.96.6.9 Tax calculation/register adjustment utility 6.9



vii

6.6.10 Conversion utilities 6.96.6.11 Tax matrix modifications by product category 6.96.6.12 Removal of transaction type restriction for taxware 6.106.6.13 Supported versions 6.106.6.14 TAX API 6.10

6.7 COMPAQ SmartStart 6.116.7.1 Purpose of SmartStart 6.116.7.2 Features of SmartStart 6.116.7.3 SmartStart - Baan Logic Flow 6.126.7.4 Components of SmartStart – BAAN integration. 6.126.7.5 Current limitations - future considerations 6.12

7 BAAN IVc extensions 7.17.1 CNT (Controlling/Kostenrechnung) 7.1

7.1.1 Budgeting and control of overhead costs 7.17.1.2 Cost price calculation 7.27.1.3 Statement of operating results 7.27.1.4 Separate controlling package 7.37.1.5 Coexistence with other extensions 7.37.1.6 Technical information 7.3

7.2 SCC (Supply Chain/Controlling) 7.37.2.1 Coexistence with other Extensions 7.47.2.2 Technical information 7.4

7.3 SCH (Supply Chain) 7.47.3.1 Features 7.4

7.4 MCR (Multicurrency) 7.67.4.1 Multicurrency accounting 7.67.4.2 Rules for dual accounting 7.67.4.3 Conclusion 7.6

Appendix A Portingsets for BAAN IVc A.1



viii



ix

About this document

This document contains information about the BAAN IVc release. It describes the newfunctionality compared to the BAAN IVb release. Note that this document does not yetcontain information about Supply Chain (SCH) and Localizations. This information will beinserted in this document in the version of June.

This document is divided into 7 chapters.

Chapter 1 describes the new functionality in the BAAN IVc applications.

Chapter 2 describes the new functionality in BAAN IVc BackOffice.

Chapter 3 describes the new functionality in the BAAN IVc Tools.

Chapter 4 describes the new functionality in the BAAN IVc Internet support.

Chapter 5 describes the new functionality in BAAN IVc Orgware.

Chapter 6 describes the new Interfaces/Partner packages incorporated in BAAN IVc.

Chapter 7 describes the BAAN IVc extensions.

Appendix A describes the BAAN IVc porting sets.

.



x

Functions and Features BAAN IVc

1 - 1

This chapter describes the new funcionality in the BAAN IVc applications. The followingtopics are covered:

n Reference designatorn Tfgld table splitn IRP enhancementsn OLE enhancementsn Performance improvementsn Finance Enhancementsn GLO functionality

1.1 Reference designator

In the BAAN IVc release reference designators are introduced. Reference designators can bedefined on the lines of the bill of material (the BOM module) and the customized bill ofmaterial (the PCS module). They identify the physical position of the components on theparent item. Every BOM line and CBOM line can refer to multiple reference designators.Reference designators can be printed on the material lists in the shop floor control module.

1.2 Tfgld table split

BAAN IVc introduces enhanced integration tables in the General Ledger (GLD) module.Some customers felt restricted by the size of the integration table. This table becomes verylarge after being operational for some months. Archiving is not always possible becauseproject data may only be archived if the project status is closed.

In BAAN IVc the table size remains manageable by:

n Reducing the number of records.This is achieved by separating the debit and credit transactions in two tables, by archiveand purge options, and by compressing data.

n Reducing the record length.This is done by moving some data that is not always used to a separate table.

1.3 IRP enhancements

The following new IRP features are introduced in BAAN IVc:

n Planning method: work load controln Enhancements to cyclic planningn Performance evaluationn Forecast time fencen Firm planned interplant receiptsn Exception message until periodn Net change MPS

The new features are described in the sections below.

1.3.1 Work load control

Work load control is a planning method that is based on the idea that production lead timesand work load level are related. The method will plan with fixed lead times, but is completelydifferent from MRP-II, as it considers the constrained availability of capacity and material.

1 Application development

1 - Application development


1 - 2

The work load control planning method controls the work load on MPS level (where ordersare accepted) and in this way ensures that the fixed lead times (used on MRP/PRP-level) arefeasible. It therefore satisfies the need of MRP-II for a work load control instrument. Thework load control planning method is suited for the following types of production companies:

n Job shopThe work load control planning method is based on the relation between work load andproduction lead time.

n Discrete multimodel flowThe work load control planning method plans with fixed lead times.

n Process flow and batchThis planning method considers (not optimizes the planning of) co-products andcontainers and is suited for the process industry.

1.3.2 Cyclic planning

Cyclic planning has been implemented already in BAAN IV b. In BAAN IVc the followingextensions have been made to cyclic planning:

n Secundary capacity constraintsn Material constraints

1.3.3 Performance evaluation

The evaluation component supports the user in evaluating the results of simulation runs onseveral levels. The user can start on a global level (for example, total sales volume) and, ifnecessary, zoom in on detailed information. This business object is based on a number ofperformance indicators specified per plan item and work center. These performance indicatorscan be viewed for complete logistic plans or for single plan items or work centers.

The results of a simulation run are evaluated on a number of categories: customer service,inventory, utilization and financial. IRP offers three types of information:

1 Performance indicators per logistical plan give a quick overview of the total performanceof the planning run and show if and what type of planning problems occured.

2 Performance reports show the planning performance per Plan Unit, plan item, and workcenter. With these reports you can compare the performance of different items or workcenters. You can determine where (for which items, and so on) planning problems haveoccured.

3 Time-phased performance charts present the time-phased performance information. Withthese charts it is possible to determine when planning problems occured.

Performance indicators will be provided for the following areas:

n Work center performance− The available capacity (total and extra)− The utilization

n Delivery and customer service performance− The stock delivery performance− The delivery performance



1 - 3

n Inventory performance− The absolute inventory performance− The relative inventory performance

n Financial performance− Cash flow− Production and material costs

1.3.4 Forecast time fence

For every item, forecast time fence parameter is introduced, which specifies over which timeperiod forecasts should be ignored when generating production plans. Within the forecasttime fence the consumed forecast and the total forecast (forecast plus extra demand) are madeequal. So you can still see the ‘old’ forecast while the forecast is ignored during planning. Aplan period is within the forecast time fence when the end date of the period is smaller thanthe current date plus the forecast time fence minus one.

In BAAN IVc the user is able to specify a certain horizon over which the execption messagesare generated.

1.3.5 Firm planned interplant receipts

The planner can firm plan individual planned interplant receipts. During a simulation run theplanner can overrule these firm-planned interplant receipts or take them into account. In thelatter case the system will not delete firm planned interplant receipts but will take them intoaccount during interplant planning. In other words: planned interplant receipts are onlygenerated for the part of the interplant plan that is not covered by the firm planned interplantreceipts.

1.3.6 Net change MPS

In BAAN IVc IRP supports net change with a time stamp. This means that for each item afield is added that denotes the date that something is changed. This field can have two states:

n = 0In this case the item is not considered in a net change simulation run because nothingchanged;

n <> 0In this case the field contains the date on which planning data related to this itemchanged.

The net change date is set in the following cases:

n Changes in state-independent data such as BCMs, BCCs and item attributes related toplanning.

n Changes in state-dependent data such as scheduled receipts, customer orders, and so on.n Manual changes of the inventory, demand, or production plan.



1 - 4

1.4 OLE enhancements

BAAN OLE was introduced in the BAAN IV a release to address the user’s need tomanipulate Microsoft Excel data and to upload that data into BAAN applications. BAANOLE provides the means for transfer of data from Microsoft Excel (an OLE/Automationcompliant product) to selected BAAN applications. Default templates are provided for a fewspecific applications to define the layout and mapping of data within Microsoft Excel. Thesetemplates include all the necessary underlying logic required for the transfer to BAAN. Oncedata has been satisfactorily loaded into the spreadsheet, you can transfer the data to BAAN.

In BAAN IVc, OLE has been enhanced to provide error handling and to provide a standardmethodology for creation of BAAN OLE applications. Spreadsheet layouts were alsoenhanced for usability.

1.4.1 Standard methodology

A standard methodology ensures that all OLE applications are created in a consistent mannerwith proper consideration given to all relevant aspects of the upload from OLE. The standardscover:

n Excel Worksheet, Module, and Application Worksheet standardsn Input Specification Sheet standard (for the creation of Excel Worksheet)n BAAN DLL Function and Coding standards

Standards are defined to ensure a common methodology in designing and coding of OLEfunctions. This ensures consistent functionality as well as a common look and feel amongexisting and future OLE functions.

1.4.2 Excel Application worksheet standards

Worksheet standards define the general layout of the worksheet, provide for proper security,and outline the mechanism to be used for proper recognition of data to be passed.

1.4.3 Excel Input Specification worksheet standards

Input Specification standards define the way an application worksheet will be built. Thisincludes defining column and row usage, ranges for specific types of data, and possibly logicalrelationships between data in certain cells. The information in the Input Specificationworksheet can be customized to meet the specific data requirements of the user.

1.4.4 Excel Module standards

Standards define the use of variables and data types, as well as the record formats for theDLLs used for specific applications, printing errors, and checking records.

1.4.5 Coding standards

Standard DLLs are provided for use in all OLE macros to start and end processes; connect,send, and disconnect to/from BAAN; validate and confirm data sent; and report errors.

1.4.6 Error handling

The OLE functionality has been enhanced to include error handling capabilities. Errorhandling functionality includes:

n Validation of data performed during upload process.



1 - 5

n Generation of error report to either BAAN or Microsoft Excel triggered from within Excelworksheet.

n Generation of error report from BAAN print session.

Because BAAN IVc OLE works in conjunction with the BAAN BW driver, this feature isonly available in the Windows95 or WindowsNT environment on the client side. TheMicrosoft Excel application must also be present on the user’s PC.

1.4.7 Validation of data

OLE data from Microsoft Excel goes through a validation process before updating BAANapplications. Only valid data will actually be written to the applications.

Error checking is performed during the update process, prior to updating the BAANapplication. Any errors detected will be reported. The presence of errors will not prevent validdata from being loaded into BAAN. Error reporting can be done through BAAN or sent backto Microsoft Excel, depending on the preference of the user.

1.4.8 Generation of error report within Excel worksheet or BAAN print session

BAAN IVc includes creation of OLE log records and, if applicable, OLE error log records foreach OLE event (each attempt at uploading data from Microsoft Excel to BAAN is consideredan OLE event, whether successful or not).

The status of the records included in each OLE event are recorded in the event log. Anyrecords which fail the validation check will have a rejected status in the event log and willalso be recorded in the OLE error log. The OLE logs assigns a unique identifier to each eventbased on the date and time of the event.

Reports are available to print both the logged event data and the logged error data. It is also bepossible to delete history from both logs in order to keep the size requirement of the logs frombecoming excessive.

1.4.9 BAAN Applications

The capabilities of importing OLE data into BAAN have not changed in the BAAN IVcrelease. They include the following functions:

n Financial budgetsn Sales budgetsn MPS forecasts

1.5 Performance improvements

The performance improvements implemented in BAAN IVc are listed listed below.

nn Short locking time of a database rowThe time a row is locked by a single user is important, because updates done by other userswill also be done by putting a lock before update. So, to decrease the chance of having arow locked by another user, the time of a locked row should be as short as possible. Thistopic is most relevant for databases working with page locking mechanism.

In releases before BAAN IVc, a part of the programs were written in such a way, that arow was locked from the beginning to the end of a Logical Transaction. Now, almost all ofthese programs are improved, doing the row lock just before the real update.

Note



1 - 6

nn Better queries done by standard programThe standard program sends queries to the database that are performance friendly. Thenumber of the queries has also been reduced. Further display of fields is done moreefficiently.

nn Bonus ticks in bshell CPUA user can have multiple tasks running on one connection. So when a database transactionis started in one task, this task must be finished as quick as possible. This has beenaccomplished by giving the task with the database transaction enough CPU ticks to finishits logical transaction.

nn Quality improvements BAAN IVcAn important improvement is the better logical transaction management and retryconsistency. All the logical transactions have been checked on their consistency aftergetting a retry. This topic is most important for databases with page locking mechanism,because on these systems the chance of an occurring retry —caused by a lock in the samepage— will be much higher than database systems with row locking.

1.6 Finance enhancements

In BAAN IVc new functionality was added to Finance in the Accounts Payable (ACP),Accounts Receivable (ACR) and Cash Management (CMG) modules. Additional reportingand Credit Control capabilities have been added, as described in the following paragraphs.

1.6.1 New reports

The following new reports have been created to improve visibility of open invoices andpayment/receipt activity:

n Variance Analysis Report (ACP)n Accounts Payable Distribution Report (ACP)n Supplier Aging Summary Display (ACP)n Supplier Aging Summary Report (ACP)n Customer Aging Summary Display (ACR)n Customer Aging Summary Report (ACR)n Daily Cash Report (CMG)n Check Report (CMG)

1.6.2 Credit control

In addition to the new reports created, some credit control features have been added forBAAN IVc. The Credit Control features mainly impact the ACR and CMG modules, butMCS and COM are also effected.

Finance Tables (MCS)

Credit Ratings have been added to the Finance Tables. Once a rating code has been created, itcan be assigned to customers and used for selection and sorting of various reports.

Common Data (COM)

New fields have been added to the Customer for Credit Rating, Credit Bureau ReferenceNumber, and Credit Analyst. Credit Analyst references the employee table and is included inthe selection and sorting criteria on many reports in ACR in CMG.



1 - 7

Accounts Receivable (ACR)

The following new sessions have been created in the ACR module to take advantage of theCredit Analyst associated to Customers:

n Maintain Reminder Diary by Credit Analystn Maintain Reminder Advise by Credit Analyst

The sessions summarize data by Credit Analyst. In order to view and maintain the data, azoom is provided to the individual Customer details.

Credit Analyst has been added as a variable for the header and footer text of both ReminderLetters and Customer Statements. It is available for use in the selection of invoices forreminding, as well as in the selection and the sorting of Reminder Letter and CustomerStatement reports.

The Credit Analyst is also available for selection and sorting of Customer Aging and CreditComparison reports.

Cash Management (CMG)

The following new session has been created in the CMG module to take advantage of theCredit Analyst associated to Customers:

n Display Customer Statistics by Credit Analyst

The session lists customers associated to the specified Credit Analyst, and displays theirrelated statistical information.

The Credit Analyst is also available for selection and sorting of statistics reports.

1.7 GLO functionality

In North America, a localized version of the Baan software has been developed containingfeatures for regulatory compliance and local flavor to support the North Americanenvironment. The North American version (GLO) was derived from the BAAN IVb standardversion.

In BAAN IVc the GLO derivation is merged into the standard version of BAAN IV. Bymerging the GLO derivation, the GLO features are available for all users worldwide. Some ofthese features are parameter-controlled, giving the user the option to use specific features. Inother cases, all the features are made generally available. For those features that are notparameter-controlled, the user can select to use a feature by entering additional static data orby performing the additional steps that are feature requirements.

By merging GLO into the BAAN IVc standard, the following new functionality is added:

n Sales tax− Destination tax− Recalculate tax code after change of delivery and/or postal address− Tax rates by tax authority− Tax exemptions− Level of tax calculations on documents− Decimal precision of tax percentage− Purchase tax expense− Multi-level use tax− Tax provider



1 - 8

n EDI− Purchase order changes− Purchase order change acknowledgment

n Distribution− Change type and change reason codes− Acknowledgment codes− Customer order number and position− Sales order acknowledgments by exception

n Finance− Journal import− US check format− 1099 reporting

n Transportation− Rate calculation− Hazardous material regulatory documents (U.S.)− Damaged goods tracking

The new functionality listed above is described in the following sections.

1.7.1 Sales tax enhancements (formerly GLO functionality)

BAAN IVc introduces the following Sales tax functionality (this functionality wasincorporated into GLO and now merged with BAAN IVc):

Destination Tax

In BAAN IVc, tax rates can be determined based on postal code or zip code for one of thefollowing:

n Destination address (default)n Origin (the warehouse address)n Invoice address

Exceptions can be defined by location or by country, supplier/customer, item group, project,budget, and item. The exceptions are used to derive the default tax code for sales and purchasetransactions.

Taxes can be calculated on the net amount (single tax rate) or the net amount plus other taxesas defined (multiple tax rates). Users can define a maximum tax amount which represents anupper limit for a tax code. A tax base amount can also be defined which can be used tocalculate progressive tax. If the tax base amount is used, the user can define a tax percentagewhich is applied to an amount in excess of the tax base amount.

For Canadian users, BAAN IVc includes the ability to calculate tax based on the net amountplus other tax to accommodate cases where PST is calculated over the net amount and theGST.

Recalculate tax code after change of delivery and/or postal address

When using destination tax, the delivery and postal addresses are used to determine theappropriate tax code to be used to calculate the tax. If there is a change in either of theseaddresses, there is a potential need to reevaluate the tax codes assigned to existing order lines.Because tax codes can be overridden by the user, it cannot be assumed that the tax codesshould be automatically reevaluated upon a change to the postal and/or delivery addresses.



1 - 9

Instead, BAAN IVc prompts the user to determine if the tax codes should be reevaluated if thepostal and/or delivery addresses are changed.

If the user responds to reevaluate the tax codes, the tax code for each existing order line willbe reevaluated based upon the new postal and/or delivery addresses.

Tax rates by tax authority

BAAN IVc has been enhanced to facilitate the maintenance of tax rates. A new utility isavailable which provides the ability to update tax rates, maximum tax amounts, tax baseamounts, and excess rates by tax authority.

Tax exemptions

BAAN IVc tax processing has been enhanced to enable exemption processing for nontaxprovider users. Tax exemption information such as exemption certificate numbers, user-defined reason codes, and expiration dates, can be recorded by customer and tax authority.The tax exemption information is used by BAAN IVc when calculating tax. If a validexemption certificate exists for a customer and tax authority, no tax is levied when computingthe tax. For auditing, reporting of exempt transactions with associated reason codeinformation is available. Tax exemption information such as the tax authority and certificatenumber can also be reported on external documents (controlled by country).

Level of tax calculation on document

In some environments, it is a legal requirement that all taxing levels are stated explicitly onorder documents. For example, it is a legal requirement that GST and PST are reportedseparately in Canada. To accommodate this need, the ability to print tax in either summary orin detail on order documents is available.

The level of tax to be printed is defined by country. When printing tax detail, the tax isaccumulated and reported by tax authority group. For tax provider users, the tax issummarized and reported by federal, state, city, county, and district components for US taxesand GST and PST/QST within a province for Canada. The total amount of tax is printed inthe footer of the documents for both the detail and summary options.

Decimal precision of tax percentage

Many tax authorities levy a tax rate with up to three decimal places of precision such as 8.025.To properly report the tax rate, BAAN IVc has been enhanced to report the tax rate with up tothree decimal places of precision.

Purchase tax expense

In the US, it is customary for tax on purchases to be charged to the same accounts as thegoods themselves. For example, tax on purchases for assets is included when valuing theasset. To account for tax on purchases properly, the ability to override the tax accounts witheither a balance sheet or an income statement account for both single and multi-level tax isavailable.

An “expensed” indicator on Tax Codes by Country determines how the tax will be handled.Tax will be expensed when this field is set to Yes. If it is set to No, tax will be charged to thepurchase tax account on the tax code.



1 - 10

For miscellaneous purchase invoices with tax calculated at the transaction line level, tax isexpensed immediately. The account and dimensions for each line are the same as those usedfor purchase on that line. It is still possible to override the account and dimensions for anindividual line in the case of an exception.

For matched purchase invoices with tax calculated at the header and a expensed tax code, thetax amount goes to an interim purchase tax account and dimensions at the time of registrationThe interim tax account and dimensions are specified on the tax code. The tax amount is thenreclassed at the time of approval. Tax is calculated based on the tax code of the relatedpurchase receipt and charged to the account and dimensions used originally for the purchasereceipt transaction. In the case of a purchase receipt for a cost item belonging to the itemgroup for cost items to be specified, the tax will be reclassed to the same account anddimensions that the cost item was reclassed to.

Any variance between the purchase invoice header tax amount and the tax amount calculationbased on the matched purchase receipts, will be posted to the variance account specified inACP parameters.

Multi level use tax

Within BAAN IVc, tax codes can be identified as shifted, meaning that the burden forpayment of the tax is shifted from the seller to the buyer, otherwise known as consumer usetax.BAAN IVc tax processing has been enhanced to provide the ability to properly track theshifted tax for environments with multi-level tax withholding requirements. multiple taxlevels can now be defined for shifted tax codes.

Additionally the Tax Provider interface has been enhanced to support Orbix for thecommunication between the Baan application and the Tax API.

Tax API with Orbix

Prior to BAAN IVc, the Tax Provider interface relied on "mailboxes" to pass data to the Baanapplication and the Tax API. The Tax API interface will support the use of Orbix forcommunication between the Tax API and the Baan application with BAAN IVc.

Orbix is a CORBA 2 compliant Object Request Broker provided by Iona Technologies. TheOrbix product facilitates the communication of pieces of software through a robust, crossplatform, and distributed computing model. Orbix integration is part of Baan's overallmiddleware strategy and provides an industry standard way to connect Baan with outsidepackages.

In the past, the Tax API and Baan application server were required to run on the same host.With BAAN IVc, an organization can run the Baan application server and TAX API (and thecorresponding tax provider software) on differnet systems. Iona's Orbix will manage thecommunication aspects of the integration in a seamless and transparent manner. This featureis particularly helpful where multiple application servers are used, the Tax software can resideon a single server. Management and administration costs will be decreased as a result.

Orbix provides a variety of ways that the Tax API can be started. This helps to allocateadequate resources for tax calculation and allows for greater efficiency of the Tax API. Orbixallows for a tax provider to be started for each user, a number of Tax APIs started for all usersto share, and other variations. Orbix provides the ability to add additional security measuresas well.



1 - 11

1.7.2 EDI

BAAN IVc includes two new messages for EDI:

1 Purchase Order Change Document2 Purchase Order Change Acknowledgment Document

Modifications have also been made to the existing order acknowledgment and purchase ordergeneration.

nn Purchase Order ChangesThis document (the ANSI X12 860 transaction set, or the UN/EDIFACT ORDCHGmessage) allows customers to send changes to previously submitted purchase orders totheir suppliers.

For outgoing order changes, users are given the flexibility to control which changes totransmit through EDI, via the assignment of change codes.

For incoming order changes, users are given flexibility in how to handle the update ofincoming changes into BAAN IVc, by specifying which type of changes are allowed, aswell as which fields can be updated.

nn Purchase Order Change AcknowledgmentsThis document is sent by the supplier in response to a customer-initiated purchase orderchange, or to notify the customer of supplier-initiated changes. Similar to the currentlysupported order acknowledgment, this document conveys to the customer the currentstatus of the order data by the supplier.

In some environments, the currently supported order acknowledgment (the ANSI X12 855transaction set, or the UN/EDIFACT ORDRSP) is used to acknowledge all activity againstan order. It is used in response to newly received orders as well as order changes. In otherenvironments, the currently supported acknowledgment is used only in response to newlyreceived orders; and, the newly supported order change acknowledgment (the ANSI X12865 transaction set) is used in response to order changes. BAAN IVc provides users withthe ability to control, by trading partner, which type of acknowledgment (the orderacknowledgment or the order change acknowledgment) to send in response to orderchanges.

In addition, acknowledgment codes, describing the changes or response to changes to thesales order, can be referenced on the outgoing EDI acknowledgment documents.

n Sales Order AcknowledgmentPrior to BAAN IVc, EDI order acknowledgments included all order lines regardless of theacknowledgment print method. For BAAN IVc, EDI order acknowledgments reflect onlythose order lines that have been selected based on the acknowledgment print method andnow mirror the printed document.

n Purchase Order GenerationVisibility is provided at the purchase order header to indicate that the purchase order hasbeen generated via EDI.



1 - 12

1.7.3 Distribution (formerly GLO functionality)

BAAN IVc introduces the following Distribution functionality (this functionality wasincorporated into GLO and is now merged with BAAN IVc):

Sales (SLS)

Several changes have been made to the Sales (SLS) module within BAAN Distribution insupport of the new BAAN IVc EDI features. Although these features have been added tosupport the new EDI features and functions, they are also available to non-EDI users. Thesechanges include:

n Change type codes and change reason codes maintained for sales order changes.Change type codes and change reason codes can be maintained when making sales orderchanges. Change type codes indicate the type of change made to the header or line. Thechange reason code indicates the purpose or reason for the change. A parameter allows theuser to control automatic prompting for the change type and reason codes when makingsales order changes. These codes are also stored within sales order history.

n Acknowledgment codes maintained.An acknowledgment code can be assigned to a sales order header or line and is used toindicate the response to a new order or customer initiated change, or to indicate a supplierinitiated change. The acknowledgment code can be manually assigned or systemmaintained. Acknowledgment history is logged when the acknowledgment is generated.

n Visibility of customer purchase order number, line number, and sequence number.The initiating customer purchase order number, line number, and delivery sequencenumber can be maintained and tracked for each sales order line.

n Ability to generate Sales Order Acknowledgments on an exception basis.Prior to BAAN IVc, an order acknowledgment was generated for all sales order changesfor sales orders requiring acknowledgment. The ability to define which sales orderchanges require acknowledgment is available in BAAN IVc. The user can indicate, forexample, that a change to the delivery date requires acknowledgment but a change to theterms of delivery does not.

n New report Print Sales Orders to be Acknowledged.A new report is available to provide visibility regarding orders to be acknowledged. Thisreport is used to indicate pertinent order information, such as the change type, changereason, and acknowledgment code, which can need to be reviewed prior to generation ofthe acknowledgment. This is particularly useful for EDI orders.

Purchasing (PUR)

Several changes have been made to the Purchasing (PUR) module within Distribution insupport of the new BAAN IVc EDI features. Although these features have been added tosupport the new EDI features and functions, they are also available to non-EDI users. Thesechanges include:

n Change type codes and change reason codes maintained for purchase order changes.Change type codes and change reason codes can be maintained when making purchaseorder changes. Change type codes indicate the type of change made to the header or line.The change reason code indicates the purpose or reason for the change. A parameterallows the user to control automatic prompting for the change type and reason codes whenmaking purchase order changes. These codes are also stored within purchase order history.



1 - 13

n Acknowledgment codes maintained.Acknowledgment code history can be logged manually, or automatically via EDI, to trackthe supplier’s response to the order and subsequent order changes.

n New report Print Purchase Orders to be Printed.A new report is available to provide visibility regarding orders to be printed. This report isused to indicate pertinent order change information, such as the change type and changereason, which can need to be reviewed prior to printing the Purchase Orders. This isparticularly useful for EDI orders.

1.7.4 Finance (formerly GLO functionality)

BAAN IVc introduces the following funcionality in Finance (this functionality wasincorporated into GLO and is now merged with BAAN IVc):

Journal import

A journal transaction is automatically created from external data using the Journal Importfeature. Data from ASCII files is transferred to Journal Import tables. The Journal Importtables are then accessed by the Journal Import function to create the journal transaction. Adefault exchange scheme is provided for loading the ASCII file into the Journal Import tables,but other methods can also be used.

The date format and decimal placement for converting imported data is specified bytransaction type. Only transaction types with a transaction category of “journal” are used forthe Journal Import.

An ID number is used to uniquely identify the batch and prevent the same batch from beingimported twice.

The Journal Import Status Report, which shows the outcome of each journal import attempt,is printed automatically. If no errors exist, the batch will be given a status of processed andthe journal can be maintained and finalized in the same manner as manually enteredtransactions.

If any errors exist, they are itemized on the Journal Import Status Report. The batch will begiven an error status and should be reimported with a new ID number after the errors arecorrected.

US check format

BAAN IVc has been enhanced to provide payment processing using the US format for checks.The US format can be accessed using report group 15. The US format includes, among otherchanges, the ability to express the amount of the check in words.

1099 Reporting

Based on requirements from the Internal Revenue Service, BAAN IV c has been enhanced toprovide 1099 reporting. The 1099 form may include a number of types of payments andshould include any applicable state and federal taxes withheld. In addition to the ability toprint 1099s on a preprinted form, a 1099 Invoices Paid report provides a complete listing ofall payments made to vendors for the year.



1 - 14

Users may define a payment method for 1099 payments that includes the followinginformation:

n recipient’s federal identification numbern federal reportable (yes/no)n state reportable (yes/no)n income tax reporting site (tax region)n income tax type (type of category the payment represents)

1099 magnetic media

The Internal Revenue Service (IRS) requires information regarding so-called qualifyingpayments made to suppliers be submitted to the IRS for each year. The data submittedincludes detailed information regarding the payer (the person making the payments); thepayee (the person receiving the payments) for which a return must be filed, and the amountpaid classified by type. Payment information may be reported on forms or on electronic media.The IRS requires payers with 250 or more payees to file electronically.

BAAN IVc 1099 filing capabilities have been enhanced to allow the ability to file 1099-MISCelectronically. Additional information is maintained, including information regarding thepayer and the payee necessary to satisfy the magnetic media reporting requirements.

1.7.5 Transportation (formerly GLO functionality)

BAAN IVc introduces new funcionality in Transportation (this functionality was incorporatedinto GLO and is now merged with BAAN IVc). The enhancements fall into the followingcategories:

n Rate calculationn Documentsn Subcontractor performance

Rate calculation

Rate structures are defined in various ways by different freight carriers. Some base their rateson miles traveled while others use a zoning system. Multiple methods of rating will now beallowed for the same transport type and service level. These methods can be grouped into thefollowing subcategories:

n Zone definitionZones can be defined based on zip codes or cities. They can be defined differently for eachsubcontractor. TRC parameters allow the user to define a search sequence for a zonedefinition by city or by zip.

n Rate codes and service levelCurrently, rate codes and service levels are used to indicate shipping priorities. Thisexisting functionality has been extended into the transport rate code tables for customer,price group, price list, general transport rate codes, and subcontractor rate codes. Servicelevels are now integrated with zones or distances and transport type for both transportorder processing and costing purposes. TRC parameters allow the user to define a searchsequence priority for selecting service levels by item, customer, or subcontractor.



1 - 15

n Rate amountsRate amounts can be based either on distances or zones based on the subcontractor’smethod for rate calculation. Rate amounts can now be defined based on quantity shippedand zone of operation. Thus the user can have rate amounts by quantity and distance or byquantity and zone, depending on the rate code being used. TRC parameters allow the userto define a search sequence priority for rate amount allocation, either distance basedamount or zone based amount.

n Transport order amount calculation and costingThe user is allowed to search and replace rate codes using the rate code, rate amount,service level, and zone or distance applicable. Rate amount calculations at the order leveland costing of transportation lines can also be done based on such criteria.

Hazardous material regulatory documents (North America)

While the general philosophy of the BAAN products is to have the users create any neededreports which are not available in the system, there are certain regulatory requirements fortransport documents in North America which must be met. Reports provided in BAAN IVcmeet some of these requirements:

n Hazardous materials reportsThis feature is for informational reporting purposes only. The US Department ofTransportation has ruled that certain reporting is required when a company is transportinghazardous materials. The ability to identify and report required information related to thegoods which fall under this requirement is provided.

The scope of this feature is limited to those requirements which cannot be handled throughthe use of item or order line text. Information related to hazardous items will be stored innew tables and reported on shipping documents.

Transportation shipping documents will provide a special column marked HM foridentification of hazardous materials. In addition, special hazardous material informationwill be printed in the required format.

Damage goods tracking

It is necessary to evaluate the performance of the subcontractors used for freight delivery inorder to identify problem trends and determine whether they should continue to be used in thefuture.

Information related to goods damaged in transit will be stored by transport order stop line. ADamaged Goods report will also be available. This feature is for informational purposes andprovides no operational link back to inventory or the original order for the damaged goodsrejected or replaced items.



1 - 16


2 - 1

This chapter describes the new funcionality in BAAN IVc BackOffice. The following topicsare covered:

n Intel NT supportn Alpha NT supportn License manager NTn Update facilityn Conversion facilityn Installation improvements on Informixn Oracle NT supportn SQL Server performance improvementsn Auto start mechanism

The sections below describe the new functionality in the BAAN IVc BackOffice.

2.1 Intel NT support

As part of the BAAN IVc release of BAAN BackOffice the support for the Intel NT processoron all major platforms is made available.

2.2 Alpha NT support

As part of the BAAN IVc release of BAAN BackOffice the support for the Digital Alphaprocessor is made available.

2.3 License manager NT

One of the last parts of the porting from UNIX to NT was the license manager. This port hasnow been finished, providing the same license manager functionality to NT as is available onUNIX.

2.4 Update facility

Due to the different installation procedure on NT, also updates to the software have to behandled in a different way. To this end a new tool has been built which facilitates theinstallation of updates.

2.5 Conversion facility

Our pilot customers used BAAN IV BackOffice on BAAN IVa, or BAAN IVb. Therefore theyneed a conversion to BAAN IVc. Due to the different technical nature of the Windows NTenvironment, some extra development was necessary to accomplish this. The conversionfacility has been built in such a way that the functionality is the same as on UNIX, howeverthe technical execution of the conversion differs somewhat.

2 BackOffice support

2 - BackOffice support


2 - 2

2.6 Installation improvements on Informix

In the BAAN IVc release the following changes are implemented in the installation process ofBAAN IV BackOffice:

n A screen will be displayed providing the following installation options:

− Install Informix Connect 7.22 for Intel NT− Install Informix Online-Dynamic Server 7.22 for Intel NT− Install BAAN IVc Client− Install BAAN IVc Server− Uninstall BAAN IVc− Uninstall Informix OnLine Dynamic Server 7.22 for Intel NT− Help− Exit

n Automatic configuration of the Informix dbspaces:

− Creation of a root dbspace of 100MB

− Creation of 5 logical logs of 40MB each

− Removal of the logical logs in the root dbspace

− Removal of the physical log out of the root dbspace and creation of physical logs of atleast 50MB.

− Removal of the temporary space out of root dbspace.

− When the disks are not stripped, the table and index data are stored in differentdbspaces stored on different physical hard disks. The physical and logical logs are alsostored on different hard disk.

− When there are only 4 disks, the temporary dbspaces along with physical and logicaldbspaces are stored on one single disk.

n Automatic execution of the SQL statement UPDATE STATISTICS after posting alltables to the database.

n Automatic tuning of Informix parameters.

2.7 Oracle NT support

As part of the BAAN IVc release of BAAN BackOffice the support for the Oracle database ismade available for the first time. The following major points have been addressed:

n Porting of the Oracle driver for Intel NTn Porting of the Oracle driver for Alpha NTn Creation of a rapid installation procedure n Support for the Oracle driver in the DBA utilities



2 - 3

2.8 SQL Server performance improvements

In BAAN IVc the BAAN IV database driver is using stored procedures instead of DynamicSQL for some queries to improve performance and reduce SQL Server’s CPU utilization.

On the application side, there are several changes implemented to improve the performance.For more information about these changes, refer to the section Performance improvements,earlier in this document.

In addition, in BAAN IVc there are improvements that have a positive impact on theperformance for all databases. One improvement has the bshell (client) do a check during anupdate request to confirm that the record being updated has actually changed (from thatoriginally selected) and will not send the update request to the driver if it has not beenmodified. This reduces locking, ipc/network traffic, and database server activity. Thisprimarily benefits the batch sessions.

Another improvement is a change to the Application Locks code for Sales and PurchaseOrder Maintenance to reduce activity and hence lock serialization.

2.9 Auto start mechanism

A new feature is the auto start mechanism. This means that as soon as you have inserted theBAAN CD in the CD-ROM drive the setup procedure will automatically start. It is no longernecessary to use the Windows Explorer to manually start the setup program.



2 - 4


3 - 1

This chapter describes the new funcionality in the BAAN IVc Tools. The following topics arecovered:

n Function Server DLLn Performance improvementsn Sybase (Controlled Release)n Exchange improvementsn Distributed Data Collection (DDC)n Orbixn Multibyte on Unixn Enhancements with Windows clientsn Performance improvement refintn Audit improvementsn Permissions on outer joins

3.1 Function Server DLL

In BAAN IVc a programming interface is implemented within the standard program. Thisinterface gives external applications access to the same business transactions that users havewhen they are using BAAN IVc. It is implemented by defining primitives in the standardprogram, which must be called via a BMS protocol.

This architecture needs an additional 3GL program to send messages to the standard programwhich was not added in the initial implementation. Because there is a strong need to be ableto call this functionality in the standard program directly by non-Baan applications, someprocesses or functions have to be implemented to provide a high-level usage of the newfunctionality in the standard program. This is called the application function server.

The following picture shows the relations between the different design entities.

Standardprogram

APIhandler

Externalprogram

SessionDLL

SessionDLL

ORBcall

API

Application function server

In the picture above, only external programs are calling the session DLLs. It must be possible,however, to call the DLLs from other BAAN programs as well.

3 Tools development

3 - Tools development


3 - 2

3.1.1 Design approach

To call BAAN Functions via the object request broker (ORB), the functions must be availablein a DLL. One problem with such a DLL is that no data can be stored to use in a subsequentcall. So there must be a separate process called by the DLL which stores some data, the APIhandler. This process must call the API in the standard program.

There must be a generator available to create DLLs by session. The advantage of thisapproach is that you can specify obvious function names, say put_Customer(value) instead ofput_field(“tccom010.cuno”, value), and checks if the right data type is compiled.

Messages can be given by the API in the standard program indicating success of a command;these messages are given in the reply of the command after the command is executed. To sendthis result back to the calling process, function calls must be synchronous.

3.2 Performance improvements

In the BAAN IVc release the following performance improvements are implemented:

nn Short locking time of a database rowThe time a row is locked by a single user is important, because updates done by otherusers will also be done by putting a lock before update. So, to decrease the chance ofhaving a row locked by another user, the time of a locked row should be as short aspossible. This topic is most relevant for databases working with page level lockingmechanism.

In releases before BAAN IVc, a part of the programs were written in such a way, that arow was locked from the beginning to the end of a Logical Transaction. Now, almost all ofthese programs are improved, doing the row lock just before the real update.

nn Better queries done by standard programThe standard program will fire more performance friendly queries to the database. Alsothe number of the queries has been reduced. Further display of fields is done in a moreefficient way. This means that each user will less load the system, so a better performanceis guaranteed!

nn Bonus ticks in bshell CPUBecause of the fact a user can have multiple tasks running on one connection, it isimportant that when a database transaction is started in one task, this task should befinished as quick as possible. For this, a mechanism has been build for this to havedatabase transaction as short as possible. This have been accomplished by giving the taskwith the database transaction enough CPU ticks to finish it’s logical transaction.

nn Update action skipped when row not modifiedThe bshell (client) does a check during an update request to confirm that the record beingupdated has actually changed (from that originally selected) and will not send the updaterequest to the driver if it has not been modified. This reduces locking, ipc/network trafficand database server activity. This must benefits the batch sessions.

nn Queries level-2An optimization in the level-2 driver is that queries in the level-2 driver are no longersplit unnecessarily.

nn Parsing in level-2 driver optimizedThe level-2 driver is optimized in query constructions with company number. The numberof times that the the query had to be parsed is significantly reduced.



3 - 3

nn Reduced number of database connectionsVarious sessions are actually read-only sessions. These sessions can now be identified bythe bshell and the standard program. In these cases only a single connection needs to bemade to the database, which enhances performance by reducing the use of machineresources like CPU and memory.

n Improvements in switching to companies

n Improvements in store.occ.min and store.occ.max

n Improvements in query.extension

n Improved function to retrieve session descriptions

n Improved graphical display of fields

n Improvements in checking reference fields

3.3 Sybase (Controlled Release, restricted shipment)

In BAAN IVc, support for the Sybase SQL server version 11.0.2 database is introduced. TheSybase Open Client Client Library/C version 10.0.3 is used for the first version of the Sybasedriver. The driver will be released for restricted shipment in BAAN IVc. The database driveris initially limited to SUN and HP UNIX platforms.

The Sybase driver is a level I driver, which means that it selects on one table at a time, not byusing the joins in database. It creates hash columns for indexes. Client library cursors andstored procedures are used for selects and dynamic SQL functionality PREPARE andEXECUTE is used for inserts, updates, and deletes.

The Sybase driver supports the storage of multibyte data in native format in the database.

The current release of Sybase SQL server (version 11.0.2) does not support bidirectionalindexes (bidirectional index means that the same index is used for ascending and descendingorder queries). Hence, the driver uses double hash columns for each index. In other words, foreach index defined by the application, two hash columns are created in the table, and an indexis created on each of them. A future release of Sybase SQL server (version 11.5) will supportbidirectional indexes. The driver has been constructed to take advantage of this feature whenit is enabled in the database.

The current release of Sybase SQL server (version 11.0.2) does not support row level locking,so concurrency within the Baan application is affected to some extent, limiting the currentimplementation to a controlled release status. A future release of Sybase SQL server willsupport row level locking.



3 - 4

3.4 Exchange improvements

The Exchange module offers the following important enhancements:

n Exchange based on audit:When you are exporting and importing data based on audit, data is read from the auditfiles. In BAAN IVb it was sometimes hard to determine the correct sequence and groupingof database actions logged in the audit files. This could result in reference errors.

In BAAN IVc a number of changes have been made in the audit server and the Exchangemodule. Exchange is now transaction-based: the actions that have been executed on thesource database within one transaction are also imported into the target database withinone transaction. The order in which the transactions are executed at the target database isthe same as the order in which they were executed at the source database, with anaccuracy of 1 second.

n Text handling:The following enhancements in text handling are implemented in BAAN IVc:

− When exchanging multiline texts, Exchange in BAAN IVb could not handle deletedtexts. When a text is deleted or unlinked from a record in BAAN IVc, a specific flag iswritten to the ASCII file during the export from the source database. When this flag isread while importing, the text is also unlinked from the record in the target database.

− In BAAN IVb the text tables (tttxt...) could not be exchanged properly. Exchangecould not overwrite already existing text and could not handle the new line charactersin table tttxt010. In BAAN IVc text tables can be exported and imported just like anyother BAAN table.

− In the BAAN tools you can specify a range of text numbers per text group. New textscreated receive a number that is in that range. This feature can be used to select arange of texts to be exported or imported using Exchange.

n A number of other enhancements have been made, the most important ones being:

− During exporting, you can use conditions to determine what records should or shouldnot be exported. This decreases the size of the ASCII files created. You can also usedthem when exporting is based on audit.

− Using regular export and import you can now import data directly from the directorywhere the data was exported to.

− When importing or exporting table fields of the multibyte string type, you can domulti-byte conversions.



3 - 5

3.5 Distributed Data Collection

DDC has been enhanced to support the Microsoft Windows NT operating system. Thisenhancement will affect both the UNIX and NT versions of DDC. The primary modificationswere in the communication layer. Both the 4GL and binary code have been converted fromUNIX message queues to mailslot. The mailslot architecture is supported on both the UNIXand NT environments. NT makes a strict difference between the server (program that createsand reads the mailslot), and the client (program that opens and writes to the mailslot). Aclient can also act as a server, but for a single message queue the relationship must be clearlydefined.

3.6 Orbix

BAAN IVc has implemented an Object Request Broker (ORB) based on the CORBA 2.0implementation of the company Iona and their product Orbix. This means that BAAN 4GLobjects can be CORBA clients or CORBA servers. This product will only be available forselected customers and also on a limited number of platforms (Sun and HP).

3.7 Multibyte on Unix

In BAAN IVc a number of enhancements have been done on the multi-byte support.Especially some of the Japanese needs have been answered. The most important being:

n Support of hankaku katakanaKatakana is the Japanese script, which is mostly used to spell words borrowed fromforeign languages. Half-width Katakana characters take up half the display space of thefull-width Katakana characters. Therefore, more information can be displayed in the samedisplay space.

n Support of Shift-JIS

n Japanese PostScript printingJapanese can be used in PostScript printing for Orgware, reports and user documents.

n Improved sorting of different character sets

3.8 Enhancements with Windows clients

The introduction of BAAN IV BackOffice has had several spin-offs which are now alsoavailable in BAAN IVc if one uses the BAAN Windows client.

n Possibility to convert report output to HTML (the Internet format for texts).

n Local printing from the PC (using BWprint), meaning that you can have your outputprinted directly on you own printer connected to your own PC.

n Windows help. The help format (not the contents of course) can be shown either in thestandard BAAN way or in the standard Microsoft Windows way.

n Possibility to use Notepad as text editor.



3 - 6

3.9 Performance improvement refint

Refint6.1 has been considerably enhanced for performance. The resetting of referencecounters has been enhanced considerably by making use of SQL update. Also the restoring ofreference counter values has been greatly enhanced which has reduced the IO considerably.

3.10 Audit improvements

Along with the Audit and Exchange improvements, UTC (universal time code) is now beingstored in the audit log files as the timestamp of a transaction. This solves timezone problems.When replaying transactions, not only the order of the transactions is identical, but also theorder of updates within a transaction.

3.11 Permissions on outer joins

Permission handling for queries with outer-join operations is changed. When a query containsan outer join operation (a ‘refers to’ construction that is not of type ‘unref skip’) and the userdoes not have ‘read’ permission for some of the records, then when the child record does notmatch with any of the parent records the entire row is still returned. In the previous releasethese rows are not returned.


4 - 1

This chapter describes the new funcionality in the BAAN IVc Internet support. The followingtopics are covered:

n Introductionn HTML 1.0n BAAN IVc Internet appletsn Electronic Shopper

4.1 Introduction

The Internet interface, already available in the BAAN IV BackOffice pilot product, is in theBAAN IVc release also available for the UNIX platforms. The Internet Netserver solutionmakes it possible to connect to the BAAN product through Internet.

BAAN IV Internet applications, development tools, and general Internet connectivitytechnology offer a solution that can be customized to meet a customer’s individual Internetneeds. Using the BAAN IV Internet applications you can access a repository of enterprise dataand execute transactional logic to immediately retrieve information. The BAAN IV Internetsolution builds on its proven architecture and on the software components that customers useto run their business.

4.2 HTML 1.0

HTML 1.0 provides an intuitive, graphic, report output for any Baan IV report based on theHTML standard. The user selects the device HTML file type in the Select Device sessionwhen running a report. The report is then delivered as an HTML file ready to be viewed in abrowser or transported over the web, using such methods as Push Technology. Customizationof the report allows the user to specify the use of a corporate logo, a division or companyname in bold type, and font sizes for the body of the report. Additional navigation featuresallow users to quickly view various pages of the report. The key features can be summarizedas follows:

n Producing HTML formatted reportsn Selecting HTML reports from Select Device Formn Embedding corporate logo in reportn Providing navigation through a multiple page report

4.3 BAAN IVc Internet applets

With BAAN IVc, Baan delivers a suite of visually enhanced Java applets designed for theInternet. These applets provide the ability to link customers, business partners, members ofthe supply chain, and internal users via the Internet. The Java applets that comprise the BaanInternet solution are delivered on HTML pages to provide easy setup and distribution. Agraphically interface enhances the user-friendliness. Using a standard http server a user canconnect to the BAAN system via the Internet.

4 Internet support

4 - Internet support


4 - 2

The following applets make up the Internet solution for BAAN IVc.

n Employee information with picturen Supplier lookup/updaten Customer lookup/updaten Generate sales information table/graphn Display inventory by item, company, and warehousen MPS available to promisen Product configurationn Order status lookupn Item lookup

4.4 Electronic Shopper

With BAAN IVc, a Microsoft Commerce Server ™ (MCS) prototype store, the ElectronicShopper, has been created which communicates with several modules within BAAN. Theintegration includes the exchange of static data such as customers and products as well asdynamic data such as orders and order status. Static data may be transferred from BAAN tothe Electronic Shopper, product catalogs created, and orders may be created and subsequentlycommunicated to BAAN.

4.4.1 Administration

The Electronic Shopper provides the ability to communicate with BAAN to transfer staticinformation such as customer and product information. Tables created within Microsoft SQLServer ™ are available to store and maintain this information. Moreover, additionalinformation not maintained within the BAAN system, such as product images, E-MailAddresses, and customer passwords may be maintained. A browser-based screen is providedwithin the Electronic Shopper to maintain the additional information.

For BAAN IVc, Item Master information will be passed directly into the Electronic Shopperto populate the product catalog. Items can be maintained in BAAN and periodically updatedto the Electronic Shopper based on Enterprise requirements. Information passed to theElectronic Shopper includes product, product description, and pricing information.

Shopper information is maintained which includes customer information from BAAN andadditional information required by the Electronic Shopper. Customer-related informationsuch as Customer Number, default Delivery Address, and default Postal Address aretransferred from BAAN to the Electronic Shopper. Additional information such as thePassword, E-Mail Address and Shopper ID are maintained within the Electronic Shopper.

4.4.2 Shopping Experience

Online shoppers will be presented with a login form. The shopper will be expected to enter alogin code and password. Only customers who exist in the customer data of the BAANCustomer Table are allowed to place orders.

After login validation, a shopper is presented with various product catalogs from which tobrowse. The shopper can browse the categories and sub categories of the catalogs to get to theproduct page. The product page will display product information along with the picture of theproduct. Product information shown includes the product description, price, unit of sales, andmore.



4 - 3

While browsing the catalog, shoppers may select items to be purchased and may indicate thequantity and requested date of the items to be purchased. The shopper may browse the catalogadding additional items to the basket. In addition, the shopper can view and maintain theinformation previously added to the basket. The items and order information are maintainedin the order basket until the shopper clicks on the Submit Button indicating that the ordershould be created.

When the shopper is done browsing and selecting the items to purchase, he may wrap up hisorder by using the Submit Button. The default delivery and postal addresses will be displayedand the shopper will be given the option of changing either of the default addresses. Uponacceptance of the order information, an Electronic Shopper order number will be assignedand the order data will then be transferred to BAAN Sales (SLS).

4.4.3 BAAN sales order generation

Baan will use the standard EDI format to transfer the order information from the ElectronicShopper to BAAN Sales (SLS). An Electronic Shopper component creates an EDI order inthe format expected by the BAAN EDI module. This component is placed in the Accept stageof the Order Pipeline Process within MCS and is automatically executed upon acceptance ofthe order by the shopper.

4.4.4 Sales order status

Once the order has been created and accepted by the BAAN system, the order status and theBaan Sales Order number will be returned from BAAN to the Electronic Shopper usingBAAN EDI. The order status indicates the acceptance of the order.



4 - 4


5 - 1

This chapter describes the new funcionality in BAAN IVc Orgware. The following topics arecovered:

n DEM enhancementsn Workflow (version for demo’s and preparation for BAAN V)n BAAN Data Navigator

5.1 DEM enhancements

The following enhancements are built in the BAAN IVc Enterprise Modeler:

n Windows applications can be linked to a business process activity and started from thebusiness process activity and the dynamic menu browser. These Windows applications canbe defined in the Maintain Helper Applications (tgwms1140m000) session (new), and canbe linked to an activity by using the Maintain Business Process Activities(tgbrg5122m000) session (changed). The argument is the file which is used by theWindows application, for example, a Microsoft Word document.

n In BAAN IVc the current project model and phase can be stored by user. The currentproject model and phase by user is necessary for the dynamic menu browser, because theroles of the user and authorizations are stored by project model. Furthermore, you canmodify the version for a range of users at once by using the Range of Users button. To beable to do so, the Project Model and Optimization Phase fields are added to the MaintainCurrent Version by User (tgbrg1110m000) session. The current project model and phaseby user is automatically set in the Generate User Dialog (tgbrg4250s000) session if adynamic menu is generated for a user.

n A dynamic menu browser can be used as interface for end users, and a similar browser isused to display utility structures. The BAAN IVa/b standard menu is not company specific.However, the business processes by user are company specific. In the financial companyother business processes are allowed then in the logistical company.

Therefore we now use our own Dynamic Menu Browser (tgbrg4260m000). This newbrowser reads the current version and project model by user and the authorizations of theuser by company.

Only the business processes a user is authorized for in the current company are placed inthe browser. The user can change the current company with a special option. If the currentcompany is changed the browser interface is started in a different window and only theroles and business processes of the new company are shown.

The sessions, utilities and nested business processes in a business process are shown asleaves of a business process. Business processes, sessions and other applications can bedirectly started from the browser after a button press. Roles, business processes, utilities,sessions and other applications have different icons. Help of business processes andsessions can also be asked from the new browser.

n Enterprise Modeler data can be exported to a common file format for spreadsheets. In theprint sessions you can now print to a data format. A file can be selected as output device.The extension of the file can be filled in as csv, which is a common data format. The filecan be placed on a PC using ftp. If the csv extension is associated with Excel in Windows,Excel will be started automatically when you click the file.

5 Orgware development

5 - Orgware development


5 - 2

5.2 Workflow (demo version)

BAAN IVc Workflow Management can be used to prepare for BAAN V workflow, by meansof creating the workflow enabled business processes and by getting acquainted with theavailable functionality. Please note that the BAAN IVc Workflow Management is notintended for operational systems.

Workflow management (WFM) aims at improving productivity and quality of administrativeprocesses (building information products) by applying logistics principles and state-of-the-artinformation technology.

Workflow management provides a mechanism for managing and controlling the flow of workby monitoring such logistic aspects as workload, capacity, throughput times, work queuelengths, and processing times.

Information-intensive business processes often have very long throughput times, although theactual processing time is relatively short. Having a Workflow management system aninformation system can streamline the work flow.

Workflow management provides the following benefits:

n A Workflow orientation on administrative processes helps an organization to move from atraditional, functional organization to a more process-oriented organizational structure.

n A Workflow orientation helps an organization to focus primarily on the customer's needsby defining Workflows starting and ending at the customer.

n Workflow management helps an organization to identify bottlenecks in the processexecution by monitoring the progress per process step.

n Workflow management helps to reduce processing times, queue lengths, and hencereduces the throughput time. As a result, the costs are reduced and at the same time thecustomer service and flexibility are improved.

n A Workflow management systems provides an infrastructure to integrate all BusinessApplications (such as ERP, LIMS, Shop Floor Scheduling, and so on).

With BAAN V Baan will provide an integrated solution for Business Modeling, WorkflowManagement, and the needed ERP functionality to fully support companies in achieving theirobjectives with respect to customer satisfaction, productivity, and costs.

5.3 BAAN Data Navigator

With the BAAN IVc product new Orgware functionality will be delivered: BAAN DataNavigator. This Navigator is developed by TopTier and Baan Development and allows theend-user to do interactive HyperData navigation over the Baan Data. The navigation is donethrough a standard Internet browser (version 3.0+) and allows the user to retrieve data fromthe Baan database in an intuitive and flexible way.

This BAAN Navigator application provides you with a simple, object-oriented drag-and-dropuser interface that allows free and associative access to large databases. You can fly throughdata, finding associations, patterns and relationships without having to rely on linkspredefined by the Baan application. As you drag-and-drop a particular displayed object (forexample, customer) on to another object (for example, sales order), the BAAN Navigatorautomatically retrieves the requested combination of information (for example, the salesorders related to this customer).



5 - 3

The BAAN Data Navigator works directly on the data dictionary of the Baan Software. Themain advantages of the software are that it supports all the databases that BAAN supports andautomatically takes into account all the user information supported by Baan (authorization,languages, and so on).

5.3.1 Scope IVc

The scope of the first phase of the project, the ‘Light Product’, can be defined using thefollowing characteristic:

n The list of available “objects” will consist of up to 70 important BAAN tables.n Thin Client (just one browser plug-in):n The BAAN Navigator Server runs on a separate Windows NT server (later on Unix as

well).

For usage it is important to know that the current version only display’s BAAN records.Calculating new fields and aggregating records is currently not possible.

A more extensive product (‘Full Product’) is scheduled for BAAN IVc in December 1997.This product will cover a complete set of the BAAN tables and data and more functionalfeatures.



5 - 4


6 - 1

This chapter describes the new Interfaces/Partner packages incorporated in BAAN IVc. Thefollowing topics are covered:

n BAAN PDMn BAAN Synchronizationn Hyperionn BAAN Salesn ISSI Safari reporting tooln Tax Provider Interface (North America)n COMPAQ SmartStart

If a partner package supports another operating system and/or database management systemthan Baan, you must refer to that partner about information.

BAAN PDM is not part of the BAAN IVc standard and will be released together with theBAAN IVc extensions.

6.1 BAAN PDM

The BAAN PDM module is based on a leading PDM solution supplied by the americancompany B.A. Intelligence Networks, Inc. (BAIN). The PDM module implements a powerfulsolution to sharing and managing product data. The BAAN IVc PDM product linksCAD/CAM engineering and design processes to product manufacturing, distribution,maintenance, and support.

By implementing BAAN PDM, your organization gains the advantages of an outstandingproduct data management system and benefits from reduced time to market, faster productinnovation, improved quality, and the ability to adopt concurrent engineering practices.

Effective product data management is especially critical for large multisite enterprises.BAAN PDM provides a visually oriented, distributed solution, without sacrificing ease ofimplementation or use. BAAN PDM also promotes process reengineering, enables reusabilityand provides an infrastructure for achieving international quality standards certification.

By implementing BAAN PDM, enterprises of all sizes benefit from one complete, integratedsystem that links engineering, manufacturing, maintenance, purchasing, and sales. Yourcompany gains the advantage of using a single, combined system that offers a common, easy-to-use interface. You benefit by avoiding the inconsistencies, errors, and wasted time thatresult from working with many different systems.

With BAAN PDM, the information-technology benefits of the Baan solution enable theengineers and employees throughout your organization to easily share and manage productinformation. The result is a dramatic increase in productivity in the areas of engineering andmanufacturing. Products reach the market quickly, decisions are made easily frominformation that is standardized throughout your entire organization, and product quality isimproved.

BAAN PDM has applications in the mechanical, automotive, aerospace, electrical, power andprocess engineering industries. BAAN PDM unifies all product design and engineeringactivities throughout the entire life cycle of a product —from the initial design on CAD/CAMsystems to production, maintenance, and support. The system tracks the large amounts ofdata, such as textual, graphical, and financial information, that are required to successfullydesign and manufacture products.

6 Interfaces and partner packages

Note 1

Note 2

6 - Interfaces and partner packages


6 - 2

With a design framework that tightly integrates with the industry's leading CAD/CAMapplications, BAAN PDM enables the engineers throughout a large dispersed enterprise toeasily and visually control and manage the tasks involved in product design. This includes thefollowing:

n document creationn file managementn release/change controln bill of materials administration

BAAN PDM keeps track of, and enables quick, effective access to, the large amounts ofinformation required to design, manufacture, and support your company's products.

With its graphical user interface, BAAN PDM enables your engineers to be productive veryquickly. The module features Windows standard, Motif based, menus and icons, which speedup interaction between users and the system. The result is a major reduction in theinformation search time and approval-tracking time. In addition, BAAN PDM virtuallyeliminates the versioning errors that can degrade product quality.

BAAN PDM also provides explicit support for configuration management that complies withworldwide industry standards, such as CALS - PDES/STEP and ISO 9000. The result is thatyour products always meet the standards requirements of your industry.

6.2 BAAN Synchronization

The BAAN IVc release introduces an integration of MOOPI with the BAAN software.

6.2.1 Functional specifications

The objective of the BAAN synchronization interface is to provide Baan’s customers short tomedium term constraint-based scheduling and execution management for each plant ormanufacturing site.

As a result of the interface, the integration of MOOPI with BAAN will provide a state-of-the-art scheduling system that will produce a feasible execution plan that provides optimizationand constraints-based scheduling.

1 OptimizationThe resulting schedule, in line with the Theory of Constraints, will maximize throughputby keeping the critical resources (or bottlenecks) busy, and minimize cycle time by pacingthe noncritical resources to the bottlenecks and properly managing the material bufferswithin the plant.

− Maximum throughputMaximum throughput in a plant is achieved by keeping the main bottlenecks as busyas demand requires it. The definition of a bottleneck is the resource that has thehighest level utilization as a percentage of their stated capacity. For example the work-center with the highest percentage utilization (113% of capacity) will be the mainbottleneck if no other work-center has a higher utilization ratio.



6 - 3

− Minimum cycle time and constraint propagation.Once the main bottleneck has been loaded and optimized, there is no advantage to letthe other resources run ahead of the bottleneck. By pacing upstream operations and allrelated sub-assemblies to the bottleneck, BAAN Synchronization will ensure that jobsdo not linger in the plant uselessly, they will start and terminate rapidly, and that is theessence of reducing WIP and manufacturing cycle time. This advanced feature, isknown as constraint propagation and is available only in high-end planning andscheduling systems.

2 Constraints. MOOPI will build a schedule that respect the following constraints:

− Raw material (on-hand and planned receipts)Example: MOOPI will not schedule a job unless the material — on-hand and plannedreceipts — is available. Should the material not be available before 5 days for example,the operation and the job will be pushed 5 days. All other sub-assemblies that must besynchronized with this one, will be pushed as well, or at the very least prioritizedagain. The system will then use the newly freed capacity to run another job that can becompleted and shipped.

− Resources (machines, employees, and tooling)Baan Synchronization will ensure that all resources are available before starting anoperation. Its ability to handle people qualifications and tooling families is unique andvery powerful.

− Interdependencies between operations and sub-assembliesMOOPI will respect the predecessor-successor relationship between operations andsubassemblies. It will make sure that the gears are built before the transmission isassembled, it also knows that the gears are required at the fifth assembly operation andnot necessarily the first one, ensuring perfect synchronization in the plant.

− Sequencing and setup optimizationMOOPI will sequence the jobs for changeover sensitive work centers, and by doingthat, will balance resources utilization versus on-time delivery and agility.

At a very high level and without going into the details of the each field, the following dataelements need to be exchanged:

1 Work-orders elementsThese are simply the jobs that must be scheduled, and they come from two main sources:

− All jobs in BAAN’s Shop-Floor-Control (SFC) module.− All MRP generated advises within a certain user-specified time horizon.

For each SFC order, the system will also transfer the corresponding manufacturinginformation (Routings and BOMs). For the MRP generated advises, the genericmanufacturing information (again routings and BOMs) will be transferred to theSynchronization module.



6 - 4

2 Inventory elementsThey consist of on-hand quantities for all items. For purchased parts, however, we alsoneed the planned receipts. In other words, for the Synchronization module to build aproper schedule, the system must not only know that we have 370 Pentium 133Mhz instock, but also that we are confirmed to receive 400 per week for the next 6 weeks. Armedwith all that information we can now optimize the plant schedule for all jobs using thisspecific purchased part.

3 Scheduled work orders elementsThese are the same work orders sent to the Synchronization module. They are beingreturned to BAAN, with the constraint based scheduled start-end dates of each job.

4 Shop floor status updateThat information is simple a work-in-process (WIP) status update. Which jobs have beencompleted; which ones are now in process and which operations have been completed;which new jobs have been released to the Shop Floor Control module, and so on. Thatinformation comes from BAAN’s Shop Floor Update module.

5 Common data elementsSeveral other data elements are required for the system to operate properly. Some of themexist in BAAN (list of machines and employees) and others exist in MOOPI (setupmatrices, and so on). These data elements are required by both systems for properintegration and data validation.

For example: although setup matrices seem to be the domain of scheduling, the setupcharacteristic (that is, the thickness or color that affect changeover) is a characteristic ofthe part produced and - with this link - will become an attribute in BAAN (that is, the userwill be able to attach the characteristics ‘Red’ to part ‘Part-1234’ in the BAAN system).

For the BAAN system to perform the correct validation and to ensure that this particularcharacteristic exist, it must have access to the full matrix. The fact that both systems needthese data elements, is what made them common to both. The way the link was developedhowever, requires these data elements to be entered and maintained in BAAN and theywill automatically be transferred and updated in the Synchronization module.

The detailed list of these common data elements is:

− Employees− Machines− Tools− Tasks− Routings− BOM− Models− Setups (classes and matrices)− Qualified teams (resources qualifications per operation)



6 - 5

6.2.2 The planning and scheduling cycle

The way the link was developed, all data is provided by the BAAN system to theSynchronization module. Whenever he desires, or whenever the business requires it, the usercan request a schedule-update, at which point the following occurs.

1 All net change information for the previously mentioned links (work-orders link,inventory link, shop floor status update, and so on) are transferred to the synchronizationmodule.

2 A new constraint based schedule is calculated. That in turn, produces new start-end datesfor all jobs in the specified horizon.

3 The planner can now look at the various graphs and reports. MOOPI is highly graphicaland that helps the planner assess the performance of the plant (delivery performances,resources utilization, inventory levels, and so on). The planner can change any systemparameter, add overtime, out-source some jobs, and reevaluate the impact of his decisionson the plant performance.

4 When satisfied, the results of this what-if analysis are sent to the BAAN system updatingall start-end jobs for all work-orders elements.

6.3 Hyperion

In BAAN IVc Hyperion is introduced as partner package. Hyperion Software develops,markets, and supports financial information management applications for corporate-level usein large, complex organizations. The company’s client/server products support budgeting,multisource consolidation and business analysis processes. This gives users fast, dynamicaccess to inter-related financial information. Hyperion’s unique Common Data Accessdelivery technology enables superior reporting, spreadsheet analysis, data entry, and Internetaccess.

Distinguishing factors to choose for the Hyperion software are:

n Hyperion Software’s company strength, including financial performance, huge customerbase, and rich experience in corporate financial solutions.

n Hyperion Software’s ability to consistently introduce best-of-class financial applicationsthat deliver the performance and efficiency advantages afforded by the newest and bestsoftware industry technologies.

n Hyperion Software offers corporations the most complete strategy for managing financialcorporate needs in a client/server computing environment.

6.3.1 General information about the Hyperion products

The Hyperion software consists of the following products:

n Hyperion Enterprise for multisource consolidationHyperion Enterprise delivers a single, global view of financial information across multiplelocations and diverse general ledgers. It manages the diverse environments of accountstructures, currency translations, and complex intercompany relationships at division andcorporate-level entities. Hyperion Enterprise inherently understands the business rules andprocesses needed to meet management, legal, and statutory consolidation and reportingrequirements worldwide.



6 - 6

n Hyperion Pillar for enterprise-wide budgeting and planningHyperion Pillar provides enterprise-wide financial planning and analysis software fortoday’s networks of desktop computers. Hyperion Pillar complements your company’sexisting financial systems and completes the financial management cycle of plan, act, andanalyze.

n Hyperion OLAP for complex business analysisHyperion OLAP, with its powerful multidimensional analysis and reporting capabilities,helps you tackle complex, high-volume business issues such as customer and product lineprofitability. Huperion OLAP combines built-in financial intelligence with a highperformance OLAP engine and superior information access capabilities. In this way,Hyperion OLAP moves beyond generic OLAP tool sets to provide powerful businessapplication solutions.

For more specific information about the Hyperion products, refer to the relevant Hyperiondocumentation.

6.3.2 The interaction between BAAN and Hyperion

The interface has to do with budgeted and actual data stored on ledger accounts anddimensions. Both amounts and quantities are to be taken. So, GLD and FBS tables areinvolved in this first interface. Summarized, the following data categories in BAAN Financemust be handled by the interface:

n Budgeted Amounts/Quantities on Ledger Accountsn Budgeted Amounts/Quantities on Dimensionsn Actual Amounts/Quantities on Ledger Accountsn Actual Amounts/Quantities on Dimensions

The data flow

The data flow will go both from BAAN Finance to Hyperion and from Hyperion to BAANFinance. So you can create figures in BAAN Finance and take them over in Hyperion. Youalso can create figures in Hyperion and take them in BAAN Finance.

It must be possible to do the following reasons:

n Actual and budgeted figures are created in BAAN Finance (GLD and FBS) and sent toHyperion Enterprise, Pillar, and OLAP. In this way, actual and budgeted figuresoriginated from BAAN Finance can be used as input for Consolidation, Budgeting, andOLAP analysis.

n If budgeted figures are created in Hyperion Pillar, they are sent to BAAN Finance (FBS).In this way, budgets can be set up in a flexible and user friendly way. Afterexporting/importing these budgets, they can be used in BAAN Finance for comparisonwith the actuals.

The actions mentioned above are possible in a multisite environment. This means that theFinance company number will be very important as a key to the figures.

Note



6 - 7

6.4 BAAN Sales

In November 1996, the Baan Company announced the acquisition of Antalys Inc. This meansthat Baan will provide an enterprise-wide software solution that automates the configurationof complex products and services. The Antalys products are called sales force automation(SFA) systems, and must be ordered separately.

The name of the current Antalys product is Baan Sales Express. This product gives acompany the ability to create and deploy a sales configuration product. Baan Sales Express isa development environment for modeling a company’s product line and configuration logic.Baan Sales Express also creates the necessary graphical user interface to deploy aconfiguration system in either sales, manufacturing, or engineering.

The modeling capability of Baan Sales Express allows the product to solve either simpleconfiguration problems, such as features and options configuration, or very complexconfiguration problems, such as network or system configuration.

Baan Sales Express also includes a set of predefined templates that can be used right away forrapid implementation. These templates include not only configuration frameworks but alsocontact management, quotation building, catalog, and proposal generation.

As to integration, BAAN will provide the back-end configuration functionality. The Antalysproduct will serve as a front-end configuration tool, with a graphical user interface, which canrun stand alone on a PC. During the phases an integration will be gradually created whichenables information download from BAAN to Antalys and a batchwise information uploadfrom Antalys to BAAN.

6.5 ISSI Safari reporting tool

Baan works together with ISSI to make the ISSI Safari reporting tool available in BAAN IVc.

The user-friendly ISSI Safari Reporting Tool is part of the BAAN IV BackOffice distribution,being delivered on a separate CD-ROM. Installing this tool is similar to the rest of the BaanIV installation process, as it uses the industry standard Install Shield product.

The ISSI Safari Reporting Tool consists of Safari (version 6.0) and Safari Reportwriter. Safari(version 2.2) is the server side of the client/server model. Installation of Safari creates theserver for the Safari Reportwriter clients. In addition, the Safari installation includes aprebuilt Safari data dictionary based on the Baan IV c release, and tools to modify, maintain,and rebuild it.

Safari Reportwriter is a desktop presentation tool that harnesses all the power andconnectivity of your server. Safari Reportwriter allows you to create and generate reports fromthe familiar Microsoft Windows 95 environment, taking advantage of the GUI interface, andusing data delivered by the Safari server. This can greatly reduce the amount of networktraffic, as well as the workload required of the desktop processor. If desired, data can befurther filtered, sorted, and summarized at the desktop level.



6 - 8

6.6 Tax provider interface (North America, formerly GLO functionality)

The tax provider interface provides the ability to interface to third-party tax providers such asTAXWARE and Vertex using an online C-API. The interface alleviates the need formaintenance of tax rates and computation methods by tax code within BAAN IVc. Wheninterfaced to a tax provider, the tax will be computed based upon address, invoice, andproduct-related information provided by BAAN IVc to TAXWARE or Vertex. The taxprovider tax registers are updated by BAAN IVc for auditing and tax reporting purposes.

6.6.1 Static data

Additional information is maintained by BAAN IVc to configure the tax provider interfaceand to provide the information needed by the tax provider to compute the correct amount oftax. Countries may be registered for the tax provider and a specific address format. Either USor Canadian can be specified for validation. Product categories and product category matricescan be defined to map items, item groups, contract types, and account numbers to productcategories used by the tax provider. A point of title passage can be specified for each type ofdelivery and a default may be specified for non-order based transactions. Transaction typessuch as sales, service, rental and lease are defined, and are used by the tax provider whencalculating the tax. A transaction type can be specified for service contracts since itsdisposition, either service or rental/lease, cannot be otherwise determined.

Restrictions have been placed on existing BAAN IVc data for tax provider users. Tax codesmust be defined as singular and amounts must be entered in Finance net of tax.

6.6.2 Address jurisdiction checks

BAAN IVc provides tax jurisdiction checking through the tax provider interface. US andCanadian addresses, determined by country, are validated and a GEO code is assigned to theaddress information to identify the associated taxing jurisdiction.

6.6.3 Product and line-based tax calculations

The taxing jurisdiction, the amount, and the rate of tax are determined by the tax provider.The tax is calculated by order line and may be based upon the type of product being bought orsold. This allows you, for example, to tax labor and materials at different rates. An errorreport is generated if the tax provider is unable to compute the tax for a transaction.

The line tax amount will be stored within BAAN IVc and you can print the line tax onexternal documents. The line tax amount can be read within sales history.

6.6.4 Tax register updates

The tax provider tax register is updated when you are invoicing definitively through Sales orService. The tax register stores information such as the type of transaction, document orinvoice number, invoice date, and the amount of tax withheld by taxing jurisdiction and isused by the provider for audit and tax reporting purposes.

6.6.5 Order balance updates

BAAN IVc customer and supplier order balances are updated inclusive of tax. Wheninterfaced to a tax provider, the customer and supplier order balances are updated using thetax rate supplied by the tax provider. The tax rate is determined based on the address, order,and product-related information passed to the provider.



6 - 9

To maintain the accuracy of the customer or supplier order balance, the order balance isupdated if a change to the postal or delivery address or terms of delivery is made for an order.In addition, a warning message is displayed when changing static address information such asthe customer or supplier address which may affect the tax amount computed for the order andthe order balance.

6.6.6 Finance impact

Finance transactions will consult the tax provider to determine the rate of tax to be charged.The tax amount is computed based upon the taxable amount entered and the tax rate. Financetransactions do not have the capability to update the tax provider tax registers. However, autility is available to manually process adjustments to the tax provider tax register.

To facilitate the tracking of tax adjustments to be processed, a parameter-controlled warningmessage is given when adding ACR invoices with tax impact to indicate that a special taxcode should be used to process and record the tax. Adjustments to the tax provider tax registermay be made using the information in the BAAN IVc tax registers for the special tax codeand the new tax register adjustment utility.

6.6.7 Sales installments

When interfacing with a tax provider occurs, the tax withheld on sales installments isconsidered ‘Estimated’ tax. The estimated tax is considered as a part of the payment terms.The BAAN IVc tax register and tax provider tax registers are not updated for the estimatedtax. The correction entry generated when closing an order will include the amount of tax andlate payment surcharge due. The tax and late payment surcharge amounts will be included inthe amount of the correction entry created and the tax code will be blank.

6.6.8 Service contracts limited to a single location

When interfacing to a provider, tax is determined based upon the location where the service isbeing provided. To calculate the tax properly, only installations from the same customerlocation may be covered under the same service contract.

6.6.9 Tax calculation/register adjustment utility

The ability to perform a test calculation of tax from BAAN IVc using information enteredsuch as the tax jurisdiction, product category, order quantity and amount, and order type isavailable. Adjustments may also be written to the tax provider tax register.

6.6.10 Conversion utilities

Conversion utilities to convert existing BAAN IVc address information into the proper formatand to assign GEO codes are available. Error reports are generated to report addresses in anincorrect format or for addresses which the tax provider is unable to assign a GEO code.

6.6.11 Tax matrix modifications by product category

By providing the optional use of ranges and effectivity dates for product categories, flexibilityhas been added to allow users to increase performance when retrieving product categoryinformation from the database.



6 - 10

The following is a list of changes made to the functionality:

n Tax provider parameters have been added to identify whether or not ranges have beenimplemented for product categories. There is one parameter setting for each of thefollowing types:

− Item− Item group− Account number− Contract type− Effectivity/expiration date

6.6.12 Removal of transaction type restriction for taxware

Previously, TAXWARE only supported 2-character transaction types. This meant that the 3-character transaction type in BAAN would be truncated and then passed to the TAXWAREsoftware.

For BAAN IVc GLO, this restriction has been removed and TAXWARE will now support theentire length of the transaction type.

6.6.13 Supported versions

In order to use the tax provider interface in BAAN IVc GLO to calculate tax, the user must berunning the following versions (or later) of the third-party tax provider software:

n QUANTUM: V1.1.4n TAXWARE: UD9612-1

6.6.14 TAX API

The Tax API support in the BAAN IVb GLO release provided support for the UNIXoperating system only. For BAAN IVc, the Tax API has been enhanced to support theMicrosoft Windows NT operating system. This enhancement will affect both the UNIX andNT versions of the Tax API. The primary modifications will be done to the communicationlayer. Both the 4GL and binary code will be converted from UNIX message queues tomailslot. The mailslot architecture is supported on both the UNIX and NT environments. NTmakes a strict difference between the server (program that creates and reads the mailslot), andthe client (program that opens and writes to the mailslot). A client can also act as a server, butfor a single message queue the relationship must be clearly defined.

The TAX API interface using ORB technology is also available in the Baan IV c release forselected customers.



6 - 11

6.7 COMPAQ SmartStart

SmartStart is an integrated system installation procedure developed by Compaq to simplifyinstallation of various software vendors' products on the full range of Compaq Servers andWorkstations. In order to become more effective and efficient in the implementation of theBAAN IVc Back Office product, Baan now includes the necessary components that make theinstallation of the Baan IVc Back Office product SmartStart compliant.

6.7.1 Purpose of SmartStart

The SmartStart tools is designed to aid in the setup of your Compaq server by.

n Optimizing hardware and software configurationn Eliminating frustrating installation errorsn Ensuring installation of correct Compaq driversn Streamlining installation of operating system and other key system softwaren Saving timen Simplifiing standardization of server setup

6.7.2 Features of SmartStart

SmartStart is the Compaq integration tool for simplifying the setup of proven and reliableservers with industry leading system software. SmartStart offers the following features:

n SmartStart provides a streamlined process for the installation of leading operatingsystems, databases and backup

n SmartStart provides automated methods of configuring your server; however, theflexibility of SmartStart allows you to verify and change settings for full customization -you keep control and have the final say.

n Throughout the integration process, you can access online help, navigate through theinterview to see exactly where you are in the process, and see a summary of theinformation you have entered.

n SmartStart saves a summary of all the setup information. You can view this information atany point online and it is saved for future reference.

n If you prefer to run the system configuration utilities and follow the softwaremanufacturers installation process, a Manual Configuration path is also available.However, this path does not offer the full hardware and software integration benefits of theAssisted Integration path.

n SmartStart also works with selected "off-the-shelf" software products, in other words,using the CDs distributed by the software vendors such as Baan Company

n Compaq has partnered with Microsoft, Novell, SCO, IBM, Oracle, Netscape, Cheyenne,and Sybase on the development of SmartStart. The process has been approved by all ofCompaq's partners for the installation of their software on Compaq servers.



6 - 12

6.7.3 SmartStart - Baan Logic Flow

SmartStart first asks the user to select the Operating System to install. For implementation ofBAAN IVc BackOffice, only Microsoft Windows NT 4.0 is currently relevant. SmartStartthen offers a list of software components to install, requiring the user to specify allcomponents up front in order to determine dependencies and properly allocate resources.

In the versions prior to Smart Start 3.50, BAAN is not listed as an optional softwarecomponent. In this case the user must manually select the BAAN product by clicking FindAdditional Products and inserting the SmartStart enabled BAAN IVc BackOffice CD.

Once the user selects the software to install, SmartStart will check all the dependencies. Forexample, to install BAAN IVc BackOffice, the user needs to install SQL Server 6.5. If theuser has not selected SQL Server 6.5 and selects BAAN IVc Back Office, SmartStart issuesan error message indicating the dependency.

SmartStart also checks disk space requirements. Currently BAAN IVc BackOffice requires500 MB for the Application portion, but that is not sufficient for the installation of thedatabase, for which another 1.5 GB is required.

6.7.4 Components of SmartStart – BAAN integration.

The following components which make the SmartStart – BAAN integration work are part ofthe BAAN IVc BackOffice distribution CD.

n PEZ file for Baan is the product information file generated by Compaq for each productthat is SmartStart enabled. The PEZ file has information about the product being installedand is read during the SmartStart. Installation process. The PEZ file specifies informationsuch as product disk requirements, product dependencies etc.

n Baan SmartStart DLL – conducts the SmartStart interview and creates the BEM (BackEnd Manager) script to be run. The BEM script in turn invokes the Baan IV c Back OfficeInstall Shield.

6.7.5 Current limitations - future considerations

n All the disk space be on a single device. In the future, disk space can be allocated acrossmultiple disks.

n Microsoft SQL Server is the only database supported by BAAN IVc BackOffice for whicha BAAN SmartStart DLL has been constructed. In the next release support for Oracle willbe included. Future plans for Informix are being made.

BAAN is not defined in the current version of SmartStart 3.42. In the future version ofSmartStart 5.0, BAAN is a defined software component.


7 - 1

This chapter describes the BAAN IVc extensions. The following topics are covered:

n CNT (Controlling/Kostenrechnung)n SCC (Supply Chain/Controlling)n SCH (Supply Chain)n MCR (Multicurrency)

The BAAN IVc extensions cannot be used concurrently. Although you can install more thanone extensions, you can only use one extension at the same time.

The BAAN IVc extensions will be released released after the BAAN IVc standard.

7.1 CNT (Controlling/Kostenrechnung)

The extension CNT (BAAN Controlling) is a package of application software written in andrunning on BAAN Tools. This version of the extension can be installed in a BAAN IVcenvironment.

The Controlling extension is a tool for planning and controlling cost units and overhead costsof cost centers. It reflects the requirements of the German market regarding cost accounting(Kostenrechnung in German).

The most important feature is the distinction between fixed and variable costs in relation toperformance output of cost centers. With BAAN Controlling a flexible budget accountingsystem can be implemented. Overhead costs can be budgeted and controlled from the costcenter (dimension) point of view. Plan amounts and results can be presented according tomultiple hierarchical structures on ledger accounts and dimensions.

A new performance planning and allocation module is available, where you can to allocatecosts between dimensions. A lot of new business functions have been introduced, but there arealso changes in the existing calculation functions of the CPR and PCS modules. Now you canwork with variable or fixed cost rates and surcharges, so that variable and full cost prices canbe calculated. Sales statistics (SST) has been enhanced to show the contribution marginsagainst variable or full cost prices.

7.1.1 Budgeting and control of overhead costs

Overhead costs can be budgeted and controlled per cost center. The cost types are split up intovariable and fixed components. On this basis allowed costs per cost center can be given as aflexible target. The cost types are a subset of ledger accounts from GLD.

Budgeting is even possible for ledger accounts with a higher sublevel. Reporting is done bymeans of definable reporting structures. Budgeted and actual cost allocation sheets arepredefined. Budgeting and analyses can be carried out according to hierarchical structures onledger accounts and dimensions.

You can define many different structures, which can be used not only for reporting, but alsofor drill-down facilities. In these online inquiries budgets and results are shown at a moreaggregated or a more detailed level, based on one of the defined hierarchical structures onledger accounts and dimensions.

Not only costs but also performance of cost centers can be planned. There are new functionsimplemented to define performance and allocation relations between cost centers. By means ofa plan price iteration cost rates can be determined exactly. The plan relation model can beloaded and modified to achieve actual allocation figures. It is also possible to post actualallocation relations directly in GLD with a new transaction type.

7 BAAN IVc extensions

Note 1

Note 2

7 - BAAN IVc extensions


7 - 2

Actual costs are entered in GLD and used for actual cost analysis. In order to give a flexiblebudget, the actual performances of cost centers are fundamental. They can be manuallyentered or derived from Hours Accounting (HRA), derived from the actual performancerelations or be copied from the budget performance figures.

On the dimensions cost amounts and performance figures can be maintained. The cost ratesresulting from dividing the amounts by the performance quantities can be used as operationrates and surcharges in cost price calculation. There are integration sessions implemented forthe purpose to copy rates and surcharges from the cost budgeting into the master data of costprice calculation in CPR and PCS. The connection between overhead cost budgeting and costobject accounting (calculation) is established with an integration scheme.

7.1.2 Cost price calculation

Cost price calculation determines the internal prices for manufactured and purchased items.The cost price of a cost unit serves as the basis for controlling costs, determining sales prices,taking make or buy decisions, valuating the goods on stock, and so on. Possible cost units areitems or projects. The cost price of a cost unit consists of direct costs and overhead costs.Direct costs are costs, which can be allocated directly to a cost unit. Overhead costs can onlybe allocated to cost centers directly. It is, however, possible to calculate the overhead costs forcost units by taking into account how much of the performance capacity of the cost centers isused by the cost units. But some of the cost center costs are fixed regarding to the performanceoutput of the cost center, some are variable. Therefore overhead costs can be calculated forcost units in two different ways:

1 Variable cost price: only variable parts of overhead costs for cost units are calculated.

2 Full cost price: variable and fixed parts of overhead costs for cost units are calculated.

Both cost prices are necessary, the full cost price for valuation of goods on stock, the variablecost price for carrying out a contribution margin analysis. With BAAN Controlling, these twocosts prices can be determined in one calculation run and both be stored in result tables andmaster data with the same cost price calculation code as key field. One of the cost price typesmust be selected as standard cost price for stock valuation. The contents of operation cost rateand surcharge tables can be derived from the dimension budgeting for calculation purposes.

The new functionality has been implemented in calculation of standard items (CPR),customized items and projects (PCS). In the PCS module the budget calculation andestimation calculation can be done for variable and full costs. When calculating actual costsfixed and variable cost portions are not distinguished.

7.1.3 Statement of operating results

Compared with profit and loss accounting the statement of operating results only contains thecosts and revenues, which are directly related to the main business of the company, that is, theproduction. Extraneous costs are eliminated, calculatory costs are incorporated.

The necessary revenue figures and contribution margins can be provided by the enhancedsales statistics (SST) module, where it is now possible to show contribution margins againstvariable or full cost prices. Both cost prices are historically stored in the point of sales. Fixedcosts and cost center deviations resulting from overhead cost control on cost centers can beposted to General Ledger (GLD). These figures are major input to establish a statement ofoperating results.



7 - 3

7.1.4 Separate controlling package

A new package called BAAN Controlling is created, which contains the new functionalities incost center control and calculation as previously described. Moreover some controllingfunctions of other modules are included in the main menu of BAAN Controlling:

n Enterprise Information System (EIS)n Inquiry functions of General Ledger (GLD)n Costing (CST)n Sales Statistics (SST)n Inventory Analysis (INV)n Capacity Requirements Planning (CRP)

7.1.5 Coexistence with other extensions

The following table shows the compatibility of CNT with the other BAAN IVc extensions:

WF Workflow no

MOOPI Production Fine Planning no

MC Multicurrency no

SCH Supply Chain yes The merged version SCC must be installed(see document for SCC)

NL1 Netherlands tp extension yes The two extensions have to be installed in aVRC derivation structure

7.1.6 Technical information

A new package ct (Baan Controlling) has been introduced. In addition, there are changes inmany standard software components of the packages cp, ps, tc, td, tf and ti. The 5 packagesare delivered in the B40L_c_cnt.

The software will be available in the following languages (s=software, h=online help):

n US (sh)n GE (sh)

7.2 SCC (Supply Chain/Controlling)

The extension SCC (Supply Chain/Controlling) is a package of application software written inand running on BAAN Tools. This version of the extension can be installed in a BAAN IVcenvironment.

The SCC extension is a merged version of the SCH (Supply Chain) and the CNT(Controlling) extensions. It comprises the functionalities of both extensions.



7 - 4

7.2.1 Coexistence with other Extensions

The following table shows the compatibility of SCC with the other BAAN IVc extensions:

WF Workflow no

MOOPI Production Fine Planning no

MC Multicurrency no

CNT Controlling notapp.

SCC contains CNT

SCH Supply Chain notapp.

SCC contains SCH

NL1 Netherlands tp extension yes The two extensions have to be installed in aVRC derivation structure

7.2.2 Technical information

The 5 packages cp, ct, ps, tc, td, tf and ti are delivered in the VRC B40L_c_scc

The software will be available in the following languages (s=software, h=online help):

n US (sh)n GE (sh)

7.3 SCH (Supply Chain)

The current BAAN IV solution for the automotive industry lacks some functions/featuresnecessary for a lean but high performant management of supply chain data - needed by allautomotive assemblers and suppliers. These gaps will be closed by the enhanced release ofBAAN IVc Supply Chain (SCH).

7.3.1 Features

The sections below list the features offered by the Supply Chain extension.

General

n MPS Purchase SchedulesAbility to create purchase contracts and schedules for MPS purchase items.

n Planned inventory movements based on schedulesIntegration of planned inventory movements based on schedules into standard display andreporting sessions.

Sales Process

n FAB & RAW Authorization ManagementControl of authorization figures for fabrication and raw material commitments on partnumber level.

n External CUM ManagementHandling and resetting of CUMs, either once a year or due to adjustments throughout ayear.

n Planning/Shipping/Sequence SchedulesConsistent handling of planning, shipping and production sequencing schedules.



7 - 5

n Delivery Lead TimeConsideration of transport times for the shipping process if dues dates reflect the deliveryat the customer site.

n Schedule consistency and historyChecking of incoming schedules against earlier schedules and generation of correspondingwarning messages.

n RAN/DON/KANBAN based scheduling supportHandling of EDI messages not-conforming with standard shipping schedules.

n Customer Part Number RevisionsRevision control of components taking into account effectiveness and expiration dates.

Purchase Process

n FAB & RAW Authorization ManagementControl of authorization figures for fabrication and raw material commitments given tosuppliers.

n External CUM ManagementResetting of purchasing CUMs, either once a year or due to adjustments throughout a year.

n Fixed delivery day and week frequencyCreation of purchase information only on defined days in a defined frequency.

n Supplier Schedule Frozen PeriodIn purchase schedules, provide firm zone of demand within which planned deliveries donot vary.

n CUMs and discrete values on schedulesShow discrete volumes as well as CUM volumes in schedule displays.

n Purchase RequisitionsMaintenance of purchase requisitions for goods not handled by MRP/SIC and generationof standard purchase orders.

Receiving Process

n Receiving EnhancementStreamlined receiving procedure based on previously sent ASN (advanced shipping note).

Shipping Process

n Shipping Planning Board with ContainerizationPlanning and management of shipping of goods to the supplier, including the handling ofcontainers and packing materials used for transportation.

n Sequenced ShippingShipping process based on received sequencing schedules.



7 - 6

Finance Process

n Evaluated Receipts Settlement (incl. Self-billing invoice, payment advise, retro-invoicing)Electronic creation of self-billed purchase invoices and payment advises based on receipts.

n Customer-specific invoice number alternativeConsideration of specific invoice numbers in order to ease the evaluated receiptssettlement procedures.

7.4 MCR (Multicurrency)

In BAAN IVc, Baan delivers its multicurrency extension. Using this multicurrency extension,the BAAN application can be implemented in many more countries than using the standardsolution. It is especially the geographical areas with high inflation rates that can use ourmulticurrency version.

Multicurrency cannot coexist with other BAAN IVc extensions.

In every RFP (request for proposal), we can answer the question whether we supportmulticurrency in the affirmative (since TRITON 3.0). What is meant by multicurrency? Eachdocument (such as sales invoices, purchase invoices), can have its own (foreign) currencywhich is also converted to the (general) home currency in which the general ledgers will bekept. In fact, in the standard BAAN application we distinguish:

1 Document currency (invoices and so on).

2 Payment currency (currency in which invoices will be paid). This can be different fromdocument currency.

3 Home currency (in which all transactions will be converted all the time for bookkeepingpurposes, which can be different from document and payment currency).

7.4.1 Multicurrency accounting

Countries with stable currency environments are sufficiently covered with the above features.But in countries with high inflation rates, additional functionality will be needed. Obviously,this is important for our business. Many clients have subsidiaries in high inflation countries.

In high inflation environments, there is a need for the so-called dual accounting system. Thelocal books are kept in local currency. For the management reporting purposes the books arekept in a stable currency, for example, US$.

7.4.2 Rules for dual accounting

The international high-inflation accounting standards will be used, as defined by the FASB(Financial Accounting Standards Board). In the United States of America, all companies(including foreign companies) must follow the Statements of Financial Accounting StandardsFASB-8 or FASB-52 regarding currency translation methods.

At this moment, the FASB-52 rules are an international standard for multinational companiessuch as ABB and Philips.

One of the rules in FASB-52 is: if inflation is more than 100% over the past 3 years, you mustreport in a stable currency and, as a result, start dual accounting.

Note



7 - 7

7.4.3 Conclusion

BAAN’s new multicurrency solution can be used without any restrictions because of thefollowing features:

1 A maximum of three different home currencies (in principle, three separate books can bekept simultaneously). Each home currency can be validated (start dateand end date can bedefined).

2 Currency translation (conversion) will be done at transaction level in all home currenciesthat are valid. Each transaction will be converted to (a maximum of) three different homecurrencies.

3 Implementation is done both in logistics and in Finance. This means that the sourceinformation of the financial system, e.g. cost prices, and in general, price/amountinformation is available in all home currencies.

4 Statutory and complementary accounts support the dual accounting system. Statutoryaccounts are the local accounts and make up the fiscal balance sheet and profit and lossstatement. Complementary accounts are used to create the management reports togetherwith the statutory accounts.

5 Monetary and nonmonetary accounts. For each account it can be checked if it is monetaryor not. Monetary accounts should be translated at the end of a month against the closingrate of that month (kind of revaluation; result will be posted to translation gain and lossaccounts). Nonmonetary accounts are not revalued at the end of month, because theyfollow the historical rates.

Because of the chosen architecture, the multicurrency solution is the basis for Euro software.



7 - 8


A - 1

This appendix describes the portingsets for BAAN IVc.

Table A-1 Overview of the A-Portingsets for BAAN IVc. Please note product version numbers are preliminary

System porting

set

bshell bx ba bisam btam oracle 7 informix sybase db2 sql-server orbix 1.0

HP9000_PA_RISC/HPUX10.0 6.1c.02 * * * 2.1 2.1 7.1.6.2.0 7.22UC1 11.0.2

HP9000_PA8000/HPUX10.2 6.1c.02 * * * 2.1 2.1 7.x 7.x 11.0.2 On request

IBM_RS6000/AIX4.1 6.1c.02 * * * 2.1 2.1 7.1.6.2.0 7.22UC1 2.1

DEC_ALPHA/DIG_UX3.2 6.1c.02 * * * 2.1 2.1 7.1.6.2.0 7.22UC1

SUN_SPARC/SOLARIS2.4 6.1c.02 * * * 2.1 2.1 7.1.6.2.0 7.22UC1 11.0.2 On request

SEQUENT_INTEL/DYNIX_PT

X4.1

6.1c.02 * * * 2.1 2.1 7.2.3.0.0 7.22UC1

COMPAQ Intel NT 6.1c.02 * 7.3.2.3.10 7.22TC1 6.50.SP3

HP Intel NT 6.1c.02 * 7.3.2.3.10 7.22TC1 6.50.SP3

DEC Intel NT 6.1c.02 * 7.3.2.3.10 7.22TC1 6.50.SP3

DEC Alpha NT 6.1c.02 * 7.3.2.2.0 7.20 6.50.SP3

BW B40c.040

Table A-2 Overview of the B-Portingsets for BAAN IVc. Please note product version numbers are preliminary

System porting

set

bshell bx ba bisam btam oracle 7 informix sybase db2 sql-server NS-

SQL/

MP

orbix 1.0

AT_T_INTEL/5.4.3 6.1c.02.01 * * * 2.1 2.1 7.1.6.2.0

DG_INTEL/4.11 6.1c.02.01 * * * 2.1 7.2.3.0.0 7.20UC3

HITACHI_PARISC/HI-

UX_WE2_V4

6.1c.02.01 * * * 2.1 2.1 7.2.3.0

SCO_UNIX_INTEL/3.2.5 6.1c.02.01 * * * 2.1 2.1 7.1.6.2.0 7.20UC2

SNI_MIPS/SINIX_5.43 6.1c.02.01 * * * 2.1 2.1 7.2.3.0.0 7.20UC2

UNIXWARE_INTEL/2.0 6.1c.02.01 * * * 2.1 2.1 7.1.6.2.0

TANDEM_NSK/D44 6.1c.02.01 * * * 3.0

DG_M88K/DG_UX5.4.3 ? * * * 2.1 2.1 7.0.16.4.0

Appendix A Portingsets for BAAN IVc

Appendix A - Portingsets for BAAN IVc


A - 2