Lesson

16 NX Integration Import and

Data Release

Purpose

The purpose of this lesson is to import native NX files and other related data
into Teamcenter Engineering.

Objectives

Upon completion of this lesson, you will be able to:

• Import NX Data into the Database

• Release Imported NX Data

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-1
NX Integration Import and Data Release

Introduction to NX Data Import

In standard NX, your parts are stored in operating system directories. NX
Integration, however, does not search for your parts in operating system
directories. Instead, it retrieves part files from the Teamcenter Engineering
database. Therefore, in order for NX Integration to locate your parts, they
need to exist in the Teamcenter Engineering database. The ug_import
utility is used to make copies of your standard NX assemblies in Teamcenter
Engineering.
The ug_import utility is commonly used to import NX part files and
assemblies. The result is the creation of Items and the included UGMASTER
and/or UGPART datasets which have the file Named References for the part
file data.
You should use the ug_import utility whenever you are importing NX data.
The ug_import utility does the following:
• Imports an entire part tree when the top level assembly Item is specified.

• Creates an Item structure for data plus a dataset.

• Imports NX assembly and master model data.

• A mapping file is typically used to provide settings for the many options.

• Can use a mapping file suited for NX parts.

• Can use a search path file to locate NX parts.

16-2 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Parts and Assemblies to be Imported

For your reference these parts and assemblies will be discussed and imported
in this lesson.
Other files (e.g. seed files) will also be imported and will be explained
appropriately during the lesson discussion.

Wheel Assembly

The wheel assembly below contains the components as listed in the Assembly
Navigator.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-3
NX Integration Import and Data Release

Frame Assembly

The frame assembly below contains the components as listed in the Assembly
Navigator.

16-4 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Prepare to Import NX Data

Preparations are usually required before using the ug_import utility to have
a successful import. The next few pages will use various native NX files to
show the necessary preparation.
The first and most important step is to understand what files there are to be
imported. Various types are listed:
• Components

• Assemblies

• Master associated files (e.g. TIF, HTML files)

• Non-master part files (Drawing and NC ".prt" files)

• Non-master associated files (e.g. NC, CLSF, PTP files)

• Non-NX files (e.g. DOD requirements, part testing results)

• Product (part) attributes

Because ug_import works slightly different for these file types, you must
ask these questions:
• What setup requirements are there?

• What mapping files must be written?

• How to use ug_import?

Consider the example directory below of native NX files that must be

imported.
1250_axle_000.tif 1600_wheel_assy_000.prt
1250_axle_000.prt 1700_spacer_000.prt
1250_axle_000_dwg.prt border_b_seed.prt
1250_000_dwg.cgm border_c_seed.prt
1300_bearing_000.prt m243_heat_treat.txt

1400_wheel_000.prt

The 1400_wheel_000.prt is in a directory at a different location.

How is the import set up, and then how is the import accomplished?

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-5
NX Integration Import and Data Release

Recognize the NX Files and Attribute Data

The directory below must be divided into the categories shown in order to
properly use ug_import and its arguments.

Components and Assemblies

1600_wheel_assy_000.prt
1700_spacer_000.prt
border_b_seed.prt
1250_axle_000.prt border_c_seed.prt

1300_bearing_000.prt

1400_wheel_000.prt

The ug_import utility essentially works the same for component and assembly
parts, but the utility performs a database login each time it is executed. The
login can take a fair amount of time. Therefore, preferably you would like to
know the assembly parts and execute ug_import on the top level assemblies.
The NX utility ugpc can be run on the part (.prt) files in
the directory to get a output listing of the assemblies
and their components, as shown in the following example.

1600_wheel_assy_000.prt
./1250_axle_000.prt
./1700_spacer_000.prt
./1300_bearing_000.prt
./1400_wheel_000.prt

For example, you could simply use:

ug_import -part=border_b_seed.prt
ug_import -part=border_c_seed.prt
ug_import -part=1600_wheel_assy_000.prt

As you will see the components and assembly master files can be imported
with one command line ug_import execution and a mapping file to convert all
files to the proper database Part ID and Revision.

16-6 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Master Associated Files (e.g. files like TIF, HTML)

1250_axle_000.tif

Next begin to recognize the files associated to the components and assemblies.
These files would be like TIF or HTML files.
These files can be placed in an individual directory and imported with one
extra argument on the command line or one extra keyword in a mapping file.
For example, you could simply use:

ug_import -part=1250_axle_000.prt -id=1250 -rev=000

-assoc_files=yes

where the 1250_axle_000.tif file would be in a sub-directory named 1250 to

correspond to the part id (-id=1250).

Non-Master Part Files (drawing and nc ".prt" files)

1250_axle_000_dwg.prt

Next recognize the non-master part files that work with the component and
assemblies. These files would be drawings and manufacturing part (.prt) files.
Non-master part files can reside in the same directory as their master part
files, but must be imported with their own ug_import execution.
For these part files you must specify the relation to the master part (e.g.
specification, manifestation, etc.) and the name of the UGPART dataset
created with the import.
For example, you could simply use:

ug_import -part=1250_axle_000_dwg.prt -id=1250 -rev=000

-name=1250_DWG –type=manifestation

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-7
NX Integration Import and Data Release

Non-Master Associated Files

1250_axle_000_dwg.cgm

Next begin to recognize the files associated to the non-master part files (e.g.,
CLSF, PTP files). These files would be like CGM files that are associated to a
drawing or the common CAM related files for manufacturing operations.
Like before, these files can be placed in an individual directory and imported
with one extra argument on the command line or one extra keyword in a
mapping file.
For example, you could simply use:

ug_import -part=1250_axle_000_dwg.cgm -id=1250 -rev=000

-name=1250_DWG –type=manifestation –assoc_files=yes

where the 1250_000_dwg.cgm file would be in a sub-directory named

1250_m_1250_dwg to correspond to the part id (-id=1250) + m
(-type=manifestation) + 1250_dwg (-name=1250_DWG). Each of these
portions are separated with an underscore ( _ ), giving the full sub-directory
1250_m_1250_dwg.

Non-NX Files

Examples of Non-Unigraphics Files are DOD requirements and part testing

results.
m243_heat_treat.txt

Finally importing the non-NX files can easily be done by importing the files
into the Item or Item Revision with the import_file utility. This utility was
used earlier in the course.

Product and Part Attributes

Product or part attributes may exist in the part file or inside another
application (e.g. MRP). Importing NX part attributes is done automatically
with the ug_import utility, after a preference is setup with the list of attribute
names. Importing attributes from other applications usually requires
exporting the attributes to a neutral file and then using a custom Teamcenter
Engineering program to import the attributes into the database.

16-8 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Example Import Directories and Files

Original directory and files.

1250_axle_000.tif 1600_wheel_assy_000.prt
1250_axle_000.prt 1700_spacer_000.prt
1250_axle_000_dwg.prt border_b_seed.prt
1250_000_dwg.cgm border_c_seed.prt
1300_bearing_000.prt m243_heat_treat.txt

1400_wheel_000.prt

Rearranged directories and files.

1250/ 1600_wheel_assy_000.prt
1250_axle_000.prt 1700_spacer_000.prt
1250_axle_000_dwg.prt border_b_seed.prt
1250_m_1250_dwg/ border_c_seed.prt
1300_bearing_000.prt m243_heat_treat.txt
1600_search.txt 1600_wheel_assy.map

1400_wheel_000.prt

As you can see the master part files for the 1600_wheel_assy_000.prt and the
seed parts still remain in their original directories. The non-master part file
(1250_axle_000_dwg.prt) and the non-NX file (m243_heat_treat.txt) also
remain in the original directory.
To convert the files names to database Part IDs and Revisions, the
1600_wheel_assy.map file has been added and will be used during the import.
Also the 1600_search.txt file has been added to locate the 1400_wheel_000.prt.
Two sub-directories have been created for the associated files. The
sub-directory contents are shown below.
1250/
1250_axle_000.tif

1250_axle_000_dwg/
1250_000_dwg.cgm

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-9
NX Integration Import and Data Release

Overview of the ug_import Capabilities

Basic Usage of ug_import

The ug_import utility takes your standard NX assembly and recreates both
the parts and the structure in Teamcenter Engineering. For each NX part,
ug_import creates items, item revisions and datasets as necessary.
The simplest import is carried out by specifying the command:

ug_import -part=1600_wheel_assy_000.prt

This imports an assembly named 1600_wheel_assy_000.prt and all of

its component parts from the current directory into the Teamcenter
Engineering database. If the assembly is located outside the current
directory, you need to specify the full pathname of the assembly, for example:

ug_import -part=/users/daytr/1600_wheel_assy_000.prt

The default behavior of ug_import is to create all the parts in the NX

assembly as master parts of type "Item" in the Teamcenter Engineering
database. The parts are named as follows:
• ug_import removes the directory prefix and the .prt extension from the
standard NX filename to form the Item ID.

• the item revision is set to "A".

The native filename /users/daytr/parts/1600_wheel_assy_000.prt becomes

1600_wheel_assy_000/A in Teamcenter Engineering.
The ug_import utility allows you to fine-tune the creation of the assembly
and each of its components by specifying extra command line keywords and
through the use of mapping files.

16-10 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Introduction to Using Mapping Files

A mapping file can set the individual components without affecting other
components in the assembly.

Mapping file syntax

[Defaults]
import_folder = "Import Project"
db_part_no=$STRIPPED_LEAFNAME
existing_data=$USE_EXISTING

[CA_36245.prt]
db_part_no="CA_36245_000"
db_part_rev="000"
assoc_files=yes
assoc_files_dir="CA_36245_files"

[ENG_83475.prt]
existing_data=$OVERWRITE_EXISTING
db_part_no="ENG_83475_000"
db_part_rev="000"
assoc_files=no

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-11
NX Integration Import and Data Release

Introduction to Using Command Line Keywords

Depending on the command line keyword the entire assembly or just the
top part of the assembly are affected.

Command line keyword syntax

ug_import -part=<part name>
[-u=<username>]
[-p=<password>]
[-g=<group>]
[-search=<search file name>]
[-mapping=<mapping file name>]
[-import_folder=<folder name>]
[-id=<Item ID>]
[-rev=<Item Revision>]
[-part_type=<Item Type>]
[-type=<relationship type>]
[-name=<dataset name>]
[-assoc_files=<yes/no>]
[-assoc_root_dir=<associated files root dir>]
[-dryrun]

The details of these will be explained on later pages by using real world
examples.

Using (Directory) Search Files

Your site may not keep all the components of all assemblies in the same
directory. If you specify the name of a search list file on the command line,
NX Integration searches the directories listed in the search list file for the
component parts of the assembly.

Importing Non-Master and Associated NX Files

You may have other files that are used with your part files (e.g. machining
operation files).
In addition to importing part files, you can import other types of NX files
associated with a part file from operating system directories.

16-12 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Understanding Various NX Integration Import Scenarios

The following import scenarios will be discussed to import native part file
data.
• Import Component Parts or Assembly Parts without a Map File

• Import an Assembly using a Map File and Search File

• Import a Non-Master Drawing and NC Part File

• Import Files Associated to a Component (Master) Part File

• Import Files Associated to the DWG (Non-Master) Part File

• Import Files Using a Full Map File

To run ug_import, use the following command syntax:

ug_import -part=<part name>

[-dryrun]

[-id=<Item ID>]
[-rev=<Item Revision>]

[-search=<search file name>]

[-mapping=<mapping file name>]

[-import_folder=<folder name>]

[-type=<relationship type>]
[-name=<dataset name>]

[-assoc_files=<yes/no>]
[-assoc_root_dir=<associated files root dir>]

The following tables give a brief description of the value corresponding to

each command line keyword, and the title of the subheading under which
further information can be found.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-13
NX Integration Import and Data Release

Import Component or Assembly Parts without a Map File

KEYWORD VALUE
-part= The operating system pathname of
the top level part in the NX assembly
which is to be imported.
-dryrun Indicates whether the import will
proceed as expected, without actually
doing the import.
-id= The Item ID which is given to the
standard NX part specified on the
command line.
-rev= The Teamcenter Engineering revision
which is given to the standard NX part
specified on the command line.
-import_folder= The name of the Teamcenter
Engineering folder which stores the
imported assembly and all of its
components.

Import an Assembly using a Map File and Search File

KEYWORD VALUE
-mapping= The operating system pathname of the
file containing details of the way in
which individual components in your
assembly should be imported.
-search= The operating system pathname
of the file which lists operating
system directories to search for the
components of your assembly.

16-14 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Import a Non-Master Drawing and NC Part

KEYWORD VALUE
-type= The type of non-master part file created
in Teamcenter Engineering.
-name= The name of the non-master part file
created in Teamcenter Engineering.

Import Files Associated to a Part and to the NC (Non-Master) Part

KEYWORD VALUE
-assoc_files= Used to instruct ug_import whether
to import files associated with the
specified assembly and all of its
components.
-assoc_root_dir= The operating system directory under
which sub-directories containing
associated files belonging to the
assembly and all of its components are
located.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-15
NX Integration Import and Data Release

Command Line Keywords With ug_import

Use of Quotation Marks

If you have any characters other than letters, digits, underscores, and
hyphens in the value that you specify for a particular keyword, it is
recommended that you enclose the value in quotation marks "" to avoid
import errors. For example, if you wish to import the part "chassis.prt" into a
folder in Teamcenter Engineering called "Concept Car" (note the space in the
folder name), it is advisable to specify the command:
ug_import -part=chassis.prt -import_folder="Concept Car"

Note that the Teamcenter Engineering folder name is surrounded by quotes.

Maximum Length Limit

There is a maximum length limit for the values corresponding to some of the
keywords used by ug_import.

Field Keyword Limit

Part Number -id= 26 characters
Revision -rev= 32 characters
Dataset Name -name= 32 characters

In addition, the combined (Part Name+Revision+Dataset Name) length must

not exceed 50 characters.

Login Keywords

If you have autologin enabled, -part= is the only keyword that must be
specified on the command line. All the other keywords listed in the table are
optional. However, if autologin is disabled the -u= and -p= keywords are
also required. For example,
ug_import -part=1400_wheel_000.prt -u=<user> -p=<password>

where <user> and <password> are the Teamcenter Engineering database

user and password.

16-16 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Import Component/Assembly Parts without a Map File

Scenario
In this scenario, seed part files will be imported.
ug_import -part=border_b_seed.prt -id=B-size -rev=000
-import_folder="Seed Parts" [-dryrun]
ug_import -part=border_c_seed.prt -id=C-size -rev=000
-import_folder="Seed Parts" [-dryrun]

Import a New Master Part File

By default, ug_import imports your assembly (that is, the part file specified
on the command line) as follows:
• All parts are imported as a master part file into the Newstuff folder.

• The top part in the assembly is overwritten, but any component parts
which already exist in the database are not overwritten.

• In order to change the default import behavior for the component parts,
you must specify a mapping file. Therefore assemblies will most likely
be imported with a mapping file.

The -part= keyword specifies the operating system pathname of the top part
in the NX assembly which is to be imported into Teamcenter Engineering.
Both master and non-master part files can be imported.
You must always specify the full pathname of the operating system part
file corresponding to the top level part in your assembly on the ug_import
command line unless the part is located in your current directory. For
example,
ug_import -part=/users/daytr/parts/1600_wheel_assy_000.prt

ug_import searches for the part files corresponding to the components of

your assembly in the same directory as the top part. If the component part
files are not located in the same operating system directory as the top part,
you must specify a search-list file so that ug_import can successfully locate
the components.
The following command line keywords can be used to change the default
import behavior for the top part in the assembly (only):
• –id=

• –rev=

The -id= and -rev= keywords can be used to import the part specified on the
command line (only) with a different part number and revision respectively.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-17
NX Integration Import and Data Release

Import Part Files into a Folder

The default behavior of ug_import is to import your standard NX assembly

into the folder named Newstuff in your Home folder in Teamcenter
Engineering. You can change the behavior of ug_import so that it imports
your assembly into a different folder. You do this by specifying the
-import_folder= keyword on the command line. For example:
ug_import -part=1600_wheel_assy_000.prt
-import_folder="1600 Wheel Assembly"

Note that the -import_folder= keyword causes the assembly and all of its
components to be imported into the specified folder. If you wish individual
components in the assembly to be imported into different folders, you must
specify the -import_folder directive in a mapping file instead.

Checking the Import

The -dryrun keyword allows you to see whether your import will progress
as you expect. It runs through the import procedure without actually
importing any parts into the Teamcenter Engineering database. The normal
ug_import messages are displayed, allowing you to check whether there will
be any errors when you do import the assembly, and to correct them before
proceeding.
The -dryrun keyword is particularly useful if you intend to import a large
assembly because the import checks are performed much faster than a full
import.

16-18 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Import an Assembly using a Map File and Search File

Scenario

In this scenario, a Wheel Assembly will be imported. A map file will be used
to convert all the part file names to their database part ID. Additionally a
search file will be used, since the parts are in various directories.
ug_import -part=1600_wheel_assy_000.prt -search=1600_search.txt
-mapping=1600_wheel_assy.map [-dryrun]

Search-List File

A search-list file is a text file which lists the operating system directories
which ug_import should search in order to locate the part files corresponding
to component parts in an assembly. The filename of a search-list file is
specified on the ug_import command line using the -search= keyword. For
example,
ug_import -part=1600_wheel_assy_000.prt
-search=1600_search.txt

You need to provide a search-list file if any part files corresponding to the
components of your assembly are located in different directories from the part
file which stores the top part in the assembly.
A search-list file simply lists the operating system directories which should be
searched to locate the component files of the assembly. Each directory should
be specified on a new line. If a directory name ends in "/...", all directories
beneath the specified directory also are searched.
For example, a search-list file with the contents:
.
/iman/daytr/v5_sitea/ug_import_files/...
/iman/class-default/v5_sitea_parts

would cause ug_import to search in the following order.

1. The current directory.

2. The directory named /iman/daytr/v5_sitea/ug_import_files and all of the

directories beneath it.

3. The /iman/class-default/v5_sitea_parts directory.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-19
NX Integration Import and Data Release

Mapping Files

A mapping file is an optional file that may be specified for the import utility.
The purpose of a mapping file is to allow you to specify exactly how individual
components in an assembly are imported into Teamcenter Engineering.

Mapping File Format

A mapping file is a simple text file which instructs ug_import how to

import the components in your assembly. The text in a mapping file may
comprise expressions, file names, directory names, and the names of parts
and revisions in the database.
A mapping file is divided into sections of the format:

[SECTION_NAME]
KEYWORD=VALUE
KEYWORD=VALUE

An example mapping file is shown below:

! Mapping file for importing chassis assembly

[Defaults]
import_folder = "Import Folder"
db_part_no=$STRIPPED_LEAFNAME
existing_data=$USE_EXISTING

[CA_36245.prt]
db_part_no="CA_36245_000"
db_part_rev="000"

[ENG_83475.prt]
existing_data=$OVERWRITE_EXISTING
db_part_no="ENG_83475_000"
db_part_rev="000"

16-20 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Key Points

There are a few general points to note when using mapping files:
• An exclamation mark (!) at the beginning of a line specifies the line as
a comment line.

• Mapping files can contain blank lines.

• ug_import ignores leading spaces at the beginning of a line.

• The maximum length of a line in a mapping file is restricted to 132

characters, including spaces.

• If you wish to include spaces in a field, then you must enclose the field
in double quotes.

• Each [SECTION_NAME] and KEYWORD=VALUE directive must be

specified on a separate line.

Using the SECTION_NAME

The SECTION_NAME field can be specified as either [Defaults] or the name

of a NX part file.
If you specify a SECTION_NAME of [Defaults], any KEYWORD=VALUE
mapping file directives specified in this section affect all of the components in
your assembly, unless they are deliberately overridden by specifying a section
corresponding to a NX part name.
For example, in the mapping file above, the directives in the [Defaults] section
affect all the parts to be imported. However, the directives in the sections
entitled [CA_36245.prt] and [ENG_83475.prt] are applied to those parts only,
and override the directives in the [Defaults] section.
A NX part number may be specified in a section by either the full operating
system pathname or just the part number.
You cannot use environment variables in filenames in a mapping file.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-21
NX Integration Import and Data Release

Using the KEYWORD AND VALUE

The KEYWORD field in a mapping file is one of a number of reserved

keywords. These keywords are tabulated below:

Keyword: db_part_no
Description: Teamcenter Engineering part (Item) ID
Valid Expression: $STRIPPED_LEAFNAME
$EXPORTED_PART_NO
Default: If the part has been previously exported
from NX Integration, defaults to the value it
had when exported. Otherwise, defaults to
$STRIPPED_LEAFNAME

Keyword: db_part_rev
Description: Teamcenter Engineering part revision
Valid Expression: $EXPORTED_PART_REV
Default: Defaults to A

Keyword: db_part_name
Description: Teamcenter Engineering part name
Valid Expression: $STRIPPED_LEAFNAME
$IMPORTED_PART_NO
Default: If the part has been previously exported from NX
Integration, defaults to the value it had when
exported. Otherwise, defaults to the same value as
db_part_no.

Keyword: db_part_desc
Description: Teamcenter Engineering part description
Valid Expression:
Default: Defaults to the same value as db_part_no, if
specified in a mapping file. Otherwise, defaults
to $STRIPPED_LEAFNAME (the file name of the
UG part without the leading directory and the .prt
extension).

16-22 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Keyword: import_folder
Description: Teamcenter Engineering folder where imported
parts are placed.
Valid Expression: $DEFAULT_IMPORT_FOLDER
Default: Your Newstuff folder. Note that -import_folder
specified on the command line takes precedence over
import_folder specified in a mapping file.

Keyword: existing_data
Description: What to do if parts already exist in Teamcenter
Engineering
Valid Expression: $FAIL_IF_PART_EXISTS
$FAIL_IF_REV_EXISTS
$OVERWRITE_EXISTING
$USE_EXISTING
Default: Overwrite the existing top part (only) in the
assembly, $OVERWRITE_EXISTING.
For all the component parts in the assembly, use
the existing data $USE_EXISTING.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-23
NX Integration Import and Data Release

The VALUE consists of part file names and optional reserved

EXPRESSION(s).
The reserved expressions are described below:

EXPRESSION EXPANDS TO:

$STRIPPED_LEAFNAME OS filename of the component (not
assembly) stripped of any prefix ending
in ‘/’ (UNIX) or ‘:’ (VMS) and the .prt
suffix. For example:
"/tmp/top_level_a.prt" → "top_level_a"
$STRIPPED___LEAFNAME OS filename of the component stripped
of any prefix ending in ‘/’ (UNIX) or ‘:’
(Note that there are three (VMS) and the suffix (delimited by ‘_’), if
underscores) present. For example:
"/tmp/top_level_a.prt" →"top_level"
$IMPORTED_PART_NO The part number, if the part is being
imported as it will be in Teamcenter
Engineering (i.e., after any renaming
specified by the mapping file has
occurred).
$DEFAULT_IMPORT_FOLDER Global default Teamcenter Engineering
target folder.
$FAIL_IF_PART_EXISTS If the Part (Item) exists, do not save the
assembly.
$FAIL_IF_REV_EXISTS If Part Revision (Item Revision) exists,
do not save the assembly.
$OVERWRITE_EXISTING If the part data exists, overwrite it.
$USE_EXISTING If a component already exists in
Teamcenter Engineering, use the
database copy in the current assembly.

16-24 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

The Import Log File

Below is an example log file (always named import.log) that is
created during the use of ug_import. Also a syslogfile is created
with more system information and placed in the /tmp directory.

**************** UG Import Utility ****************

Using UG V1.0.0.21
Using assembly load options - Load from directory.
Using supplied mapping file: [wf.map]
Loaded assembly [1600_wheel_assy_000.prt]
Connecting to the database...
Import parts to database using Teamcenter Integration for NX V9.0
Connected to the database.

The UG assembly [1600_wheel_assy_000.prt] comprises [5] part(s)

Part # 1, [/users/legacy/ug_import_files/1600_wheel_assy_000.prt]
Teamcenter Integration for NX part number is [1600/000] in folder [Newstuff]
Part will be created with type [Item].

Part # 2, [/users/legacy/ug_import_files/1250_axle_000.prt]
Teamcenter Integration for NX part number [1250/000] already exists.
Using the existing copy.
Existing part type [Item] will be retained.

Part # 3, [/users/legacy/ug_import_files/1300_bearing_000.prt]
Teamcenter Integration for NX part number is [1300/000] in folder [Newstuff]
Part will be created with type [Item].

Part # 4, [/users/legacy/ug_import_files/1400_wheel_000.prt]
Teamcenter Integration for NX part number is [1400/000] in folder [Newstuff]
Part will be created with type [Item].

Part # 5, [/users/legacy/ug_import_files/1700_spacer_000.prt]
Teamcenter Integration for NXpart number is [1700/000] in folder [Newstuff]
Part will be created with type [Item].

Creating 1600/000
Creating 1300/000
Creating 1400/000
Creating 1700/000

Starting Save.............

Saved part [1300/000] successfully.

Saved part [1400/000] successfully.
Saved part [1700/000] successfully.
Saved part [1600/000] successfully.

All parts were successfully saved.

************ UG_IMPORT finished without error ************

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-25
NX Integration Import and Data Release

Activity: Import the 1600 Wheel Assembly

In this activity, you will use ug_import to import an assembly part file and its
components into the database. You will use a mapping file to convert the part
file names to appropriate part numbers.
Step 1: Import the 1600 Wheel Assembly.
Continue to work from the Teamcenter Engineering
environment command window and the ug_import_files
directory.

Type: ug_import.scr.bat 1600 (ug_import.scr 1600 on Unix)

The following command is used to import files for the 1600
Wheel Assembly.
ug_import -part=1600_wheel_assy_000.prt
-search=1600_search.txt
-mapping=1600_wheel_assy.map

Step 2: Verify import in My Navigator.

Select your Home folder and choose View→Refresh.

Expand the Wheel Assembly Parts folder to show the assembly

parts.

Step 3: Review the 1600 Wheel assembly in NX Integration.

Expand the 1600-Wheel Assembly Item.

Expand the 1600/000-Wheel Assembly ItemRevision.

Double-click on the 1600/000 UGMASTER.

NX Integration starts and loads the 1600-Wheel Assembly.

This concludes the activity.

16-26 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Import a Non-Master Drawing File

Scenario

In this scenario, a Drawing file will be imported. To import this non-master

part file the following ug_import arguments will be used.
ug_import -part=1250_axle_000_dwg.prt -id=1250 -rev=000
-name=1250_DWG -type=manifestation [-dryrun]

Explanation

The ug_import utility cannot automatically detect whether a standard NX

part file is a master part file or a non-master part file, unless the master
part file has previously been exported from Teamcenter Engineering using
ug_export.

Using Command Line Keywords

A number of command-line keywords are provided that can be used to notify

ug_import of the type of part file to be imported:

KEYWORD VALUE
-id= The item ID of the master part
file which the non-master part
file is to belong to.
-rev= The item revision which is given
to your imported non-master
part file.
-type= The type of non-master part file.
This may be: specification (or
spec for short) ,or manifestation
(man for short).
-name= The name of the specification or
manifestation.

The keywords -id and -type must both be present for new non-master parts.
The -rev and -name keywords are optional, but are commonly used to provide
specific part revision and non-master dataset name.
Note that if -rev is omitted, and the revision is not specified in a mapping file,
the configured revision (according to the default configuration rule) is used. If
there is no configured revision, then revision "A" is used.
If the -name keyword is absent from the command line, the name of the
dataset defaults to the "stripped leafname" of the top part of the assembly.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-27
NX Integration Import and Data Release

Activity: Import the 1250 Axle Drawing

In this activity, you will import the 1250_axle_000_dwg.prt drawing file as a

non-master UGPART to the 1250 Axle Part.
Step 1: Import the 1250 Axle Drawing.
Continue working from the Teamcenter Engineering
environment command window and the ug_import_files
directory.

Type: ug_import.scr.bat 1250axledwg (ug_import.scr

1250axledwg on Unix)
The following command is used to import the
1250_axle_000_dwg.prt file.
ug_import -part=1250_axle_000_dwg.prt
-id=1250 -rev=000 -name=1250_DWG
-type=manifestation

Step 2: Review the 1250 Axle Drawing in My Navigator.

If necessary, expand the Wheel Assembly Parts folder to show
the 1250 Axle Item.

If necessary, expand the 1250 Item to show the 1250/000

ItemRevision.

Select the 1250/000 ItemRevision and choose View→Refresh to

display the new 1250_DWG UGPART dataset

Select the 1250_DWG UGPART dataset and then choose

View→Named References...
The Named References dialog displays showing the drawing
part file.

Choose Close to close the Named References window.

16-28 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Step 3: Review the 1250 Axle Drawing using NX Integration

To make this more clear, in NX Integration close all parts.
Choose File→Close→All Parts.

Choose Yes to confirm the closing of all parts.

Next Open the 1250 Axle Drawing.

Choose File→Open...

Expand the Wheel Assembly Parts folder and 1250 Item

structure.

Select the 1250_DWG dataset.

Choose OK.

The axle drawing is loaded into the graphics window.

This concludes the activity.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-29
NX Integration Import and Data Release

Import Files Associated to a (Master) Part File

Scenario
In this scenario, some files that are associated to parts will be imported. To
import these files associated to a part file the following ug_import arguments
will be used.
ug_import -part=1250_axle_a.prt -id=1250 -rev=000
-mapping=1600_wheel_assy.map -assoc_files=yes [-dryrun]

Explanation
The ug_import utility allows you to import dependent files that are associated
with both master and non-master part files. In this case dependent files
will be imported as named references into the 1250/000 UGMASTER. The
-mapping is used to map the Axle name of the 1250 part.

Using Command Line Keywords

Two further command-line arguments provide this capability:

KEYWORD VALUE
-assoc_files Used to instruct ug_import whether
to import associated files belonging to
the specified part and associated files
belonging to all of its components. The
value must be "yes" or "no".
-assoc_root_dir Specifies the root directory under
which sub-directories containing the
associated files belonging to all parts
in the specified assembly are located.
The directory must already exist.

Both -assoc_files and -assoc_root_dir are optional arguments to ug_import.

If you do not specify -assoc_root_dir on the command line, but you still want
associated files to be imported, you must specify -assoc_files=yes on the
command line. The ug_import utility then searches the following locations
(in the order shown) for the sub-directories containing associated files for
individual parts:
• the directory specified by the assoc_files_dir keyword in a mapping file
(if present).

• your current directory.

When the -assoc_root_dir argument is specified on the command line,

ug_import assumes that you wish to import associated files belonging to the

16-30 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

part specified on the command line, and the associated files belonging to each
of its components. The associated files are imported from sub-directories
beneath the directory specified by -assoc_root_dir.
If the specified associated files directory cannot be located, the import is
aborted.

Sub-directory Example

When using -assoc_files=yes without -assoc_root_dir= the dependent files

will be imported from the directory 1250. The 1250 is determined from the
Part ID (1250). The dependent files must be in this directory for ug_import
to find them.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-31
NX Integration Import and Data Release

Activity: Import the 1250 Axle Associated Files

In this activity, you will use the ug_import utility to import the 1250.tif file
associated to the 1250 Axle. This part was imported in the previous activity
with the 1600 Wheel Assembly.
Step 1: Import the 1250 Axle Associated files.
Continue working from Teamcenter Engineering environment
command window and the ug_import_files directory.

Type: ug_import.scr.bat 1250axleassoc (ug_import.scr

1250axleassoc on Unix)
The following command is used to import the 1250.tif file from
1250 sub-directory.
ug_import -part=1250_axle_000.prt -id=1250
-rev=000 -mapping=1600_wheel_assy.map
-assoc_files=yes

Step 2: Review the 1250 Axle Named References in My Navigator.

Locate and select the 1250/000 UGMASTER.

Choose View→Refresh to update the new file(s) in the

1250/000 UGMASTER.
Using View→Refresh is necessary since the 1250/000
UGMASTER was previous loaded in Teamcenter
Engineering.

Choose View→Named References...

The Named References window displays showing the part files,
including the new 1250_axle_000.tif file.

Choose Close to close the Named References window.

This concludes the activity.

16-32 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Import Files Associated to the DWG (Non-Master) Part File

Scenario

In this scenario, some files that are associated to drawings will be imported.
To import the files associated to a non-master part file the following ug_import
arguments will be used. What does this usage do?
ug_import -part=1250_axle_a.prt -id=1250 -rev=000
-name=1250_DWG -type=manifestation -assoc_files=yes

Explanation

The ug_import utility allows you to import dependent files that are associated
with non-master part files. In this case dependent files will be imported as
named references into the 1250_DWG UGPART.

Sub-directory Example

When using -assoc_files=yes without -assoc_root_dir= the dependent files will

be imported from the directory /1250_m_1250_dwg. The 1250_m_1250_dwg
is determined from part id (1250) + type (m for manifestation) + drawing
name (1250_dwg) with an underscore between each section. This gives the
sub-directory 1250_m_1250_dwg.
The dependent files must be in this directory for ug_import to find them.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-33
NX Integration Import and Data Release

Activity: Import the Axle Drawing Associated Files

In this activity, you will use the ug_import utility to import the
1250_000_dwg.cgm file associated to the 1250 Axle Drawing.
Step 1: Import the 1250 Axle Drawing Associated files.
Continue working in command window.

Type: ug_import.scr.bat 1250axledwgassoc (ug_import.scr

1250axledwgassoc on Unix)
The following command imports the 1250_000_dwg.cgm file
from the 1250_m_1250_dwg sub-directory.
ug_import -part=1250_axle_000_dwg.prt
-id=1250 -rev=000 -assoc_files=yes

Step 2: Review the 1250 Axle Drawing Named References.

In My Navigator, expand the Wheel Assembly Parts folder
structure to show the 1250 Axle Item.

Expand the 1250 Item.

Expand the 1250/000 ItemRevision.

Select the 1250_DWG UGPART dataset and then choose

View→Refresh to update the new file(s).

Choose View→Named References...

The Named References dialog displays showing the files,
including the new 1250_000_dwg.cgm file.

Choose Close to close the Named References window.

This concludes the activity.

16-34 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Import Files Using a Full Map File

Scenario 6

In this scenario, all the part files (master, non-master, and associated) will
be imported. To import all these files the following ug_import commands
will be used.

ug_import -part=2105_000.prt -mapping=2105_000.map

ug_import -part=2111_000_dwg.prt -mapping=2105_000.map
ug_import -part=2111_000_nc.prt -mapping=2105_000.map

The one map file will control the parameters for all these part files:
• components

• assemblies

• master part files

• non-master part files

• associated files to masters

• associated files to non-masters

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-35
NX Integration Import and Data Release

KEYWORDs for the Master Parts

These KEYWORDs are used in the mapping file to control the Part ID,
Revision, Part Name, and Part Description for the Item, Item Revision, and
UGMASTER created during the import.

KEYWORD DESCRIPTION DEFAULT

db_part_no Teamcenter If the part has been previously
Engineering part exported from NX Integration,
(Item) ID defaults to the value it had when
exported. Otherwise, defaults to
$STRIPPED_LEAFNAME
db_part_rev Teamcenter Defaults to A
Engineering part
revision
db_part_name Teamcenter If the part has been previously
Engineering part exported from NX Integration,
name defaults to the value it had when
exported. Otherwise, defaults to the
same value as db_part_no.
db_part_desc Teamcenter Defaults to the same value as
Engineering part db_part_no, if specified in a
description mapping file. Otherwise, defaults
to $STRIPPED_LEAFNAME (the
file name of the UG part without
the leading directory and the .prt
extension).

KEYWORDs for the Non-Master Parts

These KEYWORDs are used in the mapping file to control the name of the
UGPART (non-master) and determine the placement of the UGPART inside
the Item Revision (e.g. Specification, Manifestation relation).

db_model_name Teamcenter No default value (not required for

Engineering master model type)
dataset name
db_model_type Teamcenter The model can be: specification
Engineering (or spec for short) or manifestation
model type (man for short). If not specified the
model type defaults to master.

16-36 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

KEYWORDs for Associated Files for Master/Non-Master Parts

These KEYWORDs are used in the mapping file to control the import of
associated files (e.g. TIF, CGM, HTML, and other NX files). Specifying
assoc_files=yes will cause ug_import to import files into the UGMASTER or
UGPART as additional named references.

KEYWORD DESCRIPTION DEFAULT

assoc_files Used to instruct No default value. If assoc_files_dir
ug_import is not specified, defaults to a name
whether to resembling the part filename. For
import files example, the associated files for a
associated with part named 2111.prt are located in a
the specified sub-directory named 2111.
assembly
and all of its
components.
assoc_files_dir The The full path directory containing the
sub-directory associated files or the sub-directory
under the name from the current directory
current directory containing the associated files.
where associated
files for the
specified part
can be found.

General purpose KEYWORDs

These general purposed KEYWORDs are used in the mapping file to control
what folder imported parts are put into and whether components are
overridden.

import_folder Teamcenter Your Newstuff folder. Note that

Engineering -import_folder specified on the
folder where command line takes precedence over
imported parts import_folder specified in a mapping
are placed. file.
existing_data What to do if Overwrite the existing top
parts already part (only) in the assembly,
exists in $OVERWRITE_EXISTING. For all the
Teamcenter component parts in the assembly, use
Engineering the existing data $USE_EXISTING.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-37
NX Integration Import and Data Release

Below is an example map file. This mapping file will specify the ID and
Revision for the components but will also state the Model Type, Model Name,
and whether the part has Associated Files.
[Defaults]
existing_data=$USE_EXISTING
import_folder="2105 Assembly"
assoc_files=no

[2105_000.prt]
db_part_id=2105
db_part_name="Skate Assembly"
db_part_rev=000

[1101_000.prt]
db_part_id=1101
db_part_name="Wheel Assembly"
db_part_rev=000
assoc_files=yes

[1150_000.prt]
db_part_id=1150
db_part_name="Axle"
db_part_rev=000

[1113_000.prt]
db_part_id=1113
db_part_name="Hub"
db_part_rev=000

[1110_000.prt]
db_part_id=1110
db_part_name="Wheel"
db_part_rev=000

[2111_000.prt]
db_part_id=2111
db_part_name="Frame"
db_part_rev=000
assoc_files=yes

[2111_000_dwg.prt]
db_part_id=2111
db_part_rev=000
db_model_type=manifestation
db_model_name=2111_DWG
assoc_files=yes

[2111_000_nc.prt]
db_part_id=2111
db_part_rev=000
db_model_type=manifestation
db_model_name=2111_CAM
assoc_files=yes

16-38 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Activity: Import 2105 Frame Assy with Mapping File

In this activity, you will use the ug_import to import the 2105 Frame
Assembly by using a mapping file for all the master parts, non-master parts,
and associated files.
Step 1: Import the 2105 Frame Assembly and all of its other files.
In the command window, change to the ug_import_2105
directory, located in the aa_class directory.

Open the ug_import_2105.scr.bat script (ug_import_2105.scr

on Unix) in a text editor.

After reviewing the script, exit the text editor without saving.

Type: ug_import_2105.scr.bat (ug_import_2105.scr on Unix)

The following commands are used to import the assembly files.
ug_import -part=2105_000.prt
–mapping=2105_assy.map -assoc_files=yes
ug_import -part=2111_000_dwg.prt
-mapping=2105_assy.map -assoc_files=yes
ug_import -part=2111_000_nc.prt
-mapping=2105_assy.map -assoc_files=yes

Step 2: Review the 2105 Frame Assembly in My Navigator.

When the script is finished, select the Home folder and choose
View→Refresh.
The 2105 Assembly folder show now be visible.

Expand the 2105 Assembly folder to show the assembly parts.

Step 3: As desired, review the 2105 Frame Assembly using NX Integration.

To make this more clear, in NX Integration, choose
File→Close→All Parts.
Next Open the 2105 Frame Assembly.

Choose File→Open...

Expand the 2105 Assembly folder and 2105 Item structure.

Select the 2105/000 UGMASTER dataset.

Choose OK.
The 2105 Frame Assembly loads into the graphics window.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-39
NX Integration Import and Data Release

Step 4: Review the non-master 2111 Frame Drawing.

From NX, choose File→Open...

Expand the 2105 Assembly folder and 2111 Item structure.

Select the 2111_DWG dataset.

Choose OK.
The frame drawing loads into the graphics window.

Step 5: Close Teamcenter Integration for NX.

From NX, choose File→Exit

Choose Yes to confirm the exit.

This concludes the activity.

16-40 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Importing Non-CAD Files into an Item

The M243_Heat_Treat text file should be imported into the database to be a
reference of the 1250 axle part.
The import_file utility allows you to import files into the Teamcenter
Engineering database according to a set of user-specified arguments. These
arguments will supply:
• user identification information

• dataset information

• Item information to be associated with the imported file

The latter is new in this class for the use of import_file. In supplying the
Item information, a Dataset and Item will be created and the dataset will be
placed inside the Item.
In practice this utility is used:
1. To import files into Teamcenter Engineering just as datasets (as seem
in a previous lesson).

2. To import files into Teamcenter Engineering as datasets and automatically

place the dataset inside an Item or Item Revision. The Item can be
created or already exist.

3. To import other CAD files into Teamcenter Engineering as datasets and

place the file inside an Item Revision.

The import_file options for importing a dataset:

IMAN_ROOT/bin/import_file -f=<filename>
-type=<datasettype> -d=<dataset_name>
-ref=<named_reference> [-item=<item_id>]
[-revision=<item_rev>] [-ie={n | y}] [-log=<file>]

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-41
NX Integration Import and Data Release

Activity: Import the Heat Treat Text File

In this activity, you will use the import_file utility to import a text file into the
database to be a reference of the 1250 Axle part.
Step 1: Import the m243_heat_treat.txt text file.
In the command window, change back to the ug_import_files
directory located in the aa_class directory.

Type: ug_import.scr.bat heattreat ( ug_import.scr heattreat

on Unix)
The following command is used to import m243_heat_treat.txt
into the 1250/000 Axle ItemRevision as a Reference.
IMAN_ROOT/bin/import_file -f=m243_heat_treat.txt
-d=M243_Heat_Treat -type=Text -ref=Text -de=a
-item=1250 -revision=000 -ie=y -log=-

Step 2: Review the imported file inside the 1250 Axle.

Expand the Wheel Assembly Parts folder.

Expand the 1250 Item and 1250/000 ItemRevision.

Select the 1250/000 ItemRevision and choose View→Refresh to

display the new M243_Heat_Treat dataset.

Double-click on the M243_Heat_Treat dataset.

The M243_Heat_Treat dataset is opened into the default editor.

Review the file, then exit the text editor.

This concludes the activity.

16-42 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

Releasing Previously Imported NX Data

After the NX data has been imported into Teamcenter Engineering you may
choose to release the data. The import step only imports the data and usually
leaves the data in an unreleased, writable state.
Normally the release process would require review and signoff by one or more
employees. In this case the data may have already been in a release state
outside of Teamcenter Engineering and the data has just been imported.
Especially for CAD/CAM data, in this case the NX data, there may be a
stronger need for a Single Level Release. Before providing the signoff, the
responsible user may want to open the UGMASTER being released with
the Item Revision.

Considerations in Releasing Item Revisions

When releasing ItemRevisions, the Specification relation objects are released

together with the handler EPM-attach-target-objects.

Considerations in Releasing Non-specification Data

When non-specification data is released the reviewers defined in the

procedure may be different than the reviewer defined in the procedure for
master and specification data.
When releasing non-specification data immediately after the data has been
imported, the data could be released in the same procedure as the master and
specification data. This could be accomplished by initiating the Item Revision
and pasting the non-specification data into the Job (before the Job is started).

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-43
NX Integration Import and Data Release

Activity: Release the 2111 Item Revision

In this activity, you will use the Import Release process template to release
some of your previously imported data.
Step 1: Initiate the 2111 Frame ItemRevision.
If necessary, expand the 2105 Assembly folder.

Expand the 2111-Frame Item to show the 2111/000-Frame

ItemRevision.

Select the 2111/000 Frame ItemRevision.

Choose File→New→Process...
The New Process dialog appears. The Process Name defaults
to the object name.

Optionally enter a Description: releasing imported data

Set the Process Template Filter to Assigned.

Notice the Process Template defaults to Import Release
because of preferences you set in an earlier lesson.

Choose OK.

Step 2: Review the data from your Inbox and perform the signoff.

Choose the Open Inbox icon.

Expand your Tasks to Perform Folder

The perform-signoffs task was automatically assigned to you

because of the CR-fill-in-reviewers handler you added to the
Import Release process template in an earlier lesson.

Select the perform-signoffs task.

16-44 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007
 NX Integration Import and Data Release

View the Attachments.

Choose the No Decision link.

Choose Approve, then Apply.

In the Home folder, select the 2111/000-Frame ItemRevision

and choose View→Refresh.

If necessary, select the 2111/000 UGMASTER and choose

View→Refresh.

Notice that the status flags have now been set.

This concludes the activity.

©UGS Corp., All Rights Reserved Teamcenter Engineering Application Administration 16-45
NX Integration Import and Data Release

Summary
In this lesson you:
• Imported NX Data into the Database

• Released Imported NX Data

16-46 Teamcenter Engineering Application Administration ©UGS Corp., All Rights Reserved MT14350-S-2007