You are on page 1of 116

SAP EHS Management

General Configuration
Specify General Settings
Use
In this Customizing activity, you can configure the following general systems settings:

Default Language Key
By setting the default language, you determine the language for entering texts as well as the default target language for
translating texts. If texts do not exist in the language selected at logon, they will be displayed in this language.

Currency
Currencies are defined according to the international ISO standard.

Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.
2. If necessary, define additional entries.
A unique key must be assigned to each entry.

Specify General Settings
Use
In this Customizing activity, you can configure the following general systems settings:

Default Language Key
By setting the default language, you determine the language for entering texts as well as the default target language for
translating texts. If texts do not exist in the language selected at logon, they will be displayed in this language.

Currency
Currencies are defined according to the international ISO standard.

Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.
2. If necessary, define additional entries.
A unique key must be assigned to each entry.

Specify Active Languages
Use
In this Customizing activity, you can define the available target languages for translating free text fields in the system. If you
want to translate a free text, you can choose one of these defined languages and then translate the text into the chosen
language.
Standard settings

The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.
2. If necessary, define additional entries.
A unique key must be assigned to each entry.

Specify Field Control
Use
In this Customizing activity, you can specify field control for business objects in the SAP EHS Management (EHS-MGM)
component.
You can use field control to adapt the user interface to specific conditions of a data record. You specify these conditions and
how the system adapts the UI on the node level of a business object. You can, for example, set up field control to make specific
fields visible and editable on the user interface depending on the country or region of the data record. Field control is possible on
all nodes of a business object and for all properties of the node. You can also specify more than one profile to accommodate
each relevant set of conditions of a data record.
Prerequisites
You are familiar with the modelling and structure of the business objects of SAP EHS Management in the Business Object
Processing Framework (BOPF).
You are familiar with the legal reporting requirements of your country or region and the data that is required to be compliant.
Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.
2. If necessary, define additional entries.
To create new field control profiles, perform the following steps:
1. Specify the business object for which you want to use field control.
2. Specify the node of the business object for which you want to create a profile.
3. Make the settings for the profile. You can decide when field control applies at the node level based on the settings
you make for the following fields:

o

Authorization-Based Profile

o

Authorization Check Result

4. you can create regulations for business objects used in SAP EHS Management.) If you create more than one profile for a node. This way. for managing incidents. Standard settings . node. you can make settings for the merge strategy for each profile. you createthe regulations in this activity. or that enabled values always win (optimistic). you can use field control to display the Privacy Case and Additional Criteria radio buttons when you record data about injuries/illnesses that occurred in the United States. By default. you can define the property settings for the business object node in the subdialogs. There are certain injury/illnesses that are handled as privacy cases in the United States. for managing incidents. you can also specify how to propagate the settings to subnodes. In this case. You can use regulations as the conditional basis for applying field control settings and to control the forms available to the data record. that disabled values always win (pessimistic). Field Control for Merge Strategy Definition Specifies the strategy for merging profiles with different values specified for the attribute.o Function Class o Node Attribute Value (The system determines if field control applies in the order that the above fields are listed here. Use You can specify. After creating the profile. If your organization operates in countries and regions with specific regulatory requirements. these fields are not displayed. Create Regulations Use In this Customizing activity. If your organization has internal policy. for example. for example. you create the internal policy as a regulation in this activity. Example You use SAP EHS Management to record incidents that occur in the United States and are subject to OSHA requirements. for example. the merge strategy is pessimistic. These are settings that control the behavior and appearance of the user interface. The system gives priority to the optimistic profile when there is more than one profile. the system adapts a data record automatically according to a specific regulation and helps you fulfill regulatory requirements. In this step. action and association properties so that only one profile is returned and used for field control. Otherwise.

Further information For more information about field control. for example. If you want to create your own attachment schema. Activities 1. define additional entries. you must assign it to the respective ROOT nodes of the three delivered business objects. In this activity. The standard system is also delivered with an alternative configuration to connect to a separate file server. attachments and generated PDF reports. Standard settings The standard system is delivered with settings that use the content repository BS_ATF_DB_REPOSITORY and the content category BS_ATF_DB to store documents in the database. you can learn about setting up attachment types and assigning these to attachment schemas. see the Customizing activity Specify Regulations. For more information. the attachment schema needs to be assigned to the content category BS_ATF. The connection to the Content Management Service is specified and implemented by the attachment folder (ATF) of the business object (a reusable object for the BOPF environment in the SAP_BS_FND software layer). If necessary.The standard system is delivered with examples. 2. A unique key must be assigned to each entry. Activities Ensure that the settings for the Content Management Service are correct in Customizing for SAP NetWeaver under Knowledge Management -> Settings in the Knowledge Warehouse System -> Content Management Service. An attachment schema may be assigned for a given business object (BO) node that uses the dependent object attachment folder. Check the existing examples and adapt them as required. see Customizing activity Specify Field Control Specify Document Storage Use SAP EHS Management (EHS-MGM) uses the Content Management Service to store documents. Ensure that the settings for the attachment schema are correct for the SAP EHS Management business objects in Customizing for Cross-Application Components in activity Maintain Attachment Type Schema. Further information . This content category uses the content repository BS_ATF_CONTENT_SERVER. Note that you must specify these regulations further for use in incident management. To achieve this.

ensure that the following settings were made:  Maintain Runtime Environment: all settings  Maintain Definition Environment: o  Check Number Ranges Maintain Additional Settings and Services: o Maintain Standard Domain for Internet Mail . Activities Select the top node of the first section and choose the Perform Automatic Workflow Customizing pushbutton or F9. you can perform automatic customizing for workflows. Foundation for EHS Management->Process Foundation Basic Settings Perform Automatic Workflow Customizing Use In this Customizing activity.com under SAP Netweaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Business Services -> Knowledge Provider (BC-SRV-KPR) -> Content Management Service (BC-SRV-KPR).0 EHP 2 on SAP Help Portal at http://help. If you do not perform this activity. see SAP Library for SAP NetWeaver 7. To run EHS Management. Perform this step for all subsequent sections. the process foundation cannot support your business processes.sap.For more information about the Content Management Service. The activity is mandatory if you use the processes of the SAP EHS Management (EHS-MGM) component.

o Activate Send to Objects and HR Objects o Maintain Demo and Verification Environment  Classify Tasks as General: all settings  Guided Procedures: o Maintain Generation of Standard Tasks o Classify Generic Standard Tasks as General When you choose to perform automatic workflow customizing. see SAP Help Portal -> ERP Central Component Enhancement Package 4 -> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Business Services -> SAP Business Workflow -> Reference Documentation -> Workflow System Administration. only those activities that currently have the error status are executed automatically. and peform automatic workflow customizing again or manually perform customizing. . Further information For more information. you may need to make additional settings. If an activity still has the error status after performing automatic workflow customizing.

You can use the process definition to specify the workflows that are available where and when you want them in the application. You can also create a variant of a standard workflow to accommodate variations of the process. A process definition consists of the following information:  EHS Management component  Purpose  Variant  PCO class . you can specify the process definitions for processes handled by the process foundation.Specify Process Definitions Use In this Customizing activity. You can also exclude existing processes from process monitoring and process analysis.

for example. Activities 1. You can create a variation of the process for a specific country or region. If you want to extend your processes with additional functionalities in the SAP Business Workflow. If necessary. you have implemented a customer-specific PCO class to handle the process.Requirements You have set up the workflow system in the Customizing activity Perform Automatic Workflow Customizing for Foundation for EHS Management. For more information about extending or changing the PCO class. 3. If necessary. see Customizing activity Extend and Adapt Process in Foundation for EHS Management. select the Exclude checkbox to exclude a process from process monitoring and analysis. You can use this BAdI. Standard settings The standard system is delivered with examples. 2. BAdI: Create and Initialize Process Control Objects (PCBOs) Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. You can use this BAdI to implement customer-specific logic to adapt the processes in the system. define additional entries. Check the existing examples and adapt them as required. The PCBO creation BAdI is called each time the system creates a process control business object (PCBO). if your organization must comply with regulatory requirements in more than one country or region. A unique key must be assigned to each entry. Requirements .

you can activate the event type linkage to link the event creator and the event receiver for scheduled processes. by assigning a class name based on the name of your implementation. Save and activate your code. to recur every week for a year. Standard settings The standard system is delivered with the event type linkage deactivated. enter a short description for your implementation in the Implementation Short Text field. Note: You can also create an implementation for an Add-In and not activate it until later. Navigate back to the Change Implementation screen. the task is part of a process that must be scheduled and triggered again to occur the following week. In the dialog box. you can schedule the task. enter a name for the implementation of the Add-In and choose Create. Choose Activate. the system displays them in a dialog box. Activate Linkage for Scheduled Processes Use In this Customizing activity. and endmethod. double-click its name. the system displays a dialog box where you enter a name for the implementation. Activities . When the application program is executed. Save your entries and assign the Add-In to a package. 3. If you want to do this. 4. the code you created is run through. Standard settings This BAdI does not have a default implementation. When you schedule an action or notification in the application. so that the central user (event receiver) can schedule and trigger the processes for the user (event creator) that created and scheduled the action or notification originally. By activating the event type linkage. You have performed a consistency check without errors in the Customizing activity List Configured Processes for Foundation of SAP EHS Management. You must activate the linkage. 6. 7. 2. you allow a central user with batch administration authorizations (WF-BATCH) to schedule and trigger the corresponding process for the task. do not perform the following step: 8. The system displays the initial screen for creating Business Add-In implementations. and continue as follows: 1. Enter your implementation code between the method <Interface Name>~<Name of Method>.You have specified process definitions in the Customizing activity Specify Process Definitions for Foundation of SAP EHS Management. for example. you will notice that the system has populated the Name of the Implementing Class field automatically. If you choose the Interface tab. In the system. statements. On this screen. If implementations of this Business Add-In have already been created. Activities After you call the IMG activity. 5. You then choose one of them by choosing Create. To edit a method.

the system is set up correctly and you can execute the processes in the SAP EHS Management (EHS-MGM) component. You have performed the Customizing activity Specify Process Definitions for Foundation for EHS Management.For the following object. Requirements You have performed the Customizing activity Perform Automatic Workflow Customizing for Foundation for EHS Management. the checks are run and the result is displayed. activate the event type linkage: Object Category: ABAP Class Object Type: CL_EHFND_SCHEDULER_REPLANNER Event: TRIGGER_REPLANNING Check Configuration of Workflow System Use In this Customizing activity. . Upon executing the activity. If the checks are successful. you can perform several checks on the workflow system that is used in the process foundation.

Requirements You have specified process definitions in the Customizing activity Specify Process Definition for Foundation for EHS Management. The system displays the results of the process definition check in the report R_EHFND_WFF_PROCDEF_CHECK. and the technical information of process definitions. you can view the status. the instances. Activities Choose the Status traffic light icon to display details about the status of the configured process definition. Choose the List icon to display a list of the instances of the specified process in the report R_EHFND_WFF_PROCESS_LIST.List Configured Processes Use In this Customizing activity. From this list. you can display a list of the process definitions in the SAP EHS Management (EHS-MGM) component. Standard settings The system displays the configured processes automatically using the report R_EHFND_WFF_PROCDEF_LIST. This helps you ensure that the process definitions are configured correctly. .

such as once a day. Schedule the job to run at regular intervals. Activities 1. You define the job for the report R_EHFND_WFF_UPDATE_STATISTICS. the process foundation cannot collect all of the information about the processes. In the activity. This activity is mandatory if you use the EHS Management processes. Schedule Jobs for Process Statistics Use In this Customizing activity. This information is used by the workflow reporting and analytics functions in the SAP EHS Management (EHS-MGM) component. which can result in problems with the workflow reporting and analytics functions.Choose the Info icon to display technical information about the selected process in the report R_EHFND_WFF_PROCDEF_INFO. . If you do not perform this activity. 2. you can schedule a report to collect statistical information about processes on a regular basis. use the Job Wizard to specify the general data and schedule the job.

For more information. perform the activities described below: Adapt Existing Processes 1. see Note below.Extend and Adapt Processes Use In this activity. you must configure the corresponding tasks in the workflow inbox. 3. You can make the following changes:  Adapt existing processes  Add data fields to the PCBO  Add new variants of a process definition  Change the BAdI implementation for PCBOs  Extend or change the PCO class for a process Activities To extend and adapt processes in the following ways. you can learn about how to extend and adapt the process foundation in SAP EHS Management (EHS-MGM) to suit your customer-specific business processes. Note that if you add customer-specific dialog steps and these step appear in the user's inbox. 2. Make the desired changes in the copied template. Create a copy of the workflow template in the Workflow Builder that you want to modify. Activate the event binding for the CREATE event of the corresponding PCO class. .

Note SAP EHS Management uses the POWL-based inbox. For more information about implementing the BAdI. . enter it in the activity Specify Process Definition for the relevant process definition. you must configure the tasks in the workflow inbox in Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications -> Inbox. If you adapt processes and the corresponding workflow templates.4. Disable the event linkage for the old workflow template to prevent creating two workflow instances when the event occurs. After you have implemented the class. see the Customizing activity BAdI: Create and Initialize Process Control Objects (PCBOs) for Foundation for EHS Management. Change the BAdI implementation for PCBOs To change the implementation of the BAdI for the creation of the PCBOs. see the Customizing activity Specify Process Definition for Foundation for EHS Management. configure it in the BAdI. See also the corresponding process component to obtain the correct application ID and POWL type for the workflow inbox.  Create an own implementation of a PCO class by implementing the interface IF_EHFND_WFF_PCO. you can do one of the following:  Extend the default implementation CL_EHFND_WFF_DEF_PCBO_CREATION and add the required methods or overwrite existing ones. you can do one of the following:  Inherit and then modify the class of an existing purpose and variant that is delivered in the standard system (recommended). Add New Variants of a Process Definition You can create customer-specific variants of processes by adding a new definition with your own variant name. Add Data Fields to a PCBO You can add customer-specific data fields to a process control business object (PCBO) by modifying the extension structure in transaction SE11. For more information. After you create the PCO class.  Implement the IF_EHFND_WFF_PCBO_CREATION interface. Extend or Change the PCO Class for a Process If you want to implement a customer-specific PCO. or by extending the abstract base class for the PCO class CL_EHFND_WFF_ROOT_PCO.

If necessary. A unique key must be assigned to each entry. Specify Subjects Use In this Customizing activity. define additional entries. Check the existing examples and adapt them as required. Standard settings The standard system is delivered with examples.Specify Types Use In this Customizing activity. you can specify types for actions and notifications. 2. you can choose the type from the values you specify in this activity. you can select the Default checkbox for the corresponding entry. If you want the system to display a value on the user interface automatically. When you create an action or a notification in the SAP EHS Management (EHS-MGM) component. Activities 1. you can specify subjects for actions and notifications. .

Standard settings The standard system is delivered with examples.When you create an action or a notification in the SAP EHS Management (EHS-MGM) component. If necessary. . you can select the Default checkbox for the corresponding entry. If you want the system to display a value on the user interface automatically. If necessary. A unique key must be assigned to each entry. Activities 1. you can specify the effectiveness for actions and notifications. 2. Requirements You have made the settings for Customizing activity Specify Types for Foundation for EHS Management. Activities 1. When you create an action or a notification in the SAP EHS Management (EHS-MGM) component. 2. Specify Effectiveness Use In this Customizing activity. Check the existing examples and adapt them as required. Check the existing examples and adapt them as required. Standard settings The standard system is delivered with examples. you can select the Default checkbox for the corresponding entry. you can choose the subject from the values you specify in this activity. you can choose the effectiveness from the values you specify in this activity. define additional entries. If you want the system to display a value on the user interface automatically. define additional entries. A unique key must be assigned to each entry.

The template stores the standard values for the action or notification. you can select the Default checkbox for the corresponding entry.Specify Protection Goals Use In this Customizing activity. 2. During processing. Activities 1. If you want the system to display a value on the user interface automatically. Specify Templates Use In this Customizing activity. you can specify the protection goals for actions and notifications. The system automatically retrieves the values for the following fields from the template and fills them in on the user interface:  Type  Subject  Category  Notification  Description You can use templates to speed up the process of creating actions and notifications. Requirements You have made the settings in Customizing for Foundation for EHS Management for the following activities: . define additional entries. you can specify templates for actions and notifications that you create in the SAP EHS Management (EHS-MGM) component. you can choose the protection goal from the values you specify in this activity. When you create an action or a notification in the SAP EHS Management (EHS-MGM) component. you can choose an action or a notification from the template. If necessary. A unique key must be assigned to each entry. Check the existing examples and adapt them as required.

Check the existing examples and adapt them as required. If necessary. You can use this BAdI to return the specific workflow task and to integrate your business processes. BAdI: Define Process Steps Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. Note that you must scroll all the way to the right to see all of the settings for a template. The process can contain the following people:  Responsible Person  Implementor  Approver In the components of SAP EHS Management. workflow tasks are used to perform the work. there are specific processes that involve action. A unique key must be assigned to each entry. In these processes. Standard settings In the standard system. You can use this BAdI to see the persons that are involved in the process step of a given work process. the following BAdI implementations are activated:  EHFND_ACTION_BADI The BAdI is filter-dependent and not designed for multiple use. Activities 1. Activities . 2. Specify Types  Specify Subjects  Specify Effectiveness  Specify Protection Goals Standard settings The standard system is delivered with examples. define additional entries.

In this Customizing activity. do not perform the following step: 8. The available languages are determined . Enter your implementation code between the method <Interface Name>~<Name of Method>. Note: You can also create an implementation for an Add-In and not activate it until later. the code you created is run through. Choose Activate. 6. Save your entries and assign the Add-In to a package. In the dialog box. 5. Navigate back to the Change Implementation screen. double-click its name. If you choose the Interface tab. you will notice that the system has populated the Name of the Implementing Class field automatically. The system displays the initial screen for creating Business Add-In implementations.After you call the IMG activity. and endmethod. 7. If implementations of this Business Add-In have already been created. by assigning a class name based on the name of your implementation. You then choose one of them by choosing Create. the system displays a dialog box where you enter a name for the implementation. in legal and internal reporting or as inquiry questionnaires. If you want to do this. Each form can exist in multiple languages. You can use forms. 4. To edit a method. you can specify and configure forms to integrate them into the application. Save and activate your code. statements. the system displays them in a dialog box. and continue as follows: 1. 3. On this screen. When the application program is executed. 2. Specify Forms Use Forms contain data for a business object. for example. You can also assign the languages in which the forms are available. enter a short description for your implementation in the Implementation Short Text field. enter a name for the implementation of the Add-In and choose Create.

internal forms).com/ for SAP EHS Management under Foundation for EHS Management -> Print Forms and Interactive Forms (EHS-MGM-FND-FRM) -> Adding Print Forms and Interactive Forms. Furthermore. Requirements The configured classes (Form Controller. 2. If necessary. Standard settings The standard system is delivered with examples. If a dialog for accepting the data exists. define additional entries. Example Form name: INC_INFO_WITNESS Description: Incident Information Questionnaire for a Witness Form type: SAP Interactive Form Form category: Questionnaire Form creation controller: CL_EHFND_FW_ADS_FORM_CR_CTRL Data provider: CL_EHHSS_AIF_INC_WITN_Q_DPROV Name of form object: EHHSS_INC_AIF_INC_WITN Further information For more information about adding new forms (for example. the Form Object (Form Repository Object of transaction SFP) must be active and the corresponding interface structure must be the same as the one that is returned by the GET_DATA method of the Data Provider. Furthermore. the system uses the fallback language. you can translate it using transaction SFP and choosing Goto -> Translation. see SAP Help Portal at http://help. if relevant. Check the existing examples and adapt them as required. Activities 1.dynamically at runtime. If the requested language is not available. If required. 3. you can specify one language as a fallback language. 4.sap. If the form belongs to a questionnaire and you would like to store the data within an inquiry process. If you need the form in an additional language. . you have to set the form popup name 5. A unique key must be assigned to each entry. the Inbound Persister) must be available and active. Data Provider and. you can also add the Configuration for Accepting Data if a specified Web Dynpro configuration ID has to be used. define the Inbound Persister.

4. Assign the forms and select a default form. 2. these form groups allow an easier selection of the required form. you assign forms to the defined form groups. In a second step. . Requirements In Customizing for SAP EHS Management under Specify ADS Forms. you have defined the available forms. Define a logical name and a description for the form group. Activities 1.Specify Form Groups and Assign Forms Use In this Customizing activity. Assign a component for the form group. if you want to send an inquiry. Standard settings The standard system is delivered with examples. One form group can contain multiple forms. For an automatic selection. For example. you can select only a form of the inquiry form group instead of all available forms in the system. Select a form group and choose Assign Forms to Form Groups. In the incident recording. you can define one form of a group as a default form. 3. you can define into which groups you want to subdivide forms and assign each form group to a component.

and specific data from components that you may have already integrated. on the SAP Easy Access screen. see Notes below. you can specify the RFC destinations individually in this activity. data from the Materials Management (MM) component.Specify Destinations for Integration Use In this Customizing activity. Requirements You have defined RFC connections of connection type 3 (ABAP connection). For more information about the data that you cannot access via remote access. choose Tools -> Administration -> Administration -> Network -> RFC Destinations.0 (Basis 700) or higher for the remote system of your Quality Management system. You can access the data in those components directly on your local system or using an RFC connection to a remote system. Access to Data Available via a Remote System If you want to use data that is stored in a remote system. You can specify a customer-specific name for the RFC destination. You can access this data via the local system only. To check and define RFC connections. You have ensured the following:  You are using SAP ERP 6. you can specify destinations for integrating other SAP components into the SAP EHS Management (EHS-MGM) component. such as data from Customizing. . You can integrate the following components:  Business Partner  Customer Service  Human Resource Management  Plant Maintenance  Quality Management Access to Data Available via the Local System Only The system cannot read some data via remote access. Some data is available only on the local system.

If it is necessary to improve performance when integrating to a remote PM system. and CS Attendance and absence types 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. To make this data available on the local system. T77ED. You can access data from the local system only. Activities To access data from a remote system. Enter an existing RFC destination (connection type 3) for the specified remote system. Notes You must access certain data directly on a local system. TB003T Material number and material description from the material master Table T005U Table T005T Table T002T Table TQ80 Table T554S and T554T Table T502T Table TB027T Infotype 1039 and tables T77DB. for example.70 Extension Set 2. T77DT. You are using R/3 Enterprise 4. you can distribute the relevant HR master data between the PA-OS system and the EHS-MGM system. Standard settings The standard system is delivered without RFC destinations. . Note: The remote system for PM assets and for PM notifications is always the same system. a distribution limited to the basic infotypes is sufficient.  Table ILOA: Create an extension index with fields ILOAN and SWERK.  Table IFLOT: Create an extension index with fields TPLNR and EQART. The assignment of a user to employee (infotype 0105) for workflows must be done in the HR system.00 (Basis 620) or higher for the remote system of all other systems. since the EHS-MGM applications only require specific PA-OS data. T77ET Table T554S Note that to make organizational data from PA-OS available in the local system. using an Application Link Enabling (ALE) or by replicating data from Customizing. QM. you can create customer-specific indices on the remote PM system. The users themselves must be maintained in the local system. The distributed organizational data cannot be changed from the EHS-MGM applications as the system settings only allow read access. including organizational units and persons in PA-OS Table/Object Tables TB003. perform the following steps: 1. The following is a list of the data required on the local system and the table or object where it is located: Data Required in Local System Business partner roles Plants and plant descriptions Material and material description Currencies and exchange rates Region texts Country texts Language texts Notification types for PM. 2. The following are example indices that you can create:  Table EQUI: Create an extension index with fields EQUNR and EQART. Choose the remote system for the destination type. you can distribute it. However.

the user cannot create a notification and receives an error message. 2. The task will be filled with the following: Sort number: 1 (constant) Task text: Task description (short) Task long text: Task description 3. are visible on the user interface. 4. You have ensured one of the following with respect to mandatory fields in notifications: o The desired notification types do not contain any mandatory fields in the Customizing activity Define Screen Templates for Cross-Application Components. Plant Maintenance (PM). o Fields that you want to be mandatory exist in SAP EHS Management. You have not defined any allowed changes for the desired notification types in the Customizing activity Allowed Change of Notification Type for Cross-Application Components. If you have specified mandatory fields that do not exist in SAP EHS Management. one task is created in the notification. You have ensured that the desired notification types have internal (and not external) number range assignments. You have specified destinations for the integration of the Quality Management (QM). The following requirements apply only to the notification types that you want to use in SAP EHS Management: 1. and Customer Service (CS) components in the Customizing activity Specify Destinations for Integration for Foundation for EHS Management.Specify Notification Types Use In this Customizing activity. Standard settings . you can specify the notification types to use in the SAP EHS Management (EHS-MGM) component. You have ensured that the desired notification types contains tasks in the Customizing activity Define Screen Templates for Cross-Application Components. You must specify the notification types here in order to choose the following notification categories later in the application:  Quality notifications  Maintenance notifications  Service notifications Requirements You have defined notification types that you want to use in SAP EHS Management in the Customizing activity Define Notification Types for Cross-Application Components. For each action or notification in SAP EHS Management. and are set as mandatory in the Customizing activity Specify Field Control for Foundation for EHS Management.

If necessary. enter the value IE. define additional entries. In this Customizing activity. To define a number range interval for internal number assignment. Check the existing examples and adapt them as required. Specify Number Range Intervals for Location ID Use A unique number is assigned to each record created during processing in SAP EHS Management. Activities 1. 6.The standard system is delivered with examples. you can define number range intervals for the location ID. 2. . A unique key must be assigned to each entry. Standard settings The standard system is delivered with a predefined set of intervals for the location ID number range. Activities 5. Display the existing number range intervals for the location ID.

you can schedule the background job to run less frequently. Configure Periodical PM Synchronization Use In this organizational activity. set the Ext indicator. You can use the PM integration to import locations from PM and also to link existing locations to PM technical objects. Schedule report R_EHFND_SYNCEAM_LOCATION to run as a background job once a day. Note that the background job queries all integrated technical objects for changes. The individual number range intervals must not overlap. this may create additional load for the SAP EHS Management and PM system. If the number range interval is intended for external number assignment. Specify the limits of the number range interval. Note that you also synchronize the data of individual locations when you open the location's master data maintenance screen or link it to a technical object. Ensure that you have sufficient authorizations to read from the PM system and to update locations. Requirements  You have enabled PM integration in Customizing activity Enable/Disable PM Integration. If the PM data rarely changes. you can enable or disable the integration for locations with the Plant Maintenance (PM) component. Enable / Disable PM Integration Use In this Customizing activity.3.com -> Background Processing -> Job Scheduling Explained -> Scheduling Background Jobs.sap. you cannot disable the integration. 4. Depending on the number of objects that are integrated. Once the PM integration has been enabled and used. there are locations linked to a technical object in PM. that is. . 2. 5. Activities 1. Further information For more information about scheduling background jobs.  You have linked locations to PM technical objects. you can learn about configuring a background job to synchronize master data when you integrate locations from the Plant Maintenance (PM) component. Save your changes. see SAP Help Portal at http://help. Note that this setting does not affect other points of integration with PM in the application.

define additional entries. If necessary. Activities 1. 2. Standard settings The standard system is delivered with examples. The authorization groups are used in the authorization checks for the location. Standard settings The standard system is delivered with examples. If necessary. you can define authorization groups. Activities 1. Check the existing examples and adapt them as required. You can assign authorization groups to locations. . A unique key must be assigned to each entry.Specify Authorization Groups Use In this Customizing activity. you can restrict access to certain locations to specific users. You can use the location type to search for a location. Check the existing examples and adapt them as required. you can define the type of location. A unique key must be assigned to each entry. All actions performed inside the location structure ascribe to the authorizations for the location. 2. define additional entries. Specify Location Types Use In this Customizing activity. This way. There are no separate authorization groups for the location structure.

Activities To integrate a map. perform the following steps: 1. Requirements You have a map provider that is capable of interpreting an address string and displaying it on a map. Example Map providers that offer URL parameters can be integrated as a Web Dynpro URL CHIP. 3. 2. In this enhancement configuration. Create an enhancement of the Location Side Panel (Web Dynpro Configuration: EHFND_LOC_OIF_SIDE_PANEL). this will be a URL CHIP (see the example below). This enables users to visualize the position of a location on a map. In most cases. they will take priority over the address. Create a Web Dynpro CHIP that is capable of interpreting an address string and displaying it on a map. integrate the Web Dynpro CHIP that you created for displaying the map. the map will not be displayed automatically. The address string is built from the address fields entered in a location. If geographical coordinates are specified. otherwise. Use the "EHFND_LOC_ADDRESS" tab to enable automatic wiring (tagging). Create a side panel entry for the map in the embedded side panel.Configure Integration of Map Use In this organizational activity. You can implement the map function by using a third party CHIP to interpret and display the string parameter from the location address. Standard settings The standard system is delivered without an integrated map. you can learn about how to enhance the location Web Dynpro to include a map function in the side panel. An example URL would be: http://your-map-provider/map?address=<EHFND_LOC_ADDRESS> . The location provides tagging for the tag name EHFND_LOC_ADDRESS.

see the following Customizing activities for Foundation for EHS Management:  Specify Field Control  Create Regulations  Specify Attachment Type Schema Process Foundation . you can enter texts manually. Further information For more information about configuring Web Dynpro CHIPs and the Web Dynpro Side Panel.sap. General Configuration and Settings for Business Objects In incident management. you will find information about the foundation Customizing activities and their relevance to incident management. For more information. For more information. see SAP Help Portal at http://help. Below. and enter amounts in a given currency.The <EHFND_LOC_ADDRESS> tag will be automatically completed with the current location's corresponding address string. support you in fulfilling regulatory requirements. and store attached documents. you must first process Customizing for the Foundation for EHS Management (EHS-MGM-FND) component. see the following Customizing activities for Foundation for EHS Management:  Specify General Settings  Specify Active Languages You can customize the business objects used in incident management to use field control.com -> Web Dynpro for ABAP -> Web Dynpro ABAP: Development in Detail -> Advanced Concepts -> Web Dynpro ABAP Page Builder -> and the following topics:  Enhancing Web Dynpro Applications with a Side Panel  Creating Side Panels  Creating CHIPs Incident Management Configure Foundation for EHS Management Use Before performing the Customizing activities under Incident Management. translate these texts into other languages.

display the configured processes. For more information. or to prevent future incidents from occurring. For more information. For more information.You can customize the process foundation to support your incident-specific processes. For more information. you can perform checks on the system. you can configure the settings for actions and notifications. see the following Customizing activities for Foundation for EHS Management:  Specify Types  Specify Subjects  Specify Effectiveness  Specify Protection Goals  Specify Templates  BAdI: Define Process Steps Print Forms and Interactive Forms Forms necessary for recording incident details and reporting incidents are integrated into the incident recording process. You can configure the available forms and their grouping. for example. In Customizing. see the following Customizing activities for Foundation for EHS Management:  Specify Forms  Specify Form Groups and Assign Forms Integration In incident management. and collect statistics about your processes. see the following Customizing activities for Foundation for EHS Management:  Specify Process Definitions  BAdI: Create and Initialize Process Control Objects (PCBOs)  Extend and Adapt Processes Once you have configured processes for incident management. time data from Personnel Time Management (PT). person information from Personnel Management (PA) and SAP Business Partner (BP). you can specify actions and notifications in response to incidents. you can use data from other SAP components. assets from Plant Maintenance (PM). see the following Customizing activities for Foundation for EHS Management:  Specify Destinations for Integration . For more information. see the following Customizing activities for Foundation for EHS Management:  Check Configuration of Workflow System  List Configured Processes  Schedule Jobs for Process Statistics Actions During incident recording. and notification types from Cross-Application Components. materials from Material Management (MM).

as well as notes about the data that you can access only on your local system. and EHFND_TEXT_COLLECT. Further information For more information about SAP NetWeaver Enterprise Search. see SAP Help Portal at http://help. see the following Customizing activities for Foundation for EHS Management:  Specify Number Range Intervals for Location ID  Enable / Disable PM Integration  Configure Periodical PM Synchronization  Specify Authorization Groups  Specify Location Types Configure Embedded Search Use In this organizational activity. create real-time indexing. 2. To activate the search function. For more information. for example.  Specify Notification Types  Check Authorizations for Person Information  Specify Relevant Subtypes for a Party Infotype  Specify Contractual Relationships Locations You can use locations in incident management to describe where an incident occurred. for scheduling indexing once a week or for a manual start. you need to make the following additional configurations: 1. Create a search object connector from the EHHSS_BO_INCIDENT template in EHS Management. you can learn about using the Embedded Search service in the SAP EHS Management (EHSMGM) component. Requirements You have the SAP_ESH_LOCAL_ADMIN role assigned to your user. . you must first make the general settings in Customizing for SAP NetWeaver under Search -> Embedded Search.sap.Note that the documentation for this activity contains information about specifying destinations to make integrated data available. Activities If you want to use the NetWeaver Enterprise Search. USER_AUTHORITY. All other object types contain Customizing data and only need to be indexed as required. Schedule indexing for the search object connector as follows: for the object types EHHSS_BO_INCIDENT.com -> SAP NetWeaver Enterprise Search.

Specify the object for which you want to define a number range interval. is saved. To transport the number range interval. select Interval -> Transport. you can define number range intervals for the following number range objects:  EHFNDACTID – Action Identifier  EHFNDLCNID – Location Identifier  EHFNDPSEID – Process Setup ID  EHFNDRPTID – Report ID  EHHSSCASID – Person Injured External Case ID  EHHSSINCID – Incident Management Identifier  EHHSSPIID – ID for initial persons This is required for PERID conversion. If the number range interval is intended for external number assignment. Specify Regulations Use In this Customizing activity. The individual number range intervals must not overlap. Display the existing number range intervals. That is. you can specify which regulations apply to a certain incident group. 5. Activities 1.Specify Number Range Intervals for EHS Management Use A unique number is assigned to each record created during incident recording in SAP EHS Management. The number status. all existing intervals are deleted so that only the new number range intervals are available in the target system. numbers are always assigned sequentially. region. category. set the Ext indicator. In this Customizing activity. 6. . The next assigned number follows on from the number assigned to the object before the transport. and country. 4. incident category. however. country and region. Standard settings The standard system is delivered with a predefined set of intervals for the number range objects mentioned above. The system uses these settings to provide the regulatory information for processing the incident data records that have the specified group. Caution When you transport the newly-defined number range intervals. To define a number range interval for internal number assignment. 2. Specify the limits of the number range interval. enter the value IE. The appropriate number range object determines the number automatically by the system. 3.

The process foundation of the SAP EHS Management (EHS-MGM) component makes integration with workflows possible. A unique key must be assigned to each entry. Check the existing examples and adapt them as required. define additional entries. If necessary. Standard settings The standard system is delivered with examples.Requirements You have created regulations in the Customizing activity Create Regulations. Activities 1. Adapt Workflows for Incident Mangement Use In this activity. you can learn about the organizational activities for adapting the workflows of SAP Business Workflow to suit your customer-specific processes. You can adapt workflows to your processes in the following ways:  Change the workflow template  Add steps within a process  Call further logic from a workflow task (process step)  Use a dispatcher to send notifications about changes to the data record . 2.

You have checked the processes by implementing the Customizing activity List Configured Processes for Foundation for EHS Management.Requirements You have specified processes for the health and safety (HSS) component in the Customizing activity Specify Process Definitions for Foundation for EHS Management.EHHSS_HRANTF CL_EHHSS_PCO_INC_HR_ABS_NOTI 500051 .EHHSS_RPT_CR CL_EHHSS_PCO_INC_REPORT_GEN Activities To adapt workflows. If you want to use this functionality.EHHSS_ACT_PM CL_EHHSS_PCO_INC_ACTION_PM 500037 . do not make changes to the current process definition for the incident lifecycle process in the Customizing activity Specify Process Definitions. The standard system is delivered with settings for a fatality notification functionality.EHHSS_APPR CL_EHHSS_PCO_INC_APPROVAL 500004 .EHHSS_NOTI CL_EHHSS_PCO_INC_NOTIFIC 500005 .EHHSS_INQY CL_EHHSS_PCO_INC_INQUIRY 500003 .EHHSS_REPORT CL_EHHSS_PCO_INC_REPORT 500036 . the system starts the notification workflow for each person.EHHSS_INC CL_EHHSS_PCO_INC_LC 500002 . When a fatality is recorded in incident management. this functionality raises the event FATALITY_OCCURRED of the PCO in the incident lifecycle process (CL_EHHSS_PCO_INC_LC). The workflow retrieves the people to be notified.EHHSS_ACT CL_EHHSS_PCO_INC_ACTION_STD 500006 .EHHSS_DPAT CL_EHHSS_PCO_INC_LC 500031 . Then. The following workflow templates are delivered with the corresponding PCO class and event: WF Template PCO Class Name and Event 500001 .EHHSS_ACT_CS CL_EHHSS_PCO_INC_ACTION_CS 500038 . and the system assigns these people to workflow task 500086. Standard settings The standard system is delivered with examples.EHHSS_HR_ABS CL_EHHSS_PCO_INC_HR_ABSENCE 500040 .EHHSS_INV_LC CL_EHHSS_PCO_INV_LC 500032 . you can perform the following activities: .EHHSS_ACT_QM CL_EHHSS_PCO_INC_ACTION_QM 500039 .EHHSS_INVSTP CL_EHHSS_PCO_INV_STEP 500034 .

Create further steps and (if necessary) workflow tasks in the customer-specific namespace in the Customizing activity Define Tasks and Actions for Cross-Application Components. Note: this is the architecture that SAP EHS Management follows. or copy the delivered template to the customer-specific namespace. start the dispatcher workflow and extend the workflow template as required. It is recommended to inherit from the delivery class and adapt it with further public methods. To include your business logic.  You can add logic that can be called from a workflow task (process step) by performing the following steps: 1. Use the standard event (WORKITEM_COMPLETED) if you open a dialog and the workflow has to wait for an event. You can change the process flow directly in the workflow template (in the Workflow Builder). Configure Process Definitions Use In this Customizing activity. After you have finished implementing and adapting the workflow template.  You can use the dispatcher workflow to react to changes in the incident with an automatic notification. use one of the following two options: o Implement the logic directly in the PCO method. Change the workflow template (or copy the delivery to the customer-specific namespace) 2. Standard settings The standard system is delivered with examples. you must define the new event on the PCO class. configure the new PCO class in the process definition in the Customizing activity Configure Process Definitions for Incident Management. You have ensured that the linkage between PCO classes and the corresponding workflows of SAP Business Workflow is correct by implementing the Customizing activity List Configured Processes for Foundation for EHS Management. To add to the current changes that trigger a notification via the dispatcher process. 3. For the dialog to raise the new event to continue the workflow. Activities . Requirements You have specified processes for the health and safety (HSS) component in the Customizing activity Specify Process Definitions for Foundation for EHS Management. Activate the workflow template. Add the new tasks to the workflow inbox configuration in the Customizing activity Assign Task IDs to POWL Types for Cross-Application Components. If you want to use a more specific event. 3. o Implement the logic in a BOPF action of the corresponding process control business object (PCBO). 2. 4. Create a PCO class that inherits from the delivered class of the process that is specified in the Customizing activity Configure Process Definitions. Enter the application ID EHHSS_INBOX and the POWL type EHHSS_INBOX_TYPE for your task. you can configure the processes used in the incident management application of the SAP EHS Management (EHS-MGM) component.  You can add additional steps within a process by performing the following steps: 1. you can use the static method RAISE_WF_EVENT of the root PCO CL_EHFND_WFF_ROOT_PCO.

The standard system is delivered with default roles. Note that entries you change in this activity are changed as well in the Customizing activity Specify Process Definitions for Foundation for EHS Management. If necessary. select the Exclude checkbox to exclude a process from process monitoring and analysis. It is critical that you execute this activity if you want to use the process foundation to support your business processes. 2. You have assigned the roles used in this report to the required users in the transaction PFCG. Requirements You have set up the workflow system in the Customizing activity Perform Automatic Workflow Customizing for Foundation for EHS Management. define additional entries. 3.1. A unique key must be assigned to each entry. Check the existing examples and adapt them as required. Activities . If necessary. there are no agents assigned to the workflow tasks used in incident management. you can assign default roles to workflow tasks that are used in the incident management application in SAP EHS Management (EHS-MGM). Assign Default Roles to Workflow Tasks Use In this Customizing activity. Standard settings In the standard system.

see the report R_EHHSS_CONFIG_TASK_ROLES. This activity is critical if you want to uses forms for reporting incidents. organization-internal recipients. or insurance companies. and country in Customizing activity Specify Regulations for Incident Management. for example. Further information You can assign roles manually to tasks by opening each task in transaction PFTC_CHG. to legal authorities. For more information about the tasks and the roles that are assigned by this activity. execute this activity once.To implement the standard setup and automatically assign the roles. You have specified forms in the Customizing activity Specify Forms for Foundation for EHS Management. incident category. You have specified regulations for the incident group. The system makes these forms available in the data record only if the corresponding regulation applies. Requirements You have created regulations in the Customizing activity Create Regulations for Foundation for EHS Management. Standard settings . region. Assign Forms to Regulations Use In this Customizing activity. you can assign the forms that are relevant to a specific regulation.

and for the incident group for injury/illness (EHHSS_IGR_OCC_INC)  OSHA 301 report form (OSHA_301) is assigned to the OSHA regulation (EHFND_US_OSHA) as a legal report When you choose to add a report form to the data record. you can generate offline forms that are used for recording a near miss or a safety observation. You use the following settings delivered in the standard system:  OSHA regulation (EHFND_US_OSHA) specified for the United States (US). the system proposes the OSHA 301 form.The standard system is delivered with examples. Standard settings The standard system is delivered with examples. Further information . otherwise. If you have created an internal regulation in Customizing activity Create Regulations and the corresponding internal forms in Customizing activity Specify Forms. You can store the forms on a medium (such as an Intranet or a public file share) that can be accessed by all persons who should be able to use them to report such events. for incidents (001 Incident). Activities 1. an exception may occur. If necessary.Form for recording safety observations offline Activities Select the form for offline recording in the language you require. Requirements You have specified the offline forms in the Customizing activity Specify Forms for Foundation for EHS Management. for example. you only select a form for offline recording. 2. define additional entries. 3. Check the existing examples and adapt them as required. Ensure that when you generate the form. Example An incident involving a work-related injury occurred in the United States and is subject to OSHA reporting requirements. You can use the following example forms for offline recording:  INC_OFFLINE_REC_NM . you can assign these forms to the internal regulation. and store it on a public medium. Generate Forms for Offline Recording Use In this Customizing activity.Form for recording near misses offline  INC_OFFLINE_REC_SO .

The form is sent by e-mail to the system. In this Customizing activity. If you use an asterisk (*) as the value.If you use the example forms delivered in the standard system. For more information about setting up the inbound handling of forms.  Your company's e-mail system is set up in such a way that it forwards the e-mail to the SAP EHS Management component based on the e-mail address that is configured for the form. However. you can define how the system processes such inbound e-mails by configuring the e-mail exit handler for each e-mail address that should receive the relevant form. this inbound handler is called for each e-mail address. Requirements  You have configured the inbound e-mail address for each form in the Customizing activity Specify Forms. it is recommended that you use the recipient address(es) of the forms that are configured. It logs the e-mails that are received using the SAP Application Log.  You have assigned the PFCG role SAP_EHSM_HSS_INCIDENT_EML_REC to the user SAPCONNECT. You can use transaction SLG1 to view the logs by entering the following parameters: Object: EHHSS_BO_INC Subobject: EHHSS_AIF_INC_INBD Activities In this Customizing activity. The system attaches the returned form to the relevant workflow and the business process continues. see Define InboundProcessing for E-Mails. Standard settings There is a default exit handler for EHS Management: CL_EHHSS_INC_INB_PROC_BCS. Define Inbound Processing for E-Mails Use An e-mail inbound process is often required in the SAP EHS Management (EHS-MGM) component. For example. where the e-mail inbound handler creates a data record for the near miss or safety observation using the inbound persister of the corresponding form. the recipient of an inquiry completes a form and sends it back to a defined e-mail address. you can record safety observations and near misses offline and choose the Send pushbutton in the form to submit it to the incident manager.  Document Class: * . This role contains the authorization profiles needed to receive and process e-mails. you should specify the following parameters:  Communication Type: Internet Mail  Recipient Address: Specify the e-mail address(es) that are configured for the corresponding forms.

Check the existing examples and adapt them as required. Activities 1. In this case. create a new class that inherits from CL_EHHSS_INC_INB_PROC_BCS. go to transaction SE24. A unique key must be assigned to each entry. you can specify which inquiry forms are assigned to which reference category when an event is reported in the SAP EHS Management (EHS-MGM) component. Standard settings The standard system is delivered with examples. . Exit Name: CL_EHHSS_INC_INB_PROC_BCS If you want to change how the e-mail exit handler behaves. Specify Inquiry Forms Use In this Customizing activity. and modify the HANDLE_FORMS method. If necessary. Requirements You have specified forms in Customizing activity Specify Forms for Foundation for EHS Management. 2. you can create your own implementation that inherits from the default class. define additional entries.

A unique key must be assigned to each entry. If you assign a customer-specified group. You can use near miss groups to classify near misses. Activities 1. Check the existing examples and adapt them as required. Activities 1. 2. Standard settings The standard system is delivered with examples. You can change this classification during the review and completion step. . A unique key must be assigned to each entry. the system automatically classifies incidents according to groups. you can define additional incident groups. an injury or illness. If necessary. you can define additional near miss groups.Specify Incident Groups Use In this Customizing activity. such as Release. this will have no effect on the user interface. Depending on the data you enter during the initial recording step for the incident record. Standard settings The standard system is delivered with examples. for example. If you assign an incident group delivered with the standard system. If necessary. define additional entries. the system automatically displays relevant data fields or hides unnecessary data fields in the incident record. Specify Near Miss Groups Use In this Customizing activity. 2. Use If you assign one or more than one incident group to an incident. define additional entries. the system modifies the user interface to either reveal relevant or hide irrelevant incident parameters. Check the existing examples and adapt them as required. either during the initial recording step or during the review and completion step for incident records. Incident Group Definition Classifies the incident based on whether it is.

Standard settings The standard system is delivered with examples. Activities 1. If necessary. you can enter a location type which describes where the incident occurred. During the initial recording step for the incident record. if necessary. for example. Standard settings The standard system is delivered with examples. Check the existing examples and adapt them as required. the use of defective material. You can select more than one safety observation group.Near Miss Group Definition Classifies the near miss based on the situation it involved. You can use safety observation groups to classify safety observations. for example. an unsafe action. Check the existing examples and adapt them as required. you can define additional safety observation groups. if necessary. Specify Safety Observation Groups Use In this Customizing activity. A unique key must be assigned to each entry. Specify Location Classifications Use In this Customizing activity. define additional entries. Use You can select more than one near miss group. Activities 1. 2. Safety Observation Group classifies the safety observation based on the situation it involved. either during the initial recording step or during the review and completion step for incident records. you can define the location types. .

This parameter contributes to the weather description for an incident. In the standard delivery. For more information. you can select the Default checkbox for the corresponding entry. you can define the wind directions. 2. During the review and completion step for incident records. define additional entries. Check the existing examples and adapt them as required. you can enter a wind direction. 2. Standard settings The standard system is delivered with examples. weather data is entered only for incidents that involved a release. Activities 1. If necessary. you can select the Default checkbox for the corresponding entry. A unique key must be assigned to each entry. define additional entries. You can use the location classification for reporting and statistical purposes Specify Wind Directions Use In this Customizing activity. see the documentation under Specify Incident Groups. Location Classification specifies the primary or initial location where the incident occurred. .If you want the system to display a value on the user interface automatically. If you want the system to display a value on the user interface automatically. If necessary.

you can define estimated risk types for near misses and safety observations. Specify Estimated Risk Types Use In this Customizing activity. 2. Standard settings The standard system is delivered with examples. . If you want the system to display a value on the user interface automatically.A unique key must be assigned to each entry. Check the existing examples and adapt them as required. A unique key must be assigned to each entry. define additional entries. If necessary. Estimated Risk Type indicates the potential risk of a future incident resulting from the circumstances of a near miss or safety observation. you can select the Default checkbox for the corresponding entry. Activities 1.

Check the existing examples and adapt them as required. define additional entries. You can also define that a role can be used only for certain incident categories by selecting the corresponding indicators. Activities 1. A unique key must be assigned to each entry. 2. You can define business partner roles in Customizing for Cross-Application Components under SAP Business Partner -> Business Partner -> Basic Settings -> Business Partner Roles -> Define BP Roles. Standard settings The standard system is delivered with examples. you can define the roles of an involved person or organization. Note The person roles you define in this Customizing activity do not correspond with the roles that are assigned to business partners.Specify Roles Use In this Customizing activity. If necessary. .

For each incident type.Role of Involved Person indicates the role or roles of a person or organization involved in an incident. Injured Person Specify Incident Types Use In this Customizing activity. . you can specify whether it is occupational or non-occupational according to the regulations that are valid for your company. such as a Witness. You can select an incident type during incident recording to classify an incident with regard to the resulting injury or illness. you can define different incident types for incidents that involve the injury or illness of an involved person. The classification is required for legal reporting.

you can define additional reporting criteria for OSHA reporting. see the settings for business object EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile OSHA in the Customizing activity Specify Field Control for Foundation for EHS Management. such as the following:  Needlestick and sharps injuries (in case of contamination with another person's blood or other potentially infectious material)  Tuberculosis  Hearing losses  Cases involving medical removal Standard settings The standard system is delivered with example definitions for the above-named cases of injury or illness. If necessary. define additional entries. Activities 1. 2.Standard settings The standard system is delivered with examples. the incident is included in the OSHA 300 Log. For more information. you can select the Default checkbox for the corresponding entry. You can use the incident type to determine which incidents are taken into account for reporting purposes. For example. If you want the system to display a value on the user interface automatically. OSHA regulations require that certain cases of injury or illness are explicitly reported beyond general reporting criteria. A unique key must be assigned to each entry. Incident Type classifies further the type of incident that occurred. if you select an incident type that is classified as occupational according to OSHA standards. Depending on regulations. different types of incident are relevant for legal reporting. Check the existing examples and adapt them as required. Activities . Specify Additional Reporting Criteria (OSHA) Use In this Customizing activity. such as an incident on the way to work. The standard system is delivered with field control settings that display this field only when the incident is subject to OSHA recording requirements.

define additional entries.1. The standard system is delivered with field control settings that display this field only when the incident is subject to OSHA recording requirements. If you want the system to display a value on the user interface automatically. define additional entries. . During incident recording. you can use these types to specify where a person died. you can select the Default checkbox for the corresponding entry. A unique key must be assigned to each entry. For more information. A unique key must be assigned to each entry. If necessary. see the settings for business object EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile FATALITY_STATE in Customizing activity Specify Field Control for Foundation for EHS Management. 2. you can define different location of death types. Activities 1. Standard settings The standard system is delivered with examples. you can select the Default checkbox for the corresponding entry. Check the existing examples and adapt them as required. 2. If necessary. Check the existing examples and adapt them as required. Specify Location of Death Types Use In this Customizing activity. If you want the system to display a value on the user interface automatically.

If you want the system to display a value on the user interface automatically. see the settings for business object EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile OSHA in the Customizing activity Specify Field Control for Foundation for EHS Management. For more information. Specify Transportation to Further Treatment Use . A unique key must be assigned to each entry. The standard system is delivered with field control settings that display this field only when the incident is subject to OSHA recording requirements. Activities 1. Check the existing examples and adapt them as required. you can define different means of transportation that can be used to take injured persons to first aid treatment.Specify Transportation to First Aid Use In this Customizing activity. 2. If necessary. define additional entries. you can select the Default checkbox for the corresponding entry. Standard settings The standard system is delivered with examples.

During incident recording. you can use these types to specify why a person died. 2. If you want the system to display a value on the user interface automatically. Specify Cause of Death Types Use In this Customizing activity. Check the existing examples and adapt them as required. Standard settings . see the settings for business object EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile OSHA in the Customizing activity Specify Field Control for Foundation for EHS Management. For more information.In this Customizing activity. If necessary. Standard settings The standard system is delivered with examples. you can define different means of transportation that can be used to take an injured person from first aid treatment to further treatment or to their home. The standard system is delivered with field control settings that display this field only when the incident is subject to OSHA recording requirements. Activities 1. you can select the Default checkbox for the corresponding entry. A unique key must be assigned to each entry. define additional entries. you can define different cause of death types.

. Specify Injury/Illness Classifications Use In this Customizing activity. For more information. The standard system is delivered with field control settings that display this field only when the incident is subject to OSHA recording requirements. If necessary. Standard settings The standard system is delivered with examples. If you want the system to display a value on the user interface automatically. Check the existing examples and adapt them as required. 2. Activities 1. This classification is required to classify the injury or illness in legal reporting. define additional entries. see the settings for business object EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile FATALITY_STATE in Customizing activity Specify Field Control for Foundation for EHS Management. you can select the Default checkbox for the corresponding entry. you can define an injury or illness classification according to the current OSHA standards. A unique key must be assigned to each entry.The standard system is delivered with examples.

you can select only the injury or illness types that correspond to the selected classification. as an injury or one of several occupational health conditions. A unique key must be assigned to each entry. Check the existing examples and adapt them as required.Activities 1. define additional entries. Requirements You have defined an injury/illness classification in the Customizing activity Specify Injury/Illness Classification. Each injury/illness type is classified according to an OSHA-specific injury/illness classification. you can select the Default checkbox for the corresponding entry. for example. Standard settings The standard system is delivered with examples. Activities 1. 2. Check the existing examples and their definitions (extra short and long). 2. If the system should automatically display a value on the user interface. you can define different injury and illness types that give a detailed description of the injury or illness caused by the incident. If necessary. . If necessary. Each injury or illness type must be assigned to an injury or illness class as defined in the injury/illness classification to allow a classification according to OSHA standards. If you want the system to display a value on the user interface automatically. you can select the Default checkbox for the corresponding entry. Specify Injury/Illness Types Use In this Customizing activity. such as the following:  Skin diseases or disorders  Respiratory conditions  Poisoning  Hearing loss  All other illnesses After specifying a classification for an injury or illness. Injury/Illness Type indicates the type of injury or illness that an injured person suffered due to an incident. define additional injury or illness types and assign them to an injury/illness class. A unique key must be assigned to each entry. The OSHA 300 form collects data on specific occupational health conditions. Adapt them as required. Injury/Illness Classification classifies the injury or illness type according to OSHA standards.

you can define the different body parts of a person that can be injured during an incident. Activities 1. A unique key must be assigned to each entry. you can use these definitions to give a detailed description of the injury. define additional entries. If you want the system to display a value on the user interface automatically. Standard settings The standard system is delivered with examples. If necessary.Specify Body Parts Use In this Customizing activity. you can select the Default checkbox for the corresponding entry. 2. During incident recording. . Check the existing examples and adapt them as required.

If necessary. Standard settings The standard system is delivered with examples. Activities 1.Specify Body Sides Use In this Customizing activity. you can select the Default checkbox for the corresponding entry. 2. A unique key must be assigned to each entry. During incident recording. If you want the system to display a value on the user interface automatically. you can define the different sides of a person's body that can be injured during an incident. . define additional entries. Check the existing examples and adapt them as required. you can use these definitions to give a detailed description of the injury.

you can assign these restriction types to an injured person to give detailed information about the consequences of an injury or illness. During incident recording. Standard settings The standard system is delivered with examples. define additional entries. you can define different restriction types. Check the existing examples and adapt them as required.Specify Restriction Types Use In this Customizing activity. Activities 1. If necessary. A unique key must be assigned to each entry. Note To specify the absence types that are relevant for incident recording. If you want the system to display a value on the user interface automatically. . you use the Customizing activity Specify Relevant HR Absence Types. you can select the Default checkbox for the corresponding entry. 2.

Influencing Factors

Specify Incident-Causing Objects
Use
In this Customizing activity, you can define different incident-causing objects. During incident recording, you can specify these
objects to provide detailed information about why an incident occurred.
Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.

If you want the system to display a value on the user interface automatically, you can select the Default checkbox for
the corresponding entry.
2. If necessary, define additional entries.
A unique key must be assigned to each entry.

Specify Movements of Incident-Causing Objects
Use
In this Customizing activity, you can define different kinds of movement referring to the incident-causing object. During
incident recording, you can specify these movements to provide detailed information about why an incident occurred.
Standard settings
The standard system is delivered with examples.
The standard system is delivered with field control settings that display this field only when an incident-causing object exists. For
more information, see the settings for business object EHHSS_INCIDENT -> node HEALTH_SAF_INFO -> field control profile
INC_CAUSING_SUBST_IN in Customizing activity Specify Field Control for Foundation for EHS Management.
Activities
1. Check the existing examples and adapt them as required.
If you want the system to display a value on the user interface automatically, you can select the Default checkbox for
the corresponding entry.

2. If necessary, define additional entries.
A unique key must be assigned to each entry.

Incident-Causing Object
Definition
Specifies an object that contributed to the occurrence of the incident.
Dependencies
To further describe what happened to the incident-causing object at the time of the incident, you can also specify the
movement of this object.

Specify Activities of Injured Persons
Use
In this Customizing activity, you can define different activities that describe what the injured person was doing when the incident
occurred.
Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.
If you want the system to display a value on the user interface automatically, you can select the Default checkbox for
the corresponding entry.
2. If necessary, define additional entries.
A unique key must be assigned to each entry.

If necessary. A unique key must be assigned to each entry. Standard settings The standard system is delivered with examples. you can select the Default checkbox for the corresponding entry.Specify Movements of Injured Persons Use In this Customizing activity. define additional entries. During incident recording. . you can define different kinds of movement. Check the existing examples and adapt them as required. 2. Activities 1. If you want the system to display a value on the user interface automatically. you can use these movement definitions to provide detailed information about what the injured person was doing when the incident occurred.

Standard settings The standard system is delivered with examples. If you want the system to display a value on the user interface automatically. Activities 1. A unique key must be assigned to each entry. 2. Specify External Influences Use . you can define the personal protective equipment that can or must be used for certain jobs. If necessary. you can select the Default checkbox for the corresponding entry. Check the existing examples and adapt them as required.Specify Personal Protective Equipment Use In this Customizing activity. define additional entries.

If you want the system to display a value on the user interface automatically. you can select the Default checkbox for the corresponding entry. A unique key must be assigned to each entry. define additional entries. Standard settings The standard system is delivered with examples. Check the existing examples and adapt them as required. External Influence specifies an external influence that contributed to the incident. rain or snow. If necessary. define additional entries. Check the existing examples and adapt them as required. During incident recording. Example . you can define different actions describing the steps that are taken immediately after an incident occurred. you can select the Default checkbox for the corresponding entry. you can specify these external influences to provide detailed information about the circumstances under which an incident occurred. Standard settings The standard system is delivered with examples. If you want the system to display a value on the user interface automatically. for example. If necessary. Activities 1.In this Customizing activity. you can define different external influences. 2. A unique key must be assigned to each entry. 2. Specify Immediate Actions Use In this Customizing activity. Activities 1.

Specify Technical Safety Devices
Use
In this Customizing activity, you can define different technical safety devices.
Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.
If you want the system to display a value on the user interface automatically, you can select the Default checkbox for
the corresponding entry.
2. If necessary, define additional entries.
A unique key must be assigned to each entry.

Assets

Specify Involved Assets - Equipment Types
Use
In this Customizing activity, you can specify the equipment types that are allowed to be entered as a classification of an involved
asset during incident recording of SAP EHS Management (EHS-MGM).
You can do the following:

Select equipment types from Plant Maintenance (PM) to restrict the number of available equipment types in EHS-MGM

Define new equipment types for EHS-MGM

Requirements
If you want to select equipment types from PM, you have defined technical object types in Customizing for Plant Maintenance
under Define Types of Technical Objects. You can specify these technical object types as equipment types in Customizing for
SAP EHS Management.
Standard settings
The standard system is delivered without equipment types.
Activities

If you want to use a restricted number of PM equipment types for EHS-MGM, select the required equipment types and
enter a description for all relevant languages. If you do not enter a description, the system automatically uses the
description that is defined for the selected equipment types in PM.
Note
To maintain the description in other languages, when you edit an IMG activity, select the relevant record and then
choose Goto -> Translation.

If you want to use equipment types that are only relevant for EHS-MGM, define the required entries and enter a
description for all relevant languages.

If you do not specify any equipment types, all PM equipment types can be selected during incident recording. However, once
you have specified equipment types for EHS-MGM, you can only use the equipment types that are defined in this Customizing
activity.

Recommendation
Although it is possible to use PM equipment types together with equipment types that are only relevant for EHS-MGM, we do not
recommend this. If you used both, you would be able to select a non-PM equipment type, for example, but you would not find a
PM equipment type for it, which could cause some confusion.
Example
In Plant Maintenance, the technical object types 1000 and 2000 are defined. In Plant Maintenance, pieces of equipment are
created with these technical object types.
In the incident recording, it shall be possible to add pieces of equipment from Plant Maintenance with the technical object type
1000 or 2000 as pieces of equipment to an incident.
Specify the following entries:
Equipment Type Equipment Type Description
1000

Incident Equipment 1000

2000

Incident Equipment 2000

As a result, it is possible to add pieces of equipment with the equipment type 1000 or 2000 to an incident.

Definition: type of technical object
Plant Maintenance (PM)
A division of a technical object for precise description.
Example
 Category of technical object: "Fleet objects"
 Type of technical object: "Heavy goods vehicle," "Automobile," "Fork-lift truck"

Specify Involved Assets - Property Types
Use
In this Customizing activity, you can specify the property types that are allowed to be entered as a classification of an involved
asset during incident recording of SAP EHS Management (EHS-MGM).
You can do the following:

Select property types from Plant Maintenance (PM) to restrict the number of available property types in EHS-MGM

Define new property types for EHS-MGM

Requirements

Specify the following entries: Property Type Property Type Description 1000 Incident Property 1000 2000 Incident Property 2000 As a result. Definition: type of technical object .  If you want to use property types that are only relevant for EHS-MGM. but you would not find a PM property type for it. If you do not specify any property types. Recommendation Although it is possible to use PM property types together with property types that are only relevant for EHS-MGM. Example In Plant Maintenance. In Plant Maintenance. In the incident recording. the system automatically uses the description that is defined for the selected property types in PM.If you want to select property types from PM. select the required property types and enter a description for all relevant languages." "Fork-lift truck" . which could cause some confusion. it shall be possible to add properties from Plant Maintenance with the technical object type 1000 or 2000 as properties to an incident. you have defined technical object types in Customizing for Plant Maintenance under Define Types of Technical Objects. the technical object types 1000 and 2000 are defined. define the required entries and enter a description for all relevant languages. it is possible to add properties with the property type 1000 or 2000 to an incident. all PM property types can be selected during incident recording. If you do not enter a description." "Automobile. Activities  If you want to use a restricted number of PM property types for EHS-MGM. when you edit an IMG activity. for example. you would be able to select a non-PM property type. you can only use the property types that are defined in this Customizing activity. select the relevant record and then choose Goto -> Translation. You can specify these technical object types as property types in Customizing for SAP EHS Management. Standard settings The standard system is delivered without property types. If you used both.Plant Maintenance (PM) A division of a technical object for precise description. Note To maintain the description in other languages. once you have specified property types for EHS-MGM. we do not recommend this. Example  Category of technical object: "Fleet objects"  Type of technical object: "Heavy goods vehicle. pieces of equipment are created with these technical object types. However.

all PM vehicle types can be selected during incident recording. You can specify these technical object types as vehicle types in Customizing for SAP EHS Management. once you have specified vehicle types for EHS-MGM. but you would not find a PM vehicle type for it.Specify Involved Assets . the technical object types 1000 and 2000 are defined.  If you want to use vehicle types that are only relevant for EHS-MGM. you would be able to select a non-PM vehicle type. the system automatically uses the description that is defined for the selected vehicle types in PM. for example. you can only use the vehicle types that are defined in this Customizing activity. You can do the following:  Select vehicle types from Plant Maintenance (PM) to restrict the number of available vehicle types in EHS-MGM  Define new vehicle types for EHS-MGM Requirements If you want to select vehicle types from PM. Recommendation Although it is possible to use PM vehicle types together with vehicle types that are only relevant for EHS-MGM. define the required entries and enter a description for all relevant languages. . you have defined technical object types in Customizing for Plant Maintenance under Define Types of Technical Objects. Example In Plant Maintenance. you can specify the vehicle types that are allowed to be entered as a classification of an involved asset during incident recording of SAP EHS Management (EHS-MGM). However. If you used both. If you do not specify any vehicle types. we do not recommend this. select the relevant record and then choose Goto -> Translation. Standard settings The standard system is delivered without vehicle types. If you do not enter a description. select the required vehicle types and enter a description for all relevant languages. which could cause some confusion. Activities  If you want to use a restricted number of PM vehicle types for EHS-MGM. when you edit an IMG activity. Note To maintain the description in other languages.Vehicle Types Use In this Customizing activity. pieces of equipment are created with these technical object types. In Plant Maintenance.

you can select the Default checkbox for the corresponding entry. A unique key must be assigned to each entry. Activities 1. . If you want the system to display a value on the user interface automatically. define additional entries. Standard settings The standard system is delivered with examples. 2. Specify Damage Types Use In this Customizing activity. you can define the damage types. Damage Type describes the type of damage (such as water or fire damage) that was caused by the incident or that could be caused by the circumstances of the near miss or safety observation. it shall be possible to add vehicles from Plant Maintenance with the technical object type 1000 or 2000 as vehicles to an incident.In the incident recording. it is possible to add vehicles with the vehicle type 1000 or 2000 to an incident. Specify the following entries: Vehicle Type Vehicle Type Description 1000 Incident Vehicle 1000 2000 Incident Vehicle 2000 As a result. If necessary. Check the existing examples and adapt them as required.

you can select the Default checkbox for the corresponding entry. When you review and complete an incident record. you can define release types. Activities 1.Specify Release Types Use In this Customizing activity. . you use release types to describe how a material was released. If you want the system to display a value on the user interface automatically. Standard settings The standard system is delivered with examples. Check the existing examples and adapt them as required.

define additional entries. Standard settings The standard system is delivered with examples. you can define release sizes. 2. If necessary. Check the existing examples and adapt them as required. Release Type Definition Indicates the type of release that occurred during the incident.2. you can define material states. you use these release sizes to describe the amount of material that was released. Specify Release Sizes Use In this Customizing activity. Standard settings The standard system is delivered with examples. Activities 1. you can select the Default checkbox for the corresponding entry. or ground. Check the existing examples and adapt them as required. a release into the air. Release Size Definition Indicates the size of the release that occurred during the incident. Specify Material States Use In this Customizing activity. If necessary. A unique key must be assigned to each entry. When you review and complete an incident record. water. you use these states to give a detailed description of the material that was released. for example. If you want the system to display a value on the user interface automatically. Activities 1. define additional entries. A unique key must be assigned to each entry. . When you review and complete an incident record.

2. define additional entries. Specify Affected Land Types Use In this Customizing activity. If necessary. Material State indicates the state of matter for a material that is released. For example. If you want the system to display a value on the user interface automatically. Affected Land Type indicates the type of land affected by the release during an incident. you can select the Default checkbox for the corresponding entry. A unique key must be assigned to each entry. A unique key must be assigned to each entry. define additional entries. Specify Disposal Methods Use . Check the existing examples and adapt them as required.If you want the system to display a value on the user interface automatically. 2. an oil release is a material released in a liquid state. Standard settings The standard system is delivered with examples. you can select the Default checkbox for the corresponding entry. Activities 1. If necessary. you can define different land types.

Standard settings The standard system is delivered with examples. If necessary. you can define different disposal methods. 2. you can select the Default checkbox for the corresponding entry. 2. you can define different types of disposal sites. A unique key must be assigned to each entry. Standard settings The standard system is delivered with examples. A unique key must be assigned to each entry. you can select the Default checkbox for the corresponding entry. If you want the system to display a value on the user interface automatically. Activities 1. If you want the system to display a value on the user interface automatically. Material Disposal Site indicates the disposal site for a material that was recovered after a release. define additional entries. Specify Disposal Sites Use In this Customizing activity. define additional entries. Check the existing examples and adapt them as required. Activities 1. If necessary. .In this Customizing activity. Check the existing examples and adapt them as required.

define additional entries.Specify Recovery Methods Use In this Customizing activity. If you want the system to display a value on the user interface automatically. Material Recovery Method Definition Indicates how a material that was released during an incident was recovered. you can select the Default checkbox for the corresponding entry. 2. Activities 1. Check the existing examples and adapt them as required. you can define different recovery methods Standard settings The standard system is delivered with examples. . A unique key must be assigned to each entry. If necessary.

If you want the system to display a value on the user interface automatically. . Activities 1. Standard settings The standard system is delivered with examples. When you review and complete an incident record.Specify Waste Types Use In this Customizing activity. define additional entries. you use these waste type to indicate how dangerous the released material is to the environment. If necessary. hazardous. Waste Type Definition Classifies the disposed material according to the type of waste it is. you can select the Default checkbox for the corresponding entry. for example. you can define different waste types. Check the existing examples and adapt them as required. 2. A unique key must be assigned to each entry.

you can define different cleanup methods. you can select the Default checkbox for the corresponding entry. Check the existing examples and adapt them as required. 2.Specify Cleanup Methods Use In this Customizing activity. Specify Affected Areas Use . A unique key must be assigned to each entry. define additional entries. Activities 1. If necessary. Standard settings The standard system is delivered with examples. If you want the system to display a value on the user interface automatically. Cleanup Method indicates how the released material was cleaned up. for example. burning in situ.

for example. severity. When you review and complete an incident record. 2. people. If you want the system to display a value on the user interface automatically. Specify Severity Use In this Customizing activity. If necessary.In this Customizing activity. A unique key must be assigned to each entry. Standard settings The standard system is delivered with examples. you can select the Default checkbox for the corresponding entry. There is a unique set of severity values for each area. When you review and complete an incident record. Use You can assess the risk to an area on the Risk Assessment tab by choosing values for the various risk parameters. you can define areas affected by the incident. Check the existing examples and adapt them as required. you can assess the risk to an area on the Risk Assessment tab. Check the existing examples and adapt them as required. An incident could affect. you can define severity values and the corresponding risk scores. The severity is one of several risk parameters used to calculate the risk to that area. Activities 1. Affected Area Definition Indicates an aspect or area of a business that an incident could affect. 2. for example. you can assign a severity value to an affected area on the Risk Assessment tab. Activities 1. define additional entries. Requirements You have defined affected areas in the Specify Affected Areas Customizing activity. Standard settings The standard system is delivered with examples. Check the existing example scores under Risk Score and adapt them as required. .

The selected severity value has a corresponding score. Use The system automatically calculates the sum of the risk parameter scores to provide the total risk score. for an area in the Risk Assessment tab. for example.3. If necessary. Score for Risk Assessment Definition Indicates the score that the system uses for a risk parameter when it calculates the risk rating for a specific area. The severity is one of several risk parameters used to calculate the risk to the corresponding area. This score contributes to the total risk score. people. A unique key must be assigned to each entry. Use You can enter a severity value for an affected area on the Risk Assessment tab. Each severity value has a corresponding score value that is used in the risk calculation. Risk Rating Definition Specifies the risk to a specific area. The system automatically calculates and assigns a risk rating when the sum of the risk scores falls within a certain range (between a lower score limit and an upper score limit). such as minor. Specify Frequency Use . such as the severity on the Risk Assessment tab. define additional entries. You can assess the risk to an area on the Risk Assessment tab by choosing values for the various risk parameters. Dependencies You can define the risk parameter scores for risk assessment in the following activities in Customizing for SAP EHS Management:  Specify Incident Severity  Specify Incident Likelihood  Specify Incident Frequency  Specify Incident Duration Classifications Example You can select a severity value. An incident could affect. Incident Severity Definition Indicates the severity of an incident with respect to a specific area. Affected Area indicates an aspect or area of a business that an incident could affect. severity. Use You can assess the risk potential for a specific affected area by entering information for relevant risk parameters. for example.

When you review and complete an incident record. A unique key must be assigned to each entry. . Activities 1. you can select the Default checkbox for the corresponding entry. you can assign a frequency value to an affected area on the Risk Assessment tab. If you want the system to display a value on the user interface automatically.In this Customizing activity. When you review and complete an incident record. you can define frequency values. Specify Likelihood Use In this Customizing activity. Each likelihood value has a corresponding score value. Standard settings The standard system is delivered with examples. you can define likelihood values. 3. If necessary. Check the existing example scores under Risk Score and adapt them as required. define additional entries. you can assign a likelihood value to an affected area on the Risk Assessment tab. The frequency is one of several risk parameters used to calculate the risk to an area. The likelihood is one of several risk parameters used to calculate the risk to an area. 2. Check the existing examples and adapt them as required. Each frequency value has a corresponding score value.

you can select the Default checkbox for the corresponding entry. The likelihood is one of several risk indicators used to calculate the risk to the corresponding area. 2. Check the existing example scores under Risk Score and adapt them as required. A unique key must be assigned to each entry. Specify Frequency Use In this Customizing activity. Standard settings The standard system is delivered with examples. If you want the system to display a value on the user interface automatically. Each frequency value has a corresponding score value. A unique key must be assigned to each entry. Each likelihood value has a corresponding score value. you can define frequency values. you can assign a frequency value to an affected area on the Risk Assessment tab. 2.Standard settings The standard system is delivered with examples. Incident Frequency Definition . The frequency is one of several risk parameters used to calculate the risk to an area. Likelihood to Reoccur Definition Indicates the likelihood that an incident will reoccur and affect a specific area. define additional entries. Use You can enter the likelihood that an area will be affected again on the Risk Assessment tab. 3. Activities 1. If necessary. If you want the system to display a value on the user interface automatically. you can select the Default checkbox for the corresponding entry. Check the existing example scores under Risk Score and adapt them as required. Check the existing examples and adapt them as required. 3. If necessary. Check the existing examples and adapt them as required. define additional entries. Activities 1. When you review and complete an incident record.

Use The system automatically assigns a risk rating when the sum of the risk scores falls between the lower score limit and the upper score limit. Use You can assess the risk potential for a specific affected area by entering information for relevant risk parameters. The frequency is one of several risk indicators used to calculate the risk to the corresponding area. Use You can enter the frequency for an affected area on the Risk Assessment tab. Upper Score Limit for Risk Assessment Definition Indicates the highest score in a range of possible scores used to derive an overall risk rating for an affected area. such as the severity on the Risk Assessment tab Lower Score Limit for Risk Assessment Definition Indicates the lowest score in a range of possible scores used to derive an overall risk rating for an affected area. The system automatically calculates and assigns a risk rating when the sum of the risk scores falls within a certain range (between a lower score limit and an upper score limit). Each frequency value has a corresponding score value.Indicates the frequency that an incident may occur with respect to a specific area. . Risk Rating Definition Specifies the risk to a specific area. Use The system automatically assigns a risk rating when the sum of the risk scores falls between the lower score limit and the upper score limit.

If necessary. Check the existing examples and adapt them as required. Each duration classification has a corresponding score value. Specify Risk Ratings Use .Specify Duration Classifications Use In this Customizing activity. The duration is one of several risk parameters used to calculate the risk to an area. Incident Duration Classification Definition Classifies the duration of the exposure or hazard as it relates to a specific area. Each duration classification has a corresponding score value. When you review and complete an incident record in incident management. Standard settings The standard system is delivered with examples. If you want the system to display a value on the user interface automatically. 3. Activities 1. Use You can enter the duration classification for an affected area on the Risk Assessment tab. The duration is one of several risk parameters used to calculate the risk to the corresponding area. define additional entries. you can assign a duration to an affected area on the Risk Assessment tab. Check the existing example scores under Risk Score and adapt them as required. 2. A unique key must be assigned to each entry. you can select the Default checkbox for the corresponding entry. you can define duration classifications.

In the Description (XS) field. Select the Default checkbox if you want the system to display a specific risk rating on the Risk Assessment tab automatically until a different risk rating is calculated. enter the color of the LED icon that is to be displayed for the corresponding risk rating. enter a letter grade or word to describe the corresponding Risk Rating value. you can assess the risk to an affected area on the Risk Assessment tab by entering information for the following risk parameters:  Severity  Likelihood to Reoccur  Frequency  Duration You can enter a data value for each risk parameter. such as C or Moderate. you can define risk ratings. The system automatically calculates and assigns a risk rating when the sum of the risk scores falls within a certain range (between a lower score limit and an upper score limit). Requirements You have defined risk score values in the following Customizing activities:  Specify Incident Severity  Specify Incident Likelihood  Specify Incident Frequency  Specify Incident Duration Classifications Standard settings The standard system is delivered with examples. the lower score for one risk rating must not have the same value as the upper score for another risk rating. 6. enter the highest score for the range of possible scores for the corresponding risk rating. You can use generic descriptors. In the Description (L) field. Risk rating ranges must not overlap. In the Upper Score field.In this Customizing activity. that is. In the Lower Score field. 2. 4. When you review and complete an incident record. 3. A risk score is assigned to each of these values. In the Risk Icon field. enter words or a phrase to further describe the risk rating. Activities 1. for example. enter the lowest score for the range of possible scores for the corresponding risk rating. Acceptable with Controls. . 5.

likelihood to reoccur. Requirements You have made the following settings in the Customizing for SAP EHS Management under Incident Management: Specify Affected Areas Specify Severity Specify Likelihood Specify Frequency Specify Duration Classifications Specify Risk Ratings Standard settings This BAdI is active in the standard system. the distinctive scores for severity. The default logic for calculating the risk assessment and determining the risk icons is as follows:  The scores of the affected areas are added  The rating is determined according to the lower and upper limit of the sum of scores  The risk icon is determined according to the risk rating configuration The BAdI method calculate_risk receives the risk assessment type (initial or residual). frequency and duration. The system automatically calculates and assigns a risk rating when the sum of the risk scores falls within a certain range (between a lower score limit and an upper score limit). the precalculated sum of risk scores. BAdI: Calculate Risk Assessment and Determine Risk Icon Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. likelihood to reoccur. You can use this BAdI to adapt the standard logic to calculate the risk assessment and to determine the risk icons that are displayed. You can assess the risk potential for a specific affected area by entering information for relevant risk parameters.Risk Rating specifies the risk to a specific area. and returns the value for the risk icon. frequency and duration. The risk icons are set according to the risk rating. such as the severity on the Risk Assessment tab. . The risk rating is calculated for each affected area based on configurable scores for the following risk parameters: severity. The calculated value can be manually overwritten by the user.

Specify Violation Categories Use In this Customizing activity. Violation Category specifies the violation category. Activities 1.For more information about the standard settings (filters. If you want the system to display a value on the user interface automatically. 2. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). you can select the Default checkbox for the corresponding entry. Standard settings The standard system is delivered with examples. Check the existing examples and adapt them as required. for example. . define additional entries. you can define violation categories. repeated violations or serious violations. If necessary. Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . A unique key must be assigned to each entry. single or multiple uses).Embedding in the Enhancement Framework.

If necessary. for example. you can define violation types. A unique key must be assigned to each entry. Violation Type Definition Specifies the violation type. you can select the Default checkbox for the corresponding entry. Activities 1. Specify Violation Sources Use . Standard settings The standard system is delivered with examples. 2.Specify Violation Types Use In this Customizing activity. Check the existing examples and adapt them as required. define additional entries. a violation that is directly related to a training issue. If you want the system to display a value on the user interface automatically.

you can define violation sources. Check the existing examples and adapt them as required. Standard settings The standard system is delivered with examples. agency. Activities 1. or type of person that reported the violation. Violation Source indicates the source organization. Standard settings . 2. A unique key must be assigned to each entry. define additional entries. you can specify the categories that are used to record financial information.In this Customizing activity. you can select the Default checkbox for the corresponding entry. If necessary. Specify Financial Transaction Categories Use In this Customizing activity. If you want the system to display a value on the user interface automatically.

see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). BAdI Implementations  BADI_RDY_FOR_ACT_INC_CLOSE . maintain exchange rates in Customizing for SAP NetWeaver under General Settings -> Currencies -> Enter Exchange Rates. you can deactivate this implementation and use a customer-specific check instead.The standard system is delivered with examples. Caution If you implement customer-specific checks. Business Add-Ins (BAdIs) for Checks BAdI: Check Readiness for Action Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. If necessary. You can use this BAdI to perform checks on the following actions:  Set incident status to Closed  Set incident status to Void  Set investigation status to Closed For each action. If necessary. a BAdI implementation is delivered that performs the corresponding check in the standard system. For more information about the standard settings (filters. 2. you can select the Default checkbox for the corresponding entry. define additional entries. Activities 1. 3. for example. If necessary. when generating legal reports based on the incident data. you must ensure that these are complete in terms of data consistency and legal requirements. Check the existing examples and adapt them as required. If you want the system to display a value on the user interface automatically. Standard settings The BAdI is active in the standard system. single or multiple uses). A unique key must be assigned to each entry.

check if the investigation is completed o If the incident is an occupational incident. You can use the following filter values when defining customer-specific BAdI implementations:  INCIDENT_CATEGORY o 001 Incident o 002 Near Miss . check if at least one notice of violation is assigned o If the incident has actions assigned. check if the Required in Summary Report attribute is set to Yes or No o For any release of incident.  BADI_RDY_FOR_ACT_INV_CLOSE This BAdI implementation performs the following checks: o Check if the Investigation Required attribute is set to Yes or No o Check if an investigation lead is assigned o Check if a major root cause is selected o Check if all investigation steps are complete Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs .Embedding in the Enhancement Framework. check if the Reporting Required attribute is set to Yes or No BADI_RDY_FOR_ACT_INC_VOID This BAdI implementation does not perform any checks in the standard system. check if at least one release is assigned o Check if the Reporting Required attribute for a release is set to Yes or No o Check if assessments are complete and confirmed o If the incident is classified as a notice of violation.This BAdI implementation performs the following checks:  o Check if the Restricted Access attribute for the incident is set to Yes or No o Check if an incident group is assigned o Check if the Investigation Required attribute is set to Yes or No o If an investigation is required. You need to create your own implementation if you want to implement customer-specific checks. check if at least one involved person has the Injured Person role o Check for an injured person o If the incident is classified as Release. check if all actions that are not recurring are complete o For any injured person.

use transaction /bobf/conf_ui or execute the search help EHFND_ELM_BO_NODE_NAME in transaction SE11 in test mode using BO_NAME = EHHSS_INCIDENT. Example You want to define a check that is only executed if:  The incident is a Near Miss  The action that is performed to set the status to Closed  The BASIC_INFO_ALL node is processed. BAdI Implementations . To do this. You can use this BAdI to perform checks for data completeness in incident reports. for example. you must ensure that these are complete in terms of data consistency and legal requirements. Standard settings The BAdI is active in the standard system. For more information about the standard settings (filters. single or multiple uses). when generating legal reports based on the incident data. If you implement customer-specific checks . set the following filter values:  INCIDENT_CATEGORY = 002 (Near Miss)  ACTION_NAME = SET_CLOSED_ROOT  NODE_NAME = BASIC_INFO_ALL BAdI: Check Incident Reports Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. To display the nodes of this business object. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). you must also ensure that all actions are complete or are in the process of completing.o   003 Safety Observation ACTION_NAME o SET_VOID_ROOT o SET_CLOSED_ROOT o INVESTIG_RESULT_SET_CLOSED NODE_NAME You can use all existing node names from business object EHHSS_INCIDENT. Caution If you deactivate or change a check.

check if the date of death is maintained BADI_IRT_CHECK_BG_UNF_BER This BAdI implementation performs the following checks: o Check if the person exists in HR or exists as a business partner o Check if the Fatality attribute is set to Yes or No o Check if the incident time zone is maintained o Check if the address where the incident occurred is maintained o Check if a statement that can be included in reports is maintained o Check if an injury/illness is maintained. or a free text description for the injured person's activity is maintained o Check if a statement that can be included in reports is maintained o If an injury/illness is maintained. check if a body part is maintained o Check if a first physician or a further treatment provider is maintained o Check if the actual start working time for the injured person is maintained o Check if the actual end working time for the injured person is maintained o Check if the position description is maintained o Check if the duration in position is maintained o Check if the organizational unit of the injured person is maintained . BADI_IRT_CHECK_OSHA_301 This BAdI implementation performs the following checks:  o Check if the person exists in HR or exists as a business partner o Check if a first physician or a further treatment provider is maintained o Check if the Emergency Room attribute is set to Yes or No o Check if the Inpatient Overnight attribute is set to Yes or No o Check if the actual start working time for the injured person is maintained o Check if either an activity was selected. check if the injury/illness information and body part information is maintained o Check if only the first reportable injury/illness or the first reportable unknown injury /illness is defined o Check if the incident-causing object or an incident-causing substance is maintained o Check if the Fatality attribute is set to Yes or No o If the Fatality attribute is set to Yes. o If an injury/illness was maintained.

Specify Step Categories Use In this Customizing activity. Requirements To create new step categories. Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . you can add new step categories and modify the categories that are provided with the standard system. You need to create your own implementation if you want to implement customer-specific checks. You can use the following filter values when defining customer-specific BAdI implementations:   Possible filter values for the incident category are: o INCIDENT_CATEGORY = 001 Incident o INCIDENT_CATEGORY = 002 Near Miss o INCIDENT_CATEGORY = 003 Safety Observation Possible filter values for form names are all form names that are entered in Customizing for EHS Management.Embedding in the Enhancement Framework. This activity allows you to add your own functions to the investigation solution. Standard settings . you have already developed the new FPM dialog box and variant for the review and completion step and for the investigation step quick activity. o Check if the ceased work date and time is maintained o Check if end dates of absences are maintained BADI_IRT_CHECK_REL_REP This BAdI implementation does not perform any checks in the standard system.

Standard settings . Use The step category contains information about the user interface (UI) that is used to represent and perform the investigation step. If you want the system to display a value on the user interface automatically. Requirements  To use offline forms.  To use root cause steps for offline steps using the INV_ROOTCAUSE_FORM Interactive Form. If necessary. and specify a root cause hierarchy for the step definition. To create new step categories.The standard system is delivered with examples. see Specify Steps. Activities 1. Check the existing examples and adapt them as required. assign investigation templates. offline form. you can specify investigation steps and you can group these steps together to build the investigation process. You can specify offline steps. online form. 2. Dependencies You can specify investigation step categories in the Specify Step Categories Customizing activity. Investigation Step Category Definition Specifies the unique key for the step category. you have specified a root cause hierarchy in the Specify Root Cause Types Customizing activity. define additional entries. you can select the Default checkbox for the corresponding entry. you must enter the variant ID and dialog box ID.  To specify a root cause hierarchy for steps with the category EHHSS_ST_CAT_ROOTCAUS. Note: You must ensure that this data is consistent since the system cannot validate this data fully. or document. for example. Specify Steps Use In this Customizing activity. For more information. the hierarchy has a maximum of three levels. This setting is used for offline investigation steps when the step is sent via e-mail as an IF to the person responsible for the step. you have specified an Interactive Form for each offline step category in the Specify Step Categories Customizing activity. You can specify the form name of an existing Interactive Form (IF). We recommend that you create new categories instead of adapting existing categories to ensure that the standard examples are not affected.

Check the existing examples and adapt them as required. as required. online form. The investigation guideline is part of the template for the investigation flow that the system determines based on specific incident attributes. you can assign investigation guidelines to incident categories and incident groups. Specify Templates Use . Investigation Step Category Definition Specifies the unique key for the step category. offline form. We recommend that you add new guidelines with a higher version number. To ensure that you have an overview of all guidelines that you have used. for example. A unique key must be assigned to each entry. Use The step category contains information about the user interface (UI) that is used to represent and perform the investigation step. define additional entries. Specify Guidelines Use In this Customizing activity. 2. Dependencies You can specify investigation step categories in the Specify Step Categories Customizing activity. Activities 1. The investigation lead can access these guidelines at the start of the investigation process. Activities Add new investigation guidelines. or document. we recommend that you do not change or delete old guidelines. If necessary.The standard system is delivered with examples.

incident group. Activities 1. 2. . you can define investigation templates. Specify Root Cause Types Use In this Customizing activity. If necessary. country. country. define additional entries. plant ID. Root cause hierarchies are used in investigation steps with the EHHSS_ST_CAT_ROOTCAUS category. see the Specify Guidelines Customizing activity. plant ID. as required. You can also define the standard investigation steps in the template and the sequence in which these steps should be performed. Check the existing examples and adapt them as required.In this Customizing activity. Requirements To use root cause steps for offline steps with the INV_ROOTCAUSE_FORM Interactive Form. incident group. such as incident category. the hierarchy has a maximum of three levels. Requirements If you want to assign templates to investigation steps. Define the standard investigation steps that the template is composed of under Steps in Template. 3. and region. you can specify the root cause hierarchies that you can use when you define investigation steps in the Specify Steps Customizing activity. You can assign investigation templates to specific kinds of incidents using criteria. We recommend that you align the templates and guidelines for each incident category to ensure that the investigation lead can follow the prescribed process and guidelines. and region. For more information. you have defined investigation steps in the Specify Steps Customizing activity. Specify investigation templates. 2. Activities 1. Assign investigation templates to incidents using the criteria incident category. Standard settings The standard system is delivered with examples.

You must enter a description for each root cause.A unique key must be assigned to each entry. single or multiple uses). Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs .Embedding in the Enhancement Framework. You can use this BAdI to change how the default investigation lead is determined. the investigation lead is automatically set to the current incident manager. BAdI: Specify Investigation Lead Determination and Workflow Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. . see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). By default. Standard settings For more information about the standard settings (filters. You must enter a unique description for each root cause hierarchy.

which by default involves the creation of a workitem for the approver to complete the notification in the incident management application. You can use this report to check whether incident management notifications have been completed in other components.Equipment Types Use .Schedule Jobs for Notification Status Check Use In this Customizing activity. Check for Completed Notifications Purpose You use this report in SAP EHS Management (EHS-MGM) to check if incident management notifications have been completed in the following components:  Plant Maintenance (PM)  Customer Service (CS)  Quality Management (QM) Prerequisites   You have specified the destinations of the PM. Features The report determines all incident management notifications that are in status In Process and checks whether these notifications have been set to Completed in the relevant component. you can use the Customizing activity Schedule Jobs for Notification Status Check to schedule the report periodically. You have specified the notification types that you use in EHS-MGM in the Customizing activity Specify Notification Types for Foundation for EHS Management. CS. for example. once a day. subobject: EHHSS_IAC_EXT_NOTIF). you can schedule jobs for the report Check for Completed Notifications (R_EHHSS_ACT_CHECK_COMPL_EXT_NO). such as Plant Maintenance (PM). and QM systems in the Customizing activity Specify Destinations for Integration for Foundation for EHS Management. For all notifications that have been completed. it triggers the next workflow step. All report actions are documented in the application log (object: EHHSS_BO_INC. Specify Involved Assets . Activities Depending on the business processes of your company.

You can do the following:  Select equipment types from Plant Maintenance (PM) to restrict the number of available equipment types in EHS-MGM  Define new equipment types for EHS-MGM Requirements If you want to select equipment types from PM. pieces of equipment are created with these technical object types. once you have specified equipment types for EHS-MGM. If you do not specify any equipment types. If you do not enter a description. it shall be possible to add pieces of equipment from Plant Maintenance with the technical object type 1000 or 2000 as pieces of equipment to an incident. we do not recommend this. when you edit an IMG activity.In this Customizing activity. you have defined technical object types in Customizing for Plant Maintenance under Define Types of Technical Objects. However. In the incident recording. Specify the following entries: Equipment Type Equipment Type Description 1000 Incident Equipment 1000 2000 Incident Equipment 2000 . If you used both. Activities  If you want to use a restricted number of PM equipment types for EHS-MGM. but you would not find a PM equipment type for it. Recommendation Although it is possible to use PM equipment types together with equipment types that are only relevant for EHS-MGM. all PM equipment types can be selected during incident recording. the system automatically uses the description that is defined for the selected equipment types in PM. Example In Plant Maintenance. for example. select the relevant record and then choose Goto -> Translation. select the required equipment types and enter a description for all relevant languages. which could cause some confusion. Note To maintain the description in other languages. you can specify the equipment types that are allowed to be entered as a classification of an involved asset during incident recording of SAP EHS Management (EHS-MGM). In Plant Maintenance. you would be able to select a non-PM equipment type. Standard settings The standard system is delivered without equipment types. the technical object types 1000 and 2000 are defined. You can specify these technical object types as equipment types in Customizing for SAP EHS Management.  If you want to use equipment types that are only relevant for EHS-MGM. you can only use the equipment types that are defined in this Customizing activity. define the required entries and enter a description for all relevant languages.

but you would not find a PM property type for it. You can do the following:  Select property types from Plant Maintenance (PM) to restrict the number of available property types in EHS-MGM  Define new property types for EHS-MGM Requirements If you want to select property types from PM. all PM property types can be selected during incident recording. once you have specified property types for EHS-MGM. we do not recommend this. you would be able to select a non-PM property type.  If you want to use property types that are only relevant for EHS-MGM. define the required entries and enter a description for all relevant languages. when you edit an IMG activity. Activities  If you want to use a restricted number of PM property types for EHS-MGM. Definition: equipment Plant Maintenance (PM) An individual. select the required property types and enter a description for all relevant languages. Standard settings The standard system is delivered without property types. . you can specify the property types that are allowed to be entered as a classification of an involved asset during incident recording of SAP EHS Management (EHS-MGM).As a result. If you do not specify any property types. you can only use the property types that are defined in this Customizing activity. select the relevant record and then choose Goto -> Translation. Specify Involved Assets . If you used both. it is possible to add pieces of equipment with the equipment type 1000 or 2000 to an incident. You can specify these technical object types as property types in Customizing for SAP EHS Management. Recommendation Although it is possible to use PM property types together with property types that are only relevant for EHS-MGM. If you do not enter a description. However. physical object that is maintained as an autonomous unit. you have defined technical object types in Customizing for Plant Maintenance under Define Types of Technical Objects.Property Types Use In this Customizing activity. for example. the system automatically uses the description that is defined for the selected property types in PM. which could cause some confusion. Note To maintain the description in other languages.

the system automatically uses the description that is defined for the selected vehicle types in PM. Standard settings The standard system is delivered without vehicle types. it shall be possible to add properties from Plant Maintenance with the technical object type 1000 or 2000 as properties to an incident. In Plant Maintenance.Vehicle Types Use In this Customizing activity. it is possible to add properties with the property type 1000 or 2000 to an incident. the technical object types 1000 and 2000 are defined. You can specify these technical object types as vehicle types in Customizing for SAP EHS Management. In the incident recording. Specify the following entries: Property Type Property Type Description 1000 Incident Property 1000 2000 Incident Property 2000 As a result. Note . select the required vehicle types and enter a description for all relevant languages. pieces of equipment are created with these technical object types. If you do not enter a description. you have defined technical object types in Customizing for Plant Maintenance under Define Types of Technical Objects. Activities  If you want to use a restricted number of PM vehicle types for EHS-MGM. You can do the following:  Select vehicle types from Plant Maintenance (PM) to restrict the number of available vehicle types in EHS-MGM  Define new vehicle types for EHS-MGM Requirements If you want to select vehicle types from PM.Example In Plant Maintenance. you can specify the vehicle types that are allowed to be entered as a classification of an involved asset during incident recording of SAP EHS Management (EHS-MGM). Specify Involved Assets .

you would be able to select a non-PM vehicle type. the technical object types 1000 and 2000 are defined.  If you want to use vehicle types that are only relevant for EHS-MGM. you can only use the vehicle types that are defined in this Customizing activity. when you edit an IMG activity. Recommendation Although it is possible to use PM vehicle types together with vehicle types that are only relevant for EHS-MGM. we do not recommend this. In Plant Maintenance. In the incident recording.To maintain the description in other languages. it is possible to add vehicles with the vehicle type 1000 or 2000 to an incident. for example. all PM vehicle types can be selected during incident recording. pieces of equipment are created with these technical object types. but you would not find a PM vehicle type for it. Check Customizing for Personnel Time Management Use . If you used both. once you have specified vehicle types for EHS-MGM. select the relevant record and then choose Goto -> Translation. If you do not specify any vehicle types. However. define the required entries and enter a description for all relevant languages. which could cause some confusion. Specify the following entries: Vehicle Type Vehicle Type Description 1000 Incident Vehicle 1000 2000 Incident Vehicle 2000 As a result. Example In Plant Maintenance. it shall be possible to add vehicles from Plant Maintenance with the technical object type 1000 or 2000 as vehicles to an incident.

such as Personnel Administration. see the Customizing activity Check Authorizations for Person Information. All business processes in these application components relate to the employee. 2. Definition: absence type Personnel Time Management (PT) The grouping of employees' scheduled absences and actual absences typically according to the reason for absence. Note As PT manages time data for employees. To be able to make full use of PTintegration. Group together personnel subareas for which the same absence types are valid (personnel subarea grouping) in the Customizing activity Group Personnel Subareas for Attendances and Absences.Integration with the SAP component Personnel Time Management (PT) allows you to access working time data and absences for injured persons during the review and completion step for incident records. It is delimited according to personnel administration. For more information. check that the following settings are correct before you activate PT integration for incident management: Personnel Time Management The link between person and absence is established based on the relationship between personnel subarea and absence type that is defined in Customizing for Personnel Time Management. . Definition: personnel subarea Personnel Administration (PA-PA) An organizational entity that represents part of a personnel area. This includes the following steps: 1. time management. and payroll accounting criteria. Payroll. Time Management. Definition: employee Personnel Management (PA) A person who contributes or has contributed to the creation of goods and services in the enterprise based on a work contract or a contract for services. the required authorizations for the Absences infotype are assigned to all users with display authorization for incident records. The employee constitutes the main focus of interest for the majority of Human Resource application components. Assign absence types to the personnel subarea groupings in the Customizing activity Define Absence Types The relationship between personnel subarea groupings and absence types is time-related. integration is only possible for internal persons. The validity period is limited by the start and end date of the relationship. and so on. Foundation for EHS Management For access to PT data.

To do so either:  Enter the appropriate code  Request a list of infotypes and make a selection Example The Relationship infotype allows you to describe how different objects are linked. you enable the creation of absences in PT for injured persons directly from the incident management application. Use Use this field to identify the infotype you wish to work with. o If you do not select this checkbox.  Creation of HR Absences via Process Activated By selecting this checkbox. Activate Personnel Time Management Integration Use In this Customizing activity.absence hours. The sequence of partial periods and the assigned absence types can be displayed using an absence event. the system calculates working hours as follows: Working hours = regular working hours + overtime hours . directly in the Personnel Time Management (PT) component during the review and completion step for incident records. you enable searches for personnel time data. such as normal working times and absences. Infotype Definition Contains a code that represents a specific infotype. Infotypes allow you to describe object attributes. You can use the report Check for Changed Absences in PT to periodically check if the required absences have been created. you can configure the following settings:  Personnel Time Management (PT) Integration Activated By selecting this checkbox. such as employee time accounts and valuation of personnel times. Different absence types are assigned to partial periods of time during a health cure.  Direct Creation of HR Absences Activated By selecting this checkbox. Enter the e-mail address of the HR manager in the corresponding field. the system calculates the working hours as follows: .  Personnel Time Management (PT) Negative Time Recording o If you select this checkbox.Absences can also be grouped for other personnel-related reasons. you enable the creation of absences in PT using a process that automatically informs the responsible HR manager about the required changes.

Requirements You have checked the settings for Personnel Time Management and Foundation for EHS Management as described in Check Customizing Settings for Personnel Time Management. automatically notifies the responsible incident manager. Attendance hours are hours that are captured by Personnel Time Management. Specify Relevant HR Absence Types Use In this Customizing activity. the system determines the data from the specified date to the specified number of days into the past. If you specify a date for PT data in analytical reporting.Working hours = attendance hours + overtime hours . you use the Customizing activity Specify Restriction Types. Note To specify the restriction types that are relevant for incident recording. . During incident recording.  Number of Days Worked per Year by Full-Time Employee Enter the number of days one full-time employee works in one year. you can specify which Human Resources (HR) absence types are relevant for incident management.  Number of Hours Worked per Year by Full-Time Employee Enter the number of hours one full-time employee works in one year.absence hours Regular hours are hours an employee works according to the assigned working plan.  Months in Past This value is used to calculate PT key figures for analytical reporting using the Business Information Warehouse. This value is used to calculate the Full-Time Equivalent (FTE) for a given number of days. for example. you can select an absence type to describe an absence in more detail. This value is used to calculate the Full-Time Equivalent (FTE) for a given number of hours. if absence data of the maintained types changed in Personnel Time Management (PT). The specified absence types are taken into account by the report Check for Changed Absences in PT that.

Implementation: Determination of FTE and Working Time from P . Schedule Jobs for HR Absence Check Use In this Customizing activity. Requirements You have activated PT integration in the Customizing activity Activate Personnel Time Management Integration. you can schedule jobs for the report Check for Changed Absences in PT (R_EHHSS_CHECK_HCM_ABS_CHANGED).Requirements You have activated PT Integration in the Customizing activity Activate Personnel Time Management Integration. Check the existing examples and adapt them as required. define additional entries. Activities 1. You can use this report to check for absences of injured persons that have been created or changed in Personnel Time Management (PT). 2. A unique key must be assigned to each entry. Standard settings The standard system is delivered with examples. If necessary.

Requirements The following prerequisites must be met:  You have made the required settings for analytical reporting using the Business Information Warehouse. You can use this BAdI to determine the key figure values for Full-Time Equivalents and Working Time according to customer-specific rules. for example. If you activate the BAdI implementation. the system determines the key figure values for Full-Time Equivalents and Working Time per organizational unit and calendar day from PT.You can also use an implementation of this BAdI to determine key figure values according to company-specific determination rules. The system takes into account all objects (for example.  You have specified the required forms for legal reporting in the Customizing activity Specify Forms for Foundation for EHS Management. To include key figures for external persons or business partners in analytical reports. The key figures are determined for reporting purposes:  Full-Time Equivalents: analytical reporting  Working Time analytical reporting and legal reporting.Use You can use this BAdI implementation to activate or deactivate the integration of Personnel Time Management (PT) for analytical reporting in SAP EHS Management (EHS-MGM). single or multiple uses). Standard settings The BAdI implementation is active in the standard system. you can create a customer-specific implementation of the Business Add-In Determination of FTE and Working Time. if appropriate. no key figure values are determined for external persons or business partners. Note If you activate this implementation and an implementation of the BAdI Determination of FTE and Working Time the system combines the results of both determination runs per employee. As only employee data is managed in PT. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). employees or business partners) that are directly assigned to an organizational unit or that are assigned to a subordinate organizational unit. . OSHA reporting Note The key figure values for Full-Time Equivalents and Working Time values are always determined per organizational unit and date period. Requirements You have made the required settings for analytical reporting using the Business Information Warehouse. Standard settings The BAdI is not active in the standard system. For more information about the standard settings (filters. BAdI: Determination of FTE and Working Time Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component.

you can change the appearance of the report lauchpad.Calendar date o IV_TO_DATE . Analytical Reporting Configure Report Launchpad Use In this Customizing activity. you can access analytical reports that were generated using a spreadsheet application or SAP NetWeaver Business Warehouse.BAdI Methods  READ_EXT_DATA You can use this BAdI method to read person information from external sources. Import Parameters o IV_FROM_DATE .Calendar date o IS_ORG_MAN_OBJ .Cumulated Working Time value for the imported calendar date and organizational management object o EV_NUMFTE .Cumulated Full-Time Equivalents value for the imported calendar date and organizational management object Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . From the launchpad.Embedding in the Enhancement Framework. You can change the following aspects of the report launchpad. The method is called for a date period for an organizational management object that is requested for analytical reporting.Structure containing the object type and the object ID of the organizational management object that uniquely identifies the organizational unit Export Parameters o EV_WORKTIME . for example:  Add and remove reports or dashboards  Change the layout  Change descriptions  Change the configuration of existing launchpad entries  Create new lauchpads  Configure a URL application that references a spreadsheet report Standard settings You can identify the report lauchpad for analytical reporting by using the following properties: Role: Instance: EHHSS REPORTS .

sap. Further notes For more information about analytical reporting with spreadsheets. Business Add-Ins Implementation: Determination of FTE and Working Time from P Use . Choose the report launchpad that you want to modify. o To modify an existing entry. select this entry in the tree on the left-hand side and modify its properties on the right-hand side of the screen. see the topic Generate Spreadsheet Report in the Application Help for SAP EHS Management at http://help.com/. o To add or remove entries from the lauchpad. add or remove entries from the tree on the left-hand side of the screen.Description: Health and Safety Reports Activities 1.

Standard settings The BAdI implementation is active in the standard system. BAdI Methods .  You have specified the required forms for legal reporting in the Customizing activity Specify Forms for Foundation for EHS Management. BAdI: Determination of FTE and Working Time Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. As only employee data is managed in PT. The system takes into account all objects (for example. you can create a customer-specific implementation of the Business Add-In Determination of FTE and Working Time. Requirements The following prerequisites must be met:  You have made the required settings for analytical reporting using the Business Information Warehouse. for example. OSHA reporting Note The key figure values for Full-Time Equivalents and Working Time values are always determined per organizational unit and date period. Requirements You have made the required settings for analytical reporting using the Business Information Warehouse. For more information about the standard settings (filters. Note If you activate this implementation and an implementation of the BAdI Determination of FTE and Working Time the system combines the results of both determination runs per employee.You can also use an implementation of this BAdI to determine key figure values according to company-specific determination rules. To include key figures for external persons or business partners in analytical reports. You can use this BAdI to determine the key figure values for Full-Time Equivalents and Working Time according to customer-specific rules. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). If you activate the BAdI implementation. The key figures are determined for reporting purposes:  Full-Time Equivalents: analytical reporting  Working Time analytical reporting and legal reporting. the system determines the key figure values for Full-Time Equivalents and Working Time per organizational unit and calendar day from PT. Standard settings The BAdI is not active in the standard system. if appropriate.You can use this BAdI implementation to activate or deactivate the integration of Personnel Time Management (PT) for analytical reporting in SAP EHS Management (EHS-MGM). single or multiple uses). employees or business partners) that are directly assigned to an organizational unit or that are assigned to a subordinate organizational unit. no key figure values are determined for external persons or business partners.

Structure containing the object type and the object ID of the organizational management object that uniquely identifies the organizational unit Export Parameters o EV_WORKTIME . you must ensure that these are complete in terms of data consistency and legal requirements. a BAdI implementation is delivered that performs the corresponding check in the standard system. for example. READ_EXT_DATA You can use this BAdI method to read person information from external sources. The method is called for a date period for an organizational management object that is requested for analytical reporting. BAdI: Check Readiness for Action Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. single or multiple uses). For more information about the standard settings (filters.Cumulated Full-Time Equivalents value for the imported calendar date and organizational management object Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . BAdI Implementations  BADI_RDY_FOR_ACT_INC_CLOSE . You can use this BAdI to perform checks on the following actions:  Set incident status to Closed  Set incident status to Void  Set investigation status to Closed For each action. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).Embedding in the Enhancement Framework. Standard settings The BAdI is active in the standard system. when generating legal reports based on the incident data.Cumulated Working Time value for the imported calendar date and organizational management object o EV_NUMFTE .Calendar date o IS_ORG_MAN_OBJ .Calendar date o IV_TO_DATE . Caution If you implement customer-specific checks. you can deactivate this implementation and use a customer-specific check instead. If necessary. Import Parameters o IV_FROM_DATE .

This BAdI implementation performs the following checks:  o Check if the Restricted Access attribute for the incident is set to Yes or No o Check if an incident group is assigned o Check if the Investigation Required attribute is set to Yes or No o If an investigation is required. check if all actions that are not recurring are complete o For any injured person. check if the Reporting Required attribute is set to Yes or No BADI_RDY_FOR_ACT_INC_VOID This BAdI implementation does not perform any checks in the standard system.Embedding in the Enhancement Framework. check if the investigation is completed o If the incident is an occupational incident. check if at least one notice of violation is assigned o If the incident has actions assigned. check if the Required in Summary Report attribute is set to Yes or No o For any release of incident.  BADI_RDY_FOR_ACT_INV_CLOSE This BAdI implementation performs the following checks: o Check if the Investigation Required attribute is set to Yes or No o Check if an investigation lead is assigned o Check if a major root cause is selected o Check if all investigation steps are complete Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . check if at least one involved person has the Injured Person role o Check for an injured person o If the incident is classified as Release. check if at least one release is assigned o Check if the Reporting Required attribute for a release is set to Yes or No o Check if assessments are complete and confirmed o If the incident is classified as a notice of violation. You need to create your own implementation if you want to implement customer-specific checks. You can use the following filter values when defining customer-specific BAdI implementations:  INCIDENT_CATEGORY o 001 Incident o 002 Near Miss .

when generating legal reports based on the incident data. If necessary. set the following filter values:  INCIDENT_CATEGORY = 002 (Near Miss)  ACTION_NAME = SET_CLOSED_ROOT  NODE_NAME = BASIC_INFO_ALL BAdI: Check Readiness for Action Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. Standard settings . To do this. you must ensure that these are complete in terms of data consistency and legal requirements. use transaction /bobf/conf_ui or execute the search help EHFND_ELM_BO_NODE_NAME in transaction SE11 in test mode using BO_NAME = EHHSS_INCIDENT. Example You want to define a check that is only executed if:  The incident is a Near Miss  The action that is performed to set the status to Closed  The BASIC_INFO_ALL node is processed. Caution If you implement customer-specific checks. a BAdI implementation is delivered that performs the corresponding check in the standard system. you can deactivate this implementation and use a customer-specific check instead.o   003 Safety Observation ACTION_NAME o SET_VOID_ROOT o SET_CLOSED_ROOT o INVESTIG_RESULT_SET_CLOSED NODE_NAME You can use all existing node names from business object EHHSS_INCIDENT. You can use this BAdI to perform checks on the following actions:  Set incident status to Closed  Set incident status to Void  Set investigation status to Closed For each action. To display the nodes of this business object. for example.

BAdI Implementations  BADI_RDY_FOR_ACT_INC_CLOSE This BAdI implementation performs the following checks:  o Check if the Restricted Access attribute for the incident is set to Yes or No o Check if an incident group is assigned o Check if the Investigation Required attribute is set to Yes or No o If an investigation is required. single or multiple uses). check if at least one notice of violation is assigned o If the incident has actions assigned. check if the Required in Summary Report attribute is set to Yes or No o For any release of incident. check if at least one release is assigned o Check if the Reporting Required attribute for a release is set to Yes or No o Check if assessments are complete and confirmed o If the incident is classified as a notice of violation. check if all actions that are not recurring are complete o For any injured person. You need to create your own implementation if you want to implement customer-specific checks. For more information about the standard settings (filters.The BAdI is active in the standard system. check if the Reporting Required attribute is set to Yes or No BADI_RDY_FOR_ACT_INC_VOID This BAdI implementation does not perform any checks in the standard system. check if at least one involved person has the Injured Person role o Check for an injured person o If the incident is classified as Release.  BADI_RDY_FOR_ACT_INV_CLOSE This BAdI implementation performs the following checks: Activities o Check if the Investigation Required attribute is set to Yes or No o Check if an investigation lead is assigned o Check if a major root cause is selected o Check if all investigation steps are complete . check if the investigation is completed o If the incident is an occupational incident. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

set the following filter values:  INCIDENT_CATEGORY = 002 (Near Miss)  ACTION_NAME = SET_CLOSED_ROOT  NODE_NAME = BASIC_INFO_ALL BAdI: Check Incident Reports Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. Caution . for example. you must ensure that these are complete in terms of data consistency and legal requirements. when generating legal reports based on the incident data.Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . use transaction /bobf/conf_ui or execute the search help EHFND_ELM_BO_NODE_NAME in transaction SE11 in test mode using BO_NAME = EHHSS_INCIDENT. If you implement customer-specific checks . To display the nodes of this business object. Example You want to define a check that is only executed if:  The incident is a Near Miss  The action that is performed to set the status to Closed  The BASIC_INFO_ALL node is processed. To do this.Embedding in the Enhancement Framework. You can use the following filter values when defining customer-specific BAdI implementations:    INCIDENT_CATEGORY o 001 Incident o 002 Near Miss o 003 Safety Observation ACTION_NAME o SET_VOID_ROOT o SET_CLOSED_ROOT o INVESTIG_RESULT_SET_CLOSED NODE_NAME You can use all existing node names from business object EHHSS_INCIDENT. You can use this BAdI to perform checks for data completeness in incident reports.

see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). check if the injury/illness information and body part information is maintained o Check if only the first reportable injury/illness or the first reportable unknown injury /illness is defined o Check if the incident-causing object or an incident-causing substance is maintained o Check if the Fatality attribute is set to Yes or No o If the Fatality attribute is set to Yes. o If an injury/illness was maintained. check if the date of death is maintained BADI_IRT_CHECK_BG_UNF_BER This BAdI implementation performs the following checks: o Check if the person exists in HR or exists as a business partner o Check if the Fatality attribute is set to Yes or No o Check if the incident time zone is maintained o Check if the address where the incident occurred is maintained o Check if a statement that can be included in reports is maintained o Check if an injury/illness is maintained. BAdI Implementations  BADI_IRT_CHECK_OSHA_301 This BAdI implementation performs the following checks:  o Check if the person exists in HR or exists as a business partner o Check if a first physician or a further treatment provider is maintained o Check if the Emergency Room attribute is set to Yes or No o Check if the Inpatient Overnight attribute is set to Yes or No o Check if the actual start working time for the injured person is maintained o Check if either an activity was selected. For more information about the standard settings (filters. check if a body part is maintained . you must also ensure that all actions are complete or are in the process of completing. or a free text description for the injured person's activity is maintained o Check if a statement that can be included in reports is maintained o If an injury/illness is maintained. Standard settings The BAdI is active in the standard system.If you deactivate or change a check. single or multiple uses).

see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . o Check if a first physician or a further treatment provider is maintained o Check if the actual start working time for the injured person is maintained o Check if the actual end working time for the injured person is maintained o Check if the position description is maintained o Check if the duration in position is maintained o Check if the organizational unit of the injured person is maintained o Check if the ceased work date and time is maintained o Check if end dates of absences are maintained BADI_IRT_CHECK_REL_REP This BAdI implementation does not perform any checks in the standard system. Standard settings For more information about the standard settings (filters. You can use the following filter values when defining customer-specific BAdI implementations:   Possible filter values for the incident category are: o INCIDENT_CATEGORY = 001 Incident o INCIDENT_CATEGORY = 002 Near Miss o INCIDENT_CATEGORY = 003 Safety Observation Possible filter values for form names are all form names that are entered in Customizing for EHS Management. the investigation lead is automatically set to the current incident manager. By default. BAdI: Specify Investigation Lead Determination and Workflow Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. BAdI: Calculate Risk Assessment and Determine Risk Icon . You need to create your own implementation if you want to implement customer-specific checks.Embedding in the Enhancement Framework. You can use this BAdI to change how the default investigation lead is determined. Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs .Embedding in the Enhancement Framework. single or multiple uses).

frequency and duration.Use This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM) component. For more information about the standard settings (filters. frequency and duration.Embedding in the Enhancement Framework. see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18). Activities Information about the implementation of BAdIs in the context of the enhancement concept is available in the SAP Library for SAP NetWeaver under BAdIs . single or multiple uses). You can use this BAdI to adapt the standard logic to calculate the risk assessment and to determine the risk icons that are displayed. the distinctive scores for severity. Requirements You have made the following settings in the Customizing for SAP EHS Management under Incident Management: Specify Affected Areas Specify Severity Specify Likelihood Specify Frequency Specify Duration Classifications Specify Risk Ratings Standard settings This BAdI is active in the standard system. and returns the value for the risk icon. likelihood to reoccur. The risk rating is calculated for each affected area based on configurable scores for the following risk parameters: severity. The risk icons are set according to the risk rating. The calculated value can be manually overwritten by the user. likelihood to reoccur. the precalculated sum of risk scores. The default logic for calculating the risk assessment and determining the risk icons is as follows:  The scores of the affected areas are added  The rating is determined according to the lower and upper limit of the sum of scores  The risk icon is determined according to the risk rating configuration The BAdI method calculate_risk receives the risk assessment type (initial or residual). .