Configuration Guide -

IMDS

®
SAP Product and
REACH Compliance
2.0
Target Audience
 System Administrators
 Technology Consultants

Document version: 2.3 – January 2011

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior
notice. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and
other SAP products and services mentioned herein as well as their
Some software products marketed by SAP AG and its distributors respective logos are trademarks or registered trademarks of SAP AG
contain proprietary software components of other software vendors. in Germany and in several other countries all over the world. A ll other
product and service names mentioned are the trademarks of their
Microsoft, Windows, Outlook, and PowerPoint are registered respective companies. Data contained in this document serves
trademarks of Microsoft Corporation. informational purposes only. National product specifications may
vary.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, These materials are subject to change without notice. These materials
xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, are provided by SAP AG and its affiliated companies ("SAP Group")
Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and for informational purposes only, without representation or warranty of
PowerPC are trademarks or registered trademarks of IBM Corporation. any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either products and services are those that are set forth in the express
trademarks or registered trademarks of Adobe Systems Incorporated in warranty statements accompanying such products and services, if any.
the United States and/or other countries. Nothing herein should be construed as constituting an additional
warranty.
Oracle is a registered trademark of Oracle Corporation.
SAP Library document classification: PUBLIC
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the
Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, Disclaimer
VideoFrame, and MultiWin are trademarks or registered trademarks of Some components of this product are based on Java™. Any
Citrix Systems, Inc. code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
HTML, XML, XHTML and W3C are trademarks or registered prohibited, as is any decompilation of these components.
trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology. Any Java™ Source Code delivered with this product is
only to be used by SAP’s Support Services and may not be
Java is a registered trademark of Sun Microsystems, Inc. modified or altered in any way.

JavaScript is a registered trademark of Sun Microsystems, Inc., used Documentation in the SAP Service Marketplace
under license for technology invented and implemented by Netscape. You can find this documentation at the following address:
http://service.sap.com/instguides

MaxDB is a trademark of MySQL AB, Sweden.

 (hereinafter: Customer)

Terms for Included Open a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive,
Source Software non-transferrable, royalty-free license to use
This SAP software contains also the third party open the STLport.org C++ library (STLport) and its
source software products listed below. Please note that for documentation without fee.
these third party products the following special terms and B) By downloading, using, or copying STLport or
conditions shall apply. any portion thereof Customer agrees to abide
1. This software was developed using ANTLR. by the intellectual property laws, and to all of
2. gSOAP the terms and conditions of this Agreement.
Part of the software embedded in this product is gSOAP C) The Customer may distribute binaries compiled
software. Portions created by gSOAP are Copyright with STLport (whether original or modified)
(C) 2001-2004 Robert A. van Engelen, Genivia inc. All without any royalties or restrictions.
Rights Reserved. D) Customer shall maintain the following
THE SOFTWARE IN THIS PRODUCT WAS IN PART copyright and permissions notices on STLport
PROVIDED BY GENIVIA INC AND ANY EXPRESS sources and its documentation unchanged:
OR IMPLIED WARRANTIES, INCLUDING, BUT Copyright 2001 SAP AG
NOT LIMITED TO, THE IMPLIED WARRANTIES E) The Customer may distribute original or
OF MERCHANTABILITY AND FITNESS FOR A modified STLport sources, provided that:
PARTICULAR PURPOSE ARE DISCLAIMED. IN o The conditions indicated in the above
NO EVENT SHALL THE AUTHOR BE LIABLE permissions notice are met;
FOR ANY DIRECT, INDIRECT, INCIDENTAL, o The following copyright notices are retained
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL when present, and conditions provided in
DAMAGES (INCLUDING, BUT NOT LIMITED TO, accompanying permission notices are met:
PROCUREMENT OF SUBSTITUTE GOODS OR Copyright 1994 Hewlett-Packard
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR Company
BUSINESS INTERRUPTION) HOWEVER CAUSED Copyright 1996,97 Silicon Graphics
AND ON ANY THEORY OF LIABILITY, WHETHER Computer Systems Inc.
IN CONTRACT, STRICT LIABILITY, OR TORT Copyright 1997 Moscow Center for
(INCLUDING NEGLIGENCE OR OTHERWISE) SPARC Technology.
ARISING IN ANY WAY OUT OF THE USE OF THIS Copyright 1999,2000 Boris Fomitchev
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY Copyright 2001 SAP AG
OF SUCH DAMAGE. Permission to use, copy, modify, distribute and
3. SAP License Agreement for STLport sell this software and its documentation for
SAP License Agreement for STLPort between any purposes is hereby granted without fee,
SAP Aktiengesellschaft provided that the above copyright notice appear
Systems, Applications, Products in Data Processing in all copies and that both that copyright notice
Neurottstrasse 16 and this permission notice appear in supporting
69190 Walldorf, Germany documentation. Hewlett-Packard Company
(hereinafter: SAP) makes no representations about the suitability
and of this software for any purpose. It is provided
you “as is” without express or implied warranty.
Permission to use, copy, modify, distribute and limited warranty and liability as set forth in the
sell this software and its documentation for any License Agreement distributed with this copy.
purpose is hereby granted without fee, provided SAP offers this liability and warranty obligations
that the above copyright notice appear in all only towards its customers and only referring
copies and that both that copyright notice and to its modifications.
this permission notice appear in supporting b) Support and Maintenance
documentation. Silicon Graphics makes no SAP does not provide software maintenance for the
representations about the suitability of this STLport. Software maintenance of the STLport
software for any purpose. It is provided “as is” therefore shall be not included.
without express or implied warranty. All other services shall be charged according to the
Permission to use, copy, modify, distribute and rates for services quoted in the SAP List of Prices
sell this software and its documentation for and Conditions and shall be subject to a separate
any purposes is hereby granted without fee, contract.
provided that the above copyright notice appear c) Exclusion of warranty
in all copies and that both that copyright notice As the STLport is transferred to the Customer on a
and this permission notice appear in supporting loan basis and free of charge, SAP cannot guarantee
documentation. Moscow Center for SPARC that the STLport is error-free, without material
makes no representations about the suitability defects or suitable for a specific application under
of this software for any purpose. It is provided third-party rights. Technical data, sales brochures,
“as is” without express or implied warranty. advertising text and quality descriptions produced
Boris Fomitchev makes no representations by SAP do not indicate any assurance of particular
about the suitability of this software for any attributes.
purpose. This material is provided "as is", with d) Limited Liability
absolutely no warranty expressed or implied. A) Irrespective of the legal reasons, SAP shall only
Any use is at your own risk. Permission to be liable for damage, including unauthorized
use or copy this software for any purpose is operation, if this (i) can be compensated under
hereby granted without fee, provided the above the Product Liability Act or (ii) if caused due to
notices are retained on all copies. Permission gross negligence or intent by SAP or (iii) if based
to modify the code and to distribute modified on the failure of a guaranteed attribute.
code is granted, provided the above notices B) If SAP is liable for gross negligence or intent
are retained, and a notice that the code was caused by employees who are neither agents or
modified is included with the above copyright managerial employees of SAP, the total liability
notice. for such damage and a maximum limit on the
Permission to use, copy, modify, distribute scope of any such damage shall depend on
and sell this software and its documentation the extent to which its occurrence ought to
for any purposes is hereby granted without have anticipated by SAP when concluding the
fee, provided that the above copyright notice contract, due to the circumstances known to
appear in all copies and that both that copyright it at that point in time representing a typical
notice and this permission notice appear in transfer of the software.
supporting documentation. SAP makes no C) In the case of Art. 4.2 above, SAP shall not
representations about the suitability of this be liable for indirect damage, consequential
software for any purpose. It is provided with a damage caused by a defect or lost profit.
D) SAP and the Customer agree that the typical F) The exclusion or the limitation of claims in
foreseeable extent of damage shall under no accordance with the present Art. 4 includes
circumstances exceed EUR 5,000. claims against employees or agents of SAP.
E) The Customer shall take adequate measures 4. Adobe Document Services
for the protection of data and programs, in Adobe, the Adobe logo, Acrobat, PostScript, and Reader
particular by making backup copies at the are either registered trademarks or trademarks of
minimum intervals recommended by SAP. SAP Adobe Systems Incorporated in the United States and
shall not be liable for the loss of data and its / or other countries. For information on Third Party
recovery, notwithstanding the other limitations software delivered with Adobe document services and
of the present Art. 4 if this loss could have been Adobe LiveCycle Designer, see SAP Note 854621.
avoided by observing this obligation.
Typographic Conventions Icons
Type Style Description Icon Meaning
Example Text Words or characters quoted Caution
from the screen. These include
field names, screen titles, Example
pushbuttons labels, menu
Note
names, menu paths, and menu
options. Recommendation
Cross-references to other Syntax
documentation
Example text Emphasized words or phrases
in body text, graphic titles, and Additional icons are used in SAP
table titles Library documentation to help you
identify different types of information at
EXAMPLE TEXT Technical names of system a glance. For more information, see
objects. These include report Help on Help  General Information
names, program names, Classes and Information Classes for
transaction codes, table Business Information Warehouse on
names, and key concepts of a the first page of any version of SAP
programming language when Library.
they are surrounded by body
text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This
includes file and directory
names and their paths,
messages, names of variables
and parameters, source text,
and names of installation,
upgrade and database tools.
Example text Exact user entry. These are
words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example Variable user entry. Angle
text> brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for
example, F2 or ENTER.
Contents
1 Introduction ......................................................................................... 8
1.1 About this Document ....................................................................... 8
1.2 Installation Check and Sanity Checks............................................ 8
1.3 Known Issues ................................................................................... 8
1.4 SAP Notes ......................................................................................... 8
1.5 Information Available in SAP Service Marketplace....................... 9
2 Customizing ......................................................................................10
2.1 Cross System Adjustment............................................................. 10
2.2 Additional Customizing Activities ................................................ 11
3 Installation of IMDS Batch Client..................................................15
3.1 Prerequisites ................................................................................... 15
3.2 Installation/Upgrading ................................................................... 15
3.3 Setup RFC Connection .................................................................. 18
4 Content...............................................................................................20
4.1 Set-Up initial IMDS data ................................................................. 20
4.2 Set-Up Daily IMDS Synchronization ............................................. 20
4.3 IMDS Worklist ................................................................................. 21
5 Additional Configuration ................................................................22
5.1 Workbench Views in Simulation Mode......................................... 22

January 2011 7
About this Document

1 Introduction
1.1 About this Document
This document describes how to configure the IMDS Interface.

Processing the Basic Configuration Guide is a mandatory prerequisite of this

guide.

1.2 Installation Check and Sanity Checks

The delivery of the SAP Product and REACH Compliance Installation and
Configuration Guides in the SAP Note 1386600 also includes documents for
checking the installation and configuration, and for performing a sanity check.

It is strongly recommended that you download and use the document to

check the installation in parallel to the steps of the installation and
configuration guides. Also, after the installation and configuration, use
the document with the sanity checks to check the functions of the
business processes.

Every step in this installation and configuration guide include s a link to the
installation check document if the current step has a corresponding step.

1.3 Known Issues

The development of SAP Product and REACH Compliance created new technical demands
that lead to new technical expertise. Some known problems and errors exist. An additional
document was created that describes these problems and errors and how to fix them.

The delivery of the SAP Product and REACH Compliance Installation and
Configuration Guides in the SAP Note 1386600 include a document with
known issues.
It is recommended that you read this document and check if the described
issues apply to your installation and configuration.

1.4 SAP Notes

You must read the following SAP Notes before you start the installation. These SAP Notes
contain the most recent information on the installation, as well as corrections to the
installation documentation.
Ensure that you have the up-to-date version of each SAP Note that you can find in the SAP
Service Marketplace at the Internet address: service.sap.com/notes.
SAP Note Title Description
Number

8 January 2011
 Information Available in SAP Service Marketplace

1.5 Information Available in SAP Service

Marketplace
Information on the following areas is available in the SAP Service Marketplace.
Documentation
Description Internet Address Title
SAP NetWeaver – AS SAP NetWeaver Library: Overview and Use
Java Administration AS Java Administration
SAP Netweaver – Web SAP NetWeaver Library:
Service Configuration Configuring Individual Web Service
Clients
Sap Netweaver CE SAO Community Network:
Security Guide https://cw.sdn.sap.com/cw/docs/DO
C-105295

January 2011 9
Cross System Adjustment

2 Customizing
2.1 Cross System Adjustment
Synchronize the complete Customizing on your productive client with the reference client
000. by using the Cross System Viewer and the piece list /TDAG/RCS_PLCSC_200n (with n
equals the ServicePack Number).
Execute the following steps:
 Start transaction SCU0
 Select piece list /TDAG/RCS_PLCSC_200n (with n equals the ServicePack Number)
and
 Create new comparison

Open the downloaded installation check document from SAP Note 1386600
and execute the steps in chapter Cross System Check. Make the necessary
entries and select the relevant checkboxes in the document.

Use the cross-system viewer for the comparison.

Adjustments of the language dependent Customizing settings work only with

your logon language. Perform the adjustment for every logon language that is
used in your system.

The sort sequence in the piece list does not always reflect the correct
processing sequence. It is possible that errors can occur while comparing and
adjusting the items. In this case, continue with the adjustment and, in a
second step, try the adjustment of the value that causes the error.

10 January 2011
 Additional Customizing Activities

2.2 Additional Customizing Activities

The following customizing configurations are prefilled with default values

during the Cross System Adjustment step. In some cases a supplementary
verification and adjustment is necessary.

Basic Material Management

Enter one of the following values for the parameter IMDS_STREAMLINE_MATERIALS in the
Customizing activity
Product and REACH Compliance
 Basic Data
 Specify Environment Parameters for Back-End Processes.

X It the parameter is set to true, unknown basic materials which are contained
in a product are uploaded (created) and released as a module in the IMDS
automatically.
Space Parameter is not set and unknown basic materials are not registered
automatically at IMDS without releasing the basic material (default option)

If you are a contract manufacturer who assembles parts bought from

suppliers, you must not set this parameter. Since you do not create your own
basic materials in the laboratory, you do not release any basic materials and
get this data from your suppliers instead.
When you upload products to IMDS and the parameter is set, the basic
materials are also uploaded without checking the basic materials again.
If this parameter is not set, the base check checks if the basic materials are
released and the warning message appears, if necessary.

Regulated Substance Lists and Checks

Configure the required user exit CP_IMDS (category CHECK &

USEREXIT_OF_ANALYTICS) in Customizing under:
Product and REACH Compliance
 Basic Data
 User Exits
 Manage User Exits.

Configure the regulation GADSL in Customizing under:

Product and REACH Compliance
 Regulations
 Specify Regulatory Lists and Customer Lists.

Configure the compliance checks GADSL and IMDS in Customizing under:

Product and REACH Compliance
 Checks

January 2011 11
Additional Customizing Activities

 Specify Checks and Single Criteria.

Configure the tabs GADSL and IMDS for the compliance workbench in Customizing under:
Product and REACH Compliance
 Compliance Workbench
 Specify Compliance Workbench Views.

For the simulated Import of MDS product structure data, check here additionally the displayed
Compliance Workbench views for the Simulation Mode (see chapter 5.1).

Import Templates
Configure the listed import templates in Customizing under:
Product and REACH Compliance
 Data Exchange
 Specify Incoming Templates.

 IMDS_GRP: Import of IMDS Substance Groups

 IMDS_MODUL: Import of IMDS Material Datasheets
 IMDS_ORG: Import of IMDS Organizations and Companies
 IMDS_PURE: Import of IMDS Pure Substances
 IMDS_REQ: Import of IMDS Requests

SAP Product and REACH Compliance provides the environment parameter

GEN_UNIT_PIECE_INTERNAL for the Piece unit of measure. If you use a
different unit of measure to ST (Stück), you must make sure that the import
mapping contains the correct unit of measure in the UnitConversion view.

Normalization
With normalization, you can adapt a product structure before performing an export or a
check. Normalizations replace the BOS explosion user exit BOSEXPL. SAP Product and
REACH Compliance provides the following normalizations specific for the IMDS Interface:
 CP_PREFER Only Preferred:
The preferred and active normalization eliminates all subparts that are not
preferred. With this normalization, you work with more than one supplier or
alternative. Only the preferred normalizations are exported to IMDS.

 CP_IMDSFB IMDS Flat BOM:

In exceptional cases, you can reduce the structure of assemblies. Then, only the
assemblies/subassemblies are displayed (see Recommendations IMDS 002,
014).
The flat BOM normalization eliminates all sub parts/bulks and collects the
included basic materials. The preferred and active normalization is part of the flat
BOM normalization.

Configure the normalizations CP_PREFER and CP_IMDSFB in Customizing under:

Product and REACH Compliance

12 January 2011
 Additional Customizing Activities

 Product Database
 Specify Normalization Variants.

The used normalization variant can be defined within the Outgoing Template IMDS_MODUL.

Outgoing Template
Check the Outgoing Template IMDS_MODUL in Customizing (e.g. set the normalization
variant):
Product and REACH Compliance
 Data Exchange
 Specifiy Outgoing Templates

IMDS connectivity
Configure the IMDS connection parameters in the Customizing activity:
Product and REACH Compliance
 Data Exchange
 IMDS
 Specify IMDS System.

By default, all values that are not customer-specific are already set. Set your customer-
specific values as follows:
Company Org. Your own IMDS Company ID. The Company IDs are available using
ID the transaction /TDAG/CPO01 and must first be loaded into the
system.
DirTmpBtchCl Working directory of the IMDS Batch Client on the WWI server.
Example: c:\temp
Server Directory Directory on ERP backend system for downloaded IMDS files
Example: \\application server\..\..\sprc_files
Archive Directory Directory on ERP backend system for imported IMDS data
Example: \\application server\..\..\sprc_files\archive
U.User-ID User ID for data upload using the IMDS Advanced Interface
U.User-Pass Password for data upload using the IMDS Advanced Interface
D.User-ID User ID for data download using the IMDS Advanced Interface
D.User-Pass Password for data download using the IMDS Advanced Interface
Proxy Host Proxy settings for connecting the IMDS (used by the IMDS Batch-
Proxy Port Client Interface)
Proxy User
Proxy Password

Status Upload Indicates if the IMDS Status Upload Functionality is enabled via
Advanced Interface for your Company.

January 2011 13
Additional Customizing Activities

By default, the URLs of the IMDS test and productive systems are delivered
within two different system definitions (PRODSYSTEM and TESTSYSTEM).
The currently used system configuration is marked as active.

Check Customizing for IMDS-Specific Details Regarding Product

Structures
Check that you have an entry for REACTION (Reaction Residue) and that you have selected
the Assignment of Components Is Possible and Required checkbox in Customizing under:
Product and REACH Compliance
 Product Database
 Specify Component Types for Compositions

Check that you have an RE (Residue) entry in Customizing under:

Product and REACH Compliance
 Product Database
 Specify Exception Values for a Component

Check that the component types CONFIDENT and IMPURITY are defined.
Product and REACH Compliance
 Product Database
 Specify Component Types for Compositions

Check that you have configured the component type CONFIDENT as confidential. The
confidential component type is defined by environment parameter
SP_COMPCAT_CONFIDENTIAL in Customizing under:
Environment, Health and Safety
 Basic Data and Tools
 Basic Settings
 Specify Environment Parameters

Check the Identification Listing CP_IMDSSUP which controls the shown Specification
identifiers (at most three) in the IMDS Supplier Center hit list.
Product and REACH Compliance
 Product Database
 Check Identification Listing

Check the MDS Import Restrictions, which are defining the cases MDS structure data is
allowed to be imported using the Supplier MDS Center (Function “Import”).
Depending on the current MDS recipient status, the import of the MDS structure data is
allowed, not allowed or only allowed after a confirmation by the user.
Product and REACH Compliance
 Data Exchange
 IMDS
 Specify MDS Import Restrictions

14 January 2011
 Prerequisites

3 Installation of IMDS Batch Client

3.1 Prerequisites
The IMDS batch client is a 32-bit application from a Microsoft Windows operating system.
You can only install it on servers of a Microsoft Windows operating system that support these
32-bit applications. It communicates with the ERP back-end system via the same RFC
configuration as WWI. If a WWI installation already exists, the IMDS batch client can be
installed on the same server.

The IMDS batch client software should be installed as a windows service, to

ensure that it is started automatically at each server startup.

Additionally, the IMDS batch client communicates via https with the IMDS servers. This
communication occurs via the Internet.

Ensure that the necessary firewall configurations have been made.

The IMDS batch client uses a Java library (JSSL.zip) for the communication with the IMDS.
The Java Library is downloaded separately from IMDS. It is part of the IMDS batch client
download from IMDS.

Ensure that a Java runtime environment of release 1.4.2_16 or higher is

properly installed.

In order to run the IMDS batch client, you require an IMDS Advanced Interface contract for
your company and users with Advanced Interface profiles.

See the "Technical Preconditions" chapter in the batch client documentation

from IMDS

Technical user accounts are used for authorization between the systems. To
ensure a certain level of security it is strongly recommended to use https protocol or
SNC (Secure Network Communication) mechanisms for the communication
between the systems. Refer to SAP NetWeaver Composition Environment Security
Guide for details.

3.2 Installation/Upgrading
Preparing the Installation
Download the installation package for IMDS batch client for all of the following installations or
upgrades. For more information, see SAP Note 1394429.

Extract IMDS Batch Client Files

January 2011 15
Installation/Upgrading

Extract the IMDS batch client installation archive from SAP Note 1394429 to your local disk
on the WWI server, for example "c:\imds_interface". After you have extracted the archive to
your local disk, the root folder imds_interface has the following directory structure:
<imds_interface> <Root folder for the IMDS batch client installation>
+-- imds <Empty subfolder to be completed with IMDS downloads>
| +-- JavaClient <Extract batch client from IMDS including JSSL.zip
| file here>
| +-- Manuals <Extract upload and download manuals from IMDS here>
| +-- DTD <Extract document type definition files from IMDS here>
+-- imdsbatchclient.exe
+-- download.bat
+-- upload.bat
+-- further files

The <imds_interface> folder contains the required files, such as imdsbatchclient.exe. You
must add the latest downloads from IMDS to subfolder .\imds.

Get the latest downloads from IMDS

Before you continue, make sure that you download the latest batch client together with the
upload and download manual from the IMDS production server at
https://www.mdsystem.com.
 Login to IMDS (with AI User) and navigate to the Download section underneath the
Administration menu item. Download the requested zip files containing the batch
client, the upload manual and the download manual.
 Extract the IMDS batch client (*.zip file) to the <IMDS Interface>\IMDS\JavaClient
folder for your local server installation. In particular, the JSSL.zip file must be stored
in this folder.
 Extract the upload manual to the <IMDS Interface>\IMDS\Manuals folder.
 Extract the .zip file that contains DTD files to the <IMDS Interface>\IMDS\DTD
folder.
 Extract the download manual into the <IMDS Interface>\IMDS\Manuals folder.

Adjust the .bat files for the IMDS Batch Client

The root folder <imds_interface> contains the following three batch files:
 upload.bat
 download.bat
 result.bat
Program imdsbatchclient.exe uses these batch files to communicate with the IMDS. Edit each
.bat file from this folder to use the current folder names. Make sure that the .bat files point to
the correct location of the JSSL.zip file.
In each batch job file, you find a drive letter after the block of each statement. Change this
drive letter to the drive on which the IMDS batch client is installed.
In the subsequent line, you find a cd-statement followed by a path. Change the path so that
the drive letter and the path together match the path to the JSSL.zip file.
For example:
Full path of JSSL.zip is c:\imds_interface\imds\JavaClient\JSSL.zip
Content of the batch job files is:
...

16 January 2011
 Installation/Upgrading

echo ...
c:
cd \imds_interface\imds\JavaClient
...

Adjust the SAPRFC.INI file

Before you can start the IMDS batch client, you must adjust/create a RFC destination that
points to the ERP back-end system in the SAPRFC.INI file.

DEST=IMDS_BATCH_CLIENT_XXX
PROGID=IMDS_BATCH_CLIENT_XXX
TYPE=R
GWHOST=<your gateway host>
GWSERV=<your gateway service>
RFC_TRACE=0

Replace XXX with the system ID of your ERP back-end system. The TCP/IP
program ID (value of PROGID) must exactly match the TCP/IP program ID of
the corresponding RFC destination in the ERP back-end system (see chapter
3.3 - Setup RFC Connection).

If the environment variable RFC_INI is set on the WWI server, do not edit the
local SAPRFC.INI of the IMDS batch client. Instead, edit the global
SAPRFC.INI indicated by the environment variable.

Starting Batch Client with RFC Destination

Create a shortcut on your desktop to the file IMDSBATCHCLIENT.EXE from the IMDS batch
client installation folder (such as C:\IMDS_INTERFACE\IMDSBATCHCLIENT.EXE) with the
following settings:
Name IMDS Batch Client
Target <IMDS Batch Client installation folder>\imdsbatchclient.exe –D<RFC Destination
Name>
Example: c:\imds_interface\imdsbatchclient.exe –DIMDS_BATCH_CLIENT_XXX
Start in <IMDS Batch Client installation folder>\
Example: c:\imds_interface\

Use the value of <RFC Program ID> for setting up the RFC destination in the
ERP back-end system while processing Configuration Guide IMDS.

Refer to file PARAMETERS.TXT in the IMDS batch client installation folder for
a complete list of supported call parameters of IMDSBATCHCLIENT.EXE.

January 2011 17
3.3 Setup RFC Connection
RFC Destination in R/3 System
In transaction SM59, create the following RFC destination:
Parameter Value
Type T – TCP/IP Connection
RFC Destination IMDS_BATCH_CLIENT
Description REACH: Interface to IMDS database
Activation Type Registered Server Program
Program ID RFC Program ID from Installation Guide (Installation of IMDS
Batch Client)
Example: IMDS_BATCH_CLIENT_XXX
Replace XXX with the system ID of your ERP system

Environment Parameter BATCH_CLIENT_RFC_DEST

Check the BATCH_CLIENT_RFC_DEST environment parameter in the following
Customizing activity:
Product and REACH Compliance
 Basic Data
 Environment Parameters for Back-End Processes.
Make sure that this parameter points to the correct RFC destination of the IMDS batch client
as defined in transaction SM59.
The default value is the RFC Destination IMDS_BATCH_CLIENT.

Settings in SAPRFC.INI
The file SAPRFC.INI is located in the installation directory of the IMDS batch client on the
WWI server, for example C:\IMDS). In this file, you must maintain the parameters GWHOST,
GWSERV and PROGID according to the settings in transaction SM59.

Parameter Description
GWHOST Enter the application server on which your generation
server is to be registered. Enter the complete router string
including the application server, for example,
GWHOST=/H/mum18/H/hstd01.
You trigger the application server and the router string by
selecting your system in the SAP logon screen and then
choosing Edit.
GWSERV Enter the name of the gateway service provided on the
GWHOST.
You trigger the gateway service by selecting your system in
the SAP logon screen and then choosing Edit. The name
consists of the text sapgw and the system number, for

18 January 2011
 Setup RFC Connection

example,
GWSERV=sapgw02.

January 2011 19
Set-Up initial IMDS data

4 Content
4.1 Set-Up initial IMDS data
Before using the IMDS extension in SAP Product and REACH Compliance, it has to be set
up with the current initial data from the IMDS.
The current initial IMDS data can be distinguished in IMDS master data like:
 IMDS Substance Groups
 IMDS Pure Substances
 IMDS Organizations and Companies
and current operational data, which is stored in the IMDS for your company:
 IMDS Material Datasheets (Own MDS or Modules, Received MDS, Published MDS)
 IMDS Requests (Own Requests or received Requests)

To set up the system with this initial data, please refer to the corresponding IMG activity,
which can be found under
Product and REACH Compliance
 Data Exchange
 IMDS
 Setup System with IMDS All Files

Configure IMDS Organizations and Companies

After loading the IMDS organization and companies master data into the system, all business
relevant organizations and companies should be checked according their valid link to a
customer or vendor master record. This can be done using the transaction /TDAG/CPO01.
Further check if the correct organization / company ID of your own organization is maintained
in the active IMDS system configuration (see 2.2 - IMDS connectivity).

4.2 Set-Up Daily IMDS Synchronization

It is important to synchronize the IMDS extension in SAP Product and REACH Compliance
with the IMDS Daily Files. Using this synchronization it’s the only way to recognize e.g. new
MDS or Requests sent to your company.
Further more the response time of the IMDS system after an IMDS upload varies. This
means, the result file cannot be imported immediately by the upload process. In order to
import and process the result file automatically at a later time, you can schedule a
background job.

The set-up and the automatic result file processing can be done, using the following IMG
activity:
Product and REACH Compliance
 Data Exchange
 IMDS
 Set Up Daily Synchronization with IMDS System (…)

20 January 2011
4.3 IMDS Worklist
To set up and activate the IMDS worklist, please refer to the corresponding IMG activities,
which can be found under
Product and REACH Compliance
 Worklist Management
 Configure Worklist Management
 Business Add-Ins (BAdIs)
 BAdI: Enhancement of the IMDS Worklist

January 2011 21
Workbench Views in Simulation Mode

5 Additional Configuration
5.1 Workbench Views in Simulation Mode
For the simulated Import of MDS product structure data, the displayed Compliance
Workbench Views for the Simulation Mode can be configured in the IMG Activity:
Product and REACH Compliance
 Compliance Workbench
 Specify Compliance Workbench Views
 Workbench Views for Simulation Mode

In the default delivery the views BASE, GADSL, IMDS and REACH-SVHC are configured.
If you need an additional view, which differs from these standard views, a new check has to
be implemented and maintained here. The following sections describe how this can be done.

Creation of new class ...TAB_VIEW_CTRL_SIM

Create a new TAB_VIEW_CTRL_SIM class for the simulation mode that references the
/TDAG/CPCL_TABP_VIEW_CTRL_SIM class.
 See /TDAG/CPCL_IMDST_VIEW_CTRL_SIM (Simulation) and
/TDAG/CPCL_IMDS_TAB_VIEW_CTRL (original class for Workbench) as example.
Adaption of methods
Overwrite the methods that are overwritten in the original TAB_VIEW_VTRL class, that
controls the tab in the compliance workbench and copy the codes from the original
TAB_VIEW_VTRL class.
Example:
 FREE
 GET_PROD_STRU_OBJECT_ID
 CREATE_PRODUCT_STRUCTURE
 CREATE_IMDS_CONTEXT_ID

Overwrite the method INIT according to /TDAG/CPCL_IMDST_VIEW_CTRL_SIM:

 Call super->init
 Set new toolbar- and menu handler (type of /tdag/cpcl_def_prod_hndl_sim).
 Set new HTML control in the header control of the details control to deactivate the
links in the header.

Adaption of attributes
Add the additional attributes, that are added in the original class. Adapt the default value of
the DETAILS_VIEW_CTRL_CLASS if you implement a new detail control.
Example:
 MC_DETAILS_VIEW_CTRL_CLASS
 MC_PROD_STRU_OBJECT_ID
 MC_IMDS_CONTEXT_ID
 MO_PROD_STRU_EXT

22 January 2011
 Workbench Views in Simulation Mode

If you do not want to change the displaying of the detail section or the composition, you do
not have do execute any other steps. Then you are finished right here. Else please go on with
the following steps.
Creation of new class ... VIEW_CTRL_SIM
Create new VIEW_CTRL_SIM class for the simulation mode that references the according
VIEW_CTRL class.
 See /TDAG/CPCL_IMDS_VIEW_CTRL_SIM (Simulation) and
/TDAG/CPCL_IMDS_VIEW_CTRL (original class for Workbench) as example.
Adaption of methods
Overwrite the method OPEN_VIEW and just copy the original source code from the
VIEW_CTRL class. Through this, the new DATA_CTL class is used.
Overwrite the method GET_ALV_TITLE and adapt the displayed selection according to your
needs.
Adaption of attributes
Add the additional attributes, that are added in the original class.
Example:
 MC_LOCAL_CONTEXT_ID
 MO_IMDS_DATA_CTRL

Creation of new class ... DATA_SIM

Create a new DATA_SIM class for the simulation mode that references the according DATA
class.
 See /TDAG/CPCL_IMDS_DATA_SIM (Simulation) and /TDAG/CPCL_IMDS_DATA
(original class for Workbench) as example.
Adaption of methods
Overwrite the method /TDAG/CPIF_PROP_DATA~INIT_DATA and adapt it according to
your needs.

January 2011 23