EHSM 2 Master Guide 2012
EHSM 2 Master Guide 2012
EHSM 2 Master Guide 2012
Public
Document version 1.2 May 2012
notice.
System p5, System x, System z, System z10, System z9, z10, z9,
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.
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.
Disclaimer
Some components of this product are based on Java. Any code
change in these components may cause unpredictable and severe
Open Group.
Any Java Source Code delivered with this product is only to be used
way.
Typographic Conventions
Type Style
Example Text
Represents
Icon
Meaning
Caution
Cross-references to other
documentation
Syntax
Example text
EXAMPLE TEXT
Example text
Icons
Example text
<Example
text>
EXAMPLE TEXT
Example
Note
Recommendation
History of Changes
The migration information is regularly updated.
Make sure you have the latest version of the migration information by
checking SAP Note 1580000.
The following table provides an overview of the most important changes that were made in
the latest versions.
Important Changes
May 2012
Contents
History of Changes ................................................................................ 4
May 2012
May 2012
1 Getting Started
1 Getting Started
1.1 About this Document
This document provides an overview of a migration scenario from the earlier SAP solution for
managing environment, health, and safety (formerly called SAP EH&S) to the new
component extension 2.0 for SAP EHS Management. In the remainder of this document, the
earlier SAP solution is referred to as the "EHS solution as part of SAP ERP", and the new
component extension 2.0 for SAP EHS Management is referred to as the "add-on" in the
body text. It describes coverage of business scenarios, data migration issues, and the
particular migration steps to be executed.
The central starting point for the technical implementation of your SAP
application/solution is the Master Guide, which you can find on SAP Service
Marketplace at http://service.sap.com/instguides.
Content
Description
Location on SAP
Service Marketplace
http://service.sap
.com/instguides
SAP Business Suite
Applications
SAP EHS Management
Component
Extension for SAP
EHS Management
Release 2.0
http://service.sap
.com/instguides
SAP Business Suite
Applications
SAP EHS Management
Component
Extension for SAP
EHS Management
Release 2.0
May 2012
1 Getting Started
http://service.sap
.com/instguides
SAP Business Suite
Applications
SAP EHS Management
Component
Extension for SAP
EHS Management
Release 2.0
http://service.sap
.com/instguides
SAP Business Suite
Applications
SAP EHS Management
Component
Extension for SAP
EHS Management
Release 2.0
http://service.sap
.com/ehs
General information
about SAP EHS
Management
http://service.sap.com/message
http://service.sap.com/notes
http://service.sap.com/swdc
http://service.sap.com/rkt
May 2012
2 Migration Overview
2 Migration Overview
2.1 Migration at a Glance
Component extension 2.0 for SAP EHS Management is an add-on that provides business
scenarios for managing environment, health, and safety in a homogenous, process-oriented
way. In this version, the add-on contains new functionality for incident management and risk
assessment.
The risk assessment functionality delivered in component extension 2.0 for SAP EHS
Management does not support integration with the specification database to access
reference values, measurement projects, or the definition of HR tasks or materials as risks.
This functionality supports customers with a low number of hazardous substances that are
not used in an integrated scenario with other processes, such as processes for hazardous
substance management, product safety, or dangerous goods management.
EHS SOLUTION as
Part of SAP ERP
6.0x
Component
Extension 2.0 for
SAP EHS
Management
Action / Further
information
CHAPTER
Industrial Hygiene
and Safety: Work
Areas
Managing EHS
Locations
Migration with
possible take-over
from the Plant
Maintenance
component
3.1.1 Business
Object: Work Area
/ Location
Industrial Hygiene
and Safety:
Incident/Accident
Log
Managing Incidents
Migration of
configuration
(phrases)
3.2.1 Business
Object: Incident
Industrial Hygiene
and Safety: Reports
Industrial Hygiene
and Safety:
Reporting for the
Incident/Accident
Manual migration of
print form templates
Adapt BI content to
the BI content
delivered by
component extension
for SAP EHS
Management.
3.2.2 Business
Object: Safety
Measure / Action
3.2.4
Configuration
3.2.6 Print Form
Templates
Standard delivery of
German and U.S.
forms
3.2.8 Analytical
Reporting
To report via BI
across the old and the
new incident, there
are guidelines for
manual migration of
the old incident data
May 2012
2 Migration Overview
provided in this
document.
Industrial Hygiene
and Safety Risk
Assessment
Manual migration of
configuration
3.3.1 Identify
Risks
Manual migration of
non-chemical agents
into hazard register
Manual migration of
risk assessments
Industrial Hygiene
and Safety:
Exposure
Management
Industrial Hygiene
and Safety
Measures
Manual migration of
agents
3.3.2 Analyze
Risks
Manual migration of
amounts
3.3.3 Evaluate
Risks
Manual migration of
configuration
Manual migration of
safety measures into
controls.
You can use the following two deployment options to run the add-on:
On Top Deployment
In an on-top scenario, you install the add-on on top of an ERP system. This means, you
upgrade your ERP system to the relevant enhancement package first and have the
advantage of achieving a lower TCO than with a side-by-side deployment. You can upgrade
from ERP 6.0 to ERP 6.0 EHP5 or EHP6 and the installation of EHSMe 2.0 in one installation
step. For more information on installation, see SAP Note 1558409.
In this deployment scenario, you transfer configuration settings and data from incident
management in the EHS solution as part of SAP ERP into the add-on on the same system.
Side-by-Side Deployment
If you do not want to upgrade the existing ERP system to enhancement package 5 or 6, you
install the add-on on a separate server on top of a newly installed SAP ERP 6.05 or 6.06. In
this case you take over legacy data and configuration from incident management in the EHS
solution as part of SAP ERP across a system border. You also replicate some configuration
settings from remote systems (such as from the Human Resources system, Plant
Maintenance system, Quality Management system, and central master data), and set up
remote connections to these systems.
10
May 2012
2 Migration Overview
Software Units
Key: X = mandatory
Web AS
ABAP
7.02
(X) = optional
SAP
ERP
6.05
or
6.06
Enterprise
Portal
BI
Web AS Java,
ADS
BI-Java
Managing
Incidents
(X)
(X)
Managing
Incidents
Generate BI
Analytical
Reports
(X)
Managing EHS
Risk
(X)
Managing EHS
Risk Generate
BI Analytical
Reports
(X)
May 2012
11
3 Business Scenarios
3 Business Scenarios
3.1 Foundation for EHS Management
The Foundation for EHS Management provides business objects and configuration data for
the EHS Management business scenarios. This chapter describes business objects and
configuration data that are involved in a migration of the relevant business process from the
EHS solution as part of SAP ERP to the add-on.
You can automatically transfer data from the work areas of the EHS solution as part of SAP
ERP into the locations of the add-on by using report R_EHFND_LOC_MIGRATE_WA. This
report makes manual steps unnecessary in the case of a 1:1 migration. The structure
information of the work area hierarchy is preserved and transferred into the location structure.
The location of the add-on has a function to adapt hierarchies of technical objects from the
Plant Maintenance component. You can use this function as a starting point to build up a
location hierarchy. You can do this by using the new location management. You start from a
top-level technical object and select the objects in the hierarchy below that you want the
system to automatically import into a location hierarchy.
If the technical object hierarchy can be imported one-to-one, the effort to import existing
technical objects as locations is minimal. If you must filter more complex hierarchies first, the
effort to import existing technical objects may be more intensive depending on the number of
technical objects.
12
May 2012
3 Business Scenarios
The following table provides the mapping of authorization objects in the EHS solution as part
of SAP ERP and the semantically corresponding authorization objects in the add-on,
including the corresponding parameters.
Object
EHS Solution as
Part of SAP ERP
Component
Extension 2.0 for
SAP EHS
Management
Remarks
Work Area /
Location
C_EHSI_WAH
EHFND_LOC
WERKS
LOCPLANT
WAAUTHGRP
LOCAUTHGRP
3.1.5 Extensions
In work area management in the EHS solution as part of SAP ERP, data structures of the
work areas could be extended by means of the classification system.
In location management in the add-on, extensions are enabled by the standard extension
techniques of the ABAP Dictionary (append-structures, additional Customizing tables), Web
Dynpro, and Floorplan Manager.
You append structures with the respective attributes as the replacement for your current
characteristics and add additional Customizing tables for the associated code lists.
For more information about adding fields and nodes to a business object, see the topic
Foundation for EHS Management Business Objects Adding Fields to the User Interface
on SAP Help at http://help.sap.com/ under SAP Business Suite SAP EHS Management
Component Extension for SAP EHS Management Release 2.0.
May 2012
13
3 Business Scenarios
An incident record is transactional data. This means, the business process starts after an
incident occurred and was recorded in the system. The process ensures that you fulfill legal
reporting and investigation requirements, and ends with the closure of the incident record.
Cut-Off Scenario
It is assumed that no incident data from the EHS solution as part of SAP ERP must be
transferred into the add-on. Rather, you migrate in a cut-off scenario.
This means, on a key date defined according to your project plan and business needs, your
users start recording new incidents in the new incident management in the add-on.
Unfinished incident records in the EHS solution as part of SAP ERP are finalized in the EHS
solution as part of SAP ERP.
You could also decide to roll-out incident management in the add-on step by step, for
example, by country or plant. You then define different key dates for different entities.
Your users can create actions in the add-on in an incident data record that was created in the
add-on after the key date. Your users can continue to create safety measures in the EHS
solution as part of SAP ERP for remaining incidents older than the key date as long as the
incident record has not yet been closed.
14
May 2012
3 Business Scenarios
3.2.4 Configuration
In incident management in the EHS solution as part of SAP ERP, phrase management was
used for many attributes with code lists. In incident management in the add-on, Customizing
tables are used.
The data type of the code is compatible, so you can easily copy the phrases to the respective
Customizing tables.
You can use the migration report R_EHHSS_PHRASE_MIGRATE to migrate phrases from
phrase sets that are assigned to fields in the incident/accident log of the earlier SAP solution
for managing environment, health, and safety to Customizing tables of incident management
in the add-on. Details are described in the documentation of this report. Phrase sets from the
EHS solution as part of SAP ERP may contain semantically similar or even identical entries
as the delivered customizing content of the add-on. Therefore, you should compare both
sources of content and consolidate.
In addition, there are specific configuration settings, such as integration linkage to HR, PM,
QM, and central master data. You must manually check these settings and make
adjustments if necessary. The following Customizing activities in the add-on may require
manual data transfer:
May 2012
15
3 Business Scenarios
For Integration
The component extension 2.0 for SAP EHS Management also delivers new functionality and
business processes which were not covered in the EHS solution as part of SAP ERP. There
is no existing configuration in the EHS solution as part of SAP ERP for these aspects which
can be taken over. You must follow the respective steps described in Solution Manager and
in Customizing, and check and adapt the configuration according to your needs.
16
May 2012
3 Business Scenarios
The following table provides the mapping of authorization objects in the EHS solution as part
of SAP ERP and the semantically corresponding authorization objects in the add-on,
including the corresponding parameters.
Object
EHS Solution as
Part of SAP ERP
Component
Extension 2.0 for
SAP EHS
Management
Remarks
Change
Documents
C_EHSS_CDE
EHFND_CHDC
Incident
C_EHSI_IAL
EHHSS_INC1
WERKS
PLANT_ID
C_EHSI_DOC
EHHSS_INC2
(REFOBJ IAL)
For more information about roles and authorizations, see the Security Guide on SAP Service
Marketplace at http://service.sap.com/instguides SAP Business Suite Applications SAP
EHS Management Component Extension for SAP EHS Management Release 2.0.
3.2.7 Extensions
In incident management in the EHS solution as part of SAP ERP, data structures of the
incident/accident log and for the injured person could be extended by means of the
classification system.
May 2012
17
3 Business Scenarios
In incident management in the add-on, extensions are enabled by the standard extension
techniques of the ABAP Dictionary (append-structures, additional Customizing tables), Web
Dynpro, and Floorplan Manager.
You append structures with the respective attributes as the replacement for your current
characteristics and add additional Customizing tables for the associated code lists.
For more information about adding fields and nodes to a business object, see the topic
Foundation for EHS Management Business Objects Adding Fields to the User Interface
on SAP Help at http://help.sap.com/ under SAP Business Suite SAP EHS Management
Component Extension for SAP EHS Management Release 2.0.
The following reports are supported by the incident data in the EHS solution as part of SAP
ERP:
18
May 2012
3 Business Scenarios
number of releases. These characteristics and key figures are empty for the old
incident data.
To transfer the old incident data to the new MultiProviders, the data of the BI Content
DataStore-Objects (DSO) in the EHS solution as part of SAP ERP is transferred to the new
BI Content DSOs in the add-on by transformation rules.
The following objects in the add-on will receive data from the incident in the EHS solution as
part of SAP ERP:
Step-by-Step Procedure:
1. In the Data Warehousing Workbench, for each of the DSOs or InfoObject mentioned
above, create a new DSO or InfoObject with all fields of the DSO or InfoObject in the
add-on of the accordant mapping table below (last column).
2. Create a Microsoft Excel file with all key mappings and load it into SAP NetWeaver
Business Warehouse (BW) into a new DSO (see Key Mapping in Excel below).
3. Create a transformation of the DSO (or InfoObject) in the EHS solution as part of
SAP ERP to the new created DSO (or InfoObject).
4. Do the data mapping (as described in the Mapping Rules of the mapping table
below), if necessary create start and end routine.
5. Load the data from DSO (or InfoObject) in the EHS solution as part of SAP ERP to
the new DSO (or InfoObject).
6. Delta-load the data from the new DSO (or InfoObject) to the accordant add-on DSO
(or InfoObject).
7. Optional: If the dashboard Causes & Actions is used, do the additional necessary
loading (see Additional necessary mappings).
8. Delta-Load the add-on Incident BI Content.
Always load the master data first, and then load the transactional data.
May 2012
19
3 Business Scenarios
Head
IHBP01
EHHSS_BP_HEAD
Hand
IHBP03
EHHSS_BP_PALM_HAND
EHHSS_BP_BACK_HAND
Knee
IHBP06
EHHSS_BP_KNEE
Since there is more than one key to map, we recommend creating one Microsoft Excel file
with all mappings of the old keys to the new keys with the following two columns:
Key of EHS Solution as Part of SAP ERP | Key of Component Extension 2.0 for SAP
EHS Management
Load this Microsoft Excel data into a newly created DSO for value mappings.
In the routines, when the old values are mapped to the new values, access the Microsoft
Excel DSO table to get the corresponding new key.
InfoObject 0EH_INCIDNT
20
May 2012
3 Business Scenarios
In the new BI content of the add-on, there is one InfoObject with master data, 0EH_INCIDNT.
This master data is filled by the master data of incident Info Object 0EHS_IAL in the EHS
solution as part of SAP ERP. Some fields are also filled by the master data of 0EHS_IP in the
end routine of the transformation.
The objects must be mapped in the following way:
Mapping in Transformation
EHS Solution as
Part of SAP ERP
0EHS_IAL
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EH_INCIDNT
0EHS_IAL
Incident ID
0EH_INCIDNT
Event Description
0EHS_EVDE
Incident Title
0EH_INCIDNT
Text
Constant:
Incident Category
0EH_INCCAT
Org.Unit
0EH_INCORGU
001 (Incident)
Plant / Work area
0PLANT /
0EHS_WAID
Plant
0PLANT
Direct
Plant
0PLANT
Work area
0EHS_WAID
Inc. Location
0EH_INCLOC
Accident Location
0EHS_ALOC
Routine:
0EH_INCLOCT
0DATE
Direct
0EH_INCSDAT
Date
0DATE
Direct
Start Date
0EH_STDATE
Time
0TIME
Direct
0EH_INCSTIM
Date
0DATE
Routine:
0EH_INCSDAY
Direct
Prod. Loss
0EH_INCLP
Constant:
Restricted/Inc
Confidential
0EH_INCCONF
Emergency Resp.
0EH_INCER
0EHS_PRFL
'-' (unknown)
Constant:
'-' (unknown)
Plant
0PLANT
Postal Code
0EH_INCPC
Plant
0PLANT
Country
0EH_INCCNTR
Plant
0PLANT
Region
0EH_INCREG
May 2012
21
3 Business Scenarios
EHS Solution as
Part of SAP ERP
0EHS_IAL
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EH_INCIDNT
SO Reported
Anon.
0EH_REPANON
plant
Constant:
'-' (unknown)
Date
0DATE
Direct
Calendar Year
0CALYEAR
Date
0DATE
Direct
Calendar Year
0CALQUARTER
/Quarter
Date
0DATE
Direct
Calendar Year
0CALMONTH
/Month
Date
0DATE
Direct
Calendar
0CALDAY
Day
End Routine
In the end routine of this transformation, the following master data of InfoObject 0EHS_IP is
mapped:
EHS Solution as
Part of SAP ERP
0EHS_IP
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EH_INCIDNT
Reportable Accident
0EHS_IARE
Direct
0EH_INCRR
Fatality
0EHS_IPDE
Direct
Inc. Fatality
0EH_INCFTL
Accident Category
0EHS_IACA
Inc. Occ.
0EH_INCOCC
22
May 2012
3 Business Scenarios
0EHH_DS02
0EHH_DS03
0EHH_DS06
0EHH_DS07
Mapping in Transformation
EHS solution as
part of SAP ERP
0EIH_DS02
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS02
0EHS_IAL
Incident ID
0EH_INCIDNT
Routine:
Involved Person
GUID
0EH_IPGUID
Involved Person
Role GUID
0EH_IPRGUID
Injury or Illness
GUID
0EH_IIGUID
Generate GUID*
Routine:
Generate GUID*
Routine:
Generate GUID*
Person Involved
0EHS_IP
Direct
Involved Person
0EH_INVPERS
Injury Type
0EHS_INJU
Routine:
Injury Type
0EH_INJTYPE
Injury or Illness:
Body Part
0EH_BDYPART
Injury or Illness:
Designation
0EH_IIDESIG
0EHS_BODY
Routine:
Map phrase key to new
key (Excel DSO).
Constant:
INJ (Injury)
Number of Persons
Affected
0EHS_IPCN
Direct
Number of Involved
Persons
0EH_NUMIP
Number of
Workdays Absent
0EHS_IPAB
Direct
Number of Lost
Workdays
0EH_NUMLWD
Number of
Calendar Days
Absent
0EHS_IPAC
Direct
Number of Lost
Calendar Days
0EH_NUMLCD
May 2012
23
3 Business Scenarios
EHS solution as
part of SAP ERP
0EIH_DS02
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS02
Number of
Workdays with
Restriction or Job
Transfer
0EHS_IPRD
Direct; either to
Transferred or to
Restricted Workdays (In
the incident in the EHS
solution as part of SAP
ERP, there was no
differentiation between
restricted and
transferred days.)
Number of
Restricted Workdays
0EH_NUMRWD
Number of
Workdays with
Restriction or Job
Transfer
0EHS_IPRD
Direct; either to
Transferred or to
Restricted Workdays (In
the incident in the EHS
solution as part of SAP
ERP, there was no
differentiation between
restricted and
transferred days.)
Number of
Transferred
Workdays
0EH_NUMTWD
Number of
Calendar Days with
Restriction or Job
Transfer
0EHS_IPRC
Direct; either to
Transferred or to
Restricted Calendar
Days (In the incident in
the EHS solution as part
of SAP ERP, there was
no differentiation
between restricted and
transferred days.)
Number of
Restricted Calendar
Days
0EH_NUMRCD
Number of
Calendar Days with
Restriction or Job
Transfer
0EHS_IPRC
Direct; either to
Transferred or to
Restricted Calendar
Days (In the incident in
the EHS solution as part
of SAP ERP, there was
no differentiation
between restricted and
transferred days.)
Number of
Transferred
Calendar Days
0EH_NUMTCD
End Routine
The system must read some data from the involved person master data 0EHS_IP in end
routine of transformation:
EHS Solution as
Part of SAP ERP
0EHS_IP
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS02
Employee, Business
Partner, Applicant,
External Person
0EMPLOYEE,
0BPARTNER,
0APPLICANT,
0EHS_IPFL
Routine:
Person Group
0EH_IPGROUP
Role of Person
Involved
0EHS_IPTP
Routine:
Role
0EH_IPROLE
Accident Category
0EHS_IACA
0EH_IPITYPE
Value mapping
Value mapping
(Excel DSO)
Routine:
Value mapping
(Excel DSO)
24
May 2012
3 Business Scenarios
EHS Solution as
Part of SAP ERP
0EHS_IP
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS02
Accident Category
0EHS_IACA
Routine:
On Duty
0EH_ONDUTY
If value is WRK
Fatality
0EHS_IPDE
Direct
Fatality
0EH_IPFTLTY
Treatment in
Emergency Room
0EHS_EMER
Direct
Treated in
0EH_EMROOM
Treatment
Overnight As
Inpatient
0EHS_INPA
Reportable Accident
0EHS_IARE
Direct
Reportable
0EH_INJRR
Cause of Accident
0EHS_IACS
Routine:
Major Root
0EH_MAJORRC
Cause
Emergency Room
Direct
Inpatient over
0EH_INPAT24
24 Hours
Start Routine
Duplicate records when both 0EQUIPMENT and 0FUNCT_LOC are populated. Each record
must have either 0EQUIPMENT or 0FUNCT_LOC.
Mapping in Transformation
EHS Solution as
Part of SAP ERP
0EHS_IAL
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS03
0EHS_IAL
Incident ID
0EH_INCIDNT
Routine:
Asset GUID
0EH_ASGUID
Generate GUID*.
If both
0EQUIPMENT and
0FUNCT_LOC have
values, two records
have to be created.
May 2012
25
3 Business Scenarios
EHS Solution as
Part of SAP ERP
0EHS_IAL
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS03
Equipment,
0EQUIPMENT,
Routine:
Asset Type
0EH_ASSETTY
Functional Location
0FUNCT_LOC
If 0FUNCT_LOC has
a value, the asset
type is 'property'.
Asset of Company
0EH_BEL2ORG
Asset Equip ID
0EH_EQUIPID
Asset Equip
Operational
0EH_EQOPERA
Asset Veh ID
0EH_VEHICID
Asset Veh
Operational
0EH_VHOPERA
Direct
Asset Prop ID
0EH_PROPID
Constant:
0EH_PRUSBL
If 0EQUIPMENT has
a value, the asset
type is either
'equipment' or
'vehicle'. In this
case, there has to
be a mapping of
equipment IDs to the
asset types
Constant:
'-' (unknown)
Equipment
0EQUIPMENT
Routine:
If the equipment is
not a vehicle.
Constant:
'-' (unknown)
Equipment
0EQUIPMENT
Routine:
If the equipment is a
vehicle
Constant:
'-' (unknown)
Functional Location
0FUNCT_LOC
'-' (unknown)
*GUID is generated in routine via method
CL_UPARI_SYSTEM_UUID=>IF_UPARI_SYSTEM_UUID_STATIC~CREATE_UUID_C32.
26
May 2012
3 Business Scenarios
Mapping in Transformation
EHS Solution as
Part of SAP ERP
0EIH_DS03
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS06
0EHS_IAL
Incident ID
0EH_INCIDNT
Routine:
Action GUID
0EH_ACTGUID
Generate GUID*
Industrial Hygiene
and Safety Measure
0EHS_ACTN
Action ID
0EH_ACTION
Number of Industrial
Hygiene and Safety
Measures
0EHS_ACCN
Direct
Number of Actions
0EH_NUMACT
End Routine
Some data must be read from safety measure master data in the end routine of the
transformation:
EHS Solution as
Part of SAP ERP
0EHS_ACTN
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS06
Industrial Hygiene
and Safety Measure
Category
0EHS_ACAT
Routine:
Action Category
0EH_ACTCAT
Industrial Hygiene
and Safety Measure
Type
0EHS_ACTP
Action Type
0EH_ACTTYPE
May 2012
Value mapping
(Excel DSO)
Routine:
Value mapping
(Excel DSO)
27
3 Business Scenarios
DataStore-Object 0EHH_DS01
Map the temporary DSO for 0EHH_DS02 to the DSO 0EHH_DS01 in the add-on in the
following way (the key fields are italicized):
Mapping in Transformation
Temporary DSO for
0EHH_DS02
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS01
Incident ID
0EH_INCIDNT
Direct
Incident ID
0EH_INCIDNT
Routine:
Incident: Group
GUID
0EH_IGGUID
Involved Person:
GUID
0EH_IPGUID
Generate GUID*
Involved Person: GUID
0EH_IPGUID
Direct
DataStore-Object 0EHH_DS07
Map the temporary DSO for 0EHH_DS02 to the DSO 0EHH_DS07 in the add-on in the
following way (the key fields are italicized):
Mapping in Transformation
Temporary DSO for
0EHH_DS02
Mapping Rule
Component
Extension 2.0 for
SAP EHS
Management
0EHH_DS01
Incident ID
0EH_INCIDNT
Direct
Incident ID
0EH_INCIDNT
Routine:
0EH_RCGUID
Investigation: Major
Root Cause
0EH_MAJORRC
Generate GUID*
Investigation: Major
Root Cause
0EH_MAJORRC
Direct
After the mapping in the transformation is completed, the incident data in the EHS solution as
part of SAP ERP can be loaded into the newly created DSOs. The mapping of the new DSOs
to the incident DSOs of the add-on should now be a direct mapping for all fields. After
completing this mapping, the data can be loaded to the incident DSOs of the add-on by a
delta load.
After the loading of the old incident data into the incident DSOs of the add-on, you must
perform a complete delta load of incident BI Content in the add-on.
28
May 2012
3 Business Scenarios
Note that after every initial load of the incident BI Content in the add-on, the incident data of
the EHS solution as part of SAP ERP has to be loaded again to the incident DSOs in the addon.
HCM Data
For the Incident Key Figures dashboard, the number of employees and the number of
working hours are necessary for the calculation of the displayed key figures. For how long in
the past this data should be loaded can be configured in the customizing (see SAP Note
1462039).
If you use the incident data in the EHS solution as part of SAP ERP, you need to load the
HCM data for all the last years you want to display the key figures. We recommend loading
the HCM data for a maximum of the last five years that incident data was recorded in BW.
When migrating risks from the EHS solution as part of SAP ERP, we recommend you create
reasonable risk assessments for, for example, each site, location, or production unit,
according to the risk assessment type. These risk assessments can absorb the risks which
are to be migrated from the EHS solution as part of SAP ERP.
May 2012
29
3 Business Scenarios
3.3.1.1.1 Configuration
For the operational statuses
SAP EHS Management -> Risk Assessment -> General Configuration -> Specify
Operational Statuses
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Work
Area Management -> Specify Operation Statuses
The operational statuses have been introduced to be independent from the EHS solution as
part of SAP ERP. The customizing content from the EHS solution can be copied manually
one-to-one.
SAP EHS Management -> Risk Assessment -> Specify Reason Types
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Specify Reasons for Risk Assessments
The reason types have been introduced to be independent from the EHS solution as part of
SAP ERP. The customizing content from the EHS solution can be copied manually one-toone. Also, a connection to a business object can be manually created for each reason type.
30
May 2012
3 Business Scenarios
3.3.1.3.1 Configuration
The following Customizing activities in the add-on may require manual data transfer:
For the hazard configuration
SAP EHS Management -> Risk Assessment -> Hazard and Control Register
Configure hazard and Control Register -> Specify Hazard Categories
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Specify Agent Types
Agent types from the EHS solution can be selectively copied one-to-one, depending on the
customer requirements. Not all agent types from the EHS solution are meaningful within the
context of risk assessment, depending on the customer requirements.
SAP EHS Management -> Risk Assessment -> Hazard and Control Register
Configure hazard and Control Register -> Specify Hazards
o
For specifications of type HAZARD which are not substances, see above.
May 2012
31
3 Business Scenarios
The following table provides the mapping of authorization objects in the EHS solution as part
of SAP ERP and the semantically corresponding authorization objects in the add-on,
including the corresponding parameters.
Object
EHS Solution as
Part of SAP ERP
Component
Extension 2.0 for
SAP EHS
Management
Remarks
Change
Documents
C_EHSS_CDE
EHFND_CHDC
Risk
Assessment
C_EHSI_WAH
EHHSS_RAS
WERKS
ACTVT
WAAUTHGRP
RAS_TYPE
LOCAUTHGRP
C_EHSI_HAZ
LOCPLANT
LOCCOST
LOCCOMP
LOCBUSAREA
Data Series
EPTYPE
C_EHSI_WAH
EHFND_DTS
WERKS
LOCAUTHGRP
WAAUTHGRP
LOCPLANT
LOCCOST
C_EHSI_MPR
LOCCOMP
LOCBUSAREA
MPTYPE
C_EHSI_MJO
Agent
MJCAT
C_EHSI_HAZ
EHHSS_AGT
EPTYPE
Job
none
EHHSS_JOB
Controls
none
EHFND_CTRL
32
May 2012
3 Business Scenarios
Workflow
Tools
Limits for
Analytic
Reports
none
none
EHFND_WFF
EHSM_COMP
PURPOSE
EHSM_PVAR
EHSM_PCACT
EHFND_WFT
none
TCD
EHHSS_CLR
For more information about roles and authorizations, see the Security Guide on SAP Service
Marketplace at http://service.sap.com/instguides SAP Business Suite Applications SAP
EHS Management Component Extension for SAP EHS Management Release 2.0.
3.3.1.7 Extensions
In risk assessment in the EHS solution as part of SAP ERP, data structures of the risk
assessment could not be extended by means of the classification system.
In risk assessment in the add-on, extensions are enabled by the standard extension
techniques of the ABAP Dictionary (append-structures, additional Customizing tables), Web
Dynpro, and Floorplan Manager.
You append structures with the respective attributes as the replacement for your current
characteristics and add additional Customizing tables for the associated code lists.
May 2012
33
3 Business Scenarios
For more information about adding fields and nodes to a business object, see the topic
Foundation for EHS Management Business Objects Adding Fields to the User Interface
on SAP Help at http://help.sap.com/ under SAP Business Suite SAP EHS Management
Component Extension for SAP EHS Management Release 2.0.
Inherent risk
The existing risk identified prior to risk treatment. The inherent risk level is
determined without considering existing controls.
Initial risk
The existing risk identified prior to risk treatment. The initial risk level is determined
by considering existing controls.
Residual risk
The existing risk remaining after implementing new risk treatment measures
(controls).
This differentiation was not possible within the EHS solution as part of SAP ERP.
3.3.2.1.1 Configuration
For the amount categories
SAP EHS Management -> Risk Assessment -> Master Data Configuration -> Agents
-> Specify Amount Categories and Assign to Hazards -> Specify Amount Categories
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Specify Measurement items -> Specify Amount Categories
Amount categories from the EHS solution can be copied one-to-one to the add-on enriched
by a unit, if requested.
For the sampling types
SAP EHS Management -> Risk Assessment -> Master Data Configuration ->
Amounts -> Specify Sampling Types
o
34
Environment, Health and Safety -> Industrial Hygiene and Safety ->
Measurement Management -> Measurement Projects -> Specify Sampling
Types
May 2012
3 Business Scenarios
Sampling Types from the EHS solution can be copied one-to-one to the add-on, if requested.
For the amount business object
SAP EHS Management -> Risk Assessment -> General Configuration -> Specify
Operational Statuses
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Work
Area Management -> Specify Operation Status
Operation status from the EHS solution as part of SAP ERP can be copied one-to-one to the
add-on, if requested.
SAP EHS Management -> Risk Assessment -> Risk Analysis -> Risk Matrix ->
Specify Likelihood
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Set Up Risk Matrix -> Specify Probability of a Risk
The probability of a risk from the EHS solution as part of SAP ERP can be copied one-to-one
to the add-on, if requested.
SAP EHS Management -> Risk Assessment -> Risk Analysis -> Risk Matrix ->
Specify Severity
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Set Up Risk Matrix -> Specify Severity of a Risk
The severity of a risk from the EHS solution as part of SAP ERP can be copied one-to-one to
the add-on, if requested.
SAP EHS Management -> Risk Assessment -> Risk Analysis -> Risk Matrix -> BAdI:
Risk Level Calculation
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Business Add-Ins (BAdIs) -> BAdI: Calculation of Rating for
Standardized Criteria
May 2012
35
3 Business Scenarios
SAP EHS Management -> Risk Assessment -> Risk Analysis -> Exposure Analysis > Specify Exposure Ratings for Non-Chemical Agents and
SAP EHS Management -> Risk Assessment -> Risk Analysis -> Exposure Analysis > Specify Exposure Ratings for Chemical Agents
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Risk
Assessment -> Specify Exposure Ratings
The exposure ratings from the EHS solution as part of SAP ERP can be copied one-to-one to
the add-on, if requested.
3.3.4.1.1 Configuration
The following Customizing activities in the add-on may require manual data transfer:
For the controls
36
SAP EHS Management -> Foundation for EHS Management -> Actions and Controls
-> Specify Types
May 2012
3 Business Scenarios
Environment, Health and Safety -> Industrial Hygiene and Safety -> Industrial
Hygiene and Safety Measures -> Specify Safety Measure Categories
SAP EHS Management -> Foundation for EHS Management -> Actions and Controls
-> Specify Subtypes
o
Environment, Health and Safety -> Industrial Hygiene and Safety -> Industrial
Hygiene and Safety Measures -> Specify Safety Measure Types
The control types and subtypes can be copied one-to-one from the EHS solution as part of
ERP to the add-on, if requested.
SAP EHS Management -> Risk Assessment -> Risk Treatment -> Specify Control
Effectiveness
o
Environment, Health and Safety > Industrial Hygiene and Safety -> Industrial
Hygiene and Safety Measures -> Specify Effectiveness
The control effectiveness can be copied one-to-one from the EHS solution as part of SAP
ERP to the add-on, if requested.
May 2012
37