powered by CADENAS

Manual

Manual

3.3.10.4. Teamcenter - Pro/E / Creo

The Teamcenter interface is compatible for all CAD interfaces of Pro/E and Creo.

How does the PDM integration work?

During the export form PARTsolutions to a CAD system an inquiry is sent to the LinkDB, whether the part is already available:

  • If yes, the part is automatically exported from the server into the ProE start directory for iPEM and opened in the CAD system.

  • If no, the part is created in the working directory (=poolpath) and from there checked into Teamcenter. Afterwards this information is saved in the LinkDB and the part now saved in the ProE start directory for iPEM (working directory=poolpath) is opened in the CAD system.

    (On this also compare the key poolpath.

Preconditions and particularities

The file name can either come from PARTsolutions or from Teamcenter. This is adjustable (see below under Filename).

Installation

Please carry out the Teamcenter installation on the basis of the Teamcenter manual. For the interface installation please select the Teamcenter package in the PDM category within the installation routine. Alternatively you can download the interface from the internet.

Activate PDM interface:

  • $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/ifproeteamcenter.cfg

    ACTIVE_CONDITION has to be set on "true".

    [PLM]
    ACTIVE_CONDITION=true

Configuration

The Teamcenter interface configuration is carried out under $CADENAS_SETUP/ifproeteamcenter.cfg.

  • ItemType

    The Teamcenter ItemType for new parts. Default (key commented out) is "Item".

    [Note] Note

    An empty key is not supported!

    [CreationOptions]
    TC_ItemType(is3dPart)= 
    TC_ItemType(is3dAsm)=

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

  • ItemName

    The ItemName in Teamcenter is set to the value defined here.

    [CreationOptions]
    TC_ItemName=

    Exemplary entry:

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

    For ItemName the standard name can be set for example.

  • ItemDescription

    [CreationOptions]
    TC_ItemDescription=

    Exemplary entry:

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

    For ItemDescription the bom name can be set for example.

  • DatasetDescription

    The Teamcenter description for parts.

    [CreationOptions]
    TC_DatasetDescription=

    Exemplary entry:

    TC_DatasetDescription=?GetObject("iface.calcnameservice").start(0).Format("<GenNAME(26)>").
     alnum("").value()

  • ItemID

    [CreationOptions]
    TC_ItemId(is3dPart)=
    TC_ItemId(is3dAsm)=

    The ItemID is used for the checkin.

    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)>").alnum("").value()

    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.

  • RevisionID

    RevisionID, which is used for the checkin. If this is empty, then the RevisionID for the checkin is called from Teamcenter.

    [CreationOptions]
    TC_ItemRevision(is3dPart)=
    TC_ItemRevision(is3dAsm)=

  • TmpFolder

    [Teamcenter_iPEM_section]
    TC_TmpFolder=

    Here you can define the storage folder for parts from PARTsolutions.

    If the key is empty, then the folder “Newstuff“ is used by default.

  • TargetFolder

    [CreationOptions]
    TC_TargetFolder=

    Path to the Teamcenter folder, where a PARTsolutions part is moved after it has been checked in the TC_TmpFolder.

    Example:

    TC_TargetFolder=Home\BaseFolder01\SubFolder01

    [Important] Important

    Please regard upper and lower case!

    It is necessary to move the parts, because ipemimport.bat does not support paths.

    If moving is not wanted, then comment out the key TC_TargetFolder. In this case the part remains in the folder defined under TC_TmpFolder.

    Not existing folders are automatically created.

    [Note] Note

    If folders shall be created, <TC_TmpFolder> has also to be set correctly – if the default value is not the desired one.

  • Filename

    In order to set the file name please use the key "Filename".

    Supported place holders are:

    • %TC_ItemId%

    • %TC_ItemName%

    • %TC_ItemDescription%

    • %TC_ItemRevision%

    • %TC_ItemType%

    Examples with file name from Teamcenter

    Filename(is3dPart)=?"Part-%TC_ItemId%" 
    Filename(is3dAsm)=?"Asm-%TC_ItemId%"

    Filename=?"%TC_ItemId%-%TC_ItemName%"

    Filename=?"%TC_ItemId%-%TC_ItemDescription%"

    Examples with file name from PARTsolutions

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

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

    Notes how to individually adjust the file name are found under Section 2.2.1.4, “Variable values - functions ”.

    [Note] Note

    Should there be an additional .prt or .asm in the file name (meaning not the file extension), this will not be removed.

    If the file name has no file extension .asm or .prt, then the correct file extension is added.

    Only use characters, which are supported by ProE!

  • poolpath

    The "local WorkDir" should be set on the ProE start dir for iPEM.

    [Note] Note

    No subdirectories!

    ONE poolpath for ALL parts!!!

  • 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:

    Supported placeholders: {%TC_ItemId%, %TC_ItemName%, %TC_ItemDescription%, %TC_ItemRevision%, %TC_ItemType%, %Master_Item_Id%}.

    • %TC_ItemId%

    • %TC_ItemName%

    • %TC_ItemDescription%

    • %TC_ItemRevision%

    • %TC_ItemType%

    • %TC_ItemType%, %Master_Item_Id%

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

Checking functions in the CAD system

In order to use the ProEngineer-Teamcenter integration, please start PARTdataManager via ProEngineer (Teamcenter Addin has to be loaded) and export the parts into your CAD system. Now the parts are automatically exported to Teamcenter.

For further additional functions see Section 3.3.10.5, “Teamcenter additional functions (teamcenter_public_api.vbb) ”.