SAP Engineering Control Center Interface to Inventor

CIDEON Software & Services GmbH & Co. KG Page 1 of 128 2021-12-15Peterstrasse 1 : D-02826 Goerlitz Web: https://www.cideon.com

Configuration Manual

Management of CAD data and documents in SAP

SAP Engineering Control Center Interface toInventor

SAP Engineering Control Center Interface to Inventor manages design data in SAP.

Given by the SAP Engineering Control Center Interface, tight integration of the CAD system to the SAP PLMdata available to the company at an early stage in the design process are available. Product lifecyclemanagement thus already begins with the start of design work and not through an interface at the end of it.The coupling between the CAD system and the SAP Engineering Control Center allows you to manage thecomponents designed in the CAD system.

You can configure the SAP Engineering Control Center Interface to Inventor in many different ways and adapt itto your own requirements and working methods. This configuration manual presents the possibleconfigurations and describes the procedures and configuration parameters in detail.

© 2021 CIDEON Software & Services GmbH & Co. KG. Germany. All Rights Reserved.

Contents of this document may not be (totally or partly) reproduced, used or published without previouswritten agreement by the CIDEON Software & Services GmbH & Co. KG.Copyright applies to all forms of storage and reproduction, in those the available information flowed inparticular on magnetic storage, computer expressions or visual announcements.


Folder structure and directories 4 .................................................................................................................. Icons for CAD originals in SAP ECTR 6 ............................................................................................................... Registrationless integration of add-ins in the CAD system 7 ............................................................................. Starting Inventor from ECTR in the SAP logon language 8 ................................................................................

The configuration files 9 ................................................................................................................................... Menu definitions 9 .............................................................................................................................................

menu.guidef 9 ................................................................................................................................................ menu_macros.txt 13 ......................................................................................................................................

The files "attributes-from-sap.xml" and "attributes-to-sap.xml" 13 ................................................................... attributes-from-sap.xml 14 ............................................................................................................................ attributes-to-sap.xml 17 ................................................................................................................................. Inventor Properties 20 ....................................................................................................................................

default.txt 31 ..................................................................................................................................................... Parameter description - Part 1 31 .................................................................................................................. Parameter description - Part 2 39 .................................................................................................................. Use Excel files as parameter files 47 ............................................................................................................. Creating mold assemblies with "ECTR New" 47 .............................................................................................

dtype.xml 48 ..................................................................................................................................................... DType definitions for Inventor 48 ...................................................................................................................

Generic DType definitions 49 ..................................................................................................................... The DType definition for master documents 72 ......................................................................................... The DType definitions for nonmaster documents 109 ................................................................................

options.xml 115 ................................................................................................................................................. plm_setenv.bat 119 ........................................................................................................................................... rfc-tunnel-whitelist.txt 119 ................................................................................................................................ Loading rules for opening documents (load_scenarios.xml) 120 ....................................................................... Version information 123 ....................................................................................................................................

Final Remark 128 ...............................................................................................................................................



Folder structure and directories

The SAP Engineering Control Center requires a certain folder structure that is established during theinstallation process.

The system-wide environment variable %PLM_INSTDIR% contains the installation directory of theSAP Engineering Control Center and is set up during installation.

Under %PLM_INSTDIR%\applications\ the individual add-ins are stored during their installation in separatesubdirectories.

%PLM_INSTDIR%\applications\inv is the installation directory of the SAP Engineering Control Center Interface toInventor. It contains the following subdirectories which are significant for configuration:

%PLM_INSTDIR%\applications\inv\appdata%PLM_INSTDIR%\applications\inv\basis%PLM_INSTDIR%\applications\inv\documentation%PLM_INSTDIR%\applications\inv\templates%PLM_INSTDIR%\applications\inv\template-templates%PLM_INSTDIR%\applications\inv\customize\config%PLM_INSTDIR%\applications\inv\customize\scripts\macros%PLM_INSTDIR%\applications\inv\template-customize\config

The directory appdata

Two subdirectories are included here:

Additional Files:This subdirectory contains the template file "CdnECTRInterfaceInv.addin". This file contains thenecessary information for the integration to be loaded in Inventor. If the integration is installed bymeans of Installer, the file is already copied into the AddIn directory of Inventor under"%ProgramData%\Autodesk\Inventor 20xx\Addins" and the path to the ECTR installation is adapted inthe file.The file "readme.txt" contains a short instruction of the procedure for this.icons:This subdirectory contains the images used in the Inventor Ribbon of the SAP Engineering ControlCenter Interface to Inventor. The symbols are available as 16x16, 24x24, 32x32 and 48x48 pixel PNGfiles. The name of the file corresponds to the command to be called, plus the size. The images can bereplaced by your own images if necessary.

ATTENTION: The installer always resets them to the original state!

The directory basis

Here, the following directories are included:

aux-files: Contains the data "standard_icons.txt". This determines which symbols are to be used forcommands and document information. See also the ECTR documentation "SAP Implementation GuideIcons_EN.pdf".classes: Contains Java classes that are necessary for interface operation.dictionary: Contains subdirectories with a "dictionary.txt" file with display texts in the supportedlanguages (DE, EN, ES, FR, IT, JA, PT, RU, ZH and ZF).


sys: In sys\win\bin the individual interface modules can be found. These are loaded via the add-in inInventor (see "Registrationless integration of add-ins in the CAD system").

The directory documentation

In this directory, the user manuals can be found in both German and English as PDF files.

The directories templates and template-templates

If a new document is created via the SAP Engineering Control Center, you can choose from a list of documenttemplates. These submissions can be found in the directory templates. A pool of various documentsubmissions can be found in the template-templates directory. After re-installation, the contents of bothdirectories are identical. Should new or changed templates be delivered with a patch or an update, they will bestored in template-templates. Should these appear in the above-mentioned lists, the appropriate data must becopied into the templates directory. Furthermore, the templates must be registered in the "dtype.xml" file.

The directory customize\config

Here, files can be found that are necessary for the configuration of the SAP Engineering Control CenterInterface to Inventor. These are:

default.txtdtype.xmloptions.xmlmenu.guidefmenu_macros.txtplm_setenv.batattributes-from-sap.xmlattributes-to-sap.xmlrfc-tunnel-whitelist.txt

At the start of Inventor, these files are evaluated and override the basic installation of the SAP EngineeringControl Center that is filed under %PLM_INSTDIR%\customize\config and add additional CAD-specificconfigurations that are not included in the basic configuration, for example specific types of documents,workstation applications and menu items.

The directory customize\scripts

This directory contains additional batch scripts that extend the check-in and check-out process.

The directory customize\scripts\macros

This directory contains files that define Inventor macros. The files shipped with the installation in this directory:

inv_idw.txtinv_ipn.txtmap_attributes.txtget_related_drawings.txtget_related_presentations.txt

The files "inv_idw.txt" and "inv_ipn.txt" contain sample implementations for macros.

The directory template-customize\config

https://docu.int.cideon.de/node/9235


The standard settings are filed as copies in the template-customize\config special directory, which containshomonymous files to those in customize\config for that reason.

After a software update, i.e. patch, the bundled configuration files are only stored in the template-customize\config directory. Thus, the user settings remain in directory customize\config.However, this also means that changes and extensions to the configuration are notcustomized automatically during updates. These must be carried out manually asneeded!

Icons for CAD originals in SAP ECTR

In the SAP Engineering Control Center, information on documents is displayed in the form of icons. In additionto general icons, which are valid for all documents, there are icons especially for the <CAD> object typesdefined in the configuration file "dtype.xml". Depending on the document status, the background of the objecttype icons can be colored. Further information about the <CAD> object is placed in the form of overlays overthe object type icon.A set of standard icons is delivered in the file "%PLM_INSTDIR%\applications\inv\base\classes\images.jar".

For detailed information on icons in the SAP Engineering Control Center, see the help file "SAPImplementation Guide Icons_EN.pdf", which can be found in the directory"%PLM_INSTDIR%\documentation\Manuals\en" or in the ECTR menu under "Help->DisplayDocumentation" in the section "SAP Engineering Control Center".

The configuration file "dtype.xml" defines which icons are displayed and in which order the icons are displayedfor each DType. The status-dependent background color of the object type icons is defined in the globalconfiguration file "default.txt" of the SAP Engineering Control Center.

Displayed icons can be supplemented with overlay icons to visualize certain states in which thedisplayed objects are located. For the meaning of these symbols, refer to SAP's ECTRdocumentation.

The following table provides an overview of the standard symbols for Inventor:

Icons for Inventor supplied as standard

Symbol Description File name in "images.jar"Inventor single part documentDType: Document symbol position 1tree/inv/inventor_part_$(FAMILY)16 with$(FAMILY) = <empty>

tree\inv\inventor_part_16.png

Inventor iPart part family documentDType: Document symbol position 1tree/inv/inventor_part_$(FAMILY)16 with$(FAMILY) = g

tree\inv\inventor_part_g16.png

Inventor iPart variants documentDType: Document symbol position 1tree/inv/inventor_part_$(FAMILY)16 with$(FAMILY) = i

tree\inv\inventor_part_i16.png


Inventor Assembly documentDType: Document symbol position 1tree/inv/inventor_assembly_$(FAMILY)16with $(FAMILY) = <empty>

tree\inv\inventor_assembly_16.png

Inventor iAssembly parts family documentDType: Document symbol position 1tree/inv/inventor_assembly_$(FAMILY)16with $(FAMILY) = g

tree\inv\inventor_assembly_g16.png

Inventor iAssembly variants documentDType: Document symbol position 1tree/inv/inventor_assembly_$(FAMILY)16with $(FAMILY) = i

tree\inv\inventor_assembly_i16.png

Inventor presentation documentDType: Document symbol position 1tree/inv/inventor_presentation_16

tree\inv\inventor_presentation_16.png

Inventor drawing master documentDType: Document symbol position 1tree/inv/inventor_drawing_16

tree\inv\inventor_drawing_16.png

Inventor drawing dependent document(document is up-to-date compared to themaster)DType: Document symbol position 1tree/inv/inventor_drawing_16$(NM_OLD)with $(NM_OLD)= 0

Replacement is done in file "standard_icons. txt"tree/inv/inventor_drawing_160 =tree/inv/inventor_drawing_16Thus, the tree\inv\inventor_drawing_16.png from file"images.jar" is used.

Inventor drawing dependent document(document is outdated compared to themaster)DType: Document symbol position 1tree/inv/inventor_drawing_16$(NM_OLD)with $(NM_OLD)= 1

Replacement is done in file "standard_icons. txt"tree/inv/inventor_drawing_161 =tree/inv/inventor_drawing_16<<{0}/sap/o_outdatedtree\inv\inventor_drawing_16.png will be overlaid with{0}\sap\o_outdated.{0} stands for size. Possible values are small,medium, large.

Inventor documentWorkstation Application INV tree\file\obr_tree_file_inv.png

Inventor applicationMenu: System\Start application\Inventor small\app_inventor.png

Registrationless integration of add-ins in the CAD system

The integration of the SAP Engineering Control Center Interface to Inventor in the CAD system takes placeduring installation, without the necessity of a registration of the add-in. To this end, from the installer, thedirectory "%PLM_INSTDIR%\applications\inv\appdata\Additional Files\" is created with the files"CdnECTRInterfaceInv.addin" and "Readme.txt". The file "CdnECTRInterfaceInv.addin" is copied to thedirectory "%ProgramData%\Autodesk\<Inventor Version>\Addins\", where "<Inventor Version>" denotes thecurrently used inventor version:

The directory Addins

%ProgramData%\Autodesk\<Inventor Version>\|__ \Addins\ |__ CdnECTRInterfaceInv.addin


The path contained in the file "CdnECTRInterfaceInv.addin" under the XML tag <Assembly> for the interfacemodule "CdnECTRInterfaceInv64.dll" is adjusted to the current conditions:

Example of an adjusted path in the file "CdnECTRInterfaceInv.addin"

<Assembly>D:\CIDEON\ECTR\ECTR50_02\applications\inv\basis\sys\win\bin\CdnECTRInterfaceInv64.dll</Assembly>

During startup, the inventor evaluates this file and the path contained therein and integrates the found module"CdnECTRInterfaceInv64.dll" as an add-in.

The file "Readme.txt" contains an explanation of the methods described here for future reference.

Starting Inventor from ECTR in the SAP logon language

If Inventor is started from within the SAP Engineering Control Center, i.e. using the context menu command"Open original" or by double-clicking on an Inventor document, the CAD system is automatically executed inthe SAP logon language of the ECTR. The environment variable "%PLM_LANGUAGE%" is responsible for thisbehavior. This is set by the ECTR to the SAP logon language and evaluated accordingly when Inventor isstarted.

Whether the environment variable "%PLM_LANGUAGE%" is evaluated depends on theconfiguration of the parameter "plm.appl.language.INV" in the configuration file "default.txt"(available from patch level 14).

If the SAP logon language for Inventor is not available or unknown, the CAD system is started inthe language in which it was last started!


The configuration files

The files contained in the %PLM_INSTDIR%\applications\inv\customize\config directory serve the CAD-specificconfigurations of the SAP Engineering Control Center. These files are also marked as preference files and aresimple text files that can be edited with a simple ANSI-text editor, i.e. the Windows-specific text editor"Notepad.exe". They are filed there during the installation of the SAP Engineering Control Center Interface toInventor, with standard settings for this interface.

The standard settings are chosen so that typical usage scenarios are covered. Should this not be enough, thereaction of the interface and the SAP Engineering Control Center should adapt appropriately. Next to thecentral configuration files in %PLM_INSTDIR%\customize\config, each application has its own configuration filesin directory %PLM_INSTDIR%\applications\<<name of application>>\customize\config. The individual filesdiffer from homonymous files in the configuration directory of the SAP Engineering Control Center in that onlythe respective CAD specificity are controlled through them.

During the start of the SAP Engineering Control Center, the standard configuration is read and then overriddenwith the content of the CAD-specific configuration files. Each interface, if multiple interfaces are installed, hasits own set of CAD-specific configuration files.

For a detailed clarification of purpose, structure and handling of the configuration files, pleaserefer to the SAP Engineering Control Center documentation, specifically the configurationhandbook (file "Configuration Guide_EN.pdf") and the operations guide (file "OperationsGuide_EN.pdf"), which can be found under %PLM_INSTDIR%\documentation\Manuals\en!

Menu definitions

Menu items that should be available along with the SAP Engineering Control Center Interface to Inventor in theuser interface of the SAP Engineering Control Center are defined in the file "menu.guidef".Recurring function sequences in menus and sub-menus can be defined as macros in the file"menu_macros.txt". These macros will then only be referenced in the menu definitions in the file"menu.guidef". In addition to the global files with the same name under %PLM_INSTDIR%\customize\configthere are the CAD-specific counterparts, which additionally define appropriate menus for the SAP EngineeringControl Center.

menu.guidef

The file "menu.guidef" contains menu items that are available in connection with the SAP Engineering ControlCenter Interface to AutoCAD in the user interface of the SAP Engineering Control Center.

Construction of a menu definition

Each individual menu definition begins with a plus sign ('+') in the first column of the line, followed bythe menu identification.The individual functions that appear in the menu are arranged one after the other, in which each menufunction is preceded by an equal sign ('=').In each menu definition, macros, which are defined in the file "menu_macros.txt" or in the generalmacro definition file "%PLM_INSTDIR%\customize\config\menu_macros.txt", are referenced by theirnames which are preceded by a question mark ('?').Sub-menus in the menu are designated by indentation of the associated menu entries, for which onlyblank spaces may be used.


Tabs are not allowed!Separators within the menu are represented by a line consisting of dashes ('-').Commentaries can be inserted. These are preceded by a '#' at the beginning of the line.

Unlock menu for interoperability between Inventor and AutoCAD

As the document type "dwg" can be opened in Inventor as well as in both AutoCAD and AutoCAD Mechanical, aspecial menu for the user interface of the SAP Engineering Control Center can be offered:

Interoperability menu for Inventor

This is already included and unlocked in the supplied CAD-specific file "menu.guidef" (menu definition"om.popup.menu.DOC.DOC_INVDWG", see red mark):


Menus with interoperability with AutoCAD unlocked

This menu definition may be deactivated. It requires two steps:

Comment out the menu definition "om.popup.menu.DOC.DOC_INVDWG" marked as "Interop".In the configuration file "dtype.xml" the function_group of DType "IDWGT" in the program_options mustbe changed to "DOC_GENERAL".

Definition of the context menu for cloning

A context menu is provided for the "Clone" functionality of the SAP Engineering Control Center. Its range offunctions are defined using the parameters "om.popup. menu.CLONEPOS.DOC_INVxxx":


Definition of the context menu for "Cloning"

# ----- Cloning Options

+ om.popup.menu.CLONEPOS.DOC_INVDRW = ? DOCUMENT_INV_GENERAL_CLONING

+ om.popup.menu.CLONEPOS.DOC_INVDWG = ? DOCUMENT_INV_GENERAL_CLONING

+ om.popup.menu.CLONEPOS.DOC_INVMDL = ? DOCUMENT_INV_GENERAL_CLONING

+ om.popup.menu.CLONEPOS.DOC_INVCC = fnc.doc.clone.option.NO_ACTION = fnc.doc.clone.option.REPLACE_OPTION = fnc.doc.clone.option.DELETE_OPTION = ----------------------------- = fnc.clpbrd.delete = fnc.doc.reload

+ om.popup.menu.CLONEPOS.DOC_INVNR = fnc.doc.clone.option.NO_ACTION = fnc.doc.clone.option.INSERT_OPTION = fnc.doc.clone.option.REPLACE_OPTION = fnc.doc.clone.option.DELETE_OPTION = fnc.doc.clone.option.NEWVERS_OPTION = fnc.doc.clone.option.CHANGE_OPTION = ----------------------------- = fnc.doc.clone.select.dependent = ----------------------------- = fnc.clpbrd.delete = fnc.doc.reload

The macro "DOCUMENT_INV_GENERAL_CLONING" defined in the file "menu_macros.txt" is used, which definesthe scope of functions:

Definition of the functions of the context menu for "Cloning" in file "menu_macros.txt"

# global cloning functions

? DOCUMENT_INV_GENERAL_CLONING = fnc.doc.clone.option.NO_ACTION = fnc.doc.clone.option.NEWINTNR_OPTION = fnc.doc.clone.option.NEWEXTNR_OPTION = fnc.doc.clone.option.INSERT_OPTION = fnc.doc.clone.option.REPLACE_OPTION = fnc.doc.clone.option.DELETE_OPTION = fnc.doc.clone.option.NEWVERS_OPTION = fnc.doc.clone.option.CHANGE_OPTION = ----------------------------- = fnc.doc.clone.select.dependent = ----------------------------- = fnc.clpbrd.delete = fnc.doc.reload

The following functions are possible:

Possible functions in the context menu for "Cloning"

Parameter Functionfnc.doc.clone.option.NO_ACTION "No Action"fnc.doc.clone.option.NEWINTNR_OPTION "New internal Number"fnc.doc.clone.option.NEWEXTNR_OPTION "Extended Clon Options"fnc.doc.clone.option.INSERT_OPTION "Add Component"


fnc.doc.clone.option.REPLACE_OPTION "Replace Component"fnc.doc.clone.option.DELETE_OPTION "Delete Component"fnc.doc.clone.option.NEWVERS_OPTION "New Version"fnc.doc.clone.option.CHANGE_OPTION "Change Details"

fnc.doc.clone.select.dependent If this function is set, the menu allows you to select dependentdocuments individually.

fnc.clpbrd.delete "Remove"fnc.doc.reload "Reload"

NOTE:The "cloning" function is universally designed for various CAD systems. Therefore, not everypossible function is necessarily useful for every CAD system and document type. Before adding afunction to the context menu, this should be checked carefully! It can be useful to configuredifferent context menus for different document types.Detailed information on configuring menus can be found in the ECTR manual "OperationsGuide_EN.pdf".

menu_macros.txt

Recurring function sequences in menus and sub-menus are defined as macros in the file "menu_macros.txt."These can then be referenced using their names in the file "menu.guidef."

Structure of a macro definition

Each individual macro definition begins with a question mark at the beginning of the line, followed bythe macro name. This should be typed using capital letters, to designate it as a macro name.The individual menu functions belonging to a macro are arranged one after the other, with each menufunction being preceded by an equal sign ('=').Other macros can also be referenced by name within a macro definition, and names should bepreceded by a question mark ('?'). These macros can either come from this file itself or from thegeneral macro definition file "%PLM_INSTDIR%\customize\config\menu_macros.txt".Sub-menus in the menu are designated by indentation of the associated menu entries, for which onlyblank spaces may be used.Tabs are not allowed!Separators within the menu are represented by a line consisting of dashes ('-').Commentaries can be inserted. These are preceded by a '#' at the beginning of the line.

The defined macros "LAUNCH_APPL_INV" is required, so that the SAP Engineering Control Center can start theInventor application as needed.

The files "attributes-from-sap.xml" and "attributes-to-sap.xml"

For each document type (DType), one can define which attributes are transmitted or stored in which manner.This is also referred to as an attribute mapping. In this process, a distinction is made between the transfer ofattributes from SAP to the document and from the document to SAP. For defining the former, use the file"attributes-from-sap.xml". For defining the latter, use file "attributes-to-sap.xml". Document attributes andmaterial attributes can be passed.


For more information on this topic, see the file "Operations Guide_EN.pdf", chapter: "AttributeTransfer Between the SAP System and an Application", which is part of the ECTR documentation.

Diverse attribute mappings are included in the general configuration files

"%PLM_INSTDIR%\customize\config\attributes-from-sap.xml"

and

"%PLM_INSTDIR%\customize\config\attributes-to-sap.xml".

The following Inventor-specific attribute mapping files exist for this purpose:

"%PLM_INSTDIR%\applications\inv\customize\config\attributes-from-sap.xml"

and

"%PLM_INSTDIR%\applications\inv\customize\config\attributes-to-sap.xml".

These files are described in the chapters "attributes-from-sap.xml" and "attributes-to-sap.xml".

attributes-from-sap.xml

The file "attributes-from-sap.xml" is responsible for defining the transfer of attributes from SAP to thedocument.

Please note:With version 5.1.7 of the ECTR, the inclusion of the standard section will be adapted in the file"attributes-from-sap.xml".Before:<section name="GENERIC" default_section="true" description="Attribute mapping">With ECTR version 5.1.7:<section name="GENERIC" include_section="STANDARD" description="Attribute mapping">The name of the included standard section comes from the global file "attributes-from-sap.xml"file.By changing it to "include_section" it is possible to use any defined "section" and extend it asdesired.

Various sections can be defined in the CAD-specific attribute mapping file"%PLM_INSTDIR%\applications\inv\customize\config\attributes-from-sap.xml", each of which represents anattribute section that contains defined mappable attributes and their precise treatment. The attribute "name"gives the relationship to the DType description in the file "dtype.xml". An attribute section (attribute"attribute_section") can be assigned to each DType for creating (element "document_create") and saving(element "primary_application").


Example for attribute mapping sections in the file "attributes-from-sap.xml"

<mapping> <section name="GENERIC" include_section="STANDARD" description="Attribute mapping"> <APPL_ATTRIBUTE name="Name" hidden="false"> <XFORMAT outputFormat="{0}/{1}"> <CUTLEADING character="0"> <DIR field="DOCUMENTNUMBER"/> </CUTLEADING> <DIR field="DOCUMENTVERSION"/> </XFORMAT> </APPL_ATTRIBUTE> <APPL_ATTRIBUTE name="SAP_DESCRIPTION" hidden="false"> <DIR field="DESCRIPTION"/></APPL_ATTRIBUTE> <APPL_ATTRIBUTE name="SAP_USER" hidden="false"> <DIR field="USERNAME"/></APPL_ATTRIBUTE> <APPL_ATTRIBUTE name="SAP_LASTSAVED" hidden="false"> <DIR field="CHECKIN_DATE"/></APPL_ATTRIBUTE> </section> <section name="STDMOD" description="Attributes for material"> <APPL_ATTRIBUTE name="SAP_MATERIAL_NO" hidden="false"> <MA field="MATERIAL"/></APPL_ATTRIBUTE> <APPL_ATTRIBUTE name="SAP_MATERIAL_DESC" hidden="false"> <MA field="MATL_DESC"/></APPL_ATTRIBUTE> <APPL_ATTRIBUTE name="SAP_MATERIAL" hidden="false"> <MA field="BASIC_MATL_NEW"/></APPL_ATTRIBUTE> <APPL_ATTRIBUTE name="SAP_MATERIAL_WEIGHT" hidden="false"> <MA field="NET_WEIGHT"/></APPL_ATTRIBUTE> </section></mapping>

The element <section> defines a section which represents an attribute segment.

Attribute of element <section>

Attribute Values Description

name="..." Name of attribute division DTypes are referenced to this attribute segment withthis name in the file "dtypes.xml".

include_section="..."Name of section:"STANDARD","STDMOD","default, etc.

Specifies which section is to be included in the sectiondefined here.

description="..." Description of attributesections

This is a comprehensive description of an attributesection.

Within a section, attributes belonging to this attribute section are defined with the sub-element<APPL_ATTRIBUTE>.

Attributes of the sub-element <APPL_ATTRIBUTE>


name="..." Attribute name Name of the property in the document, possible values are listed in chapter"Inventor Properties".

hidden="..." true, false Determines whether this is a helper attribute ("true") or a regular documentattribute ("false").

Within the attribute definition, the subelement <DIR> addresses document attributes, and the subelement<MA> addresses material attributes.


Attributes of subelements <DIR> and <MA>


field="..." Field Name

Name of a field in SAP from which the value for the attribute should be readout.

Only specific SAP fields are allowed here! A list of allowed SAP fields isavailable in the Operations Guide (File "Operations Guide_DE.pdf") in SAPEngineering Control Center.

row="…" Number 0 - x(Optional) There may be a line of SAP long text to be transferred together.The value indicates the row, starting with 0. If the specified line is notpresent, an error message is generated.

language="…" SAP languagecode

Identifier of the language in which the long text is stored in SAP, forexample, "EN" = English, "DE" = German.

It is also possible to modify and combine string values read from SAP.

The subelement <CUTLEADING> deletes, for example, leading characters:

Example for subelement <CUTLEADING>

<CUTLEADING character="0"> <DIR field="DOCUMENTNUMBER"/></CUTLEADING>

If character="0", "000000004711" will be modified to "4711".

The subelement <XFORMAT> combines the values "DOCUMENTNUMBER" and "DOCUMENTTYPE" read outfrom SAP fields into one string:

Example for subelement <XFORMAT>

<XFORMAT outputFormat="{0}/{1}"> <DIR field="DOCUMENTNUMBER"/> <DIR field="DOCUMENTVERSION"/></XFORMAT>

If DOCUMENTNUMBER = "000000004711" and DOCUMENTVERSION = "02", the result is "000000004711/02".

Both subelements can be combined:

Example for combination of subelements <CUTLEADING> and <XFORMAT>

<XFORMAT outputFormat="{0}/{1}"> <CUTLEADING character="0"> <DIR field="DOCUMENTNUMBER"/> </CUTLEADING> <DIR field="DOCUMENTVERSION"/></XFORMAT>

In this case, the result is "4711/02".


Information regarding further possibilities for attribute mapping and construction of file structure"attributes-from-sap.xml" can be found in the help file "Operations Guide_EN.pdf" in the SAPEngineering Control Center, which can be found in folder"%PLM_INSTDIR%\documentation\Manuals\en"

attributes-to-sap.xml

The attribute transfer from the CAD application to the SAP system is defined in the attribute mapping file"%PLM_INSTDIR%\applications\inv\customize\config\attributes-to-sap.xml". Upon saving a CAD document, allattributes will be saved in an XML file in the folder "Additional".

The SAP Engineering Control Center reads the attribute from this file depending on the configurations in theattribute mapping file "attributes-to-sap.xml" and places the values into the SAP system.

For attribute transfer, the sections defined in the file "attributes-to-sap.xml" are used. Here, the name of thesection of the given name in the element <primary_application attribute_section="%Name of section%"...>must agree with a DType definition in the file "dtype.xml". Within this section, attributes to be transferred cannow be defined.

Example for attribute mapping sections in the file "attributes-to-sap.xml"

<mapping> <section name="GENERIC" description="Document attribs from CAD to SAP"include_section="STANDARD"> <DIR field="LONGTEXT" language="EN"> <APPL_ATTRIBUTE name="DESCRIPTION_EN"/> </DIR> </section> <section name="STDMOD" description="Material attribs from CAD to SAP"include_section="STDMOD"> <MA field="MATL_DESC"> <APPL_ATTRIBUTE name="SAP_DESCRIPTION"/> </MA> </section></mapping>

Here too, the element <section> defines a section which represents an attribute section.

Attribute of element <section>


name="..." Name of attribute section DTypes are referenced to this attribute section with thisname in the file "dtype.xml".

include_section="..."Name of the section:"STANDARD","STDMOD","default", etc.

Specifies which section is to be included in the sectiondefined here.

description="..." Description of attributesections

This is a comprehensive description of an attributesection.

Within a section, the subelement <DIR> and the subelement <MA> addresses fields of the document ormaterial, respectively, which can be changed in SAP.

Attributes of subelements <DIR> and <MA>



field="..." Field Name

Name of the document or material field which can be changed in SAP.

ATTENTION:Only specific SAP fields are allowed here! A list of allowed SAP fields isavailable in the Operations Guide (File "Operations Guide_EN.pdf") in SAPEngineering Control Center.

language="…" SAP languagecode

(Optional) If field="LONGTEXT", the identifier of the language will be givenin long text to be stored in SAP. Example "EN" = English, "DE" = German,etc.

Within a section, attributes belonging to this attribute section are defined with the sub-element<APPL_ATTRIBUTE>.


Attribute Values Descriptionname="..." Field Name SAP into which it will be written.

Configuration possibilities for drawings

To configure the creation of drawings, various attributes can be mapped in the "attributes-to-sap.xml" file.

Example of attribute mapping for drawings in the "attributes-to-sap.xml" file

<mapping> <section name="INVMDL" description="Mapping from INVENTOR 3D to SAP"> </section> <section name="INVDRW" description="Mapping from INVENTOR 2D to SAP"> <DIR_CLS transfer_empty_value="false" neutral="true" characteristic="ZDMS_SHEETS"classtype="017" class="ZDMS_CAD_DOC_CLASS"> <APPL_ATTRIBUTE name="DP-Sheets" hidden="false"/> </DIR_CLS> <DIR_CLS transfer_empty_value="false" neutral="true" characteristic="ZDMS_SHEETS"classtype="017" class="ZDMS_CAD_DOC_CLASS"> <APPL_ATTRIBUTE name="DP-Sizes" hidden="false"/> </DIR_CLS> <DIR_CLS transfer_empty_value="false" neutral="true" characteristic="ZDMS_SHEETS"classtype="017" class="ZDMS_CAD_DOC_CLASS"> <APPL_ATTRIBUTE name="DP-SheetSize" hidden="false"/> </DIR_CLS> <DIR_CLS transfer_empty_value="false" neutral="true" characteristic="ZDMS_SHEETS"classtype="017" class="ZDMS_CAD_DOC_CLASS"> <APPL_ATTRIBUTE name="DP-SheetNumber" hidden="false"/> </DIR_CLS> <DIR_CLS transfer_empty_value="false" neutral="true" characteristic="ZDMS_SHEETS"classtype="017" class="ZDMS_CAD_DOC_CLASS"> <APPL_ATTRIBUTE name="DP-ViewScales" hidden="false"/> </DIR_CLS> </section></mapping>

Again, the <section> element defines a section that represents an attribute section. Within the section, thesubelement <DIR_CLS> defines the attribute class.


Attributes of the sub-element <DIR_CLS>


transfer_empty_value="..." true, false Defines whether empty attribute values can betransferred ("true") or not ("false").

neutral="..." true, false Defines whether the neutral attribute value is used("true") or not ("false").

characteristic="..." "ZDMS_SHEETS" Name of the attribute class.classtype="..." "017" SAP class type (here: "017" = document class).class="..." "ZDMS_CAD_DOC_CLASS" Name of the class in which the attribute occurs.

The attribute belonging to this attribute section is defined by the sub-element <APPL_ATTRIBUTE>. The nameof the attribute is defined here and whether the attribute is transferred to the application or is only used as atemporary auxiliary attribute.


Attribute Values Descriptionname="..." Name Name of the attribute.hidden="..." true, false Determines whether this attribute is an auxiliary attribute ("true") or not ("false").

The attributes that can be transferred are listed in the chapter "Inventor Properties".

NOTE:Determining attributes that are not file properties (virtual properties) can have a negative effecton performance. The configuration switch "plm.options.deliverOnlyRequestedAttributesToSAP.INV= true" can be used to specify that only the configured properties are to be read! Thisinfluences the use of properties when creating a document! Please see description of theconfiguration switch!

Mapping of CAD properties to language-dependent description fields for Import on Demand

If the CAD files contain attributes (properties) that contain the description of a part in different languages(short text) and if these CAD file properties are to be mapped to the language-dependent description of thedocument info record (DIS) during Import on Demand (IoD), the mapping must be done using the attribute"_DOCDESCR":

Example for the mapping of short texts in the file "attributes-to-sap.xml"

<mapping> <section name="my_attrib_section" description="mapping during IoD"> <DIR field="SAP_DESCRIPTION" language="DE" > <APPL_ATTRIBUTE name="SAP_DOCTEXT_DE" /> </DIR> <DIR field="SAP_DESCRIPTION" language="EN" > <APPL_ATTRIBUTE name="SAP_DOCTEXT_EN" /> </DIR> <APPL_ATTRIBUTE name="_DOCDESCR" > <APPL_ATTRIBUTE name="SAP_DOCTEXT_EN" /> </APPL_ATTRIBUTE > </section>...</mapping>


Information regarding further possibilities for attribute mapping and construction of file structure"attributes-to-sap.xml" can be found in the help file "Operations Guide_EN.pdf" in the SAPEngineering Control Center, which can be found in folder"%PLM_INSTDIR%\documentation\Manuals\en".

Inventor Properties

General information

The following describes the Inventor properties provided by the SAP Engineering Control Center Interface toInventor. The properties can be used in the files "attributes-to-sap.xml" and "attributes-from-sap.xml" formatching with SAP data.

The properties consist of a prefix and the property name. The prefix indicates the property page in which theproperty is located. This allows you to distinguish between the property "Description" on the property page"Project" and the property page "Custom".

The SAP Engineering Control Center Interface to Inventor also provides virtual property sets that do not exist inInventor, such as the "Drawing Properties" (prefix "DP-"). These cannot be obtained using Inventor's propertysets.

Further information on the individual Inventor properties can also be found in the Inventor API Help:

Inventor help menu

The respective API topics are listed in the following description of the property categories under "API-HelpTopic".

NOTE:Depending on the language package installed in Inventor, the transfer of number values maydiffer in decimal form. Please refer to the file "plm_metainf-cad.xml" in the folder of the respectivedocument in the working directory. This contains the real transferred values.


Property Categories

There are the following categories of properties:

Summary InformationDocument Summary InformationDesign Tracking PropertiesUserdefined PropertiesContent Library Component PropertiesDrawing PropertiesEnvironment PropertiesPhysical PropertiesSheetMetal PropertiesVersion Properties

Overview of Inventor properties

Real Inventor properties

Category: Summary InformationPrefix: SI-API-Help Topic: PropertiesForSummaryInformationEnum Enumerator

Inventor Summary Information Properties

Name ReadOnly User Interface CommentSI-Title Summary Page SI-Subject Summary Page SI-Author Summary Page SI-Keyword Summary Page SI-Comments Summary Page SI-Last Saved By Summary Page SI-Revision Number Summary Page SI-Thumbnail X Project Page Not available

Category: Document Summary InformationPrefix: DSI-API-Help Topic: PropertiesForDocSummaryInformationEnum Enumerator

Inventor Document Summary Information Properties

Name ReadOnly User Interface CommentDSI-Category Summary Page DSI-Company Summary Page DSI-Manager Summary Page

Category: Design Tracking PropertiesPrefix: DTP-API-Help Topic: PropertiesForDesignTrackingPropertiesEnum Enumerator

Inventor Design Tracking Properties


Name ReadOnly User Interface CommentDTP-Appearance X DTP-Authority Project Page DTP-Catalog Web Link Project Page DTP-Categories X XML-StringDTP-Checked By Status Page DTP-Cost Center Project Page DTP-Cost Project Page DTP-Creation Time X Project Page DTP-Date Checked Status Page DTP-Density X DTP-Description Project Page DTP-Designer Project Page

DTP-Design Status Status Page

Numbers will be delivered:'0' = Not set'1' = Work in Progress'2' = Pending'3' = Released

DTP-Display Name Model Tab Display name of documentDTP-Document SubType X CLSID of the documentDTP-Document SubType Name X DTP-Defer Updates DTP-Engineer Project Page DTP-Engr Approved By Status Page DTP-Engr Date Approved Status Page DTP-External Property Revision Id DTP-Flat Pattern Defer Update DTP-Flat Pattern Area X DTP-Flat Pattern Length X DTP-Flat Pattern Width X DTP-Language X language specified in ISO 639-2 alpha-3DTP-Last Updated With X Detail Page DTP-Manufacturer DTP-Mass X DTP-Material X Material Page DTP-Material Identifier X DTP-Mfg Approved By Status Page DTP-Mfg Date Approved Status Page DTP-Parameterized Template X DTP-Part Icon X Not available


DTP-Part Number X Project Page DTP-Part Property Revision Id DTP-Project Project Page DTP-Proxy Refresh Date X DTP-Sheet Metal Area X DTP-Sheet Metal Length X DTP-Sheet Metal Rule X DTP-Sheet Metal Width X DTP-Size Designation DTP-Standard DTP-Standard Revision DTP-Standards Organization DTP-Stock Number Project Page DTP-SurfaceArea X DTP-Template Row X DTP-User Status Status Page DTP-Valid MassProps X Bit flagsDTP-Vendor Status Page DTP-Volume X DTP-Weld Material X

Category: User-defined PropertiesPrefix: None or UDP-API-Help Topic: PropertiesForUserDefinedPropertiesEnum Enumerator

Inventor User-defined Properties

Name ReadOnly User Interface Comment

UDP-[name] Custom Page Property with prefix[name] = User-defined property name

[name] Custom Page Property without prefix[name] = User-defined property name

User-defined properties can be used with or without a prefix. It is recommended that you alwaysuse the prefix (UDP-). If you use the Interop scenario with AutoCAD, this is also mandatory. Toactivate the prefix, the preference "plm.options.updateAttributes.useInteropPrefix.INV" must beset to "true".

Category: Content Library Component PropertiesPrefix: CLCP-API-Help Topic: PropertiesForContentLibraryEnum Enumerator

Inventor Content Library Component Properties

Name ReadOnly User Interface CommentCLCP-Component Type X Not valid


CLCP-Family X CLCP-Family Folder X CLCP-FamilyId X CLCP-Family Revision X CLCP-Family Revision Time X CLCP-Member X Not validCLCP-Member FileName X CLCP-MemberId X CLCP-Member Revision X

Virtual Properties

Category: Drawing PropertiesPrefix: DP-API-Help Topic: Not available

Drawing PropertiesName ReadOnly User Interface Comment

DP-SheetNumber X Number of the active sheet (empty if the active sheet is excluded).DP-Sheets X Number of sheets not excluded from counting.

DP-SheetSize X Size of the active sheet of the drawing as DIN or ISO symbol (e.g. "A2", "A4",etc.).

DP-Sizes X Comma separated list of the different sheet sizes in the drawing as DIN or ISOsymbol (e.g. "A2", "A4" etc.).

DP-Sheet X

Standards of the views on the individual sheets in the following format:DP-Sheet <sheetNumber>-<Viewname>-Scale

ATTENTION:The characters'<' and '>' are special symbols within the XML syntax; thereforethey must be marked here as part of the name! This is done by the usual HTMLmarking:'<' corresponds to "<", '>' corresponds to ">".

Examples:"DP-Sheet <1>-<VIEW1>-Scale" --> "5 : 1""DP-Sheet <1>-<VIEW2>-Scale" --> "1 : 1"

Category: Environment PropertiesPrefix: EP-API-Help Topic: EnvironmentManager Object

Environment Properties

Name ReadOnly User Interface CommentEP-Base Display Name X EP-Base Internal Name X EP-iCopyDefinition X EP-IsSubstitutePart X EP-Override Display Name X EP-Override Internal Name X


EP-Frame Generator X

Possible values (1): • SolveAssemblyDoc • FrameDoc • SkeletonDoc • FrameMemberDoc

EP-Routed Systems: Tube & Pipe X

Possible values (2): • Piping Assembly Environment • Piping Runs Environment • Piping Run Environment • Piping Route Environment • Piping Segment

(1): SolveAssemblyDoc: Assembly containing the Frame Generator Assembly FrameDoc: Frame Generator Assembly SkeletonDoc: Frame Generator Skeleton Part document FrameMemberDoc: Frame Generator Frame Part Document

(2): Piping Assembly Environment: Assembly containing the Tube&Pipe Assembly Piping Runs Environment: Tube&Pipe Assembly Piping Run Environment: Tube&Pipe Run Assembly Piping Route Environment: Tube&Pipe Route Part Piping Segment: Tube&Pipe Pipe Segment

Category: Physical PropertiesPrefix: PP-API-Help Topic: MassProperties Object

Physical Properties

Name ReadOnly User Interface CommentPP-AreaUnit X Physical Page PP-AreaValue X Physical Page PP-CenterOfMassUnit X Physical Page PP-CenterOfMassXValue X Physical Page PP-CenterOfMassYValue X Physical Page PP-CenterOfMassZValue X Physical Page PP-MassUnit X Physical Page PP-MassValue Physical Page PP-PrincipalMomentsOfInertiaI1 X Physical Page PP-PrincipalMomentsOfInertiaI2 X Physical Page PP-PrincipalMomentsOfInertiaI3 X Physical Page PP-RadiusOfGyrationKx X PP-RadiusOfGyrationKy X PP-RadiusOfGyrationKz X PP-RotationToPrincipalRx X Physical Page PP-RotationToPrincipalRy X Physical Page PP-RotationToPrincipalRz X Physical Page PP-VolumeUnit X Physical Page


PP-VolumeValue Physical Page PP-XYZMomentsOfInertiaIxx X Physical Page PP-XYZMomentsOfInertiaIyy X Physical Page PP-XYZMomentsOfInertiaIzz X Physical Page PP-XYZMomentsOfInertiaIxy X Physical Page PP-XYZMomentsOfInertiaIyz X Physical Page PP-XYZMomentsOfInertiaIxz X Physical Page PP-BoundingBoxX X PP-BoundingBoxY X PP-BoundingBoxZ X PP-BoundingBoxUnit X

Category: SheetMetal PropertiesPrefix: SMP-API-Help Topic: SheetMetalComponentDefinition Object

SheetMetal Properties

Name ReadOnly User Interface CommentSMP-BendRadiusUnit X SMP-BendRadiusValue X SMP-BendReliefDepthUnit X SMP-BendReliefDepthValue X SMP-BendReliefWidthUnit X SMP-BendReliefWidthValue X SMP-CornerReliefSizeUnit X SMP-CornerReliefSizeValue X SMP-LengthUnit X SMP-LengthValue X SMP-MinimumRemnantUnit X SMP-MinimumRemnantValue X SMP-Thickness X SMP-ThicknessValue X SMP-WidthUnit X SMP-WidthValue X

Category: Version PropertiesPrefix: VP-API-Help Topic: SoftwareVersionSaved Property

Version Properties

Name ReadOnly User Interface CommentVP-DisplayName X VP-DisplayVersion X


VP-Major X VP-Minor X

VP-ProductEdition X

Possible values: • Inventor LT • Inventor Suite • Inventor Professional • Inventor Routed Systems • Inventor Simulation • Inventor Tooling • Inventor • Inventor Factory Premium • Inventor Factory Ultimate • Inventor OEM

VP-ProductName X VP-ServicePack X

VP-VersionName X Format:Major.Minor SPServicePack

Inventor Properties in the user interface

Inventor Properties can be viewed for a specific document in the "iProperties" dialog in Inventor, or in theProperties dialog of the document file in Windows Explorer. Some subpages are only visible in Inventor orWindows Explorer, others in both dialogs:

Summary Page in Inventor and Windows-Explorer


Project Page in Inventor and Windows-Explorer


Status Page in Inventor and Windows-Explorer

Custom Page in Inventor and Windows-Explorer


Physical Page in Inventor


Details Page in Windows-Explorer

default.txt

The file "default.txt" contains basic settings that influence the interaction between the SAP Engineering ControlCenter, SAP Engineering Control Center to Inventor and the SAP system.

Further explanations as to the purpose of the file and the individual configuration parameters canbe found in the file "default.txt".

ATTENTION:• After all changes of options in the file "default.txt" the ECTR must be restarted!• To be able to use logging with an older ECTR version prior to 5.2 or 5.1.15, the preference"ECTR-LOG-DIR = @PLM_LOGDIR@" must be set here in the file "default.txt"! From ECTR version5.2 or 5.1.15 this is no longer necessary and the preference is then obsolete. Further informationabout this topic can be found in the user manual in the chapter "Logging".

The following pages "Parameter description - Part 1" and "Parameter description - Part 2" contain thedescription of all parameters contained in the "default.txt" file in the delivery state as well as their defaultvalues.

Parameter description - Part 1

The following table contains the first part of the description of all parameters, which are contained in the file"default.txt" in the delivery state.The second part follows on the next page, "Parameter description - Part 2"!


Parameters of the file "default.txt" for Inventor - Part 1Parameter: plm.appl.qat.INV

Description:

The ECTR interface commands can also be added to Inventor's Quick Start Toolbar (QAT) as icons for easier access. But when Inventor is closed,these entries will be removed and will not be in the QAT at the next start. Therefore, the commands which should appear in the QAT can be selectedhere. These are set automatically when Inventor is started from the ECTR.

NOTE:This only works if Inventor is started from the ECTR!

Values:

";"-separated list of command IDs.

The following command IDs are possible:CMD_ABOUT, CMD_BALLOONING, CMD_BOM_POPUP, CMD_DEPDIR_POPUP, CMD_DIRCANCELEDIT, CMD_DIRCHECKIN, CMD_DIRCHECKOUT,CMD_DIRCREATE, CMD_DIRDISPLAY, CMD_DIRIMPORT, CMD_DIRREFRESH_POPUP, CMD_DIRREPLACE, CMD_DIRSAVE, CMD_DIRSAVEAS_POPUP,CMD_DIRSEARCH, CMD_ECTR, CMD_EXTRAS_POPUP, CMD_OBJECTLISTSET, CMD_SHOW_STRUCTURE_VIEW

Default value: --Parameter: plm.appl.startViewerCommand.INV

Description:

Necessary preference for viewing Inventor files with Inventor Read-Only.

HINTS:• Requires Inventor 2020 or above!• This only works if Inventor has been started manually at least once before in ReadOnly mode!

Values: Command line to execute "start_application_inv.exe".Default value: @PLM_BINDIR_INV@\\start_application_inv.exe -View $(filename)

Parameter: plm.options.ReadOnly.DisabledCommandTypes.INVDescription: Command types can be deactivated for read-only opened documents.

Values:

";"-separated list of command types.Possible values are:ShapeEdit, QueryOnly, FileOperations, FilePropertyEdit, UpdateWithReferences, NonShapeEdit, ReferencesChange, EditMask, SchemaChange.

NOTE:For more information on the command types, please refer to the Inventor API documentation!

Default value: --Parameter: plm.options.ReadOnly.DisabledCommandList.INV

Description:

For read-only opened documents, individual Inventor commands can be deactivated.

NOTE:For more information on the internal names of Inventor commands, please refer to the Inventor API documentation!

Values: ";"-separated list of internal names of commands.Default value: --

Parameter: plm.options.DisableDirtyHandlingForWritingComponentIDs.INVDescription: Determines whether the default handling for documents marked as dirty should be disabled when writing component IDs.

Values:'0' = Dirty handling will be active for writing component IDs'1' = Dirty handling will be disabled for writing component IDs'2' = Component IDs will not be written for read only documents

Default value: 0Parameter: plm.options.checkIn.UpdateAttributesFromSAP.INVDescription: During Save, update attributes of documents to check in from SAP before transferring them to SAP.

Values: "true" = Update attributes before save"false" = Do not update attributes beforehand

Default value: falseParameter: plm.options.OpenInsert.UseLastActiveLevelOfDetail.INV

Description:

Decides whether the "Master" level or the active level of detail when checking in to SAP should be used when opening a model via the ECTR.

HINTS:• This setting is also used when opening via the "Open" dialog.• The same values can be used here as for the parameter plm.options.OpenInsert.ViewRepresentation.INV.

Values:'0', "true" = Use last active level of detail'1', "false" = Use "Master" detail level'2' = Use inventor defined setting

Default value: 0Parameter: plm.options.OpenInsert.ViewRepresentation.INV

Description:

Decides whether the "Master" design view or the active design view when checking in to SAP should be used when opening an assembly via theECTR.

HINTS:• This setting is also used when opening via the "Open" dialog.• The same values can be used here as for the parameter plm.options.OpenInsert.UseLastActiveLevelOfDetail.INV.

Values:'0' = Use last active design view'1' = Use "Master" design view'2' = Use inventor defined setting


Default value: 0Parameter: plm.options.DeferUpdateOnCheckin.INVDescription: Automatically defer updates of drawings during check in.

Values: "true" = Defer updates during check in"false" = Do not defer updates during check in

Default value: falseParameter: plm.control.popwin.name.INV

Description: Name (caption text), which the main window of the workstation application identifies to bring it to the foreground. The wild card '*' can be used tooutput a substring.

Values: Name of main window of the workstation application and substring, which is a component of the window name (driven by the wild card '*').Default value: *Inventor*

Parameter: plm.control.waitForSessionInMs.INVDescription: Defines the time until the application starts and the communication via interface will be established.

Values: Time in ms.Default value: 15000

Parameter: plm.structure.application.CollectEntries.INVDescription: Determines whether multiple built-up components in the structure overview of the ECTR will be displayed individually or summarily.

Values: "collectNone" = No summary. Every instance will be shown individually"collectAll" = Summarize all instances. Only depict and summarize a node with the total

Default value: collectNoneParameter: plm.structure.application.sendInstancesForGeneric.INVDescription: Determines whether CAD Integration should send all known instances for generics or not.

Values: "true" = CAD Integration should send all known instances for generics"false" = CAD Integration must not send instances

Default value: trueParameter: plm.structure.application.DisplayPosItem.INVDescription: Determines whether virtual components should be shown in structure tree.

Values: "true" = Show virtual components under the corresponding node in the tree"false" = Do not show virtual components in the tree

Default value: trueParameter: plm.structure.application.init.strategy.levels.INVDescription: Number of levels which should be submitted to application structure.

Values: <Number> 1-n = Number of levels"all" = Complete structure

Default value: 1Parameter: plm.structure.application.DisplayExternalReferences.INVDescription: Determines whether external references (i.e. images, parameter files, etc.) are to be displayed in the application structure.

Values: "true" = Display external references"false" = Do not display external references

Default value: falseParameter: plm.structure.application.DisplaySuppressedComponents.INVDescription: Determines whether suppressed components are to be displayed in the application structure.

Values: "true" = Display suppressed components"false" = Do not display suppressed components

Default value: falseParameter: plm.structure.application.show.drawing.INV

Description:

Specifies whether referenced drawings are to be displayed in the ECTR application structure.

NOTE:This parameter replaces the parameter "plm.structure.application.loadDrawings.INV" which was removed because it is obsolete!

Values: "true" = Show drawings"false" = Do not display drawings

Default value: falseParameter: plm.structure.application.show.drawing.container.INVDescription: Specifies whether referenced drawings in the ECTR application structure are to be displayed in a separate folder within the structure.

Values: "true" = Display referenced drawings from the session directory in a separate folder"false" = Added referenced drawings from the session directory below the document node

Default value: falseParameter: plm.structure.application.show.drawing.container.ontop.INVDescription: Determines at which position referenced drawings in the ECTR application structure should be displayed within the structure.

Values: "true" = The container with the referenced drawing will be shown above the subcomponents"false" = The container with the referenced drawing will be shown below the subcomponents

Default value: falseParameter: plm.structure.application.DisplayAdditionalAttributes.INV


Description:

Determines whether additional file properties should be displayed in the application structure.

NOTE:This parameter is optional.

Values: "true" = Show additional file properties"false" = Do not show additional file properties

Default value: falseParameter: plm.structure.application.ExpandDocumentsOnlyOnce.INV

Description:

Determines whether the first occurrence of a document node in the application structure should be expanded.Other occurrences of this document would then not be expanded automatically.


Values: "true" = Expand the same document only once"false" = Expand each occurrence of the same document

Default value: falseParameter: plm.structure.application.displaysubstitutestructure.INV

Description:

Determines whether the substructure of Substitutes should be displayed.


Values: "true" = Display the substructure of Substitutes"false" = Do not show the substructure of Substitutes

Default value: trueParameter: plm.structure.application.AdditionalAttributes.INV

Description:

Defines which file properties should be displayed in the application structure.

NOTES:• This parameter is optional.• Component properties can be used to overwrite the file property value.

Values: List of file properties to display, separated by semicolon.Example: Prop1;Prop2;Display Name;SAP_CC_NAME

Default value: --

Parameters:

plm.bom.create.IDWplm.bom.createAtCheckin.IDW plm.bom.updateAtCheckin.IDWplm.bom.update.IDWplm.bom.create.IPNplm.bom.createAtCheckin.IPNplm.bom.updateAtCheckin.IPNplm.bom.update.IPNplm.bom.create.IAMplm.bom.createAtCheckin.IAMplm.bom.updateAtCheckin.IAMplm.bom.create.IPTplm.bom.createAtCheckin.IPTplm.bom.updateAtCheckin.IPTplm.bom.update.IPTplm.bom.create.INMplm.bom.createAtCheckin.INMplm.bom.updateAtCheckin.INMplm.bom.update.INM

Description: Defines to which time frame and for which document type a bill of materials should be created or an existing bill of materials should be updated.

Values: "true" = carry out action"false" = do not carry out action

Default value: false (for all above-mentioned parameters)Parameter: plm.document.ExcelAsAdditionalFile.INVDescription: Indicates whether an Excel file (Excel parameter file) should be created as an additional file or as a separate DIR.

Values: "true" = Create Excel file as additional file"false" = Create Excel file as separate DIR

Default value: trueParameter: plm.document.PictureAsAdditionalFile.INVDescription: Indicates whether an image file should be created as an additional file packed inside ecf or as a separate DIR.

Values: "true" = Create image file as additional file"false" = Create image file as separate DIR

Default value: trueParameter: plm.docstructure.deleteBeforeMaintain

Description:

Indicates whether the document structure will be reset before maintain.

ATTENTION:This is a global setting which applies to all applications! For Inventor, this must be set to "true"!


Values: "true" = Reset document structure before maintain"false" = Do not reset document structure

Default value: trueParameter: plm.ignore.dtype.use.relative.path.flag

Description:

Use or ignore "relative path" flag so cloning is possible for this dtypes if ignored.

ATTENTION:This is a global setting which applies to all applications!

Values: "true" = Use "relative path" flag"false" = Ignore "relative path" flag

Default value: trueParameter: plm.adv.clone.renamerProgram.INVDescription: Defines the path to the program "renamer3inv.exe", which is accountable for cloning.

Values: Path to the program "renamer3inv.exe".Default value: @PLM_BINDIR_INV@\\renamer3inv.exe

Parameter: plm.document.SaveAsNewDocument.CheckOutTop.INVDescription: Determines whether the "Save as new document" and "Save as new version" functions should automatically check out the superior open document.

Values:'0' = do not check out'1' = check out'2' = check out and save (intermediate)

Default value: 1Parameter: plm.options.SaveAsNewDocument.Replace.INVDescription: Defines the method for replacing references in the "Save as new document" function.

Values:

'0' = Replace in all open views without a warning dialog'1' = Replace only in active view without a warning dialog'2' = Replace in all open views after displaying a warning dialog'3' = Replace only in active view with a warning dialog'4' = Do not replace references'5' = Replace only in copied drawings

Default value: 0Parameter: plm.control.applType.WsAppl.INVDescription: The primary application ("WsAppl") of Inventor.

Values: The shortcut for the workstation application of Inventor.Default value: INV

Parameters:

plm.control.extension.WsAppl.iptplm.control.extension.WsAppl.iamplm.control.extension.WsAppl.ipnplm.control.extension.WsAppl.idwplm.control.extension.WsAppl.ide

Description: Every document type of application must be assigned a workstation application. If this is missing here, the current file extension will be used as aworkstation application.

Values: Abbreviation of the workstation application.Default value: INV

Parameters:

plm.document.dtype.iPartMember.INV = IPTNRplm.document.dtype.iPartFactory.INV = IPTplm.document.dtype.iAssemblyMember.INV = IAMNRplm.document.dtype.iAssemblyFactory.INV = IAMNRplm.document.dtype.ContentMember.INV = IPTCCplm.document.dtype.SheetMetal.INV = IPTSMplm.document.dtype.Weldment.INV = IAMWMplm.document.dtype.Mold.INV = IAMMOplm.document.dtype.FrameGenerator.Assembly.INV = IAMplm.document.dtype.FrameGenerator.Sketch.INV = IPTplm.document.dtype.FrameGenerator.Member.INV = IPTplm.document.dtype.FactoryDesign.Asset.IPT.INV = IPTNRplm.document.dtype.FactoryDesign.Asset.IAM.INV = IAMNRplm.document.dtype.FactoryDesign.LayoutTemplate.INV = IAMplm.document.dtype.AIP.IPT.INV = IPTplm.document.dtype.AIP.IAM.INV = IAMplm.document.dtype.<LibName>.<type>.INV = <DTYPE>

Description:

Optional assignment of DTypes to individual Inventor document types.Special DTypes can be assigned for individual libraries. The <LibName> and <type> - IAM / IPT must be specified.If these DTypes are preconfigured here, they cannot be changed by the user!

IMPORTANT:• When using mold assemblies, note the notes under "Creating mold assemblies with "ECTR New""!• For iPartMember, iAssemblyMember, iAssemblyFactory, ContentMember it is imperative that the DType attribute "rename_template_filename" in"document_create" is set to "false"!

Values: Identifiers of assigned DType as defined in file "dtypes.xml".Default value: See under Parameters


Parameters:plm.document.dtype.Default.IPT.INV = IPTplm.document.dtype.Default.IAM.INV = IAMplm.document.dtype.Default.IDW.INV = IDWplm.document.dtype.Default.IPN.INV = IPN

Description: Defines default dtype assignments.

Values:

Identifiers of assigned DType as defined in "dtypes.xml".

ATTENTION:"IPT", "IAM", "IDW" and "IPN" are not the SAP document types!

Default value: See under ParametersParameter: plm.document.createMulti.cad.dtype.searchAlso.INVDescription: Specifies non Inventor DTypes that should be considered for import.

Values: A list of DTypes, separated by ';'Default value: CPA;PICP;PICG;PICT;PICJ

Parameter: plm.document.genericDTypes.INVDescription: Assignment of a DType to a generic type.

Values: A list of identifiers of assigned DType as defined in "dtypes.xml", separated by ';'.Default value: IPTNR;IAMNR;IPT

Parameters:plm.document.variantDType.IPTNR = IPTNRplm.document.variantDType.IAMNR = IAMNRplm.document.variantDType.IPT = IPTNR

Description: Assignment of variant DTypes to a generic types.Values: Identifiers of assigned DType as defined in file "dtypes.xml".

Default value: See under ParametersParameter: plm.options.importOnDemand.TransferAttributesToSAP.INVDescription: Specifies whether the CAD attributes should be updated during import (ImportOnDemand function) or not.

Values: "true" = update"false" = no update

Default value: trueParameter: plm.options.StructureAnalysis.MinimumErrorLevel.INVDescription: Defines the minimum error level for problems to be displayed in the error dialog box during structural analysis.

Values:'0' = Never show error dialog (not recommended!)'1' = Show error dialog only if errors found'2' = Show error dialog if errors or warnings found'3' = Always show dialog

Default value: 3Parameter: plm.options.importOnDemand.loadDrawings.INVDescription: Specifies whether drawings should be loaded during import (ImportOnDemand function) or not.

Values: "true" = Load drawings"false" = Do not load drawings

Default value: falseParameter: plm.options.importOnDemand.resetOccurrenceName.INVDescription: Determines whether overwritten names of individual occurrences in the imported structure are to be reset to the component name.

Values:"0" = Do not reset occurrence names"1" = Reset all occurrence names"2" = Only reset occurrence names of new imported occurrences

Default value: 1Parameter: plm.options.save.loadDrawings.INVDescription: Defines whether drawings should be loaded on save or not.

Values: "true" = Load drawings"false" = Do not load drawings

Default value: falseParameter: plm.options.openAllReferencesToReadInstanceIDs.INVDescription: Specifies whether all references in a document are to be opened to compare the instance IDs with SAP.

Values: "true" = Open all references"false" = Do not open all references

Default value: falseParameter: plm.options.Open.CopyFeaFiles.INVDescription: Use internal interface logic or script to copy stress analysis files from the Additional directory to the FEM directory when opened.

Values: "true" = Copy files"false" = Do not copy files

Default value: falseParameter: plm.options.deliverOnlyRequestedAttributesToSAP.INVDescription: Deliver only requested or all available attributes to SAP.

Values: "true" = Deliver only requested attributes"false" = Deliver all attributes


Default value: trueParameter: plm.options.updateAttributes.useInteropPrefix.INVDescription: Specifies whether to use the prefix "UDP-" for user-defined properties for the interop scenario with AutoCAD.

Values: "true" = Use prefix "UDP-""false" = Do not use prefix "UDP-"

Default value: falseParameter: plm.options.createDIRForNewDocument.INVDescription: Determines how the interface should react when the user calls the CAD function "New".

Values:'0' = A new unmanaged file is created and opened with the CAD function'1' = A new file is created and opened in SAP'2' = The user is asked each time whether he wants to create and open a file via SAP or locally

Default value: 2Parameter: plm.options.SapOpenForCadOpenDocument.INVDescription: Determines how the interface should react when the user calls the CAD function "Open".

Values:'0' = Open file with CAD standard function'1' = One or more files can be opened from SAP'2' = The user is asked each time whether he wants to open from SAP or locally

Default value: 2Parameter: plm.options.SapOpenForCadPlaceDocument.INVDescription: Indicates which "Place Document" dialog should be used..

Values:'0' = use the Inventor standard dialog'1' = use the ECTR dialog'2' = ask the user

Default value: 2Parameter: plm.options.SapOpenForLoadDrawing.INVDescription: Indicates which dialog will be used for loading document from SAP when load a drawing.

Values:'0' = use the Inventor standard dialog'1' = use the ECTR dialog'2' = ask the user

Default value: 2Parameter: plm.options.SapSaveAsNewDocumentForCadSaveAs.INVDescription: Specifies whether it is possible to save as a new document in SAP during the execution of the Inventor function "Save As".

Values:'0' = Do not save as a new document in SAP'1' = Always save as a new document in SAP'2' = The user is asked each time whether to save as a new document in SAP

Default value: 0Parameter: plm.options.SapSaveAsNewDocumentForCadSaveCopyAs.INVDescription: Specifies whether a save as a copy can be performed in SAP during the execution of the Inventor function "Save copy as".

Values:'0' = Do not save as copy in SAP'1' = Always save as copy in SAP'2' = The user is asked each time whether to save as a copy in SAP

Default value: 0Parameter: plm.options.SaveAsNewDocument.SubstitutePartHandling.INVDescription: Selects the procedure for handling Substitute Level Of Detail (LOD) parts in assemblies in SaveAsNewDocument.

Values'0' = Keep as is'1' = Delete substitute LOD'2' = Copy substitute LOD

Default value: 0Parameter: plm.options.open.UseMultiSearchForSapOpen.INV

Description: Choose which ECTR open dialog should be used when opening a document from SAP. Enabling this option will let you open multiple documents atonce. Otherwise, the single search dialog will be used, which allows exactly one document to be opened.

Values: "true" = Use multi search dialog"false" = Use single search dialog

Default value: falseParameter: plm.options.OpenInsert.ShowLoadOptionsDialog.INVDescription: Defines whether the dialog "File Open Options" should be displayed when opening or inserting files from ECTR.

Values: "true" = Show dialog"false" = Do not show dialog

Default value: trueParameter: plm.options.EmbedExcelOnInsert.INVDescription: Defines if Excel files loaded from SAP should be embedded or not.

Values:'0' = Do not embed'1' = Embed'2' = ask the user

Default value: 0Parameter: plm.document.addcomponent.allowed.dTypeList.INV


Description:

Determines which DTypes are available when inserting.

ATTENTION:If this preference is set, the preference plm.document.addComponent.notAllowed.documentTypeList is ignored.

Values: List of DTypes, separated by ';'.Default value: IPTML;IAMLT;SWPRT;ACAD

Parameter: plm.options.Ballooning.BalloonContent.INVDescription: Sets the content of balloons.

Values:'0' = Material and SAP balloon content'1' = Material number'2' = BOM item number'3' = SAP balloon content

Default value: 2Parameter: plm.options.Ballooning.BalloonContent.Override.INVDescription: Balloon content value.

Values: "true" = Set override value"false" = Set value (partslist)

Default value: trueParameter: plm.options.Ballooning.InitializeBalloonWith.INVDescription: Initialization of balloons with the specified string for balloons that could not be supplied with data from SAP.

Values: String for initialization.Default value: "--"

Parameter: plm.options.MissingReferenceReloadOption.INVDescription: Define behavior if CAD notices a missing component file when loading an assembly.

Values:'0' = Use CAD behavior'1' = Load component from SAP automatically'2' = Ask user for loading the missing component from SAP

Default value: 0Parameter: plm.options.checkForUpdates.before.CheckoutEdit.MultiLevel.INV

Description: Determines whether the complete structure or only the directly referenced documents should be checked using CheckForUpdates before aCheckoutEdit action.

Values: "true" = The complete structure will be checked"false" = Only the directly referenced documents are checked

Default value: trueParameter: plm.options.checkForUpdates.before.CheckoutEdit.ExplosionScenario.INVDescription: When using the MultiLevel-CheckForUpdate, this preference can be used to specify a explosion scenario that can be customized using CDESK_CUS.

Values: Explosion scenario according to the values possible in CDESK_CUS.Default value: CAD_LOAD

Parameter: plm.loadoptions.versionConflictResolveMode.INV

Description:

Resolves version conflicts when multiple versions of the same DIR are required.Use this parameter when the filename includes version numbers and the load option "As last saved" is being used.

NOTE:This parameter Is commented out by default!

Values:"highest_in_structure" = Only highest versions are loaded"all" = Always load all versions for all documents"auto" = Load only necessary versions

Default value: --Parameter: plm.options.ContentCenterPrimaryLanguage.INV

Description:

Sets the primary language of the content center library.

NOTES:• If no value configured, there will be no restriction on generating new content center parts.• This parameter Is commented out by default!

Values: Language ID (e.g. "en-us")Default value: --

Parameter: plm.options.ChangeDtype.INV

Description:

Allows you to change a DType when checking in. This only changes the DType in the database and no further checks are performed.

Parameter construction:plm. options. ChangeDtype. INV.[OLD_DTYPE] = <List of new document categories>

Example: "plm.options.ChangeDtype.INV.IPT = IPTSM"

ATTENTION:• Use this option with extreme caution!• The use of this option is at your own risk!• Do not use this option to switch to generic DTypes!

Values: List of DTypes, separated by ';'.


Default value: --Parameter: plm.options.TemplateProject.INV

Description:

Here, it is possible to specify the path to a project file, which is used as a template for the ECTR project file. The directories for "Working directory"and "Template directory" are adapted to the current settings in the ECTR at runtime.

IMPORTANT:The path has to be written with '\\', e.g.: "C:\\Templates\\InventorTmp.ipj"!

Values: Template file name with path.Default value: --

Parameter: plm.options.TemplateFiles.INV

Description:

Path to Inventor templates that should be used in the ECTR Inventor project file

IMPORTANT:The path has to be written with '\\', e.g.: "@PLM_INSTDIR_CONF@\\applications\\inv\\templates\\2019"!

Value: Path to Inventor templatesDefault value: @PLM_INSTDIR_CONF@\\applications\\inv\\templates\\2019

Parameter description - Part 2

The following table contains the second part of the description of all parameters contained in the "default.txt"file in the delivery state.The first part is included on the previous page "Parameter description - Part 1"!

Parameters of the file "default.txt" for Inventor - Part 2Parameter: plm.options.Thumbnail.ViewOrientation.INVDescription: Defines the view orientation for generating thumbnail images.

Values:

'0' = Top'1' = Right'2' = Back'3' = Bottom'4' = Left'5' = Front'6' = IsoTopRight'7' = IsoTopLeft'8' = IsoBottomRight'9' = IsoBottomLeft'11' = Current

Default value: 6Parameter: plm.options.Thumbnail.Size.INVDescription: Sets the size of thumbnails for the ECTR preview.

Value: Size of the thumbnails in pixels. Applies to height and width.Default value: 180

Parameter: plm.options.Thumbnail.INV.jpg.<preference>


Description:

It is possible to configure the creation of thumbnails.

ATTENTION:Currently, only the JPEG format "jpg" is allowed!

Several settings are possible for the selected file format. These are selected via <preference>.

Possible options for <preference> are:

1.) "size": This is the resolution (height and width) used for the preview image. If "size" is not set, the value of the parameter"plm.options.Thumbnail.Size.INV" is used.

Example:plm.options.Thumbnail.INV.jpg.size = 180

2.) "fileformat": Specifies a rule how the file name of the thumbnail file is to be formed. There are different placeholders (tokens) available, whichare replaced by corresponding values:$(DOCNUMBER)$(DOCTYPE)$(DOCVERSION)$(DOCPART)$(ORIGINALFILENAME)$(ORIGINALEXTENSION)

Example:plm.options.Thumbnail.INV.jpg.fileformat = $(ORIGINALFILENAME).preview

IMPORTANT:If the file name is configured in such a way that the ".preview" extension is no longer contained or otherwise named, the "filename_pattern"parameter in the "<save_direct>" and "<delete_in_session>" areas of the configuration file "dtype.xml" must be adjusted.Furthermore, it should be noted that without ".preview" for the preview image (with corresponding adjustment in configuration file "dtype.xml"),problems can occur if linked JPG files are used in the constructions, since no distinction between preview image and linked image is made here.

NOTE:If the preference is not set, the preview image will be created as "$(ORIGINALFILENAME).preview.jpg".

3.) "keepExtension": Determines whether the token "$(ORIGINALFILENAME)" keeps the extension of the master original or whether it is removed.

Possible values are:"true" = The extension of the master original remains unchanged"false" = The extension of the master original will be removed

Example:plm.options.Thumbnail.INV.jpg.keepExtension = true

Values: See under Description!

Default value:plm.options.Thumbnail.INV.jpg.fileformat = $(ORIGINALFILENAME).previewplm.options.Thumbnail.INV.jpg.keepExtension = trueplm.options.Thumbnail.INV.jpg.size = 180

Parameter: plm.document.variantKeepVersion.INVDescription: Decided whether generic factories should keep member when versioned or not.

Values: "true" = Keep member"false" = Don't keep member

Default value: trueParameter: plm.options.MakeComponents.TargetAssemblyHandling.INVDescription: Determines how a new DIR can be created for the target assembly during make components.

Values: "0" = A dialog will prompt whether to create a new DIR"1" = The target assembly has to be named "SAP_GENERATED_NAME.iam" to create a new DIR for it.

Default value: 0Parameter: plm.options.MakeComponents.AttributesToCopy.INV

Description:

Decided which document attributes will be copied from the source part to the new created documents during function "MakeComponents".

IMPORTANT:Only custom properties are supported!

Values: A list of custom property names, separated by ';'.Default value: --

Parameter: plm.options.MakeComponents.CreateDark.INV

Description:

Determines whether the function "Make Components" should be executed in dark, or whether the ECTR import dialog for external numberassignment should be displayed.

NOTE:If documents are created dark with "Make Components", they each automatically receive their own DIR. Using the ECTR import dialog, the numberassignment can be done externally, that means manually.

Values: "true" = Create dark"false" = ECTR import dialog will be shown

Default value: trueParameter: plm.options.UpdateAttributes.UpdateReadOnly.INVDescription: Refresh attributes on ReadOnly documents in structure.


Values: "true" = Attributes of ReadOnly documents will be refreshed"false" = Don't refresh attributes of ReadOnly documents

Default value: trueParameter: plm.options.UpdateAttributes.RefreshContext.INVDescription: Specify which documents will be effected during attribute refresh.

Values:'0' = Refresh the complete structure'1' = Refresh only the selected / top document'2' = Ask user

Default value: 0

Parameters:

plm.om.DOC.containers.IPT =MASTERMODEL;OLINKS;FAMILY_TEMPLATE;FAM_MEMBER;VERSIONS;SOURCEDOC;ORIGINALS;COMPS;SMART_CONT(MACRO_INV_IPN);SMART_CONT(MACRO_INV_IDW);WLINKS; WHEREUSED;CLASSESplm.om.DOC.containers.IAM = MASTERMODEL;OLINKS;FAMILY_TEMPLATE;FAM_MEMBER;VERSIONS;SOURCEDOC;ORIGINALS;COMPS;SMART_CONT(MACRO_INV_IPN);SMART_CONT(MACRO_INV_IDW); WLINKS;WHEREUSED;CLASSESplm.om.DOC.containers.IPN = MASTERMODEL;OLINKS;VERSIONS;SOURCEDOC;ORIGINALS;COMPS;SMART_CONT(MACRO_INV_IDW);WLINKS;WHEREUSED;CLASSESplm.om.DOC.containers.IDW = MASTERMODEL;OLINKS;VERSIONS;SOURCEDOC;ORIGINALS;COMPS;SMART_CONT(MACRO_INV_IDW);WLINKS;WHEREUSED;CLASSES

Description: Assignment of containers to document types.Values: List of containers, separated by ';'.

Default value: See under Parameters.

Parameters:

plm.smart.container.MACRO_INV_IDW.name = Drawings for Documentplm.smart.container.MACRO_INV_IDW.functionGroup = MACRO_INV_IDWplm.smart.container.MACRO_INV_IDW.macro = INV:inv_idw.txtplm.smart.container.MACRO_INV_IDW.icon = tree/inv/file_inv_drawingplm.smart.container.MACRO_INV_IPN.name = Drawings for Documentplm.smart.container.MACRO_INV_IPN.functionGroup = MACRO_INV_IPNplm.smart.container.MACRO_INV_IPN.macro = INV:inv_ipn.txtplm.smart.container.MACRO_INV_IPN.icon = tree/inv/file_inv_presentation

Description: Defines smart container macros.Values: For every macro, a plain text name, a function group, the macro to be performed, and an icon are given.

Default value: See under Parameters.Parameter: plm.execute.additional.INV


Description:

You can execute additional functions before or after a particular PLM process by starting either an executable file (external tool), a CAD macro(Internal VBA), or the PowerShell.

The following values are possible:

1.) Specifies the document type for execution ("DOKAR" field) and the time of execution:plm.execute.additional.INV.<DOCTYPE>.<EXEC TIME>

Possible options for <EXEC TIME> are:• "BeforeCheckIn": Execution before check in• "AfterCheckOut": Execution after checkout• "AfterBallooning": Execution after ballooning

Example:plm.execute.additional.ACD.ACD.BeforeCheckIn

2.) Specifies the type of function to be executed:plm.execute.additional.INV.<DOCTYPE>.<EXEC TIME>.type = [EXEC TYPE]

Possible options are:• "Executable": External tool• "CADMacro": CAD macro (internal VBA)• "Powershell": Starts the Windows PowerShell

Example:plm.execute.additional.INV.IAM.BeforeCheckIn.type = Executable

NOTE:A macro must return a value of '0' otherwise the current operation will fail!

3.) Specifies the name of the external program, macro or command:plm.execute.additional.INV.<DOCTYPE>.<EXEC TIME>.commandLine = [CMDLINE]

Examples:plm.execute.additional.INV.IAM.BeforeCheckIn.commandLine = D:\\test.batplm.execute.additional.INV.IAM.AfterCheckOut.commandLine = D:\\Tools\\ExtractFormat64.exeplm.execute.additional.INV.IPT.AfterBallooning.commandLine = Module1.DoSomething

NOTES:• Executable files need a valid file path with double (escaped) backslashes!• VBA macros must always be specified in the form [Macro Module].[Macro Function]!

4.) Specifies the number of parameters to pass:plm.execute.additional.ACD.<DOCTYPE>.<EXEC TIME>.NumberParam = [PARAMCOUNT]

Example:plm.execute.additional.INV.IPT.AfterBallooning.numberParam = 1

4.) Specifies the parameters to be transferred:plm.execute.additional.ACD.<DOCTYPE>.<EXEC TIME>.parameterN = [PARAM]

The placeholder 'N' stands for the parameter number. The parameter number also determines the sequence in which the parameters aretransferred!

Example:plm.execute.additional.ACD.ACD.BeforeCheckIn.parameter1 = $(FILENAME)plm.execute.additional.ACD.ACD.BeforeCheckIn.parameter2 = Test-User

Values: See under Description.Default value: ---

Parameter: plm.convert.additional.INVDescription: Defines the Inventor document types to which additional formats can be assigned.

Values: List of document types, separated by ';'.Default value: IPT;IAM;IDW


Parameters:

General parameter construction:plm.convert.additional.INV.<DOCTYPE1> = <CONVERT TYPE1>;<CONVERT TYPE2>plm.convert.additional.INV.<DOCTYPE1>.<CONVERT TYPE1>.extension = <destination extension>plm.convert.additional.INV.<CONVERT TYPE1>.options = <OPTION1>:<OPTION2>;<OPTION3>plm.convert.additional.INV.<DOCTYPE1>.<CONVERT TYPE1>.<OPTION1> = <VALUE>

Additional files formats for documenttypes:plm.convert.additional.INV.IPT = JT;FlatPatternDXFplm.convert.additional.INV.IAM = JTplm.convert.additional.INV.IDW = PDF plm.convert.additional.INV.DWG = PDF

Convert options:plm.convert.additional.INV.FlatPatternDXF.options = AcadVersionplm.convert.additional.INV.JT.options = Version;FileStructure

JT options for "IPT":plm.convert.additional.INV.IPT.JT.Version = 80plm.convert.additional.INV.IPT.JT.FileStructure = 0

JT options for "IAM":plm.convert.additional.INV.IAM.JT.Version = 80plm.convert.additional.INV.IAM.JT.FileStructure = 0

FlatPatternDXF options for "IPT":plm.convert.additional.INV.IPT.FlatPatternDXF.AcadVersion = 2004

Description: Defines the characteristics for the additional formats assigned to individual Inventor document types (convert type).

Values:

The individual additional formats will be assigned options which, in turn, are each assigned specific values (general parameter construction can befound under Parameters). Allowed formats for SheetMetal FlatPattern are: "FlatPatternDXF", "FlatPatternDWG" and "FlatPatternSAT".

IMPORTANT:• Enumeration values in the options must be specified numerically, the name is not accepted! Example PDF export, enumerator'PrintRangeEnum': The name of the value is 'kPrintAllSheets' and has the value '14082'. Therefore: plm.convert.additional.INV.PDF.PrintRangeEnum= 14082.The values of all enumerations can be found in the AutoDesk manual "Inventor API Reference Manual"!• More information about the possible options can be found in the AutoDesk Inventor documentation!

Default value: See under Parameters.Parameter: plm.convert.additional.INV.<CONVERT_TYPE>.filenameFormat

Description:

The names for neutral formats can be configured. The following placeholders are available, which are replaced by the corresponding SAP values:• "$ (DOCNUMBER)" : SAP name• "$ (DOCTYPE)" : Document category• "$ (DOCVERSION)" : Document version• "$ (DOCPART)" : Document section

Value: String that can contain the allowed placeholders.Default value: Number.$(DOCNUMBER)_Type.$(DOCTYPE)_Version.$(DOCVERSION)_Part.$(DOCPART)

Parameter: plm.convert.additional.INV.<CONVERT_TYPE>.keepExtension

Description:

The option "keepExtension" is available for all additional file formats and determines whether the file name extension of the CAD file is transferredto the file name of the additional format file.

NOTE:If this option is not defined, "true" is assumed automatically!

Value: "true" = The file name is formed from the CAD file name with its extension."false" = The file name is formed from the CAD file name without its extension.

Default value: true (or not existing!)Parameter: plm.convert.additional.FamilyMembers.INVDescription: Determines whether to create additional formats for family members.

Values: "true" = Create additional formats."false" = Do not create additional formats.

Default value: trueParameter: structure.view.INV.generic.object.type

Description:

Specifies the key name of property for different object types.

NOTE:Will be read from node attributes as follows:POS_TYPE = [INV_MATERIAL_NEW | INV_MATERIAL | INV_VIRTUAL_NEW | INV_VIRTUAL]

Values: Key name of property.Default value: POS_TYPE

Parameters:structure.view.INV.generic.object.INV_MATERIAL_NEW.namestructure.view.INV.generic.object.INV_MATERIAL.namestructure.view.INV.generic.object.INV_VIRTUAL_NEW.namestructure.view.INV.generic.object.INV_VIRTUAL.name

Description:

Specifies the property mapping for default node view.

NOTE:Will be read from node attributes as follows: DEFAULT_NAME = "Customized I18N Text".

Values: Key name of property


Default value: DEFAULT_NAME

Parameters: structure.view.INV.generic.object.DRAW_CONTAINER.name = DEFAULT_NAMEstructure.view.INV.generic.object.DRAW_CONTAINER.icon = {0}/sap/folder_open

Beschreibung: Specifies default names and icons for folders in which drawings are to be displayed separately in the application structure.

Werte: Folder name as character string or DEFAULT_NAME,Name of the icon in the file "images.jar" (see chapter "Icons for CAD originals in SAP ECTR").

Standardwert: See under Parameters.

Parameters:

plm.structure.node.CUAPOB_INV_MATERIAL.icon.1 = structure/flag/state/$(ANY_MODIFIED)/INVplm.structure.node.CUAPOB_INV_MATERIAL.icon.2 = structure/flag/state/$(STATE)/INVplm.structure.node.CUAPOB_INV_MATERIAL_NEW.icon.1= structure/flag/state/$(ANY_MODIFIED)/INVplm.structure.node.CUAPOB_INV_MATERIAL_NEW.icon.2 = structure/flag/state/$(STATE)/INVplm.structure.node.CUAPOB_INV_VIRTUAL.icon.1 = structure/flag/state/$(ANY_MODIFIED)/INVplm.structure.node.CUAPOB_INV_VIRTUAL.icon.2 = structure/flag/state/$(STATE)/INVplm.structure.node.CUAPOB_INV_VIRTUAL_NEW.icon.1 = structure/flag/state/$(ANY_MODIFIED)/INVplm.structure.node.CUAPOB_INV_VIRTUAL_NEW.icon.2 = structure/flag/state/$(STATE)/INV

Description: Specifies the icon mappings depending on status flags for each possible value of POS_TYPE.Values: Mapping paths for each icon.

Default value: See under Parameters.Parameter: plm.document.PresentationAsNonMaster.INV

Description:

Determines whether presentations should be considered within the functions "Save", "Import" and "Show CAD Structure".

ATTENTION, important note:Once this option has been set to "true", the presentations in the working directory have been cached and are always taken along. If this option issubsequently changed from "true" to "false", the cache must be cleared by deleting the file "CadCache.db" in the directory SessionDir to rebuild thecache!

NOTE:If "true", presentations behave like a dependent drawing and the parameter plm.options.importOnDemand.loadDrawings.INV andplm.options.save.loadDrawings.INV will be considered accordingly!

Values: "true" = presentations are dependent documents and behave like drawings."false" = presentations are treated as master documents.

Default value: falseParameter: plm.options.CreateDirDuringMakeDrawingOrAssemblyFromPartOrAssembly.INV

Description:

Determines which dialog should be displayed when the function "Create drawing view" is started.

NOTE:The setting "0" is not available with Inventor!

Values: "1" = Show "Create Master" dialog"2" = Show "Create Dependent Document" dialog

Default value: 1 Parameter: plm.options.command.OpenWithECTR.ACDDWG.INV

Description:

Handling of Inventor open scenarios for AnyCad documents

Parameter structure:plm.options.command.OpenWithECTR.<DocumentFormat>.INV<DocumentFormat>: The document format of the AnyCad document.

IMPORTANT:Currently, only "ACDDWG" is supported!

Values:'0' = Do not use original Inventor command "Open in AutoCAD"'1' = Replace the original Inventor "Open in AutoCAD" command'2' = Place below the original Inventor "Open in AutoCAD" command'3' = Place inside "SAP PLM" submenu

Default value: 3Parameter: plm.options.SapSaveIntermediateForCadSave.INVDescription: Determines whether saving a model with DIS in CAD automatically triggers an intermediate save in SAP.

Values: "true" = Closing the model in CAD triggers an intermediate save in SAP."false" = No intermediate save will be performed after closing the model in CAD.

Default value: falseParameter: plm.options.CheckinOnCadClose.INVDescription: Determines whether closing the CAD triggers a check-in in SAP.

Values: "True" = Closing the CAD triggers a check-in in SAP."false" = No check-in when closing the CAD.

Default value: falseParameter: plm.options.ForceTemplateProject.INVDescription: Forces the usage of the template project even when there is already an ECTR project in Inventor.

Values: "true" = Overwrites existing project with template project every time"false" = Ignore template project if ECTR project is already set

Default value: falseParameter: plm.options.InventorProjectName.INV


Description:

Name of the Inventor project to be used for creating ECTR Inventor projects.


Values: Name of the Inventor project. Example: ECTR_@PLM_SYSTEM@_@PLM_CLIENT@Default value: --

Parameter: plm.options.command.SynchronizeDrawingAssemblyBOM.INVDescription: Determines whether changes to the drawing BOM should also affect the assembly BOM.

Values: "True" = Change assembly BOM when modifying the drawing BOM"false" = No change of the assembly BOM when modifying the drawing BOM

Default value: falseParameter: plm.options.SaveAsNewDocument.CancelSourceFile.INVDescription: This parameter controls whether the source document is to be cancelled in case of a "SaveAsNewDocument".

Values: "true" = Cancel source document"false = Do not cancel source document

Default value: trueParameter: plm.options.SaveAs.CheckInAfterCreate.INVDescription: Determines whether documents should be checked in after a new version or a new document has been created.

Values: "true" = Documents are checked in"false" = Documents remain checked out

Default value: false

Parameter:experimental.renamer.call.INV = trueplm.application.INV.cadRenamer.enable = trueplm.application.INV.cadRenamer.components = MULTI_LEVELplm.document.create.references.mastercomp.add.INV = true

Description:

Controls the call of the additional application "renamer3INV.exe".

ATTENTION:These parameters come directly from the ECTR. This is necessary to ensure the function of the renamer. They should not be changed!

Values: Since these parameters are not to be changed, no values are specified here.Defaultvalues: See under Parameter!

Parameter: plm.options.ImportOnDemand.DeleteOriginals.INVDescription: Delete original CAD files after successful import on demand.

Values: "true" = Delete CAD files"false" = Do not delete CAD files

Default value: falseParameter: plm.options.ImportOnDemand.CheckInAfterCreate.INVDescription: Check-in documents after successful import on demand.

Values: "true" = Documents will be checked-in"false" = Documents will be checked-out

Default value: trueParameter: plm.options.MacroName.GetRelatedDrawings.INV

Description:

Defines a macro that is executed when the "Open drawing" function is used in Inventor. The default macro "get_related_drawings.txt" ensuresthat master drawings are also loaded.

HINTS:• Available from ECTR version 5.1.15.x and interface version 2.30.83.0!• The macro file entered here must be located in the directory "%PLM_INSTDIR%\applications\inv\customize\scripts\macros"!• The macro is only called if the parameter plm.options.SapOpenForLoadDrawing.INV is set to the value '1' or '2'!

Value: Name of the macro file.Default value: get_related_drawings.txt

Parameter: plm.options.MacroName.GetRelatedPresentations.INV

Description:

Defines a macro to get all related master and non-master presentations of a document. This macro is used e.g. for the function "OpenPresentation" in CAD.

HINTS:• Available from Inventor version 2022.1 and interface version 02.29.136.00!• The macro file entered here must be located in the directory "%PLM_INSTDIR%\applications\inv\customize\scripts\macros"!• It must be ensured that the macro is entered in the file "connector-macro-whitelist.txt", which is located in the directory "customize/config"!

Values: Name of the macro file.Default value: get_related_presentations.txt

Parameter: plm.options.MacroName.MapAttributesMacroName.INV

Description:

The name of the macro to map attributes of virtual components according to the "bod_mapping_section" of the parent document. This macro isused e.g. for "Save" or "Save & Display".

IMPORTANT:It must be ensured that the macro is entered in the file "connector-macro-whitelist.txt", which is located in the directory "customize/config"!

Values: Name of the macro file


Default value: map_attributes.txt

Parameter:

Parameter structure:plm.options.BOMTable.Column.SLE.[CAD_COLUMN] = [SAP_FIELD]

plm.options.BOMTable.Column.INV.Material = MATERIAL_EXTplm.options.BOMTable.Column.INV.Postext1 = POSTEXT1plm.options.BOMTable.Column.INV.Postext2 = POSTEXT2plm.options.BOMTable.Column.INV.OtherColumn = POSTEXT2

Description:

If a BOM table exists, and it contains a column called [CAD_COLUMN], values within this column are updated with the contents of [SAP_FIELD].

ATTENTION:• These configuration options are available from patch 14 of the interface!• If columns must be created, then always in capital letters!

Values:

Implemented values (tags) for [SAP_FIELD]. Possible values are:"MATERIAL" = Internal material number, returned in return table "ET_BALLOONS", column "MATERIAL"."MATERIAL_EXT" = External material number, returned in return table "ET_BALLOONS", column "MATERIAL_EXT"."POSTEXT1" = Return value of the return table "ET_BALLOONS", column "POSTEXT1"."POSTEXT2" = Return value of the return table "ET_BALLOONS", column "POSTEXT2".

Default value: See under Parameters!Parameter: plm.options.BOMTable.AddNonExistingColumns.INV

Description: If a column with the name [CAD_COLUMN] does not exist in the parts list table, it can be added. This is then updated with the contents of[SAP_FIELD].

Values: "true" = Add columns if not exist"false = Do not add non-existent columns

Default value: trueParameter: plm.options.bom.UsePrefixAsCategory.INV

Description:Determines whether the CATEGORY field is to be filled with the prefix of any metadata property (entry in DMU_TMXMETA) or with the CADabbreviation. This is useful for certain implementations in the extended BOM.

Example: Property "STPO-POSNR" => NAME = POSNR | CATEGORY = STPO

Values: "true" = Fill the CATEGORY field with the prefix."false" = Fill the CATEGORY field with the CAD abbreviation

Default value: falseParameter: plm.options.bom.UseAutoBomItemGroup.INV

Description: Decides whether to use an automatically calculated value for the field BOM_ITEM_GROUP (DMU_CAD) when transferring data from virtual instancesto SAP.

Values: "true" = Calculate value per instance and use as BOM_ITEM_GROUP "false" = Use attribute from CAD or empty value

Default value: falseParameter: plm.options.TransferCadPosNr.INVDescription: Decides whether item numbers in the Inventor BOM should also be transferred as ComponentAttribute.

Values: "true" = Transfer Inventor item numbers"false" = Do not transfer Inventor item numbers

Default value: falseParameter: plm.options.TransferCadQuantities.INVDescription: Decides whether quantities in the Inventor BOM should also be transferred as ComponentAttribute in the same way as item numbers.

Values: "true" = Allow transfer of quantities"false" = No quantities transferred

Default value: falseParameter: plm.appl.language.INVDescription: Specified the language of the CAD program. The appropriate language package must be installed.

Values:Language specification in the form <Language>-<Country> (e.g. "en" or "de") or the environment variable "%PLM_LANGUAGE%". This is set by theECTR according to the current SAP logon language.See also the files "%PLM_INSTDIR%\customize\config\plm_initilize.bat" and "%PLM_INSTDIR%\customize\config\saplogon.txt"(plm.logon.gui.languages).

Default value: %PLM_LANGUAGE%Parameter: plm.appl.startup.parameters.INV

Description: At program start, one or more parameters can be passed to Inventor, e.g.: "/importoptions=filename.xml". You use this parameter to specify thenames of the parameters to be transferred. The specification is made without '/'!

Values: List of names of parameters to pass, separated by ';'.Default value: --

Parameter: plm.appl.startup.[paramX].INV = [value]

Description: A value to pass must be specified for each transfer parameter specified with parameter plm.appl.startup.parameters.INV. [paramX] designates theparameter name.

Values: The value to be passed. It can also contain environment variables.Default value: --

Parameter: plm.options.CommandContext.UseActiveDocument.INVDescription: Decides whether all ribbon functions related to documents should affect the top document or the active document of an open assembly.


Values: "true" = The active (in-place editing) document is used"false" = The top document of the assembly is used

Default value: falseParameter: plm.options.Logging.LogPerformanceTrace.INVDescription: Decides whether to create a log file with performance traces in the ECTR log directory for the interface.

Values: "true" = Log performance traces"false" = No logging of performance traces

Default value: falseParameter: plm.options.Cancel.LoadedParts.INVDescription: Provides loaded parts or a subset of them to the ECTR during cancellation. This can increase the performance.

Values:'0' = Provide all loaded parts.'1' = Provide only the selected document.'2' = Do not provide any loaded parts.

Default value: 0Parameter: plm.options.Save.LoadedParts.INVDescription: Provides loaded parts or a subset of them to the ECTR during save. This can increase the performance.

Values:'0' = Provide all loaded parts.'1' = Provide only the selected document.'2' = Do not provide any loaded parts.

Default value: 0Parameter: plm.options.CloseDocumentAfterSapSaveDisplay.INV

Description: ATTENTION:

This parameter is no longer supported since version 02.25.102.00. The function can be called directly by the "Save and Close" function from theribbon!

Values: --Default value: --

Use Excel files as parameter files

Excel parameter files can be created as a separate DIR or additional format (additional file).

Should the Excel file be created as an additional format, the option plm.document.ExcelAsAdditionalFile.INVlocated in the file "%ECTR_INSTDIR%/applications/inv/customize/config/default.txt" must be set to "true".

However, should the Excel file be created as a separate DIR, the optionplm.document.ExcelAsAdditionalFile.INV must be set to "false".

In order for Excel files to be displayed as a separate DIR upon import (function "Import On Demand") atinstallation, the option plm.document.importondemand.searchAlso.INV must be set to the DType "CPA", and"CPA" must be included in the list of DTypes.As a standard, the CPA-DType (CadParameterFile) is delivered in the file "dtype.xml" for Excel files. The DTypecan differ depending on the configuration for Excel files.

Example:

plm.document.importondemand.searchAlso.INV = CPA;XLS

Creating mold assemblies with "ECTR New"

If it has to be possible to create mold assemblies with "ECTR New", already initialized mold assemblies must beused as a template.

To create such a template, a mold assembly must create and saved with Inventor. The resulting ".iam" file canthen serve as a template for the ECTR. For this, it should be moved to the template directory of the ECTR andmust be specified as seed file in the file "dtype.xml".


The DType "IAMMO", which is configured in the file "default.txt" via the parameter"plm.document.dtype.Mold.INV", has already been defined in the "dtype.xml" file for mold assemblies:

Parameter assignment in "default.txt"

plm.document.dtype.Mold.INV = IAMMO

dtype.xml

The DType settings control the behavior of the SAP Engineering Control Center when new documents arecreated and when the properties of documents are handled. Settings related to document type are defined inthe file "dtype.xml". The file "dtype.xml" sent out with the SAP Engineering Control Center Interface to Inventorcontains definitions and settings for document types supported by Inventor.

Structure

The file "dtype.xml" has the following basic structure:

File structure of "dtype.xml"

<!DOCTYPE DType_definitions SYSTEM "../../../../basis/aux-files/dtype_4110.dtd"><DType_definitions> <DType ... > . . . </DType> <DType ... > . . . </DType></DType_definitions>

The element <DType> defines the characteristics of a document type or template. It outlines distinctionsbetween the master document, nonmaster documents dependent on the master document, and templates fordocument type descriptions. The element <DType> possesses a variety of attributes and accepts a wide rangeof subelements.

The setup and structure of the file "dtype.xml" are extensively explained in the help file"Operations Guide_EN.pdf", which can be found in the directory"%PLM_INSTDIR%\documentation\Manuals\en". The XML structure of "dtype.xml" is defined in thefile "%PLM_INSTDIR%\basis\aux-files\dtype_4110.dtd".

The DType definitions for the SAP Engineering Control Center Interface to Inventor are described here.

DType definitions for Inventor

With the installation of the SAP Engineering Control Center interface to Inventor, the file "dtype.xml" isdelivered. This includes the DType definitions that are essential for the interaction with the SAP EngineeringControl Center. Below these definitions will be explained.


The definition is divided into three areas:

Template definitionsMaster document definitionsNonmaster document definitions

The correlation of the DType definitions as well as their dependencies is shown in the following table:

Overview about DType definitions for Inventor

DType-ID Type App-Type Description-----------------------------------------------------------------------------------------------DEFLT Template --- Base template from SAP/DSC| +- INVT Template INV Base template for all Inventor files| +- INMDL Template INV Base template for 3D documents (IPT/IAM)| | +- IPTML Template INV Base template for 3D Parts| | | +- IPT Master INV 3D Part| | | +- IPTNR Master INV 3D Part Not Renaming (e.g. for iPartMember)| | | +- IPTCC Master INV 3D Normteil or Library Parts| | | +- IPTSM Master INV 3D Sheet Metal| | +- IAMLT Template INV Base template for 3D Assemblies| | +- IAM Master INV 3D Assembly| | +- IAMNR Master INV 3D Assembly Not Renaming (e.g. for iAssemblies)| | +- IAMWM Master INV 3D Weldment Assembly| | +- IAMMO Master INV 3D Mold Design Assembly| +- INDRW Template INV Base template for "2D" documents (IPN/IDW/DWG)| +- IPNTL Template INV Base template for Presentations| | +- IPN Master INV Presentations as Master| | +- IPNNM NonMaster INV Presentations as NonMaster| +- IDWTL Template INV Base template for IDW-Drawings| | +- IDW Master INV IDW-Drawings as Master| | +- IDWNM NonMaster INV IDW-Drawings as NonMaster| +- IDWGT Template INV Base template for DWG-Drawings| +- IDWG Master INV DWG-Drawings as Master| +- IDWGN NonMaster INV DWG-Drawings as NonMasterXLS Template --- Base template from SAP/DSC for Excel +- CPA Master XLS XLS Parameter File (XLS)

The following are the descriptions of the individual definitions for Inventor documents.

Generic DType definitions

The generic definitions are templates with basic definitions that are valid for different types of Inventordocuments. Templates are integrated in the other DType definitions.

NOTE:It is recommended to maintain only the language English directly in the file "dtype.xml"! All otherlanguages will be offered via the particular "dictionary.txt" file. This affects the definitions ofDTypes and Seedfiles. All elements <description language="XY"> are omitted except English,which are used as fallback.

The first step is to define the default template, which defines the basic properties for Inventor:


Generic DType definition "INVT" for Inventor

<DType type="template" identifier="INVT" include_template="DEFLT" application_type="INV"group="INVENTOR">...</DType>

Attributes of element <DType> for template definition "INMDL

Attribute Value Description

type "template"Defines the type of DType definition.

"template" = This is a DType template definition.

identifier "INVT"Unique ID string of this DType definition throughout the XML document. TheID must be one to five characters long.

"INVT" = ID of this template definition.

include_template "DEFLT"Determines which template definition is included in this definition.

"DEFLT" = The DType template with the ID "DEFLT" from the global"dtype.xml" file is included

application_type "INV"Identifier for the application responsible for this document. This applicationopens the file from the SAP Engineering Control Center.

"INV" = For Inventor.

group "INVENTOR"Defines the group membership for master documents. The groupmembership is used to organize the DTypes in the "Create Document" dialog."INVENTOR" = Document belongs to this group.

The <program_options> subelement contains various settings that control the behavior of the document inSAP Engineering Control Center.

Attributes of the subelement <program_options>


auto_adjust_application_role "no"Switches the automatic adaptation of the"Application Role" in RES4 on or off"no" = No adjustment will be made.

show_for_create "yes"Determines whether this DType is visible in thecombo box of the available document types in the"Create Document" dialog."yes" = Document is visible.

has_primary_application "yes"

Defines whether the document is a normaldocument with original and assigned workstationapplication or a container object for additionaloriginals without explicit original.

"yes" = The document has an original withassigned workstation application.

dirty_flag "yes"Determines whether the newly created documenthas a dirty flag.

"yes" = The document has a dirty flag.


attempt_status_change_on_checkin "yes"

Determines whether a status change is performedby the SAP Engineering Control Center duringcheck-in or whether the SAP system performs astatus change.

"yes" = Status change by SAP EngineeringControl Center.

document_data_class "DOC_ADDIT_FIELDS"

Determines which classification from SAP is usedin the document creation dialog to configure thefollowing input fields: "Authorization Group","Laboratory/Office", "Change Number", "CMRelevance"."DOC_ADDIT_FIELDS" = Name of the class in SAP.

The subelement <copy_as> defines how the document behaves in a "CopyAs" action and how the SAPEngineering Control Center reacts to this document.

Attributes of subelement <copy_as> of subelement <program_options>


allowed "yes" Determines whether a CopyAs is allowed for this DType."yes" = "CopyAs" action is allowed

ignore_wsappl_list "ZIP"Defines which additional originals in the document are not transferred to the copyof the document during copying by means of a semicolon-separated list ofidentifiers for the workstation application of the additional originals."ZIP" = Additional originals of the type "ZIP" (ZIP archive) are not copied.

use_initial_version "yes"Determines whether the version number of the copy should be set to that of theoriginal or to the initial value (usually "00").

"yes" = Set the version number of the copy to the initial value.

The <new_version> subelement contains settings for the versioning of documents.

Attributes of subelement <new_version> of subelement <program_options>


rename_master_original "no"

Determines whether the original file name should be assignedaccording to the part rules for this DType or whether the previous filename should be kept unchanged.

"no" = Keep file name unchanged.

status_list "AC;IW;RE"Determines, for which document statuses, the versioning of adocument is allowed. A list of document statuses can be separated by";"."AC;IW;RE" = New versions are allowed for this document status.

ignore_wsappl_list "ZIP"

Determines which additional originals in the document are nottransferred to the new version of the document during versioning,using a semicolon-separated list of identifiers for the workstationapplication of the additional originals.

"ZIP" = Additional originals of the type "ZIP" (ZIP archive) are notcopied.


ignore_nm_dtype_list ""

Defines which dependent documents are omitted when the masterdocument is versioned. The dependent documents to be ignored arespecified as a semicolon-separated list of DTypes.

"" = No document types to ignore.

The subelement <document_create> contains settings that control how a new document is created in SAP.

Attributes of the subelement <document_create>


create_with_SAP_GUI "no"Determines whether the SAP GUI shouldbe opened to create a document.

"no" = do not open SAP GUI.

create_multi_allowed "no"Defines whether mass creation is allowedfor the document."no" = No mass creation allowed for thisdocument

document_number_assignment "internal"

Defines the document numberassignment in SAP.

"internal" = SAP assigns the numberautomatically.

initial_document_number "*"

In case of external number assignment,this value is entered as prefix in the inputfield of the document creation dialog. Incase of internal number assignment, thevalue in this field has no meaning.

"*" = The value in this field has nomeaning.

document_type "INV"

SAP document type for the newly createddocument.

"INV" = SAP document type for Inventordocuments.

show_classification_pane "yes"

Shows or hides the classification panel inthe document creation dialog.

"yes" = Show classification panel in thedocument creation dialog.

initial_document_part "000"Initial value for the number of the SAPdocument part for the new document tobe created."000" = Initial value for the part number.

part_editable "no"

Defines whether the default value for thepart number can be changed in the"Document Creation" dialog of the SAPEngineering Control Center.

"no" = The default value cannot bechanged.

initial_document_version "00"

Initial value of the SAP document versionfor the newly created document.

"00" = Initial value for the SAP documentversion.


version_editable "no"

Determines whether the default value forthe document version can be changed inthe "Document Creation" dialog of theSAP Engineering Control Center.


change_to_after_create_status "AC"Here you can define the initial status of anewly created document.

"AC" = Identification of the initial status.

filename_template_base "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)"

Determines how the file name for theoriginal document is composed. Thefollowing placeholders are possible:$(DOCNUMBER) for the documentnumber, $(DOCTYPE) for the documenttype and $(DOCPART) for the documentpart.

"$(DOCNUMBER)$(DOCTYPE)$(DOCPART)"= The file name consists of documentnumber, document type and partdocument.

filename_template_version ""

Specifies whether the document versionshould be appended to the file name forthe original on this document (usually"_$(DOCVERSION)"). "" = No version in the file name.

ATTENTION:This option is not supported andmust be empty!

The <material_create> subelement contains settings for creating a material for a new document.

Attributes of the subelement <material_create>


material_creation_method "deferred"

Determines whether and how a material is created for a newdocument.

"deferred" = No material is created for the document. It ispossible to create a material for this document at a later date.

material_number_assignment "internal"Defines the material number assignment in the SAP system. Thevalues are identical to those of document number assignment.

"internal" = The SAP system assigns the number automatically.

material_type "FERT;HALB"Material type or a ';'-separated list of material types for the newmaterial to be created.

"FERT;HALB" = List of SAP material types.

material_template ""Template material with which the material creation isperformed.

"" = No material template specified.


material_plant_assignment ""Initial value for the assigned work.

"" = No initial work assigned.

material_default_class ""Specifies the default class for the material.

"" = No standard class for the material.

The sub-element <primary_application> determines which application is responsible for this master document(primary application) and defines the rules for checking the originals in and out.

Attributes of the subelement <primary_application>


primary_workstation_application "INV" "INV" = Identification of the SAP workstation application forInventor.

update_attributes_for_dirty "yes"Defines whether an attribute update should occur when the dirtyflag is set.

"yes" = Perform attribute update.

update_attributes_for_rw "yes"Defines the attribute update in the "Open for editing" action.


update_attributes_for_ro "no" Defines the attribute update for the action "Open read-only"."no" = Do not perform an attribute update.

The subelement <container_file> defines the properties of the ZIP archive, which is stored in the document asa container file. It contains the subelement <plmfile>, which defines the properties of the container file.

Attributes of subelement <plmfile> of subelement <container_file> of <primary_application>


extension "ecf" Filters for file name extensions in the file system."ecf" = File name extension.

workstation_application "ECF"Assigns the original to the workstation application.

"ECF" = Identification of the workstation application.

description "ECtr container file"Adds a description to the original document.

"ECtr container file" = Description for the original.

The <checkout_rules> subelement determines how the original document is handled during check-out.

Attributes of subelement <checkout_rules> of subelement <primary_application>


rename_master_original_at_checkout "no"Defines whether the original is renamed when openedaccording to the rules for part names.

"no" = Keep file name of the original when opening.

one_version_in_session_only "yes"

Defines whether only one version of this document may bestored in the session directory.

"yes" = Only one version of the document in the sessiondirectory allowed.


hardlink_in_session "no"

Defines whether a hard link can be used for the originaldocument in the Session directory, or whether a copy mustalways be created.

"no" = Always create a copy.

check_references_on_edit "yes"

Defines whether, for all referenced components, the files in thesession directory could be provided. The check is carried outwith the Open for Edit function. If not all required files are inthe Session directory, the action is aborted and the documentis not opened for editing."yes" = Perform check.

read_structure "flag"

Determines whether a structure resolution is performed whenopening a document.

"flag" = Perform structure resolution, only if "Structure" flag isset.

The sub-element <checkin_rules> determines how files in the Additional directory and originals on thedocument are handled during check-in. It contains several subelements for this purpose.

Attributes of the subelement <checkin_rules> of <primary_application>


from_application_only "yes"

"yes" = Prevents a document without CAD from being checked in via thecontext menu in the ECTR desktop view.

ATTENTION:For the correct storage of the documents with their structure, it is absolutelynecessary that this value is set to "yes"!

The subelement <ignore> defines which files are ignored during the backup. It contains the subelement<plmfile>, which defines the additional file types to be ignored.

Attributes of subelements <plmfile> of subelement <ignore> of <checkin_rules>


extension "bak", "xml", "tmp"

The respective file name extensions of the additional filetypes to be ignored in the file system.

"bak", "xml", "tmp" = File name extensions of the additionalfile types.

filename_pattern "VEConverterResponse\.xml" Filters by file name using regular expressions."VEConverterResponse\.xml" = Filter mask.

The <delete_in_sap> subelement defines which originals on the document are deleted when checking in. Thisallows a targeted cleanup of the document. It contains the subelement <plmfile> which defines the additionalfile types to be deleted.

Attributes of subelements <plmfile> of subelement <delete_in_sap> of <checkin_rules>


workstation_application "EPG", "EPJ", "JT"Workstation application identifiers for the individual additionalformats."EPG", "EPJ", "JT" = identifiers of the workstation application.


The subelement <delete_in_session> defines which files are deleted during check-in. It contains thesubelement <plmfile> which defines the additional file types to be deleted.

Attributes of subelements <plmfile> of subelement <delete_in_session> of <checkin_rules>


extension "jt", "rh", "vds"

The file name extensions of the files to be deleted in thefile system.

"jt", "rh", "vds" = File name extensions of the additionalfile types.

filename_pattern ".*\.preview\.jpg",".*\.preview\.gif"

Filters by filenames using regular expressions.

".*\.preview\.jpg", ".*\.preview\.gif" = Regular Expressionfor file names.

The subelement <additional_files> determines which additional formats of a document can be displayed andedited in the SAP Engineering Control Center.

Attribute of the subelement <additional_files>


enable_additional_files "yes"Determines whether additional originals are allowed for this document.

"yes" = Additional originals are allowed.

The subelement <ignore_files> defines which of the additional originals on the document are NOT displayed inthe original container of a document in SAP Engineering Control Center. It contains subelements of the type<plmfile>, which define the individual document types.

Attribute of the subelement <plmfile> of subelement <ignore_files> of <additional_files>


workstation_application "EPJ", "EPG", "JT", "JTM"The identifiers of the document types that should not bedisplayed."EPJ", "EPG", "JT", "JTM" = Identifiers of the documenttypes.

The <store_files> subelement defines the assignment of the originals to the workstation application whenadding auxiliary files (neutral formats) to a document. The additional files can be added by Drag & Drop ormenu function.

Attributes of the subelement <store_files>


filename_pattern ".*\.preview\.jpg"Filters by file name for JPEG files using regular expressions.

".*\.preview\.jpg" = Filter mask for JPEG files.

extension

"gif","pdf","jt","txt","xls"

The file extensions of the respective additional files (neutralformats).


workstation_application

"EPJ","EPG","PDF","JT","TXT","XLS"

The identifiers of the document types of the respectiveadditional files (neutral formats).

description

"ECTR Preview (jpeg)","ECTR Preview (gif)","$(FILENAME)","3D Preview JT","$(FILENAME)","Excel files"

The descriptions of the respective additional files (neutralformats).

Next comes the generic DType template for 3D documents (assemblies and parts):

Generic DType definition "INMDL" for Inventor

<DType type="template" identifier="INMDL" include_template="INVT" application_type="INV"group="INVENTOR">...</DType>

Attributes of element <DType> for template definition "INMDL




identifier "INMDL"Unique ID string of this DType definition throughout the XML document. TheID must be one to five characters long.

"INMDL" = ID of this template definition.

include_template "INVT"Determines which template definition is included in this definition.

"INVT" = The DType template with the ID "INVT" from this "dtype.xml" file isincluded.

application_type "INV"Identifier for the application responsible for this document. This applicationopens the file from the SAP Engineering Control Center.


group "INVENTOR"Defines the group membership for master documents. The groupmembership is used to organize the DTypes in the "Create Document" dialog.

"INVENTOR" = Document belongs to this group.





function_group "DOC_INVMDL"

So-called "Function Groups" can be defined. For documents with acommon function group, you can define e.g. own context menus.This defines the Function Group to which documents of this typebelong.

"DOC_INVMDL" = Identification of the Function Group.

customer_data_section "INVMDL"Name of a section in the attribute mapping file in which customer-specific data is defined. The data is displayed in the Object Browserunder the "Customer Data" tab."INVMDL" = Name of the section.




attribute_section "INVMDL"Defines which attributes from the attribute mapping files are synchronizedduring document creation.

"INVMDL" = Name of the section.


Attributes of the subelement <primary_application>


attribute_section "INVMDL"Name of a section in the attribute mapping file in which the attribute exchangebetween SAP and the application is defined.

"INVMDL" = Name of the section in the attribute mapping file.

use_relative_path "yes"Determines whether a relative path should be used to address a document ofthis type.

"yes" = Use relative path.

The <checkout_rules> subelement determines how the original document is handled during check-out.The <scripts> subelement contains scripts that are executed before the check-out.

Attribute of the subelement <script> of the subelement <scripts> of <checkout_rules>


phase "after_session_update"Defines at which stage of the process the script is executed.

"after_session_update" = Runs the script after each checkout.

The individual scripts are contained in the subelement <script>.

Attribute of subelement <script> of subelement <scripts> of <checkout_rules>Attribute Value Description

name "@PLM_INSTDIR@\applications\inv\customize\scripts\copy-additional-files.bat"Defines the complete call path of the script to be executed.

"@PLM_INSTDIR@\applications\inv\customize\scripts\copy-additional-files.bat" =Call path of the script file "VEConverter.bat".

<script> contains the <params> subelement, which defines the parameters to be passed to the script to beexecuted. For this purpose, one or more subelements <param> contains <param>, each defining one


parameter.

Attributes of subelements <param> of subelement <params> of subelement <script> of subelement <scripts> of<checkout_rules>


name "--master-file","--input-directory" Contains for each defined parameter its name.

value "$(masterfile)", "$(add_dir)" Script parameters sometimes contain variable data in the form of placeholders ("$(...)").

The sub-element <checkin_rules> determines how files in the Additional directory and originals on thedocument are handled during check-in.The subelement <save_direct> determines which additional files (additional formats) are stored in theAdditional directory when saving as originals on the document. It contains the subelement <plmfile>, whichdetermines the individual additional file types.

Attributes of subelements <plmfile> of subelement <save_direct> of <checkin_rules>


filename_pattern".*\.preview\.jpg",".*\.preview\.gif",".*_mono\.rh", ".*\.vds"

Filters by file name using regular expressions.

".*\.preview\.jpg",".*\.preview\.gif", ".*_mono\.rh", ".*\.vds" = Filter masks.

extension "jt", "rh"The respective file name extensions of the additionalfiles in the file system.

"jpg", "rh" = The respective file name extensions.

workstation_application "EPJ", "EPG", "JTM","RHM", "RH"

Workstation application identifiers for the individualadditional formats.

"EPJ", "EPG", "JTM", "RHM", "RH" = Identifiers ofdocument types.

description

"ECtr Preview (jpeg)","ECtr Preview (gif)", "ECtr3D Preview", "MonolithicRH", "Monolithic VDS","SAP 3D Preview"

Description of the respective additional files.

"ECtr Preview (jpeg)", "ECtr Preview (gif)", "ECtr 3DPreview", "Monolithic RH", "Monolithic VDS", "SAP 3DPreview" = Description of the additional files.

The <scripts> subelement contains scripts that are executed before check-in. The individual scripts arecontained in the <script> subelement.

Attributes of the subelement <script> of the subelement <scripts> of <checkin_rules>Attribute Value Description

name "@PLM_INSTDIR@\basis\sys\win\bin\VEConverter.bat"

Defines the complete call path of the script to be executed.

"@PLM_INSTDIR@\basis\sys\win\bin\VEConverter.bat" =Call pathof the script file "VEConverter.bat".

NOTE:For ECTR older than version 5.1.12 the script"@PLM_INSTDIR@\customize\exec\win\addutils\VEConverter.bat"must be used!

<script> contains the <params> subelement, which defines the parameters to be passed to the script to beexecuted. For this purpose, one or more subelements <param> contains <param>, each defining oneparameter.


Attributes of subelements <param> of subelement <params> of subelement <script> of subelement <scripts> of<checkin_rules>


name

"convertfile", "$(masterfile)","--output-directory, "$(add_dir)","--output-format", "VDS" (für Visual Enterprise < 9.0: "RH"),"--sap-identifier","DOCUMENT=$(doc_type)*$(doc_nr)*$(doc_part)*$(doc_vr)","--sap-metadata", "DOCTYPE=$(doc_type)","--sap-metadata", "DOCNUMBER=$(doc_nr)","--sap-metadata", "DOCPART=$(doc_part)","--sap-metadata", "DOCVERSION=$(doc_vr)","--import-setting", "LoadExternalFiles=false"

Contains the name of eachdefined parameter. Someof them contain variabledata in the form ofplaceholders ("$(...)").

The subelement <additional_files> determines which additional formats of a document can be displayed andedited in the SAP Engineering Control Center.



enable_additional_files "yes"Determines whether additional originals are allowed for this document.

"yes" = Additional originals are allowed.

The subelement <ignore_files> defines which of the additional originals on the document are NOT displayed inthe original container of a document in SAP Engineering Control Center. It contains subelements of the type<plmfile>, which define the individual document types.

Attribute of subelement <plmfile> of subelement <ignore_files> of <additional_files>


workstation_application "EPJ", "EPG", "JT", "JTM"

The identifiers of the document types that should not bedisplayed.

"EPJ", "EPG", "JT", "JTM" = Identifiers of the documenttypes

The <allowed_nonmaster> subelement determines which document type is allowed as a dependent document(Nonmaster document).

Attributes of the subelement <allowed_nonmaster>


DType "VWINM"The unique DType-ID of the dependent document definition.

"VWINM" = DType of the allowed dependent document.

max_count "99"Number of allowed dependent documents for this master document.

"99" = Maximal number of possible dependent documents of this type.

The generic DType template for 2D documents (Drawings) follows:


Generic DType definition "INDRW" for Inventor

<DType type="template" identifier="INDRW" include_template="INVT" application_type="INV"group="INVENTOR">...</DType>

Attributes of element <DType> for template definition "INDRW




identifier "INDRW"Unique ID string of this DType definition throughout the XML document. TheID must be one to five characters long.

"INDRW" = ID of this template definition.

include_template "INVT"Determines which template definition is included in this definition.

"INVT" = The DType template with the ID "INVT" from this "dtype.xml" file isincluded.

application_type "INV"

Identifier for the application responsible for this document (workstationapplication). This application is used to open the file from the SAPEngineering Control Center.

"INV" = For Inventor, this is the Workstation Application (WSAppl).

group "INVENTOR"Defines the group membership for master documents. The groupmembership is used to organize the DTypes in the "Create Document" dialog.

"INVENTOR" = Document belongs to this group.




function_group "DOC_INVDRW"

So-called "Function Groups" can be defined. For documents with acommon function group, you can define e.g. own context menus.This defines the Function Group to which documents of this typebelong.

"DOC_INVDRW" = Identification of the Function Group.

customer_data_section "INVDRW"

Name of a section in the attribute mapping file in which customer-specific data is defined. The data is displayed in the Object Browserunder the "Customer Data" tab.

"INVDRW" = Name of the section.





document_number_assignment "master"Defines the document number assignment in SAP.

"master" = The number of the master document is taken over.


Attribute of the subelement <primary_application>


attribute_section "INVDRW"Name of a section in the attribute mapping file in which the attribute exchangebetween SAP and the application is defined.

"INVDRW" = Name of the section in the attribute mapping file.

The sub-element <checkin_rules> determines how files in the Additional directory and originals on thedocument are handled during check-in. It contains several subelements for this purpose.The subelement <save_direct> determines which additional files (additional formats) are stored in theAdditional directory when saving as originals on the document. It contains the subelement <plmfile>, whichdetermines the individual additional file types.




Filters by filenames using regular expressions.

".*\.preview\.jpg", ".*\.preview\.gif" = Filter masks.

workstation_application "EPJ", "EPG"Workstation application identifiers for theindividual additional formats.

"EPJ", "EPG" = Identifiers of the document types.

description "ECtr Preview (jpeg)", "ECtrPreview (gif)"

Description of the respective additional files.

"ECtr Preview (jpeg)", "ECtr Preview (gif)" =Description of the additional files.

And now the DType template for individual parts (standard parts and sheet metal parts):

Generic DType definition "IPTML" for Inventor

<DType type="template" identifier="IPTML" include_template="INMDL" application_type="INV"application_role="P">...</DType>

Attributes of element <DType> for template definition "IPTML




identifier "IPTML"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IPTML" = ID of this template definition.


include_template "INMDL"Determines which template definition is included in this definition.

"INMDL" = The DType template with the ID "INMDL" from this "dtype.xml" fileis included.


Identifier for the application responsible for this document (workstationapplication). This application is used to open the file from the SAP EngineeringControl Center.

"INV" = For Inventor, this is the Workstation Application (WSAppl).

application_role "P"This is used to set the object type in the RES4 field of the SAP table DRAW.

"P" = Identification of the object type for parts.

The <icon> subelement defines an abbreviation that is used to determine the symbol to be used in SAPEngineering Control Center. It contains the subelement <icondef>.

Attributes of subelement <icondef> of subelement <icon>


icon_position "1"Position of the symbol in the document entry in thetree.

"1" = Far left, "6" = far right.

icon_group "default"Identification of a symbol group. Other symbols can bedisplayed depending on their status.

"default" = This is the default icon.

icon_identifier "{0}/tree/inv/inventor_part$(FAMILY)"Path for determining the icon file containing thesymbol to be used for this symbol position.

"{0}/tree/inv/inventor_part$(FAMILY)" = The icon file.


Attribute of the subelement <document_create>


document_type "IPT"SAP document type for the newly created document.

"IPT" = SAP document type.




use_relative_path "yes"Determines whether a relative path should be used to address a document of thistype.

"yes" = Use relative paths.

The sub-element <checkin_rules> determines how files in the Additional directory and originals on thedocument are handled during check-in. It contains several subelements for this purpose.


Attribute of the subelement <checkin_rules> of <primary_application>


from_application_only "yes" "yes" = Prevents a document without CAD from being checked in via thecontext menu in the ECTR desktop view.

The subelement <save_direct> determines which additional files (additional formats) are stored in theAdditional directory when saving as originals on the document. It contains the subelement <plmfile>, whichdetermines the individual additional file types.



filename_pattern".*\.preview\.jpg",".*\.preview\.gif", ".*_mono\.rh",".*_mono\.vds"

Filters by file name using regular expressions.".*\.preview\.jpg", ".*\.preview\.gif",".*_mono\.rh", ".*_mono\.vds" = Filter masks.

extension "jt", "rh"

The respective file name extensions of theadditional file types to be backed up in the filesystem."jt", "rh" = File name extensions of theadditional file types.

workstation_application "EPJ", "EPG", "JT", "RHM", "RH"

Workstation application identifiers for theindividual additional formats.

"EPJ", "EPG", "JT", "RHM", "RH" = Identifiers ofthe document types.

description"ECtr Preview (jpeg)", "ECtrPreview (gif)", "ECtr 3D Preview","Monolithic RH", "Monolithic VDS","SAP 3D Preview"

Description of the respective additional files."ECtr Preview (jpeg)", "ECtr Preview (gif)", "ECtr3D Preview", "Monolithic RH", "Monolithic VDS","SAP 3D Preview" = Description of the additionalfiles.

The DType template for assemblies follows:

Generic DType definition "IAMLT" for Inventor

<DType type="template" identifier="IAMLT" include_template="INMDL" application_type="INV"application_role="A">...</DType>

Attributes of element <DType> for template definition "IAMLT




identifier "IAMLT"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IAMLT" = ID of this template definition.

include_template "INMDL"Determines which template definition is included in this definition.

"INMDL" = The DType template with the ID "INMDL" from this file is included.




"INV" = For Inventor, this is the workstation application (WSAppl).

application_role "A"This is used to set the object type in the RES4 field of the SAP table DRAW.

"A" = Identifier of the object type for assemblies.




icon_position "1"Position of the symbol in the document entry inthe tree."1" = Far left, "6" = far right.

icon_group "default"Identification of a symbol group. Other symbolscan be displayed depending on their status."default" = This is the default icon.

icon_identifier "{0}/tree/inv/inventor_assembly$(FAMILY)"

Path for determining the icon file containing thesymbol to be used for this symbol position.

"{0}/tree/inv/inventor_assembly$(FAMILY)" =The icon file.




document_type "IAM"SAP document type for the newly created document.

"IAM" = SAP document type.

rename_template_filename "yes"

Determines whether the file name for the original is renamed duringdocument creation according to the set naming rules, or whether the filename of the original file is transferred unchanged."yes" = The file name of the original is renamed when the document iscreated

The DType template for presentations follows:

Generic DType definition "IPNTL" for Inventor

<DType type="template" identifier="IPNTL" include_template="INDRW" application_type="INV"application_role="D">...</DType>

Attributes of element <DType> for template definition "IPNTL





identifier "IPNTL"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long."IPNTL" = ID of this template definition.

include_template "INDRW"Determines which template definition is included in this definition.

"INDRW" = The DType template with the ID "INDRW" from this "dtype.xml" fileis included.

application_type "INV"Identifier for the application responsible for this document (workstationapplication). This application is used to open the file from the SAP EngineeringControl Center."INV" = For Inventor, this is the workstation application (WSAppl).

application_role "D" This is used to set the object type in the RES4 field of the SAP table DRAW."D" = Identifier of the object type for Drawings.




icon_position "1"Position of the symbol in the document entry in the tree.




icon_identifier "{0}/tree/inv/inventor_presentation"Path for determining the icon file containing the symbolto be used for this symbol position.

"{0}/tree/inv/inventor_presentation" = The icon file.




document_type "IPN"SAP document type for the newly created document.

"IPN" = SAP document type.

document_number_assignment "internal"Defines the document number assignment in SAP.


The subelement <seedfile> contains settings for the template file. Several template files can be assigned, i.e.<seedfile> can occur several times. This contains the subelement <description>, which defines descriptiontexts in different languages. There are also template files for the Inventor versions "2019" to "2021".

Attributes of the 1st subelement <seedfile> of subelement <document_create>Attribute Value Description


filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).ipn"

When type="template" is used, this attribute defines the file nameof the template file to be used. A file with this name must exist,otherwise the program will abort with an error.

"@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).ipn" = File name of the template file to be used forpresentations with inch dimensions.

type "template"Defines how the original of the document is created.

"template" = Via the attribute "filename" the template file to beused is specified.

default "no"This allows you to determine whether this template file is preset inthe "Create Document" dialog.

"no" = This template file is not preset.

extension_filter "*.ipn"

When selecting a template file with type="select" this attributedefines the filter for the file extension. In the file selection dialog,the files matching the filter are offered for selection.

"*.ipn" = Filter for the file extension.

dictionary_identifier "20xx.English.Standard(in)"Identifier of the template description in the dictionary.

"20xx.English.Standard(in)" = Dictionary identifier.

Attributes of the 2nd subelement <seedfile> of subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).ipn"

The filename attribute is used to specify the template file to beused. You can select a template file in the Create Document dialogusing a file selection dialog.

"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).ipn" = File name of the template file for presentations withmillimeter dimensions.



default "yes"This allows you to determine whether this template file is preset inthe "Create Document" dialog.

"yes" = This template file is the default.


When selecting a template file with type="select" this attributedefines the filter for the file extension. In the file selection dialog,the files matching the filter are offered for selection.


dictionary_identifier "20xx.Metric.Standard(mm)"Identifier of the description of the template in the dictionary.

"20xx.Metric.Standard(mm)" = Dictionary identifier.

The following subelement <seedfile> contains settings for the version independent template file.

Attributes of the 3rd subelement <seedfile> of subelement <document_create>


filename ""When type="template" is used, this attribute defines the file name of thetemplate file that is used.

"" = No template file.

type "select"

Defines how the original of the document is created. The filename attributespecifies the template file to be used. A template file can be selected in the"Create Document" dialog using a file selection dialog.

"select" = A template file can be selected in the "Create Document" dialog.

default "no"This allows you to determine whether this template file is preset in the "CreateDocument" dialog.




When selecting a template file with type="select" this attribute defines thefilter for the file extension. In the file selection dialog, the files matching thefilter are offered for selection.


dictionary_identifier "select"Identifier of the template description in the dictionary.

"select" = Dictionary identifier.

The DType template for drawings of type "IDW":

Generic DType definition "IDWTL" for Inventor

<DType type="template" identifier="IDWTL" include_template="INDRW" application_type="INV"application_role="D">...</DType>

Attributes of element <DType> for template definition "IDWTL




identifier "IDWTL"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IDWTL" = ID of this template definition.


"INDRW" = The DType template with the ID "INDRW" from this file is included.




application_role "D"This is used to set the object type in the RES4 field of the SAP table DRAW.

"D" = Identifier of the object type for Drawings.









icon_identifier "{0}/tree/inv/inventor_drawing"Path for determining the icon file containing the symbol tobe used for this symbol position.

"{0}/tree/inv/inventor_drawing" = The icon file.




document_type "IDW"SAP document type for the newly created document.

"IDW" = SAP document type.



The subelement <seedfile> contains settings for the template file. Several template files can be assigned, i.e.<seedfile> can occur several times. This contains the subelement <description>, which defines descriptiontexts in different languages. There are also template files for the Inventor versions "2019" to "2021".


filename "@PLM_INSTDIR@\applications\INV\templates\2021\English\ANSI(in).idw"

When type="template" is used, this attribute defines the filename of the template file to be used. A file with this name mustexist, otherwise the program will abort with an error.

"@PLM_INSTDIR@\applications\INV\templates\2021\English\ANSI(in).idw" = File name of the template file to be used fordrawings of type "IDW" with inch dimensions.

type "template"Defines how the original of the document is created."template" = Via the attribute "filename" the template file to beused is specified.

default "no"This allows you to determine whether this template file is presetin the "Create Document" dialog.


component_reference "yes"

For dependent documents only: Determines whether thedependent document receives a component reference (sortstring: 'DC') or whether the document is a simple dependentdocument (sort string: 'D')

"yes" = A component reference is created.

dictionary_identifier "20xx.English.ANSI(in)"Identifier of the template description in the dictionary.

"20xx.English.ANSI(in)" = Dictionary identifier.


filename "@PLM_INSTDIR@\applications\INV\templates\2021\Metric\DIN.idw"


"@PLM_INSTDIR@\applications\INV\templates\2021\Metric\DIN.idw"= File name of the template file for drawings of type "IDW" withmillimeter dimensions.

type "template"Defines how the original of the document is created."template" = Via the attribute "filename" the template file to beused is specified.





For dependent documents only: Determines whether thedependent document receives a component reference (sort string:'DC') or whether the document is a simple dependent document(sort string: 'D')."yes" = A component reference is created.

dictionary_identifier "20xx.Metric.DIN"Identifier of the template description in the dictionary.

"20xx.Metric.DIN" = Dictionary identifier.

Attributes of the 3rd subelement <seedfile> of subelement <document_create>Attribute Value Description

filename "" When type="template" is used, this attribute defines the file name of the template file to be used."" = No template file.

type "select"Defines how the original of the document is created. The filename attribute specifies the template file to be used. A template file can beselected in the "Create Document" dialog using a file selection dialog.


default "no" This allows you to determine whether this template file is preset in the "Create Document" dialog."no" = This template file is not preset.

extension_filter "*.idw"When selecting a template file with type="select" this attribute defines the filter for the file extension. In the file selection dialog, the filesmatching the filter are offered for selection.

"*.idw" = Filter for the file extension.

dictionary_identifier "select" Identifier of the template description in the dictionary."select" = Dictionary identifier.

Finally the DType template for drawings of type "DWG":

Generic DType definition "IDWGT" for Inventor

<DType type="template" identifier="IDWGT" include_template="INDRW" application_type="INV"application_role="D">...</DType>

Attributes of element <DType> for template definition "IDWGT


type "template" Defines the type of DType definition."template" = This is a DType template definition.

identifier "IDWGT"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IDWGT" = ID of this template definition.


"INDRW" = The DType template with the ID "INDRW" from this file is included.

application_type "INV"Identifier for the application responsible for this document (workstationapplication). This application is used to open the file from the SAP EngineeringControl Center."INV" = For Inventor, this is the workstation application (WSAppl).

application_role "D" This is used to set the object type in the RES4 field of the SAP table DRAW."D" = Identifier of the object type for Drawings.









icon_identifier "{0}/tree/inv/inventor_drawing"Path for determining the icon file containing the symbol tobe used for this symbol position.

"{0}/tree/inv/inventor_drawing" = The icon file.




function_group "DOC_INVDWG"

So-called "Function Groups" can be defined. For documents with a commonfunction group you can define e.g. own context menus. This defines theFunction Group to which documents of this type belong.

"DOC_INVDWG" = Identification of the Function Group.




document_type "IDW"SAP document type for the newly created document.

"IDW" = SAP document type.



The subelement <seedfile> contains settings for the template file. Several template files can be assigned, i.e.<seedfile> can occur several times. This contains the subelement <description>, which defines descriptiontexts in different languages.


filename "@PLM_INSTDIR@\applications\INV\templates\20xx\English\ANSI(in).dwg"

When type="template" is used, this attribute defines the filename of the template file to be used. A file with this name mustexist, otherwise the program will abort with an error."@PLM_INSTDIR@\applications\INV\templates\20xx\English\ANSI(in).dwg" = File name of the template file to be used fordrawings of type "DWG".



default "no"This allows you to determine whether this template file ispreset in the "Create Document" dialog.




For dependent documents only: Determines whether thedependent document receives a component reference (sortstring: 'DC') or whether the document is a simple dependentdocument (sort string: 'D').


dictionary_identifier "20xx.English.ANSI(in)"Identifier of the template description in the dictionary.

"20xx.English.ANSI(in)" = Directory identifier.


filename "@PLM_INSTDIR@\applications\INV\templates\20xx\Metric\DIN.dwg"


"@PLM_INSTDIR@\applications\INV\templates\20xx\Metric\DIN.dwg"= File name of the template file for drawings of the type "DWG".






For dependent documents only: Determines whether thedependent document receives a component reference (sort string:'DC') or whether the document is a simple dependent document(sort string: 'D').


dictionary_identifier "20xx.Metric.DIN" Identifier of the template description in the dictionary."20xx.Metric.DIN" = Directory identifier.

Attributes of the 3rd subelement <seedfile> of subelement <document_create>


filename ""

When type="template" is used, this attribute defines the file name of thetemplate file to be used. A file with this name must exist, otherwise theprogram will abort with an error.

"" = No template file.

type "select"

Defines how the original of the document is created. The filename attributespecifies the template file to be used. A template file can be selected in the"Create Document" dialog using a file selection dialog.


default "no"This allows you to determine whether this template file is preset in the "CreateDocument" dialog.


extension_filter "*.dwg"When selecting a template file with type="select" this attribute defines thefilter for the file extension. In the file selection dialog, the files matching thefilter are offered for selection."*.dwg" = Filter for the file extension.

dictionary_identifier "select"Identifier of the template description in the dictionary.

"select" = Directory identifier.

The DType definition for master documents


The SAP Engineering Control Center distinguishes between master documents and dependent documents(nonmaster documents). The master document is the main document and contains the CAD model file to beprocessed. In addition, the master document is the basis for the preparation of the bill of materials.

NOTE:It is recommended to maintain only the language English directly in the file "dtype.xml"! All otherlanguages will be offered via the particular "dictionary.txt" file. This affects the definitions ofDTypes and Seedfiles. All elements <description language="XY"> are omitted except Englishwhich are used as fallback.

The DType definition is divided into template definitions and actual DType definitions for master documentswhich are included in a template. First, the DType definition for Parts:

DType definition for master documents of type "IPT"

<DType type="master" identifier="IPT" include_template="IPTML" application_type="INV"application_role="P" sort_key="1">...</DType>

Attributes of element <DType> of the DType definition "IPT"


type "master"Specifies the type of DType definition.

"master" = This is the definition for master documents.

identifier "IPT"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IPT" = ID of this DType definition.

include_template "IPTML"Determines which template definition is included in this definition.

"IPTML" = The DType template with the ID "IPTML" from this "dtype.xml" file isincluded.

application_type "INV"Identifier for the application that is responsible for this document (WorkstationApplication). This application opens the file from SAP Engineering Control Center.


application_role "P"This is used to set the object type in the "RES4" field of the SAP table DRAW.

"P" = Identifier of the object type for parts.

sort_key "1"Defines a sorting key which is used for an alphanumeric sorting of the DTypeentries in the combo box for DType selection.

"1" = sorting key.

The <program_options> subelement contains various settings that control the behavior of the document in theSAP Engineering Control Center. The subelement describes settings for versioning documents.

Attribute of the subelement <new_version> of subelement <program_options>




Determines whether, when versioning, the original is given a file nameaccording to the part rules for this DType or whether the previous filename is kept unchanged.

"no" = keep file name unchanged.

take_instances_for_generic "yes"

Determines whether the entire part family group (generic part +variants) is versioned during versioning of the generic part (template).

"yes" = The variants are co-versioned during the versioning of thegeneric part.

The <document_create> subelement determines how settings are made for how the document is created inSAP.




"IPT" = Inventor Part document.


Specifies whether the filename for the original is renamed during thedocument creation according to the set naming rules, or whether thefilename of the template file is adopted unchanged.

"yes" = The filename of the original is renamed when the document iscreated.

The <seedfile> subelement contains settings for the template file. A plurality of template files may beassociated, e.g. <seedfile> can occur several times. It contains the subelement <description>, which definesdescription texts in different languages. A seed file definition for inches and millimeters is available forInventor versions 2019 to 2021. These differ only in the access thread of the respective template files.

Attributes of the 1. subelement <seedfile> (inch) of subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).ipt"

Defines the filename of the template file to be used for models withinches (inches).

"@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).ipt" = Filepath of the template file to use.

type "template"Determines how the original of the document is generated.

"template" = The "filename" attribute specifies the template file touse.

default "no"This can be used to determine whether this template file is presetin the "Create document" dialog.


extension_filter "*.ipt"

When selecting a template file with type = "select", this attributedefines the filter for the file extension. In the file selection dialog,the files matching the filter are offered for selection.

"* .ipt" = File extension.

dictionary_identifier "20xx.English.Standard(in)"Description of the template file.

"20xx.English.Standard(in)" = Description.

Attributes of the 2. subelement <seedfile> (metric) of subelement <document_create>Attribute Value Description


filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).ipt"

Defines the filename of the template file to be used for metricmodels.

"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).ipt" = Filepath of the template file to use.



default "yes"This can be used to determine whether this template file is presetin the "Create Document" dialog.

"yes" = This template file is preset.




dictionary_identifier "20xx.Metric.Standard(mm)"Description of this template file.

"20xx.Metric.Standard(mm)" = Description.

The following is the seed file definition for version-independent template files.

Attributes of the 3. subelement <seedfile> of subelement <document_create>


filename "Standard.ipt"When using type = "template", this attribute defines the filename of thetemplate file that is used.

"Standard.ipt" = file name.

type "select"Determines how the original of the document is generated.

"select" = A template file can be selected in the dialog "Createdocument".

default "no"This can be used to determine whether this template file is preset in the"Create Document" dialog.



When selecting a template file with type = "select", this attribute definesthe filter for the file extension. In the file selection dialog, the filesmatching the filter are offered for selection.


dictionary_identifier "select"Description of this template file.

"select" = Description.

The subelements <allowed_nonmaster> determine which document types are allowed as dependentdocuments (Nonmaster document).

Attributes of the subelements <allowed_nonmaster>

Attributes Value Description

DType "IDWNM","IDWGN"

The unique DType ID of the dependent document definition.

"IDWNM", "IDWGN" = DTypes of the permitted dependent documents.




The following is the DType definition for standard parts:

DType definition of master documents of DType "IPTNR"

<DType type="master" identifier="IPTNR" include_template="IPTML" application_type="INV"application_role="P">...</DType>

Attributes of the element <DType> of the DType definition "IPTNR"




identifier "IPTNR"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IPTNR" = ID of this DType definition.






"P" = Identifier of the object type for parts.

The <program_options> subtree contains various settings that control the behavior of the document in theSAP Engineering Control Center.

Attributes of subelement <program_options>


function_group "DOC_INVNR"

Sets the Function Group to which the document belongs. For documents witha common Function Group, for example, specific context menus can bedefined.

"DOC_INVNR" = This DType is assigned to the Function Group "DOC_INVNR".

show_for_create "no"Defines whether this DType is visible in the combo box of the availabledocument types in the "Create document" dialog.

"no" = Document is not visible.

The subelement <copy_as> determines how the document behaves during a "CopyAs" action and how SAPEngineering Control Center reacts to the document.

Attribute to the subelement <copy_as> from subelement <program_options>



allowed "no"Determines whether this DType is visible in the combo box of the available documenttypes in the "Create Document" dialog.


The <new_version> subelement of <program_options> contains various settings that control the behavior ofthe document in the SAP Engineering Control Center. The subelement describes settings for versioningdocuments.

Attributes of the subelement <new_version> of subelement <program_options>



Determines whether the original is given a filename according to thecomponent rules for this DType during versioning, or whether theprevious filename is retained unchanged.

"no" = The file name is retained.





Attributes of subelement <document_create>




rename_template_filename "no"


"no" = The filename of the template file is copied to the original in thedocument.








default "no"This can be used to determine whether this template file is presetin the "Create Document" dialog.




















"20xx.Metric.Standard (mm)" Description.




filename "Standard.ipt"When using type = "template", this attribute defines the filename of thetemplate file that is being used.

"Standard.ipt" = File name.












Attributes of subelements <allowed_nonmaster>



The unique DType-ID of the dependent document definition.

"IDWNM", "IDWGN" = DTypes of the allowed dependent documents.


"99" = Max. Number of possible dependent documents of this type.

The DType definition for standard parts:

DType definition for master documents of type "IPTCC"

<DType type="master" identifier="IPTCC" include_template="IPTML" application_type="INV"application_role="PN">...</DType>




identifier "IPTCC"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IPTCC" = ID of this DType definition.





application_role "PN"This is used to set the object type in the RES4 field of the SAP table DRAW.

"PN" = Identifier of the object type for standard parts.

The <program_options> subelement contains various settings that control the behavior of the document in theSAP Engineering Control Center.



function_group "DOC_INVCC"

Function groups can be defined. For documents with a common functiongroup, e.g. custom context menus. This defines the function group to whichdocuments of this type belong.

"DOC_INVCC" = Identifier of the function group.






































dictionary_identifier "20xx.Metric.Standard(mm)"Description of the template file.














dictionary_identifier "select"Description of the template file.


The DType definition for Sheet Metal:

DType definition for master documents of type "IPTSM"

<DType type="master" identifier="IPTSM" include_template="IPTML" application_type="INV"application_role="P">...</DType>

Attributes of element <DType> of DType definition "IPTSM"




identifier "IPTSM"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IPTSM" = ID of this DType definition.







"P" = Identifier of the object type part.








filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\SheetMetal (in).ipt"

Defines the filename of the template file to be used for modelswith inches (inches).

"@PLM_INSTDIR@\applications\inv\templates\20xx\English\SheetMetal (in).ipt" = Filepath of the template file to use.


"template" = The "filename" attribute specifies the template fileto use.

default "no"This can be used to determine whether this template file ispreset in the "Create Document" dialog.



When selecting a template file with type = "select", thisattribute defines the filter for the file extension. In the fileselection dialog, the files matching the filter are offered forselection.


dictionary_identifier "20xx.English.SheetMetal(in)"Description of the template file.

"20xx.English.SheetMetal (in)" = Description.


filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\SheetMetal (mm).ipt"


"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\SheetMetal (mm).ipt" = Filepath of the template file to use.



"template" = The "filename" attribute specifies the templatefile to use.

default "yes"This can be used to determine whether this template file ispreset in the "Create Document" dialog.





dictionary_identifier "20xx.SheetMetal (mm)"Description of this template file.

"20xx.SheetMetal (mm)" = Description.























The DType definition for Assemblies:


DType definition for master document of type "IAM"

<DType type="master" identifier="IAM" include_template="IAMLT" application_type="INV"application_role="A" sort_key="1">...</DType>

Attributes of element <DType> of DType definition "IAM"




identifier "IAM"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IAM" = ID of this DType definition.

include_template "IAMLT"Determines which template definition is included in this definition.

"IAMLT" = The DType template with the ID "IAMLT" from this "dtype.xml" file isincluded.





sort_key "1"Defines a sort key that is used for alphanumeric sorting of DType entries in theDType selection combo box.

"1" = Sort key.





"IAM" = Inventor Assembly document.



"yes" = The filename of the original is renamed when the document iscreated.

The <seedfile> subelement contains settings for the template file. A plurality of template files may beassociated, e.g. <seedfile> can occur several times. It contains the subelement <description>, which definesdescription texts in different languages. A seed file definition for inches and millimeters is available forInventor versions 2014 and 2019 to 2021. These differ only in the access thread of the respective templatefiles.



filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).iam"


"@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).iam" = Filepath of the template file to use.





extension_filter "*.iam"


"* .iam" = File extension.




filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).iam"


"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).iam" = Filepath of the template file to use.











Attributes of the 3. subelement <seedfile> of subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\inv\templates\2014\Standard.iam"

When using type = "template", this attribute defines thefilename of the template file that is being used.

"@PLM_INSTDIR@\applications\inv\templates\2014\Standard.iam"= File name.











The subelements <allowed_nonmaster> determine which document types are allowed as a dependentdocument (Nonmaster document).



DType"IPNNM","IDWNM","IDWGN"


"IPNNM", "IDWNM", "IDWGN" = DTypes of the permitted dependent documents.



The DType definition for Generic Assemblies:

DType definition for master documents of type "IAMNR"

<DType type="master" identifier="IAMNR" include_template="IAMLT" application_type="INV"application_role="A">...</DType>

Attributes of element <DType> of DType definition "IAMNR"




identifier "IAMNR"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IAMNR" = ID of this DType definition.







The <program_options> subelement contains various settings that control the behavior of the document in theSAP Engineering Control Center.




function_group "DOC_INVNR"

Function groups can be defined. For documents with a common functiongroup, e.g. custom context menus. This defines the function group to whichdocuments of this type belong.

"DOC_INVNR" = Identifier of the function group.






allowed "no"Determines whether this DType is visible in the combo box of the available documenttypes in the "Create Document" dialog.


The subelement <new_version> describes settings for versioning documents.

Attributes of the subelement <new_version> of subelement <program_options>



Determines whether the original is given a filename according to thecomponent rules for this DType during versioning, or whether theprevious filename is retained unchanged.

"no" = The file name is retained.












The <seedfile> subelement contains settings for the template file. A plurality of template files may beassociated, e.g. <seedfile> can occur several times. It contains the subelement <description>, which definesdescription texts in different languages. A seed file definition for inches and millimeters is available for


Inventor versions 2014 and 2019 to 2021. These differ only in the access thread of the respective templatefiles.


filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).iam"


"@PLM_INSTDIR@\applications\inv\templates\20xx\English\Standard(in).iam" = Filepath of the template file to use.









"20xx.English.Standard (in)" = Description.


filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).iam"


"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Standard(mm).iam" = Filepath of the template file to use.









"20xx.Metric.Standard (mm)" = Description.


Attributes of the 3. subelement <seedfile> of subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\inv\templates\2014\Standard.iam"

When using type = "template", this attribute defines thefilename of the template file that is being used.

"@PLM_INSTDIR@\applications\inv\templates\2014\Standard.iam"= Filepath of the template file to use.











The subelements <allowed_nonmaster> determine which document types are allowed as a dependentdocument (Nonmaster document).








The DType definition for Weldment Assemblies:

DType definition for master documents of type "IAMWM"

<DType type="master" identifier="IAMWM" include_template="IAMLT" application_type="INV"application_role="A">...</DType>

Attributes of element <DType> of the DType definition "IAMWM"




identifier "IAMWM"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IAMWM" = ID of this DType definition.




Identifier for the application that is responsible for this document (WorkstationApplication). This application opens the file from SAP Engineering ControlCenter.










The <seedfile> subelement contains settings for the template file. A plurality of template files may beassociated, e.g. <seedfile> can occur several times. It contains the subelement <description>, which definesdescription texts in different languages. A seed file definition for ANSI and DIN is available for Inventor versions2019 to 2021. These differ only in the access thread of the respective template files.

Attributes of the 1. subelement <seedfile> (ANSI) of subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\Weldment(ANSI).iam"

Defines the filename of the template file to be used for models withANSI.

"@PLM_INSTDIR@\applications\inv\templates\20xx\English\Weldment(ANSI).iam" = Filepath of the template file to use.



default "no"This can be used to determine whether this template file is preset inthe "Create Document" dialog.



When selecting a template file with type = "select", this attributedefines the filter for the file extension. In the file selection dialog, thefiles matching the filter are offered for selection.


dictionary_identifier "20xx.English.Weldment(ANSI)"Description of this template file.

"20xx.English.Weldment(ANSI)" = Description.

Attributes of the 2. subelement <seedfile> (DIN) of subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Weldment(DIN).iam"

Defines the filename of the template file to be used for DIN models.

"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\Weldment(DIN).iam" = Filepath of the template file to use.








dictionary_identifier "20xx.Metric.Weldment(DIN)"Description of this template file.

"20xx.Metric.Weldment(DIN)" = Description.




filename "" When using type = "template", this attribute defines the filename of thetemplate file that is being used. "" = No file path.



"select" = A template file can be selected in the dialog "Create document".




When selecting a template file with type = "select", this attribute defines thefilter for the file extension. In the file selection dialog, the files matching thefilter are offered for selection.












The DType definition for Mold Design Assemblies:

DType definition for master documents of type "IAMMO"

<DType type="master" identifier="IAMMO" include_template="IAMLT" application_type="INV"application_role="A">...</DType>

Attributes of the element <DType> of the DType definition "IAMMO"




identifier "IAMMO"Unique ID string of this DType definition throughout the XML document. The IDmust be one to five characters long.

"IAMMO" = ID of this DType definition.








The <program_options> subtree contains various settings that control the behavior of the document in theSAP Engineering Control Center.



show_for_create "yes"Defines whether this DType is visible in the combo box of the available documenttypes in the "Create document" dialog.

"yes" = Document is visible.








filename "@PLM_INSTDIR@\applications\inv\templates\20xx\English\MoldDesign (in).iam"

Defines the filename of the template file to be used for modelswith inches (inches).

"@PLM_INSTDIR@\applications\inv\templates\20xx\English\MoldDesign (in).iam" = Filepath of the template file to use.








dictionary_identifier "20xx.English.Mold(in)"Description of this template file.

"20xx.English.Mold(in)" = Description.



filename "@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\MoldDesign (mm).iam"


"@PLM_INSTDIR@\applications\inv\templates\20xx\Metric\MoldDesign (mm).iam" = Filepath of the template file to use.



default "yes"This can be used to determine whether this template file ispreset in the "Create Document" dialog.





dictionary_identifier "20xx.Metric.Mold(mm)"Description of this template file.

"20xx.Metric.Mold(mm)" = Description.




filename ""When using type = "template", this attribute defines the filename of thetemplate file that is being used.

"" = No file path.


"select" = A template file can be selected in the dialog "Create document".




When selecting a template file with type = "select", this attribute defines thefilter for the file extension. In the file selection dialog, the files matching thefilter are offered for selection.













The DType definition for presentations:

The DType definition for master documents of type "IPN"

<DType type="master" identifier="IPN" include_template="IPNTL" application_type="INV"application_role="D">...</DType>

Attribute of element <DType> of DType definition "IPN"


type "master"Sets the type of DType definition.

"master" = Relates to the definition for master documents.

identifier "IPN"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one and five characters long.

"IPN" = ID of this DType definition.

include_template "IPNTL"Determines which template definition should be integrated into this definition.


application_type "INV"Designates the application that is relevant for this document (WorkstationApplication). This application opens the file from SAP Engineering Control Center.

"INV" = This is the Workstation Application for Inventor (WSAppl).

application_role "D"Here, you can adjust the object type in the RES4 field of the SAP table DRAW.

"D" = ID of the object type for Drawings.









The DType definition for Drawings ("IDW"):

The DType definition for master documents of type "IDW"

<DType type="master" identifier="IDW" include_template="IDWTL" application_type="INV"application_role="D">...</DType>

Attribute of element <DType> of DType definition "IDW"





identifier "IDW"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one to five characters long.

"IDW" = ID of this DType definition.

include_template "IDWTL"Determines which template definition should be integrated into this definition.

"IPWTL" = The DType template with the ID "IPWTL" from this "dtype.xml" file isincluded.





The DType definition for Drawings ("DWG"):

The DType definition for master documents of type "IDWG"

<DType type="master" identifier="IDWG" include_template="IDWGT" application_type="INV"application_role="D">...</DType>

Attribute of element <DType> of DType definition "IDWG"




identifier "IDWGT"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one to five characters long.

"IDWGT" = ID of this DType definition.

include_template "IDWGT"Determines which template definition should be integrated into this definition.

"IDWGT" = The DType template with the ID "IDWGT" from this "dtype.xml" file isincluded.





Finally, the DType definition for CAD parameter files of type "XLS":


The DType definition for master documents of type "XLS"

<DType type="master" identifier="CPA" include_template="TXLS" application_type="XLS"group="Microsoft Office">...</DType>

Attribute of element <DType> the template definition "CPA"




identifier "CPA"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one and five characters long.

"CPA" = ID of this DType definition.

include_template "TXLS"

Determines which template definition should be integrated into thisdefinition.

"TXLS" = The DType template with the "XLS" ID from this "dtype.xml" fileis included. This is the generic definition.

application_type "XLS"

Designates the application that is relevant for this document (WorkstationApplication). This application opens the file from SAP Engineering ControlCenter.

"XLS" = This is the Workstation Application for (WSAppl).

group "MicrosoftOffice"

Defines the group designation for master documents. The groupdesignation helps to organize DTypes within the dialog "createdocument".

"Microsoft Office" = Document belongs to this group.

The subelement <icon> defines an abbreviation that will be used when determining the applicable symbol inSAP Engineering Control Center. It also contains the subelement <icondef>.

Attributes of the first subelement <icondef> from subelement <icon>


icon_position "1"Position of the symbol in the document entry in thetree.

"1" = far left, "7" = far right.

icon_group "default"Identification of a symbol group. Depending on thestatus, other symbols can be represented.

"default" = This is the standard symbol.

icon_identifier "tree/xls/$(TYPE)$(SUBTYPE)$(FAMILY)"

Path to determine the icon file, which contains theapplicable symbol for this symbol position.

"tree/xls/$(TYPE)$(SUBTYPE)$(FAMILY)" = The iconfile.

Attributes of the second subelement <icondef> from subelement <icon>



icon_position "2"Position of the symbol in the document entry inthe tree.


icon_group "default"Identification of a symbol group. Depending onthe status, other symbols can be represented.


use_status_color "no"Turns the symbol color on or off. This attributeallows the correct display in filter lists.

"no" = The symbol color for this icon is off.

icon_identifier "flag/flag_version_$(HER)$(HNV)$(HRV)"

Path to determine the icon file, which contains theapplicable symbol for this symbol position.

"flag/flag_version_$(HER)$(HNV)$(HRV)" = Theicon file.

Attributes of the third subelement <icondef> from subelement <icon>








icon_identifier "flag/flag_primaryfiles_moe$(MOE)_moc$(MOC)_iu$(IN_USE_BY_OTHER)"

Path to determine the icon file, which containsthe applicable symbol for this symbol position.

"flag/flag_primaryfiles_moe$(MOE)_moc$(MOC)_iu$(IN_USE_BY_OTHER)" = The icon file.

Attributes of the fourth subelement <icondef> from subelement <icon>




icon_group "released"Identification of a symbol group. Depending on the status, othersymbols can be represented.

"released" = This is the "Released" symbol.

use_status_color "no"Turns the symbol color on or off. This attribute allows the correctdisplay in filter lists.



icon_identifier "flag/doc_is_released"Path to determine the icon file, which contains the applicablesymbol for this symbol position.

"flag/doc_is_released" = The icon file.

Attributes of the fifth subelement <icondef> from subelement <icon>




icon_group "blocked"Identification of a symbol group. Depending on the status,other symbols can be represented.

"blocked" = This is the "Blocked" symbol.

use_status_color "no"Turns the symbol color on or off. This attribute allows thecorrect display in filter lists.


icon_identifier "flag/doc_is_blocked" = Theicon file.

Path to determine the icon file, which contains the applicablesymbol for this symbol position.

"flag/doc_is_blocked" = The icon file.

Attributes of the fifth subelement <icondef> from subelement <icon>


icon_position "3"Position des Symbols im Dokumenteintrag im Baum.


icon_group "inchange"Identification of a symbol group. Status-depending, other symbolscan be represented.

"inchange" = This is the "In Change" symbol.



icon_identifier "flag/doc_is_in_change"Path to determine the icon file, which contains the applicablesymbol for this symbol position.

"flag/doc_is_in_change" = The icon file.

Attributes of the seventh subelement <icondef> from subelement <icon>




icon_group "archived"Identification of a symbol group. Depending on the status, othersymbols can be represented.

"archived" = This is the "Archived" symbol.




icon_identifier "flag/doc_is_archived"Path to determine the icon file, which contains the applicablesymbol for this symbol position.

"flag/doc_is_archived" = The icon file.

Attributes of the eighth subelement <icondef> from subelement <icon>








icon_identifier "flag/flag_primaryfiles_moe$(MOE)_moc$(MOC)_iu$(IN_USE_BY_OTHER)"


"flag/flag_primaryfiles_moe$(MOE)_moc$(MOC)_iu$(IN_USE_BY_OTHER)" = The icon file.

Attributes of the ninth subelement <icondef> from subelement <icon>






use_status_color "yes"Turns the symbol color on or off. This attributeallows the correct display in filter lists.

"yes" = The symbol color for this icon is on.

icon_identifier "flag/flag_material_$(MATX)$(MAT_AMB)"


"flag/flag_material_$(MATX)$(MAT_AMB)" = Theicon file.

referenced_object "material"

Determines if the determination of symbolcolors of the document status or materialstatus is used.

"material" = The material status will be used.


Attributes of the first subelement <icondef> from subelement <icon>




icon_group "default"Identification of a symbol group. Depending on the status, othersymbols can be represented.




icon_identifier "flag/flag_$(DRAW)"Path to determine the icon file, which contains the applicable symbolfor this symbol position.

"flag/flag_$(DRAW)" = The icon file.

Attributes of the eleventh subelement <icondef> from subelement <icon>




icon_group "default"Identification of a symbol group. Status-depending, other symbolscan be represented.




icon_identifier "gos_note_flag_$(HGN)"Path to determine the icon file, which contains the applicablesymbol for this symbol position.

"gos_note_flag_$(HGN)" = The icon file.

The subelement <program_options> contains different settings, which control the behavior of the document inthe SAP Engineering Control Center.

Attributes of the <program_options> subelement


show_for_create "yes"Determines whether in dialog "create document " this DType isvisible in the combo box for accessible document types.

"yes" = Document is visible.

has_primary_application "yes"

Determines if document is normal document with original anddesignated Workstation Application or container object foradditional originals without explicit original.

"yes" = the document has an original with the designatedWorkstation application


dirty_flag "yes"Determines if the newly created document has a dirty flag.

"yes" = The document has a dirty flag.

attempt_status_change_on_checkin "yes"

Determines if change of status applies during check in at SAPEngineering Control Center or if SAP System conducts change ofstatus.

"yes" = Change of status by SAP Engineering Control Center.

function_group "DOC"

Sets the Function Group to which the document belongs. Fordocuments with a common Function Group, for example, specificcontext menus can be defined.

"DOC" = This DType is assigned to the Function Group "DOC".

customer_data_section ""

Name of a section in the attribute mapping file that is defined inthe customer-specific data. The data will be displayed in theobject browser under the"Customer Data" tab.

"" = No section has been defined.





Determines which additional originals of the document will be accepted duringcopy but not into copy of document according to a table of identifiers for theWorkstation Application for additional originals all of which are separated bysemicolon.

"ZIP" = Additional originals of type "ZIP" (ZIP-Archive) will not be copied.

use_initial_version "yes"Determines whether the version number of the copy should be set on the originalor on the initial value (as a rule "00").

"yes" = Version number of the copy on which the initial value will be set.

The subelement <new_version> contains settings for versioning of documents .

Attribute to the subelement <new_version> from subelement <program_options>


status_list "AC;RE"Determines the type of document status that allows versioning of documents. Alist of document statuses can be given separateed by ";".

"AC;RE" = With this type of document status new versions are allowed.


Determines which additional originals of the document will not be accepted intoa new version of document during versioning, according to a list of identifiers forthe Workstation Application which are separated by semicolons.

"ZIP" = Additional originals of type "ZIP" (ZIP-Archive) will not be copied.

The subelement <document_create> contains settings that control the way in which the document is createdin SAP.


Attributes to the subelement <document_create>


create_with_SAP_GUI "no"Determines if SAP GUI should be openedwhen creating a document.

"no" = Do not open SAP GUI.

create_multi_allowed "no"

Determines whether mass creation ofdocuments of this type is allowed.

"no" = Mass creation of this document isnot permitted.

document_number_assignment "internal"

Determines the document numberassignment in SAP.

"internal" = SAP assigns the numberautomatically.

initial_document_number ""

The value of this field has no value whenthe number is internally assigned. Thisvalue is entered as a prefix in the inputfield of the document system dialoguewhen the number is externally assigned.The user can delete/change the prefix atany time.

"" = Empty, since there is no value,because document_number_assignment= "internal".

document_type "CPA"SAP document type for the newly createddocument.

"CPA" = CAD parameter document.

show_classification_pane "yes"

Shows or hides the classification panel inthe document creation dialog.

"yes" = Show classification panel in thedocument creation dialog.

initial_document_part "000"

SAP document part or a semicolon-separated list of SAP document parts forthe newly created document. If a list ofdocument parts has been specified, thena documentation system dialog for one ofthe document parts can be selected froma dropdown box in the SAP EngineeringControl Center.

"000" = Initial values for the documentpart.

part_editable "yes"

Defines whether the documentationsystem dialog for the default value or theselected SAP document part from the"initial_document_part" attribute can bechanged in the input field from within theSAP Engineering Control Center.

"yes" = The default value can bechanged.


initial_document_version "00"

SAP document version or a semicolon-separated list of SAP document versionsfor the newly created document. If a list ofdocument versions has been specified,then a documentation system dialog forone of the document versions can beselected from a dropdown box in the SAPEngineering Control Center.

"00" = Initial document version.

version_editable "no"

Determines whether the documentationsystem dialog for the default value for thedocument version can be changed fromthe "initial_document_version" attributewithin the SAP Engineering ControlCenter.


change_to_after_create_status ""Returns the initial status for the newlycreated document.

"" = No initial status given.

filename_template_base "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)"

Determines the composition of the filename for the original document. Thefollowing place holders are possible:$(DOCNUMBER) = document number,$(DOCTYPE) = document type, and$(DOCPART) = document.

"$(DOCNUMBER)$(DOCTYPE)$(DOCPART)"= rules for the naming of the data files.

filename_template_version ""

Determines the composition of thedocument version in the file name for theoriginal of this document. The followingplaceholder can be used: $(DOCVERSION)= Document version.

"" = The document version will not beused.

The <seedfile> subelement contains settings for the template file. Several template files can be assigned, inother words the <seedfile> may occur more than once. This includes the <description> subelement, whichdefines each description text in different languages.

Attributes of the first subelement <seedfile> inherited from the subelement <document_create>Attribute Value Description

filename "@PLM_INSTDIR@\applications\INV\templates\inv-parameter.xls"

When using type="template", this attribute defines the filename of the template file that is used. The name can bespecified as relative or absolut. There must be a file with thisname, or the process will terminate with an error.

"@PLM_INSTDIR@\applications\INV\templates\inv-parameter.xls"= Relative filename to the template file used.

type "template"Determines how the original document will be generated.

"template" = The "filename" attribute is used to specify thetemplate file that is to be used.


default "yes"This determines whether this template file should be used as apreset in the "Create Document" dialog.

"yes" = The template file is preset.

Attributes of the second <seedfile> subelement inherited from the <document_create> subelementAttribute Value Description

filename "@PLM_INSTDIR@\applications\INV\templates\inv-parameter-prefilled.xls"

When using type="template", this attribute defines the file name of thetemplate file that is used. The name can be specified as relative orabsolut. There must be a file with this name, or the process willterminate with an error.

"@PLM_INSTDIR@\applications\INV\templates\inv-parameter-prifilled.xls"= Relative filename to the template file used.

type "template"Determines how the original document will be generated.

"template" = The "filename" attribute is used to specify the templatefile that is to be used.

default "yes"This determines whether this template file should be used as a preset inthe "Create Document" dialog.

"yes" = The template file is preset.

Attributes of the third <seedfile> subelement inherited from the <document_create> subelement


filename ""

When using type="template", this attribute defines the file nameof the template file that is used. The name can be specified asrelative or absolut. There must be a file with this name, or theprocess will terminate with an error.

"" = No data file name specified.

type "select"Determines how the original document will be generated.

"select" = You can select a template file in the "Createdocument" dialog.

default "no"This determines whether this template file should be used as apreset in the "Create Document" dialog.

"no" = No template file is preset.

extension_filter "*.xls,*.xlsx,*.xlsm,*.xlsb"

When selecting a template file with the type="select", thisattribute determines the file extension filter that is used. In thefile selection dialog you can select files that are matched by thefilter.

"*.xls,*.xlsx,*.xlsm,*.xlsb" = List of file extensions.

The subelement <material_create> contains settings for creating a new document from materials.




Determines whether and how a new document is created fromMaterials.

"deferred" = No material is applied to the document. You canattach Materials subsequently to this document.


material_number_assignment "internal"

Defines material number assignment in the SAP system. Thevalues are identical to those for the document numberassignment.


material_type "FERT;HALB"Material type or a ';'-separated list of material types for the newmaterial that is to be created.

"FERT;HALB" = List of SAP material types.

material_template ""Template material with which the material attachments can beprocessed.

"" = No material template specified.

material_plant_assignment ""Initial value for the assigned plant.

"" = No initial plant.

material_default_class ""Indicates the standard class for the material.

"" = No standard class for the material.

The subelement <primary_application> determines which application is assigned to this master document(primary application) and defines the rules for the check in and check out of originals.



primary_workstation_application "XLS" "XLS" = Identification of the SAP workstation application for theoriginal.

attribute_section Defines which attributes from the attribute mapping files aresynchronized during document creation.

"XLS" = Name of the section.

update_attributes_for_ro "yes"Defines the attribute update with the action "Open as read-only".


update_attributes_for_rw "yes"Defines the attribute update for the action "Open for editing".


update_attributes_for_dirty "yes"Defines whether to update the attributes when the dirty flag is set.


The <container_file> subelement defines the characteristics of the ZIP archive which is stored in the documentas a container file. It contains the <plmfile> subelement, which defines the properties for the container file.

Attributes of the subelement <plmfile> inherited from the subelement <container_file> from <primary_application>


extension "ecf"Filters by file name extensions in the file system.

"ecf" = File name extension.


workstation_application "ECF"Filters original documents according to the workstationapplication.

"ECF" = Identification of the workstation application.

description "ECtr containerfile"

Filters original documents according to their description.

"ECtr container file" = Description of originals that will be usedfor filtering.

The subelement <checkout_rules> determines how to treat the original of the document at checkout. Itincludes the subelement <plmfile> that determines the individual additional file types.

Attribute of the <checkout_rules> subelement from the <primary_application> subelement

Parameter Values Description

rename_master_original_at_checkout "no"Defines if the original is renamed during opening according torules for component names.

"no" = Keep file name during opening.

one_version_in_session_only "no"

Determines if this document must have only one version inthe session directory.

"no" = Multiple versions of the document are allowed in thesession directory.

hardlink_in_session "no"Determines if hard link may be used for original document inthe session directory or if a copy must always be created.

"no" = Always create a copy.

The subelement <checkout_direct> defines which of the originals filed directly with the document will betransferred to the additional registery during the action "open for editing".

Attributes of the subelement <plmfile> inherited from the subelement <checkout_direct> from subelelement<primary_application>


workstation_application "TXT"Identification of workstation application for the file type that is to betransferred to the additional directory.

"TXT" = Identification of the workstation application.

The subelement <checkin_rules> determines how files in the additional directory and document originals aretreated when checking in. This is why it has multiple subelements.

Attribute of the subelement <checkin_rules> from <primary_application>


from_application_only "yes" "yes" = Prevents a document from being checked in without CAD in thedesktop view of the ECTR via the context menu.

The subelement <save_direct> determines which additional files (paragraph styles) are stored as originals inthe additional directory when saving. It includes multiple <plmfile> subelements that determine the individualadditional file types.

Attributes of the subelement <plmfile> inherited from the subelement <save_direct> from <checkin_rules>



extension "jpg", "gif"The respective file name extensions of additional files inthe file system.

"jpg", "gif" = The respective file name extensions.

workstation_application "EPJ", "EPG"Workstation application identifiers for each additional style.

"EPJ", "EPG" = Identification of the workstation application.

description "ECtr Preview (jpeg)","ECtr Preview (gif)"

Description of the respective additional file.

"ECtr Preview (jpeg)", "ECtr Preview (gif)" = Description ofadditional files.

The <ignore> subelement determines which files will be ignored when saving. It includes multiple <plmfile>subelements that determine the additional file types to ignore.

Attributes of the <plmfile> subelement inherited from the <ignore> subelement from <save_direct> subelement from<checkin_rules>


extension "bak", "tmp"The respective file name extensions of the additional files to ignore in the filesystem.

"bak", "tmp" = File name extensions of the additional file types.

The subelement <delete_in_sap> determines which original documents should be deleted during check in.This allows for a targeted adjustment of the document. It includes multiple <plmfile> subelements thatdetermine the additional file types to delete.

Attributes of the <plmfile> subelement inherited from the <delete_in_sap> subelement from the <save_direct> subelementfrom <checkin_rules>


workstation_application "EPJ", "EPG", "CGM"Workstation application identifiers for each additional style.

"EPJ", "EPG", "CGM" = Identification of the workstationapplication.

The subelement <delete_in_session> determines which files should be deleted during check in. It includesmultiple <plmfile> subelements that determine the additional file types to delete.

Attributes of the <plmfile> subelement inherited from the <delete_in_session> subelement from the <save_direct>subelement from <checkin_rules>



Filters by file names and regular expressions.

".*\.preview\.jpg", ".*\.preview\.gif" = Filter mask.

extension "cgm"


"cgm" = File name extensions of the additional filetypes.

The <delete_in_session> subelement determines which files should be deleted during check in. It includes


multiple <plmfile> subelements that determine the additional file types to delete.

Attributes of the <plmfile> subelement inherited from the <delete_in_session> subelement from the <save_direct>subelement from <checkin_rules>



Filters by file names and regular expressions.

".*\.preview\.jpg", ".*\.preview\.gif" = Filter mask.

extension "cgm"


"cgm" = File name extensions of the additional filetypes.

The subelement <save_local> determines which additional files (additional styles) are stored in the localdirectory when saving. It includes the subelement <plmfile> that determines the individual additional filetypes.

Attributes of the subelement <plmfile> inherited from the subelement <save_local> from <checkin_rules>


extension "avi"The file name extension of additional files which should be saved locally.

"avi" = File name extension.

The subelement <scripts> contains scripts or programs that run before checking in. The individualscripts/programs are contained in subelement <script>.

Attributes of the subelement <script> inherited from the subelement <scripts> from <checkin_rules>


Name "thumb_console64.exe"Sets the entire call path of the executing program.

"thumb_console64.exe" = Name of the program to be executed.

<script> contains the subelement <params> which determines the parameters to be sent to the executingscript. This includes one or more subelements <param>, which each define a parameter.

Attributes of the subelements <params>, subelement <params>, subelement <script>, subelement <scripts> from<checkin_rules>


Name"-pathFile","-pathThumb","-width","-height"

Contains the name of the defined parameter.

"-pathFile", "-pathThumb", "-width", "-height" = The parameter name.

value"$(masterfile)","$(add_dir)\zmodel.jpg","300","300"

A value can be specified for each parameter, which is passed in thisway to the executed program / script. These may include variable datain the form of placeholders ("$ (...)"), which are resolved beforeexecution.

"$(masterfile)", "$(add_dir)\zmodel.jpg", "300", "300" = Place holderfor the value to be passed.

The subelement <additional_files> determines which additional formats of a document will be displayed and


can be edited in the SAP Engineering Control Center.



enable_additional_files "yes"Determines whether the additional originals are permissable for thisdocument.

"yes" = additional originals are permissible.

The subelement <ignore_files> determines which additional originals of the document in the originalscontainer of a document can NOT be displayed in SAP Engineering Control Center. These includes subitems oftype <plmfile> which define the individual document types.

Attributes of the subelements <plmfile> of the subelement <ignore_files> from <additional_files>


workstation_application "EPJ","EPG"

The identifiers of the types of documents that should not be displayed.

"EPJ", "EPG" = Identification of the document types.

The DType definitions for nonmaster documents

The SAP Engineering Control Center distinguishes between master documents and dependent documents. Thelatter are referred to as non-master documents and are dependent on master documents.

NOTE:It is recommended to maintain only the language English directly in the file "dtype.xml"! All otherlanguages will be offered via the particular "dictionary.txt" file. This affects the definitions ofDTypes and Seedfiles. All elements <description language="XY"> are omitted except Englishwhich are used as fallback.

First the DType-definition for presentations:

DType-definition for non-master-documents of type "IPNNM"

<DType type="nonmaster" identifier="IPNNM" include_template="IPNTL" application_type="INV"application_role="D">...</DType>

Attribute of the element <DType> of the DType definition "IPNNM" template definition


type "nonmaster"Determines the kind of DType definition.

"nonmaster" = It relates to the definition for non-master documents.

identifier "IPNNM"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one and five characters long.

"IPN" = ID of this DType definition.


include_template "IPNTL"


"IPTML" = The DType template with the ID "IPTML" from this "dtype.xml" fileis included.






The <nonmaster_options> subelement specifies whether a dependent document is linked to the material ofthe master document.

Attributes of the subelement <nonmaster_options>


depends_on_master "yes"Determines whether the content of the dependent document depends onthe content of the master document

"yes" = Nonmaster document depends on the master document.

link_to_master_material "no"

Determines whether the dependent document receives an object link to thematerial of the master document.

"no" = Do not create an object link from the material of the masterdocument to this dependent document.

The sub-element <document_create> contains settings that control the way in which the document is createdin SAP.

Attributes to the sub-element <document_create>


document_type "IPN"SAP document type for the newly created document.

"IPN" = Inventor Presentation document.

document_number_assignment "internal"Determines the document number assignment in SAP.

"internal" = The number is assigned internally.




material_creation_method "deferred"Decides whether and how a material is created for a newdocument."deferred" = No material is created for the document. However,a subsequent material creation is possible.


material_number_assignment "master"

Defines the material number assignment in the SAP system (thevalues are identical to those of the document numberassignment).

"master" = Material number is taken from the master.

material_type "FERT;HALB" Type or types of material as defined in the SAP system."FERT;HALB" = List of material types.

material_template ""Template material with which the material can be created.

"" = No template material specified.

material_plant_assignment ""Initial value for the assigned plant.

"" = No initial plant assigned.

material_default_class ""Defines a default class for the material, as defined in the SAPsystem

"" = No standard class defined.

Now the DType definition for Nonmaster Drawings ("INM")

DType-definition for non-master-documents of type "IDWNM"

<DType type="nonmaster" identifier="IDWNM" include_template="IDWTL" application_type="INV"application_role="D">...</DType>

Attribute of elements <DType> of DType definition "IDW"




identifier "IDWNM"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one to five characters long.

"IDW" = ID of this DType definition.

include_template "IDWTL"


"IPWTL" = The DType template with the ID "IPWTL" from this "dtype.xml" fileis included.











"1" = Far left, "6" = Far right.

icon_group "default"Identification of a symbol group. Other symbolscan be displayed depending on their status.


icon_identifier "{0}/tree/inv/inventor_drawing$(NM_OLD)"


"{0}/tree/inv/inventor_drawing$(NM_OLD)" = Theicon file.




depends_on_master "yes"Determines whether the content of the dependent document depends onthe content of the master document.

"yes" = Nonmaster document depends on the master document



"no" = Do not create an object link from the material of the masterdocument to this dependent document




document_type "INM"SAP document type for the newly created document.

"INM" = Inventor Presentation document.

document_number_assignment "master"Determines the document number assignment in SAP.

"master" = The number will be taken up by master document.





Decides whether and how a material is created for a newdocument.

"deferred" = No material is created for the document. However,a subsequent material creation is possible.


material_number_assignment "master"Defines the material number assignment in the SAP system (thevalues are identical to those of the document numberassignment)"master" = Material number is taken over from the master.

material_type "FERT;HALB"Type or types of material as defined in the SAP system.

"FERT;HALB" = List of material types.



material_plant_assignment ""Initial value for the assigned work.

"" = No initial work assigned.



Finally, the DType definition for Nonmaster drawings ("DWG") follows:

DType-definition for non-master-documents of type "IDWGN"

<DType type="nonmaster" identifier="IDWGN" include_template="IDWGT" application_type="INV"application_role="D">...</DType>

Attribute of elements <DType> of DType definition "IDWNM"




identifier "IDWGN"Non-ambiguous ID string for this DType definition within the entire XMLdocument. The ID has to be between one to five characters long.

"IDWGN" = ID of this DType definition.

include_template "IDWGT"


"IDWGT" = The DType template with the ID "IDWGT" from this "dtype.xml"file is included.











"1" = Far left, "6" = Far right.

icon_group "default"Identification of a symbol group. Other symbolscan be displayed depending on their status.


icon_identifier "{0}/tree/inv/inventor_drawing$(NM_OLD)"


"{0}/tree/inv/inventor_drawing$(NM_OLD)" = Theicon file.




depends_on_master "yes"Determines whether the content of the dependent document depends onthe content of the master document.

"yes" = Nonmaster document depends on the master document.



"no" = Do not create an object link from the material of the masterdocument to this dependent document




document_type "INM"SAP document type for the newly created document.

"INM" = Inventor Nonmaster Drawing document.

document_number_assignment "master"Determines the document number assignment in SAP.

"master" = The number will be taken up by master document.





Decides whether and how a material is created for a newdocument.

"deferred" = No material is created for the document. However,a subsequent material creation is possible.


material_number_assignment "master"Defines the material number assignment in the SAP system (thevalues are identical to those of the document numberassignment)"master" = Material number is taken over from the master.

material_type "FERT;HALB" Type or types of material as defined in the SAP system."FERT;HALB" = List of material types.



material_plant_assignment "" Initial value for the assigned work."" = No initial work assigned.



options.xml

Any user can individually apply settings which control the behavior of the SAP Engineering Control Center. Thiscan be done in the "Preferences" dialog, which can be opened in the system bar via the menu "Settings ->Preferences" of the SAP Engineering Control Center.

ECTR menu "Settings"

There you will find setting options referring to interaction between SAP Engineering Control Center and denSAP Engineering Control Center Interfaces for individual CAD systems. For each installed interface, a node ispresent in the tree on the left side:


ECTR dialog "Preferences"

The CAD-specific data file "options.xml" determines the options that are given for the particular CAD system.We are talking about parameters, which a part of the CAD-specific data file "default.txt" and which are pre-allocated with a standard value.

Settings made under "Settings -> Preferences" in the menu will be saved in the file "user.txt" for every user intheir specific ECTR work directory, under the sub-menu "preferences" (the exact path:" % A P P D A T A % \ S A P \ E C T R \ d a t a \ < < E C T R - V e r s i o n > > \ < < S A P -Server_Mandant_Username>>\preferences\user . txt") .

ATTENTION:The settings made via the menu "Settings -> Preferences" and stored in the file "user.txt" foreach user in his ECTR working directory override the standard settings from the configuration file"default.txt"! If the default values from the "default.txt" are to be used again, the options must bedeleted from the user-specific file "user.txt" after exiting ECTR!

The file "options.xml" has the following structure:


Structure of the file "options.xml"

<options> <structure> <node label="..."> <node card="<<Card X>>"/> <node card="<<Card Y>>"/> ... </node> </structure> <card name="<<Card X>>"> <option label="..." type="..." prefname="..." tooltip="..."/> <option label="..." type="..." prefname="..." tooltip="..."> <entry name="..." value="..."/> <entry name="..." value="..."/> <entry name="..." value="..."/> </option> ... </card> <card name="<<Card Y>>"> <option label="..." type="..." prefname="..." tooltip="..." maxchars="..."> <entry name="..." value="..."/> <entry name="..." value="..."/> </option> <option label="..." type="..." prefname="..." tooltip="..." maxchars="..."/> ... </card> ...</options>

The elements <structure> define the entry on the left side of the options dialogue within the tree diagram.This must contain a sub-element <node> which describes specifically the node.

Attributes of element <node>


label="..." Name (Optional) If the attribute exists, a folder icon with the given name will appear.Below you will find the cards arranged under a branch, defined as in the following.

card="..." Cardidentifier

Defines an entry in the tree diagram, which contains changeable parameters(preferences), and which will appear on the right when clicked. The adjustableparameter will be defined in the corresponding element <card>.


All elements <node> should have a label! It is recommended that you do not write the text forthe label in plain text into this XML file, but instead reference a corresponding dictionary identifier.Then, depending on the language set in the ECTR, the appropriate text is always read from therespective file "dictionary.txt".Example options.xml:

<node label="Inventor"> <node card="Miscellaneous" label="plm.options.card.misc"/> <node card="Application structure"label="plm.options.card.application.structure"/> . . .</node>

Dictionary identifiers can and should also be used for the following attributes: <option label="...">, <option tooltip="..."> and <entry name="...">Example dictionary.txt:

# Preference keys from options.xmlplm.options.card.misc=Verschiedenesplm.options.card.application.structure=Applikationsstruktur . . .

With the element <card> you define the options that can be reached under the respective card note. Theassignment is done via name of card.

Attribute of element <card>

Attribute Value Descriptionname="..." Name Name of Card, like in the element <node>

The sub-element <option> always defines one option that appears on the card. Here you allocate a parameter(preference) from the CAD-specific file "default.txt" as well as the possible value area. In doing so, an emptyediting field will appear or a list of values will apply.

Attributes of sub-element <option>


label="..." Name or description ofthe option

Description of the option as appears on the card under"Description"

type="..." Data type file type of the option. The following are possible:"string", "boolean", "long"

prefname="..." Parameter name The complete name of the preference from file "default.txt"

tooltip="..." Description of the option (Optional) Description of the option. Appears as tooltip, whenmouse cursor is positioned on the option

maxchars="..." Number (Optional) Maximum possible number of signs or characterswithin an editing field

If you want to present a list of possible values, you have to enter the sub-element <entry> which might occurrepeatedly.


Attributes of sub-element <entry>

Attribute Value Descriptionname="..." Name Name of value in the list

value="..." Value according to attribute "type" from element<option> Value, which is given to parameter at choice

If you place the attribute "maxchars" within the element <option> and at the same time you put values over<entry>, an edit field appears. But for entries, which are identical to the values that are connected to theattribute "name", the values set in the attribute "value" will be given to the parameter.

ATTENTION:When adding new settings to this file, note the following: Some preferences are cached by theinterface, so that an update of the value is not guaranteed during operation! However, all settingsin the standard delivery of the file "options.xml" can be changed during operation.

plm_setenv.bat

The file "plm_setenv.bat" serves to set environment variables. These can then be evaluated from the SAPEngineering Control Center Interface to Inventor after launch. As this deals with a traditional batch file,command line instructions such as "set" and "if" can also be used here, as well as contents of already existingenvironment variables, with the notation "%<<Variable name>>%".

On default, the "plm_setenv.bat" file contains the default values of the environment variables supported by theinterface:

Default values in the file "plm_setenv.bat"

set USE_SIMPLE_DIALOG=1set PLM_LOG_INTERFACE_DUMP_DOC_STRUCTURE=false

The variable "USE_SIMPLE_DIALOG" can have the values '0' - '5' and determines whether a simple loadingdialog for ECTR and CAD processes (values '1' - '5') should be displayed in the user interface instead ofdetailed status messages (value '0').

ATTENTION:The file "plm_setenv.bat" is only executed if the CAD system is started from ECTR, i.e. either viathe menu "System->Launch Application->Start Inventor" or by opening a document in theApplication Structure etc. If Inventor is started without ECTR or the connection to ECTR isestablished later, setting environment variables via the file "plm_setenv.bat" does not work!

rfc-tunnel-whitelist.txt

The configuration file "rfc-tunnel-whitelist.txt" contains a list of all RFC function modules that can be called bythe SAP Engineering Control Center Interface to Inventor via the ECTR. Calling RFC function modules that arenot contained in this list is rejected with an error. With this white list, the SAP Engineering Control CenterInterface to Inventor follows the security concept of the ECTR and enables you to ensure that only permittedRFC function modules can be executed.

The standard configuration includes the following RFC functions that are allowed to be executed:


/DSCSAG/MM_GETNONMASTER2CDESK_SRV_MODIFY_INST_DATA

The wildcard character '*' is allowed when specifying the RFC function. This makes it possible tospecify entire groups of RFC functions that have the same prefix in their names, for example.

Loading rules for opening documents (load_scenarios.xml)

Since ECTR version 5.1.11.0 it is possible to combine different "explosion scenarios" with different loadingoptions for documents in CAD applications. The prerequisite for this is that a corresponding explosion scenarioexists in SAP.

Detailed information on this topic can be found in the article "How to configure different loadscenarios" in the SAP Community Wiki.

It is therefore possible to define different rules for loading different document types for the SAP EngineeringControl Center Interface to Inventor. The optional configuration file "load_scenarios.xml" must be created inthe directory "..\customize\config". In this file, corresponding loading rules are described as in the followingexample:

https://wiki.scn.sap.com/wiki/display/PLM/How+to+configure+different+load+scenarios



Example for the file "load_scenarios.xml"

<?xml version="1.0" encoding="utf-8"?><document_load_scenarios xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../../basis/aux-files/load-scenarios.xsd"> <document_load_scenario> <name>EXAMPLE_LOAD_SCENARIO</name> <description>Example LoadScenario</description> <application_type>INV</application_type> <bod_explosion> <explosion_scenario>CAD_LOAD</explosion_scenario> <explosion_rule> <active/> </explosion_rule> </bod_explosion> <application> <option> <name>DesignViewRepresentation</name> <value>0</value> </option> <option> <name>PositionalRepresentation</name> <value></value> </option> <option> <name>LevelOfDetailRepresentation</name> <value>1</value> </option> <option> <name>DeferUpdates</name> <value>false</value> </option> <option> <name>ImportNonInventorDWG</name> <value>true</value> </option> <option> <name>OpenExpress</name> <value>false</value> </option> <option> <name>SkipAllUnresolvedFiles</name> <value>false</value> </option> <option> <name>DeferFlatPatternUpdate</name> <value>true</value> </option> </application> </document_load_scenario></document_load_scenarios>

The element <document_load_scenario> describes the load rule.

Attributes of element <document_load_scenario>

Attributes Value (example) Description


name "EXAMPLE_LOAD_SCENARIO"

Name of the load scenario defined here.

"EXAMPLE_LOAD_SCENARIO" = Name.

HINT:The name can be used to store this load rule via theconfiguration file "menu_macros.txt" as a command in thecontext menu in the "Desktop" view of the ECTR (see "How toconfigure different load scenarios").

description "Example Load Scenario" Description of this load scenario.


Identifier for the application that is responsible for thisdocument. This application opens the file from the SAPEngineering Control Center.


The sub-element <bod_explosion> describes the corresponding explosion scenario, which must be defined inSAP.

Attribute of element <document_load_scenario>Attribute Value (example) Description

explosion_scenario "CAD_LOAD"

Name of the corresponding explosion scenario.

"CAD_LOAD" = Name.

ATTENTION:An explosion scenario with the name specified here must exist in SAP! For more information on explosionscenarios, see "How to configure different load scenarios").

The sub-element <application> contains several sub-elements <option>, which describe the individualaspects of the loading rule.

Attributes of the 1. element <option>


name "DesignViewRepresentation" Defines the design view representation for the document to beloaded.

value '0'

The following values can be set:

'0' = Last Active'1' = Master'2' = All Visible'3' = Nothing Visible'4' = Defaultn = n own design views



name "PositionalRepresentation" Defines the name of the positional representation for the documentto be loaded.

value "" The name as text. Can also be empty!


Attributes Value (example) Descriptionname "LevelOfDetailRepresentation" Specifies the level of detail for the document to be loaded.





value '0'

The following values can be set:

'1' = Master'2' = All Parts Suppressed'3' = All Components Suppressed'4' = All Content Center Suppressedn = n own Level Of Details


Attributes Value (example) Descriptionname "DeferUpdates" Specifies whether to defer updates.

value "false" "true" = Yes"false" = No


Attributes Value (example) Descriptionname "ImportNonInventorDWG" Specifies whether to import non Inventor DWGs.

value "true" "true" = Yes"false" = No


Attributes Value (example) Descriptionname "OpenExpress" Specifies whether to use Express Load.



Attributes Value (example) Descriptionname "SkipAllUnresolvedFiles" Determines whether all unresolved references should be skipped.



Attributes Value (example) Descriptionname "DeferFlatPatternUpdate" Specifies whether to defer the FlatPattern update.

value "true" "true" = Yes"false" = No

Version information

To gain an overview of the imported changes of the relevant releases of the SAP Engineering Control CenterInterface to Inventor, the changes are listed here in the configuration files "default.txt" and "dtype.xml".

The following table contains changes in parameters in the configuration file "default.txt". The status showswhether the relevant parameter in this version was added ( ), changed ( ) or deleted ( ). When changing aparameter, merely a new parameter name is given.

Changes in configuration file "default.txt"


Version Status Parameter02.29.136.00 plm.options.MacroName.GetRelatedPresentations.INV

02.25.102.00

plm.options.InventorProjectName.INVplm.structure.application.displaysubstitutestructure.INVplm.options.SaveAs.CheckInAfterCreate.INVplm.structure.application.ExpandDocumentsOnlyOnce.INVplm.options.Cancel.LoadedParts.INVplm.options.Save.LoadedParts.INVplm.options.CloseDocumentAfterSapSaveDisplay.INV

02.24.100.00 plm.structure.application.show.drawing.container.ontop.INV

02.23.97.00plm.options.Thumbnail.INV.jpg.<preference>plm.options.importOnDemand.TransferAttributesToSAP.INVplm.options.StructureAnalysis.MinimumErrorLevel.INVplm.options.structureAnalyze.showDialogForMissingReferences.INV

02.21.91.00 plm.options.SaveAsNewDocument.Replace.INV

02.21.90.00

plm.structure.application.DisplaySuppressedComponents.INVplm.structure.application.show.drawing.INVplm.structure.application.loadDrawings.INVplm.structure.application.show.drawing.container.INVstructure.view.INV.generic.object.DRAW_CONTAINER.namestructure.view.INV.generic.object.DRAW_CONTAINER.iconplm.options.SaveAsNewDocument.CancelSourceFile.INVplm.options.MacroName.MapAttributesMacroName.INVplm.options.checkForUpdates.before.CheckoutEdit.MultiLevel.INVplm.options.checkForUpdates.before.CheckoutEdit.ExplosionScenario.INV

02.20.88.00 plm.options.bom.InsertVirtualBOMHeader.INV

02.19.85.00

plm.options.Logging.LogPerformanceTrace.INVplm.document.dtype.FactoryDesign.Asset.IPT.INVplm.document.dtype.FactoryDesign.Asset.IAM.INVplm.document.dtype.FactoryDesign.LayoutTemplate.INVplm.options.bom.InsertVirtualBOMHeader.INVplm.options.MacroName.GetRelatedDrawings.INV

02.18.77.00

plm.appl.startViewerCommand.INVplm.options.UpdateAttributes.RefreshContext.INVplm.options.DisableDirtyHandlingForWritingComponentIDs.INVplm.options.CommandContext.UseActiveDocument.INVplm.options.SaveAsNewDocument.SubstitutePartHandling.INVplm.options.Ballooning.InitializeBalloonWith.INV

02.18.71.00 plm.options.TransferCadQuantities.INVplm.options.bom.UseAutoBomItemGroup.INV

02.18.70.00plm.options.bom.UsePrefixAsCategory.INVplm.options.Thumbnail.INV.jpg.<preference>plm.options.Thumbnail.ViewOrientation.INV

02.16.58.00

plm.options.TemplateFiles.INVplm.options.TransferCadPosNr.INVplm.options.ImportOnDemand.DeleteOriginals.INVplm.options.ImportOnDemand.CheckInAfterCreate.INVplm.control.partnameRules.applExtension.INV


Version Status Parameter

02.15.57.00

plm.bom.create.IDWplm.bom.createAtCheckin.IDWplm.bom.updateAtCheckin.IDWplm.bom.update.IDWplm.bom.create.IPNplm.bom.createAtCheckin.IPNplm.bom.updateAtCheckin.IPNplm.bom.update.IPNplm.bom.create.IAMplm.bom.createAtCheckin.IAMplm.bom.updateAtCheckin.IAMplm.bom.create.IPTplm.bom.createAtCheckin.IPTplm.bom.update.IPTplm.bom.create.INMplm.bom.createAtCheckin.INMplm.bom.updateAtCheckin.INMplm.bom.update.INMplm.options.bom.InsertVirtualBOMHeader.INVplm.options.BOMTable.AddNonExistingColumns.INVplm.options.checkIn.UpdateAttributesFromSAP.INVplm.options.SaveAsNewDocument.Replace.INVplm.options.OpenInsert.UseLastActiveLevelOfDetail.INVplm.options.OpenInsert.ViewRepresentation.INV

02.14.55.00

plm.options.DeferUpdateOnCheckin.INVplm.options.ContentCenterPrimaryLanguage.INVplm.options.MissingReferenceReloadOption.INVplm.options.SapSaveAsNewDocumentForCadSaveAs.INVplm.options.SapSaveAsNewDocumentForCadSaveCopyAs.INVplm.appl.startup.parameters.INVplm.appl.startup.[paramX].INVplm.execute.additional.INVplm.options.OpenInsert.UseLastActiveLevelOfDetail.INVplm.structure.application.DisplayExternalReferences.INVplm.document.dtype.<library name><type>.INVplm.appl.qat.INVplm.appl.language.INVplm.options.OverwriteDTypeUpdateAttributeSettings.INVplm.options.BOMTable.Column.INV.Materialplm.options.BOMTable.Column.INV.Postext1plm.options.BOMTable.Column.INV.Postext2plm.options.BOMTable.Column.INV.OtherColumnplm.options.command.SynchronizeDrawingAssemblyBOM.INVplm.options.ChangeDtype.INVplm.options.Ballooning.BalloonContent.INVplm.options.Thumbnail.Size.INVplm.options.ForceTemplateProject.INVplm.convert.additional.INV.<CONVERT_TYPE>.filenameFormat

02.13.53.00 plm.options.SapSaveAsNewDocumentForCadSaveAs.INV

02.11.47.00

plm.options.CheckinOnCadClose.INVplm.options.SapSaveIntermediateForCadSave.INVplm.options.CloseDocumentAfterSapSaveDisplay.INVplm.options.CreateDirDuringMakeDrawingOrAssemblyFromPartOrAssembly.INVplm.document.PresentationAsNonMaster.INVplm.options.MakeComponents.CreateDark.INV


Version Status Parameter02.10.44.00 plm.options.MakeComponents.TargetAssemblyHandling.INV02.10.42.00 plm.options.OpenInsert.ShowLoadOptionsDialog.INV02.09.41.00 plm.document.dtype.Mold.INV

02.09.39.00

plm.options.new.SaveActiveDocument.INVplm.document.addcomponent.allowed.dTypeList.INVplm.options.MakeComponents.AttributesToCopy.INVplm.convert.additional.INV.IPTplm.convert.additional.INV.FlatPatternDXF.optionsplm.convert.additional.INV.IPT.FlatPatternDXF.AcadVersion

02.08.37.00

plm.options.structureAnalyze.showDialogForMissingReferences.INVplm.document.dtype.Weldment.INVplm.options.open.UseMultiSearchForSapOpen.INVplm.options.SapOpenForLoadDrawing.INVplm.options.new.SaveActiveDocument.INVplm.options.TemplateProject.INV

02.07.30.00 plm.options.importOnDemand.updateAttributes.INV

02.06.27.00

plm.options.SapOpenForCadPlaceDocument.INVplm.document.dtype.SheetMetal.INVplm.options.importOnDemand.resetOccurrenceName.INVdefault.txt plm.options.EmbedExcelOnInsert.INVplm.structure.application.init.strategy.levels.INVplm.options.Thumbnail.ViewOrientation.INV

02.05.25.00

plm.options.updateAttributes.useInteropPrefix.INVplm.options.importOnDemand.loadDrawings.INVplm.options.save.loadDrawings.INVplm.structure.application.DisplayPosItem.INVplm.options.save.saveExternalReferencesplm.options.deliverOnlyRequestedAttributesToSAP.INVplm.options.importOnDemand.TransferAttributesToSAP.INVplm.structure.application.LoadDrawings.INVplm.options.Open.CopyFeaFiles.INVplm.options.SapOpenForCadOpenDocument.INVplm.document.dtype.Default.IPT.INVplm.document.dtype.Default.IAM.INVplm.document.dtype.Default.DWG.INVplm.document.dtype.Default.IPN.INV

02.04.24.00plm.structure.application.sendInstancesForGeneric.INVplm.structure.application.AdditionalAttributes.INVplm.structure.application.DisplayAdditionalAttributes.INVplm.structure.application.CollectEntries.INV (Name changed!)

02.03.22.00

plm.structure.node.CUAPOB_INV_MATERIAL.icon.1plm.structure.node.CUAPOB_INV_MATERIAL.icon.2plm.structure.node.CUAPOB_INV_MATERIAL_NEW.icon.1plm.structure.node.CUAPOB_INV_MATERIAL_NEW.icon.2plm.structure.node.CUAPOB_INV_VIRTUAL.icon.1plm.structure.node.CUAPOB_INV_VIRTUAL.icon.2plm.structure.node.CUAPOB_INV_VIRTUAL_NEW.icon.1plm.structure.node.CUAPOB_INV_VIRTUAL_NEW.icon.2

02.01.20.00 plm.options.ApplicationStructure.CollectEntries.INVplm.options.CreateDIRForNewDocument.INV


Version Status Parameter

01.03.18.00 plm.document.dtype.iPartFactory.INVplm.document.dtype.iAssemblyFactory.INV

01.03.16.00plm.options.openAllReferencesToReadInstanceIDs.INVplm.document.SaveAsNewDocument.CheckOutTop.INVplm.doc.cancel.restore.files.INV

01.00.14.00 plm.options.importOnDemand.updateAttributes.INV01.00.03.00 plm.control.partnameRules.applExtension.INV

The following table contains changes in the configuration file "dtype.xml":

Changes in configuration file "dtype.xml"

Version Description

02.12.48.00

The template definitions for "INMDL", "INDRW", "IPTML" and "IAMLT" as well as the masterdocument definition "CPA" have got the attribute from_application_only="yes" in theircheckin_rules.

ATTENTION:The attribute "from_application_only" can only be processed from ECTR version 5.1.10onwards, an older ECTR version terminates with an error message!If you are working with an older ECTR, you should use the file "dtype.5.1.9.xml" instead of thecurrent "dtype.xml", which is located in the directory "template_customize".

02.09.39.00It is recommended to maintain only the language English directly in the file "dtype.xml"! Allother languages will be offered via the particular "dictionary.txt" file. This affects the definitionsof DTypes and Seedfiles. All elements <description language="XY"> are omitted exceptEnglish, which are used as fallback.

The following table contains changes in the batch file "plm_setenv.bat" for Inventor:

Changes in the batch file "plm_setenv.bat"

Version Description

02.24.100.00On default, the "plm_setenv.bat" file contains the default values of the environment variablessupported by the interface:set USE_SIMPLE_DIALOG=falseset PLM_LOG_INTERFACE_DUMP_DOC_STRUCTURE=false


Final Remark

This manual is intended to facilitate handling of the product. Since this product is also constantly being furtherdeveloped, only the release status at the time of going to press could be taken into account here. CIDEONSoftware & Services GmbH & Co KG is grateful for information and suggestions provided by users. Please entera SAP ticket in the SAP Support Portal.

This documentation has been prepared with the greatest possible care, but we cannot accept any liability forany defects or errors that may occur.

You can find the current documentation in the SAP Help Portal.

On our homepage you will find further information and news!

CIDEON Software & Services GmbH & Co. KG

www.cideon.com

Copyright (C) 2021 CIDEON Software & Services GmbH & Co. KG. All rights reserved.

No part of this document may be reproduced or copied in any form for any purpose without the expresspermission of CIDEON Software & Services GmbH & Co KG.

https://launchpad.support.sap.com/#incident/create

https://help.sap.com

https://www.cideon.com