00 47633737069263615

11/14/2019
Component Extension for SAP EHS

Management
Generated on: 2019-11-14
Component Extension for SAP Environment, Health, and Safety Management | 6.0
PUBLIC
Original content: https://help.sap.com/viewer/c2db47abe44e4aa7ab1be93e4c20ae18/6.0/en-US
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/viewer/disclaimer.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20306918&topics=3899157e19eb44b682834131b6… 1/64
11/14/2019
Foundation for EHS Management (EHS-

MGM-FND)
Use
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 elds and nodes to business objects, control how the elds 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 Work ow, and helps you to
manage tasks. You can extend and adapt delivered processes speci cally 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-speci c 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.
Regulatory Lists
You can use customer lists and regulatory lists to group listed substances according to regulatory or company-speci c
policy and to 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 de ne 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).
Integration
The foundation of SAP EHS Management is used entirely or in part in the following components:
Incident Management
Risk Assessment
Product Compliance
11/14/2019
Process Foundation (EHS-MGM-FND-WF)

Use
The process foundation is essential to the business processes supported by SAP EHS Management. It links the SAP Business
Work ow 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 work ow at runtime. The process foundation provides a general base for
the handling of work ows 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 Work ow Engine of SAP Business Work ow. For more information, see the SAP NetWeaver
documentation at http://help.sap.com/nw and select you release. Open the Function-Oriented View and navigate to:
Application Server Application Server ABAP Other Services Services for Application Developers SAP Business Work ow .
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 noti cations, assigning tasks, complying with
regulatory requirements, reporting, and so on.
Adaptation of a process to match country and region-speci c needs
You can create variants of existing processes for a speci c country or region.
Custom development capabilities
You can use customer-speci c 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 Work ows and
Tasks.
For more information about the processes of risk assessment that use the process foundation, see Risk Assessment Work ows
and Tasks.
For more information about the processes of product compliance that use the process foundation, see Product Compliance
Work ows and Tasks
PCOs and PCBOs

11/14/2019
De nition
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
Work ow.
Process control business object (PCBO)
The PCBO is a BOPF business object that represents a work ow-driven process in the system. It provides the logic, such as
the action that starts the work ow in SAP Business Work ow, and stores the process-speci c data, such as the process
de nition key.
Process control object (PCO)
A PCO is an ABAP Objects class that represents a process control business object in the work ow for a speci c process in
SAP EHS Management. The PCO makes it technically possible to use the BOPF business objects with the work ow
functions of SAP Business Work ow.
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 speci c
type of process, for example, for inquiries or requests, noti cations, and approvals.
Use
Since the SAP Work ow 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 work ow
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 work ow in SAP Business Work ow to its corresponding PCBO. The PCBO is where
the business logic is implemented and the process-relevant data is stored. The work ow 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.
11/14/2019
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 de nition, 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 work ow in SAP Business Work ow.
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 work ow-enabled in the Class Builder, and the Work ow Engine can
use it.
For more information about IF_WORKFLOW, see the SAP Library for SAP NetWeaver 7.0 at http://help.sap.com/nw702
SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services SAP Business Work ow
Reference Documentation ABAP Classes in Work ow IF_WORKFLOW Interface .
The PCO calls the business logic from the PCBO that is to be executed in a work ow task, and also reads the data from the
PCBO, so the data is available to the work ow.
When you change the attributes of a task (for example, the approver of a maintenance noti cation) 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
11/14/2019
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
For more information about the ABAP objects classes, see the SAP Library for SAP NetWeaver 7.0 at http://help.sap.com/nw702
SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology ABAP Programming and
Runtime Environment (BC-ABA) ABAP Programming (BC-ABA) ABAP Objects Classes .
For more information about SAP Business Work ow, see the SAP Library for SAP NetWeaver 7.0 at http://help.sap.com/nw702
SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services SAP Business Work ow .
Process Con guration

Use
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-speci c process variants. This document provides an overview of the
con guration 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 con gure processes in the following ways:
Adapt existing process
You can adapt existing processes delivered in the standard system to suit your customer-speci c processes. For more
information, see Customizing for SAP EHS Management under Foundation for EHS Management Process
Foundation Extend and Adapt Processes .
Add new elds to store process-speci c data
You can add new elds to the existing PCBO to collect additional process-speci c 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.
Note
PCO classes provide the data structures of their PCBOs as public elds. This means, the SAP Business Work ow can
read the new elds 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 noti cations to integrated systems. For more information about variants, see Customizing
for SAP EHS Management under Foundation for EHS Management Process Foundation Specify Process De nitions .
11/14/2019
De ne 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 de ne customer-speci c 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-speci c logic for a process in the PCO
If you do not want to implement customer-speci c logic in the PCBO, you can extend or change an existing PCO class to
create customer-speci c 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 work ow when the CREATED event of the customer-speci c PCO class is triggered, you must assign a work ow
template to this event. You can do this in the Work ow Builder on the Start Events tab in the version-independent basic
data of the relevant work ow template.
More Information
For more information about changing work ow templates, see Changing Work ow Templates.
Changing Work ow Templates

Use
The work ow templates in the standard system for SAP EHS Management cover the standard processes of incident management
and risk assessment. You can change work ow templates to include new steps or change the process ow.
Prerequisites
You have experience using the Work ow Builder. Knowledge of ABAP programming is an advantage.
You have carried out automatic work ow Customizing. For more information, see Customizing for SAP EHS Management
under Foundation for EHS Management Process Foundation Basic Settings Perform Automatic Work ow
Customizing .
Procedure
Copying Existing Work ows
To change an existing work ow, copy it into the namespace Z.
Choose in the SAP menu Tools ABAP Workbench Overview Object Navigator . The work ow templates in the standard system
of incident management are available in the package EHHSS_WF_INC.
Changing Work ow Templates
1. To change a work ow template, choose in the SAP menu Tools Business Work ow Development De nition
Tools Work ow Builder Work ow Builder .
2. Expand the work ow with new steps or change the process ow.
11/14/2019
Note
If changes to the work ow template also change the business logic, you must extend or change the existing process
control object of the process.
For more information, see Process Con guration.
3. Save and activate the changed work ow template.
Registering Work ow Templates
1. To deactivate the work ow template in the standard system, choose in the SAP menu Tools ABAP
Workbench Overview Object Navigator .
2. Open the work ow template in the standard system.
3. Go to the Triggering Events tab page that shows event links. To deactivate the work ow 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 work ow template, open it, go to the Triggering events tab page, and register the new work ow
template for the event CREATED.
Transfer the values from the standard system work ow that you used as a template for the Object Category, Object Type,
and Event columns. To activate the work ow template, click the gray symbol in the Event creator column. The symbol
appears green and the event is registered.
Result
The work ow template includes new steps or the process ow 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 SAP Business Work ow, see the SAP Library for SAP NetWeaver 7.0 at http://help.sap.com/nw702
SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services SAP Business Work ow .
For more information about con guring processes, see Process Con guration.
Task Management
Use
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 noti cations 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
11/14/2019
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.
Noti cations
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 noti cation, 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 noti cation 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 . Choose your release and go to section Application Help. Open the
SAP Library documentation, choose the link Processes and Tools for Enterprise Applications and go to Inbox (CA-EPT-IBO).
Changing the Task Processor

Use
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 rst that you are authorized
to use the work ow tools of SAP EHS Management (authorization object EHFND_WFT).
11/14/2019
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 work ow system by choosing the Display Work ow Log
pushbutton.
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.
Continuing Execution of a Process with

Errors
Use
To continue the execution of a process, you can navigate to the SAP Business Work ow 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 work ow
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 con gured the processes of SAP EHS Management properly in the Customizing activities under SAP EHS
Management Foundation for EHS Management Process Foundation .
Procedure
To continue the execution of a process, perform the following steps:
1. Display the process details. You can do this from the Tasks tab of a data record or from task management.
2. To display technical information about the process, navigate to the work ow system by choosing the Display Work ow Log
pushbutton.
3. Select the erroneous step and choose in the menu Goto Work Item .
4. Activate the administrative functions by choosing in the menu Extras Activate Administration .
5. 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.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20306918&topics=3899157e19eb44b682834131b… 10/64
11/14/2019
More Information
You can also continue a work ow that has an error with the standard functionality of SAP Business Work ow. You can display the
erroneous work ows in Diagnosis of Work Items Containing Errors (transaction SWI2_DIAG).
Process Tools
Use
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 de nes them as recurring in the application on the Tasks tab. There, the user can add an action
or noti cation and specify the start and end date/time, as well as when and how often the action or noti cation recurs. After the
user has scheduled the action or noti cation in the application, the system automatically schedules the program
R_EHFND_SCHEDULER_JOB to start the process for the speci ed 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 about the process administrator role, see Process
Administrator
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 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.
11/14/2019
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 speci ed date in program
R_EHFND_PSE_DISABLE_ERRONEOUS.
You can exclude speci c process de nitions from monitoring and analysis. For more information, see Customizing under
SAP EHS Management Foundation for EHS Management Process Foundation Processes Specify Process De nitions .
You can exclude process steps from monitoring and analysis by removing the property
sap.eh.fw.wff.report_include in the work ow 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 noti cations in incident management, see Adding Actions and Noti cations.
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/nw . Select your
release and open the SAP Library documentation. Go toBI Content Extension SAP EHS Management SAP EHS Management –
Process Foundation Dashboards
Print Forms and Interactive Forms (EHS-

MGM-FND-FRM)
Use
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 company’s 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:
11/14/2019
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 lled out by hand.
Review data before transferring into a data record
You can con gure 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.
Adding Print Forms and Interactive Forms

Use
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 speci c 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
11/14/2019
An ABAP Objects class that obtains the data from the application and lls 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.
Con guration
You can con gure 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 de nitions 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.
Procedure
The following sections describe the steps speci c 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 de nes 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-speci c 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.
11/14/2019
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 the data available in the form layout.
Laying Out Forms
When you insert new data elds from the Data View in a form, you bind the data to a eld in the form layout by performing the
following steps:
1. Copy a eld into the form using drag and drop for the data eld, for example, a text eld.
2. Choose the tab Object Binding .
3. Enter the data eld 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 lled
interface structure
This method contains the following:
Form information that is con gured in Customizing as the

importing parameter
The process component-speci c 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 speci c object (such as the person), the
corresponding suffix of the le name can be set. This method is
called after generation of a form when the le name is created.
11/14/2019
For more information, see the test data provider CL_EHFND_FW_ADS_TEST_DPROV in the system, or the data providers
con gured in Customizing under SAP EHS Management Foundation for EHS Management Print Forms and Interactive
Forms Specify Forms .
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 speci c object (such as the person), the
corresponding suffix of the le name can be set. This method is
called after generation of a form when the le 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 con gured in Customizing under SAP EHS Management Foundation for EHS
Management Print Forms and Interactive Forms Specify Forms .
Form Con guration
You can specify forms in Customizing under SAP EHS Management Foundation for EHS Management Print Forms and
Interactive Forms Specify Forms .
You can specify the groups for forms in Customizing to control the appearance and usage of the forms in the application under
SAP EHS Management Foundation for EHS Management Print Forms and Interactive Forms Specify Forms .
Mapping Business Objects Nodes to Adobe

Forms
Use
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
11/14/2019
You have speci ed forms in Customizing for SAP EHS Management under Foundation for EHS Management Print Forms and
You have de ned the form interface in transaction SFP.
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 elds that have to be extracted.
Features
The Mapping Workbench provides the following features:
De ne eld 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 nished 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 nished 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 modi ed class, the system can handle the following
situations:
If you modi ed 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 speci c code line is obsolete after regeneration, the system comments it out.
More Information
For more information, see Customizing for SAP EHS Management under Foundation for EHS Management Print Forms and
11/14/2019
Integration (EHS-MGM-FND-INT)
Use
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 re ected 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 con gured. 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 speci es how these components can support your business scenarios in
the SAP EHS Management applications:
Component Function Usage in SAP EHS Management
Incident Risk Product Environment

Management Assessment Compliance Management
Personnel Administration Read person-related data for X X - -

(PA) employees and applicants
Personnel Time Read and create absences for X - - -

Management (PT) employees
(not activated by default)
SAP Business Partner Read data for business X X X -

(SAP BP) partners
Change and create data for X - X -

business partners
11/14/2019
Component Function Usage in SAP EHS Management
Incident Risk Product Environment

Management Assessment Compliance Management
Organizational Determine relations between X X - -

Management (PA-OS) individual persons, positions,
and organizations
Plant Maintenance (PM) Import and read data for PM X X - X

technical objects
Read and create maintenance X X - -

noti cations
Read and create maintenance X - - -

orders for nancial tracking
Flag PM technical objects for - X - -

which risk assessment
information can be retrieved
and communicate risk
information
Customer Service (CS) Read and create service X X - -

noti cations
Read and create service orders X - - -

for nancial tracking
Quality Management Read and create quality X X - -

(QM) noti cations
Accounting (AC) Read and create internal X - - -

orders for nancial tracking
Materials Management Read material data X X X X

(MM)
SAP BusinessObjects Transfer data to the SAP X - - -

governance, risk, and BusinessObjects Risk
compliance solutions Management component
(GRC solutions)
(not activated by default)
SAP Management of Transfer results of simulated - X - -

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

send it to SAP Management of
Change
Constraints
The following data must always be available in the local system:
Plants, including description and address data
Material and material descriptions
Currencies and exchange rates
11/14/2019
Noti cation 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 speci c
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 Foundation for EHS
Management Integration Specify Destinations for Integration .
More Information
For more information about integration in each SAP EHS Management component, see the following documentation:
Incident Management: Integration with Other Components
Risk Assessment: Integration with Other Components
Product Compliance: Integration
Integration for Person Information

Use
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.
11/14/2019
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 de ned the relevant subtypes for party infotypes in Customizing for SAP EHS Management under Foundation for
EHS Management Integration Human Resources Integration Specify Relevant Subtypes for a Party Infotype. .
You have de ned 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 Foundation for EHS Management Integration Specify Destinations for
Integration .
If you want to integrate personnel time data, you have made the application-speci c 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.
Integration for Noti cations

Use
You can use this function to integrate noti cation 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 noti cations that must be implemented
in other components directly from the EHS-MGM applications. The EHS-MGM system monitors the status of each noti cation
process until it is completed.
Integration is possible for the following noti cation categories:
Maintenance noti cations (PM)
Quality noti cations (QS)
Service noti cations (CS)
Prerequisites
You have speci ed the required noti cation types in Customizing for SAP EHS Management under Foundation for EHS
Management Integration Specify Noti cation Types .
11/14/2019
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 Foundation for EHS Management Integration Specify Destinations for
Integration .
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 noti cation, you can display details including its status directly from the EHS-
MGM applications.
You can use the report Check for Completed Noti cations (R_EHHSS_ACT_CHECK_COMPL_EXT_NO) to check regularly for
noti cations that have been completed in other components. For all noti cations in status Completed, the report triggers the next
process step. For more information, see the system report documentation.
Note
If you schedule noti cations as recurring actions, the system starts a noti cation process for each recurrence.
The noti cations 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).
Check for Completed Noti cations

Use
You use the report Check for Completed Noti cations (R_EHFND_CHECK_COMPL_EXT_NOTIF) in SAP EHS Management to
check if noti cations 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 speci ed under Use.
Prerequisites
You have speci ed the destinations of the PM, CS, and QM systems in Customizing for SAP EHS Management under Foundation
for EHS Management Integration Specify Destinations for Integration .
You have speci ed the noti cation types that you use in the application in Customizing for SAP EHS Management under
Foundation for EHS Management Integration Specify Noti cation Types .
Features
The report determines all noti cations that are in status In Process and checks whether these noti cations have been set to
Completed in the relevant component. For all noti cations that have been completed, the report triggers the next process step to
create a task for the approver to complete the noti cation in the application.
11/14/2019
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 Noti cation
Status Check .
Creating and Revising Regulatory Lists

Use
You can use regulatory lists in the application to store a list of substances that are subject to legal or industry-speci c regulations,
for example, declarable substances or substances for which all uses are prohibited or there are possible exemptions. Regulatory
lists can also provide information about thresholds (such as occupational exposure limits) for listed substances.
As legal or industry-speci c regulations change, you can create new revisions of regulatory lists. Each instance of a regulatory list
(even the rst 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 rst make the following settings before creating regulatory list revisions in
the application:
1. In Customizing under Foundation for EHS Management General Con guration Create Regulatory Lists and Customer
Lists , con gure the 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 Con guration Agents Specify Regulatory Lists for OELs .
Product Compliance General Con guration Regulations and Compliance Requirements Specify Regulatory
Lists and Customer Lists .
Regulatory Lists in Health and Safety
In the application, perform the following steps to create and revise regulatory lists for OELs:
1. In Health and Safety Overview Regulatory Lists for OELs , choose the service Create Regulatory List Revision.
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 chemicals, release the revision.
Note
You can only have one inactive revision open at a time. You must rst release or delete the currently inactive revision
before creating a new revision.
In the application, perform the following steps to create and revise regulatory lists for restricted substances:
11/14/2019
1. In Health and Safety Overview Regulatory Lists for Restricted Substances , choose the service Create Regulatory List
Revision.
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 if the substance is declarable or
prohibited, to the new regulatory list revision. You can add new data and update existing data.
4. If you have enabled integration to SAP Product Stewardship Network, you can check for updates of the regulatory list
content. For more information, see SAP Product Stewardship Network Integration.
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 De ning Occupational Exposure Limits (OELs).
Analytical Reporting
Use
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
SAP Business Explorer (BEx) report
Note
You can nd speci c 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.
11/14/2019
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/nw BI Content . Choose the corresponding release (see the release listed in Component Extension for SAP
EHS Management). Open the SAP Library documentation and go to BI Content the SAP EHS Management or BI Content
Extension the SAP EHS Management
Features
This component offers the following functions to enable analytical reporting:
File-Based Reporting
Allows you to export data in various le formats and generate analytical reports in your standard office environment.
Data extraction to BW
Provides a foundation for simpli ed data extraction in the standard system, and allows you to easily con gure 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 speci c type. You can use dashboards or the
process monitoring tools in the standard system.
File-Based Reporting
Use
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 le 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 le-based reporting in Customizing for SAP EHS Management under Foundation for EHS
Management File-Based Reporting .
You are using a business object node to get the data. This node contains all elds that have to be extracted.
Features
Extraction of BO data in different le formats
File-based reporting allows you to extract data from business objects in SAP EHS Management in a le format you use in
your standard office environment.
Support of foreground or background processing
Depending on your entries in the Customizing activity De ne Export Pro les, the export is processed in either the
foreground or the background.
E-mail shipment of le-based reports
11/14/2019
The generated export le is sent to the user by e-mail. If the size of the generated le is too large, the le 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 Con gure General Settings.
Use of template les
As an additional option, it is possible to upload prede ned Microsoft Excel template les in the Customizing activity De ne
Export Pro les into the system. These templates are than used for generating export les.
Note
You have to save the exported le on your computer before opening it. Otherwise, your le is opened in protected view.
If you use pivot tables in your Microsoft Excel template le, 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 le, the system performs the following activities depending on the various export
possibilities:
Export in a CSV le format
If only one data selection is selected, the exported le is in CSV format.
If several data selections are selected, the exported le is a ZIP archive that includes one CSV le per data selection.
Export in a Microsoft Excel 2007/2010 le format without template le
If only one data selection is selected, the exported Microsoft Excel le contains one sheet.
If multiple data selections are selected, the exported Microsoft Excel le contains one sheet for each data selection.
If errors occur, the Microsoft Excel le contains a separate sheet for error messages.
Export in a Microsoft Excel 2007/2010 le format with template le
If no sheet exists in the template le 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 le, proceed as follows:
De ne an export pro le in the Customizing activity De ne Export Pro les without a template le.
Export data using your newly created export pro le.
Modify this exported le to your preferences.
Save the changed le and upload it as a template to your export pro le.
11/14/2019
More Information
For more information about con guring le-based reporting, see Customizing for SAP EHS Management under Foundation for
EHS Management File-Based Reporting .
Data Extraction to BW
Use
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 simpli ed
data extraction in the standard system, and allows you to easily con gure 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
elds to be extracted. The extractor foundation reads the data provided by the node from BOPF. The node and additional data is
11/14/2019
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 elds 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 node’s
determination reads data from multiple BO nodes.
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 speci c 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 ful lls the SAPI requirements.
Extensible for Customer-Speci c Extraction
You can use the extractor foundation in your customer-speci c 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 con guring extractors for BI analytical reporting, see Customizing for SAP EHS Management under
Foundation for EHS Management Analytical Reporting .
DataSources
A DataSource is a set of elds that provide the data for a business unit for data transfer. From a technical perspective, the
DataSource is a set of logically-related elds that are provided to transfer data to SAP NetWeaver BW and the operational data
provider in the backend either in a at structure (extraction structure) or in multiple at 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.
Work ow Process De nitions

11/14/2019
DataSource Transactional Data 0EHSM_FND_WF_01
Use
You can use this DataSource to extract process de nitions 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)
Exchange 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
Veri able No
Data Modeling
Delta Update
The delta update used for this DataSource is AIE (After-Images by Extractor). The deciding eld for the update is
BW_DELTATIMESTMP.
Fields of Origin for the Extraction Structure
Fields in the Extraction Description of the Field in the Table of Origin Field in the Table of Origin
Structure Extraction Structure
EHSM_COMP Component of EHS EHFNDC_PROCDEF EHSM_COMPONENT

Management
PURPOSE Purpose of EHS Management EHFNDC_PROCDEF PURPOSE

Process
PROC_VARIANT Name of Process Variant EHFNDC_PROCDEF VARIANT
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 all process templates from the table containing the process de nitions EHFNDC_PROCDEF into SAP
NetWeaver BW. The data is not aggregated or transformed.
Work ow Process Instances

11/14/2019
Use
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
Content Versions EHM300
Delta-Capable Yes
Veri able Yes
Data Modeling
Delta Update
BW_DELTATIMESTMP.
EHSM_COMP Component of EHS - -

Management
PURPOSE Purpose of EHS Management - -

Process
PROC_VARIANT Name of Process 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
11/14/2019
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).
Veri cation of Key Figures
The process log is checked.
Work ow Step De nitions

Use
Technical Data
Delta-Capable Yes
Veri able No
11/14/2019
Data Modeling
Delta Update
BW_DELTATIMESTMP.

Management

Process
TEMP_ID Task ID - -
NODE_ID Node Number - -
THRESHOLD Threshold of Report-Relevant - -

Steps
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 con gured for each step into
SAP NetWeaver BW. The system extracts only those steps which are foreground steps or marked as relevant for reporting.
Work ow Step Instances

Use
Technical Data
Delta-Capable Yes
11/14/2019
Veri able Yes
Data Modeling
Delta Update
BW_DELTATIMESTMP.

Management

Process
CONF_KEY NodeID - -
TEMP_ID Task ID - -
WORKITEM_ID Work item ID - -
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
AGE_PROC Overall Age Of This Item In - -

Number Of Days
Extractor Logic
The DataSource is implemented by a function module (extraction method F1).
Veri cation of Key Figures
The step details are checked.
11/14/2019
Work ow Process De nitions - Text

Extraction (Full)
DataSource Texts 0EH_DESCRP_TEXT
Use
You can use this DataSource to extract texts for the work ow process de nitions.
Technical Data
Delta-Capable No
Veri able No
Data Modeling
LANGUAGE Language Key - -
EHSM_COMPONENT Component of EHS - -

Management

Process
VARIANT Name of Process Variant - -
DESCRIPTION Description (Long) - -
Work ow Reporting - Component

Description
DataSource Texts 0EH_COMP_TEXT
Use
11/14/2019
You can use this DataSource to extract descriptions of components for the work ow reporting.
Technical Data
Delta-Capable No
Veri able No
Data Modeling
COMPONENT_ID Component of EHS - -

Management
Work ow Reporting - URL Extraction (Full)

DataSource Attributes 0EH_URL_ATTR
Use
You can use this DataSource to extract the full URL for the work ow reporting.
Technical Data
Delta-Capable no
11/14/2019
Veri able No
Data Modeling
SERVER — - -
PORT System ID - -
PATH_PREFIX — - -
Work ow Step De nitions - Text Extraction

(Full)
DataSource Texts 0EH_DESCRS_TEXT
Use
You can use this DataSource to extract texts for the work ow step de nitions.
Technical Data
Delta-Capable No
Veri able No
Data Modeling
11/14/2019
TEMP_ID Task ID - -
Texts for Material ID

DataSource Texts 0EH_MATID_TEXT
Use
You can use this DataSource to extract texts for materials.
Technical Data
Shipment SAP NetWeaver 7.0 BI Content add-on 6 SP 03
Delta-Capable No
Veri able No
Data Modeling
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.
Common Objects
11/14/2019
As of component extension 3.0 for SAP EHS Management, the DataSources for common objects, such as the locations, are
documented in this structure.
Location Master Data

DataSource Attributes 0EH_LOCATIN_ATTR
Use
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
Delta-Capable No
Veri able No
Prerequisites
You have con gured the DataSource in Customizing in the source system under SAP EHS Management Foundation for
EHS Management Analytical Reporting Con gure 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 SAP EHS
Management Foundation for EHS Management Analytical Reporting BAdI: Extraction of One Object .
Data Modeling
11/14/2019
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
STATUS Location Status - -
FUNCT_LOC_ID Functional Location ID - -
EQUIPMENT_ID Equipment - -
COMPANY_CODE Company Code - -
BUSS_AREA Business Area - -
COST_CENTER Cost Center - -
CONTROLLING_AREA Controlling Area - -
ORG_UNIT Organizational Unit ID - -
AUTH_GROUP Location Authorization Group - -
LONGITUTE Geo Location for Longitude - -
LATITUDE Geo Location for Latitude - -
ELEVATION Geo Location for Elevation - -
STORAGE_LOC Storage Location - -
WAREHOUSE_NUM Warehouse Number - -
STORAGE_TYPE Storage Type - -
BW_RECORDNUMBER Serial number of records since - -

one risk can have multiple
records
BW_RECORDMODE Record mode that allows - -

agging 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.
11/14/2019
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 eld SPLITDATE that speci es the date when the revision of
the location started being valid. The value of this eld is extracted into the eld DATEFROM in the extractor structure. The eld
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.
Location Hierarchy
DataSource Hierarchy 0EH_LOCATIN_0001_HIER
Use
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
Delta-Capable No
Veri able No
Data Modeling
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.
Texts for Location

DataSource Texts 0EH_LOCATIN_TEXT
Use
11/14/2019
You can use this DataSource to extract texts for locations.
Technical Data
Application Component SAP EHS Management (EHS-MGM-INC)
Delta-Capable No
Veri able No
Data Modeling
ID Business Object ID - -
DATEFROM Valid-From Date - -
DATETO Valid-To Date - -
TEXT Location Name Description - -
Texts for Location Type

DataSource Texts 0EH_LOCTYPE_TEXT
Use
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
11/14/2019
Delta-Capable No
Veri able No
Prerequisites
You have con gured location types in the source system in the Customizing activity for SAP EHS Management under Foundation
for EHS Management Locations Specify Location Types .
Data Modeling
LANGUAGE Language - -
CODE Location Type - -
DESCRIPTION Description (Extra Short) of - -

Location
Texts for Location Authorization Group

DataSource Texts 0EH_LOCAGRP_TEXT
Use
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
Delta-Capable No
Veri able No
Prerequisites
11/14/2019
You have con gured location types in the source system in the Customizing activity for SAP EHS Management under Foundation
for EHS Management Locations Specify Authorization Groups .
Data Modeling
LANGUAGE Language - -
CODE Authorization Group - -
DESCRIPTION Description (Extra Short) of - -

Authorization Group
Technical Solution Information

Business Objects
De nition
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 noti cation), and protection goal.
Location (EHFND_LOCATION)
You can use the location in incident management and risk assessment to represent identi ed real places, virtual
spaces, or objects in the system. For more information about using this business object, see Locations.
Chemical (EHFND_CHEMICAL)
You can use the chemical business object to store information that you need for health and safety processes. If you
use a chemical in a risk assessment process, it is referred to as an agent.
Regulatory List (EHFND_REGLIST)
You can use regulatory lists in risk assessment and product compliance. On the regulatory lists business object, you
can store listed substances (EHFND_LISTED_SUBSTANCE) that are subject to legal or industry-speci c
regulations. In addition, you can store information about thresholds such as occupational exposure limits (OELs) for
listed substances.
Sampling Method (EHFND_SAMPLING_METHOD)
You can use the sampling method business object in environmental management and risk assessment to store data
used in the execution of your sampling processes. In environmental management the business object for the
activity where the sampling method is used is, (EHENV_SAMPLING_DEFINITION), while in risk assessment it is
(EHHSS_SAMPLING_CAMPAIGN).
11/14/2019
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
Business Objects for environmental management
For a list of the business objects used for environmental management, see Business Objects for Environmental
Management
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).
Adding Fields to the User Interface

Use
You can add elds 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 de nitions in the ABAP Dictionary, have some experience with business objects based on BOPF
(transaction /BOBF/CUST_UI), and have experience con guring Web Dynpro ABAP user interfaces with the Floorplan Manager
for Web Dynpro ABAP (FPM).
Procedure
To add elds, you have to perform two main activities:
1. Add the elds to the business object
11/14/2019
2. Modify the GUIBB con guration to include the elds
Adding Fields to the Business Object
Note
Each BO node generally consists of a particular DDIC structure that is used for adding new elds, for example. To add new
elds 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. Then select the node structure that you want to enhance.
3. Double-click the Extension Include to display the ABAP Dictionary maintenance for this structure.
4. Then choose Goto Append Structure to display the ABAP Dictionary maintenance for the append structure.
5. In the dialog box, enter the name of the append structure. Then click Continue.
6. In the Dictionary maintenance for this structure, provide a short description of the structure. Enter the components (in this
case, the elds) that you want to add and specify their type. Then choose Activate to activate the changed structure.
Modifying the GUIBB Con guration
Note
The following steps describe how you enhance generic user interface building block (GUIBB) con gurations.
For more information about adapting GUIBB con gurations, see SAP Library for SAP NetWeaver on the SAP Help Portal at
http://help.sap.com/nw702 . Go to section Application Help and open the documentation for Function-Oriented View. Go to
Application Platform by Key Capability ABAP Technology UI Technology Web UI Technology Floorplan Manager for Web
Dynpro ABAP 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 con guration editor in administrator mode.
You use the administrator mode of the Web Dynpro Explorer to make modi cation-free changes to a user interface with the
con guration editor for Floorplan Manager. To start the con guration editor in administrator mode, perform the steps
described in the Procedure of Administrator Mode in the SAP Library for SAP NetWeaver on the SAP Help Portal at
http://help.sap.com/nw702 . Go to section Application Help and open the documentation for Function-Oriented View.
Go to Application Platform by Key Capability ABAP Technology UI Technology Web UI Technology Floorplan Manager
for Web Dynpro ABAP Fitting Web Dynpro to Your Needs Administrator Mode .
2. The Component Con guration screen is now displayed. Choose Con gure UIBB for Form UIBB (1).
3. On the next screen, choose the group to which the new eld is to be added. Choose Con gure Group.
4. The Con gure Group dialog box is displayed. Here you can select which of the available elds shall be displayed in the
GUIBB at runtime. The list of Available Fields should include the previously added component. Select this eld and choose
Add Fields. You can change the display sequence for the eld you just added. Then choose OK.
5. The new eld is now displayed on the Component Con guration screen. Here you can select the eld 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 elds will be displayed.
11/14/2019
Note
If the new UI eld is to be based on a customizable code eld, you create additionally a corresponding customizing table and
maintenance view using transaction SE54, and add a corresponding search help. You can then de ne a list of valid entries
using the maintenance view for the eld. In the GUIBB con guration, you can optionally change the UI element of the
corresponding eld to a dropdown box displaying the list of valid data.
Result
You have successfully added the new eld to your Web Dynpro application. Since the new eld is part of a BO node extension
include, the data that was entered is saved and retrieved successfully without any additional changes or modi cations to the BO
itself. The FBI-based Web Dynpro application itself also handles the data access without you needing to make any changes or
modi cations to the BO or the UI.
This approach to adapt the Web Dynpro screens applies not only to adding elds, but also to other screen changes, for example,
renaming labels and changing the sequence of elds and groups.
More Information
For more information about the BOPF enhancement framework, see SAP Note 1457235 .
For more information , see SAP Library for SAP NetWeaver on the SAP Help Portal at http://help.sap.com/nw702 . Go to section
Application Help and open the documentation for Function-Oriented View. Go to Application Platform by Key Capability ABAP
Technology UI Technology Web UI Technology Floorplan Manager for Web Dynpro ABAP .
Field Control
Use
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 elds, buttons, and groups on the user
interface at runtime if a data record ful lls 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 elds visible and mandatory for a speci c region or
country. This function helps organizations to ful ll 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 speci ed eld control in Customizing for SAP EHS Management under Foundation for EHS Management Settings for
Business Objects Specify Field Control .
Features
Field control provides the following features:
Pro les
Field control uses pro les to store the information about both the conditions that a data record must ful ll for eld control
to apply, and how the system then controls the user interface when eld control applies.
11/14/2019
You can set up a pro le to use the following conditions when determining if eld control applies:
Node Attribute Value
You can use pro les that are based on an entered value for a given eld (node attribute). For example, when you
have entered the value X for the Y eld, the corresponding pro le applies.
Authorization-Based Pro le
You can use pro les that adapt the user interface based on a user’s 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.
Function Class
You can use pro les that contain customer-speci c logic implemented by classes. This allows you to specify more
complicated logic for a eld if basing the pro le on a node attribute value is not sufficient.
You can set up a pro le to use the following property settings to control how the system applies eld control:
Attribute
You can specify elds 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 pro le. This makes it possible to apply eld
control settings for a given pro le 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 pro les whose conditions all apply in parallel for a certain node, but which de ne 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
con guration effort if you want to reuse settings in a eld control pro le.
Document Storage
Use
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 de ne the storage location for these documents, for example, in the database or in an
external content server.
Features
11/14/2019
Document storage provides the following features:
The connection to the Content Management Service is speci ed 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 con guring document storage for SAP EHS Management, see Customizing for SAP EHS
Management under Foundation for EHS Management Business Objects Specify Document Storage .
For more information about the Content Management Service, see the SAP Library for SAP NetWeaver 7.0 at
http://help.sap.com/nw702 SAP NetWeaver by Key Capability Application Platform by Key Capability Business
Services Knowledge Provider (BC-SRV-KPR) Content Management Service (BC-SRV-KPR) .
Creation of Change Documents

Use
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 ful lling your auditing requirements.
The type of change documents you can access depends on where you are in the application. For example, you can display change
documents only for actions and noti cations, if an action or noti cation is selected on the Tasks tab.
Under Display Change Document Objects (transaction SCDO), you can nd the delivered change document objects. (EHS change
document objects start with EH*.)
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 eld
User who made the change
Details about the change action
More Information
11/14/2019
For more information about which change document objects are delivered, see Display Change Document Objects (transaction
SCDO). EHS change document objects start with EHFND*, EHHSS*, and EHENV*.
For more information about change documents, see the SAP NetWeaver documentation on the SAP Help Portal at
http://help.sap.com/nw. Select your release and in section Application Help, open the SAP NetWeaver Library: Function-
Oriented View. Go to Application Server Application Server ABAP Other Services Audit Trail (BC-SRV-ASF-AT) Changing
Table and Data Element Logging Creation of Change Documents .
Roles
Use
In SAP EHS Management, you use speci c roles in the application to access content. You can use roles to support your EHS
business processes.
All roles support SAP NetWeaver Business Client. However, the roles can be used to generate Portal Contend for the SAP
NetWeaver Portal. For more information about creating Portal Content, see SAP Note 2083956 .
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, a PFCG role (SAP_EHSM_MASTER) is provided that contains the complete content of the SAP EHS
Management application. When creating user-de ned roles, SAP recommends you to use each master role as a template and to
remove the undesired functions. This ensures that no con gurations (for example, OBN settings) are lost.
Activities
The roles provided with SAP EHS Management contain speci c con guration settings, for example, object-based navigation
settings. To create custom roles without losing the con guration settings, proceed as follows:
1. Create your custom PFCG role.
2. Copy the menu structure from either delivery role SAP_EHSM_MASTER.
3. Remove all not required functions.
4. Generate the authorization pro le.
5. Assign the custom role to users.
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 role (SAP_EHSM_MASTER) for SAP EHS Management
as a template.
More Information
For more information about editing roles, see SAP Library for SAP NetWeaver on the SAP Help Portal at http://help.sap.com/nw74
. Go to section Application Help and open the documentation for Function-Oriented View. Go to Security Identity
Management User and Role Administration of Application Server ABAP Con guration of User and Role Administration Role
Administration Role Administration Functions .
11/14/2019
Alternatively, you can use the following link:
http://help.sap.com/saphelp_nw74/helpdata/en/e4/15e48efd6c11d296430000e82de14a/content.htm .
For more information about PFCG roles, see SAP Library for SAP NetWeaver on the SAP Help Portal at http://help.sap.com/nw74
. Go to section Application Help and open the documentation for UI Technologies in SAP NetWeaver. Go to SAP NetWeaver
Business Client SAP NetWeaver Business Client Administration Guide Role Maintenance in PFCG .
Alternatively, you can use the following link:

http://help.sap.com/saphelp_nw74/helpdata/en/4c/5bdc2a97817511e10000000a42189b/content.htm .
Roles for Health and Safety Processes

With component extension for SAP EHS Management, the following roles are delivered to support your health and safety
processes:
BI Content Analyst for HSS
Chemical Approver
Chemical Requestor
Corporate Health and Safety Manager
Environmental Manager
Hazardous Substance Manager
Incident Manager
Incident Reporter
Industrial Hygienist
Line Manager
Noti cation Recipient
Process Administrator
Safety Data Sheet Clerk
Safety Manager
Sampling Technician
BI Content Analyst for HSS

SAP_EHSM_HSS_BW_ANALYTICS
Use
The BI Content Analyst for HSS role is assigned to employees who are responsible for health and safety at their organization and
for analyzing key gures and statistics related to the management of environment, health, and safety. This person can display a
report launchpad that contains links to multidimensional reports and dashboards.
Integration
11/14/2019
This role is integrated in all scenarios.
Chemical Approver
SAP_EHSM_HSS_CHEMAPPR
Use
The Chemical Approver role is intended to be used as a template for any other business role that has to be involved in the
approval process of a chemical. The role can be assigned to employees who have to be considered as additional approvers directly,
or it can be used as a copy template to create new roles. Examples for additional approvers that might be added are occupational
health experts, plant security responsible, or members of the plant re brigade.
Integration
This role is integrated in the following scenario:
Approving chemicals
Chemical Requestor
SAP_EHSM_HSS_CHEMREQ
Use
The Chemical Requestor role is assigned to employees who introduce new chemicals to the company. Chemicals can be raw
materials used in the production process as well as auxiliaries or operating supplies needed to support or facilitate the operation
of a company. The chemical requestor has to initiate the chemical approval process. If the chemical is approved, the requestor
initiates the procurement process for this material.
Integration
Searching for chemicals
Requesting chemical approvals

SAP_EHSM_HSS_HSMGRCORP
Use
The Corporate Health and Safety Manager role is assigned to employees who are responsible for all health and safety-related
activities in a company. The corporate health and safety manager is responsible for specifying health and safety programs at a
corporate level and monitor how they are implemented into the different areas of the company. The corporate health and safety
manager sets goals that have to be reached over several years in order to improve the health and safety compliance of own
employees or third parties that work for the company.
11/14/2019
Integration
Monitoring workplace sampling processes
SAP_EHSM_HSS_ENVMGR
Use
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. He takes part in the chemical approval process to ensure that a new chemical that is introduced in the
company is checked from an environmental point of view.
Integration
Assessing environmental risks
Approving chemicals
Conducting control inspections

SAP_EHSM_HSS_HAZSUBMGR
Use
The Hazardous Substance Manager role is assigned to employees who are responsible for the continuous assessment of
hazardous substances to ensure that high standards of risk management are ful lled and regulatory requirements are met. The
hazardous substance manager is the main responsible person for the chemical approval and ensures that chemicals that are used
in the company are approved for from a regulatory point of view. During the chemical approval process, the hazardous substance
manager can select other roles to be involved in the approval. The hazardous substance manager is also responsible for the
chemical inventory management and provides regulatory driven reports containing chemical data like SARA 311, 312 or a list of
hazardous chemicals (Gefahrstoffkataster). In addition, the hazardous substance manager can conduct control inspections.
Integration
Approving chemicals
Providing regulatory reports for chemicals
11/14/2019
Incident Manager
SAP_EHSM_HSS_INCIDENT_MANAGER
De nition
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, veri ed, 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.
Use
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 speci c 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 work ows such as noti cation 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.
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 noti ed
Incident Reporter
SAP_EHSM_HSS_INCIDENT_REPORTER
11/14/2019
Use
The Incident Reporter role is assigned to the person who initially reports an incident. This can be any person with access to the
application, 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 application, 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.
SAP_EHSM_HSS_HYGIENIST
Use
The Industrial Hygienist role is assigned to employees who are responsible for ensuring that the workplace is compliant to health
and safety standards. The industrial hygienist is responsible for monitoring exposures, assessing health aspects and impacts,
implementing risk treatment programs for health risks, managing information about agents, conducting site (workplace)
inspections, and determining risk treatment measures (controls) and checking their effectiveness. This person also ensures that
the workers and the community are protected from potential health threats.
Integration
This role is integrated in the following scenarios:
Assessing health risks
Managing job information
Managing agent information
Implementing safe handling for chemicals
Approving chemicals
Creating and managing sampling campaigns
Creating and managing sampling methods
11/14/2019
Line Manager
SAP_EHSM_HSS_LINEMGR
Use
The line manager is responsible for a “line” in the organizational hierarchy for a product. This person has cross-functional
responsibilities that include managing personnel, assets, production, and taking responsibility for the EHS tasks in the line. The
line manager's main EHS goal is to ensure compliance with health and safety standards.
The line manager has the following responsibilities:
Ensure that people in the line are assigned to the correct locations and jobs.
Ensure that incidents are recorded and the relevant corrective and preventative measures (such as training) as well as
controls (such as personal protective equipment) are implemented.
Approve execution of risk assessments for the line.
Inform the line of risks in the area and how to prevent or minimize negative consequences.
Noti cation Recipient

SAP_EHSM_HSS_INCIDENT_NOTIFIED
Use
The Noti cation 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.
Process Administrator
SAP_EHSM_PROCESS_ADMIN
Use
The Process Administrator role is assigned to an employee in the IT department. This person is responsible for monitoring
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 Work ow system
Setting up jobs and work ows
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.
11/14/2019

SAP_EHSM_HSS_SDSCLERK
Use
The Safety Data Sheet Clerk role is assigned to employees who are responsible to handle incoming vendor safety data sheets for
chemicals that are used in the company. During the chemical approval process, the SDS clerk ensures that the relevant data from
the safety data sheet documents is entered into the system. For updated safety data sheets received from vendors, the SDS clerk
ensures the storage of the updated document as well as the update of the relevant SDS data in the system.
The SDS clerk usually has a certain level of chemical expertise in order to check the plausibility of the SDS content to ensure
consistent data with high quality. In case of inconsistencies this person discusses the issues with the vendor and requests
corrected SDSs from the vendor.
Integration
Entering chemical data
Safety Manager
SAP_EHSM_HSS_SAFEMGR
Use
The Safety Manager role is assigned to employees who are responsible for ensuring compliance with applicable safety
regulations. The safety manager is responsible for assessing safety aspects and impacts, implementing risk treatment programs
for safety risks, and monitoring the effectiveness of safety controls. To ensure compliance with safety regulations, the safety
manager communicates with employees and provides training courses with regards to job safety.
Integration
This role is integrated in the following scenarios:
Assessing safety risks
Assessing job hazard risks
Managing job information
Sampling Technician
SAP_EHSM_HSS_SMPLTECH
Use
11/14/2019
The Sampling Technician role is assigned to employees who are responsible for planning, preparing, and executing samplings as
required by the industrial hygienist in a sampling campaign. The sampling technician is also responsible for sending the samples
to a laboratory for analysis if they cannot be analyzed within the company and for entering the analytical results in the application.
Additionally, the sampling technician validates the samples based on calibrations performed during sampling and results of blank
samples that have been taken during sampling.
Integration
Planning and processing workplace sampling
Roles for Environmental Management

Processes
With component extension for SAP EHS Management, the following roles are delivered to support your environmental
management processes:
Environmental Technician
SAP_EHSM_HSS_ENVMGR
Use
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. He takes part in the chemical approval process to ensure that a new chemical that is introduced in the
company is checked from an environmental point of view.
Integration
Assessing environmental risks
Approving chemicals
Environmental Technician
SAP_EHSM_ENV_TECHNICIAN
11/14/2019
Use
The Environmental Technician role is assigned to employees who are responsible for the collection and keeping of measurement
data, as well as importing the collected data into the system for further processing. Each environmental technician takes
measurement data from measurement devices in the industrial plant or facility and ensures that the data is provided as requested
by the collection process. This role interacts and cooperates with the environmental manager in monitoring the consumption and
emission data within the industrial plant.
Roles for Product Safety and Stewardship

Processes
With component extension for SAP EHS Management, the following roles are delivered to support your product safety and
stewardship processes:
Basic Material Specialist
BI Content Analyst for PSS
Compliance Consumer
Compliance Engineer
Compliance Manager
Component Engineer
EHS Management Administrator
Basic Material Specialist

SAP_EHSM_PRC_BASMAT_SPEC
Use
The Basic Material Specialist role is assigned to employees who are responsible for selecting appropriate materials and surfaces
for design parts and for approving their release for use. The basic material specialist determines the speci c application of
materials and surfaces, and manages the material database.
Integration
The basic material specialist is a specialist for basic materials and surfaces and ensures compliance on basic material level.
BI Content Analyst for PSS

SAP_EHSM_PRC_BW_ANALYTICS
Use
The BI Content Analyst for Product Safety and Stewardship role is assigned to persons who are responsible for analyzing
product safety and stewardship assessments as well as the executed processes. The BI Content analyst for Product Safety and
11/14/2019
Stewardship can navigate to the report launchpad for the product safety and stewardship work area with access to all dashboards
and queries.
Integration
The BI Content analyst for PSS generates all kinds of reports out of the system. It is not necessarily one person that does all the
reporting. The BI Content Analyst for PSS role can also be splitted, providing all other roles with the reports and dashboards they
need for their work.
Compliance Consumer
SAP_EHSM_PRC_COMPL_CONSUMER
Use
The Compliance Consumer role is assigned to employees who are responsible for managing awareness of regulations and
compliance requirements. In addition, the compliance consumer can be responsible for the following tasks, depending on the
purpose:
Managing product knowledge and data
Con guring customer orders
Scheduling service requests
Researching and evaluating product data
Designing, testing, and analyzing components
This role can be adapted for use as the following subroles:
Purchasing agent
Sales and services representative
Mechanical engineer
Electrical engineer
Integration
The compliance consumer consumes released compliance information, for example, purchasing agent, sales and services
representative, mechanical engineer, or electrical engineer. The compliance consumer does not change any compliance-related
information but uses it to inform third parties (for example, customers and suppliers) or to be sure that a certain component or
basic material can be used in engineering.
Compliance Engineer
SAP_EHSM_PRC_COMPL_ENG
Use
11/14/2019
The Compliance Engineer role is assigned to employees who are responsible for monitoring daily operations that contribute to
ensuring compliance. The compliance engineer is responsible for the company compliance data set. The compliance engineer
manages compliance data in cooperation with the engineering teams and cooperates with the compliance manager to keep
regulations information up-to-date. This role is involved in material-based and component-based engineering changes and new
product reviews.
Integration
The compliance engineer executes and coordinates the daily work to enable product compliance. They work closely together with
engineering teams, the compliance manager, the component engineer, the basic material specialist and others to solve any
compliance-related problems. The compliance engineer coordinates compliance activities down the whole product structure, from
products and components on different levels to basic material and pure substances.
Compliance Manager
SAP_EHSM_PRC_COMPL_MGR
Use
The Compliance Manager role is assigned to persons who are responsible for monitoring compliance-related programs for
product lines and de ning policies and procedures for other departments to ensure compliance. The compliance manager
approves the manufacturing processes and equipment that will be used in production, and supervises design compliance.
Integration
The compliance manager supervises and organizes all product compliance-related programs on a higher level. They do not work
daily with the system.
Component Engineer
SAP_EHSM_PRC_COMPONENT_ENG
Use
The Component Engineer role is assigned to employees who are responsible for selecting and working with electrical or other
components to be incorporated into future products and for managing purchased components and their documentation. The
component engineer approves parts obtained externally, works closely with vendors, and ensures compliance by following the
established procedures and policies.
Integration
The component engineer is a specialist for components and ensures that they are compliant. They work closely together with:
Vendors to approve external components
Engineering teams to provide them with compliant components
The basic material specialist to ensure that the used basic materials are suitable for the component
The compliance engineer to help getting products compliant
11/14/2019
EHS Management Administrator

SAP_EHSM_ADMINISTRATOR
Use
The Administrator role is assigned to persons who monitor changes in master data for product compliance, compliance objects,
and the application log. This person also corrects data issues, enters data for customers and suppliers, and manually imports
incoming documents either from the front-end system or from an application server.
Integration
The administrator supervises the system, monitors the application log, maintains or imports basic data and deletes obsolete data,
if necessary. In case of problems with the system, the administrator assists the other roles in solving them.
Risk Assessment (EHS-MGM-RAS)

Use
You use this component to assess risk within your organization as it relates to the environment or health and safety of people. This
enables you to comply with regulations and gain a comprehensive insight into the situations that involve risk. This component
supports you in identifying, analyzing, evaluating, and managing risks. You can take the appropriate actions necessary to reduce
risk to acceptable levels and prevent any harmful effects to the health and safety of your employees and the environment. You can
also perform job hazard analyses to assess risk for a speci c job or activity.
To ensure safe handling of chemicals within your company, you can use this component to enter relevant information for
chemicals and use the information to assess risk for chemicals. Additionally, you can create documents, such as safety
instructions, that are used to inform employees about all health, safety, and personal protection relevant aspects of the chemicals
they use. This ensures regulatory compliance and protects the health and safety of workers that handle chemicals.
This component helps you reduce the cost of risk management by supporting and automating administrative tasks and processes,
which increases the efficiency of the people responsible for risk assessment as well as the reliability and cost-efficiency of
implementing controls.
If your organization implements strategies and processes to prevent incidents that affect the health, safety or environment of your
organization, you can use this component to support and automate risk assessment tasks and processes.
This component can support your organization if you use the ISO 31000 framework for assessing risk, and can assist
organizations in meeting the requirements of ISO 14001 and OHSAS 18001 management systems.
Integration
You can integrate with other SAP components to use data from those systems, or to transfer data to those systems.
For an overview of SAP EHS Management integration, see Integration (EHS-MGM-FND-INT).
For more speci c integration information for risk assessment, see Integration with Other Components.
11/14/2019
Features
You can access the features of risk assessment in the Health and Safety work center. Risk assessment supports people that
occupy one of the following roles:
Chemical Requestor
Chemical Approver
Line Manager
Safety Manager
Sampling Technician
For more information about the roles, see Roles.
Process
The following graphic depicts how you can use this component to support your risk assessment process:
11/14/2019
Risk Assessment at Your Organization and in the Application
The process of assessing risk includes organizational activities and speci c process steps in this component. Before performing
the risk assessment in the component, you prepare for risk assessment at your organization by establishing the context of the risk
assessment and examining internal and external factors that in uence the risk assessment. If chemicals are relevant to your
company’s health and safety processes, you must rst manage the chemicals within your organization and in the component
before they can be used in risk assessment.
After preparations are complete, you perform the following process steps in the solution:
1. Identify any risks.
2. Analyze the risks.
3. Evaluate the risks.
4. Treat the risks.
5. Monitor and review the risks.
11/14/2019
In addition to monitoring and reviewing risk in the component, your organization can also perform additional organizational
activities to further monitor and review risk.
While the process can end after completing these process steps, you may also view the process as a continuous loop in your risk
management system and return to the beginning.

00 47633737069263615

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

00 47633737069263615

Transféré par

Droits d'auteur :

Formats disponibles

11/14/2019

Component Extension for SAP EHS

Original content: https://help.sap.com/viewer/c2db47abe44e4aa7ab1be93e4c20ae18/6.0/en-US

For more information, please visit the https://help.sap.com/viewer/disclaimer.

Foundation for EHS Management (EHS-

Print Forms and Interactive Forms

Process Foundation (EHS-MGM-FND-WF)

Easy implementation of your business processes in the system as processes

Adaptation of a process to match country and region-speci c needs

Custom development capabilities

Statistical data collection and monitoring capabilities

PCOs and PCBOs

Process control business object (PCBO)

Process control object (PCO)

PCO and PCBOs in the Process Foundation

Use in Monitoring and Analyzing Processes

Process Con guration

You have read the topic PCOs and PCBOs.

Adapt existing process

Add new elds to store process-speci c data

Add new variants of a process

Create customer-speci c logic for a process in the PCO

Changing Work ow Templates

To change an existing work ow, copy it into the namespace Z.

Changing Work ow Templates

For more information, see Process Con guration.

3. Save and activate the changed work ow template.

Registering Work ow Templates

2. Open the work ow template in the standard system.

Queries and Export to Spreadsheet

Changing the Task Processor

Changing the Task Processor in the Back-End System

6. Enter the user of the new processor.

Continuing Execution of a Process with

Usage of Processes in the Application

You are authorized to call programs in transaction SE36.

Log Object Log Subobject Description

EHFND_FW WF_SCHEDULER General Scheduler Log

Displays information about the activities of

EHFND_FW WF_SCHEDULER_ITEM Scheduler Item Log

Displays detailed information about the

Print Forms and Interactive Forms (EHS-

Review data before transferring into a data record

Adding Print Forms and Interactive Forms

Form creation controller

These components are used in the Procedure.

Creating ABAP Dictionary-Based Structures

Creating Form Interfaces

1. Create the form interface in transaction SFP.

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)

Laying Out Forms

2. Choose the tab Object Binding .

3. Enter the data eld value for the default binding.

This method contains the following:

Form information that is con gured in Customizing as the

The process component-speci c form context