As of: 06/2021
SAP product data management
integration to Teamcenter
Installation and Configuration Guide
Preface
SAP product data management integration to Teamcenter
Installation and Configuration Guide
Content responsibility:
SAP SE, 06/2021
Copyright © SAP SE 2004–2021. All rights reserved.
SAP SE Logo is a registered trademark of SAP SE.
SAP product data management integration to Teamcenter 1.0.3.0
[10000050970 / EHB / ENU / V:13]
Neither this document nor parts thereof may be reproduced or forwarded without the express
permission of SAP SE.
Technical and functional specifications are subject to change without notice.
The information contained in this document may be changed or supplemented without previous
announcement.
Inform us by sending an e-mail if you have questions or hints on this document. SAP SE does not
guarantee that this document is free of errors.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 2 of 20
Preface
Preface
Thank you for your interest in our software. This guide explains the installation and configuration of
SAP product data management integration to Teamcenter.
Directory Names
We use the default settings including the directory names created by the standard installation in
explanations. If you are using different names, you must replace these accordingly.
Since you can choose any installation directory, we use the synonym <DJM_INSTALLATION_DIR>.
Your Comments are Always Welcome
We greatly appreciate your remarks and your criticism as a reader of this guide. Your opinion helps us
to continuously improve the software as well as the documentation.
SAP SE
Neutrottstr. 16
69190 Walldorf
Tel.: +49 (0) 62 27/ 34 - 0
Internet: www.sap.com
Registered trademarks
Windows, Microsoft Word, Microsoft Excel, Microsoft PowerPoint and Microsoft Office are registered
trademarks of the Microsoft Corp.
SAP and SAP PLM are registered trademarks of the SAP SE.
All additional program names and terms used in this manual are possibly also registered trademarks
of the manufacturer and are not allowed to be used in a commercial or another modality. Errors
excepted.
SAP SE makes no representations or warranties of any kind expressed or implied with regard to
completeness, accuracy, reliability, suitability or availability of the information, products, services, or
related graphics contained herein.
In no event will SAP SE be liable for any loss or damage including without limitation, indirect or
consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits
arising out of or in connection with the use of the information contained herein.
No part of this manual may be reproduced or copied in any kind of form (print, copy or storage and/or
distribution in electronic form) without written approval of SAP SE.
SAP SE improves their products constantly in order to offer you a maximum of convenience. Thus, we
kindly ask you for your understanding that in some cases the content of the manual may differ from
the product.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 3 of 20
Table of contents
Content
1
Introduction .................................................................................................................................... 5
1.1
System Architecture ................................................................................................................ 5
1.1.1 Components – SAP product data management integration to Teamcenter ....................... 5
1.1.1.1
DTP – DSC T4EA Plug-In ........................................................................................... 5
1.1.1.2
DJM – DSC Job Messaging ........................................................................................ 6
1.1.1.3
DWV – DSC Web View ............................................................................................... 6
2
System Requirements.................................................................................................................... 7
2.1
Third-Party Software ................................................................................................................ 7
2.2
SAP System............................................................................................................................. 7
2.2.1 SAP Service User ................................................................................................................ 7
2.2.2 SAP Connection Data .......................................................................................................... 8
2.2.3 SSO Token Generation ....................................................................................................... 8
2.2.4 SAP Server Groups ............................................................................................................. 8
2.3
Teamcenter.............................................................................................................................. 8
3
Installation ...................................................................................................................................... 9
3.1
PostgreSQL Database Management System ......................................................................... 9
3.2
Installation Files ....................................................................................................................... 9
3.3
Services ................................................................................................................................. 10
3.4
DTP – DSC T4EA Plug-In ..................................................................................................... 10
3.5
DWV RAC Plug-In ................................................................................................................. 11
3.5.1 Installation .......................................................................................................................... 11
3.5.2 Operating System Settings ................................................................................................ 12
3.6
Configuring the firewall .......................................................................................................... 12
4
Configuration ................................................................................................................................ 13
4.1
DJM ....................................................................................................................................... 13
4.1.1 Configuration File............................................................................................................... 13
4.1.2 Monitoring .......................................................................................................................... 13
4.2
SAP PDMI.............................................................................................................................. 13
4.2.1 Establishment of a RFC Connection ................................................................................. 13
4.2.2 Monitoring .......................................................................................................................... 13
4.3
Teamcenter............................................................................................................................ 14
4.3.1 Gateway Service................................................................................................................ 14
4.3.2 Workflows .......................................................................................................................... 16
4.3.2.1
Workflow Templates .................................................................................................. 16
4.3.2.2
Workflow Tasks for Data Transfer ............................................................................. 16
5
Update ........................................................................................................................................... 18
5.1
Update of Version 1.0.1.0, 1.0.2.0, or 1.0.2.2 to Version 1.0.3.0 .......................................... 18
5.2
Update from version 1.0.0.0 to version 1.0.3.0 ..................................................................... 18
6
Troubleshooting ........................................................................................................................... 19
6.1
No SAP Object Data in DWV................................................................................................. 19
6.2
DWV: Problems with Plug-In Execution ................................................................................ 19
7
Support .......................................................................................................................................... 20
© DSC Software AG
SAP product data management integration to Teamcenter
Page 4 of 20
Introduction
1
Introduction
SAP product data management integration to Teamcenter integrates data from Teamcenter into
SAP.
The product is not executable independently and requires the following two products:
 SAP product data management integration to SAP S/4HANA - Abbreviation PDMI
 Siemens Teamcenter Gateway for Enterprise Applications - Abbreviation T4EA
SAP product data management integration to Teamcenter reads data from Teamcenter and
transmits the data to PDMI via RFC function calls. The interface displays the most important data from
SAP directly within Teamcenter.
PDMI processes the data transmitted, ensures persistence and monitoring, and creates or updates
SAP objects.
1.1
System Architecture
The following picture details the system architecture:
1.1.1
1.1.1.1
Components – SAP product data management integration to
Teamcenter
DTP – DSC T4EA Plug-In
The DSC T4EA Plug-In (DTP) is a set of scripts, which are called by Teamcenter Gateway for
Enterprise Applications (T4EA) and its Teamcenter Gateway Service. The scripts read data from the
Teamcenter database and hand the data over to DSC Job Messaging (DJM).
 DTP consists of DSC-specific configurations for T4EA to manage the retrieval of Teamcenter data.
 DTP utilizes the T4EA-Framework, exports data from Teamcenter and transfers it to the software
main component DJM (DSC Job Messaging).
© DSC Software AG
SAP product data management integration to Teamcenter
Page 5 of 20
Introduction
1.1.1.2
DJM – DSC Job Messaging
The software main component receives Teamcenter data, transforms the data, and sends it to the
SAP PDMI framework.
 Receives events from the Teamcenter Gateway Service or the DTP scripts and stores them as a
job in a database. The events contain Teamcenter data and processing instructions.
 The Data Package Transformer processes the events, creates SAP data packages for the
transfer to SAP, and calls function modules in SAP via the SAP JCo Client, which triggers the data
processing in SAP (PDMI).
 Provides a file system data storage for Teamcenter data files.
 Provides transfer details to Teamcenter frontend.
 Provides a JCo server implementation to receive external events from SAP.
 Manages the provision of data from SAP in Teamcenter.
1.1.1.3
DWV – DSC Web View
DSC Web View provides the user with a new view in Teamcenter with two different areas: On the one
hand, SAP object data is displayed, on the other hand, within the transfer details, the current status
information concerning the processing state of jobs in the DJM can be seen.
The DWV RAC Plug-In consists of a .jar file, that needs to be installed in the Teamcenter RAC on
the user's computer.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 6 of 20
System Requirements
2
System Requirements
The system requirements are available in SAP Note 2962886 - Release Strategy and Maintenance
information for SAP product data management integration to Teamcenter:
https://launchpad.support.sap.com/#/notes/2962886
The SAP Java Connector (SAP JCo) is part of SAP product data management integration to
Teamcenter and does not have to be installed separately.
2.1
Third-Party Software
SAP product data management integration to Teamcenter uses third-party software for the
components DJM, DWV, and the DWV RAC Plug-In.
Further information is available in the distribution within the .zip file in the license folder.
The service DJM also requires a PostgreSQL 12.x database, that is installed according to chapter
3.1 PostgreSQL Database Management System.
2.2
2.2.1
SAP System
SAP Service User
An SAP service user is required in order to use the PDMI services and it needs to have the following
authorizations:
 SAP_TST_AGENT_RFC
 SAP_BR_PDMI
 Engineering roles for the managing SAP objects, e.g. Document, Change Number, Material – for
creating, changing, and deleting
Either generate authorization roles from the template SAP_AIFECC_ALL or assign the authorization
objects from the template SAP_AIFECC_ALL to an existing authorization role.
In the following, the SAP service user is referred to as SAP_PDMI_USER.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 7 of 20
System Requirements
2.2.2
SAP Connection Data
For the communication between DJM and the SAP system, connection data is necessary, such as
described in the following:
Description
Example Value
192.168.100.2
IP address or DNS name
of the SAP system
or
Client number
100
Note
subdomain.domain.net
DE
or
Language
EN
SAP router address
/H/110.108.204.178/H/15
3.184.106.130/S/3300
System number
00
SAP system name
Required if the SAP system is
accessible via an SAP router
ABC
Three-digit system ID of the
SAP system
SAP_PDMI_USER name
pdmi_user_name
Freely selectable
SAP_PDMI_USER
password
pdmi_user_password
Freely selectable
SAP Gateway Server port
3300
Consists of the value 33 plus
the SAP system number
2.2.3
SSO Token Generation
Check the following parameters in SAP transaction RZ11:
login/create_sso2_ticket = 2 (Token without certificate)
login/accept_sso2_ticket = 1 (Accept SSO token)
Check in SAP transaction SSO2 (host name = current SAP system), if the login ticket can be accepted
and generated.
NOTE
The SSO token generation has no connection with SAP client certificates.
2.2.4
SAP Server Groups
Set the server group "parallel_generators" in the SAP transaction RZ12.
2.3
Teamcenter
For Teamcenter, the version 11.x, 12.x or 13.x is required. For T4EA, the Teamcenter Environment
Manager enhancement Teamcenter Gateway for Enterprise Applications/Integration for Rich
Client from Active Integration Gateway from version 19.2 or higher is required.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 8 of 20
Installation
3
3.1
Installation
PostgreSQL Database Management System
Install and set up the PostgreSQL database management system | PostgreSQL-DBMS in version
12.x. according to the official PostgreSQL documentation.
NOTE
We recommend creating a separate user that has all rights, such as delete, edit, read, for only the
DJM database that is described in the following:
Create the database for DJM in the PostgreSQL DBMS, for example with the name djm_db, with a
separate user, for example with the name djm_db_user and a separate password, e.g.
djm_db_user_pw.
The following settings are important for configuration in chapter 4 Configuration:
Parameter
Database name
Example Value
Configuration Variable in the DJM
Configuration File
djm_db
Port number of the
PostgreSQL
database
management
system
5432
IP address / DNS
name of the
computer with the
PostgreSQL DBMS
192.168.100.1 or
subdomain.domain.net
User name
djm_db_user
spring.datasource.username
Password
djm_db_user_pw
spring.datasource.password
3.2
spring.datasource.url:
jdbc:postgresql://192.168.100.1
:5432/djm_db
Installation Files
A .zip file is provided to install the required services. It contains the following:
 the DJM service to start it on the Teamcenter server
 the DWV RAC plug-ins
 the DTP scripts and DTP preference files
© DSC Software AG
SAP product data management integration to Teamcenter
Page 9 of 20
Installation
3.3
Services
To start the services for DJM, unpack the .zip file on a server to the directory
<DJM_INSTALLATION_DIR>.
After unpacking, register the service via the file tci_ctl.bat. This file needs to be executed within
the Windows command line with administrator rights.
 In the command line, execute the following command:
<DJM_INSTALLATION_DIR>\tci_ctl.bat register
Afterwards, the service can be started, stopped, or status information can be retrieved.
 Start: <DJM_INSTALLATION_DIR>\tci_ctl.bat start
 Stop: <DJM_INSTALLATION_DIR>\tci_ctl.bat stop
 Retrieve status information: <DJM_INSTALLATION_DIR>\tci_ctl.bat status
If the service has already been registered, it can also be deregistered. To deregister it, execute the
following command in the command line: <DJM_INSTALLATION_DIR>\tci_ctl.bat unregister
As an alternative to the command functions for starting and stopping the services, the Windows Task
Manager can also be used. For this, start the Task Manager, select the Services tab and start or stop
the service tci-djm-service.
NOTE
For each SAP system, a separate DJM service is required. This is the prerequisite for the use of
connections to different SAP systems.
3.4
DTP – DSC T4EA Plug-In
NOTE
The freely selectable names of the SAP PDMI Connection and the SAP PDMI Connection Alias
need to be defined at first, as they are used in the following for several configuration steps. For
example:
 SAP PDMI Connection: DSC_SAP_PDMI_CONNECTION
 SAP PDMI Connection Alias: DSC_SAP_PDMI_ALIAS
For specific object types, further configuration according to T4EA documentation is required for the
following files, before they can implemented:
 t4ea_prefs_DWV.xml
 Defines the DJM connection URLs for the DWV RAC Plug-In
 Replace the following parts in the preference variable
DWV.BASE.URL.[SAP_PDMI_CONNECTION]:
 Replace the parts containing the string [SAP_PDMI_CONNECTION] with the individually
defined name of the SAP PDMI Connection
 Replace the URL http(s)://URL-TO-SAP-PDMI-CONNECTION according to the description
of the field EA System Connection Data in chapter 4.3.1 Gateway Service
 t4ea_prefs_merge_DTP.xml
 Defines all DJM connection names available in Teamcenter
 Replace the following parts in the preference variable T4EA.EaConnections:
 Replace the part containing the string [SAP_PDMI_CONNECTION] with the individually
defined name of the SAP PDMI Connection
© DSC Software AG
SAP product data management integration to Teamcenter
Page 10 of 20
Installation
 t4ea_prefs_overwrite_DTP.xml
 Defines which data and object types are read from Teamcenter and then transferred to DJM
 t4ea_mapping_config.sd
 Defines the DJM connections that are available for the DTP scripts and the corresponding
Credential Alias
 Replace the following parts in the section EA Connection:
 Replace the parts containing the string [SAP_PDMI_CONNECTION] with the individually
defined name of the SAP PDMI Connection
 Replace the parts containing the string [SAP_PDMI_ALIAS] with the individually defined
name of the SAP PDMI Connection Alias
 The edited .xml files are to be imported into the Teamcenter server via Teamcenter RAC to
Standort/Site. The import mode has to be set differently for each file:
 t4ea_prefs_DWV.xml
 Mode: Overwrite default settings
 t4ea_prefs_merge_DTP.xml
 Mode: Merge default settings
 t4ea_prefs_overwrite_DTP.xml
 Mode: Overwrite default settings
 The .sd files are to be copied to the T4EA mapping directory
<ACTIVEINTEGRATION_INSTALLATION_DIR>\gs\var\mmap\t4ea_mapping_config on all
GS servers. In the following, the T4EA mapping directory is referred to as
<DTP_INSTALLATION_DIR>.
 On the Teamcenter Gateway Service user interface, execute the script Generate mapping and
mapping deployment in the tab Form in Mode: Generate Mapping and File Copy.
 The log-in data for DJM, to which the DTP delivers the data, has to be saved according to the
templates in the Gateway Service (GS) as Alias. For further information, see chapter 4.3.1
Gateway Service
 Afterwards, restart the GS.
3.5
3.5.1
DWV RAC Plug-In
Installation
NOTE
The .zip file has already been unzipped to the directory <DJM_INSTALLATION_DIR>.
Step-by-Step Installation Guide:
 The current releases are provided at <DJM_INSTALLATION_DIR>\dwv-rac-plugins.
 Select the version of the DWV RAC Plug-In from the folder according to the Teamcenter
version:
DWV RAC Plug-In
dwv-rac-plugin-tc-11.jar
Teamcenter Version
dwv-rac-plugin-tc-12.jar
12.x
dwv-rac-plugin-tc-13.jar
13.x
© DSC Software AG
11.x
SAP product data management integration to Teamcenter
Page 11 of 20
Installation
 Put the respective .jar file of the DWV RAC Plug-In into the directory
<TC_ROOT>/portal/plugin
 Note: For the installation, it is assumed that <TC_ROOT> is the path (e.g.:
C:\Siemens\Teamcenter) to the local Teamcenter RAC installation.
 Within the directory <TC_ROOT>/portal/registry, run the file genregxml.bat as
administrator. Wait until the process is complete and the window closes automatically.
 For selecting the active connection in Teamcenter RAC:
 If only one T4EA connection exists, the active connection is automatically assigned (Default).
 If several T4EA connections exist, the desired connection can be selected via the T4EA
Gateway menu in Teamcenter. This is set as an active connection.
 If the desired connection has not been selected via the T4EA Gateway menu, the first
connection from the list T4EA.Ea connections is used as the active connection.
3.5.2
Operating System Settings
On each computer, select the following setting via the control panel:
Internet Options
> Security
> Trusted sites
> Sites
> Add this website to the zone:
http(s)://djm-server, according to
EA System Connection Data in chapter 4.3.1 Gateway
Service
If SSL is not used (or http is used) for the DJM URL, uncheck the field Require server verification
(https:) for all sites in this zone.
3.6
Configuring the firewall
The following network ports are to be considered:
 DJM service port: 8080
 SAP Gateway Server port, e.g. 3300, for details see chapter 2.2.2 SAP Connection Data
 PostgreSQL database: 5432, for details see chapter 3.1 PostgreSQL Database Management
System
The port numbers may differ from the DJM Configuration File
<DJM_INSTALLATION_DIR>\config\djm.config.yml.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 12 of 20
Configuration
4
Configuration
4.1
DJM
Configuration File
4.1.1
The single parameters of the configuration file and their description can be found in the DJM
Configuration File <DJM_INSTALLATION_DIR>\config\djm.config.yml.
Variables, that are already predefined, can be seen as recommendation values. For some variables,
please refer to the respective SAP documentation, if indicated.
4.1.2
Monitoring
Logging of DJM takes place locally in the folder <DJM_INSTALLATION_DIR>/logs.
There are various log levels that can be configured.
 DEBUG
 INFO
 WARN
 ERROR
Depending on the setting, more (DEBUG) or less (ERROR) information is logged.
The configuration is to be set in the file <DJM_INSTALLATION_DIR>/config/djm.config.yml.
Further information is available in the DJM Configuration File.
4.2
SAP PDMI
Further information and documentation concerning SAP Product Data Management Integration to SAP
S/4HANA are available via SAP Help Portal:
https://help.sap.com/viewer/product/SAP_PRODUCT_DATA_MANAGEMENT_INTEGRATION_TO_S
AP_S_4HANA.
4.2.1
Establishment of a RFC Connection
Define a new TCP/IP connection with a Program-ID of your choice within the SAP transaction SM59.
This Program-ID is to be set in the DJM Configuration File within the variable
sap.jco.server.progid.
4.2.2
Monitoring
For starting the PDMI tools, the SAP transaction /AIFECC/TOOLS is to be executed.
Within the PDMI tools, two ´PDMI Cockpits can be opened:
 Integration Cockpit
 Data and status information of the single transmissions can be seen here.
 Configuration Cockpit
 The single PDMI instances can be configured and server information of DJM can be seen here.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 13 of 20
Configuration
4.3
4.3.1
Teamcenter
Gateway Service
Via the Gateway Service user interface, the following settings can be made:
 EA-Connections
 Execute the script EA Connection Test with Parameter/Action „Define and Store
Credentials Alias” and set the following values:
Field
Value
Credential Alias
Name of the Credential
Alias defined in the file
t4ea_mapping_config.
sd
Destination
EA System
Connection Data
Name of the PDMI
connection defined in the
file
t4ea_prefs_merge_DTP
.xml
URL to the DJM server
defined in the file
t4ea_prefs_DWV.xml
Note
Note: Use the individually defined name of
the SAP PDMI Connection from chapter
3.4 DTP – DSC T4EA Plug-In here.
The URL of the DJM server consists of the
IP address / DNS name and the defined
port number of the DJM server. The port
number is configured in the DJM
Configuration File djm.config.yml (see
chapter 4.1.1 Configuration File), within the
variable server.port.
Example:
http://192.168.100.1:9876
User
Name of the user that is
defined in the DJM
Configuration File
djm.config.yml (see
chapter 4.1.1
Configuration File), in the
variable
spring.security.user
.name.
Password
Password of the user that
is defined in the DJM
Configuration File
djm.config.yml (see
chapter 4.1.1
Configuration File), in the
variable
spring.security.user
.password.
Language
EN
Overwrite
Yes
 Execute the script EA Connection Test and make sure that a connection can be established.
 Database user
 Define the database user that is used for executing workflows in the background.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 14 of 20
Configuration
 Execute the script Tc database connection test. For this, select in the tab Form the Action
„Define Default Credentials Alias“ with the following key value pairs:
Field
Value
Note
User
<USERNAME>
User name of an existing Teamcenter user
with DBA rights.
Password
<PASSWORD OF THE
USER>
Group
-
Can be left empty. If no value is entered,
the group is automatically read from the
database.
Overwrite
yes
Overwrites all existing settings for the
entered user.
 Job agent
 With the Job agent, the workflows in the background can be executed.
 In the user interface of the Teamcenter Gateway Service, navigate to the menu Configuration,
select the tab Job agent and add a new Job agent.
 Server instances
 Configure the server instances for the retransfer to Gateway Service.
 Define a new server instance in the GS and set the following values:
Field
Value
Note
Name
Random
Port
E.g. 11309
Only displayed in the GS
Context-sensitive, according to the
network configuration of Teamcenter
Interface Binding
Random
IP Stack
IPv4 + IPv6
HTTP
Protocol
Basic Authentication
Encryption
Function Binding
On
Off (default)
On
Off (default)
::dtp::import::jobcr
eate
If an authentification of DJM to
Teamcenter is supposed to be executed,
both configuration variables
djm.teamcenter.restclient.username and
djm.teamcenter.restclient.password are to be set in the
DJM Configuration File.
If an encryption via SSL is supposed to be
used, the configuration variable
djm.teamcenter.restclient.ssl.trust-store-path is to
be set with a path to the Teamcenter SSL
certificate or the configuration variable
djm.teamcenter.restclient.ssl.allow-all-sslcertificates in the DJM Configuration
File is to be set to true, so that all
certificates are accepted.
Function in the DTP scripts that manages
the import of SAP objects.
Afterwards, restart the Gateway Service.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 15 of 20
Configuration
4.3.2
Workflows
For transferring data from Teamcenter to SAP, so-called workflows are necessary in Teamcenter.
A detailed description of workflows is available in the Teamcenter Workflow Designer.
4.3.2.1
Workflow Templates
In the installation directory <DJM_INSTALLATION_DIR>\tc-workflows the file
TC_Workflow_Templates.xml can be found, which can be imported into Teamcenter. It provides
different workflow templates for the transfer of Teamcenter objects to SAP, e.g. the objects Item
Revision and BOMView Revision.
For transferring a package for the PEO scenario, use the workflow SAP_TCI_TRANSFER_Package.
If no PEO scenario is used, use the workflow SAP_TCI_TRANSFER_Data for the transfer of data.
NOTE
The delivered workflow templates need to be implemented into customer-specific workflows.
4.3.2.2
Workflow Tasks for Data Transfer
The transfer of Teamcenter objects to SAP within workflow templates takes place via these tasks:
 Starting and completing workflows:
 As a prerequisite for executing the workflows, a start and end signal has to be sent.
 Integrate the Action Handler T4EA-validate-EALogon wit the following parameters into the
workflow via Task - Complete of both tasks T4EA-WF-Start and T4EA-WF-End
Argument
-DTP_DJM_CALL
Value
start
Note
-DTP_DJM_CALL
ready
End signal
fm=data
End signal
Whether the value data or package has to be
set depends on whether the PEO scenario is
used or not. See 4.3.2.1 Workflow Templates.
-DTP_DJM_CALL_
PARAMETER
© DSC Software AG
or
fm=package
Start signal
SAP product data management integration to Teamcenter
Page 16 of 20
Configuration
 T4EA ItemRevision Transfer
 Integrate the Action Handler T4EA-transfer-GenericObject within Task - Complete of a "Do"
task with the following parameters:
Argument
-TargetTypeName
Value
SAPProduct++
-use_EA_system
e.g.
DSC_DJM_CONNECTION
Note
Use the individually defined name of
the SAP PDMI Connection from
chapter 3.4 DTP – DSC T4EA Plug-In
here.
 T4EA BOMViewRevision Transfer
 Integrate the Action Handler T4EA-transfer-GenericObject within Task - Complete of a "Do"
task with the following parameters:
Argument
-useView4Transfer
Value
TRUE
-TargetTypeName
SAPBom++
-use_EA_system
e.g.
DSC_DJM_CONNECTION
-unpack_all_bomlines
TRUE
-collect_all_errors
TRUE
-continue_on_error
TRUE
© DSC Software AG
Note
Use the individually defined name of
the SAP PDMI Connection from
chapter 3.4 DTP – DSC T4EA Plug-In
here.
SAP product data management integration to Teamcenter
Page 17 of 20
Update
5
Update
5.1
Update of Version 1.0.1.0, 1.0.2.0, or 1.0.2.2 to Version 1.0.3.0
To update, download version 1.0.3.0 of SAP product data management integration to Teamcenter
and unzip. Execute the following steps afterwards:
1) Stop DJM service tci-djm-service.
2) Save the current installation directory and rename it to e.g. <DJM_INSTALLATION_DIR_OLD>.
a. Note: In this chapter, the name <DJM_INSTALLATION_DIR_OLD> is used for the
installation directory of the original version.
3) Move the contents of the unzipped directory with version 1.0.3.0 to the new directory
<DJM_INSTALLATION_DIR>.
4) Compare the file <DJM_INSTALLATION_DIR>\config\djm.config.yml in the new version
with the previous version <DJM_INSTALLATION_DIR_OLD>\config\djm.config.yml:
a. Take over values from the old file into the new file
b. check whether new configuration variables were added or deleted and add or delete
them according to the description in the file
<DJM_INSTALLATION_DIR>\config\djm.config.yml.
5) Open the new file <DJM_INSTALLATION_DIR>\dtp-mapping\t4ea_mapping_config.sd
for edit and add changes from <DTP_INSTALLATION_DIR>\t4ea_mapping_config.sd to it.
6) Open all .xml files <DJM_INSTALLATION_DIR>\dtp-mapping\*.xml for editing and copy
changes from the files <DTP_INSTALLATION_DIR>\*.xml into the new files.
7) Save all files in <DTP_INSTALLATION_DIR>, move them to another location and delete them
from <DTP_INSTALLATION_DIR> so the directory is empty.
8) Copy all files from the directory <DJM_INSTALLATION_DIR>\dtp-mapping to the directory
<DTP_INSTALLATION_DIR>.
9) In the GS, execute the script Generate mapping and mapping deployment in mode Generate
Mapping and File Copy and restart the GS afterwards.
10)
Delete all preference variables in Teamcenter that begin with T4EA_SAP*.
11)
Import the edited .xml files from the directory <DTP_INSTALLATION_DIR> as preference
variables in Teamcenter.
12)
Update the DWV RAC Plug-In according to the installation manual in chapter 3.5.1 Installation.
13)
Update the file TC_Workflow_Templates.xml in Teamcenter according to the installation
manual in chapter 4.3.2 Workflows.
14)
Start the DJM service tci-djm-service.
5.2
Update from version 1.0.0.0 to version 1.0.3.0
To update, follow the same steps as described in chapter 5.1, just step 4 is different:
4) Compare <DJM_INSTALLATION_DIR>\config\djm.config.yml in the new version with
the previous file versions <DJM_INSTALLATION_DIR_OLD>\config\djm.config.yml
and <DJM_INSTALLATION_DIR_OLD>\config\dwv.config.yml. Make sure that no keys
are duplicates, and merge them if necessary:
a. copy values from the old files to the new files,
b. check whether new configuration variables were added or deleted and add or delete
them according to the description in the file
<DJM_INSTALLATION_DIR>\config\djm.config.yml.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 18 of 20
Troubleshooting
6
Troubleshooting
6.1
No SAP Object Data in DWV
Problem:
In DWV, no SAP data (material and document data) is displayed.
Recommendation:
Compare the keys of the return values that are delivered by the function module
/AIFTC/GET_ATTRIBUTES for different SAP objects, in the respective language, with the following
section from the DJM Configuration File and edit the DJM Configuration File accordingly, if necessary.
Please pay attention to correct spelling and case-sensitivity.
sap:
masterdata-mapping:
en:
document-number: 'Document number'
material-number: 'Material Number'
part: 'Document part'
type: 'Document Type'
version: 'Document version'
de:
document-number: 'Dokumentnummer'
material-number: 'Materialnummer'
part: 'Teildokument'
type: 'Dokumentart'
version: 'Dokumentversion'
NOTE
Other languages in addition to the preconfigured languages German and English can be added in the
DJM Configuration File. Detailed information about adding another language is available in the DJM
Configuration File in section DJM – Teamcenter Integration Configuration at the variable
djm.sap.masterdata-mapping.
6.2
DWV: Problems with Plug-In Execution
Problem:
The plug-in cannot be started or it crashes.
Recommendation:
Teamcenter RAC has to be restarted after clearing the cache as follows:
 First remove the folder C:\Users\<your-system-user-name>\Teamcenter and test.
 If the previous step does not help, remove the folder
C:\Users\<your-system-user-name>\FCCCache and try again.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 19 of 20
Support
7
Support
In case you encounter problems when installing, upgrading, or running SAP product data
management integration to Teamcenter, report an incident using component PLM-PDM-TC.
https://support.sap.com/en/my-support/product-support.html
Software Maintenance
Please check http://support.sap.com/ and navigate to Software downloads  By Category  SAP
Solution Extensions by Partners.
© DSC Software AG
SAP product data management integration to Teamcenter
Page 20 of 20