ssa plm 8.0 sp4 release notes

!SSA® Product Lifecycle Management

SSA PLM 8.0 SP4 Release Notes

© Copyright 2006 by SSA Global Technologies, Inc. and its Subsidiaries and Affiliates

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any way or by any means, including, without limitation, photocopying or recording, without the prior written consent of SSA Global Technologies, Inc.

Important Notices

The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of SSA Global Technologies, Inc. or its Subsidiaries and Affiliates.

By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of SSA Global Technologies, Inc. and/or it Subsidiaries and Affiliates and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from SSA Global Technologies, Inc. or its Subsidiaries and Affiliates (as applicable) pursuant to a separate agreement (“Purpose”).

In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above.

Although SSA Global Technologies, Inc. and/or its Subsidiaries and Affiliates has taken due care to ensure that the material included in this publication is accurate and complete, neither SSA Global Technologies, Inc. or its Subsidiaries or Affiliates can warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, neither SSA Global Technologies, Inc. or its Subsidiaries or Affiliates assumes and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.

Trademark Acknowledgements

SSA, SSA Global and SSA Global Technologies are trademarks or registered trademarks of SSA Global Technologies, Inc. in the United States and/or other countries.

All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.

Publication Information

Document code: P3604A US

Release: SSA® Product Lifecycle Management 8.0 SP4

Publication date: November 2006

Table of Contents

Chapter 1 Installation and Usage Information...........................................................................1-1 Database changes.......................................................................................................................1-1 Installation changes .....................................................................................................................1-1 Character limitations ....................................................................................................................1-2 Environment definition for integration to ERP LN.........................................................................1-2 Gateway Configuration changes for RoHS fields – BaanERP 4 & 5 and ERP LN FP0 & FP1.....1-2

Change LoadItem ...................................................................................................................1-3 Change Supplier .....................................................................................................................1-4 Additional changes – ERP LN (FP0 & FP1) only ....................................................................1-4

Vault Server Unix/Linux support ..................................................................................................1-6 How to work with LoadFiles .........................................................................................................1-6 Client uninstall dependency check...............................................................................................1-7 Installing PLM add-ins using Terminal-Server/Multi Profile setup ................................................1-7 CAD integrations and viewing assemblies ...................................................................................1-7 Business process Check Out step ...............................................................................................1-8 Informix Unicode database support .............................................................................................1-8 Working with multiple databases .................................................................................................1-8

Chapter 2 Performance Recommendations...............................................................................2-1 Windows “Show window contents while dragging” setting ...........................................................2-1 Windows Inet component of Internet Explorer v6.0 .....................................................................2-3 JVM memory requirement............................................................................................................2-4

ii | Table of Contents

Vault Server .................................................................................................................................2-4 Database Server ..........................................................................................................................2-5 Support for Oracle ODBC driver ..................................................................................................2-5

Chapter 3 System Requirements................................................................................................3-1 Hardware and software requirements ..........................................................................................3-1 Software component build tracking table .....................................................................................3-1

Chapter 4 SSA PDM Issues .........................................................................................................4-1 PDM closed issues ......................................................................................................................4-1 PDM limitations..........................................................................................................................4-11 PDM - Baan ERP (IV/5) integration limitations...........................................................................4-14

About this Document

This document provides Release Notes to inform you about

! Software component builds for the 8.0 SP4 release of SSA PLM and related products.

! A summary list of known cases resolved, defects and limitations in this release of SSA PLM.

Further information

For information about known defects and limitations for other products in the PLM line, please refer to the specific product’s Release Notes:

For an overview of the functionality provided by this release of SSA PLM and each of its related products, please refer to the relevant user documentation.

Note

Major technical changes in this release include the following:

! Integration to ERP LN is now supported using SSA Technology Architecture 2.6 (replaces OpenWorld).

! PLM Server installation requires Java ™ 2 SDK, Standard Edition version 1.4.2_07.

! AutoVue Professional for Java version 18 SP8 is now supported.

Send us your comments

We continually review and improve our documentation. Any remarks or requests for information concerning this document or topic are appreciated. Please e-mail your comments to [email protected].

In your e-mail, refer to the document number and title. More specific information will enable us to process feedback efficiently.

Database changes

Customers that work with PLM version 8.0 SP3 are not required to operate the Upgrade Database utility to prepare the database for PLM 8.0 SP4.

However, there is one parameter that needs to be changed in order to continue using the Reference Designations in grouping mode, that is, the mode in which PLM creates reference designation list from a range.

The required SQL command is:

update SYS_CONFIG set PREF_VALUE='1'

where PREF_NAME = 'REF_DESIGNATION_GROUPING'

Installation changes

The default installed directory of the PLM Core and PLM Server application has been changed. The default location is now:

! For PLM Core: C:\Program Files\SSA_PLMCore

! For PLM Server: C:\Program Files\SSA_PLMServer

1Chapter 1 Installation and Usage Information

1-2 | Installation and Usage Information

Character limitations

The € sign is not yet supported by regular Windows operating systems. As a result, this character is not supported by PLM. In case of an ERP currency that is defined as “€”, it should be replaced with “Euro.”

Environment definition for integration to ERP LN

Access the <Tomcat>\bin directory and verify that the following definition exists in the setclasspath.bat file:

set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%CATALINA_HOME%\webapps\CFEServer\WEB-INF\lib\ErpItemData.jar;%CLASSPATH%

When activating Tomcat as a service, the changes can be applied by operating:

! SSA PDM Server>\Tools\installTomcatAsService.bat

Gateway Configuration changes for RoHS fields – BaanERP 4 & 5 and ERP LN FP0 & FP1

RoHS fields COMPLIANCE_STATUS and COMPLIANCE_CERTIFY exist only in Baan LN; they are not defined in BaanERP 4 and 5, nor in early FPs of ERP LN. These two fields are lookup fields and as such must have a valid value when adding a new record to the database.

The following sections describe the steps that must be performed to change the LoadItem and Supplier Gateway objects.

Installation and Usage Information | 1-3

Change LoadItem

1 On the Mapping tab, set Gateway Object to LoadItem.

2 On the Field Mapping tab, select COMPLIANCE_STATUS.

3 Change the type to Constant.

4 Set Value to ‘0’ (zero).

5 Click Save.


Change Supplier

1 On the Mapping tab, set Gateway Object to Supplier.

2 On the Field Mapping tab, select COMPLIANCE_CERTIFY.

3 Change the type to Constant.

4 Set Value to ‘0’ (zero).

5 Click Save.

Additional changes – ERP LN (FP0 & FP1) only

Step 1 – Clear COMPLIANCE_STATUS selection

1 Start the ERP Mapping (cfeerpmap.exe) tool.

2 On the Mapping Fields menu, click PDM to ERP.

3 In the object tree, make sure ST-Item is selected.

4 In the list of attributes, locate COMPLIANCE_STATUS.

5 Clear the associated Active check box, as shown in the following figure.


6 On the Mapping Fields menu, click ERP to PDM.

7 In the object tree, make sure Item is selected.

8 In the list of attributes, locate COMPLIANCE_STATUS.

9 Clear the associated Active check box, as shown in the following figure.


Step 2 – Remove two lines from the server file

In the <server>\storage\server\scheme\erpScheme.xml file, for the SUPPLIER object, remove the following lines:

<ATTR ATTR_NAME="COMPLIANCE_CERTIFY" DB_NAME="encd" TABLE="tccom120" ATTR_TYPE="string" />

<ATTR ATTR_NAME="COMPLIANCE_CERTIFY" ERP_ATTR="COMPLIANCE_CERTIFY" />

Vault Server Unix/Linux support

The Vault Server can be installed on a Unix/Linux operating system, but Text Search can only be supported if the Vault Server is installed on Microsoft Windows.

How to work with LoadFiles

1 Copy LoadFiles.exe into the same directory as jvm.dll. The original file is located in the %BPDM_DIR%\bin directory.

2 From a Command Prompt window, test with the command:

LoadFiles -c -Djava.class.path=”%bpdm_dir%\BIN\Gateway.jar” <DB connection string>

3 Install as a service using the command:

LoadFiles -i -Djava.class.path=”%bpdm_dir%\BIN\Gateway.jar” <DB connection string>

To uninstall LoadFiles as a service use:

LoadFiles –r


Client uninstall dependency check

The dependency check that required users to uninstall all integrations and add-ins before uninstalling the SSA PDM client has been removed. This check existed to make sure users did not try to run versions of the SSA PDM client with incompatible versions of SSA Integrations or add-ins.

In the interests of ease of maintenance, the dependency check has been removed, meaning that users can now uninstall the SSA PDM client without first having to uninstall related SSA integrations or add-ins.

The removal of the dependency check increases the risk of users installing a version of the SSA PDM client that is not compatible with existing installed SSA integrations or add-ins.

Installing PLM add-ins using Terminal-Server/Multi Profile setup

Using the Terminal-Server/Multi Profile setup when installing add-Ins such as Lifecycle Reporter, Product Packager, and so on, requires, once complete, that users reset server connection information.

CAD integrations and viewing assemblies

Users of any of the SSA PDM CAD integrations must be aware that viewing native CAD assembly or drawing files from the SSA PDM client using a native CAD-supplied plug-in viewer or other third-party viewer, bypasses the SSA PDM configuration control mechanism. This is because any viewer not under the control of the SSA PDM application will use local copies of files (which may or may not be the required revision), instead of taking the required revision from the SSA PLM vault.

To ensure that assembly information is displayed correctly when viewed, it is strongly recommended that you only use the SSA PDM integration to AutoVue SolidModel Professional for Java (jVue); the “Mark-up” or “Red-lining” mode must be used.


Note

The list of CAD file formats supported by the AutoVue viewer is subject to change as new versions of CAD applications are released. For an up-to-date list, please contact your SSA account representative.

Business process Check Out step

Users can configure the behavior of a business process Check Out tool step to either fail or continue when there are no released files attached to the Check Out step. The default behavior is for the step to fail (Ref #12779). If it is required that the step continue, run the following SQL command:

update SYS_CONFIG set PREF_VALUE='1' where PREF_NAME = 'IGNORE_ALL_ATTACHMENTS_UNDEFINED';

Informix Unicode database support

Currently, there is no Unicode database support when using Informix.

Working with multiple databases

If a single SSA PLM Server will be used against multiple databases, the database scheme (including customization changes) must be identical for all databases used.

Windows “Show window contents while dragging” setting

The Show window contents while dragging check box must be cleared.

Windows 2000 ! In the Display Properties dialog box, on the Effects tab, make sure the

Show window contents while dragging check box is cleared.

2Chapter 2 Performance Recommendations

2-2 | Performance Recommendations

Windows XP 1 In the Display Properties dialog box, on the Appearance tab, click Effects.

2 In the Effects dialog box, make sure the Show window contents while dragging check box is cleared.

If the Show window contents while dragging check box is selected, users will experience severe performance degradation when moving SSA PDM client windows about on their desktop.

Performance Recommendations | 2-3

Windows Inet component of Internet Explorer v6.0

Problem: After the client makes a request and the response is received, the client waits for about 30 seconds.

Proposed work-around: SSA has been notified by Microsoft that this is a known bug of Internet Explorer 6.0 SP1, and occurs only if Internet Explorer is configured to use Autoproxy.

Two work-arounds exist:

Work-around 1

Do not use Autoproxy. To verify your Internet Explorer settings, complete the following steps:

1 On the Tools menu, click Internet Options. The Internet Options dialog box appears.

2 On the Connections tab, click LAN Settings.

3 In the Local Area Network (LAN) Settings dialog box, make sure the Automatically detect settings check box is cleared, as shown in the following figure.

2-4 | Performance Recommendations

Work-around 2

If you are using Microsoft ISA proxy, you can run it either in SecureNAT mode or with Firewall Client. For more information, go to: http://msdn.microsoft.com/library/en-us/isa/isaabout_4u7n.asp?frame=true

In this case you will configure your browsers to use Direct Internet Connection (no proxy, no Autoproxy), and you will not run into this problem.

JVM memory requirement

Java Virtual Machine (JVM) requires at least 1024 MB for each 100 users. For more details, please refer to the latest SSA PDM Sizing & Prerequisites Guide.

Vault Server

When the SSA PLM Server and Vault Server are located at the same site, it is strongly recommended (for performance reasons) that the Vault Server is installed on the same machine as the SSA PLM Server.

Performance Recommendations | 2-5

Database Server

The Database Server should always be installed on a separate machine and must be located on the same Local Area Network as the PLM Server.

The PLM Server and the database must not communicate through a Wide Area Network connection.

Support for Oracle ODBC driver

From the 8.0 SP2 release, the Oracle ODBC driver is supported for Oracle 9i and later. Please note the following limitations:

! Support is only from Oracle 9i and later.

! Database migration is not supported with the Oracle ODBC driver, you must use the standard Windows ODBC driver.

! Customization is not supported with the Oracle ODBC driver, you must use the standard Windows ODBC driver.

Hardware and software requirements

For details of hardware and software requirements, please refer to the SSA PDM Sizing & Prerequisites Guide.

Software component build tracking table

Software Component Build/Service Pack Number

Core Product Build 161

SSA PDM Client (Windows 2000/XP) Build 151

SSA PLM Web, Services and Vault Servers

Build 392

SSA Redlining (for jVue 18 SP8) Part of SSA PLM Server

SSA PDM Upgrade Utility SSA PDM Pass Conv Utility

Build 129

3Chapter 3 System Requirements

This chapter lists details of known issues for SSA PDM 8.0 SP4.

PDM closed issues

Functional Area Internal ID Description

Upgrade Database Tool

Inquiry: 312536

Request: PLM-00000-00132

The following problems that are resolved related to the Upgrade Database Tool:

! Resolves Oracle tablespace problems during migration process:

! Tables copy to the original tablespace.

! The system provides warning messages about free space availability.

! Improve performance.

Database structure Inquiry. 334151


Unique indexes were added to tables: PROJ_CONFIG and BASE_CONFIG in order to prevent occurrences that customers have duplicate records in these tables.

Note This change requires the use of the Upgrade Database Tool.

4Chapter 4 SSA PDM Issues

4-2 | SSA PDM Issues


Business process creation

Inquiry. 323085


When the user links items or documents to a business process via the PDM client, the system now allows him/her to automatically attach these objects to all BP steps.

Item / Document workspaces


The Collection and Structure workspaces for items and documents can now include a property for the BPs that are linked to the selected item or document.

To integrate this property to existing workspace it is required to operate the Migration Tool from the Administrative Console.

Reference Designation


Reference designation used to support only one mode: Grouping. It was not possible to insert reference designations containing characters such as dash as part of the field.

The solution provided supports two modes of reference designation:

! Grouping When the system automatically creates list of references from a definition of a range.

! Non Grouping When each entry of reference designation considered being a regular text field that is not manipulated. This text field can be used without any character restrictions.

Note: To continue using the single Grouping mode requires a database change, for which the Upgrade Database Tool must be used.


Inquiry: 322398


It was not possible to use the same Reference Designator for two or more items if they were on same level in the BOM.

This problem is now resolved. The solution requires the use of the Upgrade Database Tool.

SSA PDM Issues | 4-3


Link manufacturers/ suppliers to item

Internal In PDM, manufacturers and suppliers could only be linked to items that were defined as “Standard Parts.”

This limitation is now removed. It is still required that the Item Type field specifies “Purchased.”

Vault parameters Inquiry: 344555


When Vault parameters were set to Automatically check out parent items, the system did not behave properly if the child item was purchased.

This problem is now solved and the system behaves the same for purchased and manufactured items.

Supporting special characters

Inquiry: 355727, 342649

Request: PLM-00000-00283 PLM-00000-00203

There was a problem with letters "µ" and “ß” in PDM file names.

This problem is now resolved.

Customization Inquiry: 329471


In PLM 8.0 SP3, no new attributes could be added to objects via the Customization Tool.


Security issues Inquiry: 351545


The password was displayed in the cfe-http.txt log file under the Server installation directory.


Delete files Internal When the user tries to delete a file from PDM, and the actual file is missing from the vault, the operation is now allowed.



Security Access Level

Inquiry: 242596


If a file is set with Security Access Level that is higher than the user’s, the user will not be able to view or access this file.

Note Implementing this topic requires the use of the Upgrade Database Tool.

Obsolete object Inquiry. 297562


If a BOM contained an OBSOLETE item, it was not possible to unlink this item from its UNDEFINED parent.


Obsolete object Inquiry. 312069


It was not possible to unlink an OBSOLETE document from a business process.


Working with SW drawing

Inquiry. 240874


Expanding the view window has problem when viewing SW drawing.


Site synchronization Inquiry. 287255


Setting a filter for file/document synchronization in the Administrative Console did not work.


Part list Inquiry. 334148


In PLM 8.0 SP3, no Item-child links (part list) could be created when system preferences were set to work without reference designation.




Item attributes Inquiry. 329596


ITEM fields CONFIG_ID, QUOTE_ID, QUOTE_REV were missing from the Customization Tool.

These fields are now present in addition to all the other item attributes.

Link folder/item Inquiry. 339750


Users can now link an existing UNDEFINED document to a RELEASED item.

Change future effectivity date

Inquiry. 401748


When an Administrator updates a released object and changes the Effective From date to an earlier date, the system will now ask the user if the previous revision should be fixed automatically. If, in response to that question, the Administrator clicks Yes, PDM now modifies the previous version’s Effective To date to match the Effective From date of the new version.

Delete markup Inquiry. 239707


It was not possible to delete a file that had a markup file.


Mask Inquiry. 239730


If was not possible to remove the Alternate Key for the Administrator Object Mask.




Documents and files Inquiry. 275599


When the user tried to link a file to a RELEASED document, the user received an error message only at the end of the linking process.

Now, when the user tries to link a file to a document and the document status is not UNDEFINED, the Link to Current Document option is disabled.

Classification Inquiry. 240213


In the Administrative Console when using the Save Tree to File option under Classification - Item, large names were added to more than one line in the .xls file.


Classification Inquiry. 307123


After a category was renamed it was not possible to rename another category.


Site synchronization Inquiry. 287255


It was not possible to update the filter condition for the site synchronization.


Workflow email notification

Inquiry. 286646


The mail notification used to be sent from "[email protected]" which sometimes was recognized as an invalid address by a random check on the mail server.

The solution enables the Administrator to define the proper sender address in table: SYS_CONFIG, field: PREF_VALUE, where CLASS_ID='*' and PREF_NAME='MAIL_FROM_ADDR'



BP history Inquiry. 294948


The titles in the BP history property did not match the content.


BP Delete Step Inquiry. 353143


If the BP was failed, it was possible to delete the step from which this BP has failed. The deletion of the step corrupted the BP.

It is now not allowed to delete the step from which the BP has failed.


Inquiry. 302538


It was not possible to search an item in the part list property according to reference designation.


Admin Console Inquiry. 301979


User Connection Manager was not accurate.

Now it displays only the users that are currently connected (except for the ECM connections that are still not accurate).

Check Out Inquiry. 305150


It was not possible to perform a selective check-out for objects that were linked to folders.


User Preferences Inquiry. 333886


The User Preferences -> Locations -> View Files path was not saved.




Send to Production Inquiry. 299932

Request: PLM-00000-00109, PLM-00000-00147

In some cases business processes hung in the Send to Production step.

A default value of five minutes is set for searching the Send to Production status file. In case the time ends, the step is now failing (and does not wait for the status forever).

This default value can be changed using the system environment variable: BPDM_WRK_CHECK_MINUTES. This value has to be set directly to the database.

Send to Production Inquiry. 352566


When a Baan ST-Item was sent to production the created .xml file was empty. This file caused problems when sent to ERP.

The Send to Production now checks for empty files before sending them to ERP.

Load Server Inquiry. 315561


The Load Server did not work properly when installed as a service.


File Server Inquiry. 303331


It was not possible to run the File Server as a service.


‘ba’ package Inquiry. 260890, 281469

Request: PLM-00000-00061, PLM-00000-00082

A specific configuration/customization in the ‘ba’ package did not work properly.




Baan 5c - ‘ba’ package

Inquiry. 301102


The Export Item process did not work properly and did not export all items from ERP to PDM.


Baan 5c - ‘ba’ package – TOP Project

Inquiry. 350247


Sending existing WBS element from PDM to ERP caused problems with the existing data of the WBS in ERP.

These problems are now resolved.

Workflow Send to Production

Internal The workflow that operated the Send to Production step operated “java” from the %JAVA_HOME% directory instead of %JAVA_HOME%\bin.


Workflow Send to Production

Inquiry. 299975 343490 395154 401953

Request: PLM-00000-00111, PLM-00000-00216

If more than one item is attached to the Send to Production step, PDM now behaves as follows:

! A separate .xml file is created for each item.

! If a specific item has a problem that prevents it from being sent to ERP (for example, as a result of an UNDEFINED child item), the .xml file will not be created, and no BP item will be sent to ERP.

Load Server Inquiry. 300119


The Import process sometimes creates empty .xml files that were not handled properly by the Load Server.


Integration with ERP LN

Inquiry. 281962


It was not possible to send to ERP LN an item twice on the same day.





Inquiry. 291731


The PDM Owner field in the ERP LN Integra-tion Configuration Tool (cfeerpmap.exe) did not work properly.



Inquiry. 305654


It was not possible to send a BOM to production as a result of a wrong value (No) in the Revision Control Indicator field.



Inquiry. 352617


The ERP LN integration process.xml log file did not log problems that were related to Open World Adapter.

This issue is now resolved, and Open World problems are also logged within the ERP LN integration log file.


Inquiry. 397092


There was a problem to transfer items from PDM to ERP when the search key had the character "µ" in the Search Key 1 field.

This problem was a result of converting the field to uppercase in the PDM ERP integration. This conversion was removed from the integration. An ERP LN solution is available (213410) that takes care of the conversion when the item is created in ERP LN.


PDM limitations


Task list Inquiry. 239676


After all attachments are getting approved to a specific task, it is still required to refresh the task itself in order to be able to approve it.

Units of measure and weight units

7906 Units of Measure and Weight Units used in PDM must be defined as Inventory Units in Baan ERP (IV/5).

In the Units by Unit Set (tcmcs0112m000) session, the required units must be marked with Yes in INV. Units that are not inventory units will not have conversion factors defined in PDM for the Weight Rollup calculation.

Redlining 11050 The user is not prompted to save unsaved redline changes when closing a workspace associated with a file that contains unsaved markup changes.

Classification attributes names

14463 Classification attributes names cannot contain more than a single consecutive space character.

Informix SSA PDM database creation

DC#163 When using Informix, an error occurs during the creation of one of the indexes on the ECM history table. This error can be ignored.

Informix and the workflow daemon

DC#164 When using Informix, the workflow daemon cannot be run as a service. Instead, it must be run as a batch process. This is an Informix-specific limitation.

Multi-select DC#90 Multi-select operations do not apply to Structure workspaces or registering files to SSA PDM via drag-and-drop operations.

File name character limitations

DC#207 Although it is possible to use the following characters as part of file names: & < > ‘ “

These characters should not be used, as the SSA PDM Integrations do not support them.



Multi-Object workspace

NA If you define a view that selects objects based on an attribute value that does not match the attribute value of a child object in a tree, the tree will be truncated before the child object.

Release Area 15774 The PLM server does not issue a warning message if the Release Area directory being defined does not exist.

Text Search 17317 It is currently not possible to search for text containing the “&” character.

Customization 18059 If you are using both PDM and ECM, note that it is not possible to add a reference attribute for an object unknown to ECM.

Workflow daemon as a service

18271 In some cases running the workflow daemon as a service causes the daemon process to function incorrectly. In such cases, the daemon should not be run as a service, but should be started from the Server Configuration Tool. See the Server Installation Guide for details.

Query dialog box 18533 In some cases, because of technical limitations, the Query dialog box opens behind the current open dialog box. Users should look for the Query icon on the main window’s toolbar.



Customization 18786 When using the Customization Tool, new attributes may be defined for PDM objects or the length of existing attributes may be modified to enable more data entry.

Field limitations in PLM 8.0 depend also on deployment. If you use Unicode, allocation is double (and limits are half).

! SQL Server max record (sum of all fields in table): 8000 bytes.

! Informix Dynamic Server 2000, Informix Dynamic Server, and INFORMIX-Universal Server allow 16 key parts (columnar or functional) and a width of 390 bytes.

! Informix SE supports 8 columns and a width of 126 bytes. Other Informix database servers allow 16 columns and 255 characters.

Character not supported

The following characters are not supported in key fields: %, *, ?, “, ‘


PDM - Baan ERP (IV/5) integration limitations


Alternative item suppliers

6799 Transfer of Item-Supplier links from Baan ERP (IV/5) to SSA PDM is currently not supported. This includes Item-Supplier and Item Code by Item Code System details.

Transfer of multiple WBS objects

9722 Multiple occurrences of WBS objects within a single structure cannot be transferred from SSA PDM to Baan IV Estimate Projects.

Customization 18210 When using the Customization Tool, new attributes may be defined for PDM objects or the length of existing attributes may be modified to enable more data entry. The new attributes may then be transferred to ERP by adding them to the field mapping of Gateway objects in the PDM Gateway Configuration.

Limitations:

! The total length of a Gateway object to be imported to Baan5.0c cannot exceed 2820 characters.

! The total length of a Gateway object to be imported to BaanIVc cannot exceed 2745 characters. This includes all data and tag names.

! Objects greater than 2820 or 2745 characters will not be imported using the PDM-ERP Integration for BaanERP or BaanIV (ba package). An error message will be generated and written in the Activity Log.