CIDEON ECTR Interface To SolidEdge Configuration Manual

Configuration 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 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 Solid Edge 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.
© 2023 CIDEON Software & Services GmbH & Co. KG. Germany. All Rights Reserved.
Contents of this document may not be (totally or partly) reproduced, used or published without previous
written agreement by the CIDEON Software & Services GmbH & Co. KG.
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.
CIDEON Software & Services GmbH & Co. KG Page 1 of 86 2023-05-17

Peterstrasse 1 : D-02826 Goerlitz
Web: https://www.cideon.com
Folder structure and directories .................................................................................................................. 4
Icons for CAD originals in SAP ECTR ............................................................................................................... 5
Starting Solid Edge from ECTR in the SAP logon language ............................................................................. 7
The configuration files ................................................................................................................................... 9
Menu definitions ............................................................................................................................................. 9
menu.guidef ................................................................................................................................................ 9
menu_macros.txt ...................................................................................................................................... 11
attributes-from-sap.xml and attributes-to-sap.xml ....................................................................................... 11
attributes-from-sap.xml ............................................................................................................................ 12
attributes-to-sap.xml ................................................................................................................................. 15
Solid Edge Properties ................................................................................................................................ 16
default.txt ..................................................................................................................................................... 22
Parameter description - Part 1 .................................................................................................................. 22
Parameter description - Part 2 .................................................................................................................. 29
Problems with FOA handling and AdvancedBOM ...................................................................................... 36
dtype.xml ..................................................................................................................................................... 37
DType definitions for Solid Edge ............................................................................................................... 37
Generic DType definitions ..................................................................................................................... 38
The DType definitions for master documents ........................................................................................ 51
The DType definition for nonmaster documents .................................................................................... 69
Adopt component attributes .................................................................................................................. 72
options.xml ................................................................................................................................................... 73
plm_setenv.bat ............................................................................................................................................. 77
CustomOccurrenceProperty.xml (Assign material) ....................................................................................... 77
Version information ...................................................................................................................................... 78
Notes and configuration examples ............................................................................................................ 83
BOM derivation for Family Of Assembly (FOA) .............................................................................................. 83
Final Remark ................................................................................................................................................. 86

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\sle" is the installation directory of the SAP Engineering Control Center Interface
to Solid Edge. It contains the following subdirectories which are significant for configuration:
%PLM_INSTDIR%\applications\sle\appdata
%PLM_INSTDIR%\applications\sle\basis
%PLM_INSTDIR%\applications\sle\documentation
%PLM_INSTDIR%\applications\sle\templates
%PLM_INSTDIR%\applications\sle\template-templates
%PLM_INSTDIR%\applications\sle\customize\config
%PLM_INSTDIR%\applications\sle\template-customize\config
The directory "appdata"
The SAP Engineering Control Center Interface to Solid Edge has a ribbon bar in CAD next to the main menu
that contains its functions as buttons. In the subdirectory icons contained here, all 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 file "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".
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. They are copied and registered
here during installation.
The directory "documentation"
In this directory, the user manuals can be found in both German and English as PDF files.
The directories "templates" and "template-templates"
If a new document is created via the SAP Engineering Control Center, you can choose from a list of document
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 Solid Edge. These are:
default.txt
dtype.xml
options.xml
menu.guidef
menu_macros.txt
plm_setenv.bat
attributes-from-sap.xml
attributes-to-sap.xml
At the start of Solid Edge, 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, i.e. 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 directory "customize\config" for that reason.
After a software update, i.e. patch, the bundled configuration files are only stored in the
"template-customize\config" directory. Thus, the user settings remain in the directory
"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!
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 file "%PLM_INSTDIR%\applications\sle\base\classes\images.jar".
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
"%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 Solid Edge:
Icons for Solid Edge supplied as standard

Symbol Description File name in "images.jar"
Solid Edge single part document
DType: Document symbol position 1
tree\sle\solid_edge_part_16.png
tree/sle/solid_edge_part_$(FAMILY)16 with
$(FAMILY) = <empty>
Solid Edge family of parts document
tree\sle\solid_edge_part_g16.png
$(FAMILY) = g
Solid Edge alternative part document
tree\sle\solid_edge_part_i16.png
$(FAMILY) = i
Solid Edge sheet metal part document
DType: Document symbol position 1 tree\sle\solid_edge_sheet_metal_16.png
tree/sle/solid_edge_sheet_metal_16
Solid Edge assembly document
tree\sle\solid_edge_assembly_16.pngg
tree/sle/solid_edge_assembly_$(FAMILY)16 with
$(FAMILY) = <empty>
Solid Edge family of assemblies document
tree\sle\solid_edge_assembly_g16.png
$(FAMILY) = g
Solid Edge alternative assembly document
tree\sle\solid_edge_assembly_i16.png
$(FAMILY) = i
Solid Edge weldment assembly
DType: Document symbol position 1 tree\sle\solid_edge_weldment_16.png
tree/sle/solid_edge_weldment_16
Solid Edge drawing master document
DType: Document symbol position 1 tree\sle\solid_edge_draft_16.png
tree/sle/solid_edge_draft_16
Replacement is done in the file
Solid Edge drawing dependent document
"standard_icons.txt".
tree/sle/solid_edge_draft_160 =
(Document is up-to-date compared to the master)
tree/sle/solid_edge_draft_16
tree/sle/solid_edge_draft_16$(NM_OLD) with
Thus the file "tree\sle\solid_edge_draft_16.png"
$(NM_OLD)= 0
from the archive "images. jar" is used.

Replacement is done in the file
"standard_icons.txt".
Solid Edge drawing dependent document tree/sle/solid_edge_draft_161 =
DType: Document symbol position 1 tree/sle/solid_edge_draft_16
(Document is outdated compared to the master) <<{0}/sap/o_outdated
tree/sle/solid_edge_draft_16$(NM_OLD) with The file "tree\sle\solid_edge_draft_16.png" is
$(NM_OLD)= 1 overlaid with {0}\sap\o_outdated.
{0} stands for the size. Possible values are
small, medium, large.
Solid Edge document - single part
tree\file\obr_tree_file_sep.png
Workstation Application SEP
Solid Edge document – sheet metal part
tree\file\obr_tree_file_ses.png
Workstation Application SES
Solid Edge document – assembly
tree\file\obr_tree_file_sea.png
Workstation Application SEA
Solid Edge document – alternative assembly
tree\file\obr_tree_file_sem.png
Workstation Application SEM
Solid Edge document – drawing
tree\file\obr_tree_file_sed.png
Workstation Application SED
Solid Edge document – drawing
tree\file\obr_tree_file_seu.png
Workstation Application SEU
Solid Edge document – weldment assembly
tree\file\obr_tree_file_sew.png
Workstation Application SEW
Picture document
tree\file\obr_tree_file_bmp.png
Workstation Application BMP
Configuration document
tree\file\obr_tree_file_cfg.png
Workstation Application CFG
Configuration document
tree\file\obr_tree_file_sec.png
Workstation Application SEC
Monolithic JT document
tree\file\obr_tree_file_jtm.png
Workstation Application JTM
Dynamic JT document
tree\file\obr_tree_file_jtm.png
Workstation Application JTS
3D PDF document
tree\file\obr_tree_file_p3d.png
Workstation Application P3D
PDF document
tree\file\obr_tree_file_pde.png
Workstation Application PDE
Solid Edge Application
small\app_solid_edge.png
Menu: System\Start application\Solid Edge
Starting Solid Edge from ECTR in the SAP logon language

After its start, the SAP Engineering Control Center sets the environment variable "%PLM_LANGUAGE%" to the
SAP logon language. Their purpose is to be evaluated by other processes so that the CAD system to be started
appears in the corresponding language.
However, Solid Edge does not support this!
Unfortunately, there is currently no possibility to realize this technically. Solid Edge is always started in the

language in which it was installed.

The configuration files
The files contained in the %PLM_INSTDIR%\applications\sle\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 ANSI-text editor, i.e. the Windows-specific text editor
"Notepad.exe". They are filed there during the installation of the SAP Engineering Control Center Interface to
Solid Edge, 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 overridden
with the content of the CAD-specific configuration files. Each interface, if multiple interfaces are installed, has
its own set of CAD-specific 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!
Menu definitions
Menu items that should be available along with the SAP Engineering Control Center Interface to Solid Edge 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 Solid Edge 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.
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_SLEMDL":
Definition of the context menu for "Cloning"
# Cloning
+ om.popup.menu.CLONEPOS.DOC_SLEMDL = fnc.doc.clone.option.NO_ACTION
= fnc.doc.clone.option.NEWINTNR_OPTION
= fnc.doc.clone.option.NEWEXTNR_OPTION
= fnc.doc.clone.option.NEWVERS_OPTION
= fnc.doc.clone.option.CHANGE_OPTION
= -----------------------------
= fnc.doc.clone.select.dependent
= -----------------------------
= fnc.clpbrd.delete
= fnc.doc.reload
+ om.popup.menu.CLONEPOS.DOC_SLEDRW = fnc.doc.clone.option.NO_ACTION
= fnc.doc.clone.option.NEWINTNR_OPTION
= fnc.doc.clone.option.NEWEXTNR_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 Function
fnc.doc.clone.option.NO_ACTION "No Action"
fnc.doc.clone.option.NEWINTNR_OPTION "New internal Number"
fnc.doc.clone.option.NEWEXTNR_OPTION "Extended Clon Options"
fnc.doc.clone.option.INSERT_OPTION "Add Component"
fnc.doc.clone.option.REPLACE_OPTION "Replace Component"
fnc.doc.clone.option.DELETE_OPTION "Delete Component"
fnc.doc.clone.option.NEWVERS_OPTION "New Version"
fnc.doc.clone.option.CHANGE_OPTION "Change Details"
If this function is set, the menu allows you to select dependent
fnc.doc.clone.select.dependent
documents individually.
fnc.clpbrd.delete "Remove"
fnc.doc.reload "Reload"

IMPORTANT:
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.
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_SLE" is required, so that the SAP Engineering Control Center can start the
Solid Edge application as needed.
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 the 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 Solid Edge-specific attribute mapping files exist for this purpose:

"%PLM_INSTDIR%\applications\sle\customize\config\attributes-from-sap.xml"
and
"%PLM_INSTDIR%\applications\sle\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.
Please note:
With version 5.1.7 of the ECTR the inclusion of the standard section will be adapted in the file
"attributes-from-sap.xml".
Before:
<section name="GENERIC" default_section="true" description="Attribute mapping">
With ECTR version 5.1.7:
<section name="GENERIC" include_section="STANDARD" description="Attribute mapping">
The name of the included standard section comes from the global file "attributes-from-sap.xml"
file.
By changing it to "include_section" it is possible to use any defined "section" and extend it as
desired.
Various sections can be defined in the CAD-specific attribute mapping file

"%PLM_INSTDIR%\applications\sle\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 "dtype.xml". An attribute section (attribute
"attribute_section") can be assigned to each DType for creating (element "document_create") and saving
(element "primary_application").

Example for attribute mapping sections in the file "attributes-from-sap.xml"
<mapping>
<section name="GENERIC" include_section="STANDARD" description="Attribute mapping">
<APPL_ATTRIBUTE name="Name" hidden="false">
<XFORMAT outputFormat="{0}/{1}">
<CUTLEADING character="0">
<DIR field="DOCUMENTNUMBER"/>
</CUTLEADING>
<DIR field="DOCUMENTVERSION"/>
</XFORMAT>
</APPL_ATTRIBUTE>
<APPL_ATTRIBUTE name="SAP_DESCRIPTION" hidden="false"> <DIR field="DESCRIPTION"/>
</APPL_ATTRIBUTE>
<APPL_ATTRIBUTE name="SAP_USER" hidden="false"> <DIR field="USERNAME"/>
</APPL_ATTRIBUTE>
<APPL_ATTRIBUTE name="SAP_LASTSAVED" hidden="false"> <DIR field="CHECKIN_DATE"/>
</APPL_ATTRIBUTE>
</section>
<section name="STDMOD" description="Attributes for material">
<APPL_ATTRIBUTE name="SAP_MATERIAL_NO" hidden="false"> <MA field="MATERIAL"/>
</APPL_ATTRIBUTE>
<APPL_ATTRIBUTE name="SAP_MATERIAL_DESC" hidden="false"> <MA field="MATL_DESC"/>
</APPL_ATTRIBUTE>
<APPL_ATTRIBUTE name="SAP_MATERIAL" hidden="false"> <MA field="BASIC_MATL_NEW"/>
</APPL_ATTRIBUTE>
<APPL_ATTRIBUTE name="SAP_MATERIAL_WEIGHT" hidden="false"> <MA field="NET_WEIGHT"/>
</APPL_ATTRIBUTE>
</section>
</mapping>
The element <section> defines a section which represents an attribute segment.
Attribute of element <section>

Attribute Values Description
DTypes are referenced to this attribute segment with
name="..." Name of attribute division
this name in the file "dtypes.xml".
Name of section:
Specifies which section is to be included in the section
include_section="..." "STANDARD",
defined here.
"STDMOD", "default", etc.
Description of attribute This is a comprehensive description of an attribute
description="..."
sections section.
Within a section, attributes belonging to this attribute section are defined with the sub-element
<APPL_ATTRIBUTE>.
Attributes of the sub-element <APPL_ATTRIBUTE>

Name of the property in the document, possible values are listed in chapter
name="..." Attribute name
"Solid Edge Properties".
Determines whether this is a helper attribute ("true") or a regular document
hidden="..." true, false
attribute ("false").
Within the attribute definition, the subelement <DIR> addresses document attributes, and the subelement
<MA> addresses material attributes.

Attributes of subelements <DIR> and <MA>
Name of a field in SAP from which the value for the attribute should be read
out.
field="..." Field Name ATTENTION:

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.
row="…" Number 0 - x The value indicates the row, starting with 0. If the specified line is not
present, an error message is generated.
SAP language Identifier of the language in which the long text is stored in SAP, for
language="…"
code 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>
If character="0", "000000004711" 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>
If DOCUMENTNUMBER = "000000004711" and DOCUMENTVERSION = "02", the result is "000000004711/02".
Both subelements can be combined:
Example for combination of subelements <CUTLEADING> and <XFORMAT>
</CUTLEADING>
</XFORMAT>
In this case, the result is "4711/02".

Information regarding further possibilities for attribute mapping and the file structure of
"attributes-from-sap.xml" can be found in the "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\sle\customize\config\attributes-to-sap.xml".
Upon saving a CAD document, all attributes 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 of element <section>

DTypes are referenced to this attribute section with this
name="..." Name of attribute section
name in the file "dtype.xml".
Name of the section:
"STANDARD", Specifies which section is to be included in the section
include_section="..."
"STDMOD", defined here.
"default", etc.
Description of attribute This is a comprehensive description of an attribute
description="..."
sections 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>


Name of the document or material field which can be changed in SAP.
field="..." Field Name 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
(Optional) If field="LONGTEXT", the identifier of the language will be given
SAP language
language="…" in long text to be stored in SAP. Example "EN" = English, "DE" = German,
code
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>

name="..." Field Name SAP into which it will be written.
Mapping of CAD properties to language-dependent description fields for Import on Demand
If the CAD files contain attributes (properties) that contain the description of a part in different languages
(short text) and if these CAD file properties are to be mapped to the language-dependent description of the
document info record (DIS) during Import on Demand (IoD), the mapping must be done using the attribute
"_DOCDESCR":
Example for the mapping of short texts in the file "attributes-to-sap.xml"
<mapping>
<section name="my_attrib_section" description="mapping during IoD">
<DIR field="SAP_DESCRIPTION" language="DE" >
<APPL_ATTRIBUTE name="SAP_DOCTEXT_DE" />
</DIR>
<DIR field="SAP_DESCRIPTION" language="EN" >
<APPL_ATTRIBUTE name="SAP_DOCTEXT_EN" />
</DIR>
<APPL_ATTRIBUTE name="_DOCDESCR" >
<APPL_ATTRIBUTE name="SAP_DOCTEXT_EN" />
</APPL_ATTRIBUTE >
</section>
...
</mapping>
Information regarding further possibilities for attribute mapping and the file structure of
"attributes-to-sap.xml" can be found in the "Operations Guide_EN.pdf" in the SAP Engineering
Control Center, which can be found in folder "%PLM_INSTDIR%\documentation\Manuals\en".
Solid Edge Properties
General information
The Solid Edge properties provided by the SAP Engineering Control Center Interface to Solid Edge are
described below. The properties can be used in the files "attributes-to-sap.xml" and "attributes-from-sap.xml"
for the synchronization with SAP data.

The properties consist of a prefix and the actual property name. The prefix designates the property category.
Property categories
The following categories of properties exist:
Summary Information
Document Summary Information Properties
Custom Properties (User Defined Properties)
Extended Summary Information Properties
Project Information
Physical Properties
Mechanical Modeling Properties
Drawing Properties
Overview of Solid Edge Properties
Category: Summary Information

Prefix: SI-
ATTENTION:
The names of the Summary Information Properties are executed in the respective national
language! Here they are listed for English and German.
Solid Edge Summary Information Properties

Name (English) Name (German) Example property value Note
SI-Application Name SI-Anwendungsname Solid Edge
SI-Author SI-Autor user
SI-Comments SI-Kommentare ComfortMaker
SI-Keywords SI-Stichwörter Keyword - MainV5_H1.asm
SI-Last Author SI-Letzer Autor user
SI-Letztes
SI-Last Print Date 21.03.2019 14:48:04
Druckdatum
SI-Last Save Date SI-Zuletzt gespeichert 21.03.2019 14:48:04
SI-Number of
SI-Zeichenanzahl 42
characters
SI-Number of pages SI-Seitenzahl 14
SI-Number of words SI-Wortzahl 15
SI-Origination Date SI-Ursprungsdatum 19.03.2019 08:50:16
SI-Revision Number SI-Revisionsnummer 5
SI-Security SI-Datensicherheit 0
SI-Subject SI-Thema Subject - MainV5_H1.asm
SI-Template SI-Vorlage iso metric assembly.asm
SI-Title SI-Titel Title - MainV5_H1.asm
SI-Total Editing Time SI-Bearbeitungszeit
Only for assemblies. Supplied by SAP interface and not by Solid Edge! The
WELDMENTASSEMBLY WELDMENTASSEMBLY x
value is either "x" or empty.
LAST_SAVED_VERSION LAST_SAVED_VERSION Solid Edge 2019 Supplied by SAP interface and not by Solid Edge!
Category: Document Summary Information

Prefix: DSI-

ATTENTION:
The names of the Document Summary Information Properties are executed in the respective
national language! Here they are listed for English and German.
Solid Edge Document Summary Information Properties

Name (English) Name (German) Example property value
DSI-Byte Count DSI-Anzahl der Bytes 4711
DSI-Category DSI-Kategorie Product
DSI-Company DSI-Firma CIDEON
DSI-Hidden Objects DSI-Verdeckte Objekte 2
DSI-Lines DSI-Linien 5
DSI-Manager DSI-Manager
DSI-Multimedia Clips DSI-Multimediaclips 0
DSI-Notes DSI-Notizen 5
DSI-Paragraphs DSI-Absätze 3
DSI-Presentation Format DSI-Präsentationsformat
DSI-Slides DSI-Folien 1
Category: Custom Properties (User Defined Properties)

Prefix: None or UDP-
User-defined properties can be used with or without the prefix "UDP-". The parameter
"plm.options.updateAttributes.useInteropPrefix.SLE" in the configuration file "default.txt" can be
used to determine whether the prefix "UDP-" should be added to the custom properties.
Examples:
UDP-<Propertyname> --> "UDP- SAPName"
<Propertyname> --> "SAPName"
Category: Extended Summary Information

Prefix: ESI-
Solid Edge Extended Summary Information Properties

Name Example property value
ESI-CreationLocale 1031
ESI-DocumentID {9B48627F-375E-4E6C-B9BC-DE2BFD4E7901}
ESI-FriendlyUserName Mustermann, Max (DF PL S&SE DE PSM VC)
ESI-Name of Saving Application Solid Edge
ESI-Status 0
ESI-StatusChangeDate 13.03.2019 17:12:33
ESI-Username user
Category: Project Information

Prefix: PI-
Solid Edge Project Information Properties

PI-Document Number DocumentNumber - MainV5_H1_Top_V1_H1_V2_H1_V3_H1_V4_H1.asm

PI-Project Name ProjectNumber - MainV5_H1_Top_V1_H1_V2_H1_V3_H1_V4_H1.asm
PI-Revision RevisonNumber - MainV5_H1_Top_V1_H1_V2_H1_V3_H1_V4_H1.asm
Category: Physical Properties

Prefix: PP-
Solid Edge Physical Properties

PP-Area 60000,00
PP-AreaUnit mm^2
PP-Density 886,000
PP-DensityUnit kg/m^3
PP-Mass 0,886
PP-MassUnit kg
PP-Volume 1000000,000
PP-VolumeUnit mm^3
Category: Physical Properties

Prefix: Var-
ATTENTION:
The "Var-" properties for mass and volume listed here, like all other var properties, should not
be used, as they are often obsolete and not correctly updated by Solid Edge. You should always
use "PP-" properties for mass and volume instead! They are listed here for completeness only.
Solid Edge Physical Properties (VAR)
Name Example property value Note
Var-Mass 0.886000 Should not be used!
Var-MassUnit kg Should not be used!
Var-Volume 0.001000 Should not be used!
Var-VolumeUnit dm^3 Should not be used!
Category: Mechanical Modeling Properties

Prefix: MM-
Solid Edge Mechanical Modeling Properties

MM-Coef. of Thermal Exp 0,00016
MM-Elongation 0
MM-Face Style Blue
MM-Fill Style ANSI34(Plastic)
Can be overwritten from SAP (via the file "attributes-from-sap.xml"). For this, the integration checks
whether the material is also contained in one of the Solid Edge tables. If not, no update takes place.
MM-Material Polyethylene, low density
Currently, this is only noted in the log file. The material can also be changed in closed files without
having to open them!
It is possible to specify the material library where the material is located. This can be transferred from
SAP via the property MM-MaterialLibrary (via the file "attributes-from-sap.xml") or it is specified in
MM-MaterialLibrary CustomMaterialLibrary
the configuration file "default.txt" via the preference
plm.options.MechanicalModeling.UpdateMaterial.MaterialLibrary.SLE.
MM-Modulus of Elasticity 144789897
MM-Poission's Ratio 0,35
MM-Specific Heat 2219
MM-Thermal Conductivity 3,9
MM-Ultimate Stress 0

MM-Virtual Style Blue (shiny)
MM-Yield Stress 9652659,8
Category: Drawing Properties

Prefix: DP-
Solid Edge Drawing Properties

DP-BackgroundName A2-Sheet
DP-DefaultDrawingViewScale 2:1
DP-IsManualSheetScale false
DP-PaperUnit mm
DP-Scale 2:1
DP-ScaleFactor 2
DP-SheetCount2dModelSection 1
DP-SheetCountAll 7
DP-SheetCountBackgroundSection 4
DP-SheetCountBlockViewSection 0
DP-SheetCountDrawingViewSection 1
DP-SheetCountWorkingSection 1
DP-SheetHeight 0,42
DP-SheetSize ISO A2 Wide (594mm x 420mm)
DP-SheetSizeID IsoA2Wide
DP-SheetWidth 0,594
The individual sheet names are delivered to SAP in the file "plm_metainf-sap.xml" in
the following format:
DP-SheetName-Index-[Index number]
Example:
DP-SheetName A4-Sheet
Supply physical units in DocumentUnit
In Solid Edge, units can be selected for specific documents. This is done in the "Solid Edge Options" dialog
under "Units".

ATTENTION:
With the unit "Area", problems can occur if a value from "1/2" to "1/64" is selected for the
accuracy:
Possible values for the precision of the unit "Area"

Solid Edge does not always convert the values. It may happen that the value "½" is transferred
alphanumerically for the area. Since this is not a number, SAP will report an error here!
To be able to supply physical units in the units specifically selected or user-defined for a document, there are
the "DocumentUnit" properties. These are also configuration-dependent and must be used in the form "PP-
<Propertyname>".
Solid Edge Physical Properties

Name ReadOnly Example value Comment
PP-MassInDocumentUnit X 0,125
PP-MassUnitInDocumentUnit X kg
PP-VolumeInDocumentUnit X 0,000125
PP-VolumeUnitInDocumentUnit X m3
PP-AreaInDocumentUnit X 0,015 Note restrictions for values "1/x"!
PP-AreaUnitInDocumentUnit X m2 Note restrictions for values "1/x"!
The DocumentUnit properties in the configuration file "attribute-to-sap.xml" are used as follows:

Using the DocumentUnit properties in the "attribute-to-sap.xml" configuration file
<MA field="MARA-NTGEW">
<APPL_ATTRIBUTE name="PP-MassInDocumentUnit" />
</MA>
<MA field="MARA-GEWEI">
<APPL_ATTRIBUTE name="PP-MassUnitInDocumentUnit" />
</MA>
<MA field="MARA-VOLUM">
<APPL_ATTRIBUTE name="PP-VolumeInDocumentUnit" />
</MA>
<MA field="MARA-VOLEH">
<APPL_ATTRIBUTE name="PP-VolumeUnitInDocumentUnit" />
</MA>
The following conversion factors and text values for the units apply:
Conversion factors and text values for units

Setting in Solid Edge Conversion factor (from kg) Unit
Grams 1000 g
Kilograms 1 kg
Milligrams 1000000 mg
Pounds 2,2046 lb
default.txt
The file "default.txt" contains basic settings that influence the interaction between the SAP Engineering Control
Center, SAP Engineering Control Center to Solid Edge 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".
ATTENTION:
• After all changes of options in the file "default.txt" the ECTR must be restarted!
• To be able to use logging with an older ECTR version prior to 5.2 or 5.1.15, the preference
"ECTR-LOG-DIR = @PLM_LOGDIR@" must be set here in the file "default.txt"! From ECTR version
5.2 or 5.1.15 this is no longer necessary and the preference is then obsolete.
Further information about this topic can be found in the user manual in the chapter "Logging"!
The following pages "Parameter description - Part 1" and "Parameter description - Part 2" contain the
description of all parameters contained in the "default.txt" file in the delivery state as well as their default
values.
Parameter description - Part 1
The following table contains the first part of the description of all parameters, which are contained in the file

"default.txt" in the delivery state.
The second part follows on the next page, "Parameter description - Part 2"!
Parameters of file "default.txt" for Solid Edge - Part 1

Parameter construction:
plm.control.empty.dtype.<DOKAR> = <DTYPE>
plm.control.empty.dtype.SEA = SEA
Parameter:
plm.control.empty.dtype.SEP = SEP
plm.control.empty.dtype.SED = SED
plm.control.empty.dtype.SES = SES
plm.control.empty.dtype.SEW = SEW
Necessary for the parallel operation CDESK / ECTR. As the documents created with CDESK have no DType, a DType can be allocated to every type of
Description:
document here.
Values: DType identifier.
Default value: See under Parameters.
Parameter: plm.document.genericDTypes.SLE
Description: Specifies the generic DTypes.
Values: A list of DTypes, separated by ';'
Default value: SEP;SEA
plm.document.variantDType.SEA = SEM
Parameters: plm.document.variantDType.SEP = SEP
plm.document.variantDType.SES = SES
Description: Defines the assignment of variant DTypes to specific generic DTypes.
Values: A list of DTypes, separated by ';'.
plm.document.dtype.Default.PAR.SLE = SEP
plm.document.dtype.Default.ASM.SLE = SEA
Parameters:
plm.document.dtype.Default.DFT.SLE = SED
plm.document.dtype.Default.PSM.SLE = PSM
Description: Defines the assignment of the default DTypes to the document types Part, Assembly, Drawing and Weldment Part.
Values: The respective default type.
Parameter: plm.appl.popwin.name.SLE
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
Description:
substring.
Values: Name of main window of the Workstation application and substring, which is a component of the window name (driven by the wild card '*').
Default value: *Solid Edge*
Parameter: plm.adv.clone.renamerProgram.SLE
Description: During cloning, renaming is necessary through an external program, which must be specified here.
Values: Full path of the program to be renamed.
Default value: @PLM_BINDIR_SLE@\\renamer3sle.exe
Parameter: plm.options.importOnDemand.TransferAttributesToSAP.SLE
Description: If you use an attribute section for <document_create> you have to set this option.
"true" = Use an attribute_section for <document_create>
Values:
"false" = No using of an attribute section for <document_create>
Default value: false
Parameter: plm.options.UpdateAttributes.UpdateReadOnly.SLE
Description: Determines whether attributes of ReadOnly documents should be updated in the structure.
"true" = Update attributes of ReadOnly documents
Values:
"false = Attributes of ReadOnly documents are not updated
Default value: true
Parameter: plm.options.Draft.UpdateViews.AfterAttributeUpdate.SLE
Specifies whether views of drawings should be updated automatically or not.
By default, views are automatically updated after properties of drawings are updated. However, this can take quite a long time for many views. Therefore,
there is the possibility to suppress this.
Description:
ATTENTION:
It should be noted that the views should be updated manually if the value is set to "false"!
"true" = Views automatisch aktualisieren
Values:
"false" = Keine automatische Aktualisierung der Views
Default value: true
Parameter: plm.convert.additional.SLE
Description: Specifies to which Solid Edge document types additional formats can be generated.
Values: A list of DTypes, separated by ';'
Default value: SEA;SEP;SED;SES;SEW;SDM

plm.convert.additional.SLE.<DOCTYPE1> = <CONVERT TYPE1>;<CONVERT TYPE2>
plm.convert.additional.SLE.SEA = jt
Parameters: plm.convert.additional.SLE.SEP = jt
plm.convert.additional.SLE.SES = jt
plm.convert.additional.SLE.SEW = jt
plm.convert.additional.SLE.SED = pdf
plm.convert.additional.SLE.SDM = pdf
Description: Specifies which additional file formats should be generated for which Solid Edge document types.
A list of additional file formats, separated by ';'.
The additional format type "3dpdf" creates a simple 3D-PDF of the model.
Values:
ATTENTION:
The creation of additional 3D-PDF formats is only possible if the corresponding documents are opened in Solid Edge. Otherwise, no export is performed,
and an error message will be written to the log!
Default value: See under Parameters
Parameter: plm.convert.additional.SLE.jt.keepExtension
Description: Determines whether the file extension for jt files should be retained.
"true" = Keep file extension
Values:
"false" = Do not keep file extension
Parameter: plm.convert.additional.SLE.JT.filenameFormat
The names for additional formats can be configured.
The following placeholders are available, which are replaced by the corresponding SAP values:
Description: • "$ (DOCNUMBER)": SAP name
• "$ (DOCTYPE)": Document category
• "$ (DOCVERSION)": Document version
• "$ (DOCPART)": Document section
Value: String that can contain the allowed placeholders.
Default value: Number.$(DOCNUMBER)_Type.$(DOCTYPE)_Version.$(DOCVERSION)_Part.$(DOCPART)
plm.convert.additional.SLE.<DOCTYPE1>.<CONVERT TYPE1>.extension = destination Extension
Parameter:
plm.convert.additional.SLE.SEA.JT.extension
Description: Specifies which file name extension should have an additional format ("JT" here)
Value: File extension
Default value: jt
plm.convert.additional.SLE.<DOCTYPE1>.<CONVERT TYPE1>.options = <VALUE>
Parameter:
plm.convert.additional.SLE.JT.options
Description: The option exists to set specific options for additional formats (here for "JT"). These can then be assigned a value.
Values: The name of an assigned option
Default value: Version
plm.convert.additional.SLE.<DOCTYPE1>.<CONVERT TYPE1>.<OPTION> = <VALUE>
Parameter:
plm.convert.additional.SLE.SEA.JT.Version
Description: If a specific option is set for an additional format, this can also be given a value for a Solid Edge document type (here, the document type "SEA").
Values: The value that the option should be assigned
Default value: 9
Parameter: plm.options.Thumbnail.SLE.jpg.<preference>

It is possible to configure the creation of thumbnails.
ATTENTION:
Currently, only the Jpeg format "jpg" is allowed!
Several settings are possible for the selected file format. These are selected via <preference>.
Possible options for <preference> are:
1.) "size": This is the resolution used for the preview image. If "size" is not set, the value of the parameter "plm.options.Thumbnail.Size.SLE" is used.
Example:
plm.options.Thumbnail.SLE.jpg.size = 180
2.) "fileformat": Specifies a rule how the file name of the thumbnail file is to be formed. There are different placeholders (tokens) available, which are
replaced by corresponding values:
• $(DOCNUMBER)
• $(DOCTYPE)
• $(DOCVERSION)
• $(DOCPART)
• $(ORIGINALFILENAME)
• $(ORIGINALEXTENSION)
Description:
Example:
plm.options.Thumbnail.SLE.jpg.fileformat = $(ORIGINALFILENAME).preview
IMPORTANT:
• If the file name is configured in such a way that the ".preview" extension is no longer contained or otherwise named, the "filename_pattern" parameter in
the "<save_direct>" and "<delete_in_session>" areas of the configuration file "dtype.xml" must be adjusted.
• It should be noted that without ".preview" for the preview image (with corresponding adjustment in configuration file "dtype.xml"), problems can occur if
linked JPG files are used in the constructions, since no distinction between preview image and linked image is made here.
NOTE:
If the preference is not set, the preview image will be created as "$(ORIGINALFILENAME).preview.jpg".
3.) "keepExtension": Determines whether the token "$(ORIGINALFILENAME)" keeps the extension of the master original or whether it is removed.
Possible values are:

"true" = The extension of the master original remains unchanged
"false" = The extension of the master original will be removed
Example:
plm.options.Thumbnail.SLE.jpg.keepExtension = true
Values: See under Description!
plm.options.Thumbnail.SLE.jpg.size = 180
Default value: plm.options.Thumbnail.SLE.jpg.fileformat = $(ORIGINALFILENAME).preview
plm.options.Thumbnail.SLE.jpg.keepExtension = true
Parameter: plm.options.CreateDIRForNewDocument.SLE
Description: Determines whether and how a document info record (DIR) should be created in a newly generated document.
'0' = never generate a document info record
Values: '1' = always generate a document info record
'2' = ask the user if a document info record should be generated
Default value: 2
Parameter: plm.options.HideDIRCreationDialog.SLE
Description: Determines whether the display of the ECTR dialog "Create DIS" should be prevented when creating a new document info record (Create Dark).
"true" = Prevent display of the dialog (create dark)
Values:
"false" = Show dialog
Parameter: plm.options.SaveDIRAfterCreation.SLE
Defines whether documents are to be saved in SAP when an assembly or drawing with a DIR is created from an active model.
Description: ATTENTION:
When a drawing is created from a model, it is saved after positioning the first view. So, you cannot insert more than one view! When inserting further
views, the drawing must be checked out.
"true" = Save to SAP
Values:
"false" = Do not save
Parameter: plm.bom.create.SED
Description: Determines whether a bill of materials (BOM) should be generated for drawings (document type SED).
"true" = Generate BOM
Values:
"false" = Do not generate BOM
Parameter: plm.bom.createAtCheckin.SED
Description: Determines whether a bill of materials (BOM) should be generated for drawings (document type SED).
"true" = Generate BOM
Values:
"false" = Do not generate BOM
Parameter: plm.bom.updateAtCheckin.SED
Description: Determines whether an existing BOM should be updated during checkin.

"true" = Update BOM
Values:
"false" = Do not update BOM
Parameter: plm.bom.update.SED
Description: Determines whether an existing BOM should be updated
"true" = Update BOM
Values:
Parameter: plm.document.save.alwaysUpdateStructures
Description: Determines whether an existing BOM should be updated when a connected document is being saved.
"true" = Update BOM
Values:
Default value: true
Parameter: sap.plm.attributesmapping.CAD_GET_TITLE_BLOCK_DATA.<DOKAR>
Determines whether the function module "CAD_GET_TITLE_BLOCK_DATA" should be called up during the update of attributes for a specific document
Description:
type <DOKAR>.
"true" = Call the function module for the specified document type
Values:
"false" = Do not call the function module
Parameter: plm.document.createMulti.cad.dtype.searchAlso.SLE
Description: Specifies non-solid edge DTypes to be considered for import.
Values: List of DTypes, separated by semicolon.
Default value: SXLS;PICP;PICT;PICJ;PICB
Parameter: plm.options.updateAttributes.useInteropPrefix.SLE
Description: Determines whether the prefix "UDP-" will be used for user-defined properties ("UDP").
"true" = Use prefix
Values:
"false" = Do not use prefix
Default value: true
Parameter: plm.document.SaveAsNewDocument.CheckOutTop.SLE
Determines how the parent document should be moved during the functions "save as new document" and "save as new version".
Description: WARNING:
Checking out before "save as new document" and "save as new version" does not work with all parent documents in Solid Edge! Therefore, this has been
disabled by default.
'0' = Do not check out
Values: '1' = Check out
'2' = Check out and save (intermediate)
Default value: 0
Parameter: plm.options.ReplaceVersion.CheckoutParents.SLE
Description: Determines whether all parent documents should be automatically checked out when the version of a document is replaced.
"true" = Check-out of all parent documents
Values:
"false" = Do not check out parent documents
plm.bom.item.property.SLE
Parameter:
plm.bom.item.property.SLE.<OccurrencePropName>
"Custom Occurrence Properties" from Solid Edge can be transferred to the SAP system as properties.
To achieve this, the names of the Custom Occurrence Properties to be transferred must be defined and the names of the SAP properties assigned to them
must be specified:
1. plm.bom.item.property.SLE
This parameter is used to pass a list of Custom Occurrence Properties.
Example: plm.bom.item.property.SLE = OccurrencePropName1;OccurrencePropName2
2. plm.bom.item.property.SLE.<OccurrencePropName>
Description: This parameter is used to assign one SAP property to each Custom Occurrence Property.
Example: plm.bom.item.property.SLE.OccurrencePropName1 = SAPProperty1
ATTENTION:
• To use this feature, the option "Maintain item numbers" must be activated in the "Solid Edge Options" dialog under "Position numbers" so that the
position numbers are retained. Otherwise, the Custom Occurrence Properties are not processed.
IMPORTANT: This option is file-dependent and must be set for each SLE document individually!
• Using these parameters is optional. Therefore, no default values are delivered!
plm.bom.item.property.SLE: List of Custom Occurrence Properties names, separated by semicolons.
Values:
plm.bom.item.property.SLE.<OccurrencePropName>: Name of the SAP property assigned to the respective Custom Occurrence Property.
Default value: --
Parameter: plm.document.FOA.Handling.SLE
Determines whether "Family of Assemblies" (FOA) is supported using MaintainGeneric.
Description: ATENTION:
• A change becomes effective only after restarting Solid Edge and ECTR!
• The value '2' causes that in addition to the Occurrences of a part also the names of the FOA members, in which it is installed, write into the SAP table
DMU_TMXMETA. For further information, see chapter "Problems with FOA handling and AdvancedBOM"!
'0' = No special handling for FOAs.
Values: '1' = Use MaintainGeneric.
'2' = Store the number of shoring units of a part and the names of the FOA members in the SAP table DMU_TMXMETA.

Default value: 0
Parameter: plm.doc.checkout.allowedFamilyMembersApplTypes
Description: Specifies which members of Family of Assemblies (FOA) should be able to check out.
Values: List of Application Types
Default value: SLE;@plm.doc.checkout.allowedFamilyMembersApplTypes@
Parameter: plm.document.variantKeepVersion.SLE
Description: Specifies whether MaintainGeneric should keep its members during versioning.
"true" = Yes
Values:
"false" = No
Default value: true
Parameter: plm.convert.additional.FamilyMembers.SLE
Description: Specifies whether additional formats should be created for members of FOAs.
"true" = Yes
Values:
"false" = No
Default value: true
Parameter: plm.document.DirtyFlag.SLE
Specifies the dirty flag handling.
There are two different dirty flags in Solid Edge:
Description:
• "Dirty": Specifies whether the referenced document has been modified since the last time it was saved.
• "GeometricVersionDirty": Retrieves whether the geometric version number of the document is dirty or not.
'0' = "Dirty" flag
Values:
'1' = "GeometricVersionDirty" flag
Default value: 0
Parameter: plm.options.DisableDirtyHandlingForWritingComponentIDs.SLE
Determines whether the default handling for documents marked as dirty should be disabled when writing component IDs.
Description:
NOTE:
This setting is only used for Solid Edge versions older than 2019! From Solid Edge version 2019 on, the Solid Edge component IDs are used.
'0' = Component IDs will be written for read only documents
Values:
'1' = Component IDs will not be written for read only documents
Default value: 0
Parameter: plm.options.UpdateAttributes.RefreshContext.SLE
Description: Specify which documents will be affected during attribute refresh.
'0' = Complete structure
Values: '1' = Only selected / top document
'2' = Ask user
Default value: 0
Parameter: plm.document.variants.importOnDemand.SAPDescription.SLE
Description: Defines the SAP description for members of FOAs.
'1' = Member name in Solid Edge
Values: '2' = SAP FOA description
'3' = SAP FOA description and Solid Edge member name
Default value: 3
Parameter: plm.options.importOnDemand.loadDrawings.SLE
Determines whether drawings with a reference to the actual model will be imported too.
Description:
ATTENTION:
This option may decrease performance if activated!
"true" = Import
Values:
"false" = Do not import
Parameter: plm.options.CreateDependentDocument.AskUserOnAdditionalNonMasterCreate.SLE
Determines whether a new dependent document should always be created or an existing document should be opened during the "Create dependent
Description:
document" action if at least one dependent document is already assigned to the selected master.
"true" = Ask user
Values:
"false" = Always create a new dependent document
Parameter: plm.options.save.loadDrawings.SLE
Determines whether drawings with a reference to the actual model will be saved too.
Description:
ATTENTION:
This option may decrease performance if activated!
"true" = Save
Values:
"false" = Don't save
Parameter: plm.doc.cancel.restore.files.SLE
Description: Determines the action during the function "Cancel, discard changes."
"true" = Reset the local copy to the last check-in point
Values:
"false" = Delete the local copy from the session directory

Parameter: plm.structure.application.show.drawing.SLE
Description: Specifies whether referenced drawings are to be displayed in the ECTR application structure.
"true" = Show drawings
Values:
"false" = Do not display drawings
Parameter: plm.structure.application.show.drawing.container.SLE
Description: Specifies whether referenced drawings in the ECTR application structure are to be displayed in a separate folder within the structure.
"true" = Display referenced drawings from the session directory in a separate folder
Values:
"false" = Add referenced drawings from the session directory below the document node
Parameter: plm.structure.application.show.drawing.container.ontop.SLE
Description: Determines at which position referenced drawings in the ECTR application structure should be displayed within the structure.
"true" = The container with the referenced drawing will be shown above the subcomponents
Values:
"false" = The container with the referenced drawing will be shown below the subcomponents
Parameter: plm.structure.application.DisplaySuppressedComponents.SLE
Determines whether suppressed components should be displayed in the application structure or not.
Description:
ATTENTION:
This option is valid from Solid Edge version 2022!
"true" = Display suppressed components
Values:
"false" = Do not display suppressed components
Default value: true
Parameter: structure.view.SLE.generic.object.type
Specifies the generic object type to be displayed in the application structure.
Description:
NOTE:
For further information, please refer to the ECTR documentation.
Values: Generic object type.
Default value: POS_TYPE
structure.view.SLE.generic.object.DRAW_CONTAINER.name = DEFAULT_NAME
Parameters:
structure.view.SLE.generic.object.DRAW_CONTAINER.icon = {0}/sap/folder_open
Specifies default name and icon for folders in which drawings are to be displayed separately in the application structure.
Description:
NOTE:
For further information, please refer to the ECTR documentation.
Folder name as character string or DEFAULT_NAME.
Values:
Icon name in the file "images.jar" (see chapter "Icons for CAD originals in SAP ECTR").
Default value: See under Parameters!
structure.view.SLE.generic.object.SLE_VIRTUAL_NEW.name
Parameter:
structure.view.SLE.generic.object.SLE_VIRTUAL.name
Description: Specifies the attribute mapping for the default display of nodes.
Values: The key name or DEFAULT_NAME.
Default value: DEFAULT_NAME
Parameter: obr.filter.filter.asvselectpossible.sle
Description: Defines filter for the exclusion of the context menu function "Select" in the application structure of the ECTR.
Values: List of filters, separated by semicolon ';'.
Default value: *;PRP;_SELECT_POSSIBLE;STRING;(?i)false;RE
Parameter: obr.filter.filter.asvforeignpossible.sle
Defines filter for the exclusion of some context menu functions in the application structure of the ECTR for built-in non-solid edge files, e.g. "NX" and "JT"
Description:
files.
Values: List of filters, separated by semicolon ';'.
Default value: *;PRP;_ASV_FOREIGN_ORIGINAL;STRING;(?i)true;RE
Parameter: obr.filter.fnc.structure.view.application.generic(FUNCTION_ID)
Setting the filters as function filters for the Application Structure.
For FUNCTION_ID the following is possible:

sap_checkout, sap_save_checkin, sap_save, sap_save_as_new_version, sap_save_as_new_document, sap_cancel, sap_set_displayed, sap_set_active,
Description: sap_replace_version, sap_allow_local_modify, sap_replace_component.
NOTE:
Several parameters can be specified, each with a different function ID.
Function filter, separated by semicolon.
Example:
Values:
"filter.asvselectpossible.sle" associates the filters set with the parameter obr.filter.filter.asvselectpossible.sle with the corresponding function in the
application structure view.
Default value: filter.asvforeignpossible.sle;filter.asvforeignpossible.sle
Parameter: plm.document.IgnoreDrawing2DrawingReferences.SLE
Defines whether references from drawings to drawings in the application structure are to be ignored.
Description:
This is important for handling drawing frames and applies to Import, Save, Application Structure, etc.

"true" = Ignore references from drawings to drawings
Values:
"false" = Show references from drawings to drawings
Parameter: plm.control.waitForSessionInMs.SLE
Description: Maximum wait time for an application to send a request to ECTR once it has been contacted successfully.
Values: Time in ms.
Default value: 15000
Parameter: plm.Occurrence.IncludeInBOM.SLE
Description: Specify the SORTF for occurrences which are not included in assembly reports (Reports/Parts List = No).
Values: SORTF string
Default value: WU
Parameter: plm.Occurrence.UserDefinedQuantity.SLE
Specifiy the SORTF for occurrences with UserDefinedQuantity = 0.
Description:
The SAP Engineering Control Center to Solid Edge doesn't consider "UserDefinedQuantity" for excluded occurrences, if you set Reports/Parts List = No and
UserDefinedQuantity = 0 you will get the SORTF defined with this parameter.
Values: SORTF string
Default value: @plm.Occurrence.IncludeInBOM.SLE@
Parameter: plm.document.explode.hiddenExternalReferencesSortf.SLE
Description: There is a risk of circle references during cloning. This parameter is intended to prevent this.
Values: Sort criteria: 'Y' or 'N'.
Default value: Y
Parameter: plm.options.SapOpenForCadOpenDocument.SLE
Description: Decides which open file dialog will be used.
'0' = Use CAD default dialog
Values: '1' = Use SAP engineering control center dialog
'2' = Ask user
Default value: 0
Parameter: plm.loadoptions.SLE.ShowCADOpenDialog
Description: Defines whether the CAD dialog will be used for open during "Load".
"true" = Yes
Values:
"false" = No
Parameter: plm.options.open.UseMultiSearchForSapOpen.SLE
Description: Choose which ECTR open dialog should be used when opening a document from SAP. Enabling this option will let you open multiple documents at once.
"true" = Use multi search dialog
Values:
"false" = Use single search dialog
Default value: true
Parameter: plm.options.deliverOnlyRequestedAttributesToSAP.SLE
Description: Defines whether all existing or only requested attributes will be transferred.
"true" = transfer only requested attributes
Values:
"false" = transfer all existing attributes
Default value: true
Parameter description - Part 2
The following table contains the second part of the description of all parameters contained in the "default.txt"
file in the delivery state.
The first part is included on the previous page "Parameter description - Part 1"!
Parameters of file "default.txt" for Solid Edge - Part 2

experimental.renamer.call.SLE = true
plm.application.SLE.cadRenamer.enable = true
Parameter:
plm.application.SLE.cadRenamer.components = MULTI_LEVEL
plm.application.SLE.cadRenamer.explosionScenario = CAD_RENAMER
Controls the call of the additional application "renamer3sle.exe".
• These parameters come directly from the ECTR. This is necessary to ensure the function of the renamer. They should not be changed!
• For ECTR version 5.1.15 and from 5.2. the preference "experimental.renamer.call.SLE" is obsolete and can be removed!
Values: Since these parameters are not to be changed, no values are specified here.
Default values: See under Parameter!
Parameter: plm.document.create.references.mastercomp.name.SLE
Description: ECTR requires that the wildcard reference "mastermodel.asm" be replaced by a correct reference.
Values: Name of the reference by which the wildcard reference is to be replaced.

Default values: DummyRef.asm
Parameter: plm.options.Ballooning.BalloonContent.SLE
Description: Defines the content type of balloons.
'0' = material and BOM item number
'1' = material number
Values:
'2' = BOM position number
'3' = SAP balloon content
Default value: 2
Parameter: plm.options.Ballooning.InitializeBalloonWith.SLE
Description: Initialization of balloons with the specified string for balloons that could not be supplied with data from SAP.
Values: String for initialization.
Default value: "--"
Parameter: plm.options.checkIn.AbortAnalysisOfCheckedInComponents.SLE
Defines the check in strategy.
Description:
ATTENTION:
The value "false" can greatly influence the performance for complex document structures!
"true" = Only check in components, which have documents in their structure or are themselves locally modified and/or checked out.
Values:
"false" = Always analyze and check in the complete document structure whether components were modified or not.
Default value: true
Parameter: plm.options.checkIn.AbortAnalysisOfCheckedInComponents.AbortAtFOA.SLE
Determines whether to abort structural analysis of read-only FOA components that are not the active document during check-in.
Data can be lost if FOAs are not checked out when changes are made!
"true" = Abort
Values:
"false" = Do not abort
Default value: true
Parameter: plm.options.Thumbnail.Size.SLE
Description: Sets the size of thumbnails for the ECTR preview.
Value: Size of the thumbnails in pixels. Applies to height and width.
Default value: 180
Parameter: plm.options.PathFinder.Show.DocumentStatus.SLE
Value: Set the document status in Solid Edge, visible in Path Finder.
"true" = Update document status
Wert:
"false" = Don't update document status
Parameter: plm.options.SaveAsNewDocument.UseCopyAs.SLE
During "Save As New Document", the integration uses the "SaveAs" API function by default, which changes the reference in all files opened in Solid Edge.
With this setting, the default behavior can be changed, and the integration uses the "SaveCopyAs" API function instead, which creates a detached copy of
the file.
Description:
ATTENTION:
Not supported for generic files (Family of Parts and Family of Assemblies)!
'1' = Use "SaveAs"
Values:
'2' = Use "SaveCopyAs"
Default value: 1
Parameter structure:
plm.options.BOMTable.Column.SLE.[CAD_COLUMN] = [SAP_FIELD]
Parameters: plm.options.BOMTable.Column.SLE.Material = MATERIAL_EXT

plm.options.BOMTable.Column.SLE.Postext1 = POSTEXT1
plm.options.BOMTable.Column.SLE.Postext2 = POSTEXT2
plm.options.BOMTable.Column.SLE.OtherColumn = POSTEXT2
If a BOM table exists, and it contains a column with the name [CAD_COLUMN]
values within this column will be updated with the content of [SAP_FIELD].
Description:
ATTENTION:
These configuration options are available from Patch 12 of the interface!
Implemented values (tags) for [SAP_FIELD].
Possible values are:

• "MATERIAL" = Internal material number, returned in return table "ET_BALLOONS", column "MATERIAL"
• "MATERIAL_EXT" = External material number, returned in return table "ET_BALLOONS", column "MATERIAL_EXT"
• "POSTEXT1" = Value returned in return table "ET_BALLOONS", column "POSTEXT1"
• "POSTEXT2" = Value returned in return table "ET_BALLOONS", column "POSTEXT2"
Values: • "QUANTITY" = Value returned in return table "ET_BALLOONS", column "MENGE"
• "UNIT" = Value returned in return table "ET_BALLOONS", column "MEINS"
• <NAME> = Value returned in return table "ET_CUSTOMER_DATA", columns which are filled in enhancement implementation of
"/DSCSAG/DOC_BALLOONING_PROVIDE"
IMPORTANT:
For <NAME> you can take the values from "ET_CUSTOMER_DATA", which the function module "/DSCSAG/DOC_BALLOONING_PROVIDE" returns. However,
this table must be filled in a BAdI implementation!
Default value: See under "Parameters"!
Parameter: plm.options.BOMTable.AddNonExistingColumns.SLE

Add non-existing columns to BOM Table
Description:
If a column of name [CAD_COLUMN] does not exist in the BOM table, add this column and update the value with the content of [SAP_FIELD].
"true" = Add Columns
Values:
"false" = Do not add columns
Default value: true
Parameter: plm.options.Ballooning.UpdateStrategy.SLE
Determines in which area the balloon info should be written, regardless of how balloons are configured in Solid Edge.
Description: NOTES:
• The settings for balloons in the Solid Edge settings dialog "Partslist Properties" are ignored!
• If the item numbers are to be overwritten, they must be unique in the parts list!
'0' = According to the Balloon configuration in Solid Edge
'1' = Upper text in balloon
Values:
'2' = Bottom text in balloon
'3' = Overwrite item number
Default value: 0
Parameter: plm.document.IgnoreInterpartLinks.SLE
Determines whether interpart links should be ignored when importing new data.
Description:
NOTE:
A warning is displayed if the linked document is not found.
Values: "ignorePartToAssemblyLinks" = Links from parts to assemblies are ignored. This is logged while the import is running.
Default value: ignorePartToAssemblyLinks
Parameter: plm.document.CustomIgnoreDirectories.SLE
This setting is used to specify user-defined directories of parts or assemblies that should not be stored in a DIR.
Description: NOTES:
• This parameter is optional!
• The directory paths must be enclosed in quotes and backslashes must be doubled ('\\')!
Values: A list of directory paths, separated by semicolons.
Default value: "D:\\IgnoreAdditionals"; "D:\\ExcludedReferences"
Parameter: plm.document.CustomIgnoreDirectories.IgnoreSubDirectories.SLE
Specifies whether references in subdirectories in the user-defined directories from which references are to be ignored should also be ignored or not.
Description: NOTE:
This parameter is optional!
"true" = All references in subdirectories are also ignored.
Values:
"false" = All references in subdirectories are respected.
Default value: true
plm.library.SLE.<library name> = <Path to library>
Parameter:
plm.library.SLE.PartLib
To define a user-defined standard part library, its file path must be specified.
• This path must be identical on all workstations!
• The directory path must be enclosed in quotes and backslashes must be doubled ('\\')!
File path of the standard parts library.
Values: Example:
"C:\\Solid Edge Standard Parts\\Standard Parts"
Default value: --
plm.document.dtype.<library name>.SLE= <DType name>
Parameter:
plm.document.dtype.PartLib.SLE
Description: This parameter can be used to predefine a DType in the "Import on demand" dialog for a user-defined standard.
Name of the DType.
Values:
Example: SEN
Default value: --
plm.tree.workdir.unknown.files.exclude.SLE.[Category] = [Regular Expression]
Parameters: plm.tree.workdir.unknown.files.exclude.SLE.CFG = .*\.(?i)(cfg)

plm.tree.workdir.unknown.files.exclude.SLE.CadCache = .*\.(?i)(db)
plm.tree.workdir.unknown.files.exclude.SLE.LogFiles = .*\.(?i)(log)
plm.tree.workdir.unknown.files.exclude.SLE.CollectionOfExtensions = .*\.(?i)(jt|jpg|jpeg|bmp)
Description: With this setting, you can hide unknown files that are located in the working directory.
Values: The filter expression is specified as a Regular Expression.
Default value: See under "Parameters"!
Parameters: plm.execute.additional.SLE

It is possible to execute additional functions before or after a specific PLM process by starting either an executable file (external tool), the PowerShell or
CADMacro (Solid Edge).
The following specifications are possible:
1.) Specifies the time of execution per document type:

plm.execute.additional.SLE.<DOCTYPE>.<EXEC TIME>
Possible options for <EXEC TIME> are:

• "BeforeCheckIn": Execute before check in
• "AfterCheckOut": Execute after check out
• "AfterBallooning": Execute after ballooning
• "BeforeCreateDocuments": Execute before import
• "BeforeSaveAs": Execute before save
Example:
plm.execute.additional.SLE.SEA.BeforeCheckIn
2.) Specifies the type of additional function:

plm.execute.additional.SLE.<DOCTYPE>.<EXEC TIME>.type = [EXEC TYPE]
Possible options for are:

• "Executable": External tool
• "Powershell": Starts the Windows PowerShell
• "CADMacro": Starts a Solid Edge CADMacro
Example:
plm.execute.additional.SLE.SEP.BeforeCheckIn.type = Executable
3.) Specifies the name of the external program, macro or command:

plm.execute.additional.SLE.<DOCTYPE>.<EXEC TIME>.commandLine = [CMDLINE]
Description: Example:
plm.execute.additional.SLE.SEA.BeforeCheckIn.commandLine = D:\\Data\\Tools\\ExternalTool.exe
NOTE:
• Executables need a valid file path with escaped backslashes!
Example: "D:\\Data\\Tools\\ExternalTool64.exe"
• When using CADMacro, relative paths can also be specified!
Example: "..\\..\\..\\..\\..\\..\\Script\%USERNAME%\CIDEON.exe"
• When using CADMacro, environment variables are also evaluated!
4.) Specifies the parameters to pass as a string:

plm.execute.additional.SLE.<DOCTYPE>.<EXEC TIME>.parameterN = [PARAM VALUE]
The placeholder 'N' stands for the parameter number. The parameter number determines the order in which the parameters are passed!
There are 2 tokens which can be integrated into the parameter string to be passed:
• $(FILENAME): Returns the file name of the document.
• $(MetaData:<PropertyName>): Returns certain SAP metadata whose name has been specified.
Possible values for <PropertyName> are:
AUTHORIZATIONGROUP, CADKZ, CHANGENUMBER, CONV_STATUS, DELETEFLAG, DELFL, DESCRIPTION, DIRTY, FAMILY, HASMATERIAL, HASMULTIMATLINK,
HASNONMASTER, HASREFERENCE, HNV, HRV, ISASSEMBLY, MASTER, MASTER_FILENAME, NUMBER, OFFICE, PART, REVLEVEL, STATUS, STRUCT, SUBTYPE,
TYPE, USER, USERDEFINED1, USERDEFINED2, USERDEFINED3, USERDEFINED4, VERSION.
Examples:
plm.execute.additional.SLE.SEA.BeforeCheckIn.parameter1 = -File
plm.execute.additional.SLE.SEA.BeforeCheckIn.parameter2 = $(FILENAME)
plm.execute.additional.SLE.SEA.BeforeCheckIn.parameter3 = -DType
plm.execute.additional.SLE.SEA.BeforeCheckIn.parameter4 = $(MetaData:SUBTYPE)
NOTES:
• The DType can be queried with "$(MetaData:SUBTYPE)".
• For executables and PowerShell calls, the parameters can also be given as arguments (only the parameter values).
Values: See "Description"!
Default value: ---
Parameter: plm.loadoptions.versionConflictResolveMode.SLE
Resolves version conflicts when multiple versions of the same DIR are required.
Description: NOTES:
• Only works when filenames include versions!
• Use "auto" if the file name contains version numbers and the loading option "As last saved" is used!
"highest_in_structure" = Only the highest versions are loaded.
Values: "all" = Always load all versions for all documents.
"auto" = Load only necessary versions.
Default value: auto
Parameter: plm.control.partnameRules.resolveInSap.SLE
Activation of FileLookUp for Import on Demand.
Description:
IMPORTANT:
Do not change this parameter unless you are advised otherwise!
"true" = FileLookUp is activated
Values:
"false" = FileLookUp is deactivated
Default value: true
Parameter: plm.options.checkIn.UpdateAttributesFromSAP.SLE
Description: During Save, update attributes of documents to check in from SAP before transferring them to SAP.
"true" = Update attributes before save
Values:
"false" = Do not update attributes before save

Parameter: plm.document.AS.Selection.SLE
Controls the context menu function "Selection" in the Application Structure if the preference "plm.structure.application.CollectEntries.SLE" is set to the
value "true".
Description:
NOTE:
This setting can be achieved in the ECTR preferences for Solid Edge under "Application Structure" as preference "Selection Application Structure -> CAD".
"true" = The first occurrence on the layer is selected.
Values:
"false" = All occurrences on the layer are selected.
Default value: true
Parameter: plm.document.AS.Selection.ScrollTo.SLE
Controls the context menu function "Selection" for assemblies in the Application Structure. Scrolls in the PathFinder to the selection.
Description: NOTE:
These settings can be reached in the ECTR preferences for Solid Edge under "Application Structure" as preference "Scroll to selection: Application Structure
-> CAD".
"true" = Scrolls in the PathFinder to the selection.
Values:
"false" = Do not scroll to the selection in the PathFinder. The selection may be outside the visible area.
Parameter: plm.structure.application.CollectEntries.SLE
Determines whether multiple installed components are displayed individually or combined on one level in the Application Structure of the ECTR.
ATTENTION:
Single parts, sheet metal parts, welded parts (pwd) and assembly families ("plm.document.FOA.Handling.SLE" = 0) are always displayed together.
Description:
NOTE:
These settings can be reached in the ECTR preferences for Solid Edge under "Application Structure" as preference "Collect Entries?".
"collectNone" = No summary. Each instance is presented individually.
Values:
"collectAll" = Summarize all instances. Display only one node with the total number.
Default value: collectNone
Parameter: plm.structure.application.init.strategy.levels.SLE
Number of levels to be displayed in the application structure of the ECTR.
Description: NOTE:
These settings can be achieved in the ECTR preferences for Solid Edge under "Application Structure" as preference "Number of levels which should be
submitted to application structure".
'1' - n = Number of levels to be displayed.
Values:
"all" = Display all layers.
Default value: 1
Parameter: plm.options.ImportOnDemand.DeleteOriginals.SLE
Description: Specifies whether the original CAD files are to be deleted after successful import on demand.
"true" = Delete CAD files
Values:
"false" = Do not delete CAD files
Parameter: plm.options.ImportOnDemand.CheckInAfterCreate.SLE
Description: Determines whether documents should be checked in after successful import.
"true" = Documents are checked in
Values:
"false" = Documents won't check in
Default value: true
Parameter: plm.docstructure.instdata.attr.namepattern.SLE
Determines whether and how the CATEGORY field for component attributes is filled.
Regular expression pattern to define the parts of instance property names used as category and name. The expression must contain two capture groups
named "category" and "fieldname".
Example:
Description: Expression: (?<category>.*)-(?<fieldname>.*)
Property: STPO-POSNR => CATEGORY = STPO | NAME = POSNR
ATTENTION:
ECTR version 5.2.6.0 or higher for real components and ECTR version 5.2.7.0 or higher for virtual components is required to use this preference!
Values: Regular expression
Default value: (?<category>.*)-(?<fieldname>.*)
Parameter: plm.options.CreateDirDuringMakeDrawingOrAssemblyFromPartOrAssembly.SLE
Determines whether an "Import on demand" should be performed during the action "Create Drawing / Assembly from Assembly / Part" or whether a "Create
Description:
DIS" dialog should be displayed.
'0' = Use Import on demand
Values: '1' = Use "Create DIR" dialog with drawing as master DIR
'2' = Use "Create DIR" dialog with drawing as dependent document
Default value: 0
Parameter: plm.options.SapSaveAsNewDocumentForCadSaveAs.SLE
Description: Specifies whether the command "Save as..." in CAD can optionally be enabled to save as a new document in SAP.
'0' = Never save as new document, use CAD behavior
Values: '1' = Always save as new document
'2' = Ask user
Default value: 0

Parameter: plm.options.SapSaveAsNewDocumentForCadSaveCopyAs.SLE
Description: Determines whether the "SaveCopyAs..." command in CAD can optionally be used to save as a new document in SAP.
'0' = Never save as new document, use CAD behavior
Values: '1' = Always save as new document
'2' = Ask user
Default value: 0
Parameter: plm.options.Logging.LogPerformanceTrace.SLE
Description: Decides whether to create a log file with performance traces in the ECTR log directory for the interface.
"true" = Log performance traces
Values:
"false = No logging of performance traces
Parameter: plm.options.checkForUpdates.before.CheckoutEdit.MultiLevel.SLE
Determines whether the complete structure or only the directly referenced documents should be checked using CheckForUpdates before a CheckoutEdit
Description:
action.
"true" = The complete structure will be checked
Values:
"false" = Only the directly referenced documents are checked
Default value: true
Parameter: plm.options.checkForUpdates.before.CheckoutEdit.ExplosionScenario.SLE
Description: When using the MultiLevel-CheckForUpdate, this preference can be used to specify an explosion scenario that can be customized using CDESK_CUS.
Values: Explosion scenario according to the values possible in CDESK_CUS
Default value: CAD_LOAD
Parameter: plm.options.SaveAsNewDocument.CancelSourceFile.SLE
Description: This parameter controls whether the source document is to be cancelled in case of a "SaveAsNewDocument".
"true" = Cancel source document.
Values:
"false = Do not cancel source document.
Default value: true
Parameter: plm.document.ExcelAsAdditionalFileForDrawings.SLE
Decides whether an Excel parameter file is considered an additional file or as own DIR.
If the value is "true", the search path in the "LinkMgmt.txt" file may have to be adjusted in Solid Edge:
Description: BEGIN SEARCH PATH
..
..\..
END SEARCH PATH
"true" = Additional file.
Values:
"false" = Own DIR.
plm.document.BMPAsAdditionalFile.SLE
plm.document.PNGAsAdditionalFile.SLE
Parameter:
plm.document.JPGAsAdditionalFile.SLE
plm.document.TIFAsAdditionalFile.SLE
Decides whether a BMP, PNG, JPG or TIF file is considered an additional format file or is given its own DIS.
If the value is "true", the search path in the "LinkMgmt.txt" file may have to be adjusted in Solid Edge:
Description: BEGIN SEARCH PATH
..
..\..
END SEARCH PATH
"true" = Additional file.
Values:
"false" = Own DIR.
Parameter: plm.options.MissingReferenceReloadOption.SLE
Description: Define behavior if Solid Edge notices a missing component file when loading an assembly.
'0' = Use Solid Edge behavior.
'1' = Load component from SAP automatically.
'2' = Ask user to load the missing component from SAP.
Values:
ATTENTION:
If the option is set to value 1 or 2, the assembly document will be dirty after loading it.
Default value: 0
Parameter: plm.loadoptions.SLE.ShowCADOpenDialog.Extensions
Description: The Solid Edge "Open File" dialog should be displayed for the file extensions specified here.
Values: List of file extensions in the form ".xyz", separated by ';'. If the parameter remains empty, this applies to all file extensions.
Default value: <Empty>
Parameter: plm.options.StructureAnalysis.MinimumErrorLevel.SLE
Description: Defines the minimum error level for problems to be displayed in the error dialog during the structure analysis.
'0' = Never show dialog (not recommended!)
'1' = Display dialog only if errors were found
Values:
'2' = Display dialog if errors or warnings were found
'3' = Always show dialog
Default value: 3
Parameter: sap.bapi.useGuiTransaction

This is an ECTR preference which enables ECTR to call a function module via GUI channel to show SAP Dynpro PopUps.
Description: NOTES:
This parameter is optional.
If it is set here, it overwrites a possibly set value in the file "default.txt" of the ECTR.
List of names of SAP DynPros separated by semicolon.
Values:
Example: /DSCSAG/DOC_CREATE2; /DSCSAG/DOC_CREATE_MULTI
Default value: --
Parameter: plm.structure.application.DisplayAdditionalAttributes.SLE
Determines whether additional file properties should be displayed in the application structure.
Description:
NOTE:
"true" = Show additional file properties
Values:
"false" = Don't show additional file properties
Default value: --
Parameter: plm.structure.application.AdditionalAttributes.SLE
Defines which file properties should be displayed in the application structure.
Description:
NOTE:
List of file properties to display, separated by semicolon.
Values:
Example: Prop1;Prop2;Display Name;SAP_CC_NAME
Default value: --
Parameter: plm.options.MechanicalModeling.UpdateMaterial.MaterialLibrary.SLE
Specifies a custom Solid Edge material library when assigning a Solid Edge material for a model from SAP.
Description: NOTES:
• This setting only has an effect if no value for the property "MM-MaterialLibrary" is transferred from SAP!
• If no material library is specified, the integration searches for the material in the standard material libraries of Solid Edge!
Value: Name of the material library to be used.
Default value: CustomMaterialLibrary
Parameter: plm.document.FOA.ReplaceInAllMembers.SLE
Description: Defines whether the context menu function "Replace Component" should be offered for FOA components on the first level.
"true" = Function is offered.
Values:
"false" = Function is not available.
Parameter: plm.structure.application.ExpandDocumentsOnlyOnce.SLE
Defines whether only the first occurrence of a document node should be expanded in the application structure view of the ECTR. Further occurrences of
Description:
this document will then not be expanded automatically.
"true" = Expand the same document only once.
Values:
"false" = Expand each occurrence of the same document.
Parameter: plm.structure.application.UsePlmObjectContent.SLE
Specifies whether "PlmObjectContent" or "GenericContentObject" should be used for virtual component nodes. This controls whether virtual components
linked to materials should be displayed as SAP objects (in the case material) ("true").
Description:
NOTE:
Setting this parameter to "true" requires ECTR version 5.1.12.12.0 or higher!
"true" = Use "PlmObjectContent" for virtual components.
Values:
"false" = Use "GenericContentObject" for virtual components.
plm.structure.node.CUAPOB_SLE_VIRTUAL.icon.1 = structure/flag/state/$(ANY_MODIFIED)/SLE
plm.structure.node.CUAPOB_SLE_VIRTUAL.icon.2 = structure/flag/state/$(STATE)SLE
Parameter:
plm.structure.node.CUAPOB_SLE_VIRTUAL_NEW.icon.1 = structure/flag/state/$(ANY_MODIFIED)/SLE
plm.structure.node.CUAPOB_SLE_VIRTUAL_NEW.icon.2 = structure/flag/state/$(STATE)/SLE
Description: Specifies the icon mapping depending on the status flags for each possible value of POS_TYPE.
Values: Mapping path for the respective icon.
Default value: See under Parameter!
Parameter: plm.structure.application.DisplayPosItem.SLE
Description: Specifies whether virtual components should be displayed below the corresponding node in the application structure tree.
"true" = Display virtual components.
Values:
"false" = Do not display virtual components.
Default value: true
Parameter: plm.options.Cancel.LoadedParts.SLE
The interface makes the parts loaded in the CAD available to the ECTR during cancel. This costs time and is not absolutely necessary for the action
"Cancel". It is therefore possible to choose whether only the parts of the active document should be transferred or no parts at all. This can increase the
performance, but only for very large assemblies.
Description:
ATTENTION:
Changing this preference should only be done after prior consultation! In case of doubt, the default value '0' should be retained.

'0' = Provide all loaded parts.
Values: '1' = Provide only the parts of the active document.
'2' = Do not provide any loaded parts.
Default value: 0
Parameter: plm.options.Save.LoadedParts.SLE
The interface makes the parts loaded in the CAD available to the ECTR during save. This costs time and is not absolutely necessary for the action
"Save". It is therefore possible to choose whether only the parts of the active document should be transferred or no parts at all. This can increase the
performance, but only for very large assemblies.
Description:
ATTENTION:
Changing this preference should only be done after prior consultation! In case of doubt, the default value '0' should be retained.
'0' = Provide all loaded parts.
Values: '1' = Provide only the parts of the active document.
'2' = Do not provide any loaded parts.
Default value: 0
Parameter: plm.options.SaveAs.CheckInAfterCreate.SLE
Description: Decides whether documents should be checked in after a new version or a new document has been created.
"true" = Documents are checked in.
Values:
"false" = Documents remain checked out.
Parameter: plm.options.InPlaceActivated.CheckOutDocument.SLE
When a part is opened with "Edit-in-Place" ("InPlaceActivated" command, "Edit" in Pathfinder) from a Solid Edge assembly, this assembly can be
Description:
checked out automatically.
'0' = No, do not check out the assembly.
Values: '1' = Yes, check out the assembly.
'2' = Ask user.
Default value: 0
Parameter: plm.options.MaintainGeneric.DeleteMissingMember.SLE
Determines whether to delete MaintainGeneric for FOA and FOP that are no longer transferred when saved.
Description:
ATTENTION:
This preference is available from ECTR version 5.2.6.0!
"true" = Delete
Values:
"false" = Do not delete
Parameter: plm.options.Save.UseDocumentPropertiesAsRequestedComponentAttributes.SLE
The value for non-existent component attributes referenced in "bod_mapping_section" in the DType definition in the "dtype.xml" file is taken from the
document properties. Only properties included in the "bod_mapping_section" in the DType definition are taken from the document properties. Which
document properties are available is controlled by the preference plm.options.deliverOnlyRequestedAttributesToSAP.SLE.
Note:
Description: More information about the configuration in the configuration files "dtype.xml" and "attributes-to-sap.xml" can be found in chapter "Adopt component
attributes"!
ATTENTION:
• If the value is set to "true", this can reduce the performance!
• This functionality is available from ECTR version 5.2.6.1 or S/4 1.1.6.1!
• Supersedes the parameter plm.options.TransferPropertiesTo.DMUTMX_META.SLW. This should not be used anymore!
"true" = Uses the document property if the component attribute is not present.
Values:
"false" = Do not use document properties as component attributes.
Parameter: plm.options.Cancel.DialogDefaultValue.SLE
Description: Determines which option is selected by default in the dialog "Cancel edit and discard work".
'0' = Reload original from SAP
Values:
'1' = Close original in CAD
Default value: 0
Problems with FOA handling and AdvancedBOM
There may be problems with FOA handling and AdvancedBOM derivation because users often do not insert a
part in an FOA member, but prefer to replace it, as this is faster for them. In this case, the data in the DMU
tables in SAP is no longer sufficient for correct mapping. As a result, not only is a different shoring state
displayed, but the Occurrences are also different. To counteract this, the number and names of the FOA
members in which an Occurrence is installed can be stored in the SAP table DMUTMX_META. This is done in the
SAP table DMUTMX_META according to the following scheme:
SE_MEMBER_COUNT = n (Number of member)

SE_MEMBER_NAME_1 = Membername1

SE_MEMBER_NAME_2 = Membername2
...
SE_MEMBER_NAME_n = MembernameN
This information can be used for the material BOM derivation process. However, this requires a customer-
specific extension of the AdvancedBOM process, as this is not an SAP standard functionality!
To enable this functionality, in the configuration file "default.txt" the

parameter plm.document.FOA.Handling.SLE must be set to the value '2'!
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 Solid
Edge contains definitions and settings for document types supported by Solid Edge.
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 Solid Edge are described here.
DType definitions for Solid Edge
With the installation of the SAP Engineering Control Center interface to Solid Edge 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
Nonmaster document definitions
The correlation of the DType definitions as well as their dependencies is shown in the following table:
Overview about DType definitions for Solid Edge
DType-ID Type App type Description

------------------------------------------------------------------------------------------------------
DEFLT Template Base template from SAP/DSC
| +- SLEMDL Template SLE Base template for 3D documents (SEA, SEP, SES, SEW)
| | +- SEP Master SLE 3D Part
| | +- SES Master SLE Sheet Metal
| | +- SEW Master SLE Weldment
| | +- SEA Master SLE 3D Assembly
| | +- SEM Master SLE Family of Assmebly Member: Dummy file created by the integration
| +- SLEDRW Template SLE Base template for "2D" documents (SED/SDM)
| +- SED NonMaster SLE Drawings as NonMaster - Dependent Document
| +- SEDM Master SLE Drawings as Master
TXLS Template Base template from SAP/DSC
| +- SXLS Master SLE Linked Excel files
The following are the descriptions of the individual definitions for Solid Edge documents.
Generic DType definitions
The generic definitions are templates with basic definitions that are valid for all Solid Edge document types.
Templates are integrated in the other DType definitions. Two DType templates are defined for Solid Edge:
"SLESTD" as default template

"SLEMDL" for parts and assemblies
"SLEDRW" for drawings
NOTE:
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.
First, the default template is defined, which defines the basic properties for Solid Edge:
Generic DType definition "SLESTD" for Solid Edge
<DType type="template" identifier="SLESTD" include_template="DEFLT" application_type="SLE"

group="Solid Edge">
...
</DType>
Attributes of the element <DType>

Attribute Value Description

Defines the type of DType definition.
type "template"
"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.
identifier "SLESTD"
"SLESTD" = ID of this template definition.
Determines which template definition is included in this definition.
include_template "DEFLT"
"DEFLT" = The DType template with the ID "DEFLT" from the global "dtype.xml" file is included.
Identifier for the application responsible for this document (workstation application). This application is used to open the file from the
SAP Engineering Control Center.
application_type "SLE"
"SLE" = For Solid Edge this is the workstation application (WSAppl).
Defines the group membership for master documents. The group membership is used to organize the DTypes in the dialog "Create
document".
group "Solid Edge"
"Solid Edge" = Document belongs to this group.
The <program_options> subelement contains various settings that control the behavior of the document in the
Attributes of the subelement <program_options>

Determines whether this DType is visible in the combo box of the
available document types in the "Create Document" dialog.
show_for_create "yes"
"yes" = Document is visible.
Defines whether the document is a normal document with
original and assigned workstation application or a container
object for additional originals without explicit original.
has_primary_application "yes"
"yes" = The document has an original with assigned workstation
application.
Determines whether the newly created document has a dirty
flag.
dirty_flag "yes"
"yes" = The document has a dirty flag.
Defines whether a status change is performed by the SAP
Engineering Control Center during check-in or whether the SAP
attempt_status_change_on_checkin "yes" system performs a status change.
"yes" = Status change by SAP Engineering Control Center.

Switches the automatic adjustment of the "application role" in
RES4 in SAP on or off.
auto_adjust_application_role "no"
"no" = No automatic adjustment.
The subelement <copy_as> defines how the document behaves during a "CopyAs" action and how the SAP
Engineering Control Center reacts to this document.
Attributes of subelement <copy_as> of subelement <program_options>

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

Determines which additional originals in the document are not transferred to the
copy of the document during copying by means of a semicolon-separated list of
ignore_wsappl_list "ZIP" identifiers for the workstation application of the additional originals.
"ZIP" = Additional originals of type "ZIP" (ZIP archive) are not copied.
Determines whether the version number of the copy should be set to that of the
original or to the initial value (usually "00").
use_initial_version "yes"
"yes" = Set the version number of the copy to the initial value.
Determines whether the assigned material is also copied when the master
document is copied.
copy_material "no"
"no" = Do not copy assigned material.
Determines whether the dirty flag is removed from the copy.
remove_dirty_flag "no"
"no" = do not remove dirty flag.
The <new_version> subelement contains settings for the versioning of documents.
Attributes of subelement <new_version> of subelement <program_options>

Determines for which document statuses, the versioning of a document
is allowed. You can specify a list of document statuses separated by ';'.
status_list "AC;RE;RR"
"AC;RE;RR" = With this document status, new versions are allowed.
Determines which additional originals in the document are not
transferred to the new version of the document during versioning,
using a semicolon-separated list of identifiers for the workstation
ignore_wsappl_list "ZIP"
application of the additional originals.
"ZIP" = Additional originals of this type are not copied.

Defines which dependent documents are omitted when the master
document is versioned. The dependent documents to be ignored are
ignore_nm_dtype_list "" specified as a semicolon-separated list of DTypes.
"" = No document types to be ignored defined.

Determines whether the original file name should be assigned
according to the part rules for this DType or whether the previous file
rename_master_original "no" name should be kept unchanged.
"no" = Keep file name unchanged.

Determines whether the dirty flag is removed in the new version.
remove_dirty_flag "no"
"no" = Do not remove dirty flag.
The subelement <document_create> contains settings that control how a new document is created in SAP.
Attributes of the subelement <document_create>

Determines whether the SAP GUI should
be opened to create a document.
create_with_SAP_GUI "no"
"no" = Do not open SAP GUI.

Defines whether mass creation is allowed
for the document.
create_multi_allowed "no"
"no" = No mass creation allowed for this
document.
Defines the document number
assignment in SAP.
document_number_assignment "internal"
"internal" = SAP automatically assigns the
number itself.
With internal number assignment
(document_number_assignment), the
value in this field has no meaning. With
external number assignment, this value is
initial_document_number "*" entered as a prefix in the input field of the
document creation dialog.
"*" = No opinion due to internal number

assignment.
SAP document type for the newly created
document.
document_type "SEA"
"SEA" = SAP document type.
Defines the initial value of the part
number for documents.
initial_document_part "000"
"000" = Intial value of the document part
number.
Defines whether the default value in the
document creation dialog of the SAP
Engineering Control Center or the
selected SAP part document can be
part_editable "yes"
changed from the attribute
"initial_document_part" in the input field.
"yes" = Default value can be changed.

Defines the initial value of the version
number.
initial_document_version "00"
"00" = Intial value of the version number.
Defines whether the default value for the
document version can be changed in the
document creation dialog of the SAP
version_editable "yes"
"yes" = Default value can be changed.

Here you can define the initial status of a
newly created document.
change_to_after_create_status "AC"
"AC" = Identification of the initial status.

Determines how the file name for the
original document is composed. The
following placeholders are possible:
$(DOCNUMBER) for the document
number, $(DOCTYPE) for the document
type and $(DOCPART) for the document
filename_template_base "$(DOCNUMBER)$(DOCTYPE)$(DOCPART)"
part.
"$(DOCNUMBER)$(DOCTYPE)$(DOCPART)"
= The file name consists of document
number, document type and part
document.
Specifies whether the document version
should be appended to the file name for
the original on this document (usually
"_$(DOCVERSION)").
filename_template_version "" "" = No version in the file name.
ATTENTION:
It is strongly discouraged to use this
option as it may cause errors, so it should
be left empty!
Shows or hides the classification panel in
the document creation dialog.
show_classification_pane "yes"
"yes" = Show classification panel in the
document creation dialog.
The <material_create> subelement contains settings for creating a material for a new document.
Attributes of the subelement <material_create>

Determines whether and how a material is created for a new
document.
material_creation_method "deferred"
"deferred" = No material is created for the document. It is
possible to create a material for this document at a later date.
Defines the material number assignment in the SAP system. The
values are identical to those of document number assignment.
material_number_assignment "internal"
"internal" = The SAP system assigns the number automatically.
Material type or a ';'-separated list of material types for the new
material to be created.
material_type "FERT;HALB"
"FERT;HALB" = List of SAP material types.
Template material with which the material creation is
performed.
material_template ""
"" = No material template specified.
Initial value for the assigned work.
material_plant_assignment ""
"" = No initial work assigned.

Specifies the default class for the material.
material_default_class ""
"" = No standard class for the material.
The sub-element <primary_application> determines which application is responsible for this master document
(primary application) and defines the rules for checking the originals in and out.
Attributes of the subelement <primary_application>

Defines whether an attribute update should occur when the dirty flag is
set.
update_attributes_for_dirty "yes"
"yes" = perform attribute update.
Defines the attribute update in the "Open for editing" action.
update_attributes_for_rw "yes"
"yes" = Perform attribute update.
Defines the attribute update for the action "Open read-only".
update_attributes_for_ro "no"
"no" = Do not perform an attribute update.
The subelement <container_file> defines the properties of the ZIP archive, which is stored in the document as
a container file. It contains the subelement <plmfile>, which defines the properties of the container file.
Attributes of subelement <plmfile> of subelement <container_file> of <primary_application>

Filters for file name extensions in the file system.
extension "ecf"
"ecf" = File name extension.
Filters originals on the document by the workstation
application.
workstation_application "ECF"
"ECF" = Identification of the workstation application.
Filters originals on the document according to their description.
description "ECtr container file"
"ECtr container file" = Description for originals to be filtered
by.
The <checkout_rules> subelement determines how the original document is handled during check-out.
Attributes of subelement <checkout_rules> of subelement <primary_application>

Defines whether the "Open for editing" function could provide
the files in the Session directory for all referenced components.
check_references_on_edit "yes" Check is performed during the. If not, the action is aborted.
"yes" = Perform check.

Defines whether the original is renamed when opened
according to the rules for part names.
rename_master_original_at_checkout "no"
"no" = Keep file name of the original when opening.

Defines whether only one version of this document may be
stored in the session directory.
one_version_in_session_only "no"
"no" = Multiple versions of the document in the session
directory allowed.
Defines whether a hard link can be used for the original
document in the Session directory or whether a copy must
hardlink_in_session "no" always be created.
"no" = Always create a copy.
The subelement <checkout_direct> defines which of the originals stored directly on the document are
transferred to the Additional directory when the "Open for editing" action is performed on the original.
Attributes of subelement <plmfile> of subelement <checkout_direct> of subelement <checkout_rules> of subelement

<primary_application>
Identification of the workstation application of the file type to be transferred
to the Additional directory.
workstation_application "XLS"
"XLS" = identifier of the workstation application.
The subelement <checkin_rules> determines how files in the Additional directory and originals on the
document are handled during check-in. It contains several subelements for this purpose.
Attributes of the subelement <checkin_rules> of <primary_application>

Attribut Value Description
"yes" = Prevents a document without CAD from being checked in via the
from_application_only "yes"
context menu in the ECTR desktop view.
The <ignore> subelement defines which files are ignored when saving. For this purpose, it contains the
<plmfile> subelement several times, which defines the additional file types to be ignored.
Attributes of the <plmfile> subelements of the <ignore> subelement of <checkin_rules>.

The respective file name extensions of the additional file
types to be ignored in the file system.
extension "bak", "xml", "tmp"
"bak", "xml", "tmp" = File name extensions of the additional
file types.
Filters by file name using regular expressions.
filename_pattern "VEConverterResponse\.xml"
"VEConverterResponse\.xml" = Filter mask.
The <delete_in_sap> subelement defines which originals on the document are deleted when checking in. This
allows a targeted cleanup of the document. It contains the subelement <plmfile> which defines the additional
file types to be deleted.
Attributes of subelements <plmfile> of subelement <delete_in_sap> of <checkin_rules>


Workstation application identifiers for the individual
additional formats.
workstation_application "EPG", "EPJ", "JT", "XLS"
"EPG", "EPJ", "JT", "XLS" = Workstation application
identifiers.
The subelement <delete_in_session> defines which files are deleted during check-in. It contains the
subelement <plmfile> which defines the additional file types to be deleted.
Attributes of subelements <plmfile> of subelement <delete_in_session> of <checkin_rules>

The file name extensions of the files to be deleted in the file
system.
"jpg", "gif", "jt", "pdf", "rh",
extension
"vds"
"jpg", "gif", "jt", "pdf", "rh", "vds" = File name extensions of the
additional file types.
The subelement <additional_files> defines, determines which additional formats of a document can be
displayed and edited in the SAP Engineering Control Center.
Attribute of the subelement <additional_files>

Determines whether additional originals are allowed for this document.
enable_additional_files "yes"
"yes" = Additional originals are permitted.
The subelement <view_files> determines for which of the additional originals displayed in the original
container, no processing can be performed on the document. These originals can only be displayed. For this
purpose, it contains subelements of the type <plmfile>, which define the individual document types.
Attributes of subelements <plmfile> of subelement <view_files> of <additional_files>

The identifier of the document type that cannot be edited.
workstation_application "XLS"
"XLS", = Identifier of the document type.
The subelement <ignore_files> defines which of the additional originals on the document are NOT displayed in
the original container of a document in SAP Engineering Control Center. For this purpose, it contains
subelements of the type <plmfile>, which define the individual document types.
Attributes of subelements <plmfile> of subelement <ignore_files> of <additional_files>

The identifiers of the document types that should not be
displayed.
workstation_application "EPJ", "EPG", "JT"
"EPJ", "EPG", "JT" = Identifiers of the document types.
The <store_files> subelement defines the assignment of the originals to the workstation application when
adding auxiliary files (neutral formats) to a document. The additional files can be added by Drag & Drop or
menu function.
Attributes of the subelement <store_files>

Filters by file name for JPEG files using regular expressions.
filename_pattern ".*\.preview\.jpg"
".*\.preview\.jpg" = Filter mask for JPEG files.
"gif",
"pdf",
The file extensions of the respective additional files (neutral
extension "jt",
formats).
"txt",
"xls"
"EPG",
"PDF",
The identifiers of the document types of the respective
workstation_application "JT",
additional files (neutral formats).
"TXT",
"XLS"
"ECTR Preview (jpeg)",
"ECTR Preview (gif)",
"$(FILENAME)", The descriptions of the respective additional files (neutral
description
"3D Preview JT", formats).
"$(FILENAME)",
"Excel files"
Second, we will explain the definition for parts and assemblies:
Generic DType definition for Solid Edge parts and assemblies
<DType type="template" identifier="SLEMDL" include_template="SLESTD" application_type="SLE"

group="Solid Edge">
...
</DType>
Attribute of the element <DType>

Determines the type of DType definition.
type "template"
Non-ambiguous ID string for this DType definition within the entire XML
document. The ID must be between one to five characters long.
identifier "SLEMDL"
"SLEMDL" = ID of this template definition.
Determines which template definition should be integrated into this
definition.
include_template "SLESTD"
"SLESTD" = The DType template with ID "SLESTD" from this "dtype.xml" file
is included.
Designates the application that is relevant for this document (Workstation
Applikation). This application opens the file from SAP Engineering Control
application_type "SLE" Center.
"SLE" = This is the Workstation Application for (WSAppl) for Solid Edge.
Defines the group designation for master documents. The group designation
helps to organize DTypes within the dialog "Create document".
group "Solid Edge"

The sub-element <program_options> contains different settings, which control the behavior of the document
in the SAP Engineering Control Center.
Attributes of the <program_options> sub-element

Sets the Function Group to which the document belongs. For
documents with a common Function Group, for example, specific
function_group "DOC_SLEMDL" context menus can be defined.
"DOC_SLEMDL" = Identifier of the Function Group.

Name of a section in the attribute mapping file that is defined in
customer-specific data. The data will be displayed in the object
customer_data_section "SLEMDL" browser of ECTR under the tab "Customer data".
"SLEMDL" = Name of section.
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.
Attributes of the sub-element <primary_application>

"SEA" = Identification of the SAP workstation application for the
primary_workstation_application "SEA"
original.
Name of the section within the Attribute Mapping File in which
attribute exchanges between SAP and the application (Solid
attribute_section "SLEMDL" Edge) are defined.
"SLEMDL" = Name of section within the Attribute Mapping file.
The sub-element <checkout_rules> determines how to treat the original of the document at checkout.
Attributes of the <checkout_rules> sub-element from the <primary_application> sub-element

Determines whether a structure resolution is performed when opening a document.
read_structure "flag"
"flag" = If the "Structure" flag is set, perform structure resolution.
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>

"yes" = Prevents a document from being checked in without CAD in the
from_application_only "yes"
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> inherited from the sub-element <save_direct> from <checkin_rules>

"jpg",
"xlsx", The respective file name extensions of additional files in the
"gif", file system.
extension "jt",
"pdf", "jpg", "xlsx", "gif", "jt", "pdf", "rh", "dxf"= The respective
"rh", file name extensions.
"dxf"
"EPJ",
"XLS",
"EPG", Workstation application identifiers for each additional
"JT", format.
workstation_application "PDF",
"RHM", "EPJ", "XLS", "EPG", "JT", "PDF", "RHM", "RHM", "RH",
"RHM", "ACD" = Identification of the document types.
"RH",
"ACD"
"Preview (jpeg)",
"Excel",
"Preview (gif)", Description of each respective additional file.
"3D Preview",
description "PDF", "Preview (jpeg)", "Excel", "Preview (gif)", "3D Preview",
"Monolithic RH", "PDF", "Monolithic RH", "Monolithic VDS", "$(FILENAME)",
"Monolithic VDS", "flat pattern" = Description of the additional files.
"$(FILENAME)",
"flat pattern"
Filters by file names and regular expressions.
".*_mono\.rh",
filename_pattern
".*_mono\.vds"
".*_mono\.rh", ".*_mono\.vds" = Filter masks.
The sub-element <scripts> contains scripts that are executed before checking in. Individual scripts are
included in the sub-element <script>.
Attributes of the sub-element <script> of the sub-element <scripts> from <checkin_rules>

Sets the entire call path of the script to run.
"@PLM_INSTDIR@\basis\sys\win\bin\VEConverter.bat" = script
call path "VEConverter.bat".
name "@PLM_INSTDIR@\basis\sys\win\bin\VEConverter.bat"
ATTENTION:
For ECTR versions older than version 5.1.12 the default call
path is
"@PLM_INSTDIR@\customize\exec\win\addutils\VEConverter.bat"!
<script> contains the sub-element <params>, which determins parameters to be passed to the running
script. For this purpose, it includes one or more sub-elements <param>, each of which defines a parameter.
Attributes of the sub-elements <param>, sub-element <params>, sub-element <script>, sub-element <scripts> from
<checkin_rules>

"convertfile", "$(masterfile)",
"--output-directory", "$(add_dir)",
"--output-format", "VDS" (for Visual Enterprise < 9.0: "RH"!),
"--sap-identifier", Contains the name of each
"DOCUMENT=$(doc_type)*$(doc_nr)*$(doc_part)*$(doc_vr)", parameter defined. This partly
Name
"--sap-metadata", "DOCTYPE=$(doc_type)", contain variable data in the form of
"--sap-metadata", "DOCNUMBER=$(doc_nr)", placeholders ("$ (...)").
"--sap-metadata", "DOCPART=$(doc_part)",
"--sap-metadata", "DOCVERSION=$(doc_vr)",
"--import-setting", "LoadExternalFiles=false"
The sub-element <allowed_nonmaster> determines the type of document (Nonmaster document) that is
accepted as a dependent document.
Attribute of the sub-element <allowed_nonmaster>

The unique ID of the DType definition of the dependent document.
"SED",
DType
"VWINM"
"SED", "VWINM" = DTypes of the allowed dependent documents.
Allowable number of dependent documents for this master document.
"99",
max_count
"99"
"99" = Maximum possible number of dependent documents for this document type.
Below, you can find the definition of the templates for the DType definition of Drawings:
Generic DType definition for Solid Edge drawings
<DType type="template" identifier="SLEDRW" include_template="SLESTD" application_type="SLE"

group="Solid Edge">
...
</DType>
Attributes of the <DType> element

Determines the type of DType definition.
type "template"
document. The ID has to be between one to five characters long.
identifier "SLEDRW"
"SLEDRW" = ID of this template definition.
definition.
include_template "SLESTD"
"SLESTD" = The DType template with ID "SLESTD" from this "dtype.xml" file
is included.
Application). This application opens the file from SAP Engineering Control
"SLE" = This is the Workstation Application (WSAppl) for Solid Edge.

Defines the group designation for master documents. The group designation
helps to organize DTypes within the dialog "Create document".
group "Solid Edge"
The sub-element <program_options> contains different settings, which control the behavior of the document
in the SAP Engineering Control Center.
Attributes of the <program_options> sub-element

Sets the Function Group to which the document belongs. For
documents with a common Function Group, for example, specific
function_group "DOC_SLEDRW" context menus can be defined.
"DOC_SLEDRW" = Identifier of the function group.

Name of a section in the attribute mapping file that is defined in
customer-specific data. The data is displayed in the Object Browser
customer_data_section "SLEDRW" ECTR under the tab"Customer information".
"SLEDRW" = Name of the section.
(primary application) and defines the rules for the check in and check out of originals.
Attribute of the sub-element <primary_application>

"SED" = Identification of the SAP Workstation Application for the
primary_workstation_application "SED"
original.
Name of a section within the Attribute Mapping File, in which
attribute exchanges between SAP and the application (Solid
attribute_section "SLEDRW" Edge) are defined.
"SLEDRW" = Name of the section in the Attribute Mapping File.
The sub-element <checkout_rules> determines how to treat the original of the document at checkout.
Attribute of the <checkout_rules> sub-element from the <primary_application> sub-element

Determines whether a structure resolution is performed when opening a document.
read_structure "flag"
"flag" = If the "Structure" flag is set, perform structure resolution.
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.
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> inherited from the sub-element <save_direct> from <checkin_rules>

"jpg", The respective file name extensions of additional files in the file
"gif", system.
extension
"pdf",
"xlsx" "jpg", "gif", "pdf", "xlsx" = Each file name extension.
"EPJ", Identification of the Workstation application for the individual
"EPG", additional formats.
workstation_application
"PDF",
"XLS" "EPJ", "EPG", "PDF", "XLS" = Identification of the document types.
"Preview (jpeg)", Description of the respective additional file.
"Preview (gif)",
description
"PDF", "Preview (jpeg)", "Preview (gif)", "PDF", "Excel" = Identification of
"Excel" additional file types.
The DType definitions 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. The DType definition of master
documents is divided into the DType definitions for assemblies ("SEA"), parts ("SEP"), drawings ("SEDM"),
sheet metal parts "SES") and weldment assemblies ("SEW").
NOTE:
DType definition for master documents of type "SEA" for Solid Edge
<DType type="master" identifier="SEA" include_template="SLEMDL" application_type="SLE"

application_role="A">
...
</DType>
Attributes of the element <DType> of the definition "SEA

type "master"
"master" = This is a DType definition for master documents.
Unique ID string of this DType definition throughout the XML document. The ID
must be one to five characters long.
identifier "SEA"
"SEA " = ID of this DType definition.
include_template "SLEMDL"
"SLEMDL" = The DType template with the ID "SLWMDL" from this "dtype.xml"
file is included. This is the generic definition.
Identifier for the application responsible for this document (Workstation
Application). This application is used to open the file from the SAP Engineering
application_type "SLE" Control Center.
"SLE" = For Solid Edge, this is the Workstation Application (WSAppl).

This is used to set the object type in the RES4 field of the SAP table DRAW.
application_role "A"
"A" = Identifier of the object type for assemblies.
The <icon> subelement defines an abbreviation that is used to determine the symbol to be used in SAP
Engineering Control Center. It contains the subelement <icondef>.
Attributes of subelement <icondef> of subelement <icon>

Position of the symbol in the document entry in
the tree.
icon_position "1"
"1" = Far left, "6" = Far right.
Identification of a symbol group. Other symbols
can be displayed depending on their status.
icon_group "default"
"default" = This is the default icon.
Path for determining the icon file containing
the symbol to be used for this symbol position.
icon_identifier "{0}/tree/sle/solid_edge_assembly$(FAMILY)"
"{0}/tree/sle/solid_edge_assembly$(FAMILY)" =
The icon file.
SAP Engineering Control Center. It contains the subelement <new_version> which contains settings for
versioning documents.

Determines whether the entire part family group (generic part +
variants) is versioned when the generic part is versioned.
take_instances_for_generic "yes"
"yes" = Version the entire part family group.
The subelement <document_create> determines how the document is created in SAP.

SAP document type for the newly created document.
document_type "SEA"
"SEA" = Solid Edge Assembly document.
The subelement <seedfile> contains settings for the template file. Several template files can be assigned, i.e.
<seedfile> can occur several times. This contains the subelement <description>, which defines description
texts in different languages.
Attributes of the 1st subelement <seedfile> of subelement <document_create>


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

Defines how the original of the document is created.
type "template"
"template" = Via the attribute "filename" the template file to be used is
specified.
This allows you to determine whether this template file is preset in the
"Create Document" dialog.
default "yes"
"yes" = This template file is the default.
Identifier of the template description in the dictionary.
dictionary_identifier "Asm"
"Asm" = Dictionary Identifier.
attributes of the 2nd subelement <seedfile> of subelement <document_create>

The filename attribute is used to specify the template file to be used. You
can select a template file in the Create Document dialog using a file
filename "Asm.asm" selection dialog.
"Asm.asm" = File name of the template file.

Defines 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
type "select" "Create Document" dialog using a file selection dialog.
"select" = A template file can be selected in the "Create Document" dialog.

default "no"
"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
extension_filter "*.asm" filter are offered for selection.
"*.asm" = Filter for the file extension.

Identifier der Beschreibung der Vorlage im Dictionary.
dictionary_identifier "select"
"select" = Dictionary Identifier.

"SEA" = Identification of the SAP workstation application for Solid
primary_workstation_application "SEA"
Edge Assemblies.
The <first_level_files> subelement defines which additional originals in the document are stored next to the
original in the Session directory when checking out. It contains the subelement <plmfile>, which defines which

files these are.
Attributes of the subelement <first_level_files>

The file name extension of the additional originals that are
stored next to the original in the session directory.
extension "cfg"
"cfg" = File name extension.
Identification of the workstation application for the additional
format.
workstation_application "CFG"
"CFG" = Identification of the document type.
Description of the additional file.
"Assembly config
description
file"
"Assembly config file" = Description of the additional files.
The following is a description of the DType definition for Solid Edge FOA documents:
DType definition for master documents of type "SEM" for Solid Edge FOA member documents
<DType type="master" identifier="SEM" include_template="SLEMDL" application_type="SLE"

...
</DType>
Attributes of the element <DType> of the definition "SEM"

type "master"
identifier "SEM"
"SEM" = ID of this DType definition.
"SLEMDL" = The DType template with the ID "SLEMDL" from this "dtype.xml"
file will be included. This is the generic definition.
Application). This application is used to open the file from SAP Engineering
"SLE" = For Solid Edge this is the Workstation Application (WSAppl).



the tree.
icon_position "1"
"1" = far left, "6" = far right.
Identification of a symbol group. Other symbols
can be displayed depending on their status.
Path to determine the icon file containing the
symbol to be used for this symbol position.
icon_identifier {0}/tree/sle/solid_edge_assembly$(FAMILY)"
{0}/tree/sle/solid_edge_assembly$(FAMILY)"
= The icon file.
Attributes of the subelement <program_options>

Determines whether this DType is visible in the combo box of the available
document types in the "Create Document" dialog.
show_for_create "no"
"no" = Not visible.
The subelement <copy_as> contains different settings, which determine how the document behaves during a
"CopyAs".
Attributes of the subelement <copy_as> of <program_options>

Attribut Wert Description
Determines whether a "CopyAs" is allowed for this DType. The setting includes the "Clone"
dialog.
allowed "no"
"no" = "CopyAs" not allowed for this DType.
The subelement <new_version> contains settings for document versioning.

Determines whether the original file name should be assigned according to
the part rules for this DType or whether the previous file name should be
rename_master_original "no" kept unchanged.
"no" = Copy the file name of the previous version unchanged.

document_type "SEM"
"SEM" = Solid Edge Assembly document as FOA member.

Determines whether the file name for the original is renamed during
document creation according to the set naming rules, or whether the file
rename_template_filename "no" name of the original file is transferred unchanged.
"no" = The file name of the original is copied unchanged.
attributes of subelement <seedfile> of subelement <document_create>

The filename attribute is used to specify the template file to be used.
You can select a template file in the Create Document dialog using a
filename "FOA.asm" file selection dialog.
"FOA.asm" = File name of the template file.

Defines 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.
type "select"
"select" = A template file can be selected in the "Create Document"
dialog.
default "no"
Extended filter option to restrict the selection of a template file from
the file system using a Regular Expression ("RegExp").
filename_pattern ".*\.asm![0-z]*"
".*\.asm![0-z]*" = Filter for the template file.

"SEM" = Identification of the SAP workstation application for Solid
primary_workstation_application "SEM"
Edge FOA documents.
The following is a description of the DType definition for Solid Edge Part documents:
DType definition for master documents of type "SEP" for Solid Edge Part documents
<DType type="master" identifier="SEP" include_template="SLEMDL" application_type="SLE"

application_role="P">
...
</DType>

Attributes of the element <DType> of the definition "SEP
type "master"
identifier "SEP"
"SEP" = ID of this DType definition.

application_role "P"
"P" = Identification of the object type for parts.
attributes of subelement <icondef> of subelement <icon>

Position of the symbol in the document entry in the
tree.
icon_position "1"
Identification of a symbol group. Other symbols can
be displayed depending on their status.
Path to determine the icon file containing the symbol
to be used for this symbol position.
icon_identifier "{0}/tree/sle/solid_edge_part$(FAMILY)"
"{0}/tree/sle/solid_edge_part$(FAMILY)" = The icon
file.



document_type "SEP"
"SEP" = Solid Edge part document.

filename "Part.par" selection dialog.
"Part.par" = File name of the template file.

type "template"
specified.
default "yes"
dictionary_identifier "part"
"part" = Dictionary Identifier.
Attributes of the 2nd subelement <seedfile> of subelement <document_create>

can select a template file in the "Create Document" dialog using a file


default "no"
extension_filter "*.par" filter are offered for selection.
"*.par" = Filter for the file extension.

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

"SEP" = Identification of the SAP workstation application for Solid
primary_workstation_application "SEP"
Edge Parts.
The following is a description of the DType definition for Solid Edge Part documents:
DType definition for master documents of type "SEN" for Solid Edge Standard Part documents
<DType type="master" identifier="SEN" include_template="SLEMDL" application_type="SLE"

application_role="N">
...
</DType>
Attributes of the element <DType> of the definition "SEP"

type "master"
identifier "SEN"
"SEN" = ID of this DType definition.

application_role "N"
"N" = Identification of the object type for Standard Parts.

tree.
icon_position "1"

Identification of a symbol group. Other symbols can
be displayed depending on their status.
Path for determining the icon file containing the
icon_identifier "{0}/tree/sle/solid_edge_part$(FAMILY)"
"{0}/tree/sle/solid_edge_part$(FAMILY)" = The icon
file.

Attribute of subelement <document_create>

document_type "SEN"
"SEN" = Solid Edge Standard Part document.
Determines whether the file name for the original is renamed during
document creation according to the set naming rules, or whether the file
rename_template_filename "no" name of the original file is transferred unchanged.
"no" = The file name of the original is copied unchanged.


type "template"
specified.

default "yes"
dictionary_identifier "part"
"part" = Dictionary Identifier.

can select a template file in the "Create Document" dialog using a file

type "select"
"Create Document" dialog using a file selection dialog.
default "no"
extension_filter "*.par" filter are offered for selection.
"*.par" = Filter for the file extension.


"SEN" = Identification of the SAP workstation application for Solid
primary_workstation_application "SEN"
Edge Standard Parts.
Determines whether a relative path is stored for the document with
this DType and should be used when checking out.
use_relative_path "yes"
"yes" = Use relative path.
Next comes the description of the DType definition for Solid Edge Part documents for sheet metal parts
("SES"):

DType definition for master documents of type "SES" for Solid Edge sheet metal part documents
<DType type="master" identifier="SES" include_template="SLEMDL" application_type="SLE"

application_role="P">
...
</DType>
Attributes of the element <DType> of the definition "SES"

type "master"
identifier "SES"
"SES" = ID of this DType definition.

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

tree.
icon_position "1"
Identification of a symbol group. Other symbols can be
displayed depending on their status.
Path for determining the icon file containing the
icon_identifier "{0}/tree/sle/solid_edge_sheet_metal"
"{0}/tree/sle/solid_edge_sheet_metal" = The icon file.


document_type "SES"
"SES" = Solid Edge Sheet Metal Part document.

The filename attribute is used to specify the template file to be
used. You can select a template file in the Create Document dialog
filename "Sheet Metal.psm" using a file selection dialog.
"Sheet Metal.psm" = File name of the template file.

type "template"
"template" = Via the attribute "filename" the template file to be
used is specified.
This allows you to determine whether this template file is preset in
the "Create Document" dialog.
default "yes"
dictionary_identifier "SheetMetal"
"SheetMetal" = Dictionary Identifier.

The filename attribute specifies the template file to be used. You can
select a template file in the Create Document dialog using a file
"Sheet
filename selection dialog.
Metal.psm"
"Sheet Metal.psm" = File name of the template file.
type "select"
dialog.
default "no"
When selecting a template file with type="select" this attribute defines
the filter for the file extension. In the file selection dialog, the files
extension_filter "*.psm" matching the filter are offered for selection.
"*.psm" = Filter for the file extension.



"SES" = Identification of the SAP workstation application for Solid
primary_workstation_application "SES"
Edge sheet metal parts.
Now follows the description of the DType definition for Solid Edge Assemblies documents for welded
assemblies ("SEW"):
DType definition for master documents of type "SEW" for Solid Edge welding assemblies
<DType type="master" identifier="SEW" include_template="SLEMDL" application_type="SLE"

...
</DType>
Attributes of the element <DType> of the definition "SES"

type "master"
identifier "SEW"
"SEW" = ID of this DType definition.


Position of the symbol in the document entry in the tree.
icon_position "1"
"default" = This is the default symbol.

Path for determining the icon file containing the symbol
to be used for this symbol position.
icon_identifier "{0}/tree/sle/solid_edge_weldment"
"{0}/tree/sle/solid_edge_weldment" = The icon file.

document_type "SEW"
"SEW" = Solid Edge Welding Assembly.
attributes of subelement <seedfile> of subelement <document_create>

select a template file in the "Create Document" dialog using a file
filename "Normal.pwd" selection dialog.
"Normal.pwd" = File name of the template file.

type "select"
dialog.
default "no"
When selecting a template file with type="select" this attribute defines
the filter for the file extension. In the file selection dialog, the files
extension_filter "*.pwd" matching the filter are offered for selection.
"*.pwd" = Filter for the file extension.


"SEW" = Identification of the SAP workstation application for Solid
primary_workstation_application "SEW"
Edge welding assemblies.
The following is a description of the DType definition for Solid Edge Master Drawing ("SEDM") documents:

DType definition for master documents of type "SEDM" for Solid Edge drawings
<DType type="master" identifier="SEDM" include_template="SLEDRW" application_type="SLE"

application_role="D" sort_key="2">
...
</DType>
Attributes of the element <DType> of the definition "SEDM"

type "master"
identifier "SEDM"
"SEDM" = ID of this DType definition.
include_template "SLEDRW"
"SLEDRW" = The DType template with the ID "SLEDRW" from this "dtype.xml"

application_role "D"
"D" = Identifier of the object type for Drawings.
Defines a sort key that is used for alphanumeric sorting of DType entries in the
DType selection combo box.
sort_key "2"
"2" = Sorting key.

Position of the symbol in the document entry in the tree.
icon_position "1"
"1" = Far left, "6" = far right.
Path for determining the icon file containing the symbol to be
used for this symbol position.
icon_identifier "{0}/tree/sle/solid_edge_draft"
"{0}/tree/sle/solid_edge_draft" = The icon file.

document_type "SDM"
"SDM" = Solid Edge Drawings (master).

select a template file in the Create Document dialog using a file selection
filename "Draft.dft" dialog.
"Draft.dft" = File name of the template file.

type "template"
specified.
default "yes"
Only for dependent documents: Determines whether the dependent
document receives a component reference (identifier in the sort string
':DC') or whether the document is a simple dependent document
component_reference "no"
(identifier: 'D')
"no" = Dependent document without component reference.

dictionary_identifier "Draft"
"Draft" = Dictionary Identifier.

The filename attribute specifies the template file to be used. You can select
a template file in the Create Document dialog using a file selection dialog.
filename "Draft.dft"
"Draft.dft" = file name of the template file.

default "no"

extension_filter "*.dft" filter are offered for selection.
"*.dft" = Filter for the file extension.

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

Determines whether and how a material is created for a new document.
material_creation_method "no" "no" = No material is created for the document. A subsequent material
creation for this document via SAP Engineering Control Center is not
possible.

"SED" = Identification of the SAP workstation application for Solid
Edge Drawings.
The last section describes the DType definition for Solid Edge Master Drawing ("SEDM") documents:
DType definition for master documents of type "SXLS" for Linked Excel files
<DType type="master" identifier="SXLS" include_template="TXLS" application_type="XLS"

group="Solid Edge">
...
</DType>
Attributes of the element <DType> of the definition "SXLS"

Sets the type of DType definition.
type "master"
"master" = It is a DType definition for master documents.
Unique ID string of this DType definition throughout the XML document. The
ID must be one to five characters long.
identifier "SXLS"
"SXLS" = ID of this DType definition.
include_template "TXLS"
"TXLS" = The DType template with the ID "TXLS" from the global "dtype.xml"

Application). This application is used to open the file from the SAP
application_type "XLS" Engineering Control Center.
"XLS" = The Workstation Application (WSAppl) for Excel.

Defines the group membership for master documents.
group "Solid Edge"
"Solid Edge" = Group Identifier.
The DType definition for nonmaster documents
The SAP Engineering Control Center distinguishes between master documents and dependent documents. The
latter are referred to as nonmaster documents and are assigned to their respective master documents.
NOTE:
Here are the DType definitions of nonmaster documents for Solid Edge for the type "SED"-nonmaster:
DType definition for nonmaster documents for Solid Edge
<DType type="nonmaster" identifier="SED" include_template="SLEDRW" application_type="SLE"

application_role="D" sort_key="1">
...
</DType>
Attribute of the element <DType> of the "SED" definition

Sets the type of DType definition.
type "nonmaster"
"nonmaster" = It's a matter of a DType definition for nonmaster documents.
document. The ID has to be between one and five characters long.
identifier "SED"
"SED" = ID of this DType definition.
definition.
include_template "SLEDRW"
"SLEDRW" = The DType-Template with the ID "SLEDRW" from this
"dtype.xml" file is included. This is the generic definition for Solid Edge
Drawings.
Application). This application opens the file from SAP Engineering Control
"SLE" = This is the Workstation Application for (WSAppl) for Solid Edge.

Here, you can adjust the object type in the RES4 field of the SAP table DRAW.
application_role "D"
"D" = ID of the object type for Drawings.
Sort key used to sort the DType entries in the DType selection combo box.
sort_key "1"
"1" = Sort key.
The sub-element <icon> defines an abbreviation that will be used when determining the applicable symbol in
the SAP Engineering Control Center. It also contains the sub-element <icondef>.
Attribute of the sub-element <icondef> from the sub-element <icon>

the tree.
icon_position "1"
Identification of a symbol group. Depending on the
status, 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.
icon_identifier "{0}/tree/sle/solid_edge_draft$(NM_OLD)"
"{0}/tree/sle/solid_edge_draft$(NM_OLD)" = The
icon file.
The sub-element <nonmaster_options> is used to control how the dependent document responds in relation
to the master document.
Attribute of the sub-element <nonmaster_options>

Determines whether the content of the dependent document depends on the
content of the master document.
depends_on_master "yes"
"yes" = Nonmaster document depends on the master document.
The sub-element <document_create> determines the way in which the document is created in SAP.
Attributes of the sub-element <document_create>

document_type "SED"
"SED" = Solid Edge Drawing as nonmaster document.
Determines the document number assignment in SAP.
document_number_assignment "master"
"master" = The number of the master document is adopted.
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 <seedfile> sub-element inherited from the <document_create> sub-element
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
filename "Draft.dft" process will terminate with an error.
"Draft.dft" = File name of the template file that is to be used.

Determines how the original document will be generated.
type "template"
"template" = The "filename" attribute is used to specify the template file
that is to be used.
This determines whether this template file should be used as a preset in
default "yes"
"yes" = The template file is preset.
Determines whether a dependent document gets a component reference
(definition in the sorting term: 'DC') or whether the document is a simple
component_reference "yes" dependent document (definition 'D').
"yes" = Dependent document receives component reference.

dictionary_identifier "Draft"
"Draft" = Dictionary Identifier.
Attributes of the second <seedfile> sub-element inherited from the <document_create> sub-element
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
filename "Draft.dft" a file selection dialog.
"Draft.dft" = 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
select a template file in the "Create document" dialog using a file selection
type "select" dialog.
"select" = It is possible to select a template file in the "Create document"

dialog.
This determines whether this template file should be used as a preset in
Default "no"
"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,
extension_filter "*.dft" you can select files that are matched by the filter.
"*.dwg" = Filter for the file extension.

Determines whether a dependent document gets a component reference
(definition in the sorting term: 'DC') or whether the document is a simple
component_reference "yes" dependent document (definition 'D').
"yes" = Dependent document receives component reference.

The sub-element <material_create> contains settings for creating a new document from materials.
Attributes of the sub-element <material_create>

Determines whether and how a new document is created from Materials.
material_creation_method "no"
"no" = No material is applied to the document. You cannot attach
materials to this document later through SAP Engineering Control Center.
(primary application) and defines the rules for the checking in and out of the originals.
Attribute of the sub-element <primary_application>

"SED" = Identification of the SAP workstation application for Solid
Edge Drawings.
Adopt component attributes
If component attributes are to be adopted, the section bod_mapping_section="SLEBOD" must be defined in

the DType definition in the configuration file "dtype.xml":
Definition of the section "SLEBOD" in file "dtype.xml
The actual definition of the component attributes to be adopted is then done in the corresponding section in
the configuration file "attributes-to-sap.xml":

Definition of component attributes in section "SLEBOD" in file "attributes-to-sap.xml".
Whether non-existing component attributes should be taken from the document properties is
controlled by the parameter
"plm.options.Save.UseDocumentPropertiesAsRequestedComponentAttributes.SLE"!
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 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:

ECTR dialog "Preferences"
The CAD-specific data file "options.xml" determines the options that are given for the particular CAD system.
We are talking about parameters, which a part of the CAD-specific data file "default.txt" and which are pre-
allocated with a standard value.
Settings made under "Settings -> Preferences" in the menu will be saved in the file "user.txt" for every user in
their specific ECTR work directory, under the sub-menu "preferences" (the exact path:
"%APPDATA%\SAP\ECTR\data\<<ECTR-Version>>\<<SAP-
Server_Mandant_Username>>\preferences\user.txt").
ATTENTION:
The settings made via the menu "Settings -> Preferences" and stored in the file "user.txt" for
each user in his ECTR working directory override the standard settings from the configuration file
"default.txt"! If the default values from the "default.txt" are to be used again, the options must be
deleted from the user-specific file "user.txt" after exiting ECTR!
The file "options.xml" has the following structure:

Structure of the file "options.xml"
<options>
<structure>
<node label="...">
<node card="<<Card X>>"/>
<node card="<<Card Y>>"/>
...
</node>
</structure>
<card name="<<Card X>>">
<option label="..." type="..." prefname="..." tooltip="..."/>
<option label="..." type="..." prefname="..." tooltip="...">
<entry name="..." value="..."/>
</option>
...
</card>
<card name="<<Card Y>>">
<option label="..." type="..." prefname="..." tooltip="..." maxchars="...">
</option>
<option label="..." type="..." prefname="..." tooltip="..." maxchars="..."/>
...
</card>
...
</options>
The elements <structure> define the entry on the left side of the options dialogue within the tree diagram.
This must contain a sub-element <node> which describes specifically the node.
Attributes of element <node>

(Optional) If attribute exists, a folder icon with the given name will appear. Below
label="..." Name
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
Card
card="..." (preferences), and which will appear on the right when clicked. The adjustable
identifier
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 options.xml:
<node label="Solid Edge">

<node card="Miscellaneous" label="plm.options.card.misc"/>
<node card="Application structure"
label="plm.options.card.application.structure"/>
.
.
.
</node>
Dictionary identifiers can and should also be used for the following attributes:
<option label="...">, <option tooltip="..."> and <entry name="...">
Example dictionary.txt:
# Preference keys from options.xml

plm.options.card.misc=Verschiedenes
plm.options.card.application.structure=Applikationsstruktur
.
.
.
With the element <card> you define the options that can be reached under the respective card node. The
assignment is done via name of card.
Attribute of element <card>

name="..." Name Name of Card, like in the element <node>
The sub-element <option> always defines one option that appears on the card. Here you allocate a parameter
(preference) from the CAD-specific file "default.txt" as well as the possible value area. In doing so, an empty
editing field will appear or a list of values will apply.
Attributes of sub-element <option>

Name or description of Description of the option as appears on the card under
label="..."
the option "Description"
file type of the option. The following is possible:
type="..." Data type
"string", "boolean", "long"
prefname="..." Parameter name The complete name of the preference from file "default.txt"
(Optional) Description of the option. Appears as tooltip, when
tooltip="..." Description of the option
mouse cursor is positioned on the option
(Optional) Maximum possible number of signs or characters
maxchars="..." Number
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.

Attributes of sub-element <entry>
name="..." Name Name of value in the list
Value according to attribute "type" from element
value="..." Value, which is given to parameter at choice
<option>
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.
plm_setenv.bat
The file "plm_setenv.bat" serves to set environment variables. These can then be evaluated from the SAP
Engineering Control Center Interface to Solid Edge 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>>%".
On default, the "plm_setenv.bat" file contains the default values of the environment variables supported by the
interface.
Possible environment variables are:
Available environment variables

Environment variable Possible values Description
'0' = Detailed dialog. Defines whether a simple loading dialog for ECTR and CAD processes ('1' - '5')
USE_SIMPLE_DIALOG '1' - '5' = Simple dialog with should be displayed in the user interface instead of detailed status messages
different loading icons. ('0').
"true" = Write document Enables writing a complete dump of the current document structure to the log
structure to log. file ("true").
PLM_LOG_INTERFACE_DUMP_DOC_STRUCTURE
"false" = Do not write document ATTENTION:
structure to log. This can affect the performance of large assemblies!
ATTENTION:
The file "plm_setenv.bat" is only executed if the CAD system is started from ECTR, i.e. either via
the menu "System->Launch Application->Start Solid Edge" or by opening a document in the
Application Structure etc. If Solid Edge is started without ECTR or the connection to ECTR is
established later, setting environment variables via the file "plm_setenv.bat" does not work!
CustomOccurrenceProperty.xml (Assign material)

As of Solid Edge 2022, virtual components are also supported. With the function "Assign material" (in the
context menu of the application structure view of the ECTR), the material is stored in the Custom Occurrence
Properties in both the internal and the external representation. Virtual components can also have a structure.
Subsequently, a material BOM derivation in SAP is possible.
For this to work, the following extensions must be added to the Solid Edge configuration file
"C:\Program Files\Siemens\Solid Edge 202X\Preferences\CustomOccurrenceProperty.xml":

Extensions to the file "CustomOccurrenceProperty.xml" for the function "Assign
material"
<OccurrenceProperty>
<Name>SAP_MATERIAL_EXT</Name>
<Description>External Material number for virtual Components</Description>
<PropertyBehavior>Global+Overrides</PropertyBehavior>
<ListOfValues></ListOfValues>
<DefaultValue></DefaultValue>
</OccurrenceProperty>
<OccurrenceProperty>
<Name>SAP_MATERIAL_INT</Name>
<Description>Internal Material number for virtual Components</Description>
<PropertyBehavior>Global+Overrides</PropertyBehavior>
<ListOfValues></ListOfValues>
<DefaultValue></DefaultValue>
</OccurrenceProperty>
Version information
To gain an overview of the imported changes of the relevant releases of the SAP Engineering Control Center
Interface to Solid Edge, the changes are listed here in the configuration files "default.txt" and "dtype.xml".
The following table contains changes in parameters in the configuration file "default.txt". The status shows
whether the relevant parameter in this version was added ( ), changed ( ) or deleted ( ). When changing a
parameter, merely a new parameter name is given.
Changes in configuration file "default.txt"

Version Status Parameter
plm.document.dtype.decal.SLE
02.33.222.00 plm.docstructure.instdata.attr.namepattern.SLE
plm.options.bom.UsePrefixAsCategory.SLE
02.33.220.00 plm.execute.additional.SLE
02.32.219.00 plm.options.Cancel.DialogDefaultValue.SLE
plm.options.InsertComponent.AdjustablePart.ActivateWorkaround.SLE
plm.options.Draft.UpdateViews.AfterAttributeUpdate.SLE
02.32.214.00 plm.execute.additional.SLE
plm.options.Ballooning.UpdateStrategy.SLE
plm.options.Save.UseDocumentPropertiesAsRequestedComponentAttributes.SLE
plm.options.InsertComponent.AdjustablePart.ActivateWorkaround.SLE
02.31.210.00
plm.options.MaintainGeneric.DeleteMissingMember.SLE
02.30.201.00 plm.options.checkIn.AbortAnalysisOfCheckedInComponents.AbortAtFOA.SLE
plm.options.ReplaceVersion.CheckoutParents.SLE
02.30.194.00
plm.options.InPlaceActivated.CheckOutDocument.SLE
plm.appl.popwin.name.SLE
02.29.193.00
plm.control.popwin.name.SLE

plm.document.dtype.decal.SLE
plm.document.BMPAsAdditionalFile.SLE
plm.document.PNGsAdditionalFile.SLE
plm.document.JPGAsAdditionalFile.SLE
plm.document.TIFAsAdditionalFile.SLE
plm.document.createMulti.cad.dtype.searchAlso.SLE
plm.structure.application.DisplaySuppressedComponents.SLE
plm.structure.application.deactivate.SelectForSubElements.SLE
02.28.187.00
plm.structure.node.CUAPOB_SLE_VIRTUAL.icon.2
plm.structure.node.CUAPOB_SLE_VIRTUAL.icon.1
plm.structure.node.CUAPOB_SLE_VIRTUAL_NEW.icon.2
plm.structure.node.CUAPOB_SLE_VIRTUAL_NEW.icon.1
plm.structure.application.UsePlmObjectContent.SLE
structure.view.SLE.generic.object.SLE_VIRTUAL.name
structure.view.SLE.generic.object.SLE_VIRTUAL_NEW.name
plm.structure.application.DisplayPosItem.SLE
02.27.183.00 plm.options.save.useTwoTierStructureAnalyze.SLE
plm.options.SaveAs.CheckInAfterCreate.SLE
obr.filter.filter.asvforeignpossible.sle
plm.structure.application.ExpandDocumentsOnlyOnce.SLE
02.27.182.00
plm.options.Cancel.LoadedParts.SLE
plm.options.Save.LoadedParts.SLE
plm.document.FOA.Handling.SLE
plm.document.CustomIgnoreDirectories.IgnoreSubDirectories.SLE
02.26.176.00
plm.document.CustomIgnoreDirectories.SLE
02.25.171.00 plm.document.UseNewRenameLogic.SLE
02.25.169.00
plm.document.FOA.ReplaceInAllMembers.SLE
plm.document.ExcelAsAdditionalFile.SLE
plm.document.dtype.Default.SEA.SLE
plm.document.dtype.Default.SEP.SLE
02.24.165.00 plm.document.dtype.Default.SES.SLE
plm.document.dtype.Default.SEW.SLE
plm.document.dtype.Default.SDM.SLE
plm.document.AssemblyCopies.Handling.SLE
plm.structure.application.deactivate.SelectForSubElements.SLE
obr.filter.filter.asvselectpossible.sle
02.24.164.00
obr.filter.fnc.structure.view.application.generic(FUNCTION_ID)
plm.options.MechanicalModeling.UpdateMaterial.MaterialLibrary.SLE
plm.structure.application.DisplayAdditionalAttributes.SLE
plm.structure.application.AdditionalAttributes.SLE
02.24.152.00
plm.document.IgnoreDrawing2DrawingReferences.SLE
plm.document.UseNewRenameLogic.SLE
02.22.147.00 plm.structure.application.show.drawing.container.ontop.SLE

plm.bom.item.property.SLE
plm.bom.item.property.SLE.<OccurrencePropName>
plm.options.structureAnalyze.showDialogForMissingReferences.SLE
plm.options.StructureAnalysis.MinimumErrorLevel.SLE
plm.document.ExcelAsAdditionalFile.SLE
02.22.145.00
plm.loadoptions.SLE.ShowCADOpenDialog.Extensions
plm.document.IgnoreInterpartLinks.SLE
plm.document.AssemblyCopies.Handling.SLE
plm.options.Thumbnail.SLE.jpg.<preference>
plm.options.MissingReferenceReloadOption.SLE
02.20.129.00 plm.options.CreateDependentDocument.AskUserOnAdditionalNonMasterCreate.SLE
plm.library.SLE.PartLib
plm.document.dtype.PartLib.SLE
plm.document.createMulti.cad.dtype.searchAlso.SLE
plm.document.create.references.mastercomp.name.SLE
plm.convert.additional.SLE.jt.keepExtension
plm.control.partnameRules.resolveInSap.SLE
plm.options.PathFinder.Show.DocumentStatus.SLE
02.20.126.00 plm.loadoptions.SLE.ShowCADOpenDialog
plm.document.ExcelAsAdditionalFileForDrawings.SLE
plm.structure.application.show.drawing.SLE
plm.structure.application.show.drawing.container.SLE
structure.view.SLE.generic.object.DRAW_CONTAINER.name
structure.view.SLE.generic.object.DRAW_CONTAINER.icon
structure.view.SLE.generic.object.type
plm.structure.application.LoadDrawings.SLE
plm.document.dtype.Default.PAR.SLE
plm.document.dtype.Default.ASM.SLE
plm.document.dtype.Default.DFT.SLE
02.20.124.00
plm.document.dtype.Default.PSM.SLE
plm.options.HideDIRCreationDialog.SLE
plm.options.save.useTwoTierStructureAnalyze.SLE
plm.options.checkForUpdates.before.CheckoutEdit.MultiLevel.SLE
02.19.124.00 plm.options.checkForUpdates.before.CheckoutEdit.ExplosionScenario.SLE
plm.options.SaveAsNewDocument.CancelSourceFile.SLE
plm.options.DisableDirtyHandlingForWritingComponentIDs.SLE
02.17.115.00
plm.options.UpdateAttributes.RefreshContext.SLE
02.17.111.00 plm.options.Ballooning.InitializeBalloonWith.SLE
plm.options.UpdateAttributes.UpdateReadOnly.SLE
plm.options.Thumbnail.SLE.jpg.<preference>
02.16.106.00
plm.options.BOMTable.Column.SLE.[CAD_COLUMN]
plm.document.DirtyFlag.SLE
plm.options.ImportOnDemand.CheckInAfterCreate.SLE
02.14.84.00
plm.options.ImportOnDemand.DeleteOriginals.SLE
02.13.83.00 plm.control.partnameRules.applExtension.SLE
plm.options.BOMTable.AddNonExistingColumns.SLE
02.13.81.00
plm.options.checkIn.UpdateAttributesFromSAP.SLE
02.13.79.00 plm.options.Ballooning.BalloonContent.SLE
02.12.79.00 plm.document.variants.importOnDemand.SAPDescription.SLE
plm.loadoptions.versionConflictResolveMode.SLE
02.12.72.00
plm.execute.additional.SLE

02.12.71.00 plm.convert.additional.SLE
plm.options.BOMTable.Column.SLE.Material
plm.options.BOMTable.Column.SLE.Postext1
plm.options.BOMTable.Column.SLE.Postext2
02.12.66.00
plm.options.BOMTable.Column.SLE.OtherColumn
plm.options.Thumbnail.Size.SLE
plm.convert.additional.SLE.JT.filenameFormat
plm.options.SaveDIRAfterCreation.SLE
02.11.62.00
plm.doc.checkout.allowedFamilyMembersApplTypes
plm.document.variantKeepVersion.SLE
02.10.58.00 plm.options.checkIn.AbortAnalysisOfCheckedInComponents.SLE
02.09.52.00 plm.options.deliverOnlyRequestedAttributesToSAP.SLE
plm.options.new.SaveActiveDocument.SLE
plm.options.OnFileOpenUI.DeactivatedForAddin.ST9.SLE
02.08.50.00 plm.options.Ballooning.InitializeString.SLE
plm.options.SapOpenForLoadDrawing.SLE
plm.doc.cancel.restore.files.SLE
plm.options.OnFileOpenUI.DeactivatedForAddin.ST9.SLE
plm.options.open.UseMultiSearchForSapOpen.SLE
02.07.49.00
plm.options.structureAnalyze.showDialogForMissingReferences.SLE
plm.document.Import.IgnoreMissingReferences.SLE
plm.options.new.SaveActiveDocument.SLE
02.06.47.00 plm.options.SapOpenForLoadDrawing.SLE
plm.options.importOnDemand.updateAttributes.SLE
plm.structure.application.init.strategy.levels.SLE
02.05.40.00 plm.loadoptions.SLE.ShowCADOpenDialog
plm.document.SaveAsNewDocument.CheckOutTop.SLE
plm.options.SapOpenForCadOpenDocument.SLE
plm.Occurrence.IncludeInBOM.SLE
plm.Occurrence.UserDefinedQuantity.SLE
plm.options.Ballooning.InitializeString.SLE
plm.options.importOnDemand.TransferAttributesToSAP.SLE
02.04.36.00
plm.document.dtype.Default.SEA.SLE
plm.document.dtype.Default.SEP.SLE
plm.document.dtype.Default.SES.SLE
plm.document.dtype.Default.SEW.SLE
plm.document.dtype.Default.SDM.SLE
plm.structure.application.LoadDrawings.SLE
plm.options.importOnDemand.loadDrawings.SLE
02.03.32.00
plm.options.save.loadDrawings.SLE
plm.options.CreateDIRForNewDocument.SLE
02.02.27.00 plm.document.Import.IgnoreMissingReferences.SLE
02.01.22.00 plm.structure.application.CollectEntries.SLE
01.03.15.00 plm.options.updateAttributes.useInteropPrefix.SLE
01.02.14.00 plm.options.CreateDIRForNewDocument.SLE

plm.convert.additional.SLE
plm.convert.additional.SLE.SEA
plm.convert.additional.SLE.SEP
plm.convert.additional.SLE.SES
01.00.11.00
plm.convert.additional.SLE.SEW
plm.convert.additional.SLE.SED
plm.convert.additional.SLE.SDM
plm.convert.additional.SLE.SEA.JT.extension
The following table contains changes in the configuration file "dtype.xml":
Changes in configuration file "dtype.xml"

Version Description
• The template definitions for "SLEMDL" and "SLEDRW" have got the attribute
from_application_only="yes" in their checkin_rules.
The attribute "from_application_only" can only be processed from ECTR version

5.1.10 onwards, an older ECTR version terminates with an error message!
02.11.62.00 If you are working with an older ECTR, you should use the file "dtype.5.1.9.xml"
instead of the current "dtype. xml", which is located in the directory
"template_customize".
• The DType definitions "SEA" and "SEM" have both got the sub-element <program_options>
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
02.08.50.00
of DTypes and Seedfiles. All elements <description language="XY"> are omitted except
English, which are used as fallback.
The following table contains changes in the configuration file "plm_setenv.bat":
Changes in the "plm_setenv.bat" configuration file

Version Description
The "plm_setenv.bat" file is now delivered with the following content by default:
02.24.158.00 set USE_SIMPLE_DIALOG=false
set PLM_LOG_INTERFACE_DUMP_DOC_STRUCTURE=false

Notes and configuration examples
In the following chapter, various configuration options in the ECTR environment are presented using process-
related examples based on the SAP Engineering Control Center Interface to Solid Edge. The intention is to
illustrate how the various requirements can be implemented. This chapter should be used just as an aid. The
values to be configured are described using placeholders and should be replaced, in actual use, according to
customer requirements.
BOM derivation for Family Of Assembly (FOA)

Part lists (BOM) can also be derived from Family Of Assembly (FOA). But it must be possible to derive the BOM
from an assembly in which a member is installed. In the member itself, the FOA generic and its children should
be completely ignored. However, this requires customizing of the explosion scenarios in SAP.
You must use transaction "CDESK_CUS" (for R/3 Systems) or "CAD_SRV_CUS" (for S/4HANA Systems) to define
the explosion rule "BOM_DERIVE" for the CAD system "SOLIDEDGE". You do this in the view "Explosion Rules"
under "Explosion Scenario":

Define the explosion rules in SAP Customizing
The explosion rule "BOM_DERIVE" is empty by default. This must now be set as follows:
Entries for explosion rule "BOM_DERIVE"

Column Value
CAD-Field SORTF: Sort string in STPO (BOM item)
CAD-Field Abbreviation SLE:I
Expl. Bhr. ST: Stop Directly; Do not Return Child DIR
This customizing setting stops the determination of the document structure as soon as a document with SORTF
= SLE:I will be found. This means that the document itself and all subordinate documents are not added to the
hierarchy and are not determined further. This may prevent circular references:

FOA document structure

Final Remark
This manual is intended to facilitate handling of the product. Since this product is also constantly being further
developed, only the release status at the time of going to press could be taken into account here. CIDEON
Software & Services GmbH & Co KG is grateful for information and suggestions provided by users. Please enter
a SAP ticket in the SAP Support Portal.
This documentation has been prepared with the greatest possible care, but we cannot accept any liability for
any defects or errors that may occur.
You can find the current documentation in the SAP Help Portal.
On our homepage you will find further information and news!
CIDEON Software & Services GmbH & Co. KG
www.cideon.com
Copyright (C) 2023 CIDEON Software & Services GmbH & Co. KG. All rights reserved.
No part of this document may be reproduced or copied in any form for any purpose without the express
permission of CIDEON Software & Services GmbH & Co KG.


CIDEON ECTR Interface To SolidEdge Configuration Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CIDEON ECTR Interface To SolidEdge Configuration Manual

Uploaded by

Copyright:

Available Formats

Conﬁguration Manual

Management of CAD data and documents in SAP

SAP Engineering Control Center Interface to Solid

CIDEON Software & Services GmbH & Co. KG Page 1 of 86 2023-05-17

CIDEON Software & Services GmbH & Co. KG Page 2 of 86 2023-05-17

The system-wide environment variable "%PLM_INSTDIR%" contains the installation directory of

The directory "appdata"

The directory "basis"

Here, the following directories are included:

The directory "documentation"

The directories "templates" and "template-templates"

CIDEON Software & Services GmbH & Co. KG Page 4 of 86 2023-05-17

The directory "customize\conﬁg"

The directory template-customize\conﬁg

Icons for CAD originals in SAP ECTR

CIDEON Software & Services GmbH & Co. KG Page 5 of 86 2023-05-17

Icons for Solid Edge supplied as standard

CIDEON Software & Services GmbH & Co. KG Page 6 of 86 2023-05-17

Starting Solid Edge from ECTR in the SAP logon language

However, Solid Edge does not support this!

CIDEON Software & Services GmbH & Co. KG Page 7 of 86 2023-05-17

CIDEON Software & Services GmbH & Co. KG Page 8 of 86 2023-05-17

Construction of a menu deﬁnition

CIDEON Software & Services GmbH & Co. KG Page 9 of 86 2023-05-17

Deﬁnition of the context menu for cloning

Deﬁnition of the context menu for "Cloning"

The following functions are possible:

Possible functions in the context menu for "Cloning"

CIDEON Software & Services GmbH & Co. KG Page 10 of 86 2023-05-17

Structure of a macro deﬁnition

attributes-from-sap.xml and attributes-to-sap.xml

Diverse attribute mappings are included in the general conﬁguration ﬁles

CIDEON Software & Services GmbH & Co. KG Page 11 of 86 2023-05-17

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

Various sections can be defined in the CAD-specific attribute mapping file

CIDEON Software & Services GmbH & Co. KG Page 12 of 86 2023-05-17

The element <section> deﬁnes a section which represents an attribute segment.

Attribute of element <section>

Attributes of the sub-element <APPL_ATTRIBUTE>

CIDEON Software & Services GmbH & Co. KG Page 13 of 86 2023-05-17

ﬁeld="..." Field Name ATTENTION:

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

Example for subelement <CUTLEADING>

If character="0", "000000004711" will be modiﬁed to "4711".

Example for subelement <XFORMAT>

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

Both subelements can be combined:

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

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

CIDEON Software & Services GmbH & Co. KG Page 14 of 86 2023-05-17

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

Attribute of element <section>

Attributes of subelements <DIR> and <MA>

CIDEON Software & Services GmbH & Co. KG Page 15 of 86 2023-05-17

ﬁeld="..." Field Name ATTENTION:

Attributes of the sub-element <APPL_ATTRIBUTE>

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

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

Solid Edge Properties

CIDEON Software & Services GmbH & Co. KG Page 16 of 86 2023-05-17

The following categories of properties exist:

Overview of Solid Edge Properties

Category: Summary Information