If yes, the part is automatically copied from the server into the local cache and opened in the CAD system.

If not, the part is created in the local cache and form there "checked into" Teamcenter. Finally this information is saved in the LinkDB.

$CADENAS_SETUP/ifacecommon.cfg

"AppBeforeCreate" and "AppAfterCreate" have to be commented in.

[CreationOptions]
AppBeforeCreate=GetObject("pdm.callbackCheckinout").AppBeforeCreate
AppAfterCreate=GetObject("pdm.callbackCheckinout").AppAfterCreate

$CADENAS_SETUP/ifseteamcenter.cfg

ACTIVE_CONDITION has to be set on "true".

[PLM]
ACTIVE_CONDITION=true

ItemType

[CreationOptions]
TC_ItemType=

Here you can define the ItemType for parts from PARTsolutions. If this key is not defined, then the type “Item“ is used.

ItemID

[CreationOptions]
TC_ItemId=

If the ItemID shall come from Teamcenter, then leave this key empty.

The following example shows, how you can define the ItemID yourself:

TC_ItemId=?GetObject("iface.calcnameservice").start(0).Format("<ATTR(NB)>").value()

The display name in the following figure is composed of TC_ItemId and TC_ItemName (here in this example NB=standard name).

"TC_ItemId" assigned from Teamcenter and "TC_ItemName" from NB

Detailed information how you can individually adjust the ItemID is found under Section 2.2.1.4, “Variable values - functions ” or in the examples of the configuration file.

Revision

[CreationOptions]
TC_ItemRevision=

If nothing is declared, then revision “A“ is used by default.

ItemName

[CreationOptions]
TC_ItemName=

If nothing is declared for TC_ItemName, then this value is set with TC_ItemID.

Exemplary entry:

TC_ItemName=?GetObject("iface.calcnameservice").start(0).Format("<SHORTNAME>").value()

In this way the Shortname is set.

ItemDescription

[CreationOptions]
TC_ItemDescription=

If nothing is declared for TC_ItemDescription, then this key is set with the standard name.

Exemplary entry:

TC_ItemDescription=?GetObject("iface.calcnameservice").start(0).
 Format("<ATTR(LINA)>").value()

In this way the bom name is set.

TargetFolder

[CreationOptions]
TC_TargetFolder=

Path to the Teamcenter directory, where a part is moved after checkin to Teamcenter.

Example:

TC_TargetFolder=Home\BaseFolder01\SubFolder01

Not existing directories are automatically created.

Note The following 3 keys are needed, when the key under [CreationOptions] -> TC_TargetFolder is set. (Login data for the Teamcenter API: user name, password, host name). They also can be used for other Teamcenter HookService methods. TC_HookService_Login_USER= Only a value (no categories) per key is supported. The stated user has to have access right on the objects of that user logged in to Solid Edge for TC. TC_HookService_Login_PASS= Only a value (no categories) per key is supported. TC_HookService_Login_HOST=

If moving is not wanted, comment out the keyTC_TargetFolder. Then parts will remain in the Solid Edge standard directory.

LinkDB ReturnMapping

Via LinkDB-ReturnMapping, PDM attributes can be mapped to link database fields.

At first, in the block [AttributeMapping(is3d)], the block for the actual LinkDB mapping has to be declared (as usual).

[AttributeMapping(is3d)]
Attr_Content_00=LINKDB_RETURN_MAPPING
Attr_Section_00=LINKDB_RETURN_MAPPING

Now in NX, start PARTdataManager as usual and export the parts into the CAD system. Now the parts are automatically exported to Teamcenter. <ERP_COLUMN_NAME> or LINKTABLE.<ERP_COLUMN_NAME> have to be an existing VARCHAR column!

Example:

[LINKDB_RETURN_MAPPING(is3d)]
ERPTABLE.<ERP_COLUMN_NAME>=?"'%TC_ItemId%'"

ERPTABLE.<ERP_COLUMN_NAME> specifies table and column, the value the placeholder to be used. Thereby the ItemId for example (which is possibly created during the generation in Teamcenter) can be saved in the LinkDB.

Supported placeholders for ERPTABLE.<ERP_COLUMN_NAME> are:

After a new creation of parts the project has to be reloaded in PARTdataManager in order for the PDM values to be displayed.