Teamcenter

Integration for I-
deas
12.2.0.2

User's Guide

eng00013 - Q
2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Manual History

NX Manager I- Teamcenter
Manual deas/ Engineering/ I-deas Publication
Revision Integration for I- Teamcenter Version Date
deas Version
Version

A — 7.0.3 9m2 December 2002

A1 — 7.0.3 9m2 February 2003

B 1.0 8.1.0.3 9m3 March 2003

C 2.0 8.1.1.5 10m1, 10m2 September 2003

D 3.0 8.1.1.5 10m3 December 2003

E 3.1 8.1.1.5 or higher, 10m3, 11 August 2004

9.1

F 4.0 9.1.2.x 10m1, 10m3, 11, 12 September 2005

G 4.3 9.1.3.4.b 11, 12 August 2006

H TcII 5.0 2005 SR1 MP1 12 October 2006

I TcII 5.1 2005 SR1 MP3 NX I-deas 5m1 November 2007

J TcII 6.0 Tc 2007.1 MP3 NX I-deas 5m2 May 2008

K TcII 6.1 Tc 2007.1 MP7 NX I-deas 6m1, NX I- October 2009

deas 6.1

L TcII 8.3 Tc 8.3 NX I-deas 6m2, NX I- September 2010

deas 6.1m1

M Note 1 Note 1 Note 1 March 2013

N TcII 10.1 Tc 10.1.0.1 NX I-deas 6.4, NX I- June 2014

deas 6.5

O TcII 11.2 Tc 11.2.1 NX I-deas 6.5, NX I- March 2016

deas 6.6

P TcII 12.2 Tc 12.2 or later NX I-deas 6.7, NX I- June 2020

deas 6.8

Q TcII 12.2.0.2 Tc 12.2.0.2 or later NX I-deas 6.7, NX I- August 2020

deas 6.8

Note 1:
Release of this guide only. For applicable software
versions, refer to the specific TcII software release.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3

© 2020 Siemens
 This edition obsoletes all previous editions.

4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 Contents

Manual History 3

Preface
Audience ─────────────────────────────────────────── 15
Organization ───────────────────────────────────────── 15
Conventions ───────────────────────────────────────── 16
Revision Marks ────────────────────────────────────────── 16
Note, Caution, and Warning Icons ───────────────────────────────
16
Names and Values ──────────────────────────────────────── 16
Command Line Entries, File Contents, and Code ──────────────────────
18
Syntax Definitions ────────────────────────────────────────
18
Teamcenter Documentation ─────────────────────────────── 19
Submitting Comments ─────────────────────────────────── 20
Software Copyright and Trademark Notices ───────────────────── 20

Introduction
Understanding Integration for I-deas ───────────────────────── 1-1
Integration for I-deas Architecture ────────────────────────────── 1-1
Integration for I-deas Data Management ────────────────────────── 1-2
Understanding Groups ────────────────────────────────── 1-3
Sharing Data With Nongroup Members ─────────────────────────── 1-3
Planning Your Groups ────────────────────────────────────── 1-4
Creating and Managing Groups ──────────────────────────────── 1-4
Understanding Group Roles in Integration for I-deas ─────────────── 1-5
Understanding My Teamcenter and the Integration for I-deas Window ─── 1-5
My Teamcenter as a Client ─────────────────────────────────── 1-5
My Teamcenter Users ────────────────────────────────────── 1-6
Running My Teamcenter ──────────────────────────────────── 1-7
Teamcenter and I-deas Supported Versions ───────────────────── 1-7
Local Languages ────────────────────────────────────── 1-7
Installation of Integration for I-deas ───────────────────────── 1-8

Preferences
List of Preferences ───────────────────────────────────── 2-1
Integration for I-deas Preferences I ────────────────────────── 2-7
Integration for I-deas Preferences II ───────────────────────── 2-62
Specific Preference Data ──────────────────────────────── 2-75
IDEAS_external_owning_user_name ──────────────────────────── 2-75
Disabling Preferences For an Integration for I-deas Session ────────── 2-76
Engineering Translation Services Preferences ─────────────────── 2-76
Disable Preferences When Running ETS ────────────────────── 2-88

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5

© 2020 Siemens
 Getting Started
Launching My Teamcenter and Integration for I-deas From I-deas ────── 3-1
Launching Integration for I-deas and I-deas From My Teamcenter ────── 3-2
Launching My Teamcenter ─────────────────────────────────── 3-2
Launching Integration for I-deas and I-deas ───────────────────────── 3-2
Launching Integration for I-deas and I-deas From Structure Manager ──── 3-3
Connection Issues ───────────────────────────────────── 3-3
Non-Integration for I-deas Users ──────────────────────────── 3-4
Understanding the My Teamcenter Interface ──────────────────── 3-4
My Teamcenter ─────────────────────────────────────── 3-4
My Teamcenter Tree Pane ─────────────────────────────────── 3-4
Summary Pane ────────────────────────────────────────── 3-4
Details Pane ─────────────────────────────────────────── 3-4
Viewer Pane ─────────────────────────────────────────── 3-4
Referencers Pane ──────────────────────────────────────── 3-5
Display Data Pane ──────────────────────────────────────── 3-5
Menu Bar ───────────────────────────────────────────── 3-5
Integration for I-deas Window ───────────────────────────── 3-6
Toolbar ────────────────────────────────────────────── 3-7
Understanding Teamcenter Objects, Revisions, and Versions ───────── 3-7
Items ──────────────────────────────────────────────── 3-8
Item Revisions ────────────────────────────────────────── 3-8
Datasets ────────────────────────────────────────────── 3-8
BOMView Revisions (BVR) ─────────────────────────────────── 3-9
Closing My Teamcenter and Exiting Teamcenter ───────────────── 3-9
Closing My Teamcenter ───────────────────────────────────── 3-9
Exiting Teamcenter Rich Client ──────────────────────────────── 3-9
Programmatic Access to Integration for I-deas ─────────────────── 3-9
Using Integration for I-deas Openess ──────────────────────────── 3-10
Running the Openness Sample Application ──────────────────────── 3-11
Openness Troubleshooting ────────────────────────────────── 3-12
IDS User Exits for Migration ───────────────────────────────── 3-13
Running Custom Applications Created in NX Manager I-deas 4.3 or Earlier ───── 3-13

Using Integration for I-deas: Working With Modeling Data

One Version Per Revision In Teamcenter ─────────────────────── 4-1
Activating One Version Per Revision ───────────────────────────── 4-1
Using One Version Per Revision ──────────────────────────────── 4-2
Mapping Drawings For One Version Per Revision ───────────────────── 4-3
Mapping a Drawing of Multiple Models ─────────────────────────── 4-3
Mapping Standalone Drawings ──────────────────────────────── 4-4
Mapping FEMs For One Version Per Revision ──────────────────────── 4-5
Changing the Mapping of Drawings and FEMS ─────────────────────── 4-5
Warnings for Referenced but Modified condition ───────────────── 4-6
Change Status ────────────────────────────────────────── 4-6
Add Parent ──────────────────────────────────────────── 4-6
Send to I-deas ────────────────────────────────────────── 4-6

6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 Contents

Update to Latest ───────────────────────────────────────── 4-7

Save to Teamcenter ─────────────────────────────────────── 4-7
JT Files ──────────────────────────────────────────── 4-7
Creating JT Files ───────────────────────────────────────── 4-7
Viewing Assemblies ────────────────────────────────────── 4-10
Adding JT Component to an Assembly ─────────────────────────── 4-10
Location of Saved Harnesses ───────────────────────────────── 4-10
JT File Creation Errors ───────────────────────────────────── 4-11
GUID Considerations When Creating an I-deas Dataset ───────────── 4-11
I-deas GUIDs ────────────────────────────────────────── 4-11
Issues With Datasets and I-deas GUIDs ─────────────────────────── 4-12
Methods and Issues When Working With Modeling Data ──────────── 4-13
Different dataset types in Item Revisions ───────────────────────── 4-14
Support for Teamcenter 128 character limit ──────────────────── 4-15
Item ID ────────────────────────────────────────────── 4-16
Item Name ─────────────────────────────────────────── 4-16
Revision ID ─────────────────────────────────────────── 4-16
Teamcenter 128 character limit disabled ───────────────────────── 4-17
Customizing the Toolbar ──────────────────────────────── 4-17
Filtering the Display in the Integration for I-deas Window ─────────── 4-18
Advanced Filtering ─────────────────────────────────────── 4-18
Save Data: Methods ─────────────────────────────────── 4-19
Integration for I-deas Save Menu Options ───────────────────────── 4-19
Saving Large Assemblies in Teamcenter ────────────────────────── 4-20
Saving Drawing Sets ────────────────────────────────────── 4-21
Saving ACF Parts ──────────────────────────────────────── 4-21
Saving Assemblies With Precise BOM ──────────────────────────── 4-21
Saving New or Updated Modeling Items to Teamcenter ──────────── 4-22
Saving to Teamcenter Dialog Box ────────────────────────────── 4-22
Saving Checked-Out Modeling Items in Teamcenter ────────────── 4-27
Clean Database of Items On Failed Checkin ──────────────────── 4-28
Creating CGM Datasets for Drawings ──────────────────────── 4-28
Creating New Item Revisions ───────────────────────────── 4-29
Perform Revise On Any Item Revision ─────────────────────────── 4-30
Purging Item Revisions ───────────────────────────────── 4-31
Creating I-deas Datasets ──────────────────────────────── 4-31
Deleting I-deas Modeling Data Using Teamcenter ──────────────── 4-32
Deleting I-deas Modeling Data Using Integration for I-deas ────────── 4-33
Renaming/Renumbering Items ──────────────────────────── 4-34
Derived I-deas Parts ────────────────────────────────────── 4-35
Moving Items ─────────────────────────────────────── 4-35
Copying Items ─────────────────────────────────────── 4-35
Creating Bins ─────────────────────────────────────── 4-36
Bin Item on Workbench ──────────────────────────────────── 4-37
Remote Checkout ───────────────────────────────────── 4-37
Compressing I-deas CAD Files ───────────────────────────── 4-37
Improving Performance ───────────────────────────────── 4-38

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7

© 2020 Siemens
 Apply a Status and Create a New Revision In One Step ───────────── 4-39
Attribute Mapping ──────────────────────────────────── 4-41
Mapping I-deas Part Number Attributes ────────────────────── 4-41
Mapping I-deas User Attributes to Teamcenter Attributes ─────────── 4-42
Defining the Attribute Type ───────────────────────────────── 4-43
Special Attributes ─────────────────────────────────────── 4-44
Master Variable for Part Number and User Attributes ────────────── 4-44
Mapping Attributes with BMNR Defined For Item Name ──────────── 4-45
Attribute mapping performance ─────────────────────────── 4-46
Attribute Customization User Exits ────────────────────────── 4-46
Change Ownership and Right To Modify For Datasets ────────────── 4-47
I-deas Right to Modify Utility ───────────────────────────────── 4-47
Working in Multi-Site Collaboration ───────────────────────── 4-49
Enabling Checkin/Checkout ───────────────────────────────── 4-49
Multi-Site Relationship Types ──────────────────────────────── 4-49
Remote Import Relationship Types ───────────────────────────── 4-50
Remote Import Revisions and Versions ─────────────────────────── 4-50
Preferences For Automatically Selecting Relationship Types ────────────── 4-51

Using Integration for I-deas: Sending Modeling Data From My

Teamcenter to I-deas
I-deas Version Issues When Accessing I-deas Data ───────────────── 5-2
I-deas ─────────────────────────────────────────────── 5-3
I-deas With Integration for I-deas ─────────────────────────────── 5-3
I-deas Package Imported into Teamcenter ───────────────────────── 5-3
Working With Item Revisions ────────────────────────────── 5-3
Export Directory Name Length ───────────────────────────── 5-4
Unsupported Characters Handled During Send to I-deas ───────────── 5-4
Sending I-deas Modeling Data to I-deas ─────────────────────── 5-5
Sending Related Drawings ─────────────────────────────────── 5-7
Automatically Send an Item to a Bin ───────────────────────────── 5-7
Increasing Performance When Sending Items to I-deas ────────────────── 5-9
HAM Medic ─────────────────────────────────────────── 5-10
Send to I-deas From a Remote Site ───────────────────────────── 5-11
Detecting Referenced But Modified Condition During Send To I-deas ──── 5-11
Items Modified in Structure Manager ──────────────────────── 5-12
Assembly in a Model File ─────────────────────────────────── 5-12
Assembly Outside of a Model File ────────────────────────────── 5-13
ACF Relations ────────────────────────────────────────── 5-13
File Status Options ──────────────────────────────────── 5-13
Changing the Checkout Status of an Item ───────────────────── 5-15
Changing the Status of Pruned or Faceted Parts ───────────────── 5-16
Version Numbering for NX assemblies and external parts ─────────── 5-16
Canceling a Checkout ────────────────────────────────── 5-17
Sending NX Parts to I-deas ─────────────────────────────── 5-17
Default Functionality ───────────────────────────────────── 5-19

8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 Contents

Sending NX Assemblies to I-deas ─────────────────────────── 5-19

Sending Revisions of the Same Part to I-deas ─────────────────── 5-20
I-deas Derived Part and NX Part Are Not Synchronized ───────────── 5-21
Integration for I-deas Window ──────────────────────────────── 5-21
NX Source Part Version and Revision Attributes ───────────────────── 5-22
Updating ───────────────────────────────────────────── 5-22

Using Integration for I-deas: Updating and Synchronizing Data

Finding Out-of-Date Modeling Data ────────────────────────── 6-1
Out-of-Date Modeling Data in Interoperability ─────────────────────── 6-2
Synchronization of Model Files ───────────────────────────── 6-2
Synchronize Dialog ─────────────────────────────────────── 6-3
Synchronize Menu Selection ────────────────────────────────── 6-3
Synchronize Preference ───────────────────────────────────── 6-4
Synchronize Part Name and Part Number ────────────────────────── 6-4
Updating Model File Data ──────────────────────────────── 6-5
Updating NX Assemblies ───────────────────────────────── 6-7

Using Integration for I-deas: Managing Assembly Structures

Overview ─────────────────────────────────────────── 7-1
View Data for I-deas Assemblies ─────────────────────────────── 7-1
Assembly Configuration in Structure Manager ─────────────────────── 7-1
View Associated PMI Instances and Geometry ─────────────────────── 7-2
Wire Harness Assemblies ──────────────────────────────────── 7-2
Component Versions ────────────────────────────────────── 7-3
Legacy Assemblies ──────────────────────────────────────── 7-3
Assemblies Containing Components From Other CAD System ───────────── 7-3
Orphaned JT Files ──────────────────────────────────────── 7-3
Saving I-deas Assemblies in Teamcenter ─────────────────────── 7-3
Setting BOMView Revision Precise Preference ─────────────────────── 7-4
Transformation Matrixes ──────────────────────────────────── 7-4
Transformation Matrix Caveats ──────────────────────────────── 7-5
Saving I-deas Configurations as Teamcenter Assembly Arrangements ──── 7-5
General Considerations ───────────────────────────────────── 7-6
Harnesses ───────────────────────────────────────────── 7-6
Configurations Stored ────────────────────────────────────── 7-6
Store configurations command line utility ────────────────────── 7-7
General considerations ───────────────────────────────────── 7-7
Modify/Create Translation service access rules ─────────────────────── 7-8
Input to the Store Configurations Utility ─────────────────────────── 7-9
Running the Store Configurations Utility ────────────────────────── 7-10
Aborting the Store Configurations Utility ───────────────────────── 7-11
Output From the Store Configurations Utility ─────────────────────── 7-11
Using Top-Down Design to Create Assembly Structures in Teamcenter ─── 7-12
Basic Top-Down Design ──────────────────────────────────── 7-12
Using Multiple Select to Add I-deas Datasets ─────────────────────── 7-12
Sending Assemblies to I-deas From Structure Manager ───────────── 7-13

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 9

© 2020 Siemens
 Pruning Parts ─────────────────────────────────────── 7-14

Data Sharing
Integration for I-deas Data Sharing ────────────────────────── 8-1
Item Ownership ───────────────────────────────────────── 8-1
What Is Integration for I-deas Data Sharing? ──────────────────────── 8-2
I-deas Version Issues with Data Sharing ─────────────────────────── 8-3
Changing Item Revision Master and Dataset Properties ────────────────── 8-4
Data Sharing Export Process ────────────────────────────────── 8-4
Exporting with Transfer of Ownership ──────────────────────────── 8-5
Data Sharing Import Process ────────────────────────────────── 8-5
Importing with Transfer of Ownership ──────────────────────────── 8-6
How to Export a Data Sharing Package ──────────────────────── 8-7
Creating a Package ─────────────────────────────────────── 8-7
What Happens When You Create a Data Package? ──────────────────── 8-10
How to Import a Data Sharing Package ─────────────────────── 8-11
Creating Items, Item Revisions, and Datasets ─────────────────────── 8-13
Customizing Item Type ──────────────────────────────────── 8-14
Import Ownership Considerations ────────────────────────── 8-14
Import I-deas Design Data for Reference ────────────────────────── 8-14
Import I-deas Design Data for Modification ──────────────────────── 8-15
Other Import Options ─────────────────────────────────── 8-2
Change Owning User For I-deas Package Import ───────────────────── 8-16
Pre-Validate I-deas Package for Import ─────────────────────────── 8-17
Skipping Items With a Different Item ID In the I-deas Package During Import ──── 8-17
Import Items Into Subfolders ───────────────────────────────── 8-17
Import Standalone Drawings ───────────────────────────────── 8-18
Import Legacy Assemblies ────────────────────────────────── 8-19
Scope for Preferences ────────────────────────────────── 8-19

Glossary A-1

Integration for I-deas Troubleshooting

Adding Data For Troubleshooting ─────────────────────────── B-3
Increasing Java memory ───────────────────────────────── B-4
Symptom ───────────────────────────────────────────── B-5
Cause ─────────────────────────────────────────────── B-5
Solution ────────────────────────────────────────────── B-5
Symptom ───────────────────────────────────────────── B-6
Cause ─────────────────────────────────────────────── B-6
Solution ────────────────────────────────────────────── B-6
Symptom ───────────────────────────────────────────── B-8
Cause ─────────────────────────────────────────────── B-8
Solution ────────────────────────────────────────────── B-8
Symptoms ───────────────────────────────────────────── B-9
Cause ─────────────────────────────────────────────── B-9
Solution ────────────────────────────────────────────── B-9

10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 Contents

Symptom ──────────────────────────────────────────── B-11

Cause ─────────────────────────────────────────────── B-11
Solution ───────────────────────────────────────────── B-11
Symptom ──────────────────────────────────────────── B-12
Cause ─────────────────────────────────────────────── B-12
Solution ───────────────────────────────────────────── B-12
Symptom ──────────────────────────────────────────── B-13
Cause ─────────────────────────────────────────────── B-13
Solution ───────────────────────────────────────────── B-13
Symptom ──────────────────────────────────────────── B-14
Cause ─────────────────────────────────────────────── B-14
Solution ───────────────────────────────────────────── B-14
Symptom ──────────────────────────────────────────── B-15
Cause ─────────────────────────────────────────────── B-15
Solution ───────────────────────────────────────────── B-15
Symptom ──────────────────────────────────────────── B-16
Cause ─────────────────────────────────────────────── B-16
Solution ───────────────────────────────────────────── B-16
Symptom ──────────────────────────────────────────── B-17
Cause ─────────────────────────────────────────────── B-17
Solution ───────────────────────────────────────────── B-17
Symptom ──────────────────────────────────────────── B-18
Cause ─────────────────────────────────────────────── B-18
Solution ───────────────────────────────────────────── B-18
Symptom ──────────────────────────────────────────── B-19
Cause ─────────────────────────────────────────────── B-19
Solution ───────────────────────────────────────────── B-19
Symptom ──────────────────────────────────────────── B-20
Cause ─────────────────────────────────────────────── B-20
Solution ───────────────────────────────────────────── B-20
Symptom ──────────────────────────────────────────── B-21
Cause ─────────────────────────────────────────────── B-21
Solution ───────────────────────────────────────────── B-21
Symptom ──────────────────────────────────────────── B-22
Cause ─────────────────────────────────────────────── B-22
Solution ───────────────────────────────────────────── B-22
Symptom ──────────────────────────────────────────── B-23
Cause ─────────────────────────────────────────────── B-23
Solution ───────────────────────────────────────────── B-23
Symptom ──────────────────────────────────────────── B-24
Cause ─────────────────────────────────────────────── B-24
Solution ───────────────────────────────────────────── B-24
Symptom ──────────────────────────────────────────── B-25
Cause ─────────────────────────────────────────────── B-25
Solution ───────────────────────────────────────────── B-25
Symptom ──────────────────────────────────────────── B-26
Cause ─────────────────────────────────────────────── B-26
Solution ───────────────────────────────────────────── B-26
Symptom ──────────────────────────────────────────── B-27

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 11

© 2020 Siemens
 Cause ─────────────────────────────────────────────── B-27
Solution ───────────────────────────────────────────── B-27
Symptom ──────────────────────────────────────────── B-28
Cause ─────────────────────────────────────────────── B-28
Solution ───────────────────────────────────────────── B-28
Symptom ──────────────────────────────────────────── B-29
Cause ─────────────────────────────────────────────── B-29
Solution ───────────────────────────────────────────── B-29
Symptom ──────────────────────────────────────────── B-30
Cause ─────────────────────────────────────────────── B-30
Solution ───────────────────────────────────────────── B-30
Symptom ──────────────────────────────────────────── B-31
Cause ─────────────────────────────────────────────── B-31
Solution ───────────────────────────────────────────── B-31
Symptom ──────────────────────────────────────────── B-32
Cause ─────────────────────────────────────────────── B-32
Solution ───────────────────────────────────────────── B-32
Symptom ──────────────────────────────────────────── B-33
Cause ─────────────────────────────────────────────── B-33
Solution ───────────────────────────────────────────── B-33
Symptom ──────────────────────────────────────────── B-34
Cause ─────────────────────────────────────────────── B-34
Solution ───────────────────────────────────────────── B-34
Symptom ──────────────────────────────────────────── B-35
Cause ─────────────────────────────────────────────── B-35
Solution ───────────────────────────────────────────── B-35
Symptom ──────────────────────────────────────────── B-36
Cause ─────────────────────────────────────────────── B-36
Solution ───────────────────────────────────────────── B-36
Symptom ──────────────────────────────────────────── B-37
Cause ─────────────────────────────────────────────── B-37
Solution ───────────────────────────────────────────── B-37
Symptom ──────────────────────────────────────────── B-38
Cause ─────────────────────────────────────────────── B-38
Solution ───────────────────────────────────────────── B-38
Symptom ──────────────────────────────────────────── B-39
Cause ─────────────────────────────────────────────── B-39
Solution ───────────────────────────────────────────── B-39
Symptom ──────────────────────────────────────────── B-40
Cause ─────────────────────────────────────────────── B-40
Solution ───────────────────────────────────────────── B-40
Symptom ──────────────────────────────────────────── B-41
Cause ─────────────────────────────────────────────── B-41
Solution ───────────────────────────────────────────── B-41
Symptom ──────────────────────────────────────────── B-42
Cause ─────────────────────────────────────────────── B-42
Solution ───────────────────────────────────────────── B-42
Symptom ──────────────────────────────────────────── B-43
Cause ─────────────────────────────────────────────── B-43

12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 Contents

Solution ─────────────────────────────────────────────
B-43
Symptom ────────────────────────────────────────────
B-44
Cause ───────────────────────────────────────────────
B-44
Solution ─────────────────────────────────────────────
B-44
Symptom ────────────────────────────────────────────
B-45
Cause ───────────────────────────────────────────────
B-45
Solution ─────────────────────────────────────────────
B-45
Symptom ────────────────────────────────────────────
B-46
Cause ───────────────────────────────────────────────
B-46
Solution ─────────────────────────────────────────────
B-46
Symptom ────────────────────────────────────────────
B-47
Cause ───────────────────────────────────────────────
B-47
Solution ─────────────────────────────────────────────
B-47
Symptom ────────────────────────────────────────────
B-48
Cause ───────────────────────────────────────────────
B-48
Solution ─────────────────────────────────────────────
B-48
Symptom ────────────────────────────────────────────
B-49
Cause ───────────────────────────────────────────────
B-49
Solution ─────────────────────────────────────────────
B-49
Symptom ────────────────────────────────────────────
B-51
Cause ───────────────────────────────────────────────
B-51
Solution ─────────────────────────────────────────────
B-51
Symptom ────────────────────────────────────────────
B-56
Cause ───────────────────────────────────────────────
B-56
Solution ─────────────────────────────────────────────
B-56
Release Notes ─────────────────────────────────────── B-56
Customer Support ──────────────────────────────────── B-56

Index ─ Index-1

Figures

7-1. I-deas Assembly Saved in Teamcenter ───────────────────── 7-4

Tables

2-1. Integration for I-deas Preferences ──────────────────────── 2-7

5-1. Export Marking Options ───────────────────────────── 5-13
5-2. Export Options by Dataset Type ──────────────────────── 5-14

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 13

© 2020 Siemens
14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Preface
This document describes the installation, setup, and usage of Teamcenter Integration for I-deas®.

Integration for I-deas integrates Teamcenter and I-deas to provide a single authoring and data
management environment.

Note:
This document supplements the Teamcenter Help Library. If you find information here
inconsistent with that found in the Teamcenter Help Library, contact the Global Technical Access
Center (GTAC) for clarification.

Audience
The reader of this guide should be an experienced I-deas data management administrator with
additional experience administering Teamcenter.

Organization
This manual contains the following chapters and appendix:

Chapter Introduction explains the Integration for I-deas architecture, and basic
data management concepts.

Chapter Preferences describes the preferences used in Integration for I-deas.

Chapter Getting Started describes terms and concepts used in Integration for I-
deas. This chapter also explains how to launch and exit Integration for I-
deas.

Chapter Using Integration for I-deas: Working With Modeling Data explains
how to work with I-deas model file data using Integration for I-deas.

Chapter Using Integration for I-deas: Sending Modeling Data From My

Teamcenter to I-deas explains how to send data being managed by
Teamcenter to the I-deas application for reference or modification.

Chapter Using Integration for I-deas: Updating and Synchronizing Data

explains how to locate version inconsistencies between the data in the I-
deas model file and that stored in the Teamcenter database and also
describes methods for updating and synchronizing the data.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 15

© 2020 Siemens
 Chapter Using Integration for I-deas: Managing Assembly Structures describes
how assemblies can be managed in Teamcenter and transferred between
I-deas and Teamcenter.

Chapter Data Sharing describes how to import data from an I-deas installation
into an Integration for I-deas installation and how to export data I-deas
data stored in Teamcenter to an I-deas installation.

Appendix Glossary describes Teamcenter terminology.

Appendix Integration for I-deas Troubleshooting describes steps to resolve

problems in an Integration for I-deas installation.

Conventions
This manual uses the conventions described in the following sections.

Revision Marks
Technical changes are marked by a bar adjacent to the changed text.

Note, Caution, and Warning Icons

The following icons represent note, caution, and warning messages:

Note:
A note icon identifies general instructions or comments that need to be emphasized.

Caution:
A caution icon identifies practices that can either produce results contrary to what you expect or
result in damage to software or data.

Warning:
A warning icon identifies practices that could result in permanent loss of data or software.

Names and Values

This manual represents system names, file names, and values in fonts that help you interpret the name
or value. For example:

16 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 The file name is pom_schema_server-name_sid.

The conventions are:

Bold Bold font represents unvarying text or numbers within a name or value.
Capitalization is as it appears.
In the preceding example, pom_schema_ identifies an unvarying portion of the
name.

Italic Italic font represents text or numbers that vary. The characters in italic text
describe the entry. Letters are shown in lowercase, but the varying text may
include uppercase letters.
In the preceding example, server-name and sid represent varying portions of the
name.

text-text A hyphen separates two words that describe a single entry.

In the preceding example, server-name is a single value.

For example, the name of the pom_schema_server-name_sid file may be:

pom_schema_Blue5_f731

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 17

© 2020 Siemens
 Command Line Entries, File Contents, and
Code
This manual represents command line input and output, the contents of system files, and computer
code in fonts that help you understand how to enter text or to interpret displayed text. For example, the
following line represents a command entry:

install –regen_schema_file —u=user-name —p=password —g=group

The conventions are:

Monospace Monospace font represents text or numbers you enter on a command line, the
computer's response, the contents of system files, and computer code.
Capitalization and spacing are shown exactly as you must enter the characters or
as the computer displays the characters.
In the preceding example, -regen_schema_file identifies an unvarying
portion of the command.

Italic Italic font represents text or numbers that vary. The words in italic text describe
the entry.
The words are shown in lowercase letters, but the varying text may include
uppercase letters. When entering text, use the case required by the system.
In the preceding example, user-name, password, and group identify varying
portions of the command.

text-text A hyphen separates two words that describe a single entry.

In the preceding example, user-name is a single entry in the command.

The following example is a correct entry for the preceding regen_schema_file command:

install -regen_schema_file —u=infodba —p=KLH3b —g=dba

Syntax Definitions
This manual uses a set of conventions to define the syntax of Teamcenter commands, functions, and
properties. Following is a sample syntax format:

harvester_jt.pl [bookmark-file-name bookmark-file-name ...]

[directory-name directory-name ...]

18 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 The conventions are:

Bold Bold text represents words and symbols you must enter exactly as shown.
In the preceding example, you enter harvester_jt.pl exactly as shown.

Italic Italic text represents values that you supply.

In the preceding example, you supply values for bookmark-file-name and directory-
name.

text-text A hyphen separates two words that describe a single value.

In the preceding example, bookmark-file-name is a single value.

[] Brackets represent optional elements.

... An ellipsis indicates that you can repeat the preceding element.

Following are examples of correct syntax for the harvester_jt.pl: command:

harvester_jt.pl
harvester_jt.pl assembly123.bkm
harvester_jt.pl assembly123.bkm assembly124.bkm assembly125.bkm
harvester_jt.pl AssemblyBookmarks

Teamcenter Documentation
Teamcenter documentation is provided as online help and as printable manuals:

• You can access online help by choosing Help from the menu bar of a Teamcenter rich client
application or by clicking one of the links under the Help icon in the Teamcenter thin client user
interface.

• You can access the printable manuals from the Teamcenter Documentation CD-ROM. To view the PDF-
formatted manuals, use Adobe Acrobat Reader, downloadable free-of-charge from Adobe Systems
Incorporated at the following URL:

http://www.adobe.com

Acrobat Reader allows you to view these manuals online and print selected pages, sections, or the
entire manual. Siemens Digital Industries Software grants permission for Teamcenter users to print,
duplicate, and distribute this documentation.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 19

© 2020 Siemens
 Submitting Comments
Portions of Teamcenter software are provided by third-party vendors. Special agreements with these
vendors require Siemens Digital Industries Software to handle all problem reports concerning the
software they provide. Please submit all comments directly to Siemens Digital Industries Software.

Submit incident reports to the online support center.

https://support.sw.siemens.com/en-US/

Software Copyright and Trademark Notices

© 2020 Siemens. All Rights Reserved. This software and related documentation are proprietary to
Siemens Industry Software Inc. LIMITATIONS TO U.S. GOVERNMENT RIGHTS. UNPUBLISHED - RIGHTS
RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. This computer software and related
computer software documentation have been developed exclusively at private expense and are provided
subject to the following rights: If this computer software and computer software documentation qualify
as "commercial items" (as that term is defined in FAR 2.101), their use, duplication or disclosure by the
U.S. Government is subject to the protections and restrictions as set forth in the Siemens Digital
Industries Software commercial license for the software and/or documentation, as prescribed in FAR
12.212 and FAR 27.405(b)(2)(i) (for civilian agencies) and in DFARS 227.7202-1(a) and DFARS
227.7202-3(a) (for the Department of Defense), or any successor or similar regulation, as applicable or
as amended from time to time. If this computer software and computer documentation do not qualify as
"commercial items," then they are "restricted computer software" and are provided with "restrictive
rights," and their use, duplication or disclosure by the U.S. Government is subject to the protections and
restrictions as set forth in FAR 27.404(b) and FAR 52-227-14 (for civilian agencies), and DFARS
227.7203-5(c) and DFARS 252.227-7014 (for the Department of Defense), or any successor or similar
regulation, as applicable or as amended from time to time. Siemens Digital Industries Software, 5800
Granite Parkway, Suite 600, Plano, Texas 75024.

Java and all Java-based marks are trademarks or registered trademarks of Oracle, Inc. in the United
States and other countries.

A list of relevant Siemens Digital Industries Software trademarks can be found here. All other
trademarks or registered trademarks belong to their respective holders.

20 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2

© 2020 Siemens
 1. Introduction
Understanding Integration for I-deas ───────────────────────── 1-1
Integration for I-deas Architecture ────────────────────────────── 1-1
Integration for I-deas Data Management ────────────────────────── 1-2
Understanding Groups ────────────────────────────────── 1-3
Sharing Data With Nongroup Members ─────────────────────────── 1-3
Planning Your Groups ────────────────────────────────────── 1-4
Creating and Managing Groups ──────────────────────────────── 1-4
Understanding Group Roles in Integration for I-deas ─────────────── 1-5
Understanding My Teamcenter and the Integration for I-deas Window ─── 1-5
My Teamcenter as a Client ─────────────────────────────────── 1-5
My Teamcenter Users ────────────────────────────────────── 1-6
Running My Teamcenter ──────────────────────────────────── 1-7
Teamcenter and I-deas Supported Versions ───────────────────── 1-7
Local Languages ────────────────────────────────────── 1-7
Installation of Integration for I-deas ───────────────────────── 1-8

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 1. Introduction
This chapter presents an overview of Integration for I-deas.

Understanding Integration for I-deas

Integration for I-deas is a product that integrates Teamcenter and I-deas, an integrated CAD/CAM/CAE
authoring tool, to provide a single data management environment for users. Integration for I-deas users
author their data in I-deas and manage the data in Teamcenter using the My Teamcenter application.
Assembly structures can be created and maintained in Structure Manager and sent to I-deas.

Integration for I-deas has two main components:

• I-deas
The CAD/CAM/CAE application in which data is authored.

• My Teamcenter
The data management interface for Integration for I-deas users. Users can transfer data between I-
deas model files and Teamcenter volumes.

Integration for I-deas Architecture

Teamcenter provides two architecture models: two-tier and four-tier. Integration for I-deas can be
installed with either architecture.

Teamcenter Rich Client and My Teamcenter communicate with a Teamcenter server. Because I-deas and
the Teamcenter server cannot communicate directly with one another, all communication between the
two is handled through My Teamcenter using an Orbix daemon.

You must have a separate I-deas installation for each Rich Client and you can run only one Integration
for I-deas session per workstation.

Note:
For additional information about two-tier and four-tier architectures, see the Teamcenter
documentation.

Two-Tier Architecture

The Teamcenter two-tier architectural model contains:

• Client tier
The client tier comprises the Teamcenter rich clients.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 1-1
© 2020 Siemens
 1. Introduction

The Teamcenter server runs on the client workstation. Integration for I-deas runs on the client tier
with the Teamcenter server and rich client.

• Resource tier
The resource tier comprises a database server, database, volumes, and file servers.

In the two-tier model, you deploy the Teamcenter rich client, which includes the local server, and the
optional applications that integrate with the rich client (including Integration for I-deas) on the client
workstation. Typically, the database server, volumes, and file servers are installed on one or more
separate computers.

The Teamcenter File Management System (FMS) and Teamcenter File Services (TCFS) manage the rich
client access to volumes.

Four-Tier Architecture

The Teamcenter four-tier architecture model contains:

• Client tier
The client tier comprises the Teamcenter clients: the thin client, rich client, and WebDAV client.
Integration for I-deas runs on the client tier with the rich client.

• J2EE Web tier

The J2EE Web tier is a Java application that runs in a Java 2 Enterprise Edition (J2EE) application
server, such as BEA WebLogic, and is responsible for communication between the client tier and
enterprise tier.
The Web tier application also includes the Application Interface Web Service (AIWS), WebDAV service,
Teamcenter DIS Adapter, and thin client.

• Enterprise tier
The enterprise tier comprises a configurable pool of Teamcenter C++ server processes and a server
manager. The enterprise tier retrieves data from and stores data in the database. A server manager
controls a pool of Teamcenter server processes.

• Resource tier
The resource tier comprises a database server, database, volumes, and file servers.

Integration for I-deas Data Management

Consider the following topics when managing Integration for I-deas data.

Storage Locations for Integration for I-deas Data

All data stored within Teamcenter is stored in volumes. For more information, see Organization Help.

1-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Data Management Process

Data Management Process

In Integration for I-deas, the overall data management process is as follows:

1. Create or modify geometry data in the I-deas model file.

2. Using My Teamcenter, save the data in Teamcenter.

3. Check out or reference the data from Teamcenter.

4. When the data is finalized, release it with a workflow process. For more information, see Workflow
Viewer Help.

5. If the release data needs to be updated, perhaps for the next release of the product, create a new
item revision in My Teamcenter.

6. Check the data out to your I-deas model for modification. The data management cycle repeats.

Note:
You are not required to perform all of these steps in a single Integration for I-deas session or
perform them in this order. The process described is only a typical data management cycle.

Understanding Groups
Integration for I-deas uses groups to organize information and create a shared work environment for
product development. A group is a cluster of users working sharing data and working on a common
design task. Groups consist of roles reflecting the functions performed by various group members.
Groups are created as objects in the database to which users are associated through role assignments.

Access to data is granted to a group. Group roles determine which members have various types of access
to the data.

Sharing Data With Nongroup Members

In addition to sharing data with your group, you can also share data with users who are not members of
your group.

You can share group data with the following users:

• Other groups in your Integration for I-deas installation.

Through My Teamcenter, the group sharer designates which groups have access to your data. For
more information, see Navigator Help.

• Other Teamcenter users.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 1-3
© 2020 Siemens
 1. Introduction

When you release data, it becomes available to other Teamcenter users who do not have access to
Integration for I-deas. However, these users must have access privileges to the objects in order to see
the data.

• I-deas data installations.

Through My Teamcenter, you can share I-deas data from your Integration for I-deas installation with
an I-deas data installation.

Planning Your Groups

Consider the following topics when planning your groups. These topics highlight the factors that affect
users' access to Integration for I-deas data.

Assigning Group Roles

When you assign a group member to a role, keep in mind that the group member has access privileges
through that role to all data in the group. For example, a group member with the group author role
could have permission to modify all data, not just data in a certain folder or state.

For more information, see Understanding Group Roles in Integration for I-deas, later in this chapter.

Data Sharing

Integration for I-deas group data can be shared with I-deas data installations. Data sharing is
accomplished using export and import mechanisms.

For export, a group exporter exports an I-deas data sharing package and then an I-deas user imports it
into an I-deas installation. For import, an I-deas user exports an I-deas data sharing package and an
Integration for I-deas group importer imports it.

For more information, see chapter , Using Integration for I-deas: Updating and Synchronizing Data,
and chapter , Data Sharing.

Creating and Managing Groups

The following tasks describe the high-level process of creating and maintaining a group.

Task 1: Create the Group

The Teamcenter administrator uses the Organization application to create the group. This task includes:

• Naming the group

• Assigning a group administrator

• Specifying the default volume for the group

1-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Task 2: Manage the Group

Task 2: Manage the Group

The group administrator uses the Organization application to manage the team. This task includes:

• Adding, removing, activating, and deactivating group members

• Assigning group members to roles

Understanding Group Roles in Integration for I-deas

Group members must be assigned to at least one role within a group. The group role determines what
actions the member can perform.

Users can be assigned to multiple roles within a group. For example, a group leader may not
automatically have privileges to perform authoring tasks, such as creating and modifying data.
Therefore, the group leader must also be assigned the group author role. Having both roles enables the
user to perform group leader and group author tasks.

Group roles can be created and modified by Teamcenter administrators using the Rich Client
Organization application. For more information, see Organization Help.

Understanding My Teamcenter and the Integration for I-deas

Window
My Teamcenter is a Java™ application used to perform data management tasks in Integration for I-deas.

You launch the Integration for I-deas window from My Teamcenter to establish a connection to I-deas
and to display the active content of your current I-deas model file. The Integration for I-deas window is
updated dynamically to reflect changes that occur in I-deas. It is from this window that files are saved to
the Teamcenter database or sent to I-deas for review or modification.

My Teamcenter as a Client

My Teamcenter transfers data between Teamcenter and I-deas by functioning as a client to each.

• As a Teamcenter client, My Teamcenter uses the Teamcenter network to access the shared data and
to transfer data to and from volumes.

• As an I-deas client, My Teamcenter and I-deas share access to the I-deas model file.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 1-5
© 2020 Siemens
 1. Introduction

My Teamcenter Users

1-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Running My Teamcenter

My Teamcenter is intended for I-deas users who have traditionally used I-deas Data Management to
manage shared data.

Running My Teamcenter

There are two ways to run My Teamcenter:

• From within I-deas

On the I-deas icon panel, click the External Data Manager icon.

• Independent of I-deas
Launch Teamcenter Rich Client from the IDNPortal.bat file (Windows) or the idn_start_portal (UNIX)
file supplied with the Integration for I-deas installation.
Click the My Teamcenter button in the Rich Client Application Manager bar.

You can then click the Open/Locate Integration for I-deas Window button to display the Integration for
I-deas window, which connects to I-deas and lets you view and manage the contents of your active I-
deas model file.

Teamcenter and I-deas Supported Versions

Integration for I-deas 12.2.0.2 supports the following software versions:

Teamcenter Version I-deas Version

Tc 12.2.0.2 or later NX I-deas 6.7, NX I-deas 6.8

Local Languages
The Integration for I-deas product and associated documentation are localized in the following
languages:

• English

• German

• French

• Japanese

• Korean

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 1-7
© 2020 Siemens
 1. Introduction

Installation of Integration for I-deas

To install Integration for I-deas, see the Integration for I-deas Installation Guide.

1-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 2. Preferences
List of Preferences ───────────────────────────────────── 2-1
Integration for I-deas Preferences I ────────────────────────── 2-7
Integration for I-deas Preferences II ───────────────────────── 2-62
Specific Preference Data ──────────────────────────────── 2-75
IDEAS_external_owning_user_name ──────────────────────────── 2-75
Disabling Preferences For an Integration for I-deas Session ────────── 2-76
Engineering Translation Services Preferences ─────────────────── 2-76
Disable Preferences When Running ETS ────────────────────── 2-88

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 2. Preferences
This chapter provides a description of preferences for Integration for I-deas. The preferences are used to
configure the functionality of Integration for I-deas to perform as desired at your site. The preference
names are listed in the List of Preferences below and the descriptions are provided in the tables
Integration for I-deas Preferences I and Integration for I-deas Preferences II.

Note:
These preferences can be viewed and modified in the Teamcenter preferences. To access the
preferences, in My Teamcenter, choose Edit→Options→Index.

List of Preferences
The following preferences are included in this chapter:

IDEAS_part_create_jt

IDEAS_assembly_create_jt

IDEAS_default_view_type

IDEAS_default_scale_factor

IDEAS_fem_send_latest_ref

IDEAS_default_item_type

IDEAS_connect_time

IDEAS_bvr_create_precise

IDEAS_bvr_create_precise.Disallow

IDEAS_revision_id_format_specifier

IDEAS_revision_id_format_allow_truncate_ideas_rev

IDEAS_revision_id_format_blank_ideas_rev

IDEAS_sync_partnumber

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-1
© 2020 Siemens
 2. Preferences

IDEAS_show_open_in_ideas_button

IDEAS_migration_create_jt

IDEAS_default_view_type

IdeasPart_DefaultChildProperties

IdeasAssembly_DefaultChildProperties

IdeasFem_DefaultChildProperties

IdeasDrawing_DefaultChildProperties

IdeasDrawingSet_DefaultChildProperties

IDEAS_DRAWING_relation_primary

IDEAS_FEM_relation_primary

IDEAS_DWGSET_relation_primary

IDEAS_ACCONTEXT_relation_primary

IDEAS_ACSOURCE_relation_primary

IDEAS_send_nx_dataset

IDEAS_send_derived_ideas_dataset

IDEAS_send_default_NX_as

IDEAS_delete_items_on_checkin_failure

IDEAS_automatically_synchronize

IDEAS_one_version_per_revision

IDEAS_one_version_per_revision_ps_only

IDEAS_keep_drawing_with_related_model

IDEAS_keep_fem_with_related_model

IDEAS_keep_dwg_of_mult_parts_with_related_model

2-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 List of Preferences

IDEAS_keep_dwgset_with_related_drawing

IDEAS_Allow_Non_Latest_Revise

IDEAS_send_option_replace_revisions

IDEAS_send_option_display_replace_ui

IDEAS_2D_drawing_autoassign_conflicting_ids

IDEAS_rename_conflicting_dataset

IDEAS_override_itemid

IDEAS_mig_import_add_to_folders

IDEAS_mig_import_parent_folder_name

IDEAS_mig_import_parent_folder_user

IDEAS_mig_import_proj_hier_sep

IDEAS_hub_site_name

IDEAS_giman_util_batch_size

IDEAS_query_before_remote_import

IDEAS_update_matched_versions

IDEAS_inconsistent_create_date_action

IDEAS_JT_Resolution_Preference

IDEAS_related_objects_to_publish

IDEAS_CM_Release_statuses

IDEAS_auxfile_dataset_map

IDEAS_import_auxfiles

IDEAS_create_auxfile_refs

IDEAS_detail_level

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-3
© 2020 Siemens
 2. Preferences

IDEAS_skip_ADBFiles_Transfer

IDEAS_import_default_tcuser

IDEAS_import_default_tcgroup

IDEAS_import_default_tcproject

IDEAS_external_owning_user_name

IDEAS_send_option_check_refmod

IDEAS_send_option_enable_file_cache

IDEAS_migration_stats_level

IDEAS_append_autoassignid_to_originalid

IDEAS_<I-deas Dataset Type>_forms

IDEAS_types_to_exclude

IDEAS_ideas_datasets

IDEAS_catiav4_Datasets

IDEAS_catiav5_Datasets

IDEAS_push_ng_to_hub

IDEAS_use_item_level_right_to_modify

IDEAS_set_latest_dataset_right_to_modify_only

IDEAS_import_mapfile

IDEAS_threaded_migration

TC_truncate_file_name

IDEAS_name_replace_invalid_chars

IDEAS_Project_Mandatory_on_save

IDEAS_Mandatory_Attr

2-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 List of Preferences

IDEAS_cad_file_compression

IDEAS_migrate_attr_sync_missing_object_action

IDEAS_import_attr_sync_missing_object_action

IDEAS_export_attr_sync_missing_object_action

IDEAS_item_id_with_wildcard_chars_action

IDEAS_item_id_with_wildcard_replacement_char

IDEAS_item_revision_create_date_value

IDEAS_external_owning_user_update_use_ItemRevision

IDEAS_default_item_type_part

IDEAS_default_item_type_assembly

IDEAS_default_item_type_drawing

IDEAS_default_item_type_drawing_set

IDEAS_default_item_type_fem

IDEAS_migrate_all_for_reference

IDEAS_default_item_name

IDEAS_default_item_name

IDEAS_precise_rev_rule

IDEAS_check_BMNR

IDEAS_import_skip_renamed_items

IDEAS_send_default_NX_as

IDEAS_import_compressed_files

IDEAS_migrate_compressed_files

IDEAS_keep_standalone_dwg_with_existing_item

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-5
© 2020 Siemens
 2. Preferences

IDEAS_send_assembly_config_data

IDEAS_checkin_allow_non_synchronized_items

IDEAS_harness_translator_hn_option

IDEAS_use_tc_desc_as_partname

IDEAS_<I-deas Dataset Type>_forms

IDEAS_auto_assign_all_itemid

IDEAS_export_auto_expand_acf_relations

IDEAS_import_attr_sync_invalid_value_action

IDEAS_import_attr_sync_type_mismatch_action

IDEAS_import_compressed_files

IDEAS_mig_import_add_to_folders_matched_item

IDEAS_imgrate_attr_sync_invalid_value_action

IDEAS_migrate_attr_sync_type_mismatch_action

IDEAS_migrate_compressed_files

IDEAS_migrate_non_latest_versions_for_reference

IDEAS_multi_site_impl

IDEAS_multisite_util_batch_size

IDEAS_pre-import_validation

IDEAS_skip_remote_import_matched_versions

IDEAS_skip_remote_transfer_ownership_matched_versions

IDEAS_use_existing_item_with_only_non_ideas_data

IDEAS_drawing_create_cgm

IDEAS_drawing_create_cgm_multi_sheet

2-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

IDEAS_run_hammedic

IDEAS_show_purge_revision_ui

IDEAS_purge_revision_keep_limit

IDEAS_save_configurations

IDEAS_send_option_bin_attributes

IDEAS_import_allow_legacy_assemblies

IDEAS_use_tmtid_as_seqno

IDEAS_use_existing_item_with_no_data

Integration for I-deas Preferences I

This table contains preferences that are used to configure Integration for I-deas.

Table 2-1. Integration for I-deas Preferences

Preference Name Description

IDEAS_part_create_jt Controls whether DirectModel dataset versions are created

when parts are saved from I-deas to Teamcenter.
Valid values:

0
NO
OFF
FALSE

Any other value is considered to be positive and causes a

DirectModel dataset to be created.
Default values:

If not explicitly set, this preference defaults to TRUE.

Note:
If you change the value of this preference from a
TRUE to a FALSE value, you must also modify the
following line in the I-deas site parameter

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-7
© 2020 Siemens
 2. Preferences

Preference Name Description

file .ideas_paramXX (where XX is the I-deas

version):

Team.AssociatedFileGenerateParts: 1

Change the value 1 to 0 to disable creation of JT files

when parts are saved to Teamcenter.

Note:
This preference also affects import. If set to TRUE,
empty DirectModel datasets are created for the
imported items (no JT files are created).

IDEAS_assembly_create_jt Controls whether DirectModel dataset versions are created

when assemblies are saved from I-deas to Teamcenter.
Valid values:

0
NO
OFF
FALSE

Any other value is considered to be positive and causes a

DirectModel dataset to be created.
Default values:

If not explicitly set, this preference defaults to FALSE.

Note:
If you change the value of this preference from a
FALSE to a TRUE value, you must also modify the
following line in the I-deas site parameter
file .ideas_paramXX (where XX is the I-deas
version):

Team.AssociatedFileGenerateAssemblie
s: 0

Change the value to 1 to enable creation of JT files

when assemblies are saved to Teamcenter.

2-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Note:
This preference also affects import. If set to TRUE,
empty DirectModel datasets are created for the
imported items (no JT files are created).

IDEAS_default_view_type Determines the BOMView revision type created when a

new assembly is saved from I-deas to Teamcenter.
Valid values:

Any existing Teamcenter BOMView revision type.

Default values:

If not explicitly set, the default Teamcenter BOMView

Revision type is used.

IDEAS_default_scale_factor Defines the scale factor used to create Teamcenter

transformation matrices and provide information when
assemblies are sent to I-deas. This preference need only be
set when a scale factor is not stored in Teamcenter, usually
when dealing with external assemblies or those created
with top-down design.
Valid values:

Any positive real number.

Default values:

If not explicitly set, this preference defaults to 1000.0,

which represents the number of millimeters per
meter.

IDEAS_fem_send_latest_ref Specifies whether the latest version of a part referenced by

an FE model is sent to I-deas when the FE model is sent.
Valid values:

YES
1
ON
TRUE

Default values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-9
© 2020 Siemens
 2. Preferences

Preference Name Description

If not explicitly set, this preference defaults to FALSE.

The version of the part that was originally saved with
the FE model is sent to I-deas.

IDEAS_default_item_type Defines the type of item created when new objects are
saved from I-deas to Teamcenter. This preference sets the
default item type, which can be overridden when the
Teamcenter item is created.
Valid values:

Any valid Teamcenter item type.

Default values:

If not explicitly set, this preference uses the default

Teamcenter item type.

IDEAS_connect_time Defines the maximum number of seconds that Teamcenter

waits when attempting to connect to I-deas.
Valid values:

Any positive integer.

Default value:

If not explicitly set, this preference defaults to 110

seconds.

IDEAS_bvr_create_precise Controls whether a BOMView Revision that is created at

assembly checkin or data sharing import is precise or
imprecise.
Valid values:

TRUE
FALSE

Default value:

If not explicitly set, this preference defaults to TRUE.

IDEAS_bvr_create _precise.Disallow Site preference that controls whether a user can set the
preference to create a precise BVR at assembly checkin or
data sharing import. (This is initially set at the site by the
IDEAS_bvr_create_precise preference.)

2-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

If the value is set to FALSE, you can set this preference

from My Teamcenter by pulling down the Edit menu and
choosing the following options:

Options→Integration for I-deas

Valid values:

TRUE
FALSE

Default value:

If not explicitly set, this preference defaults to FALSE.

IDEAS_revision_id_format _specifier Defines the format for the revision ID for new item
revisions created with migration and import. The
preference provides formatting control based on the syntax
of the printf format string used in C programming. The
output can be composed of optional constant characters
that are mixed with the I-deas version number attribute
and/or the I-deas revision attribute.

The I-deas version number attribute is represented by %d.

The I-deas revision attribute is represented by %s.

The following restrictions apply:

• You can use either %d or %s, or both, but you cannot use
multiples of either one.
• You cannot use a length modifier, such as %ld.
• The only flag characters allowed are: – and 0.
• A * as a field width or precision is not allowed. All other
valid standard C printf field widths and precision
modifiers that apply to %d and %s in C are allowed.
• The revision ID attribute is limited to 32 characters. If the
length is longer, an error message is logged and
processing of that I-deas item version fails.
• The value of this preference is validated at the beginning
of the import and migration processes. If the value
specified is invalid, or always produces values longer
than 32 characters, an error message is displayed and
processing is stopped.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-11
© 2020 Siemens
 2. Preferences

Preference Name Description

For example, with an I-deas item at version 1 and revision

A:

%d results in a revision ID of 1.

%s results in a revision ID of A.

%d_%s results in a revision ID of 1_A.

%05d_%s results in a revision ID of 00001_A.

%s-%0.5d results in a revision ID of –00001.

Valid values:

%d and %s variables as specified above.

Default value:

None. The standard method for generating revision

IDs is used.

IDEAS_revision_id_format_allow Determines whether the input I-deas revision ID value is

_truncate_ideas_rev truncated if it is longer than 32 characters.
If the value is set to TRUE, the input revision ID is truncated
to reduce the length of the string. The string is not
truncated to less than one character.
The format is %s_%d equals 32 characters maximum,
where s is the revision ID and d is the version number as
detailed in the I-DEAS_revision_id_format_specifier
preference. For example, if the input I-deas revision ID is 37
characters and the version number is one character, the
result is the first 30 characters of the revision ID, a _, and
then one character for the version.
If the string cannot be truncated to 32 characters or less,
then an error message is logged and processing of that I-
deas item is stopped.
Valid values:

TRUE
FALSE

Default:

2-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

FALSE

IDEAS_revision_id_format_blank Specifies the value used in the

_ideas_rev IDEAS_revision_id_format_specifier preference if the I-
deas revision ID is blank.
If this preference is not defined, an empty string is used for
the revision ID.
This preference provides the same formatting control based
on the syntax of the printf format string used in C
programming as in the preference
IDEAS_revision_id_format_specifier. The output can be
composed of optional constant characters that are mixed
with the I-deas version number attribute (represented by
%d). The I-deas revision attribute is blank so %s does not
apply to this preference.
Valid values:

Any string of characters up to 32 in length, or %d. If it's

equal to %d only, the I-deas version value is
substituted.

Default:

Empty string

IDEAS_sync_partnumber Synchronizes the I-deas part number and the part name to
the corresponding item in Teamcenter when the I-deas
model file is synced.
Valid values:

TRUE
YES
1
ON
FALSE

Default value:

If not explicitly set, this preference defaults to FALSE.

IDEAS_show_open_in_ideas_button Displays the I-deas icon in the My Teamcenter application.

You use the I-deas icon to connect to I-deas using the
Integration for I-deas integration.
Valid values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-13
© 2020 Siemens
 2. Preferences

Preference Name Description

TRUE
FALSE

Default value:

If not explicitly set, this preference defaults to TRUE.

IDEAS_migration_create_jt Controls whether DIrectModel dataset versions are created

when parts and assemblies are migrated from I-deas TDM.
JT files are not created, only JT datasets.
Valid values:

TRUE
FALSE

Default value:

If not explicitly set, the preference defaults to FALSE.

JT datasets are not created during migration.
For additional information, see the section Setting Up
Migration ETS Translation Requests to Avoid the
"Duplicate sanitized part name/number" Error in the
chapter Preparing for Data Migration in the
Integration for I-deas Data Migration Reference
Guide.

IDEAS_default_view_type Determines the BOMView revision type created when a

new assembly is saved from I-deas to Teamcenter.
Valid values:

Any valid Teamcenter BOMView revision type.

Default value:

If not explicitly set, the preference uses the default

Teamcenter BOMView revision type.

IdeasPart_DefaultChildProperties Defines the secondary relations (children) for an I-deas part

that is an associated member of a relationship.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

2-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

IDEAS_DRAWING
IDEAS_FEM
IDEAS_ACSOURCE
IDEAS_ACCONTEXT

Default value:

If not explicitly set, the preference defaults to:

IDEAS_DRAWING
IDEAS_FEM
IDEAS_ACSOURCE
IDEAS_ACCONTEXT

IdeasAssembly Defines the secondary relations (children) for an I-deas

_DefaultChildProperties assembly that is an associated member of a relationship.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IDEAS_DRAWING
IDEAS_FEM
IDEAS_ACCONTEXT

Default value:

IDEAS_DRAWING
IDEAS_FEM
IDEAS_ACCONTEXT

IdeasFem_DefaultChildProperties Defines the secondary relations (children) for an I-deas FEM

that is an associated member of a relationship.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IDEAS_FEM

Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-15
© 2020 Siemens
 2. Preferences

Preference Name Description

IDEAS_FEM

IdeasDrawing _DefaultChildProperties Defines the secondary relations (children) for an I-deas

drawing that is an associated member of a relationship.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IDEAS_DRAWING
IDEAS_DWGSET
IMAN_CAPTURE

Default value:

IDEAS_DRAWING
IDEAS_DWGSET
IMAN_CAPTURE

IdeasDrawingSet_DefaultChild Defines the secondary relations (children) for an I-deas

Properties drawing set that is an associated member of a relationship.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IDEAS_DWGSET

Default value:

IDEAS_DWGSET

IDEAS_DRAWING_relation _primary Defines the primary relations for an I-deas drawing that is
an associated member of a relationship. An I-deas drawing
can be shown as the top item with related items in My
Teamcenter. The plus (+) sign is enabled for the item in My
Teamcenter so that the related items can be displayed.

2-16 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IdeasDrawing

Default value:

IdeasDrawing

IDEAS_FEM_relation_primary Defines the primary relations for an I-deas FEM that is an

associated member of a relationship. An I-deas FEM can be
shown as the top item with related items in My
Teamcenter. The plus (+) sign is enabled for the item in My
Teamcenter so that the related items can be displayed.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IdeasFem

Default value:

IdeasFem

IDEAS_DWGSET_relation_primary Defines the primary relations for an I-deas drawing set that
is an associated member of a relationship. An I-deas
drawing set can be shown as the top item with related
items in My Teamcenter. The plus (+) sign is enabled for the
item in My Teamcenter so that the related items can be
displayed.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-17
© 2020 Siemens
 2. Preferences

Preference Name Description

IdeasDrawingSet

Default value:

IdeasDrawingSet

IDEAS_ACCONTEXT_relation _primary Defines the primary relations for an I-deas associative copy
target part that is an associated member of a relationship.
A target part in an I-deas associative copy relationship can
be shown as the top item with related items in My
Teamcenter. The plus (+) sign is enabled for the item in My
Teamcenter so that the related items can be displayed.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Valid values:

IdeasPart

Default value:

IdeasPart

IDEAS_ACSOURCE_relation _primary Defines the primary relations for an I-deas associative copy
source that is an associated member of a relationship. A
source part in an I-deas associative copy relationship can be
shown as the top item with related items in My
Teamcenter. The plus (+) sign is enabled for the item in My
Teamcenter so that the related items can be displayed.

Note:
This is a Teamcenter preference. For additional
information, see the Teamcenter documentation.

Note:
It's recommended that this preference is not changed
from the default.

Valid values:

IdeasPart

2-18 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Default value:

IdeasPart

IDEAS_send_nx_dataset Specifies the dataset to send during a send to I-deas

operation when there are NX and I-deas datasets in the
same Item Revision.

Note:
All of the parts of an assembly (NX parts or I-deas
parts) are automatically selected and sent to I-deas.

Valid values:

TRUE
Sends the NX dataset.
FALSE
Sends the I-deas dataset.

Default value:

FALSE

IDEAS_send_derived_ideas_dataset Specifies the dataset to send during a send to I-deas

operation when there are NX and I-deas derived datasets in
the same Item Revision.

Note:
This preference overrides the
IDEAS_send_nx_dataset preference (above) when
the I-deas dataset is derived from an NX dataset.

Note:
All of the parts of an assembly (NX parts or I-deas
parts) are automatically selected and sent to I-deas.

Valid values:

TRUE
Sends the I-deas dataset.
FALSE
Sends the NX dataset.

Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-19
© 2020 Siemens
 2. Preferences

Preference Name Description

FALSE

IDEAS_send_default_NX_as Specifies the default option in the Send to I-deas dialog

pulldown menu for how a part is sent during a send to I-
deas operation when there are NX and JT (Direct Model)
datasets in the same Item Revision.
Available pulldown menu options are:

• None – Sends the Direct Model dataset (JT file) for the
part.

• New – Sends the part as a new derived I-deas part. This

is used for interoperability (e.g., when creating a FEM).

• Part Name – Sends an existing derived I-deas part. This

is used for interoperability (e.g., when creating a FEM).

Valid values:

JT
Sends the JT dataset. The option in the Send to I-deas
dialog pulldown menu is NONE).
NX
Sends the NX dataset. The option in the Send to I-
deas dialog pulldown menu is NEW).

Note:
When the preference
IDEAS_send_derived_ideas_dataset is set to true
and the derived I-deas part is in the same Item
Revision as the NX part, the pulldown menu is not
activated; the existing derived I-deas part is always
sent.

Default value:

JT

IDEAS_delete_items_on_checkin Specifies if an item is deleted if it fails checkin.

_failure
Valid values:

TRUE
Deletes all items from the Teamcenter database that
were created during a failed checkin.

2-20 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Note:
Setting the preference to this value decreases
performance on subsequent checkins as all
items (e.g., for an assembly) have to be
recreated.

FALSE
Items that were assigned a new ItemID (automatically
or manually) are deleted during a failed checkin. Items
created during checkin are not deleted if they were
not assigned a new ItemID.

Default value:

FALSE

IDEAS_automatically_synchronize Controls whether the automatic synchronization process

occurs. The process is activated during startup of I-deas and
whenever a new model file is opened. It includes
synchronization of the model file and finding out-of-date
items. If the preference is set to FALSE, you may need to
manually execute synchronization and the finding of out-
of-date items by using the commands in the Integration for
I-deas window.
Valid values:

TRUE
FALSE

Default value:

TRUE

IDEAS_one_version_per_revision Controls how I-deas item versions are mapped to

Teamcenter Item Revisions.
Valid values:

TRUE
When an I-deas dataset (part, assembly, drawing,
FEM) is modified, the new version is saved to its own
unique Teamcenter Item Revision. The default revision
ID follows the business rules for checkin.
FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-21
© 2020 Siemens
 2. Preferences

Preference Name Description

When an I-deas dataset (part, assembly, drawing,

FEM) is modified, the new version is saved to the
same Item Revision that it came from.

Default value:

TRUE

IDEAS_one_version_per_revision Determines whether drawings and FEMs are mapped to

_ps_only separate Teamcenter Item Revisions if one version per
revision functionality is enabled. This preference works in
conjunction with the preference
IDEAS_one_version_per_revision.
When the preference IDEAS_one_version_per_revision is
set to TRUE, one version per revision functionality is
enabled. If you modify an I-deas dataset (part, assembly,
drawing, FEM), the new version of the dataset is saved to
its own unique, newly created Item Revision.
If you also set IDEAS_one_version_per_revision_ps_only
to TRUE, new versions of drawings and FEMs are not saved
to a new Item Revision; they are saved to the Item Revision
that they came from. New versions of parts and assemblies
are still saved to a new Item Revision in accordance with
one version per revision functionality. The addition of the
preference IDEAS_one_version_per_revision_ps_only
negates one version per revision functionality for drawings
and FEMs.

Note:
This preference is also applicable for migration and
import.

This preference interacts with the drawing and FEM

mapping preferences
IDEAS_keep_drawing_with_related_model,
IDEAS_keep_FEM_with_related_model, and
IDEAS_keep_dwg_of_mult_parts_with_related_model. If
a drawing or FEM is not mapped to its related model Item
based on the settings of those preferences, then the
preference IDEAS_one_version_per_revision_ps_only
determines how they're mapped. When set to TRUE, it
maps them to the Item Revision that they came from.
Valid values:

2-22 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

TRUE
FALSE

Default value:

FALSE

IDEAS_keep_drawing_with Specifies how new I-deas drawings are mapped to

_related_model Teamcenter Item Revisions. The drawing can be newly
created in I-deas and saved to Teamcenter or can be
imported through data sharing. Once a drawing has been
placed according to this preference setting, the following
versions of the drawing follow the same placement.
Valid values:

ONLY_IF_SAME_ID
The drawing is mapped to the related model if the
drawing has the same ItemID (I-deas part number) as
the model. The drawing is placed in the same Item
Revision as the model. This applies to multiple
versions of a drawing as long as the versions have the
same ItemID as the model. If the drawing ItemID is
different than the related model, it's mapped to its
own unique Item Revision.

Note:
This functionality is used automatically when
the IDEAS_one_version_per_revision
preference is set.

ALWAYS
All versions of a drawing are mapped to the related
model regardless of the ItemID of the drawing. All of
the version are placed in the same Item Revision as
the model.

Note:
If the IDEAS_one_version_per_revision
preference is set, this setting only applies to
data sharing.

NEVER
Each version of a drawing always maps to its own
separate Item Revision; they are never placed in the
same Item Revision as the model. This occurs even if

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-23
© 2020 Siemens
 2. Preferences

Preference Name Description

you are trying to store the drawing with an unrelated

model.

Note:
If the IDEAS_one_version_per_revision
preference is set, this setting only applies to
data sharing.

Default value:

NEVER

IDEAS_keep_fem_with _related_model Same functionality as

IDEAS_keep_drawing_with_related_model (described in
above preference).

IDEAS_keep_dwg_of_mult_parts Controls mapping of a drawing for multiple models. During

_with_related_model migration and import, a drawing is normally mapped to the
same Item Revision as its related model. If a drawing is
related to multiple models, it's mapped to its own separate
Item Revision, by default. This allows the drawing and
many related models to be revised independently of each
other. However, this functionality is overridden with this
preference.

NEVER
A drawing for multiple parts is mapped to its own
separate Item Revision.
ONLY_IF_SAME_ID
If you have a drawing of multiple parts, the drawing
continues to be mapped to the same Item Revision as
the part it was related to when first migrated.
For example, you have a drawing related to a single
part and it's mapped to the same Item Revision as the
part (part A). Then the drawing is modified to contain
many parts (parts A, B, C, and D). The drawing is still
mapped to the Item Revision for part A, not to a
separate Item Revision.

Note:
This preference applies to migration, import,
and checkin of drawings.

Default value:

2-24 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

NEVER

IDEAS_keep_dwgset_with Specifies how new I-deas drawing sets are mapped to

_related_drawing Teamcenter Item Revisions. The drawing set can be newly
created in I-deas and saved to Teamcenter or can be
imported through data sharing. Once a drawing set has
been placed according to this preference setting, the
following versions of the drawing set follow the same
placement.
Valid values:

ONLY_IF_SAME_ID
The drawing set is mapped to a related member
drawing if the drawing set has the same ItemID as the
related member drawing. The drawing is placed in the
same Item Revision as the related member drawing.
This applies to multiple versions of a drawing set as
long as the versions have the same ItemID as the
related member drawing. If the drawing set ItemID is
different than the related member drawing, it's
mapped to its own unique Item Revision.

Default value:

NEVER
Each version of a drawing set maps to its own
separate Item Revision; they are not placed in the
same Item Revision as the related member drawing.

Default value:

NEVER

IDEAS_Allow_Non_Latest_Revise Allows you to perform a revise operation (I-deas→Revise)

on any Item Revision, not just the latest Item Revision.
During the revise operation, a message is displayed
informing you that you are revising a non-latest Item
Revision.

Note:
This preference also applies to the I-deas→Freeze
and Create New Revision command.

When the items in the Item Revision are copied, the I-deas
dataset version number is incremented one more than the

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-25
© 2020 Siemens
 2. Preferences

Preference Name Description

last version number of the I-deas dataset that exists, not

just one more than the dataset in that particular Item
Revision. However, the new I-deas dataset is a copy of the
version in that Item Revision, which is not a copy of the
latest dataset if the Item Revision is not the latest. This can
cause problems with the latest version having the latest
changes.
For example, You have Item Revisions A, B, C, and D, with I-
deas dataset versions 1, 2, 3, and 4 respectively. You
perform a revise operation on Item Revision B (I-deas
dataset version 2) and get a new Item Revision E. The I-
deas dataset in Item Revision E is incremented to version 5
although it's really a copy of version 2. The changes made
in versions 3 and 4 are not in version 5.

Warning:
When you perform a revise operation on a non-latest
Item Revision, the new I-deas dataset does not
contain the latest changes.

Valid values:

TRUE
FALSE

Default value:

FALSE

IDEAS_send_option_replace _revisions Controls the replacement of existing revisions in the model

file for all Send to I-deas operations. If the option is true,
the existing revision of an item in the model file is replaced.
If the option is false, the existing revision is not replaced,
thereby allowing two revisions of the same item in the
model file.
Valid values:

TRUE
FALSE

Default value:

FALSE

2-26 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

IDEAS_send_option_display Provides the option Replace existing revisions in the

_replace_ui model file in the Send to I-deas dialog box. If the option is
checked, the existing revision of an item in the model file is
replaced. If the option is not checked, the existing revision
is not replaced, thereby allowing two revisions of the same
item in the model file.
This preference overrides the setting of the
IDEAS_send_option_replace_revisions preference
(above) for each separate Send to I-deas operation
performed.
Valid values:

TRUE
FALSE

Default value:

FALSE

IDEAS_2D_drawing_autoassign Specifies how I-deas standalone 2D drawings are mapped

_conflicting_ids to Teamcenter Items during migration or import only. This
preference doesn't apply to checkin of standalone drawings
using Integration for I-deas.
When an Item contains an I-deas part or assembly, the Item
Revision sequence for the various Item Revisions is defined
by the creation date of the part or assembly. When the Item
contains only drawings, the creation date of each drawing
migrated or imported is used to sequence the Item
Revisions. Drawings can be created at any time which may
not result in the correct sequence when multiple drawings
get mapped into the same Item with no part or assembly,
therefore the Item Revisions are likely to get out of proper
sequence, which can cause problems. The default behavior
of this preference is to always create separate Items for
standalone 2D drawings that have the same ItemID.
Valid values:

ALWAYS
Always auto-assign a new ItemID to standalone
drawings with duplicate ItemIDs and place each
drawing into its own Item.

Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-27
© 2020 Siemens
 2. Preferences

Preference Name Description

NEVER
Never auto-assign ItemIDs for standalone drawings.
Using this option will probably require pre-configured
Items and Item Revisions, or custom user exit code to
manage the process without errors.
UNLESS_WITH_MODEL_OF_SAME_ID
Place standalone drawings into an Item Revision that
contains a part or assembly with the same ItemID;
otherwise, auto-assign a new ItemID and place the
standalone drawing into its own Item.

Default value:

ALWAYS

IDEAS_rename_conflicting_dataset Controls whether automatic renaming of a drawing is

performed when the naming is the same during migration
or import. This allows multiple drawings to be placed under
the same Teamcenter Item.

Note:
This preference is applicable when the preference
IDEAS_dataset_types_per_item is set to MULTIPLE.

Valid values:

TRUE
FALSE

Default value:

FALSE

IDEAS_override_itemid Causes the migration and import processes to call the

IDS_override_itemid() user exit. This user exit provides a
programmatic override of the ItemID for the incoming item
instead of automatically using the I-deas part number from
the package file.

IDEAS_mig_import_add_to _folders The preference IDEAS_mig_import_add_to_folders

provides mapping of projects and libraries to folders.
IDEAS_mig_import_parent
_folder_name The following functionality is provided:
IDEAS_mig_import_parent
_folder_user • The preference maps projects into folders and libraries as
sub-folders under the project folder.

2-28 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

IDEAS_mig_import_proj_hier_sep • The creation of the folders is done by truncating the

folder name to 32 characters maximum and placing the
full 80 character name in the folder description attribute.

• While querying for a folder during item creation, the

program looks for a folder-parent folder combination
corresponding to the library-project mapping to find a
match.

• To avoid the problems of large queries and no

uniqueness of folder names, the following preferences
provide values for folder query during item creation.

• IDEAS_mig_import_parent_folder_name
This is the root folder where the nested folder
hierarchy starts. If this preference is not set, or the
query doesn't find a folder, the program defaults to
the current user's home folder as the root folder.
• IDEAS_mig_import_parent_folder_user
This is the owning user of the root folder. If this
preference is not set, the query searches for a folder
owned by the current user.

Note:
If both of these preferences aren't set, the program
defaults to the current user and the user's home
folder for initiating the query and creates the
folder there if it doesn't exist.

• If the I-deas TDM uses the DataMgt.HierarchySeparator

parameter for hierarchical display of items, the
IDEAS_mig_import_proj_hier_sep preference can be
set to the same ASCII character to provide the same
hierarchical display.
Values for the preferences:

• IDEAS_mig_import_add_to_folders
Valid values:

ON
OFF

Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-29
© 2020 Siemens
 2. Preferences

Preference Name Description

OFF
• IDEAS_mig_import_parent_folder_name
Valid values:

Name of the project

Default value:

Projects
• IDEAS_mig_import_parent_folder_user
Valid values:

Name of the user

Default value:

infodba
• IDEAS_mig_import_proj_hier_sep
Valid values:

ASCII value for the hierarchy separator

Default value:

IDEAS_hub_site_name Specifies the name of the hub site where data is pushed
(replicated) during migration and import in a multi-site
environment. The hub site must be defined in the
database.

Note:
This preference is required in a mulit-site
environment.

Valid values:

The name of the site acting as the hub site

Default value:

NONE

IDEAS_giman_util_batch_size Controls the batch size when using the utility giman_util
(Teamcenter 8) or data_share Teamcenter 9.

2-30 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Valid values:

A positive integer

Default value:

NONE (data_share default is used)

IDEAS_query_before_remote _import Determines whether a query by the verison GUID is

performed on the local database before querying the ODS
and/or hub site during migration and import.
Valid values:

TRUE
FALSE

Default value:

FALSE

IDEAS_update_matched_versions Determines whether there is a transfer of site ownership

for matching item versions that are being imported for
reference. When the item is modified, it must be owned by
the local site.

Note:
If this preference is set to FALSE, when the
IDSUSER_import_item_post() user exit is used,
ensure the objects are owned by the local site before
modifying them.

Valid values:

TRUE
FALSE

Default value:

TRUE

IDEAS_inconsistent_create Determines whether an inconsistent create date timestamp

_date_action is considered a warning or an error.
Valid values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-31
© 2020 Siemens
 2. Preferences

Preference Name Description

WARNING
ERROR

Default value:

WARNING

IDEAS_JT_Resolution_Preference Determines the resolution for JT files during checkin.

Valid values:

LOW_RES
HIGH_RES

Default value:

LOW_RES

IDEAS_related _objects_to_publish Freezing an Item Revision applies a status to the datasets

and copies the datasets to a new item revision. This
Identifies the relationships that are kept on the items in the
frozen Item Revision.
This is performed with the Freeze→Create New Revision
menu selection.
Valid values:

Teamcenter objects

Default value:

IMAN_specification
IMAN_Rendering
IMAN_manifestation
IMAN_requirement
IMAN_master_form

IDEAS_CM_Release_statuses Identifies the status to create for an item when it has been
frozen. This is performed with the Freeze→Create New
Revision menu selection. The status name must match an
existing status object in the Teamcenter Admin application
manager, Type application, Status section.
Valid values:

A defined Teamcenter status

2-32 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Default value:

FROZEN

IDEAS_auxfile_dataset_map Specifies the mapping between I-deas auxiliary files (using

file extensions) to Teamcenter dataset types. This map is
used by TDM migration and data sharing import to create
corresponding datasets for auxiliary files that can be
attached to I-deas parts, assemblies, drawings, FEMs,
drawing sets and legacy drawings.
You can store auxiliary files in their own datasets under the
same Item Revision as the I-deas dataset that they are
associated with (mapping defined). Or they can be stored
directly under the I-deas dataset that they are attached to
(no mapping defined).
The mapping is between the auxiliary file extension and
DatasetType + Named Reference Name.
This preference is required to be defined when
IDEAS_import_auxfiles is set to TRUE.
Use:

<Auxiliary File Extension>:<Valid TC Dataset

Type>:<Named Reference Name>

For example, you want to map the following:

Auxiliary file extension for MS Word document .doc to

TC MS Word dataset MSWord
Auxiliary file extension for MS Excel document .doc to
TC MS Excel dataset MSExcel

The preference value is:

IDEAS_auxfile_dataset_map=doc:MSWord:word
xls:MSExcel:excel

Default value:

There is no default value.

IDEAS_import_auxfiles Specifies whether to migrate/import the auxiliary files

attached to I-deas library items.
Valid values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-33
© 2020 Siemens
 2. Preferences

Preference Name Description

TRUE
Migrate/import the auxiliary files.
FALSE
Don't migrate the auxiliary files.

Default value:

FALSE

IDEAS_create_auxfile_refs Specifies whether to populate the auxiliary file references

object in the database. The references object is attached to
an I-deas dataset that has an attached auxiliary file.
It's recommended that sites populate the reference object if
you intend to share the auxiliary files using data sharing
(value set to TRUE).
If you don't have sharing/roundtrip requirements for
auxiliary files, then set the value to FALSE. This saves time
during migration and import. It also saves database space.
Valid values:

TRUE
FALSE

Default value:

FALSE

IDEAS_detail_level Specifies the amount of detail that is logged. There are

three levels of detail represented by the integers 1, 2, 3. If
set to 0 or a negative number, the detail level logging is off.
Valid values:

1, 2, 3
0 or a negative number

Default value:

IDEAS_skip_ADBFiles_Transfer Specifies whether ADB files (.prt, .asm, .fem, .dwg, .mdf)
are transferred during migration.
This preference can be used where the ADB files are to be
uplodaded as a post-migration step. Migration logs the fact
that it is skipping the transfer of ADB files. You can search
the log file for the occurrence of the phrase "Skip ADBFile

2-34 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Transfer" and extract resulting output to a separate text file.

This text file can then be provided as input to the
ideas_upload_files utility to upload the ADB files to
Teamcenter volumes as part of post-migration.
Valid values:

TRUE
ADB files are not transferred.
FALSE
ADB files are transferred.

Default value:

FALSE

IDEAS_import_default _tcuser Identifies the default Teamcenter user (TCUser) for the
migration import.
Valid values:

Any valid Teamcenter user

Default value:

NONE

IDEAS_import_default _tcgroup Identifies the default Teamcenter group (TCGroup) for the
migration import.
Valid values:

Any valid Teamcenter group name

Default value:

NONE

IDEAS_import_default _tcproject Identifies the default Teamcenter project (TCProject) for the
migration import.
Valid values:

Any valid Teamcenter project ID

Default value:

NONE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-35
© 2020 Siemens
 2. Preferences

Preference Name Description

IDEAS_external_owning_user _name Ensures an external ownership user with the same standard
name is created at all sites. The specified user must also be
defined in the database.
When items are migrated or imported for reference, or
exported for modification, the owning_user attribute for
the CAD dataset (I-deas dataset) is set to the value of this
preference.
You must create Access Manager rules that do not allow
write access by other users to objects that have this
owning_user value.
This preference is required for migration and data sharing.

Note:
It's recommended that you don't use the
IDEAS_external_owning_user_name user for
interactive data creation.

Valid values:

The user ID of a valid user

Default value:

NONE

For additional information, see the Additional Preference

Data section.

IDEAS_send_option_check_refmod Displays a warning dialog during a send to I-deas operation

under certain conditions. If the data being sent to I-deas
will result in a referenced but modified condition later
when the assembly is saved to Teamcenter, the warning
dialog is displayed.
The preference detects when the product structure sent to
I-deas contains a different hierarchy than the as-saved
model. This indicates that an item in the product structure
has been modified but is not reflected in the existing as-
saved model, resulting in a referenced but modified
condition.
The warning dialog states that a reference but modified
condition has been detected and asks if you want to
checkout the affected assembly components. If the
components are checked out, you can update the assembly

2-36 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

in I-deas to eliminate the referenced but modified

condition.

Note:
This preference is applicable when you perform send
to I-deas from Teamcenter's My Teamcenter and
Structure Manager.

Valid values:

TRUE
FALSE
The reference but modified condition is not detected
and the dialog is not displayed.

Default value:

FALSE

IDEAS_send_option_enable_file Adds the option Enable caching of files during Send to I-

_cache deas in the Options dialog. Checking this option enables
caching of files locally to increase performance on
checkout.
When an item is sent to I-deas, the CAD and CPD files are
downloaded to the local client and get deleted after the
send to I-deas operation has completed. This preference
lets you modify the functionality to keep those files (cache
the files locally) instead of deleting them. Subsequent
checkout operations will check the local location for the
files, thereby increasing performance after the first
checkout has been performed.
Valid values:

TRUE
Adds the option Enable caching of files during Send
to I-deas to the Options dialog. Check the option to
enable the functionality.
FALSE

Default value:

FALSE

IDEAS_migration_stats_level Provides migration structure and import package summary

information in the migration log file. This gives you data

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-37
© 2020 Siemens
 2. Preferences

Preference Name Description

about the migration process to help determine the status,

depth, and completeness of the migration. This summary
information can be used to monitor the progress and
performance of a migration. It includes the number of new
items migrated and at what rate the migration is occurring.
In addition, detailed migration statistics can also be output.
The information is added to the migration log file
(migtrans.log).
The following values are available for the preference:

• NONE – Do not include the statistical summaries.

• BASIC – This is the default. Includes the summary

statistics at the end of each structure processing (an
example is below).

• DETAIL – Outputs a delimited line for each structure that

includes all of the summary information plus a more
granular breakdown of counts and times. This line can be
extracted for import into a spreadsheet, such as
Microsoft Excel, where the migration statistics can be
examined in total and graphically. A tab delimited
column header line is also output that identifies each
field (an example is below).

The following is an example of the output for the BASIC

option:

2005/07/13-14:07:28 Structure
Statistics:
2005/07/13-14:07:28 329 items were
processed
2005/07/13-14:07:28 Of these, 329
were new,
0 were inserted, 0 were matched
2005/07/13-14:07:28 Of the new and
inserted items,
0 had ownership
2005/07/13-14:07:28 Of the matched
items,
0 had ownership updated
2005/07/13-14:07:28 Elapsed minutes =
9.54
2005/07/13-14:07:28 Total minutes
retrieving items
from pkg/TDM = 0.03

2-38 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

2005/07/13-14:07:28 Total minutes

transferring
files = 1.65
2005/07/13-14:07:28 Items processed
per minute
= 34.50
2005/07/13-14:07:28 Items created per
minute
= 34.50
2005/07/13-14:07:28 Accumulated rate:
25.13
processed, 24.28 created

The following is an abbreviated example of the additional

output for the DETAIL option (the basic output above is
also included):

STATS wall clock structure id

structure time struct pclsvr
time
struct thread time struct item
time...
STATS 2005/07/13-13:41:05 1
00:01:37.180
00:00:06.781 00:00:06.734
00:01:30.337 00:00:00.108...

Note:
This preference also applies when importing a
package file to Teamcenter.

Note:
This preference must be added manually to the
Teamcenter preferences even if you are doing a
complete new install; it is not automatically added to
the file.

IDEAS_append_autoassignid Modifies the functionality of auto-assign to keep the

_to_originalid original part number when auto-assign is implemented
during migration. Normally, if there is an ItemID conflict
during migration (occurs when there is a duplicate part
number), migration assigns a completely new ItemID to
the dataset being imported. This can become difficult to
track if there are a number of conflicts during migration.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-39
© 2020 Siemens
 2. Preferences

Preference Name Description

This preference concatenates the original part number with

an auto generated number to create the new ItemID,
thereby preserving the identity of the migrated item.
The ItemID still contains 32 characters maximum and is
comprised of the following:

• The original part number up to 25 characters maximum.

It's truncated if longer than that.

• An underscore.

• A six digit number created by the ID generator.

For example, you migrate the part bracket7274 and if that

ItemID is already used, the migrated ItemID is
bracket7274_000001.
In addition, information is added to the migration log
identifying the old part number and the new ItemID. For
example,

Auto assigned Conflicting ItemID. Old

value=ORIGINAL,
new value=ORIGINAL_002910

Note:
The option Auto-assign the item ID of such an item
must be selected in the Migration Wizard to enable
the concatenated auto-assign functionality of this
preference.

Valid values:

No value
The append-to-original ID functionality is not used.
IMPORT
Use the append-to-original ID functionality for import,
no effect on migration.
MIGRATE
Use the append-to-original ID functionality for
migration, no effect on import.
IMPORT, MIGRATE
Use the append-to-original ID functionality for both
import and migration.

2-40 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

TC_SAVE
Use the append-to-original ID functionality for checkin
when the Assign button is used to create the ID in the
Save to Teamcenter dialog box.

Note:
If you select Assign to create an item ID for an
item that already has one, you are prompted to
reassign. If you reassign, this functionality is
applicable.

Note:
If the item ID field is empty, this functionality is
applicable.

Note:
This functionality is not applicable to Integration
for I-deas openness, since user action is
required.

Default value:

No value

IDEAS_<I-deas Dataset Type>_forms Creates custom Teamcenter forms that are attached to I-
deas datasets during migration. The forms are used to
capture attribute information for migrated items and are
attached to the dataset using a named reference or a GRM.
The data in the forms can be used to populate attributes
through the use of user exits.

Note:
For additional information on Teamcenter forms, see
the Teamcenter online help.

Valid I-deas Dataset Types:

Insert the type of I-deas dataset into the preference name
that the preference is applicable for.

IdeasPart; the preference is IDEAS_I-deasPart_forms

IdeasAssembly

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-41
© 2020 Siemens
 2. Preferences

Preference Name Description

IdeasDrawing
IdeasDrawingSet
IdeasFem

Valid values:
The value for the preference takes the following form:

<FormTypeName>:<GRM or NR>:<GRMName or
NamedRefName>

For example, you need to create two custom forms for each
I-deas part that is imported/migrated. You attach one
custom form (IdeasPartAttr1) using a GRM of type
IdeasPartAttr1 (site defined) to the I-deas part dataset. You
attach a second custom form (IdeasPartAttr2) using the
named reference name IdeasPartAttr2 to the I-deas part
dataset.
The preference is defined as follows:

IDEAS_IdeasPart_forms=
IdeasPartAttr1:GRM:IdeasPartAttr1
IdeasPartAttr2:NR:IdeasPartAttr2

IDEAS_types_to_exclude List of object types that do not get a status during the
freeze part of the Freeze→Create New Revision
operation. This does not affect the objects that are copied
forward to the new revision. That is determined by the
Business Modeler deep copy rules.
Valid values:

I-deas object types (e.g., I-deasPart, I-deasAssembly)

Default value:

There is no default.

IDEAS_ideas_datasets List of dataset types specific to the I-deas application. This

preference is applicable to the Freeze→Create New
Revision functionality.
Valid values:

I-deas object types (e.g., I-deasPart, I-deasAssembly)

Default value:

2-42 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

There is no default.

IDEAS_catiav4_Datasets List of dataset types specific to the Catia V4 application.

This preference is applicable to the Freeze→Create New
Revision functionality.
Valid values:

Catia object types

Default value:

There is no default.

IDEAS_catiav5_Datasets List of dataset types specific to the Catia V5 application.

This preference is applicable to the Freeze→Create New
Revision functionality.
Valid values:

Catia object types (e.g., CATPart, CATProduct)

Default value:

There is no default.

IDEAS_push_ng_to_hub While performing the Freeze→Create New Revision

operation on the first revision of an Item, the Item along
with its revision and the revision contents are pushed to
the hub site. This supports the Multi-Site environment in
the NG model.
Valid values:

TRUE
FALSE

Default value:

There is no default.

IDEAS_use_item_level_right Specifies whether the Item level or dataset level of

_to_modify ownership (right to modify) is used.
Valid values:

FALSE
The dataset level of ownership (right to modify) is
used.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-43
© 2020 Siemens
 2. Preferences

Preference Name Description

TRUE
The Item level of ownership (right to modify) is used.

Note:
This value should only be used if you cannot
transition to the new dataset level method for
some reason.

Default value:

FALSE

IDEAS_set_latest_dataset_right_to Specifies whether the datasets under all Item Revisions or

_modify_only only the latest Item Revision has the owning user set to the
I-deas external owning user when using the dataset level
method for ownership. The method of ownership is set in
the preference IDEAS_use_item_level_right_to_modify
described above.
Valid values:

FALSE
All Item Revisions are set to the I-deas external
owning user.
TRUE
Only the latest Item Revision is set to the I-deas
external owning user.
When set to TRUE, the Teamcenter Access Manager
rules for objects owned by the I-deas external owning
user must be set to prevent delete privilege. If the
delete privilege is not prevented, the latest dataset
could be deleted and the previous Item Revision
checked out thereby bypassing the right to modify
constraints.

Default value:

FALSE

IDEAS_import_mapfile Specifies the path (including file name) for the XML map
file used for import.
Valid values:

Any valid location on disc. The complete file path

must be used with the filename.

2-44 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

NONE

Default value:

NONE

IDEAS_threaded_migration Enables the multi-threaded migration mode when set to

TRUE. In this mode, the migration process starts extracting
the next structure from the TDM while the data from the
current structure is being loaded into the Teamcenter
database.
Valid values:

TRUE
FALSE

Default value:

FALSE

TC_truncate_file_name Truncates file names when importing or migrating I-deas

data into Teamcenter.
During import, file names are truncated to 30 characters if
the TC_truncate_file_name preference is set to TRUE (the
default). Truncation can cause file names to become non-
unique (Teamcenter handles this situation such that it
recognizes all file names as unique).
When the files are exported to I-deas, the uniqueness is
given by appending a unique suffix to each non-unique file
name.
To preserve the original I-deas file names for uniqueness,
set the preference to FALSE to allow file names of 132
characters maximum (I-deas file names are only 80
characters maximum).
Valid values are:

• TRUE
Truncates file names to 30 characters maximum. This is
the default.
• FALSE
Allows long file names to be used up to 132 characters
maximum.

This preference affects the value of the original filename

attribute for a file object in Teamcenter. This value only

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-45
© 2020 Siemens
 2. Preferences

Preference Name Description

affects the export I-deas package operation in Integration

for I-deas. The export will contain filenames that have
potentially lost their unique identification. This is only a
concern if the filename is important in a downstream
export process.

IDEAS_name_replace_invalid Some characters, such as the colon (:), are allowed in

_chars Teamcenter for Item IDs and item names but are not
supported in I-deas. This can cause a problem when
sending an item to I-deas. This preference modifies the
Item ID and item name for I-deas while preserving the
original Item ID and name in Teamcenter.
Characters in the Item ID and item name that are not
supported by I-deas are replaced with the underscore (_)
character when an item is sent to I-deas. The Item ID and
item name is shown with the underscore in the Integration
for I-deas window, but in Teamcenter, it's shown with the
original name. The character replacement is a temporary
modification to enable the item to be used in I-deas.
Characters not supported by I-deas include:

comma ,

exclamation point !

dollar sign $

asterisk *

at sign @

quotation marks "

question mark ?

colon :

semicolon ;

If a drawing is created for a part in I-deas that has had

characters replaced with underscore characters, the
drawing part number/name also has the underscore
characters in I-deas, but those characters are replaced to
match the part when the drawing is saved in the same Item
Revision as the part in Teamcenter.
Valid values:

2-46 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

• TRUE
Characters are replaced with underscores for items sent
to I-deas that contain characters in the Item ID and name
not supported by I-deas.

• FALSE
Item ID and item name are not modified when an item is
sent to I-deas.

Default value:

FALSE

IDEAS_Project_Mandatory_on _save This controls whether project assignment is mandatory.

Valid values:

TRUE – You must set a project for each new item

saved. The Save to Teamcenter dialog is displayed
until the project is defined.

FALSE – A project is not mandatory.

Default value:

FALSE

IDEAS_Mandatory_Attr This provides a list of the attributes that are mandatory for
each item saved.

Note:
This preference must be created as a site preference.

Valid values:

Valid attributes. Each attribute name is followed by a

comma.
Use only I-deas attribute names, not Teamcenter
attribute names for the values. The I-deas attribute
names are in the I-deas Manage Bins dialog box,
Details list. The attributes must be mapped in
Teamcenter. Refer to the attribute mapping file for
names of the attributes that are mapped.
The attribute master cannot be iman, where
master=iman. It can only be cad or both.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-47
© 2020 Siemens
 2. Preferences

Preference Name Description

Default value:

No values listed

IDEAS_cad_file_compression Compresses the CAD files. Enabling compression of files

can provide a performance improvement. The performance
gain depends upon the size and makeup of the product
structure. Typical improvement gains are 0 – 45% for
checkout and 18 – 35% for checkin.
Before using compression, you need to be aware of the
implications. All I-deas CAD files are compressed in the
Teamcenter volume. If you have customizations that obtain
files from the Teamcenter volume, these customizations
could be affected. In addition, anti-virus programs must be
configured to skip files with a .Z extension or to bypass the
following directories entirely:

Teamcenter volume directory (s)

Checkin temporary directory (java.io.tmpdir)

Checkout temporary directory (TCExportDir, unless

file caching is used)

IDEAS_migrate_attr_sync_missing These preferences specify the action that occurs when the
_object_action object specified by the mapping cannot be found. This is
during the processing of database attribute mapping
IDEAS_import_attr_sync_missing
definitions during the migration, import, and export
_object_action
processes.
IDEAS_export_attr_sync_missing
Valid values:
_object_action
IGNORE
Ignore the missing object and skip mapping the
attribute.

WARN
Print a warning to the log file that the attribute was
skipped.

ERROR
Produces an error that causes the operation to fail.

Default value:

Migration and import: FALSE

2-48 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Export: IGNORE

Note:
The default for export is IGNORE because there
may be attributes mapped by migration that are
not present for new checked in data.

IDEAS_item_id_with_wildcard Specifies how ItemID values are handled when they

_chars_action contain wildcard characters.
Valid values:

WARN
Print a warning to the log file and use the ItemID as it
is (with the wildcard characters).

RECOVERABLE_CONFLICT
The ItemID is treated as a conflict. Action taken is
specified by the conflicting ID option selected (skip,
auto-assign, and so on).

ERROR
The ItemID is an error. Do not import the item
version.

REPLACE_WILDCARDS
Replace a wildcard character with a valid character as
specified by the
IDEAS_item_id_with_wildcard_replacement_char
preference (below).

Default value:

WARN

IDEAS_item_id_with_wildcard Specifies the character to use as the replacement for a

_replacement_char wildcard character in an ItemID. Replacement of characters
is enabled by the preference and setting
IDEAS_item_id_with_wildcard_chars_action=
REPLACE_WILDCARDS (above).
Valid values:

Any character that is valid for an ItemID.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-49
© 2020 Siemens
 2. Preferences

Preference Name Description

Default value:

The dash character (—)

IDEAS_item_revision_create Specifies the value used for the Item Revision creation date.
_date_value The value is taken from the TDM metadata or derived from
the version GUID value.

Note:
This applies to migration and import only and the
GUID option should only be used when all data
migrated or imported is from I-deas Master Series 8
or later.

Note:
Because GUID values can change based on various
TDM actions which lose the original creation date
information, it is recommended that the default value
for this preference is not changed from the
METADATA value. The miadmin tool can repair
problems with the metadata but cannot repair the
effects of the GUID changes.

Valid values:

METADATA
Value taken from the TDM metadata.

GUID
Value derived from the GUID.

Default value:

METADATA

IDEAS_external_owning_user When external ownership (the right to modify) is updated

_update_use_ItemRevision during the I-deas package file import process, normally the
owning user is defined to be the user that is doing the
import (the default). You can change the owning user of
the imported dataset to be the same as the owning user of
the Item Revision where the dataset is placed. This is
particularly useful where the original I-deas creation user
was applied to the dataset by a customizaton during the
migration process.

2-50 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Valid values:

TRUE
Owning user is same as Item Revision

FALSE
Owning user is importer.

Default value:

FALSE

IDEAS_default_item_type_part Defines the default item type for a newly created I-deas
part, assembly, and so on.
IDEAS_default_item_type_assembly
If these preferences are not defined, the
IDEAS_default_item_type_drawing
IDEAS_default_item_type defines the type of item created
IDEAS_default_item_type by default when new items are saved from I-deas to
_drawing_set Teamcenter.
IDEAS_default_item_type_fem If the preference IDEAS_default_item_type is not defined,
the default item type used for newly created items is Item.
These preferences apply to newly created items that are
being saved to Teamcenter. These are default item types
assigned and can be changed with the Item Type pull-
down menu in the Save to Teamcenter dialog.

Note:
These preferences are also applicable for migration
and data sharing.

IDEAS_migrate_all_for_reference Creates all items with a reference status when

IDEAS_external_owning_user_name is used.
During migration, you can ignore the status of the I-deas
import/export lock on items and create all items in
Teamcenter as owned by the value defined by the
preference IDEAS_external_owning_user_name.
Valid values:

TRUE
All items are owned by the external owning user.

FALSE
Items are owned by importer.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-51
© 2020 Siemens
 2. Preferences

Preference Name Description

Default value:

FALSE

IDEAS_default_item_name_<user When you have Teamcenter Business Modeler Naming

defined item type> Rules (BMNR) defined for item name, the preference is
required to get attribute mapping to work correctly.
IDEAS_default_item_name
• IDEAS_default_item_name_<user defined item type>
Set this to a value that complies with the BMNR for this
item type. For example, if the BMNR name for this item
type is defined as @@@NNN and the user defined item
type is test, then
IDEAS_default_item_name_test=XYZ678 is correct
usage of the preference. In this example, XYZ678 is the
value for the default item name for the item type test.
Valid values:

Valid user defined item type and name that

complies with the BMNR for the item type.

Default value:

None

Alternatively, if you have the same BNMR for all/remaining

item types for the item name field, add the following
preference:

• IDEAS_default_item_name=@@@NNN
Valid values:

Name that complies with the BMNR for the item

type.

Default value:

None

If neither preference is set, the item name dummy is used

to allow the software to pass naming rules for the item
name field for item types. You must ensure that the item
name dummy is a valid item name for the item type (i.e.,
the BMNR is defined as @@@@@).

2-52 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

IDEAS_precise_rev_rule Sets the Teamcenter revision rule to precise BOM when this
preference is set to a revision rule with precise as the first
entry.
A precise BOM allows you to have an assembly that
contains specific revisions of parts and subassemblies. In
Teamcenter, the BOMView Revisions (BVR) objects store the
single-level assembly structure. A precise BOM reflects the
latest changes made to the assembly when the Teamcenter
revision rule is set to precise.
For example, you can modify a part in an assembly in I-deas
and update the assembly to contain the latest revision of
the part. When you save the part and assembly to
Teamcenter, the BOM is updated to contain the latest
revision of the part.
If the BOM is not being updated (precise BOM), the
Teamcenter revision rule doesn't contain Precise as the
first entry in the revision rule dialog box. Set the first entry
to Precise.

Note:
If the Precise Only revision rule entry has been
deleted (not available for selection), set this
preference to the name of a revision rule that
contains Precise as the first entry.

Valid values:

Revision rule that contains Precise as the first entry.

Default value:

None

IDEAS_check_BMNR Checks for the Teamcenter Business Modeler Naming Rules

(BMNR) for ItemID and RevId during save to Teamcenter.
If the items don't comply with BMNR for ItemId and RevId,
when you click OK on the save dialog box, you get error
messages that include the format for each (ItemId and
RevId). When you close the error dialog, you can edit the
values in the save dialog box to comply with the BMNR.
Valid values:

TRUE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-53
© 2020 Siemens
 2. Preferences

Preference Name Description

Checks for the BMNR during save to Teamcenter.

FALSE
Saves to Teamcenter without checking for BMNR.

Default value:

FALSE

IDEAS_send_itemrev_dataset _PS When set to TRUE, the following option in the Integration
for I-deas Preferences dialog box is checked (set to On):

Sending an Item Revision causes the Part/Assy to

be sent
When you select an Item Revision, the assembly and
part datasets are sent to I-deas.
This is checked Yes (set to TRUE) by default. If this is
unchecked and the three preferences listed below are
unchecked, no datasets will be selected when an Item
Revision is selected and an error is output during the
send to I-deas operation.

Valid values:

TRUE

FALSE

Default value:

TRUE

IDEAS_send_itemrev_dataset When set to TRUE, the following option in the Integration

_DWG_FEM for I-deas Preferences dialog box is checked (set to On):

Sending an Item Revision causes the DWG/FEM to

be sent
When you select an Item Revision, the drawing or FEM
dataset is sent to I-deas. If the I-deas application open
is Simulation, the FEM datset is sent. If the application
is Design, the drawing dataset is sent.

Valid values:

TRUE

2-54 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

FALSE

Default value:

FALSE

IDEAS_send_itemrev_dataset _DSET When set to TRUE, the following option in the Integration
for I-deas Preferences dialog box is checked (set to On):

Sending an Item Revision causes the Drawing Set

to be sent
When you select an Item Revision, the drawing set
dataset is sent to I-deas.

Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_send_itemrev_dataset When set to TRUE, the following option in the Integration

_allow_multiple_datasets for I-deas Preferences dialog box is checked (set to On):

Should multiple DWG/FEM be sent?

When you select an Item Revision that contains
multiple drawings or FEMs, they are all sent to I-deas.
If the I-deas application open is Simulation, all the
FEM datsets are sent. If the application is Design, all
the drawing datasets are sent.
If this option is not checked and multiple drawing or
FEM datasets are available, then no datasets are sent.
However, if only one drawing or FEM dataset is
available, it is sent if the option Sending an Item
Revision causes the DWG/FEM to be sent (above) is
checked.

Valid values:

TRUE

FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-55
© 2020 Siemens
 2. Preferences

Preference Name Description

Default value:

FALSE

IDEAS_pre-import_validation Performs some validation checking prior to actually

importing the data during I-deas package import.
Only certain types of problems can be validated prior to
actually creating the data in the database, such as name
conflict, ownership conflict, and most internal item GUID
conflicts. Validations with other items within the package
are not performed and conflicts between parts and
drawings that are managed within the same item revision
cannot be detected until the items are created in the
Teamcenter database.
The default (FALSE) is to begin importing data to
Teamcenter and only go into validation mode for the
remaining items when an item fails to import.
Valid values:

TRUE
Perform I-deas package validation prior to creating
data in Teamcenter.

FALSE
Start package data import creation immediately.

Default value:

FALSE

IDEAS_import_skip_renamed _items By default, during import of a package file, if the Item ID for
an item already exists in Teamcenter (identified using the
internal Item GUID) but it is different than the Item ID for
the same item in the package file, the Item ID that already
exists in Teamcenter is used. A warning is displayed that
the Item ID was reassigned during import.
The preference changes the warning to an error when the
Item ID is changed. If the conflicting ID option is set to skip
(Skip such an item in the package import dialog box) and
the preference is set, the package import skips a renamed
item, reports an error to the import log file, and aborts the
import process.
This does not apply when the package Item ID is missing.
This preference also does not apply to drawing and FEM

2-56 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

items types since they may be managed with the related

part or assembly.
Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_send_default_NX_as When a new part is added to an NX assembly during an

update, it is added according to the setting of the
preference.
Valid values:

JT – Sends the part as a JT part.

NX – Sends the part as an NX part.

Default value:

JT

IDEAS_import_compressed_files This preference does not compress files, but supports

migration and import of already compressed files.
IDEAS_migrate_compressed_files
Valid values:

TRUE

FALSE

Default value:

TRUE

IDEAS_keep_standalone_dwg This preference controls how standalone drawings are

_with_existing_item saved.
Valid values:

• ONLY_IF_SAME_ID
The standalone drawing is saved in the Item Revision of
any dataset if the drawing has the same ItemID as the

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-57
© 2020 Siemens
 2. Preferences

Preference Name Description

dataset. If the standalone drawing has a different ItemID

than the dataset, it is placed in its own unique Item.

• NEVER
Standalone drawings are not saved into an Item if the
Item already contains any other I-deas dataset, including
other standalone drawings. Also, any other I-deas
dataset cannot be saved to an Item that contains a
standalone drawing.
Two or more new standalone drawings (not part of a
drawing set) cannot be assigned the same ItemID
because they cannot be saved to the same Item.
If a standalone drawing is saved with any other I-deas
dataset type (such as a part), they cannot be assigned
the same ItemID because they cannot be saved together
in the same Item.

Note:
When you click the OK button in the Save dialog
box, an error message dialog is displayed and the
Save dialog box is again displayed with the ItemID
values set to blank for those items that need to
have different ItemIDs.

Default value:

NEVER

The following exclusions also apply:

• The preference
IDEAS_keep_dwgset_with_related_drawing overrides
IDEAS_keep_standalone_dwg_with_exisitng_item.

• If a part/assembly is already saved with a standalone

drawing and a drawing of the existing part/assembly is
created and the preference
IDEAS_keep_drawing_with_related_model is set to
either ALWAYS or ONLY_IF_SAME_ID, the related
drawing is allowed to be saved with the part/assembly.
This allows legacy items to be saved as they were
previously.

2-58 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Note:
This also applies to FEMs and the preference
IDEAS_keep_fem_with_related_model.

IDEAS_send_assembly_config_data Controls the amount of Integration for I-deas data saved to

Teamcenter during checkin of assemblies.
Valid values:

FALSE
Easily recomputed assembly data is not sent to
Teamcenter during checkin. This improves
performance of the checkin for assemblies.

Note:
This does not cause degradation of the model or
data corruption.

TRUE
All assembly data is sent to Teamcenter during
checkin.

Default value:

TRUE

IDEAS_checkin_allow_non Controls checkin of items that are not synchronized with

_synchronized_items Teamcenter.
Valid values:

TRUE
Checkin proceeds although some items are not
synchronized with Teamcenter. This could cause
checkin to fail more often compared to synchronizing
the data before checking in. For example, checkin
could fail if some of the items are no longer in
Teamcenter or if their status has changed.
This preference works in conjunction with the
preference IDEAS_automatically_synchronize which
should be set to FALSE to avoid automatic
synchronization during model file open.

FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-59
© 2020 Siemens
 2. Preferences

Preference Name Description

Checkin does not proceed if the items are not

synchronized with Teamcenter.

Default value:

FALSE

IDEAS_harness_translator_hn _option Controls where the JT file for a harness is located.

When saving to Teamcenter, a JT file is created for each
wire harness referenced by the assembly. This preference
determines where the harness is attached.
Valid values:

FALSE
The JT file created for the wire harness is attached to
the context assembly containing the harness.

TRUE
The JT file created for the wire harness is attached to
the DirectModel dataset that represents the harness.

Note:
The harness display is more accurate if this
value is used.

Note:
This preference is applicable only for I-deas 12
m4 or higher. If this is set to TRUE on an earlier
version, JT translation failure could result.

Default value:

FALSE

IDEAS_use_tc_desc_as_partname Determines what is used for the name when an item is

saved, sent to I-deas, and so on. Depending on the
operation, length of part name, and value of this
preference, the name could be different in I-deas and
Teamcenter.

2-60 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences I

Preference Name Description

Note:
This applies to parts, assemblies, and drawing sets
where the Item Name and item description are used,
and drawings and FEMs where the Dataset Name and
dataset description are used in Teamcenter.

Valid values:

TRUE
When a part is saved, the Teamcenter Description field
and Item Name field are populated with the I-deas
part name.
When the part is sent to I-deas (or during a
Synchronize or Find Out of Date operation), the
Description field is used as the I-deas part name.
If the Description field is empty, the Item Name is used
as the I-deas part name.

FALSE
When a part is saved, if the I-deas part name is less
than 32 characters, the part name is the Item Name
and the Description field is empty. If the I-deas part
name is greater than 32 characters, Teamcenter uses
the first 32 characters as the Item Name and the
entire part name is stored in the Teamcenter
Description field.
When the part is sent to I-deas (or during a
Synchronize or Find Out of Date operation), the Item
Name is used as the I-deas part name. This occurs if
the Description field is empty (part name) was not
over 32 characters) or the Description field is
populated but the first 32 characters in the
Description field do not match the Item Name
(Description field was modified in Teamcenter),
If the Description field is populated (part name was
over 32 characters) and the first 32 characters match
the Item Name, that is used as the I-deas part name
during a send to I-deas operation.

Default value:

FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-61
© 2020 Siemens
 2. Preferences

Integration for I-deas Preferences II

This table also contains preferences that are used to configure Integration for I-deas.

Preference Name Description

IDEAS_<I-deas Dataset Type>_forms Preference can take the form of:

IDEAS_IdeasPart_forms

IDEAS_IdeasAssembly_forms

IDEAS_IdeasDrawing_forms

IDEAS_IdeasFem_forms

IDEAS_IdeasDrawingSet_forms

Specifies the I-deas dataset forms that are to be created

during import and migration. The forms are attached to the
I-deas datasets using either a Named Reference or a GRM as
specified in the preference.
Created forms can be used to populate attributes using
USER_EXITs to populate the necessary information. Format:
FormTypeName:GRM or NR:GRMName or NamedRefName

IDEAS_auto_assign_all _itemid Controls whether to always auto assign the Item ID during
import and migration. If this preference is set to TRUE, then
the imported or migrated Item ID will be set to the auto-
generated number from Teamcenter.
Also, if this preference is set to TRUE, it overrides the
migration option when an Item ID is missing. Effectively,
this preference set to TRUE causes that option to behave in
the auto-assign mode regardless of how it is set.
Valid values:

TRUE

FALSE

Default value:

FALSE

2-62 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences II

Preference Name Description

IDEAS_export_auto_expand Automatically adds any context assembly required to the

_acf_relations resulting package in order to satisfy ACF dependencies in
the items selected for export.
When set to TRUE, the ACF relations of the part are
traversed such that the related items are included in the
package file. Only the latest version of the part/assembly
under the related Item Revision is included in the package
file and it is included with reference status. The process
occurs automatically without any input or selection and is
transparent during the export process.
When set to FALSE, you must interactively select all required
ACF context assemblies. The export process reports all
missing dependent items in this case.
Valid values:

TRUE

FALSE

Default value:

TRUE

IDEAS_import_attr_sync Specifies the action to take when applying database

_invalid_value_action attribute mapping definitions during the migration and
import processes when the value being processed is not a
valid value for the attribute specified by the mapping
definition.
For example, the attribute may have an exhaustive List of
Values attached and the incoming value is not one of the
allowed values. The process can ignore, warn, or produce an
error.
Valid values:

IGNORE
Ignore the invalid value and skip mapping the
attribute.

WARN
Print a warning to the log file and skip mapping the
attribute.

ERROR
Produce an error causing the operation to fail.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-63
© 2020 Siemens
 2. Preferences

Preference Name Description

Default value:

WARN

IDEAS_import_attr_sync Specifies the action to take when applying database

_type_mismatch_action attribute mapping definitions during the migration and
import processes when the attribute type being processed
does not match the attribute type as defined by the
database schema.
For example, the attribute is an integer TDM attribute and
the attribute mapping definition specifies a POM String
attribute. The process can ignore, warn, or produce an error.
Valid values:

IGNORE
Ignore the invalid value and skip mapping the
attribute.

WARN
Print a warning to the log file and skip mapping the
attribute.

ERROR
Produce an error causing the operation to fail.

Default value:

ERROR

IDEAS_import_compressed _files Specifies whether compressed ADB files should be loaded

into the volume. This preference does not specify whether
the files should be compressed by the migration and import
processes, only that they should look for and upload the
compressed file if it already exists.
Compressed files must have a .Z file extension.
Valid values:

TRUE

FALSE

Default value:

TRUE

2-64 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences II

Preference Name Description

IDEAS_mig_import_add_to This preference is applicable when the preference

_folders_matched_item IDEAS_mig_import_add_to_folders is set to ON.
Valid values:

IMPORT

FALSE

BOTH

NONE

Default value:

IMPORT

IDEAS_migrate_attr_sync Specifies the action to take when applying database

_invalid_value_action attribute mapping definitions during the migration and
import processes when the value being processed is not a
valid value for the attribute specified by the mapping
definition.
For example, the attribute may have an exhaustive List of
Values attached and the incoming value is not one of the
allowed values. The process can ignore, warn, or produce an
error.
Valid values:

IGNORE
Ignore the invalid value and skip mapping the
attribute.

WARN
Print a warning to the log file and skip mapping the
attribute.

ERROR
Produce an error causing the operation to fail.

Default value:

WARN

IDEAS_migrate_attr_sync This preference specifies the action to take when applying

_type_mismatch_action database attribute mapping definitions during the migration

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-65
© 2020 Siemens
 2. Preferences

Preference Name Description

and import processes when the attribute type being

processed does not match the attribute type as defined by
the database schema.
For example, if the attribute is an integer TDM attribute and
the attribute mapping definition specifies a POM String
attribute. The process can ignore, warn, or produce an error.
the invalid mapping and skip mapping the attribute, print a
warning to the log file and skip mapping the attribute, or
produce an error causing the operation to fail. Valid values:
IGNORE, WARN, ERROR Default value: ERROR
Valid values:

IGNORE
Ignore the invalid mapping and skip mapping the
attribute.

WARN
Print a warning to the log file and skip mapping the
attribute.

ERROR
Produce an error causing the operation to fail.

Default value:

ERROR

IDEAS_migrate_compressed _files Specifies whether compressed ADB files should be loaded

into the volume. This preference does not specify whether
the files should be compressed by the migration and import
processes, only that they should look for and upload the
compressed file if it already exists.
Compressed files must have a .Z file extension.
Valid values:

TRUE

FALSE

Default value:

TRUE

2-66 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences II

Preference Name Description

IDEAS_migrate_non_latest Specifies whether non-latest versions in an item series

_versions_for_reference should be explicitly marked for reference during migration.
Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_multi_site_impl Specifies the method used to index I-deas Item GUIDs across
sites in a Multi-Site Collaboration environment. An I-deas
item version series must be tracked by a single Teamcenter
Item object. I-deas Item GUIDs can be indexed in two ways:

• HUB – Using a site configured as an I-deas GUID Hub Site.

(deprecated)

• APPREF – Using a site configured to provide an APPREF

REGISTRY. The preference TC_appref_registry_site must
be defined when this mode is used.

• HYBRID – Using a site configured to operate in an Hybrid

multisite environment. Hybrid multisite configuration
where some sites in the collaboration are configured as
HUB, some can be configured as HYBRID, and some can
be configured as APPREF.
Both of the preferences TC_appref_registry_site and
IDEAS_hub_site_name must be defined when HYBRID
mode is used.

This preference is required in a Multi-Site environment.

Valid values:

HUB

HYBRID

APPREF

Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-67
© 2020 Siemens
 2. Preferences

Preference Name Description

None

IDEAS_multisite_util_batch _size Controls the batch size used when invoking the data_share
utility. Only used with an I-deas GUID Hub site.

Note:
This preference replaces the old
IDEAS_giman_util_batch_size preference.

Valid values:

A positive integer batch size

Default value:

None, data_share utility default is used.

IDEAS_pre-import_validation Allows import to operate in validate mode. If there are any

errors during validation, the import does not create any
items. If the validation was successful, the import will create
the new items

IDEAS_skip_remote_import Normally in a Multi-Site environment, items which are

_matched_versions owned by another site are remote imported for reference so
that an up-to-date copy of the I-deas data is available at the
local site. This preference allows the remote import to be
skipped when the exact matching version is already present
in the local database.

Note:
This preference provides the same behavior as the old
preference IDEAS_query_before_remote_import.

Valid values:

TRUE

FALSE

Default value:

TRUE

IDEAS_skip_remote_transfer For an object to be modified it must be owned by the local

_ownership_matched _versions site. By default, when an exact version match is found which

2-68 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences II

Preference Name Description

is owned by a remote site the ownership is not transferred

to the local site if the import process does not need to
modify the objects. This preference allows you to specify
that site ownership should always be transfered in this case.
If the IDSUSER_import_item_post() user exit is used, care
must be taken to check if the objects are owned by the local
site before modifying them when this preference is set to
TRUE.

Note:
This preference provides the same behavior as the old
preference IDEAS_update_matched_versions.

Valid values:

TRUE

FALSE

Default value:

TRUE

IDEAS_use_existing_item By default an existing Item with the same ID will always be

_with_only_non_ideas_data used by migration and import processing as long as there
are no conflicting I-deas datasets under the Item. Set this
preference to FALSE to treat Items with the same ID which
only contain non I-deas datasets as a conflicting Item ID
case.
Valid values:

TRUE

FALSE

Default value:

TRUE

IDEAS_drawing_create_cgm Creates an Image dataset for an I-deas drawing when the

drawing is checked in. You can then view the CGM in
Teamcenter Visualization. The CGM is created in accordance
with the CGM options set in I-deas. The Image dataset

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-69
© 2020 Siemens
 2. Preferences

Preference Name Description

contains the CGM file and is attached to the I-deas drawing

dataset.
This is a user and site preference. When this preference is
set, performing a checkout of the drawing also checks out
the associated Image dataset, cancelling checkout of the
drawing cancels checkout of the Image dataset, and
synchronization of the drawing syncs the Image dataset.
Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_drawing_create_cgm Creates an Image dataset for each sheet of an I-deas

_multi_sheet drawing that has multiple sheets.
The preference IDEAS_drawing_create_cgm (above) must
also be set to enable the functionality for this preference.
This is a site preference only.
Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_run_hammedic Runs the HAM Medic utility during the send to I-deas
process on all checked out and referenced items sent to I-
deas.
HAM Medic is an I-deas utility used to clean bad HAMs from
I-deas data. The I-deas History Access Mechanism (HAM)
adds history data to I-deas parts, assemblies, and so on.
After a period of time these HAMS can accumulate and
cause problems for I-deas data. You might experience
significant performance degradation during send to I-deas,
or the operation could hang indefinitely. Periodically, this
data needs to be cleansed from I-deas items.

2-70 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences II

Preference Name Description

Send to I-deas performance is affected when using this

utility so it should be used only when required. When HAM
Medic is run, the output is written to the TB.log file.
If HAM Medic is run during export to TDM, the preference
IDEAS_run_hammedic must be set to TRUE as a site
preference. The output is written to the export log file if
available, otherwise it is written to the TB.log file.
The HAM Medic command is in the ham_medic.bat file
located in the Portal directory. The command can take
multiple options and you can add/change options to get
different results. The default option used by Integration for
I-deas is –v (verbose). For additional information on HAM
Medic including options available, see the I-deas
documentation set.

Note:
You can also enable this functionality by choosing Run
HAM Medic in the Teamcenter Integration for I-
deas Preferences dialog box (Edit→Preferences in
the Integration for I-deas window):

Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_show_purge Enables the purge Item Revisions functionality. This adds the
menu selection Purge Item Revisions to the Teamcenter
_revision_ui
IDEAS menu.
Valid values:

TRUE

FALSE

Default value:

FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-71
© 2020 Siemens
 2. Preferences

Preference Name Description

IDEAS_purge_revision Determines the number of Item Revisions kept when the

Item Revisions are purged from an Item.
_keep_limit
Valid values:

Any integer.

Default value:

IDEAS_save_configurations Saves the assembly design configurations during checkin to

Teamcenter.

Note:
To ensure the accuracy of the configuration in
Teamcenter, design configurations must be used and
this preference should be set to TRUE.

Valid values:

TRUE
Saves assembly configurations.

FALSE
Does not save assembly configurations. Teamcenter
arrangements are not created. Instead relative
transforms are set on each occurrence (previous
functionality). When this is done, the view of a model
may not be correct.
Also, relative transforms used are based on the active
configuration, not the assembly's used configuration,
which could result in slightly different looking models
than if it was based on the used configuration.

Default value:

TRUE

IDEAS_send_option_bin _attributes When an part/assembly/drawing/drawing set is sent to I-

deas it can automatically be sent to a specific bin based on
the attributes of the part/assembly/drawing/drawing set.
The preference is defined with attribute names. If the
attributes of the part match the attributes of the preference
a bin is created for the item. The name of the bin is the
value of each attribute separated by a hyphen. If an

2-72 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Integration for I-deas Preferences II

Preference Name Description

attribute is not present in the part, it is skipped and the next

attribute is used for the name. If the bin does not exist, a bin
is automatically created. If no part attributes match the
preference attributes, the Destination Bin is used.

Note:
The attributes in the part must have the master
mapped as iman or both.

Valid values:

Comma separated list of attributes that define the bin

name during Send to I-deas.

TC_GROUP
This is an optional value included if the owning group
of part/assembly/drawing/drawing is added to the bin
name.

The attribute TC_GROUP defines the owning group of the

item in Teamcenter. It can be added to the preference list of
attribute names. If the attribute is present in the preference,
the owning group of the part/assembly/drawing/drawing is
added to the bin name.

Note:
This preference is not applicable for FEMs because
FEMs always go to the same bin as its related part.

The following example uses this preference:

The following attributes are defined for IdeasAssembly:

Weight, Height, Color. The master for these

attributes is iman or both.

The values for the attributes in the assembly are:

Weight=10

Height=50

Color=Red

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-73
© 2020 Siemens
 2. Preferences

Preference Name Description

The owning group of the assembly is dba.

The preference is defined as follows:

IDEAS_send_option_bin_attributes
=Weight,Color,TC_GROUP

When the assembly is sent to I-deas, the following new

bin is created:

10_Red_dba

IDEAS_import_allow_legacy Controls whether mixed mode I-deas assemblies are

_assemblies imported into Teamcenter. Mixed mode assemblies are post-
MS8 assemblies that contain pre-MS8 subassemblies.
Valid values:

TRUE
Mixed mode I-deas assemblies can be imported into
Teamcenter.

FALSE
Mixed mode I-deas assemblies cannot be imported into
Teamcenter.

Default value:

FALSE

IDEAS_use_tmtid_as_seqno During import from TDM, determines whether to assign the

sequence number/find number from the Tree Map Table
Identifier (TMTid)/Child ID specified in the package file, or to
assign in accordance with the value of the Teamcenter
preference PS_new_seqno_mode.
Valid values:

TRUE
Use the TMIid/Child ID from the package file

FALSE
Use the Teamcenter preference PS_new_seqno_mode

Default value:

2-74 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Specific Preference Data

Preference Name Description

FALSE

IDEAS_use_existing_item Used during migration and import processing to identify

_with_no_data Items that contain no datasets.
By default, an existing Item with the same Item ID is used by
migration (and import) as long as there are no conflicting I-
deas datasets in the Item.
When the preference IDEAS_use_existing_item_with_only
_non_ideas_data is set to FALSE, Items with the same Item
ID which only contain non-I-deas datasets are treated as a
conflicting Item ID case.
When this preference,
IDEAS_use_existing_item_with_no_data, is also set to
FALSE, Items with the same Item ID that contain no
datasets are also treated as a conflicting Item ID case.
This preference is dependent upon and must be used with
the preference IDEAS_use_existing_item_with_only
_non_ideas_data.
Valid values:

TRUE

FALSE

Default value:

TRUE

Specific Preference Data

The following is additional information, requirements, and user actions for specific preferences:

IDEAS_external_owning_user_name

You must create Access Manager rules that do not allow write access to objects that have this preference
value as their owning user value.

Use the Access Manager Rule tree within the Teamcenter Access Manager application to create rules
that block out other users that are in the importing user group from having write privileges on the
external owning user data.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-75
© 2020 Siemens
 2. Preferences

Note:
For information on using Access Manager, see the Teamcenter online help.

Within Access Manager:

1. Create a new condition under the out-of-the-box (OOTB) Has Class (POM_application_object) →
Import/Export condition.

2. Create the new Owning User condition.

3. Add the condition value asideas_external.

4. Attach a new I-deas external ACL name, for example, XYZ I-deas External.

5. On the ACL, explicitly prevent the World from modifying the data and allow publish and transfer
out.

Disabling Preferences For an Integration for I-deas Session

The preferences used to configure the Integration for I-deas options are located in the Teamcenter
preferences. Many of these options are available in My Teamcenter by selecting Edit→Options, and
choosing Integration for I-deas in the Options dialog. They can be changed in the dialog during the
session of Integration for I-deas you're running.

To lockout an option and keep it from being changed during a session, add Disallow to the end of the
preference in the Teamcenter preferences and set it to true (lowercase), on (lowercase), or 1. The
checkbox for the option is grayed out in the Options dialog. The preference must be set before starting
the session of Integration for I-deas.

This can be useful at the site level if, for example, you want all users to create a DirectModel dataset (JT
file) when saving parts to Teamcenter. Set the following in the Teamcenter preferences:

IDEAS_part_create_jt=TRUE

IDEAS_part_create_jt.Disallow= true

Engineering Translation Services Preferences

This listing contains preferences that are used to configure Teamcenter engineering translation services
(ETS) for Integration for I-deas.

ETS.PRIORITY.UGS.IDEASTOJT_DIRECT

ETS.DATASETTYPES.UGS.IDEASTOJT_DIRECT

2-76 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Engineering Translation Services Preferences

ETS.PRIORITY.UGS.IDEASTOCGM_DIRECT

ETS.DATASETTYPES.UGS.IDEASTOCGM_DIRECT

IDEAS_translation_service_name

IDEAS_check_in_generate_vis_data_priority

IDEAS_import_translation_service_name

IDEAS_imort_from_tdm_default_gen_vis_data_priority

IDEAS_import_from_tdm_gen_vis_data_display

IDEAS_import_from_tdm_gen_vis_data_input

IDEAS_import_from_tdm_options_default_gen_vis_data_priority

IDEAS_ideastojt_import_translation_config_filename

IDEAS_migration_translation_service_name

IDEAS_migrate_gen_vis_data_priority

IDEAS_migrate_translate_tl_individually

IDEAS_migrate_translate_pre-existing_tl

IDEAS_cgm_translation_service_name

IDEAS_cgm_translation_dataset_type_name

IDEAS_ideastocgm_translation_config_filename

IDEAS_NXRefile

IDEAS_NXRefile_priority

IDEAS_NXRefile_translation_service_name

IDEAS_translation_dataset_type_names

UGSideastojt_IdeasAssembly_ets_nr_types

UGSideastojt_IdeasDrawing_ets_nr_types

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-77
© 2020 Siemens
 2. Preferences

UGSideastojt_IdeasPart_ets_nr_types

IDEAS_ideastojt_translation_config_filename

IDEAS_ideastojt_translation_config_path

ETS_available

Preference Name Description

ETS.PRIORITY.UGS. The scheduling priority for I-deas on-demand JT translations.

IDEASTOJT_DIRECT If this preference is not specified, no visualization data is
generated on-demand.

Note:
Prior to Integration for I-deas 6.0, this was set using
the preference IDEAS_on_demand_generate_vis
_data_priority

For more information, see the Teamcenter Translation

Service documentation.
Valid values:

0
This is OFF.

1
This is low priority.

2
This is medium priority.

3
This is high priority.

Default value:

ETS.DATASETTYPES.UGS. The dataset type names of the I-deas datasets that can be
IDEASTOJT_DIRECT translated by the I-deas to JT translator. If no dataset types
are specified, no dataset type validation is performed.
Additional named reference type validation can be
configured for the datasets specified by this preference
value.

2-78 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Engineering Translation Services Preferences

Preference Name Description

For more information, see the Teamcenter Translation

Service documentation.
Default value:

IdeasPart
IdeasAssembly
IdeasDrawing

ETS.PRIORITY.UGS. The scheduling priority for I-deas on-demand CGM

IDEASTOCGM_DIRECT translations. If this preference is not specified, no
visualization data is generated on-demand.

Note:
Prior to Integration for I-deas 6.0, this was set using
the preference UGSideastocgm_ON_DEMAND
_PRIORITY_PREF

For more information, see the Teamcenter Translation

Service documentation.
Valid values:

0
This is OFF.

1
This is low priority.

2
This is medium priority.

3
This is high priority.

Default value:

ETS.DATASETTYPES.UGS. The dataset type names of the I-deas datasets that can be
IDEASTOCGM_DIRECT translated by the I-deas to CGM translator. If no dataset
types are specified, no dataset type validation is performed.
Additional named reference type validation can be
configured for the datasets specified by this preference
value.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-79
© 2020 Siemens
 2. Preferences

Preference Name Description

For more information, see the Teamcenter Translation

Service documentation.
Default value:

IdeasDrawing

IDEAS_translation_service _name The TSTK provider name and service name of the translator
to be used for I-deas to JT translation.

Note:
If this preference is not specified, requests for I-deas
to JT translations are ignored.

Default value:

UGS.ideastojt_direct

IDEAS_check_in_generate The scheduling priority for I-deas checkin and save

_vis_data_priority translations. If this preference is not specified, no
visualization data is generated for checkin and save.
Valid values:

0
This is OFF.

1
This is low priority.

2
This is medium priority.

3
This is high priority.

Default value:

IDEAS_import_translation The TSTK provider name and special ETS service name of the
_service_name translator to be used for I-deas to JT translation of I-deas
data during data sharing import.

2-80 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Engineering Translation Services Preferences

Preference Name Description

Note:
If this preference is not specified, requests for I-deas
to JT translations during data sharing import are
ignored.

Default value:

UGS.ideastojt_direct_imp

IDEAS_import_from_tdm The translation schedule priority to be used when

_default_gen_vis_data _priority visualization data input is not enabled on the I-deas data
sharing import dialog box. If this preference is not specified,
no visualization data is generated for I-deas data sharing
import.
Valid values:

0
This is OFF.

1
This is low priority.

2
This is medium priority.

3
This is high priority.

Default value:

IDEAS_import_from_tdm Specifies the display of visualization data information on the

_gen_vis_data_display I-deas data sharing import dialog box. If this preference is
not specified, no visualization data generation information
is displayed on the I-deas data sharing import dialog box.
Valid values:

YES

NO

Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-81
© 2020 Siemens
 2. Preferences

Preference Name Description

YES

IDEAS_import_from_tdm Specifies the input of visualization data information on the I-

_gen_vis_data_input deas data sharing import dialog box. If this preference is not
specified, no visualization data generation information can
be input on the I-deas data sharing import dialog box.
Valid values:

YES

NO

Default value:

YES

IDEAS_import_from_tdm The initial value of the generate visualization data selections

_options_default_gen_vis on the data sharing import options dialog box.
_data_priority
Valid values:

1
This is low priority.

2
This is medium priority.

3
This is high priority.

Default value:

IDEAS_ideastojt_import Specifies a different configuration file name for controlling

_translation_config_filename the ideastojt_imp_direct translation. By default,
ideastojt_imp_direct uses the same file as is specified in the
preference for ideastojt_direct
(IDEAS_ideastojt_translation_config_filename)
If you want to use a different file, you can copy this file and
make changes to the copy.
Default value:

IDEAS_ideastojt_translation_config_filename

2-82 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Engineering Translation Services Preferences

Preference Name Description

IDEAS_migration_translation The TSTK provider name and special ETS service name of the
_service_name translator to be used for I-deas to JT translation of migrated
I-deas data.

Note:
If this preference is not specified, requests for I-deas
to JT translations of migrated data are ignored.

Default value:

UGS.ideastojt_direct_imp

IDEAS_migrate_gen_vis Specifies the generate visualization data schedule priority

_data_priority for the I-deas migration operation.

Note:
If this preference is not specified, visualization data is
not generated during migration.

Valid values:

0
Do not generate visualization data.

1
Generate visualization data with scheduler priority low.

2
Generate visualization data with scheduler priority
medium.

3
Generate visualization data with scheduler priority
high.

Default value:

IDEAS_migrate_translate_tl Controls whether the ETS translation request is generated

_individually individually for each top level item or if it is processed as
one request for a set of top level items. This preference
applies to migration only.
Valid values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-83
© 2020 Siemens
 2. Preferences

Preference Name Description

TRUE

FALSE

Default value:

TRUE

IDEAS_migrate_translate _pre- By Default, migration submits translation requests only for

existing_tl newly created item versions, and skips a match case and
does not submit the translation request for an already
migrated top level item version.
Set this preference to TRUE to force an ETS translation
request even if the item was a match case. This preference
only applies to migration.
Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_cgm_translation The TSTK provider name and service name of the translator
_service_name to be used for I-deas to CGM translation of I-deas drawings.

Note:
If this preference is not specified, requests for I-deas
to CGM translations are ignored.

Default value:

UGS.ideastocgm_direct

IDEAS_cgm_translation The dataset type names of the I-deas datasets that can be
_dataset_type_name translated by the I-deas to CGM translator. If no dataset
types are specified, no dataset type validation is performed.
Additional named reference type validation can be
configured for the datasets specified by this preference
value.
Default value:

2-84 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Engineering Translation Services Preferences

Preference Name Description

IdeasDrawing

IDEAS_ideastocgm Specifies a different configuration file name for controlling

_translation_config _filename the ideastocgm_direct translation. By default,
ideastocgm_direct uses the same file as is specified in the
preference for ideastojt_direct
(IDEAS_ideastojt_translation_config_filename)
If you want to use a different file, you can copy this file and
make changes to the copy.
Default value:

IDEAS_ideastojt_translation_config _filename

IDEAS_NXRefile This preference is used to trigger an NX Refile during an I-

deas to JT translation. This causes an NX part or assembly
dataset to be created from an I-deas dataset.
This preference applies to all I-deas to JT translations using
ETS. NX and NX refile must be installed.
For more information about installing NX and NX refile, see
the NX documentation.
Valid values:

TRUE

FALSE

Default value:

FALSE

IDEAS_NXRefile_priority Specifies the schedule priority for creating NX datasets

during the I-deas to JT ETS process. NX and NX refile must
be installed.
For more information about installing NX and NX refile, see
the NX documentation.

Note:
If this preference is not specified, NX refile is not
performed during I-deas to JT translation through ETS.

Valid values:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-85
© 2020 Siemens
 2. Preferences

Preference Name Description

Do not perform NX refile.

1
Perform NX refile with scheduler priority low.

2
Perform NX refile with scheduler priority medium.

3
Perform NX refile with scheduler priority high.

Default value:

IDEAS_NXRefile_translation The TSTK provider name and service name of the translator
_service_name to be used for NX refile after an I-deas to JT translation.

Note:
If this preference is not specified, requests for NX
refile translations are ignored.

Default value:

UGS.nxrefile

IDEAS_translation_dataset The dataset type names of the I-deas datasets that can be
_type_names translated by the I-deas to JT translator. If no dataset types
are specified, no dataset type validation is performed.
Additional named reference type validation can be
configured for the datasets specified by this preference
value.
This value is used by the ideastojt_direct and
ideastojt_imp_direct translators.
Default value:

IdeasPart
IdeasAssembly
IdeasDrawing

UGSideastojt_IdeasAssembly The IdeasAssembly dataset named references necessary for

_ets_nr_types translation. All named reference types specified by this
preference must exist for a dataset of this type to be
translated. If no named reference types are specified, no
named reference type validation is performed.

2-86 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Engineering Translation Services Preferences

Preference Name Description

This value is used by the ideastojt_direct and

ideastojt_imp_direct translators.
Default value:

IdeasGuids
IdeasPrivateData
IdeasAssembly

UGSideastojt_IdeasDrawing The IdeasDrawing dataset named references necessary for

_ets_nr_types translation. All named reference types specified by this
preference must exist for a dataset of this type to be
translated. If no named reference types are specified, no
named reference type validation is performed.
This value is used by the ideastojt_direct and
ideastojt_imp_direct translators.
Default value:

IdeasGuids
IdeasPrivateData
IdeasAssembly

UGSideastojt_IdeasPart_ets _nr_types The IdeasPart dataset named references necessary for

translation. All named reference types specified by this
preference must exist for a dataset of this type to be
translated. If no named reference types are specified, no
named reference type validation is performed.
This value is used by the ideastojt_direct and
ideastojt_imp_direct translators.
Default value:

IdeasGuids
IdeasPrivateData
IdeasAssembly

IDEAS_ideastojt_translation Specifies a different configuration file name for controlling

_config_filename the ideastojt_direct translation. The value for the default file
name is ideastojt.config. This value is also used by the
ideastojt_direct translator, which is generally used for save
to Teamcenter and on-demand translations.
If you want to use a different file, you can copy this file and
make changes to the copy.
Default value:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 2-87
© 2020 Siemens
 2. Preferences

Preference Name Description

ideastojt.config

IDEAS_ideastojt_translation Specifies a different path to the configuration files. All

_config_path configuration files must be in the same directory.
Default value: <None>

ETS_available Indicates that translation services have been installed.

Valid values:

YES

NO

Default value:

YES

Disable Preferences When Running ETS

If you are using Teamcenter's Engineering Translation Services (ETS) as a replacement for in-line JT
translation at your site, the following options must be set as follows to prevent users from overriding the
system level settings:

• IDEAS_part_create_jt=FALSE

• IDEAS_part_create_jt.Disallow=TRUE

• IDEAS_assembly_create_jt=FALSE

• IDEAS_assembly_create_jt.Disallow=TRUE

2-88 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 3. Getting Started
Launching My Teamcenter and Integration for I-deas From I-deas ────── 3-1
Launching Integration for I-deas and I-deas From My Teamcenter ────── 3-2
Launching My Teamcenter ─────────────────────────────────── 3-2
Launching Integration for I-deas and I-deas ───────────────────────── 3-2
Launching Integration for I-deas and I-deas From Structure Manager ──── 3-3
Connection Issues ───────────────────────────────────── 3-3
Non-Integration for I-deas Users ──────────────────────────── 3-4
Understanding the My Teamcenter Interface ──────────────────── 3-4
My Teamcenter ─────────────────────────────────────── 3-4
My Teamcenter Tree Pane ─────────────────────────────────── 3-4
Summary Pane ────────────────────────────────────────── 3-4
Details Pane ─────────────────────────────────────────── 3-4
Viewer Pane ─────────────────────────────────────────── 3-4
Referencers Pane ──────────────────────────────────────── 3-5
Display Data Pane ──────────────────────────────────────── 3-5
Menu Bar ───────────────────────────────────────────── 3-5
Integration for I-deas Window ───────────────────────────── 3-6
Toolbar ────────────────────────────────────────────── 3-7
Understanding Teamcenter Objects, Revisions, and Versions ───────── 3-7
Items ──────────────────────────────────────────────── 3-8
Item Revisions ────────────────────────────────────────── 3-8
Datasets ────────────────────────────────────────────── 3-8
BOMView Revisions (BVR) ─────────────────────────────────── 3-9
Closing My Teamcenter and Exiting Teamcenter ───────────────── 3-9
Closing My Teamcenter ───────────────────────────────────── 3-9
Exiting Teamcenter Rich Client ──────────────────────────────── 3-9
Programmatic Access to Integration for I-deas ─────────────────── 3-9
Using Integration for I-deas Openess ──────────────────────────── 3-10
Running the Openness Sample Application ──────────────────────── 3-11
Openness Troubleshooting ────────────────────────────────── 3-12
IDS User Exits for Migration ───────────────────────────────── 3-13
Running Custom Applications Created in NX Manager I-deas 4.3 or Earlier ───── 3-13

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 3. Getting Started
This chapter describes how to start Integration for I-deas and provides information on the My
Teamcenter and Integration for I-deas interface.

You can launch My Teamcenter and Integration for I-deas from I-deas, or launch My Teamcenter
separately and then launch Integration for I-deas.

Because Integration for I-deas runs in the My Teamcenter environment, you need to know some key My
Teamcenter concepts and functionality.

Note:
You can run only one Integration for I-deas session per workstation.

Note:
To improve the performance of the Integration for I-deas checkout operation, the following file
types should have virus checking turned off: .asm, .jt, .mdf, .drw, .dwg, .asc, .fem, .prt.

Launching My Teamcenter and Integration for I-deas From I-deas

Perform the following steps to launch the Teamcenter Rich Client and the My Teamcenter application
from within I-deas:

1. From the I-deas icon panel, click the external data manager icon (also called the Teamcenter icon),
located next to the Manage Bins icon stack.
The system launches Teamcenter Rich Client with the default application and displays the login
dialog.

2. Log in to Rich Client.

• User ID
Enter the ID corresponding to the Teamcenter user profile you will use for this session.

• Password
Enter the password established for the user profile.

• Group
Enter the name of the group that you want to work in for this session. If you do not enter a
group name, you are logged in under your default group.

• Role

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-1
© 2020 Siemens
 3. Getting Started

Enter your role for this session.

• Database
Select the Teamcenter database in which to store your I-deas data.

3. Click Login.
The system launches the Teamcenter Getting Started application and Integration for I-deas
application, which is the active application.

4. In the Rich Client session, click the My Teamcenter application to launch it.

5. Log in if required.

Launching Integration for I-deas and I-deas From My Teamcenter

Launching My Teamcenter

1. Start the Teamcenter Rich Client session.

To access Integration for I-deas, the Rich Client session must be started from the IDNPortal.bat file
(Windows) or idn_start_portal (UNIX) file supplied with the Integration for I-deas installation. If
the session is started from the standard Portal.bat (Windows) or start_portal (UNIX) file,
Integration for I-deas is not available.

2. In the Rich Client session, click the My Teamcenter application to launch it.

Note:
You do not need to have My Teamcenter running to run Integration for I-deas. To do this, just
launch Integration for I-deas from your Teamcenter Rich Client session by clicking on the
Integration for I-deas application without launching My Teamcenter.

3. Log in if required.

Launching Integration for I-deas and I-deas

From the tool bar at the top of the My Teamcenter window, click the Open/Locate Integration for I-
deas button , choose Integration for I-deas from the I-deas menu, or click the Integration for I-
deas application.

This launches the I-deas Integration for I-deas window and establishes a connection between My
Teamcenter and I-deas. If I-deas is not already running, the system launches it with a default model file
and establishes the connection.

3-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Launching Integration for I-deas and I-deas From Structure Manager

Launching Integration for I-deas and I-deas From Structure

Manager
If the Integration for I-deas components are not running when you attempt to send an assembly from
Structure Manager to I-deas, click the Open/Locate Integration for I-deas button on the toolbar.

The system then attempts to establish a connection with I-deas. If an I-deas session is not already
running, one is launched with a default model file and the connection between My Teamcenter and I-
deas is established.

Connection Issues
Integration for I-deas establishes a connection between your Teamcenter and I-deas sessions.

• If you attempt an Integration for I-deas operation before a connection is made, you are prompted to
connect.

• Connection with I-deas remains until you exit My Teamcenter or Rich Client.

• When you switch between I-deas Design and Simulation or Manufacturing applications (any I-deas
application which brings I-deas down and up again), you need to log back into Teamcenter, if
Integration for I-deas is the only application running in Teamcenter. If you have other applications
running in Teamcenter, then you do not need to log back in.

• If you attempt to have the I-deas connection launch in the Drafting task, the connection can't be
made and will time out. Establish the connection such that the I-deas Master Modeler task is
launched.

• If you try to perform a solve with Model Solution with Integration for I-deas running, the solve will not
complete and could lock-up Teamcenter or Integration for I-deas. Performing a solve with Model
Solution is not a supported operation.

• If the Orbix daemon used by I-deas is shut down at any point, it must be restarted by the appropriate
I-deas administrative user.

• If you send a part to I-deas, then export the part as an I-deas archive file, a separate application is
launched and the connection to Teamcenter is broken. Re-establish connection by using the Rich
Client icon from the existing I-deas session.

• If you cannot connect Integration for I-deas and Rich Client by starting Integration for I-deas from Rich
Client, or by starting Rich Client from Integration for I-deas, start up both Rich Client and Integration
for I-deas individually. Then choose I-deas→Integration for I-deas in Rich Client to establish the
connection.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-3
© 2020 Siemens
 3. Getting Started

Non-Integration for I-deas Users

In normal Integration for I-deas operations, I-deas parts, assemblies, drawings, and FE models are placed
into Teamcenter volumes. Although non-Integration for I-deas users may be able to access these
volumes, they cannot perform common actions with I-deas objects because they are not running
Integration for I-deas.

Understanding the My Teamcenter Interface

My Teamcenter is an application within Teamcenter. With Integration for I-deas, you launch the
Integration for I-deas window by selecting the I-deas→Integration for I-deas menu option in the My
Teamcenter interface.

My Teamcenter
The My Teamcenter interface in Teamcenter provides the My Teamcenter tree pane and a pull-down
menu for selecting data panes to display information in the main window.

Note:
For additional information about My Teamcenter, see the Teamcenter Online Help.

My Teamcenter Tree Pane

The My Teamcenter tree pane lets you access information stored in the Teamcenter database. It displays
your Home folder, which is your personal workspace, as the root node in a tree structure that allows you
to organize information in a way that best suits your needs.

Summary Pane

The summary pane displays the attributes of the item, such as name, revision, and description. A non-
detailed view of the item is provided in the Preview window.

Details Pane

The Details pane displays the properties of a selected object in tabular format. When an item or item
revision is selected, the properties of the related objects are also displayed.

Viewer Pane

The Viewer pane displays data about an item or image files attached to the item. You can work with a
wide range of graphic and business file formats. For example, if you select a Microsoft Word file, the
viewer displays the contents. If you have the embedded viewer installed, you can also use the Viewer
pane to view 2D and 3D geometry within My Teamcenter.

3-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Referencers Pane

Referencers Pane

The Referencers pane displays where-used and where-referenced information about a selected object.

Display Data Pane

The Display Data pane becomes active after results are found during a search. The properties of the
objects found during the search can be viewed in the pane.

Menu Bar

The menu bar is located at the top of the window and contains the following menus:

• File
Contains options used to create, modify, and delete Teamcenter objects, close an application, .

• Edit
Contains options used to cut, copy, and paste object references and to set program options and
preferences.

• View
Enables you to view properties and access data about selected objects and to refresh the My
Teamcenter display.

• I-deas
Options let you transfer data between Teamcenter and I-deas, open the Integration for I-deas
window, create new revisions of an item, and purge old revisions of an item. The About Integration
option displays version information.

• Tools
Contains tools used to check objects in and out of the database, import and export items to remote
Teamcenter sites, access the Address List, and generate reports.

Note:
The Check-In/Out option on this menu is not intended for use with Integration for I-deas.

• Window
Enables you to control the display of toolbars and look and feel of your Teamcenter desktop.

• Help
Provides access to My Teamcenter online help and to the complete Teamcenter Online Help
collection.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-5
© 2020 Siemens
 3. Getting Started

Integration for I-deas Window

The Integration for I-deas window displays a tree corresponding to the active model file in your I-deas
session. A single root node represents the model file. Each bin and its corresponding parts, assemblies,
FE models, and drawings are displayed beneath the root node, along with icons indicating the item type
and status of each item (if it has been checked in to Teamcenter). If no status icons are displayed, the
object is new and has never been checked in to Teamcenter.

The menu bar at the top of the Integration for I-deas window contains all of the available menu options.
You can right-click in the window to get a popup menu that is context sensitive, such that it displays the
menu selections that pertain to the item selected. For example, the menu selections are different if a bin
is selected versus a part selected.

If multiple items are selected, the options available for each item are combined, which could render
some options invalid for some items. In that case, a dialog is displayed in succession for each item type
(for example, one for copy part and one for copy assembly), or an informational message is displayed
indicating items were skipped or the command is not applicable.

If one item is selected, all instances of that item that are displayed are also selected. When you expand
an item (clicking on the +), any instances of the item that are now displayed are also automatically
selected. When the item is collapsed, the instances are no longer selected since they are no longer
displayed.

Note:
Teamcenter Command Suppression is supported for the Integration for I-deas window. However,
for Command Suppression to take effect on the Integration for I-deas window, you have to exit
out of Teamcenter Rich Client and login again (this does not have to be done to suppress Rich
Client commands). Also, you can only suppress and not add commands to the Integration for I-
deas window.

Note:
Functionality available in the Integration for I-deas window cannot be performed on pruned parts
(except for Unprune).

Detailed usage of the menu selections and options in the Integration for I-deas window are described in
context in other sections of this manual.

Menu Bar

The menu bar is located at the top of the window and contains the following menus:

• File
Enables you to save and check in the part to Teamcenter. You can also remove the part from the list
after checkin or use Save As to save the part as a new revision of the item. The part must have been
changed to use Save As.

3-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Toolbar

• Edit
Contains options to update items, prune items, and find out-of-date items. You can also synchronize
the model file to ensure the status of an item in the model file matches the status in Teamcenter. This
menu also provides access to the dialog for the Integration for I-deas preferences.

• View
Enables you to sort items by part number or name, and view selected item types, such as parts,
assemblies, and drawings. You can expand an item (including bins) one level down, or use Expand
Below to open up all levels below the selected item.

Note:
When I-deas is running the Simulation application, the Integration for I-deas window doesn't list
drawings. To see drawings, run an application other than Simulation. When I-deas is running an
application other than Simulation, the Integration for I-deas window does not list FEMs. To see
FEMs, run the Simulation application.

• Show Only Out Of Date

Enables you to display only those items that are out-of-date. This option works with your view
selections. For example, if you select parts and drawings for viewing in the View menu, but not
assemblies, this option displays only out-of-date parts and drawings, but not assemblies.

• Manage Bins
Enables you to perform the same manage bin functions as in I-deas including create bins, get, put,
copy, move, rename, and delete.

• Help
Displays version information about Integration for I-deas.

Toolbar

A toolbar that contains specified menu commands is provided below the menu bar in the Integration for
I-deas window. The toolbar is customizable with the commands from the Integration for I-deas window
menu and contains a default toolbar that contains the basic commands.

The toolbar is in synchronization with the Menu Bar and selected items in the Integration for I-deas
window such that menu selections and the corresponding buttons on the toolbar are disabled
depending on the selections. For example, if a selected item is on the workbench, the button/icon for
the Get From Bin command is disabled on the toolbar and the Get From Bin menu selection is also
disabled .

Understanding Teamcenter Objects, Revisions, and Versions

This section describes the Teamcenter objects used in Integration for I-deas and explains the concepts of
Teamcenter item revisions and dataset versions.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-7
© 2020 Siemens
 3. Getting Started

Items

Items are fundamental objects used to manage information in Teamcenter and generally represent a
product, part, or component. Items can contain references to other workspace objects, including other
items and folders.

Items are represented in My Teamcenter using the standard Teamcenter item icon.

Item Revisions

Item revisions are used to manage changes to items. Each Teamcenter item has at least one associated
item revision object. Item revisions are identified by item ID, item name, and revision letter. The revision
letter increments when you create a new item revision by performing a Revise or Save As action in My
Teamcenter.

Item revisions are represented in the My Teamcenter interface using the standard
Teamcenter item revision icon.

Datasets

Datasets reside within Item Revisions. They are used by Teamcenter to manage data files created by
other software applications. Dataset types are created to support Integration for I-deas. Each dataset
type has an associated icon that is displayed in the My Teamcenter application, as follows:

Represents an I-deas part dataset.

Represents an I-deas assembly dataset.

Represents an I-deas drawing dataset.

Represents an I-deas FE model dataset.

Represents an I-deas drawing set dataset.

Represents a DirectModel data that references the JT file used to visualize parts in the My
Teamcenter Viewer.

Version numbers are associated with dataset objects. Each time a dataset is checked out of My
Teamcenter, the version number is increased by one. If the checkout is canceled, the dataset reverts to
the previous version.

The number of dataset versions retained per dataset in the Teamcenter database is controlled by the
AE_dataset_default_keep_limit preference. When the version limit is exceeded, the earliest version of

3-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 BOMView Revisions (BVR)

the dataset is purged from the database to make room for the latest version. For more information, see
System Administration online help in the Teamcenter Online Help Collection.

Note:
Dataset versions used by other datasets in Teamcenter are not deleted by the automatic purge.

BOMView Revisions (BVR)

BOMView Revision objects store the single-level assembly structure of an Item Revision. BOMView
Revisions are only meaningful in the context of the item revisions in which they are created. Access
privileges to BOMView Revisions can be controlled independent of other data.

BOM views are represented in the My Teamcenter interface using the standard
Teamcenter BOM view icon.

Closing My Teamcenter and Exiting Teamcenter

If you are running My Teamcenter from within I-deas, you should close My Teamcenter before you exit I-
deas.

Closing My Teamcenter

If you are running My Teamcenter from within I-deas, you can close the My Teamcenter window by
choosing the File→Close option.

Exiting Teamcenter Rich Client

Choose File→Exit or click the Exit button on the toolbar to end your Teamcenter session.

Note:
You can close the Integration for I-deas window. If this is the last open application, the Teamcenter
session is terminated.

Programmatic Access to Integration for I-deas

Integration for I-deas provides openness for custom applications. APIs are provided to support sending
modeling data from Teamcenter to I-deas and saving data to Teamcenter.

The client side application is written as a plug-in to Teamcenter. A sample openness application is
included in the installation kit. The following files are placed in the TC_ROOT\portal\tcii\Openness
\samplePlugin directory during installation of Integration for I-deas:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-9
© 2020 Siemens
 3. Getting Started

• build_openness.xml
This is the ANT build file to build the sample plug-in.

Note:
ANT is an Apache open source, Java-based build tool. ANT 1.6.5 or higher is required. For
additional information, see http://ant.apache.org.

• BuildOpenness.bat
This file is the script for driving the ANT build file to build the sample plug-in.

• TcIIOpenness.bat
This file is the script for running the sample openness application (Microsoft Windows only).

• mit.jar, mtiidsNX13.jar, openideasNX13.jar

Jar files that are present in the plug-in, but are required to build and so are also shipped.

• config.ini
This is a sample configuration file required to run the standalone openness application. This
references the sample plug-in com.teamcenter.rac.TcIIOpenness.

• com.teamcenter.rac.tciiOpenness
This is the package that contains the source files.

• TcIIopenness.java
This is the main source file.

• TcIIOpennessApplicationContext.java
This is a source file.

• Activator.java
This is a source file.

The following file is included in the installation kit but is not installed automatically with the Integration
for I-deas installation. You must extract from the install kit zip file to a directory.

• javadoc.zip
This is the javadoc needed for Integration for I-deas openness.

Using Integration for I-deas Openess

The openness sample application is a good starting point for learning the openness API. It is
recommended that you first look at the TCIIOpenness.java class before attempting to create any of your
own openness applications.

3-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Running the Openness Sample Application

Note:
The following instructions for using Integration for I-deas openness is applicable to Windows
platforms only.

Once you begin looking at the TCIIOpenness.java sample code, access to the openness API javadocs will
be helpful. These docs provide detailed information about each method in the openness API. To view the
openness API javadoc, perform the following steps:

1. Create a directory to store the information.

2. Under this directory, create the subdirectory TCII.

3. Use a zip utility to extract the contents of javadoc.zip into the TCII subdirectory. Javadoc.zip is in the
kit directory, \Documents\en.

4. To begin viewing the openness API javadoc, open \TCII\overview-summary.html in a web browser.
From here you can click on any of the listed packages to see more detailed information. The
following main classes are located in the package com.teamcenter.rac.ideasnavigator:

• OINTransferController

• NXMIOpennessUtil

Running the Openness Sample Application

To run the sample openness application, TCIIOpenness.bat, perform the following steps:

1. Prior to running the sample openness application, ensure you have ANT 1.6.5 and JDK 1.5.0.11
installed.

2. Open a Windows command prompt window.

3. Set the environment variable ANT_HOME to point to the location of ANT.

4. Set the environment variable JAVA_HOME to point to the directory that contains the installation of
Java JDK 1.5.0.11.
For example, SET JAVA_HOME=C:\j2sdk1.5.0_11

5. Run BuildOpenness.bat in the command prompt.

6. As an alternative to steps 3, 4 and 5 above, you can set the value of the environment variables in
the first line of the BuildOpenness.bat file and just double-click it from Windows Explorer.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-11
© 2020 Siemens
 3. Getting Started

7. After the plug-ins are built, they are placed in the build directory. Copy them to the %PORTAL%/
plugins/ directory.

8. Run the openness application using TCIIOpenness.bat. You must also include your user name,
password, and group, for example:

TCIIOpenness.bat —u <username> —p <password> —g <group> —

checkout <itemID>

9. Launch the sample openness application, TCIIOpenness.bat, using other options. Ensure you
include your user name, password, and group. The options are listed in the following table:

Option Definition

-save <part name> Saves the specified item, but leaves it checked out.

-checkin <part name> Checks in the specified item, but leaves it referenced.

-checkinremove <part name> Checks in the specified item and removes it from the model
file.

-checkout <item ID> Checks out the specified item into the Main bin. All folders are
searched until an item with the specified name is found.

-reference <item ID> Transfers (for reference) the specified item into the Main bin.
All folders are searched until an item with the specified name
is found.

Openness Troubleshooting

If you have problems running the openness application, verify or perform the following:

1. The directory specified by the value java.io.tmpdir in the sample openness batch file contains the
files tpn.tmp and ns_ior.txt.

2. The tpn.tmp file contains the following entries:

• Process ID (TPN)

• IS_Server_IOR

3. Ensure the tpn.tmp file is written out. You can write out the file by invoking the script
make_ior.bat with the –e option in the start_ideas script.

4. The sample openness batch file should invoke make_ns_ior.bat, which writes out the nx_ior_txt
file. The ns_ior.txt file should contains the entry:

• NameServerIOR

3-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 IDS User Exits for Migration

IDS User Exits for Migration

User exits are provided for I-deas TDM to Teamcenter migration that allow you to customize the
migration. The user exits are built into a customization file that can be used by the migration
application. For information on using IDS User Exits, see the Integration for I-deas Data Migration
Reference Guide, User Customization Methods appendix.

Running Custom Applications Created in NX Manager I-deas 4.3 or Earlier

Openness functionality checks for the following preferences starting with Integration for I-deas 5.0.
Since the openness functionality now checks for these preferences, custom applications created for NX
Manager I-deas 4.3 or earlier may not work as they previously did. To get the 4.3 and earlier behavior,
set the preferences as follows:

• IDEAS_keep_drawing_with_related_model=ONLY_IF_SAME_ID

• IDEAS_deep_dwg_of_mult_parts_with_related_model=ONLY_IF_SAME_ID

• IDEAS_keep_dwgset_with_related_drawing=ONLY_IF_SAME_ID

• IDEAS_keep_fem_with_related_model=ONLY_IF_SAME_ID

• IDEAS_one_version_per_revision=FALSE

• IDEAS_one_version_per_revision_ps_only=FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 3-13
© 2020 Siemens
 3. Getting Started

3-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 4. Using Integration for I-deas: Working
With Modeling Data
One Version Per Revision In Teamcenter ─────────────────────── 4-1
Activating One Version Per Revision ───────────────────────────── 4-1
Using One Version Per Revision ──────────────────────────────── 4-2
Mapping Drawings For One Version Per Revision ───────────────────── 4-3
Mapping a Drawing of Multiple Models ─────────────────────────── 4-3
Mapping Standalone Drawings ──────────────────────────────── 4-4
Mapping FEMs For One Version Per Revision ──────────────────────── 4-5
Changing the Mapping of Drawings and FEMS ─────────────────────── 4-5
Warnings for Referenced but Modified condition ───────────────── 4-6
Change Status ────────────────────────────────────────── 4-6
Add Parent ──────────────────────────────────────────── 4-6
Send to I-deas ────────────────────────────────────────── 4-6
Update to Latest ───────────────────────────────────────── 4-7
Save to Teamcenter ─────────────────────────────────────── 4-7
JT Files ──────────────────────────────────────────── 4-7
Creating JT Files ───────────────────────────────────────── 4-7
Viewing Assemblies ────────────────────────────────────── 4-10
Adding JT Component to an Assembly ─────────────────────────── 4-10
Location of Saved Harnesses ───────────────────────────────── 4-10
JT File Creation Errors ───────────────────────────────────── 4-11
GUID Considerations When Creating an I-deas Dataset ───────────── 4-11
I-deas GUIDs ────────────────────────────────────────── 4-11
Issues With Datasets and I-deas GUIDs ─────────────────────────── 4-12
Methods and Issues When Working With Modeling Data ──────────── 4-13
Different dataset types in Item Revisions ───────────────────────── 4-14
Support for Teamcenter 128 character limit ──────────────────── 4-15
Item ID ────────────────────────────────────────────── 4-16
Item Name ─────────────────────────────────────────── 4-16
Revision ID ─────────────────────────────────────────── 4-16
Teamcenter 128 character limit disabled ───────────────────────── 4-17
Customizing the Toolbar ──────────────────────────────── 4-17
Filtering the Display in the Integration for I-deas Window ─────────── 4-18
Advanced Filtering ─────────────────────────────────────── 4-18
Save Data: Methods ─────────────────────────────────── 4-19
Integration for I-deas Save Menu Options ───────────────────────── 4-19
Saving Large Assemblies in Teamcenter ────────────────────────── 4-20
Saving Drawing Sets ────────────────────────────────────── 4-21
Saving ACF Parts ──────────────────────────────────────── 4-21
Saving Assemblies With Precise BOM ──────────────────────────── 4-21
Saving New or Updated Modeling Items to Teamcenter ──────────── 4-22
Saving to Teamcenter Dialog Box ────────────────────────────── 4-22
Saving Checked-Out Modeling Items in Teamcenter ────────────── 4-27
Clean Database of Items On Failed Checkin ──────────────────── 4-28

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
 Creating CGM Datasets for Drawings ──────────────────────── 4-28
Creating New Item Revisions ───────────────────────────── 4-29
Perform Revise On Any Item Revision ─────────────────────────── 4-30
Purging Item Revisions ───────────────────────────────── 4-31
Creating I-deas Datasets ──────────────────────────────── 4-31
Deleting I-deas Modeling Data Using Teamcenter ──────────────── 4-32
Deleting I-deas Modeling Data Using Integration for I-deas ────────── 4-33
Renaming/Renumbering Items ──────────────────────────── 4-34
Derived I-deas Parts ────────────────────────────────────── 4-35
Moving Items ─────────────────────────────────────── 4-35
Copying Items ─────────────────────────────────────── 4-35
Creating Bins ─────────────────────────────────────── 4-36
Bin Item on Workbench ──────────────────────────────────── 4-37
Remote Checkout ───────────────────────────────────── 4-37
Compressing I-deas CAD Files ───────────────────────────── 4-37
Improving Performance ───────────────────────────────── 4-38
Apply a Status and Create a New Revision In One Step ───────────── 4-39
Attribute Mapping ──────────────────────────────────── 4-41
Mapping I-deas Part Number Attributes ────────────────────── 4-41
Mapping I-deas User Attributes to Teamcenter Attributes ─────────── 4-42
Defining the Attribute Type ───────────────────────────────── 4-43
Special Attributes ─────────────────────────────────────── 4-44
Master Variable for Part Number and User Attributes ────────────── 4-44
Mapping Attributes with BMNR Defined For Item Name ──────────── 4-45
Attribute mapping performance ─────────────────────────── 4-46
Attribute Customization User Exits ────────────────────────── 4-46
Change Ownership and Right To Modify For Datasets ────────────── 4-47
I-deas Right to Modify Utility ───────────────────────────────── 4-47
Working in Multi-Site Collaboration ───────────────────────── 4-49
Enabling Checkin/Checkout ───────────────────────────────── 4-49
Multi-Site Relationship Types ──────────────────────────────── 4-49
Remote Import Relationship Types ───────────────────────────── 4-50
Remote Import Revisions and Versions ─────────────────────────── 4-50
Preferences For Automatically Selecting Relationship Types ────────────── 4-51

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
 4. Using Integration for I-deas: Working
With Modeling Data
This chapter describes how to use Integration for I-deas with I-deas modeling data in the Teamcenter
database.

One Version Per Revision In Teamcenter

The data management paradigm of one version per revision is the preferred method (and the default
method) for storing and managing data in Teamcenter. This method avoids the Reference but Modified
condition in I-deas. This method also provides a smoother transition when the next step of the migration
process is performed, migrating I-deas items to NX, as NX doesn't support previous versions of
components for an assembly in an Item Revision; only the latest version of components is supported.

This method prevents the Referenced but Modified condition where an assembly references a
component that has been modified. When you have an assembly that references a component and you
send the component to I-deas, modify it, and save it back to Teamcenter as a new version in the same
Item Revision, the assembly now references a previous version in the Item Revision. When you send the
assembly to I-deas for reference (the assembly is now Referenced but Modified), the assembly is out-of-
date (the assembly is sent to I-deas referencing the latest version of the Item Revision). You can
checkout and update the assembly to the latest version of that component, but that may not be what
you want to do or have permissions to do. The assembly may be correct by referencing the previous
version of the component. Going to the one version per revision paradigm eliminates this problem.
Instead of sending the latest version to I-deas, the as-saved assembly hierarchy (the hierarchy has
specific versions of subassemblies and parts) is sent to I-deas.

Activating One Version Per Revision

To activate the one version per revision methodology, the following conditions must be in place. Each
condition is enabled by an applicable preference in the Teamcenter preferences.

Note:
These preferences are set to the appropriate values by default to enable one version per revision
functionality.

Note:
For additional information on these preferences, see chapter , Preferences.

• Save one version per revision

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-1
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

IDEAS_one_version_per_revision=TRUE
This preference specifies that I-deas item versions are mapped to Teamcenter Item Revisions.

Warning:
It is strongly recommended that this value is never set to FALSE. I-deas assembly modeling
is a precise only assembly modeler. If set to FALSE, multiple versions are saved within an
Item Revision and Integration for I-deas won't be able to send the assembly as-saved to I-
deas. This will cause assemblies that are referenced to the model file to be modified from
the as-saved condition, which will cause a RefMod error and prevent that assembly from
being saved back to Teamcenter.
• Don't replace revisions

IDEAS_send_option_replace_revisions=FALSE
This preference replaces existing revisions in the model file during a send to I-deas operation.
• Save precise assemblies

IDEAS_bvr_create_precise=TRUE
This preference creates a precise BOMView revision at assembly checkin.

Using One Version Per Revision

The one version per revision functionality is somewhat transparent. You don't really realize that it's been
implemented or guiding you to use the methodology.

When you modify and save a part or assembly, the new version is automatically placed into a new Item
Revision. The revision numbering is automatically assigned to the next higher ID in accordance with the
business rules for checkin. This applies to the save types Save, Save & Checkin, and Save, Checkin, &
Remove. When you perform a Save-As, the assigned revision ID is displayed in the Save-As dialog
allowing you to change it. However, if you change it to one that already exists for that item, you'll get an
error when you execute the save.

When you save a drawing or FEM, it's automatically saved to the Item Revision that contains its related
dataset. For example, a FEM is saved to its related part Item Revision. This applies to the save types
Save, Save & Checkin, Save As and Save, Checkin, & Remove. When you perform a Save-As, a
message is displayed stating that the dataset is being placed into the related Item Revision. When you
save a drawing or FEM that has previously been saved separately from its related dataset or if it has no
related dataset, it will continue to be saved separately. Drawings and FEMs can have multiple versions in
the same Item Revision.

The Integration for I-deas window shows the out-of-date items for revision and version. If you update
the assembly in the model file to eliminate the out-of-date items, you will be referencing the latest
versions of those items, thereby changing the assembly and negating the benefits of one version per
revision.

4-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Mapping Drawings For One Version Per Revision

Note:
If you do update the assembly and want to get it back to its previous state, delete the assembly in
the Integration for I-deas window and resend it to I-deas

Mapping Drawings For One Version Per Revision

The following is a preference (in the Teamcenter preferences) for controlling how drawings are mapped
when using one version per revision.

• IDEAS_keep_drawing_with_related_model
This preference specifies how new I-deas drawings are mapped to Teamcenter Item Revisions. The
drawing can be newly created in I-deas and saved to Teamcenter or can be imported through data
sharing. Once a drawing has been placed according to this preference setting, the following versions
of the drawing follow the same placement.

• NEVER – This is the default. Each version of a drawing always maps to its own separate Item
Revision; they are not placed in the same Item Revision as the model.

Note:
This functionality is used automatically by default when the
IDEAS_one_version_per_revision preference is set.

• ONLY_IF_SAME_ID – The drawing is mapped to the related model if the drawing has the same
ItemID (I-deas part number) as the model. The drawing is placed in the same Item Revision as the
model. This applies to multiple versions of a drawing as long as the versions have the same ItemID
as the model. If the drawing ItemID is different than the related model, it's mapped to its own
unique Item Revision.

• ALWAYS – All versions of a drawing are mapped to the related model regardless of the ItemID of
the drawing. All of the version are placed in the same Item Revision as the model.

Mapping a Drawing of Multiple Models

With the data management paradigm of one version per revision, a drawing is mapped to its own Item
Revision. If a drawing is related to multiple models, it's also mapped to its own separate Item Revision,
by default. This allows the drawing and many related models to be revised independently of each other.
However, this functionality can be overridden with the following preference (in the Teamcenter
preferences):

• IDEAS_keep_dwg_of_mult_parts_with_related_model

• NEVER – This is the default. A drawing for multiple parts is mapped to its own separate Item
Revision.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-3
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• ONLY_IF_SAME_ID – If you have a drawing of multiple parts, the drawing continues to be mapped
to the same Item Revision as the part it was related to when first migrated.
For example, you have a drawing related to a single part and it's mapped to the same Item Revision
as the part (part A). Then the drawing is modified to contain many parts (parts A, B, C, and D). The
drawing is still mapped to the Item Revision for part A, not to a separate Item Revision.

Mapping Standalone Drawings

Standalone drawings are drawings that do not have associativity to a specific part or assembly and can
be mapped with the following option:

• IDEAS_keep_standalone_dwg_with_exisitng_item

• ONLY_IF_SAME_ID
The standalone drawing is saved in the Item Revision of any dataset if the drawing has the same
ItemID as the dataset. If the standalone drawing has a different ItemID than the dataset, it is placed
in its own unique Item.

• NEVER
This is the default. Standalone drawings are not saved into an Item if the Item already contains any
other I-deas dataset, including other standalone drawings. Also, any other I-deas dataset cannot be
saved to an Item that contains a standalone drawing.
Two or more new standalone drawings (not part of a drawing set) cannot be assigned the same
ItemID because they cannot be saved to the same Item.
If a standalone drawing is saved with any other I-deas dataset type (such as a part), they cannot be
assigned the same ItemID because they cannot be saved together in the same Item.

Note:
When you click the OK button in the Save dialog box, an error message dialog is displayed
and the Save dialog box is again displayed with the ItemID values set to blank for those items
that need to have different ItemIDs.

In addition, the following exclusions apply:

• The preference IDEAS_keep_dwgset_with_related_drawing overrides

IDEAS_keep_standalone_dwg_with_exisitng_item.

• If a part/assembly is already saved with a standalone drawing and a drawing of the existing part/
assembly is created and the preference IDEAS_keep_drawing_with_related_model is set to either
ALWAYS or ONLY_IF_SAME_ID, the related drawing is allowed to be saved with the part/assembly.
This allows legacy items to be saved as they were previously.

Note:
This also applies to FEMs and the preference IDEAS_keep_fem_with_related_model.

4-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Mapping FEMs For One Version Per Revision

Mapping FEMs For One Version Per Revision

The mapping of FEMs is handled the same as drawings as described in the above section Mapping
Drawings For One Version Per Revision, except the preference is
IDEAS_keep_fem_with_related_model.

Changing the Mapping of Drawings and FEMS

The following is an additional preference (in the Teamcenter preferences) for controlling how drawings
and FEMs are mapped:

IDEAS_one_version_per_revision_ps_only

This preference determines whether drawings and FEMs are mapped to separate Teamcenter Item
Revisions if one version per revision functionality is enabled. This preference works in conjunction with
the preference IDEAS_one_version_per_revision.

When the preference IDEAS_one_version_per_revision is set to TRUE, one version per revision
functionality is enabled. If you modify an I-deas dataset (part, assembly, drawing, FEM), the new version
of the dataset is saved to its own unique, newly created Item Revision.

If you also set IDEAS_one_version_per_revision_ps_only to TRUE, new versions of drawings and FEMs
are not saved to a new Item Revision; they are saved to the Item Revision that they came from. New
versions of parts and assemblies are still saved to a new Item Revision in accordance with one version
per revision functionality. The addition of the preference IDEAS_one_version_per_revision_ps_only
negates one version per revision functionality for drawings and FEMs.

Note:
This preference is also applicable for migration and import.

This preference interacts with the drawing and FEM mapping preferences
IDEAS_keep_drawing_with_related_model, IDEAS_keep_FEM_with_related_model, and
IDEAS_keep_dwg_of_mult_parts_with_related_model. If a drawing or FEM is not mapped to its
related model Item based on the settings of those preferences, then the preference
IDEAS_one_version_per_revision_ps_only determines how they're mapped. When set to TRUE, it
maps them to the Item Revision that they came from.

Valid values:

TRUE
FALSE

Default value:

FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-5
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Warnings for Referenced but Modified condition

The referenced but modified condition exists when an assembly references a component that has been
modified. When you make changes to that assembly, you may not be able to save work that has been
done. Warning messages are provided to inform you of potential problems when the following
situations occur:

Note:
This functionality is available with I-deas 12m4.

Change Status

• The status of a higher level item is changed to checkout or new when a lower level item of a
referenced assembly is already checked out.

• The status of a higher level item is changed to checkout or new when a lower level item in a
referenced subassembly is already changed to new.

• The status of a lower level item is changed to checkout or new when a higher level item above a
referenced subassembly is already checked out.

• The status of a lower level item is changed to checkout or new when a higher level item above a
referenced subassembly is new.

• The status of an intermediate assembly is changed to reference when both a higher level item and a
lower level item are already checked out.

Add Parent

• A subassembly is added to a new assembly when the lower level items of the subassembly have been
updated.
When all items in a subassembly are referenced, the lower level items can be updated to new
revisions. Once the lower level items are updated, if the higher level items are added to a new
assembly, a warning is displayed.

Send to I-deas

• A higher level item is sent to I-deas after a lower level item that is already in the model file is
modified.

• A higher level item is sent to I-deas when a lower level assembly is referenced and an item in the
referenced assembly is checked out and modified.

4-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Update to Latest

• A higher level item is sent to I-deas when a lower level assembly is referenced and an item within the
referenced assembly is checked out.

• A lower level item is sent to I-deas for checkout after a new higher level item has been created in the
model file.

• A referenced item is between two checked out items during a send to I-deas operation.

• When the revision rule Latest by Creation date is used and the intermediate assemblies are not or
cannot be checked out.

• When an item below a referenced assembly has been updated to a new revision and a higher level
item is sent to I-deas.

Update to Latest

• When a higher level item is updated after a referenced item below a referenced subassembly is
updated to a later revision.

Save to Teamcenter

• When an assembly and part have new revisions and both are selected for update simultaneously.

Note:
In this case, do not select multiple items at different levels of the hierarchy for simultaneous
update, instead update them one at a time.

JT Files
A JT file is a file type (filename.jt) that allows you to view the part geometry in Teamcenter Visualization.
You can also view the JT file with Teamcenter Visualization software or any other software that can read
JT files.

Creating JT Files

When saving parts, I-deas generates a .vca file or .idi file (depending on which preference you enable)
in addition to the part file . The .vca file or .idi file is then converted to a JT file and associated with a
DirectModel dataset, which is attached to the same item revision object in Teamcenter as the part. JT
file creation can take a long time depending upon the complexity of the parts, therefore it's
recommended that you use Engineering Translation Services (ETS) to create JT files. Refer to the
Teamcenter online help for information on using ETS.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-7
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Note:
The following settings apply to interactive check in using I-deas and Integration for I-deas. These
are not applicable for Teamcenter ETS translation.

The creation of JT files is controlled by I-deas and Integration for I-deas preferences. I-deas preferences
determine whether VCA or IDI files are created; Integration for I-deas preferences control whether the
files are converted to JT files.

The .vca file generated contains a standard set of options and cannot be customized. You can customize
generation of .idi files in I-deas.

To enable .vca or .idi file creation, set the following preferences:

Note:
If all preferences are set to off (0), performance during a save operation is improved.

To create an IDI file, set the I-deas preferences (set by default):

• Team.AssociatedFileGenerateParts: 1

• Team.AssociatedFileGenerateAssemblies: 1

• Team.AssociatedFileEai: 0
Team.AssociatedFileIdi:1

Note:
If both of these preferences are set to 1, Team.AssociatedFileIdi takes precedence and IDI files
are created.

To create a VCA file, change the I-deas preferences :

• Team.AssociatedFileEai: 1

• Team.AssociatedFileIdi:0

• Change includeXT=TRUE to includeXT=FALSE in the following tess config files located at

PORTAL_DIR\plugins\com.teamcenter.rac.tcii_config_<revision no>:

tessMS.config.HIGH_RES

tessMS.config.LOW_RES

4-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Creating JT Files

tessMSassem.config.HIGH_RES

tessMSassem.LOW_RES

tessMSharness.config.HIGH_RES

tessMSharness.config.LOW_RES

Set the Integration for I-deas preferences:

• IDEAS_part_create_jt = TRUE

• IDEAS_assembly_create_jt = TRUE

Note:
In addition, the following files must be present to enable creation of JT files:

• eaicatojt.exe in the directory %SDRC_INSTL%\gif\

• The six tessellation configuration files shipped with Integration for I-deas are installed in the
Teamcenter Rich Client directory. These are installed automatically when Integration for I-deas
is installed.

During creation of JT files, by default:

• JT files created contain XT B-Reps for parts

• Motion files for assemblies are included, if applicable (AssemblyViewInfo dataset with .vfz named
reference)

• JT files are created for harness bundles

• PMI is not included

The contents of the IDI file is controlled by the I-deas site level file export_param_idip.ipf located at
directory %SDRC_INSTL%\ideas. You can edit this file to change the results of IDI creation and hence the
resulting JT file creation. You can also override the site level settings in this file by placing an edited
version of this file in the directory where I-deas is started.

If you are using Teamcenter's Engineering Translation Services (ETS) as a replacement for in-line JT
translation at your site, the following options must also be set to prevent users from overriding the
system level settings:

• IDEAS_part_create_jt=FALSE

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-9
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• IDEAS_assembly_create_jt=FALSE

Viewing Assemblies

A JT file is created when models are saved from I-deas to Teamcenter (if you have set the preference to
create a JT file). They can be viewed using the My Teamcenter Viewer.

The JT files associated with assemblies only contain PMI information. No geometry is contained within
the assembly JT file. If you want to view the assembly structure in Teamcenter Rich Client, use the
viewer within Structure Manager. The assembly configuration displayed in Structure Manager is the last
saved configuration in Teamcenter.

Viewing I-deas Assembly PMI in an Embedded Viewer

Assembly PMI (Product Manufacturing Information) can be viewed in Structure Manager. To enable this,
the JT assembly file for each top-level assembly is placed into the assembly's direct model dataset.

Adding JT Component to an Assembly

When adding a JT component to an I-deas assembly, the component must already exist in Teamcenter.
You cannot add a JT component that is imported directly into I-deas. JT data must first be imported into
Teamcenter, then added to the assembly.

Location of Saved Harnesses

When saving to Teamcenter, a JT file is created for each wire harness referenced by the assembly. This
following preference determines where the harness is located:

• IDEAS_harness_translator_hn_option

• FALSE
The JT file created for the wire harness is attached to the context assembly containing the harness.
This is the default.

• TRUE
The JT file created for the wire harness is attached to the DirectModel dataset that represents the
harness.

Note:
The harness display is more accurate if this value is used.

4-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 JT File Creation Errors

Note:
This preference is applicable only for I-deas 12 m4 or higher. If this is set to TRUE on an
earlier version, JT translation failure could result.

JT File Creation Errors

All errors that occur during JT file conversion process at checkin are logged and can be accessed from an
error dialog displayed to the user. When the user clicks the More button on the dialog window, the list
of errors displays.

The errors are also saved to a file with the following naming convention:

JtConversionError_hostid_userid__MMM_DD_YYYatHH_MM.log

For example:

JtConversionError_ccgnw444_infodba_July_05_2003at13_31.log

The file is saved to a location indicated by the JTErrorLogLocation variable, specified as a Java
command line qualifier in the Rich Client start script. If JTErrorLogLocation is not specified, the file is
saved to a location indicated by the java.io.tmpdir variable, a Java command line qualifier in the Rich
Client start script (IDNPortal.bat on Windows and idn_start_portal on UNIX).

GUID Considerations When Creating an I-deas Dataset

There are several methods that can be used with Teamcenter and Integration for I-deas to create I-deas
items, however some of the methods can break the I-deas data model. Performing the correct procedure
when copying items preserves the data model.

I-deas GUIDs

All I-deas items are identified by a globally unique identifier (GUID), which is used by I-deas in the TDM.
The Integration for I-deas data model is driven by I-deas TDM and those GUIDs. The GUID rules are:

• Every I-deas item version has one item GUID and one version GUID.

• Every version GUID has one unique item version.

• The same item GUID cannot be assigned to items with different part numbers. Each item (part
number) has a unique item GUID.

• The same version GUID cannot be assigned to different item versions of the same item. Each item
version has a unique version GUID.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-11
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• You cannot checkout for modify an item twice at the same time. This prevents forking of an item
series where the item is taking two modification paths.

Warning:
Do not turn on the Teamcenter Item Revision sequencing functionality. The sequence number
should be 1 for all Item Revisions. If higher sequence numbers are present, duplicate I-deas GUIDs
are created during certain operations.
During installation of Integration for I-deas, the Teamcenter Item Revision sequencing
functionality is turned off. To ensure this is turned off, see the Teamcenter preference
TCCheckoutReserveOnly.

Issues With Datasets and I-deas GUIDs

Based on the GUID rules that exist for I-deas items, the following are operations that can be performed
but should not be performed as they can cause problems with I-deas data.

4-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Methods and Issues When Working With Modeling Data

• My Teamcenter Revise
The Integration for I-deas revise command (I-deas→Revise) should be used for any item revisions
that contain I-deas data. The My Teamcenter revise command (File→Revise) should not be used on
any revisions that contain I-deas data.
The Integration for I-deas revise command operates just like My Teamcenter Revise for non-I-deas
datasets but performs additional functions for I-deas datasets to preserve the I-deas data model. It
makes a new copy of the I-deas dataset, increments the version number by one, and updates the CPD,
GUIDs, and reference objects.
If you use the My Teamcenter revise, the I-deas item series under the item will contain more than one
dataset of the same version number and version GUID.

• My Teamcenter Baseline
The My Teamcenter baseline command (Tools→Baseline) uses the My Teamcenter revise
functionality for part of its operation so the same problems can occur as with the My Teamcenter
revise command described above.

• Copy I-deas datasets between Items or Item Revisions

Copying I-deas datasets to another Item or Item Revision copies everything for the dataset including
version number and GUID. This forks the items series and allows parallel development of the same
item.

• Create a new I-deas dataset and copy I-deas references to it.

You can create an empty I-deas dataset in Teamcenter and copy files to the dataset as named
references. However, you can only add two named references to the dataset, CPD and bulk data file.
You can't add other required named references such as IdeasGUIDs, IdeasAssemblyData, and
IdeasDrawingReferences. If the other named references are not attached, the I-deas dataset is
incomplete and you will encounter problems/errors when working with the dataset.
This method should never be used as it can corrupt the dataset and cause other problems if it is
referenced by another item, such as an assembly or drawing.

Methods and Issues When Working With Modeling Data

• Change the name of the Item Revision Master and the dataset at the same time.
When you change the name of the Item Revision Master and the dataset at the same time a new
dataset version is automatically created. When you select both the Item Revision Master and the
dataset and choose Properties, the Common modifiable properties dialog box is displayed which
allows you to change the name for both. When you enter a new name and click OK, a new dataset
version in that Item Revision is created with the new name. This will cause problems when you
attempt to import or export this item to a TDM.
If you select the Item Revision Master and the dataset separately and change the name, the name is
changed successfully for both without creating a new version. This difference in handling the name
change is due to existing functionality within Teamcenter.

• Synchronization of multiple versions of an item.

The synchronize operation is performed during model file open and requested synchronization.
During synchronization of multiple versions of a part, each version becomes a new part and the name
of each part has the version number appended to it.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-13
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• Sending the latest dataset to I-deas

When you send a part or assembly to I-deas, you must be checking out from the latest Item Revision
that contains the dataset of the same type. Other Item Revisions may exist in the Item, but only the
ones that contain the dataset of the same type to be checked out are considered.
For example, you have Item Revision (IR) A, IRB, IRC, and IRD. You want to checkout a part dataset in
IRB. IRC and IRD do not contain the part dataset so the checkout is allowed.
If you don't have access to any of the later Item Revisions that contain the dataset (due to write/read
permissions, released status, and so on), the checkout is not allowed. This is because it must be
determined if a dataset of the same type exists in a later Item Revision. The part can still be sent for
reference.
For example, you want to checkout an assembly dataset in IRB. You have read access to IRD, but not
IRC. The assembly dataset is not in IRD. The checkout is denied because it cannot be determined if a
later assembly dataset exists in IRC.

• Sending an empty dataset to I-deas

When sending to I-deas, the part or assembly dataset is checked to ensure it is consistent. A
consistent dataset contains all required I-deas named reference objects. An empty dataset contains no
I-deas named reference objects. Typically, empty datasets are generated in Teamcenter during top-
down design of an assembly.
If the empty dataset is in an Item Revision of an Item where there is no consistent dataset of the same
type in any other Item Revision of the Item, the empty dataset is sent to I-deas. During this process all
previous Item Revisions to which you have read access are checked to determine if a consistent
dataset of the same type exists; if you do not have read access, the Item Revision is skipped.

Warning:
However, if an Item Revision contains a consistent dataset and you do not have read access to
it, the empty dataset is sent to I-deas and results in data corruption.

Note:
You cannot send an empty drawing, drawing set, or FEM dataset to I-deas.

Different dataset types in Item Revisions

When there are two or more datasets of different types in the same Item Revision, the behavior of the
datasets is dependent upon the setting of the applicable preferences, however the general behavior
transcends the preference settings. The following paragraphs describe the general behavior of different
datasets.

The following dataset groups are used as reference:

• Dataset group 1: I-deas part, I-deas assembly, I-deas drawing set

• Dataset group 2: I-deas drawing, I-deas FEM

4-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Drawing, FEM modified

Drawing, FEM modified

Typically, a group 2 dataset that is stored in an Item Revision that contains a group 1 dataset is related to
the group 1 dataset. If they are related, when a group 2 dataset is modifed, it is always forced into the
same Item Revision as the group 1 dataset.

For example, Item Revision A contains part version 1 (Pv1) and related drawing version 1 (Dv1). Item
Revision B contains Pv2. When the drawing is modified and saved, it is incremented to version Dv2 and
forced to Item Revision A. If you update Dv1 to point to Pv2 in the model file (using the Update Revision
command), Dv2 is forced to Item Revision B when saved.

Part, assembly, drawing set modified

When a group 1 dataset and group 2 dataset are in the same Item Revision and you modify a group 1
dataset and save it to a new Item Revision, the group 2 dataset is not carried forward to the new Item
Revision.

For example, Item Revision A contains Pv1 and related drawing Dv1. You modify the part and save it to
Item Revision B. Only the part dataset exists in Item Revision B. The drawing dataset is not automatically
included. To create a drawing in the new Item Revision, send the Dv1 drawing to I-deas and update it to
the latest revision of the part and save it to Teamcenter.

Drawing, FEM and existing Item Revision

When a group 1 dataset and group 2 dataset are in the same Item Revision and you modify a group 2
dataset, you are prevented from creating a new Item Revision in the Item.

For example, Item Revision A contains Pv1 and related drawing Dv1. You modify Dv1 and save it. You are
forced to save it to Item Revision A and cannot save it to Item Revision B.

Drawing, FEM and new Item Revision

When two group 2 datasets and no group 1 datasets are in the same Item Revision and you modify a
group 2 dataset, you can save it to a new Item Revision. Only the modified dataset is saved to the new
Item Revision.

For example, Item Revision A contains D1 and D2. You modify D1 and save it to Item Revision B. D2 is
not saved to Item Revision B. To get D2 to Item Revision B, send D2 to I-deas, modify it and save it to
Item Revision B.

Support for Teamcenter 128 character limit

Teamcenter can handle 128 characters in its item name, item ID, dataset name, and revision ID. This is
greater than the 32 characters it could previously handle and is greater than the 80 character limit for I-
deas. Integration for I-deas supports the 128 character limit for Teamcenter and resolves the character
length difference between Teamcenter and I-deas.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-15
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Note:
These changes apply to the item ID, name, and so on used in the Send to I-deas dialog box, in the
Integration for I-deas window, and in the I-deas Manage Bins dialog box.

Item ID

During Send to I-deas, if the Teamcenter item ID is greater than 80 characters, the value is truncated to
65 characters with an underline “_” appended. Then the Teamcenter UID (which is 14 characters) is
added at the end. The end result is 65 characters, plus _, plus 14 characters.

Item Name

Note:
This applies to the part name for part, assembly, and drawing set and the dataset name for
drawing, FEM, and standalone drawing.

During Send to I-deas, if the Teamcenter item name is less than 32 characters, that is used as the I-deas
part name.

If the Teamcenter item name equals 32 characters, it's compared with the first 32 characters in the
Teamcenter item description. If they are not the same, the item name is used and the Teamcenter name
matches the I-deas name. If they are the same, the entire item description is used, and the name in I-
deas is not the same as in Teamcenter.

Note:
This method is used for legacy data where previously Teamcenter could only handle 32 characters
and I-deas can handle 80.

If the Teamcenter item name is greater than 32 and less than or equal to 80 characters, the entire item
name is used and the I-deas name and Teamcenter name match.

If the Teamcenter item name is greater than 80 characters, it is truncated to 80 characters.

Note:
Drawings, FEMs, and standalone drawings are limited to 80 characters for the dataset name.

Revision ID

If the Teamcenter revision ID is greater than 80 characters, the value is truncated to 80 characters.

4-16 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Teamcenter 128 character limit disabled

Teamcenter 128 character limit disabled

It is possible to disable the 128 character limit in Teamcenter. The limit reverts back to 32 characters and
previous Integration for I-deas functionality for 32 character Teamcenter limit is applicable. This
functionality is controlled by the Teamcenter preference TC_Allow_Longer_ID_Name.

Customizing the Toolbar

The toolbar contains specified menu commands at the top of the Integration for I-deas window. The
toolbar contains a default but can be customized with commands from the Integration for I-deas
window.

To customize the toolbar, right click on the toolbar and choose Customize or Restore Default Toolbar.
Customize opens a dialog that lets you add, remove, and reorder buttons on the toolbar. You can also
use Sep to add a separator between groups of buttons.

The customization applied to the toolbar is kept after the Integration for I-deas session is closed and
reapplied upon startup. However, filter selections applied with the View Filter command are not kept.

The default toolbar contains the following buttons:

• View Part

• View Assembly

• View Drawing

• View Drawing Set

• View FEM

• View Top Assemblies Only

• Expand Below

• Get from Bin

• Put to Bin

• Save to Teamcenter

• Find Out of Date Items

• Update to Latest Revision

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-17
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• Delete from Model File

Filtering the Display in the Integration for I-deas Window

You can modify the display of parts, assemblies, and so on to provide a cleaner view of the items in the
model file. You can also use filtering to provide a more specific display of items in a complex assembly.

The filtering functionality is provided in the View main menu in the Integration for I-deas window. Click
on the item type you want to view, such as drawings, parts, or FEMs. The External item type refers to
parts, drawings, and so on that came from applications other than I-deas, such as NX. The external items
are displayed in accordance with the other filters, such as Top Level Assembly. Top Assemblies Only
indicates that subassemblies are not shown; only the top assemblies are displayed. Your filter selections
are remembered so the next time you start an Integration for I-deas session, the same filtering is used.

The Expand menu option (or the +) expands a selected item one level. Expand Below opens up all
levels below the selected item.

If one item is selected, all instances of that item that are displayed are also selected. When you expand
an item, any instances of the item that are now displayed are also automatically selected. When the item
is collapsed, the instances are no longer selected since they are no longer displayed.

Advanced Filtering

When you select the Advance Filter menu option, the View Filter dialog is displayed which provides
additional filtering options. The options are remembered so the next time you start an Integration for I-
deas session, the same options are selected. However, advanced filtering is turned off by default when
you start a session.

The View section of the dialog contains the same filter items, such as drawings and parts, found in the
View main menu. This section works together with the View main menu so that what is done in one is
reflected in the other.

Check the Advanced Filter option to activate the options below it:

• Enter a name, part number, or revision to use as a filter for items. You can use wildcards to help in
defining the particular filter used, such as 73* for the part number. The wildcards used can be
changed to Microsoft Windows, UNIX, or SQL conventions. To select a convention, in My Teamcenter,
choose Edit->Options->Search to change the wildcard type.
In addition, you can add case sensitivity to the name, part number, or revision fields. To add case
sensitivity, in My Teamcenter, choose Edit->Options->Search and select the Case checkbox.

• Specify the access as all, reference, checked out, or local. Only items with the specified access status
are displayed. Local refers to newly created parts that have not been checked in.

• Specify the version by using the symbols with a version value. For example, > 5, lists only those items
greater than version 5. For local items (new parts), use = –1 to list only local items.

4-18 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Save Data: Methods

• Select whether you want pruned items, unpruned items, or all items.

Note:
You can't perform operations on pruned items in the Integration for I-deas window, except for
Unprune.

• Check Parts/Assemblies and click the radio buttons to determine whether parts and assemblies
displayed have drawings or FEMs. This checkbox works in conjunction with the basic item type filters
Assembly and Part (at the top of the dialog and in the View main menu). For example, if the basic
filter type is set to assembly and not part, then this option combines with that to display only
assemblies with/without drawings or FEMs.

Save Data: Methods

This section describes options for saving I-deas modeling data in Teamcenter.

Integration for I-deas Save Menu Options

The save options on the Integration for I-deas window behave differently depending on the type of item
selected and its status. The options are located in the File menu. You can also access the options by
selecting the item and right-clicking. This section describes the options and their behavior.

• Save to Teamcenter
Saves the selected dataset and marks it as checked out in both Teamcenter and the I-deas model file.
Additionally, the version number of the I-deas item is set to one more than the saved dataset version.
This is known as preversioning.

• Save & Checkin

Saves and checks in selected datasets and their dependent objects to the Teamcenter database and
marks the I-deas model file item as reference only. The model file version numbers are synchronized
with the version numbers of the datasets. Selected or dependent datasets that are checked out but
not modified in I-deas are not saved (because they were not modified), but are marked as reference
only and the model file version number is decreased by one.

• Save, Checkin, & Remove

Saves and checks in selected datasets and their dependent objects to the Teamcenter database and
deletes the corresponding data from the I-deas model file. Because the tree in the Integration for I-
deas window reflects the contents of the I-deas model file, the datasets are also removed from the
tree. The datasets are stored in the Teamcenter database and can be displayed in the My Teamcenter
tree panel or Properties table.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-19
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Note:
If the selected datasets are referenced by items in the I-deas model file that have not been
selected for removal by this action, the datasets are checked into the database but are left as
reference items in the model file.

• Save As
Saves the selected datasets and dependent objects in the Teamcenter database. The first time data is
saved in Teamcenter, the system displays the I-deas to Teamcenter SaveAs dialog window regardless
of which option is chosen.
The Save As option allows you to assign identification to new items, select the item type, and
increment the revision letter when saving a new revision of an item. The item has to have been
modified and you cannot change the item ID (part number). Additionally, this option provides
subsequent processing options to control system behavior when saving multiple datasets.

Note:
To create a new revision of an item without modifying the item, use the My Teamcenter Revise
option on the I-deas menu. You cannot change the item ID.

Note:
To create a new part, use the My Teamcenter Save As option on the File menu.

Saving Large Assemblies in Teamcenter

If you work with large assemblies, increase the Orbix® buffer size to prevent failures. The default Orbix
buffer size is 512 KB. To increase the size of the buffer to unlimited, source the setup_varbs script from
the I-deas installation, then issue the following Orbix command (the following lines represent the entire
command and must be issued on a single line):

itadmin variable create –scope eds.ideas10 –t long –v ––1

policies:iiop:buffer_sizes_policy:max_buffer_size

Note:
Where —1 is two dashes with no space and a 1

Execute this script once for each client installation.

This setting is kept on the workstation and remains set between Integration for I-deas sessions.

To change the setting back to the default, execute the following command (all on one line):

4-20 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Saving Drawing Sets

itadmin variable remove –scope eds.ideas10

policies:iiop:buffer_sizes_policy:max_buffer_size

Note:
You can increase the Orbix buffer size after installing Integration for I-deas (this step is
independent), if you begin to experience failures when saving large assemblies. Prior to
performing this step, exit Integration for I-deas and Teamcenter.

Note:
Failure may include a CORBA/Orbix error, such as org.omg.CORBA*.

Saving Drawing Sets

The drawing set name is handled the same as a part or assembly when saving to Teamcenter, sending to
I-deas, or performing a revise operation.

The ItemID of the drawing set is the part number of the drawing set (if it's not mapped) and the Item
name (and Item description) is the drawing set name. Similar to a part, to change the drawing set name,
change both the Item name and Item description.

Saving ACF Parts

You can checkin to Teamcenter an Associative Copy Feature (ACF) target part without having to also
checkin the source part or context assembly. The target part can be checked in by itself.

To enable this functionality, the source part and context assembly must have been previously checked in
using Integration for I-deas 4.3. If you have checked in those items using an earlier version of
Integration for I-deas, you will get an error message.

Saving Assemblies With Precise BOM

A precise BOM allows you to have an assembly that contains specific revisions of parts and
subassemblies. In Teamcenter, the BOMView Revisions (BVR) objects store the single-level assembly
structure. A precise BOM reflects the latest changes made to the assembly when the Teamcenter
revision rule is set to precise.

For example, you can modify a part in an assembly in I-deas and update the assembly to contain the
latest revision of the part. When you save the part and assembly to Teamcenter, the BOM is updated to
contain the latest revision of the part.

If the BOM is not being updated (precise BOM), the Teamcenter revision rule doesn't contain Precise as
the first entry in the revision rule dialog box. Set it to Precise. If the Precise Only revision rule entry has
been deleted (not available for selection), then you can set the following preference to the name of a
revision rule that contains Precise as the first entry.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-21
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

IDEAS_precise_rev_rule

Saving New or Updated Modeling Items to Teamcenter

Once you name your model file in I-deas, its contents are reflected as datasets in the Integration for I-
deas window.

Perform the following steps to save modeling data in Teamcenter:

1. Select the folder in the My Teamcenter tree panel in which you want to save the modeling data.
If you do not select a folder, the new item is saved in the default folder defined by your user
preference settings. The default preference is the Newstuff folder. For more information about
setting user preferences, see Navigator Help.

2. In the Integration for I-deas window, select the unsaved dataset, or datasets, corresponding to the
modeling data that you want to save.

Note:
Unsaved modeling datasets reflect the I-deas part name and have no associated status icon.

3. From the Integration for I-deas window File menu, choose one of the following options: Save to
Teamcenter, Save & Checkin, or Save, Checkin, & Remove. Alternately, right-click the selected
datasets and choose an option from the popup menu. For more information, see Integration for I-
deas Save Menu Options, earlier in this chapter.
The system displays the dataset in the SaveAs dialog window.

4. Complete/modify the item details information for the modeling item in the Save to Teamcenter
dialog box.

Saving to Teamcenter Dialog Box

The Save to Teamcenter dialog contains rows, columns, and buttons to enable you to specify how
items are saved to Teamcenter. The dialog box is displayed when you select Save to Teamcenter, Save
& Checkin, or Save, Checkin, & Remove for an item or items on the Integration for I-deas window.

The dialog box lists the items you selected to be saved with columns for:

• Part Number

• ItemID

• RevisionID

• Name

4-22 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Item Types

• Item Type

• Dataset Type

• Projects

• CheckIn Intent

All newly created items you selected for saving are listed, including related items if they are new also. If
you are performing a Save As action, new and checked out, modified items that you selected or that are
related to selected items are also included. On the dialog, the items can be selected and deselected
individually, or you can use the Select All and Deselect All buttons for all items.

You can change the width of the columns and move the columns by selecting and dragging. Columns
with a red star indicate that these columns are mandatory and require an entry for each item saved. All
of the column fields, except Part Number and Dataset Type, can be changed by clicking or double-
clicking in the field.

When you save items from the Integration for I-deas window, you determine the checkin intent by
selecting Save to Teamcenter, Save & Checkin, or Save, Checkin & Remove. You can change the
checkin intent on the dialog by selecting the appropriate checkin intent for the items selected.

The Item Type pull-down menu provides a listing of the available item types. You can select an item or
items and change the item type with this feature, or click in the Item Type field for an item and use the
pull-down menu provided there.

Item Types

The Item Type assigned to an item is determined by the value of preferences in the Teamcenter
preferences.

The IDEAS_default_item_type defines the type of item created by default when new items are saved
from I-deas to Teamcenter.

Note:
If the preference IDEAS_default_item_type is not defined, the default item type used for newly
created items is Item.

New preferences are added to enable you to assign a specific item type for different items. The
preferences override the preference IDEAS_default_item_type. However, if a preference is not defined
for an item type, then it's assigned the value of IDEAS_default_item_type.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-23
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Note:
These preferences apply to newly created items that are being saved to Teamcenter. These are
default item types assigned and can be changed with the Item Type pull-down menu in the Save
to Teamcenter dialog.

Note:
These preferences are also applicable for migration and data sharing.

The following additional preferences are available. The default value is blank (no value).

• IDEAS_default_item_type_part
Defines the default item type for a newly created I-deas part, such as Part, Component, and so on.

• IDEAS_default_item_type_assembly
Defines the default item type for a newly created I-deas assembly, such as Assembly, Structure, and so
on.

• IDEAS_default_item_type_drawing
Defines the default item type for a newly created I-deas drawing, such as Drawing, Specification, and
so on.

• IDEAS_default_item_type_drawing_set
Defines the default item type for a newly created I-deas drawing set.

• IDEAS_default_item_type_fem
Defines the default item type for a newly created I-deas FEM.

When primary and secondary datasets are stored in the same Item Revision, such as a part and drawing,
the item type of the primary dataset (e.g., part) is assigned to the secondary dataset (e.g., drawing).
This is done because datasets in the same Item Revision must have the same item type. This is true
regardless of the setting for the preferences IDEAS_keep_drawing_with_related_model and
IDEAS_keep_dwgset_with_related_drawing. For example, if
IDEAS_keep_drawing_with_related_model=ALWAYS, the drawing is placed in the same Item Revision
as the part, and the drawing item type is the same as the part item type.

Assign Item ID, Revision ID

The ItemID is the I-deas part number by default, however, it can be different. You can double-click in the
field to change it or select the item and click on Assign ItemID to assign an ItemID.

4-24 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Assign Projects

Note:
The ItemId field must be blank to enable an assigned ID. If an ItemID already exists, double-click
the field and delete the entry before assigning an ItemID.

The RevisionID field and Assign RevID button have the same functionality as item ID.

Note:
The ItemID and RevisionID columns operate in accordance with the preferences set for your site/
session. For example, if the preference IDEAS_keep_drawing_with_related_model is set to
NEVER (the default), the drawing cannot have the same ItemID as it's related part. If you enter the
same ItemID for a drawing as the part ItemID, an error message is displayed.

Assign Projects

The Projects button allows you to assign selected items to projects for which you are a member. You can
click on the project name field for the item, or select the item and click on the Projects button. The
Project Selection dialog is displayed. The projects that you are a member of are listed in the Projects
for Selection window. Click an arrow button to move the project to the Selected Projects window,
which assigns the item to the project. An item can have multiple projects.

Note:
You must be a privileged team member within the project to be able to assign items to the project.

If you select multiple items with different projects and click the Projects button to change them, a
dialog informs you that multiple projects are present. Click Yes to continue to the Project Selection
dialog.

The following also apply:

• Projects can be assigned only for new items. The Projects button is grayed out if the item already has
projects assigned.

• If a secondary item is associated to a primary item, for example, a drawing to a part, you cannot
assign projects for the secondary item (drawing). The secondary item is automatically assigned to the
same project as the primary item. However, if the secondary is not stored with the primary (not in the
same Teamcenter Item), you can assign a different project to the secondary.

Note:
This also applies to FEMs.

• If the preference IDEAS_Mandatory_Projects_on_save is set to TRUE and no projects are assigned to

the item, then you must assign projects. The projects are assigned at the Item level. Associated items,

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-25
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

such as drawings or FEMs, also have projects assigned at the Item level if they are not saved with the
primary item.

• By default, Teamcenter propagates the following relations to a dataset:

• Specification

• Manifestation

• AltRep

• EC_affected_item_rel

• EC_solution_item_rel

To propagate all object types under an item including the Rendering relationship and be able to add
BOMView data, run the Teamcenter utility update_project_data. This ensures that you have
privileges to automatically propagate projects as necessary when using Integration for I-deas. For
information on running the utility, see the Teamcenter Utilities Reference guide, Maintenance Utilities
chapter.

Add or Change User Attributes

Note:
User attribute functionality is only available with I-deas 11m2 or later.

You can add or change user attributes. Select the item, then click on the Attributes button. Only user
mapped attributes defined with a master of cad or both are available.

You can add an attributes column to the item listing for cad and both attribute types by selecting a row
or rows in the table, right-clicking anywhere in the table, and selecting Add Attribute Column. The Add
Attribute Column dialog is displayed which lists all the mapped attributes available for the selected
row(s). Select the attribute(s) to be added as column(s). After the attribute column is displayed, you can
change an attribute by double-clicking on the field. When you close the Integration for I-deas session
and open it again later, the added columns are remembered and displayed.

In addition, the Teamcenter List of Values (LOV) attributes are supported as attributes that can be added
or modified.

Caution:
Only LOVs defined with an Exhaustive usage are supported.

4-26 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Preferences

Preferences

The following preferences in the Teamcenter preferences are available for the Save to Teamcenter
dialog:

• IDEAS_Project_Mandatory_on_save
This controls whether project assignment is mandatory.
Valid values:

TRUE – You must set a project for each new item saved. The Save to Teamcenter dialog is
displayed until the project is defined.

FALSE – A project is not mandatory.

Default value:

FALSE

• IDEAS_Mandatory_Attr
This provides a list of the attributes that are mandatory for each item saved.

Note:
This preference must be created as a site preference.

Valid values:

Valid attributes. Each attribute name is followed by a comma.

Use only I-deas attribute names, not Teamcenter attribute names for the values. The I-deas
attribute names are in the I-deas Manage Bins dialog box, Details list. The attributes must be
mapped in Teamcenter. Refer to the attribute mapping file for names of the attributes that are
mapped.
The attribute master cannot be iman, where master=iman. It can only be cad or both.

Default value:

No values listed

Saving Checked-Out Modeling Items in Teamcenter

Perform one of the following to save checked-out modeling datasets using Save to Teamcenter, Save &
Checkin, or Save, Checkin, & Remove:

• From the Integration for I-deas window, select the dataset or datasets corresponding to the modeling
data that you want to save, then use the right mouse button menu to choose the save option.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-27
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• From the My Teamcenter tree panel, highlight the dataset or datasets corresponding to the modeling
data that you want to save, then choose File→Save.

New dataset versions are saved in the database and associated with the item revision with which they
were previously saved. For more information, see Integration for I-deas Save Menu Options, earlier in
this chapter.

Clean Database of Items On Failed Checkin

(PR 2048909) The following preference is added (in the Teamcenter preferences) for checkin of items:

• IDEAS_delete_items_on_checkin_failure
When set to TRUE, this preference deletes all items from the Teamcenter database that were created
during a failed checkin. However, this decreases performance on subsequent checkins as all items
(e.g., for an assembly) have to be recreated.
When set to FALSE (the default), items with new ItemIDs assigned automatically or manually during
checkin are deleted from the Teamcenter database during a failed checkin. The other items are left in
the database for subsequent checkin.

Creating CGM Datasets for Drawings

You can create an Image dataset for an I-deas drawing when the drawing is checked in and then view
the CGM in Teamcenter Visualization. The CGM is created in accordance with the CGM options set in I-
deas. The Image dataset contains the CGM file and is attached to the I-deas drawing dataset.

You can create a CGM for the active displayed sheet or for multiple sheets. When multiple sheets are
involved, a CGM is created for each sheet.

To create the CGM for the active displayed drawing sheet, select the following option in the Integration
for I-deas Preferences dialog box (Edit→Preferences in the Integration for I-deas window):

Create CGM File

Or you can set the following preference:

IDEAS_drawing_create_cgm=TRUE

Note:
This is a user and site preference. Default is FALSE.

When this preference is set to TRUE, performing a checkout of the drawing also checks out the
associated Image dataset, cancelling checkout of the drawing cancels checkout of the Image
dataset, and synchronization of the drawing syncs the Image dataset.

To create CGMs for multiple sheets, set the above preference and the following preference:

4-28 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Creating New Item Revisions

IDEAS_drawing_create_cgm_multi_sheet=TRUE

Note:
This is a site preference only. Default is FALSE.

Creating New Item Revisions

The Revise option on the I-deas menu creates a new revision of an existing item and also creates new
datasets based on each of the I-deas datasets and DirectModel datasets associated with the original item
revision. The new datasets contain the same data, I-deas files and metadata, and JT files as the original
datasets; however, modifying the files associated with these datasets does not affect the base files.

When using I-deas→Revise, Teamcenter Business Modeler deep copy rules must not be set that cause I-
deas datasets to be copied as objects or not copied at all. I-deas datasets must be copied as a reference
to the new item revision. In addition, Copy as Reference must be set on I-deas data objects in the
Define Attached Objects step of the Revise dialog box, and you should not have any Action Rules for I-
deas datasets.

Note:
Only datasets used by I-deas are replicated in item revisions created with the Revise option. Other
associated datasets, such as documents and forms, are not replicated by the Revise option, unless
the Business Modeler is configured to do that.

Perform the following steps to create a new revision of an item:

1. Select the Item Revision in the My Teamcenter tree panel.

Note:
The site performing the revise operation must have ownership of the Item and all Item
Revisions under it.

Warning:
Do not use the standard Teamcenter Revise option (located on the File menu) to create a
revision of an I-deas item. This creates only a new revision of the I-deas item and breaks the I-
deas data model; it does not create the related I-deas datasets.

2. Choose Revise from the I-deas menu.

The system displays the Revise window.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-29
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Note:
When using I-deas→Revise, the default settings copy the item in the correct manner to
allow all I-deas metadata, attributes, and so on to be copied. Don't use another copy type in
the Revise window, such as Copy As Object in the Advanced tab, to copy the item.

3. Enter the next consecutive revision identifier in the Revision ID field. To let My Teamcenter
automatically assign a unique revision identifier, click Assign.

4. Optionally, choose the Open on Create option to open the new item revision in the Product Data
application. For more information, see TeamcenterProduct Data Help.

5. Click the OK button.

If you choose the Open on Create option, the system launches the Product Data application and
displays the new item revision. If not, the new item revision and associated datasets are displayed
in the My Teamcenter tree panel.

Perform Revise On Any Item Revision

(PR 5198424) The following preference (in the Teamcenter preferences) allows you to revise any Item
Revision.

• IDEAS_Allow_Non_Latest_Revise
When set to TRUE, the preference allows you to perform a Revise operation (I-deas→Revise) on any
Item Revision, not just the latest Item Revision. The Revise operation has the same functionality as it
previously did, however a message is displayed informing you that you are revising a non-latest Item
Revision. Click OK to continue the revise operation.
When the items in the Item Revision are copied, the I-deas dataset version number is incremented 1
more than the last version number of the I-deas dataset that exists, not just one more than the
dataset in that particular Item Revision. The new I-deas dataset is a copy of the version in that Item
Revision, which is not a copy of the latest dataset if the Item Revision is not the latest.

Note:
The previous I-deas datasets still exist and contain the latest changes.

For example, you have Item Revisions A, B, C, and D, with I-deas dataset versions 1, 2, 3, and 4,
respectively. You perform a Revise operation on Item Revision B (I-deas dataset version 2) and get a
new Item Revision E. The I-deas dataset in Item Revision E is incremented to version 5 although it's
really a copy of version 2. The changes made in versions 3 and 4 are not in version 5.

Caution:
When you perform a Revise operation on a non-latest Item Revision, the new I-deas dataset
does not contain the latest changes.

4-30 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Purging Item Revisions

This preference is set to FALSE by default.

Purging Item Revisions

When you use the one version per revision method for storing and managing data, Item Revisions can
accumulate and result in the extra burden of handling large numbers of unneeded Item Revisions. When
using I-deas→Purge Item Revisions, the Item Revisions under an Item are purged with only a specified
number kept.

To purge Item Revisions:

1. In Teamcenter, select an Item or Item Revision. If an Item Revision is selected, the Item where it is
contained is purged.

2. From the I-deas menu, choose Purge Item Revisions. The item revisions are deleted and
information about the operation is output to the TB.log file. If some Item Revisions could not be
deleted, this is output to the TB.log file along with an explanation about why they could not be
deleted.

Note:
The latest Item Revision is never deleted.

When an Item Revision is being deleted, all Teamcenter entities under it are deleted, including part
datasets, assembly datasets, JT datasets, and so on.

If an Item Revision is to be deleted but it contains an item referenced by another Item Revision, it is not
deleted. For example, if an item in Item Revision ABC is referenced by Item Revision DEF, Item Revision
ABC is not deleted.

The purge item revisions functionality is not activated by default. To enable the functionality, set the
following preference:

• IDEAS_show_purge_revision_ui=TRUE

The number of Item Revisions kept is controlled with the following preference:

• IDEAS_purge_revision_keep_limit
Set this to any integer. The default is 1 (keep only the latest).

Creating I-deas Datasets

Datasets are used by Teamcenter to manage data files created by other software applications.

Create a single I-deas dataset in My Teamcenter by using the File→New→Dataset menu option.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-31
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Create multiple I-deas datasets in Structure Manager as follows:

1. Select one or more part BOM lines or assembly BOM lines, but not both.

2. Pull down the I-deas menu and choose either the Create I-deas Part Dataset option if you have
selected parts or the Create I-deas Assembly Dataset option if you have selected assemblies.
The items are processed.
There are three error conditions for which a dialog is displayed:

• When any of the selected items already contain datasets, they are skipped in processing and the
dialog window lists the skipped items.
• If you attempt to create an I-deas part dataset or an item revision that has children, this item is
skipped.
• A customization call, through validation failure, can force an item to be skipped or can abort the
create process.

Caution:
If the item revision already contains a non-I-deas dataset, it receives an I-deas dataset. Items
must not have more than one CAD dataset type, as this can cause problems in the operation
of Integration for I-deas. If an item has more than one CAD dataset type, you must delete
inappropriate data set types.

To see the I-deas datasets that are created, open My Teamcenter.

You can send datasets to I-deas from My Teamcenter by performing one of the following:

• Double-click the dataset.

• Select the dataset, pull down the File menu, and choose the Open option.

• Select the dataset, pull down the I-deas menu, and choose the Send to I-deas option.

For more information about sending datasets to I-deas, see chapter , Using Integration for I-deas:
Sending Modeling Data From My Teamcenter to I-deas.

For general information about datasets, see Understanding Teamcenter Objects, Revisions, and Versions
in chapter , Getting Started, and the Teamcenter online help.

Deleting I-deas Modeling Data Using Teamcenter

If you have many data items to delete, use the following general process to delete I-deas data from
Teamcenter:

1. Ensure the datasets you want to delete are checked in.

4-32 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Deleting I-deas Modeling Data Using Integration for I-deas

2. Ensure related BVRs are checked in.

3. From the item revision context, delete assembly, drawing, and FEM datasets first because they
reference other datasets and item revisions.

4. After deleting assembly, drawing, and FEM datasets, delete the part datasets.

5. Delete all other datasets.

6. Delete the item.

To delete a limited number of data items using My Teamcenter:

1. Go to the top-level assembly.

2. Delete JT, I-deas, and BVR data.

3. Delete the item.

4. Repeat the process for subcomponents.

To delete a context assembly, you must first delete all associated target part datasets to remove the
associative copy relationships (ACR). You can select multiple items in the correct order and delete them
in a single operation. To delete the data with associative copy relationships, delete in this order:

1. Assembly BVR.

2. Assembly dataset.

3. Target dataset.

4. Source dataset.

5. Assembly and part items.

Deleting I-deas Modeling Data Using Integration for I-deas

Perform the following procedure to delete items with Integration for I-deas.

1. In the Integration for I-deas window, choose Delete From Model File from the Manage Bins main
menu. Or alternatively, right-click the selected item(s) to display the popup menu and select Delete
From Model File. The Delete dialog window displays the part name, part number, version number,
and entity type of the item to be deleted.

2. If you delete an assembly, the Recursively Delete Related Parts and Subassemblies option is
displayed. Check the option to delete all parts and subassemblies contained within the assembly.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-33
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

3. If you delete an assembly, and you choose the option to recursively delete related parts and
assemblies, the Prune Part Instances option is also displayed. Check the option to prune this item
including all of its related children from all assemblies/subassemblies that they currently belong to.

4. If you delete a part or assembly and there are related drawings, the Delete related Drawings
option is displayed. Check the option to also delete related drawings. If there are no related
drawings, this option is not displayed.

5. If you delete a drawing, the Recursively Delete Related Parts and Assemblies option is displayed.
If you choose this option to delete all related parts and assemblies, the Prune Part Instances
option is also displayed. Check the option to prune the drawing and its related children from all
assemblies/subassemblies that they currently belong to.

6. Click Delete to remove the item. Click Delete All to remove multiple items at once.

Note:
You cannot delete a part if a drawing or FEM is dependent upon the part. You must delete the
drawing/FEM first, then the part.

Note:
If you get an error message when deleting that states there is an internal error, the likely cause is
that a relationship exists to a drawing or FEM. The related FEM may not be listed in the Integration
for I-deas window if I-deas is running an application other than Simulation. You can delete the
FEM in I-deas Manage Bins.
The same situation exists for drawings if I-deas is running the Simulation application.

Renaming/Renumbering Items
Perform the following procedure to change the part name or part number of items.

Note:
The part name and part number cannot be changed for items that have already been checked into
Teamcenter.

1. In the Integration for I-deas window, choose Rename from the Manage Bins main menu. Or
alternatively, right-click the selected item to display the popup menu and choose Rename. The
Rename/Renumber dialog window is displays the existing part name and part number.

2. Enter the new part name and/or part number.

3. Click OK to rename/renumber the item.

4-34 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Derived I-deas Parts

Derived I-deas Parts

For a derived I-deas part (derived from an NX part to create a FEM in I-deas), the name cannot be
changed if the derived part is saved in the same Item Revision as the source part. You can only change
the name if it's saved as a new Item in Teamcenter.

To change the part name, first change the part number in the number field.

Note:
If you change the part number back to the source part number, the name field is disabled.

Moving Items
Perform the following procedure to move items between bins.

1. In the Integration for I-deas window, choose Move from the Manage Bins main menu. Or
alternatively, right-click the selected item(s) to display the popup menu and choose Move. The
Move dialog is displays the part name, part number, and current bin where the item is located.

2. Select the target bin in the To Bin pull-down menu. This is the bin where the item is moved to.

3. The Create Bin option is available in the pull-down menu which displays the Create Bin dialog to
create a new bin.

4. Click Move to move the item to the selected bin. Click Move All to move multiple items at once.

Copying Items
Note:
To copy an item as a workable, modifiable copy that is recognized in I-deas, use the copy
command in the Integration for I-deas window. Don't use the copy function in Teamcenter My
Teamcenter application.

Perform the following procedure to copy items.

1. In the Integration for I-deas window, choose Copy from the Manage Bins main menu. Or
alternatively, right-click the selected item to display the popup menu and choose Copy. The Copy
dialog window displays the part name, part number, and bin. The To section in the dialog shows
the part name and part number with _copy appended.

2. Modify the part name and part number as needed.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-35
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

3. Select a bin to place the new item from the Bin pulldown menu. The default bin is the same as
where the original item is located. The Create Bin option is available from the pulldown menu to
allow you to create a bin.

4. Depending on the item you are copying, you may have additional options in the Copy dialog. If you
have drawings or FEMs associated with the item:

Note:
When I-deas is running the Simulation application, the Integration for I-deas window doesn't
list drawings and the option to copy related drawings is not available. When I-deas is running
an application other than Simulation, the Integration for I-deas window doesn't list FEMs and
the option to copy related FEMs is not available.

• Copy Related Drawings – Check this to copy associated drawings with the item.

Note:
When copying related drawings, COPY_OF_ is placed before the name and a 1 is
appended, by default. For example, the related drawing bracket_A is copied as
COPY_OF_bracket_A1. This is different from the default copy naming process for related
drawings in I-deas Manage Bins. After copying, you can change the name of the copied
drawing in the Integration for I-deas window.

• Copy Related FEMs – Check this to copy associated FEMs with the item.

Note:
The default naming of related FEMs is the same as related drawings described above.

If an assembly is selected that has associative copy features (ACF):

• Copy Assembly Only – Check this option to copy only the assembly and not any associative copy
features.
• Copy Associative Copy Target Parts – Check this option to copy the assembly and the selected
associative parts contained in the assembly.
• Copy Associative Copy Target and Source Parts – Check this option to copy the assembly and
all selected and source associative parts contained in the assembly.

5. Click Copy to make a copy of the item and place it in the designated bin.

Creating Bins
Perform the following procedure to create bins:

4-36 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Bin Item on Workbench

1. In the Integration for I-deas window, choose Create Bin from the Manage Bins main menu. Or
alternatively, right-click the selected item to display the popup menu and choose Create Bin. The
Create Bin dialog displays the existing bins.

2. Enter the name for the new bin.

3. Click OK to create the new bin. Click Apply to create the bin and leave the dialog open to create
another bin.

Note:
You can also delete and rename bins that you have created. Select the bin and right-click or go to
the Manage Bins main menu to choose the option. However, you cannot delete or rename the
Main bin.

Note:
When sending items to I-deas, you must pick a destination bin. You can also create a bin at that
time from the Send to I-deas dialog and use it as the destination.

Bin Item on Workbench

When you get an item from the bin on to the I-deas workbench, the icon is displayed next to the item
in the Integration for I-deas window. When you put the item away, the icon is removed.

Remote Checkout
When you checkout a part to I-deas (send to I-deas) for modification, the I-deas site performing the
modification must have the right to modify the part. If the part is owned by another site, Integration for
I-deas performs a remote checkout where the right to modify is granted to the importing site. The
specified part and all other datasets needed for the part, such as a DirectModel dataset, are also checked
out.

When the part is modified and checked back in (Save, Save & Checkin, and so on) Integration for I-deas
performs a remote checkin where a new Item Revision is created (one version per revision functionality)
and ownership of the modified part is still with the site that originally owned the part.

When a part is checked out, the Item is also automatically checked out if the right to modify is granted
to the importing site. During checkin of the part, the Item is also automatically checked in.

Compressing I-deas CAD Files

Enabling compression of files can provide a performance improvement. The performance gain depends
upon the size and makeup of the product structure. Typical improvement gains are: 0 – 45% for
checkout and 18 – 35% for checkin.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-37
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

You should perform a test on sample data before deciding to use compression. Integration for I-deas 4.2
and later supports compression of CAD files.

To enable compression, set the following preference in the Teamcenter preferences:

• IDEAS_cad_file_compression=TRUE

Before using compression, you need to be aware of the implications. All I-deas CAD files are compressed
in the Teamcenter volume. If you have customizations that obtain files from the Teamcenter volume,
these customizations could be affected. In addition, anti-virus programs must be configured to skip files
with a .Z extension or to bypass the following directories entirely:

Teamcenter volume directory (s)

Checkin temporary directory (java.io.tmpdir)

Checkout temporary directory (TCExportDir, unless file caching is used)

The following Teamcenter products are known to support compressed files:

• CMM 4.1

• NX Manager / I-deas Interop (04/06 release date)

When files are compressed, checkin is able to upload more files in a given period of time. This can lead
to an “ipc queue” error. This error occurs because Windows runs into a limit on the number of ports
assigned to active and closing TCP/IP connections. The default maximum port number is 5000. This
default limits Windows to an average of about 2 file uploads per second over an extended period of
time. The maximum port number can be increased by editing the Windows registry. A maximum of
20,000 is recommended for migration and this should be sufficient for checkin also.

Note:
Migration and import will accept already compressed files if the corresponding preferences
IDEAS_import_compressed_files and IDEAS_migrate_compressed_files are set to TRUE, which
is the default. These preferences do not compress files, but support already compressed files
during migration and import.

Improving Performance
The following preferences allow you to improve performance during check in of assemblies and during
model file open:

• IDEAS_send_assembly_config_data
This preference controls the amount of Integration for I-deas data saved to Teamcenter during check
in of assemblies.

4-38 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Apply a Status and Create a New Revision In One Step

• FALSE
Easily recomputed assembly data is not sent to Teamcenter during check in. This improves
performance of the check in for assemblies.

Note:
This does not cause degradation of the model or data corruption.

• TRUE
All assembly data is sent to Teamcenter during check in. This is the default.

• IDEAS_checkin_allow_non_synchronized_items
This preference controls check in of items that are not sychronized with Teamcenter.

• TRUE
Checkin proceeds although some items are not synchronized with Teamcenter. This could cause
checkin to fail more often compared to synchronizing the data before checking in. For example,
checkin could fail if some of the items are no longer in Teamcenter or if their status has changed.
This preference works in conjunction with the preference IDEAS_automatically_synchronize
which should be set to FALSE to avoid automatic synchronization during model file open.

• FALSE
Checkin does not proceed if the items are not synchronized with Teamcenter. This is the default.

Apply a Status and Create a New Revision In One Step

You can apply a status to the datasets within an Item Revision, thereby locking in the modifications
made, and create a new Item Revision with one step. The menu selection I-deas→Freeze and Create
New Revision combines both of these functions. This functionality allows you to select an Item Revision
and quickly apply a status to each item within it instead of manually applying a status to each item. All
components within an assembly also have the status applied. This saves time and avoids errors
especially when large assemblies with complex hierarchies have to be manually traversed.

Note:
Integration for I-deas follows Teamcenter Business Modeler deep copy rules where non-I-deas
datasets are copied as reference datasets, by default. You can change the Teamcenter Business
Modeler deep copy rules to copy those datasets as objects.

The status applied must match one defined in the Teamcenter Admin application manager, Type
application, Status section.

The new revision is created automatically using the same functionality as the Integration for I-deas
revise operation (I-deas→Revise).

The I-deas→Revise and I-deas→Freeze and Create New Revision commands are applied differently to
derived I-deas parts. When an Item Revision contains a derived I-deas part and it's source, the Item

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-39
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Revision is created but the I-deas datasets are not copied over to the new revision, except for drawing
sets and standalone drawings.

As part of the Revise operation, the DirectModel and IdeasAssemblyViewInfo datasets are copied
forward for an I-deas assembly item in accordance with Teamcenter Business Modeler deep copy rules
(Copy As Reference by default). To not copy these datasets, set the deep copy rule Renderings:Direct
Model to Don't Copy.

To freeze and create a new revision:

1. Choose an Item Revision.

Note:
You can select only one Item Revision.

Note:
If you select an Item, the operation is performed on the latest Item Revision within the Item.

2. Select I-deas→Freeze and Create New Revision. The Submit For Review-Create New Revision
window is displayed with the Item Revision to be frozen listed.

3. Click OK.

4. The status is applied to all datasets within the Item Revision and a new Item Revision is created.

The following preferences control the I-deas→Freeze and Create New Revision functionality:

• IDEAS_related_objects_to_publish
Freezing an Item Revision applies a status to the datasets and copies the datasets to a new item
revision. This Identifies the relationships that are kept on the items in the frozen Item Revision.

• IDEAS_relations_copied
Freezing an Item Revision applies a status to the datasets and copies the datasets to a new item
revision. This Identifies the relationships that are kept on the items in the copied Item Revision.

• IDEAS_CM_Release_statuses
Identifies the status to create for an item when it has been frozen.

• IDEAS_Allow_Non_Latest_Revise
This preference enables you to perform the revise part of this command on any Item Revision, not just
the latest.
When set to TRUE, the preference allows you to perform a Revise operation (I-deas→Revise) on any
Item Revision, not just the latest Item Revision. The Revise operation has the same functionality as it
previously did, however a message is displayed informing you that you are revising a non-latest Item
Revision. Click OK to continue the revise operation.

4-40 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Attribute Mapping

When the items in the Item Revision are copied, the I-deas dataset version number is incremented 1
more than the last version number of the I-deas dataset that exists, not just one more than the
dataset in that particular Item Revision. The new I-deas dataset is a copy of the version in that Item
Revision, which is not a copy of the latest dataset if the Item Revision is not the latest.

Note:
The previous I-deas datasets still exist and contain the latest changes.

For example, you have Item Revisions A, B, C, and D, with I-deas dataset versions 1, 2, 3, and 4,
respectively. You perform a Revise operation on Item Revision B (I-deas dataset version 2) and get a
new Item Revision E. The I-deas dataset in Item Revision E is incremented to version 5 although it's
really a copy of version 2. The changes made in versions 3 and 4 are not in version 5.

Caution:
When you perform a Revise operation on a non-latest Item Revision, the new I-deas dataset
does not contain the latest changes.

This preference is set to FALSE by default.

For additional information on these preferences and other preferences related to this functionality, see
chapter , Preferences.

Attribute Mapping
Attributes must be transferred between Teamcenter and I-deas. The process of transferring attributes
between the two systems is referred to as attribute handling. Attribute handling involves mapping an
attribute identifier from one system to an attribute identifier of the other system (attribute mapping),
and potentially modifying the value of an attribute (value mapping).

Hardcoded attributes and attributes mapped as constant are not supported by Integration for I-deas and
are skipped during the mapping process.

In addition to application-defined attributes in both Teamcenter and I-deas, each system allows creation
of user-defined attributes that must be mapped with a user customization.

Mapping I-deas Part Number Attributes

An I-deas part number can be mapped to a custom Teamcenter attribute, I-deas Part Number. This
allows an original part number to be maintained with a part.

• Without custom part number mapping, the I-deas part number is mapped to the standard Teamcenter
ItemID attribute.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-41
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• With custom part number mapping, the I-deas part number is preserved in the I-deas Part Number
attribute, and for the Teamcenter ItemID the user can specify a unique value, or accept the
automatically-generated value.

Perform the following steps to map the I-deas part number attribute and send the item to I-deas:

1. Dump the current mappings to a file using the export_attr_mappings.exe utility in the
Teamcenter bin directory. Modify the mapping file as needed to the part number mapping you
want. For example, you could map the part number attribute to a custom attribute in the Item
Revision Master form, then import the revised mapping file using the import_attr_mappings.exe
utility.

Note:
Be sure to terminate all the Teamcenter sessions so no sessions are running on the database
before you run import_attr_mappings.exe.

2. Create a new part or assembly in a model file and save the file.
If you go to My Teamcenter and open the item revision master form for the item, you see the I-deas
part number in the field you mapped. For example, if you mapped the part number to the custom
attribute on the Item Revision Master form, you see the part number in the related field.

3. Create a drawing for the new part or assembly. The ItemId field in the Save As dialog window
defaults to the item ID of the part or assembly. Assign a new item ID by either typing in a new
value, or click the Assign button to autoassign a value.

4. Remove the part or assembly from the model file and send to I-deas by pulling down the I-deas
menu and choosing the Send to I-deas option.
The Send to I-deas dialog window displays the custom part number for the item. After sending to I-
deas, the original part number and custom part number display in the Integration for I-deas
window.

Mapping I-deas User Attributes to Teamcenter Attributes

User attributes are stored in Teamcenter as internal private data. To enable user attributes to be visible
in Teamcenter, you must define the equivalent user attribute for the Integration for I-deas dataset as a
custom Teamcenter attribute. You can change the names of the attributes between the two systems,
but for consistency you should keep them the same.

Note:
I-deas title attributes are treated as I-deas user attributes.

4-42 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Defining the Attribute Type

Note:
I-deas revision attributes and part name attributes are not user attributes and can't be mapped.

The mapping of the I-deas internal user attribute to the custom Teamcenter attribute is accomplished by
defining the attribute synchronization. Attribute synchronization uses attribute mapping definitions that
are stored in the database to map attributes. The context of an attribute synchronization mapping
definition is an I-deas dataset. Mapping definitions can be specified for a particular dataset type. A
mapping definition consists of an identifier (a title) and the location of the Teamcenter attribute in
relation to the context dataset. The same mapping definition is used for migration, import, export,
checkout, and checkin processes. The I-deas user attribute label is used as the mapping definition title.

The I-deas user attributes are created in the I-deas Item Details dialog and mapped using the
Teamcenter attribute mapping functionality. The mapping title must exactly match the I-deas user
attribute name.

For additional information about using Teamcenter attribute mapping functionality, see the Teamcenter
documentation and choose System Administration Help→Configuring the Teamcenter
Environment→UG Part to Teamcenter Attribute Mapping.

The attributes are synched only when a save to Teamcenter (checkin), send to I-deas (checkout), or
change to checkout operation is performed.

Note:
The attributes are not synched if the same version of the part is in the model file. Remove the part
version from the model file before performing a send to I-deas operation, or use a fresh model file
to synchronize user attributes.

If any attribute of a part is not mapped properly, saving the item to Teamcenter will fail, or sending the
item to I-deas will fail.

Defining the Attribute Type

The attributes are defined as having the ability to be changed by I-deas, Teamcenter, or both. When
using the Teamcenter attribute mapping functionality, define the master variable as cad, iman, both, or
none. For example:

master=cad

The default is no definition for the master variable which indicates both.

The definitions determine the software that has control over the attribute:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-43
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

• cad – The attribute can only be modified when the part is in I-deas (as a checked out item). Checkin
from I-deas to Teamcenter changes/creates the value for the attribute.

Note:
The attribute is not sent to I-deas during checkout because I-deas already has the value and it's
not allowed to be changed by Teamcenter.

• iman – The attribute can only be modified when the part is in Teamcenter. Checkout from
Teamcenter to I-deas changes/creates the value for the attribute.
If you modify an attribute in I-deas that has been defined as iman and checkin to Teamcenter, the
corresponding value in Teamcenter is not changed.

• both – The attribute can be modified when the part is in I-deas or Teamcenter. During checkin from I-
deas to Teamcenter, the value in Teamcenter is changed to the I-deas value. During checkout from
Teamcenter to I-deas, the value in I-deas is changed to the Teamcenter value.

Note:
If an attribute is marked as BOTH, checkin/checkout fails if the mapping cannot be resolved. For
example, this can occur if an I-deas attribute is mapped to a Teamcenter attribute that does not
exist (for example, because of where the item is in the workflow process).

• none – The attribute is not modified by I-deas or Teamcenter. It's skipped during checkout from
Teamcenter to I-deas and checkin from I-deas to Teamcenter.

Special Attributes

Some attributes require a specific title. The following attributes can be mapped as cad, iman, or both,
but the attribute title must be the following (exactly as shown):

• I-deas Change History

• I-deas Version Description

Note:
In addition, to map I-deas Version Description, the IDEAS_supports_version_desc preference
must be set. The default for this preference is TRUE.

• I-deas Part Number

Master Variable for Part Number and User Attributes

When you define the attribute map master variable, you get different results when mapping the I-deas
part number and mapping custom attributes.

4-44 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Mapping Attributes with BMNR Defined For Item Name

The following table shows the results when you map the I-deas part number. attrX is the Teamcenter
attribute to which the I-deas part number is mapped.

* If attrX is blank, then the Item ID is used instead.

Action master=both master=cad master=iman master=none

Checkin attrX mapped attrX mapped Not mapped Not mapped

Checkout attrX mapped* attrX mapped* attrX mapped* attrX mapped*

Sync attrX mapped* attrX mapped* attrX mapped* attrX mapped*

Update attrX mapped* attrX mapped* attrX mapped* attrX mapped*

The following table shows the results when you map user attributes. attrX is the Teamcenter attribute to
which the I-deas user attribute is mapped.

Action master=both master=cad master=iman master=none

Checkin attrX mapped attrX mapped Not mapped Not mapped

Checkout attrX mapped Not mapped attrX mapped Not mapped

Mapping Attributes with BMNR Defined For Item Name

When you have Teamcenter Business Modeler Naming Rules (BMNR) defined for item name, the
following additional step is required to get attribute mapping to work correctly.

Define the following preference in Teamcenter:

• IDEAS_default_item_name_<user defined item type>

Set this to a value that complies with the BMNR for this item type. For example, if the BMNR name for
this item type is defined as @@@NNN and the user defined item type is test, then
IDEAS_default_item_name_test=XYZ678 is correct usage of the preference. In this example,
XYZ678 is the value you want for the default item name for the item type test.

Alternatively, if you have the same BNMR for all/remaining item types for the item name field, add the
following preference:

• IDEAS_default_item_name=@@@NNN

If neither preference is set, the item name dummy is used to allow the software to pass naming rules for
the item name field for item types. You must ensure that the item name dummy is a valid item name for
the item type (i.e., the BMNR is defined as @@@@@).

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-45
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Attribute mapping performance

During a save to Teamcenter, if you observe a degradation in performance when you change the item
type on the Save to Teamcenter dialog box, this could be due to the information available in the
attribute mapping.

The recommendation is to use the long format where more information is provided as shown in the
number 3 example below. The number 1 and 2 examples are not recommended.

For example, AttributeX can be mapped to the User Data 2 field in the Item Revision master form in the
following three ways:

1. AttributeX : IRM.user_data_1

2. AttributeX : ItemRevision.GRM(IMAN_master_form) .user_data_2

3. AttributeX : Itemrevision>GRM(IMAN_master_form, Item Revision master) .user_data_2

Note:
This is the preferred method of mapping.

If you mapped it as shown in number 3, then Integration for I-deas can obtain the type information from
Teamcenter without having to create the dummy objects.

The query of the attribute information for an attribute type (Item type plus dataset type) is performed
once per session so the performance impact occurs once in a session for a given combination.

Attribute Customization User Exits

There are user exits available to allow you to customize the mapping of I-deas user attributes during
checkin and checkout from Teamcenter. These user exits are:

• IDSUSER_checkin_attrmap

• IDSUSER_checkout_attrmap

The ids_user_exits.c file contains information about using the user exits. This file is delivered as part of
the Integration for I-deas installation kit.

See the Teamcenter ITK manual for information on how to modify user exits, compile the source, link a
new library, and replace the default library that is shipped with Integration for I-deas.

See the Integration for I-deas Data Migration Reference Guide for customization related to migration
and data sharing.

4-46 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Change Ownership and Right To Modify For Datasets

Change Ownership and Right To Modify For Datasets

You can change ownership of Items in Teamcenter from the Item level to the dataset level. This allows
you to have individual ownership (and corresponding right to modify) of datasets within an Item and
Item Revision. Each dataset can have a different site ownership. This can also be helpful when migrating
items from I-deas where you don't want all datasets to be owned by the external owning user.

For example, an I-deas part and drawing of that part are in the same Item Revision. Since the right to
modify is at the dataset level, the part and drawing can be exported with different intent, either for
reference or modification. With Item level right to modify, the part and drawing would have to be
exported with the same intent.

This functionality is implemented by default in Integration for I-deas 5.1, but can be applied with the
ideas_rtm_util utility to items in Teamcenter where previous versions of Integration for I-deas have
been used.

The following preferences are applicable to this functionality:

• IDEAS_use_item_level_right_to_modify
Specifies whether the Item level or dataset level of ownership (right to modify) is used.

• IDEAS_set_latest_dataset_right_to_modify_only
Specifies whether the datasets under all Item Revisions or only the latest Item Revision has the
owning user set to the I-deas external owning user when using the dataset level method for
ownership. The method of ownership is set in the preference
IDEAS_use_item_level_right_to_modify described above.

For additional information on these preferences, see chapter , Preferences.

I-deas Right to Modify Utility

This utility allows you to transition from the Item level of ownership to the dataset level. If you have
upgraded your installation to Integration for I-deas 5.1 and want to use the dataset level of ownership
(the default for version 5.1), then you can use this utility to move existing Items to the dataset level of
ownership also.

Each Item specified by the utility that is owned by the external owning user has the owning user set to
the specified user. This occurs for all datasets under the Item except for I-deas datasets which remain
under the external owning user.

Note:
You can only change ownership for items owned by the external owning user.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-47
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

Note:
The utility can be run only by a Teamcenter system administrator.

To run the utility, enter the following command at the directory %Teamcenter_ROOT%\bin:

ideas_rtm_util [-u=user id —p=password –g=group] —item_id=item ID —owner=user

ID

4-48 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Working in Multi-Site Collaboration

The variable definitions are:

Variable Definition Comments

-u Teamcenter user ID. The If a user ID is not provided with the –u variable, the
specified ID must have operating system name is used. This is consistent
Teamcenter system with an autologin.
administrator privileges.

-p Teamcenter password If a password is not provided with the –p variable, a

associated with the user ID. NULL value is used for the password.
If the –p variable is not used, the user ID is used for
the password.

-g Teamcenter group If a group is not provided with the –g variable, the

associated with the user ID. user's default group is used.
Typically, the group is dba.

-item_id The item ID or list of item You can use wildcards in the variable. A list of item
IDs to process IDs is provided in a text file.

-owner The user ID to change

ownership to.

-h Displays help for the utility.

Working in Multi-Site Collaboration

If you are performing migration or doing data sharing in a Multi-Site Collaboration environment, see the
Migration and Data Sharing in a Multi-Site Collaboration Environment chapter in the Integration for I-
deas Data Migration Reference Guide.

Enabling Checkin/Checkout

To enable checkin/checkout between Integration for I-deas and Teamcenter in a Multi-Site Collaboration
environment, the following Teamcenter preferences must be set:

• TC_remote_checkin_assy_option=1
This preference is set to 0 by default.

Multi-Site Relationship Types

When importing items from a remote Teamcenter site using Multi-Site Collaboration, select the
appropriate I-deas relationship type to also import any related items. This lets you automatically import
associated items without having to manually search, select, and import the associated items.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-49
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

When using Multi-Site Collaboration, in the Import Remote Options window, select the Advanced tab.
The Relationship Options list displays the relationship type options (which is the type of item you are
importing). For example, if you are importing a FEM, select the IDEAS_FEM relationship type to import
the FEM and the associated part.

• IDEAS_ACCONTEXT

• IDEAS_ACSOURCE

• IDEAS_DRAWING

• IDEAS_DWGSET

• IDEAS_FEM

• IDEAS_SOURCE

• IMAN_Rendering

• IMAN_manifestation

• IMAN_specification

Alternatively, you can define the following preferences to include the above relations. This would ensure
the above relations are included during export or transfer from the site. However, the use of these
preferences for I-deas relationship types causes problems for I-deas migration and data sharing.

If I-deas package file import or export or TDM migration is required in a Teamcenter Multi-Site context,
neither of these preferences should include I-deas_* relationships. Instead, only the advanced tab on
the Teamcenter Import Remote Options dialog box should be used to specify the I-deas relationships.

• TC_relation_required_on_export

• TC_relation_required_on_transfer

Remote Import Relationship Types

All of the relationship types above should be selected when remote importing with Multi-Site
Collaboration to ensure that all of the objects necessary to complete the I-deas data model are imported.
For example, if the IMAN_Rendering relationship is not specified, the Direct Model dataset will appear
as a stub in the local site, and send to I-deas will display an error message.

Remote Import Revisions and Versions

All of the revisions and versions should be selected when remote importing an I-deas dataset with Multi-
Site Collaboration. If you do not select all of them, you could get an error during the send to I-deas

4-50 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Preferences For Automatically Selecting Relationship Types

operation. To send an assembly/drawing/drawingset/FE model to I-deas at the remote site, Integration

for I-deas requires access to all versions referenced by the item being sent, when the item was last saved
to Teamcenter.

Preferences For Automatically Selecting Relationship Types

The following Teamcenter preferences automatically select the proper relationship types. Ensure these
are set in Teamcenter:

• PORTAL_SESSION_TC_dataset_refs_export=TRUE
Relationships for dataset options for save all file, copy, and paste.

• PORTAL_SESSION_TC_relation_export=

IMAN_master_form
IMAN_specification
IMAN_manifestation
IMAN_Rendering
IDEAS_FEM
IDEAS_ACSOURCE
IDEAS_ACCONTEXT
IDEAS_DWGSET
IDEAS_DRAWING
IDEAS_SOURCE

Relationships included during remote import from Portal.

• TC_relation_required_on_export=

IMAN_master_form
IMAN_specification
IMAN_manifestation
IMAN_Rendering
IDEAS_FEM
IDEAS_ACSOURCE
IDEAS_ACCONTEXT
IDEAS_DWGSET
IDEAS_DRAWING
IDEAS_SOURCE

Default settings.

• TC_relation_required_on_transfer=

IMAN_master_form
IMAN_Rendering
IMAN_manifestation

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 4-51
© 2020 Siemens
 4. Using Integration for I-deas: Working With Modeling Data

IMAN_specification
IDEAS_FEM
IDEAS_ACSOURCE
IDEAS_ACCONTEXT
IDEAS_DWGSET
IDEAS_DRAWING
IDEAS_SOURCE

• In addition, you can also set the following preference to help manage the delivery of large I-deas
assemblies. The default batch size is 1000. You can increase or decrease this to suit your network
loading comfort level.

IDEAS_giman_util_batch_size=1500
Specifies the number of objects for each batch (a new process is created for each batch). The
batch size must be a positive integer. This is useful when processing thousands of objects
because it helps avoid memory and disk space shortage problems.

Note:
Giman_util is the former name of data_share, as in the data_share utility.

4-52 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 5. Using Integration for I-deas: Sending
Modeling Data From My Teamcenter to I-
deas
I-deas Version Issues When Accessing I-deas Data ───────────────── 5-2
I-deas ─────────────────────────────────────────────── 5-3
I-deas With Integration for I-deas ─────────────────────────────── 5-3
I-deas Package Imported into Teamcenter ───────────────────────── 5-3
Working With Item Revisions ────────────────────────────── 5-3
Export Directory Name Length ───────────────────────────── 5-4
Unsupported Characters Handled During Send to I-deas ───────────── 5-4
Sending I-deas Modeling Data to I-deas ─────────────────────── 5-5
Sending Related Drawings ─────────────────────────────────── 5-7
Automatically Send an Item to a Bin ───────────────────────────── 5-7
Increasing Performance When Sending Items to I-deas ────────────────── 5-9
HAM Medic ─────────────────────────────────────────── 5-10
Send to I-deas From a Remote Site ───────────────────────────── 5-11
Detecting Referenced But Modified Condition During Send To I-deas ──── 5-11
Items Modified in Structure Manager ──────────────────────── 5-12
Assembly in a Model File ─────────────────────────────────── 5-12
Assembly Outside of a Model File ────────────────────────────── 5-13
ACF Relations ────────────────────────────────────────── 5-13
File Status Options ──────────────────────────────────── 5-13
Changing the Checkout Status of an Item ───────────────────── 5-15
Changing the Status of Pruned or Faceted Parts ───────────────── 5-16
Version Numbering for NX assemblies and external parts ─────────── 5-16
Canceling a Checkout ────────────────────────────────── 5-17
Sending NX Parts to I-deas ─────────────────────────────── 5-17
Default Functionality ───────────────────────────────────── 5-19
Sending NX Assemblies to I-deas ─────────────────────────── 5-19
Sending Revisions of the Same Part to I-deas ─────────────────── 5-20
I-deas Derived Part and NX Part Are Not Synchronized ───────────── 5-21
Integration for I-deas Window ──────────────────────────────── 5-21
NX Source Part Version and Revision Attributes ───────────────────── 5-22
Updating ───────────────────────────────────────────── 5-22

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 5. Using Integration for I-deas: Sending
Modeling Data From My Teamcenter to I-
deas
This chapter describes how to use My Teamcenter to send saved parts, assemblies, drawings, and FE
models to the I-deas application for reference or modification.

Modeling data saved in Teamcenter datasets can be transferred to I-deas for reference or modification.
You can transfer multiple datasets; the dependent objects of each dataset are also transferred.

This section describes considerations that should be taken into account when sending modeling data
from Teamcenter to I-deas.

Note:
For additional information on sending modeling data in a Multi-Site Collaboration environment,
see the Preparing for Data Migration chapter in the Data Migration Reference Guide.

When sending modeling data to I-deas, it is important to consider the dependency and version
implications of your selections. The following list outlines these considerations for various I-deas data
types:

• I-deas parts and external parts

If you send an I-deas part to I-deas, by default it goes as precise geometry and as a referenced part,
though you do have the checkout option. In an assembly context you have pruned and faceted
options for parts, and you have faceted or precise options for external parts.
An external part or external assembly, in the context of Integration for I-deas, is any part or assembly
that is authored by a CAD tool other than I-deas. An external part is represented by a JT dataset in an
item revision that has no BOMView Revision (BVR). If there is a BVR, it is an external assembly. If you
send an external part by itself (not in the context of an assembly), the external part is sent precise. To
send an external part by itself you must use the I-deas menu in My Teamcenter.

• Assemblies
When you select an assembly dataset, all component parts and subassemblies are sent to I-deas.
Components of assemblies, both parts and subassemblies, can be modified and saved in Teamcenter
outside the context of the main assembly. Therefore, it is possible for a newer version of a component
to exist in Teamcenter than that originally saved with the assembly. When you send the main
assembly to I-deas, the newest version of the component is sent rather than the version originally
referenced by the main assembly.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-1
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

Note:
This behavior does not apply to legacy assemblies. For more information, see chapter , Using
Integration for I-deas: Managing Assembly Structures.

• Drawings
When sending drawing datasets to I-deas, any part or assembly referenced by the drawing is also
sent. It is possible that a referenced dataset may have been modified and saved in Teamcenter, in
which case a newer version of the referenced dataset may exist than that originally saved with the
drawing. In this case, the latest version of the referenced parts or assemblies is sent to I-deas.

• Drawing sets
When drawing sets are sent to or from Teamcenter, all of their member drawings are also sent.
Drawing sets are handled like assemblies where the drawing set is dependent on the member
drawings. However, you can't modify drawing sets in Teamcenter Structure Manager.

• FE Models
When sending FE models to I-deas, any part referenced by the FE model is also sent. It is possible that
a part may have been modified and saved in Teamcenter after it was saved as a reference to the FE
model, in which case a newer version of the referenced part may exist than that originally saved with
the FE model. In this case, the original version of the referenced part is sent to I-deas along with the
model.
This behavior can be overridden by modifying the value assigned to the IDEAS_fem_send_latest_ref
preference. For more information, see chapter , Preferences.
Versions of individual parts that have been sent to I-deas can be updated using the Update
command. For more information, see chapter , Using Integration for I-deas: Updating and
Synchronizing Data.

• NX Parts
When sending NX parts to I-deas, a derived I-deas part is created that maintains association with the
NX part. The derived part has a checked-out status in the Integration for I-deas window although it is
a new part. The FEM created has associativity to the derived I-deas part. If the NX source part is
revised, the derived I-deas part becomes out-of-date. The FEM maintains associativity when the
derived I-deas part is updated.

Note:
Starting with Integration for I-deas 6.1 you can no longer send NX parts to I-deas to create new
derived I-deas parts. However, previously created, derived I-deas parts can be sent to I-deas.

5-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 I-deas

I-deas Version Issues When Accessing I-deas Data

I-deas

I-deas created models are not backwards compatible to previous versions of the software. For example,
if you create a model in I-deas 11, it must be opened in I-deas 11. If you try to open it in I-deas 10, the
part won't open and you'll get an error message in the List region.

I-deas With Integration for I-deas

In addition, I-deas used with Integration for I-deas is not backwards compatible even if the same version
of I-deas that created the part is used to open it. For example, you create a part in I-deas 10, and use I-
deas 11 and Integration for I-deas to import the part into Teamcenter. The part must now be opened in
I-deas 11. The part can't be opened in I-deas 10, even though it was created in I-deas 10. An error
message is displayed in I-deas and Teamcenter explaining that the import into I-deas failed. The
following message is displayed in the I-deas List region:

I-deas cannot access the data. The file has a format that is not
backwards compatible with the current software release.

I-deas Package Imported into Teamcenter

This applies to data created when an I-deas package is imported into Teamcenter. For example, you
import an I-deas package with I-deas 11 and Integration for I-deas. The data in the package can only be
accessed in I-deas 11 since that was the I-deas version used when the package was imported, even if the
package was created using I-deas 10.

This also applies to I-deas data items exported with Integration for I-deas and I-deas 11. They cannot be
imported into an I-deas 10 site even if all of the data files had been originally created using I-deas 10.

Note:
We recommend that the entire Teamcenter installation, including all sites and all users, be
upgraded to the next major release of I-deas at the same time.

Working With Item Revisions

The following functionality applies when working with Item Revisions:

• Parts and assemblies must be in the latest Item Revision to be sent for checkout.

• You must have read access to the Item Revision where the datasets are being checked out. An I-deas
drawing, FEM, or drawing dataset exists in an item revision and you do not have read access to that
Item Revision. However, you do have read access to the earlier Item Revision. If you send a dataset to
I-deas from the earlier revision for checkout, the checkout will fail. This is because you do not have

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-3
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

read access to the later revision. Integration for I-deas cannot determine if a dataset of the same type
exists in a later revision.

• A consistent dataset contains all required I-deas named reference objects. An empty dataset has no I-
deas named reference objects. Empty datasets are generated in Teamcenter during top down design.
If the empty dataset is an I-deas part or assembly and there is no consistent dataset of the same type
in the Item, the empty dataset can be sent to I-deas. However, sending empty drawings, FEMs, and
drawing sets to I-deas is not supported.
Integration for I-deas determines if there is a consistent dataset of the same type in any previous Item
Revisions. The Item Revisions that you do not have read access to and that have no impact on the
determination are skipped.
If an inaccessible Item Revision (where you do not have read access) does contain a consistent dataset
of the same type, there is a data corruption. In this case, the Send to I-deas functionality works and
propagates the data corruption. However, the likelihood of this occurring is low. The alternative is to
require read access to every Item Revision and this is not practical.

Export Directory Name Length

I-deas has an 80 character limit for file name length including the directory path for the file. The part file
name is determined to be 41 characters maximum with 39 characters for the remaining file name
length. If the file name length is over 80 characters, the send operation fails.

To set the directory path location to 39 characters maximum, perform one of the following:

• Set the path specified by the TCExportDir variable in the client_specific.properties file. The file is
located in the Teamcenter Rich Client installation.

• Modify the startup script, IDNPortal.bat (Microsoft® Windows®) or idn_start_portal (Unix), located
in the Teamcenter Rich Client installation. Modify the script by adding the – D parameter with the
IDEAS_FILES_EXPORT_DIR variable set to the directory path.
For example, add the following (entered on one line) to the startup script after other –D parameters
in the file:

start Teamcenter.exe %* %IDEAS_APP_INVOKE% -vmargs -Djava.io.tmpdir=

"%TCII_TMP%" –DIDEAS_FILES_EXPORT_DIR=C:\temp

Note:
The location specified in the startup script supersedes the location specified by the TCExportDir
variable.

Unsupported Characters Handled During Send to I-deas

Some characters, such as the colon (:), are allowed in Teamcenter for Item IDs and item names but are
not supported in I-deas. This can cause a problem when sending an item to I-deas. The following

5-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Sending I-deas Modeling Data to I-deas

preference (in the Teamcenter preferences) modifies the Item ID and item name for I-deas while
preserving the original Item ID and name in Teamcenter.

• IDEAS_name_replace_invalid_chars
Characters in the Item ID and item name that are not supported by I-deas are replaced with the
underscore (_) character when an item is sent to I-deas. The Item ID and item name are shown with
the underscore in the Integration for I-deas window, but in Teamcenter they are shown with the
original Item ID and name. The character replacement is a temporary modification to enable the item
to be used in I-deas.
If a drawing is created for a part in I-deas that has had characters replaced with underscore
characters, the drawing part number/name also has the underscore characters in I-deas, but those
characters are replaced to match the part when the drawing is saved in the same Item Revision as the
part in Teamcenter.
Characters not supported by I-deas include:

comma ,

exclamation point !

dollar sign $

asterisk *

at sign @

quotation marks “

question mark ?

colon :

seimcolon ;

Valid values:

TRUE – Characters are replaced with underscores for items sent to I-deas that contain characters
in the Item ID and name not supported by I-deas.

FALSE – Item ID and item name are not modified when an item is sent to I-deas.

Default value:

FALSE

Sending I-deas Modeling Data to I-deas

You can send modeling data to I-deas using the Send to I-deas dialog window.

There are three ways to send datasets to I-deas:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-5
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

Note:
Choose the appropriate options in the Integration for I-deas Preferences dialog box to enable
sending of specific datasets (for example, part and assembly) when an Item or Item Revision is
selected, or Ham Medic.

• In the My Teamcenter tree, select the Item, Item Revision, or I-deas dataset that you want to send to I-
deas, pull down the I-deas menu, and choose the Send to I-deas option. Optionally, you can select
the Item, Item Revision, or I-deas dataset and right-click Send To→Send to I-deas.

• In the My Teamcenter tree, select the Item, Item Revision, or I-deas dataset that you want to send to I-
deas, pull down the File menu, and choose the Open option.

• Double-click the I-deas dataset.

The system displays the Send to I-deas dialog window.

Note:

If you are exporting an assembly to I-deas, it is important that any changes to the revision rule
be made before you mark the individual components. Revision rules affect the structure of the
assembly; therefore, when a new revision rule is selected, the dialog window is refreshed and
all export option selections are lost.
The default revision rule is determined by the Teamcenter preference TC_config_rule_name.

Note:
The send to I-deas operation fails if the My Teamcenter Referencers panel is active. Close the
Referencers panel by selecting a different tab, then choose the send to I-deas operation.

• Optionally, change the revision rule for the assembly.

a. Click the Change Revision Rule button.

The system displays the Revision Rule Selection dialog window.

b. Select a revision rule from the dropdown list.

c. Click the OK button.

• Optionally, expand the nodes and select the appropriate status options, such as check out,
reference, prune. For more information, see File Status Options, later in this chapter.
By default, the datasets are sent to the Main bin in I-deas.

• Optionally, select a destination bin from the Destination Bin list.

5-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Sending Related Drawings

This list shows all bins that exist in the current model file. All files selected for export are sent to the
same bin. If you are exporting a file that is already in the model file in a different bin than the one
specified, the item remains in its current bin.

• Optionally, create a new bin and use it as the destination bin. Select Create Bin from the
Destination Bin list.

• Optionally, if checking out items, enter information in the Check-out History area. The change ID
and comments apply to all objects being checked out.

• Click the OK button.

The selected objects are sent to your active I-deas session. The status of the objects is reflected in the
Integration for I-deas window.

Sending Related Drawings

To send related drawings with the part or assembly you are sending, choose one of the Related
Drawing Options on the Send to I-deas dialog box. The related drawings sent are not displayed in the
Send to I-deas window, but a message is displayed listing the drawings that were sent. This is also
written to the TB.log file. In addition, you can click Save As on the message dialog box to save the list to
a file.

If related drawings cannot be sent, an error message is displayed listing the drawings and applicable
information. This is also saved to the TB.log file and you can use Save As to save the information to a
file.

Related drawings are sent for all of the items in the Send to I-deas dialog box. Drawings that reside in a
different site are not remote imported. Only the latest revision of a related drawing is sent.

The options are:

• No Related Drawings
This option does not send any related drawings. It is the default.

• Reference Related Drawings

This option sends related drawings as reference.

• Checkout Related Drawings

This option sends related drawings as checked out.

Automatically Send an Item to a Bin

When an part/assembly/drawing/drawing set is sent to I-deas it can automatically be sent to a specific

bin based on the attributes of the part/assembly/drawing/drawing set. The following preference is used:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-7
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

IDEAS_send_option_bin_attributes
Valid values:

Comma separated list of attributes that define the bin name during Send to I-deas.

TC_GROUP
This is an optional value included if the owning group of part/assembly/drawing/drawing is
added to the bin name.

The preference is defined with attribute names. If the attributes of the part match the attributes of the
preference a bin is created for the item. The name of the bin is the value of each attribute separated by a
hyphen. If an attribute is not present in the part, it is skipped and the next attribute is used for the
name. If the bin does not exist, a bin is automatically created. If no part attributes match the preference
attributes, the Destination Bin is used.

Note:
The attributes in the part must have the master mapped as iman or both.

The attribute TC_GROUP defines the owning group of the item in Teamcenter. It can be added to the
preference list of attribute names. If the attribute is present in the preference, the owning group of the
part/assembly/drawing/drawing is added to the bin name.

Note:
This preference is not applicable for FEMs because FEMs always go to the same bin as its related
part.

The following example uses this preference:

The following attributes are defined for IdeasAssembly:

Weight, Height, Color. The master for these attributes is iman or both.

The values for the attributes in the assembly are:

Weight=10

Height=50

Color=Red

5-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Increasing Performance When Sending Items to I-deas

Note:
The owning group of the assembly is dba. Therefore the TC_GROUP attribute evaluates to
dba.

The preference is defined as follows:

IDEAS_send_option_bin_attributes=Weight,Color,TC_GROUP

When the assembly is sent to I-deas, the following new bin is created:

10_Red_dba

Increasing Performance When Sending Items to I-deas

When an item is sent to I-deas, the CAD and CPD files are downloaded to the local client and get deleted
after the send to I-deas operation has completed. You can modify this functionality to keep these files
instead of deleting them (cache the files locally). Subsequent checkout operations will check the local
location for the files, thereby increasing performance after the first checkout has been performed.

To enable caching of the files, perform one of the following:

• Set the following preference in the Teamcenter preferences:

IDEAS_send_option_enable_file_cache=TRUE

• Check the following option in the Options dialog (Edit→Preferences in the Integration for I-deas
window):

Enable caching of files during Send to I-deas

You can also define where the cached files are located. The location must already exist and have read/
write privileges for the Teamcenter Rich Client users. By default, this is the Teamcenter Rich Client temp
directory. To change the location, perform one of the following:

Note:
The directory name for the location of the cache files can be 39 characters maximum.

• Change the location specified by the TCExportDir variable in the client_specific.properties file. The
file is located in the Teamcenter Rich Client installation.
• Modify the startup script, IDN_PORTAL.bat, located in the Teamcenter Rich Client installation. Modify
the script by adding the – D parameter with the IDEAS_FILES_EXPORT_DIR variable set to the
location for the cached files.
For example, add the following (entered on one line) to the startup script after other – D parameters
in the file:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-9
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

start Teamcenter.exe %* %IDEAS_APP_INVOKE% -vmargs -Djava.io.tmpdir=

"%TCII_TMP% –DIDEAS_FILES_EXPORT_DIR=”D:\ideasdownload”

The location specified in the startup script supersedes the location specified by the TCExportDir
variable.

Note:
If caching is enabled, Integration for I-deas doesn't delete the cached files. You have to periodically
clear out the directory designated for cache.

HAM Medic

HAM Medic is an I-deas utility used to clean bad HAMs from I-deas data. The I-deas History Access
Mechanism (HAM) adds history data to I-deas parts, assemblies, and so on. After a period of time these
HAMS can accumulate and cause problems for I-deas data. You might experience significant
performance degradation during send to I-deas, or the operation could hang indefinitely. Periodically,
this data needs to be cleansed from I-deas items.

The HAM Medic utility is run during the send to I-deas process on all checked out and referenced items
sent to I-deas. To enable this functionality, choose the following option in the Teamcenter Integration
for I-deas Preferences dialog box (Edit→Preferences in the Integration for I-deas window):

Run HAM Medic

You can also enable the functionality by setting the following preference. This preference is a user and
site preference and is set to FALSE by default:

IDEAS_run_hammedic=TRUE

Send to I-deas performance is affected when using this utility so it should be used only when required.
When HAM Medic is run, the output is written to the TB.log file.

If HAM Medic is run during export to TDM, the preference IDEAS_run_hammedic must be set to TRUE
as a site preference. The output is written to the export log file if available, otherwise it is written to the
TB.log file.

The HAM Medic command is in the ham_medic.bat file located in the Portal directory. The command
can take multiple options and you can add/change options to get different results. The default option
used by Integration for I-deas is –v (verbose). For additional information on HAM Medic including
options available, see the I-deas documentation set.

5-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Send to I-deas From a Remote Site

Send to I-deas From a Remote Site

When an item is sent to I-deas, if certain relationships exist, they must not reference a stub. The
following table lists those relationships (cannot reference a stub) for an Item Revision or dataset for each
item type.

Item Type Item Revision Dataset

Part IMAN_Specification IDEAS_ACCONTEXT

IMAN_Rendering (if IDEAS_ACSOURCE
IDEAS_part_create_jt preference is
true)

Assembly IMAN_specification N/A

IMAN_manifiestation (if
IDEAS_assembly_create_jt preference
is true)
IMAN_Rendering (if
IDEAS_assembly_create_jt preference
is true)

Drawing IMAN__specification IDEAS_DRAWING

IMAN_capture (if
IDEAS_drawing_create_cgm
preference is true)

FEM IMAN_specification IDEAS_FEM

Drawing Set IMAN_specification IDEAS_DWGSET

UGMASTER IMAN_specification IMAN_Rendering

Detecting Referenced But Modified Condition During Send To I-deas

The following preference (in the Teamcenter preferences) detects and warns when a referenced but
modified condition exists within an assembly being sent to I-deas:

IDEAS_send_option_check_refmod

When the preference is set to TRUE, If the data being sent to I-deas will result in a referenced but
modified condition later when the assembly is saved to Teamcenter, the warning dialog is displayed.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-11
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

The preference detects when the product structure sent to I-deas contains a different hierarchy than the
as-saved model. This indicates that an item in the product structure has been modified but is not
reflected in the existing as-saved model, resulting in a referenced but modified condition.

The warning dialog states that a reference but modified condition has been detected and asks if you
want to checkout the affected assembly components. If the components are checked out, you can
update the assembly in I-deas to eliminate the referenced but modified condition.

Note:
The default for this preference is FALSE.

Note:
This preference is applicable when you perform send to I-deas from Teamcenter's My Teamcenter
and Structure Manager.

Items Modified in Structure Manager

Assemblies in an I-deas model file modified in Teamcenter Structure Manager are not recognized as
modified by I-deas. I-deas only recognizes the original assembly. However, these assemblies are
recognized as modified in Integration for I-deas. The modified assembly has a Structure Manager icon
next to it in the Integration for I-deas window.

Assemblies that are not in an I-deas model file and are modified in Teamcenter Structure Manager are
recognized by I-deas when sent to I-deas. They are shown as not requiring updating.

Drawings are not recognized as modified when an assembly in the model file or outside the model file is
modified in Structure Manager.

Assembly in a Model File

If you have an assembly that is in a model file and you edit the assembly in Structure Manager and send
the assembly to I-deas, I-deas does not show the edited product structure. The original assembly is
shown. However, Integration for I-deas recognizes the Structure Manager edit and displays the Structure
Manager icon on the assembly in the Integration for I-deas Integration for I-deas window. If there is a
drawing associated with the assembly, it also gets the Structure Manager icon. You can't update the
assembly or drawing in the Integration for I-deas window because I-deas isn't aware of any changes that
need to be updated (nothing was changed in I-deas).

To work around this problem, delete the original assembly in I-deas before sending the Structure
Manager-modified assembly to I-deas. To update the drawing, see the section below.

5-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Assembly Outside of a Model File

Assembly Outside of a Model File

If you have an assembly that is not in the model file and you edit the assembly in Structure Manager and
send the assembly to I-deas, I-deas shows the edited product structure. The Structure Manager icon is
displayed on the assembly in the Integration for I-deas window. Any associated drawing also gets the
Structure Manager icon, however, the drawing doesn't show the new product structure. You can't
update the assembly or drawing because I-deas isn't aware of any changes that need to be updated (this
was new to the model file).

To work around this problem, change the assembly and associated drawing to checkout status, then
make a slight change to the assembly, such as suppressing a component in the assembly, to cause it to
be out-of-date. Then update the assembly. Check in the assembly and perform a Find out of date items
in the Integration for I-deas window; the assembly Structure Manager icon is removed. Since the
assembly was changed in I-deas, you can update the drawing, check it in, and perform a Find out of
date items to get the Structure Manager icon removed for it. The result is a new assembly product
structure with an updated drawing that can be checked into Teamcenter.

ACF Relations

In Structure Manager, if an assembly contains an item that is a source for an associative copy feature
(ACF), the BOM line for the ACF item has the note IDEAS ACR SOURCE. This indicates that it has an
associative copy relation and it is the source. If you try to delete that item, a warning message is
displayed informing you that ACF relations will be lost.

Note:
This does not apply to legacy data.

This functionality is applicable when the following preference is set:

IDEAS_acr_create_occ_note=TRUE

File Status Options

When sending files to I-deas, you can mark the selected or dependent datasets to assign the status they
will have in the I-deas session or to define the type of data to be sent. Table 5-1 describes the status
options and icons related to datasets being sent to I-deas.

Table 5-1. Export Marking Options

Option Description

Check Out Reserves exclusive access to the dataset and any associated Teamcenter
objects. While you have the object checked out, no one else can modify

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-13
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

Option Description

it. You can choose this option only if the object is not already checked
out to another user.
When you check an object out of Teamcenter, the dataset version is
increased by one. The new version number displays next to the dataset
in the Integration for I-deas window and is reflected in your I-deas
model file, but is not displayed in the My Teamcenter tree until you
check the dataset back in to Teamcenter.

Reference Specifies that the objects sent to I-deas are for reference only and
cannot be modified. A pointer, or reference, to the selected version is
maintained. The system displays an asterisk (*) next to the reference
when it becomes out-of-date (the original has been revised).

Prune Specifies that only the metadata associated with the object is sent to I-
deas.

Faceted Specifies that if a JT representation exists for the dataset, it is sent to I-

deas and read in its faceted form.

Precise Specifies that if a JT representation exists for the dataset, the JT file is
sent to I-deas and read in its precise, Non-Uniform Rational B-Splines
(NURBS) form.

Not all of the options shown in table 5-1 can be applied to all data types.

Table 5-2 shows the dataset types and their applicable options. Default options are indicated by an
asterisk (*).

Table 5-2. Export Options by Dataset Type

Dataset Type Check Out Reference Prune Faceted Precise

I-deas assembly X X*

I-deas part X X* X X X*

I-deas drawing X X*

I-deas FE model X X*

External assembly X

External part X X ** X **

By default, assemblies, FEMs, and drawings are sent to I-deas as reference objects and cannot be
modified. Parts are sent as reference objects (by default), unless it is an external part (not part of an
assembly) where a JT file exists, then it is sent as precise (reference). If it is part of an assembly, it is sent

5-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Changing the Checkout Status of an Item

as faceted (reference) as part of the assembly. If the part is a derived I-deas part (derived from a NX
part), its status is check out by default. If it is sent from Structure Manager with the part selected, it is
sent as pruned.

There are several exceptions to the general export option rules shown in table 5-2, as follows:

• If a FE model is sent to I-deas, the part that it references cannot be marked as pruned or faceted
because I-deas requires complete CAD data for parts in a FE context. In such cases, the Prune and
Faceted options are not displayed.

• If a version of a dataset other than the latest Teamcenter version is selected for export, it cannot be
checked out. This can occur when sending FE models or legacy assemblies (pre-I-deas 8). In such
cases, the Check Out option is not displayed.

• If an external part is sent to I-deas in an assembly, it is sent faceted by default. If an external part is
sent by itself to I-deas it is sent precise, with no other option.

In the previous examples invalid options are removed from the dialog window. However, there may be
situations in which the option is available, yet deemed invalid when the system sends the objects to I-
deas, in which case the objects are sent in a reference-only state. This is particularly true of the Check
Out option. Some of the conditions under which the Check Out options are available but invalid are as
follows:

• If the I-deas dataset or one of the dependent objects is currently checked out of Teamcenter, either by
you or another user.

• If you do not have the Teamcenter privileges required to check out the dataset or any of its dependent
objects.

• If you attempt to send a dataset for which a later revision exists.

Changing the Checkout Status of an Item

The status of datasets displayed in the Integration for I-deas window can be changed from reference-
only to checked-out or new, provided that the following conditions are met:

• The item must be the latest version and, if there are revisions, the latest revision.

• The item is not an external part or assembly.

• The corresponding I-deas dataset or an associated object is not already checked out. The items must
be reference items. If they're checked out, right-click the selected datasets and choose Cancel Check-
out from the popup menu, or choose Cancel Check-out from the Manage Bins menu.

• You have checkout permissions on the selected dataset and its related objects.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-15
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

Perform the following steps to change checkout status of a dataset:

1. Select the datasets in the Integration for I-deas window.

Note:
When changing the status of a dataset to new, select the dataset in top-down or bottom-up
heirarchy, not random heirarchy. This avoids a possible reference modification warning
message during the change to new operation.
In top-down heirarchy (recommended), first select the assembly, then subassembly, then the
dataset. Bottom-up heirarchy is dataset, then subassembly, then assembly. Do not randomly
select the dataset, then assembly, then subassembly or use another random order.

2. Right-click the selected datasets and choose Change to Check-out or Change to New from the
popup menu. Alternatively, you can select the datasets and choose Change to Check-out or
Change to New from the Manage Bins menu.

Changing the Status of Pruned or Faceted Parts

The status of parts that are sent to I-deas in a pruned or faceted state can be changed to either checked-
out or reference status. Change a part from pruned or faceted status to reference status to view the
geometry in I-deas. Change the status to checked-out to modify the data.

Perform the following steps to change the status of pruned parts:

1. Select the datasets corresponding to pruned or faceted parts in the Integration for I-deas window.

2. Choose Unprune from the Edit menu or right-click and choose Unprune from the popup menu.
The system displays the selected datasets in the Send to I-deas dialog window.

3. Set the status of each dataset by either choosing the Check Out option or leaving all options blank.
Leaving the options blank changes the status to reference.

Version Numbering for NX assemblies and external parts

The version numbering for NX assemblies and external parts (NX parts, JT datasets) is different than the
version numbering for I-deas items.

Note:
When you check an item out of Teamcenter, the dataset version is increased. The new version
number is in the model file, but is not reflected in Teamcenter until you check the dataset back in.

5-16 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Canceling a Checkout

For NX assemblies and external parts (NX parts, JT datasets), the version number is calculated by adding
together the latest version number of that revision and each previous revision. For example, you have JT
datasets in Teamcenter as follows:

• Rev A; version 1.
When you send it to I-deas, it becomes Rev A; version 1

• Rev A; version 1, Rev B; version 2.

When you send Rev B to I-deas, it becomes Rev B; version 3 (1+2)

• Rev A; version 1, Rev B; version 2, Rev C; version 3.

When you send Rev C to I-deas, it becomes Rev C; version 6 (1+2+3)

Canceling a Checkout
If you check out an item but do not modify it, you can cancel the checkout lock.

Perform the following steps to cancel a checkout:

1. Select the checked-out datasets in the Integration for I-deas window.

2. Right-click the selected datasets and choose Cancel Check-out from the popup menu. Alternately,
you can select the datasets and choose Cancel Check-out from the Manage Bins menu.
The system displays the Cancel CheckOut dialog window.

3. Click the Yes button to proceed.

The checkout lock is removed and the dataset status is changed to referenced-latest.

Sending NX Parts to I-deas

While Teamcenter may contain external items (items not created in I-deas), you can send an NX part to
I-deas as a JT file, or as a derived I-deas file that has been previously created. The derived I-deas file
allows you to use FEM capabilities. This interoperability between NX and I-deas is brokered by
Integration for I-deas.

Note:
Starting with Integration for I-deas 6.1 you can no longer send NX parts to I-deas to create new
derived I-deas parts. However, previously created, derived I-deas parts can be sent to I-deas.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-17
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

The following functionality applies to interoperability:

• The derived I-deas part is a geometric copy of the NX part and I-deas retains association with the NX
part in Teamcenter.

• The interoperability is one way; you can only send parts from NX to I-deas, not from I-deas to NX.

• The derived I-deas part is automatically put on the workbench.

• The derived I-deas part has the item name and item ID of the NX dataset, by default. You can rename
and renumber the part in the Integration for I-deas window once it is in the I-deas model file.

Note:
You cannot change the name or item ID of the derived part in I-deas Manage Bins.

• The derived I-deas dataset version number is 1 regardless of the source NX part version.

• If you want to save the derived I-deas part as part of an assembly, you must save it to a different item.
If you save it in the same item, and you send the assembly to I-deas, only the JT representation of the
source part is sent. The item is treated as an external item.

• The I-deas→Revise and I-deas→Freeze and Create New Revision commands do not propagate the
derived I-deas dataset. To create the new derived part, send the derived part to I-deas, perform an
update source revision operation, then save the part. The new part (was derived I-deas part) is
created in a new revision.

To use this interoperability:

1. In the My Teamcenter tree, select the NX part that you want to send to I-deas.

2. Choose Send to I-deas from the I-deas menu. The Send to I-deas dialog window is displayed with
the NX part listed.

3. Select how the part is sent from the pulldown menu:

• JT – This option sends the part as an external part. The part is sent as a DirectModel (i.e., JT file).

• Part Name – This is an already existing derived I-deas part that is saved in the same ItemRevision
as the NX part (this option is not displayed if a derived I-deas part is not available). You can select
to send the derived I-deas part as a checkout by selecting the checkbox provided.

4. Click OK on the Send to I-deas dialog window.

5-18 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Default Functionality

Default Functionality

When an Item Revision contains both an NX part and an I-deas part, the I-deas part is sent by default. If
the Item Revision contains an NX part and a derived I-deas part, the derived I-deas part is sent by
default.

You can change the default by changing the values for the preferences IDEAS_send_nx_dataset and
IDEAS_send_derived_ideas_dataset, or by selecting an option from the pulldown menu on the Send to
I-deas dialog. These options let you send the NX part as an external part, send the NX part as a new
derived I-deas part, or send an existing I-deas derived part.

Sending NX Assemblies to I-deas

You can send an NX assembly to I-deas. When the assembly is sent, each of the components of the
assembly is sent individually. Geometry in the top level of the assembly (stored in the assembly dataset)
does not get sent. Since only the assembly hierarchy and positioning of the components are required,
the components can be sent pruned if the part or derived I-deas part already exists in I-deas.

Note:
Starting with Integration for I-deas 6.1 you can no longer send NX parts to I-deas to create new
derived I-deas parts. However, previously created, derived I-deas parts can be sent to I-deas.

To send an NX assembly:

1. In the My Teamcenter tree, select the UGMASTER dataset for the NX assembly that you want to
send to I-deas.

2. Choose Send to I-deas from the I-deas menu. The Send to I-deas dialog window is displayed with
each component of the assembly listed.

3. For each NX component listed, you can select how it's sent from the pulldown menu:

• JT – This option sends the part as an external part (sent as a JT file). You can select how the
external part is sent from the additional checkboxes provided:

• Precise – Send the part as precise geometry.

• Pruned – Send the part pruned from the assembly if the part already exists in I-deas. This is
also applicable if a derived I-deas part for this NX part already exists in another ItemRevision
and that is being sent to I-deas.

• Faceted – Send the part as a faceted model.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-19
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

• Part Name – This is an already existing derived I-deas part that is saved in the same ItemRevision
as the NX part (this option is not displayed if a derived I-deas part is not available). You can select
how the derived I-deas part is sent from the additional checkboxes provided.

• Checkout – Send the part with status of checkout.

• Pruned – Send the part pruned from the assembly if the derived I-deas part already exists in I-
deas.

• Faceted – Send the part as a faceted model (i.e., JT file).

4. Click OK on the Send to I-deas dialog window. The assembly components are sent to I-deas.

Sending Revisions of the Same Part to I-deas

There are two options in the Integration for I-deas Options dialog that let you control the part revisions
that are sent to I-deas:

• Replace existing revisions in model file during Send to I-deas operation

This option replaces the existing revisions in the model file when a later revision of the part is sent.

Note:
If an earlier revision of a part is sent, the model file is not updated with the earlier revision. The
existing later revision is kept in the model file.

For example, when the option is checked Yes, revision A in a model file is replaced by revision C when
revision C is sent to I-deas. Revision C exists in the model file.
For example, when the option is checked Yes, and the part doesn't exist in the model file, revisions A
and B are sent to I-deas. Revision B exists in the model file.
Parts that have the same revision but different versions that are sent to I-deas are updated to the
latest version, even if the option is unchecked (option is set to No).
To avoid unintentionally updating a part to the latest revision, such as when two parts with different
revisions and versions exist in an assembly, turn off this option (uncheck the Yes checkbox) before
sending the assembly to I-deas.
• Display a UI to override replace revision Preference in Send to I-deas dialog
This option adds the Replace existing revisions in the model file checkbox on the Send to I-deas
dialog. This allows you to override the Replace existing revisions in model file during Send to I-
deas operation option on a case by case basis. It allows you to decide to replace (or not replace) the
existing revisions in the model file with the item revisions that are currently being sent to I-deas.
If you select the checkbox, then existing revisions are replaced (as described in the above option). If
the checkbox is unchecked, then existing revisions are not replaced (as described in the above
option).

5-20 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 I-deas Derived Part and NX Part Are Not Synchronized

Note:
This option is not applicable to Teamcenter Structure Manager.

I-deas Derived Part and NX Part Are Not Synchronized

Integration for I-deas tracks the source NX and derived I-deas items. If either one is updated and they are
not synchronized with what is in the model file, the item is flagged with the appropriate icon in the
Integration for I-deas window. They can be updated with the Integration for I-deas update commands.

Integration for I-deas Window

The Integration for I-deas window shows the derived I-deas item and associated NX item as out-of-date
for version and revision.

It is possible for the derived I-deas part to be version and/or revision out-of-date in both the part that it
represents and the source NX part that it was derived from:

• I-deas derived part out-of-date: version and/or revision

• NX source part out-of-date: version and/or revision

The out-of-date status of items is indicated by an icon next to the dataset:

The version is out-of-date; the version in Teamcenter is later than the current
version of the item in the I-deas model file.
The revision is out-of-date; the revision in Teamcenter is later than the current
revision of the item in the I-deas model file.

For more information on these icons, see chapter , Using Integration for I-deas: Updating and
Synchronizing Data.

The status of the derived I-deas part and NX source part are shown in the Integration for I-deas window.
The icons can be combined to represent both out-of-date version and revision. They can be further
combined to represent out-of-date version and revision for both the I-deas part and the NX source part.

When displayed in the Integration for I-deas window, the UG Master icon is shown and if it is out-of-date
for version or revision, the or icons are shown before the UG Master icon. If the NX source part
is out-of-date, the icons are shown after the UG Master icon. In the following example, the derived I-
deas part and the NX source part are both version and revision out-of-date.

bracket_A, 0057, v3

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 5-21
© 2020 Siemens
 5. Using Integration for I-deas: Sending Modeling Data From My Teamcenter to I-deas

NX Source Part Version and Revision Attributes

You can check the version and revision attributes for the NX source part that the derived I-deas part is
currently referencing. In I-deas, the following attributes are displayed by choosing the User Attribute
pulldown menu selection in Manage Bins.

• SRC_DATASET_TYPE

• SRC_DATASET_VERSION

• SRC_ITEM_ID

• SRC_ITEM_REV_ID

Updating

You can use the standard updating menu commands to update the NX and derived I-deas items.

• When a later revision of a part exists, the out of date revisions icon is displayed next to the item in the
Integration for I-deas window. You can update the item to the latest revision by choosing Update to
Latest Revision from the Edit menu. Or alternatively, right-click the selected item to display the
popup menu and choose Update to Latest Revision. The item is updated and the out of date icon is
removed.

• Use the Update menu option if the derived I-deas part version is out-of-date.

• If the derived I-deas part revision is out-of-date, select the latest version of the latest revision of the
derived I-deas part in Teamcenter and send it to I-deas.

• Use the Update Source Part menu option if the derived I-deas part is referencing an out-of-date NX
part version. The latest version of the current revision of the source NX part is sent to I-deas. The
derived I-deas part must be checked out to enable the menu option.

Note:
Update Source Part merges the NX part geometry changes with the I-deas part. The update
can fail if the changes to the part are contradictory or not compatible with each other.

• Use the Update Source Revision menu option if the derived I-deas part is referencing an out-of-date
NX part revision. The latest version of the latest revision of the source NX part is sent to I-deas. The
derived I-deas part must be checked out to enable the menu option.

5-22 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 6. Using Integration for I-deas: Updating
and Synchronizing Data
Finding Out-of-Date Modeling Data ────────────────────────── 6-1
Out-of-Date Modeling Data in Interoperability ─────────────────────── 6-2
Synchronization of Model Files ───────────────────────────── 6-2
Synchronize Dialog ───────────────────────────────────────
6-3
Synchronize Menu Selection ──────────────────────────────────
6-3
Synchronize Preference ─────────────────────────────────────
6-4
Synchronize Part Name and Part Number ──────────────────────────
6-4
Updating Model File Data ──────────────────────────────── 6-5
Updating NX Assemblies ───────────────────────────────── 6-7

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 6. Using Integration for I-deas: Updating
and Synchronizing Data
This chapter describes how to find and update out-of-date modeling data and how to manually
synchronize I-deas model file data with Teamcenter.

Finding Out-of-Date Modeling Data

The status of items in the I-deas model file relative to their corresponding Teamcenter datasets is
indicated by an icon next to the dataset in the Model File View window, as follows:

Indicates that the dataset version in Teamcenter is higher than the current version
of the item in the I-deas model file.

This can be caused if another user modified the file and checked it back into
Teamcenter after you sent the file to I-deas. It can also be the result of sending an
older version of a file to I-deas when sending an FE model or legacy assembly.

Objects with this status cannot be checked out for modification.

Objects with this status can be updated using the Update command or by
resending the dataset to I-deas.
Indicates that a later revision of the Teamcenter item exists than that in the model
file.

Objects with this status cannot be checked out for modification.

Objects with this status can be updated using the Edit→Update to Latest
Revision command. For additional information, see Updating in the previous
chapter. However, they can also be updated by sending the dataset associated
with the later item revision to I-deas. For additional information, see Sending
Revisions of Same Part to I-deas in the previous chapter, or refer to the
preference IDEAS_send_option_replace_revisions in the Preferences chapter.
Indicates that the BOMView revision object in Teamcenter has a last-modified date
later than the last-modified date of the corresponding assembly dataset.

This occurs when someone modifies the assembly structure in Structure Manager.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 6-1
© 2020 Siemens
 6. Using Integration for I-deas: Updating and Synchronizing Data

Note:
Even minor changes to a BOMView revision cause the last-modified date to
change.

Assemblies with this status can be checked out for modification.

Assemblies with this status cannot be updated. They must be removed from the
model file and resent from Teamcenter.

To find out-of-date modeling data, choose the Find Out of Date Items option from the Integration for I-
deas window Edit menu or right-click in the Model File View window and choose the option from the
popup menu. The status icons are updated in the Model File View window.

To find out-of-date modeling data for specific items, choose the Find Out of Date Items on Selected
option from the Integration for I-deas window Edit menu or right-click in the Model File View window
and choose the option.

Note:
A Find Out of Date Items operation occurs automatically when you load an I-deas model file or
send data to I-deas.

Out-of-Date Modeling Data in Interoperability

The display for out-of-date items that are involved in interoperablity has additional requirements
because I-deas and NX have associativity between the NX part and the derived I-deas part.

The display includes the I-deas part icon, followed by any out-of-date icons relevant to the I-deas part
dataset. These icons are then followed by the NX part icon, also followed by any out-of-date icons
relevant to the UGMASTER dataset. Therefore, you could see two * icons (indicating version is out-of-
date). One indicates the I-deas part dataset is out-of-date, and the other indicates the NX part dataset is
out-of-date. The same situation applies to the rev-out-of-date icons (can have one for the I-deas part
dataset and one for the NX part dataset).

Synchronization of Model Files

The following is provided for synchronization of model files:

• Synchronize dialog

• Synchronize menu selection

• Synchronize preference

6-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Synchronize Dialog

When you open a model file in I-deas, items in the model file and in Teamcenter are synced. The
following situations are resolved by synchronization:

• If an item exists in the I-deas model file (and it's not a new item) but doesn't exist in Teamcenter, the
item in the model file is converted to new. In this situation, the item could have been referenced or
checked out to I-deas, then deleted in Teamcenter.

• If an item in the I-deas model file has a status of checkout but is not marked checkout in Teamcenter,
the item in Teamcenter is marked as checkout. In this situation, the item could have been checked out
to I-deas, then the checkout was cancelled in Teamcenter. Reverting the item back to checkout is also
called reserving the item.

• If an item in the I-deas model file has a status of checkout but is checked out to somebody else in
Teamcenter, the item in the model file is converted to new. In this situation somebody else has
already checked out the item when you open the model file.

Synchronize Dialog

When synchronization is going to be performed, such as when opening a model file, a Model File
Synchronization dialog is displayed. If all items are OK and none need to be synced, the dialog is not
displayed. The dialog lists:

• The items that will be synchronized

• The issue causing the synchronization for each item, such as the checked out item is not found in
Teamcenter

• The proposed fix for the item, such as changing the status to new in the I-deas model file

If you want to proceed with synchronization, click OK on the dialog, or Cancel to not synchronize. All
items in the Model File Synchronization dialog are synced or not synced; they can't be individually
selected.

Note:
You can't perform a Teamcenter related function on an item in an I-deas model file, such as
changing the status or saving it to Teamcenter, unless it has been synced.

Synchronize Menu Selection

You can select specific items to synchronize by selecting the items in the Integration for I-deas window
and choosing Edit→Synchronize. The Model File Synchronization dialog is displayed prompting you to
OK or cancel.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 6-3
© 2020 Siemens
 6. Using Integration for I-deas: Updating and Synchronizing Data

Synchronize Preference

The following preference is added (in the Teamcenter preferences) that allows you to specify whether
synchronization automatically occurs when a model file is opened and during startup of I-deas:

• IDEAS_automatically_synchronize

If set to TRUE (the default), synchronization automatically occurs. If set to FALSE, you'll have to
manually synchronize items (if needed) by choosing Edit→Synchronize (for individual items), or
Edit→Synchronize Model File (for all items in the model file).

Note:
Integration for I-deas may need to perform the sync process on an item even though its status is
the same as in Teamcenter (i.e., the item is in sync). You can't perform a Teamcenter related
function on an item in an I-deas model file unless it has been synced.

Note:
The preference also determines whether the finding out of date items function is performed when
a new model file is opened. If synchronize is not performed, then this process is also not
performed.

Synchronize Part Name and Part Number

Synchronize the part number and part name of a referenced item in I-deas to the corresponding values
in Teamcenter when the I-deas model file is synched. Select the following option in the Teamcenter
Options dialog (Edit→Options).

Synchronize the I-deas part number and part name during Model File Synchronization

This is applicable when you choose Edit→Synchronize for individual items or Edit→Synchronize
Model File for all items in the model file.

The Teamcenter Item name and Item ID corresponds to the I-deas part name and part number. The
Teamcenter dataset name and Item ID corresponds to the I-deas part name and part number for a
drawing or FEM.

Note:
For information on how the master variable affects the mapping of the part number and Item ID
during synchronization, see the Master Variable for Part Number and User Attributes section in
the Using Integration for I-deas: Working With Modeling Data chapter.

When you select Yes, for a part/assembly referenced in I-deas:

6-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Updating Model File Data

• When the item name or item ID is changed in Teamcenter, synchronization updates the part name or
part number in I-deas.

• When the dataset name is changed in Teamcenter, synchronization does not update the part name in
I-deas.

When you select Yes, for a drawing or FEM referenced in I-deas:

• When the item name is changed in Teamcenter, synchronization does not update the part name in I-
deas.

• When the item ID or dataset name is changed in Teamcenter, synchronization updates the part
number or part name in I-deas.

When you select Yes, for a part/assembly/drawing/FEM checked out to I-deas:

• When the item name, item ID, or dataset name is changed in Teamcenter, synchronization does not
update anything.

When you select No, for a part/assembly/drawing/FEM checked out or referenced in I-deas:

• If you change the item name, item ID, or dataset name in Teamcenter, synchronization does not
update anything.

Updating Model File Data

The My Teamcenter Update option can be used to synchronize the version of data in the I-deas model
file with the version of the data referenced by the Teamcenter dataset.

Note:
The Update option works only across dataset versions, not item revisions. It is possible that a later
version of a dataset exists in a later revision of an item.

Perform the following steps to update the model file items:

1. Select the items in the Integration for I-deas window. Don't select an assembly and its associated
parts. They cannot be updated at the same time. Update the assembly separately from its parts.

2. Choose Update from the Integration for I-deas window Edit menu, or right-click and choose the
option from the popup menu.
The selected items are updated in the model file.
Choose the Update All option to update the files corresponding to all objects in the Integration for
I-deas window.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 6-5
© 2020 Siemens
 6. Using Integration for I-deas: Updating and Synchronizing Data

Note:
If the objects include an assembly and its associated parts, the update is not performed and
an error message is displayed. An assembly and its parts must be updated separately.

The following restrictions apply when updating model file data:

• FE models cannot be updated in I-deas. FE models selected for update are ignored.

• Items that are checked out cannot be updated.

Note:
Under normal conditions, there should be no inconsistencies between checked-out datasets
and model files. However, if datasets are checked out or checkouts are cancelled using the
standard Teamcenter commands instead of the Integration for I-deas Integration for I-deas
commands, version inconsistencies could arise.

• The Update option has no effect if a new version of the dataset was created in Teamcenter by means
other than being saved from I-deas. For example, if the properties of a dataset were modified in
Teamcenter, a new version of the dataset is generated but the underlying I-deas data is not modified.

• I-deas parts and assemblies can be updated.

• Standalone JT parts can be updated.

• When an Update source part operation is performed on a derived part, the revision and version of
the derived part are not updated, they are updated for the source part. After the update, the derived
part points to the newer source part.

• For an NX assembly and associated part, where the assembly is sent to I-deas, and the part (and
corresponding assembly) is modified in NX, the Update option updates the selected assembly, but
not the part. You have to update the part separately (Update source part option).

• You can't update multiple versions of an item at the same time; update one version at a time.

• An I-deas assembly cannot be updated with its associated parts, even if the assembly and its
associated parts are both selected. The assembly must be updated separately from its parts.

• It is recommended that you update items higher in the product structure before updating lower level
items. This reduces the number of updates that Integration for I-deas needs to perform.

6-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Updating NX Assemblies

Updating NX Assemblies
When an existing part in an NX assembly is updated, it is updated the same way it was sent to I-deas. For
example, if it was sent as Precise, it is updated as Precise.

Note:
This functionality is only available with I-deas 12m3 and later.

When an NX assembly is updated and a new part is added to the assembly, it can be added as an NX part
or JT part. The following preference specifies how the part is added:

IDEAS_send_default_NX_as
Valid values:

JT — Sends the part as a JT part. This is the default.

NX — Sends the part as an NX part.

Pruned parts in an NX assembly cannot be updated. Therefore, when you update a pruned part in an NX
assembly, you must first unprune the part, perform the update, then prune the part.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 6-7
© 2020 Siemens
 6. Using Integration for I-deas: Updating and Synchronizing Data

6-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 7. Using Integration for I-deas: Managing
Assembly Structures
Overview ─────────────────────────────────────────── 7-1
View Data for I-deas Assemblies ─────────────────────────────── 7-1
Assembly Configuration in Structure Manager ─────────────────────── 7-1
View Associated PMI Instances and Geometry ─────────────────────── 7-2
Wire Harness Assemblies ──────────────────────────────────── 7-2
Component Versions ────────────────────────────────────── 7-3
Legacy Assemblies ──────────────────────────────────────── 7-3
Assemblies Containing Components From Other CAD System ───────────── 7-3
Orphaned JT Files ──────────────────────────────────────── 7-3
Saving I-deas Assemblies in Teamcenter ─────────────────────── 7-3
Setting BOMView Revision Precise Preference ─────────────────────── 7-4
Transformation Matrixes ──────────────────────────────────── 7-4
Transformation Matrix Caveats ──────────────────────────────── 7-5
Saving I-deas Configurations as Teamcenter Assembly Arrangements ──── 7-5
General Considerations ───────────────────────────────────── 7-6
Harnesses ───────────────────────────────────────────── 7-6
Configurations Stored ────────────────────────────────────── 7-6
Store configurations command line utility ────────────────────── 7-7
General considerations ───────────────────────────────────── 7-7
Modify/Create Translation service access rules ─────────────────────── 7-8
Input to the Store Configurations Utility ─────────────────────────── 7-9
Running the Store Configurations Utility ────────────────────────── 7-10
Aborting the Store Configurations Utility ───────────────────────── 7-11
Output From the Store Configurations Utility ─────────────────────── 7-11
Using Top-Down Design to Create Assembly Structures in Teamcenter ─── 7-12
Basic Top-Down Design ──────────────────────────────────── 7-12
Using Multiple Select to Add I-deas Datasets ─────────────────────── 7-12
Sending Assemblies to I-deas From Structure Manager ───────────── 7-13
Pruning Parts ─────────────────────────────────────── 7-14

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 7. Using Integration for I-deas: Managing
Assembly Structures
This chapter describes how Integration for I-deas is used to create and manage assembly data.

Overview
Integration for I-deas supports the transfer of assembly data between I-deas and Teamcenter. I-deas
assemblies are represented using standard Teamcenter BOM view and occurrence objects in conjunction
with the item and item revision objects and datasets used to represent I-deas parts and assemblies.

View Data for I-deas Assemblies

When assemblies are saved in Teamcenter, an IdeasAssemblyViewInfo dataset is created and attached
to the assembly item revision. The single named reference of this dataset is a compressed .vfz file
containing the assembly JT file, any motion files generated for the assembly, and a text file containing
the name of the assembly JT file.

Assembly Configuration in Structure Manager

When I-deas assemblies are saved, by default, the configuration data of the assembly is exported to
Teamcenter for the design configurations; the active configuration data is not exported. If no design
configuration is set, then no configuration data is exported. When viewing an assembly like this in
Structure Manager, the components are shown in the part orientation, not the assembly orientation.

Note:
Changing from one assembly configuration to another in I-deas does not cause the assembly to be
modified and therefore, does not result in a new version being saved to Teamcenter. Creating a
new design configuration in I-deas does save a new version to Teamcenter.

Note:
The IDEAS TMTID note on each BOM occurrence within the I-deas assembly items in Structure
Manager should not be edited. The TMTID note identifies items that originated from I-deas. Items
that are added to the assembly in Structure Manager don't get the TMTID identification. This
information is CAD private data and is useful to I-deas during a send-to-I-deas operation in
identifying those items that originally came from I-deas, and therefore should not be edited.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-1
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

View Associated PMI Instances and Geometry

When you display assembly JT files in the Teamcenter Structure Manager and select PMI in the
Teamcenter Viewer, the corresponding instances and geometry referenced by the PMI are highlighted in
the Viewer. This enables you to see the associativity for assembly PMI in JT files in Teamcenter.

Wire Harness Assemblies

I-deas wire harnesses are saved into Teamcenter as assembly datasets and are treated like any other
assembly object, with the exception of how the associated JT files are handled.

When saving I-deas assemblies to Teamcenter, JT files are created for each wire harness bundle
referenced by the assembly. These JT files are then stored as named references of a single DirectModel
dataset that is attached to the item revision of the assembly.

The creation of the DirectModel dataset and JT files are controlled by the IDEAS_assembly_create_jt
preference and the I-deas site parameter file. For more information, see Preferences.

Viewing Wire Harness Assemblies in Teamcenter Structure Manager

To see wire harness assemblies in the Teamcenter Structure Manager:

1. Turn on the JT generation preference in the I-deas site parameter file.

2. Set the IDEAS_assembly_create_jt preference to TRUE in the Teamcenter preferences.

3. Set the environment variable JTK_MS8_ENABLE_SOLID_WIREHARNESS=1 in the IDNPortal.bat

script (Windows) or idn_start_portal script (Unix).

To view a harness, send only the assembly (not the harness) to the Structure Manager. Right-click on a
node and you'll get an option to replace the JT file. Pick the harness you want to view from the list of JT
files displayed.

Structure Manager views of harnesses are only correct in the active configuration of the harness context
assembly (HCA) and harness assembly (HA). Since harness bundle shapes are viewed in the Structure
Manager with a JT file and I-deas produces a JT file for only the active configuration of the HCA and HA,
the harness geometry may not be correct for other configurations.

For higher level assemblies that reference this HCA and either don't use the configuration of this HCA or
use a non-active configuration of the HCA or HA, the bundle orientation and shape may not be correct.

When the HA is in more than one HCA, the harness component positioning is correct for all
configurations of the HCAs and HAs, but the bundle shape reflects the last HCA saved.

7-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Component Versions

Component Versions

Components of assemblies, both parts and subassemblies, can be modified and saved in Teamcenter
outside the context of the main assembly. Therefore, a newer version of a component may exist than
that originally saved with the assembly. When you send the main assembly to I-deas, the newest version
of the component is sent rather than the version originally referenced by the main assembly.

Note:
This behavior does not apply to legacy assemblies.

Legacy Assemblies

Legacy assemblies are assemblies created in I-deas prior to version 8. These assemblies occur in the
Teamcenter database as a result of data sharing or migration.

While the datasets associated with legacy assemblies look like any other I-deas assembly dataset in the
Teamcenter interface, they do not exhibit the same behavior when sent to I-deas. These assemblies are
sent to I-deas in their original state; therefore, changes made to the assembly structure in Structure
Manager before it is sent to I-deas are not reflected in I-deas. Additionally, newer versions of assembly
components other than those originally saved with the assembly are not sent to I-deas; rather, the
component versions originally referenced by the legacy assembly are sent.

Assemblies Containing Components From Other CAD System

Integration for I-deas supports I-deas assemblies that contain components from other CAD systems,
provided that the foreign components are represented as JT files. When saved to Teamcenter, these files
are stored in DirectModel datasets.

Orphaned JT Files

To delete an orphaned JT part from the model file, send it to I-deas as precise. This changes the
orphaned JT part that was previously pruned-faceted in the model file into a new I-deas part. Then
delete the part from the model file.

Saving I-deas Assemblies in Teamcenter

When an assembly is saved in Teamcenter for the first time, a BOM view is created and attached to the
newly created item. Additionally, an imprecise BOMView Revision is created and attached to the item
revision. Occurrence objects are then created to connect the assembly to the items representing the
first-level assembly components (figure 7-1).

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-3
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

Figure 7-1. I-deas Assembly Saved in Teamcenter

Setting BOMView Revision Precise Preference

User preferences can be set to create a precise BOMView Revision (BVR) at assembly checkin and data
sharing import.

To set user preferences to create a precise BVR for an assembly at checkin or import, perform the
following steps:

1. Pull down the Edit menu and choose the Options option. The Options dialog window displays.

2. Select Integration for I-deas from the list at the left of the window.

3. Check the yes checkbox next to the Create Precise BVR on Check-in option.

Note:
The preferences are set within the Teamcenter preferences. For more information about setting
preferences, see Preferences.

Transformation Matrixes

When an I-deas assembly is saved to Teamcenter, a transformation matrix representing the positioning
and orientation of each occurrence of each assembly component is created and attached to the
Teamcenter occurrence object. This allows you to view assembly structures in My Teamcenter using
Teamcenter Visualization or other integrated visualization tools.

This creation of matrixes is applicable only when the following preference is set:

IDEAS_save_configurations=FALSE

When this preference is set to TRUE, configurations are stored and arrangements are created as
documented in the section Saving I-deas Configurations as Teamcenter Assembly Arrangements.

7-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Transformation Matrix Caveats

Transformation Matrix Caveats

The following caveat applies to Integration for I-deas transformation matrices and may affect the display
of assemblies in Teamcenter Visualization:

• When arrangement creation is turned off, Teamcenter allows only one transformation matrix per
occurrence of a component in a subassembly.
If an I-deas assembly contains multiple occurrences of a particular subassembly, and each occurrence
uses a different configuration, the orientations of the components on the subassemblies may not be
displayed properly.

• When arrangement creation is turned on, only those transforms that are associated with I-deas design
configurations are available to Teamcenter.
If an assembly contains one or more subassemblies for which design configurations are not used to
control the positioning of the components, an error message is displayed in I-deas when saving the
assembly to Teamcenter. Additionally, transformation matrices are not saved in Teamcenter for the
components.

Saving I-deas Configurations as Teamcenter Assembly

Arrangements
I-deas configurations can be saved in Teamcenter such that the view of the assembly product structure
in Structure Manager is the same as it is in I-deas. Design configurations in I-deas are stored in
Teamcenter and then absolute occurrences in Teamcenter are used to build the different arrangements
for an assembly. This allows components of an assembly to be positioned and used as intended by the I-
deas design.

Once configuration information is saved to Teamcenter, it is used by Teamcenter to create arrangements

that match the configurations. You can save design configurations for new assemblies by setting a
preference to enable the functionality. For existing assemblies, you can run the Store Configurations
command line utility.

To enable design configurations to be saved for new assemblies, set the following preference:

IDEAS_save_configurations
Saves the assembly design configurations during checkin to Teamcenter.

Note:
To ensure the accuracy of the configuration in Teamcenter, design configurations must be
used and this preference should be set to TRUE.

Valid values:

TRUE — Saves assembly configurations. The default.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-5
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

FALSE — Does not save assembly configurations. Teamcenter arrangements are not created.
Instead relative transforms are set on each occurrence (previous functionality). When this is
done, the view of a model may not be correct.
Also, relative transforms used are based on the active configuration, not the assembly's used
configuration (previous functionality), which could result in slightly different looking models
than if it was based on the used configuration.

General Considerations

The following apply when saving I-deas design configurations as Teamcenter arrangements:

• During send to I-deas, Teamcenter arrangements are not sent to I-deas. Only as-saved absolute
occurrence positioning of I-deas components is sent.

• Check in of an assembly still continues even if the configuration information fails to be saved to the
database. In this case, an error message is output to the TB.log file.

• The Model File window displays the PS edit icon next to each assembly that had its arrangements
created by the Store Configurations utility.

• For additional information on arrangements and absolute occurrences, see the Teamcenter
documentation.

• Teamcenter Express does not support arrangements.

Harnesses

Structure Manager views of harnesses are only correct in the active configuration of the harness context
assembly (HCA) and harness assembly (HA). Since harness bundle shapes are viewed in the Structure
Manager with a JT file and I-deas produces a JT file for only the active configuration of the HCA and HA,
the harness geometry may not be correct for other configurations.

For higher level assemblies that reference this HCA and either do not use the configuration of this HCA
or use a non-active configuration of the HCA or HA, the bundle orientation and shape may not be
correct.

When the HA is in more than one HCA, the harness component positioning is correct for all
configurations of the HCAs and HAs, but the bundle shape reflects the last HCA saved.

Configurations Stored

The configurations stored when you check in an assembly are design configurations (other
configurations cause problems during check in). You create the design configurations in I-deas and have
them checked into Teamcenter. If a configuration cannot be checked in, check in of the assembly still
occurs and info is output to the TB.log file about the configurations that cannot be checked in. You can

7-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Store configurations command line utility

then use the Store Configurations command line utility to store the configurations (and create the
arrangements) in that case.

The Store Configurations utility stores either All or Active, Design, Used configurations (set by an
option in the utility). The utility is typically run for existing assemblies, then design configurations are
created for the assemblies and saved during check in (if the preference IDEAS_save_configurations is
set).

Note:
Configurations other than design configurations cause problems during check in. These must be
stored using the Store Configurations utility.

To store design configurations during check in, the following I-deas parameter must be set to 0 (this is
the default):

Assembly.ExportActiveConfigData: 0

Store configurations command line utility

The Store Configurations command line utility adds configuration data to existing I-deas assemblies and
creates corresponding arrangements in Teamcenter.

The utility loads the complete assembly into I-deas, then processes the assembly from the bottom up
(subassemblies processed before top assembly) and creates Teamcenter arrangements for all existing
configurations. If an arrangement already exists for an assembly, a new one is not created.

If an error occurs while processing an item in the assembly, the utility stops processing and logs an error
to the console and to the error log file failed_stored_configs.log. After you fix the problem, you can
rerun the utility on the item.

General considerations

The following apply when using the Store Configurations utility:

• It is recommended that you are in the DBA group when running this utility even on items that you
own.

• You can only process items to which you have write access.

• It is expected that you have Teamcenter bypass privileges.

Bypass privileges allow an administrator to freely access any object permitting the bypass of Access
Manager rules.

• Bypass privilege is required to process released items.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-7
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

• You cannot process parts that are checked out, unless they are checked out to you.

Modify/Create Translation service access rules

Before running the store configurations utility, you need to modify/create rules in the access rule tree
which allow the store configs user to update attributes of a BomView object and BVR object. If these
rules are not created correctly, the store configuration utility could fail to create arrangements.

1. Log in to Teamcenter Rich Client as a system administrator.

2. Open the Access Manager.

3. In Access Manager, modify the following ACL by adding a line for your store configs user:
Rule = Has Class (POM_application_object)->Working

Condition = Has Class

Value = POM_application_object

ACL Name = Working

ACE Type of Accessor = User

ACE ID of Accessor = store configs user ID

ACE Privilege = Read

ACE Privilege Value = Grant

ACE Privilege = Write

ACE Privilege Value = Grant

ACE Privilege = Delete

ACE Privilege Value = Grant

ACE Privilege = Checkin/Checkout

ACE Privilege Value = Grant

4. In Access Manager, create the following ACL and add it for both PSBOMView and
PSBOMViewRevision to the rule tree under:
Has Class (POM_application_object)->Working

Condition = Has Class

7-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Input to the Store Configurations Utility

Value = PSBOMView

ACL Name = TS Access

ACE Type of Accessor = User

ACE ID of Accessor = store configs user ID

ACE Privilege = Read

ACE Privilege Value = Grant

ACE Privilege = Write

ACE Privilege Value = Grant

ACE Privilege = Delete

ACE Privilege Value = Grant

ACE Privilege = Checkin/Checkout

ACE Privilege Value = Grant

Note:
This rule applies only to the standard Access Manager rule tree. If custom rules are specified for
this installation, your custom rules must be modified to provide the equivalent access of this rule.

Input to the Store Configurations Utility

There are three methods of providing input for the utility to process:

• Text file that contains a list of items

• Teamcenter folder that contains the items you want to process

• Entering the item on the command line

For all three methods the input can be Items or Item Revisions. The format is ITEM or ITEM/REVISION,
where ITEM is the Item ID and REVISION is the revision ID. If REVISION is not specified, the latest Item
Revision is used.

The following is an example for a text file:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-9
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

<input.txt>
# comment lines allowed
1023–485/A
1567–908
1111–321/B

To use the options, specify the absolute path, folder name, or Item/Item Revision name, for example:

store_configs —in=c:\temp\input.txt <-u=user_id> <-p=password> <-

g=group>

store_configs —folder=Input <-u=user_id> <-p=password> <-g=group>

store_configs —item=0974/C <-u=user_id> <-p=password> <-g=group>

Running the Store Configurations Utility

To run the utility, perform the following:

1. Ensure Teamcenter Portal is not running.

2. Start an I-deas session with the start_ideas.bat script located in the Portal directory. This sets up
the proper I-deas environment.

3. In I-deas, turn off the auto-save functionality. Auto-save could display dialogs that interfere with
execution of the Store Configurations utility.

4. Start a Teamcenter Command Prompt window.

5. In the Command Prompt window, enter the following command to run the utility:

store_configs —item=000711 <-u=user_id> <-p=password> <-g=group>

Where the variables are:

Variable Definition

-u[ser] <user name> Specifies the Teamcenter user name.

-p[assword] <password> Specifies the Teamcenter password for the user..

-g[roup] <group name> Specifies the Teamcenter group. This is optional.

-d[atabase] <database> Teamcenter database name. This is optional. Default database

connection is used if not specified.

-b[ypass] Yes | No. Run the utility with bypass privileges.

7-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Aborting the Store Configurations Utility

Variable Definition

-in[put_list] <file name> File that defines list of items to process. Must specify the absolute
path.

-fol[der] <folder name> Teamcenter folder that contains items to process.

-it[em] <item ID> Indicates a single item to process.

-l[og_file] <file name> Name of log file that records output. Default (this variable is not
used) is store_configs.log at <TCII_TEMP> directory.

-o[utput_file] <file name> Name of the log file that records items that failed to process.
Default (this variable is not used) is failed_store_configs.log at <TCII_TEMP>
directory.

-s[ave_released] Yes | No. Processes items marked with a released status. Otherwise, released
items cause an error during processing. This option is valid only when running
in bypass mode.

-r[ecurse] Yes | No. Processes the subassemblies of an assembly. The utility's default is
yes (processes all subassemblies).

-c[onfig_type] all | active_design_used. Stores either all configurations or just the active,
design, used configurations. The utility's default is to store just the active,
design, used ones.

-for[ce] Update existing Teamcenter arrangement data. By default, items with existing
arrangement data are skipped during processing. This option overrides the
default.

-h / -H / -h[elp] Displays the usage and options for the tool.

Aborting the Store Configurations Utility

You should only stop the utility by letting it gracefully exit the process. To do this, create an empty file
store_configs_stop in the Integration for I-deas temp directory that was specified during Integration for
I-deas installation. This file is checked between processing of successive Item Revisions and if found, the
utility is stopped at a point that prevents any data corruption.

Caution:
If the utility is aborted by other means, such as keying CTRL-C, data corruption could result.

Output From the Store Configurations Utility

The default location for the output files is the Integration for I-deas temp directory specified during
installation. The output files are:

• Processing report

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-11
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

This file is defined by the variable –log_file and contains a record of what was processed and whether
it was successful or failed.

• Error report
This file is defined by the variable –output_file and contains the items that failed to process and the
reason why it failed. This report conforms to the format of the input file so you can use it as input to
rerun the utility once you have fixed the problems. This makes it easier to re-run and avoids
processing items that were already successfully processed.

Using Top-Down Design to Create Assembly Structures in

Teamcenter
Integration for I-deas supports top-down design. You can construct an assembly structure in Teamcenter
using My Teamcenter in conjunction with Structure Manager, and then send that assembly structure to
I-deas to be associated with the corresponding modeling data.

Basic Top-Down Design

The top-down design process includes the following basic tasks:

• Create assembly items in Teamcenter.

• Create I-deas assembly datasets and associate them with the assembly item revisions.

• Create part items in Teamcenter.

• Create I-deas part datasets and associate them with the part item revisions.

• Build the assembly structure in Structure Manager using the component items created in the previous
steps.

• From Structure Manager, send the structure to I-deas.

Note:
Drawing and FE model datasets cannot be created manually in Teamcenter. Only parts and
assembly datasets can be created in Teamcenter and sent to I-deas.

For more information on creating items and datasets, see Navigator Help. For more information on
creating assembly structures, see the Structure Manager Help in the Teamcenter documentation.

Using Multiple Select to Add I-deas Datasets

You can create multiple datasets for parts or for assemblies, as follows:

7-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Sending Assemblies to I-deas From Structure Manager

1. Create assembly items or create part items in Teamcenter.

2. Build the assembly structure in Structure Manager using the component items created in the
previous steps.

3. Select one or more part BOM lines or assembly BOM lines (but not both), and select the appropriate
dataset creation option from the I-deas menu in Structure Manager.

4. From Structure Manager, send the structure to I-deas.

To see the I-deas datasets that are created, open My Teamcenter.

For more information, see Creating I-deas Datasets in chapter , Using Integration for I-deas: Working
With Modeling Data.

Customized Rules for Dataset Creation

A user exit lets you customize dataset creation based on rules you provide.

The user exit API is similar to:

extern USER_EXITS_API int IDSUSER_verify_ds_creation (

tag_t bomline, /* <I> */
const char* dsType, /* <I> */
logical* skipCreation, /* <O> */
char** message ); /* <O> */

• If the user exit returns anything other than ITK_ok the dataset creation is aborted.

• If skipCreation is set to true, the dataset creation for the particular bomline is skipped and the
message returned is displayed.

Note:
The user exit only applies to multiple selections of datasets added by Create I-deas Part Dataset
and Create I-deas Assembly Dataset.

For more information, see the Integration for I-deas Data Migration Reference Guide and the
Teamcenter Help Library.

Sending Assemblies to I-deas From Structure Manager

Fully configured assemblies can be sent to I-deas from either My Teamcenter or Structure Manager. For
more information on managing assemblies in Structure Manager, see the Teamcenter documentation.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 7-13
© 2020 Siemens
 7. Using Integration for I-deas: Managing Assembly Structures

Note:
Assemblies sent to I-deas from Structure Manager are sent in a reference-only state. Once the
assembly is sent to I-deas, the components can be checked out using the Change to Checkout
option in the Manage Bins menu in the Integration for I-deas window.

Perform the following steps to send assembly data from Structure Manager to I-deas:

1. Load the assembly in Structure Manager.

2. Select one or more BOM lines corresponding to the assemblies or subassemblies that you want to
send to I-deas.

3. Click the Send to I-deas button on the toolbar.

If no BOM lines were selected, the entire assembly is sent in a reference-only, unpruned state. If
one or more BOM lines were selected, the assembly is sent to I-deas in a reference-only state. All
components of the assembly are pruned except those corresponding to the selected BOM lines.

Pruning Parts
When you reference or check out an assembly to I-deas, you have the option to prune some or all of its
component parts. Pruning parts in an assembly means that you transfer the assembly structure and
subassemblies, but not the associated geometry of any parts you prune. Pruning parts improves transfer
time and model file performance.

When part has been pruned, the pruned icon displays in the Integration for I-deas window.

Pruned parts cannot be displayed or modified in I-deas.

7-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 8. Data Sharing
Integration for I-deas Data Sharing ────────────────────────── 8-1
Item Ownership ───────────────────────────────────────── 8-1
What Is Integration for I-deas Data Sharing? ──────────────────────── 8-2
I-deas Version Issues with Data Sharing ─────────────────────────── 8-3
Changing Item Revision Master and Dataset Properties ────────────────── 8-4
Data Sharing Export Process ────────────────────────────────── 8-4
Exporting with Transfer of Ownership ──────────────────────────── 8-5
Data Sharing Import Process ────────────────────────────────── 8-5
Importing with Transfer of Ownership ──────────────────────────── 8-6
How to Export a Data Sharing Package ──────────────────────── 8-7
Creating a Package ─────────────────────────────────────── 8-7
What Happens When You Create a Data Package? ──────────────────── 8-10
How to Import a Data Sharing Package ─────────────────────── 8-11
Creating Items, Item Revisions, and Datasets ─────────────────────── 8-13
Customizing Item Type ──────────────────────────────────── 8-14
Import Ownership Considerations ────────────────────────── 8-14
Import I-deas Design Data for Reference ────────────────────────── 8-14
Import I-deas Design Data for Modification ──────────────────────── 8-15
Other Import Options ─────────────────────────────────── 8-2
Change Owning User For I-deas Package Import ───────────────────── 8-16
Pre-Validate I-deas Package for Import ─────────────────────────── 8-17
Skipping Items With a Different Item ID In the I-deas Package During Import ──── 8-17
Import Items Into Subfolders ───────────────────────────────── 8-17
Import Standalone Drawings ───────────────────────────────── 8-18
Import Legacy Assemblies ────────────────────────────────── 8-19
Scope for Preferences ────────────────────────────────── 8-19

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 8. Data Sharing
This chapter describes Integration for I-deas data sharing and provides instructions for importing and
exporting data sharing packages.

Integration for I-deas Data Sharing

The Integration for I-deas data sharing functionality enables I-deas data from an Integration for I-deas
installation to be exported to an I-deas data installation. It also enables data to be imported from an I-
deas data installation to an Integration for I-deas installation. You can export and import parts,
assemblies, drawings, and FE models.

Note:
The IDEAS_external_owning_user_name preference must be defined before import or export
can be performed.
Objects that are successfully imported for modification are modifiable in My Teamcenter. Objects
that are successfully imported for reference are not modifiable in My Teamcenter. These reference
datasets have the Owning User attribute set to the value of the
IDEAS_external_owning_user_name preference. This attribute is visible in the Properties dialog
window.
The Teamcenter settings in Access Manager must be set to prevent modification to items owned
by the external owning user.
For additional information, see Preparing for Data Migration in the Integration for I-deas Data
Migration Guide.

Note:
Data sharing and migration are not supported from four-tier clients. A two-tier client is required
for import and export of I-deas package files.

Item Ownership

Ownership and transfer of ownership control the ability to modify an I-deas item dataset, such as when
checking out an I-deas dataset to create a new version. Having ownership lets you modify the item.
Transferring ownership gives the right to modify to an external data installation while only reference
privileges are left at the originating site.

During import, ownership is either transferred to Teamcenter or it is kept in the TDM and the item is
imported for reference use only. The ownership is determined by the Intent attribute in the package file.
For additional information on import conflicts and import/export locks, see Import Considerations later

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-1
© 2020 Siemens
 8. Data Sharing

in this chapter and Appendix B, Characteristics of Migration Processing chapter in the Integration for I-
deas Data Migration Guide.

The core paradigm is that Integration for I-deas processes and operations revolve around the part and
assembly geometry and product structure. The drawing is a supportive document to the part. Therefore,
the basic concept of structure and relationship of items in Integration for I-deas is that it is part-centric.

Note:
Starting with NX Manager I-deas version 4.0, the default for the right to modify (owning user) is at
the dataset level, not the Item level. To change the right to modify to the Item level, set the
following preference:

IDEAS_use_item_level_right_to_modify=TRUE

You can use the tool, ideas_rtm_util, to convert 3.X data to 4.0 data for the owning user
attribute.

Extending the part-centric concept to item ownership, the right to modify the part is the controlling
factor in whether related datasets can also be modified. For example, if a part and related drawing are
managed within the same Item/ItemRevision, then during migration (or import), only the ownership or
intent of the part is applied to the Item/ItemRevision. The intent of the drawing is ignored. If the same
part is exported where ownership is transferred to another site, the associated drawing's ownership, or
right to modify, is also transferred even if the drawing is not exported with the part. Also, in this case, if
you intend to transfer the ownership of the drawing during export, the ownership of the part is also
transferred.

Note:
To avoid potential ownership problems, we recommend that you export the part and drawing
together, and import them back together.

There isn't any custom programmatic mapping that can be done to overwrite the part centric paradigm
to apply different behavior to certain objects. However, when importing related items, you can import
them into different item series to get them separated, such as importing a part into one Item/
ItemRevision and the associated drawing into another Item/ItemRevision. This method allows you to
control the item ownership for related drawing and FEM items.

What Is Integration for I-deas Data Sharing?

Export is accomplished by packaging copies of the appropriate data in My Teamcenter and then
exporting the package to the I-deas data installation. Import is accomplished by selecting an I-deas data
package and copying its contents into a folder in My Teamcenter.

8-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 I-deas Version Issues with Data Sharing

Note:
I-deas data can be exported and imported from within Navigator and Find, as well as from My
Teamcenter.

An I-deas package includes a single package file and one or more I-deas application data files.

• The package file is an ASCII file containing metadata about each I-deas data object that is being
exported.
The data being exported can be either UNIX- or Microsoft Windows XP/2000-compatible data.
Therefore, the I-deas package file also contains platform information indicating that the data is a
mixture of UNIX- and Microsoft Windows XP/2000-compatible data.
When the package is imported into the I-deas installation, the data is converted to the appropriate
platform type. The conversion is performed through either the Heterogeneous Team functionality or
the HDS utility, depending on which one is used by the I-deas installation.

• The I-deas application data files contain I-deas application data for each I-deas part, assembly,
drawing, or FE model.

Note:
Drawings can be I-deas independent drawings, I-deas drafting setups, I-deas binary drawings, or
I-deas ASCII drawings.

I-deas Version Issues with Data Sharing

I-deas created models are not backwards compatible to previous versions of the software. For example,
if you create a model in I-deas 11, it must be opened in I-deas 11. If you try to open it in I-deas 10, the
part won't open and you'll get the following error message in the List region:

I-deas cannot access the data. The file has a format that is not
backwards compatible with the current software release.

This applies to data created when an I-deas package is imported into Teamcenter. For example, you
import an I-deas package with I-deas 11 and Integration for I-deas. The data in the package can only be
accessed in I-deas 11 since that was the I-deas version used when the package was imported, even if the
package was created using I-deas 10.

This also applies to I-deas data items exported with Integration for I-deas and I-deas 11. They cannot be
imported into an I-deas 10 site even if all of the data files had been originally created using I-deas 10.

Note:
We recommend that the entire Teamcenter installation, including all sites and all users, be
upgraded to the next major release of I-deas at the same time.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-3
© 2020 Siemens
 8. Data Sharing

Changing Item Revision Master and Dataset Properties

When you change the name of the Item Revision Master and the dataset at the same time a new dataset
version is automatically created. This causes problems when you attempt to import or export any
version of this item to a TDM. The following error message is displayed in the import or export logs:

More than 1 datasets are found to be associated with the same I-deas
version GUID

When you select both the Item Revision Master and the dataset and choose Properties, the Common
modifiable properties dialog box is displayed which allows you to change the name for both. When you
enter a new name and click OK, a new dataset version in that Item Revision is created with the new
name.

If you select the Item Revision Master and the dataset separately and change the name, the name is
changed successfully for both without creating a new version. This difference in handling the name
change is due to existing functionality within Teamcenter.

Data Sharing Export Process

The process to share I-deas data from an Integration for I-deas installation is as follows:

1. Specify the data to be exported, whether the data is to be exported for modification or for
reference, and the package file name.

2. The system ensures that the data is valid I-deas data, and that a package file with the same file
name does not already exist in the specified directory.

3. The package file is written to the location specified by the user. The corresponding I-deas
application data files are copied to this same location.

4. If necessary, copy or transfer (FTP) the package file and the I-deas application data files to a
directory that can be accessed by the I-deas user.

Note:
This step is most likely needed in situations where data sharing is occurring with users from
another organization, such as a company's suppliers.

5. The I-deas user imports the package.

6. After the item is imported into a library, I-deas users can reference the item in the model file or
modify the item (depending on whether the data was exported for modification or reference).

8-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Exporting with Transfer of Ownership

Note:
The package cannot be imported into a version of I-deas earlier than the one with which the
Integration for I-deas installation is associated.
Attributes in Integration for I-deas that are not supported in I-deas can be mapped to I-deas user
attributes when it is exported from My Teamcenter. Similarly, I-deas user attributes can be
mapped to custom Integration for I-deas attributes during the import process. For more
information, see Attribute Mapping, later in this chapter.

For instructions on how to export data, see How to Export a Data Sharing Package, later in this chapter.

Exporting with Transfer of Ownership

When transferring ownership of items external to Teamcenter, the following is required:

• The item must be owned by the local site (when in a Multi-Site Collaboration environment).

• The I-deas dataset must not be owned by the I-deas external owning user.

• The user must have write privilege on the dataset.

• The user must have transfer out privilege on the item.

• The latest revision of the item must be the one that is exported.

For each item that is included in the package file for transfer of ownership:

• Export for Check Out is checked for each item in the Data Sharing Export dialog.

Data Sharing Import Process

The process to share I-deas data with an Integration for I-deas installation is as follows:

1. The I-deas user creates a data sharing package containing the data to be shared. The data sharing
package contains a package file and I-deas application data files. The I-deas user copies the data
sharing package to the staging location.

2. The system ensures that the data is valid I-deas data.

3. A My Teamcenter user imports the package. Items, item revisions, and datasets corresponding to
new package items are created in the My Teamcenter folder selected by the user. By default, the
one version per revision method for storing and managing data is implemented, where a separate
Item Revision is created for each I-deas version.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-5
© 2020 Siemens
 8. Data Sharing

4. By default, the items are imported into Teamcenter until a problem or conflict occurs, which
prevents the import. At that point no other package items are imported. Instead, the process
performs basic validation of the remaining items so that similar errors are reported in the log file.
The items already imported remain in the Teamcenter database.

5. Optionally, dataset versions can be mapped to a unique item revision using the
IDEAS_revision_id_format_specifier preference. For additional information, see chapter ,
Preferences. Datasets can also be mapped to item revisions in a user customization.
If the default one version per revision method is not followed, the following rules apply to the
import process.
The I-deas version series is maintained across item revisions. When a version is imported, it is
inserted in the item revision which contains the next highest dataset version. If no versions of this
item exist, the latest item revision is used. You can specify which item revision is used with a
customization. However, if the item revision specified by a customization would cause the version
to be inserted out of order, that revision is not used.
For example, if the source data installation has these revisions and versions:

Revision A
Version 2
Version 4
Revision C
Version 7
Version 8

The standard import behavior results in the following outcome:

Version 1 goes to Revision A

Version 3 goes to Revision A
Version 5 goes to Revision C
Version 9 goes to Revision C

• If a customization tries to put Version 1 into Revision C, it is ignored and Version 1 is put into
Revision A.

• If a customization specifies that Version 6 should go to Revision B, Revision B is created with

Version 6.

6. My Teamcenter users with access to the folder can access the I-deas data.

7. For instructions on how to import data, see How to Import a Data Sharing Package, later in this
chapter.

Importing with Transfer of Ownership

An import can fail when a conflict arises. An import conflict arises when a data sharing package version
intent conflicts with the state of the existing dataset ownership in an importing Integration for I-deas
installation. For instance, an Integration for I-deas installation owns an item and attempts to import a

8-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 How to Export a Data Sharing Package

data sharing package containing a new dataset version where the data sharing package version intent is
modification. This represents a conflict of ownership and the import is terminated. The installation
where the data sharing package was created owned the dataset version when the data sharing package
was created.

When transferring ownership of items external to Teamcenter, the following is required:

If the dataset and item are new to the Teamcenter installation:

• The user must have transfer-in privileges. This is determined by the rules defined in Teamcenter
Access Manager.

If an item with a version of the dataset being imported already exists:

• The item must already be owned by the I-deas external owning user.

• The item must be owned by the local site (when in a Multi-Site Collaboration environment).

• The user must have write privilege on the dataset.

• The user must have transfer-in privileges. This is determined by the rules defined in Teamcenter
Access Manager.

• The latest revision and dataset version of the item must be the one that is imported.

How to Export a Data Sharing Package

This section explains how to create the package in the My Teamcenter and what happens when you
create it.

You can share I-deas parts, assemblies, drawings, and FE models.

Note:
In I-deas (except in the Master Drafting task), you can input only data that is composed of 7-bit
English ASCII characters. Therefore, do not export Integration for I-deas items containing data that
does not conform to this standard. For example, do not export an item with a name containing an
umlaut (ü) character. If I-deas encounters a nonstandard English ASCII character, it replaces it with
an underscore. To prevent this situation, use only standard (7-bit) English ASCII data in the
following My Teamcenter fields that potentially could be read by I-deas: item name, item number,
bin name, dataset name, and dataset ID.

Creating a Package

To share data for reference or modification with an I-deas installation:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-7
© 2020 Siemens
 8. Data Sharing

1. Verify that you have set the preferences in the Teamcenter environment files. The following
preference is required:

IDEAS_external_owning_user_name

See the Data Migration Setup Requirements in the Integration for I-deas Data Migration Guide for
optional preferences that affect the import process.

2. By default, Integration for I-deas exports the I-deas package with a heterogeneous platform type.
This is because the I-deas files could have been created on Windows or Unix platforms and the
system does not record the platform type. This causes the imported TDM to convert all of the files
to the platform of the importing user.
If you know that the I-deas data was created on the same platform type as the destination TDM,
then the package platform can be overridden with the following preference:
Optionally, In the pclsvr.bat/sh file, set the following preference:

PCLSVR_SET_PACKAGE_PLATFORM
The options indicate the platform types:

• 1 — Unix

• 2 — Windows

• 3 — Heterogeneous (a mixture of Unix and Windows). This is the default.

3. Select the items, item revisions, or datasets that you want to share. You can select multiple
datasets to export.
You can select one or more datasets (I-deas parts, assemblies, drawings, and FE models). Any
dependent datasets are also shared. For example, if you select a drawing, the related part is
shared. If you select an item or item revision, the latest dataset version of the part or assembly
datasets are chosen for export unless the Export Associated options are chosen, in which case all
I-deas dataset types within the item are included for export.

Note:
Empty parts, or parts without geometry, can be created through classic Teamcenter. These
parts cannot be shared with I-deas.

4. Choose the Export →To TDM options from the My Teamcenter Tools menu to display the Export
dialog window.
This dialog window displays the datasets to be included in the package. These are the selected
datasets and all datasets on which they depend. By default, each is shown with an export intent of
reference. Choosing the Transfer Ownership option changes the export intent to modification.

8-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Creating a Package

Note:
To import a data sharing package you must have import privilege for transfer-in. To export a
data sharing package you must have export privilege for transfer-out. These are Teamcenter
settings in Access Manager.

5. Choose Transfer Ownership to transfer ownership to the export site. When you transfer
ownership to the export site, the dataset owning_user is set to the value of the
IDEAS_external_owning_user_name preference.

6. Click the Options button to select from the following general, item, or dataset export options:

• Swap Part Numbers and Names

Maps the Teamcenter item number to the I-deas part name and the Teamcenter item ID to the I-
deas part number.

• Export Associated Drawings

Includes all drawings related to the selected items and the items on which these drawings
depend in the package. This also applies to related drawings stored in different items.

• Export Associated FEMs

Includes all FE models related to the selected items and the items on which these FE models
depend in the package.

• Export Latest Revision Only

Exports latest item revision datasets in the I-deas package. (Available only when you have
selected an item for export.)

• Latest Working Revision Only

Exports latest working item revision datasets in the I-deas package. (Available only when you
have selected an item for export.)

• Latest Working/Any Release Status

Exports latest working item revision datasets and any release status item revision datasets in the
I-deas package. (Available only when you have selected an item for export.)

• Latest Any Release Status

Exports any release status item revision datasets in the I-deas package. (Available only when you
have selected an item for export.)

• Export All Revisions

Exports latest dataset for all item revisions in the I-deas package. (Available only when you have
selected an item for export.)

• Export Latest Version Only

Exports latest item revision datasets in the I-deas package. This is the default behavior. (Available
only when you have selected an item, item revision, or dataset.)

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-9
© 2020 Siemens
 8. Data Sharing

• Export All Versions

Exports all dataset versions in the I-deas package. (Available only when you have selected an
item, item revision, or dataset.)

7. Click the OK button to accept the options.

8. Enter an export directory path in the Export Directory field.

9. Enter a name for the package in the File Name field. The file name uses a .pkg extension. The
extension is added for you if you do not enter it.

10. Optionally, check the Create log file checkbox to generate a log file for the export operation.
The file is created in the same directory as the package file. The log file has a .log file extension.

Note:
If the user importing the package is unable to access this location, you must copy the package or
send the package via FTP to the user once it is created.

Note:
Make sure that the export directory does not already contain any of the items you are exporting. If
one of the items already exists in this location, you will get an error message. You must delete any
items that were already copied and then retry creating the package file.

What Happens When You Create a Data Package?

When you click OK on the Export dialog window, the system validates that:

• Each Integration for I-deas item to be exported is a valid I-deas part, assembly, drawing, or FE model.

• You have sufficient privileges to the selected items, the specified host, and the specified path. The
Teamcenter account owner (infodba) must have write privileges to this path.

Note:
You must have transfer-out privileges to the selected datasets to export them.

• The destination package file does not already exist in the specified location.

The selected I-deas item, any items on which it depends, and any drawings (if the Related Drawings
option is chosen) are validated as a group. A validation failure of a selected item excludes that item and
its dependent items from the exported package. Any remaining groups that successfully validate are
exported.

8-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 How to Import a Data Sharing Package

Note:
If any I-deas application data files cannot be copied to the export directory, you get an error
message about an incomplete package. Since incomplete packages are not removed
automatically, you must remove them and recreate them.

How to Import a Data Sharing Package

This section explains how to import a data sharing package from I-deas into Integration for I-deas, and
what happens when you import.

Data sharing packages can include I-deas parts, assemblies, drawings, and FE models.

To import a data sharing package you must have Import privilege for Transfer-in. To export a data
sharing package you must have Export privilege for Transfer-out.

Note:
These privileges are Teamcenter settings in Access Manager.

To import a data sharing package, ensure the following option is set in the .ideas_paramXX file:

• Team.ExternalAppDataManager: False

This setting may be set to TRUE during installation to enable Integration for I-deas functionality.
Therefore, Siemens Digital Industries Software recommends that the .ideas_paramXX file used for
import is not the same as the one used for Integration for I-deas operation.

If the value is set to TRUE during import, binary drawings (the .dwg of the .drw/.dwg drawing pair) is
not imported. To correct this, delete the drawing items from Teamcenter and re-import them with the
preference set to FALSE.

During import, file names are truncated to 30 characters if the TC_truncate_file_name preference is set
to TRUE (the default).

Note:
Truncation can cause file names to become non-unique (Teamcenter handles this situation such
that it recognizes file names as unique). When the files are exported to I-deas, the uniqueness is
given by appending a unique suffix to each mon-unique file name. To preserve the original I-deas
file names for uniqueness, set the preference to FALSE to allow 132 characters maximum to be
used in the file name (I-deas file names are only 80 characters maximum).

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-11
© 2020 Siemens
 8. Data Sharing

To import a package from an I-deas installation:

1. Verify that you have set the preferences in the Teamcenter environment files. One preference is
required:

IDEAS_external_owning_user_name

See the Data Migration Setup Requirements in the Integration for I-deas Data Migration Guide for
optional preferences that affect the import process.

2. Select the folder into which you want the package items to be imported. If no folder is selected, the
package is imported into your Newstuff folder.

3. Choose Import→From TDM from the Teamcenter Tools menu to display the Import dialog
window.

4. Select the directory location and the package file name for import.

5. Click the Options button to select from the following import options:

• Swap part number (item ID) and part name (item name)
Maps the I-deas part numbers to Teamcenter item names and I-deas part names to Teamcenter
item IDs.

• Auto-assign missing item IDs

Automatically assigns a sequential Item ID when creating the item if the I-deas part number is
blank.

• Use item name as ID if item ID is missing

If the I-deas part number is blank, use the I-deas item name attribute for the item ID when
creating the item.

• Skip items with missing IDs

If the I-deas part number is blank, skip this item during the import. This causes the remainder of
the package to be skipped.

• Auto-assign conflicting item IDs

Automatically assigns an ID to the item being imported if there is an issue with the item ID.
If an I-deas item is being imported and there is an existing Teamcenter item with the same item
ID containing an I-deas dataset, a new item ID is assigned to the item being imported.
If a Teamcenter item exists with the same item ID as the incoming I-deas item, and it does not
contain an I-deas dataset, then the existing Teamcenter item is used for the incoming I-deas
data.

8-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Creating Items, Item Revisions, and Datasets

Note:
An item ID conflict occurs if the item already exists and has another I-deas dataset
associated with it.

Note:
Using the Auto-assign conflicting item IDs option requires that an ID generator be
developed.

• Use item name as ID if item ID has conflict

If the I-deas part number is determined to be a duplicate of an existing item ID, use the I-deas
item name attribute for the item ID when creating the item.

• Skip items with conflicting IDs

If the I-deas part number is determined to be a duplicate of an existing item ID, skip this item
during the import. This causes the remainder of the package to be skipped.

6. Click the OK button to accept the options.

7. Optionally, check the Create log file checkbox to generate a log file for the import operation.

8. Click OK to start the import operation.

Note:
• Place the data sharing package to be imported in an empty subdirectory to avoid confusion
between packages.

• You cannot import a package whose full path name is greater than 80 characters. (The full path
name includes the work location directory, relative path, and package file name.)

• Objects that are successfully imported for modification are modifiable in Integration for I-deas.
However, an import can fail when a conflict arises. An import conflict arises when a data
sharing package version intent conflicts with the state of the existing dataset ownership in an
importing Integration for I-deas installation. For instance, an Integration for I-deas installation
owns an item and attempts to import a data sharing package containing a new dataset version
where the data sharing package version intent is modification. This represents a conflict of
ownership and the import is terminated. The installation where the data sharing package was
created owned the dataset when the data sharing package was created.

Creating Items, Item Revisions, and Datasets

Items contained in the imported package are placed into Teamcenter based on the status of the
imported item.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-13
© 2020 Siemens
 8. Data Sharing

Note:
This also applies to items that have been renumbered due to duplicate itemIDs.

• New — The status is new if the item is a new item series due to a new item GUID (item_passport) in
the Teamcenter site (all sites in a Multi-Site Collaboration environment). A new item, item revision,
and dataset are created in Teamcenter.

• Insert — The status is insert if the item has the same part number and item GUID as another item, but
the version number and version GUID (version_passport) are new in the Teamcenter site. A new
dataset is inserted in the appropriate item revision of an existing item and a new item revision could
also be inserted depending upon the options.

• Match — The status is match if the item is exactly the same (item GUID, version GUID, and version
number match) as a dataset that already exists in the Teamcenter site. The ownership of the item is
changed to local (external ownership) in case the item is for modification and the existing matched
item in Teamcenter is for reference.

Customizing Item Type

You can define a custom item type for each individual item imported from a TDM or package file by
predefining an I-deas attribute with an item type name and setting the preference
IDEAS_import_custom_item_type_attr to identify that attribute. The item type is created based on the
value of the I-deas attribute in the TDM or the package file.

If the TDM attribute is not found, then the item type to be created is based on the preferences
IDEAS_default_item_type and IDEAS_default_item_type_<dataset type> that define the default item
type based on the I-deas data type.

Note:
The new preference IDEAS_import_custom_item_type_attr overrides those other preferences.

Import Ownership Considerations

When importing design data from I-deas to Integration for I-deas, My Teamcenter users can import data
for reference or modification. This section discusses how the imported object is handled, depending on
the version number of the object and other factors. These considerations should be kept in mind during
import to ensure successful completion of the import process.

Import I-deas Design Data for Reference

Objects that are successfully imported for reference are not modifiable in the importing Integration for I-
deas installation.

8-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Import I-deas Design Data for Modification

The version number of the import object relative to existing versions in the same item series determines
how the import object is processed for reference. In the case that the import object version number is
higher than any version in the existing item series, the modifiability of the existing version series must
be considered.

The following table defines the actions to be taken in different scenarios. The conflict action indicates
that the import fails because the intent of the import object conflicts with that of the existing version
series.

Import Object Version Relative to

Existing Item Series Item Series Modifiable
Import Action

New N/A Import

Earlier N/A Import

Same as existing nonlatest N/A Skip

Between existing N/A Import

Same as latest N/A Skip

Higher No Import

Higher Yes Conflict

Import I-deas Design Data for Modification

Objects that are successfully imported for modification are modifiable in the importing Integration for I-
deas installation.

Only the latest existing version of an item series in Integration for I-deas is considered when
determining if that item series is modifiable. An item series is not modifiable if the latest version is either
checked out or the latest version was imported or migrated for reference only.

The version number of the import object relative to existing versions in the same item series determines
how the import object is processed for modification. In the case that the import object version number is
the same or higher than that of the existing latest version, the item series modifiability and the state of
several locks must be considered.

The following table defines the actions to be taken in different scenarios. The conflict action indicates
that the import fails because the intent of the import object conflicts with that of the existing version
series.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-15
© 2020 Siemens
 8. Data Sharing

Import Object Version

Relative to Existing Item
Series Checked Out to
Item Series I-deas
Modifiable Import Action

New N/A N/A Import

Earlier N/A N/A Conflict

Same as existing nonlatest N/A N/A Skip

Between existing N/A N/A Conflict

Same as latest No N/A Set modifiable

Same as latest Yes N/A Skip

Higher No N/A Import, set modifiable

Higher Yes No Conflict

Higher Yes Yes Conflict

Other Import Options

Change Owning User For I-deas Package Import

When external ownership (the right to modify) is updated during the I-deas package file import process,
normally the owning user is defined to be the user that is doing the import (the default). You can
change the owning user of the imported dataset to be the same as the owning user of the Item Revision
where the dataset is placed. This is particularly useful where the original I-deas creation user was
applied to the dataset by a customizaton during the migration process. Change the owning user with the
following preference:

• IDEAS_external_owning_user_update_use_ItemRevision
Valid values:

TRUE — Owning user is same as Ite m Revision

FALSE — Owning user is importer.

Default value:

FALSE

8-16 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Pre-Validate I-deas Package for Import

Pre-Validate I-deas Package for Import

The I-deas package import can perform some validation checking prior to actually importing the data by
setting the following preference:

IDEAS_pre-import_validation=TRUE

Only certain types of problems can be validated prior to actually creating the data in the database, such
as name conflict, ownership conflict, and most internal item GUID conflicts. Validations with other items
within the package are not performed and conflicts between parts and drawings that are managed
within the same item revision cannot be detected until the items are created in the Teamcenter
database.

The default (FALSE) is to begin importing data to Teamcenter and only go into validation mode for the
remaining items when an item fails to import.

Valid values:

TRUE – perform I-deas package validation prior to creating data in Teamcenter.

FALSE – start package data import creation immediately.

Skipping Items With a Different Item ID In the I-deas Package During Import

By default, during import of a package file, if the Item ID for an item already exists in Teamcenter
(identified using the internal Item GUID) but it is different than the Item ID for the same item in the
package file, the Item ID that already exists in Teamcenter is used. A warning is displayed that the Item
ID was reassigned during import.

The following preference changes the warning to an error when the Item ID is changed. If the conflicting
ID option is set to skip (Skip such an item in the package import dialog box) and the preference is set,
the package import skips a renamed item, reports an error to the import log file, and aborts the import
process.

IDEAS_import_skip_renamed_items=TRUE

This does not apply when the package Item ID is missing. This preference also does not apply to drawing
and FEM items types since they may be managed with the related part or assembly.

Import Items Into Subfolders

The preference IDEAS_mig_import_add_to_folders provides mapping of projects and libraries to

folders as follows:

• The preference maps projects into folders and libraries as sub-folders under the project folder.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-17
© 2020 Siemens
 8. Data Sharing

• The creation of the folders is done by truncating the folder name to 32 characters maximum and
placing the full 80 character name in the folder description attribute.

• While querying for a folder during item creation, the program looks for a folder-parent folder
combination corresponding to the library-project mapping to find a match.

• To avoid the problems of large queries and no uniqueness of folder names, the following preferences
provide values for folder query during item creation.

• IDEAS_mig_import_parent_folder_name
This is the root folder where the nested folder hierarchy starts. If this preference is not set, or the
query doesn't find a folder, the program defaults to the current user's home folder as the root
folder.
• IDEAS_mig_import_parent_folder_name_user
This is the owning user of the root folder. If this preference is not set, the query searches for a
folder owned by the current user.

Note:
If both of these preferences aren't set, the program defaults to the current user and the user's
home folder for initiating the query and creates the folder there if it doesn't exist.

• If the I-deas TDM uses the DataMgt.HierarchySeparator parameter for hierarchical display of items,
the IDEAS_mig_import_proj_hier_sep preference can be set to the same ASCII character to provide
the same hierarchical display.

Import Standalone Drawings

The following preference (in the Teamcenter preferences) controls the item mapping of standalone
drawings that are migrated or imported:

Note:
This preference applies only to migration and import, not to checkin of standalone drawings using
Integration for I-deas.

• IDEAS_2D_drawing_autoassign_conflicting_ids
This preference specifies how I-deas standalone 2D drawings are mapped to Teamcenter Items.
During migration, drawings are typically mapped to the item (part, assembly) with the same ItemID
(this is the default migration operation). Standalone drawings are also migrated in the same way.
When an Item contains an I-deas part or assembly, the Item Revision sequence for the various Item
Revisions is defined by the creation date of the part or assembly. When the Item contains only
drawings, the creation date of each drawing migrated or imported is used to sequence the Item
Revisions. Drawings can be created at any time which may not result in the correct sequence when
multiple drawings get mapped into the same Item with no part or assembly, therefore the Item
Revisions are likely to get out of proper sequence, which can cause problems. The default behavior of

8-18 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Import Legacy Assemblies

this preference is to always create separate Items for standalone 2D drawings that have the same
ItemID.

• ALWAYS – This is the default. Always auto-assign a new ItemID to standalone drawings with
duplicate ItemIDs and place each drawing into its own Item.

• NEVER – Never auto-assign ItemIDs for standalone drawings. Using this option will probably
require pre-configured items and Item Revisions, or custom user exit code to manage the process
without errors.

• UNLESS_WITH_MODEL_OF_SAME_ID – Place standalone drawings into an Item Revision that

contains a part or assembly with the same ItemID; otherwise, auto-assign a new ItemID and place
the standalone drawing into its own Item.

Import Legacy Assemblies

Legacy assemblies (pre-MS8) can be imported by setting the following preference:

IDEAS_import_allow_legacy_assemblies

This preference controls whether mixed mode I-deas assemblies are imported into Teamcenter. Mixed
mode assemblies are post-MS8 assemblies that contain pre-MS8 subassemblies.

Valid values:

TRUE
Mixed mode I-deas assemblies can be imported into Teamcenter.

FALSE
Mixed mode I-deas assemblies cannot be imported into Teamcenter.

Default value:

FALSE

Scope for Preferences

To support different import and migration functionality for different user groups, most preferences
related to migration and data sharing have been changed so that they can be defined at any scope: user,
group, or site.

However, the following preferences are an exception and are required to be site scope only:

IDEAS_one_version_per_revision

IDEAS_one_version_per_revision_ps_only

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q 8-19
© 2020 Siemens
 8. Data Sharing

IDEAS_auto_assign_all_itemid

IDEAS_ds_attrsync_update_item_on_latest_rev_only

IDEAS_update_item_revision_create_date

IDEAS_sec_rep_group_names

IDEAS_use_item_level_right_to_modify

IDEAS_external_owning_user_name

TC_appref_registry_site

IDEAS_multi_site_impl

IDEAS_multisite_util_batch_size

IDEAS_multisite_ds_never_exclude_rels

IDEAS_multisite_query_by_item_id

TC_relation_required_on_transfer

TC_relation_required_on_export

8-20 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 A. Glossary

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 A. Glossary
This appendix defines Teamcenter terms.

A
Assembly
Compound object that is assembled from other objects and may add additional information to their
interpretation. In the context of an assembly, other assemblies are called subassemblies, while
noncompound objects are called components.

Attribute
Named storage variable that describes an object and is stored with the object. Users can search the
database for objects using the object's attributes.
In an object, an attribute is a name/value pair; in the database, an attribute is a field.

B
BLOB
Binary large object; attribute type of undefined structure. BLOBs are stored as binary images within an
object.

Bulk Data
Physical information represented in the database by a data item. Examples of bulk data are file system
items, paper documents, and microfiche. The Teamcenter database describes the bulk data. The bulk
data resides elsewhere, for example, in a file system or in a filing cabinet. See also Data Item.

C
Client
Role played by a software component of a system when it requests particular services be performed on
its behalf by another entity, a server. In the case of data migration, the Migration Wizard is a client that
gathers user input and requests services from the TDS server. See also Server.

Component
Objects used to build up an assembly or subassembly.

D
Data Item
Teamcenter object representing bulk data defined and manipulated by application products, for
example, papers that reside in a filing cabinet, directories and files that reside in a file system, Excel

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q A-1
© 2020 Siemens
 A. Glossary

spreadsheets, and CAD model and drawing files. Metadata for the data item resides in the Teamcenter
database. See also Bulk Data and Metadata.

F
Folder
Graphical representation of an aggregation of objects, such as a group, class, or subclass. For easy
distinction in the class hierarchy, each of these aggregations has a different type of folder icon
associated with it: a group folder icon, a class folder icon, or a subclass folder icon.

G
Globally Unique Identifier
Identifier that is assigned to each I-deas data item by the I-deas applications software and used to
identify the data item. See also Item GUID and Version GUID.

GUID
See Globally Unique Identifier.

I
I-deas
UGS’s integrated CAD/CAM/CAE solution that is used to design, analyze, test, and manufacture products.

I-deas Migration Wizard

Client for the migration processing tool. The I-deas Migration Wizard interacts with the user to gather
information and requests migration services.

Integration for I-deas

Product that integrates Teamcenter and I-deas to provide a single data management environment for
users. Integration for I-deas users author their data in I-deas and manage the data in Teamcenter.
Integration for I-deas is comprised of the My Teamcenter user interface and the I-deas Data Services
(IDS) and Team Data Sharing (TDS) modules. See also I-deas and My Teamcenter.

Integration for I-deas Host

Teamcenter host that functions as the gateway through which the Migration Wizard initiates
communications with the TDS server for data migration processing.

Item GUID
Common GUID assigned to all versions of an I-deas data item in the data item series. See also GUID and
Version GUID.

A-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 M
Metadata
Object description in the Teamcenter database.

Model File View Window

Separate window launched from My Teamcenter that connects to I-deas and allows users to view and
manage the contents of their active I-deas model files.

My Teamcenter
Teamcenter rich client application that is the main access point for managing product information. My
Teamcenter provides the functionality for creating objects in the Teamcenter database, querying the
database for objects, checking in and checking out objects, and managing tasks. Users can also open
objects, automatically launching the related application.
Each user has a personal My Teamcenter window that displays product information as graphical objects.
Although users share product information across the enterprise, they organize this information
individually in personal workspaces.

O
Occurrence
Hierarchical structure relationship between the immediate parent assembly and its child component
item or item revision in a precise assembly. Sometimes called relative occurrence.

P
PCL Server
Software that performs the first phase of data migration processing to convert I-deas data for use in
Integration for I-deas.
The PCL server exposes the I-deas project metadata to the TDS server for interpretation.

R
Relative Occurrence
See Occurrence.

S
Server
System software component that performs a specifically defined set of software services on behalf of
one or more clients. In a typical Teamcenter installation, servers are centralized on dedicated hosts that

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q A-3
© 2020 Siemens
 A. Glossary

support a large number of clients. Clients are distributed on hosts connected to the servers via various
networking techniques. See also Client.

SQL
See Structured Query Language.

Staging Directory
Storage location created by the data migration software to store the package file for the structure being
processed during Integration for I-deas data migration.

Structure
Software processing constraint developed to limit the number of I-deas top-level items processed
simultaneously for data migration. The number of top-level items processed per structure can be
adjusted.

Structured Query Language

ANSI standard command and embedded language for manipulating data in a relational database.

T
Teamcenter Application Root Directory
Directory location of the Teamcenter shared binary executables. The TC_ROOT environment variable
defines this location. Generally, the contents of this directory change only with a new version of
Teamcenter.

Teamcenter Data Directory

Directory location of the Teamcenter shared data subdirectories and files. The TC_DATA environment
variable defines this location. Each data directory is associated with a single database instance.

V
Version GUID
Distinct GUID assigned to each separate version of an I-deas data item in the data item series. The
version GUID uniquely identifies the data item. See also GUID.

A-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 B. Integration for I-deas Troubleshooting
Adding Data For Troubleshooting ─────────────────────────── B-3
Increasing Java memory ───────────────────────────────── B-4
Symptom ───────────────────────────────────────────── B-5
Cause ─────────────────────────────────────────────── B-5
Solution ────────────────────────────────────────────── B-5
Symptom ───────────────────────────────────────────── B-6
Cause ─────────────────────────────────────────────── B-6
Solution ────────────────────────────────────────────── B-6
Symptom ───────────────────────────────────────────── B-8
Cause ─────────────────────────────────────────────── B-8
Solution ────────────────────────────────────────────── B-8
Symptoms ───────────────────────────────────────────── B-9
Cause ─────────────────────────────────────────────── B-9
Solution ────────────────────────────────────────────── B-9
Symptom ──────────────────────────────────────────── B-11
Cause ─────────────────────────────────────────────── B-11
Solution ───────────────────────────────────────────── B-11
Symptom ──────────────────────────────────────────── B-12
Cause ─────────────────────────────────────────────── B-12
Solution ───────────────────────────────────────────── B-12
Symptom ──────────────────────────────────────────── B-13
Cause ─────────────────────────────────────────────── B-13
Solution ───────────────────────────────────────────── B-13
Symptom ──────────────────────────────────────────── B-14
Cause ─────────────────────────────────────────────── B-14
Solution ───────────────────────────────────────────── B-14
Symptom ──────────────────────────────────────────── B-15
Cause ─────────────────────────────────────────────── B-15
Solution ───────────────────────────────────────────── B-15
Symptom ──────────────────────────────────────────── B-16
Cause ─────────────────────────────────────────────── B-16
Solution ───────────────────────────────────────────── B-16
Symptom ──────────────────────────────────────────── B-17
Cause ─────────────────────────────────────────────── B-17
Solution ───────────────────────────────────────────── B-17
Symptom ──────────────────────────────────────────── B-18
Cause ─────────────────────────────────────────────── B-18
Solution ───────────────────────────────────────────── B-18
Symptom ──────────────────────────────────────────── B-19
Cause ─────────────────────────────────────────────── B-19
Solution ───────────────────────────────────────────── B-19
Symptom ──────────────────────────────────────────── B-20
Cause ─────────────────────────────────────────────── B-20
Solution ───────────────────────────────────────────── B-20
Symptom ──────────────────────────────────────────── B-21
Cause ─────────────────────────────────────────────── B-21

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
 Solution ───────────────────────────────────────────── B-21
Symptom ──────────────────────────────────────────── B-22
Cause ─────────────────────────────────────────────── B-22
Solution ───────────────────────────────────────────── B-22
Symptom ──────────────────────────────────────────── B-23
Cause ─────────────────────────────────────────────── B-23
Solution ───────────────────────────────────────────── B-23
Symptom ──────────────────────────────────────────── B-24
Cause ─────────────────────────────────────────────── B-24
Solution ───────────────────────────────────────────── B-24
Symptom ──────────────────────────────────────────── B-25
Cause ─────────────────────────────────────────────── B-25
Solution ───────────────────────────────────────────── B-25
Symptom ──────────────────────────────────────────── B-26
Cause ─────────────────────────────────────────────── B-26
Solution ───────────────────────────────────────────── B-26
Symptom ──────────────────────────────────────────── B-27
Cause ─────────────────────────────────────────────── B-27
Solution ───────────────────────────────────────────── B-27
Symptom ──────────────────────────────────────────── B-28
Cause ─────────────────────────────────────────────── B-28
Solution ───────────────────────────────────────────── B-28
Symptom ──────────────────────────────────────────── B-29
Cause ─────────────────────────────────────────────── B-29
Solution ───────────────────────────────────────────── B-29
Symptom ──────────────────────────────────────────── B-30
Cause ─────────────────────────────────────────────── B-30
Solution ───────────────────────────────────────────── B-30
Symptom ──────────────────────────────────────────── B-31
Cause ─────────────────────────────────────────────── B-31
Solution ───────────────────────────────────────────── B-31
Symptom ──────────────────────────────────────────── B-32
Cause ─────────────────────────────────────────────── B-32
Solution ───────────────────────────────────────────── B-32
Symptom ──────────────────────────────────────────── B-33
Cause ─────────────────────────────────────────────── B-33
Solution ───────────────────────────────────────────── B-33
Symptom ──────────────────────────────────────────── B-34
Cause ─────────────────────────────────────────────── B-34
Solution ───────────────────────────────────────────── B-34
Symptom ──────────────────────────────────────────── B-35
Cause ─────────────────────────────────────────────── B-35
Solution ───────────────────────────────────────────── B-35
Symptom ──────────────────────────────────────────── B-36
Cause ─────────────────────────────────────────────── B-36
Solution ───────────────────────────────────────────── B-36
Symptom ──────────────────────────────────────────── B-37
Cause ─────────────────────────────────────────────── B-37
Solution ───────────────────────────────────────────── B-37

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
 Symptom ────────────────────────────────────────────
B-38
Cause ───────────────────────────────────────────────
B-38
Solution ─────────────────────────────────────────────
B-38
Symptom ────────────────────────────────────────────
B-39
Cause ───────────────────────────────────────────────
B-39
Solution ─────────────────────────────────────────────
B-39
Symptom ────────────────────────────────────────────
B-40
Cause ───────────────────────────────────────────────
B-40
Solution ─────────────────────────────────────────────
B-40
Symptom ────────────────────────────────────────────
B-41
Cause ───────────────────────────────────────────────
B-41
Solution ─────────────────────────────────────────────
B-41
Symptom ────────────────────────────────────────────
B-42
Cause ───────────────────────────────────────────────
B-42
Solution ─────────────────────────────────────────────
B-42
Symptom ────────────────────────────────────────────
B-43
Cause ───────────────────────────────────────────────
B-43
Solution ─────────────────────────────────────────────
B-43
Symptom ────────────────────────────────────────────
B-44
Cause ───────────────────────────────────────────────
B-44
Solution ─────────────────────────────────────────────
B-44
Symptom ────────────────────────────────────────────
B-45
Cause ───────────────────────────────────────────────
B-45
Solution ─────────────────────────────────────────────
B-45
Symptom ────────────────────────────────────────────
B-46
Cause ───────────────────────────────────────────────
B-46
Solution ─────────────────────────────────────────────
B-46
Symptom ────────────────────────────────────────────
B-47
Cause ───────────────────────────────────────────────
B-47
Solution ─────────────────────────────────────────────
B-47
Symptom ────────────────────────────────────────────
B-48
Cause ───────────────────────────────────────────────
B-48
Solution ─────────────────────────────────────────────
B-48
Symptom ────────────────────────────────────────────
B-49
Cause ───────────────────────────────────────────────
B-49
Solution ─────────────────────────────────────────────
B-49
Symptom ────────────────────────────────────────────
B-51
Cause ───────────────────────────────────────────────
B-51
Solution ─────────────────────────────────────────────
B-51
Symptom ────────────────────────────────────────────
B-56
Cause ───────────────────────────────────────────────
B-56
Solution ─────────────────────────────────────────────
B-56
Release Notes ─────────────────────────────────────── B-56
Customer Support ──────────────────────────────────── B-56

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q

© 2020 Siemens
Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q
© 2020 Siemens
 B. Integration for I-deas Troubleshooting
Symptoms and solutions related to problems with Integration for I-deas are described in this appendix.

Note:
In some sections, a specific version of Teamcenter or Integration for I-deas may be used to
illustrate a symptom, solution, or example. The versions of Teamcenter and Integration for I-deas
applicable for your situation are based on the software versions installed at your site.

The following topics are discussed:

• Connection time outs

• Connection time out due to stale server registration

• Connection time out due to stale Orbix process

• Connection issues

• External file display from UNIX to Windows

• NamedReference error message at checkin

• Teamcenter Visualization problems on Sun Workstations

• I-deas does not launch

• File Name Length Error when sending items to I-deas

• IMAN Export Directory Error When Sending Items to I-deas

• On Unix, a second I-deas session is launched when launching Integration for I-deas.

• Items are displayed in Manage Bins, but not displayed in Integration for I-deas window or shows the
items with incorrect icons

• Double-clicking on a dataset doesn't open application

• Creating JT files

• Transfer failure while loading error during checkout/checkin of large assemblies

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-1
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

• Components are not properly oriented when viewing I-deas assembly JT in Structure Manager

• IDNPortal.bat file launches Rich Client, but not Integration for I-deas

• The I-deas menu is not in My Teamcenter after launching IDNPortal.bat

• I-deas Assembly Configured Incorrectly

• Deleting Large Assemblies Causes Integration for I-deas to Lock Up

• CGM Creation Error During Save to Teamcenter

• Structure Manager Open in I-deas Command

• Arrangement Creation Failure During Assembly Checkin

• Cannot Connect to Rich Client from I-deas

• Error When I-deas Attributes Contain Multi-Byte Characters

• Ref Mod Warning When Changing the Status of a Dataset to New

• Unknown Send to I-deas Error

• On a Single Machine Can Only Run One Translator at a Time

• Login Error When Trying to Run an ideastojt_direct or ideastocgm_direct Translator

• I-deas to JT or I-deas to CGM Translation is Not Provided as an Option in My Teamcenter

• JT Files are Created and Loaded But When Displayed They are Empty

• When a Translation is Executed, a Headless Exception Error is Displayed

• When a Harness is Translated, Dressings are Shown Instead of Wire Path

• Cannot Write to the TeamBrowser Log File

• Cannot delete an Item or Item Revision because it is referenced by ETSTranslationRequest

• Arrangements are not created on frozen items using Translation Services

• Arrangements are not created on imported items that are owned externally

• Arrangements are not created using Translation Services during data sharing import or migration

B-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Adding Data For Troubleshooting

• Translations are stopped and have time out message in the module log

• There is a long delay between completion of a translation and marked as complete in the TS
administration command prompt window

• After Teamcenter fcc process has crashed or terminated, next translation hangs

• Vague message contains error_80XXXX

• Both CMM and Integration for I-deas are installed, but Integration for I-deas menus are not displayed
in Teamcenter

• Teamcenter Database Not Configured Properly for Integration for I-deas

• When opening a large model both Teamcenter and I-deas hang

• Release notes

• Customer support

Note:
For additional troubleshooting data related to installing Integration for I-deas, see Troubleshooting
in the Integration for I-deas Installation Guide. For additional information on other problems and
issues related to installing and running Integration for I-deas, see the Integration for I-deas
Release Notes.

Adding Data For Troubleshooting

It's helpful to have as much data as possible when trying to troubleshoot a problem. When you are
planning to report a problem to Siemens Digital Industries Software, you can increase the amount of
data acquired by setting the –D parameter, DLogLevel, in the Rich Client startup script. The additional
data is added to the TB.log file which is written to the TcII temp directory.

To increase the amount of data captured, modify the existing lines as follows in to the Rich Client startup
script (IDNPortal.bat) after similar JAVA settings:

start Teamcenter.exe %* %IDEAS_APP_INVOKE% -vmargs –DLogLevel=4

-Djava.io.tmpdir=
"%TCII_TMP%"
-Dorg.omg.PortableInterceptor.ORBInitializerClass.NXMIInterceptor=
COM.metaphasetech.tasks.ids.ops.cad._ideas.proxy.NXMIInterceptor
-Djacorb.poa.queue_wait=on -DIDEAS_FILES_EXPORT_DIR="%TCII_TMP%"

Optionally, to include performance statistics in the log file, modify the – DPerformanceMode option in
the start Teamcenter.exe line as follows:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-3
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

start Teamcenter.exe %* %IDEAS_APP_INVOKE% -vmargs –DLogLevel=4 –

DPerformanceMode=
TRUE -Djava.io.tmpdir="%TCII_TMP%"
-Dorg.omg.PortableInterceptor.ORBInitializerClass.NXMIInterceptor=
COM.metaphasetech.tasks.ids.ops.cad._ideas.proxy.NXMIInterceptor
-Djacorb.poa.queue_wait=on -DIDEAS_FILES_EXPORT_DIR="%TCII_TMP%"

Note:
This setting must be made in the IDNPortal.bat startup script. The Java memory settings made in
the Teamcenter.ini file are not honored by the scripts shipped with Integration for I-deas.

Increasing Java memory

You can increase the Java memory settings to improve performance and overall operation. An indication
that the Java memory needs to be increased is if you get an out of memory error similar to the following
displayed in the Teamcenter console or <username>_TcRAC.log file:

ERROR: Exception while executing operation -

com.teamcenter.rac.ideasnavigator.commands.SendToIdeasCommand
$SendToIdeasOperation
java.lang.OutOfMemoryError: Java heap space

To increase the Java memory settings, in the IDNPortal.bat startup script increase the –Xms256m and
Xmx512m options in the start Teamcenter.exe line. These are set during installation and may need to
be increased depending upon the needs at your site.

The change must be made in the IDNPortal.bat startup script because the settings in the Teamcenter.ini
script are not honored by Integration for I-deas.

These changes can also be made in ideas_translator.bat for the I-deas translator and store_configs.bat
for the store configuration application.

B-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Connection Time Outs

Problem: Connection Time Outs

This section provides possible solutions to connection time out problems.

Symptom

Integration for I-deas fails to connect to I-deas.

Cause

There are several possible causes for this problem.

Solution

Following is a process to determine possible solutions for this problem:

1. Ensure the user account has write/read access to the temporary directory specified during
installation. You can identify this directory by checking PORTAL_DIR/make_ior.bat to see where
output is appended.

2. When Rich Client is started, make sure the ns_ior.txt file is created in the temporary directory.

3. When I-deas is started it should execute the make_ior.bat file, which should output tpn.tmp in the
temporary directory.

4. Verify the orbixd process is running. This should start when the idn_start_portal script is executed
(during boot on UNIX machines).

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-5
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Connection Time Out Due to Stale Server Registration

This section provides a possible solution to a connection time out problem.

Symptom

One of the two following symptoms can occur:

Integration for I-deas fails to connect to I-deas and generates a

java.lang.ArrayIndexOutOfBoundsException error. The I-deas error*.out file lists an error such as:

The name ugs/ideas10/cinsun5/ideasmanager is already bound

to a reference in the naming service.

I-deas fails to connect to Teamcenter; Teamcenter won't launch. An error message is listed such as:

eWIP/Open-IDEAS is not enabled

Cause

A possible cause for this problem is that Integration for I-deas is unable to connect with I-deas due to a
stale I-deas server registered with Orbix E2A.

Solution

Following is a possible solution for this problem:

1. To find the problematic server, issue an itadmin command such as:

itadmin ns list ugs/ideas10/<HOST>

2. You should get a response that I-deas is running such as:

ideasmanager Object

3. Locate the stale server in the list, and remove it using a command such as:

itadmin ns remove ugs/ideas10/<HOST>/<SERVER_NAME>

(where SERVER_NAME, in this example, is ideasmanager)

4. Restart I-deas to have the software re-register itself with Orbix E2A and Integration for I-deas.

Integration for I-deas and Teamcenter can now connect to I-deas.

B-6 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Solution

Following is another possible solution for this problem:

1. Remove the Orbix server:

%SDRC_INSTALL%\bin\Setup_Varbs
%SDRC_INSTALL%\INSTALL\OrbixE2AInstall.exe /r

2. Then re-install the Orbix server:

%SDRC_INSTALL%\INSTALL\OrbixE2AInstall.exe /i

Note:
When you remove the Orbix server, you also disconnect Orbix from other applications that may be
using it.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-7
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Connection Time Out Due to Stale Orbix Process

This section provides possible solutions to a connection time out problem.

Symptom

The following error message may be displayed if there is a stale Orbix process running:

org.omg.CORBA.COM_FAILURE: HO minor code: 10086 completed:

No ideas_sysenvlog.exe-Application Error" The instruction at "xxx"
referenced memory at "xxx". The memory could not be "read".

Cause

Following is a possible cause for this problem:

There could be a stale Orbix process running.

Solution

Following is a possible solution for this problem:

Check Obrix processes currently running and restart, if necessary.

B-8 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Connection Issues

Problem: Connection Issues

This section provides possible solutions to several connection problems.

Symptoms

Integration for I-deas cannot connect to I-deas.

Cause

Following are possible causes for this problem:

• Improper Integration for I-deas temporary directory

• Wrong I-deas parameter file

• Missing or misconfigured ns_ior.txt file

• Missing or misconfigured tpn.tmp file

• Nonstandard I-deas startup

• Teamcenter references in default library path

Solution

Following are the possible solutions for this problem:

• Improper Integration for I-deas temporary directory: Each Integration for I-deas user must have
exclusive write access to this directory on a given host. This cannot be a shared location. Check the
directory specified by the –Djava.io.tmpdir Java command argument in the Rich Client start script for
compliance.

• Wrong I-deas parameter file: The I-deas start script references the location of the I-deas Parameter file
through the IDEAS_PARAMXX (where XX is the I-deas version) environment variable set by the I-deas
setup_varbsscript. Check that the setup_varbs definition for IDEAS_PARAMXX (where XX is the I-
deas version) points to the correct I-deas parameter file directory.

• Missing or misconfigured ns_ior.txt file: This file contains a Naming Service IOR string and is
generated by the make_ns_ior script every time the Rich Client start script is run. The file is written to
the Integration for I-deas temporary directory specified by the –Djava.io.tmpdir Java command
argument in the Rich Client start script. Integration for I-deas uses this file to access I-deas Orbix E2A
services. If the file exists and has a date/time stamp that matches the last time the Rich Client start
script was run, the naming service IOR string in the file may not be correct. Run itadmin ns resolve
and compare the IOR with that contained in ns_ior.txt.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-9
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

• Missing or misconfigured tpn.tmp file: This file contains the IOR string for IS_Server. Integration for I-
deas uses it to connect to a running session of I-deas. The file is written to the Integration for I-deas
temporary directory specified by the –Djava.io.tmpdir Java command argument in the IDNPortal
script. It is written by the make_ior script every time I-deas is launched from Rich Client or when the I-
deas start script is run.
If the tpn.tmp file exists and has a date/time stamp that matches the last time I-deas was started by
Rich Client or by the I-deas start script, the IOR string in the file may not be correct. Enter the oaxx
execute cmd command on Windows or oaxx execute xterm on UNIX in the I-deas command panel.
Look for the IS_SERVER_IIOP environment variable. The tpn.tmp file should contain the IOR string
referenced by this variable.
If IS_SERVER_IIOP is not set, look for OI_SERVER_IIOP. If that value is set, look for the
IDEAS_PARAMXX (where XX is the I-deas version) environment variable. Open the I-deas parameter
file in that directory and see if Team.ExternalDataManager is set to true. If not, either
IDEAS_PARAMXX (where XX is the I-deas version) is referencing a wrong location or the parameter
file is incorrect. If OI_SERVER_IIOP is not set, or if the appropriate oaxx execute command does not
bring up a shell, OI is not initialized properly.

• Nonstandard I-deas startup: The I-deas startup script or batch file in the PORTAL_DIR directory
contains information needed to connect to I-deas from Integration for I-deas. If you use another
method to start I-deas, you may need to execute the following command in the I-deas command
window:

oaxx execute PORTAL_DIR/make_ior.[bat|ksh]

This generates the tpn.tmp file in the temporary directory, which is needed to connection between
Rich Client and I-deas.

• Teamcenter references in default library path: The default library path cannot contain any specific
Teamcenter references. This is especially true for the tc_profilevars script; it should not be executed.
The script is located in the TC DATA directory in your profile. The default library paths are:

• HP: SHLIB

• IBM: LIBPATH

• SUN: LD_LIBRARY_PATH

B-10 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: External File Display From UNIX to Windows

Problem: External File Display From UNIX to Windows

This section provides a possible solution to a display problem.

Symptom

External JT files do not show up in Teamcenter Visualization on a Windows machine remotely logged in
to a UNIX machine.

Cause

Teamcenter Visualization does not support the remote login into UNIX.

Solution

Log in to the UNIX machine from another UNIX machine, or work directly on the workstation running
Teamcenter Visualization to properly view the JT files.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-11
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: NamedReference Error Message at Checkin

This section provides a possible solution to a checkin problem.

Symptom

Attempts to check in items to Teamcenter from I-deas through Integration for I-deas generate a missing
NamedReference error.

Cause

A possible cause for this problem is an out-of-date schema file on the client workstation.

Solution

For a possible solution for this problem, run one of the following commands:

• UNIX:
$TC_BIN/install -regen_schema_file -u=infodba -p=infodba -g=dba

• Windows:
%TC_BIN%\install -regen_schema_file -u=infodba -p=infodba -g=dba

B-12 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Teamcenter Visualization Problems on Sun Workstations

Problem: Teamcenter Visualization Problems on Sun Workstations

This section provides a possible solution to a problem on Sun workstations.

Symptom

Teamcenter Visualization crashes or does not operate correctly on Sun workstations.

Cause

A possible causes for this problem is that system hardware and OS specifications are not in compliance
with requirements.

Solution

Teamcenter Visualization may fail on Sun workstations unless the following minimum hardware and OS
requirements are met:

• SUN Solaris 8
• SUN Solaris 8 Recommended Patch Cluster (2/2002) or newer
• Java JRE 1.3.1_01 and required patches
• Patch 108652-50 or newer revision
• Patch 108940-41 or newer revision
• 24-bit graphics card

Note:
Teamcenter Visualization is not supported in remote mode. If you run Teamcenter Visualization
remotely and send displays across a network, images do not display correctly.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-13
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: I-deas Does Not Launch

This section provides a possible solution to an I-deas non-start problem.

Symptom

I-deas doesn't launch.

Cause

A possible cause for this problem is that OGL graphics is not supported on the machine where you're
trying to run I-deas.

Note:
This is only one possible cause for an I-deas non-start problem. For additional information on
running I-deas and more extensive troubleshooting, see the I-deas user documentation.

Solution

I-deas supports OGL graphics by default. If your machine doesn't support OGL graphics, then you need
to modify the start script to provide an option to OGL.

Modify the start_ideas script to add the —d (device) option. The script is typically located in the
Teamcenter Rich Client portal directory.

B-14 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: File Name Length Error When Sending Items to I-deas

Problem: File Name Length Error When Sending Items to I-deas

This section provides a possible solution when you receive an error when sending items to I-deas.

Symptom

Sending items to I-deas from Teamcenter fails and displays a message that the directory path is longer
than 39 characters.

Cause

The directory path is longer than 39 characters.

Solution

I-deas has an 80 character limit for file name length. This includes the directory path for the file. The
part file name is determined to be 41 characters maximum. This allows only 39 characters for the
remaining file name length.

To set the directory path location to 39 characters maximum, perform one of the following:

• Set the path specified by the TCExportDir variable in the client_specific.properties file. The file is
located in the Teamcenter Rich Client installation.

• Modify the startup script, IDN_PORTAL.bat (Microsoft® Windows®) or idn_start_portal (Unix),

located in the Teamcenter Rich Client installation. Modify the script by adding the – D parameter with
the IDEAS_FILES_EXPORT_DIR variable set to the directory path.
For example, add the following (entered on one line) to the startup script after other –D parameters
in the file:

start Teamcenter.exe %* %IDEAS_APP_INVOKE% -vmargs -Djava.io.tmpdir=

"%TCII_TMP%" –DIDEAS_FILES_EXPORT_DIR=”D:\ideasdownload”

The location specified in the startup script supersedes the location specified by the TCExportDir
variable.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-15
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Teamcenter Export Directory Error When Sending Items to

I-deas
This section provides a possible solution when you receive an error when sending items to I-deas.

Symptom

An error message indicating null CadPrivateData may be displayed:

Cause

The TCExportDir value in the client_specific.properties file is in the wrong format.

Solution

1. Open the file TC_ROOT\portal\plugins\configuration_2007.1.0\client_specific.properties and

search for the TCExportDir value.

2. The following is an example of the value:

# Export Directory
TCExportDir=d:/TCE200~1/portal/temp

3. Ensure the path uses forward slashes ( / ) and not backward slashes ( \ ). If backward slashes are
being used, change them to forward slashes and save the file. Also, the file path can only be 80
characters maximum.

B-16 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
Problem: On Unix, a Second I-deas Session is Launched When Launching Integration for I-deas From I-deas

Problem: On Unix, a Second I-deas Session is Launched When

Launching Integration for I-deas From I-deas
This section provides a possible solution to a problem when you launch Integration for I-deas from I-deas
on Unix.

Symptom

On Unix, when you launch Integration for I-deas from I-deas, another I-deas session is also launched.

Cause

The setup_varbs script in I-deas 12 has been changed which causes the incorrect version of the Orbix
shared library to load.

Solution

In the make_nx_ior.ksh file, add a line after the call to setup_varbs as follows:

.scratch/ideas12/bin/setup_varbs
.$IT_CONFIG_DOMAINS_DIR/../bin/${IT_DOMAIN_NAME}_env

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-17
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Items Are Displayed In Manage Bins, But Not Displayed In

Integration for I-deas Window or Shows the Items With Incorrect
Icons
This section provides a possible solution to a problem where the Integration for I-deas window doesn't
show the items in the model file, or shows the items with incorrect icons (which look like three
overlapping pieces of paper) After synchronization the icons are corrected to lock/unlock.

Symptom

When you open a very large model file, the I-deas Manage Bins dialog contains all of the items, but the
Integration for I-deas Integration for I-deas window doesn't contain any items (it's empty).

Cause

A possible cause for this problem is the Orbix service.

Solution

Following is a possible solution for this problem:

Add the following preference to the Teamcenter preferences:

IDEAS_SleepAfterConnecting=true

Note:
This preference does not fix the incorrect icons.

B-18 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Double-Clicking on a Dataset Doesn't Open Application

Problem: Double-Clicking on a Dataset Doesn't Open Application

This section provides a possible solution to a problem where an error occurs when you double-click on a
dataset.

Symptom

When you double-click on a dataset, the dataset expands to show relations and doesn't open the I-deas
application.

Cause

I-deas is not connected.

Solution

Following is a possible solution for this problem:

Ensure that Integration for I-deas is completely installed and I-deas and Teamcenter are connected.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-19
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Creating JT Files

This section provides a possible solution to a problem where JT files are not created.

Symptom

JT files are not created. The following error message is provided:

Some JT Conversion Errors were encountered.

The messages will be logged to file:............

Cause

A possible cause for this problem is that the Integration for I-deas and I-deas preferences have not been
set.

Solution

Following is a possible solution for this problem:

Set the following preferences:

I-deas preferences:

• Team.AssociatedFileGenerateParts: 1

• Team.AssociatedFileGenerateAssemblies: 1

• Team.AssociatedFileIdi: 1

Integration for I-deas preferences:

• IDEAS_part_create_jt = TRUE

• IDEAS_assembly_create_jt = TRUE

B-20 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Transfer Failure While Loading Error During Checkout/Checkin of Large Assemblies

Problem: Transfer Failure While Loading Error During Checkout/

Checkin of Large Assemblies
This section provides a possible solution to a problem where an error occurs during checkout or checkin
of large assemblies.

Symptom

During checkout of large assemblies, the checkout fails and following error is provided:

Transfer failure while loading

The following may also be displayed in the Rich Client console window:

org.omg.CORBA.INTERNAL: remote exception — Undefined system exception

.....
COM.metaphasetech.tasks.ids.ops.cad._ideas.xfer.exp.CADExportAssembly
Impl.fillCADData
(CADExportAssemblyImpl.java:137)

Cause

A possible cause for this problem is the Orbix buffer is not large enough. The default Orbix buffer sized is
512 KB.

Solution

Following is a possible solution for this problem:

Set the Orbix buffer to the largest possible size to unlimited as follows:

Source the setup_varbs script from the I-deas installation, then issue the following Orbix command (the
following lines represent the entire command and must be issued on a single line):

itadmin variable create –scope eds.ideas10 –t long –v ––1

policies:iiop:buffer_sizes_policy:max_buffer_size

Note:
Where —1 is two dashes with no space and a 1

Execute this script once for each client installation.

This setting is kept on the workstation and remains set between Integration for I-deas sessions.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-21
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Components Are Not Properly Oriented When Viewing I-

deas Assembly JT in Structure Manager
This section provides a possible solution to a problem where components are not positioned correctly
during creation of JT files.

Symptom

When viewing assembly JTs in Teamcenter Structure Manager, the components are not positioned
correctly when compared to the active assembly configuration. Components are viewed in the as built
location. This can occur through the Integration for I-deas Save operation or asynchronous ETS
translation.

Note:
This problem is only applicable when the preference IDEAS_save_configuration=FALSE
(configuration is turned off).

Cause

A possible cause for this problem is the active configuration is not being identified as a Design
Configuration during translation and the associated default settings related to the handling of this
information are not correct.

Note:
This problem only occurs when assemblies are created in I-deas without the Design Configuration
option active.

Solution

The Assembly.ExportActiveConfigData parameter (added in I-deas 10m1) controls how the

configuration data is handled during JT creation. The default value is 0, which results in the
configuration data not being included in the JT creation for non-design configurations. To ensure proper
JT creation and viewing, define the parameter as follows:

Assembly.ExportActiveConfigData: 0

Define this parameter in all I-deas parameter files referenced by Integration for I-deas clients and the ETS
ideastojt translator, if deployed.

B-22 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: IDNPortal.bat File Launches Rich Client, But Not Integration for I-deas

Problem: IDNPortal.bat File Launches Rich Client, But Not

Integration for I-deas
This section provides a possible solution to a problem where you can't launch Integration for I-deas
when running IDNPortal.bat.

Symptom

When you launch Integration for I-deas using the IDNPortal.bat file, Rich Client launches but Integration
for I-deas doesn't launch.

Cause

A possible cause for this problem is the portal.bat file has been edited at the site (due to site
customizations). As a result, the Integration for I-deas installation routine was unable to properly read
the portal.bat file when creating the IDNPortal.bat file..

Solution

Following is a possible solution for this problem:

Revert the portal.bat file back to it's original installed version, then reinstall Integration for I-deas.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-23
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: The I-deas Menu Is Not In My Teamcenter After Launching

IDNPortal.bat
This section provides a possible solution to a problem where the I-deas menu is not displayed in My
Teamcenter.

Symptom

When you launch Integration for I-deas using the IDNPortal.bat file, the I-deas menu is not displayed in
My Teamcenter.

Cause

Integration for I-deas configuration error.

Solution

Verify the following:

1. ADDON entries in the portal.properties file in the Rich Client directory (TC_ROOT\portal\plugins
\configuration_2007.1.0) contain:

com.teamcenter.rac.explorer.ExplorerApplicationMenuBar.ADDON=
com.teamcenter.rac.ideasnavigator.IDEASTcMenuBuilder

Note:
There is a case where there was a duplicate ADDON entry that did not contain this string and
caused the error.

2. The following preference is set:

IMAN_show_open_in_ideas_button=true

Steps 2 and 3 are automatically done by the install program. However, this problem can occur if the
install program did not perform correctly or some install steps were bypassed.

Note:
There is a case where a custom portal.bat file caused the install to not perform step 2 correctly.

B-24 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: I-deas Assembly Configured Incorrectly

Problem: I-deas Assembly Configured Incorrectly

This section provides a possible solution to a problem when sending an assembly to I-deas.

Symptom

When you send an assembly to I-deas that is configured with earlier revisions of components, you get an
error message that states the assembly is not configured properly.

Cause

The assembly contains components that are an earlier revision than what was originally saved in I-deas.

Solution

Ensure the assembly contains components that are the same revision or later revision than what was
originally saved in I-deas.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-25
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Deleting Large Assemblies Causes Integration for I-deas

to Lock Up
This section provides a possible solution to a problem when deleting a large assembly.

Symptom

When you delete a large assembly from the Integration for I-deas window, the assembly is not deleted
and Integration for I-deas locks up.

Cause

A property is not configured properly.

Solution

Modify the file IDNPortal.bat file located in the Portal directory (PORTAL_DIR) as follows:

start Teamcenter.exe %* %IDEAS_APP_INVOKE% -vmargs -Djava.io.tmpdir=

"D:\\Scratch\\NXMI\\Temp\\\\" -DLogLevel=4
-Dorg.omg.PortableInterceptor.ORBInitializerClass.NXMIInterceptor=
COM.metaphasetech.tasks.ids.ops.cad._ideas.proxy.NXMIInterceptor
-Djacorb.poa.queue_max=8000 -Djacorb.poa.queue_wait=on

B-26 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: CGM Creation Error During Save to Teamcenter

Problem: CGM Creation Error During Save to Teamcenter

This section provides a possible solution to a problem when a CGM file is created.

Symptom

When you save an item to Teamcenter, a CGM file is created and the following error may be displayed in
the I-deas List Region.

Error, line 35: illegal mnemonic

Error, line 36: illegal mnemonic

Cause

I-deas processing mistakenly outputs an error.

Solution

This error does not indicate a failure and can be ignored.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-27
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Structure Manager Open in I-deas Command

This section provides a possible solution to a problem where the Structure Manager Open in I-deas
command locks up the application.

Symptom

When you create or modify an I-deas product structure in Structure Manager and execute an Open in I-
deas command, the application locks up.

Cause

A possible cause for this problem is a hidden modal dialog that needs to be cleared.

Solution

Switch through the desktop's open windows and locate the Send To I-deas – Save BOM Window dialog
box. Clear the dialog box by clicking Yes or No. This should cause the Open In I-deas command to
continue execution.

B-28 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Arrangement Creation Failure During Assembly Checkin

Problem: Arrangement Creation Failure During Assembly Checkin

This section provides a possible solution to a problem during checkin of an assembly. This problem
occurs in a Teamcenter four-tier architecture environment.

Symptom

During checkin of an assembly, the assembly and parts are created successfully in Teamcenter, but the
arrangement is not. The following error message is displayed.

No route available for enterprise: '475264640

',transientvolume:'a7a07c9cafccdbc88b6ce7dd7198fde5'

Cause

Possible cause is the transient volume directory does not exist on the four–tier server machine, or the
FMS server the client is connected to is not aware of the transient volume of the server machine.

Solution

See the Teamcenter FMS documentation for a possible solution.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-29
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Cannot Connect to Rich Client from I-deas

This section provides a possible solution to a connection problem when starting Rich Client from I-deas.

Symptom

When you start Rich Client from I-deas, multiple TAO IMR windows are displayed and the Rich Client
application fails to launch.

Cause

Possible cause is incorrect location of IDNPortal.bat file in I-deas command file.

Solution

Verify the location of the IDNPortal.bat file is correct. Check that the following lines in the %SDRC_INSTL
%\ideas\ideas_envv.cmd file contain the correct location for IDNPorta.bat. Make corrections as
necessary.

X%EDS_IMAN% == X set EDS_IMAN=D:\Programs\Tc2007\Portal\IDNPortal.bat

if X%EXTADM_TCII% == X set EXTADM_TCII=D:\Programs\Tc2007\Portal
\IDNPortal.bat

Note:
The location of IDNPortal.bat is specific to your site and may not match the example shown.

B-30 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Error When I-deas Attributes Contain Multi-Byte Characters

Problem: Error When I-deas Attributes Contain Multi-Byte

Characters
This section provides a possible solution to a connection problem when checking in an item to
Teamcenter.

Symptom

Check in of an item fails and produces a General TcException error.

Cause

The problem is caused by a multi-byte string in the change history attribute. Multi-byte strings are not
supported by I-deas, but in previous releases you could get around this limitation due to holes in the
software. These holes are closed starting with NX I-deas 6.

To help detect multi-byte strings in older data, starting with NX I-deas 6 messages are output to the I-
deas List Region when multi-byte strings are detected and the I-deas debug level is medium (3) or
higher. The List Region messages show the data fields that contain multi-byte strings, along with the
name and part number of the item that owns the data, if applicable. In addition, a hexadecimal and
ASCII dump of the multi-byte string shows the characters that need to be modified for the operation to
work successfully.

Solution

Change the multi-byte strings to single-byte strings.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-31
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Ref Mod Warning When Changing the Status of a Dataset

to New
This section provides a possible solution to a problem when changing the status of a dataset to new.

Symptom

When changing the status of a dataset to new in the Integration for I-deas window (Manage
Bins→Change to New) a reference modification warning message is displayed.

Cause

The problem is caused by selecting the dataset using a random hierarchy, not a top-down or bottom-up
hierarchy.

In top-down heirarchy, first select the assembly, then subassembly, then the dataset. Bottom-up
heirarchy is dataset, then subassembly, then assembly. Do not randomly select the dataset, then
assembly, then subassembly or use another random order.

Solution

Use a top-down (recommended) or bottom up hierarchy when selecting the dataset.

B-32 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Unknown Send to I-deas Error

Problem: Unknown Send to I-deas Error

This section describes the problem of an unknown error reported during a Send to I-deas operation.

Symptom

During Send to I-deas, the following error is displayed in the Send to I-deas message box:

Send to I-deas from Teamcenter failed because of an unknown error. This

exception
was reported by the server, it is only re-thrown here.

Cause

The Orbix connection with the I-deas server was lost. This can be due to an Orbix problem or a problem
inside I-deas.

Solution

Verify Orbix is setup and running properly and the I-deas server is running.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-33
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: On a Single Machine Can Only Run One Translator at a

Time
This section provides a possible solution to a problem when trying to run two or more translations
simultaneously on a single machine.

Symptom

Can only run one ideastojt_direct or ideastocgm_direct translator at a time on a single machine.

Cause

The problem could occur due to an incorrect Teamcenter Translation Services module setup.

Another possible cause is the IIOP Server Activation Mode was not set correctly during installation of
Integration for I-deas on the machine that hosts the translation module.

Solution

Refer to the Teamcenter Translation Services documentation for more information on configuring
modules.

Use the Teamcenter Tem installer to perform feature maintenance on your IIOP servers:

1. On the Feature Maintenance dialog box, select the IIOP Servers feature for maintenance.

2. On the IIOP Servers Settings dialog box, set the Server Activation Mode to PER_CLIENT. This
allows more than one tcserver process to run on the host machine.

B-34 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Login Error When Trying to Run an ideastojt_direct or ideastocgm_direct Translator

Problem: Login Error When Trying to Run an ideastojt_direct or

ideastocgm_direct Translator
This section provides a possible solution to a problem when the translator process tries to login to
Teamcenter.

Symptom

Error during login to Teamcenter when running the ideastojt_direct or ideastocgm_direct translator.

Cause

One possible cause is the password for the translation services proxy user has changed since translation
services was installed. The proxy user is defined by the value for the variable Service.Tc.User=tsproxy in
the file %TSTK_ROOT%\TranslationService\conf\Service.properties.

Solution

Refer to the Teamcenter Translation Services documentation for more information on defining the proxy
user.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-35
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: I-deas to JT or I-deas to CGM Translation is Not Provided as

an Option in My Teamcenter
This section provides a possible solution to a problem when trying to translate I-deas datasets using the
selections on the Translation menu in My Teamcenter.

Symptom

In My Teamcenter, from the Translation menu, selections for the ideastojt_direct or ideastocgm_direct
translators are not available.

Cause

The preferences for on-demand translation (translation from My Teamcenter) may not be set correctly.

Solution

Verify the preference ETS_TRANSLATORS.SIEMENS contains the following values:

• ideastojt_direct

• ideastocgm_direct

You may also need to verify other on-demand translator preferences. See the Integration for I-deas
Installation Guide for a list of these preferences.

B-36 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: JT Files are Created and Loaded But When Displayed They are Empty

Problem: JT Files are Created and Loaded But When Displayed They
are Empty
This section provides a possible solution to a problem when translating parts and assemblies.

Symptom

JT files for parts and assemblies are created but when displayed are empty.

Cause

The settings in the tess.config or export_param_idin.idf files are incorrect. Or these files cannot be
found because the path specified in the ideastojt.config file is incorrect or exceeds 80 characters.

Solution

Verify the settings in the tess.config, export_param_idin.idf, and ideastojt.config files.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-37
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: When a Translation is Executed, a Headless Exception

Error is Displayed
This section provides a possible solution to a problem that is displayed in the TranslationServices window
during a translation.

Symptom

During translation, a Headless Exception error is displayed in the TranslationServices window. The error
is similar to the following:

2008–02–13 10:15:56,544 ERROR —

java.awt.HeadlessException

Cause

An access control (ACL) rule may need to be added to your Teamcenter installation.

Solution

Add an access control rule to your Teamcenter installation. For information on creating an ACL rule, see
the Teamcenter 2007 Getting Started with Translation Management Guide.

B-38 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: When a Harness is Translated, Dressings are Shown Instead of Wire Path

Problem: When a Harness is Translated, Dressings are Shown

Instead of Wire Path
This section provides a possible solution to a problem when translating a harness to JT.

Symptom

After translation, in the JT file, harnesses are displayed as dressings instead of wire paths.

Cause

Harnesses used to be displayed as wire paths but are now displayed as dressings because the translators
now have the ability to create a JT representation of the harness bundles. This was not available in
earlier versions of the translators.

Solution

The ability to create a JT representation of the harness bundle is on by default. You can turn it off to
have the harness represented by a wire path by removing the following line or setting the variable to 0,
in the file %TC_PORTAL%\ideas_translator.

JTK_MS8_ENABLE_SOLID_WIREHARNESS=1

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-39
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Cannot Write to the TeamBrowser Log File

This section provides a possible solution to a problem that occurs during translation to JT or CGM.

Symptom

During translation, get an error message that the translator was not able to write to the TeamBrowser
log file.

Cause

You do not have write access to the TeamBrowser (TB) log file. If you have run Integration for I-deas on
the same machine that hosts the translation module, the TB log file may be owned by a different user.
This can cause problems if the file does not allow write access to other users.

Solution

There are several possible solutions:

• Open up permissions to the file to allow other users write permission.

• Delete the TB.log file before running the translator if you do not plan to use Integration for I-deas as a
standalone application.

• Set the environment variable TCII_TMP in the ideas_translator file to point to a different directory so
that Integration for I-deas and the translator do not use the same temp directory.

B-40 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Cannot delete an Item or Item Revision because it is referenced by ETSTranslationRequest

Problem: Cannot delete an Item or Item Revision because it is

referenced by ETSTranslationRequest
This section provides a possible solution to a problem deleting or purging items referenced by
ETSTranslationRequest.

Symptom

During translation, get an error message that the translator was not able to write to the TeamBrowser
log file.

Cause

During the time when an item is queued for translation through Translation Services (TS) and when it
completes, the item is referenced by an ETSTranslationRequest. During this time the item is protected
from accidental deletion and the request is denied.

Solution

Under normal conditions, TS deletes this reference when it deletes the translation request from the TS
queue at completion. Sometimes users try to delete an item before the translation request is complete
or the translation fails and deletion of the reference takes longer than expected or fails to happen.

To resolve this issue, the simplest solution is to wait until the reference is deleted by the normal TS
processing. If this does not work or you cannot wait, then you must query for ETSTranslationRequests in
the Teamcenter Rich Client and manually delete the reference. Ensure you only delete the
ETSTranslationRequest related to the specific item you are trying to delete.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-41
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Arrangements are not created on frozen items using

Translation Services
This section provides a possible solution to a problem where Translation Services (TS) does not update
the arrangements on frozen items.

Symptom

When JT files are created for assemblies through TS, arrangements are added to the assembly Item
Revision. However, if that Item Revision is frozen, arrangements are not added.

Cause

Frozen Item Revisions have frozen arrangements also. This behavior is expected.

Solution

By design, TS does not update the arrangements on frozen Item Revisions. These updates should only be
done on a case-by-case basis at the decision of the site administrator. To update the arrangements on
frozen Item Revisions, you need to use the StoreConfigs tool provided by Integration for I-deas. Refer to
the tool documentation for additional information.

B-42 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Arrangements are not created on imported items that are owned externally

Problem: Arrangements are not created on imported items that are

owned externally
This section provides a possible solution to a problem where Translation Services (TS) does not update
the arrangements on imported items that are owned externally (by the I-deas external owning user).

Symptom

When JT files are created for assemblies through TS, arrangements are added to the assembly Item
Revision. However, if that Item Revision is owned externally, arrangements are not added.

Cause

Externally owned items have limited write permission in Teamcenter. This behavior is expected.

Solution

By design, TS does not update the arrangements on externally owned items. To update the
arrangements on externally owned items, you can use the StoreConfigs tool provided by Integration for
I-deas. Refer to the tool documentation for additional information.

You can also enable the bypass mode for the I-deas to JT translator. This setting is found in the
IdeasToJt.config file located in the %PORTAL_ROOT%\ideasTranslator\transConfig directory. Set the
preference EnableBypassForConfigCreation to true.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-43
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Arrangements are not created using Translation Services

during data sharing import or migration
This section provides a possible solution to a problem where Translation Services (TS) does not create
arrangements during data sharing import or migration.

Symptom

No arrangements are created for items that have been imported (through data sharing) or migrated. The
ideasToJT.log file contains a message that arrangements were not created.

Cause

The most likely cause is that the TS Proxy user does not have permission to update the BVR during the
migration process.

Solution

Add an Access Control Rule to allow the TS Proxy user to update the BVR. Refer to the Integration for I-
deas installation guide section Configuring Translation Services for Integration for I-deas for additional
information.

B-44 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Translations are stopped and have time out message in the module log

Problem: Translations are stopped and have time out message in

the module log
This section provides a possible solution to a problem where Translation Services (TS) is terminating
translations prematurely.

Symptom

Translations are frequently being stopped with the following message in the TS log file.

Stopped because it timed out

Cause

TS is designed to terminate translations that hang and are unable to finish. This is based on a time out
that is set in the TS transmodule.properties file. Starting in Integration for I-deas 6.0, the following
may increase the chance of seeing this problem:

• Integration for I-deas 6.0 does not report progress as frequently as earlier versions, so it may appear
to TS that no progress is being made when it actually is progressing.

• The default translation now uses XTBrep for the JT file. This increases translation times, but is
necessary to support additional functionality.

Solution

Update the following values in the TS transmodule.properties file. Refer to the Translation Services
documentation for additional information:

• MaximumProgress

• MonitorInterval

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-45
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: There is a long delay between completion of a translation

and marked as complete in the TS administration command prompt
window
This section provides a possible solution to a problem where a translation has finished but it is not
marked as complete right away.

Symptom

There is a long delay between the time when the ideastojt.log shows a translation is complete and
Translation Services (TS) recognizes the translation as successful. This may appear to be a translation
that is hung in the translating or loading state.

This is most likely to occur on lightly loaded translation servers or after the Teamcenter fcc process has
been shut down.

Cause

Under normal circumstances the Teamcenter fcc process is started by the TS Module on startup and the
process is shared by all translations. The fcc process has a time out period (specified amount of idle
time) that occurs after all translator processing is complete and it shuts down when the time out period
is finished.

If the fcc process is not already running when a translation starts, it is started by the translator process.
If you have multiple translation processes occurring, the first translation is the one that starts the fcc
process and the fcc will continue to run until all of the translations are complete. TS recognizes a
translation as complete when all processes the translation has started have been shutdown. Therefore,
the translation that started the fcc may appear to hang while it is waiting for fcc to complete the rest of
the translations, go through the time out period, and shut down.

Solution

Keep the fcc process running so that it is not restarted by a translation.

The time out period for the fcc process is controlled by the fcc.xml property file located in the
%FMS_HOME% directory. By default, the property FCC_IdleTimeoutMinutes is set to 30 minutes.

You can adjust this to a larger number to prevent any time outs from occurring. Then the fcc process
started by the TS Module remains running, which prevents the occurrence of this problem.

B-46 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: After Teamcenter fcc process has crashed or terminated, next translation hangs

Problem: After Teamcenter fcc process has crashed or terminated,

next translation hangs
This section provides a possible solution to a problem where a translation hangs.

Symptom

After the Teamcenter fcc process has crashed or terminated, the next translation hangs.

Cause

Under normal circumstances the Teamcenter fcc process is started by the Translation Services (TS)
Module on startup. If the fcc process is terminated but the module is not restarted, when a translation
starts it automatically restarts the fcc process. However, TS does not recognize a translation as complete
until all processes the translation has started have been shutdown. The fcc process is shared by all
translations and will not shutdown at the completion of the translation. Therefore, the translation that
started the fcc may appear to hang.

Solution

Terminate the fcc process and then either restart the TS Module or manually start the fcc process from a
command prompt window using the script %PORTAL_ROOT%\ideas_translator_startsvc.bat.

When you restart the fcc process manually, you must be logged in as the TS user. Terminating the fcc
process causes any currently active translations to fail, which must then be restarted.

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-47
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: Vague message contains error_80XXXX

This section provides a possible solution to a problem where the Teamcenter shared memory cache is
causing problems.

Symptom

Messages contain the error 80XXXX, for example:

error_801203, “1”, “Part 1 B error_801207,.......

Cause

Shared memory techniques are implemented in Teamcenter to improve memory performance. Using
this technique requires that you manage memory mapped files when new text IDs or values are added
to the database.

When new text IDs or values are added to the database during the Integration for I-deas installation, the
memory store backing files must be removed prior to using Integration for I-deas.

Note:
For additional information, see the Teamcenter documentation at Administering
Teamcenter→System Administration→Using File Management System→Using FMS→Shared
memory method for Text Server data.

Solution

Refresh the Teamcenter shared memory cache by removing the memory store backing files as follows:

1. Ensure Teamcenter is idle and no Teamcenter processes are running.

2. Locate the memory store backing files. The environment variable TC_TMP_DIR specifies the
directory where the files are stored. If the environment variable is not set, the TEMP environment
variable (Windows) or /tmp directory (non-Windows) is used.
On Windows, if the environment variable TEMP is not available, the C:\temp\V2007.1.(last build
date\database site ID\language) directory is used.

3. Delete the memory store backing files (*.mem).

B-48 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
Problem: Both CMM and Integration for I-deas are installed, but Integration for I-deas menus are not displayed in

Teamcenter

Problem: Both CMM and Integration for I-deas are installed, but
Integration for I-deas menus are not displayed in Teamcenter
This section provides a possible solution to a problem where the Integration for I-deas menus are not
displayed in Teamcenter.

Symptom

When Content Migration Manager (CMM) and Integration for I-deas are installed, the Integration for I-
deas menus are not displayed in Teamcenter.

Cause

This could be caused by manual editing of installed files, errors that occurred during installation, or
incomplete installation on multiple databases.

Solution

The following are possible solutions to the problem:

• The portal properties file was manually edited. In the file %TC_ROOT%\portal\plugins
\configuration_2007.1\portal.properties, the following variables must contain the applicable values:

Note:
These values are already set in the delivered software.

• com.teamcenter.rac.explorer.ExplorerApplicationMenuBar.ADDON (controls the My

Teamcenter menu) must include:
com.teamcenter.rac.ideasnavigator.IDEASTcMenuBuilder

• com.teamcenter.rac.explorer.ExplorerApplicationToolBar.ADDON (controls the My Teamcenter

toolbar) must include:
com.teamcenter.rac.ideasnavigator.IDEASTcToolBarBuilder

• com.teamcenter.rac.pse.PSEApplicationMenuBar.ADDON (controls the Structure Manager

menu) must include:
com.teamcenter.rac.ideasnavigator.IDEASTcMenuBuilder

• com.teamcenter.rac.pse.PSEApplicationToolBar.ADDON (controls the Structure Manager tool

bar) must include:
com.teamcenter.rac.ideasnavigator.IDEASTcToolBarBuilder

• There was a problem with the plugins during the Integration for I-deas installation. Ensure the
following Integration for I-deas plugins are present in the folder %TC_ROOT%\portal\plugins:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-49
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

com.teamcenter.rac.tcii_6.0.0.jar

com.teamcenter.rac.tcii_ets_6.0.0.jar

com.teamcenter.rac.tcii_overload_6.0.0.jar

com.teamcenter.rac.tcii_ief_6.0.0.jar

com.teamcenter.rac.tcii_storeConfigs_6.0.0.jar

also the directory com.teamcenter.rac.tcii_config_6.0.0

• There was an incomplete Integration for I-deas installation. Ensure the following:

The preference TC_show_open_in_ideas_button is set to TRUE. This should be set

automatically by the Integration for I-deas installation.

Even though Integration for I-deas client/server pieces exist, the menus do not show until the
preference is set to TRUE.
The database you are connecting to must have the Integration for I-deas schema/preferences
installed. This could be a problem if you are connecting to multiple databases and each database
does not have Integration for I-deas installed.

B-50 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Problem: Teamcenter Database Not Configured Properly for Integration for I-deas

Problem: Teamcenter Database Not Configured Properly for

Integration for I-deas
This section provides a possible solution to a problem where the Teamcenter database is not configured
properly for the Integration for I-deas installation.

Symptom

The following error message is displayed:

This is most likely because your Teamcenter database is not configured

properly for Teamcenter Integration for I-deas

Cause

The Integration for I-deas database installation is not installed correctly, or the version of Integration for
I-deas installed is not compatible with the database.

Solution

The following are possible solutions to the problem:

• For Integration for I-deas 5.x releases, rerun the database schema option in the Integration for I-deas
install (there is no TEM install for this release). See the Integration for I-deas installation
documentation for information on updating the database schema.

• For Integration for I-deas 6.x releases:

1. Ensure the Teamcenter Integration for I-deas Database Extensions option is installed in the
database.
Verify this by launching the Teamcenter Environment Manager (TEM). This is available at the
%TC_ROOT%\install directory.
When running TEM, select Maintenance, Configuration Manager→Perform maintenance on
an existing configuration and the Configuration Selection dialog box should list Teamcenter
Integration for I-deas – Database Extensions as one of the options that is installed. If this is
not listed, then install this feature. This feature is shipped as part of the Integration for I-deas
install kit.

2. Ensure the correct version of the libius library (Integration for I-deas library) is installed on the
server. If it is incorrect or not present, install/reinstall the correct version Teamcenter
Integration for I-deas – TcII for Corporate Server feature. The libius library is installed as part
of that feature installation.
Verify this by examining the Teamcenter syslog file:

• If a correct version of the libius library is present, the syslog includes a message similar to:

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-51
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Successfully loaded dynamic module D:\Programs\TC2007~2\bin\libius.dll. Teamcenter

Integration for I-deas 6.0.4 (6.0.4.6) library loaded.

• If an incorrect version of the library is present or missing, the syslog includes an error similar
to:

The reason D:\Programs\TC2007~1\bin\libius.dll failed to load was: Invalid library type

3. Check the gs_info directory in the Teamcenter TC_DATA directory to see if it is missing the
following .des files. The .des files are generated files and if the database was installed correctly,
they should be present. The files should also contain a references section as listed in the
References Section (below).
The .des files are:

ideasassembly.des

ideasassemblyviewinfo.des

ideasdrawing.des

ideasdrawingset.des

ideasfem.des

ideaspart.des

If the .des files are missing or its contents do not match the contents in the References Section,
this could cause the error. To fix the problem, run the following command from the Teamcenter
command prompt to generate these files:

make_datasettype –u=infodba –p=$(TC_USER_PASSWD) –g=dba –definition=$(Location)/

IdeasTcDatasetTypes.dat

Note:
The IdeasTcDatasetTypes.dat definition file is shipped in the Integration for I-deas
6.0.4 or later kit. If you have a kit from Integration for I-deas 6.0 to 6.0.3, the file is
not there. Get the file from any Integration for I-deas 5.x kit, but notice the name of
the file is slightly different: IdeasImanDatasetTypes.dat (where Tc is replaced by
Iman). Use this file name in the command.

Reference Section. Ensure the .des files contain their reference sections as follows:

• ideasassembly.des:

References {
BINARY "IdeasAssembly" *.asm -1

B-52 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Solution

BINARY "IdeasAssembly" *.Z -1

BINARY "IdeasPrivateData" *.cpd -1
Object "IdeasGuids" OBJECT -1
Object "IdeasAssemblyRelations" OBJECT -1
Object "IdeasUserAttributes" OBJECT -1
Object "IdeasAuxFileRefs" OBJECT -1
BINARY "IdeasAuxFiles" *.auf -1
}

• ideasassemblyviewinfo.des:

References
{
BINARY "IdeasAssemblyViewInfo" *.vfz -1
}

• ideasdrawing.des:

References {
BINARY "IdeasDrawing" * -1
BINARY "IdeasDraftSetupBin" *.dwg -1
BINARY "IdeasPrivateData" *.cpd -1
Object "IdeasGuids" OBJECT -1
Object "IdeasDrawingReferences" OBJECT -1
Object "IdeasMigratedItemGuid" OBJECT -1
Object "IdeasUserAttributes" OBJECT -1
Object "IdeasAuxFileRefs" OBJECT -1
BINARY "IdeasAuxFiles" *.auf -1
}

• ideasdrawingset.des

References {
BINARY "IdeasPrivateData" *.cpd -1
Object "IdeasGuids" OBJECT -1
Object "IdeasDrawingSetRefs" OBJECT -1
Object "IdeasUserAttributes" OBJECT -1
Object "IdeasAuxFileRefs" OBJECT -1
BINARY "IdeasAuxFiles" *.auf -1
}

• ideasfem.des

References {
BINARY "IdeasFem" *.fem -1
BINARY "IdeasFem" *.Z -1
BINARY "IdeasPrivateData" *.cpd -1
Object "IdeasGuids" OBJECT -1

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-53
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Object "IdeasFemReference" OBJECT -1

Object "IdeasUserAttributes" OBJECT -1
Object "IdeasAuxFileRefs" OBJECT -1
BINARY "IdeasAuxFiles" *.auf -1
}

• ideaspart.des

References {
BINARY "IdeasPart" *.prt -1
BINARY "IdeasPart" *.Z -1
BINARY "IdeasPrivateData" *.cpd -1
Object "IdeasGuids" OBJECT -1
Object "IdeasBoundingBox" OBJECT -1
Object "IdeasPartAcr" OBJECT -1
Object "IdeasSourceReference" OBJECT -1
Object "IdeasUserAttributes" OBJECT -1
Object "IdeasAuxFileRefs" OBJECT -1
BINARY "IdeasAuxFiles" *.auf -1
}

4. If the above three steps are correct, then this must be a database schema update problem and
you need to file an IR with GTAC.
To further troubleshoot the problem and provide GTAC with additional information, execute the
following commands (in the example below all logs are located in C:\dataaccuracy):

• business_model_extractor –u=infodba –p=<infodba password> –g=dba –

outfile=C:\dataaccuracy\testdb_model.xml –log=C:\dataaccuracy\extractor_testdb.log

• bmide_consolidator –dir=%TC_DATA%\model –file= C:\dataaccuracy

\consolidated_model_testdb.xml

• bmide_comparator –all –old= C:\dataaccuracy\consolidated_model_testdb.xml –

new=C:\dataaccuracy\testdb_model.xml –delta= C:\dataaccuracy\delta_testdb_install.xml –
log= C:\dataaccuracy\ bmide_comparator_testdb.log

After you run these commands, provide the following files to GTAC:

• testdb_model.xml

• consolidated_model_testdb.xml

• delta_testdb_install.xml

• ideasassembly.des

• ideasassemblyviewinfo.des

B-54 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Solution

• ideasdrawing.des

• ideasdrawingset.des

• ideasfem.des

• ideaspart.des

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q B-55
© 2020 Siemens
 B. Integration for I-deas Troubleshooting

Problem: When opening a large model both Teamcenter and I-deas

hang
This section provides a possible solution to a problem where Teamcenter and I-deas hang when you try
to open a large model.

Symptom

When you try to open a large model both Teamcenter and I-deas hang.

Cause

The probable cause is a setting in Teamcenter.

Solution

The following is a possible solution to the problem:

In the IDNPortal.bat file, set the following preferences:

-Djacorb.poa.queue_max=800
-Djacorb.poa.queue_wait=on

Release Notes
For the latest information on installation and use of the product, see the Integration for I-deas Release
Notes. Integration for I-deas Release Notes is delivered in printed form with the Integration for I-deas
product.

Customer Support
To help customers with problems or questions, Siemens Digital Industries Software maintains worldwide
response centers staffed by our technical support representatives. Contact your local response center if
you have questions you cannot resolve by using the Integration for I-deas documentation or other
resources at hand.

B-56 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Index
Customer support B-56
A
Adobe Acrobat Reader -19
AE_dataset_default_keep_limit preference 3-8
D
Data management 1-3
Assembly structures
Data sharing 1-3
Component versions 7-3
Data sharing with I-deas 8-1
Creating in Teamcenter 7-12
Exporting 8-7
Legacy assemblies 7-3
Importing 8-11
Saving in Teamcenter 7-3
Data storage 1-2
Transformation matrices 7-4
Datasets 3-8
View data 7-1
AE_dataset_default_keep_limit preference 3-8
Wire harnesses 7-2
DirectModel 3-0
Assembly, viewing 4-10
I-deas FE model 3-0
Attribute mapping 4-41
I-deas assembly 3-0
I-deas drawing 3-0
B I-deas parts 3-8
Bins Versions 3-8
Create 4-36 Deleting
BOMView Revisions (BVR) 3-9 Using Integration for I-deas 4-33
BVR 3-9 Using Teamcenter 4-32
Derived I-deas part
C Revision out-of-date 5-21
Version out-of-date 5-21
Canceling checkout status 5-17
Desktop menu 3-5
Checkout status
Details pane 3-4
Canceling 5-17
Display
Icon 5-13
Viewing types of items 4-18
Closing My Teamcenter 3-9
Display data pane 3-5
Code conventions -18
Documentation
Command line entry conventions -18
Online help -19
Connection issues 3-3
Printable files -19
Connection timeout for stale server B-6
Connection timeouts B-5
Conventions E
Caution icons -16 Edit menu 3-5
Code -18 Error logging at JT file creation 4-11
Command line entries -18 Errors
File contents -18 Connection Issues B-9
Names -16 Connection timeout for stale server B-6
Note icons -16 Connection timeouts B-5
Revisions -16 External file display (UNIX) B-11
Syntax definitions -18 I-deas doesn't launch B-14
Values -16 NamedReference error message at checkin B-12
Warning icons -16 Teamcenter Visualization problems on Sun
Copying Items 4-35 Workstations B-13
Creating Exiting Teamcenter Rich Client 3-9
Assembly structures in Teamcenter 7-12 export_attr_maping.exe file 4-41
Data sharing packages 8-7 Exporting data to I-deas 8-7
Item revisions 4-20 External file display (UNIX) B-11
Creating bins 4-36 External items
Creating JT files 4-7 Sending to I-deas 5-17

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q Index-1
© 2020 Siemens
 F IDEAS_connect_time preference 2-10
File contents conventions -18 IDEAS_create_auxfile_refs 2-34
File menu 3-5 IDEAS_default_item_type preference 2-10
File status 5-13 IDEAS_default_scale_factor preference 2-9
Files, JT type 4-7 IDEAS_default_view_type 2-14
Filtering the display 4-18 IDEAS_default_view_type preference 2-9
Advanced filtering 4-18 IDEAS_delete_items_on_checkin_failure 2-20
IDEAS_detail_level 2-34
IDEAS_DRAWING_relation_primary 2-16
G IDEAS_DWGSET_relation_primary 2-17
Groups 1-3 IDEAS_external_owning_user_name 2-36
Assigning roles 1-4 IDEAS_FEM_relation_primary 2-17
Creating 1-4 IDEAS_fem_send_latest_ref preference 2-9
Data sharing 1-4 IDEAS_giman_util_batch_size 2-30
Managing 1-5 IDEAS_hub_site_name 2-30
Planning 1-4 IDEAS_ideas_datasets 2-42
Roles 1-5 IDEAS_import_auxfiles 2-33
IDEAS_import_mapfile 2-44
H IDEAS_inconsistent_create_date_action 2-31
Help menu 3-5 IDEAS_JT_Resolution_Preference 2-32
IDEAS_keep_drawing_with_related_model 2-23
IDEAS_keep_dwg_of_mult_parts_with_related_mod
I el 2-24
I-deas IDEAS_keep_dwgset_with_related_drawing 2-25
Datasets 4-31 IDEAS_keep_fem_with_related_model 2-24
Exporting data from 8-7 IDEAS_map_partnumber 4-41
Importing data from 8-11 IDEAS_mig_import_add_to_folders 2-28
Part number attribute mapping 4-41 IDEAS_mig_import_default_tcgroup 2-35
I-deas doesn't launch B-14 IDEAS_mig_import_default_tcproject 2-35
I-deas menu 3-5 IDEAS_mig_import_default_tcuser 2-35
Icon conventions -16 IDEAS_mig_import_parent_folder_name 2-28
Icons IDEAS_mig_import_parent_folder_user 2-28
DirectModel dataset 3-0 IDEAS_mig_import_proj_hier_sep 2-29
I-deas External Data Manager 3-1 IDEAS_migration_create_jt 2-14
I-deas FE model dataset 3-0 IDEAS_migration_stats_level 2-37
I-deas assembly dataset 3-0 IDEAS_one_version_per_revision 2-21
I-deas drawing dataset 3-0 IDEAS_override_itemid 2-28
I-deas part dataset 3-8 IDEAS_part_create_jt preference 2-7
Status IDEAS_push_ng_to_hub 2-43
Check Out 5-13 IDEAS_query_before_remote_import 2-31
Prune 5-14 IDEAS_related_objects_to_publish 2-32
Reference 5-14 IDEAS_rename_conflicting_dataset 2-28
IDEAS_2D_drawing_autoassign_conflicting_ids 2-27 IDEAS_revision_id_format_allow_truncate_ideas_rev
IDEAS_ACCONTEXT_relation_primary 2-18 2-12
IDEAS_ACSOURCE_relation_primary 2-18 IDEAS_revision_id_format_blank_ideas_rev 2-13
IDEAS_Allow_Non_Latest_Revise 2-25 IDEAS_revision_id_format_specifier 2-11
IDEAS_append_autoassignid_to_originalid 2-39 IDEAS_send_default_NX_as 2-20
IDEAS_assembly_create_jt preference 2-8 IDEAS_send_derived_ideas_dataset 2-19
IDEAS_automatically_synchronize 2-21 IDEAS_send_nx_dataset 2-19
IDEAS_auxfile_dataset_map 2-33 IDEAS_send_option_check_refmod 2-36
IDEAS_bvr_create_precise preference 2-10 IDEAS_send_option_display_replace_ui 2-27
IDEAS_bvr_create_precise.Disallow preference 2-10 IDEAS_send_option_enable_file_cache 2-37
IDEAS_catiav4_Datasets 2-43 IDEAS_send_option_replace_revisions 2-26
IDEAS_catiav5_Datasets 2-43 IDEAS_set_latest_dataset_right_to_modify_only 2-44
IDEAS_CM_Release_statuses 2-32

Index-2 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 IDEAS_show_open_in_ideas_button 2-13 Desktop 3-5
IDEAS_skip_ADBFiles_Transfer 2-34 Edit 3-5
IDEAS_sync_partnumber 2-13 File 3-5
IDEAS_types_to_exclude 2-42 Help 3-5
IDEAS_update_matched_versions 2-31 I-deas 3-5
IDEAS_use_item_level_right_to_modify 2-43 Revise option 4-29
IdeasAssembly_DefaultChildProperties 2-15 Save & Checkin option 4-19
IdeasDrawing_DefaultChildProperties 2-16 Save As option 4-20
IdeasDrawingSet_DefaultChildProperties 2-16 Save to Teamcenter option 4-19
IdeasFem_DefaultChildProperties 2-15 Save, Checkin, & Remove option 4-19
IdeasPart_DefaultChildProperties 2-14 Send to I-deas option 5-5
import_attr_mapping.exe file 4-41 Tools 3-5
Importing data View 3-5
Considerations 8-14 Model file
From I-deas 8-11 Synchronizing 6-2
Integration for I-deas window Updating 6-5
Edit menu 3-0 Modeling data
File menu 3-0 Out-of-date 6-1
Help menu 3-0 Out-of-date in interoperability 6-2
Manage Bins menu 3-0 Moving Items 4-35
Menu Bar 3-6 My Teamcenter 1-5
View menu 3-0 Client 1-5
Integration for I-deas, troubleshooting B-1 Users 1-6
Interoperability 5-17 My Teamcenter interface 3-4
Interoperability for non-Integration for I-deas Users Details pane 3-4
3-4 Display data pane 3-5
Item objects 3-8 Integration for I-deas window 3-6
Item revision objects 3-8 Menu bar 3-5
Overview 3-4
J Referencers pane 3-5
JT file creation 4-7 Summary pane 3-4
JT file preferences 4-8 Viewer pane 3-4
JT files 3-0 My Teamcenter tree pane 3-4

L N
Launching My Teamcenter 3-1 Name conventions -16
From within I-deas 3-1 NamedReference error message at checkin B-12
Logging JT file creation errors 4-11 NX
Updating source part 5-22
NX
M Source part attributes 5-22
Manage bins
Copying 4-35
Creating bins 4-36 O
Deleting 4-33 Online help -19
Moving 4-35 Out of Sync
renaming 4-34 Derived I-deas part and NX 5-21
renumbering 4-34 Out-of-date modeling data 6-1
Manual set -19
Mapping I-deas part number attributes 4-41 P
Menus Packages for data sharing

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q Index-3
© 2020 Siemens
 Exporting 8-7 IDEAS_migration_create_jt 2-14
Importing 8-11 IDEAS_migration_stats_level 2-37
Part name IDEAS_one_version_per_revision 2-21
Changing 4-34 IDEAS_override_itemid 2-28
Part number IDEAS_part_create_jt 2-7
Changing 4-34 IDEAS_push_ng_to_hub 2-43
Part number attribute mapping 4-41 IDEAS_query_before_remote_import 2-31
PMI (Product Manufacturing Information) 4-10 IDEAS_related_objects_to_publish 2-32
Precise BOMView Revisions 7-4 IDEAS_rename_conflicting_dataset 2-28
Preferences 2-7 IDEAS_revision_id_format_allow_truncate_ideas_re
IDEAS_2D_drawing_autoassign_conflicting_ids 2-27 v 2-12
IDEAS_ACCONTEXT_relation_primary 2-18 IDEAS_revision_id_format_blank_ideas_rev 2-13
IDEAS_ACSOURCE_relation_primary 2-18 IDEAS_revision_id_format_specifier 2-11
IDEAS_Allow_Non_Latest_Revise 2-25 IDEAS_send_default_NX_as 2-20
IDEAS_CM_Release_statuses 2-32 IDEAS_send_derived_ideas_dataset 2-19
IDEAS_DRAWING_relation_primary 2-16 IDEAS_send_nx_dataset 2-19
IDEAS_DWGSET_relation_primary 2-17 IDEAS_send_option_check_refmod 2-36
IDEAS_FEM_relation_primary 2-17 IDEAS_send_option_display_replace_ui 2-27
IDEAS_JT_Resolution_Preference 2-32 IDEAS_send_option_enable_file_cache 2-37
IDEAS_append_autoassignid_to_originalid 2-39 IDEAS_send_option_replace_revisions 2-26
IDEAS_assembly_create_jt 2-8 IDEAS_set_latest_dataset_right_to_modify_only 2-
IDEAS_automatically_synchronize 2-21 44
IDEAS_auxfile_dataset_map 2-33 IDEAS_show_open_in_ideas_button 2-13
IDEAS_bvr_create_precise 2-10 IDEAS_skip_ADBFiles_Transfer 2-34
IDEAS_bvr_create_precise.Disallow 2-10 IDEAS_sync_partnumber 2-13
IDEAS_catiav4_Datasets 2-43 IDEAS_types_to_exclude 2-42
IDEAS_catiav5_Datasets 2-43 IDEAS_update_matched_versions 2-31
IDEAS_connect_time 2-10 IDEAS_use_item_level_right_to_modify 2-43
IDEAS_create_auxfile_refs 2-34 IdeasAssembly_DefaultChildProperties 2-15
IDEAS_default_item_type 2-10 IdeasDrawingSet_DefaultChildProperties 2-16
IDEAS_default_scale_factor 2-9 IdeasDrawing_DefaultChildProperties 2-16
IDEAS_default_view_type 2-9 IdeasFem_DefaultChildProperties 2-15
IDEAS_delete_items_on_checkin_failure 2-20 IdeasPart_DefaultChildProperties 2-14
IDEAS_detail_level 2-34 Pruned status
IDEAS_external_owning_user_name 2-36 Changing 5-15
IDEAS_fem_send_latest_ref 2-9 Icon 5-14
IDEAS_giman_util_batch_size 2-30 Pruning parts 7-14
IDEAS_hub_site_name 2-30
IDEAS_ideas_datasets 2-42 R
IDEAS_import_auxfiles 2-33 Referencers pane 3-5
IDEAS_import_default_tcgroup 2-35 Release notes B-56
IDEAS_import_default_tcproject 2-35 Remote checkout 4-37
IDEAS_import_default_tcuser 2-35 Renaming Items 4-34
IDEAS_import_mapfile 2-44 Renumbering Items 4-34
IDEAS_inconsistent_create_date_action 2-31 Restoring connections 3-3
IDEAS_keep_drawing_with_related_model 2-23 Revision conventions -16
IDEAS_keep_dwg_of_mult_parts_with_related_mo Revision out-of-date
del 2-24 Derived I-deas part 5-21
IDEAS_keep_dwgset_with_related_drawing 2-25 Roles 1-5
IDEAS_keep_fem_with_related_model 2-24
IDEAS_mig_import_add_to_folders 2-28
IDEAS_mig_import_parent_folder_name 2-28
S
IDEAS_mig_import_parent_folder_user 2-28 Saving data in Teamcenter 4-19
IDEAS_mig_import_proj_hier_sep 2-29 Checked–out modeling items 4-27
Considerations and restrictions 4-19

Index-4 eng00013 Q Integration for I-deas User's Guide, I-DEAS Integration 12.2
© 2020 Siemens
 Menu options 4-19 Derived I-deas part 5-21
New modeling items 4-22 View menu 3-5
Sending data to I-deas 5-1 Viewer pane 3-4
Considerations and restrictions 5-1 Viewing
Dependencies 5-1 Advanced filtering 4-18
I-deas Parts and External Parts 5-0 Filtering the view 4-18
Assemblies 5-0 Viewing assemblies 4-10
Drawing sets 5-2
Drawings 5-2
FE models 5-2
File status 5-13
Check Out 5-13
Faceted 5-14
Precise 5-14
Prune 5-14
Reference 5-14
File status exceptions 5-15
Revision rules 5-6
Sending data to I-deas
From Structure Manager 7-13
Sending external items to I-deas 5-17
Sharing data 1-3
Exporting to I-deas 8-7
Import considerations 8-14
Importing 8-11
Summary pane 3-4
Support information B-56
Synchronizing model file 6-2
Syntax definition conventions -18

T
Teamcenter
Release notes B-56
Teamcenter objects 3-7
BOMView Revisions (BVR) 3-9
Datasets 3-7
Item revisions 3-8
Items 3-8
Teamcenter Visualization problems B-13
Tools menu 3-5
Transformation matrices 7-4
Troubleshooting Integration for I-deas B-1

U
Updating derived I-deas part 5-22
Updating model file 6-5

V
Value conventions -16
Version out-of-date

Integration for I-deas User's Guide, I-DEAS Integration 12.2 eng00013 Q Index-5
© 2020 Siemens
Siemens Digital Industries Software
Headquarters Europe
Granite Park One Stephenson House
5800 Granite Parkway Sir William Siemens Square
Suite 600 Frimley, Camberley
Plano, TX 75024 Surrey, GU16 8QD
USA +44 (0) 1276 413200
+1 972 987 3000

Asia-Pacific
Americas Suites 4301-4302, 43/F
Granite Park One AIA Kowloon Tower, Landmark East
5800 Granite Parkway 100 How Ming Street
Suite 600 Kwun Tong, Kowloon
Plano, TX 75024 Hong Kong
USA +852 2230 3308
+1 314 264 8499

About Siemens Digital Industries Software

Siemens Digital Industries Software is a leading global provider of product life cycle management
(PLM) software and services with 7 million licensed seats and 71,000 customers worldwide.
Headquartered in Plano, Texas, Siemens Digital Industries Software works collaboratively with
companies to deliver open solutions that help them turn more ideas into successful products. For
more information on Siemens Digital Industries Software products and services, visit
www.siemens.com/plm.
This software and related documentation are proprietary and confidential to Siemens.
© 2020 Siemens. A list of relevant Siemens trademarks is available. Other trademarks belong to
their respective owners.