SAP Engineering Control Center Interface to AutoCAD - Configuration Manual

Size: px
Start display at page:

Download "SAP Engineering Control Center Interface to AutoCAD - Configuration Manual"

Transcription

1 Configuration Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to AutoCAD SAP Engineering Control Center Interface to AutoCAD manages design data in SAP. Given by the SAP Engineering Control Center Interface, tight integration of the CAD system to the SAP PLM data available to the company at an early stage in the design process are available. Product lifecycle management 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 the components designed in the CAD system. You can configure the SAP Engineering Control Center Interface to AutoCAD in many different ways and adapt it to your own requirements and working methods. This configuration manual presents the possible configurations and describes the procedures and configuration parameters in detail. The current version of the manual can be found in the CIDEON Software Portal.

2 2018. Germany. All Rights Reserved. Contents of this document may not be (totally or partly) reproduced, used or published without previous written agreement by the. Copyright applies to all forms of storage and reproduction, in those the available information flowed in particular on magnetic storage, computer expressions or visual announcements. - 2 / 106 -

3 1 Folder structure and directories Icons for CAD originals in SAP ECTR Prerequisite for the maintenance of material BOMs in AutoCAD Registration-less integration of Add-Ins in the CAD-System Starting AutoCAD from ECTR in the SAP logon language The configuration files Menu definitions menu.guidef menu_macros.txt The files attributes-from-sap.xml and attributes-to-sap.xml attributes-from-sap.xml attributes-to-sap.xml AutoCAD Properties default.txt dtype.xml DType definition for AutoCAD Generic DType definition The DType definition for master documents DType definitions for AutoCAD Mechanical Generic DType definition DType definition for master documents options.xml plm_setenv.bat rfc-tunnel-whitelist.txt Version information Configuration examples Inserting external references Mapping of properties Title block attributes as drawing properties Illustrative approach Creation of the drawing template Reference in the configuration file "dtype.xml" Mapping rules in the configuration file "attributes-from-sap.xml" Publication of the block in the configuration file "default.txt" Title block attributes as separate TBK attributes Illustrative approach Final Remark / 106 -

4 1 Folder structure and directories The SAP Engineering Control Center requires a certain folder structure that is established during the installation process. The system-wide environment variable %PLM_INSTDIR% contains the installation directory of the SAP Engineering Control Center and is set up during installation. Under %PLM_INSTDIR%\applications\ the individual add-ins are stored during their installation in separate subdirectories. %PLM_INSTDIR%\applications\acd is the installation directory of the SAP Engineering Control Center Interface to AutoCAD. For AutoCAD Mechanical %PLM_INSTDIR%\applications\acd is used as installation folder. It contains the following subdirectories which are significant for configuration: %PLM_INSTDIR%\applications\acX\appdata %PLM_INSTDIR%\applications\acX\basis %PLM_INSTDIR%\applications\acX\documentation %PLM_INSTDIR%\applications\acX\templates %PLM_INSTDIR%\applications\acX\template-templates %PLM_INSTDIR%\applications\acX\customize\config %PLM_INSTDIR%\applications\acX\template-customize\config %PLM_INSTDIR%\applications\acX\customize\scripts The directory appdata The SAP Engineering Control Center Interface to AutoCAD has a ribbon bar in CAD next to the main menu that contains its functions as buttons. In the subdirectory icons contained here, all of the symbols used for these ribbon bar buttons can be found in two sizes: 16 x 16 and 32 x 32 pixels. 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 for commands and document information. See also the ECTR documentation "SAP Implementation Guide Icons_EN.pdf". The needed files must be available within the class path of the SAP Engineering Control Center. classes: Contains Java classes that are necessary for interface operation. dictionary: Contains subdirectories with a "dictionary.txt" file with display texts in the supported languages (DE, EN, ES, FR, IT, JA, PT, RU, ZH and ZF). sys: In sys\win\bin the individual interface modules can be found. During the installation of the interface the necessary files will be copied to %ProgramFiles%\Autodesk\ApplicationPlugins to enable AutoCAD to load it as "AutoCAD Plugin". The delivered file "Readme.txt" contains the real path and name of the plugin for manual installation (for further information see Registration-less integration of Add-Ins in the CAD-System). The file "start_application_acx.exe" will not be copied and will be used to start AutoCAD out of the SAP Engineering Control Center. The directory documentation In this directory, the user manuals can be found in both German and English as PDF files. The directories template and template-templates - 4 / 106 -

5 Will create a new document on the SAP Engineering Control Center, so you can choose from a list of templates. These submissions can be found in the directory templates. A pool of various document submissions can be found in the template-templates directory. After re-installation, the contents of both directories are identical. Should new or changed templates be delivered with a patch or an update, they will be stored in template-templates. Should these appear in the above-mentioned lists, the appropriate data must be copied 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 Center Interface to AutoCAD. These are: default.txt dtype.xml options.xml menu.guidef menu_macros.txt plm_setenv.bat attributes-from-sap.xml attributes-to-sap.xml rfc-tunnel-whitelist.txt At the start of AutoCAD, these files are evaluated and override the basic installation of the SAP Engineering Control Center that is filed under %PLM_INSTDIR%\customize\config and add additional CAD-specific configurations that are not included in the basic configuration, for example specific types of documents, workstation applications and menu items. The directory template-customize\config The standard settings are filed as copies in the template-customize\config special directory, which contains homonymous 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 templatecustomize\config directory. Thus, the user settings remain in customize\config. However, this also means that changes and extensions to the configuration are not customized automatically during updates. These must be carried out manually as needed! The directory customize\scripts This directory contains additional batch scripts that extend the check-in and check-out process. 1.1 Icons for CAD originals in SAP ECTR In the SAP Engineering Control Center, information on documents is displayed in the form of icons. In addition to general icons, which are valid for all documents, there are icons especially for the <CAD> object types defined in the configuration file "dtype.xml". Depending on the document status, the background of the object type icons can be colored. Further information about the <CAD> object is placed in the form of overlays over the object type icon. A set of standard icons is delivered in the files "%PLM_INSTDIR%\applications\acd\base\classes\images.jar" (AutoCAD) and "%PLM_INSTDIR%\applications\acm\base\classes\images.jar" (AutoCAD Mechanical). For detailed information on icons in the SAP Engineering Control Center, see the help file "SAP Implementation Guide Icons_EN.pdf", which can be found in the directory - 5 / 106 -

6 "%PLM_INSTDIR%\documentation\Manuals\en" or in the ECTR menu under "Help->Display Documentation" in the section "SAP Engineering Control Center". The configuration file "dtype.xml" defines which icons are displayed and in which order the icons are displayed for each DType. The status-dependent background color of the object type icons is defined in the global configuration file "default.txt" of the SAP Engineering Control Center. Displayed icons can be supplemented with overlay icons to visualize certain states in which the displayed objects are located. For the meaning of these symbols, refer to SAP's ECTR documentation. The following table provides an overview of the standard symbols for AutoCAD: Icons for AutoCAD supplied as standard Symbol Description File name in "images.jar" AutoCAD document DType: Document symbol position 1 AutoCAD Sheet Set document DType: Document symbol position 1 AutoCAD document Workstation Application ACD AutoCAD Sheet Set document Workstation Application DST Point Cloud document Workstation Application ACP DWF document Workstation Application DWF AutoCAD DXF document Workstation Application DXF AutoCAD application Menu: System\Start Application\AutoCAD tree\acd\autocad_drawing_16.png tree\acd\autocad_sheetset_16.png tree\file\obr_tree_file_acd.png tree\file\obr_tree_file_dst.png tree\file\obr_tree_file_acp.png tree\file\obr_tree_file_dwf.png tree\file\obr_tree_file_dxf.png small\app_autocad.png The following table provides an overview of the standard symbols for AutoCAD Mechanical: Icons for AutoCAD Mechanical supplied as standard Symbol Description File name in "images.jar" AutoCAD Mechanical document DType: Document symbol position 1 AutoCAD Mechanical Sheet Set document DType: Document symbol position 1 AutoCAD Mechanical document Workstation Applikation ACM AutoCAD Mechanical Sheet Set document Workstation Application DST Point Cloud document Workstation Application ACP DWF document Workstation Application DWF AutoCAD Mechanical DXF document Workstation Application DST tree\acm\acad_drawing_16.png tree\acm\acad_sheetset_16.png tree\file\obr_tree_file_acm.png tree\file\obr_tree_file_dst.png tree\file\obr_tree_file_acp.png tree\file\obr_tree_file_dwf.png tree\file\obr_tree_file_dxf.png - 6 / 106 -

7 AutoCAD Mechanical application Menu: System\Start Application\AutoCAD Mechanical small\app_autocad_mechanical.png 1.2 Prerequisite for the maintenance of material BOMs in AutoCAD The extension described here for CDESK_BOM_WIZARD is only possible on an R3 system! On S4 systems, the module is obsolete and a material BOM must be generated with the new Advanced BOM services! In order to be able to derive material BOMs over the SAP Engineering Control Center Interface to AutoCAD and SAP Engineering Control Center Interface to AutoCAD Mechanical, the use of the function module "CDESK_BOM_WIZARD" for the SAP Engineering Control Center must be enabled. To this end, an extension of the BAdI "CDESK_BOM" for the method "FIND_EXISTING_ITEMS" is necessary. For this purpose, SAP has provided the note , which contains all the necessary information and coding. But the SAP note is required to have been previously imported. The implementation "Z_PLM_ECC" described here must be created manually if it does not already exist! It must be ensured that the implementation is stamped out with the corresponding filters "ACAD" and "ACADM" (filter type "CAD_SYSTEM"). Here is the corresponding code that makes sure the function module "CDESK_BOM_WIZARD" is called up: Extension of the BAdI "CDESK_BOM" in the method "FIND_EXISTING_ITEMS" METHOD if_ex_cdesk_bom~find_existing_items. DATA: lt_add_items TYPE plm_document_tab, lt_add_items_attr TYPE /dscsag/srv_t_fdt_bomitm. FIELD-SYMBOLS: <l_plm_doc> TYPE plm_document, <l_plm_doc_new> TYPE plm_document. CALL FUNCTION '/DSCSAG/CDESK_BOM_WIZARD_GET' TABLES gt_add_items = lt_add_items gt_bomitm_attr = lt_add_items_attr. LOOP AT lt_add_items ASSIGNING <l_plm_doc_new>. <l_plm_doc_new>-index = '1'. LOOP AT plm_documents ASSIGNING <l_plm_doc>. IF <l_plm_doc_new>-index LE <l_plm_doc>-index. <l_plm_doc_new>-index = <l_plm_doc>-index + 1. ENDIF. ENDLOOP. IF <l_plm_doc_new>-is_selected IS INITIAL. <l_plm_doc_new>-is_selected = 'I'. ENDIF. APPEND <l_plm_doc_new> TO plm_documents. ENDLOOP. ENDMETHOD. To check whether the SAP system in use contains the extension, the transaction SE18 can be used: - 7 / 106 -

8 Transaction "SE18": BAdI builder There, the BAdI name "CDESK_BOM" must be entered and under the menu "enhancement implementation" the point "overview" is to be selected. This opens a list of all implementations for "CDESK_BOM": Implementation overview for "CDESK_BOM" On that list, the implementation "Z_PLM_ECC" should be available. If this is not the case, it has to be manually created! Double-clicking on this entry opens the implementation view. Here, the CAD systems "ACAD" and "ACADM" must be entered: - 8 / 106 -

9 Implementation view of "Z_PLM_ECC" Selecting the tab "Interface" leads to a list of implementation methods: - 9 / 106 -

10 List of methods of "Z_PLM_ECC" The method "FIND_EXISTING_ITEMS" should be included on that list. Double-clicking opens the code display. The implementation of the method can be checked here: - 10 / 106 -

11 Code display of "FIND_EXISTING_ITEMS" In addition to the configuration in SAP, the configuration in the respective default.txt must also be checked for maintaining material parts lists. Different settings have to be made depending on the AutoCAD profile. The following settings represents the standard delivery. More information about the individual values can be found in the section on default.txt. AutoCAD plm.mat.properties.acd = MATNR;MATEXTNR;DESCR plm.mat.property.acd.matnr.cadname = SAPMATNR plm.mat.property.acd.matnr.sapname = MARA-MATNR plm.mat.property.acd.matextnr.cadname = MATERIAL plm.mat.property.acd.matextnr.sapname = MATERIAL_EXT plm.mat.property.acd.descr.cadname = DESCR plm.mat.property.acd.descr.sapname = MAKT-MAKTX plm.mat.property.acd.blocknames = MATPOS plm.bom.item.properties.acd = POSTYPE;POSNR;COMPID;QUANTITY plm.bom.item.property.acd.postype.sapvalue = L plm.bom.item.property.acd.posnr.cadname = BOM_ITEM_POSNR plm.bom.item.property.acd.compid.cadname = BOM_ITEM_COMPID plm.bom.item.property.acd.quantity.cadname = BOM_ITEM_QTY AutoCAD Mechanical plm.mat.properties.acm = MATNR;MATEXTNR;DESCR - 11 / 106 -

12 plm.mat.property.acm.matnr.cadname = SAPMATNR plm.mat.property.acm.matnr.sapname = MARA-MATNR plm.mat.property.acm.matextnr.cadname = MATERIAL plm.mat.property.acm.matextnr.sapname = MATERIAL_EXT plm.mat.property.acm.descr.cadname = DESCR plm.mat.property.acm.descr.sapname = MAKT-MAKTX plm.bom.item.properties.acm = POSTYPE plm.bom.item.property.acm.postype.sapvalue = L 1.3 Registration-less integration of Add-Ins in the CAD-System Integration of SAP Engineering Control Center Interface to AutoCAD (Mechanical) in the CAD System happens during the installation, without enabling the requirement of registration of Add-Ins. For this, the content of archives "Release201x.zip", which has been saved by the installation program in the directory %PLM_INSTDIR%\applications\acd\basis\sys\win\bin, is extracted as per %ProgramFiles%\Autodesk\ApplicationPlugins, wherein the content of an already existing installation in the directory \CdnECTRInterfaceAutoCAD.bundle\ is removed. The directory now contains following sub-directories and files: Directories and files in ApplicationPlugins %ProgramFiles%\Autodesk\ApplicationPlugins\ \CdnECTRInterfaceAutoCAD.bundle\ PackageContents.xml \Contents\ CdnECTRInterface_messages_de.txt CdnECTRInterface_messages_en.txt CdnECTRInterface_messages_es.txt CdnECTRInterface_messages_fr.txt CdnECTRInterface_messages_it.txt CdnECTRInterface_messages_ja.txt CdnECTRInterface_messages_pt.txt CdnECTRInterface_messages_ru.txt CdnECTRInterface_messages_zh.txt CdnECTRInterface_messages_zf.txt CdnECTRInterfaceAcd201x.arx CdnECTRInterfaceAcd201x_64.arx CdnECTRInterfaceAcm201x.arx CdnECTRInterfaceAcm201x_64.arx CdnECTRInterfaceRibbon201x.dll plm_conn.dll Details refer to the AutoCAD or AutoCAD Mechanical Release 2017, 2018 and 'x' refers to the corresponding digit. 1.4 Starting AutoCAD from ECTR in the SAP logon language If AutoCAD (Mechanical) is started from within the SAP Engineering Control Center, i.e. using the context menu command "Open original" or by double-clicking on an AutoCAD (Mechanical) document, the CAD system is automatically started in the SAP logon language of the ECTR. The environment variable "%PLM_LANGUAGE%" is responsible for this behavior. This is set by the SAP Engineering Control Center to the SAP logon language and evaluated accordingly when AutoCAD (Mechanical) is started / 106 -

13 Whether the environment variable "%PLM_LANGUAGE%" is evaluated depends on the configuration of the parameter "plm.appl.language.acx" in the configuration file "default.txt". If the SAP logon language for AutoCAD (Mechanical) is not available or unknown, the CAD system is started in the language in which it was last started! - 13 / 106 -

14 2 The configuration files The files contained in the %PLM_INSTDIR%\applications\acd\customize\config directory serve the CAD-specific configurations of the SAP Engineering Control Center. These files are also marked as preference files and are simple text files that can be edited with a simple 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 to AutoCAD with standard settings for this interface. The standard settings are chosen so that typical usage scenarios are covered. Should this not be enough, the reaction of the interface and the SAP Engineering Control Center should adapt appropriately. Next to the central configuration files in %PLM_INSTDIR%\customize\config, each application has its own configuration files in %PLM_INSTDIR%\applications\<<name of application>>\customize\config. The individual files differ from homonymous files in the configuration directory of the SAP Engineering Control Center in that only the respective CAD specificity are controlled through them. During the start of the SAP Engineering Control Center, the standard configuration is read and then overriden with the content of the CAD-specific configuration files. Each interface, if multiple interfaces are installed, has its own set of CADspecific configuration files. For a detailed clarification of purpose, structure and handling of the configuration files, please refer to the SAP Engineering Control Center documentation, specifically the configuration handbook (file "Configuration Guide_EN.pdf") and the operations guide (file "Operations Guide_EN.pdf"), which can be found under %PLM_INSTDIR%\documentation\Manuals\en! 2.1 Menu definitions Menu items that should be available along with the SAP Engineering Control Center Interface to AutoCAD in the user 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\config there are the CAD-specific counterparts, which additionally define appropriate menus for the SAP Engineering Control Center menu.guidef The file "menu.guidef" contains menu items that are available in connection with the SAP Engineering Control Center 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 by the menu identification. The individual functions that appear in the menu are arranged one after the other, in which each menu function is preceded by an equal sign ('='). In each menu definition, macros, which are defined in the file "menu_macros.txt" or in the general macro definition file "%PLM_INSTDIR%\customize\config\menu_macros.txt", are referenced by their names which are preceded by a question mark ('?'). Sub-menus in the menu are designated by indentation of the associated menu entries, for which only blank 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 / 106 -

15 Unlock menu for interoperability between AutoCAD and Inventor As the document type "dwg" can be opened in both AutoCAD and AutoCAD Mechanical as well as Inventor, a special menu for the user interface of the SAP Engineering Control Center can be offered: Interoperability menu for AutoCAD Interoperability menu for AutoCAD Mechanical - 15 / 106 -

16 This is already included in the supplied CAD-specific file "menu.guidef", but still needs to be unlocked. To this end, the out-commenting of the menu definitions marked with "Interop" "om.popup.menu.doc.doc_acd" and "om.popup.menu.doc.doc_acm" for documents and "om.popup.menu.docpos.doc_acd" and "om.popup.menu.docpos.doc_acm" for assemblies are to be removed. Instead, the respective currently active menu definitions comment are to be out-commented (ACAD Mechanical is analogous to AutoCAD here): Menus without interoperability unlocked Menus with interoperability unlocked Definition of the context menu for cloning A context menu is provided for the "Clone" functionality of the SAP Engineering Control Center. Its range of functions are defined using the parameters "om. popup. menu. CLONEPOS. DOC_SLWMDL" (for SOLIDWORKS models) and "om. popup. menu. CLONEPOS. DOC_SLWDRW" (for SOLIDWORKS drawings): - 16 / 106 -

17 Definition of the context menu for "Cloning" # Cloning context menu # om.popup.menu.clonepos.doc_acd = 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.clpbrd.delete = fnc.doc.reload The following functions are possible: Possible functions in the context menu for "Cloning" Parameter 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.clpbrd.delete fnc.doc.reload Function "No Action" "New internal Number" "Extended Clone Options" "Add Component" "Replace Component" "Delete Component" "New Version" "Change Details" "Remove" "Reload" The "cloning" function is universally designed for various CAD systems. Therefore, not every possible function is necessarily useful for every CAD system and document type. Before adding a function to the context menu, this should be checked carefully! It can be useful to configure different context menus for different document types 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 by the macro name. This should be typed using capital letters, to designate it as a macro name / 106 -

18 The individual menu functions belonging to a macro are arranged one after the other, with each menu function being preceded by an equal sign ('='). Other macros can also be referenced by name within a macro definition, and names should be preceded by a question mark ('?'). These macros can either come from this file itself or from the general 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 only blank 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_ACD" and "LAUNCH_APPL_ACM" are required, so that the SAP Engineering Control Center can start the AutoCAD application or AutoCAD Mechanical as needed. 2.2 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 of attributes from SAP to the document and from the document to SAP. For defining the former, use file "attributes-from-sap.xml". For defining the latter, use file "attributes-to-sap.xml". Document attributes and material attributes can be passed. For more information on this topic, see the file "Operations Guide_EN.pdf", chapter: "Attribute Transfer 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 AutoCAD-specific attribute mapping files exist for this purpose: "%PLM_INSTDIR%\applications\acd\customize\config\attributes-from-sap.xml" and "%PLM_INSTDIR%\applications\acd\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 the document. With version of the ECTR the inclusion of the standard section will be adapted in the file "attributesfrom-sap.xml". Before: <section name="generic" default_section="true" description="attribute mapping"> With ECTR version 5.1.7: - 18 / 106 -

19 <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. Possible values are: "STANDARD", "default" und "STDMOD". Various sections can be defined in the CAD-specific attribute mapping file "%PLM_INSTDIR%\applications\acd\customize\config\attributes-from-sap.xml", each of which represents an attribute section that contains defined mappable attributes and their precise treatment. The attribute "name" gives the relationship to the DType description in the file "dtypes.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 Values Description Attribute of element <section> name="..." include_section="..." description="..." Name of attribute division Name of section: "STANDARD", "STDMOD" or "default Description of attribute sections DTypes are referenced to this attribute segment with this name in the file "dtypes.xml". Determines which section will be included from the global "attributes-from-sap.xml" file (%PLM_INSTDIR%/customize/config/attributes-from-sap.xml) in the section defined here. This is a comprehensive description of an attribute section. Within a section, attributes belonging to this attribute section are defined with the sub-element <APPL_ATTRIBUTE> / 106 -

20 Attributes of the sub-element <APPL_ATTRIBUTE> Attribute Values Description name="..." Attribute name Document-side name of the attribute. hidden="..." true, false Determines whether this is a helper attribute ("true") or a regular document attribute ("false"). Within the attribute definition, the subelement <DIR> addresses document attributes, and the subelement <MA> addresses material attributes. Attribute Values Description Attributes of subelements <DIR> and <MA> Name of a field in SAP from which the value for the attribute should be read out. field="..." row=" " language=" " Field Name Number 0 - x SAP language code Only specific SAP fields are allowed here! A list of allowed SAP fields is available in the Operations Guide (File "Operations Guide_DE.pdf") in SAP Engineering Control Center. (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 not present, an error message is generated. Identifier of the language in which the long text is stored in SAP, for example, "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", " " will be modified to "4711". The subelement <XFORMAT> combines the values "DOCUMENTNUMBER" and "DOCUMENTTYPE" read out from SAP fields into one string: Example for subelement <XFORMAT> <XFORMAT outputformat="{0}/{1}"> <DIR field="documentnumber"/> <DIR field="documentversion"/> </XFORMAT> If DOCUMENTNUMBER = " " and DOCUMENTVERSION = "02", the result is " /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"/> - 20 / 106 -

21 </XFORMAT> In this case, the result is "4711/02". Information regarding further possibilities for attribute mapping and construction of file structure "attributes-fromsap.xml" can be found in the help file "Operations Guide_EN.pdf" in the SAP Engineering 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\acd\customize\config\attributes-to-sap.xml". Upon saving a CAD document, all atributes 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 the attribute 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 the section 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 can now 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 Values Description Attribute of element <section> name="..." include_section="..." description="..." Name of attribute section Name of section: "STANDARD", "STDMOD", "default, etc. Description of attribute sections DTypes are referenced to this attribute section with this name in the file "dtypes.xml". Determines which section will be included from the global file "%PLM_INSTDIR%/customize/config/attributes-to-sap.xml" in the section defined here. This is a comprehensive description of an attribute section. Within a section, the subelement <DIR> and the subelement <MA> addresses fields of the document or material, respectively, which can be changed in SAP. Attributes of subelements <DIR> and <MA> - 21 / 106 -

22 Attribute Values Description Name of the document or material field which can be changed in SAP. field="..." language=" " Field Name SAP language code ATTENTION: Only specific SAP fields are allowed here! A list of allowed SAP fields is available in the Operations Guide (File "Operations Guide_EN.pdf") in SAP Engineering Control Center. (Optional) If field="longtext", the identifier of the language will be given in 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>. Attributes of the sub-element <APPL_ATTRIBUTE> Attribute Values Description name="..." Field Name SAP into which it will be written. Sheets have a number of file properties that can be overwritten when the properties are refreshed with the values from SAP. When mapping, note that the property prefixes "SP-" and "PCP-" must be used for the fixed Sheet Set properties and Project Control properties. No prefix is required for user-defined (custom) properties. A sheet set also contains a number of properties that affect the contained layouts (sheets). The sheet properties are set in the mapping of the respective DWG file. Here too,"sp-" and user-defined properties are distinguished. For an update of the DWG's Sheet Properties, the respective Sheet Set must be checked out. Information regarding further possibilities for attribute mapping and construction of file structure "attributesto-sap.xml" can be found in the help file "Operations Guide_EN.pdf" in the SAP Engineering Control Center, which can be found in folder "%PLM_INSTDIR%\documentation\Manuals\en" AutoCAD Properties General information The following describes the AutoCAD (Mechanical) properties provided by the SAP Engineering Control Center Interface to AutoCAD (Mechanical). The properties can be used in the files "attributes-to-sap.xml" and "attributes-from-sap.xml" for comparison with SAP data. The properties consist of a prefix and the actual property name. The available prefixes can be divided into properties supplied by AutoCAD (Mechanical) and conventions defined by the Interface to AutoCAD (Mechanical). These are grouped by application area. However, properties that do not have a prefix are also made available. These usually refer to drawing properties. Properties that are marked as "ReadOnly" cannot be overwritten by attribute transfer. Further information on this topic is contained in the chapter "Attribute Transfer Between the SAP System and an Application" of the ECTR manual "Operations Guide_EN.pdf" / 106 -

23 Property categories There are the following categories of properties: Summary Information Custom Properties Sheet Set Properties Project Configuration Properties (Sheet Sets) Custom Properties (Sheet Sets) Sheet Properties Custom Sheet Properties AutoCAD System Variables Free Properties Overview of Inventor Properties Properties supplied by AutoCAD Category: Summary Information Prefix: SI- AutoCAD Summary Information Properties Name ReadOnly User Interface Comment SI-Title Tab "File Info", field "Drawing Properties" SI-Subject Tab "File Info", field "Drawing Properties" SI-Author Tab "File Info", field "Drawing Properties" SI-Keyword Tab "File Info", field "Drawing Properties" SI-Comments Tab "File Info", field "Drawing Properties" SI-HyperlinkBase Tab "File Info", field "Drawing Properties" SI-Last Saved By X Tab "Statistics" SI-Revision Number X Tab "Statistics" Category: Custom Properties Prefix: None or UDP- AutoCAD Custom Properties Name ReadOnly User Interface Comment UDP-[name] Tab "User specific", field "Drawing Properties" User-defined property with prefix [name] Tab "User specific", field "Drawing Properties" User-defined property without prefix User-defined properties can be used with or without a prefix, although a prefix is usually not used. In the interop scenario with Inventor, however, the prefix "UDP-" is mandatory. This is defined by the parameter plm.options.updateattributes.useinteropprefix.acx in the configuration file "default.txt". If "true" is entered here, the prefix is used. The default value is "false" / 106 -

24 Properties delivered by SAP Engineering Control Center Interface to AutoCAD Category: Sheet Sets Subcategory: Sheet Set Properties Prefix: SP- Sheet Set Properties Name ReadOnly User Interface Comment SP-Name SP-Description Sheet Set Properties Sheet Set Properties Category: Sheet Sets Subcategory: Project Configuration Properties (Sheet Sets) Prefix: PCP- Project Configuration Properties (Sheet Sets) Name ReadOnly User Interface Comment PCP-ProjectNumber PCP-ProjectName PCP-ProjectPhase PCP-ProjectMilestone Sheet Set Properties Sheet Set Properties Sheet Set Properties Sheet Set Properties Category: Sheet Sets Subcategory: Custom Properties (Sheet Sets) Prefix: None Custom Properties (Sheet Sets) Name ReadOnly User Interface Comment [name] Sheet Set Properties User defined property Category: Sheet Properties Prefix: SP- Sheet Properties Name ReadOnly User Interface Comment SP-Title SP-Description SP-Number SP-RevisionNumber SP-RevisionDate SP-Purpose SP-Category Sheet Properties Sheet Properties Sheet Properties Sheet Properties Sheet Properties Sheet Properties Sheet Properties - 24 / 106 -

25 Category: Custom Sheet Properties Prefix: None Custom Sheet Properties Name ReadOnly User Interface Comment [name] Sheet Properties User defined property Category: AutoCAD System Variables Prefix: VAR- AutoCAD System Variables Name ReadOnly User Interface Comment VAR-[name] X System variable with name [name] Category: Free Properties Prefix: None Free Properties Name ReadOnly User Interface Comment ScaleActiveView X Scale of the active viewport Scale[n] X Scale of the viewport with the index [n]. AutoCAD (Mechanical) properties in the program The dialog for drawing properties can be opened with the command "_DWGPROPS". Some of these properties can also be viewed in the Windows Explorer. Properties for sheet sets and sheets can be edited by right-clicking on the respective sheet set / 106 -

26 AutoCAD properties "Summary" AutoCAD properties "Statistics" - 26 / 106 -

27 AutoCAD properties "Custom" AutoCAD properties "Sheet Set Properties" - 27 / 106 -

28 AutoCAD properties "Sheet Properties" 2.3 default.txt The file "default.txt" contains basic settings that influence the interaction between the SAP Engineering Control Center, SAP Engineering Control Center to AutoCAD and the SAP Engineering Control Center to AutoCAD Mechanical and the SAP system. Further explanations as to the purpose of the file and the individual configuration parameters can be found in the file "default.txt". It is to be noted that the parameters of the character string ".ACD" listed here must be included for AutoCAD, as well as ".ACM" for AutoCAD Mechanical, in order to be assigned to the appropriate CAD system from the SAP Engineering Control Center! In the following table, ".ACx" stands for both ".ACD" (AutoCAD) and ".ACM" (AutoCAD Mechanical)! The following table contains all parameters included in the file "default.txt" in delivery status, as well as their default settings: Parameter: Default value: Parameter: Parameters of the file "default.txt" for AutoCAD and AutoCAD Mechanical plm.document.createmulti.cad.dtype.searchalso.acx List of non AutoCAD DTypes that should be considered for import. ATTENTION: No generic DType IDs can be used here! A list of DTypes, separated by ';' ACPIC;PICP;PICG;PICT;PICJ;PDF plm.document.addcomponent.allowed.dtypelist.acx - 28 / 106 -

29 Default value: Parameters: Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameters: The selection of components to be added to a module in ECTR (in ADD COMPONENT mode) can be specifically controlled, in which a list of allowed DTypes (which must be listed in "dtypes.xml"!) are given here. In this case, the parameter of the same name that gives a generic list will ignore the ECTR in the base file "default.txt". A list of DTypes, separated by ';' ACAD;ACDNR;PICP;PICG;PICT;PICJ;ACPIC;ACPC;PDF;ACDWF;IPTML (AutoCAD) ACADM;PICP;PICG;PICT;PICJ;ACPIC;AMPC;PDF;AMDWF;IPTML (AutoCAD Mechanical) plm.document.create.extensionprimaryapplication.dwg plm.document.create.extensionprimaryapplication.dst When a file is dropped onto a folder, It is needed to decide which primary application type it belongs to in order to select suitable DTypes for creating a new document. This is determined based on the file extension. Abbreviation of the primary application type. ACD (AutoCAD) ACM (AutoCAD Mechanical) plm.control.appltype.wsappl.acx Every application type must be assigned a primary workstation application (WSA). Abbreviation of the primary workstation application ACD (AutoCAD) ACM (AutoCAD Mechanical) plm.control.extension.wsappl.dwg plm.control.extension.wsappl.dst Every application type must be assigned a SAP-defined workstation application. Should no definition be available, the file extension will be used as a default value for the workstation application. Abbreviation of the assigned workstation application ACD (AutoCAD) ACM (AutoCAD Mechanical) plm.control.partnamerules.resolveinsap.acx Activation of FileLookUp for the Import on Demand functionality. NOTE: It is strongly recommended not to change the default setting for this parameter, FileLookUp should be activated! "true" = FileLookUp is activated "false" = FileLookUp is deactivated true plm.mat.properties.acx Indicates which properties are associated with a material information from SAP. A list of property names, separated by ';' MATNR;MATEXTNR;DESCR;UNITS NOTE: The properties MATNR, MATEXTNR and DESCR are reserved and should not be deleted! plm.mat.property.acx.matnr.cadname = SAPMATNR plm.mat.property.acx.matnr.sapname = MARA-MATNR plm.mat.property.acx.matextnr.cadname = MATERIAL plm.mat.property.acx.matextnr.sapname = MATERIAL_EXT plm.mat.property.acx.descr.cadname = DESCR plm.mat.property.acx.descr.sapname = MAKT-MAKTX plm.mat.property.acx.units.cadname = BOM_UNITS plm.mat.property.acx.units.sapname = MARA-MEINS Defines the mapping of material information between CAD and SAP. For every property declared with plm.mat.properties.acx it must exist a mapping. "CADName" is the name of the field from CAD, "SAPName" is the name of the field in the corresponding SAP table. CADName = Name of the field from CAD, SAPName = Name of the field in the corresponding SAP table - 29 / 106 -

30 Default value: Parameter: See under "Parameters"! plm.mat.property.acd.blocknames (AutoCAD only) Declares all names of material blocks defined with parameters plm.mat.property.acd. AutoCAD Mechanical ignores this parameter. List of block names, separated by ";" Default value: Parameters: MATPOS plm.bom.create.acx = true plm.bom.createatcheckin.acx = false plm.bom.update.acx = true plm.bom.updateatcheckin.acx = false plm.bom.create.dst = true plm.bom.createatcheckin.dst = false plm.bom.update.dst = true plm.bom.updateatcheckin.dst = false These parameters controls BOM creation and update. They can be made document type (DOKAR) or DType dependent. Default values: Parameter: Default value: Parameter: Default value: Parameter: Default value: ATTENTION: This option should not activated! "true" = Carry out action "false" = Do not carry out action See at Parameters! plm.bom.item.properties.acx Indicates which properties are used for the creation of a BOM. List of custom properties, separated by ";". IMPORTANT: - These Properties are deprecated and only compatible with the old CDESK BOM wizard (no advanced BOM)! - The properties "POSTYPE", "POSNR", "COMPID" and "QUANTITY" (AutoCAD only) are reserved! POSTYPE;QUANTITY;POSNR;COMPID (AutoCAD) POSTYPE;POSNR;COMPID (AutoCAD Mechanical) plm.bom.item.property.acx.<my_property>.cadname plm.bom.item.property.acx.<my_property>.sapname Defines the mapping of BOM positions (<MY_PROPERTY>) between CAD and SAP. "CADName" is the name of the field from CAD, "SAPName" is the name of the field in the corresponding SAP table. IMPORTANT: - These Properties are deprecated and only compatible with the old CDESK BOM wizard (no advanced BOM)! - For every property declared with plm.bom.item.properties.acd it must exist a mapping! CADName = Name of the field from CAD, SAPName = Name of the field in the corresponding SAP table CADName = BOM_ITEM_QTY plm.bom.item.property.acx.<my_property>.sapvalue Default value for property <MY_PROPERTY>, if it's value isn't substituted in CAD. IMPORTANT: - These Properties are deprecated and only compatible with the old CDESK BOM wizard (no advanced BOM)! - Actually working only for the property "POSTYPE"! Position type: 'C', 'D', 'I', 'K', 'L', 'M', 'N', 'R', 'T' L - 30 / 106 -

31 Parameter: "DMU_CAD" table data: plm.bom.item.property.acd.dmucad.quantity.name = BOM_ITEM_QTY plm.bom.item.property.acm.dmucad.quantity.name = QTY "DMU_D" table data: plm.bom.item.property.acx.dmud.material.name = SAPMATNR Internal data (please do NOT change!): plm.bom.item.property.acx.internal.display.name = DESCR "DMU_TMX_META" table data: plm.bom.item.property.acx.comp_material.name = MATERIAL plm.bom.item.property.acd.comp_posnr.name = BOM_ITEM_POSNR plm.bom.item.property.acm.comp_posnr.name = ITEM Defines the CAD and SAP mapping for bom item properties. This mapping is used for transferring the instance data of virtual components to SAP. See "CDESK_SRV_MODIFY_INST_DATA" for details on possible values! Default value: Parameter: Default value: Parameter: IMPORTANT: - These properties are part of advanced BOM and compatible only with the new "MODIFY_INST_DATA" service and the CDESK MBOM WIZARD! - All properties that are not part of the DMU_CAD or DMU_D table, are automatically stored in the "DMU_TMX_META" table. Names of BOM item properties. See at Parameter! plm.options.bom.insertvirtuelbomheader.acx When transferring virtual instance data to SAP, it may necessary to insert the document itself as additional row into the DMU tables. NOTE: This is currently necessary for the MBOM wizard to properly recognize the corresponding header material! "true" = Insert a virtual row for the document "false" = Do not insert virtual a row for the document true plm.options.ballooning.ballooncontent.acm Specify the balloon content during SAP ballooning. Default value: 3 Parameters: NOTE: This option is only available for AutoCAD Mechanical! "0" = Material and BOM position number "1" = Material number "2" = BOM position number "3" = SAP balloon content "4" = Retain CAD position number plm.options.bomtable.column.acm.sapmatnr = MATERIAL plm.options.bomtable.column.acm.material = MATERIAL_EXT plm.options.bomtable.column.acm.postext1 = POSTEXT1 plm.options.bomtable.column.acm.postext2 = POSTEXT2 plm.options.bomtable.column.acm.othercolumn = POSTEXT2 Defines the CAD and SAP mapping for the drawing BOM table ET_BALLOONS column names during ballooning update. The parameter has the following basic structure: plm.options.bomtable.column.acm.<cad_column> = <SAP_FIELD> If a BOM table exists and it contains a column of the name <CAD_COLUMN>, values within this column will be updated with the content of <SAP_FIELD>. ATTENTION: This options are only available for AutoCAD Mechanical! - 31 / 106 -

32 Default value: Parameter: Implemented possible values (tags) for <SAP_FIELD> are the following fields in table ET_BALLOONS: MATERIAL = Internal material number from column MATERIAL MATERIAL_EXT = External material number from column MATERIAL_EXT POSTEXT1 = Value from column POSTEXT1 POSTEXT2 = Value from column POSTEXT2 See under "Parameters"! plm.options.bomtable.addnonexistingcolumns.acm Add non existing columns to BOM table. If a column [CAD_COLUMN] does not exist in the BOM table, add this column and update the value with the content of [SAP_FIELD]. Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameter: ATTENTION: This options are only available for AutoCAD Mechanical! "true" = Add new columns to BOM "false" = Do not add new columns true plm.attributes.updateaftercheckoutview.acx Indicates whether an update of the BOM properties should be performed during checkout. "true" = Perform update "false" = Do not perform update false plm.adv.clone.renamerprogram.acx Specifies the access path of the "renamer3acd. exe" or "renamer3acm. exe" Utility program. Full access path of the Utility (AutoCAD Mechanical) plm.control.popwin.name.acx Name (caption text), which the main window of the workstation application identifies to bring it to the foreground. The wild card '*' can be used to output a substring. Name of main window of the workstation application and substring, which is a component of the window name (driven by the wild card '*'). *AutoCAD* (AutoCAD) *AutoCAD Mechanical* (AutoCAD Mechanical) plm.options.notification.showasdialog.acx Indicates whether relevant ECTR messages should be displayed as a dialog or only written into the AutoCAD console. "true" = Display dialog "false" = Do not display dialog (write to AutoCAD console) false Default value: Parameter: plm.control.waitforsessioninms.acx Maximum wait time for AutoCAD to send a request to ECTR once it has been contacted successfully. Time in milliseconds plm.options.thumbnail.usescreenshot.acx - 32 / 106 -

33 Defines if a screenshot of the AutoCAD graphic window will be used as preview graphic (thumbnail) instead of the preview graphic stored in a DWG file as DIS thumbnail for the ECTR object browser. NOTE: This decreases the performance a little, but the quality of the preview graphics will be increased drastically! This setting overwrites the system variable "THUMBSAVE": Parameter value Value of THUMBSAVE Result false 0 Generate screenshot as fallback false 1 Use DWG graphic (default) true 0 Generate screenshot as thumbnail true 1 Generate screenshot as thumbnail Default value: Parameter: "true", "false" false plm.options.thumbnail.size.acx Sets the high of thumbnails for the ECTR preview. The width will be calculated automatically. Default value: 180 Parameter: NOTE: For thumbnails with more than 200 pixels it is recommended to adjust the setting of the parameter "plm.options.thumbnail.usescreenshot.acx" to create higher quality images. High of the thumbnails (previews) in pixels. plm.options.enablesheetset.acx Enable or disable support for Sheet Sets. Default values: Parameter: ATTENTION: Activating this setting using AutoCAD 2017 is not recommended! "true" = Sheet Set support enabled "false" = Sheet Set support disabled false plm.convert.additional.acx - 33 / 106 -

34 Additional file formats (neutral formats) and their conversion are adapted via this parameter. The parameter has the following characteristics: 1.) Defines the AutoCAD document types for the additional format files (equal to the DOKAR field): plm.convert.additional.acx = <DOCTYPE1>;<DOCTYPE2> Example: plm.convert.additional.acd = ACD 2.) Define which additional formats are to be generated for which AutoCAD document type: plm.convert.additional.acx.<doctype> = <CONVERT TYPE1>;<CONVERT TYPE2> Supported formats: PDF, DXF, DWF Example: plm.convert.additional.acd.acd = pdf 3.) Setting the file extension for each additional file format: plm.convert.additional.acx.<convert TYPE>.extension = <File extension> Example: plm.convert.additional.acd.pdf.extension = pdf 4.) Sets the rule for the file name of the additional format file: plm.convert.additional.acx.<convert TYPE>.keepExtension = <BOOL> Example: plm.convert.additional.acd.pdf.keepextension = true Possible values are: - "true":the file extension of the additional format file is attached to the filename of the document. - "false": The file extension of the document is enhanced by the file extension of the additional format file. 5.) Configure the names for neutral formats: plm.convert.additional.acx.<convert TYPE>.filenameFormat = <PLACEHOLDER> The following placeholders are available, which are replaced by the corresponding SAP values: - "$ (DOCNUMBER)": SAP name - "$ (DOCTYPE)": Document type - "$ (DOCVERSION)": Document version - "$ (DOCPART)": Document part Additional file formats and their conversion are adapted via this parameter. Example: plm.convert.additional.acd.pdf.filenameformat = Number.$(DOCNUMBER)_Type.$(DOCTYPE)_Version.$(DOCVERSION)_Part.$(DOCPART) 6.) Specify a list of options for the converter: plm.convert.additional.<apptype>.<convert TYPE1>.Options = <Option_1>;<Option_n> Possible values: 3dDwf, MultiSheet, DeviceName Example: plm.convert.additional.acd.dwf.options = 3dDwf;MultiSheet;DeviceName 7.) Specifies the value for the corresponding option: plm.convert.additional.<apptype>.<doctype1>.<convert TYPE1>.<Option_1> = <Value_1> Example: plm.convert.additional.acd.acd.dwf.3ddwf = true Default value: Parameter: Default value: See Description! These parameters are commented out by default! plm.options.importondemand.transferattributestosap.acx Defines if drawing attributes will be transferred to SAP during import. Must be activated if used a separate attribute section <attribute_section> for "<document_create/>" in the file "dtype.xml"! "true" = Use <attribute_section> for <document_create/> "false" = Don't use <attribute_section> for <document_create/> false - 34 / 106 -

35 Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: 2 Parameter: plm.options.deliveronlyrequestedattributestosap.acx Indicates that only the specified attributes in file "attributes-to-sap.xml" will be delivered during the transfer of drawing attributes to SAP. NOTE: AutoCAD (Mechanical) and the ECTR must restarted if this option is changed! "true" = Yes "false" = No false plm.attributes.acx.tbkupdateinalllayouts Indicates the update of all title blocks of all drawing areas (model and layout area) during attribute update. "true" = Update of all title blocks of all drawing areas (model and layout area) "false" = Update of the title block only in the actual view true plm.attributes.acx.tbknames Defines the names of all title blocks for update. List of title block names, separated by ';' DIN_CIDEON (This value refers to the CIDEON example title block, delivered with the install package) plm.options.updateattributes.useinteropprefix.acx Indicates whether User Defined Properties (UDP) should be written with or without the prefix "UDP-". "true" = Use prefix "UDP-" "false" = Do not use prefix "UDP-" false plm.document.dtype.default.dwg.acx Defines the use of the default master DType during creation of a new document info record (DIR) in SAP and indicates it's name. Name of master DType ACAD (AutoCAD) ACADM (AutoCAD Mechanical) plm.options.createdirfornewdocument.acx Determines whether a document info record (DIR) should be created for a newly created document. 0 = never create a DIR 1 = always create a DIR 2 = always ask plm.options.importondemand.deleteoriginals.acx Delete original CAD files after successful import on demand. Default value: Parameter: Default value: ATTENTION: This option should only be activated with extreme caution, because deleting the original cannot be undone and can cause unexpected side effects! "true" = Delete CAD files "false" = Do not delete CAD files false plm.options.importondemand.checkinaftercreate.acx Checkin documents after successful import on demand. "true" = Documents will be checked-in "false" = Documents will be checked-out true - 35 / 106 -

36 Parameter: Default value: 2 Parameter: plm.options.sapopenforcadplacedocument.acx Defines which dialog comes up for component insertion. 0 = Use CAD system's dialog 1 = Use the ECTR dialog 2 = Ask the user plm.options.references.attachmultiplecomponents.acx Insert multiple parts at once when adding components from SAP. "true" = Allow to add multiple components "false" = Allow only one component to add Default value: Parameter: Default value: false plm.doc.cancel.restore.files.acx Determines how changes to a checked-out document should be handled when executing "Reset clipboard". "true" = The document is reset to the status of the last check-in "false" = The document is deleted from the working directory false Parameter: Default value: 0 Parameter: Default value: Parameter: Default value: 2 Parameter: Default value: Parameter: Default value: 1 Parameter: plm.options.sapopenforcadopendocument.acx Determines the reaction of the interface if the user uses the integrated CAD-Open function (Ctrl+O oder _OPEN). "0" = A local file will be opened "1" = One or more files may be opened from SAP "2" = Ask the user whether to open a local file or open a file from SAP plm.options.open.usemultisearchforsapopen.acx Defines the use a dialog for multiple search to open files from SAP. This dialog allows it to open many files at once. "true" = Use multiple search dialog "false" = Use single search true plm.options.missingreferencereloadoption.acx Defines the behavior if AutoCAD (Mechanical) notes a missing component file when loading a document with references. ATTENTION: If the option is set to value "1" or "2" the assembly document might be dirty after loading it! "0" = Use AutoCAD (Mechanical) behavior "1" = Load component from SAP automatically "2" = Ask user plm.structure.application.collectentries.acx Determines how instances of the same component in the ECTR structure are viewed in the application structure view. "collectnone" = Do not collect anything - for each instance an entry in application structure should be displayed "collectall" = Collect entries of same component files collectnone plm.structure.application.init.strategy.levels.acx Number of layer displayed in the structure view. Number 1-n = Number of displayed layer "all" = Display all layer plm.structure.application.displayexternalreferences.acx - 36 / 106 -

37 Default value: Parameter: Default value: Parameter: Default value: Parameter: Default value: Parameters: Display external references in Application Structure. "true" = Display external references "false" = Do not display external references false plm.structure.application.displaypositem.acx Determines how material positions are displayed in the tree. "true" = Show material positions under the corresponding component node "false" = Do not show material positions in the tree false structure.view.acx.generic.object.type Additional mapping options for user defined nodes in the application structure, necessary for the material positions. Name of properties. Has to be read from the node "attributes" as follows: POS_TYPE = [ACx_MATERIAL_NEW ACx_MATERIAL ACx_VIRTUAL_NEW ACx_VIRTUAL] POS_TYPE structure.view.acx.generic.object.acx_material_new.name structure.view.acx.generic.object.acx_material.name structure.view.acx.generic.object.acx_virtual_new.name structure.view.acx.generic.object.acx_virtual.name Determines the key name of the property for assignment of the default presentation of the nodes. Name of property. Has to be read from the node "attributes" as follows: DEFAULT_NAME = "Customized I18N Text" (Example) DEFAULT_NAME plm.structure.node.cuapob_acx_material.icon.1 = structure/flag/state/$(any_modified)/acx plm.structure.node.cuapob_acx_material.icon.2 = structure/flag/state/$(state)/acx plm.structure.node.cuapob_acx_material_new.icon.1 = structure/flag/state/$(any_modified)/acx plm.structure.node.cuapob_acx_material_new.icon.2 = structure/flag/state/$(state)/acx plm.structure.node.cuapob_acx_virtual.icon.1 = structure/flag/state/$(any_modified)/acx plm.structure.node.cuapob_acx_virtual.icon.2 = structure/flag/state/$(state)/acx plm.structure.node.cuapob_acx_virtual_new.icon.1 = structure/flag/state/$(any_modified)/acx plm.structure.node.cuapob_acx_virtual_new.icon.2 = structure/flag/state/$(state)/acx Default value: Parameter: Default value: Parameter: Default value: Additional mapping options for user defined nodes in the application structure necessary for material positions. Path to the respective icons. See under "Parameters"! plm.options.structureanalyze.showdialogformissingreferences.acx Indicates the display of a dialog indicating an error during structure analysis. "true" = Display a dialog for every missing reference found "false" = No dialog will be viewed. The missing references will be written into the log true plm.options.checkin.abortanalysisofcheckedincomponents.acx When an assembly is checked in, its entire structure is usually analyzed to find also checked out and / or modified documents. This takes a long time, however. Assuming that a read-only, unmodified component file can not have been modified (i.e., in its components and its contents), its structure analysis can optionally be dispensed with in order to speed up the process. ATTENTION: This only works reliably if the CAD system reliably passes changes to sub-sub components to the top module. Otherwise inconsistencies may occur! In case of uncertainty this option should not be activated! "true" = Performance option is activated "false" = Performance option is not used false - 37 / 106 -

38 Parameter: plm.document.saveasnewdocument.checkouttop.acx Specifies whether the relevant superordinate assemblies are to be checked out before with a "SaveAs" ("SaveAsNewDocument" or "SaveAsNewVersion"). The checkout is necessary, as the references to the new document must be changed in these modules - this is not possible in case of write-protection. WARNING: Choosing the value "0" is not recommended because this may cause inconsistencies! "0" = Do not checkout any documents (not recommended) "1" = Checkout relevant documents "2" = Checkout relevant documents and save afterwards Default value: 1 Parameter: Default value: 1 Parameter: Default value: Parameter: Value: Default value: Parameter: plm.options.saveasnewdocument.replace.acx Defines the method for replacing references in the "Save as new document" function. '0' = Replace in all open views without warning dialog '1' = Replace only in active and unavoidable other views without warning dialog '2' = Replace in all open views after displaying a warning dialog '3' = Replace only in active and unavoidable other views without warning dialog '4' = Do not replace references plm.options.checkin.updateattributesfromsap.acx Determines whether the attributes (metadata) are to be read from the SAP system and updated first during checkin (save). "true" = Update of SAP attributes before checkin "false" = No update of SAP attributes before checkin false plm.options.updatetitleblockdataoninsert.acx Determines whether attributes from SAP are to be updated when a title block is inserted. "true" = Automatically update title block data "false" = Do not update title block data false plm.appl.location.acx Indicates the installation directory of the AutoCAD program file "acad.exe" Default value: Parameter: NOTES: - This parameter is mandatory, otherwise the AutoCAD program file will not be found! - This setting cannot be maintained user-specifically via "options.xml"! - As of version , environment variables with "%Variable%" can also be used here. But "%PROGRAMFILES%" is not possible! Path of the AutoCAD installation directory Path of the actual AutoCAD installation directory plm.appl.profile.acx Defines the user profile used to start AutoCAD ("<<Profilename>>"). Default value: Parameter: NOTES: - An AutoCAD user profile must absolutely be given in order to ensure communication between AutoCAD and ECTR! - This setting cannot be maintained user-specifically via "options.xml"! - As of version , environment variables with "%Variable%" can also be used here. Profile name or ACAD default profile <<VANILLA>> (AutoCAD), <<ACADMPP>> (AutoCAD Mechanical) plm.appl.product.acx - 38 / 106 -

39 Corresponds to the product abbreviation of AutoCAD or AutoCAD Mechanical. Standardwert: Parameter: NOTES: - This setting cannot be maintained user-specifically via "options.xml"! - As of version , environment variables with "%Variable%" can also be used here. "ACAD" (AutoCAD) "ACADM" (AutoCAD Mechanical) ACAD (AutoCAD), ACADM (AutoCAD Mechanical) plm.appl.language.acx Specified the language of the CAD program. The appropriate language package must be installed. Default value: Parameter: Default value: 2 Parameter: NOTES: - This setting cannot be maintained user-specifically via "options.xml"! - As of version , the environment variable "%PLM_LANGUAGE%" can also be used here. Language specification in the form <Language>-<Country> (e.g. "en-us" or "de-de") or the environment variable "%PLM_LANGUAGE%". This is set by the ECTR according to the current SAP logon language. en-us plm.options.sapsaveasnewdocumentforcadsaveas.acx Specifies whether the command "Save as..." (_SAVEAS) in CAD can optionally be enabled to save as a new document in SAP. NOTE: This option is available with patch 12 (version ) of the interface! '0' = Never save as new document '1' = Always save as new document '2' = Ask user plm.execute.additional.acx - 39 / 106 -

40 It is possible to execute additional functions before or after a specific PLM process by starting either an executable file (external tool), a CAD macro (internal VBA, LISP or command routine) or the powershell. The following specifications are possible: 1.) Specifies the time of execution per document type: plm.execute.additional.acx.<doctype> = <EXEC TIME> Possible options are: - "BeforeCheckIn": Execute before checkin - "AfterCheckOut": Execute after checkout - "AfterBallooning": Execute after ballooning Example: plm.execute.additional.acd.acd = BeforeCheckIn 2.) Specifies the type of additional function: plm.execute.additional.acx.<doctype>.<exec TIME>.type = <EXEC TYPE> Possible options are: - "Executable": External tool - "CADMacro": CAD macro (VBA, LISP or command routine) - "Powershell": Starts the Windows powershell Example: plm.execute.additional.acd.acd.beforecheckin.type = Executable 3.) Specifies the name of the external program, macro or command: plm.execute.additional.acx.<doctype>.<exec TIME>.commandLine = <CMDLINE> Example: plm.execute.additional.acd.acd.beforecheckin.commandline = D:\\test.bat Structure of the command line: - Executables need a valid file path with escaped backslashes. Example: D:\\Data\\Tools\\ExtractFormat64.exe - LISP routines need the prefix "LSP:" and must be registered functions. Example: LSP:c:cdntest - VBA macros need the prefix "VBA:" and the path is optional if the project is already loaded. Example: VBA:D:\\VBA\\Project.dvb!CdnEctrTest.Utils.ACD_Export - AutoCAD commands need the prefix "CMD:" and must be transparent. Example: CMD:'ZOOM Default value: --- NOTES: - Executables need a valid file path with escaped backslashes! - The use of VBA macros, LISP macros and CMD routines will open the respective documents if they are not opened at the time of the function call! 4.) Specifies the parameters to pass: plm.execute.additional.acx.<doctype>.beforecheckin.parametern = <PARAM> The placeholder 'N' represents the parameter number. The parameter number also determines the order in which the parameters are passed! Examples: plm.execute.additional.acd.acd.beforecheckin.parameter1 = $(FILENAME) plm.execute.additional.acd.acd.afterballooning.parameter2 = Test-User See under Description! 2.4 dtype.xml The DType settings control the behavior of the SAP Engineering Control Center when new documents are created and when the properties of documents are handled. Settings related to document type are defined in the file "dtype.xml". The file "dtype.xml" sent out with the SAP Engineering Control Center Interface to AutoCAD and SAP Engineering - 40 / 106 -

41 Control Center Interface to AutoCAD Mechanical contains definitions and settings for document types supported by AutoCAD and AutoCAD Mechanical. 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 distinctions between the master document, nonmaster documents dependent on the master document, and templates for document type descriptions. The element <DType> possesses a variety of attributes and accepts a wide range of 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 the file "%PLM_INSTDIR%\basis\aux-files\dtype_4110.dtd". The DType definitions for the SAP Engineering Control Center Interface to AutoCAD and the SAP Engineering Control Center Interface to AutoCAD Mechanical are described here DType definition for AutoCAD With the installation of the SAP Engineering Control Center interface to AutoCAD the file "dtype.xml" is delivered. This includes the DType definitions that are essential for the interaction with the SAP Engineering Control Center. Below these definitions will be explained. The definition is divided into two areas: Generic functions (template definition) Master document definitions The correlation of the DType definitions as well as their dependencies is shown in the following table: Overview about DType definitions for AutoCAD DType-ID Type App-Type Description DEFLT Template Base template from SAP/DSC - 41 / 106 -

42 +- ACGEN Template ACD Base template for AutoCAD documents +- ACMM Template ACD Base template for DWG-drawings as Master +- ACAD Master ACD Drawing (DWG) +- ACDNR Master ACD Not Renaming DWG-drawing for fixed block definitions +- ACDWF Master ACD Design Web Format file (DWF) +- ACDST Master ACD Sheet Set Data file (DST) +- ACPC Master ACD Sample configuration: Point clouds +- ACPIC Master PIC Sample configuration: Raster images The following are the descriptions of the individual definitions for AutoCAD documents Generic DType definition The Generic Definition is a template with basic definitions that are valid for all AutoCAD file types. It is integrated in the other DType definitions. Generic DType definition for AutoCAD <DType type="template" identifier="acgen" include_template="deflt" application_type="acd" group="autocad"> <icon> <icondef icon_position="1" icon_group="default" icon_identifier="tree/acd/autocad_drawing_16"/> </icon> <program_options show_for_create="yes" has_primary_application="yes" dirty_flag="yes" attempt_status_change_on_checkin="yes" dataexchange_rename_on_import="yes" dataexchange_show_for_import="yes"> <copy_as allowed="yes" ignore_wsappl_list="zip" use_initial_version="yes" copy_material="no" remove_dirty_flag="no"/> <new_version status_list="ac;fr" ignore_wsappl_list="zip" ignore_nm_dtype_list="drwt;draw" remove_dirty_flag="no" rename_master_original="no"/> </program_options> <document_create create_with_sap_gui="no" create_multi_allowed="no" change_to_after_create_status="" filename_template_base="$(docnumber)$(doctype)$(docpart)" filename_template_version=""> </document_create> <primary_application attribute_section="stdmod" update_attributes_for_dirty="yes" update_attributes_for_rw="yes" update_attributes_for_ro="no"> <container_file> <plmfile extension="ecf" workstation_application="ecf" description="ectr container file"/> </container_file> <checkout_rules check_references_on_edit="yes" rename_master_original_at_checkout="no" one_version_in_session_only="no" - 42 / 106 -

43 hardlink_in_session="no" read_structure="flag"> </checkout_rules> </primary_application> </DType> Attributes of the element <DType> type identifier include_template application_type group "template" "ACGEN" "DEFLT" "ACD" "AutoCAD" Sets the kind of DType definition. "template" = This is a DType template definition. Non-ambiguous ID string to this definition of DType within the entire XML document. The ID has to be between one to five characters long. "ACGEN" = ID of this template definition. Sets which template definition should be integrated into this definition. "DEFLT" = The DType template with ID "DEFLT" from global "dtype.xml" file will be included. Designates the application that is relevant for this document. This application opens the file from SAP Engineering Control Center. "ACD" = This is the application type for AutoCAD. Defines the group designation for master documents. The group designation helps organizing the DTypes within Dialogue "create document". "AutoCAD" = Document belongs to this group. The sub-element <icon> defines an acronym that will be used when determining the applicable symbol in SAP Engineering Control Center. It also contains the sub-element <icondef>. Attributes of the sub-element <icondef> from sub-element <icon> icon_position "1" icon_group "default" icon_identifier "tree/acd/autocad_drawing_16" Position of icon in the document entry of the tree. "1" = Left, "6" = Right. Identification of a symbol group. Status-depending, other symbols can be represented. "default" = This is the standard symbol. Path to determine the icon file, which contains the applicable symbol for this symbol position. "tree/acd/autocad_drawing_16" = the icon file. The sub-element <program_options> contains different settings, which control the behavior of the document in the SAP Engineering Control Center. Attribute of the sub-element <program_options> show_for_create "yes" Determines if in dialogue "Create Document " this DType is visible in the combo box for accessible document types. "yes" = document visible / 106 -

44 has_primary_application dirty_flag attempt_status_change_on_checkin dataexchange_rename_on_import dataexchange_show_for_import "yes" "yes" "yes" "yes" "yes" Determines if document is normal document with original and designated Workstation Application or container object for additional originals without explicit original. "yes" = document possesses original with designated Workstation Application. Determines if the newly created document has a dirty flag. "yes" = The document possesses a dirty flag. Determines if change of status applies during check in at SAP Engineering Control Center or if SAP System conducts change of status. "yes" = change of status by SAP Engineering Control Center. Determines if original is renamed during import. "yes" = Original will be renamed during import according to determined rules and dependent on document. Determines if this DType can be used during import. "yes" = This DType is available during import. The sub-element <copy_as> determines how the document behaves during "CopyAs"-activity and how SAP Engineering Control Center reacts to the document. Attributes of the sub-element <copy_as> from sub-element <program_options> allowed ignore_wsappl_list use_initial_version copy_material remove_dirty_flag "yes" "ZIP" "yes" "no" "no" Determines if a CopyAs is permitted for this DType. "yes" = "CopyAs" - operation permitted. Determines which additional originals of the document will be accepted during copy but not into copy of document according to a table of identifiers for the Workstation Application for additional originals all of which are separated by semicolon. "ZIP" = Additional originals of type "ZIP" (ZIP-Archive) will not be copied. Determines if the number of version of the copy is to be set on the original or on to initial value (in most cases "00"). "yes" = Number of copy version to be set onto initial value. Determines if designated material will also be copied during copy of master document. This attribute has no influence on depending documents, which are copied onto the master documents during copy process. "no" = Material will not be copied. Determines if dirty flag of copy will be reset. "no" = The dirty flag of copy remains set. The sub-element <new_version> contains settings for versioning of documents. Attributes of the sub-element <new_version> Status list ignore_wsappl_list "AC;FR" "ZIP" Determines the type of document status that allows visioning of documents. A table of document status can be separately stated through ";". "AC;FR" = With this kind of document status new versions are allowed. Determines which additional originals of the document will be accepted during versioning but not into new version of document according to a table of identifiers for the Workstation Application for additional originals all of which are separated by semicolon. "ZIP" = Additional originals of type "ZIP" (ZIP-Archive) will not be copied / 106 -

45 ignore_nm_dtype_list remove_dirty_flag rename_master_original "DRWT;DRAW" "no" "no" Determines which depending documents will be ommitted during versioning of master documents. Depending documents to be omitted will be listed in a table of DTypes, separated by semicolon. "DRWT;DRAW" = Table of document types to be omitted. Determines if dirty flag of new version will be reset. "no" = The dirty flag of new version remains set. Determines whether the original file name is assigned a file name according to the part rules for this DType during versioning or whether the previous file name is retained unchanged. "no" = Keep file name unchanged. The sub-element <document_create> contains settings that control the way in which a new document is created in SAP. Attributes of the sub-element <document_create> create_with_sap_gui "no" create_multi_allowed "no" change_to_after_create_status "" filename_template_base "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)" filename_template_version "" Determines if SAP GUI should be opened when creating a document. "no" = Don't open SAP GUI. Determines if the mass creation of this document is allowed. "no" = Mass creation of this document is not permitted. Initial status of newly created document can be set here. "" = Standard status will be used. Determines composition of file name of original document. The following place holders are possible: $(DOCNUMBER) for the document number, $(DOCTYPE) for the document type and $(DOCPART) for partial document. "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)" = The file name consists of document number, document type and partial document. Determines the composition of the document version in the file name for the original of this document. The following placeholder can be used: $(DOCVERSION) for the document version. "" = No version in the file name. The sub-element <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 the originals. Attributes of the sub-element <primary_application> attribute_section update_attributes_for_dirty update_attributes_for_rw "STDMOD" "yes" "yes" Name of section within Attribute Mapping File, in which attributes exchange between SAP and the application is defined. "STDMOD" = Name of section within Attribute Mapping File. Defines if to update the attributes when dirty flag was set. "yes" = Perform Attribute Update. Defines the attribute update at the operation "Open for edit". "yes" = Perform Attribute Update / 106 -

46 update_attributes_for_ro "no" Defines the attribute update at the operation "Open read-only". "yes" = Don't Perform Attribute Update. The subelement <container_file> defines the file type for container files in AutoCAD. Attributes of the subelement <container_file> of subelement <primary_application> Parameter Value Description extension workstation_application description "ecf" "ECF" "ECtr container file" Defines the file extension of AutoCAD container files. "ecf" = File extension. Defines the workstation application for AutoCAD container files. "ECF" = Workstation application. Defines a description of the file type for AutoCAD container files. "ECtr container file" = Description of the file type. The sub-element <checkout_rules> determines how to treat the original of document at checkout. Attributes of the sub-element<checkout_rules> from sub-element <primary_application> Parameter Value Description check_references_on_edit rename_master_original_at_checkout one_version_in_session_only hardlink_in_session read_structure "yes" "no" "no" "no" "flag" Defines if under function "Open for Edit" all files for referenced components were provided in the session directory. Test has been done If not, operation will be abandoned. "yes" = Run test. Defines if original is renamed during opening according to rules for component names. "no" = Keep file name during opening. Determines if document must have only one version in session directory. "no" = Multiple versions of document are allowed in session directory. Determines if hard link may be used for original document in the session directory or if copy creation is always necessary. "no" = Always create copy. Specifies whether opening the document results in a structure explosion. "flag" = If the "Structure" flag is set, perform structure explosion The DType definition for master documents The SAP Engineering Control Center distinguishes between master documents and dependent documents. The master document is the main document and contains the CAD model file to be processed. In addition, the master document is the basis for the preparation of the bill of materials. It is recommended to maintain only the language English directly in the file "dtype.xml"! All other languages will be offered via the particular "dictionary.txt" file. This affects the definitions of DTypes and Seedfiles. All elements <description language="xy"> are omitted except English which are used as fallback. The DType definition is divided into a template definition and the actual DType definition for master documents. The template is included here / 106 -

47 Template definition for master documents for AutoCAD <DType type="template" identifier="acmm" include_template="acgen" application_type="acd" group="autocad"> <program_options function_group="doc_acd" customer_data_section=""/> <document_create document_number_assignment="internal" initial_document_number="" document_type="acd" initial_document_part="000" part_editable="no" initial_document_version="00" version_editable="no"> <seedfile filename="acad.dwg" type="template" default="yes" dictionary_identifier="acad"> <description language="en" text="empty drawing" /> </seedfile> <seedfile type="template" default="no" dictionary_identifier="samples.cideon_din_a4"> <description language="en" text="cideon DIN A4 sample drawing" /> </seedfile> <seedfile type="template" default="no" dictionary_identifier="samples.cideon_din_a2"> <description language="en" text="cideon DIN A2 sample drawing" /> </seedfile> <seedfile filename="" type="select" default="no" extension_filter="*.dwg" > <description language="en" text="select existing drawing" /> </seedfile> </document_create> <material_create material_creation_method="deferred" material_number_assignment="internal" /> <primary_application primary_workstation_application="acd" attribute_section="acd"> <checkin_rules from_application_only="yes"> <save_direct> <plmfile extension="jpg" workstation_application="epj" description="ectr Preview (jpeg)"/> <plmfile extension="gif" workstation_application="epg" description="ectr Preview (gif)"/> <plmfile extension="txt" workstation_application="txt" description="$(filename)"/> <plmfile extension="pdf" workstation_application="pdf" description="$(filename)" /> <plmfile extension="dwf" workstation_application="dwf" description="$(filename)"/> <plmfile extension="dwfx" workstation_application="dwf" description="$(filename)"/> <plmfile filename_pattern="plm_metainf-viewing\.xml" workstation_application="evi" description="ectr Viewing metainf" /> </save_direct> <ignore> <plmfile extension="bak"/> <plmfile extension="tmp"/> <plmfile extension="bat"/> - 47 / 106 -

48 <plmfile filename_pattern="plm_metainf-*.*"/> </ignore> <delete_in_sap> <plmfile workstation_application="epj"/> <plmfile workstation_application="epg"/> <plmfile workstation_application="pdf"/> <plmfile workstation_application="dwf"/> <plmfile workstation_application="pic"/> <plmfile workstation_application="evi"/> </delete_in_sap> <delete_in_session> <plmfile extension="jpg"/> <plmfile extension="gif"/> <plmfile extension="pdf" /> <plmfile extension="bat"/> <plmfile filename_pattern="plm_metainf-*.*"/> </delete_in_session> <scripts> </scripts> </checkin_rules> </primary_application> </DType> Attributes of the element <DType> of the template definition "ACMM" type identifier include_template application_type group "template" "ACMM" "ACGEN" "ACD" "AutoCAD" Determines the type of DType definition. "template" = This is a DType template definition. An unambiguous ID string for this DType definition within the entire XML document. The ID has to be between one to five characters long. "ACNM" = ID of this template definition. Sets which template definition will be integrated into this definition. "ACGEN" = The DType template with the "ACGEN" ID from this "dtype.xml" file is included. This is the generic definition. Designates the application that is relevant for this document (Workstation Application). This application opens the file from SAP Engineering Control Center. "ACD" = This is the Workstation Application for AutoCAD (WSAppl). Defines the group designation for master documents. The group designation helps to organize DTypes within the dialog "create document". "AutoCAD" = Document belongs to this group. The sub-element <program_options> contains different settings, which control the behavior of the document in the SAP Engineering Control Center. Attributes of the sub-element <program_options> function_group "DOC_ACD" Sets the Function Group to which the document belongs. For documents with a common Function Group, for example, specific context menus can be defined. "DOC_ACD" = This DType is assigned to the Function Group "DOC_ACD" / 106 -

49 customer_data_section "" Name of a section in the attribute mapping file that is defined in the customer-specific data. The data will be displayed in the object browser under the "Customer Data" tab. "" = No section has been defined. The sub-element <document_create> contains settings that control the way in which the document is created in SAP. Attributes of the sub-element <document_create> document_number_assignment initial_document_number "" "internal" Determines the document number assignment in SAP. "internal" = SAP assigns the number automatically. The value of this field has no value when the number is internally assigned. This value is entered as a prefix in the input field of the document system dialogue when the number is externally assigned. The user can delete/change the prefix at any time. "" = Empty, since there is no value, because document_number_assignment = "internal". document_type "ACD" initial_document_part "000" SAP document type for the newly created document. "ACD" = AutoCAD Document. SAP document part or a semicolon-separated list of SAP document parts for the newly created document. If a list of document parts has been specified, then a documentation system dialog for one of the document parts can be selected from a dropdown box in the SAP Engineering Control Center. part_editable "no" "000" = Initial value for the document part. Defines whether the documentation system dialog for the default value or the selected SAP document part from the "initial_document_part" attribute can be changed in the input field from within the SAP Engineering Control Center. "no" = The default value in the documentation system dialog cannot be changed. initial_document_version "00" SAP document version or a semicolon-separated list of SAP document versions for the newly created document. If a list of document versions has been specified, then a documentation system dialog for one of the document versions can be selected from a dropdown box in the SAP Engineering Control Center. version_editable "no" "00" = Initial document version. Determines whether the documentation system dialog for the default value for the document version can be changed from the "initial_document_version" attribute within the SAP Engineering Control Center. "no" = The default value cannot be changed. The <seedfile> sub-element contains settings for the template file. Several template files can be assigned, in other words the <seedfile> may occur more than once. This includes the <description> sub-element, which defines each description text in different languages. Attributes of the first sub-element <seedfile> from sub-element <document_create> filename type default "acad.dwg" "template" "no" When using type="template", this attribute defines the file name of the template file that is used. There must be a file with this name, or the process will terminate with an error. "acad.dwg" = File name of the template file that is to be used. Determines how the original document will be generated. "template" = The "filename" attribute is used to specify the template file that is to be used. Here you can determine whether this template file should be used as a preset in the "Create Document" dialog. "no" = The template file is not preset / 106 -

50 dictionary_identifier "acad" Identifier of the description of the template in the dictionary. "acad" = Identifier in the dictionary. Attributes of the second sub-element <seedfile> from sub-element <document_create> filename type Default extension_filter "acad.dwg" "select" "no" "*.dwg" The "filename" attribute is used to specify the template file that is to be used. You can create a template file in the "Create Document" dialog using a file selection dialog. "acad.dwg" = File name of the template file. Determines how the original document will be generated. The "filename" attribute is used to specify the template file that is to be used. You can create a template file in the "Create Document" dialog using a file selection dialog. "select" = It is possible to select a template file in the "Create Document" dialog. Here you can determine whether this template file should be used as a preset in the "Create Document" dialog. "no" = The template file is not preset. When selecting a template file with the type="select", this attribute determines the file extension filter that is used. In the file selection dialog you can select files that are matched by the filter. "*.dwg" = Filter for the file extension. The sub-element <material_create> contains settings for creating a new document from materials. Attributes of the sub-element <material_create> material_creation_method material_number_assignment "deferred" "internal" Determines whether and how a material is applied to a new document. "deferred" = No material is applied to the document. You can attach Materials subsequently to this document. Defines the material number assignment in the SAP System. "Internal" = External number assignment. The user must specify the material number himself. The sub-element <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. Attribute of the sub-element <primary_application> primary_workstation_application "ACD" "ACD" = SAP workstation application identifier for AutoCAD attribute_section "ACD" Name of section within the Attribute Mapping File, in which attribute exchanges between SAP and the application are defined. "ACD" = Name of section within the Attribute Mapping file. The sub-element <checkin_rules> determines how files in the additional directory and document originals are treated when checking in. This is why it has multiple sub-elements. Attribute of the sub-element <checkin_rules> from <primary_application> - 50 / 106 -

51 from_application_only "yes" "yes" = Prevents a document from being checked in without CAD in the desktop view of the ECTR via the context menu. The sub-element <save_direct> determines which additional files (paragraph styles) are stored as originals in the additional directory when saving. It includes multiple <plmfile> sub-elements that determine the individual additional file types. Attributes of the sub-element <plmfile> from sub-element <save_direct> from <checkin_rules> extension workstation_application description filename_pattern "jpg", "gif", "txt", "pdf", "dwf", "dwfx" "EPJ", "EPG", "TXT", "PDF", "DWF", "DWF", "EVI" "ECtr Preview (jpeg)", "ECtr Preview (gif)", "$(FILENAME)", "ECTR Viewing metainf" "plm_metainf-viewing\.xml" The respective file name extensions of additional files in the file system. "jpg", "gif", "txt", "pdf", "dwf", "dwfx" = The current file name extensions. Workstation application identifiers for each paragraph style. "EPJ", "EPG", "TXT", "PDF", "DWF", "DWF", "EVI" = Workstation application identifiers. Description of the respective additional file. "ECtr Preview (jpeg)", "ECtr Preview (gif)", "$(FILENAME)", "ECTR Viewing metainf" = Description of additional files. Filters by file names and regular expressions. "plm_metainf-viewing\.xml" = Filter mask. The <ignore> sub-element determines which files will be ignored when saving. It includes multiple <plmfile> subelements that determine the additional file types to ignore. Attributes of the sub-element <plmfile> from sub-element <ignore> from sub-element <save_direct> from <checkin_rules> Parameter Values Description extension filename_pattern "bak", "tmp", "bat" "plm_metainf-*.*" The respective file name extensions of the additional files to ignore in the file system. "bak", "tmp", "bat" = File name extensions of the additional file types. Filters by file names and regular expressions. "plm_metainf-*.*" = Filter mask. The sub-element <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> sub-elements that determine the additional file types to delete. Attributes of the sub-element <plmfile> from sub-element <delete_in_sap> from sub-element <save_direct> from <checkin_rules> Parameter Values Description workstation_application "EPJ", "EPG", "PDF", "DWF", "PIC", "EVI" Workstation application identifiers for each paragraph style. "EPJ", "EPG", "PDF", "DWF", "PIC", "EVI" = Workstation application identifiers. The <delete_in_session> sub-element determines which files should be deleted during check in. It includes multiple <plmfile> sub-elements that determine the additional file types to delete. Attributes of the sub-element <plmfile> from sub-element <delete_in_session> from sub-element <save_direct> from <checkin_rules> - 51 / 106 -

52 Parameter Values Description extension filename_pattern "jpg", "gif", "pdf", "bat" "plm_metainf-*.*" The file name extensions of the files to be deleted in the file system. "jpg", "gif", "pdf", "bat" = File name extensions of the additional file types. Filters by file names and regular expressions. "plm_metainf-*.*" = Filter mask. This follows the DType definition for master documents. The previously defined "ACMM" template is included here. DType-Definition for master documents of type "ACAD" for AutoCAD <DType type="master" identifier="acad" include_template="acmm" sort_key="a01" > <description language="en" text="autocad Vanilla document"/> <document_create rename_template_filename="yes"/> <material_create material_type="fert;halb" material_template="" material_plant_assignment="0001" material_default_class=""/> </DType> Attributes of the element <DType> of the DType definition for master documents of type "ACAD" for AutoCAD type identifier include_template sort_key "master" "ACAD" "ACMM" "A01" Specifies the type of DType definition. "Master" = This is the definition for master documents. Unique ID string of this DType definition throughout the XML document. The ID must be one to five characters long. "ACAD" = ID of this master document definition. Determines which template definition is included in this definition. "ACMM" = The DType template with the ID "ACMM" from this "dtype.xml" file is included. Defines a sorting key which is used for an alphanumeric sorting of the DType entries in the combo box for DType selection. "A01" = Sorting key. The contained sub-elements <description> define description texts in different languages. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of sub-element <document_create> rename_template_filename "yes" Determines whether the file name can be changed when creating a document info record. "Yes" = When creating a document info record, the file name of the CAD original can be changed. The <material_create> subelement contains settings for attaching a material to a new document. Attributes of sub-element <material_create> - 52 / 106 -

53 material_type "FERT;HALB" material_template "" material_plant_assignment "0001" material_default_class "" Type or types of material. Possible values can be found in the SAP system. "FERT; HALB" = Material types. Template material that can be specified. The material installation is then done with this master material. The basic data and the classification are copied. "" = No template material. The assigned work. Possible values can be found in the SAP system. "0001" = Identifier of the assigned plant. The default class for the material. Possible values can be found in the SAP system. "" = No standard class. Definition for master documents of type "ACDNR" for AutoCAD Vanilla <DType type="master" identifier="acdnr" include_template="acmm" sort_key="a02" > <description language="en" text="autocad Vanilla document, fixed name"/> <program_options> <copy_as allowed="no"/> <new_version rename_master_original="no"/> </program_options> <document_create rename_template_filename="no" /> <material_create material_type="fert;halb" material_template="" material_plant_assignment="0001" material_default_class="" /> <DType> Attributes of the element <DType> of the DType definition for master documents of type "ACDNR" for AutoCAD type identifier include_template sort_key "master" "ACDNR" "ACMM" "A02" Specifies the type of DType definition. "Master" = This is the definition for master documents. Unique ID string of this DType definition throughout the XML document. The ID must be one to five characters long. "ACDNR" = ID of this master document definition. Determines which template definition is included in this definition. "ACMM" = The DType template with the ID "ACMM" from this "dtype.xml" file is included. Defines a sorting key which is used for an alphanumeric sorting of the DType entries in the combo box for DType selection. "A02" = sorting key. The contained sub-elements <description> define description texts in different languages. The <program_options> sub-element contains various settings that control the behavior of the document in the SAP Engineering Control Center / 106 -

54 Attributes of sub-element <program_options> copy_as allowed new_version rename_master_original "no" "no" Determines whether "Copy as" actions are allowed. "No" = Any "copying as" actions are prohibited for this DType. Determines whether the original is to be renamed during versioning. "No" = When creating a new version, the original is not renamed. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of sub-element <document_create> rename_template_filename "yes" Determines whether the file name can be changed when creating a document info record. "Yes" = When creating a document info record, the file name of the CAD original can be changed. The <material_create> subelement contains settings for attaching a material to a new document. Attributes of sub-element <material_create> material_type "FERT;HALB" material_template "" material_plant_assignment "0001" material_default_class "" Type or types of material. Possible values can be found in the SAP system. "FERT; HALB" = Material types. Template material that can be specified. The material installation is then done with this master material. The basic data and the classification are copied. "" = No template material. The assigned work. Possible values can be found in the SAP system. "0001" = Identifier of the assigned plant. The default class for the material. Possible values can be found in the SAP system. "" = No standard class. The DType definition for master documents of type "ACDWF" follows. Definition for master documents of type "ACDWF" for AutoCAD Vanilla <DType type="master" identifier="acdwf" include_template="acgen" > <description language="en" text="autocad Vanilla document, fixed name"/> <program_options dirty_flag="no" function_group="doc" customer_data_section=""> </program_options> <document_create document_number_assignment="internal" initial_document_number="*" document_type="dwf" initial_document_part="000" part_editable="no" initial_document_version="00" version_editable="no"> <seedfile filename="" type="select" - 54 / 106 -

55 default="yes" extension_filter="*.dwf,*.dwfx" dictionary_identifier="select" > <description language="en" text="select existing file" /> </seedfile> </document_create> <primary_application primary_workstation_application="dwf" attribute_section="default" > <checkin_rules> <save_direct> <plmfile extension="jpg" workstation_application="epj" description="ectr Preview (jpeg)"/> <plmfile extension="gif" workstation_application="epg" description="ectr Preview (gif)"/> </save_direct> <ignore> <plmfile filename_pattern="plm_metainf-*.*"/> </ignore> <delete_in_session> <plmfile filename_pattern="plm_metainf-*.*"/> </delete_in_session> </checkin_rules> </primary_application> <DType> Attributes of the element <DType> of the DType definition for master documents of type "ACDWF" for AutoCAD type identifier include_template "master" "ACDWF" "ACGEN" Specifies the type of DType definition. "Master" = This is the definition for master documents. Unique ID string of this DType definition throughout the XML document. The ID must be one to five characters long. "ACDWF" = ID of this master document definition. Determines which template definition is included in this definition. "ACGEN" = The DType template with the ID "ACGEN" from this "dtype.xml" file is included. The contained sub-elements <description> define description texts in different languages. The <program_options> sub-element contains various settings that control the behavior of the document in the SAP Engineering Control Center. Attributes of the sub-element <program_options> dirty_flag function_group "no" "DOC" Determines if the dirty flag should be set. "No" = Do not set dirty flag. Specifies the function group to which the document belongs. For documents with a common function group, e.g. Custom context menus. "DOC" = This DType is assigned to the function group "DOC" / 106 -

56 customer_data_section "" Name of a section in the attribute mapping file in which customer-specific data are defined. The data is displayed in the Object Browser under the "Customer data" tab. "" = No section is defined. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of sub-element <document_create> document_number_assignment initial_document_number "*" "internal" Defines the document number assignment in SAP. "Internal" = SAP assigns the number automatically. For internal number assignment, the value in this field is of no significance. For external numbers, this value is entered as a prefix in the input field of the document layout dialog. The user can delete / change the prefix at any time. "*" = No meaning, because document_number_assignment = "internal". document_type "DWF" initial_document_part "000" SAP Document type for the newly created document. "DWF" = AutoCAD document. SAP document part or as a semicolon-separated list of SAP document parts for the new document to be created. If a list of partial documents has been specified, one of the partial documents can be selected from a selection list in the document creation dialog of the SAP Engineering Control Center. part_editable "no" "000" = Initial value for document part. Defines whether the default value or the selected SAP document part from the attribute "initial_document_part" in the input field can be changed in the SAP Engineering Control Center document dialog creation dialog. "No" = The default value in the document creation dialog can not be changed. initial_document_version "00" SAP document version or as a semicolon-separated list of document versions for the newly created document. If a list of document versions has been specified, one of the document versions can be selected from the selection list in the SAP Engineering Control Center document creation dialog. version_editable "no" "00" = Initial document version. Defines whether the default value for the document version can be changed from the "initial_document_version" attribute in the SAP Engineering Control Center document creation dialog. "No" = The default value can not be changed. The <seedfile> sub-element contains settings for the template file. Several template files can be assigned, in other words the <seedfile> may occur more than once. This includes the <description> sub-element, which defines each description text in different languages. Attributes of sub-element <seedfile> filename "" type "select" The filename attribute specifies the template file to be used. In the Create Document dialog, you can select a template file using a file selection dialog. "" = No template file specified. Determines how the original of the document is generated. The filename attribute specifies the template file to be used. A template file can be selected in the dialog "Create document" by means of a file selection dialog. "Select" = Select a template file in the "Create document" dialog / 106 -

57 default extension_filter dictionary_identifier "yes" "*.dwf,*.dwfx" "select" This can be used to determine whether this template file is preset in the "Create Document" dialog. "No" = This template file is preset. When selecting a template file with type = "select", this attribute defines the filter for the file extension. In the file selection dialog, the files matching the filter are offered for selection. "*.dwf, *. dwfx" = filter for file extension. If no description is provided for the template file, the plm searches for the plm.dtype.description. <Dtype_id> key and uses the description there. "Select" = Select a template file in the "Create document" dialog. The sub-element <primary_application> determines which application is responsible for this master document (primary application) and defines the rules for checking in and checking out the originals. Attributes of sub-element <primary_application> primary_workstation_application "DWF" "DWF" = ID of the SAP workstation application attribute_section "default" Name of a section in the attribute mapping file in which the attribute exchange between SAP and the application is defined. "Default" = Name of the section in the attribute mapping file The <checkin_rules> subelement determines how files in the additional directory and originals on the document are handled when they are checked in. For this, it contains several subelements. The sub-element <save_direct> determines which additional files (additional formats) are stored in the additional directory when saving as originals on the document. It contains the subelement <plmfile>, which defines the individual additional file types. Attributes of sub-elements <plmfile> of the sub-element <save_direct> of <checkin_rules> extension workstation_application description "jpg", "gif" "EPJ", "EPG" "ECtr Preview (jpeg)", "ECtr Preview (gif)" The respective filename extensions of the additional files in the file system. "Jpg", "gif" = The respective filename extensions. Identifiers of the workstation application for the individual additional formats. "EPJ", "EPG" = Identifiers of the workstation application. Description of the additional files. "ECtr Preview (jpg)", "ECtr Preview (gif)" = Description of additional files. The <ignore> subelement defines which files are ignored when saving. For this purpose, it contains the subelement <plmfile>, which defines the additional data type to be ignored. Attributes of sub-elements <plmfile> of the sub-element <ignore> of sub-element <save_direct> of <checkin_rules> filename_pattern "plm_metainf-*.*" Filters by filenames using regular expressions. "Plm_metainf - *. *" = Filter mask. The subelement <delete_in_session> defines which files are deleted during check-in. For this purpose, it contains the subelement <plmfile>, which defines the additional data types to be deleted / 106 -

58 Attribute of sub-element <plmfile> of sub-element <delete_in_session> of sub-element <save_direct> of <checkin_rules> filename_pattern "plm_metainf-*.*" Filters by filenames using regular expressions. "Plm_metainf - *. *" = Filter mask. The DType definition for master documents of type "ACDST" follows. Definition for master documents of type "ACDST" for AutoCAD Vanilla <DType type="master" identifier="acdst" include_template="acgen" application_role="a"> <description language="en" text="autocad Sheet Set"/> <icon> <icondef icon_position="1" icon_group="default" icon_identifier="tree/acd/autocad_sheetset_16"/> </icon> <program_options dirty_flag="yes" function_group="doc_acdst" customer_data_section="" auto_adjust_application_role="no"> </program_options> <document_create document_number_assignment="internal" initial_document_number="*" document_type="dst" initial_document_part="000" part_editable="no" initial_document_version="00" version_editable="no"> <seedfile filename="empty.dst" type="template" default="yes" dictionary_identifier="empty" > <description language="en" text="empty Sheet Set" /> </seedfile> <seedfile filename="" type="select" default="no" extension_filter="*.dst" dictionary_identifier="select" > <description language="en" text="select existing file" /> </seedfile> </document_create> <primary_application primary_workstation_application="dst" attribute_section="dst" > <checkin_rules from_application_only="yes"> <save_direct> <plmfile extension="jpg" workstation_application="epj" description="ectr Preview (jpeg)"/> <plmfile extension="gif" workstation_application="epg" description="ectr Preview (gif)"/> <plmfile extension="pdf" workstation_application="pdf" description="$(filename)" /> <plmfile extension="dwf" workstation_application="dwf" description="$(filename)" /> - 58 / 106 -

59 <plmfile extension="dwfx" workstation_application="dwf" description="$(filename)" /> </save_direct> <ignore> <plmfile filename_pattern="plm_metainf-*.*"/> <plmfile extension="dbl"/> <plmfile extension="ds$"/> </ignore> <delete_in_sap> <plmfile workstation_application="epj"/> <plmfile workstation_application="epg"/> <plmfile workstation_application="pdf"/> <plmfile workstation_application="dwf"/> </delete_in_sap> <delete_in_session> <plmfile filename_pattern="plm_metainf-*.*"/> <plmfile extension="jpg" /> <plmfile extension="gif" /> <plmfile extension="pdf" /> <plmfile extension="dwf" /> <plmfile extension="dwfx" /> </delete_in_session> </checkin_rules> </primary_application> <DType> Attributes of the element <DType> of the DType definition for master documents of type "ACDST" for AutoCAD type identifier include_template application_role "master" "ACDST" "ACGEN" "A" Defines the type of DType definition. "master" = This is the definition for master documents. Unique ID string of this DType definition in the entire XML document. The ID must be one to five characters long. "ACDST" = ID of this master document definition. Determines which template definition is included in this definition. "ACGEN" = The DType template with the ID "ACGEN" from this "dtype.xml" file is included. Setting of object type in the RES4 field of SAP table DRAW. "A" = Assembly. The contained subelements <description> define description texts in different languages. The subelement <icon> defines with the subelement <icondef> the symbol used and its position for this DType. Attributes of subelement <icondef> of subelement <icon> Attribut Wert Beschreibung icon_position "1" icon_group "default" Determines the position of the symbol in the document entry in the tree. "1" = Position 1. ID of the icon group. "default" = Standard icon / 106 -

60 icon_identifier "tree/acd/autocad_sheetset_16" Path and name of the icon file. "tree/acd/autocad_sheetset_16" = Path and name of the icon file. The <program_options> subelement contains various settings that control the behavior of the document in SAP Engineering Control Center. Attributes of the subelement <program_options> dirty_flag "yes" function_group "DOC_ACDST" customer_data_section "" auto_adjust_application_role "no" Determines whether the dirty flag should be set. "yes" = Set the dirty flag. Determines the function group to which the document belongs. For documents with a shared function group, for example, you can define your own context menus. "DOC_ACDST" = This DType is assigned to the function group "DOC_ACDST". Name of a section in the attribute mapping file in which customer-specific data is defined. The data is displayed in the Object Browser in the "Customer Data" tab. "no" = No section is defined. Switches the automatic adaptation of the application role in RES4 on or off. "no" = No automatic adjustment. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of the subelement <document_create> document_number_assignment initial_document_number "*" "internal" Defines the document number assignment in SAP. "internal" = SAP assigns the number automatically. For internal number assignment, the value in this field has no meaning. For external number assignment, this value is entered as a prefix in the input field of the document creation dialog. The user can delete / change the prefix at any time. "*" = No meaning, because document_number_assignment = "internal". document_type "DST" initial_document_part "000" SAP document type for the newly created document. "DST" = AutoCAD Sheet Set document. SAP part document or as a semicolon-separated list of SAP part documents for the document to be created. If a list of part documents has been specified, one of the part documents can be selected from a selection list in the SAP Engineering Control Center "Create document" dialog. part_editable "no" "000" = Initial value for part document. Defines whether the default value or the selected SAP part document from the Attribute "initial_document_part" can be changed in the input field in the SAP Engineering Control Center "Create document" dialog. "no" = The default value in the document creation dialog cannot be changed. initial_document_version "00" SAP document version or as a semicolon-separated list of document versions for the newly created document. If a list of document versions has been specified, one of the document versions can be selected from the selection list in the SAP Engineering Control Center "Create document" dialog. "00" = Initial document version / 106 -

61 version_editable "no" Determines whether the default value for the document version from the attribute "initial_document_version" can be changed in the SAP Engineering Control Center "Create document" dialog. "no" = The default value cannot be changed. The <seedfile> subelement contains settings for the template file. Several template files can be assigned, i.e. <seedfile> can occur more than once. This contains the <description> subelement, which defines description texts in different languages. Attribute of the 1. subelement <seedfile> filename type default extension_filter dictionary_identifier "empty.dst" "select" "yes" "*.dst" "empty" The filename attribute specifies the template file to be used. In the "Create document" dialog, you can select a template file using a file selection dialog. "empty.dst" = Name of the template file. Determines how the original of the document is created. The filename attribute specifies the template file to be used. A template file can be selected in the "Create document" dialog using a file selection dialog. "select" = Selection of a template file possible in the "Create document" dialog. This allows you to determine whether this template file is preset in the"create document" dialog. "yes" = This template file is preset. When selecting a template file with type="select", this attribute defines the filter for the file extension. The files matching the filter are offered for selection in the file selection dialog. "*.dst" = Filter for the file extension. If no description is stored for the template file, it will be searched in the dictionary for the key plm.dtype.description.<dtype_id> and uses the description there. "empty" = No selection of a template file possible. Attributes of the 2. subelement <seedfile> filename "" type "select" default "no" extension_filter "*.dst" dictionary_identifier "select" The filename attribute specifies the template file to be used. In the "Create document" dialog, you can select a template file using a file selection dialog. "" = No template file. Determines how the original of the document is created. The filename attribute specifies the template file to be used. A template file can be selected in the "Create Document" dialog using a file selection dialog. "select" = Selection of a template file possible in the "Create document" dialog. This allows the user to determine whether this template file is preset in the "Create document" dialog. "no" = This template file is not preset. When selecting a template file with type="select", this attribute defines the filter for the file extension. The files matching the filter are offered for selection in the file selection dialog. "*.dst" = Filter for the file extension. WIf no description is stored for the template file, it will be searched in the dictionary for the key plm.dtype.description.<dtype_id> and uses the description there. "select" = A selection of a template file is possible in the "Create document" dialog / 106 -

62 The <primary_application> subelement specifies which application is responsible for this master document (primary application) and defines the rules for checking originals in and out. Attributes of the subelement <primary_application> primary_workstation_application "DST" "DST" = ID of the SAP workstation application. attribute_section "DST" Name of a section in the attribute mapping file in which the attribute exchange between SAP and the application is defined. "DST" = Name of the section in the attribute mapping file. The <checkin_rules> subelement specifies how files in the Additional directory and originals on the document are handled during checkin. To do this, it contains several subelements. The <save_direct> subelement determines which additional files (additional formats) are stored in the Additional directory when the document is saved as originals. It contains the <plmfile> subelement that specifies the individual additional file types. Attributes of the subelements <plmfile> of subelement <save_direct> of <checkin_rules> extension workstation_application description "jpg", "gif" "EPJ", "EPG" "ECtr Preview (jpeg)", "ECtr Preview (gif)" The respective file name extensions of the additional files in the file system. "jpg", "gif" = The respective file name extensions. IDs of the workstation application for the individual additional formats. "EPJ", "EPG" = IDs of the workstation application. Description of the respective additional files. "ECtr Preview (jpeg)", "ECtr Preview (gif)" = Description of the additional files. The <ignore> subelement defines which files are ignored during save. It contains the <plmfile> subelement, which specifies the additional file type to be ignored. Attributes of the subelements <plmfile> of subelement <ignore> of subelement <save_direct> of <checkin_rules> Attribute Values Description filename_pattern extension "plm_metainf-*.*" "dbl", "ds$" Filters by file name using regular expressions. "plm_metainf-*.*" = Filter mask. Filters by file name extensions in the file system. "dbl", "ds$" = File name extensions. The <delete_in_sap> subelement defines which originals in the document are deleted during checkin. This enables a targeted cleanup of the document. To do this, it contains the <plmfile> subelement, which specifies the additional file types to be deleted. Attributes of the subelements <plmfile> of subelement <delete_in_sap> of subelement <save_direct> of <checkin_rules> Attribute Values Description workstation_application "EPJ", "EPG", "PDF", "DWF" IDs of the workstation application for the individual additional formats. "EPJ", "EPG", "PDF", "DWF" = IDs of the workstation application. The <delete_in_session> subelement defines which files are deleted at checkin. To do this, it contains the <plmfile> subelement, which specifies the additional file types to be deleted / 106 -

63 Attributes of the subelements <plmfile> of subelement <delete_in_session> of subelement <save_direct> of <checkin_rules> Attribute Values Description filename_pattern extension "plm_metainf-*.*" "jpg", "gif", "pdf", "dwf", "dwfx" Filters by file name using regular expressions. "plm_metainf-*.*" = Filter mask. Filters by file name extensions in the file system. "jpg", "gif", "pdf", "dwf", "dwfx" = file name extensions DType definitions for AutoCAD Mechanical With the installation of the SAP Engineering Control Center interface to AutoCAD Mechanical the file "dtype.xml" is delivered. This includes the DType definitions that are essential for the interaction with the SAP Engineering Control Center. Below these definitions will be explained. The definition is divided into three areas: Generic functions (template definition) Master document definitions The correlation of the DType definitions as well as their dependencies is shown in the following table: Overview about DType definitions for AutoCAD Mechanical DType-ID Type App-Type Description DEFLT Template Base template from SAP/DSC +- AMGEN Template ACM Base template for AutoCAD Mechanical documents +- ACMMM Template ACM Base template for DWG-drawings as Master +- ACADM Master ACM Drawing (DWG) +- AMDWF Master ACM Design Web Format file (DWF) +- AMDST Master ACM Sheet Set Data file (DST) +- AMPC Master ACM Sample configuration: Point clouds +- ACPIC Master PIC Sample configuration: Raster images The following are the descriptions of the individual definitions for AutoCAD Mechanical documents Generic DType definition The generic definition is a template with basic definitions that are valid for all AutoCAD file types. It is integrated in the other DType definitions. Generic DType definition for AutoCAD Mechanical <DType type="template" identifier="amgen" include_template="deflt" application_type="acm" group="autocad Mechanical"> <icon> <icondef icon_position="1" icon_group="default" icon_identifier="tree/acm/autocad_drawing_16"/> </icon> - 63 / 106 -

64 <program_options show_for_create="yes" has_primary_application="yes" dirty_flag="yes" attempt_status_change_on_checkin="yes" dataexchange_rename_on_import="yes" dataexchange_show_for_import="yes"> <copy_as allowed="yes" ignore_wsappl_list="zip" use_initial_version="yes" copy_material="no" remove_dirty_flag="no" /> <new_version status_list="ac;fr" ignore_wsappl_list="zip" ignore_nm_dtype_list="drwt;draw" remove_dirty_flag="no" rename_master_original="no"/> </program_options> <document_create create_with_sap_gui="no" create_multi_allowed="no" change_to_after_create_status="" filename_template_base="$(docnumber)$(doctype)$(docpart)" filename_template_version=""> </document_create> <primary_application attribute_section="stdmod" update_attributes_for_dirty="yes" update_attributes_for_rw="yes" update_attributes_for_ro="no"> <container_file> <plmfile extension="ecf" workstation_application="ecf" description="ectr container file"/> </container_file> <checkout_rules check_references_on_edit="yes" rename_master_original_at_checkout="no" one_version_in_session_only="no" hardlink_in_session="no"> </checkout_rules> </primary_application> </DType> Attributes of the element <DType> type "template" Sets the kind of DType definition. "template" = This is a DType template definition. identifier include_template application_type group "AMGEN" "DEFLT" "ACM" "AutoCAD Mechanical" Non-ambiguous ID string to this definition of DType within the entire XML document. The ID has to be between one to five characters long. "AMGEN" = ID of this template definition. Sets which template definition should be integrated into this definition. "DEFLT" = The DType template with ID "DEFLT" from global "dtype.xml" file will be included. Designates the application that is relevant for this document. This application opens the file from SAP Engineering Control Center. "ACM" = This is the application type for AutoCAD Mechanical. Defines the group designation for master documents. The group designation helps organizing the DTypes within dialogue "Create Document". "AutoCAD Mechanical" = Document belongs to this group / 106 -

65 The sub-element <icon> defines an acronym that will be used when determining the applicable symbol in SAP Engineering Control Center. It also contains the sub-element <icondef>. Attributes of the sub-element <icondef> from sub-element <icon> icon_position "1" icon_group "default" icon_identifier "tree/acd/autocad_drawing_16" Position of the symbols in the document entry in the tree. "1" = Left, "6" = Right. Identification of a symbol group. Status-depending, other symbols can be represented. "default" = This is the standard symbol. Path to determine the icon file, which contains the applicable symbol for this symbol position. "tree/acd/autocad_drawing_16" = the icon file. The sub-element <program_options> contains different settings, which control the behavior of the document in the SAP Engineering Control Center. Attributes of the sub-element <program_options> show_for_create has_primary_application dirty_flag attempt_status_change_on_checkin dataexchange_rename_on_import dataexchange_show_for_import "yes" "yes" "yes" "yes" "yes" "yes" Determines if in dialogue "Create Document " this DType is visible in the combo box for accessible document types. "yes" = document visible. Determines if document is normal document with original and designated Workstation Application or container object for additional originals without explicit original. "yes" = document possesses original with designated Workstation Application. Determines if the newly created document has a dirty flag. "yes" = The document possesses a dirty flag. Determines if change of status applies during check in at SAP Engineering Control Center or if SAP System conducts change of status. "yes" = change of status by SAP Engineering Control Center. Determines if original is renamed during import. "yes" = Original will be renamed during import according to determined rules and dependent on document. Determines if this DType can be used during import. "yes" = This DType is available during import. The sub-element <copy_as> determines how the document behaves during "CopyAs"-activity and how SAP Engineering Control Center reacts to the document. Attributes of the sub-element <copy_as> from sub-element <program_options> allowed ignore_wsappl_list "yes" "ZIP" Determines if a "CopyAs"- operation is permitted for this DType. "yes" = "CopyAs" - operation permitted. Determines which additional originals of the document will be accepted during copy but not into copy of document according to a table of identifiers for the Workstation Application for additional originals all of which are separated by semicolon. "ZIP" = Additional originals of type "ZIP" (ZIP-archive) will not be copied / 106 -

66 use_initial_version copy_material remove_dirty_flag "yes" "no" "no" Determines if the number of version of the copy is to be set on the original or on to initial value (in most cases "00"). "yes" = Number of copy version to be set onto initial value. Determines if designated material will also be copied during copy of master document. This attribute has no influence on depending documents, which are copied onto the master documents during copy process. "no" = Material will not be copied. Determines if dirty flag of copy will be reset. "no" = The dirty flag of copy remains set. The sub-element <new_version> contains settings for versioning of documents. Attributes of the sub-element <new_version> from sub-element <program_options> status_list ignore_wsappl_list ignore_nm_dtype_list remove_dirty_flag rename_master_original "AC;FR" "ZIP" "DRWT;DRAW" "no" "no" Determines the type of document status that allows visioning of documents. A table of document status can be separately stated through ";". "AC;FR" = With this kind of document status new versions are allowed. Determines which additional originals of the document will be accepted during versioning but not into new version of document according to a table of identifiers for the Workstation Application for additional originals all of which are separated by semicolon. "ZIP" = Additional originals of type "ZIP" (ZIP-archive) will not be copied. Determines which depending documents will be ommitted during versioning of master documents. Depending documents to be omitted will be listed in a table of DTypes, separated by semicolon. "DRWT;DRAW" = Table of document types to be omitted. Determines if dirty flag of new version will be reset. "no" = The dirty flag of new version remains set. Determines whether the original file name is assigned a file name according to the part rules for this DType during versioning or whether the previous file name is retained unchanged. "no" = Keep file name unchanged. The sub-element <document_create> contains settings that control the way in which a new document is created in SAP. Attributes of the sub-element <document_create> create_with_sap_gui "no" create_multi_allowed "no" change_to_after_create_status "" Determines if SAP GUI should be opened when creating a document. "no" = Don't open SAP GUI. Determines if the mass creation of this document is allowed. "no" = Mass creation of this document in not permitted. Initial status of newly created document can be set here. "" = Standard status will be used / 106 -

67 filename_template_base filename_template_version "" "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)" Determines composition of file name of original document. The following place holders are possible: $(DOCNUMBER) for the document number, $(DOCTYPE) for the document type and $(DOCPART) for partial document. "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)" = The file name consists of document number, document type and partial document. Determines the composition of the document version in the file name for the original of this document. The following placeholder can be used: $(DOCVERSION) for the document version. "" = No version in the file name. The sub-element <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 the originals. Attributes of the sub-element <primary_application> attribute_section update_attributes_for_dirty update_attributes_for_rw update_attributes_for_ro "STDMOD" "yes" "yes" "no" Name of section within Attribute Mapping File, in which attributes exchange between SAP and the application is defined. "STDMOD" = Name of section within Attribute Mapping File. Defines if to update the attributes when dirty flag was set. "yes" = Perform Attribute Update. Defines the attribute update at the operation "Open for edit". "yes" = Perform Attribute Update. Defines the attribute update at the operation "Open for edit with read-only". "yes" = Don't Perform Attribute Update. The Subelement <container_file> defines the properties of the ZIP archive, which is stored as a container file in the document. These properties are defined in the sub-element <plmfile>. Attribute of the sub-element <plmfile> of the sub-element <container_file> of sub-element <primary_application> extension workstation_application description "ecf" "ECF" "ECtr container file" File extension in the file system. "ecf" = The file extension for container files. Workstation application for container files. "ECF" = The workstation application. Description of the file type container file. "ECtr container file" = The description. The sub-element <checkout_rules> determines how to treat the original of document at checkout. Attributes of the sub-element <checkout_rules> from sub-element <primary_application> check_references_on_edit "yes" Defines if under function "Open for Edit" all files for referenced components were provided in the session directory. Test has been done If not, operation will be abandoned. "yes" = Run test / 106 -

68 rename_master_original_at_checkout one_version_in_session_only hardlink_in_session "no" "no" "no" >Defines if original is renamed during opening according to rules for component names. "no" = Keep file name during opening. Determines if document must have only one version in session directory. "no" = Multiple versions of document are allowed in session directory. Determines if hard link may be used for original document in the session directory or if copy creation is always necessary. "no" = Always create copy DType definition for master documents The SAP Engineering Control Center distinguishes between master documents and dependent documents. The master document is the main document and contains the CAD model file to be processed. In addition, the master document is the basis for the preparation of the bill of materials. It is recommended to maintain only the language English directly in the file "dtype.xml"! All other languages will be offered via the particular "dictionary.txt" file. This affects the definitions of DTypes and Seedfiles. All elements <description language="xy"> are omitted except English which are used as fallback. The DType definition is divided into a template definition and the actual DType definition for master documents. The template is included here. Template definition for master documents for AutoCAD Mechanical <DType type="template" identifier="acmmm" include_template="amgen"> <program_options function_group="doc_acm" customer_data_section=""/> <document_create document_type="acm" document_number_assignment="internal" initial_document_number="*" initial_document_part="000" part_editable="no" initial_document_version="00" version_editable="no"> <seedfile filename="acad.dwg" type="template" default="yes" dictionary_identifier="acad"> <description language="en" text="empty drawing" /> </seedfile> <seedfile filename="@plm_instdir@\applications\acm\templates\samples\cideon_din_a4.dwg" type="template" default="no" dictionary_identifier="samples.cideon_din_a4"> <description language="en" text="cideon DIN A4 sample drawing" /> </seedfile> <seedfile filename="@plm_instdir@\applications\acm\templates\samples\cideon_din_a2.dwg" type="template" default="no" dictionary_identifier="samples.cideon_din_a2"> <description language="en" text="cideon DIN A2 sample drawing" /> - 68 / 106 -

69 </seedfile> <seedfile filename="" type="select" default="no" extension_filter="*.dwg" dictionary_identifier="select"> <description language="en" text="select existing drawing" /> </seedfile> </document_create> <material_create material_creation_method="deferred" material_number_assignment="internal"/> <primary_application primary_workstation_application="acm" attribute_section="acm"> <checkin_rules from_application_only="yes"> <save_direct> <plmfile extension="jpg" workstation_application="epj" description="ectr Preview (jpeg)"/> <plmfile extension="gif" workstation_application="epg" description="ectr Preview (gif)"/> <plmfile extension="txt" workstation_application="txt" description="$(filename)"/> <plmfile extension="pdf" workstation_application="pdf" description="$(filename)" /> <plmfile extension="dwf" workstation_application="dwf" description="$(filename)" /> <plmfile extension="dwfx" workstation_application="dwf" description="$(filename)" /> <!-- <plmfile extension="bmp" workstation_application="aci" description="$(filename)" /> <plmfile extension="tga" workstation_application="aci" description="$(filename)" /> <plmfile extension="pcx" workstation_application="aci" description="$(filename)" /> <plmfile extension="cal" workstation_application="aci" description="$(filename)" /> <plmfile extension="rcs" workstation_application="apc" description="$(filename)" /> <plmfile extension="rcp" workstation_application="apc" description="$(filename)" /> --> <plmfile filename_pattern="plm_metainf-viewing\.xml" workstation_application="evi" description="ectr Viewing metainf" /> </save_direct> <ignore> <plmfile extension="bak"/> <plmfile extension="tmp"/> <plmfile extension="bat"/> <plmfile filename_pattern="plm_metainf-*.*"/> </ignore> <delete_in_sap> <plmfile workstation_application="epj"/> <plmfile workstation_application="epg"/> <plmfile workstation_application="pdf"/> - 69 / 106 -

70 <plmfile workstation_application="dwf"/> <plmfile workstation_application="pic"/> <!-- <plmfile workstation_application="aci"/> <plmfile workstation_application="apc"/> --> <plmfile workstation_application="evi"/> </delete_in_sap> <delete_in_session> <plmfile extension="jpg"/> <plmfile extension="gif"/> <plmfile extension="pdf" /> <plmfile extension="bat"/> <plmfile filename_pattern="plm_metainf-*.*"/> </delete_in_session> </checkin_rules> </primary_application> </DType> Attributes of element <DType> of the template definition "ACMMM" type identifier include_template "template" "ACMMM" "AMGEN" Specifies the type of DType definition. "Template" = This is a DType template definition. Unique ID string of this DType definition throughout the XML document. The ID must be one to five characters long. "ACMMM" = ID of this template definition. Determines which template definition is included in this definition. "AMGEN" = The DType template with the ID "AMGEN" from this "dtype.xml" file is included. This is the generic definition. The <program_options> subtree contains various settings that control the behavior of the document in the SAP Engineering Control Center. Attributes of sub-element <program_options> function_group customer_data_section "" "DOC_ACM" Specifies the function group to which the document belongs. For documents with a common function group, e.g. custom context menus. "DOC_ACM" = This DType is assigned to the function group "DOC_ACM". Name of a section in the attribute mapping file in which customer-specific data are defined. The data is displayed in the Object Browser under the "Customer data" tab. "" = No section is defined. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of sub-element <document_create> document_type "ACM" SAP Document type for the newly created document. "ACM" = AutoCAD Mechanical Document / 106 -

71 document_number_assignment initial_document_number "*" "internal" Defines the document number assignment in SAP. "Internal" = SAP assigns the number automatically. For internal numbering, the value in this field is of no significance. For external numbering, this value is entered as a prefix in the input field of the document layout dialog. The user can delete / change the prefix at any time. "*" = No meaning, because document_number_assignment = "internal". initial_document_part "000" SAP document part or as a semicolon-separated list of SAP document parts for the new document to be created. If a list of document parts has been specified, the document create dialog of one of the document parts can be selected from a selection list in the SAP Engineering Control Center. part_editable "no" "000" = Initial value for document part. Defines whether the default value or the selected SAP document part from the attribute "initial_document_part" in the input field can be changed in the SAP Engineering Control Center document create dialog. "No" = The default value in the document creation dialog can not be changed. initial_document_version "00" SAP document version or as a semicolon-separated list of document versions for the newly created document. If a list of document versions has been specified, one of the document versions can be selected from the selection list in the SAP Engineering Control Center document creation dialog. version_editable "no" "00" = Initial document version. Defines whether the default value for the document version can be changed from the "initial_document_version" attribute in the SAP Engineering Control Center document creation dialog. "No" = The default value can not be changed. The <seedfile> subelement contains settings for the template file. Several template files may be associated, e.g. <Seedfile> can occur several times. This contains the subelement <description>, which in each case defines descriptive texts in different languages. Attributs Value Description Attributes of the 1. sub-element <seedfile> of sub-element <document_create> filename type default "acad.dwg" "template" "yes" When using type = "template", this attribute defines the filename of the template file that is used. A file with this name must exist, otherwise it is aborted with errors. "Acad.dwg" = filename of the template file to use. Determines how the original of the document is generated. "Template" = The "filename" attribute specifies the template file to use. This can be used to determine whether this template file is preset in the "Create Document" dialog. "Yes" = This template file is preset. Attributes of the 2. sub-element <seedfile> of sub-relement <document_create> filename "@PLM_INSTDIR@\ applications\acm\ templates\samples\ CIDEON_DIN_A4.dwg" The filename attribute specifies the template file to be used. In the "Create Document" dialog, you can select a template file using a file selection dialog. "@PLM_INSTDIR@\applications\acm\templates\ samples\cideon_din_a4.dwg" = filename of the template file / 106 -

72 type default dictionary_identifier "template" "no" "samples.cideon_din_a4" Determines how the original of the document is generated. "Template" = The "filename" attribute specifies the template file to use. This can be used to determine whether this template file is preset in the "Create Document" dialog. "No" = This template file is not preset. If no description is provided for the template file, the plm searches for the plm.dtype.description.<dtype_id> key and uses the description there. "Samples.CIDEON_DIN_A4" = Description of the template file. Attributes of the 2. sub-element <seedfile> of sub-relement <document_create> filename type default dictionary_identifier "@PLM_INSTDIR@\ applications\acm\ templates\samples\ CIDEON_DIN_A2.dwg" "template" "no" "samples.cideon_din_a2" The filename attribute specifies the template file to be used. In the "Create Document" dialog, you can select a template file using a file selection dialog. "@PLM_INSTDIR@\applications\acm\templates\ samples\cideon_din_a2.dwg" = filename of the template file. Determines how the original of the document is generated. "Template" = The "filename" attribute specifies the template file to use. This can be used to determine whether this template file is preset in the "Create Document" dialog. "No" = This template file is not preset. If no description is provided for the template file, the plm searches for the plm.dtype.description.<dtype_id> key and uses the description there. "Samples.CIDEON_DIN_A2" = Description of the template file. Attributes of the 2. sub-element <seedfile> of sub-relement <document_create> filename "" type "select" default "no" extension_filter "*.dwg" dictionary_identifier "select" The filename attribute specifies the template file to be used. In the "Create Document" dialog, you can select a template file using a file selection dialog. "" = No file name specified. Determines how the original of the document is generated. The filename attribute specifies the template file to be used. A template file can be selected in the "Create document" dialog by means of a file selection dialog. "Select" = Select a template file in the "Create document" dialog. This can be used to determine whether this template file is preset in the "Create Document" dialog. "No" = This template file is not preset. When selecting a template file with type = "select", this attribute defines the filter for the file extension. In the file selection dialog, the files matching the filter are offered for selection. "*.dwg" = filter for file extension. If no description is provided for the template file, the plm searches for the plm.dtype.description.<dtype_id> key and uses the description there. "Select" = Select a template file in the "Create document" dialog. The <material_create> subelement contains settings for attaching a material to a new document / 106 -

73 Attributes of sub-element <material_create> material_creation_method material_number_assignment "deferred" "internal" Determines whether and how a material is created for a new document. "Deferred" = No material is created for the document. A subsequent material installation for this document is possible. Defines the material number assignment in the SAP system. "Internal" = SAP assigns the material number automatically. The sub-element <primary_application> determines which application is responsible for this master document (primary application) and defines the rules for checking in and checking out the originals. Attributes of sub-element <primary_application> primary_workstation_application "ACM" "ACM" = ID of the SAP workstation application for AutoCAD Mechanical. attribute_section "ACM" Name of a section in the attribute mapping file in which the attribute exchange between SAP and the application is defined. "ACM" = Name of the section in the attribute mapping file. The <checkin_rules> subelement determines how files in the additional directory and originals on the document are handled when they are checked in. For this, it contains several subelements. Attribute of the sub-element <checkin_rules> from <primary_application> from_application_only "yes" "yes" = Prevents a document from being checked in without CAD in the desktop view of the ECTR via the context menu. The sub-element <save_direct> determines which additional files (additional formats) are stored in the additional directory when saving as originals on the document. It contains the subelement <plmfile>, which defines the individual additional file types. Attributes of the sub-elements <plmfile> of sub-element <save_direct> of <checkin_rules> extension workstation_application description filename_pattern "jpg", "gif", "txt", pdf", "dwf", "dwfx" "EPJ", "EPG", "TXT", "PDF", "DWF", "EVI" "ECtr Preview (jpeg)", "ECtr Preview (gif)", "$(FILENAME)" "plm_metainf-viewing\.xml" The respective filename extensions of the additional files in the file system. "Jpg", "gif", "txt", pdf "," dwf "," dwfx "= The respective file extensions. Identifiers of the workstation application for the individual additional formats. "EPJ", "EPG", "TXT", "PDF", "DWF", "EVI" = Identifiers of the workstation application. Description of the additional files. "ECtr Preview (jpg)", "ECtr Preview (gif)", "$ (FILENAME)" = Description of additional files. Filters by filenames using regular expressions. "Plm_metainf-viewing \.xml" = filter mask. The <ignore> subelement defines which files are ignored when saving. For this purpose, it contains the subelement <plmfile>, which defines the additional data types to be ignored / 106 -

74 Attributes of the sub-elements <plmfile> of sub-element <ignore> of sub-element <save_direct> of <checkin_rules> extension filename_pattern "bak", "tmp", "bat" "plm_metainf-*.*" The respective file name extensions of the additional data types to be ignored in the file system. "Bak", "tmp", "bat" = file extensions of the additional data types. Filters by filenames using regular expressions. "Plm_metainf - *. *" = Filter mask. The subelement <delete_in_sap> defines which originals are deleted from the document at check-in. This allows a targeted cleanup of the document. For this purpose, it contains the subelement <plmfile>, which defines the additional data types to be deleted. Attributes of the sub-elements <plmfile> of sub-element <delete_in_sap> of sub-element <save_direct> of <checkin_rules> workstation_application "EPJ", "EPG", "PDF", "DWF", "PIC", "EVI" Identifiers of the workstation application for the individual additional formats. "EPJ", "EPG", "PDF", "DWF", "PIC", "EVI" = Identifiers of the workstation application. The subelement <delete_in_session> defines which files are deleted during check-in. For this purpose, it contains the subelement <plmfile>, which defines the additional data types to be deleted. Attributes of the sub-elements <plmfile> of sub-element <delete_in_session> of sub-element <save_direct> of <checkin_rules> extension filename_pattern "jpg", "gif", "pdf", "bat" "plm_metainf-*.*" The file extensions of the files to be deleted in the file system. "Jpg", "gif", "pdf", "bat" = file extensions of additional file types. Filters by filenames using regular expressions. "Plm_metainf - *. *" = Filter mask. The DType definitions for master documents follow. The previously defined template "ACMMM" is included here. DType definition for master documents of type "ACADM" for AutoCAD Mechanical <DType type="master" identifier="acadm" include_template="acmmm" sort_key="a01" > <description language="en" text="autocad Mechanical document, generated number"/> <document_create rename_template_filename="yes"/> <material_create material_type="fert;halb" material_template="" material_plant_assignment="0001" material_default_class=""/> </DType> Attributes of element <DType> of the DType definition for master documents of type "ACAD" for AutoCAD Mechanical type "master" Specifies the type of DType definition. "Master" = This is the definition for master documents / 106 -

75 identifier include_template sort_key "ACADM" "ACMMM" "A01" Unique ID string of this DType definition throughout the XML document. The ID must be one to five characters long. "ACADM" = ID of this master document definition. Determines which template definition is included in this definition. "ACMMM" = The DType template with ID "ACMMM" from this "dtype.xml" file is included. Defines a sorting key which is used for an alphanumeric sorting of the DType entries in the combo box for DType selection. "A01" = sorting key. The contained sub-elements <description> define description texts in different languages. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attribute of sub-element <document_create> rename_template_filename "yes" Determines whether the file name can be changed when creating a document info record. "Yes" = When creating a document info record, the file name of the CAD original can be changed. The <material_create> subelement contains settings for attaching a material to a new document. Attributes of sub-element <material_create> material_type "FERT;HALB" material_template "" material_plant_assignment "0001" material_default_class "" Type or types of material. Possible values can be found in the SAP system. "FERT; HALB" = Material types. Template material that can be specified. The material installation is then done with this template material. The basic data and the classification are copied. "" = No template material. The assigned plant. Possible values can be found in the SAP system. "0001" = Identifier of the assigned plant. The default class for the material. Possible values can be found in the SAP system. "" = Not a standard class. The DType definition for master documents of type "AMDWF" follows. Definition for master documents of type "AMDWF" for AutoCAD Mechanical <DType type="master" identifier="amdwf" include_template="amgen" > <description language="en" text="design Web Format document"/> <program_options dirty_flag="no" function_group="doc" customer_data_section=""> </program_options> <document_create document_number_assignment="internal" initial_document_number="*" document_type="dwf" initial_document_part="000" part_editable="no" initial_document_version="00" - 75 / 106 -

76 version_editable="no"> <seedfile filename="" type="select" default="yes" extension_filter="*.dwf,*.dwfx" dictionary_identifier="select" > <description language="en" text="select existing file" /> </seedfile> </document_create> <primary_application primary_workstation_application="dwf" attribute_section="default" > <checkin_rules> <save_direct> <plmfile extension="jpg" workstation_application="epj" description="ectr Preview (jpeg)"/> <plmfile extension="gif" workstation_application="epg" description="ectr Preview (gif)"/> </save_direct> <ignore> <plmfile filename_pattern="plm_metainf-*.*"/> </ignore> <delete_in_session> <plmfile filename_pattern="plm_metainf-*.*"/> </delete_in_session> </checkin_rules> </primary_application> <DType> Attributes of element <DType> of the DType definition for master documents of type "AMDWF" for AutoCAD Mechanical type identifier include_template "master" "AMDWF" "AMGEN" Specifies the type of DType definition. "master" = This is the definition for master documents. Unique ID string of this DType definition throughout the XML document. The ID must be one to five characters long. "AMDWF" = ID of this master document definition. Determines which template definition is included in this definition. "AMGEN" = The DType template with the ID "AMGEN" from this "dtype.xml" file is included. The contained sub-elements <description> define description texts in different languages. The <program_options> subtree contains various settings that control the behavior of the document in the SAP Engineering Control Center. Attributes of sub-element <program_options> dirty_flag "no" Determines if the dirty flag should be set. "No" = Do not set dirty flag / 106 -

77 function_group customer_data_section "" "DOC" Specifies the function group to which the document belongs. For documents with a common function group, e.g. custom context menus. "DOC" = This DType is assigned to the function group "DOC". Name of a section in the attribute mapping file in which customer-specific data are defined. The data is displayed in the Object Browser under the "Customer data" tab. "" = No section is defined. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of sub-element <document_create> document_number_assignment initial_document_number "*" "internal" Defines the document number assignment in SAP. "Internal" = SAP assigns the number automatically. For internal numbering, the value in this field is of no significance. For external numbering, this value is entered as a prefix in the input field of the document layout dialog. The user can delete / change the prefix at any time. "*" = No meaning, because document_number_assignment = "internal". document_type "DWF" initial_document_part "000" SAP Document type for the newly created document. "DWF" = AutoCAD document. SAP document part or as a semicolon-separated list of SAP document parts for the new document to be created. If a list of document parts has been specified, the document create dialog of one of the document parts can be selected from a selection list in the SAP Engineering Control Center. part_editable "no" "000" = Initial value for document part. Defines whether the default value or the selected SAP document part from the attribute "initial_document_part" in the input field can be changed in the SAP Engineering Control Center document create dialog. "No" = The default value in the document creation dialog can not be changed. initial_document_version "00" SAP document version or as a semicolon-separated list of document versions for the newly created document. If a list of document versions has been specified, one of the document versions can be selected from the selection list in the SAP Engineering Control Center document creation dialog. version_editable "no" "00" = Initial document version. Defines whether the default value for the document version can be changed from the "initial_document_version" attribute in the SAP Engineering Control Center document creation dialog. "No" = The default value can not be changed. Attributes of sub-element <seedfile> filename "" The filename attribute specifies the template file to be used. In the "Create Document" dialog, you can select a template file using a file selection dialog. "" = No template file / 106 -

78 type default extension_filter dictionary_identifier "select" "yes" "*.dwf,*.dwfx" "select" Determines how the original of the document is generated. The filename attribute specifies the template file to be used. A template file can be selected in the "Create Document" dialog by means of a file selection dialog. "Select" = Select a template file in the "Create Document" dialog. This can be used to determine whether this template file is preset in the "Create Document" dialog. "No" = This template file is preset. When selecting a template file with type = "select", this attribute defines the filter for the file extension. In the file selection dialog, the files matching the filter are offered for selection. "*.dwf, *. Dwfx" = Filter for file extension. If no description is provided for the template file, the plm searches for the plm.dtype.description. <Dtype_id> key and uses the description there. "Select" = Select a template file in the "Create Document" dialog. The sub-element <primary_application> determines which application is responsible for this master document (primary application) and defines the rules for checking in and checking out the originals. Attributes of sub-element <primary_application> primary_workstation_application "DWF" "DWF" = ID of the SAP workstation application. attribute_section "default" Name of a section in the attribute mapping file in which the attribute exchange between SAP and the application is defined. "Default" = Name of the section in the attribute mapping file. The <checkin_rules> subelement determines how files in the additional directory and originals on the document are handled when they are checked in. For this, it contains several subelements. The sub-element <save_direct> determines which additional files (additional formats) are stored in the additional directory when saving as originals on the document. It contains the subelement <plmfile>, which defines the individual additional file types. Attributes of sub-elements <plmfile> of sub-element <save_direct> of <checkin_rules> extension workstation_application description "jpg", "gif" "EPJ", "EPG" "ECtr Preview (jpeg)", "ECtr Preview (gif)" The respective filename extensions of the additional files in the file system. "Jpg", "gif" = The respective filename extensions. Identifiers of the workstation application for the individual additional formats. "EPJ", "EPG" = Identifiers of the workstation application. Description of the supplementary files. "ECtr Preview (jpg)", "ECtr Preview (gif)" = Description of additional files. The <ignore> subelement defines which files are ignored when saving. For this purpose, it contains the subelement <plmfile>, which defines the additional data type to be ignored. Attributes of sub-elements <plmfile> of sub-element <ignore> of sub-element <save_direct> of <checkin_rules> - 78 / 106 -

79 filename_pattern "plm_metainf-*.*" Filters by filenames using regular expressions. "Plm_metainf - *. *" = Filter mask. The subelement <delete_in_session> defines which files are deleted during check-in. For this purpose, it contains the subelement <plmfile>, which defines the additional data types to be deleted. Attributes of sub-elements <plmfile> of sub-element <delete_in_session> of sub-element <save_direct> of <checkin_rules> filename_pattern "plm_metainf-*.*" Filters by filenames using regular expressions. "Plm_metainf - *. *" = Filter mask. The DType definition for master documents of type "AMDST" follows. Definition for master documents of type "AMDST" for AutoCAD Mechanical <DType type="master" identifier="amdst" include_template="amgen" application_role="a"> <description language="en" text="autocad Sheet Set"/> <icon> <icondef icon_position="1" icon_group="default" icon_identifier="tree/amd/autocad_sheetset_16"/> </icon> <program_options dirty_flag="yes" function_group="doc_amdst" customer_data_section="" auto_adjust_application_role="no"> </program_options> <document_create document_number_assignment="internal" initial_document_number="*" document_type="dst" initial_document_part="000" part_editable="no" initial_document_version="00" version_editable="no"> <seedfile filename="empty.dst" type="template" default="yes" dictionary_identifier="empty" > <description language="en" text="empty Sheet Set" /> </seedfile> <seedfile filename="" type="select" default="no" extension_filter="*.dst" dictionary_identifier="select" > <description language="en" text="select existing file" /> </seedfile> </document_create> <primary_application primary_workstation_application="dst" attribute_section="dst" > <checkin_rules from_application_only="yes"> <save_direct> - 79 / 106 -

80 <plmfile extension="jpg" workstation_application="epj" description="ectr Preview (jpeg)"/> <plmfile extension="gif" workstation_application="epg" description="ectr Preview (gif)"/> <plmfile extension="pdf" workstation_application="pdf" description="$(filename)" /> <plmfile extension="dwf" workstation_application="dwf" description="$(filename)" /> <plmfile extension="dwfx" workstation_application="dwf" description="$(filename)" /> </save_direct> <ignore> <plmfile filename_pattern="plm_metainf-*.*"/> <plmfile extension="dbl"/> <plmfile extension="ds$"/> </ignore> <delete_in_sap> <plmfile workstation_application="epj"/> <plmfile workstation_application="epg"/> <plmfile workstation_application="pdf"/> <plmfile workstation_application="dwf"/> </delete_in_sap> <delete_in_session> <plmfile filename_pattern="plm_metainf-*.*"/> <plmfile extension="jpg" /> <plmfile extension="gif" /> <plmfile extension="pdf" /> <plmfile extension="dwf" /> <plmfile extension="dwfx" /> </delete_in_session> </checkin_rules> </primary_application> <DType> Attributes of the element <DType> of the DType definition for master documents of type "AMDST" for AutoCAD Mechanical type identifier include_template application_role "master" "AMDST" "AMGEN" "A" Defines the type of DType definition. "master" = This is the definition for master documents. Unique ID string of this DType definition in the entire XML document. The ID must be one to five characters long. "AMDST" = ID of this master document definition. Determines which template definition is included in this definition. "AMGEN" = The DType template with the ID "AMGEN" from this "dtype.xml" file is included. Setting of object type in the RES4 field of SAP table DRAW. "A" = Assembly. The contained subelements <description> define description texts in different languages. The subelement <icon> defines with the subelement <icondef> the symbol used and its position for this DType. Attributes of subelement <icondef> of subelement <icon> - 80 / 106 -

81 Attribut Wert Beschreibung icon_position "1" icon_group "default" icon_identifier "tree/acd/autocad_sheetset_16" Determines the position of the symbol in the document entry in the tree. "1" = Position 1. ID of the icon group. "default" = Standard icon. Path and name of the icon file. "tree/acd/autocad_sheetset_16" = Path and name of the icon file. The <program_options> subelement contains various settings that control the behavior of the document in SAP Engineering Control Center. Attributes of the subelement <program_options> dirty_flag "yes" function_group "DOC_AMDST" customer_data_section "" auto_adjust_application_role "no" Determines whether the dirty flag should be set. "yes" = Set the dirty flag. Determines the function group to which the document belongs. For documents with a shared function group, for example, you can define your own context menus. "DOC_AMDST" = This DType is assigned to the function group "DOC_AMDST". Name of a section in the attribute mapping file in which customer-specific data is defined. The data is displayed in the Object Browser in the "Customer Data" tab. "no" = No section is defined. Switches the automatic adaptation of the application role in RES4 on or off. "no" = No automatic adjustment. The <document_create> subelement determines how settings are made for how the document is created in SAP. Attributes of the subelement <document_create> document_number_assignment initial_document_number "*" "internal" Defines the document number assignment in SAP. "internal" = SAP assigns the number automatically. For internal number assignment, the value in this field has no meaning. For external number assignment, this value is entered as a prefix in the input field of the document creation dialog. The user can delete / change the prefix at any time. "*" = No meaning, because document_number_assignment = "internal". document_type "DST" initial_document_part "000" SAP document type for the newly created document. "DST" = AutoCAD Sheet Set document. SAP part document or as a semicolon-separated list of SAP part documents for the document to be created. If a list of part documents has been specified, one of the part documents can be selected from a selection list in the SAP Engineering Control Center "Create document" dialog. part_editable "no" "000" = Initial value for part document. Defines whether the default value or the selected SAP part document from the Attribute "initial_document_part" can be changed in the input field in the SAP Engineering Control Center "Create document" dialog. "no" = The default value in the document creation dialog cannot be changed / 106 -

82 initial_document_version "00" SAP document version or as a semicolon-separated list of document versions for the newly created document. If a list of document versions has been specified, one of the document versions can be selected from the selection list in the SAP Engineering Control Center "Create document" dialog. version_editable "no" "00" = Initial document version. Determines whether the default value for the document version from the attribute "initial_document_version" can be changed in the SAP Engineering Control Center "Create document" dialog. "no" = The default value cannot be changed. The <seedfile> subelement contains settings for the template file. Several template files can be assigned, i.e. <seedfile> can occur more than once. This contains the <description> subelement, which defines description texts in different languages. Attribute of the 1. subelement <seedfile> filename type default extension_filter dictionary_identifier "empty.dst" "select" "yes" "*.dst" "empty" The filename attribute specifies the template file to be used. In the "Create document" dialog, you can select a template file using a file selection dialog. "empty.dst" = Name of the template file. Determines how the original of the document is created. The filename attribute specifies the template file to be used. A template file can be selected in the "Create document" dialog using a file selection dialog. "select" = Selection of a template file possible in the "Create document" dialog. This allows you to determine whether this template file is preset in the"create document" dialog. "yes" = This template file is preset. When selecting a template file with type="select", this attribute defines the filter for the file extension. The files matching the filter are offered for selection in the file selection dialog. "*.dst" = Filter for the file extension. If no description is stored for the template file, it will be searched in the dictionary for the key plm.dtype.description.<dtype_id> and uses the description there. "empty" = No selection of a template file possible. Attributes of the 2. subelement <seedfile> filename "" type "select" default "no" extension_filter "*.dst" The filename attribute specifies the template file to be used. In the "Create document" dialog, you can select a template file using a file selection dialog. "" = No template file. Determines how the original of the document is created. The filename attribute specifies the template file to be used. A template file can be selected in the "Create Document" dialog using a file selection dialog. "select" = Selection of a template file possible in the "Create document" dialog. This allows the user to determine whether this template file is preset in the "Create document" dialog. "no" = This template file is not preset. When selecting a template file with type="select", this attribute defines the filter for the file extension. The files matching the filter are offered for selection in the file selection dialog. "*.dst" = Filter for the file extension / 106 -

83 dictionary_identifier "select" WIf no description is stored for the template file, it will be searched in the dictionary for the key plm.dtype.description.<dtype_id> and uses the description there. "select" = A selection of a template file is possible in the "Create document" dialog. The <primary_application> subelement specifies which application is responsible for this master document (primary application) and defines the rules for checking originals in and out. Attributes of the subelement <primary_application> primary_workstation_application "DST" "DST" = ID of the SAP workstation application. attribute_section "DST" Name of a section in the attribute mapping file in which the attribute exchange between SAP and the application is defined. "DST" = Name of the section in the attribute mapping file. The <checkin_rules> subelement specifies how files in the Additional directory and originals on the document are handled during checkin. To do this, it contains several subelements. The <save_direct> subelement determines which additional files (additional formats) are stored in the Additional directory when the document is saved as originals. It contains the <plmfile> subelement that specifies the individual additional file types. Attributes of the subelements <plmfile> of subelement <save_direct> of <checkin_rules> extension workstation_application description "jpg", "gif" "EPJ", "EPG" "ECtr Preview (jpeg)", "ECtr Preview (gif)" The respective file name extensions of the additional files in the file system. "jpg", "gif" = The respective file name extensions. IDs of the workstation application for the individual additional formats. "EPJ", "EPG" = IDs of the workstation application. Description of the respective additional files. "ECtr Preview (jpeg)", "ECtr Preview (gif)" = Description of the additional files. The <ignore> subelement defines which files are ignored during save. It contains the <plmfile> subelement, which specifies the additional file type to be ignored. Attributes of the subelements <plmfile> of subelement <ignore> of subelement <save_direct> of <checkin_rules> Attribute Values Description filename_pattern extension "plm_metainf-*.*" "dbl", "ds$" Filters by file name using regular expressions. "plm_metainf-*.*" = Filter mask. Filters by file name extensions in the file system. "dbl", "ds$" = File name extensions. The <delete_in_sap> subelement defines which originals in the document are deleted during checkin. This enables a targeted cleanup of the document. To do this, it contains the <plmfile> subelement, which specifies the additional file types to be deleted. Attributes of the subelements <plmfile> of subelement <delete_in_sap> of subelement <save_direct> of <checkin_rules> Attribute Values Description - 83 / 106 -

84 workstation_application "EPJ", "EPG", "PDF", "DWF" IDs of the workstation application for the individual additional formats. "EPJ", "EPG", "PDF", "DWF" = IDs of the workstation application. The <delete_in_session> subelement defines which files are deleted at checkin. To do this, it contains the <plmfile> subelement, which specifies the additional file types to be deleted. Attributes of the subelements <plmfile> of subelement <delete_in_session> of subelement <save_direct> of <checkin_rules> Attribute Values Description filename_pattern extension "plm_metainf-*.*" "jpg", "gif", "pdf", "dwf", "dwfx" Filters by file name using regular expressions. "plm_metainf-*.*" = Filter mask. Filters by file name extensions in the file system. "jpg", "gif", "pdf", "dwf", "dwfx" = file name extensions. 2.5 options.xml Any user can individually apply settings which control the behavior of the SAP Engineering Control Center. This can 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 dem SAP Engineering Control Center and den SAP Engineering Control Center Interfaces for individual CAD systems. For each installed interface a node is present in the tree on the left side: - 84 / 106 -

85 ECTR dialog "Preferences" with AutoCAD settings 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 safed under "user.txt" for every user in their specific ECTR work directory, under the sub-menue "preferences" (the exact path: "%APPDATA%\SAP\ECTR\data\<<ECTR-Version>>\<<SAP- Server_Mandant_Username>>\preferences\user.txt"). 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="..."/> - 85 / 106 -

86 </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. Attributs of elemtent <node> label="..." card="..." Name Card identifier (Optional) If attribut 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. Defines an entry in the tree diagram, which contains changeable parameters (preferences), and which will appear on the right when clicked. The adjustable parameter 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 for the 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 the respective file "dictionary.txt". Example: <node label="autocad"> <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="..."> With the element <card> you define the options that can be reached under the respective card note. The assignment is done via name of card. Attribut of element <card> name="..." Name Name of Card, like in the element <node> The sub-element <option> defines always 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 empty editing field will appear or a list of values will apply. Attributs of sub-element <option> label="..." Name or description of the option Description of the option as appears on the card under "Description" - 86 / 106 -

87 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, when mouse cursor is positioned on the option maxchars="..." Number (Optional) Maximum possible number of signes or characters within an editing field If you want to present a list of possible values, you have to enter the sub-element <entry> which might occur repeatedly. Attributs of sub-element <entry> name="..." Name Name of value in the list value="..." Value accordung 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 the attribute "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 the interface, so that an update of the value is not guaranteed during operation! However, all settings in the standard delivery of the file "options. xml" can be changed during operation. 2.6 plm_setenv.bat The file "plm_setenv.bat" serves to set environment variables. These can then be evaluated from the SAP Engineering Control Center and SAP Engineering Control Center Interface to AutoCAD as well as SAP Engineering Control Center Interface to AutoCAD Mechanical 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 existing environment variables, with the notation "%<<Variable name>>%". Note: As the SAP Engineering Control Center Interface to AutoCAD and SAP Engineering Control Center Interface to AutoCAD Mechanical do not require any special environment variables but the SAP Engineering Control Center does expect a CAD-specific file "plm_setenv.bat", and this file does not contain any definitions of environment variables after installation, and is therefore empty! 2.7 rfc-tunnel-whitelist.txt The configuration file "rfc-tunnel-whitelist.txt" contains a list of all RFC function modules that can be called by the SAP Engineering Control Center Interface to AutoCAD via the ECTR. Calling RFC function modules that are not contained in this list is rejected with an error. With this white list, the SAP Engineering Control Center Interface to AutoCAD follows the security concept of the ECTR and enables you to ensure that only permitted RFC function modules can be executed. The standard configuration includes the following RFC functions that are allowed to be executed: CDESK_SRV_MODIFY_INST_DATA - 87 / 106 -

88 The wildcard character '*' is allowed when specifying the RFC function. This makes it possible to specify entire groups of RFC functions that have the same prefix in their names, for example. 2.8 Version information To gain an overview of the imported changes of the relevant releases of the SAP Engineering Control Center Interface to AutoCAD (Mechanical), the changes are listed here in the configuration files "default.txt" and "dtype.xml" for AutoCAD and AutoCAD Mechanical. The following table contains changes in parameters in the configuration file "default.txt". The status shows whether the relevant parameter in this version was added ( ), changed ( ) or deleted ( ). When changing a parameter, merely a new parameter name is given. Version Status Parameter Changes in configuration file "default.txt" plm.options.importondemand.deleteoriginals.acx plm.options.importondemand.checkinaftercreate.acx plm.convert.additional.acx plm.options.updatetitleblockdataoninsert.acx plm.control.partnamerules.applextension.acx plm.bom.item.property.acx.dmucad.quantity.name plm.bom.item.property.acx.dmud.material.name plm.bom.item.property.acx.internal.display.name plm.bom.item.property.acx.comp_material.name plm.bom.item.property.acx.comp_posnr.name plm.options.bom.insertvirtuelbomheader.acx plm.options.checkin.updateattributesfromsap.acx plm.options.bomtable.addnonexistingcolumns.acm plm.options.saveasnewdocument.replace.acx plm.control.partnamerules.resolveinsap.acx - 88 / 106 -

89 plm.options.overwritedtypeupdateattributesettings.acx plm.control.partnamerules.applextension.acx plm.control.extension.wsappl.dst plm.document.create.extensionprimaryapplication.dst plm.options.enablesheetset.acx plm.structure.application.displayexternalreferences.acx plm.options.overwritedtypeupdateattributesettings.acx plm.execute.additional.acx plm.options.missingreferencereloadoption.acx plm.options.ballooning.ballooncontent.acm plm.options.thumbnail.size.acx plm.options.bomtable.column.acm.sapmatnr plm.options.bomtable.column.acm.material plm.options.bomtable.column.acm.postext1 plm.options.bomtable.column.acm.postext2 plm.options.bomtable.column.acm.othercolumn plm.options.sapsaveasnewdocumentforcadsaveas.acx plm.options.references.attachmultiplecomponents.acx plm.appl.location.acx plm.appl.profile.acx plm.appl.product.acx plm.appl.language.acx plm.adv.clone.renamerprogram.acx plm.options.saveasnewdocument.replace.acx plm.options.ballooning.ballooncontent.acm plm.document.createmulti.cad.dtype.searchalso.acx plm.document.addcomponent.allowed.dtypelist.acx - 89 / 106 -

90 plm.convert.additional.acx plm.document.createmulti.cad.dtype.searchalso.acx plm.document.addcomponent.allowed.dtypelist.acx plm.document.saveasnewdocument.checkouttop.acx plm.options.new.saveactivedocument.acx plm.options.structureanalyze.showdialogformissingreferences.acx plm.options.open.usemultisearchforsapopen.acx plm.options.importondemand.updateattributes.acx plm.options.new.saveactivedocument.acx plm.options.sapopenforcadplacedocument.acx plm.structure.application.init.strategy.levels.acx plm.options.thumbnail.usescreenshot.acx plm.structure.application.displaypositem.acx plm.options.deliveronlyrequestedattributestosap.acx plm.document.dtype.default.dwg.acx plm.options.createdirfornewdocument.acx plm.options.sapopenforcadopendocument.acx structure.view.acx.generic.object.type structure.view.acx.generic.object.acx_material_new.name structure.view.acx.generic.object.acx_material.name structure.view.acx.generic.object.acx_virtual_new.name structure.view.acx.generic.object.acx_virtual.name plm.structure.node.cuapob_acx_material.icon.1 plm.structure.node.cuapob_acx_material.icon.2 plm.structure.node.cuapob_acx_material_new.icon.1 plm.structure.node.cuapob_acx_material_new.icon.2 plm.structure.node.cuapob_acx_virtual.icon.1 plm.structure.node.cuapob_acx_virtual.icon.2 plm.structure.node.cuapob_acx_virtual_new.icon.1 plm.structure.node.cuapob_acx_virtual_new.icon.2-90 / 106 -

91 plm.structure.application.collectentries.acx plm.structure.application.collectentries.acx plm.options.createdirfornewdocument.acx plm.options.updateattributes.useinteropprefix.acx The following table contains changes in the configuration file "dtype.xml" for AutoCAD and AutoCAD Mechanical: Changes in configuration file "dtype.xml" Version Description The generic DType definitions for AutoCAD documents "ACGEN" and for AutoCAD Mechanical documents "AMGEN" have the attribute rename_master_original="no" added in their definitions new_version. The template definitions for master documents for AutoCAD "ACMM" as well as for AutoCAD Mechanical "ACMMM" have got the attribute from_application_only="yes" in their checkin_rules. The template definitions for "SLWMDL" and "SLWDRW" have got the attribute from_application_only="yes" in their checkin_rules ATTENTION: The attribute "from_application_only" can only be processed from ECTR version onwards, an older ECTR version terminates with an error message! If you are working with an older ECTR, you should use the file "dtype xml" instead of the current "dtype. xml", which is located in the directory "template_customize" The DType "ACDWF" (AutoCAD) and "AMDWF" (AutoCAD Mechanical) has been added It is recommended to maintain only the language english directly in the file "dtype.xml"! All other languages will be offered via the particular "dictionary.txt" file. This affects the definitions of DTypes and Seedfiles. All elements <description language="xy"> are omitted except english which are used as fallback. - The seed file "acad.dwg" now is marked as default (default="yes"). - The file name of the Select seed file has been removed because a file name makes no sense there. The following table contains changes in the configuration file "menu.guidef" for AutoCAD and AutoCAD Mechanical: Changes in configuration file "menu.guidef" Version Status Parameter om.popup.menu.clonepos.doc_acx - 91 / 106 -

92 3 Configuration examples In the following chapter, based on process-related examples, various possibilities for configuration in the ECTR environment, related to the SAP Engineering Control Center Interface to AutoCAD (Mechanical) will be presented. The purpose is to demonstate how the various requirements can be implemented. This chapter is to serve as support because the values to be configured are described with placeholders and when in use, are to be replaced in accordance with the customer. 3.1 Inserting external references The following sections explain how the configuration in the files "dtype.xml" and "default.txt" as well as on the SAP side has to be done by the transactions "DC10" and "DC30" in order to insert various file formats as external references into a drawing. External references When allocating DWG files with the command AutoCAD "_ATTACH", the referenced files are automatically treated as subcomponents by the ECTR Integration and are entered accordingly into the document structure without the need for additional configuration work. However, the command "_ATTACH" also supports numerous non-dwg formats, such as pictures or point clouds. These files are converted to external references by the interface because they are non-native file formats. External references are marked as follows in the ECTR: - 92 / 106 -

93 External references in structure view of the ECTR If a drawing with external references is imported into SAP, a DIR is created for each reference, similar to that for ordinary components. In order for the ECTR to find a suitable DType for all non-native file formats and to create a document in SAP for this purpose, some settings have to be made beforehand, which are explained in more detail below. Example Dtype: ACPIC This is done using the example of a format for image formats, which contains both settings from the ECTR standard delivery as well as your own configurations: "ACPIC" (AutoCAD Raster Picture). Our example Dtype should support all image formats that can be inserted in AutoCAD. Since the ECTR standard delivery already covers the formats JPG, GIF, PNG and TIF, these are the extensions BMP, CAL, PCX and TGA. Definition of Workstation Applikation and document type A DIR must always be assigned a valid Workstation Application (WSA) and a document type. These settings are made on the SAP side via transactions "DC10" (document type) and "DC30" (WSA). The ECTR standard already provides the WSA and document type PIC for images. The document type should be adopted in our example. In addition, we define the WSA "ACI" (AutoCAD RasterImage) for the other file extensions. Definition of WSA "ACI" in SAP Definition of the Dtype "ACPIC" A separate Dtype must be defined so that attached image files can be stored correctly as such in SAP. This Dtype uses the previously created WSA ACI and the document type provided by ECTR for images: PIC / 106 -

94 The following shows the configuration as it must be inserted into the file "dtype.xml": Definition of DType "ACPIC" Important is the link to the respective WSA (ACI) and document type (PIC) as well as the specification of a seed file with the permitted file extensions. All other settings can be taken from various standard configurations. Enabling Dtype for import Since the Dtype "ACPIC" belongs to the application PIC as defined, it is normally not visible to the processes within the application ACD or ACM and is not found during the import of such a file. This results in an error message and the termination of the import process / 106 -

95 The "plm.document.createmulti.cad.dtype.searchalso.acx" setting in the configuration file "default.txt" is used as a remedy. It defines a list of Dtype IDs, which are to be used in the creation of a document in addition to those from their own application: plm.document.createmulti.cad.dtype.searchalso.acx = ACPIC;PICP;PICG;PICT;PICJ Note: This list does not accept template DTypes. The PICx IDs comes from the application PIC delivered in the ECTR standard and stand for PNG, GIF, TIF and JPG. If a Dtype could be successfully assigned to each referenced file, all new components of the document are listed in the import dialog. ECTR dialog "Import On Demand" Enable Dtype for "Add Component" The ability to insert a desired component from the SAP into the drawing must also be configured accordingly. The setting plm.document.addcomponent.allowed.dtypelist.acx determines which DTypes may be inserted into the current document during Add Component. Here you also have to enter the DTypes of your own application as well as all the additional formats to be supported during this process. plm.document.addcomponent.allowed.dtypelist.acx = ACAD;ACDNR;ACADM;TPIC; ACPIC;ACPC;PDF;IPTML Note: This setting also accepts template DTypes. Instead of listing each PICx IDs, for example, the ID TPIC from the ECTR standard installation is sufficient to include all derived Dtypes. 3.2 Mapping of properties The mapping of attributes can, on the one hand, take place automatically as part of particular actions (e.g. check-out) or on the other hand, manually by means of the SAP PLM function "Refresh Attributes" in the "Refresh" menu. In the process, selected metadata of the document information record are transferred from SAP to the CAD-original. In the AutoCAD environment, that means that these values will be attached to the drawing properties of the DWG. All drawing properties can be in the AutoCAD (English) with the command "DWGPROPS" ("DWEIGEN" German). Most of the properties added via the integration can be found in the "Custom" tab / 106 -

96 Drawing properties of a DWG In order that values from SAP will be written to the drawing, a corresponding mapping must be prescribed in the configuration file "attributes-from-sap.xml" from the application folder. The file can be found in the standard under: % PLM_INSTDIR%\applications\acd\customize\config\attributes-from-sap.xml (AutoCAD Vanilla) % PLM_INSTDIR%\applications\acm\customize\config\attributes-from-sap.xml (AutoCAD Mechanical) Where applicable, additional adjustments to the configuration are necessary. This will be explained in greater detail in the following examples. In addition, particular attributes from the CAD-original can also be written to the DIS in SAP. This can, for example, be useful in completing mandatory fields or properties of a classification during document creation. For this purpose, there is analogously a configuration file "attributes-to-sap.xml", that includes this mapping. Methods of mapping In the AutoCAD environment, there are two different ways to define its title block attributes and to update them via the ECTR interface. For both approaches, different action steps must be observed; these will be explained below Title block attributes as drawing properties This approach assigns every attribute in the title block a drawing property ("Field") with the same name. This assignment must take place from the user during the creation of his template so that by using this template later, the smooth updating of all attributes can be guaranteed. Since the ECTR for the creation of a document uses a so-called "Seed File" as its basis, the specification of the fields applicable to the title block in this file should be undertaken. All documents based on this Seed File will then assume all properties of the drawing and the title block automatically. For the definition of the block for the title block, the corresponding drawing properties will now be linked during administration of the attributes. This takes place during the value assignment via the context menu entry "Insert Field": - 96 / 106 -

97 Attribute definition in title block Insert field in title block After successful assignment, the attribute field will now appear in gray. This background color will not be displayed when plotting or printing. Filled title block After manually updating the attributes via "Refresh Attributes" the drawing must still be secured locally under this approach so that all the fields in the title block are also updated / 106 -

98 Illustrative approach An example for purposes of illustration follows. It uses the title block that is also delivered with the standard installation of the SAP Engineering Control Center Interface to AutoCAD. Additionally necessary configuration steps will likewise be explained Creation of the drawing template When creating the drawing template, the required properties should already be defined when defining the block of characters. For this purpose, a temporary drawing property should be created for each attribute in the file that contains the block definition. Drawing properties When the block attributes are created, these properties are then linked via Insert Field. This link will not be lost if the block is channeled as usual and inserted into other drawings / 106 -

99 Assigning a drawing property The selection dialog is reached via the context menu The required drawing properties can also be deleted after the block definition. When the attribute mapping is carried out by the ECTR interface, they are automatically added to the respective drawing. If you are using AutoCAD Mechanical, the title block can also be defined with a self-selected drawing frame as a standard for the "AMTITLE" command / 106 -

100 Define standard title block Reference in the configuration file "dtype.xml" The drawing template that has been created will now be processed into a Seed File. To do this, a drawing will be created in the DWG format from the DWT file. In addition, the title block and drawing framework will be inserted in the selected format. Finally, it will be filed in the template directory of the ECTR installation. This can be found as usual under: %PLM_INSTDIR%\applications\acd\templates (AutoCAD Vanilla) %PLM_INSTDIR%\applications\acm\templates (AutoCAD Mechanical) In the configuration file "dtype.xml", this seed file will now be referenced in the corresponding Dtype. This file can be found as usual under: %PLM_INSTDIR%\applications\acd\customize\config\dtype.xml (AutoCAD Vanilla) %PLM_INSTDIR%\applications\acm\customize\config\dtype.xml (AutoCAD Mechanical) The path name comes about in relative or absolute terms, depending on the storage location. A relative path can be chosen if the Seed File is located right in the template directory. However, if it is located in a sub-directory or in another location altogether, then an absolute path has to be specified: / 106 -

101 Seed File definitions with relative and absolute paths In the file "dtype.xml", any number of Seed Files can be specified Mapping rules in the configuration file "attributes-from-sap.xml" In accordance with the conventions in the ECTR environment, now for every attribute in the title block that is to receive data from SAP, a mapping in the configuration file "attributes-from-sap.xml" file will be applied. If the use of the global attribute section is activated, properties can also be referenced out of it: / 106 -

102 Mapping with global attribute section activated If the global attribute section is activated, attributes defined there can also be used Publication of the block in the configuration file "default.txt" In order that the SAP Engineering Control Center Interface to AutoCAD (Mechanical) knows during updating of the attributes which blocks in the drawing represent title blocks that are to be overwritten, the respective block names must be set in the configuration file "default.txt". This file is to be found as usual under: % PLM_INSTDIR%\applications\acd\customize\config\default.txt (AutoCAD Vanilla) % PLM_INSTDIR%\applications\acm\customize\config\default.txt (AutoCAD Mechanical) In the AutoCAD environment, the name of a block can be seen in the property window. In addition, the respective block must be selected / 106 -

103 Name of the block The file "default.txt" contains, under the "plm.attributes.acd.tbknames" setting, a list of all potential title blocks. The list entries are separated by a semicolon. Setting plm.attributes.acd.tbknames If several title blocks are to be found in a drawing, especially in different areas (model and paper space/layout), so should the setting "plm.attributes.acd.tbkupdateinalllayouts" also be set. That is how the update of the attribute in all areas of the drawing can be assured. Setting of plm.attributes.acd.tbkupdateinalllayouts Title block attributes as separate TBK attributes To use title block attributes as separate TBK attributes the title block attributes do not have to be explicitly associated with drawing properties in the template. During mapping, the corresponding field is searched and filled in its title block by its identifier ("TAG"). In addition, a drawing property is created whose name is composed of the identifier and the prefix "TBK-". This combined name must also be used in the configuration file. When defining attributes, however, it should not appear in the tag / 106 -

104 Mapping of an TBK attribute After manually updating the attributes via "Refresh attributes" the title block will automatically be updated, as long as the block in use with the attributes is not nested in the drawing. A block is considered nested if its attributes cannot be displayed in the first level in the Properties window. This is the case, for example, if drawing frames and title blocks are combined to form a common block reference. The drawing must then be saved locally in order for the title block to be updated Illustrative approach Creation of the drawing template During the creation of the drawing template, there are no special restrictions for this approach. The title block can be created and provided with attributes as desired. In order to reuse the block with the title block, this can be diverted beforehand. Reference in the configuration file "dtype.xml" The drawing template that has been created will now be described, as previously in section Reference in the configuration file "dtype.xml" and prepared for its use as ECTR Seed File. In addition, a DWG drawing will be created, title block as well as drawing framework inserted and filed in the ECTR template directory. Mapping rules in the configuration file "attributes-from-sap.xml" Now for every desired attribute, a corresponding mapping will be set up. In so doing, the following rules must be respected: Every title block attribute must be referenced with the "TBK-" prefix and its identifier ("Tag"), that was established during the definition of the block. Normal drawing properties will be mapped without the prefix / 106 -

105 Mixed mapping of title block and drawing attributes Title block attributes, but not drawing attributes must be identified with "TBK-". Publication of the block in the configuration file "default.txt" The same references and settings apply here as in the section Publication of the block in the configuration file "default.txt" / 106 -

SAP Engineering Control Center Interface to SOLIDWORKS - Configuration Manual

SAP Engineering Control Center Interface to SOLIDWORKS - Configuration Manual Configuration manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to SOLIDWORKS SAP Engineering Control Center Interface to SOLIDWORKS manages the design data in

More information

SAP Engineering Control Center Interface to EPLAN - Configuration Manual

SAP Engineering Control Center Interface to EPLAN - Configuration Manual Configuration Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to EPLAN SAP Engineering Control Center Interface to EPLAN manages design data in SAP. Given by

More information

SAP Engineering Control Center Interface to Inventor - User Manual

SAP Engineering Control Center Interface to Inventor - User Manual User Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to Inventor SAP Engineering Control Center Interface to Inventor manages design data in SAP. Given by the

More information

SAP Engineering Control Center Interface to Solid Edge - User Manual

SAP Engineering Control Center Interface to Solid Edge - User Manual User Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to Solid Edge SAP Engineering Control Center Interface to Solid Edge manages design data in SAP. Given by

More information

SAP Engineering Control Center Interface to EPLAN - User Manual

SAP Engineering Control Center Interface to EPLAN - User Manual User Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to EPLAN SAP Engineering Control Center Interface to EPLAN manages design data in SAP. Given by the SAP

More information

SAP Engineering Control Center Interface to AutoCAD - User Manual

SAP Engineering Control Center Interface to AutoCAD - User Manual User Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to AutoCAD SAP Engineering Control Center Interface to AutoCAD manages design data in SAP. Given by the

More information

SAP Engineering Control Center Interface to SOLIDWORKS - User Manual

SAP Engineering Control Center Interface to SOLIDWORKS - User Manual User Manual Management of CAD data and documents in SAP SAP Engineering Control Center Interface to SOLIDWORKS SAP Engineering Control Center Interface to SOLIDWORKS manages design data in SAP. Given by

More information

SAP Engineering Control Center 5.1

SAP Engineering Control Center 5.1 Installation Guide CUSTOMER Document Version: 11.0 2017-09-29 Typographical Conventions Format Example Description Words or characters that are quote from the screen display. These include field names,

More information

SAP Engineering Control Center 5.1

SAP Engineering Control Center 5.1 Configuration Guide Document Version: 20.0 2018-06-22 CUSTOMER Typographical Conventions Format Example Description Words or characters that are quoted from the screen display. These include field names,

More information

SAP Engineering Control

SAP Engineering Control SAP Engineering Control Center Interface to CATIA V5 User Documentation 01.02.2016 CENIT AG Software Product / Components: Product Version: 1.1.4 Creation Date: 28.08.2015 16:27 Document Version: 5 Last

More information

SAP Engineering Control

SAP Engineering Control SAP Engineering Control Center Interface to CATIA V5 User Documentation 01.02.2016 CENIT AG Software Product / Components: Product Version: 1.1.5 Creation Date: 28.08.2015 16:27 Document Version: 8 Last

More information

12d Synergy V4 Release Notes. 12d Synergy V4 Release Notes. Prerequisites. Upgrade Path. Check Outs. Scripts. Workspaces

12d Synergy V4 Release Notes. 12d Synergy V4 Release Notes. Prerequisites. Upgrade Path. Check Outs. Scripts. Workspaces 12d Synergy V4 Release Notes V4 contains a large number of features. Many of these features are listed in this document, but this list may not be exhaustive. This document also contains pre-requisites

More information

SAP Engineering Control Center 5.1

SAP Engineering Control Center 5.1 Application Help Document Version: 20.0 2018-06-22 CUSTOMER Typographical Conventions Format Example Description Words or characters that are quoted from the screen display. These include field names,

More information

EDAConnect-Dashboard User s Guide Version 3.4.0

EDAConnect-Dashboard User s Guide Version 3.4.0 EDAConnect-Dashboard User s Guide Version 3.4.0 Oracle Part Number: E61758-02 Perception Software Company Confidential Copyright 2015 Perception Software All Rights Reserved This document contains information

More information

COMOS Material Management. Operation COMOS. Process COMOS Material Management Operation. Trademarks 1. Introduction. Definitions 3

COMOS Material Management. Operation COMOS. Process COMOS Material Management Operation. Trademarks 1. Introduction. Definitions 3 COMOS Material Management Operation COMOS Process COMOS Material Management Operation Operating Manual Trademarks 1 Introduction 2 Definitions 3 Creating material in COMOS 4 Importing material from external

More information

GV 2 Devicemanagement 2

GV 2 Devicemanagement 2 GV 2 Devicemanagement 2 getting started & usage 1/13 Index 1 General Remarks...3 2 Software...3 2.1 System Requirements...3 2.2 Installation...4 2.3 Un-Installation...5 3 User Interface...5 3.1 Menu Bar...6

More information

Drawing Manager 2.5.1

Drawing Manager 2.5.1 www.mclarensoftware.com Drawing Manager 2.5.1 Installation Guide May 2004 Drawing Manager Installation Guide Product Version: 2.5.1 Guide Version: 1.0 McLaren Software 2004. All rights reserved. Information

More information

Siemens Controls. SAP interface COMOS. Platform SAP interface. Trademarks 1. Introduction. Technical prerequisites 3

Siemens Controls. SAP interface COMOS. Platform SAP interface. Trademarks 1. Introduction. Technical prerequisites 3 Trademarks 1 Introduction 2 COMOS Platform Operating Manual Technical prerequisites 3 Basic concepts of the COMOS SAP Interface 4 General settings 5 XML scheme for the data exchange 6 SAP Maintenance module

More information

Introduction to Autodesk VaultChapter1:

Introduction to Autodesk VaultChapter1: Introduction to Autodesk VaultChapter1: Chapter 1 This chapter provides an overview of Autodesk Vault features and functionality. You learn how to use Autodesk Vault to manage engineering design data in

More information

USE OF BASELINES. Definition, reasons and examples. RD.11/######.#

USE OF BASELINES. Definition, reasons and examples.  RD.11/######.# USE OF BASELINES Definition, reasons and examples www.ricardo.com 2 Agenda Introduction Principles and reasons for use Examples Advanced features Using Baselines Baseline Views 3 BASELINES Introduction

More information

COMOS Material Management. Operation COMOS. Process COMOS Material Management Operation. Trademarks. Introduction. Definitions

COMOS Material Management. Operation COMOS. Process COMOS Material Management Operation. Trademarks. Introduction. Definitions COMOS Material Management Operation COMOS Process COMOS Material Management Operation Operating Manual Trademarks 1 Introduction 2 Definitions 3 Creating material in COMOS 4 Importing material from external

More information

FOCUS ON REAL DESIGN AUTOMATE THE REST CUSTOMTOOLS GETTING STARTED GUIDE

FOCUS ON REAL DESIGN AUTOMATE THE REST CUSTOMTOOLS GETTING STARTED GUIDE FOCUS ON REAL DESIGN AUTOMATE THE REST CUSTOMTOOLS GETTING STARTED GUIDE Table of Contents CHAPTER 1: INTRODUCTION... 11 Read this first... 11 About this manual... 11 Intended Audience... 12 Late Changes...

More information

Introduction to Autodesk ProductstreamChapter1:

Introduction to Autodesk ProductstreamChapter1: Chapter 1 Introduction to Autodesk ProductstreamChapter1: This chapter gives an overview of Autodesk Productstream, its features, functions, and benefits, and the Autodesk Productstream user interface.

More information

Multi-Sponsor Environment. SAS Clinical Trial Data Transparency User Guide

Multi-Sponsor Environment. SAS Clinical Trial Data Transparency User Guide Multi-Sponsor Environment SAS Clinical Trial Data Transparency User Guide Version 6.0 01 December 2017 Contents Contents 1 Overview...1 2 Setting up Your Account...3 2.1 Completing the Initial Email and

More information

Functions of Mold EX-Press for Press Die

Functions of Mold EX-Press for Press Die 11 B. Basic Operations B1-1. Functions in Home, the 1st page Functions of Mold EX-Press for Press Die Search box Home BOM list Help Select parts by image Select parts by diagram Shortcut to My Library

More information

Installing and Updating SAP HANA Products and Software Components

Installing and Updating SAP HANA Products and Software Components Product Documentation Document Version: 1.0 2015-10-09 Installing and Updating SAP HANA Products and Software Components SAP HANA SPS 10, as of Database Maintenance Revision 102.1 Typographic Conventions

More information

Introduction to Autodesk VaultChapter1:

Introduction to Autodesk VaultChapter1: Introduction to Autodesk VaultChapter1: Chapter 1 This chapter provides an overview of Autodesk Vault features and functionality. You learn how to use Autodesk Vault to manage engineering design data in

More information

Introduction to Autodesk Vault

Introduction to Autodesk Vault Chapter Introduction to Autodesk Vault 1 This chapter provides an overview of Autodesk Vault features and functionality. You learn how to use Autodesk Vault to manage engineering design data in a secure,

More information

Teamcenter NX Remote Manager Guide. Publication Number PLM00123 G

Teamcenter NX Remote Manager Guide. Publication Number PLM00123 G Teamcenter 10.1 NX Remote Manager Guide Publication Number PLM00123 G Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management

More information

Getting_started_EN (Ind : 3) 06/01/2014. elecworks. Getting Started

Getting_started_EN (Ind : 3) 06/01/2014. elecworks. Getting Started Getting_started_EN (Ind : 3) 06/01/2014 elecworks Getting Started 1 Start with elecworks This document has been made to help you in starting elecworks. It summarizes the features available. If you would

More information

PUBLIC. How to Manage Batch Numbers. All Countries. Solutions from SAP. SAP Business One 2007 A and 2007 B. August English

PUBLIC. How to Manage Batch Numbers. All Countries. Solutions from SAP. SAP Business One 2007 A and 2007 B. August English PUBLIC How to Manage Batch Numbers All Countries Solutions from SAP SAP Business One 2007 A and 2007 B August 2008 English Contents Purpose... 3 Defining General Settings... 4 Procedure... 4 Setting Authorizations...

More information

JMP to LSAF Add-in. User Guide v1.1

JMP to LSAF Add-in. User Guide v1.1 JMP to LSAF Add-in User Guide v1.1 Table of Contents Terms and Conditions... 3 System Requirements... 3 Installation... 3 Configuration... 4 API Setup... 4 Java Configuration... 5 Logging In... 5 Launching

More information

User Manual - Tick Tool. anage

User Manual - Tick Tool. anage User Manual - Tick Tool anage Contents Introduction... 0 Getting started... 1 Installation... 1 Activation... 1 Get started... 2 Available File types in Tick Tool Manage... 2 User Interface... 3 Overview...

More information

EMC Documentum Content Services for SAP Document Controllers

EMC Documentum Content Services for SAP Document Controllers EMC Documentum Content Services for SAP Document Controllers Version 6.5 User Guide P/N 300 006 307 Rev A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com Copyright

More information

CADMANAGERTOOLS.COM. LayoutManager 4.1. Layout Management tool for AutoCAD and Verticals

CADMANAGERTOOLS.COM. LayoutManager 4.1. Layout Management tool for AutoCAD and Verticals CADMANAGERTOOLS.COM LayoutManager 4.1 Layout Management tool for AutoCAD and Verticals Compatible with AutoCAD 2013 to 2018 LayoutManager Layout tool for AutoCAD Introduction: The LayoutManager is a powerful

More information

1. WELDMANAGEMENT PRODUCT

1. WELDMANAGEMENT PRODUCT Table of Contents WeldManagement Product.................................. 3 Workflow Overview........................................ 4 Weld Types.............................................. 5 Weld

More information

IBM Rational Rhapsody Gateway Add On. Customization Guide

IBM Rational Rhapsody Gateway Add On. Customization Guide Customization Guide Rhapsody IBM Rational Rhapsody Gateway Add On Customization Guide License Agreement No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated

More information

SIMATIC. Process Control System PCS 7 OS Process Control (V8.1) Security information 1. Preface 2. Additional documentation 3

SIMATIC. Process Control System PCS 7 OS Process Control (V8.1) Security information 1. Preface 2. Additional documentation 3 Security information 1 Preface 2 SIMATIC Process Control System PCS 7 Operating Instructions Additional documentation 3 Functions of the PCS 7 OS in process mode 4 PCS 7 OS process mode - user interface

More information

Vault 2018: What's New. J e n s M ø l l e r

Vault 2018: What's New. J e n s M ø l l e r Vault 2018: What's New J e n s M ø l l e r Enhanced Design Experience IDEAS V a u l t B r o w s e r & S e a r c h Detachable Enhanced Search Execute command on search results Search on Vaulted Properties

More information

Configuring Job Monitoring in SAP Solution Manager 7.2

Configuring Job Monitoring in SAP Solution Manager 7.2 How-To Guide SAP Solution Manager Document Version: 1.0 2017-05-31 Configuring Job Monitoring in SAP Solution Manager 7.2 Typographic Conventions Type Style Example Example EXAMPLE Example Example

More information

Student Lifecycle Management Academic Advisor User Interface Cookbook

Student Lifecycle Management Academic Advisor User Interface Cookbook Student Lifecycle Management Academic Advisor User Interface Cookbook Applies to: Student Lifecycle Management EHP 3. For more information, visit the Higher Education & Research homepage. Summary This

More information

Cryptshare for Outlook Installation Guide

Cryptshare for Outlook Installation Guide Cryptshare for Outlook Installation Guide V1.6.2 Befine Solutions AG Werthmannstr. 15 79098 Freiburg i. Br. Germany Web: https://www.cryptshare.com E-Mail: info@cryptshare.com Tel.: +49 761 389 13 0 Fax:

More information

Determination Applications Softproviding Core User Documentation

Determination Applications Softproviding Core User Documentation Great ideas are always simple Softproviding simply makes them happen. Determination Applications Softproviding Core User Documentation Version: 1.00 Date: 20. June 2018 Release: v2.60 Softproviding AG

More information

Impossible Solutions, Inc. JDF Ticket Creator & DP2 to Indigo scripts Reference Manual Rev

Impossible Solutions, Inc. JDF Ticket Creator & DP2 to Indigo scripts Reference Manual Rev Impossible Solutions, Inc. JDF Ticket Creator & DP2 to Indigo scripts Reference Manual Rev. 06.29.09 Overview: This reference manual will cover two separate applications that work together to produce a

More information

Autodesk Vault What s new in 2015

Autodesk Vault What s new in 2015 Autodesk Vault What s new in 2015 Lieven Grauls Technical Manager Manufacturing - Autodesk Digital Prototyping with Vault Autodesk Vault 2015 What s new Improved integration Updates to CAD add-ins Data

More information

1 2 3 DETERMINING THE SAP BUSINESS OBJECT AND ITS KEY FIELDS... 12

1 2 3 DETERMINING THE SAP BUSINESS OBJECT AND ITS KEY FIELDS... 12 BOR... 3 TRANSACTION MODEL FOR DEVELOPING BAPIS... 4 USING THE TRANSACTION MODEL IN RELEASE 3.1... 5 TRANSACTION MODEL FOR RELEASE 3.1... 6 USING THE TRANSACTION MODEL IN RELEASE 4.0A... 6 EXTENDED TRANSACTION

More information

COMOS. Platform COMOS Platform Interfaces. Importing and exporting data 1. XML connectors 2. Standard import "Blank XML" 3

COMOS. Platform COMOS Platform Interfaces. Importing and exporting data 1. XML connectors 2. Standard import Blank XML 3 Importing and exporting data 1 XML connectors 2 COMOS Platform Operating Manual Standard import "Blank XML" 3 Standard import "Blank table" 4 Engineering projects 5 Data exchange with NOXIE 6 COMOS document

More information

USER GUIDE MADCAP FLARE Accessibility

USER GUIDE MADCAP FLARE Accessibility USER GUIDE MADCAP FLARE 2018 Accessibility Copyright 2018 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document

More information

Ocean Wizards and Developers Tools in Visual Studio

Ocean Wizards and Developers Tools in Visual Studio Ocean Wizards and Developers Tools in Visual Studio For Geoscientists and Software Developers Published by Schlumberger Information Solutions, 5599 San Felipe, Houston Texas 77056 Copyright Notice Copyright

More information

imos Drawing Output The following document includes the topics borders and viewsets.

imos Drawing Output The following document includes the topics borders and viewsets. imos Drawing Output The following document includes the topics borders and viewsets. We have attempted to keep the content of the document complete, accurate and under permanent review. However, due to

More information

Coveo Platform 6.5. Microsoft SharePoint Connector Guide

Coveo Platform 6.5. Microsoft SharePoint Connector Guide Coveo Platform 6.5 Microsoft SharePoint Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing

More information

PATHFINDER3D Help. Updated September 26, Page 1 of 40

PATHFINDER3D Help. Updated September 26, Page 1 of 40 PATHFINDER3D Help Updated September 26, 2012 Page 1 of 40 Contents Introduction... 4 Product Description... 4 How to use this document... 4 Terms... 4 Procedures... 5 Installing... 5 Configuring... 6 Licensing...

More information

Agile Product Lifecycle Management

Agile Product Lifecycle Management Agile Product Lifecycle Management MCAD Connectors for Agile Engineering Collaboration Installation Guide V3.3.0.0 Oracle Part Number E50823-01 December 2013 Copyrights and Trademarks IMPORTANT NOTICE

More information

Quick Start Guide. Version R94. English

Quick Start Guide. Version R94. English Custom Reports Quick Start Guide Version R94 English December 12, 2016 Copyright Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya s Click-Accept

More information

EMC Documentum Composer

EMC Documentum Composer EMC Documentum Composer Version 6 SP1 User Guide P/N 300 005 253 A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com Copyright 2008 EMC Corporation. All rights

More information

StreamServe Persuasion SP5 StreamServe Connect for SAP - Business Processes

StreamServe Persuasion SP5 StreamServe Connect for SAP - Business Processes StreamServe Persuasion SP5 StreamServe Connect for SAP - Business Processes User Guide Rev A StreamServe Persuasion SP5StreamServe Connect for SAP - Business Processes User Guide Rev A SAP, mysap.com,

More information

Applications & Tools. Configuring Electronic Signatures in SIMATIC PCS 7. SIMATIC PCS 7 V8.0 SP1, SIMATIC Logon V 1.5. Application May 2014

Applications & Tools. Configuring Electronic Signatures in SIMATIC PCS 7. SIMATIC PCS 7 V8.0 SP1, SIMATIC Logon V 1.5. Application May 2014 Cover sheet Configuring s in SIMATIC PCS 7 SIMATIC PCS 7 V8.0 SP1, SIMATIC Logon V 1.5 Application May 2014 Applications & Tools Answers for industry. Siemens Industry Online Support This entry is taken

More information

MRO Management 6.0 Users Manual by Scanlon Associates

MRO Management 6.0 Users Manual by Scanlon Associates MRO Management 6.0 Users Manual by Scanlon Associates Version 6.0.70725 I 6.0.70725 Table of Contents Part I Main Screen 2 1 Work Area... 2 2 Browse Work... File 2 3 Toolbar... 2 4 Result Data Tab... 3

More information

Vault PlusPack App. Manual instructions

Vault PlusPack App. Manual instructions Greenock CAD Service NV/SA Industrielaan 27 (IZ III) B-9320 Erembodegem Tel: +32 53 781332 Fax: +32 53 779360 http://www.greenock.eu helpdesk@greenock.eu Vault PlusPack App Manual instructions Table of

More information

Adept 2018 PREP GUIDE

Adept 2018 PREP GUIDE Adept 2018 PREP GUIDE WHY WE WROTE THIS GUIDE We developed the Adept 2018 Prep Guide to make you aware of some important changes to Adept 2018 suite of products that you need to consider when you upgrade

More information

AUTOTEXT MASTER 1 PROGRAM HELP GILLMEISTER SOFTWARE.

AUTOTEXT MASTER 1 PROGRAM HELP GILLMEISTER SOFTWARE. AUTOTEXT MASTER 1 PROGRAM HELP GILLMEISTER SOFTWARE www.gillmeister-software.com 1 TABLE OF CONTENTS 1 Table of contents... 1 1. Start... 3 2 Main menu... 3 2.1 Menu entries of the group Main Menu... 3

More information

BC ABAP Workbench Tools

BC ABAP Workbench Tools HELP.BCDWBTOO Release 4.6B SAP AG Copyright Copyright 2000 SAP AG. All rights reserved. No part of this brochure may be reproduced or transmitted in any form or for any purpose without the express permission

More information

User Manual TypMaster/DD 3.1 PDC ECM&CRM&BI. Version 1.2 Last Revised Status Final Author Frank Merath / Ingrid Restle

User Manual TypMaster/DD 3.1 PDC ECM&CRM&BI. Version 1.2 Last Revised Status Final Author Frank Merath / Ingrid Restle User Manual TypMaster/DD 3.1 PDC ECM&CRM&BI Version 1.2 Last Revised 2012-08-20 Status Final Author Frank Merath / Ingrid Restle Privacy note: Internal Imprint Copyright 2012 by T-Systems T-Systems International

More information

Workspace Administrator Help File

Workspace Administrator Help File Workspace Administrator Help File Table of Contents HotDocs Workspace Help File... 1 Getting Started with Workspace... 3 What is HotDocs Workspace?... 3 Getting Started with Workspace... 3 To access Workspace...

More information

User Guide Items, Structures and Product Documentation

User Guide Items, Structures and Product Documentation User Guide Items, Structures and Product Documentation (c) 2013 Cad-Quality Finland Oy 2 1 Introduction This section describes SOVELIA PLM Core template features. The functionality provides you with systems

More information

Object Determination Softproviding Core User Documentation

Object Determination Softproviding Core User Documentation Great ideas are always simple Softproviding simply makes them happen. Object Determination Softproviding Core User Documentation Version: 1.00 Date 28. June 2017 Release: v2.50 Softproviding AG Riehenring

More information

SIMATIC. Process Control System PCS 7 OS Process Control (V8.1) Preface 1. Additional documentation 2. Functions of the PCS 7 OS in process mode 3

SIMATIC. Process Control System PCS 7 OS Process Control (V8.1) Preface 1. Additional documentation 2. Functions of the PCS 7 OS in process mode 3 Preface 1 Additional documentation 2 SIMATIC Process Control System PCS 7 Operating Instructions Functions of the PCS 7 OS in process mode 3 PCS 7 OS process mode - user interface 4 System operator inputs

More information

Manual. Software Protection. TwinCAT 3. Version: Date:

Manual. Software Protection. TwinCAT 3. Version: Date: Manual Software Protection TwinCAT 3 Version: Date: 1.7 2018-10-25 Table of contents Table of contents 1 Foreword... 5 1.1 Notes on the documentation... 5 1.2 Safety instructions... 6 2 Introduction...

More information

Publishing Options for Autodesk Vault 2009

Publishing Options for Autodesk Vault 2009 AUTODESK VAULT WHITE PAPER Publishing Options for Autodesk Vault 2009 Introduction When a CAD file is checked into Autodesk Vault, the vault client publishes a DWF of the file. In previous releases, Autodesk

More information

Office Adapters for Quark Publishing Platform

Office Adapters for Quark Publishing Platform Office Adapters for Quark Publishing Platform Contents Getting started... 1 About Quark Publishing Platform...1 System requirements... 3 Installing the Office Adapters for Quark Publishing Platform...

More information

COMOS. Lifecycle Material Management. General information 1. Introduction 2. Definitions 3. Creating material in COMOS 4

COMOS. Lifecycle Material Management. General information 1. Introduction 2. Definitions 3. Creating material in COMOS 4 General information 1 Introduction 2 COMOS Lifecycle Operating Manual Definitions 3 Creating material in COMOS 4 Importing material from external sources 5 Material documentation and order requests 6 Administration

More information

Agile Product Lifecycle Management

Agile Product Lifecycle Management Agile Product Lifecycle Management MCAD Connectors for Agile Engineering Collaboration User Guide V3.3.0.0 Oracle Part Number E50822-01 Dezember 2013 Copyrights and Trademarks IMPORTANT NOTICE This document

More information

H A N D B O O K. Tools. Intrexx 7

H A N D B O O K. Tools. Intrexx 7 H A N D B O O K Tools Intrexx 7 Contents 1. General... 4 2. E-mail-Service... 4 2.1. Determine from which portal the message was sent... 9 3. System Monitor... 10 3.1. Sessions... 10 3.2. Databases...

More information

Kaseya 2. User Guide. Version 7.0. English

Kaseya 2. User Guide. Version 7.0. English Kaseya 2 Custom Reports User Guide Version 7.0 English September 3, 2014 Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya s Click-Accept EULATOS

More information

EMC Documentum External Viewing Services for SAP

EMC Documentum External Viewing Services for SAP EMC Documentum External Viewing Services for SAP Version 6.0 Administration Guide P/N 300 005 459 Rev A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com Copyright

More information

WORKFLOW MANAGER RELEASE NOTES NEW FEATURES * OPEN ISSUES * ADDRESSED ISSUES RELEASE DATE: MAY 17, 2013 CS.THOMSONREUTERS.COM

WORKFLOW MANAGER RELEASE NOTES NEW FEATURES * OPEN ISSUES * ADDRESSED ISSUES RELEASE DATE: MAY 17, 2013 CS.THOMSONREUTERS.COM WORKFLOW MANAGER RELEASE NOTES NEW FEATURES * OPEN ISSUES * ADDRESSED ISSUES RELEASE DATE: MAY 17, 2013 CS.THOMSONREUTERS.COM Proprietary Materials No use of these Proprietary materials is permitted without

More information

COMOS. Operations MRO. Introduction 1. Maintenance objects 2. "General maintenance" plugins 3. "Events" plugin 4. "Resources" plugin 5

COMOS. Operations MRO. Introduction 1. Maintenance objects 2. General maintenance plugins 3. Events plugin 4. Resources plugin 5 Introduction 1 Maintenance objects 2 COMOS Operations Operating Manual "General maintenance" plugins 3 "Events" plugin 4 "Resources" plugin 5 "Warehouse management" plugin 6 Object search 7 Lifecycle structure

More information

AmpereSoft ToolSystem

AmpereSoft ToolSystem AmpereSoft ToolSystem 2016.1 New Functions & Improvements AmpereSoft MatClass AmpereSoft ToolDataManager AmpereSoft TemperatureCalculator 2016 by AmpereSoft GmbH Any software and hardware names and brand

More information

OpenLM Agent Installation V and Up

OpenLM Agent Installation V and Up OpenLM Agent Installation V4.2.12 and Up 1 OpenLM Agent Installation V4.2.12 and Up Introduction The OpenLM Agent may be installed on any number of workstations to enhance the enduser experience and control.

More information

Function. Description

Function. Description Function Check In Get / Checkout Description Checking in a file uploads the file from the user s hard drive into the vault and creates a new file version with any changes to the file that have been saved.

More information

Agile Product Lifecycle Management. User Guide

Agile Product Lifecycle Management. User Guide Agile Product Lifecycle Management MCAD Connectors for Agile Engineering Collaboration User Guide V 3.6.0.0 Oracle Part Number E86330-01 June 2017 Copyrights and Trademarks IMPORTANT NOTICE This document

More information

Agile Product Lifecycle Management. User Guide

Agile Product Lifecycle Management. User Guide Agile Product Lifecycle Management MCAD Connectors for Agile Engineering Collaboration User Guide V 3.4.0.0 Oracle Part Number E60708-02 March 2015 Copyrights and Trademarks IMPORTANT NOTICE This document

More information

CATIA Teamcenter Interface RII

CATIA Teamcenter Interface RII CATIA Teamcenter Interface RII CMI RII Release 3.1 User Manual Copyright 1999, 2011 T-Systems International GmbH. All rights reserved. Printed in Germany. Contact T-Systems International GmbH PDC PLM Fasanenweg

More information

CADMANAGERTOOLS.COM. BatchInDatabase 4.0. Automated Batch process tool for AutoCAD and Verticals

CADMANAGERTOOLS.COM. BatchInDatabase 4.0. Automated Batch process tool for AutoCAD and Verticals CADMANAGERTOOLS.COM BatchInDatabase 4.0 Automated Batch process tool for AutoCAD and Verticals Compatible with AutoCAD 2013 to 2018 BatchInDatabase - Batch process for AutoCAD Introduction: The BatchInDatabase

More information

SAP NetWeaver How-To Guide How To... Configure SAP HANA for CTS

SAP NetWeaver How-To Guide How To... Configure SAP HANA for CTS SAP NetWeaver How-To Guide How To... Configure SAP HANA for CTS Applicable Releases: SAP Solution Manager 7.1 SPS05, SAP NetWeaver 7.3 including enhancement package 1, or SAP NetWeaver 7.4 SAP HANA Platform

More information

Flow Computer. Manual Configuration of Device Software. FC1-CDS-EN b i From ensuite version 3.4

Flow Computer. Manual Configuration of Device Software. FC1-CDS-EN b i From ensuite version 3.4 Flow Computer encore FC1 Manual Configuration of Device Software FC1-CDS-EN b 2015-11-18 i 2015-11-18 From ensuite version 3.4 Elster GmbH Schloßstraße 95a D - 44357 Dortmund/Germany Tel.: +49 231 937110-0

More information

Agile Product Lifecycle Management

Agile Product Lifecycle Management Agile Product Lifecycle Management MCAD Connectors for Oracle Agile Engineering Collaboration Release Notes V3.0.2 Oracle Part Number - E26193-01 October 2011 COPYRIGHTS AND TRADEMARKS This document contains

More information

Agile Product Lifecycle Management

Agile Product Lifecycle Management Agile Product Lifecycle Management MCAD Connectors for Agile Engineering Collaboration User Guide V3.1.0.0 Oracle Part Number E38571-01 December 2012 Copyrights and Trademarks IMPORTANT NOTICE This document

More information

OUTLOOK ATTACHMENT EXTRACTOR 3

OUTLOOK ATTACHMENT EXTRACTOR 3 OUTLOOK ATTACHMENT EXTRACTOR 3 PROGRAM HELP GILLMEISTER SOFTWARE WWW.GILLMEISTER-SOFTWARE.COM 1 TABLE OF CONTENTS 1 Table of contents... 1 2 Start... 4 3 Main menu... 4 3.1 Menu entries of the group Menu...

More information

What s New in Autodesk V a ul t 20 18

What s New in Autodesk V a ul t 20 18 What s New in Autodesk V a ul t 20 18 Welcome & Agenda Introduction to Vault 2018 Enhanced Design Experience Engineering Efficiency Enabled Administration Tasks Delegation Autodesk Vault 2018 Building

More information

IBM Rational Rhapsody Gateway Add On. Rhapsody Coupling Notes

IBM Rational Rhapsody Gateway Add On. Rhapsody Coupling Notes Rhapsody Coupling Notes Rhapsody IBM Rational Rhapsody Gateway Add On Rhapsody Coupling Notes License Agreement No part of this publication may be reproduced, transmitted, stored in a retrieval system,

More information

INDEX. Installation Instructions. Basic Operations

INDEX. Installation Instructions. Basic Operations INDEX A B Installation Instructions A1-1. Steps for installation...06 A1-2. Preparation before installation...07 A1-3. How to uninstall via Start menu...08 A1-4. Install the basic program and library...09

More information

What's New GRAITEC Advance PowerPack 2016

What's New GRAITEC Advance PowerPack 2016 What's New GRAITEC Advance PowerPack 2016 Table of contents WELCOME TO GRAITEC POWERPACK FOR REVIT... 5 NEWS... 6 Managers... 6 1: Family Manager... 6 BIM Connect... 7 1: Compliancy with Autodesk Revit

More information

IBM TRIRIGA Application Platform Version 3.2. Graphics User Guide. Copyright IBM Corp i

IBM TRIRIGA Application Platform Version 3.2. Graphics User Guide. Copyright IBM Corp i IBM TRIRIGA Application Platform Version 3.2 Graphics User Guide Copyright IBM Corp. 2011 i Note Before using this information and the product it supports, read the information in Notices on page 31. This

More information

AppBot. Streaming Profiler to App-V version: 1.0 status: finished 11/2013 creation date: Andreas Nick

AppBot. Streaming Profiler to App-V  version: 1.0 status: finished 11/2013 creation date: Andreas Nick AppBot Streaming Profiler to App-V www.appbot.biz version: 1.0 status: finished 11/2013 creation date: 29.11.2013 Andreas Nick THIS DOCUMENT IS COPYRIGHTED BY NICK INFORMATIONSTECHNIK GMBH. IT MAY NOT

More information

This is new in Smap3D Plant Design 2016

This is new in Smap3D Plant Design 2016 This is new in Smap3D Plant Design 2016 Welcome to Smap3D Plant Design 2016 with Solid Edge Once again, the new version of Smap3D Plant Design contains a number of new features as well as enhancements

More information

SAP Workforce Performance Builder 9.5

SAP Workforce Performance Builder 9.5 Additional Guides Workforce Performance Builder Document Version: 1.0 2016-07-15 CUSTOMER Customization Typographic Conventions Type Style Example Description Words or characters quoted from the screen.

More information

IBM TRIRIGA Application Platform Version 3.3. Graphics User Guide. Copyright IBM Corp i

IBM TRIRIGA Application Platform Version 3.3. Graphics User Guide. Copyright IBM Corp i IBM TRIRIGA Application Platform Version 3.3 Graphics User Guide Copyright IBM Corp. 2011 i Note Before using this information and the product it supports, read the information in Notices on page 33. This

More information

Kaseya 2. User Guide. for VSA 6.3

Kaseya 2. User Guide. for VSA 6.3 Kaseya 2 InfoCenter User Guide for VSA 6.3 September 25, 2013 Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya s Click-Accept EULA as updated

More information

EMC Documentum Composer

EMC Documentum Composer EMC Documentum Composer Version 6.0 SP1.5 User Guide P/N 300 005 253 A02 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748 9103 1 508 435 1000 www.emc.com Copyright 2008 EMC Corporation. All

More information