SReach Compleance - ConfigGuide

Configuration Guide
SAP
REACH
Compliance 1.1
Target Audience
System administrators
Technology consultants

Document version: 1.4 January, 2011

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.

Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,
xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,
Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and
PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either
trademarks or registered trademarks of Adobe Systems Incorporated in
the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the
Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered
trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used
under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and
other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves
informational purposes only. National product specifications may
vary.

These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional
warranty.

SAP Library document classification: PUBLIC

Disclaimer
Some components of this product are based on Java. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is
only to be used by SAPs Support Services and may not be
modified or altered in any way.

Documentation in the SAP Service Marketplace
You can find this documentation at the following address:
http://service.sap.com/instguides

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

Terms for Included Open
Source Software
This SAP software contains also the third party open
source software products listed below. Please note that for
these third party products the following special terms and
conditions shall apply.
1. This software was developed using ANTLR.
2. gSOAP
Part of the software embedded in this product is gSOAP
software. Portions created by gSOAP are Copyright
(C) 2001-2004 Robert A. van Engelen, Genivia inc. All
Rights Reserved.
THE SOFTWARE IN THIS PRODUCT WAS IN PART
PROVIDED BY GENIVIA INC AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE AUTHOR BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
3. SAP License Agreement for STLport
SAP License Agreement for STLPort between
SAP Aktiengesellschaft
Systems, Applications, Products in Data Processing
Neurottstrasse 16
69190 Walldorf, Germany
(hereinafter: SAP)
and
you
(hereinafter: Customer)
a) Subject Matter of the Agreement
A) SAP grants Customer a non-exclusive,
non-transferrable, royalty-free license to use
the STLport.org C++ library (STLport) and its
documentation without fee.
B) By downloading, using, or copying STLport or
any portion thereof Customer agrees to abide
by the intellectual property laws, and to all of
the terms and conditions of this Agreement.
C) The Customer may distribute binaries compiled
with STLport (whether original or modified)
without any royalties or restrictions.
D) Customer shall maintain the following
copyright and permissions notices on STLport
sources and its documentation unchanged:
Copyright 2001 SAP AG
E) The Customer may distribute original or
modified STLport sources, provided that:
o The conditions indicated in the above
permissions notice are met;
o The following copyright notices are retained
when present, and conditions provided in
accompanying permission notices are met:
Coypright 1994 Hewlett-Packard
Company
Copyright 1996,97 Silicon Graphics
Computer Systems Inc.
Copyright 1997 Moscow Center for
SPARC Technology.
Copyright 1999,2000 Boris Fomitchev
Copyright 2001 SAP AG
Permission to use, copy, modify, distribute and
sell this software and its documentation for
any purposes is hereby granted without fee,
provided that the above copyright notice appear
in all copies and that both that copyright notice
and this permission notice appear in supporting
documentation. Hewlett-Packard Company
makes no representations about the suitability
of this software for any purpose. It is provided
as is without express or implied warranty.

sell this software and its documentation for any
purpose is hereby granted without fee, provided
that the above copyright notice appear in all
copies and that both that copyright notice and
this permission notice appear in supporting
documentation. Silicon Graphics makes no
representations about the suitability of this
software for any purpose. It is provided as is
without express or implied warranty.
sell this software and its documentation for
any purposes is hereby granted without fee,
provided that the above copyright notice appear
in all copies and that both that copyright notice
and this permission notice appear in supporting
documentation. Moscow Center for SPARC
makes no representations about the suitability
of this software for any purpose. It is provided
as is without express or implied warranty.
Boris Fomitchev makes no representations
about the suitability of this software for any
purpose. This material is provided "as is", with
absolutely no warranty expressed or implied.
Any use is at your own risk. Permission to
use or copy this software for any purpose is
hereby granted without fee, provided the above
notices are retained on all copies. Permission
to modify the code and to distribute modified
code is granted, provided the above notices
are retained, and a notice that the code was
modified is included with the above copyright
notice.
Permission to use, copy, modify, distribute
and sell this software and its documentation
for any purposes is hereby granted without
fee, provided that the above copyright notice
appear in all copies and that both that copyright
notice and this permission notice appear in
supporting documentation. SAP makes no
representations about the suitability of this
software for any purpose. It is provided with a
limited warranty and liability as set forth in the
License Agreement distributed with this copy.
SAP offers this liability and warranty obligations
only towards its customers and only referring
to its modifications.
b) Support and Maintenance
SAP does not provide software maintenance for the
STLport. Software maintenance of the STLport
therefore shall be not included.
All other services shall be charged according to the
rates for services quoted in the SAP List of Prices
and Conditions and shall be subject to a separate
contract.
c) Exclusion of warranty
As the STLport is transferred to the Customer on a
loan basis and free of charge, SAP cannot guarantee
that the STLport is error-free, without material
defects or suitable for a specific application under
third-party rights. Technical data, sales brochures,
advertising text and quality descriptions produced
by SAP do not indicate any assurance of particular
attributes.
d) Limited Liability
A) Irrespective of the legal reasons, SAP shall only
be liable for damage, including unauthorized
operation, if this (i) can be compensated under
the Product Liability Act or (ii) if caused due to
gross negligence or intent by SAP or (iii) if based
on the failure of a guaranteed attribute.
B) If SAP is liable for gross negligence or intent
caused by employees who are neither agents or
managerial employees of SAP, the total liability
for such damage and a maximum limit on the
scope of any such damage shall depend on
the extent to which its occurrence ought to
have anticipated by SAP when concluding the
contract, due to the circumstances known to
it at that point in time representing a typical
transfer of the software.
C) In the case of Art. 4.2 above, SAP shall not
be liable for indirect damage, consequential
damage caused by a defect or lost profit.

D) SAP and the Customer agree that the typical
foreseeable extent of damage shall under no
circumstances exceed EUR 5,000.
E) The Customer shall take adequate measures
for the protection of data and programs, in
particular by making backup copies at the
minimum intervals recommended by SAP. SAP
shall not be liable for the loss of data and its
recovery, notwithstanding the other limitations
of the present Art. 4 if this loss could have been
avoided by observing this obligation.
F) The exclusion or the limitation of claims in
accordance with the present Art. 4 includes
claims against employees or agents of SAP.
4. Adobe Document Services
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and
/ or other countries. For information on Third Party
software delivered with Adobe document services and
Adobe LiveCycle Designer, see SAP Note 854621.

Typographic Conventions

Type Style Description
Example Text Words or characters quoted
from the screen. These include
field names, screen titles,
pushbuttons labels, menu
names, menu paths, and menu
options.
Cross-references to other
documentation
Example text Emphasized words or phrases
in body text, graphic titles, and
table ti tles
EXAMPLE TEXT Technical names of system
objects. These include report
names, program names,
transaction codes, table
names, and key concepts of a
programming language when
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
text>
Variable user entry. Angle
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.
Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP
Library documentation to help you
identify different types of information at
a glance. For more information, see
Help on Help General Information
Classes and Information Classes for
Business Information Warehouse on
the first page of any version of SAP
Library.

January, 2011 7
Contents
1 Introduction ......................................................................................... 9
1.1 About this Document ....................................................................... 9
1.2 Installation Check and Sanity Checks............................................ 9
1.3 Known Issues ................................................................................... 9
1.4 SAP Notes ....................................................................................... 10
1.5 Information available in SAP Service Marketplace ..................... 10
2 Customizing ......................................................................................11
2.1 Cross System Adjustment............................................................. 11
2.2 Additional IMG Activities ............................................................... 12
3 Content ...............................................................................................14
3.1 Classes and Characteristics ......................................................... 14
3.2 Create Phrase Sets and Phrase Set-to-Attribute Assignment .. 20
3.3 Match Up Master Data .................................................................... 20
3.4 Import of the phrases ..................................................................... 20
4 Additional Configuration ................................................................21
4.1 Determination of Configuration Parameters................................ 21
4.2 Portal Configuration ....................................................................... 22
4.2.1 Removing Obsolete Log Configuration ...................................... 22
4.2.2 Portal Content System Administration ....................................... 22
4.2.3 RFC-Connection ......................................................................... 25
4.2.4 Configure JCo Client RFC Destination........................................ 27
4.3 Configuration of Backend ............................................................. 32
4.3.1 Creating Number Ranges............................................................ 32
4.3.2 Deactivation of User Exits .......................................................... 33
4.3.3 BAdI Implementations ................................................................ 33
4.3.4 Adapt AIF REACH Templates ...................................................... 34
4.3.5 Legal Entities .............................................................................. 38
4.3.6 Business Partners ...................................................................... 38
4.3.7 E-Mail Processing ....................................................................... 39
4.3.8 Portfolio Reporting ..................................................................... 43
4.3.9 Configuration of the Xcelsius Integration ................................... 46
4.4 CFP Worklist Management ............................................................ 48
4.5 Configure Internet Graphics Service ............................................ 48
4.6 Configuration of Workflow ............................................................ 49
4.6.1 Workflow-based Material Assessment ........................................ 49
4.6.2 Universal Work List (UWL) .......................................................... 49
4.6.3 Workflow..................................................................................... 50
4.6.4 Workflow Foundation (WFF) ....................................................... 51
5 Post-Installation ...............................................................................55
Installation Guide: SAP REACH Compliance

8 January, 2011
5.1 User Management .......................................................................... 55
5.2 Test the Installation ........................................................................ 57
About this Document

January, 2011 9
1 Introduction
1.1 About this Document
This document describes how to configure the SAP REACH Compliance solution based on
SAP NetWeaver.
1.2 Installation Check and Sanity Checks

The deli very of the SAP REACH Compliance Installation and Configuration
Guides in the SAP Note 1305182 includes also documents to check the
installation and configuration and to do a sanity check.

It is strongly recommend that the document to check the installation will
download and use parallel to the steps in 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 a constrain to
the installation check document if the current step has a correspondent step

1.3 Known Issues
Because of the facts that the developing process of the SAP REACH Compliance creates
and find new technical expertise, it cannot avoid that some problems and errors occurred.
Therefore, an additional document was created which include the problems and errors and
how to fix them.

The deli very of the SAP REACH Compliance Installation and Configuration
Guides in the SAP Note 1305182 include a document wi th known issues.
It is recommended to read this document and verify that the described issues
related to the own si tuation.

SAP Notes

10 January, 2011
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.
Make sure that you have the up-to-date version of each SAP Note, which you can find in the
SAP Service Marketplace at the Internet address: service.sap.com/notes.
SAP Note
Number
Title Description
1305336 REACH: Part list for Cross-System-
Check
This note contains a part list for all
necessary IMG acti vities for
REACH 1.1 SP02.
1299496 REACH: Phrases and Phrases sets
704604 Business graphics, GeoMaps are
not displayed in WD Java

337623 Customizing after installation or
upgrade
Some of the deli vered
Customizing is client-specific and
requires specific manual steps to
be copied from the Customizing
master client to the working client.
This note provides the
documentation on these steps.

1.5 Information available in SAP Service
Marketplace
Information on the following areas is avai lable in the SAP Service Marketplace.
Documentation
Description Internet Address Title
SAP NetWeaver
Installation Guide
SAP Service Marketplace:
SAP NetWeaver <your release>
Installation SAP Web AS
SAP Web AS <version> Related
Documentation
Installation Guide
SAP ERP Installation
Guide
SAP Service Marketplace:
SAP Business Suite Applications
SAP ERP <your release>
Installation
Installation Guide
SAP NetWeaver- System
Landscape Directory
SAP NetWeaver Library
SLD

Cross System Adjustment

January, 2011 11
2 Customizing
2.1 Cross System Adjustment
Compare the customizing on your productive client with the reference client 000. You have
two options how to do that:
Go through the acti vities of the SAP Customizing Implementation Guide (IMG) and
execute menu item Utilities(M) Adjustment for each to compare the two clients.

Execute transaction SCU0 and use the Cross-System Viewer to compare the
customizing on the producti ve client with the reference client. Create new comparison
for the activities mentioned below and, finally, run the comparison. Use piece list for
comparison /TDAG/RCS_PLCSC_1102 (see note 1305336)

We strongly recommend using the Cross-System Viewer for the comparison.

Because of the fact that the adjustments of the customizing works only wi th
your logon language, we recommend to do the adjustment wi th every logon
language that will be used in your system.

The sorting in the piece list cannot control whi le the creation of the list. It is
possible that during the comparison and adjustment errors occurred. In this
case, continue with the adjustment and try in a second step the adjustment of
the value that throws an error.

Open the downloaded installation check document from the SAP Node
1305182 and execute the steps in chapter 5.1 Cross System Check and fill
out the gaps or tick the checkboxes.
Additional IMG Activities

12 January, 2011
2.2 Additional IMG Activities
Go through the following customizing acti vities in the IMG under REACH Compliance taking
into account the appropriate documentation of each IMG acti vity.
Executing IMG acti vity REACH Compliance Organizational Data.

Do not forget to create at least one legal entity and organi zational unit for SAP
REACH Compliance using the appropriate IMG acti vities.
Executing IMG acti vity REACH Compliance Analytics and Reporting Xcelsius
Integration asks you to replace the placeholders wi thin the URL deli vered with the
product standard by your own <host>, <port> and <client>. Look for the Web Service
configuration in Chapter Configuration of the Xcelsius Integration.

Here is an example how the URL might look like:

Some identifiers for REACH are deli vered. If you want to add other identifiers use
IMG acti vi ty Environment, Health & Safety Basic Data and Tools Specification
Management Specification Master Check Identification Types to create the new
identifier.
Afterwards, use IMG acti vity Environment, Health & Safety Basic Data and Tools
Specification Management Specification Master Check Identification Listing
to create identification listing for SAP REACH Compliance.
Select listing ID:
a. RCS_REACH Standard listing for identifiers to change the identifier listing
to your needs. This list wi ll use for the maintenance in the Substance
Management and Legal Processes. Among other things with this list, it is
possible to define the amount of editable identifiers in the Substance
Management.

Be careful if you want to change the following identifiers as the business logic
of SAP REACH Compliance is dependent on these identifiers! We strongly
recommend not changing or removing these identifiers:

o NAM.RCS
o NUM.CAS
o NUM.RCSECNUM

These identifiers will also use for the hit list on the search views for the
Substance Management and Legal Processes.
b. RCS_RSRL Identification list for Material Management and will use for the
display of the indents in the Real Substance Assessment
Additional IMG Activities

January, 2011 13
Create REACH substance authorization groups (RSAGs)
Use IMG acti vity Environment, Health & Safety Basic Data and Tools
Specification Management Specification Master Specify Authorization Groups
to create authorization groups for REACH substances.
Select specification category Substance.
Create substance legal authorization groups (SLAGs)
Use IMG acti vity Environment, Health & Safety Basic Data and Tools
Specification Management Additional Information for Value Assignment Usage
Specify Validity Areas to create authorization groups for substances in
consideration of legal enti ties.
Select validi ty area category LEGENT.

Do not use same name for legal entity and plant even if the validi ty area
category differs.

Partner and Contact Functions
SAP REACH Compliance uses partner functions and contact functions to find contacts for the
supply chain collaboration. These partner functions and contact functions are deli vered with
the product standard. If you want to reuse your existing business partners (supplier,
customers) and existing contacts wi th their address data, change the partner and contact
functions to your own functions wi th IMG acti vity Environment, Health and Safety
Compliance for Products Technology Basic Data Specify Determination for Business
Partners and Contacts.
See documentation of the IMG acti vity for further details.

1305182 and execute the steps in chapter 5.2 Additional IMG Activities and
fill out the gaps or tick the checkboxes.

Classes and Characteristics

14 January, 2011
3 Content
3.1 Classes and Characteristics
Move Classes and Characteristics to Productive Client
To transfer the classes and characteristics from client 000 to your producti ve client use the
client copier (transaction SCC1) with component piece list /TDAG/RCS_PLCL_11_02.

The piece list /TDAG/RCS_PLCL_11_02 is part of the deli very of SAP
REACH Compliance and the list shall be available in the transaction SCC1.
Material Classification
Use SAP Class System to create class ZRCS_REACH_REL for the REACH relevance with
class type 001 (material classification). The class name has to be maintained as value for the
environment parameter SVT_MATERIAL_CLASS use the IMG acti vity Environment, Health
and Safety Basic Data and Tools Basic Settings Specify Environment Parameters for
this purpose.

Add the characteristics documented as follows to your already configured
class for Material Classification instead of creating a new class, if you have
already processes of Substance Volume Tracking implemented. Perform the
IMG acti vi ty "Activate Material-Classification-Characteristics Phrasing"
afterwards.
The IMG acti vity only updates the phrase set assignments of those
characteristics which are configured with a value check function module
specific for SAP REACH Compliance.

Enter the characteristic of this class as shown in the screenshot below using transaction
CL02 and check whether the characteristics are defined as shown in the screenshots.


January, 2011 15
SAP_RCS_MATBAS_ISRELEVANT
o Description: REACH Relevant
o Data Type: CHAR
o Number of Chars: 1


16 January, 2011
SAP_RCS_MATBAS_MATNATURE
o Description: REACH Material Nature
o Data Type: CHAR


January, 2011 17
SAP_RCS_MATBAS_MATEXEMPTION
o Description: REACH Material Exemption
o Data Type: CHAR


18 January, 2011
SAP_RCS_MATBAS_INTERMEDIATE
o Description: REACH Isolated Intermediate
o Data Type: CHAR


January, 2011 19
SAP_EHS_SVT_RELEVANT
o Description: Relevant for SVT
o Data Type: CHAR

After having created this material class and having added it to the environment parameter,
the IMG acti vity REACH Compliance Basic Data Activate Material-Classification-
Characteristics Phrasing has to be executed.

1305182 and execute the steps in chapter 6.1 Classes and Characteristics
and fill out the gaps or tick the checkboxes.

Create Phrase Sets and
Phrase Set-to-Attribute Assignment

20 January, 2011
3.2 Create Phrase Sets and
Phrase Set-to-Attribute Assignment
To create the phrase sets and the phrase set attribute assignment start in the SAP GUI the
transaction SPRO and navigate to the IMG acti vity:
REACH Compliance -> Basic Data -> Create phrase sets
This acti vi ty creates all currently nonexistent phrase sets, which are given in system table
/TDAG/RCSW_PHSET, including language dependent descriptions in English and German.
This acti vi ty creates also the currently non-existing phrase set to attribute assignments, which
are given in system table /TDAG/RCSW_PAWM.
Already existing phrase sets and attribute assignments wi ll not be changed at this.
3.3 Match Up Master Data
Execute the transaction CGCZ Match Up Master Data with the following options enabled:
Match Up ValAss Type and Char.
Activate Phrasing of Characteristics
Activate Phrasing of Fields

3.4 Import of the phrases
SAP REACH Compliance uses the phrases that are including in the SAP Note 1299496.
Prerequisite
Read the installation and configuration guide, which is attaching to the SAP Note 1299496.
Import
Follow the installation and configuration steps from the guide to install the phrases.

1305182 and execute the steps in chapter 6.2 Phrases and Phrase Sets and

Determination of Configuration Parameters

January, 2011 21
4 Additional Configuration
4.1 Determination of Configuration Parameters
SAP REACH Compliance solution uses the SAP ERP as backend. Thus, make sure that the
CPIC/RFC protocol is unlocked between the SAP ERP system and the NetWeaver Java
engine.
To be able to configure this backend connection you need the following information:
Type Example
Load Balancing of SAP ERP System No
If no Load Balancing: System name (host) of SAP ERP system vmc01
If no Load Balancing: System number of SAP ERP 00
System ID of SAP ERP TDH
Gateway-Host of SAP ERP vmc01
Gateway-Service of SAP ERP sapgw00
Language for the connection EN
Client of the SAP ERP to connect 050
Name of the RFC user for the connection RCS_USER
Password of the user MyPassword123
Message Server leave empty
Logon Group leave empty
HTTP port of the back-end vmc01:8000

Portal Configuration

22 January, 2011
4.2 Portal Configuration
4.2.1 Removing Obsolete Log Configuration
This section about removing obsolete log configuration is only relevant on upgrading from
any patch level of SAP REACH Compliance 1.0. Follow the illustrated steps below to remove
the trace location of SAP REACH Compliance 1.0, which has been replaced by another one.
Connect to NetWeaver Web Administrator on the Server, where the component
TDAG_RCS_INV has been deployed.
Navi gate to Confi guration Log Configuration Tracing Locations and select location
de.technidata.rcs.inv from the hierarchy.

Click Remove Location from the tables toolbar.

Click Save Configuration to save your changes.

4.2.2 Portal Content System Administration
You create a logical system in order to connect to a specific back-end application.

Do not forget to setup the permissions after having configured the system.
Chapter User Management [page 55] (sub-chapter Setting up the
Permissions in Enterprise Portal) describes how to do so.

1. Go to System Administration
2. Go to System Configuration
3. Go to Portal Content (right side panel), open that folder.
4. Right click on Portal Content, a panel is displayed select New System (from
template).


January, 2011 23

5. A new vi ew on the right side is shown. Select SAP system using dedicated
application server from the exi sting templates. (Other templates are possible - for
example, load balanced or through a SAProuter connection string.)
6. Enter the System Name and System Id which are mandatory fields. Enter any brief
notes in the Description field in case you want to.
7. Open the newly created system.
8. To be able to create the new system you need to enter the following data:
a. Connector
Contains basic connectivi ty details
b. User Management

Connector Details
The connector property has the following mandatory fields:

24 January, 2011
Required Field Description
Application Host The application host should be a fully qualified hostname. Gi ve the
SAP ERP Application Name, which can be obtained from the SAP
Logon Pad (check what SAP ERP system you are using, right click
on it, go to the properties, a window will open up which has the
Application Server Name.
Logical System Name Gi ve the logical name as defined in the backend system. Retrieve
the logical system name:
Log on to the back-end-system
Start transaction SALE
Navi gate to node IDoc Interface/Application Link Enabling (ALE)
Basic Settings Logical Systems Define Logical System
Pick the suitable name from column name of the displayed list
(most often these names are concatenations of system name
and client number in the form <system ID>CLNT<client>).
If the column name is empty, the customi zing is not done yet.
Enter suitable names in the above mentioned format.
SAP Client Check the Client in the back-end-system and give the appropriate
number (3 digits)
Sap System ID (SID) Check the SAP ERP properties and gi ve the check for System ID
Server Port The port is the concatenation of 32 and the system number. E.g. if
the system number is 00 the server port is 3200.
System Type Gi ve the correct system type (select SAP_R3 system).
System Number This is a two digit number that you can find in the SAP Logon Pad
Web AS Hostname Hostname and HTTP port of the back-end system. The port number
is a concatenation of 80 and the system number. E.g. if the system
number is 00 the Web AS port is 8000.
Web AS Protocol There are two protocols "http" and "https". Select the appropriate
protocol which is visible when you open the Test Service window.

User Management Details
The User Management property has the following mandatory fields:
Required Field Description
Authentication Ticket
Type
Only relevant if Logon Method is SAPLOGONTICKET: Type of
authentication tickets used to log on to SAP system.
Logon Method Authentication method used to log on to SAP system:
SAPLOGONTICKET
UIDPW
X509CERT
User Mapping Type In case you have rights for administration choose admin or in case
you just have user rights then choose user, better go for
admin/user.


January, 2011 25
Setup Logical System Alias
A system alias identifies uniquely each SAP system in the portal system landscape. All SAP
REACH Compliance portal content objects rely on the system alias RCS_Backend.
The logical system created in chapter Portal Content System Administration [page 22]) needs
the system alias named RCS_Backend
Provide the system alias for the participating systems in the system landscape using the
System Aliases Editor.

4.2.3 RFC-Connection
Use
After the installation of the ABAP stack, the JAVA stack and the portal content has been
finished it is necessary to create the connection between the frontend and the backend.
Procedure
1. Starting Destination Service
The JCo Service provider uses the SAP ERP as repository to look up the runti me description
of the server function. That means SAP ERP defines a RFC function module (stub). The
interface is queried at runtime from the JCo service provider to map the data from the RFC
layer to Java data types. The settings have to be configured using the Visual Administrator of
the SAP NetWeaver J2EE Server.
1. Start the Visual Administrator on your computer and connect to the corresponding
server.
2. Navi gate to the tree item Server/Services/Destinations.


26 January, 2011
2. Creating RFC Destinations
To get the SAP REACH Compliance solution up and running the following two RFC
destinations have to create in the Destinations folder:
Field name Destination 1 Destination 2
Destination Name TDAG_RCS_IMG TDAG_RCS_APP
Destination Type RFC RFC
Load Balancing <see prerequisites> <see prerequisites>
System <see prerequisites> <see prerequisites>
System Number <see prerequisites> <see prerequisites>
System ID <see prerequisites> <see prerequisites>
Message Server <see prerequisites> <see prerequisites>
Logon Group <see prerequisites> <see prerequisites>
Gateway host <see prerequisites> <see prerequisites>
Gateway service <see prerequisites> <see prerequisites>
Authentication Configured User Current User (Logon Ticket)
Language <language of technical user, for
example EN>
<see prerequisites>
Client <see prerequisites> <see prerequisites>
Username <name of the technical user> disabled
Password <password of the technical user> disabled

The figure below shows that the RFC client destination has already been
created which is used to connect direct to a SAP system called TDH. This is
an example for the TDAG_RCS_APP destination configuration, which we
strongly recommend as connection setting for the REACH application.


January, 2011 27

The figure below shows that the RFC client destination has already been
created which is used to connect to a SAP system called TDG with the use of
a message server.

Caution:
o You can use HTTP load balancing on the SAP Message Server for
stateless applications only. For stateful Web applications wi th a state in
the back end (such as BSP applications), you require the Web
Dispatcher.
o You can only use the SAP message server for HTTP load distribution if
the browser is the direct client of the message server. If another
component lies between the client (browser) and the message server, (for
example, the portal), you cannot use the message server to distribute the
load.

We strongly recommended not using this kind of connection setting.

Select Current User (Logon Ticket) at RFC destination for single-sign-on.
4.2.4 Configure JCo Client RFC Destination
Use
This chapter describes how to define the RFC client destination. The RFC destination has to
be maintained on the server where the Java component technidata.de/TDAG_CP_SCOLL
has been deployed.

If you have not applied the recommended scenario and you have separate
servers for the Java application and for the portal, the RFC destination has to
be maintained on the server on which the Java application runs.

To maintain the destination open a browser and connect to the server
(http://<host>:<port>/). Navigate to Web Dynpro Content Administrator and
proceed with step 3 of the procedure mentioned below.


28 January, 2011
Procedure
1. Open a browser and connect to SAP NetWeaver Portal as administrator
(http://<host>:<port>/irj/portal)
2. Navi gate to Content Administration WebDynpro
3. Check, that the System Landscape Directory (SLD) connection is active by clicking
Check SLD Connection
4. Click button Maintain JCo Destinations

5. If you have a destination called /TDAG/CP_CUSTOMIZING proceed at 14
6. Click on Create JCo Destination
7. Fill in the name /TDAG/CP_CUSTOMIZING and the client of the SAP ERP system, to
which the connection shall be established in the first step.

8. Go to step 3 and choose the options shown in the screenshot below.

9. Select the SAP ERP system form the list of systems known by the SLD in the next
step.

January, 2011 29

10. In the next step, enter the user credentials to be used for the connection. It is
recommended to use a non-dialog user for this.

It is vitally important that you select User/Password as Used
Method!

11. The configuration is completed when clicking Finish in the next step.
12. Check the configuration of the JCo Destination

13. Enter the client number of the SAP ERP system where the portal has to connect to
and click the Next button.

30 January, 2011

14. Select the application server to which the connection has to be established and press
the Next button.

15. Edit the user authentication providing user and password for the client connection.

Special attention to the password is required dependent on the
security configuration regarding RFC logon of the back end system.
If the back end system is configured to support case sensiti ve
passwords, the password has to be entered case sensiti ve, else it
must be entered on upper case letters.

January, 2011 31

16. Verify your settings and press the Finish button.

1305182 and execute the steps in chapter 7.1 Portal Configuration and fill

Configuration of Backend

32 January, 2011
4.3 Configuration of Backend
4.3.1 Creating Number Ranges
Internal and external number ranges have to be created for the following number range
objects wi th transaction SNUM whereas 01 is used for internal and 02 for external number
ranges:
/TDAG/RCS1 for Studies
No From number To number Current number Ext
01 000000000001 899999999999
02 A ZZZZZZZZZZZZ
/TDAG/RCS2 for Alternati ves
01 000000000001 899999999999
02 A ZZZZZZZZZZZZ
/TDAG/RCS3 for Testing Proposals
01 000000000001 899999999999
02 A ZZZZZZZZZZZZ
/TDAG/RCS4 for Letter of Access
01 000000000001 899999999999
02 A ZZZZZZZZZZZZ
/TDAG/RCS5 for Data Waiving
01 000000000001 899999999999
02 A ZZZZZZZZZZZZ
/TDAG/RCS6 for Literature
01 000000000001 899999999999
02 A ZZZZZZZZZZZZ

Use also transaction SNUM to verify that the following number range intervals do exi st:
/TDAG/CPN0 interval 01
01 00000000000000000001 99999999999999999999

January, 2011 33

/TDAG/CPN1 interval 0I
0I 00000000000000000001 89999999999999999999

/TDAG/CPN2 interval 0I
0I 00000000000000000001 89999999999999999999

1305182 and execute the steps in chapter 7.2.1 Number Ranges and fill out
the gaps or tick the checkboxes.

4.3.2 Deactivation of User Exits
The implementation of the exit CLFM0002 by function module
/TDAG/CP_BB10R_MATCL_CHG_SCAN has become obsolete for SAP REACH
Compliance. The exit based logic has been replaced by an alternati ve logic to determine
material classification changes. We recommend that you remove the function module for this
exit if you have no other implemented processes that rely on this exi t.

4.3.3 BAdI Implementations
This sub-chapter describes how to implement or change required BAdIs.

BAdI /TDAG/CP_BADI_005
If you do NOT use the default implementation of BAdI /TDAG/CP_BADI_005 but an own
implementation you have to consider that the definition of this BAdI has changed. The filter
type has changed from /TDAG/CPE_REQNO to /TDAG/RCSE_UEC_EMLCONFID.
Accordingly, filtering is now done by the e-mai l configuration ID rather than the request ID in
the standard implementation.

BAdI EHSS_SPEC_CHECKS
The BAdI EHSS_SPEC_CHECKS (Extended Check for Specifications) has to be
implemented so that the category information for specifications is created automatically. To
do so, use the IMG acti vity Environment, Health & Safety Basic Data and Tools
Specification Management BAdI: Extended Checks for Specifications.
Every time you save a specification, the acti vated BAdI checks if the category information flag
for the specification is set. If it is not set the BAdI sets the flag to false. This exit avoids
incomplete search results for specifications if you look for the category flag if the flag was
not set the specification wouldnt be part of the search result, neither within the search for the
category flag set nor within the search for the category flag not set.

Read the documentation of this IMG acti vity attenti vely before executing it.

34 January, 2011

Proceed as follows:
1. Follow the IMG documentation to create a new BAdI implementation. The
implementation does not need any filters.
2. On the Interface tab you find the methods of the generated BAdI class. Double-click
the method AT_SAVE_CHECK to get the implementation of this method. Add a call
for the function module /TDAG/RCS_SUB_SAVE_CHECK. The method then should
look like as follows:
method IF_EX_EHSS_SPEC_CHECKS~AT_SAVE_CHECK.

CALL FUNCTION '/TDAG/RCS_SUB_SAVE_CHECK'.

endmethod.

The other methods of this class do not need any coding.

3. Save and acti vate your implementation (class and methods).
4. Go back to the BAdI implementation and acti vate it.

4.3.4 Adapt AIF REACH Templates
For the supply chain collaboration templates for questionnaires that are sent to customers
and suppliers are avai lable in your system after the installation. Addi tionally, you have to
configure them once at the beginning.
With the SAP REACH Compliance product standard three questionnaire templates (.pdf
documents) are deli vered which require adaption before they are ready to use for supply
chain collaboration. The following templates are deli vered:

Form for the use collection: Customer REACH region
(/TDAG/RCSAIF_UEC_CUS_REACH)

Form to collect the OR: Supplier non REACH
(/TDAG/RCSAIF_UEC_SUP_NON_REACH)

Form for the collection of the registration status: Sup / OR
(/TDAG/RCSAIF_UEC_SUP_OR_REACH)

Do not use the questionnaire templates deli vered with the product standard wi thout
having adapted them as described in this document.


January, 2011 35

Before you can use the deli vered .pdf templates for supply chain collaboration it is required
that you change the e-mail address of the mailto: button in the footer of the documents to
the appropriate e-mail address of your company. To do so, follow the steps below for each of
the three forms use transaction SFP:
1. Copy the default templates
Enter the form name
Copy each form and enter the name beginning wi th Z_ instead of /TDAG/
o Z_ RCSAIF_UEC_CUS_REACH
o Z_ RCSAIF_UEC_SUP_NON_REACH
o Z_ RCSAIF_UEC_SUP_OR_REACH

2. Change the layout of each form
Open the form with the Change option and proceed as follows
Select Layout

The button Layout does only work if the user, who is adapting the form, has a local
installation of Adobe Formdesigners. Adobe Formdesigners is contained in the
SAP NetWeaver package and can be downloaded from the SAP Service
Marketplace.
Select the view Master Pages to edi t the page footer
Select the button and change the label of the button (Field Caption) and the
e-mail address (Field Submit) to your own e-mail address

Adapt the company data in the page footer to your own data
Save and activate your changes
3. Translate the form
Select menu item Go to Translation to translate the label of the button
4. Change the configuration
Open IMG acti vity REACH Compliance Communication with Business Partners
Define Templates
Select the template and navi gate to Template Language / Country dependent
Change the Forename from /TDAG/ to Z_...


36 January, 2011

If you want to use own documents from your DMS instead of the deli vered templates
as e-mai l attachments within the supply chain collaboration, you have to configure
the template of type DMS document. To upload these documents into your DMS
with the correct document type proceed as follows.
To be able to load your own documents into the DMS the SAP REACH Compliance
configuration for the number ranges has to correspond with the DMS configuration.
To check the SAP REACH Compliance configuration use the IMG acti vi ty
Environment, Health & Safety Compliance for Products Technology Basic
Data Document Management Check Document Types and Document Status.
Double-click on IBD/Inbound Document and check the Number Assgmt.
If you have not already installed and configured your DMS, we recommend to set the
Number Assgmt to value 5 (External number assignment without number range
check only).


January, 2011 37

For each of the following document types the Screen no. within the object link has
to be defined as shown in the screenshot below (Screen no.: 500). This is
contained in the standard deli very of the customizing. Nevertheless, ensure that the
Screen no. is correct.

o CPD
o CPT
o CPE

It is also required, that the link to the object Substance (ESTRH) is configured.

Additional Information for Supply Chain Collaboration
If you send an e-mai l to your business partner with a .pdf form (generated from the REACH
templates mentioned above) attached, the business partner might attach some documents to
the .pdf form in his response. These documents are transferred wi thin the .pdf document.
During the task execution within your company (maintenance of use and exposure) these
attachments (contained in the .pdf form) are extracted from the .pdf document and stored in
your DMS with the document type CPD.

1305182 and execute the steps in chapter 7.2.2 Adapt AIF REACH
Templates and 7.2.3 ADS setting and fill out the gaps or tick the
checkboxes.


38 January, 2011
4.3.5 Legal Entities
A legal entity in terms of REACH means a legally autonomous company that has to register
the substances that are used within the own company.

At least one legal entity has exists in REACH and can be maintained wi th the
IMG acti vi ty Create Legal Enti ties for REACH.

4.3.6 Business Partners
Use transaction BP to create business partners. Consider the following:
for companies select Organization
for groups (e.g. SIEFs) select Group
for persons select Person
Do always enter RCS for BP Type (business partner type). Only business partners of type
RCS are considered in SAP REACH Compliance.

Authorization groups have to be maintained as prerequisite so that the
business partners are displayed and avai lable within the portal application.

Use IMG acti vity Cross-Application Components SAP Business Partner
Business Partner Basic Settings Authorization Management Maintain
Authorization Groups to maintain the appropriate authorization groups.

The authorization groups might look as follows.


January, 2011 39
4.3.7 E-Mail Processing
Prerequisite
A technical system user is required to set up a background job. Following parameters for the
technical user have to be set:
User Type Service
Logon Language EN
Profile S_A.SCON

E-Mail Outbound
To be able to send e-mails to external e-mai l addresses the SAP ERP has to be configured
as follows.
There are two possibilities to send out e-mai ls: either schedule a job in regular periods or use
transaction SCOT. Call transaction SCOT for job definition and push button Jobs to see
which job is scheduled. We recommend to schedule a regular job (period 5 min) for the
address type INT with the technical user which was created as prerequisi te.
For the customer and supplier collaboration the environment parameter for the reply-to-
addresses have to be maintained in each client manually.

Sending E-Mails Asynchronously
Since support package SP04, campaign management sends out e-mail asynchronously by
default. An event and an event-driven job must be setup to complete the configuration of this
functionali ty. For a more detailed description of the configuration steps, see SAP Notes
1402876 and 1501031.

E-Mail Inbound

Your back-end system has generally to be configured for receiving e-mails. See SAP
standard documentations for detai lled information:
http://help.sap.com/saphelp_nw2004s/helpdata/en/af/73563c1e734f0fe10000000a11
4084/frameset.htm
To enable the system to handle incoming e-mai ls properly, the following configuration has to
be done:
Define two e-mai l addresses one for CRM and one for SRM.
srm@<sysid>CL<client>.<your domain>
crm@<sysid>CL<client>.<your domain>
Create shared folders in the SAP Business Workplace.

40 January, 2011

Use transaction SO16 to ensure that the address type SAP Business Objects is activated.
This is necessary to forward e-mails to a shared folder.

Use transaction SO28 to specify the settings for inbound distribution. Ensure that incoming e-
mai ls from external are automatically forwarded to the shared folder which is supposed to be
used to store incoming compliance related e-mails.

January, 2011 41

Variants for the Report
Two variants to process the e-mai ls are needed. Create the following two variants for the
report /TDAG/CPR_TASK_EMAILPROCESS using transaction /TDAG/CPT03.

Variant CUSTOMER

42 January, 2011

Variant SUPPLIER


January, 2011 43

1305182 and execute the steps in chapter 7.2.4 Email Processing and fill

4.3.8 Portfolio Reporting
Prerequisite
To register the Java RFC function in the ABAP RFC Connections service a technical system
user is required. Following parameters for the technical user have to be set:
User Type Communications Data
Logon Language EN
Roles SAP_J2EE_ADMIN
Profile SAP_ALL

Configure the Portfolio Reporting
The portfolio reporting contains the functionali ty to generate the report in a background
process and to send it afterwards to a gi ven e-mail address. For that purpose the RFC
destination TDAG_RCS_PFR_GEN_RFC has to be maintained at the environment
PFR_BGR_RFC_DEST parameter (IMG acti vity REACH Compliance Basic Data Maintain
environment parameters).
Additionally, the IMG acti vity REACH Compliance Analytics and Reporting Set
spreadsheet reports has to be executed. Check whether the thresholds of all reports are set
properly.
Max.subst.:
The overall threshold for report generation maxi mum number of substances; if
more substances are selected the report is not executed
Max.S*WSh:
The overall threshold for report generation maxi mum number of substances
multiplied by the number of worksheets in the result file; if the number of selected
substances multiplied by the number of worksheets is greater than the threshold the
report is not executed
Subst. BG:
The threshold between online and background processing maximum number of
substances; if the number of substances is greater than the threshold, the report is
generated in the background and sent via e-mai l to the addressee
BG sub*ws:
The threshold between online and background processing maximum number of
substances multiplied by the number of worksheets in the resul t file; if the number of
substances multiplied by the number of worksheets is greater than the threshold, the
report is generated in the background and sent via e-mail to the addressee

44 January, 2011

Take care that the communication type of the RFC destination is set to the
communication type of the target system!

Execute transaction SM59 to check or if necessary to setup the RFC destination TCP/IP
connections TDAG_RCS_PFR_GEN_RFC.
RFC Destination TDAG_RCS_PFR_GEN_RFC
Connection Type TCP/IP Connection
Activation Type Registered Server Program
Program ID TDAG_RCS_EJB_REP_SERVICE
(Remember thi s name because it will be used in the Web AS
configuration)

It is important that the communication type on the tab "MDMP & Unicode" is
set to the type of the target system.

Set the communication type to "Unicode" when the target system is a
Unicode system


January, 2011 45

Additionally, the configuration and registration of the Java service has to be done via the
Visual Administrator on the Web Application Server.
Configure the main service in the JCo RFC Provider. Enter the same Program Id as in the
RFC destination at the back-end (TDAG_RCS_EJB_REP_SERVICE). The other fields are the
standard configuration for connecting to the back-end.

Add a new RFC destination whereas the Destination Name also represents the Program Id
configured as destination in transaction SM59.

See also chapter RFC-Connection [page 25] for details on how to setup the RFC
destination.

Select Confi gured User at RFC destination for single-sign-on and use the technical
user which was created in the Prerequisi te of this chapter.

After having configured the Java service the connection can be tested and checked with the
two buttons:
Connection Test
Checks the connection to the Java service
Unicode Test
Provides the information about the communication type of the target system
You can also get the information about the target system wi th the menu item Extras
System Information Target System.

46 January, 2011

1305182 and execute the steps in chapter 7.2.5 Portfolio Reporting and fill

4.3.9 Configuration of the Xcelsius Integration
SAP REACH Compliance integrates Xcelsius for the Campaign Overview (Xcelsius
Dashboard).
Prerequisite
The IMG acti vity REACH Compliance Analytics and Reporting Xcelsius Integration was
executed and the placeholders for <host>, <port> and <client> are replaced by your own
ones:
<host> fully qualified name wi th domain of the ERP application server
<port> http port of the ERP application server; by default 8000
<client> client of your ERP system
Activation of Web Service
Execute transaction WSCONFIG to activate service /TDAG/RCSWS_UEC_CAMP_
OVERVIEW.

If this service is not yet listed (see also screenshot above), you have to create it. To do so,
click on the Create button (F5) and add it. Enter the data shown in the screenshot below:
Name: /TDAG/RCSWS_UEC_CAMP_OVERVIEW
SOAP Application: urn:sap-com:soap:runtime:application:rfc
Release Text: Web Service /TDAG/RCSWS_UEC_CAMP_OVERVIEW
Virtual Host: default_host
URL: /sap/bc/srt/rfc/TDAG/RCSWS_UEC_CAMP_OVERVIEW


January, 2011 47

Maintain Services
After having acti vated the web service, the appropriate web service node must be acti vated.
To do so, execute transaction SICF and navigate to default_host sap bc srt rfc
TDAG activate web service RCSWS_UEC_CAMP_OVERVIEW.

Additionally, the node default_host sap bc bsp tdag ehfnd_xcel must be
activated, to enable the iView accessing the Business Server Pages (BSP), which render the
Xcelsius Flash into HTML.

Setup User Authorization
By assigning a copy of the template role /TDAG/RCS_TEMPLATE to the user, all required
authorizations are assigned. For more information about the required authorizations and
system table entries, see SAP Note 1412641.

CFP Worklist Management

48 January, 2011

1305182 and execute the steps in chapter 7.2.6 Xcelsius Integration and fill

4.4 CFP Worklist Management
Ensure that the job for work list determination and execution are scheduled. The job has to
contain the following steps:
/TDAG/CPR_WORKLIST_DETERMINATE
Determine relevant objects for execution
/TDAG/CPR_WORKLIST_EXECUTE
Execute the work lists

1305182 and execute the steps in chapter 7.2.7 Worklist Management and

4.5 Configure Internet Graphics Service
SAP REACH Compliance uses the Internet Graphics Service (IGS) for Campaign Moni toring.
Therefore, the IGS must be setup as described in this chapter.
Prerequisite
Ensure that the Internet Graphics Service runs on your ABAP stack and that it is acti vated.
Configure URL for IGS
To enable the Java web application server routing enquiries for the Internet Graphics Service
properly, the correct URL has to be maintained in the WebDynpro configuration. Apply SAP
Note 704604 to do so.

1305182 and execute the steps in chapter 7.3 Internet Graphics Service
and fill out the gaps or tick the checkboxes.

Configuration of Workflow

January, 2011 49
4.6 Configuration of Workflow

4.6.1 Workflow-based Material Assessment
Material Assessment of SAP REACH Compliance integrates the capabi lities of SAP Business
Workflow. For a deeper understanding of the underlying workflow mechanism this
documentation may be useful as an introduction.
http://help.sap.com/saphelp_nw70/helpdata/en/a1/172437130e0d09e10000009b38f839/fram
eset.htm
4.6.2 Universal Work List (UWL)
This sub-chapter describes how to configure the system alias for work item retrieval.

Prerequisites
The standard configuration for the UWL must be present especially, the view definition for
DefaultView.
System alias RCS_Backend must be present and point to your backend system. See chapter
Setup Logical System Alias [page 25] for detai led description of how to create this alias in
your System landscape.
Create connector

To find the UWL configuration login to your portal as administrator. Navigate to
System Administration System Configuration Universal Worklist & Workflow
Universal Worklist Administration.


50 January, 2011
Create new connector executing the following steps:
1. Click on button New
2. Enter data for
System Alias: RCS_Backend
Connector Type: WebFlowConnector
3. Click button Save
4. Register the backend system by pressing button Register (button wi ll be renamed to
Re-register after successful registration)

1305182 and execute the steps in chapter 7.4 Workflow Check UWL
Configuration and fill out the gaps or tick the checkboxes.

4.6.3 Workflow
Prerequisites
The SAP Business Workflow itself defines the following roles in order to define the
permissions concerning workflow execution and administration:

Role Description
SAP_BC_BMT_WFM_ADMIN Administrator for Business Workflow
SAP_BC_BMT_WFM_CONTROLLER Process Controller for Business Workflow
SAP_BC_BMT_WFM_DEVELOPER Developer for Business Workflow
SAP_BC_BMT_WFM_PROCESS Business Workflow Implementation Team
SAP_BC_SRV_USER User for Communication, Workflow,
Appointments

Initialization
1. Automatic Workflow Customizing
If you have never used SAP Business Workflow before on your system there are some
steps to be conducted in order to initialize and configure the workflow engine. To do so
execute transaction SWU3.
Refer to the following source for a detailed description of the automatic workflow
customizing.

http://help.sap.com/saphelp_nw70/helpdata/en/a0/28e937a5caba6ee10000009b38f842/fr
ameset.htm

One effect that might occur here is that a data inconsistency in table SOBJ will be
reported. If this is the case, run report RHSOBJCH (see also the help long text). It will
automatically create the needed table entries.

January, 2011 51

1305182 and execute the steps in chapter 7.4 Workflow Check
automatic workflow customizing and fill out the gaps or tick the
checkboxes.

2. Establish event coupling
The workflows wi ll be started when ABAP objects of a certain kind are created at the
back-end. In order to couple the creation of these objects with the start of a workflow
instance, execute the following steps.
Start transaction SWDD
Open workflow template WS00276201
Display basic data: (CTRL+F8)
Navi gate to tabs Version-Independent (Task) / Start Events
Activate the event CREATED for the class /TDAG/CL_TBO_MA as shown in the
screenshot below
Save your changes

1305182 and execute the steps in chapter 7.4 Workflow Execute
workflow check report and fill out the gaps or tick the checkboxes.

4.6.4 Workflow Foundation (WFF)
Configuration
Check whether the following settings are present within your installation (using transaction
SE11 or SE16N).
Workflow Foundation as a generic component is connected to specific implementations via
two configuration tables:
/TDAG/EHFNDC_PER WFF:
Customizing: Relation between Transactional Business Object (TBO) class and
persister

52 January, 2011

In contrast to a Business Object (BO), which represents master data, a TBO
represents the processing of these master data via a workflow instance. It
stores additional data not located wi thon the BO as well as the outcome of the
process. One can think of it as a route card, e. g. a leave request.

A persister is an ABAP OO class responsible for reading/writing TBO
instances to and from the database..
/TDAG/EHFNDC_VAR WFF:
Customizing: Process variant of a TBO
These tables contain technical configurations only and must have the content listed below in
order to ensure proper functionality of Material Assessment.
/TDAG/EHFNDC_PER
TBO class name Persister class
/TDAG/CL_TBO_MA /TDAG/CL_TBO_MA_PERSISTER

/TDAG/EHFNDC_VAR
TBO class name Variant Status class name
/TDAG/CL_TBO_MA SPECIAL /TDAG/CL_MA_STATUS
/TDAG/CL_TBO_MA STANDARD /TDAG/CL_MA_STATUS
Roles
SAP Business Workflow is capable to determine possible agents (users) to whom a work
item can be assigned via different mechanisms. This may be your Organizational Plan,
specially defined rules or just roles containing a list of possible users.
The product standard of SAP REACH Compliance provides four predefined roles which
represent the four possible assessment steps for Material Assessment.
Using Predefined Roles
1. Assign users to predefined Material Assessment roles
Start transaction PFCG and assign users to the following four roles which represent the four
assessment steps:
/TDAG/RCS_ROUGH_ASSESSMENT
/TDAG/RCS_PRECISE_ASSESSMENT
/TDAG/RCS_REAL_SUB_ASSESSMENT
/TDAG/RCS_COMP_MAINT
Within these roles you must not use composite roles as the workflow engine is not capable to
resolve nested roles hierarchies. It is important to use only user names within these roles.
After having altered the members of these roles it is always necessary to refresh the
organizational environment of the workflow engine. In order to do so, follow these steps:
Go to Business Workplace (transaction SBWP)
Select menu Settings Workflow settings Refresh organizational environment

2. Maintain roles also for each task definition used within workflow template

January, 2011 53
Enter transaction SWDD and open workflow template WS00276201 in order to maintain the
settings described below.
There are four workflow steps to be configured. The node numbers and role name for each
task are listed below.

Click at a node using the Navi gation Area
Click on button Agent assignment for task
Click on button Create agent assignment (F5)
Choose Role and enter the same role as used in the workflow step

Ensure that the icon beside the button Agent assignment for task turned to green

Repeat the steps mentioned above for the following nodes
Node Task ID Role
000071 Rough Assessment TS00276203 /TDAG/RCS_ROUGH_ASSESSMENT
000075 Precise Assessment TS00276204 /TDAG/RCS_PRECISE_ASSESSMENT
000079 Real Substance
Assessment
TS00276205 /TDAG/RCS_REAL_SUB_ASSESSMENT
000087 Substance
Composition Maintenance
TS00276207 /TDAG/RCS_COMP_MAINT

Use syntax check and ensure that there are no errors and warnings


54 January, 2011
Using Organizational Plan
In principle, the explanations above apply here as well. The difference lies in using the
Organizational Plan instead of plain roles.
For details on the definition and using an Organization Plan, please refer to
http://help.sap.com/saphelp_nw70/helpdata/en/b2/145f4ac70711d2b49a006094b9c9b4/fram
eset.htm.

Implement user exit WISEXIT
In order to collect some statistical data about the workflow instances which process the
different TBO instances, a reference implementation of user exit WISEXIT has to be
provided.

*&---------------------------------------------------------------------*
*& Include ZXMCAU01
*&---------------------------------------------------------------------*

*
* User exit WISEXIT
* This code is called by FM 'EXIT_SAPLMCWF_001'
* when report RMCADATA is run.
*
* Passed parameters
* Tables paramter
* XMCWF_TRANS LIKE MCWF_TRANS
*

* Get the corresponding TBO and update its statistical data
/tdag/cl_wff_utils=>update_tbo_statistic( xmcwf_trans[] ).

Already existing code within this exi t may be kept as it does not interfere wi th other
implementations exi sting in parallel at this location.

User Management

January, 2011 55
5 Post-Installation
5.1 User Management
Creating Roles in SAP ERP
Use transaction PFCG to create security roles for users working with SAP REACH
Compliance.
The role /TDAG/RCS_TEMPLATE is deli vered wi th the product standard and can be used as
template for the creation of security roles for SAP REACH Compliance.
Adapt the four default security roles for Material Assessment (see also chapter 1.2.2 Security
Guide in the installation guide for REACH Compliance) to your needs if necessary and assign
the appropriate users to these roles.
Adapt the security role /TDAG/CP_PDM_MANAGER to your needs if necessary and assign
users who work wi th the area menu for Compliance for products to this role.
The following authorization groups have to be considered under the security aspect for SAP
REACH Compliance:
REACH Substance Authorization Groups (RSAGs)
RSAGs are authorization groups regarding substances. They define the read and
write permissions at substance level for the users with their specific roles.

The logical RSAGs are technically implemented with the help of the authorization
groups for specifications known from SAP Environment, Health & Safety (SAP
EH&S). Refer to the appropriate SAP EH&S guides for further information.
Substance Legal Authorization Groups (SLAGs)

SLAGs are authorization groups regarding substances in legal enti ties. They define
the read and write permissions for the substance properties with reference to legal
entities.
The logical SLAGs are technically implemented with the help of the usages known
from SAP Environment, Health & Safety. Refer to the appropriate EH&S guides for
further information.

See chapter Additional IMG Activi ties for more information on how to create RSAGs and
SLAGs.
Users
RSAG SLAG
Substance
Properties
dependent from
legal entity
Roles Users
RSAG SLAG
Substance
Properties
dependent from
legal entity
Roles
User Management

56 January, 2011

For more information see also SAP ERP Security Guide under
service.sap.com/securityguide
SAP ERP
Additionally, for more information see SAP NetWeaver Security Guide under
service.sap.com/instguides
SAP NetWeaver
SAP NetWeaver 2004
Security Guide

Creating Users in SAP ERP
Create users with transaction SU01 and assign the appropriate role created in the step
before.

It depends on the setting of the UME Data Source of the J2EE engine
whether it is necessary to create the same users in the Enterpri se Portal.

There is no need to create the users in the Enterprise Portal if the back-end is
selected as data source.

If you selected the J2EE engine as data source it is required that you also
create the same users in the Enterprise Portal.

Setting up the Permissions in Enterprise Portal
Navi gate to System Administration Permissions Portal Permissions and open the
navigation tree Portal Content Content provided by SAP End User Content and select
the node SAP REACH Compliance.
Select item Open Permissions in the context menu of the node SAP REACH Compliance.
The Permission editor for the SAP REACH Compliance opens up.
Search for each role of SAP REACH Compliance, select it and press the Add button (see
also screenshot below).

Role Technical name
Product Manager de.technidata.rcs.pc.role.productmgr
Substance Manager and
Registrant
de.technidata.rcs.pc.role.substancemgr
Sales-Oriented Employee de.technidata.rcs.pc.role.salesemp
Purchase-Oriented Employee de.technidata.rcs.pc.role.purchemp
REACH Administrator de.technidata.rcs.pc.role.admin

Test the Installation

January, 2011 57

Set the checkbox End User and press the Save button. The system will ask you if you want to
save confirm with Yes.

The permissions can now be assigned to the end users in the next step.
Repeat the steps mentioned above for the logical system from chapter Portal Content System
Administration [page 22].
Assigning portal roles to users
Open the web browser and start the user administration program using the URL pattern
http://<host>:<port>/useradmin.
Press the button Identity Management and select the values Role and Portal Role as search
criteria. Leave the input field empty and press the Go button. Each user for the SAP REACH
Compliance solution has to have at least one of the five roles mentioned above.
To assign a role to other users select the role, press the Modify button and open the tab page
Assigned Users. All users that are currently assigned to the selected role are listed here.
Select the user on the right view and press the Add button to assign new users. Do not forget
to Save your settings.

1305182 and execute the steps in chapter 8 Check User Management and

5.2 Test the Installation

It is recommendable to verify the installation and configuration wi th help of the
sanity check, which is finding in note 1305182.

Please use the sanity check to verify the installation and configuration before
requisition a support.

SReach Compleance - ConfigGuide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SReach Compleance - ConfigGuide

Hochgeladen von

Copyright:

Verfügbare Formate

Configuration Guide

Das könnte Ihnen auch gefallen