Sap Ehsm

Component Extension for SAP Environment, Health, and Safety
Mana
PDF download from SAP Help Portal:
http://help.sap.com/saphelp_ehsext30/helpdata/en/5b/22b8d6606b4d32b8af9283901d3bdc/content.htm
Created on November 06, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.
2014 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE 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 and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 82
Table of content
1 Component Extension for SAP Environment, Health, and Safety Mana
1.1 Foundation for EHS Management (EHS-MGM-FND)
1.1.1 Business Objects
1.1.1.1 Adding Fields to the User Interface
1.1.1.2 Field Control
1.1.1.3 Document Storage
1.1.1.4 Creation of Change Documents
1.1.2 Process Foundation (EHS-MGM-FND-WF)
1.1.2.1 PCOs and PCBOs
1.1.2.2 Process Configuration
1.1.2.2.1 Changing Workflow Templates
1.1.2.3 Task Management
1.1.2.3.1 Changing the Task Processor
1.1.2.3.2 Continuing Execution of a Process with Errors
1.1.2.4 Process Tools
1.1.3 Print Forms and Interactive Forms (EHS-MGM-FND-FRM)
1.1.3.1 Adding Print Forms and Interactive Forms
1.1.3.2 Mapping Business Objects Nodes to Adobe Forms
1.1.4 Integration (EHS-MGM-FND-INT)
1.1.4.1 Integration for Person Information
1.1.4.2 Integration for Notifications
1.1.4.3 Check for Completed Notifications
1.1.5 Locations
1.1.5.1 Location
1.1.5.2 Maintaining Locations and the Structure
1.1.5.3 Importing Locations from PM
1.1.6 Chemicals
1.1.6.1 Creating and Revising Regulatory Lists
1.1.6.2 Transferring Data from the Specification Database
1.1.7 Analytical Reporting
1.1.7.1 File-Based Reporting
1.1.7.2 Data Extraction to BW
1.1.7.3 DataSources
1.1.7.3.1 Workflow Process Definitions
1.1.7.3.2 Workflow Process Instances
1.1.7.3.3 Workflow Step Definitions
1.1.7.3.4 Workflow Step Instances
1.1.7.3.5 Workflow Process Definitions - Text Extraction (Full)
1.1.7.3.6 Workflow Reporting - Component Description
1.1.7.3.7 Workflow Reporting - URL Extraction (Full)
1.1.7.3.8 Workflow Step Definitions - Text Extraction (Full)
1.1.7.3.9 Texts for Material ID
1.1.7.3.10 Common Objects
1.1.7.3.10.1 Location Master Data
1.1.7.3.10.2 Location Hierarchy
1.1.7.3.10.3 Texts for Location
1.1.7.3.10.4 Texts for Location Type
1.1.7.3.10.5 Texts for Location Authorization Group
1.1.8 Roles
1.1.8.1 Business Package (Portal Content)
1.1.8.1.1 Business Package for EHS Management
1.1.8.1.2 Configuration Information
1.1.8.1.2.1 Adding Incident-Related iViews to the Employee Self-Service Cent
1.1.8.1.2.2 Creating Custom Roles
1.1.8.1.2.3 Setting Up the System Landscape
1.1.8.1.2.4 Setting Up the Universal Worklist
1.1.8.1.2.5 Role Assignments for Cross-Role Activities
1.1.8.1.3 Roles
1.1.8.1.3.1 Incident Manager
1.1.8.1.3.1.1 Health and Safety
PUBLIC
Page 2 of 82
1.1.8.1.3.1.1.1 Overview
1.1.8.1.3.1.1.1.1 Work Overview
1.1.8.1.3.1.1.1.1.1 Inbox
1.1.8.1.3.1.1.1.2 Incidents
1.1.8.1.3.1.1.1.2.1 Incident Entry Screen
1.1.8.1.3.1.1.1.2.2 Incident Search
1.1.8.1.3.1.1.1.2.3 Report Incident (Simplified)
1.1.8.1.3.1.1.1.2.4 Report Incident
1.1.8.1.3.1.1.1.2.5 Report Near Miss
1.1.8.1.3.1.1.1.2.6 Report Safety Observation
1.1.8.1.3.1.1.1.2.7 Display Progress Log for External Notifications
1.1.8.1.3.1.1.1.2.8 Notify Task Processor
1.1.8.1.3.1.1.1.2.9 Display Application Log
1.1.8.1.3.1.1.1.2.10 Execute Process Decision
1.1.8.1.3.1.1.1.2.11 Display Incident
1.1.8.1.3.1.1.1.2.12 Edit Incident
1.1.8.1.3.1.1.1.2.13 Investigate Step
1.1.8.1.3.1.1.1.2.14 Take Over Inquiry Response
1.1.8.1.3.1.1.1.2.15 Display Generic Process Setup
1.1.8.1.3.1.1.1.2.16 Edit Generic Process Setup
1.1.8.1.3.1.1.1.2.17 Display Change Documents
1.1.8.1.3.1.1.1.2.18 Create Generic Process Setup
1.1.8.1.3.1.1.1.2.19 Change Assignee
1.1.8.1.3.1.1.1.2.20 Assign Absence to Incident
1.1.8.1.3.1.1.1.2.21 Display Person Details
1.1.8.1.3.1.1.1.2.22 Display PM Notification
1.1.8.1.3.1.1.1.3 Incident Reports
1.1.8.1.3.1.1.1.3.1 Review Incident Summary Reports
1.1.8.1.3.1.1.1.3.2 Change Parameters for Sending Reports
1.1.8.1.3.1.1.1.3.3 Display/Edit Incident Summary Report
1.1.8.1.3.1.1.1.3.4 Create Incident Report
1.1.8.1.3.1.1.1.3.5 Change Incident Report
1.1.8.1.3.1.1.1.3.6 Generate Incident Report
1.1.8.1.3.1.1.1.4 Locations
1.1.8.1.3.1.1.1.4.1 Explore Locations
1.1.8.1.3.1.1.1.4.2 Create Location
1.1.8.1.3.1.1.1.4.3 Manage Structure
1.1.8.1.3.1.1.1.4.4 Import from PM
1.1.8.1.3.1.1.1.4.5 Change Attributes
1.1.8.1.3.1.1.1.4.6 Display Location
1.1.8.1.3.1.1.1.4.7 Edit Location
1.1.8.1.3.1.1.1.4.8 Display Location Structure
1.1.8.1.3.1.1.1.4.9 Edit Location Structure
1.1.8.1.3.1.1.1.4.10 Display Where-Used List
1.1.8.1.3.1.1.1.5 Tasks
1.1.8.1.3.1.1.1.5.1 Display HSS Tasks
1.1.8.1.3.1.1.1.5.2 Forward Task to Another Processor
1.1.8.1.3.1.1.1.5.3 Process Details
1.1.8.1.3.1.1.1.6 Processes
1.1.8.1.3.1.1.1.6.1 EHS Management Task (Technical Information)
1.1.8.1.3.1.1.1.6.2 Graphical Workflow Log
1.1.8.1.3.1.1.1.6.3 Technical Workflow Log
1.1.8.1.3.1.1.1.6.4 Open Comment
1.1.8.1.3.2 Incident Reporter
1.1.8.1.3.2.1.1 Overview
1.1.8.1.3.2.1.1.1 Incidents
1.1.8.1.3.2.1.1.1.1 Workset Map
1.1.8.1.3.2.1.1.1.4 Report Near Miss
PUBLIC
Page 3 of 82
1.1.8.1.3.3 Notification Recipient

1.1.8.1.3.3.1.1 Overview
1.1.8.1.3.3.1.1.1 Work Overview
1.1.8.1.3.3.1.1.1.1 Inbox
1.1.8.1.3.3.1.1.2 Incidents
1.1.8.1.3.4 Process Administrator
1.1.8.1.3.4.1.1 Overview
1.1.8.1.3.4.1.1.1 Processes
1.1.8.1.3.4.1.1.1.1 Display Process Definitions
1.1.8.1.3.4.1.1.1.2 Check Workflow System
1.1.8.1.3.4.1.1.1.3 Check Process Definition
1.1.8.1.3.4.1.1.1.4 Display Technical Details for Process Definition
1.1.8.1.3.4.1.1.1.5 Check Process Instance
1.1.8.1.3.4.1.1.1.6 Display Technical Details for Process Instance
1.1.8.1.3.4.1.1.1.7 Display Process Instances
1.1.8.1.3.4.1.1.1.8 Technical Workflow Inbox
1.1.8.1.3.4.1.1.1.11 EHS Management Task (Technical Information)
1.1.8.1.3.4.1.1.1.12 Open Comment
1.1.8.1.3.5 Environmental Manager
1.1.8.1.3.5.1.1 Overview
1.1.8.1.3.5.1.1.1 Work Overview
PUBLIC
Page 4 of 82
1 Component Extension for SAP Environment, Health, and Safety

Management
Product Information
Product
Component extension for SAP Environment, Health, and Safety Management (SAP
EHS Management)
Release
3.0 SP03 or higher
Based On
SAP ERP 6.05 or 6.06

SAP NetWeaver 7.02 or 7.31
BI Content Release
SAP NetWeaver 7.0 BI Content Add-On 7

Extension for SAP NetWeaver 7.0 BI Content Add-On 7 (dashboards)
Documentation Published
October 2013
Use
Component extension for SAP Environment, Health, and Safety Management ( SAP EHS Management ) is an add-on to SAP ERP and supports your
organization in managing business processes related to environment, health, and safety. This component extension provides comprehensive functionality to
support you in the following scenarios and their corresponding processes:
Health and Safety
Managing incidents
Managing EHS risk
Managing EHS locations
Product Safety and Stewardship
Managing product compliance
Managing IMDS compliance
This add-on features integration points with other SAP components throughout the solution and a foundation layer that connects the processes of SAP EHS
Management to the SAP Business Workflow engine.
If you use existing components in SAP EHS Management as part of SAP ERP or SAP Product and REACH Compliance that support these processes, they are
still supported. However, further enhancements are developed in this add-on.
This component extension for SAP EHS Management is part of SAP Business Suite.
The documentation for this component extension for SAP EHS Management offers a comprehensive description of the functional scope and highlights the
relationship between the application and the underlying technologies.
1.1 Foundation for EHS Management (EHS-MGM-FND)

This component provides the required functionality and infrastructure to use SAP EHS Management . You use this component in the following ways:
Business Objects
Business objects are the basic building blocks that store the data and provide the business logic to support your processes. Business objects in SAP
EHS Management are implemented using the Business Object Processing Framework (BOPF). You can add new fields and nodes to business objects,
control how the fields appear and behave on the user interface, and store documents for a business object. For more information, see Business Objects.
Process Foundation
The process foundation helps you execute your business processes using the SAP Business Workflow, and helps you to manage tasks. You can extend
and adapt delivered process specifically for your organization. The process foundation also provides tools and services to make process administration
easy.
Print Forms and Interactive Forms
You can use forms in the components of SAP EHS Management . You can use the forms delivered in the standard system, or adapt forms and add
customer-specific ones.
Integration
There are integration points to other systems in SAP EHS Management . This enables you to access data that you already store in other systems and
communicate with those systems.
Locations
You can use locations in SAP EHS Management to represent the real places, virtual spaces, and objects at your organization in the system. The location
makes it possible to harmonize existing assets in the Plant Maintenance component and to migrate work areas from the old solution provided by SAP for
managing environment, health, and safety.
Chemicals
You can use chemical data in your business processes, for example, chemical agents in assessing risk and listed substances in ensuring product
compliance. Customer lists and regulatory lists help you group listed substances according to regulatory or company-specific policy and integrate this
information into your processes.
Analytical Reporting
This section provides information about the functionality to support you in generating analytical reports.
Roles
SAP EHS Management is delivered with roles, work centers, worksets, and iViews to help you define how your users can use the application. SAP EHS
Management provides content in the Business Package (portal content) and for the SAP NetWeaver Business Client (NWBC).
PUBLIC
Page 5 of 82
Integration
The foundation of SAP EHS Management is used entirely or in part in the following components:
Incident Management
Risk Assessment
Product Compliance (EHS-MGM-PRC)
1.1.1 Business Objects

SAP EHS Management is delivered with the following business objects (BOs) to support your business processes.
Common objects
Action
There is an action object for each component of SAP EHS Management . It allows you to store data, such as the task processor, the category (action
or notification), and protection goal.
Location (EHFND_LOCATION)
You can use the location in incident management and risk assessment to represent identified real places, virtual spaces, or objects in the system.
For more information about using this business object, see Locations.
Chemical (EHFND_CHEMICAL), regulatory list (EHFND_REGLIST), and listed substance (EHFND_LISTED_SUBSTANCE)
You can use the chemical to store information for chemical agents in risk assessment, and you can use regulatory lists and listed substances in risk
assessment and product compliance.
Process Control Business Objects
There is one process control business object (PCBO) for every process supported by SAP EHS Management . This business object stores the data
that belongs to a process and provides the required functions for executing a process.
Business objects for incident management
Incident (EHHSS_INCIDENT)
The incident business object allows you to collect all the relevant data for recording incidents, near misses, and safety observations. For more
information about this business object, see Incident.
Report/forms (EHHSS_INCIDENT_REPORT and EHHSS_INCIDENT_SUMMARY_REPORT)
The report business object stores the data that is relevant to a report or a form, for example, the form name, language, and generation date.
Business objects for risk assessment
For a list of the business objects used for risk assessment, see Business Objects for Risk Assessment.
Business objects for product compliance
For a list of the business objects used for product compliance, see Business Objects for Product Compliance
Structure
The business objects of SAP EHS Management have been modeled in the Business Object Processing Framework (BOPF). BOPF controls the application
businesses logic as well as the data retrieval of the buffer and persistency layer. You can display and make yourself familiar with the structure and logic of a
business object in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI ).
1.1.1.1 Adding Fields to the User Interface

You can add fields to the user interface (UI) of a Web Dynpro application that is based on the integration of the Floorplan Manager and the Business Object
Processing Framework (BOPF).
Prerequisites
You have experience using data definitions in the ABAP Dictionary, have some experience with business objects based on BOPF (transaction
/BOBF/CUST_UI ), and have experience configuring Web Dynpro ABAP user interfaces with the Floorplan Manager for Web Dynpro ABAP (FPM).
Procedure
To add fields, you have to perform two main activities:
1. Add the fields to the business object
2. Modify the GUIBB configuration to include the fields
Adding Fields to the Business Object
Note
Each BO node generally consists of a particular DDIC structure that is used for adding new fields, for example. To add new fields to the business object
without modifying it, you have to append a structure to the Extension Include for the corresponding BO node.
1. Call transaction /BOBF/CUST_UI and select the business object that you want to change.
2.
3.
4.
5.
Then select the node structure that you want to enhance.

Double-click the Extension Include to display the ABAP Dictionary maintenance for this structure.
Then choose
Goto Append Structure
to display the ABAP Dictionary maintenance for the append structure.
In the dialog box, enter the name of the append structure. Then click Continue .
PUBLIC
Page 6 of 82
6. In the Dictionary maintenance for this structure, provide a short description of the structure. Enter the components (in this case, the fields) that you want to
add and specify their type. Then choose Activate to activate the changed structure.
Modifying the GUIBB Configuration
Note
The following steps describe how you enhance generic user interface building block (GUIBB) configurations. For more information about adapting GUIBB
configurations, see Fitting Web Dynpro to Your Needs.
You can determine the name of the Web Dynpro Application from the technical information in More Field Help on the context menu of the respective screen.
1. Start the configuration editor in administrator mode.
You use the administrator mode of the Web Dynpro Explorer to make modification-free changes to a user interface with the configuration editor for Floorplan
Manager. To start the configuration editor in administrator mode, perform the steps described in the Procedure of Administrator Mode.
2. The Component Configuration screen is now displayed. Choose Configure UIBB for Form UIBB (1) .
3. On the next screen, choose the group to which the new field is to be added. Choose Configure Group .
4. The Configure Group dialog box is displayed. Here you can select which of the available fields shall be displayed in the GUIBB at runtime. The list of
Available Fields should include the previously added component. Select this field and choose Add Fields . You can change the display sequence for the
field you just added. Then choose OK .
5. The new field is now displayed on the Component Configuration screen. Here you can select the field to change the properties of the Attributes Element .
Choose Save to save your changes to the UIBB. The next time the GUIBB is loaded, the new fields will be displayed.
Note
If the new UI field is to be based on a customizable code field, you create additionally a corresponding customizing table and maintenance view using
transaction SE54 , and add a corresponding search help. You can then define a list of valid entries using the maintenance view for the field. In the GUIBB
configuration, you can optionally change the UI element of the corresponding field to a dropdown box displaying the list of valid data.
Result
You have successfully added the new field to your Web Dynpro application. Since the new field is part of a BO node extension include, the data that was entered
is saved and retrieved successfully without any additional changes or modifications to the BO itself. The FBI-based Web Dynpro application itself also handles
the data access without you needing to make any changes or modifications to the BO or the UI.
This approach to adapt the Web Dynpro screens applies not only to adding fields, but also to other screen changes, for example, renaming labels and changing
the sequence of fields and groups.
More Information
For more information about the BOPF enhancement framework, see SAP Note 1457235.
For more information about FPM, see Floorplan Manager for Web Dynpro ABAP.
1.1.1.2 Field Control

This function enables you to adapt the user interface to ensure that you record and process exactly the data that you need in SAP EHS Management . Field
control enables you to control the behavior and appearance of the fields, buttons, and groups on the user interface at runtime if a data record fulfills certain
conditions. For example, if you use SAP EHS Management to record work-related injuries and illnesses, you can adapt the user interface to make certain fields
visible and mandatory for a specific region or country. This function helps organizations to fulfill data recording and regulatory compliance requirements.
Prerequisites
You are familiar with the structure of the business objects of SAP EHS Management that are modeled in the Business Object Processing Framework (BOPF).
For more information about the business objects of SAP EHS Management , see Business Objects.
You have specified field control in Customizing for SAP EHS Management under
Specify Field Control .
Foundation for EHS Management
Settings for Business Objects
Features
Field control provides the following features:
Profiles
Field control uses profiles to store the information about both the conditions that a data record must fulfill for field control to apply, and how the system then
controls the user interface when field control applies.
You can set up a profile to use the following conditions when determining if field control applies:
Node Attribute Value
You can use profiles that are based on an entered value for a given field (node attribute). For example, when you have entered the value X for the Y
field, the corresponding profile applies.
Authorization-Based Profile
You can use profiles that adapt the user interface based on a users authorizations for the corresponding node level. This way, you can ensure that the
system provides data access and the possibility to execute business logic only to authorized users.
PUBLIC
Page 7 of 82
Function Class
You can use profiles that contain customer-specific logic implemented by classes. This allows you to specify more complicated logic for a field if
basing the profile on a node attribute value is not sufficient.
You can set up a profile to use the following property settings to control how the system applies field control:
Attribute
You can specify fields to be enabled (visible), read-only, or mandatory.
Node
You can specify whether instances of the node can be created, read, updated, or deleted.
Action
You can specify the actions that a user can perform on the data of a corresponding node, for example, change the status, create subnodes, and so
on.
Association
You can specify other nodes that are associated with the node of your profile. This makes it possible to apply field control settings for a given profile to
associated nodes. Such settings specify, for example, if a new data record of an associated node can be created.
Merge Strategy
When you have two or more profiles whose conditions all apply in parallel for a certain node, but which define contradicting property settings, you can
specify a merge strategy. This strategy dictates priorities for contradicting property settings.
Propagation
You can apply node and association property settings dynamically to all subnodes (to the whole subtree). This saves configuration effort if you want to reuse
settings in a field control profile.
1.1.1.3 Document Storage

This function enables you to use the Content Management Service to store documents, such as attachments and generated PDF reports, in SAP EHS
Management . You can define the storage location for these documents, for example, in the database or in an external content server.
Features
Document storage provides the following features:
The connection to the Content Management Service is specified and implemented by the attachment folder (ATF) object of the Business Object Processing
Framework. Such attachment folders are assigned to the corresponding business objects of SAP EHS Management .
Print forms and SAP Interactive Forms by Adobe, as well as other attached documents of any format, are stored using such attachment folder objects within
the Content Management Service.
More Information
For more information about configuring document storage for SAP EHS Management , see Customizing for SAP EHS Management under
Management Business Objects
Specify Document Storage .
Foundation for EHS
For more information about the Content Management Service, see Content Management Service.
1.1.1.4 Creation of Change Documents

You can use change documents to trace the changes made to a data record. Change documents enable you to document data changes, and support you in
fulfilling your auditing requirements. The following types of change documents are available:
Change documents
Change documents
Change documents
Change documents
Change documents
for incident records

for location records
for actions and notifications
for risks
for risk assessments
The type of change documents you can access depends on where you are in the application. For example, you can only display change documents for actions
and notifications, if an action or notification is selected on the Tasks tab.
Features
You can access change documents by choosing the relevant entry from the You can also link. Note that if you want to access change documents relevant to a
control, you must choose the Display Change Documents pushbutton on the Tasks for Control dialog box. After you have entered parameters to limit the
changes that are displayed, you can see the following information in the results list:
Date and time of the change
Type of change, for example, an update or insertion
Name of the business object node that stores the change, for example, incident root or involved person role
(Old) Value before the change, and the (new) value after the change
Affected field
User who made the change
Details about the change action
More Information
PUBLIC
Page 8 of 82
For more information about change documents, see SAP Help Portal at http://help.sap.com/nw70/. Choose
SAP Library
SAP NetWeaver SAP
NetWeaver by Key Capability
Application Platform by Key Capability
ABAP Technology
ABAP Workbench (BC-DWB) BC Extended Applications
Function Library
Change Documents .
1.1.2 Process Foundation (EHS-MGM-FND-WF)

The process foundation is essential to the business processes supported by SAP EHS Management . It links the SAP Business Workflow engine and the
business objects of SAP EHS Management together. This link comprises parts that are common to every implementation of a process, namely a process
control business object (PCBO) for storing process-relevant information and a process control object (PCO) for communicating with a workflow at runtime. The
process foundation provides a general base for the handling of workflows associated with your business object, and makes adapting and extending the processes
easy. In addition, the process foundation makes it possible to collect statistical data about tasks and processes as well as monitor them. The system is delivered
with processes.
Integration
The process foundation uses the Workflow Engine of SAP Business Workflow.
Features
The process foundation provides the following features:
Easy implementation of your business processes in the system as processes
You can use processes for internal and external communication, sending notifications, assigning tasks, complying with regulatory requirements, reporting,
and so on.
Adaptation of a process to match country and region-specific needs
You can create variants of existing processes for a specific country or region.
Custom development capabilities
You can use customer-specific business logic in ABAP Objects to create new process variants.
Statistical data collection and monitoring capabilities
You can monitor and analyze the progress of your business processes as well as monitor the completion of the tasks associated with processes.
More Information
For more information about the processes of incident management that use the process foundation, see Incident Workflows and Tasks.
For more information about the processes of risk assessment that use the process foundation, see Risk Assessment Workflows and Tasks.
For more information about the processes of product compliance that use the process foundation, see Product Compliance Workflows and Tasks
1.1.2.1 PCOs and PCBOs

The following objects make up the process foundation that was developed for SAP EHS Management . They provide a layer of integration between the business
objects stored with the Business Object Processing Framework (BOPF) and the SAP Business Workflow.
Process control business object (PCBO)
The PCBO is a BOPF business object that represents a workflow-driven process in the system. It provides the logic, such as the action that starts the
workflow in SAP Business Workflow, and stores the process-specific data, such as the process definition key.
Process control object (PCO)
A PCO is an ABAP Objects class that represents a process control business object in the workflow for a specific process in SAP EHS Management .
The PCO makes it technically possible to use the BOPF business objects with the workflow functions of SAP Business Workflow.
The class CL_EHFND_WFF_ROOT_PCO is the most basic abstract PCO class in the foundation for SAP EHS Management . It implements all the basic
functionality needed for all processes. There are also foundation PCO classes for each specific type of process, for example, for inquiries or requests,
notifications, and approvals.
Since the SAP Workflow System can only communicate with ABAP Objects classes and business object repository (BOR) objects, SAP EHS Management
uses the PCO as a layer to make BOPF business objects and their functionality available to the workflow system. For each PCBO in the BOPF, a corresponding
PCO class exists. The PCBO is valid for the duration of the process and the data is archived.
The following sections describe in detail how the PCO and PCBO are used:
Use in Processes
The PCO is used for communication from the workflow in SAP Business Workflow to its corresponding PCBO. The PCBO is where the business logic is
implemented and the process-relevant data is stored. The workflow can add to and read this data with the help of the PCO. The PCBO also contains a reference to
the business object that the process supports.
The graphic below illustrates how PCOs and PCBOs help you execute processes in SAP EHS Management .
PUBLIC
Page 9 of 82
PCO and PCBOs in the Process Foundation
You start a process on the user interface of the application, for example, when you add an inquiry in incident management (see Inquiries).
The system creates an instance of the PCBO according to the corresponding process definition, for example, an instance of the inquiry PCBO for the
incident inquiry process.
The event CREATED is emitted by the call of an action (START_WORKFLOW_ROOT) for the newly created PCBO instance. This starts the workflow in
SAP Business Workflow.
The PCO acts as a wrapper for the respective PCBO and implements the ABAP Objects interface IF_WORKFLOW. By implementing this interface, the
PCO is recognized as workflow-enabled in the Class Builder, and the Workflow Engine can use it.
The PCO calls the business logic from the PCBO that is to be executed in a workflow task, and also reads the data from the PCBO, so the data is
available to the workflow.
When you change the attributes of a task (for example, the approver of a maintenance notification) on the user interface of the application, the BOPF
provides a functionality so the PCBO can read, update, or delete the data automatically.
Use in Monitoring and Analyzing Processes

The data about a process that is stored in the PCBO is also used in monitoring and analyzing processes. For more information, see Process Scheduling and
Process Monitoring.
More Information
ABAP Objects classes
SAP Business Workflow
1.1.2.2 Process Configuration

SAP EHS Management is delivered with processes and a process foundation to support your business processes. You can extend and adapt these processes,
as well as create customer-specific process variants. This document provides an overview of the configuration possibilities.
Prerequisites
You have development experience with ABAP Objects and have some experience with business objects based on the Business Object Processing Framework
(BOPF) (transaction /BOBF/CUST_UI ).
You have read the topic PCOs and PCBOs.
Activities
You can configure processes in the following ways:
Adapt existing process
You can adapt existing processes delivered in the standard system to suit your customer-specific processes. For more information, see Customizing for
SAP EHS Management under
Foundation for EHS Management Process Foundation Extend and Adapt Processes .
Add new fields to store process-specific data
You can add new fields to the existing PCBO to collect additional process-specific data. For more information, see Customizing under
SAP EHS
Management Foundation for EHS Management Process Foundation Extend and Adapt Processes
and Adding Fields to the User Interface.
PUBLIC
Page 10 of 82
Note
PCO classes provide the data structures of their PCBOs as public fields. This means, the SAP Business Workflow can read the new fields
automatically that you have added.
Add new variants of a process
You can add a new variant to an existing process. You use a variant of the standard action process, for example, in incident management to handle sending
notifications to integrated systems. For more information about variants, see Customizing for SAP EHS Management under
Foundation for EHS
Management Process Foundation Specify Process Definitions .
Define logic to control how the system starts a process
The system uses an implementation of the BAdI BADI_EHFND_WFF_PCBO_CREATION to create and start processes in SAP EHS Management . You can
define customer-specific logic to control how the system starts a process. You do this, for example, when your organization must comply with regulatory
requirements in more than one country or region, and you need the system to start a different or separate process for each country or region.
For more information, see Customizing for SAP EHS Management under
Foundation for EHS Management Process Foundation BAdI: Create and
Initialize Process Control Objects (PCBOs)
.
Create customer-specific logic for a process in the PCO
If you do not want to implement customer-specific logic in the PCBO, you can extend or change an existing PCO class to create customer-specific logic for
a process. This way, a person with experiencing developing in ABAP Objects can implement this logic and must not extend the PCBO. For more
information, see Customizing for SAP EHS Management under
Foundation for EHS Management Process Foundation Extend and Adapt
Processes .
To start a workflow when the CREATED event of the customer-specific PCO class is triggered, you must assign a workflow template to this event. You can
do this in the Workflow Builder on the Start Events tab in the version-independent basic data of the relevant workflow template.
More Information
For more information about changing workflow templates, see Changing Workflow Templates.
1.1.2.2.1 Changing Workflow Templates

The workflow templates in the standard system for SAP EHS Management cover the standard processes of incident management and risk assessment. You can
change workflow templates to include new steps or change the process flow.
Prerequisites
You have experience using the Workflow Builder . Knowledge of ABAP programming is an advantage.
You have carried out automatic workflow Customizing. For more information, see Customizing for SAP EHS Management under
Management Process Foundation Basic Settings
Perform Automatic Workflow Customizing .
Foundation for EHS
Procedure
Copying Existing Workflows
To change an existing workflow, copy it into the namespace Z.
Choose in the SAP menu
Tools
ABAP Workbench Overview
management are available in the package EHHSS_WF_INC.
Object Navigator
. The workflow templates in the standard system of incident
Changing Workflow Templates

1. To change a workflow template, choose in the SAP menu
Tools
Builder .
2. Expand the workflow with new steps or change the process flow.
Business Workflow
Development
Definition Tools
Workflow Builder
Workflow
Note
If changes to the workflow template also change the business logic, you must extend or change the existing process control object of the process.
For more information, see Process Configuration.
3. Save and activate the changed workflow template.
Registering Workflow Templates

1. To deactivate the workflow template in the standard system, choose in the SAP menu
Tools
ABAP Workbench Overview Object Navigator .
2. Open the workflow template in the standard system.
3. Go to the Triggering Events tab page that shows event links. To deactivate the workflow template of the event CREATED, click the green symbol in the
Event Creator column. The symbol appears gray and the event is deactivated.
4. To register the new workflow template, open it, go to the Triggering events tab page, and register the new workflow template for the event CREATED.
Transfer the values from the standard system workflow that you used as a template for the Object Category , Object Type , and Event columns . To
activate the workflow template, click the gray symbol in the Event creator column. The symbol appears green and the event is registered.
Result
PUBLIC
Page 11 of 82
The workflow template includes new steps or the process flow has changed.
Note
If you create a new version of the template, any tasks already performed based on the previous version of the template can still be displayed during a search
on the Tasks menu or in analytical dashboards. However, if you create a new template, any tasks created with the previous template are no longer displayed
in the system.
More Information
For more information about workflows, see SAP Business Workflow.
For more information about configuring processes, see Process Configuration.
1.1.2.3 Task Management

This function provides the person responsible for a business process, such as a manager or supervisor, an overview of the tasks for the processes of SAP EHS
Management , and the ability to send notifications to the task processor. You can use task management to monitor the progress of work on tasks for the processes
supported by SAP EHS Management , and to identify and respond quickly to delays in completing tasks.
Features
Task management for SAP EHS Management provides the following features:
Overview of Tasks
The tasks results list displays all relevant information for a task, such as processor or days overdue, and links take you directly to the data record for the
referenced object or processor. You can also display the process details for a task to see the task in the business process context.
Task Operations
You can change task assignments, forward tasks, change the due date for tasks, and set the task status to complete.
Queries and Export to Spreadsheet
You can use your own queries to search tasks and display an exportable task hit list. If you are responsible for employees that use the system to process
tasks, you can display tasks assigned to your subordinates.
Notifications
You can notify a task processor directly from the task query hit list to provide a comment or reminder for the task. When you choose to send a notification, the
system automatically displays the maintained language (or languages) of the processor, so you can comment in the appropriate language if necessary. The
system sends the notification via an e-mail that contains the task details and your comments. You can also display the information for a person involved in a
task or process, and send an e-mail directly from the information dialog for the person.
More Information
If you have been assigned tasks in SAP EHS Management , you receive the tasks in the Work Overview . For more information about the functionality available
for this inbox (for example, entering substitutions for a planned absence), see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp SAP
ERP Enhancement Packages
ERP Central Component Enhancement Package 5 . Choose
SAP Library
SAP Business Suite Processes and Tools
for Enterprise Applications
Inbox (CA-EPT-IBO) .
1.1.2.3.1 Changing the Task Processor

Changing the Task Processor in the Application
You can change the processor of a task in task management or directly from the process details view of a data record.
These screens provide task operations to make processing tasks simple. Depending on the selected task, different operations are available. You can choose one
of the following task operations for a task:
Assign To Me
Cancel Assignment
Forward
For more information about task management and displaying process details, see Task Management and Tracking Progress on Tasks and Processes.
Changing the Task Processor in the Back-End System

You can perform the following procedure to change the task processor in the back-end system. Ensure first that you are authorized to use the workflow tools of
SAP EHS Management (authorization object EHFND_WFT).
Procedure
To change the current processor of a task, you can perform the following steps:
1. Display the process details. You can do this in the data record by selecting the status link for a task on the Tasks tab, or in task management by choosing
the Display Process Details pushbutton for a task.
2. To display technical information about the process, navigate to the workflow system by choosing the Display Workflow Log pushbutton.
PUBLIC
Page 12 of 82
3. Select the step for which you want to change the processor and choose in the menu
Goto Work Item .
4. In the subsequent screen for the work item, choose in the menu
Goto Technical Work Item Display .
5. In the change mode (choose in the menu
Edit Change ) of the Display work item screen, choose the Execute pushbutton for the Forward
service.
6. Enter the user of the new processor.
The system forwards the work item as a task to the new processor.
1.1.2.3.2 Continuing Execution of a Process with Errors

To continue the execution of a process, you can navigate to the SAP Business Workflow system to continue processing after the erroneous step or to start
processing of an erroneous step again. Errors can be caused by temporary problems in the workflow engine or by other exceptions during the execution of a
process step. You can see the error state in task management or on the Tasks tab of a data record.
Prerequisites
You have been assigned the Process Administrator role and the authorization object EHFND_WFT.
You have configured the processes of SAP EHS Management properly in the Customizing activities under
Management Process Foundation .
SAP EHS Management
Foundation for EHS
Procedure
To continue the execution of a process, perform the following steps:
1.
2.
3.
4.
5.
Display the process details. You can do this from the Tasks tab of a data record or from task management.
To display technical information about the process, navigate to the workflow system by choosing the Display Workflow Log pushbutton.
Select the erroneous step and choose in the menu
Goto Work Item .
Activate the administrative functions by choosing in the menu
Extras
Activate Administration .
You can start the execution of the process after the error. Or if you have corrected the cause of the error, you can also start execution of the erroneous step
again.
More Information
You can also continue a workflow that has an error with the standard functionality of SAP Business Workflow. You can display the erroneous workflows in
Diagnosis of Work Items Containing Errors (transaction SWI2_DIAG ).
1.1.2.4 Process Tools

Process tools enable a process administrator to monitor scheduled and recurring processes in the application log of SAP EHS Management . You can keep track
of the running processes and access the messages logged, such as success or failure messages. This helps you to pinpoint any problems that prevent a
process from running properly.
Note
This document describes the monitoring functions available for a process administrator in the delivered system. If you are not a process administrator and want
basic capabilities to monitor processes and tasks, see Tracking Progress on Tasks and Processes. If you want to monitor and analyze processes using SAP
BusinessObjects Dashboards, see More Information below.
Usage of Processes in the Application

The user schedules processes and defines them as recurring in the application on the Tasks tab. There, the user can add an action or notification and specify
the start and end date/time, as well as when and how often the action or notification recurs. After the user has scheduled the action or notification in the application,
the system automatically schedules the program R_EHFND_SCHEDULER_JOB to start the process for the specified start date/time. The program logs the
messages in the application log for you to monitor and analyze.
Prerequisites
You have been assigned the Process Administrator role. For more information, see Process Administrator (for Business Package) or Process Administrator (for
SAP NetWeaver Business Client).
You are authorized to call programs in transaction SE36 .
Features
SAP EHS Management is delivered with the following log objects and subobjects to monitor and analyze processes in the application log (transaction SLG1 ):
Log Object
Log Subobject
Description
EHFND_FW
WF_SCHEDULER
General Scheduler Log

Displays information about the activities of the process
PUBLIC
Page 13 of 82
scheduler, the instances of a process setup, and any

errors.
EHFND_FW
WF_SCHEDULER_ITEM
Scheduler Item Log

Displays detailed information about the execution of the
instance of a process setup and about any errors.
You can use the following features of process monitoring and analysis:
The system displays the instance of a process setup and its corresponding messages in the application log with green (information), yellow (warnings), and
red (error) LED lights.
You can use the instance ID of a process setup to disable the process setup in program R_EHFND_PSE_DISABLE_ENTRY.
You can set up the system to disable processes that have a given number of errors after a specified date in program
R_EHFND_PSE_DISABLE_ERRONEOUS.
You can exclude specific process definitions from monitoring and analysis. For more information, see Customizing under
SAP EHS Management
Foundation for EHS Management Process Foundation Processes
Specify Process Definitions .
You can exclude process steps from monitoring and analysis by removing the property sap.eh.fw.wff.report_include in the workflow template for
a process. By default, the process steps with an agent assigned are relevant for monitoring and analysis as well as several background steps.
More Information
For more information about adding actions and notifications in incident management, see Adding Actions and Notifications.
The data for scheduled and recurring processes is stored by the process setup business object. For more information, see Business Objects.
For more information about monitoring and analyzing processes in dashboards, see http://help.sap.com
EHS Management SAP EHS Management Process Foundation Xcelsius Dashboards .
SAP NetWeaver
BI Content 7.05, SP02
SAP
1.1.3 Print Forms and Interactive Forms (EHS-MGM-FND-FRM)

You use this component to generate print forms (such as a report) and interactive forms with data from the application. You can add, remove, and modify the
standard reports and questionnaires that are delivered.
Implementation Considerations
Adobe Document Services (ADS) are required and used to generate the forms and extract the data. They are located in the SAP EHS Management foundation
layer.
Integration
You can use the legal reports that are delivered with the standard system as they are, without making any changes. For more information, see Reporting to Legal
Authorities.
You should adapt the questionnaires and internal reports that are delivered to your companys internal layout. SAP EHS Management uses the default technology
for developing the layout of a form.
Print forms and interactive forms can be used by several components and processes within SAP EHS Management :
Inquiries and questionnaires to gather additional information from another system user or an external person
Report forms
Control evaluations
Features
Questionnaires, legal reports, and summary reports
SAP EHS Management is delivered with print forms and interactive forms to request information in a questionnaire, report to authorities, or produce a
summary of collected data. You can generate forms directly from the data record and as part of a process. In some cases, the system suggests forms to
support you in complying with legal reporting requirements.
Send forms via e-mail, print forms, or store forms for offline use
You can send forms from the data record via e-mail as part of a process. The recipient can send the form back using the Send pushbutton at the end of
the form. Since some recipients of a form do not have access to the SAP EHS Management system, some forms can be stored on an Intranet to complete
offline, or printed out and filled out by hand.
Review data before transferring into a data record
You can configure forms to provide a review step. When the form is returned, the system generates a task for the sender to review the returned data. This
enables you to preview the contents of the form and select which data you want to transfer into the data record.
Example
You can send a PDF-based questionnaire to a witness, asking them to provide additional information about an incident.
More Information
For more information about adding new forms, see Adding Print Forms and Interactive Forms and Mapping business objects nodes to Adobe Forms.
PUBLIC
Page 14 of 82
1.1.3.1 Adding Print Forms and Interactive Forms

You can add additional print forms and interactive forms to SAP EHS Management , for example, additional legal reports or questionnaires.
The framework for form generation in SAP EHS Management consists of the following components:
Form controller
An ABAP Objects class that is the public interface to generate forms and extract the data (CL_EHFND_FW_ADS_CONTROLLER)
Form creation controller
An ABAP Objects class that is called by the form controller and can be implemented for a specific form. A form creation controller must implement the
interface IF_EHFND_FW_ADS_FORM_CR_CTRL. We recommend using the generic form creation controller of SAP EHS Management :
CL_EHFND_FW_ADS_FORM_CR_CTRL.
Data provider
An ABAP Objects class that obtains the data from the application and fills the interface structure of a form. A data provider must implement the interface
IF_EHFND_FW_ADS_DATA_PROV.
Inbound persister
An ABAP Objects class used to store the data of an interactive form automatically in the application. An inbound persister must implement the interface
IF_EHFND_FW_ADS_INBD_PER.
Configuration
You can configure forms in Customizing for usage in the application.
These components are used in the Procedure.
Prerequisites
You have experience developing in ABAP Objects, using data definitions in the ABAP Dictionary, and developing interactive forms based on the Adobe software
in transaction SFP .
To develop the form layout, you have the Adobe Document Services (ADS) installed locally. For more information about ADS, see SAP Service Marketplace at
http://service.sap.com/ADOBE .
Procedure
The following sections describe the steps specific to SAP EHS Management for adding new forms in the Form Builder (transaction SFP ).
Creating ABAP Dictionary-Based Structures

The framework for form processing in SAP EHS Management supports only one interface structure for each form interface. This means, for example, if you need
to have the data of a person and the data of a release in the form, you must do the following:
1. Create an ABAP Dictionary-based structure for both types of data (for example, the person data and the release data).
2. Create an ABAP Dictionary-based structure for the interface that contains both the person and release structures.
Note
If you create an interactive form, include the structure EHFNDS_FW_ADS_META in the interface structure to provide metadata for the form during inbound
processing.
Creating Form Interfaces

The form interface defines the data that is available in the form layout, and which data the system must retrieve in the data provider implementation. To create a
new form interface, perform the following steps:
1. Create the form interface in transaction SFP .
2. Under Form Interface , double-click the Import node and enter the Parameter Name .
Recommendation
To use the generic form generation controller, enter INTERFACE_STRUCTURE as the parameter name. If you want to use a customer-specific form
generation controller, you must implement the interface IF_EHFND_FW_ADS_FORM_CR_CTRL.
3. Enter the ABAP Dictionary-based structure as the Type Name . If you created an interface structure as described in Creating ABAP Dictionary-Based
Structures, you enter the interface structure here.
Creating Forms
1. Create the form name in transaction SFP .
2. Specify the following values for the properties of the form:
Description: (form description)
(Layout) translation: Standard
(Layout) technology: XFA
(Layout) type: Standard Layout
Interface: (enter the form interface from Creating Form Interfaces)
Inbound Handler: (optional)
To create an interactive form, enter the default inbound handler for SAP EHS Management . Based on this setting, the system generates coding for
the extraction of the form data.
3. In the Context tab, enter the form context by dragging and dropping the structures from the left side of the screen to the right side. In doing this, you make
PUBLIC
Page 15 of 82
the data available in the form layout.
Laying Out Forms

When you insert new data fields from the Data View in a form, you bind the data to a field in the form layout by performing the following steps:
1. Copy a field into the form using drag and drop for the data field, for example, a text field.
2. Choose the tab
Object Binding .
3. Enter the data field value for the default binding.
Data Provider
The following methods of the data provider are delivered. They store the data within the form and the form itself.
Method
Description
GET_DATA
Extracts the data from the application and returns the filled interface structure
This method contains the following:
Form information that is configured in Customizing as the importing parameter
The process component-specific form context
The corresponding relation to the process control object if the form is used in a
process
For more information about processes, see Process Foundation.
VALIDATE_DATA
Validates the data that is in the form
GET_FILENAME_SUFFIX
If the form belongs to a specific object (such as the person), the corresponding suffix of
the file name can be set. This method is called after generation of a form when the file
name is created.
For more information, see the test data provider CL_EHFND_FW_ADS_TEST_DPROV in the system, or the data providers configured in Customizing under
EHS Management
Specify Forms
SAP
Inbound Persister Implementation (Optional)
Note
The inbound persister is needed for SAP Interactive Forms by Adobe only.
The inbound persister must implement the interface IF_EHFND_FW_ADS_INBD_PER that contains the following methods:
Method
Description
STORE_DATA
Stores the data of a form
VALIDATE_DATA
Validates the data that is in the form
GET_FILENAME_SUFFIX
If the form belongs to a specific object (such as the person), the corresponding suffix of
the file name can be set. This method is called after generation of a form when the file
name is created.
STORE_FORM
Stores the form
GET_COMMENT_OF_FORM
Returns the comments that have been entered in the form
For more information, see the inbound persisters configured in Customizing under
and Interactive Forms
Specify Forms .
SAP EHS Management
Print Forms
Form Configuration
You can specify forms in Customizing under
Forms .
SAP EHS Management
You can specify the groups for forms in Customizing to control the appearance and usage of the forms in the application under
Foundation for EHS Management Print Forms and Interactive Forms
Specify Forms .
Specify
SAP EHS Management
1.1.3.2 Mapping Business Objects Nodes to Adobe Forms

If you want to build your own reports based on Adobe Document Services (ADS), you have to perform the steps described in Adding Print Forms and Interactive
Forms. The step Data Provider requires a high level of knowledge about how to read data from the business object. This function supports you in implementing a
the data provider class. The Mapping Workbench enables you to map business object nodes to nodes that are used in SAP Interactive Forms by Adobe by
dragging node elements from the business object tree and dropping them to the form context tree. After mapping the nodes you need, you can generate the
corresponding data provider class that reads the data from the business object and provides the data for the interactive form generation.
Prerequisites
You have specified forms in Customizing for SAP EHS Management under
Forms .
Specify
You have defined the form interface in transaction SFP .
PUBLIC
Page 16 of 82
You are using the business objects delivered in the standard system.
You are using a business object node to obtain the data. This node contains all fields that have to be extracted.
Features
The Mapping Workbench provides the following features:
Define field mapping
You can create mappings between the business object nodes and the form context nodes by using the drag and drop functionality. The system visualizes
the created mappings in a separate table and with an icon at the mapped elements.
Note
You can map a node from the form context only once.
Generate data provider
After you have finished the mapping, the system generates all needed code lines for creating or changing the data provider.
Activities
While building up the mapping and creating a data provider, the system performs the following activities:
The system performs the following compatibility checks, and forbids the mapping in case of errors. Possible errors include the following:
The data type of the business object elements it not convertible into the data type of the form context element.
The data type of the form context element is not convertible into the data type of the business object element.
After you have saved your work, the system saves the created mappings and checks whether existing mappings are consistent. In case of an error, the
system generates mapping proposals that you can execute by choosing the Propose Mapping pushbutton.
After you have finished the mapping, you can choose the Generate Data Provider pushbutton, and the system generates the data provider. When you
choose the Edit pushbutton, the system opens a source code editor with which you can modify the generated class. When you regenerate a manually
modified class, the system can handle the following situations:
If you modified or added code line, the system adds the coding to the regenerated code.
If you deleted a generated code line, the system adds the coding again if the node is still mapped.
If a specific code line is obsolete after regeneration, the system comments it out.
More Information
For more information, see Customizing for SAP EHS Management under
Forms .
Specify
1.1.4 Integration (EHS-MGM-FND-INT)

You can use this component to integrate SAP EHS Management (EHS-MGM) with other components. This enables you to access data in other components from
within the EHS-MGM applications and transfer data from EHS-MGM to other components. In addition to simplifying work with the applications, integration also
ensures consistency by reusing existing data in different components. If you use integrated data in EHS-MGM , changes to this data are automatically reflected in
all applications.
You can also use integration to start EHS-MGM processes involving actions in different components.
The integration of other components is only possible if the relevant components are fully installed and configured. Depending on which component you integrate,
you can access data that is stored locally or in a remote system, or you can transfer data to a remote system. You specify the destinations for remote systems in
Customizing for SAP EHS Management under
Foundation for EHS Management Integration Specify Destinations for Integration .
Note
It is not possible to access MM and PA-OS data that is managed in a remote system. This data must always be stored locally.
Authorizations
If you are responsible for setting up integration, be aware that the following authorization objects are required for the corresponding activities:
S_USER_RFC Editing RFC connections
<name of auth. object> Entering RFC connections for PFCG roles in SM59
Features
The following table lists the integrated components and specifies how these components can support your business scenarios in the SAP EHS Management
applications:
Component
Function
Usage in SAP EHS Management

Incident Management
PUBLIC
Risk Assessment
Product Compliance
Page 17 of 82
Personnel Administration (PA)
Personnel Time Management

(PT)
Read person-related data for

employees and applicants
Read and create absences for

employees
Read data for business partners
Change and create data for

business partners
(not activated by default)

SAP Business Partner (SAP
BP)
Organizational Management (PA- Determine relations between

X
OS)
individual persons, positions, and
X
X
organizations
Plant Maintenance (PM)
Import and read data for PM
Read and create maintenance

notifications
Read and create maintenance

orders for financial tracking
technical objects
Flag PM technical objects for

which risk assessment
information can be retrieved and

communicate risk information
Customer Service (CS)
Quality Management (QM)
Read and create service

notifications
Read and create service orders for

financial tracking
Read and create quality
notifications
Accounting (AC)
Read and create internal orders for X

financial tracking
Materials Management (MM)
Read material data
SAP BusinessObjects
Transfer data to the SAP
governance, risk, and compliance BusinessObjects Risk
solutions (GRC solutions)
(not activated by default)
SAP Management of Change
Management component
Transfer results of simulated risk

assessments to SAP
Management of Change
Create a change request and send X

it to SAP Management of
Change
Constraints
The following data must always be available in the local system:
Plants and plant descriptions
Material and material descriptions
Currencies and exchange rates
Notification types for PM, QS, and CS
Business partner roles
Marital status texts for HR persons
Marital status texts for business partners
Attendance and absence types
Shift group and shift planning of the organizational unit
Organizational data, including organizational units and persons in PA-OS
Note
To make organizational data from PA-OS available in the local system, you can distribute the relevant HR master data between the PA-OS system
and the EHS-MGM system. However, since the EHS-MGM applications only require specific PA-OS data, distribution limited to the basic infotypes
is sufficient. The distributed organizational data cannot be changed from the EHS-MGM applications as the system settings only allow read access.
For more information about distributing HR master data, see the application help documentation for SAP ERP at http://help.sap.com/erp605/ SAP
ERP Cross-Application Functions
Scenarios in Applications
ALE/EDI Business Processes
Library of ALE Business Processes
Human
Resources
Master Data Distribution (Human Resources) .
For more information, see the documentation in Customizing for SAP EHS Management under
Destinations for Integration .
Integration
Specify
More Information
For more information about integration in each SAP EHS Management component, see the following documentation:
PUBLIC
Page 18 of 82
Incident Management: Integration with Other Components

Risk Assessment: Integration with Other Components
Product Compliance: Integration
1.1.4.1 Integration for Person Information

You can use this function to integrate person-related data from other components with SAP EHS Management (EHS-MGM) . This data can either be stored locally
or in remote systems. The function allows you to access data for HR persons and business partners, organizational information, and time data. You can access
person information through integration to the corresponding components:
Personnel Administration (PA)
SAP Business Partner (SAP BP)
Organizational Management (PA-OS)
Personnel Time Management (PT)
Note
PT integration is only available for the incident management application and must be activated separately.
Prerequisites
You have checked the settings for the relevant authorization objects as described in Customizing for SAP EHS Management under
Foundation for EHS
Management Integration Human Resources Integration Check Authorizations for Person Information .
You have defined the relevant subtypes for party infotypes in Customizing for SAP EHS Management under
Integration Human Resources Integration Specify Relevant Subtypes for a Party Infotype. .
You have defined the contractual relationships to employee groups and employee subgroups or business partner roles that are relevant for legal reporting.
You can make these settings in Customizing for SAP EHS Management under
Foundation for EHS Management Integration Human Resources
Integration Specify Person Groups and Contractual Relationships .
If you want to integrate data that is stored in remote systems, you have set up the integration of the required systems in Customizing for SAP EHS
Management under
If you want to integrate personnel time data, you have made the application-specific integration settings as described in HR Integration for Absence
Assignment.
Features
You can use this function to read person information from the components listed above.
For the incident management application, PT integration and SAP BP integration also allow you to change person-related data:
You can create new business partners and change the data of existing business partners.
If PT integration is activated, you can create HR absences for injured persons.
1.1.4.2 Integration for Notifications

You can use this function to integrate notification processes between SAP EHS Management (EHS-MGM) and other components that are either managed locally
or in remote systems. It allows you to start processes for notifications that must be implemented in other components directly from the EHS-MGM applications.
The EHS-MGM system monitors the status of each notification process until it is completed.
Integration is possible for the following notification categories:
Maintenance notifications (PM)
Quality notifications (QS)
Service notifications (CS)
Prerequisites
You have specified the required notification types in Customizing for SAP EHS Management under
Foundation for EHS Management Integration
Specify Notification Types .
If you want to integrate data that is stored in remote systems, you have set up the integration of the required systems in Customizing for SAP EHS
Management under
Features
If the circumstances of an event or situation require actions to be taken in other components, you can start processes to communicate and initiate related tasks.
For each notification, you can display details including its status directly from the EHS-MGM applications.
You can use the report Check for Completed Notifications (R_EHHSS_ACT_CHECK_COMPL_EXT_NO) to check regularly for notifications that have been
completed in other components. For all notifications in status Completed , the report triggers the next process step. For more information, see the system report
documentation.
Note
If you schedule notifications as recurring actions, the system starts a notification process for each recurrence.
PUBLIC
Page 19 of 82
The notifications sent to integrated systems are logged in the application log. You can display the log in transaction SLG1 (object EHFND_INTEGRATION,
subobject EHFND_EXT_NOTIF).
1.1.4.3 Check for Completed Notifications

You use the report Check for Completed Notifications (R_EHFND_CHECK_COMPL_EXT_NOTIF) in SAP EHS Management to check if notifications have been
completed in the following components:
Plant Maintenance (PM)
Customer Service (CS)
Quality Management (QM)
Integration
You use this report when your system is integrated with one or more than one of the components specified under Use.
Prerequisites
You have specified the destinations of the PM, CS, and QM systems in Customizing for SAP EHS Management under
Integration Specify Destinations for Integration .
You have specified the notification types that you use in the application in Customizing for SAP EHS Management under
Integration Specify Notification Types .
Features
The report determines all notifications that are in status In Process and checks whether these notifications have been set to Completed in the relevant
component. For all notifications that have been completed, the report triggers the next process step to create a task for the approver to complete the notification in
the application.
The system document report actions in the application log (object EHFND_INTEGRATION, subobject EHFND_EXT_NOTIF).
Activities
Depending on the business processes of your company, you can schedule the report to occur periodically, for example, once a day, in Customizing for SAP
EHS Management under
Foundation for EHS Management Integration Schedule Job for Notification Status Check .
1.1.8.1.3.1.1.1.4 Locations
You use this component to represent an identified real place, virtual space, or object in the system. The location is a central master data object that can be
organized in a structure to represent where a location exists spatially or functionally in a company. Examples of a location are a plant, a piece of equipment, or a
work area.
The location makes it possible to utilize existing technical objects and functional locations from the Plant Maintenance (PM) component, and work areas from
existing EHS solution in SAP EHS Management . For more information, see Integration.
In incident management, locations specify precisely where an incident took place and, in risk assessment, locations specify precisely where hazards exist. A
location could be a hallway, a fire hydrant, or a boiler that produces emissions, for example. When you open a location, the system displays an overview of all
location-relevant incidents according to the selected filter criteria. You can access the corresponding incident records directly from this incident overview.
Note
The incident overview does not include archived incidents and incidents with the status Void .
For more information about incident management, see Incident Recording
Integration
You can create your own locations, or you can import technical objects that already exist in the Plant Maintenance (PM) component as locations into SAP EHS
Management to save you the time and effort of entering duplicate information. You can also integrate existing locations that you have already created in your SAP
EHS Management system with technical objects from PM .
You can use report R_EHFND_LOC_MIGRATE_WA to migrate work areas from the existing SAP solution for managing environment, health, and safety into
locations in SAP EHS Management . For more information, see the report documentation.
Features
Location details
Displays detailed information about a location, such as the plant, company code, and business area to which it is assigned. You can also display the
locations address and geographic coordinates to identify its precise position. This way, you can visualize it on a map that can be integrated into the system
PUBLIC
Page 20 of 82
in Customizing.
Revisions
You can create revisions for recording time-specific versions of a location. For example, if a location is currently assigned to plant 0001 but will be
reassigned to plant 0002 tomorrow, then you create a revision with tomorrows date and define the new plant there. Revisions ensure that a locations historic
data is retained and not simply overwritten.
Status
You can specify whether a location is active or inactive. You can also use the Historic status if a location is no longer used, but you need to keep a record
of it in the system to document historical information. You can use the Historic status, for example, if a location is out of service, or has been sold.
Location structures
You can organize your locations in structures and expand the structure to show any subordinate nodes.
Mass changes
You can make changes to several locations at once to save time and administrative effort.
More Information
Maintaining Locations and the Structure
Importing Locations from PM
1.1.5.1 Location
An identified real place, virtual space, or object. The location is a central master data object that can be organized in a structure to represent where a location
exists spatially or functionally in an organization.
Examples of a location are a plant, a piece of equipment, or a work area.
You use this business object to recreate the real places, virtual spaces, and objects at your organization in the system. You can organize locations in a structure
to show the hierarchical relationships between locations and allow navigation.
Once a location exists in the system, you can reference it in data records to describe, for example, where an incident occurred or where a risk assessment will
take place.
Structure
The location is comprised of the following data:
Data
Notes
Identifying information, such as name and ID

Integrated technical object or functional location via a link to the Plant Maintenance
(PM) component
Establishing a link fills the attributes data with data from PM. Data changes in PM appear
automatically in the location. Removing a link allows you to edit the attributes for the
location and disables automatic transfer of changes from PM.
Attributes, such as a plant ID and cost center

Address information
Partner information
If an integrated object has business partner data assigned, the system displays this
information in the Partners tab. Otherwise, the tab is not visible.
Positions
If people work at a location, you can assign the positions from HR to the location. The
system displays the objects, such as employees or business partners, assigned to the
position when you display the details for the position.
Status Values
When you create a location, the system assigns the New status. You can edit the location and keep the location in the New status if you have not finished
editing. Once you have finished editing, you can set the following status values in the location master data:
New -> Active
The location data is complete and up-to-date.
Active <-> Inactive
The location or its data are no longer relevant. You can make changes to the location and set the status back to Active .
Inactive -> Historic
The location no longer exists. However, the location must remain in the system, because it is assigned to older data records. You cannot edit the master data
of historic locations.
Regardless of the status, you can assign locations (even new, inactive, and historic locations) to your data records in SAP EHS Management .
Integration
You can use locations without integration to other components. However, if you want to link to technical objects and functional locations, you require integration with
PM. If you want to assign positions to a location, you require integration with the Organizational Management (PA-OS) component.
1.1.5.2 Maintaining Locations and the Structure
PUBLIC
Page 21 of 82
You can create and maintain locations in two ways. You can create them manually, or you can import technical objects from the Plant Maintenance (PM)
component as locations.
The following information describes how you create a location manually and maintain the location structure.
When you create a location, you can define master data such as the plant or company code to which that location belongs. You can also specify the locations
address and geographic coordinates to identify its precise position. You can use the precise position to visualize a location on a map that can be integrated into
the system in Customizing for SAP EHS Management under
Foundation for EHS Management Locations
Configure Integration of Map .
You use location structures to organize your locations. You can create locations at different positions within the structure, or change the position of existing locations
within the structure using the Insert and Remove , and Cut and Paste functions.
You can make mass changes to the attributes of multiple locations in one go. This saves you the time and effort of having to maintain each location individually.
Prerequisites
You have enabled PM integration in Customizing for SAP EHS Management under
PM Integration
You have specified location types in Customizing for SAP EHS Management under
Types

Locations
Locations
Enable/Disable
Specify Location
Procedure
You can maintain the locations and structure using the following three procedures:
Creating a Location Manually

1. Choose Locations and in the Services area, choose Manage Structure . If you are creating a new structure, select the first node in the table, Location
Structure . If you want to add a location to existing structure, select the position in the structure where you want to add it. Then choose Create Location .
2. Enter the Location Description and Type for your new location and choose OK .
3. You now see your location in the location structure. Choose Save and then Open .
4. Enter master data to identify your location and to specify it further. Set the Status and define a Revision if you require.
5. When you have finished, choose Save .
Maintaining the Location Structure

1. Choose Locations and in the Services area, choose Manage Structure . To change the position of an existing location in the location structure, select the
relevant location and then choose one of the following functions:
Function
Explanation
Insert
Adds a location below the selected position in the structure
Remove
Removes the location from the location structure
Caution
Removing locations from the structure does not delete them. If you remove a
location, you can still reference the location and use its data. However, it is not
possible on some screens in the application to select a location that is not in the
structure.
Cut
Temporarily saves the location so you can insert it using the Paste function
Paste
Pastes the cut location as a subordinate node of the selected location and removes it from
its previous place in the hierarchy
Changing Location Attributes

1.
2.
3.
4.
Choose Locations and then choose

Services
Change Attributes .
Select the Key Date from which you want the changes to apply.
Change the location attributes that you want to change and choose Next .
Now select the locations you want to change, either by searching for them or by adding them from the location structure. To do the latter, select one or more
locations by holding down the CTRL button and clicking with the primary mouse button on the relevant location. To expand subordinate locations, you can
click the arrows and display the subordinate locations. You can automatically add all subordinate locations by selecting the relevant checkbox.
Choose Next .
5. Review the changes that you want to apply to the location or locations before choosing Change .
6. The system confirms that your changes were made.
Result
The locations and their structure are displayed on the Recent Locations and Structure View tabs in the Locations area. The locations can be used when you
report an incident or assess risk.
1.1.5.3 Importing Locations from PM

You can search for technical objects from the Plant Maintenance (PM) component and import them as locations into the SAP EHS Management component.
The advantage of this is that you do not have to enter duplicate data; the basic data for these locations originates from PM . You can import up to 50 locations into
PUBLIC
Page 22 of 82
SAP EHS Management at any one time. Alternatively, you can link locations that already exist in SAP EHS Management with technical objects from PM .
In either case, you always have the option of removing the PM link at any time. This removes the association between the technical object and the location. You
can then import a completely different location, or import the same location at a different position in the location structure, for example.
Prerequisites
You have enabled PM integration in Customizing for SAP EHS Management under
PM Integration
You have specified location types in Customizing for SAP EHS Management under
Types

Locations
Locations
Enable/Disable
Specify Location
Procedure
Importing New Locations from PM
1. Click Locations and then in the Services area, choose Import Locations from PM .
2. Specify your search criteria for finding the technical object you require (detailed search criteria shortens the search time) and choose Search . Select the
technical object you require and then choose Next .
Note
You cannot import a location that is already linked to another location.
3. Decide which locations you want to import. If a location contains subordinate objects, choose whether you want to import these as well. You can only import
subordinate objects together with their parent node.
Use the Import As (Location Type) options to define the location type that a location has when it is imported.
To specify a location type for one or more than one location, choose Import As above the table and select the relevant location type. The system
applies the selected location type to all of the locations in the table.
To specify the location type for only one location in the table, choose the relevant location type for the location directly in the table using the Import As
(Location Type) option. The system applies the selected location type to just this location.
Choose Next .
4. Select the position in the existing location structure below which you want to insert the location (and any subordinate objects). Choose Next .
5. Review the technical object that you are about to import and its location parent node. Choose Import .
The system imports the locations.
Linking Existing Locations to PM

1. Display the location in the location structure by choosing Locations and in the Services area, choose Manage Location Structure .
2. Open the location you want to link to a technical object from PM and choose Establish PM Link .
Note
This overwrites the locations existing master data.
3. Follow steps 2 to 5 above.
Result
The system inserts the location into the location structure and you can use it in the application, for example, for reporting incidents.
1.1.6 Chemicals
When you work with chemicals, your organization is subject to regulatory requirements that govern the use of chemicals and the exposure to your workers. SAP
EHS Management enables you to manage chemical data and protect the health and safety of workers that use chemicals, and ensure product and regulatory
compliance.
The following business objects are common to the processes of SAP EHS Management :
Chemical
Listed substance
Regulatory list
Health and Safety

You can analyze exposure to chemical agents in risk assessments, group workers together by their exposure to chemical agents into similar exposure groups,
and monitor exposure to chemical agents with personal exposure profiles.
To support these business processes, the common business objects listed above are used in the following ways:
Chemical
When you create a chemical agent, the chemical business object stores the physical and chemical properties data for the chemical agent. While the
chemical agent references the chemical data, you work primarily with the chemical agent in the health and safety processes.
Listed substance
You enter listed substances as hazardous ingredients in the chemical agent. You can also create listed substances from within the chemical agent data
record. The listed substance stores the CAS number and the listed substance name.
PUBLIC
Page 23 of 82
Regulatory list
You define occupational exposure limits (OELs) for listed substances in regulatory lists. Each instance of the regulatory list is called a revision and you can
enter the current OELs for a listed substance. When regulations change, you can create a new revision of the regulatory list and update the OELs. Since the
chemical agent consists of listed substances, the OEL data for the listed substance is available for the chemical agent and for use in health and safety
processes.
Product Compliance
In handling articles, you use the chemical substances that they contain. For more information, see Regulatory Lists.
More Information
For more information about chemical agents, see the business object documentation for Agents.
1.1.6.1 Creating and Revising Regulatory Lists

You can use regulatory lists in the application to store a list of substances that are subject to legal or industry-specific regulations, for example, declarable
substances or substances for which all uses are prohibited or there are possible exemptions. Regulatory lists also can also provide information about thresholds
(such as occupational exposure limits) for listed substances.
As legal or industry-specific regulations change, you can create new revisions of regulatory lists. Each instance of a regulatory list (even the first instance) is
called a revision. The system stores all revisions of a regulatory list and keeps existing references to historical data. This enables you to keep accurate records
and helps you ensure compliance.
Process
In Customizing for SAP EHS Management , you must first make the following settings before creating regulatory list revisions in the application:
1. In Customizing under
Foundation for EHS Management General Configuration Create Regulatory Lists and Customer Lists
regulatory lists that you want to use in the application, for example, China RoHS .
2. Make further settings for regulatory lists in the following Customizing activities as required:
Risk Assessment Master Data Configuration Agents
Specify Regulatory Lists for OELs .
Product Compliance Regulations
Specify Regulatory Lists and Customer Lists .
, configure the
Regulatory Lists in Health and Safety

In the application, perform the following steps to create and revise regulatory lists:
1. In
Health and Safety
Overview Agents and OELs , choose the service Create Regulatory List Revisions .
2. Select a regulatory list and enter data about the new revision.
3. The system copies any existing data in the regulatory list, such as listed substances and occupational exposure limits, to the new regulatory list revision.
You can add new data and update existing data.
4. To use the data from the regulatory list in analyzing exposure to chemical agents, release the revision.
Note
You can only have one inactive revision open at a time. You must first release or delete the currently inactive revision before creating a new revision.
Regulatory Lists in Product and Safety Stewardship

For more information about using and managing regulatory lists, see the following topics:
Regulatory Lists and their Revisions
Regulatory List Management
More Information
For more information about using regulatory lists in health and safety, see Defining Occupational Exposure Limits (OELs).
1.1.6.2 Transferring Data from the Specification Database

The component extension for SAP EHS Management (the add-on) provides two reports to transfer chemical data from the specification database of SAP EHS
Management as part of SAP ERP to the add-on system for use in the risk assessment business process. If you use the specification database for managing
hazardous substances, you can leverage your existing investment and transfer the chemical data via RFC from a remote EHS system to the add-on system.
You can use the reports to replicate data from the following substances for use in the add-on system:
Real substance or agent (as a source for the chemical agent) Report R_EHFND_FILL_CHM_BY_EHS_SUBST
Listed substance (as a source for the listed substance and its OEL in the regulatory list) Report R_EHFND_FILL_REGL_BY_EHS_SUBST
You configure the reports in Customizing to specify and map the data sources from the specification database to their corresponding destinations in the add-on
system. You save a set of hits in the specification database to provide a preselection of the substances to transfer. The reports then use the Customizing settings
to determine the value assignment types and characteristics of the substance in the specification database that contain the data to replicate. Finally, the reports
replicate the data as required and create new chemical agents and listed substances (and OELs) in the add-on system. You can run the reports again or regularly
as background jobs to update this data, especially if you continue to maintain substances in the specification database.
PUBLIC
Page 24 of 82
as background jobs to update this data, especially if you continue to maintain substances in the specification database.
Prerequisites
You have configured the connection from the add-on system to the remote system where the specification data is stored. Enter an RFC destination for the EHS
system in Customizing for SAP EHS Management under
You have fulfilled the prerequisites as described in the report documentation to ensure that phrases and Customizing values from the specification database
system exist as required in the add-on system. For more information, see the following reports in the back-end system Creation and Update of Chemicals from
EHS Substances (R_EHFND_FILL_CHM_BY_EHS_SUBST) and Creation and Update of Listed Substances from EHS Substances
(R_EHFND_FILL_REGL_BY_EHS_SUBST).
Procedure
1. Select substances in the specification database (in the remote system).
Select substances by searching and using a set of hits in the specification workbench, and then save the results (via
Utilities
Set of Hits
Save .
You can also modify the set of hits regardless of the search criteria, for example, to reduce the results. Save one set of hits for the data transfer to chemical
agents and one set of hits for the data transfer to listed substances.
If you plan to regularly transfer data, you can create queries. Otherwise, search and save sets of hits to refresh the results before every transfer to the addon system.
2. Configure the report to transfer chemicals in Customizing for SAP EHS Management under
Foundation for EHS Management Chemicals
Configure
Report to Transfer Chemicals . In this activity, you specify the data sources that determine the substances to transfer as well as the data sources of the
actual values, such as physical-chemical properties
The following table provides example settings for the report and does not contain all possible data sources (see the Customizing activity). It lists the data
sources in the specification database and how the report uses their data.
Purpose of Data Source
Data Source in Specification

Database
Technical Key of Data Source
Characteristic of Value Assignment

Type of Data Source
Determines the substances to transfer
Set of Hits Group Entry
User-defined key
Not applicable
When you save a set of hits in the

specification workbench, you enter a
group entry as a unique identifier.
Provides Name of chemical business
object
Identification Listing (for chemical agent)
D_IHEXPOS ( Agents in Industrial
Provides Name and CAS Number of

listed substance business object
Identification Listing for Listed Substance D_DEFAULT ( Standard listing for
Not applicable
Hygiene and Safety )

You can display the identification listings
and their corresponding ID categories and
ID types in Customizing activity Check
Identification Listing in the system for the
specification workbench.
Not applicable
identifiers )
The identification listings and their
corresponding identification categories
and identification types are defined in
Customizing activity Check Identification
Listing in the system for the specification
workbench. The report uses the
identification types within an identification
listing type that are customized for
position 1 and 2.
Provides Color data for the chemical
Color
business object
Provides Hazard Classification data for

the chemical business object
Hazard classification
SAP_EHS_1013_008
SAP_EHS_1013_008_VALUE
You can display the technical key of value

assignment types in the specification
workbench for a substance by selecting
the value assignment type in the property
You can display the characteristic name

by selecting the characteristic field that
contains, for example, the color red and
choosing F1 in the specification
tree and choosing F1.
workbench.
SAP_EHS_1023_043 ( GHS
SAP_EHS_1023_043_CLASS
Classification )
You can display the technical key of value
assignment types in the specification
workbench for a substance by selecting
the value assignment type in the property
tree and choosing F1.
The corresponding data source

determines (together with the validity
area) the characteristic to transfer.
Value Assignment Rating
PUBLIC (Released without restrictions)
Not applicable
When you enter value assignment

information for a property (such as color),
you enter on the Usage tab a [value
assignment] rating. The rating specifies
the users that can view an identifier or a
value assignment.
The corresponding data source
Validity Area
determines (together with the value

assignment rating) the characteristic to
transfer.
REG_WORLD ( World )
Not applicable
When you enter value assignment

information for a property (such as color),
you enter on the Usage tab a validity
area for the corresponding rating.
3. Configure the report to transfer listed substances and OELs in Customizing for SAP EHS Management under
PUBLIC
Risk Assessment
Master Data
Page 25 of 82
Configuration Agents . In this activity, you specify the data sources that determine the substances to transfer as well as the data sources of the actual
values, such as physical-chemical properties.
The following table provides example settings for the report. It lists the data sources in the specification database and how the report uses their data.
Purpose of Data Source
Data Source in
Specification Database
Technical Key of Data

Source
Characteristic
(Regulatory List)
Characteristic (Value
Type for OEL)
Characteristic (OEL
Value)
Determines the
Set of Hits Group Entry
User-defined key
Not applicable
Not applicable
Not applicable
Not applicable
Not applicable
Not applicable
substances to transfer
Provides Name and

CAS Number of listed
substance business object
When you save a set of

hits in the specification
workbench, you enter a
group entry as a unique
identifier.
Identification Listing (for
Listed Substance)
D_DEFAULT (Standard
listing for identifiers)
The identification listings
and their corresponding
identification categories and
identification types are
defined in Customizing
activity Check
Identification Listing in the
system for the specification
workbench.
Provides the occupational

exposure limit for the
Occupational Exposure
Limit
SAP_EHS_1023_006
SAP_EHS_1023_006_BAS SAP_EHS_1023_006_VAL SAP_EHS_1023_006_VAL

E
UE_TYPE
UE_PPM
corresponding listed
substance in the regulatory
list.
4. Ensure that you have fulfilled all prerequisites before executing the following reports. For more information, see the documentation of the following reports in
the addon system:
Creation and Update of Chemicals from EHS Substances (R_EHFND_FILL_CHM_BY_EHS_SUBST)
Creation and Update of Listed Substances from EHS Substances (R_EHFND_FILL_REGL_BY_EHS_SUBST)
5. Execute the reports as required.
Result
You have replicated the data from the specification database to the add-on system. You have created chemical agents (based on real substances or real
substance groups) and listed substances. The listed substances appear in your regulatory lists with their corresponding OELs and the listed substances appear
as hazardous ingredients in the chemical agent.
To enable subsequent data transfers, the root node of the chemical business object and listed substance business object contain an attribute to remember the
source substance in the specification database from which data was transferred.
Example
The following list contains example errors that can occur, their potential causes, and possible solutions:
No value for key specified
Cause: The phrases or Customizing entries used in the specification database do not exist as Customizing entries in the add-on system. To transfer data
from the specification database, the system requires that the technical keys of Customizing entries in the add-on system (for example, for color, form, and so
on) are identical to the phrase keys and Customizing entry keys used in the specification database.
Solution: The reports for replicating the data contain instructions for transferring phrases and Customizing entries to the add-on system.
Real substance was transferred, but a characteristic (such as color or odor) is missing
Cause: The value assignment rating and validity area of the characteristic do not match the value assignment rating and validity area you specified in
Customizing activity Configure Report to Transfer Chemicals .
Solution: Check the specified values in the add-on Customizing (see step 2 of the Procedure ) or enter the relevant value for the characteristic in the
specification database. Note that if you have specified a validity area, such as REG_WORLD, the system transfers the characteristics with this validity area.
If no validity area or a different validity area is assigned, the report replicates the real substance without this characteristic.
More Information
For more information about hit lists (saving sets of hits) and queries in the specification workbench, see http://help.sap.com/ehs under SAP EHS Management as
Part of SAP ERP and your relevant release, then choose
SAP Library
Environment, Health and Safety (EHS) Basic Data and Tools (EHS-BD)
Specification Management (EHS-BD-SPE) Specification Editing
then Hit List or Query Management .
See also chemical agents.
1.1.7 Analytical Reporting

You can use the data that you record in SAP EHS Management in analytical reports. The foundation for SAP EHS Management provides functionality to extract
data, so you can generate analytical reports in the following forms:
File-based
Spreadsheet
SAP BusinessObjects Dashboard
PUBLIC
Page 26 of 82
SAP Business Explorer (BEx) report
Note
You can find specific information about analytical reporting for each process component under the corresponding Analytical Reporting node in the application
help of the process component (for example, see
Incident Management Analytical Reporting ).
If you want to use SAP BusinessObjects Dashboards with queries, note the following information:
To display the dashboards provided, you require Adobe Flash Player version 9. Note also the license terms for SAP BusinessObjects.
To create your own dashboards, you require SAP BusinessObjects Dashboards. For more information, see SAP Note 1486885. Take note of the
corresponding license terms.
The dashboards and BEx reports use BI content. BI content contains BW modeling/objects, BEx queries (multidimensional reports), and SAP BusinessObjects
Dashboards. You can access the BI content documentation on SAP Help Portal at http://help.sap.com SAP NetWeaver BI Content and then select the
corresponding release (see the release listed in Component Extension for SAP EHS Management).
Features
This component offers the following functions to enable analytical reporting:
File-Based Reporting
Allows you to export data in various file formats and generate analytical reports in your standard office environment.
Data extraction to BW
Provides a foundation for simplified data extraction in the standard system, and allows you to easily configure analytical reporting to suit your needs.
Process monitoring and analysis
Analytical reports provide an overview of open and closed processes as well as the average time for completing a type of process. You can analyze the
type of process and display processes for the specific type. You can use dashboards or the process monitoring tools in the standard system.
1.1.7.1 File-Based Reporting

This function enables you to extract data from the BOPF business objects in SAP EHS Management and export it to your front-end computer in file formats such
as CSV, Microsoft Excel 2007, or Microsoft Excel 2010. You can use the extracted data later on for performing analytics.
Prerequisites
You have made the settings for file-based reporting in Customizing for SAP EHS Management under
Reporting .
File-Based
You are using a business object node to get the data. This node contains all fields that have to be extracted.
Features
Extraction of BO data in different file formats
File-based reporting allows you to extract data from business objects in SAP EHS Management in a file format you use in your standard office
environment.
Support of foreground or background processing
Depending on your entries in the Customizing activity Define Export Profiles , the export is processed in either the foreground or the background.
E-mail shipment of file-based reports
The generated export file is sent to the user by e-mail. If the size of the generated file is too large, the file itself will be stored in the system for downloading.
Only the link with the download information is included in the e-mail. You can adopt these settings in the Customizing activity Configure General Settings .
Use of template files
As an additional option, it is possible to upload predefined Microsoft Excel template files in the Customizing activity Define Export Profiles into the system.
These templates are than used for generating export files.
Note
You have to save the exported file on your computer before opening it. Otherwise, your file is opened in protected view. If you use pivot tables in your
Microsoft Excel template file, the data refresh function may not work correctly.
For more information about the support of Microsoft Excel Macro-Enabled Workbooks, see SAP Note 1716252
Activities
When you start the generation of an export file, the system performs the following activities depending on the various export possibilities:
Export in a CSV file format
If only one data selection is selected, the exported file is in CSV format.
If several data selections are selected, the exported file is a ZIP archive that includes one CSV file per data selection.
Export in a Microsoft Excel 2007/2010 file format without template file
PUBLIC
Page 27 of 82
If only one data selection is selected, the exported Microsoft Excel file contains one sheet.
If multiple data selections are selected, the exported Microsoft Excel file contains one sheet for each data selection.
If errors occur, the Microsoft Excel file contains a separate sheet for error messages.
Export in a Microsoft Excel 2007/2010 file format with template file
If no sheet exists in the template file with the same technical name as the data selection, a new sheet is created during the export.
If a sheet exists with the same technical name as the data selection, the data is exported into this sheet. The formatting of the sheet and the order of
the columns remains unchanged. Other sheets with, for example, pivot tables or charts for performing analytics, also remain unchanged.
Note
Formulas and functions in your Microsoft Excel template are not updated automatically. You have to start the refresh manually.
If you want to create a template file, proceed as follows:
Define an export profile in the Customizing activity Define Export Profiles without a template file.
Export data using your newly created export profile.
Modify this exported file to your preferences.
Save the changed file and upload it as a template to your export profile.
More Information
For more information about configuring file-based reporting, see Customizing for SAP EHS Management under
Reporting .
File-Based
1.1.7.2 Data Extraction to BW

This function enables you to extract data from the BOPF business objects in SAP EHS Management and transfer it to SAP NetWeaver Business Warehouse
(BW) for use later on reports and dashboards. The function provides a foundation for simplified data extraction in the standard system, and allows you to easily
configure analytical reporting to suit your needs.
The following graphic depicts where the extractor foundation is used:
Extractor Foundation in Extracting to BW
In the source system, the extractor functionality is part of the business object, and the business object contains a node with the fields to be extracted. The
extractor foundation reads the data provided by the node from BOPF. The node and additional data is included in the extractor structure. The SAPI interface of the
DataSource then receives the data from the extractor foundation and transfers it into BW.
Integration
You use the extractor foundation only if you use SAP NetWeaver Business Warehouse (BW) for analytical reporting.
Prerequisites
You are using a BO node to get the data. This node contains all fields that have to be extracted to BW and enables the extractor foundation to use the standard
BOPF API for reading the data and sending it to BW via the SAPI interface of the DataSource. A transient node can be used if the DataSource has to provide data
from multiple BO nodes. In that case, the transient nodes determination reads data from multiple BO nodes.
PUBLIC
Page 28 of 82
Features
Easier Implementation
The BW service API (SAPI) is the interface solution for data transfer to a DataSource in BW and requires that all extractors in the source system implement
specific logic. Since the logic is repeated in each extractor, the extractor foundation implements the logic in a common class that is used by all extractors
and fulfills the SAPI requirements.
Extensible for Customer-Specific Extraction
You can use the extractor foundation in your customer-specific projects. You can adjust and create your own transient node. To get the data for extraction,
you implement a determination on the root node to get the data for the transient node. The extractor foundation then handles reading and transferring the data,
as well as logging errors.
Increased Performance
The extractor foundation supports processing mass amounts of data by allowing the extraction of multiple data records in one step.
More Information
For more information about configuring extractors for BI analytical reporting, see Customizing for SAP EHS Management under
Management Analytical Reporting .
Foundation for EHS
1.1.7.3 DataSources
A DataSource is a set of fields that provide the data for a business unit for data transfer. From a technical perspective, the DataSource is a set of logically-related
fields that are provided to transfer data to SAP NetWeaver BW and the operational data provider in the backend either in a flat structure (extraction structure) or in
multiple flat structures (for hierarchies).
More Information
For more information, search for DataSource, data staging, and Operational Data Provider in the documentation for SAP NetWeaver at http://help.sap.com.
1.1.7.3.1 Workflow Process Definitions

DataSource Transactional Data: 0EHSM_FND_WF_01
You can use this DataSource to extract process definitions from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). You
can process the extracted data by using the DataSource object 0EHF_DS04 shipped with this release.
Technical Data
Application Component
SAP EHS Management (EHS-MGM-FND)
Available as of Release
Component Extension 1.0 for SAP EHS Management
Shipment
SAP NetWeaver 7.0 BI Content Add-On 5 SP 02
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
Yes
Extraction from Archives
No
Verifiable
No
Data Modeling
Delta Update
The delta update used for this DataSource is AIE (After-Images by Extractor) . The deciding field for the update is BW_DELTATIMESTMP.
Fields of Origin for the Extract Structure
Fields in the Extract Structure
Description of the Field in the Extract

Structure
Table of Origin
Field in the Table of Origin
EHSM_COMP
Component of EHS Management
EHFNDC_PROCDEF
EHSM_COMPONENT
PURPOSE
Purpose of EHS Management Process
EHFNDC_PROCDEF
PURPOSE
PROC_VARIANT
Name of Process Variant
EHFNDC_PROCDEF
VARIANT
BW_DELTATIMESTMP
BW Delta Time Stamp
Extractor Logic
PUBLIC
Page 29 of 82
The DataSource is implemented by a function module (extraction method F1). The extractor transfers the component, the purpose, and the variant of all process
templates from the table containing the process definitions EHFNDC_PROCDEF into SAP NetWeaver BW. The data is not aggregated or transformed.
1.1.7.3.2 Workflow Process Instances

You can use this DataSource to extract process data from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). You can
process the extracted data by using the DataSource object 0EHF_DS05 shipped with this release.
Technical Data
Shipment
Content Versions
EHM300
RemoteCube-Capable
No
Delta-Capable
Yes
No
Verifiable
Yes
Data Modeling
Delta Update

Structure
Table of Origin
EHSM_COMP
PURPOSE
PROC_VARIANT
CONF_KEY
NodeID
DATE_CREATED
Field of type DATS
DATE_COMPLETED
Field of type DATS
STATUS
Internal Status of PCO
AGE
Overall Age Of This Item In Number Of

Days
OVERDUE
Number of Overdue Processes/Steps
BW_DELTATIMESTMP
BW Delta Time Stamp
SUBSTANCE_ID
Substance
MATERIAL_ID
Material
CUSTOMER_ID
Customer
SUPPLIER_ID
Supplier
BW_RECORDNUMBER
Record Number
PROD_COMP_ID
Product Component
PARENT_COMP_ID
Parent Component
DUPLICATE
Duplicate Record
REV_STATUS
Revision Status
ACTIVITY
Activity
OBJECT_TYPE
Object Type
Extractor Logic
The DataSource is implemented by a function module (extraction method F1).
Verification of Key Figures
PUBLIC
Page 30 of 82
The process log is checked.
1.1.7.3.3 Workflow Step Definitions

Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
Yes
No
Verifiable
No
Data Modeling
Delta Update

Structure
Table of Origin
EHSM_COMP
PURPOSE
PROC_VARIANT
TEMP_ID
Task ID
NODE_ID
Node Number
THRESHOLD
Threshold of Report-Relevant Steps
BW_DELTATIMESTMP
BW Delta Time Stamp
Extractor Logic
The DataSource is implemented by a function module (extraction method F1). The extractor transfers the component, the purpose, and the variant of the process,
the node ID, and the task ID of the step and the threshold configured for each step into SAP NetWeaver BW. The system extracts only those steps which are
foreground steps or marked as relevant for reporting.
1.1.7.3.4 Workflow Step Instances

Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
Yes
No
Verifiable
Yes
PUBLIC
Page 31 of 82
Data Modeling
Delta Update

Structure
Table of Origin
EHSM_COMP
PURPOSE
PROC_VARIANT
CONF_KEY
NodeID
TEMP_ID
Task ID
NODE_ID
Node Number
WORKITEM_ID
Work item ID
DATE_CREATED
Field of type DATS
DATE_COMPLETED
Field of type DATS
STATUS
Internal Status of PCO
AGE

Days
OVERDUE
Number of Overdue Processes/Steps
BW_DELTATIMESTMP
BW Delta Time Stamp
AGE_PROC

Days
Extractor Logic
The DataSource is implemented by a function module (extraction method F1).
Verification of Key Figures

The step details are checked.
1.1.7.3.5 Workflow Process Definitions - Text Extraction (Full)

DataSource Texts: 0EH_DESCRP_TEXT
You can use this DataSource to extract texts for the workflow process definitions.
Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Data Modeling
Table of Origin
Structure
LANGUAGE
Language Key
EHSM_COMPONENT
PURPOSE
PUBLIC
Page 32 of 82
VARIANT
DESCRIPTION
Description (Long)
1.1.7.3.6 Workflow Reporting - Component Description

DataSource Texts: 0EH_COMP_TEXT
You can use this DataSource to extract descriptions of components for the workflow reporting.
Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Data Modeling

Structure
Table of Origin
LANGUAGE
Language Key
COMPONENT_ID
DESCRIPTION
Description (Long)
1.1.7.3.7 Workflow Reporting - URL Extraction (Full)

DataSource Attributes: 0EH_URL_ATTR
You can use this DataSource to extract the full URL for the workflow reporting.
Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
no
No
Verifiable
No
Data Modeling

Structure
Table of Origin
SERVER
PORT
System ID
PATH_PREFIX

PUBLIC
Page 33 of 82

DataSource Texts: 0EH_DESCRS_TEXT
You can use this DataSource to extract texts for the workflow step definitions.
Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Data Modeling

Structure
Table of Origin
LANGUAGE
Language Key
DESCRIPTION
Description (Long)
TEMP_ID
Task ID
NODE_ID
Node Number
1.1.7.3.9 Texts for Material ID

DataSource Texts: 0EH_MATID_TEXT
You can use this DataSource to extract texts for materials.
Technical Data
Shipment
SAP NetWeaver 7.0 BI Content add-on 6 SP 03
Content Versions
EHM200
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Data Modeling

Structure
Table of Origin
MATNR
Material (Number)
MAKT
SPRAS
Language
MAKT
MAKTX
Description (short)
MAKT
MAKTG
Description (uppercase)
MAKT
Extractor Logic
When there is no short text maintained for the material, the material number is used.
PUBLIC
Page 34 of 82
1.1.7.3.10 Common Objects

As of component extension 3.0 for SAP EHS Management , the DataSources for common objects, such as the locations, are documented in this structure.
1.1.7.3.10.1 Location Master Data

DataSource Attributes: 0EH_LOCATIN_ATTR
You can use this DataSource to extract master data attributes of locations from SAP EHS Management into SAP NetWeaver Business Warehouse (BW). The
DataSource extracts the data from the following nodes of the location business object EHFND_LOCATION:
ROOT
REVISION
You can process the extracted data by using the InfoObject 0EH_LOCATIN. The location business object supports multiple revisions of the same location. Thus,
the master data attributes are time-dependent.
Technical Data
Shipment
SAP NetWeaver 7.0 BI Content add-on 6 SP 03
Content Versions
EHM200
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Prerequisites
You have configured the DataSource in Customizing in the source system under
SAP EHS Management Foundation for EHS Management
Analytical Reporting Configure Extractors .
The BAdI implementation BADI_EHFND_FW_BI_BOPF_OBJ_LIST must be an active default implementation of the BAdI
BADI_EHFND_FW_BI_OBJ_LIST. For more information, see Customizing in the source system under
SAP EHS Management
Foundation for EHS
Management Analytical Reporting BAdI: Determination of Objects to Extract .

The BAdI implementation BADI_EHFND_FW_BI_BOPF_EXTRACT must be an active default implementation of the BAdI
BADI_EHFND_FW_BI_EXTRACTOR. For more information, see Customizing in the source system under
Management
Analytical Reporting
BAdI: Extraction of One Object
SAP EHS Management
Foundation for EHS
Data Modeling

Structure
Table of Origin
ID
ID of the location
COUNTRY
Country of the location
REGION
Region of the location
PLANT
Plant of the location
TYPE
Location Type
DATEFROM
Start date of validity period of record
DATETO
End date of validity period of record
BW_RECORDNUMBER
Serial number of records since one risk can have multiple records
BW_RECORDMODE
Record mode that allows flagging records
for deletion in BW
BW_DELTATIMESTMP
Time stamp for delta load
Extractor Logic
The current extractor logic is implemented as a BOPF determination of the transient node BI_LOCATION of the business object EHFND_LOCATION.
Since you can revise a location and store older revisions of a location, the revision data is extracted as time-dependent master data attributes. The REVISION
node of the location BO contains a field SPLITDATE that specifies the date when the revision of the location started being valid. The value of this field is extracted
PUBLIC
Page 35 of 82
into the field DATEFROM in the extractor structure. The field DATETO of the extractor structure is populated with the value of the SPLITDATE minus one day. You
can process the extracted data by using the InfoObject 0EH_LOCATIN .
1.1.7.3.10.2 Location Hierarchy

DataSource Hierarchy: 0EH_LOCATIN_0001_HIER
You can use this DataSource to extract hierarchy data from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). You can
process the extracted data by using the InfoSource 0EH_LOCATIN shipped with this release.
Technical Data
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Data Modeling

Structure
Table of Origin
OLTPSOURCE
DataSource (OSOA/OSOD)
Extractor Logic
The DataSource is implemented by a function module (extraction method F1). The extractor transfers the location hierarchy (header and the different nodes) into
SAP NetWeaver BW.
1.1.7.3.10.3 Texts for Location

DataSource Texts: 0EH_LOCATIN_TEXT
You can use this DataSource to extract texts for locations.
Technical Data
SAP EHS Management (EHS-MGM-INC)
Shipment
Content Versions
EHSM10
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Data Modeling

Structure
Table of Origin
ID
Business Object ID
DATEFROM
Valid-From Date
DATETO
Valid-To Date
LANGUAGE
Language Key
PUBLIC
Page 36 of 82
TEXT
Location Name Description
1.1.7.3.10.4 Texts for Location Type

DataSource Texts: 0EH_LOCTYPE_TEXT
You can use this DataSource to extract texts for location types from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW).
Technical Data
Shipment
Content Versions
EHM200
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Prerequisites
You have configured location types in the source system in the Customizing activity for SAP EHS Management under
Locations
Specify Location Types .
Data Modeling

Structure
Table of Origin
LANGUAGE
Language
CODE
Location Type
DESCRIPTION
Description (Extra Short) of Location
1.1.7.3.10.5 Texts for Location Authorization Group

DataSource Texts: 0EH_LOCAGRP_TEXT
You can use this DataSource to extract texts for location authorization groups from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP
NetWeaver BW).
Technical Data
Shipment
Content Versions
EHM200
RemoteCube-Capable
No
Delta-Capable
No
No
Verifiable
No
Prerequisites
You have configured location types in the source system in the Customizing activity for SAP EHS Management under
Locations
Specify Authorization Groups .
PUBLIC
Page 37 of 82

Table of Origin
Structure
LANGUAGE
Language
CODE
Authorization Group
DESCRIPTION
Description (Extra Short) of Authorization

Group
1.1.8.1.3 Roles
In SAP EHS Management , you use specific roles in the application to access content. These roles are specific to the two different user interfaces supported by
the application SAP NetWeaver Portal and SAP NetWeaver Business Client. The roles for each of these interfaces are described in the following
documentation:
Business Package (Portal Content)
Roles in SAP NetWeaver Business Client
All roles are provided without any authorizations assigned to them. You must assign authorizations using the authorization objects in the back-end system.
Master Roles
In addition to these roles, two master roles (PFCG roles in the back-end system) are provided for both user interfaces. These roles contain the complete content of
the SAP EHS Management application.
SAP_EHSM_MASTER
This role contains the complete SAP EHS Management content.
SAP_EHSM_MASTER_CLASSIC
This role contains content for SAP EHS Management as part of SAP ERP, which is not covered by the add-on SAP EHS Management .
When creating user-defined roles, we recommend you use each master role as a template and you remove the undesired functions. This ensures that no
configurations (for example, OBN settings) are lost.
1.1.8.1 Business Package (Portal Content)

As of component extension 3.0 for SAP Environment, Health, and Safety Management (SAP EHS Management), the Business Package for EHS Management
is available. The enhanced business package allows you to use the functions provided in incident management, product compliance, risk assessment, and in
the foundation for SAP EHS Management. For more information, see Incident Management, Product Compliance (EHS-MGM-PRC), Risk Assessment, and
Foundation for EHS Management.
Technical Data
Availability
As of component extension 3.0 for SAP EHS Management with SAP enhancement package 5 for SAP ERP 6.0 (minimum
SP stack 05) and SAP enhancement package 2 for SAP NetWeaver 7.0 (minimum SP stack 08).
Data Source
Component extension 3.0 for SAP EHS Management and SAP enhancement package 5 for SAP ERP 6.0
Browser Recommendation
Microsoft Internet Explorer 7

Microsoft Internet Explorer 8
Mozilla Firefox 3.5
Apple Safari 4
For more information about system prerequisites for these components, see the Product Availability Matrix on SAP Service
Marketplace at http://service.sap.com/pam.
Languages Available
SA Arabic
ES Catalan
CS Czech
DE German
EN English
ES Spanish
FI Finnish
FR French
HE Hebrew
HU Hungarian
IT Italian
JA Japanese
KO Korean
NL Dutch
NO Norwegian
PT Portuguese
RU Russian
SK Slovakian
SV Swedish
TR Turkish
ZF Chinese Traditional
ZH Chinese Simplified
Support
EHS-MGM-FND-EP
PUBLIC
Page 38 of 82
Prerequisites
To use the most up-to-date functions delivered for the roles integrated with enhancement package 5 for SAP ERP 6.0, you have activated the EH&S
Continuous Improvement (LOG_EHS_CI2) business function and the Enterprise Extension PLM (EA-PLM switch).
If you want to use SAP BusinessObjects Dashboards and SAP Business Explorer (BEx) reports to analyze aggregated data, you need to order the relevant
SAP BusinessObjects software. For more information, see SAP Note 1486885.
You have all the authorizations required for the back-end system.
You have a portal user that is assigned to a user with the required authorizations.
This business package uses objects from a further business package or packages. These objects are listed in the section Shared Objects in this
Business Package. If you intend to use these objects, you must also implement the relevant business package. For more information, see the relevant
business package documentation.
1.1.8.1.1 Business Package for EHS Management (Enhanced)

Technical Data
Product Version
Component extension 3.0 SP03 for SAP Environment, Health, and Safety
Management (SAP EHS Management) .
Country Relevance
Not valid for:

Spain: If you would like to use this product version in Spain, contact your local SAP
representative.
As of component extension 3.0 SP03 for SAP EHS Management , the Business Package for EHS Management has been enhanced. The roles for risk
assessment and product compliance have been enhanced to include the following new iViews:
iView
Application
Edit Recommendation Criteria for Health Surveillance Protocols
Risk Assessment
Edit Health Surveillance Protocols
Risk Assessment
Display ProdStewNet Confirmation Import Display ProdStewNet Confirmation Import
Product Compliance
The existing functions for incident management, risk assessment, product compliance and foundation are also available in the business package.
For more information about the functionality in SAP EHS Management , see the following documentation:
Foundation for EHS Management (EHS-MGM-FND)
Incident Management (EHS-MGM-INC)
Risk Assessment (EHS-MGM-RAS)
Product Compliance (EHS-MGM-PRC)
1.1.8.1.2 Configuration Information

You use this procedure to make the necessary settings to integrate the Business Package for EHS Management into your SAP NetWeaver Portal.
Prerequisites
You have familiarized yourself with the software components required and the implementation strategy. To do this, see the relevant guides on SAP Service
Marketplace at http://service.sap.com/instguides.
Note
For information about Web browsers, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/pam.
Procedure
1. You set up the system landscape in the SAP NetWeaver Portal (see Setting Up the System Landscape).
2. In the SAP NetWeaver Portal, you assign the portal roles to users. You define the following system aliases for the SAP NetWeaver Portal content:
SAP_ECC_EnvironmentHealthSafety for the SAP EHS Management functions
SAP_R3_EHS for the environment, health, and safety functions based on SAP ERP
You must enter a target system for the entire role for the PFCG roles in the environment, health, and safety processes based on SAP ERP. For more
information, see Role Maintenance in PFCG.
For more information about creating custom roles specifically for SAP EHS Management , see Creating Custom Roles. For general information about
changing standard roles, see Changing Standard Roles.
3. To open iViews delivered with the Business Packages of integrated systems, for example, iViews for a material of Material Management (MM) or for a
functional location of Plant Maintenance (PM), from within the SAP EHS Management application, you must enter a target system for the corresponding
service in the PFCG role. The target systems for integrated systems are also maintained in Customizing for SAP EHS Management under
Foundation
for EHS Management Integration Specify Destinations for Integration .
For more information about entering a target system in the PFCG role, see 5.10 Remote Systems.
For more information about the objects from other Business Packages, see Shared Objects.
PUBLIC
Page 39 of 82
4. You make the settings as described in Setting Up the Universal Worklist.

5. To integrate incident management into your employee self-service center, you follow the procedure described in Adding Incident-Related iViews to the
Employee Self-Service Center.
1.1.8.1.2.1 Adding Incident-Related iViews to the Employee SelfService Center

You can integrate initial incident recording from SAP EHS Management into the Employee Self-Service (ESS) area in the SAP NetWeaver Portal so that you
can record an incident from there. The following information describes how you configure ESS to include initial incident recording.
Procedure
1. In the SAP NetWeaver Portal, choose the Content Administration work center.
2. Choose the Portal Content workset from the structure on the left.
Creating an Incident Reporting iView Using the iView Wizard

1. Choose
New iView
and then select the iView template Create an iView from an existing iView template radio button. Then choose Next .
2. Select the Workset Map iView template and choose Next .
3. Complete the following fields. You can either use the example input below or make your own entries:
Field
Example Input
Name
Incident Reporting
iView ID
IncidentReporting
iView ID Prefix
com.technidata.hss.ess
Choose Next .
4. Review the summary of your iView and then choose Finish .
Creating a new Report Incident iView Using the iView Wizard

1. Choose the iView template Create an iView from an existing iView template radio button and then choose Next .
2. Select the SAP Web Dynpro iView template and choose Next .
Field
Example Input
Name
Report Incident
iView ID
ReportIncident
iView ID Prefix
Choose Next .
4. Select the Web Dynpro platform as Web Dynpro for ABAP and choose Next .
Field
Example Input
System
Q35LNT004
Namespace
SAP
Application Name
EHHSS_INC_REC_GAF
Select Plain HTML as the Web Dynpro Client and choose Next .
6. Review the summary of your iView and then choose Finish .
Creating a New Incident Reporting Page Using the Page Wizard

1. Choose
New Page .
Field
3.
4.
5.
6.
Example Input
Page Name
Incident Reporting
Page ID
IncidentReporting
Page ID Prefix
Description
Offers access to report incidents of different categories. Possible categories are

incident, near miss and safety observation.
Choose Next .
Select Web Dynpro Proxy Page as the page template and choose Next .
Select 1 Column (Full Width) from the Available Layouts and Add to add it to the Selected Layouts . Then choose Next .
Review the summary of your page and then choose Finish . Choose the option to Open the object for editing and choose OK .
Open the page and add the Incident Reporting iView to the page as a delta link.
Creating a New Report Incident Page Using the Page Wizard

1. Choose
New
Page
PUBLIC
Page 40 of 82
Field
Example Input
Page Name
Report Incident
Page ID
ReportIncident
Page ID Prefix
Description
Offers access to report an incident including persons, assets and releases.
Choose Next .
3. Follow steps 3 to 5 above.
4. Open the page and add the Report Incident iView to the page as a delta link.
Creating a New Incident Reporting Workset Using the Workset Wizard

1. Choose
New Workset .
Field
Example Input
Workset Name
Incident Reporting
Workset ID
IncidentReporting
Workset ID Prefix
Description
Offers access to report incidents of different categories. Possible categories are

incident, near miss and safety observation.
Choose Next .
3. Review the summary of the workset and then choose Finish .
4. Open the workset and add the Incident Reporting and Report Incident pages as delta links.
Adding the Incident Reporting Workset to an Existing Employee Self Service Role
Note
The following information provides a sample configuration. If incident recording has been implemented in the customer's ESS, the keys and PCD locations will
be customer specific. You must use the PCD location in the correct context (the complete path).
1. Call transaction SPRO and display the Personnel Management structure.
2. Choose
Personnel Management Employee Self-Service
Resources
and make the following entries:
Component
Server
General Settings
Field
Define Server for
Server
Z_HSS_TEST
Protocol
http
Name and Port
uxai2q35.wdf.sap.corp:50021
Directory Path
Resource 1 (Incident Reporting Page)
Resources
Example Configuration
3. Choose
Personnel Management Employee Self-Service General Settings
Define Resources (Add Entries)
Component
Homepage for Self-Services
Field
sap/bc/webdynpro/sap/ehhss_inc_rec_gaf
Resources
Define Resources
Resource Object Key
Z_HSS_INCREP_PAG
Description
Incident Reporting Page
URL of PCD Page
ROLES://portal_content/Sandbox/C5111368/com.techni
data.hss.ess.roles/com.sap.pct.erp.ess.employee_self_s
ervice/com.sap.pct.erp.ess.employee_self_service/com.t
echnidata.hss.ess.incidentReporting/com.technidata.hss
.ess.incidentReporting
4. Choose
Define Resources (Add Entries)
Component
Resource 2 (Report Incident Page)
Field
Resources
Define Resources
Resource Object Key
Z_HSS_INCREP_SER_INC
Description
Report Incident
Server Definition
Z_HSS_TEST
URL Parameter
sap-client=004&sap-language;=EN
URL of PCD Page
ROLES://portal_content/Sandbox/C5111368/com.techni
data.hss.ess.roles/com.sap.pct.erp.ess.employee_self_s
ervice/com.sap.pct.erp.ess.employee_self_service/com.t
echnidata.hss.ess.incidentReporting/com.technidata.hss
.ess.reportIncident
5. Choose
Services (Add Entries)
Component
General Settings
Field
PUBLIC
Services
Define Services
Define
Page 41 of 82
Service
Service Key
Service Link Text
Report Incident
Type
Web Dynpro ABAP application
Link Resource
Service Description
Report incident including injured persons, damaged

assets and/or releases
6. Choose
Subareas
Assign Services to Subareas (Find Entries)
Component
Field
Assign Service to Subarea
Z_HSS_INCREP
Service Key Short (Table Key)
001
7. Choose
Define Subareas (Add Entries)
Field
Subarea
Z_HSS_INCREP
Subarea Text
Report Incident
Z_HSS_INCREP
Subarea Key
Z_HSS_INCREP
10. Choose
Pages
001
General Settings
Field
Area
Define Areas
Define Areas
Z_HSS_INCREP
Area Link Text
Incident Reporting
Link Type
Web Dynpro Java application
Link Resource
Z_HSS_INCREP_PAG
Area Description Summary
Report Incidents, Near Misses and Safety Observations
Field
Assign Area to Area Group Page
Areas
Area Key

Assign Areas to Area Group Pages (Find Entries)
Component
Assign Subareas to
Position
Component
Subareas
Area Key
9. Choose
(Add Entries)
Define Subareas
Field
Assign Subarea to Area
Subareas
Subarea Key
8. Choose
Areas
Assign Subareas to Areas (Find Entries)
Component
Assign Services to
Subarea Key
Position
Component
Services
Areas
Assign Areas to Area Group
Area Group Key
SAPDEFAULTESSINEIC_ERP2005
Area Key
Z_HSS_INCREP
Position
15
1.1.8.1.2.2 Creating Custom Roles

Procedure
The roles provided with the Business Package for EHS Management contain specific configuration settings, for example, as object-based navigation settings. To
create custom roles without losing the configuration settings, proceed as follows:
1. Create your custom PFCG role.
2. Copy the menu structure from either delivery role SAP_EHSM_MASTER or SAP_EHSM_MASTER_CLASSIC.
3. Generate the authorization profile.
4. Assign the custom role to end users.
For custom portal roles, the following additional steps are required. Either upload the custom role to the SAP NetWeaver Portal using the role upload tool, or create
a custom portal role directly in the SAP NetWeaver Portal using the following procedures.
For custom roles created from role SAP_EHSM_MASTER:
1. Create the custom portal role as new portal role
2. Add the workset SAP_EHSM_MASTER as a delta link.
3. Remove all delta links to the services that you do not want to include in your custom portal role.
4. Assign the custom portal role to end users.
For custom roles created from roles SAP_EHMS_MASTER_CLASSIC:
1.
2.
3.
4.
Create the custom portal role as new role.

Add delta-links to the Product Safety and Stewardship and Health and Safety worksets.
Remove all delta links to the services that you do not want to include in your custom portal role.
Assign the custom portal role to end users.
PUBLIC
Page 42 of 82
Note
All applications for which a user should have authorization must exist in a role and the user must be assigned to that role. The applications cannot be split
over multiple roles. You can use the master roles (SAP_EHSM_MASTER or SAP_EHSM_MASTER_CLASSIC) for SAP EHS Management as a template.
More Information
For more information about configuring roles, see Creating Single Roles.
For more information about configuring role menus, see Creating Role Menus Creating Role Menus.
1.1.8.1.2.3 Setting Up the System Landscape

Procedure
1. Create a Systems folder (if one does not already exist) in the SAP NetWeaver Portal. To do so, proceed as follows:
1. Choose
System Administration System Configuration System Landscape . Position your cursor on Portal Content and use the context
menu (right mouse button) to create the new Systems folder.
2. Create entries for the logical systems listed below in the Systems folder.
Note
If you run more than one of the specified logical systems in a physical system (such as SAP EHS Management and Environment, Health, and Safety
in ERP in one system XYZ in client 000), it is sufficient if you create one entry that you assign all the relevant system aliases to.
Proceed as follows:
1. Create a portal system for each system by using the context menu for the Systems folder (choose
2. Use an SAP system with load balancing as a template.
3. Enter the name of the physical system (such as XYZ/000) as the description and ID.
New
System from Template
).
Make your company-specific settings to the fields under the following property categories:
Connector
Internet Transaction Server (ITS)
The correct ITS path is /sap/bc/gui/sap/its/webgui
Web Application Server (WAS)
4. Assign the specified system aliases.
Software components:
Logical System
SAP EHS Management
System Alias
SAP_ECC_EnvironmentHealthSafety
Physical System
ERP system with SAP EHS Management processes is
EH&S in ERP
SAP_R3_EHS ERP
installed
System with EH&S processes in ERP 6.0 is installed
More Information
For general information about the system landscape for the SAP NetWeaver Portal, see System Landscape.
1.1.8.1.2.4 Setting Up the Universal Worklist

Workflow items of users appear in the default universal worklist in the SAP NetWeaver Portal. For general information about changing configuration settings, see
Universal Worklist Configuration.
Prerequisites
You have installed the Universal Worklist configuration file.
You have installed the business package.
Procedure
The following procedure provides you with information about setting up system connections for the universal worklist:
1. In the SAP NetWeaver Portal, choose
System Administration
Systems Configuration .
2. Create the following system connections:
System alias: SAP_ECC_EnvironmentHealthSafety
Connection type: WebFlowConnector
System Configuration
Universal Worklist and Workflow
Universal Worklist
UWL
Note
If you have already registered a suitable connector to the system that is connected to the system alias, the existing connector is sufficient and you do not
need to register an additional one.
PUBLIC
Page 43 of 82
Leave the Web Dynpro Launch System field blank for all system connections.
1.1.8.1.2.5 Role Assignments for Cross-Role Activities

The delivered roles of SAP EHS Management allow the user to focus on the activities specific to that role and allow access to only that roles iViews. In some
cases, however, the user may need to use the iViews assigned to a different role.
Depending on the client you use, you can set up roles in the following ways to enable cross-role activities:
If you use the SAP NetWeaver Business Client (NWBC), you can assign one or more of the delivered roles to a user as required. You can also create your
own roles.
If you use the portal, you must create a custom role that contains all of the relevant iViews. This role must contain the source iView and the destination iView
if the user accesses an iView from another iView.
The following sections provide information about situations where you perform cross-role activities:
Managing Links and References to Other Data Records

You can reference and link between incident and risk assessment data records in SAP EHS Management.
To access linked risk assessments from an incident, the user needs one of the following role assignments:
Incident manager and safety manager, environmental manager, or industrial hygienist
Safety manager, environmental manager, or industrial hygienist
Custom role with relevant iViews
To access referenced incidents from a risk assessment, the user needs only one of the risk assessment roles (safety manager, environmental manager, or
industrial hygienist).
Evaluating Control Involved in Incidents

The investigation lead can initiate a control evaluation from the incident as part of an investigation. The investigation lead (or a person responsible for this
investigation step) performs the evaluation and can display the related incident and risk assessment data records. To display both data records, the user must
have the relevant iViews in his or her role assignment.
To initiate the control evaluation, perform the investigation step, and display relevant incident and risk assessment data, the user needs one of the following role
assignments:
Incident manager and safety manager, environmental manager, or industrial hygienist
Safety manager, environmental manager, or industrial hygienist
Custom role with relevant iViews
The following table provides example control evaluation activities and the corresponding iViews. The table indicates which activities require a risk assessment
role in addition to the incident manager role.
User
Activity
Relevant iView
Investigation Lead
1. Adds and assigns the investigation step

for evaluating controls to a investigation
Edit Incident (00000033)
Risk Assessment Role Required
step responsible.
2. Opens the investigation step to review
the controls and add comments for the step
responsible.
3. Selects the linked hazard name to review Display Risk Assessment (00000169)
the hazard for the control.

Investigation Step Responsible
4. Opens inbox and selects the evaluation

task.
Inbox (00000048)
5. Chooses the Display Inc. pushbutton
Display Incident (00000034)
from the inbox.

6. Opens the task and evaluates the
controls.
Investigation Step (00000032)
7. Selects the linked location name to view

the location information.
Display Location (00000015)
8. Selects the linked hazard name to review Display Risk Assessment (00000169)
the risk assessment for the hazard.
More Information
For more information about creating custom roles, see Creating Custom Roles.
1.1.8.1.3 Roles
1.1.8.1.3.1 Incident Manager
Role: com.sap.pct.eh.role.IncidentManager
PUBLIC
Page 44 of 82
The Incident Manager role is assigned to the person who manages and maintains the incident record that was initially created by the incident reporter. This person
is responsible for ensuring that all information associated with the incident is properly entered in a timely manner, verified, and approved, and that the record is
closed.
The incident manager is an expert for incident management and is expected to use the solution on a daily basis. The number of incidents processed strongly
depends on the size of the company, the industry, and the number of employees and contractors. Depending on the severity and complexity of an incident, the
corresponding incident record may need to remain open for a certain period until the process is completed. It is therefore possible for the incident manager to
manage more than one incident at the same time.
The incident manager checks and completes the basic information that is already saved in the initial incident record and enters additional data on, for example,
involved persons, assets, damages, or released materials. To provide more detailed background information on specific aspects of an incident, the incident
manager can gather statements from involved persons and attach documents to the incident record. The incident management process can also include workflows
such as notification and approval, along with actions that might avoid further incidents in the future. After completing and approving an incident record, the incident
manager prepares and submits the relevant incident report(s) to the local authorities.
For more information about the individual tasks, see the workset descriptions in this documentation.
Integration
The incident manager checks and completes the basic information that is initially entered by the incident reporter during initial incident recording. To complete the
incident management process, the incident manager has to work in close cooperation with the following people:
Injured person (if applicable)
To gather information that must be included in the incident record and in legal reports
Other involved persons such as witnesses
To gather additional information that must be included in the incident record and in legal reports
Responsible human resources administrator
To gather organizational information and information on the involved persons
Manager of the plant where the incident occurred
This person is the person who is legally responsible
Responsible members of management who must be notified
Configuration
This role uses object-based navigation. For more information, see Object-Based Navigation.

Technical Data
Technical Name
00000002
You can use this work center to access the health and safety worksets.
1.1.8.1.3.5.1.1 Overview
Technical Data
Technical Name
00000003
1.1.8.1.3.5.1.1.1 Work Overview

Technical Data
Technical Name
00000047
You use this workset to display your tasks.
Features
For more information, see the individual iViews.
More Information
For more information, see Process Foundation (EHS-MGM-FND-WF).
1.1.8.1.3.3.1.1.1.1 Inbox
Technical Data
PUBLIC
Page 45 of 82
Technical Name of the iView
00000048
Technical Name of the Application
Web Dynpro Application: IBO_WDA_INBOX (Parameter: WDCONFIGURATIONID=EHHSS_WDAC_POWL_INBOX)
Runtime Technology
ABAP/Web Dynpro
Data Source or Data Store
Data source as specified for the business package
Support
EHS-MGM-FND
Availability
Availability as specified in the business package
Visibility
The iView is invisible in the navigation area.
You can use this iView to display the tasks that are assigned to you in an inbox. The inbox displays the task subject, when the task was sent, and its priority.
You can also see the date by which the task must be completed, the status of the task, who forwarded it to you, and a preview of the task. In the preview, you can
provide additional notes and add attachments to the task preview.
When you choose the task link in your inbox, the system displays the corresponding data record or a screen where you can perform the task. If you want to see
the related incident record associated with the task, you can select the task row and choose Display Inc..
From this iView you can also specify that you are not responsible for the work, resubmit it, or end the resubmission. You can forward the work to someone else, or
assign it to yourself if it is already assigned to another processor. You can also maintain a substitute who will take over your work in the event of planned or
unexpected absences and you can create and activate a rule that assigns tasks to a specified assignee.
This iView displays the tasks in the inbox according to a specified query. You can define and change queries in this iView.
You can export the list of tasks in a spreadsheet format.
Prerequisites
You have all authorizations required in the back-end system.
Configuration
If you want to replace the inbox with the universal worklist (UWL), you must create a customer-specific SAP NetWeaver Portal role that includes this iView. To do
this, perform the following steps:
1.
2.
3.
4.
Copy the role.

Include the Universal Worklist iView in the copied role next to the Inbox iView.
Delete the Inbox iView from the copied role.
To include the standard Services iView, choose Edit for the iView and select Dynamic Navigation in the Display selection box. Then, add the iView to
dynamic navigation.
5. Configure the Universal Worklist iView as the default entry for the folder and to be invisible in navigation areas
6. Set the parameters specific to the universal worklist, for example, View , to have the same values as in the configuration XML file.
For more information about configuring the UWL, see Universal Worklist Configuration.
1.1.8.1.3.3.1.1.2 Incidents
Technical Data
Technical Name
00000022
You can use this workset to manage and maintain incident records. This includes various types of data, corrective actions, witness statements, photographs, and
other documents.
Features
More Information
Incident Management
1.1.8.1.3.1.1.1.2.1 Incident Entry Screen

Technical Data
00000023
Web Dynpro Application: EHHSS_INC_ENTRY
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
PUBLIC
Page 46 of 82
Availability
Availability as specified for the business package
Visibility
You can use this iView to access incident records. You can display a list of the incident records that you used recently and you can search for incident records.
Prerequisites
More Information
Incident Management
1.1.8.1.3.1.1.1.2.2 Incident Search

Technical Data
00000024
Web Dynpro Application: ESH_SEARCH_RESULTS_UI (Parameter:

SCOPE_DDLB=EHHSS_INCIDENT&EMBEDDED=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
Visibility
You can use this iView to search for data records in incident management with SAP NetWeaver Enterprise Search.
Prerequisites
You have implemented the Configure Embedded Search for SAP EHS Management activity in Customizing for SAP EHS Management under
Management General Configuration .
Incident
Configuration
To make SAP NetWeaver Enterprise Search the default entry on the user interface, you must perform the following steps:
1. In the Incident Entry Screen iView in the SAP_EHSM_MASTER workset, set the default entry for the folder property to No .
2. In the Incident Search iView, set the default entry for the folder property to Yes .

Technical Data
00000046
Web Dynpro Application: EHHSS_INC_REC_QAF (Parameters: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about an incident that occurred in your organization, for example:
A description of the incident
People who were injured during the incident
People who witnessed the incident
The initial incident information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.
Integration
PUBLIC
Page 47 of 82
To record more detailed initial information about an incident, you can use the Report Incident iView.
The incident record can be reviewed and completed by an authorized user in the Review and Completion of Incident Records step.
This iView is called via object-based navigation using the method CreateSimple of the business object BPR_INCIDENT. For more information about the
business object, see Incident.
Prerequisites
More Information
Incident Recording

Technical Data
00000045
Web Dynpro Application: EHHSS_INC_REC_GAF_V3 (Parameters: CHANGE_MODE=C&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about an incident in your organization, for example:
Injured people
Witnesses
Releases
Involved assets
Integration
To record less detailed initial information about an incident, you can use the Report Incident (Simplified) iView.
This iView is called via object-based navigation using the method create of the business object BPR_INCIDENT. For more information about the
Prerequisites
Depending on the information you want to record, you have made the relevant settings in Customizing for SAP EHS Management under
Management Incident Recording .
Incident

More Information
Incident Recording
1.1.8.1.3.2.1.1.1.4 Report Near Miss

Technical Data
00000044
Web Dynpro Application: EHHSS_INC_REC_NRM_QAF_V3 (Parameters: CHANGE_MODE=C&sapexplanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
PUBLIC
Page 48 of 82
You can use this iView to record initial information about a near miss that occurred in your organization, for example:
A description of the near miss
People who were nearly injured during the near miss
The circumstances of the near miss
The initial near miss information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.
Integration
Prerequisites
You have specified the relevant near miss groups in Customizing for SAP EHS Management under
Information Specify Near Miss Groups .
Incident Management
Incident Recording
Basic

Configuration
We recommend that you also make the following setting in Customizing for SAP EHS Management under
Information :
Incident Management
Incident Recording
Basic
Specify the relevant risk types to classify the likelihood of the near miss circumstances causing an incident in the future under Specify Estimated Risk
Types.
Specify the relevant location types under Specify Location Types.
More Information
Incident Recording

Technical Data
00000043
Web Dynpro Application: EHHSS_INC_REC_SFO_QAF_V3 (Parameter: CHANGE_MODE=C&sapexplanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about a safety observation in your organization, for example:
A description of the safety observation
The people who were observed
The circumstances of the safety observation
The initial safety observation information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.
Integration
Prerequisites
You have specified the relevant safety observation groups in Customizing for SAP EHS Management under
Basic Information Specify Safety Observation Groups .
Incident Management
Incident Recording

Configuration
Information :
Incident Management
Incident Recording
Basic
PUBLIC
Page 49 of 82
Types.
More Information
Incident Recording
1.1.8.1.3.1.1.1.2.7 Display Progress Log for External

Notifications
Technical Data
00000039
Web Dynpro Application: EHFND_EXT_NOTIF_PROCESS_LOG (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display the progress log for a process. You can see when each process was sent, its status, and who or what performed the
processing. You can also view any comments or attachments for the process step.
This iView also enables you to create a print version of the result list as a PDF document or to export the list in a spreadsheet format.
Integration
From this iView you can display technical information about the task, and also display the workflow log view showing technical details or a graphical
workflow log.
This iView is called via object-based navigation using the method OpenProgressLog of the business object BPR_FNDEXT using the parameters
EXT_NOTIF_CAT={EXT_NOTIF_CAT}, EXT_NOTIF_ID={EXT_NOTIF_ID}, and WORKITEM_ID={WORKITEM_ID}. For more information about the
business object, see Business Objects.
More Information
Integration for Notifications
Process Foundation (EHS-MGM-FND-WF)
1.1.8.1.3.1.1.1.2.8 Notify Task Processor

Technical Data
00000037
Web Dynpro Application: EHFND_TMG_NOTIFY_PROCESSOR_QAF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to send a notification to the person who is responsible for processing a task. You can enter an e-mail text and then send it to the person
responsible.
An e-mail is sent to the person who is responsible for processing the task.
Integration
This iView is called via object-based navigation using the method NotifyProcessor of the business object EH_FND_WFF_OBN using the parameter
SO_GUID={SO_GUID}. For more information about the business object, see Business Objects.
Prerequisites
PUBLIC
Page 50 of 82
1.1.8.1.3.1.1.1.2.9 Display Application Log

Technical Data
00000036
Web Dynpro Application: EHFND_WF_APPL_LOG_OIF (Parameter: CHANGE_MODE=' '&sapexplanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
This iView displays the log messages for the process scheduler, which stores messages in the application log. You see the type of message, the message text,
and the time when message was created.
Integration
This iView is called via object-based navigation using the method Show_Log of the business object BPR_EHFND_APPL_LOG using the parameters
LOG_HDL={LOG_HDL} and LOG_NO={LOG_NO}.
Prerequisites
More Information
Process Foundation (EHS-MGM-FND-WF)

Technical Data
00000035
Web Dynpro Application: EHFND_WFF_DECISION (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to make a decision, for example, to approve that an action has been completed. You access this iView by selecting the link in the
Category column of a decision task in the Edit Incident iView. After you have made the decision in this iView, the system triggers the next step in the process and
displays the Edit Incident iView again. This way, you can make decisions directly in an incident data record. Alternatively, you can access the decision task in
your inbox (Inbox iView).
Integration
This iView is called via object-based navigation using the method OpenProgressLog of the business object EH_FND_WFF_OBN using the method
OpenProcessDecision and parameter ID={ID}. For more information about the business object, see Business Objects.
Prerequisites
The decision step of the process is assigned to you. If you are not the processor, the link in the Category column is inactive.

Technical Data
PUBLIC
Page 51 of 82
00000034
Web Dynpro Application: EHHSS_INC_REC_OIF_V3 (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
Visibility
You can use this iView to display incident records. For example, the incident record can contain the following information:
Injured people
Witnesses
Releases
Involved assets
Investigation details
Risk matrix information
Financial information
Forms, supporting documents, and associated actions and notifications.
For more information, see Review and Completion of Incident Records.
Integration
This iView is called via object-based navigation using the method Display of the business object BPR_INCIDENT using the parameter KEY={Key}. For more
information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.2.12 Edit Incident

Technical Data
00000033
Web Dynpro Application: EHHSS_INC_REC_OIF_V3 (CHANGE_MODE=U&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to edit incident records. For example, the incident record can contain the following information:
Injured people
Witnesses
Releases
Involved assets
Integration
This iView is called via object-based navigation using the method Edit of the business object BPR_INCIDENT using the parameter KEY={Key}. For more
Prerequisites
PUBLIC
Page 52 of 82
1.1.8.1.3.1.1.1.2.13 Investigate Step

Technical Data
00000032
Web Dynpro Application: EHHSS_UI_INC_QAF_INV_STEP (Parameter: CHANGE_MODE=U&sapexplanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
Visibility
You can use this iView to process an online investigation step.

For more information, see Investigation.
Integration
This iView is called via object-based navigation using the method InvestigateStep of the business object BPR_INCIDENT using the parameter
KEY={Key}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.2.14 Take Over Inquiry Response

Technical Data
00000031
WebDynpro Application: EHHSS_INC_REC_ITO_QAF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
Visibility
You can use this iView to review the data that the recipient of an inquiry has provided offline on the inquiry form. The data is displayed in a table listing the
changes that were made. You can decide whether or not to keep these changes. Keeping them transfers the additional information into the incident record. With this
iView you can display the data of the inquiry recipient and injured people using the links provided.
You use the checkboxes to choose whether or not to keep the changes that were made to the data. Choose Submit to integrate the changes in the record.
This iView allows you to display the form that the recipient of the inquiry has completed. You can display the relevant form using the link provided.
Integration
This iView is called via object-based navigation using the method TakeOverInquiry of the business object BPR_INCIDENT using the method and the
parameters WDCONFIGURATIONID={WDCONFIGURATIONID} and PCBO_KEY={PCBO_KEY}. For more information about the business object, see Incident.
Prerequisites
The inquiry recipient has completed and returned the inquiry form.
More Information
Inquiries
1.1.8.1.3.1.1.1.2.15 Display Generic Process Setup

PUBLIC
Page 53 of 82
Technical Data
00000030
Web Dynpro Application: EHFND_PSE_OIF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display information about a recurring task. You can see when the task is scheduled, how often the task recurs, and how long the task
should run for. You can also see a log of the processes that were started and the log messages from the process scheduler.
Integration
This iView is called via object-based navigation using the method Display of the business object BPR_PROC_SETUP using the parameter KEY={Key}. For
more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.2.16 Edit Generic Process Setup

Technical Data
00000029
Web Dynpro Application: EHFND_PSE_OIF (Parameter: sap-explanation=X&change_mode=D)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to edit information about a recurring task.
Integration
This iView is called via object-based navigation using the method Edit of the business object BPR_PROC_SETUP using the parameter KEY={Key}. For more
Prerequisites
1.1.8.1.3.1.1.1.2.17 Display Change Documents

Technical Data
00000038
Web Dynpro Application: EHFNDWDC_CH_DOC_SEARCH (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display change documents. You can specify a date range and/or a user and then search for the relevant change documents. The result
list displays the following:
PUBLIC
Page 54 of 82
Date and time of the changes

Type of change that was made
Node name
Old and new values
Field description
User who made the changes
You can also view additional details about the change by clicking the link in the Action column.
This iView is called via object-based navigation using the method Display of the business object BPR_FND_CD using the parameters
OBJECT_ID={OBJECT_ID} and OBJECT_NAME={OBJECT_NAME}.
Prerequisites
1.1.8.1.3.1.1.1.2.18 Create Generic Process Setup

Technical Data
00000027
Web Dynpro Application: EHFND_PSE_OIF (Parameter: CHANGE_MODE=C&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to create a recurring task. You can define when the task is scheduled, how often the task recurs, and how long the task should run for.
Integration
This iView is called via object-based navigation using the method Create of the business object BPR_PROC_SETUP using the parameters
COMP={Component} and PURPOSE={Purpose}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.2.19 Change Assignee

Technical Data
00000026
Web Dynpro Application: EHFND_PCBO_CHANGE_ASSIGNEE (Parameter:

WDCONFIGURATIONID=EHFND_PCBO_CHANGE_ASSIGNEE_QAF&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You use this iView to change the person who should implement an action. It displays the relevant action including its category, type, and a description. You also
see the person to whom the action is currently assigned, and you can specify the new assignee who should implement the action.
Integration
This iView is called via object-based navigation using the method ChangeAssignee of the business object BPR_FNDACT using the parameter
INSTANCEID={instanceID}&OBJECTTYPE={ObjectType}. For more information about the business object, see Business Objects.
Prerequisites
PUBLIC
Page 55 of 82

1.1.8.1.3.1.1.1.2.20 Assign Absence to Incident

Technical Data
00000053
WebDynpro Application: EHHSS_INC_ASSIGN_INC_ABSENCE (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
Visibility
You can use this iView to assign an absence that has been created for a person in Personnel Time Management (PT) to an incident during which this person
was injured.
This iView is called when report R_EHHSS_CHECK_HCM_ABS_CHANGED finds absences that have been changed in PT.
In this iView, you can:
Assign the absence to an incident that has already been recorded
Create a new incident record to which you want to assign the absence
Ignore the absence and cancel the incident assignment
Integration
The relevant absence must be created for the injured person by a HR manager in the Personnel Time Management component.
This iView is called via object-based navigation using the method AbsenceAssign of the business object BPR_INCIDENT using the parameter
Key={Key}. For more information about the business object, see Incident.
Prerequisites
The following prerequisites must be met:
You are assigned to the incident manager role.
You have activated PT integration in Customizing for SAP EHS Management under
Incident Management Integration Human Resources Integration
.
You have executed report R_EHHSS_CHECK_HCM_ABS_CHANGED to find absences that have been changed in PT. For more information, see the report
documentation.
More Information
HR Integration for Absence Assignment
1.1.8.1.3.1.1.1.2.21 Display Person Details

Technical Data
00000038
Web Dynpro Application: EHFND_UI_COMN_PER_DETAIL (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display details about a person, such as the gender, date of birth, and address, as well as that persons communication details
(telephone number, e-mail address, and so on). If an e-mail address has been entered, you can use the link to send an e-mail to the person.
This iView is called via object-based navigation using the method DisplayPersonDetails of the business object BPR_FND_PD using the parameters
PARTY_ID={PARTY_ID} and EMAIL={EMAIL}.
Prerequisites
PUBLIC
Page 56 of 82
More Information
Integration for Person Information
1.1.8.1.3.1.1.1.2.22 Display PM Notification

Technical Data
00000254
Web Dynpro Application: EAMS_WDA_NTF_OIF
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-INT
Availability
Visibility
You can use this iView to display details about PM notifications. Details can include the following information:
General data
Location data
Organization data
Malfunction data
Task data
Integration
This iView is called via object-based navigation using the method Display of the business object eam_notification using the parameter
FRW_DATA_HANDLE={FRW_DATA_HANDLE}&QMNUM={QMNUM}.
1.1.8.1.3.1.1.1.3 Incident Reports

Technical Data
Technical Name
00000018
You can use this workset to display incident reports.
Features
More Information
For more information about incident reporting, see Incident Reporting.
1.1.8.1.3.1.1.1.3.1 Review Incident Summary Reports

Technical Data
00000019
Web Dynpro Application: POWL (Parameter: WDCONFIGURATIONID=EHHSS_IRT_ISR_POWL_UI_APPL)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC-REP
Availability
Visibility
This iView is not visible in the Incident Manager role.
You can use this iView to display all of the summary reports that have been created. The report type and the file name is displayed, and you can use the links
provided to display the relevant reports in a PDF format. You can also see the relevant plant, location, and organizational unit, as well as the report dates. You can
also export the list of reports in a spreadsheet for further processing.
You can use the links provided to change the current query or to define a new query.
PUBLIC
Page 57 of 82
Integration
From this iView you can create a summary report or display and generate a report.
Prerequisites
Configuration
You can personalize the iView by deleting and/or renaming queries, adding and removing queries to those that are available, or by changing the position of the
active queries in the list. You can add a category to the queries or remove a category from them. You can specify whether a query is the default query and change
the category description.
You can also personalize the layout of the report summary, displaying it either as a tab strip or a link matrix. You can also choose whether or not to enhance the
query text with category information.
More Information
Incident Reporting
1.1.8.1.3.1.1.1.3.2 Change Parameters for Sending Reports

Technical Data
00000063
Web Dynpro Application: EHHSS_INC_REP_CH_SEND_PARAMS (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC-REP
Availability
Visibility
You can use this iView to view and change the settings for sending a report. You can review the recipient, choose whether to send the report by fax or e-mail, and
also change the recipients e-mail address and fax number.
Integration
This iView is called via object-based navigation using the method ChangeReportSendingParams of the business object bpr_rpt_inc with parameter
Key={Key}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.3.3 Display/Edit Incident Summary Report

Technical Data
00000020
Web Dynpro Application: EHHSS_RPT_OIF_V3 (Parameter:

WDCONFIGURATIONID=EHHSS_INC_RPT_OIF_V3&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC-REP
Availability
Visibility
You can use this iView to display and edit an incident summary report. You specify the dates for the report, any additional criteria that is required such as the
plant ID and location, and also select which report you want to create. You can then use the relevant buttons to create the report, either in the foreground or in the
background. You can also check the report and display any report generation messages that are created. You can also use this iView to display the component
PUBLIC
Page 58 of 82
(report) name as a PDF file.
Integration
This iView is called via object-based navigation using the method Display of the business object bpr_rpt_inc with the parameters KEY={Key} and
CHANGE_MODE={U}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.3.4 Create Incident Report

Technical Data
00000020
Web Dynpro Application: EHHSS_RPT_OIF_V3 (Parameter:

CHANGE_MODE=C&WDCONFIGURATIONID=EHHSS_INC_RPT_OIF_V3&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC-REP
Availability
Visibility
You can use this iView to create an incident summary report. You specify the dates for the report, any additional criteria that is required such as the plant ID and
location, and also select which report you want to create. You can then use the relevant buttons to create the report, either in the foreground or in the background.
You can also check the report and display any report generation messages that are created. You can also use this iView to display the component (report) name
as a PDF file.
Integration
This iView is called via object-based navigation using the method create of the business object bpr_rpt_inc. For more information about the business
object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.3.5 Change Incident Report

Technical Data
00000041
Web Dynpro Application: EHHSS_UI_REC_OIF_V3 (Parameter: CHANGE_MODE=U&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC-REP
Availability
Visibility
You can use this iView to change an existing incident report. You can change:
Basic information about the report such as where and when it occurred
The people who were involved in the incident (for example, witnesses, the reporting person, or vehicle driver) and their information, any injuries or illnesses,
and treatment that they received as a result of the incident.
Information about any assets that were involved in the incident.
Information about any releases into the air, ground, or water as a result of the incident and cleanup responses to this.
The estimated total expenses and income incurred by the incident.
The risk matrix information of the areas affected by the incident, the severity, and the likelihood of them reoccurring.
The investigation into the incident and its related documents and tasks.
The report forms that are required for the reporting the incident to authorities.
Details of any tasks that are related to the incident processing, such as the task schedule.
You can also use this iView to check the contents of the record, change the group or regulations that apply to the incident, manage links, and set the status of the
PUBLIC
Page 59 of 82
record.
Integration
This iView is called via object-based navigation using the method ChangeReport of the business object BPR_INCIDENT with the key KEY={Key},
IS_REPORT={IS_REPORT}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.3.6 Generate Incident Report

Technical Data
00000071
Web Dynpro Application: EHHSS_UI_REC_OIF_V3 (Parameter: CHANGE_MODE=U&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC-REP
Availability
Visibility
You can use this iView to generate reports. Depending on which report you want to generate, you can specify:
Report parameters such as the report language and country
Sender information such as the sender ID and insurance number
The recipients address
You can then send the report to the recipient by fax or e-mail, or you can print out the report and ship it manually.
Integration
This iView is called via object-based navigation using the method RegenerateReport of the business object BPR_INCIDENT with the parameters
KEY={Key}, IS_REPORT={IS_REPORT} and REGENERATE={regenerate}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.1.1.1.4 Locations
Technical Data
Technical Name
00000008
You can use this workset to browse locations and set up all locations in the company.
Features
More Information
For more information about locations in SAP EHS Management, see Locations.
1.1.8.1.3.1.1.1.4.1 Explore Locations

Technical Data
00000009
Web Dynpro: EHFND_UI_LOC_ENTRY (Parameter: WDCONFIGURATIONID=EHFND_UI_LOC_ENTRY&sapexplanation=X)
PUBLIC
Page 60 of 82
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Visibility
This service is invisible in the navigation area.
You can use this iView to display the locations that exist in your system. The iView has four tabs:
Recent Locations
Displays the locations that were recently created.
Structure View
Displays either the location structure or the organizational structure.
Search
Enables you to search for a specific location and then to display information about it.
Favorites
Displays any locations that you added to your favorites.
Prerequisites
You have created a location manually or you have imported technical objects from the Plant Maintenance component as locations.
More Information
Locations
1.1.8.1.3.1.1.1.4.2 Create Location

Technical Data
00000011
Web Dynpro Application: EHFND_UI_LOCATION_OIF (Parameter: CHANGE_MODE=C&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Visibility
You can use this iView to create organizational information about a location, for example, the plant or company code that the location is assigned to or the address
of the location.
You can use this iView to link the location to a technical object in the Plant Maintenance component, thereby avoiding the need to enter duplicate data. You can
also remove the PM link if necessary.
The iView also enables you to set the locations status, to create a revision for the location that records any changes that were made to its attributes, or to delete a
location.
If the location is linked to a PM technical object, you also see the Partners tab.
Integration
You can also use the iView to display the position of the location on a map in the side panel. If a technical object has been linked to the location, you can
use the Equipment ID link to display detailed information about that technical object from PM.
This iView is called via object-based navigation using the method Create of the business object BPR_LOCATION_OBJECT. For more information about
the business object, see Business Objects.
Prerequisites
Locations exist in your system.
Configuration
For more information about configuring the side panel to display a map, see Customizing for SAP EHS Management under
Locations
Configure Integration of Map (EHFND_LOC_MAP) .

PUBLIC
Page 61 of 82

Technical Data
00000012
Web Dynpro Application: EHFND_UI_LHR_OIF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Availability
Visibility
You can use this iView to manage the location structure. You can insert a new location into the structure, or remove an existing one from it. You can also cut a
location from its existing position in the structure and paste it into a new one. You can also use this iView to create a revision of a location.
Integration
You can import technical objects from Plant Maintenance (PM) as locations into SAP EHS Management.
Prerequisites
1.1.8.1.3.1.1.1.4.4 Import from PM

Technical Data
00000013
Web Dynpro Application: EHFND_LOC_EAMIMP_GAF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
You can use this iView to import technical objects as locations from the Plant Maintenance component into SAP EHS Management. The iView has five steps:
1. You can search for the technical objects that you want to import as locations.
2. You then select the technical objects to be imported and as which type of location they should be imported. You can assign a location type to all technical
objects, or else you can assign separate location types to each technical object.
3. You can choose the position in the structure below which you want to import the technical objects.
4. You can review your selection before you import the technical objects.
5. The system confirms your changes.
Integration
The iView displays data about the technical objects from Plant Maintenance.
This iView is called via object-based navigation using the method ImportEAM of the business object BPR_LOCATION_OBJECT. For more information about the
Prerequisites
Technical objects exist in Plant Maintenance.
More Information
Importing Locations from PM
1.1.8.1.3.1.1.1.4.5 Change Attributes

Technical Data
00000014
PUBLIC
Page 62 of 82
Web Dynpro Application: EHFND_LOC_BULKCHG_GAF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
You can use the iView to update multiple location attributes in one operation, thereby saving time and administrative effort. You can make changes to a location
and all of its subordinate locations, if you require. The iView has four steps. In the first step, you define which changes you want to make to multiple locations, and
when you want to make them. In the second step, you select the locations that you want to change. In the third step you can review your changes before you make
them, while the fourth step confirms your changes.
Integration
The iView displays data about the technical objects from Plant Maintenance.
This iView is called via object-based navigation using the method MassChange of the business object BPR_LOCATION_OBJECT. For more information about the
Prerequisites
Locations exist in your system, either because you have created them manually or because you have imported them from Plant Maintenance.
Example
You know that three locations will be assigned to a different plant from tomorrow and want to change the assignment accordingly. You specify tomorrows date as
the key date and select the new plant ID. In the second step in the iView, you select the locations (and their subordinate locations, if required) that should have the
new plant ID. You then review your selection, the attributes are changed, and a confirmation message appears. From this iView, you can also follow the link to
change additional attributes.
More Information
Locations
1.1.8.1.3.1.1.1.4.6 Display Location

Technical Data
00000015
Web Dynpro Application: EHFND_UI_LOCATION_OIF (Parameters: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Visibility
You can use this iView to display organizational information about a location, for example, the plant or company code that the location is assigned to or the address
of the location.
Integration
You can also use the iView to display the position of the location on a map in the side panel.
This iView is called via object-based navigation using the method Display of the business object BPR_LOCATION_OBJECT with parameter KEY={Key}.
Prerequisites
More Information
PUBLIC
Page 63 of 82
Locations
1.1.8.1.3.1.1.1.4.7 Edit Location

Technical Data
00000077
Web Dynpro Application: EHFND_UI_LOCATION_OIF
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Visibility
You can use this iView to edit organizational information about a location such as the plant or company code to which it is assigned or the address of the location.
You can use this iView to link the location to a technical object in the Plant Maintenance (PM) component, thereby avoiding the need to enter duplicate data. You
can also remove the PM link if necessary.
The iView also enables you to change the locations status, to create a revision for the location which records any changes that were made to its attributes, or to
delete a location.
Integration
You can also use the iView to display the position of the location on a map in the side panel.
You can link a technical object in PM to the location using the Establish PM Link button and selecting the existing technical object you want to link to. When this
operation is complete, you can use the Equipment ID link to display detailed information about that technical object from PM.
This iView is called via object-based navigation using the method Edit of the business object BPR_LOCATION_OBJECT with parameter KEY={Key}.
Prerequisites
More Information
Locations
1.1.8.1.3.1.1.1.4.8 Display Location Structure

Technical Data
00000017
Web Dynpro Application: EHFND_UI_LHR_OIF (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Visibility
You can use this iView to display the location structure. You can see the location name, its type, status and the technical name that is linked to it. You can also
open the location to display more information.
You can expand the locations to display their subordinate locations, if any exist.
Integration
This iView is called via object-based navigation using the method Display of the business object BPR_LOCATION_HRCHY. For more information about the
Prerequisites
PUBLIC
Page 64 of 82
More Information
Locations
1.1.8.1.3.1.1.1.4.9 Edit Location Structure

Technical Data
00000078
Web Dynpro Application: EHFND_UI_LHR_OIF (Parameter: sap-explanation=X&change_mode=U)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND-LOC
Visibility
You can use this iView to edit the location structure. You can insert a new location into the structure, or remove an existing one from it. You can also cut a location
from its existing position in the structure and paste it into a new one. With this iView you can also create a revision of a location.
Integration
This iView is called via object-based navigation using the method Edit of the business object BPR_LOCATION_HRCHY. For more information about the business
Prerequisites
More Information
Locations
1.1.8.1.3.1.1.1.4.10 Display Where-Used List

Technical Data
00000052
Web Dynpro Application: EHFND_UI_COMN_WHERE_USED_LIST (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display the other business objects that use this location, for example, the incident is displayed in the where-used list if an it includes
this location and you can navigate directly from there to the incident.
Integration
This iView allows you to display detailed information about existing incidents that use the selected location.
This iView is called via object-based navigation using the method display of the business object BPR_FND_UL using the parameters
OBJECT_ID={OBJECT_ID} and OBJECT_NAME={OBJECT_NAME}.
Prerequisites
1.1.8.1.3.1.1.1.5 Tasks
PUBLIC
Page 65 of 82
1.1.8.1.3.1.1.1.5 Tasks
Technical Data
Technical Name
00000006
You can use this workset to display tasks.
Features
1.1.8.1.3.1.1.1.5.1 Display HSS Tasks

Technical Data
00000007
Web Dynpro Application: POWL (Parameters: WDCONFIGURATIONID=EHHSS_POWL_TASK_MGMT)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to query and display tasks of the HSS component. For more information, see Task Management.
Prerequisites
Configuration
You can personalize the iView by deleting or renaming queries, by adding and removing queries to those that are available, or by changing the position of the
active queries in the list. You can add a category to the queries or remove a category from them. You can specify whether a query is the default query and change
the category description.
1.1.8.1.3.1.1.1.5.2 Forward Task to Another Processor

Technical Data
00000140
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
The iView is not visible in the Tasks workset.
You can use this iView to forward a task to another processor.
Integration
This iView is called via object-based navigation using the method ForwardTask of the business object EH_FND_WFF_OBN using the parameter
SO_GUID={SO_GUID}. For more information about the business object, see Business Objects.
Prerequisites
A task has been created and assigned to your user.
1.1.8.1.3.1.1.1.5.3 Process Details

PUBLIC
Page 66 of 82
Technical Data
00000040
Web Dynpro Application: EHFND_WFF_PROGRESS_LOG (Parameter: sapexplanation=X&change_mode=U)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display the progress log for a process. You can see when each process was sent, its status, and who or what performed the
processing. You can also view any comments or attachments for the process step.
This iView also enables you to create a print version of the result list as a PDF document or to export the list in a spreadsheet format.
Integration
From this iView, you can display technical information about the task, and also display the workflow log view showing technical details or a graphical
workflow log.
This iView is called via object-based navigation using the method OpenProgressLog of the business object EH_FND_WFF_OBN using the parameter
WORKITEM_ID={WORKITEM_ID}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.4.1.1.1 Processes
Technical Data
Technical Name
00000082
You can use this workset to monitor the processes in your company.
Features
More Information
For more information about processes in SAP EHS Management, see Process Foundation (EHS-MGM-FND-WF).
1.1.8.1.3.4.1.1.1.11 EHS Management Task (Technical

Information)
Technical Data
00000094
Runtime Technology
Remote IAC iView on ITS

Transaction: EHFND_WFF_WI_INF
Support
EHS-MGM-FND
Availability
You can use this iView to display information about a specific task and the corresponding process instance, if applicable.
A transaction in the back-end system is called when you access this iView.
Integration
This iView is called via object-based navigation using the method OpenWorkitemInfo of the business object EH_FND_WFF_OBN using the parameter
p_wiid={ID}. For more information about the business object, see Business Objects.
PUBLIC
Page 67 of 82
Prerequisites

Technical Data
00000093
Runtime Technology

Transaction: EHFND_WFF_GRAPH_WFLG
Support
EHS-MGM-FND
Availability
You can use this iView to open the graphical workflow log for a given workflow instance or task ID. The iView displays the progress of a workflow instance. You
can see the original workflow template and an overlay of the actual route that the workflow took.
Integration
This iView is called via object-based navigation using the method OpenGraphicalWorkflowLog of the business object EH_FND_WFF_OBN using the
parameter p_wiid={ID}. For more information about the business object, see Business Objects.
Prerequisites

Technical Data
00000092
Runtime Technology

Transaction: EHFND_WFF_TECH_WFLOG
Support
EHS-MGM-FND
Availability
You can use this iView to display the technical workflow log for a given task ID. The technical workflow log displays technical information about a workflow
instance. The only parameter you can select is the task ID. This ID can either be the ID of a workflow instance, or the ID of a task. If the ID of a task is passed,
the iView displays the corresponding workflow instance.
Integration
This iView is called via object-based navigation using the method OpenTechnicalWorkflowLog of the business object EH_FND_WFF_OBN using the
Prerequisites
1.1.8.1.3.4.1.1.1.12 Open Comment

Technical Data
00000153
Runtime Technology
ABAP/Web Dynpro
PUBLIC
Page 68 of 82
Support
EHS-MGM-FND
Availability
You can use this iView to display the comment.
Integration
This iView is called via object-based navigation using the method OpenComment of the business object EH_FND_WFF_OBN. For more information about the
1.1.8.1.3.2 Incident Reporter

Role: com.sap.pct.eh.role.IncidentReporter
The Incident Reporter role is assigned to the person who initially reports an incident. This can be any person with access to the SAP NetWeaver Portal or SAP
NetWeaver Business Client, regardless of their role, position, or task within an organization. For example:
An internal employee
An external contractor
A vendor
A customer
This person is not expected to use the solution on a regular basis.
The incident reporter enters the basic information about an incident in a guided activity in the SAP NetWeaver Business Client or SAP Enterprise Portal, or in a
form. The level of detail can vary depending on the incident reporter's position in the company, their level of experience, and the company business process. The
incident reporter mainly enters the information as free text. To give additional information on certain aspects of an incident, the incident reporter can add
attachments such as photographs, forms, or protocols.
Integration
When the incident reporting process is completed, the data is sent to the incident manager to be further edited and structured.

Technical Data
Technical Name
00000002
1.1.8.1.3.5.1.1 Overview
Technical Data
Technical Name
00000003
1.1.8.1.3.3.1.1.2 Incidents
Technical Data
Technical Name
00000022
other documents.
Features
More Information
Incident Management
1.1.8.1.3.2.1.1.1.1 Workset Map

PUBLIC
Page 69 of 82
Technical Data
com.sap.pct.eh.iview.txTDAGCPW00
Runtime Technology
ABAP/Web Dynpro
SAP ERP
Support
EHS, EHS-MGM
Availability
You can use this iView to display the workset map.
Prerequisites

Technical Data
00000046
Web Dynpro Application: EHHSS_INC_REC_QAF (Parameters: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about an incident that occurred in your organization, for example:
People who were injured during the incident
People who witnessed the incident
Integration
To record more detailed initial information about an incident, you can use the Report Incident iView.
This iView is called via object-based navigation using the method CreateSimple of the business object BPR_INCIDENT. For more information about the
Prerequisites
More Information
Incident Recording

Technical Data
00000045
Web Dynpro Application: EHHSS_INC_REC_GAF_V3 (Parameters: CHANGE_MODE=C&sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about an incident in your organization, for example:
PUBLIC
Page 70 of 82
Injured people
Witnesses
Releases
Involved assets
Integration
To record less detailed initial information about an incident, you can use the Report Incident (Simplified) iView.
This iView is called via object-based navigation using the method create of the business object BPR_INCIDENT. For more information about the
Prerequisites
Depending on the information you want to record, you have made the relevant settings in Customizing for SAP EHS Management under
Management Incident Recording .
Incident

More Information
Incident Recording
1.1.8.1.3.2.1.1.1.4 Report Near Miss

Technical Data
00000044
Web Dynpro Application: EHHSS_INC_REC_NRM_QAF_V3 (Parameters: CHANGE_MODE=C&sapexplanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about a near miss that occurred in your organization, for example:
A description of the near miss
People who were nearly injured during the near miss
The circumstances of the near miss
The initial near miss information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.
Integration
Prerequisites
You have specified the relevant near miss groups in Customizing for SAP EHS Management under
Information Specify Near Miss Groups .
Incident Management
Incident Recording
Basic

Configuration
Information :
Incident Management
Incident Recording
Basic
Types.
More Information
PUBLIC
Page 71 of 82
Incident Recording

Technical Data
00000043
Web Dynpro Application: EHHSS_INC_REC_SFO_QAF_V3 (Parameter: CHANGE_MODE=C&sapexplanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
You can use this iView to record initial information about a safety observation in your organization, for example:
A description of the safety observation
The people who were observed
The circumstances of the safety observation
The initial safety observation information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.
Integration
Prerequisites
You have specified the relevant safety observation groups in Customizing for SAP EHS Management under
Basic Information Specify Safety Observation Groups .
Incident Management
Incident Recording

Configuration
Information :
Incident Management
Incident Recording
Basic
Types.
More Information
Incident Recording
1.1.8.1.3.3 Notification Recipient

Role: com.sap.pct.eh.roles.IncidentNotified
The Notification Recipient role is assigned to the person who is informed if an incident results in a fatality. This person does not have to be involved in the normal
incident management process, but they must be informed if a fatality occurs, for example, the CEO.
This person is not expected to use the solution on a regular basis.

Technical Data
Technical Name
00000002
1.1.8.1.3.5.1.1 Overview
Technical Data
PUBLIC
Page 72 of 82
Technical Name
00000003
1.1.8.1.3.5.1.1.1 Work Overview

Technical Data
Technical Name
00000047
Features
More Information
1.1.8.1.3.3.1.1.1.1 Inbox
Technical Data
00000048
Web Dynpro Application: IBO_WDA_INBOX (Parameter: WDCONFIGURATIONID=EHHSS_WDAC_POWL_INBOX)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display the tasks that are assigned to you in an inbox. The inbox displays the task subject, when the task was sent, and its priority.
You can also see the date by which the task must be completed, the status of the task, who forwarded it to you, and a preview of the task. In the preview, you can
provide additional notes and add attachments to the task preview.
When you choose the task link in your inbox, the system displays the corresponding data record or a screen where you can perform the task. If you want to see
the related incident record associated with the task, you can select the task row and choose Display Inc..
From this iView you can also specify that you are not responsible for the work, resubmit it, or end the resubmission. You can forward the work to someone else, or
assign it to yourself if it is already assigned to another processor. You can also maintain a substitute who will take over your work in the event of planned or
unexpected absences and you can create and activate a rule that assigns tasks to a specified assignee.
This iView displays the tasks in the inbox according to a specified query. You can define and change queries in this iView.
You can export the list of tasks in a spreadsheet format.
Prerequisites
Configuration
If you want to replace the inbox with the universal worklist (UWL), you must create a customer-specific SAP NetWeaver Portal role that includes this iView. To do
this, perform the following steps:
1.
2.
3.
4.
Copy the role.

Include the Universal Worklist iView in the copied role next to the Inbox iView.
Delete the Inbox iView from the copied role.
To include the standard Services iView, choose Edit for the iView and select Dynamic Navigation in the Display selection box. Then, add the iView to
dynamic navigation.
5. Configure the Universal Worklist iView as the default entry for the folder and to be invisible in navigation areas
6. Set the parameters specific to the universal worklist, for example, View , to have the same values as in the configuration XML file.
For more information about configuring the UWL, see Universal Worklist Configuration.
1.1.8.1.3.3.1.1.2 Incidents
Technical Data
Technical Name
00000022
PUBLIC
Page 73 of 82
other documents.
Features
More Information
Incident Management

Technical Data
00000035
Web Dynpro Application: EHFND_WFF_DECISION (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to make a decision, for example, to approve that an action has been completed. You access this iView by selecting the link in the
Category column of a decision task in the Edit Incident iView. After you have made the decision in this iView, the system triggers the next step in the process and
displays the Edit Incident iView again. This way, you can make decisions directly in an incident data record. Alternatively, you can access the decision task in
your inbox (Inbox iView).
Integration
This iView is called via object-based navigation using the method OpenProgressLog of the business object EH_FND_WFF_OBN using the method
OpenProcessDecision and parameter ID={ID}. For more information about the business object, see Business Objects.
Prerequisites
The decision step of the process is assigned to you. If you are not the processor, the link in the Category column is inactive.

Technical Data
00000034
Web Dynpro Application: EHHSS_INC_REC_OIF_V3 (Parameter: sap-explanation=X)
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-INC
Availability
Visibility
You can use this iView to display incident records. For example, the incident record can contain the following information:
Injured people
Witnesses
Releases
Involved assets
PUBLIC
Page 74 of 82
Integration
This iView is called via object-based navigation using the method Display of the business object BPR_INCIDENT using the parameter KEY={Key}. For more
Prerequisites
1.1.8.1.3.4 Process Administrator

Role: com.sap.pct.eh.roles.EHSMAdmin
The Process Administrator role is assigned to an employee in the IT department. This person is responsible for monitoring the SAP EHS Management processes
and ensuring that the processes are running properly. If issues occur, the process administrator has to determine the root cause and correct the issue. The
process administrator is responsible for the following:
Making settings in the SAP Business Workflow system
Setting up jobs and workflows
Integration
The process administrator works closely with the person who is organizationally responsible for a process. The implementor of a task may also contact the
process administrator if there are technical problems with a process.
Configuration

Technical Data
Technical Name
00000002
1.1.8.1.3.5.1.1 Overview
Technical Data
Technical Name
00000003
1.1.8.1.3.4.1.1.1 Processes
Technical Data
Technical Name
00000082
You can use this workset to monitor the processes in your company.
Features
More Information
For more information about processes in SAP EHS Management, see Process Foundation (EHS-MGM-FND-WF).
1.1.8.1.3.4.1.1.1.1 Display Process Definitions

Technical Data
PUBLIC
Page 75 of 82
00000087
Runtime Technology

Transaction: EHFND_WFF_PRCDEF_LST
Support
EHS-MGM-FND
Availability
Visibility
The iView is not visible in the Process Administrator role.
You can use this iView to display a list of available process definitions in the SAP EHS Management component.
The system displays the process definitions as a list. From the list, you can do the following:
Display a list of process instances for the process definition.
Display detailed information about the process definition.
Use a report to check the process definition for its validity and consistency. You do this by choosing the Status traffic light icon in the report.
Integration
This iView is called via object-based navigation using the method OpenProcessDefList of the business object EH_FND_WFF_OBN. For more information
about the business object, see Business Objects.
Prerequisites
You have specified process definitions in Customizing for SAP EHS Management in the Specify Process Definitions activity (table EHFNDC_PROCDEF).
1.1.8.1.3.4.1.1.1.2 Check Workflow System

Technical Data
00000083
Runtime Technology

Transaction: EHFND_WFF_SYSTEM_CHK
Support
EHS-MGM-FND
Availability
You can use this iView to run checks on the system for SAP EHS Management. You can use this iView to find problems in the processes based on the process
foundation.
The system performs the following checks:
Check whether the workflow runtime environment is set up correctly.
Check whether all required tasks in transaction SWU3 ( Automatic Workflow Customizing ) are completed.
Check whether the collector report for the process foundation statistics is scheduled.
Check whether the process definitions in the Customizing activity Specify Process Definitions are maintained.
Prerequisites
You have made the settings in the Perform Automatic Workflow Customizing activity in Customizing for SAP EHS Management.
You have made the settings in the Specify Process Definitions Customizing activity in Customizing for SAP EHS Management.
1.1.8.1.3.4.1.1.1.3 Check Process Definition

Technical Data
00000085
Runtime Technology

Transaction: EHFND_WFF_PRCDEF_CHK
Support
EHS-MGM-FND
Availability
PUBLIC
Page 76 of 82
Visibility
You can use this iView to perform checks on a process definition and to display the results. This iView helps a system administrator to detect problems within the
processes in the SAP EHS Management component.
The system checks the process definition for the following:
Check
Check
Check
Check
Check
Check
that the process definition entry in the table is consistent.

that PCO class exists, and is valid for implementing the PCO interface and providing a PCBO key.
that PCBO exists, is consistent, and can be instantiated.
that associated workflow templates exist and have been linked to an event.
that the Start Processing and End Processing steps exist in the workflow template.
that the user has performed these steps and whether there are possible agents for these steps.
The iView displays any errors that occurred and any data inconsistencies.
Integration
This iView is called via object-based navigation using the method OpenProcessDefCheck of the business object EH_FND_WFF_OBN using the parameters
p_ehsmc={EHSManagementComp}, p_purpo={Purpose}, and p_varia={ProcessVariant}. For more information about the business object, see
Business Objects.
Prerequisites
You have specified process definitions in Customizing for SAP EHS Management in the Specify Process Definitions activity (table EHFNDC_PROCDEF).
1.1.8.1.3.4.1.1.1.4 Display Technical Details for Process

Definition
Technical Data
00000086
Runtime Technology

Transaction: EHFND_WFF_PRCDEF_INF
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display information about a process definition in the SAP EHS Management component.
The iView provides the following information:
The process definition key
Information about the associated PCO class
Information about the associated PCBO (such as keys and the table of the ROOT node)
Information about associated workflow templates
Integration
This iView is called via object-based navigation using the method OpenProcessDefInfo of the business object EH_FND_WFF_OBN using the parameters
p_ehsmc={EHSManagementComp}, p_purpo={Purpose}, and p_varia={ProcessVariant}. For more information about the business object, see
Business Objects.
Prerequisites
You have maintained the process definition in table EHFNDC_PROCDEF.
1.1.8.1.3.4.1.1.1.5 Check Process Instance

Technical Data
00000088
PUBLIC
Page 77 of 82
Runtime Technology

Transaction: EHFND_WFF_PROCS_CHK
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to perform various checks on a process instance and to display the results. It helps you to detect any problems within SAP EHS
Management processes.
The iView checks the following parts of a process definition:
Availability of the PCBO instance
Associated process definition
Associated business object instance
Data business object instance
Parent PCBO instance
Availability of the associated workflow instance
Status of the workflow instance
Associated PCO
Check the current/last step of the workflow instance
This iView checks the process instance and displays any errors and problems that have occurred.
Integration
This iView is called via object-based navigation using the method OpenProcessInstCheck of the business object EH_FND_WFF_OBN using the
parameter p_pcbok={Key}. For more information about the business object, see Business Objects.
Prerequisites
The process instance to be checked must be a process based on a PCBO. The PCBO instance must exist.
1.1.8.1.3.4.1.1.1.6 Display Technical Details for Process Instance

Technical Data
00000089
Runtime Technology

Transaction: EHFND_WFF_PROCS_INF
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display technical information about an SAP EHS Management process instance. The iView provides information about the following
parts of a process instance:
Information stored in the PCBO itself (such as the process definition and the creation date)
Associated business object
PCO class
PCBO
Workflow template
Workflow instance
Workflow progress
Integration
This iView is called via object-based navigation using the method OpenProcessInstInfo of the business object EH_FND_WFF_OBN using the parameter
p_pcbok={Key}. For more information about the business object, see Business Objects.
Prerequisites
PUBLIC
Page 78 of 82
The process instance is based on a PCBO.
1.1.8.1.3.4.1.1.1.7 Display Process Instances

Technical Data
00000090
Runtime Technology

Transaction: EHFND_WFF_PROCS_LST
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display the instances of a process configured for the SAP EHS Management component. The system displays the process instances
that are based on a PCBO. From this list, you can display additional information about the selected process instance.
To display additional information about the process instance, proceed as follows:
Choose the
Choose the
Choose the
Choose the
Info icon to display technical information about the selected process instance in the report.
Log icon to display the technical workflow log for the selected process instance in the report.
Graph icon to display the graphical workflow log for the selected process instance in the report.
Check icon to run checks on the selected process instance in the report.
Integration
This iView is called via object-based navigation using the method OpenProcessInstList of the business object EH_FND_WFF_OBN using the
parameter p_ehsmc={EHSManagementComp}, p_purpo={Purpose}, and p_varia={ProcessVariant}. For more information about the business
Prerequisites
You have specified process definitions in Customizing for SAP EHS Management in the Specify Process Definition activity.
1.1.8.1.3.4.1.1.1.8 Technical Workflow Inbox

Technical Data
00000091
Runtime Technology

Transaction: EHFND_WFF_TECH_WFIBO
Support
EHS-MGM-FND
Availability
Visibility
You can use this iView to display a user's tasks. You can also display additional information for a selected task. You select the user inbox that you want to display
by entering that user ID in the selection screen. To display additional information about the task, proceed as follows:
1. Choose the Info icon to display additional information about the selected task.
2. Choose the Log icon to display the technical workflow log for the selected task.
3. Choose the Graph icon to display the graphical workflow log for the selected task.
Integration
This iView is called via object-based navigation using the method OpenTechWfInbox of the business object EH_FND_WFF_OBN using the parameter
p_uname={UserName}. For more information about the business object, see Business Objects.
Prerequisites
PUBLIC
Page 79 of 82

Technical Data
00000092
Runtime Technology

Transaction: EHFND_WFF_TECH_WFLOG
Support
EHS-MGM-FND
Availability
You can use this iView to display the technical workflow log for a given task ID. The technical workflow log displays technical information about a workflow
instance. The only parameter you can select is the task ID. This ID can either be the ID of a workflow instance, or the ID of a task. If the ID of a task is passed,
the iView displays the corresponding workflow instance.
Integration
This iView is called via object-based navigation using the method OpenTechnicalWorkflowLog of the business object EH_FND_WFF_OBN using the
Prerequisites

Technical Data
00000093
Runtime Technology

Transaction: EHFND_WFF_GRAPH_WFLG
Support
EHS-MGM-FND
Availability
You can use this iView to open the graphical workflow log for a given workflow instance or task ID. The iView displays the progress of a workflow instance. You
can see the original workflow template and an overlay of the actual route that the workflow took.
Integration
This iView is called via object-based navigation using the method OpenGraphicalWorkflowLog of the business object EH_FND_WFF_OBN using the
Prerequisites
1.1.8.1.3.4.1.1.1.11 EHS Management Task (Technical

Information)
Technical Data
00000094
Runtime Technology

Transaction: EHFND_WFF_WI_INF
Support
EHS-MGM-FND
PUBLIC
Page 80 of 82
Availability
You can use this iView to display information about a specific task and the corresponding process instance, if applicable.
Integration
This iView is called via object-based navigation using the method OpenWorkitemInfo of the business object EH_FND_WFF_OBN using the parameter
p_wiid={ID}. For more information about the business object, see Business Objects.
Prerequisites
1.1.8.1.3.4.1.1.1.12 Open Comment

Technical Data
00000153
Runtime Technology
ABAP/Web Dynpro
Support
EHS-MGM-FND
Availability
You can use this iView to display the comment.
Integration
This iView is called via object-based navigation using the method OpenComment of the business object EH_FND_WFF_OBN. For more information about the
1.1.8.1.3.5 Environmental Manager

Role: com.sap.pct.eh.role.EnvManager
The Environmental Manager role is assigned to employees who are responsible for ensuring the organization is compliant with environmental regulations and
standards. The environmental manager is responsible for assessing environmental aspects and impacts , implementing risk treatment programs for
environmental risks, monitoring environmental performance , and investigating any incident that involves releases into the environment. To ensure compliance with
environmental regulations and standards, the environmental manager communicates with employees and performs training courses with regards to potential
environmental impacts.
Integration
This role is integrated in the following scenario:
Assessing environmental risks
Configuration

Technical Data
Technical Name
00000002
1.1.8.1.3.5.1.1 Overview
PUBLIC
Page 81 of 82
Technical Data
Technical Name
00000003
1.1.8.1.3.5.1.1.1 Work Overview

Technical Data
Technical Name
00000047
Features
More Information
PUBLIC
Page 82 of 82

Sap Ehsm

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Sap Ehsm

Diunggah oleh

Hak Cipta:

Format Tersedia

Component Extension for SAP Environment, Health, and Safety

1.1.8.1.3.3 Notification Recipient

1 Component Extension for SAP Environment, Health, and Safety

3.0 SP03 or higher

SAP ERP 6.05 or 6.06

SAP NetWeaver 7.0 BI Content Add-On 7

1.1 Foundation for EHS Management (EHS-MGM-FND)

1.1.1 Business Objects

1.1.1.1 Adding Fields to the User Interface

Adding Fields to the Business Object

Then select the node structure that you want to enhance.

Modifying the GUIBB Configuration

1.1.1.2 Field Control

Foundation for EHS Management

Settings for Business Objects

1.1.1.3 Document Storage

Foundation for EHS

1.1.1.4 Creation of Change Documents

for incident records

1.1.2 Process Foundation (EHS-MGM-FND-WF)

1.1.2.1 PCOs and PCBOs

PCO and PCBOs in the Process Foundation

Use in Monitoring and Analyzing Processes

1.1.2.2 Process Configuration

1.1.2.2.1 Changing Workflow Templates

Foundation for EHS

. The workflow templates in the standard system of incident

Changing Workflow Templates

Registering Workflow Templates

1.1.2.3 Task Management

1.1.2.3.1 Changing the Task Processor

Changing the Task Processor in the Back-End System

1.1.2.3.2 Continuing Execution of a Process with Errors

SAP EHS Management

Foundation for EHS

1.1.2.4 Process Tools

Usage of Processes in the Application

General Scheduler Log

scheduler, the instances of a process setup, and any

Scheduler Item Log

BI Content 7.05, SP02

1.1.3 Print Forms and Interactive Forms (EHS-MGM-FND-FRM)

1.1.3.1 Adding Print Forms and Interactive Forms

Creating ABAP Dictionary-Based Structures

Creating Form Interfaces

the data available in the form layout.

Laying Out Forms

Validates the data that is in the form

Foundation for EHS Management

Print Forms and Interactive Forms

Inbound Persister Implementation (Optional)

Stores the data of a form

Validates the data that is in the form

Stores the form

Returns the comments that have been entered in the form

SAP EHS Management

Foundation for EHS Management

Foundation for EHS Management

Print Forms and Interactive Forms

SAP EHS Management

SAP EHS Management

1.1.3.2 Mapping Business Objects Nodes to Adobe Forms

Foundation for EHS Management