SAP Engineering Control Center Interface to CATIA V5

SAP Engineering Control Center Interface to CATIA V5

ECTRV5

Page 1 SAP Engineering Control Center Interface to CATIA V5

Customizing Dokumentation

SAP Engineering Control Center Interface to CATIA V5 Installation and Setup CENIT AG

Software Product / Components: ECTRV5

Product Version: 1.1.7

Creation Date: 28.08.2015 15:14

Document Version: 11

Last Changed: 22.02.2019 11:55


ECTRV5



Content

1 Preface 3

2 System Prerequisites 4

2.1 Client Prerequisites 4

2.2 CATIA 4

2.3 SAP Engineering Control Center 5

2.4 Further Information 5

3 Configuration for CATIA 6

4 Configuration for SAP DMS 9

4.1 Document Types 9

4.2 Document Status Network 16

4.3 Maintain Workstation Applications 21

4.4 Maintain CAD Desktop customizing 24

5 Installation of SAP Engineering Control Center Interface to CATIA V5 34

5.1 Installation using the Setup 34

5.2 Installation without using the setup from installation media 34

5.2.1 Extraction of the installation data from the installation media 34

5.2.2 Copy to the target directory 34

5.2.3 Registrierung 35

5.2.4 Finalizing the installation 35

5.2.5 Special case: Manual Update 35

6 Customizing SAP Engineering Control Center 36

6.1.1 Customizing within Default.txt 36

6.1.2 Customizing within SapLogon.txt 37

6.1.3 Customizing within System-Default.txt 37

6.1.4 Customizing within menu.guidef and menu_macros.txt 37

6.1.5 Customizing within DType.xml 41

6.1.5.1 Customizing within DType.xml for cgrs und V4 Models 45

6.1.6 Customizing within plm_setenv.bat respectively StartApplicationCat.xml 46

7 Customizing for SAP Engineering Control Center Interface to CATIA 49

8 Appendix 50

8.1 Copyright 50

8.2 Open Source Software 50

8.3 Original Apache 2.0 License 50

9 Illustrations 51


ECTRV5



1 Preface

This document describes the installation and first setup steps for SAP Engineering Control Center Interface to CATIA V5.

This document assumes that the installation and administration manuals of SAP Engineering Control Center have been read and understood.


ECTRV5



2 System Prerequisites

2.1 Client Prerequisites

The following operating systems are supported:

Windows 7 (64 Bit) (in combination with CATIA R26, R27 und R28)

Windows 8.1 (64 Bit) (in combination with CATIA R26, R27 und R28)

Windows 10 (64 Bit) (only in combination with R26 SP3 or higher, earlier CATIA releases on Windows 10 are not supported by Dassault Systèmes)

To execute the setup application administrative rights are required.

The operating system (64 Bit only) also needs to have installed Microsoft Visual C++ 2008 SP1 Redistributable Package including the following updates:

Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security

Update

Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security

Update

Additionally, the .net Framework in version 3.5 is required.

2.2 CATIA

At the release of the current product version, the last 3 versions of CATIA V5 will be supported.

With the release of the “SAP ECTR Interface to CATIA V5” in the version mentioned on the title, these are:

- CATIA V5-6R2016 (aka CATIA R26) at least SP1 - CATIA V5-6R2017 (aka CATIA R27) at least SP1 - CATIA V5-6R2018 (aka CATIA R28) at least SP1

For the CATIA installation prerequisites, please contact your CATIA partner or check the installation prerequisites in the available CATIA setup manuals.

Note:

Before executing the setup for SAP Engineering Control Center Interface to CATIA V5, at least one of the supported CATIA V5 versions must be installed on the workstation and registered within the windows registry. The setup will check if CATIA is installed.

http://www.microsoft.com/en-us/download/details.aspx?id=11895





ECTRV5



2.3 SAP Engineering Control Center

SAP Engineering Control Center 5.1.13 or higher must be installed.

For further details regarding the installation prerequisites for SAP Engineering Control Center, check the manual for SAP Engineering Control Center or get in contact with your SAP partner.

You find the manual for the SAP Engineering Control Center for example in the SAP support portal:

Go to help.sap.com

Search for SAP Engineering Control Center

Download the Installation Guide from the search results

Note:

When executing the setup of SAP Engineering Control Center Interface to CATIA V5, the setup will check if SAP Engineering Control Center is already installed, without SAP Engineering Control Center the setup will be aborted.

2.4 Further Information

Due to constant improvements and bugfixes, especially in regards of the SAP Engineering Control Center, a special SAP note is available.

In this note you will find the latest information regarding the system prerequisites of the SAP Engineering Control Center to CATIA V5. It can be found at

https://launchpad.support.sap.com/#/notes/ 2572830


ECTRV5



3 Configuration for CATIA

SAP Engineering Control Center Interface to CATIA V5 requires certain CATIA settings in order to work correctly

To use the correct subdocuments for a product in multi user operation the Linked Document Localization in the CATIA options has to be set in an appropriate way. Tools – Options path:

Folder of the pointing document has to be on top. Without this CATIA setting the SAP Engineering Control Center Interface to CATIA V5 will not work properly!

In CATIA the option “Do not activate default shapes on open” must not be set. Tools – Options path:

Without this CATIA setting the SAP Engineering Control Center Interface to CATIA V5 does not work properly!

In CATIA the Option “Disable Product Structure cache system” has to be set. Tools – Options path:


In CATIA the Option “Pointed documents not loaded” must not be set.

General

Document

Linked Document Localization

Infrastructure

Procuct Structure

Product Visualization

Representation

Analysis & Simulation

General

Load Management


ECTRV5



Tools – Options path:


In CATIA the Option “Load referenced documents” has to be set. Tools – Options path:


In CATIA the Option “Visualization mode with local cache” has to be set. Tools – Options path:


The CATIA CGR Cache should be activated.

Tools – Options path:

In CATIA the Option “No automatic backup” should be set. Tools – Options path:

Analysis & Simulation

General

Load Management

General

General

Referenced Documents

Infrastructure

Product Structure

Product Visualization

Visualization mode type

Infrastructure

Productstructure

Cache Administration


ECTRV5



If you are using CATIA DLNames, the paths for the session directory of SAP Engineering Control Center Interface to CATIA V5 and the temporary directory need to be defined as DLName.

Important: All CATIA CATSetting files (CATReferenceSetting files and CATUserSetting files) should be deleted and set up as new when updating CATIA or SAP Engineering Control Center Interface to CATIA V5.

This comes from the fact that the use of CATSettings from an older CATIA release is known to be the cause for all kinds of errors in CATIA and SAP Engineering Control Center Interface to CATIA V5, from wrongly displayed CATSettings in the Tools/Options dialogs of CATIA up to crashes of CATIA or SAP Engineering Control Center Interface to CATIA V5.

General

General


ECTRV5



4 Configuration for SAP DMS

To support different CATIA documents certain configuration settings within SAP need to be checked and set. This chapter describes those prerequisites.

Note: SAP delivers so-called BC-Sets within the package of SAP Engineering Control Center, with which the SAP customizing settings described in the following chapters are pre-configured and easily deployed to the SAP server.

These BC sets should only be used if it is ensured that the following document-types, WS applications and CAD-Desktop customizing settings are not already configured in the SAP system and would be overwritten by the import of the BC sets!

The hereinafter described customizing settings are contained in the BC Set „/DSCSAG/ECTR_CAT“.

For further information regarding these BC sets please consult the SAP Engineering Control Center documentation.

4.1 Document Types

It is recommended to use three different document types in SAP for the CATIA documents:

Designation File types Description

5PR CATProduct Common assembly

5PA CATParts, cgr, model, design-tables (txt, xls, xlsx, xlsm)

Single part files

5DR CATDrawings, CATAnalysis, CATProcess

This type is for additional documents which have a reference to another document. For example, if a drawing is referenced to a CATProduct

In the following chapters for configuring DTypes you will find references to those document types. If you use other identifications for your document types they need to be adjusted accordingly.

For the maintenance of document types in SAP, start the SAP transaction spro.


ECTRV5



Illustration 1: Customizing (entry screen)

The SAP reference IMG provides an overview of commands:

Select SAP Reference-IMG


ECTRV5



Illustration 2: Customizing

Continue:

-> Cross-Application Components -> Document Management -> Control Data -> Define Document Types to document type definition.

In this view for the document type “5PR” the following settings are stored


ECTRV5



Illustration 3: Customizing the document types 5PR, 5PA and 5DR

It is appropriate to copy a template of an existing document type.


ECTRV5



Illustration 4: Document type example 5PR

Important: Storage KPro

Shorttext +

Key:

- suppress field

+ required field

* display field

. optional field


ECTRV5



Illustration 5: Document type example 5PA


ECTRV5



Illustration 6: Document type example 5DR


ECTRV5



4.2 Document Status Network

For the defined document types a minimal status network is required. Within customizing the definition of the status is:

-> Cross-Application Components

-> Document Management

-> Control Data

-> Define Document Types

-> Define Document status

Examples for the three defined document types

Illustration 7: Status Network for 5PR


ECTRV5



Illustration 8: Status Network for 5PA


ECTRV5



Illustration 9: Status Network for 5DR


ECTRV5



Based on the status network for the document type 5PR here is a brief technical explanation of the setup of the status network:

Illustration 10: Entry Point for Definition

Define document status


ECTRV5



Illustration 11: Define New Status

Illustration 12: Status

Define a new status using new entries

Key Status type:

I = initial status

P = primary status

T = temporary status

O = original in work

S = locked status

A = archive status

C = check-in status

There is not usually an entry for the status type. This means not special status.

The difference between primary- and initial-status is, that it is possible to go back to initial-status, whereas it is not possible to go back to a primary status after having left it.

Most of the data in the document info record can no longer be changed, the original cannot be edited and stored


ECTRV5



Illustration 13: Example for Previous Status

4.3 Maintain Workstation Applications

For SAP Engineering Control Center Interface to CATIA V5, at least three workstation applications need to be maintained

- CAT CATIA-documents - CCF for CATIA-Cache-Files (cgr) - ANA for automatic generated CATAnalysis files (like CATAnalysisComputations

and CATAnalysisResults)

Workstation applications can be maintained within SAP Customizing:

Cross-Application Components

-> Document Management

-> General Data

-> Define Workstation Application


ECTRV5



Illustration 14: Necessary Settings for the WS Application

Important:

You cannot rename temporary files


ECTRV5



Illustration 15: Further Required Settings for the WS Application

Analog to the workstation application CAT the workstation application ANA has to be created with the same settings.

Following the settings for the workstation application CCF - other than for CAT or ANA, this will be limited for a file type.


ECTRV5



Illustration 16: Define the WS Application CCF

No further settings for this workstation application are necessary.

4.4 Maintain CAD Desktop customizing

For the SAP Engineering Control Center interface to CATIA V5 certain settings in the CAD-Desktop customizing must be made. The CAD-Desktop customizing can be found (via transaction spro) in:

Cross-Application Components

Important:

Limit to *.cgr


ECTRV5



-> CAD Integration

-> CAD Desktop

Illustration 17: CAD Desktop Customizing


ECTRV5



Illustration 18: CAD-Systems

Within the CAD-Desktop customizing the CAD system “CATIAV5” must be selected. If it doesn’t exist yet, it has to be created via “New Entries” with the settings given in illustration 18. After the creation, the new entry must be selected and in the left tree, the topic “Group maintenance” has to be activated:


ECTRV5



Illustration 19: Group maintenance

In the “Group Maintenance” a valid user group has to be selected. If no valid group exists, it has to be created via “New Entries” with the settings given in illustration 19. After the creation, the new entry must be selected and in the left tree, the topic “Explosion Scenarios” has to be activated:


ECTRV5



Illustration 20: Explosion Scenario

In the “Explosion Scenario” screen the three entries given in illustration 20 must be created.

For every new created entry the topic “Explosion Rules” must be activated:


ECTRV5



Illustration 21: Explosion rules BOM_DERIVE

The entries shown in illustration 21 must be created with the command “New Entries“, then return to the “Explosion Scenario“ screen with the “Back“ command.

Important note: If an error message occures, while trying to customize entries like RES4 or SORTF, please check them. Proceed as follows, please:

1. Open the view V_CDESK_C_EXPLCF via transaction SM30 or SE16.

Illustration 22: Customizing entries via V_CDESK_C_EXPLC


ECTRV5



When the values RES4 and SORTF are missing, add them via "New Entries".

Illustration 23: Customizing new entries

Illustration 24: Customizing entries RES4 and SORTF

2. Add the following CAD-Fields with their abbrevations in the View V_CDESK_C_EXPLFA.


ECTRV5



Illustration 25: Customizing the values in V_CDESK_C_EXPLFA

With these entries, the explosions rules can now be customized without errors.

Now, analogous entries must be made for CAD_LOAD and CTX-View:


ECTRV5



Illustration 26: Explosion rules CAD_LOAD



ECTRV5



Illustration 27: Explosion rules CTX_VIEW



ECTRV5



5 Installation of SAP Engineering Control Center Interface to CATIA V5

5.1 Installation using the Setup

The setup for the SAP Engineering Control Center to CATIA V5 can be acquired via the SAP marketplace. This is the recommended way of installing this software, as some components need to be registered in Windows.

For the installation a SAP Engineering Control Center and a CATIA V5 need to be installed. This will be verified by the installation program. In addition the Microsoft © .NET Framework 3.5 is required.

If one of the prerequisites is not fulfilled an appropriate error message will be generated.

After starting the setup, follow the instruction step-by-step.

Note:

If you receive messages / message boxes after installing SAP ECTR interface to CATIA V5 saying that CATIA or the module “ComWrapper.dll” aren’t correctly registered solve this by running the batch-tool “Register.bat” located in folder <ECTR installation directory>\applications\cat\basis\sys\win\bin. Using this batch-tool Windows registry keys for CATIA V5 and SAP ECTR interface to CATIA V5 will be renewed.

5.2 Installation without using the setup from installation media

In this section it will be described, which steps are needed to take the SAP ECTR Interface to CATIA V5 into operation without an installation.

Note:

This is not the recommended way of installing or distributing this software as recommended by SAP. It is described here to have a complete description available, in case it is needed.

5.2.1 Extraction of the installation data from the installation media

With the following command all data will be extracted from the „SAP ECTR Interface to CATIA V5“-Setup into a working directory:

SAP ECTR Interface to Catia <Version>.exe /Extract:<working directory>

After the extraction the working directory will contain a subdirectory called ECTRCATIA, which

contains the SAP ECTR Interface to CATIA V5.

5.2.2 Copy to the target directory

The content of the directory ECTRCATIA needs to be copied to

<ECTR installation directory>\applications\cat

Afterwards, the content of the target directory will look as follows:

Illustration 28: Content of the target directory


ECTRV5



As next step, the directories template-customize and template-templates have to be

copied and renamed in the same directory.

template-customize customize

template-templates templates

In the end, the directory needs to look approximately like this:

Illustration 29: Final content of the target directory

5.2.3 Registrierung

Before the first use, an initial registration of some software components has to be done in

Windows. To do so, there is a batch script called Register.bat which can be found in the

directory

<ECTR installation directory>\applications\cat\basis\sys\win\bin

It needs to be executed with administrative rights. Otherwise, the registration will fail.

Note:

This step has to be performed on all computers, on which the integration should be used.

5.2.4 Finalizing the installation

For finalizing the installation, please follow the step described in the chapter for customizing SAP Engineering Control Center.

5.2.5 Special case: Manual Update

In the case a manual update should be performed, a batch script called

unRegister_Codebase.bat has to be executed before the update. The batch script can be

found in the directory

<ECTR installation directory>\applications\cat\basis\sys\win\bin

It has to be executed with administrative right.

After the update the batch file Register.bat from the directory above needs to be run again with administrative right.


ECTRV5



6 Customizing SAP Engineering Control Center

After successful installation of SAP Engineering Control Center Interface to CATIA V5 some configuration files for SAP Engineering Control Center need to be changed. These changes will be described in this chapter.

For further possible settings within SAP Engineering Control Center please refer to the manuals of the SAP Engineering Control Center.

6.1.1 Customizing within Default.txt

Note:

The Default.txt is the configuration file of SAP Engineering Control Center. There are many versions of this file in the installation in order to make them more readable when they are used with different CAD systems and document types respectively.

The standard ECTR file is located at <ECTR installation directory>\customize\config. Furthermore such a file can also be located at <ECTR installation directory>\<abbreviation of the document type or CAD system>\customize\config.

The final configuration is the combination of all files. This combination follows the rule, that the values of the standard ECTR file are overwritten by the values in the other files.

For further details about this topic please refer to the manuals for SAP Engineering Control Center.

Within the ECTR configuration file “default.txt” (in <ECTR installation directory>\application\cat\customize\config) the following settings need to be defined:

plm.document.checkout.posSortf.CAT= D;C;R;Y;L;d;c;r;y;l

plm.control.applType.WsAppl.CAT = <definierte Workstation Applikation für CATIA- Originale>

plm.control.empty.dtype.<Document Type des CATIA-Dtype>=<DType für den Dokumenttyp>

plm.attributes.updateAfterCheckOutView.CAT = true

plm.doc.checkout.prevent.update.for.loaded.CAT=true

plm.adv.clone.renamerProgram.cat = @PLM_BINDIR_CAT@\\renamer3cat.cmd

plm.attributes.useCaseSensitiveNames = true

plm.check.environment.CAT = true

plm.control.waitForSessionInMs.cat = 15000

plm.structure.application.init.strategy.levels.CAT=1


ECTRV5



plm.control.partnameRules.resolveInSap.CAT=true

plm.bom.createAtCheckin.CAT = false

In addition the existence of the following settings within the general “Default.txt” of ECTR (located in <ECTR installation directory>\customize\config) needs to be checked and modified if necessary:

plm.kpro.storageCateg.default = <Default storage category for CATIA-Originals>

plm.kpro.storageCateg.lastUsedDocument < Default storage category for CATIA-Originals >

6.1.2 Customizing within SapLogon.txt

Within the ECTR configuration file “SapLogon.txt” (in <ECTR installation directory>\customize\config) the connection data for the SAP server(s) are maintained.

6.1.3 Customizing within System-Default.txt

The file System-Default.txt is located in <ECTR installation directory>\basis\config.

In order to use the fast checkout routines of ECTR (the so called URL checkout), this variable should be set:

plm.doc.checkouturls = true

6.1.4 Customizing within menu.guidef and menu_macros.txt

This chapter describes the changes for the file menu.guidef and menu_macros.txt (both in <ECTR installation directory>\customize\config) so certain commands are available.

Important:

The changes described here will only work if combined with changes applied to the dtype.xml as described in the following chapter. If those changes are incomplete, the menu setup will be malfunctioning.

Don’t use the tab key within menu.guidef and menu_macros.txt, only use blanks (!). Also use blanks for indents, as they are relevant as well. Please also check the first block within menu.guidef.

Firstly the macro definitions are enhanced. These need to be appended to the file menu_macros.txt (in <ECTR installation directory>\customize\config)


ECTRV5



? LAUNCH_APPL_CAT = fnc.launch.generic.file(applications/cat/basis/sys/win/bin/start_application_cat.exe) # -------------------------------------------------------------------------------------- #menu definition of CAT ? DOC_DOC_CAT = mnu.flyout.doc_doc = fnc.doc.checkout = ----------------------------- = fnc.doc.checkout(view) = fnc.doc.cache.update = ----------------------------- = fnc.doc.checkout.cancel = fnc.doc.copy.as = fnc.doc.change.multi = fnc.doc.delete = ----------------------------- = fnc.api.generic2(VE_CONVERSION) = fnc.generate.monolith = ----------------------------- = fnc.doc.display = fnc.doc.change = ----------------------------- = ? DOC_WUI ? DOC_GENERAL_CATN = fnc.doc.open.fast.view = fnc.doc.open.fast.edit = ----------------------------- = fnc.doc.status.change = fnc.doc.new.version

The following sections need to be added to the file menu.guidef (in <ECTR installation directory>\customize\config), so that the menu setup for CATIA documents is correct (for leading as well as depending document).

# Master documents (function group CATM) # Desktop context toolbar + om.custom.tool.DOC.CATM.ctx_desk = ? DOC_MASTER_TOOLBAR_DESK = ----------------------------- = ? DOCUMENT_3D_VIEWING = fnc.object.refresh # ObjectBrowser context toolbar + om.custom.tool.DOC.CATM.ctx_ob = ? DOC_MASTER_TOOLBAR_OBR = ----------------------------- = ? DOCUMENT_3D_VIEWING = fnc.object.refresh = fnc.send.to.AC


ECTRV5



# Document popup menu + om.popup.menu.DOC.CATM = ? DOC_GENERAL = ----------------------------- = ? DOC_DOC_CAT = ? DOC_MAT = ? DOC_BOM = ? DOC_VIEW = ? DOC_COLLAB = ? DOC_ACC = ? DOC_ALSO = ? DOC_TEMP = ----------------------------- = ? CLPBRD_REFRESH_DOC + om.popup.menu.DOCPOS.CATM = ? DOC_GENERAL = ----------------------------- = ? DOC_DOC_CAT = ? DOC_MAT = ? DOC_BOM = ? DOC_COLLAB = ? DOC_ACC = ? DOC_ALSO = ? DOC_TEMP = ----------------------------- = ? CLPBRD_REFRESH_DOC = fnc.doc.reload #commands for Clone++ for CATIA documents + om.popup.menu.CLONEPOS.CATM = 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.option.INSERT_OPTION = fnc.doc.clone.option.REPLACE_OPTION = fnc.doc.clone.option.DELETE_OPTION = ----------------------------- = fnc.clpbrd.delete = fnc.doc.reload # Active list context toolbar definition for documents # behaviour on double click om.popup.menu.DOC.CATM.function = fnc.doc.open.fast.view # -------------------------------------------------------------------------------------- # NonMaster documents (function group CATN) # Desktop context toolbar


ECTRV5



+ om.custom.tool.DOC.CATN.ctx_desk = ? DOC_MASTER_TOOLBAR_DESK = ----------------------------- = ? DOCUMENT_3D_VIEWING = fnc.object.refresh # ObjectBrowser context toolbar + om.custom.tool.DOC.CATN.ctx_ob = ? DOC_MASTER_TOOLBAR_OBR = ----------------------------- = ? DOCUMENT_3D_VIEWING = fnc.object.refresh # Document popup menu + om.popup.menu.DOC.CATN = ? DOC_GENERAL_CATN = ----------------------------- = ? DOC_DOC_CAT = ? DOC_MAT = ? DOC_BOM = ? DOC_VIEW = ? DOC_COLLAB = ? DOC_ACC = ? DOC_ALSO = ? DOC_TEMP = ----------------------------- = ? CLPBRD_REFRESH_DOC + om.popup.menu.DOCPOS.CATN = ? DOC_GENERAL_CATN = ----------------------------- = ? DOC_DOC_CAT = ? DOC_MAT = ? DOC_BOM = ? DOC_COLLAB = ? DOC_ACC = ? DOC_ALSO = ? DOC_TEMP = ----------------------------- = ? CLPBRD_REFRESH_DOC = fnc.doc.reload #commands for Clone++ for CATIA documents + om.popup.menu.CLONEPOS.CATN = 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.option.INSERT_OPTION = fnc.doc.clone.option.REPLACE_OPTION = fnc.doc.clone.option.DELETE_OPTION = ----------------------------- = fnc.clpbrd.delete = fnc.doc.reload # Active list context toolbar definition for documents


ECTRV5



# behaviour on double click om.popup.menu.DOC.CATN.function = fnc.doc.open.fast.view # CAD parts with existing DIRs (SOB): + om.popup.menu.SOB.CATM = fnc.structure.view.application.generic(sap_set_displayed) = fnc.structure.view.application.generic(sap_checkout) = fnc.structure.view.application.generic(sap_save_checkin) = fnc.structure.view.application.generic(sap_save) = fnc.structure.view.application.generic(sap_cancel) = fnc.structure.view.application.generic(sap_import) = fnc.structure.view.application.generic(sap_save_as_new_version) + om.popup.menu.SOB.CATN = fnc.structure.view.application.generic(sap_set_displayed) = fnc.structure.view.application.generic(sap_checkout) = fnc.structure.view.application.generic(sap_save_checkin) = fnc.structure.view.application.generic(sap_save) = fnc.structure.view.application.generic(sap_cancel) = fnc.structure.view.application.generic(sap_import) = fnc.structure.view.application.generic(sap_save_as_new_version)

For further customizing and the available commands please refer to the manuals for SAP Engineering Control Centers.

6.1.5 Customizing within DType.xml

In the CATIA specific ECTR configuration file “DType.xml” (in <ECTR installation directroy>\applications\cat\customize\config) the necessary CATIA DTypes and SAP document types are defined.

Note: With this documentation a complete example for a DType.xml is provided (in the subdirectory Docs). This DType.xml contains the CATIA file types necessary for the CATIA-ECTR interface. They include the leading document definitions as well as the depending document definitions. The used document types need to be changed accordingly.

Important:

At least the following marked entries have to be part of the DType.xml, so that the menu configuration of ECTR can be loaded correctly:

…  <DType type="template" identifier="CATMM" include_template="CATGEN" >  …. <program_options function_group="CATM"/> ….  <DType type="template" identifier="CATNM" include_template="CATGEN">  ….


ECTRV5



<program_options function_group="CATN"/> … </DType>

As an explanation here is an example of a generic definition – valid for all Dtypes – and a definition for all Dtypes – defining master or leading document types – with the most important settings for SAP Engineering Control Center Interface to CATIA V5 marked in red:

  <DType type="template" identifier="CATGEN" include_template="DEFLT" application_type="CAT"

group="CATIAV5"> 

<icon>

<icondef icon_position="1" icon_group="default" icon_identifier="tree/cdesk/cdt_$(SUBTYPE)$(FAMILY)"/>

</icon> <program_options

show_for_create="yes" has_primary_application="yes" dirty_flag="yes" attempt_status_change_on_checkin="yes" dataexchange_rename_on_import="yes" dataexchange_show_for_import="yes">

<copy_as

ignore_wsappl_list="CCF" delete_local_additionals="yes" use_initial_version="yes" copy_material="no" ignore_nm_dtype_list="CNODW" remove_dirty_flag="no">

</copy_as> <new_version

status_list="AC;FR" ignore_wsappl_list="CCF" ignore_nm_dtype_list="CNODW" remove_dirty_flag="no">

</new_version>

</program_options> <nonmaster_options new_version_nonmaster_alone="yes"/> <document_create create_with_SAP_GUI="no"

create_multi_allowed="no" change_to_after_create_status=""


ECTRV5



filename_template_base="$(DOCNUMBER)_$(DOCTYPE)_$(DOCPART)" filename_template_version="">

</document_create> <primary_application primary_workstation_application="CAT"

attribute_section="CATMOD" update_attributes_for_dirty="yes" update_attributes_for_rw="yes" update_attributes_for_ro="no"> <checkout_rules

rename_master_original_at_checkout="no" one_version_in_session_only="no" setrw_for_checkedin="yes" check_references_on_edit="yes" hardlink_in_session="no" read_structure="flag">

</checkout_rules> </primary_application>

</DType>   <DType type="template" identifier="CATMM" include_template="CATGEN" > 

<program_options function_group="CATM" customer_data_section="CATMOD"/>

<document_create document_number_assignment="internal"

initial_document_number="*" document_type="5PA" initial_document_part="000" part_editable="no" initial_document_version="00" version_editable="yes">

</document_create> <material_create material_creation_method="deferred"/> <primary_application

primary_workstation_application="CAT" attribute_section="CATMOD" update_attributes_for_dirty="yes" update_attributes_for_rw="yes" update_attributes_for_ro="no">


ECTRV5



<container_file> <plmfile

extension="ecf" workstation_application="ECF" description="ECtr container file"/>

</container_file> <checkout_rules

rename_master_original_at_checkout="no" one_version_in_session_only="no" hardlink_in_session="no" setrw_for_checkedin="yes">

<checkout_direct>

<plmfile workstation_application="CCF"/> </checkout_direct>

</checkout_rules> <checkin_rules>

<save_direct> <plmfile extension="jpg" workstation_application="EPJ" description="ECtr

Preview (jpeg)"/> <plmfile extension="txt" workstation_application="TXT"

description="$(FILENAME)"/> <plmfile extension="cgr" workstation_application="CCF" description="Cache

CGR"/> <plmfile extension="jt" workstation_application="JT" description="JT"/> <plmfile description="SAP 3D Monolithic RH" workstation_application="RHM"

filename_pattern=".*_mono\.rh"/> <plmfile description="SAP 3D Monolithic VDS" workstation_application="RHM"

filename_pattern=".*_mono\.vds"/> <plmfile description="SAP 3D Preview RH" workstation_application="RH"

extension="rh"/> </save_direct> <ignore>

<plmfile extension="bak"/> <plmfile extension="tmp"/> <plmfile extension="xjt"/> <plmfile extension="bat"/> <plmfile filename_pattern="plm_metainf-sap.*"/> <plmfile filename_pattern="plm_metainf-cad.*"/>

</ignore> <delete_in_sap>

<plmfile workstation_application="EPJ"/> <plmfile workstation_application="SGO"/> <plmfile workstation_application="EVI"/> <plmfile workstation_application="RH"/> <plmfile workstation_application="RHM"/> <plmfile extension="cgr" delete_always="yes"/>

</delete_in_sap> <delete_in_session>


ECTRV5



<plmfile extension="jpg"/> <plmfile extension="gif"/> <plmfile extension="bat"/> <plmfile extension="cgr"/> <plmfile extension="rh"/> <plmfile extension="vds"/>

</delete_in_session> <scripts> </scripts>

</checkin_rules>

</primary_application> <allowed_nonmaster DType="CNOCG" max_count="999" /> <allowed_nonmaster DType="CNOV4" max_count="999" /> <allowed_nonmaster DType="CNODW" max_count="999" /> <allowed_nonmaster DType="CNOPR" max_count="999" /> <allowed_nonmaster DType="CNOPA" max_count="999" /> <allowed_nonmaster DType="CNOAN" max_count="999" /> <allowed_nonmaster DType="CNOPC" max_count="999" /> <allowed_nonmaster DType="VWINM" max_count="999"/>

</DType>

…

For further customizing and the available commands please refer to the manuals for SAP Engineering Control Centers.

6.1.5.1 Customizing within DType.xml for cgrs und V4 Models

In order to support cgr-files and V4-models with SAP Engineering Control Center Interface to CATIA V5 as primary originals, the files cannot be renamed. Therefore the following DType settings need to be made:

<document_create

create_with_SAP_GUI="no" create_multi_allowed="no" change_to_after_create_status="" rename_template_filename="no">

… </document_create> … <program_options

customer_data_section="CAT_MA"> <new rename_master_original="no" />

</program_options>


ECTRV5



6.1.6 Customizing within plm_setenv.bat respectively StartApplicationCat.xml

The file plm_setenv.bat is no longer in the current version of SAP ECTR Interface to CATIA

V5. Instead of it the configuration file StartApplicationCat.xml located in <ECTR installation

directory>\applications\cat\customize\config\integration is used.

In this file all CATIA-installation paths and starting parameters have to be configured, in case

different CATIA versions and environments are used.

The factory default always uses the last registered CATIA, this means the CATIA which is

executed when double clicking on a CATIA document in Windows. This CATIA does not

normally have an environment.

Note:

In case it is not possible for of SAP ECTR Interface to CATIA V5 to determine the CATIA

environment, e.g. when starting via Registry or double clicking on a CATIA document in

Windows, the environment is considered to be UNDEFINED. A corresponding environment

needs to be defined within start_application_cat.xml. If this is not the case or an environment

is used which is not part of the aforementioned xml file, SAP ECTR interface to CATIA V5

will not work properly with CATIA.

Here is an example for CATIA V5-6 R2014 aka R24 with the lines to be configured marked in

red:

<listcontainer name="StartCat-Config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ConfigSchem.xsd"> <listcontainer name="CommandDef"> <listcontainer name="R22-ECTR CATIA"> <stringelement name="ApplicationName" value="cnext.exe"/> <stringelement name="StartApplication" value="C:\Program Files\Dassault

Systemes\B22\win_b64\code\bin\CATSTART.exe"/> <stringelement name="ApplicationParameter" value="-run

"CNEXT.exe" -env CATIA_P3.V5-6R2012.B22 -direnv "C:\ProgramData\DassaultSystemes\CATEnv" -nowindow"/>

<stringelement name="Type" value="WaitForReady"/> <stringelement name="ApplicationWindowTitle" value=""/> </listcontainer> <listcontainer name="R22-ECTR CATIA regsvr"> <stringelement name="ApplicationName" value="cnext.exe"/> <stringelement name="StartApplication" value="C:\Program Files\Dassault

Systemes\B22\win_b64\code\bin\CNEXT.exe"/> <stringelement name="ApplicationParameter" value="-Regserver"/> <stringelement name="Type" value="WaitForTerminate"/> <stringelement name="ApplicationWindowTitle" value=""/> </listcontainer> <listcontainer name="R24-ECTR CATIA"> <stringelement name="ApplicationName" value="cnext.exe"/>


ECTRV5



<stringelement name="StartApplication" value="C:\Program Files\Dassault Systemes\B24\win_b64\code\bin\CATSTART.exe"/>

<stringelement name="ApplicationParameter" value="-run "CNEXT.exe" -env CATIA.V5-6R2014.B24 -direnv "C:\ProgramData\DassaultSystemes\CATEnv" -nowindow"/>

<stringelement name="Type" value="WaitForReady"/> <stringelement name="ApplicationWindowTitle" value=""/> </listcontainer> <listcontainer name="R24-ECTR CATIA regsvr"> <stringelement name="ApplicationName" value="cnext.exe"/> <stringelement name="StartApplication" value="C:\Program Files\Dassault

Systemes\B24\win_b64\code\bin\CNEXT.exe"/> <stringelement name="ApplicationParameter" value="-Regserver"/> <stringelement name="Type" value="WaitForTerminate"/> <stringelement name="ApplicationWindowTitle" value=""/> </listcontainer> <listcontainer name="ECTR net"> <stringelement name="ApplicationName" value="SAP Engineering Control

Center Interface to CATIA V5.exe"/> <stringelement name="StartApplication" value="SAP Engineering Control

Center Interface to CATIA V5.exe"/> <stringelement name="ApplicationParameter" value=""/> <stringelement name="Type" value="WaitForReady"/> <stringelement name="ApplicationWindowTitle" value=""/> <boolelement name="SendKey" value="true"/> </listcontainer> </listcontainer> <listcontainer name="RelEnvDef" > <listcontainer name="V5R22" > <listcontainer name="CATIA_P3.V5-6R2012.B22"> <stringelement name="CommandName" value="R22-ECTR CATIA"/> <stringelement name="PreCommandName" value="R22-ECTR CATIA

regsvr"/> <stringelement name="PostCommandName" value="ECTR net"/> </listcontainer> </listcontainer> <listcontainer name="V5R24" > <listcontainer name="CATIA.V5-6R2014.B24"> <stringelement name="CommandName" value="R24-ECTR CATIA"/> <stringelement name="PreCommandName" value="R24-ECTR CATIA

regsvr"/> <stringelement name="PostCommandName" value="ECTR net"/> </listcontainer>

<listcontainer name="UNDEFINED"> <stringelement name="CommandName" value="FromReg CATIA"/> <stringelement name="PreCommandName" value="FromReg CATIA

regsvr"/> <stringelement name="PostCommandName" value="ECTR net"/> <boolelement name="ShowInSelectBox" value="false"/>


ECTRV5



</listcontainer> </listcontainer> </listcontainer> <listcontainer name="Default"> <stringelement name="Release" value="Registered CATIA"/> <stringelement name="Environment" value="Registered CATIA"/> </listcontainer> <listcontainer name="Options"> <stringelement name="ConfigNotFound" value="selection"/> <boolelement name="ApplicationAutomationMod" value="true"/> <boolelement name="ApplicationParameterMod" value="false"/> <stringelement name="ApplicationKeyStroke" value="${F11}"/> <integerelement name="ApplicationMaxWait" value="240" /> <integerelement name="ApplicationWaitAfterStart" value="10" /> <boolelement name="AbortOnUnequalVersion" value="false" /> <boolelement name="CatBusyCheck" value="true" /> <stringelement name="CatBusyEnvironmentName" value="CAD_BUSY" /> <stringelement name="CatBusyMutexNewName" value="CEN_CAD_BUSY_MUTEX"

/> <stringelement name="Language" value="de" /> <stringelement name="LanguagePath" value="language" />

<boolelement name="ShowProgressBar" value="true"/> <stringelement name="LaunchApplicationName" value="cnext.exe"/> <stringelement name="LaunchApplication" value="selection"/> <integerelement name="ApplicationWaitAfterLoaderTerminated" value="10"/> </listcontainer> </listcontainer>

Note:

To get the correct values for “StartApplication” and “StartApplicationParameter” in section

CommandDef it’s useful to look up the properties of Windows-links to CATIA in Windows

starting menu. On register page link in field target you should normally find the correct

starting parameters for CATIA.

Further information on “StartApplicationCAT.exe” can be found in chapter 8 of

“Customizing.pdf”.


ECTRV5



7 Customizing for SAP Engineering Control Center Interface to CATIA

The SAP Engineering Control Center Interface to CATIA V5 requires no further settings for a default installation. For special settings, like data-mapping or certain system localizations, please refer to the customizing manual for SAP Engineering Control Center Interface to CATIA V5.


ECTRV5



8 Appendix

8.1 Copyright

© 2014-2019 Cenit AG. All rights reserved.

This publication or parts of this publication may not be reproduced or transmitted in any form or for any purpose without the express permission of Cenit AG.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or a SAP affiliated company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

For additional trademark information and notices refer to

http://www.sap.com/corporate-de/legal/copyright/index.epx.

8.2 Open Source Software

This product contains software, developed by the Apache Software Foundation (http://www.apache.org/).

Parts of this software were developed by the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This software contains source code, derived from the RSA Data Security Inc. MD5 Message-Digest-algorithm, among different modifications from Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc. (Bellcore).

For processing of regular expression this software is using the PCRE library package, an Open Source Software, developed by Philip Hazel and is under the copyright of the University of Cambridge England. The original software is available at:

ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

8.3 Original Apache 2.0 License

The original text of the used Apache licenses (Version 2.0 from January 2004) for this product can be found:

http://www.apache.org/licenses/.

http://www.sap.com/corporate-de/legal/copyright/index.epx

ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

http://www.apache.org/licenses/


ECTRV5



9 Illustrations

Illustration 1: Customizing (entry screen) ..............................................................................10 Illustration 2: Customizing ....................................................................................................11 Illustration 3: Customizing the document types 5PR, 5PA and 5DR .....................................12 Illustration 4: Document type example 5PR ..........................................................................13 Illustration 5: Document type example 5PA ..........................................................................14 Illustration 6: Document type example 5DR ..........................................................................15 Illustration 7: Status Network for 5PR ...................................................................................16 Illustration 8: Status Network for 5PA ...................................................................................17 Illustration 9: Status Network for 5DR ...................................................................................18 Illustration 10: Entry Point for Definition ................................................................................19 Illustration 11: Define New Status .........................................................................................20 Illustration 12: Status ............................................................................................................20 Illustration 13: Example for Previous Status .........................................................................21 Illustration 14: Necessary Settings for the WS Application ....................................................22 Illustration 15: Further Required Settings for the WS Application ..........................................23 Illustration 16: Define the WS Application CCF .....................................................................24 Illustration 17: CAD Desktop Customizing ............................................................................25 Illustration 18: CAD-Systems ................................................................................................26 Illustration 19: Group maintenance .......................................................................................27 Illustration 20: Explosion Scenario ........................................................................................28 Illustration 21: Explosion rules BOM_DERIVE ......................................................................29 Illustration 22: Customizing entries via V_CDESK_C_EXPLC ..............................................29 Illustration 23: Customizing new entries ...............................................................................30 Illustration 24: Customizing entries RES4 and SORTF .........................................................30 Illustration 25: Customizing the values in V_CDESK_C_EXPLFA ........................................31 Illustration 26: Explosion rules CAD_LOAD ..........................................................................32 Illustration 27: Explosion rules CTX_VIEW ...........................................................................33 Illustration 28: Content of the target directory .......................................................................34 Illustration 29: Final content of the target directory ...............................................................35