sap ehsm

Component Extension for SAP Environment, Health, and Safety Mana PDF download from SAP Help Portal: http://help.sap.com/saphelp_ehsext30/helpdata/en/5b/22b8d6606b4d32b8af9283901d3bdc/content.htm Created on November 06, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 82

Table Tab le of content cont ent 1 Component Extension for SAP SAP Environment, Environment, Health, and and Safety Mana 1.1 1.1 Foundation for EHS Management Management (EHS-MGM-FND) (EHS-MGM-FND) 1.1. 1.1.1 1 Business Objects 1.1. 1.1.1. 1.1 1 Adding Fields to the User User Interface 1.1.1.2 1.1.1.2 Field Control Contro l 1.1.1.3 1.1.1.3 Document Docum ent Storage Stora ge 1.1.1.4 1.1.1.4 Creation Crea tion of Change Documents Docume nts 1.1.2 1.1.2 Process Proc ess Foundation Foundati on (EHS-MGM-FND-WF) 1.1.2.1 1.1.2.1 PCOs and PCBOs 1.1.2.2 1.1.2.2 Proc Pr ocess ess Configuration Configurat ion 1.1.2.2. 1.1.2.2.1 1 Changing Workflow Wor kflow Template Temp lates s 1.1.2.3 1.1.2.3 Task Management Manage ment 1.1.2.3.1 1.1.2.3.1 Changing the Task Processo Proces sor r 1.1. 1.1.2. 2.3.2 3.2 Continuing Continuing Execution Execution of a Proce ss with Errors 1.1. 1.1.2. 2.4 4 Process Proces s Tools 1.1. 1.1.3 3 Print Forms and Interac Interactive tive Forms (EHS-MGM-FND-FR (EHS-MGM-FND-FRM) M) 1.1. 1.1.3.1 3.1 Adding Print Print Forms and Interactive Interactive Forms 1.1. 1.1.3.2 3.2 Mapping Business Business Objects Nodes to Adobe Forms 1.1.4 1.1.4 Integration Integratio n (EHS-MGM-FND-INT) 1.1. 1.1.4.1 4.1 Integration Integration for Person IInformation nformation 1.1.4.2 1.1.4.2 Integration Integratio n for Notifica Notifi cations tions 1.1. 1.1.4.3 4.3 Check for Completed Notifications 1.1.5 Locations 1.1.5.1 Location 1.1. 1.1.5.2 5.2 Maintaining Locations and the Structure 1.1. 1.1.5.3 5.3 Importing Locations from PM 1.1.6 Chemicals 1.1. 1.1.6.1 6.1 Creating and Revisi Revising ng Regulatory Lists 1.1. 1.1.6.2 6.2 Transferring Data Data from the Specification Specific ation Database 1.1. 1.1.7 7 Analytical Reporting 1.1. 1.1.7.1 7.1 File-Based Reporting 1.1. 1.1.7.2 7.2 Data Extraction to BW 1.1.7.3 DataSources 1.1. 1.1.7.3.1 7.3.1 Workflow Process Definitions 1.1. 1.1.7.3.2 7.3.2 Workflow Process Instances Instances 1.1. 1.1.7.3.3 7.3.3 Workflow Step Definitions 1.1. 1.1.7.3.4 7.3.4 Workflow Step Instances Instances 1.1. 1.1.7.3.5 7.3.5 Workflow Process Proces s Definitions - Text Extraction (Full) 1.1. 1.1.7.3.6 7.3.6 Workflow Reporting - Component Description 1.1. 1.1.7.3.7 7.3.7 Workflow Reporting - URL URL Extraction (Full) 1.1. 1.1.7.3.8 7.3.8 Workflow Step Definitions - Text Extraction Extractio n (Full) (Full) 1.1. 1.1.7.3.9 7.3.9 Texts for Material ID ID 1.1. 1.1.7.3.1 7.3.10 0 Common Objects 1.1. 1.1.7.3.1 7.3.10.1 0.1 Location Master Data 1.1.7.3.10.2 1.1.7.3.10.2 Location Loca tion Hierarc Hier archy hy 1.1. 1.1.7.3.1 7.3.10.3 0.3 Texts for Location 1.1. 1.1.7.3.1 7.3.10.4 0.4 Texts for Location Type Type 1.1. 1.1.7.3.1 7.3.10.5 0.5 Texts for Location Authoriza Authorization tion Group 1.1.8 Roles 1.1. 1.1.8.1 8.1 Business Package (Portal Content) Content) 1.1. 1.1.8.1. 8.1.1 1 Business Package for EHS Management Management 1.1.8.1.2 1.1.8.1.2 Configuration Configurat ion Information Informat ion 1.1. 1.1.8.1. 8.1.2. 2.1 1 Adding Incident-Related Incident-Related iViews to the Employee Employ ee Self-Service Cent Ce nt 1.1.8.1.2 1.1.8.1.2.2 .2 Creating Crea ting Custom Roles 1.1. 1.1.8.1. 8.1.2. 2.3 3 Setting Up the System Landscape 1.1.8.1.2 1.1.8.1.2.4 .4 Setting Setti ng Up the Universal Univer sal Worklist Worklis t 1.1. 1.1.8.1. 8.1.2. 2.5 5 Role Assignments for Cross Cross-Role -Role Activities 1.1.8.1.3 Roles 1.1.8.1.3.1 1.1.8.1.3.1 Incident Manager Mana ger 1.1.8.1.3.1 1.1.8.1.3.1.1 .1 Health Heal th and Safety Safe ty


Page 2 of 82

1.1.8.1.3.1.1.1 Overview 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.1 1.1 Work Wor k Overvie Ove rview w 1.1.8.1.3.1.1.1.1.1 Inbox 1.1.8.1.3.1.1.1.2 Incidents 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.1 1 Incident Entry Scree Screen n 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.2 2 Incident Search Searc h 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.3 3 Report Repo rt Incident Incide nt (Simplifie (Simp lified) d) 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.4 4 Report Repo rt Incident Incide nt 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.5 5 Report Repo rt Near Nea r Miss Mis s 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.6 6 Report Repo rt Safety Safe ty Observ Obs ervatio ation n 1.1. 1.1.8.1. 8.1.3.1. 3.1.1. 1.1. 1.2. 2.7 7 Display Progress Log for External Exte rnal Notifications Notificatio ns 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.8 8 Notify Notif y Task Process Proc essor or 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.9 9 Display Disp lay Applicatio Applic ation n Log 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.10 10 Execute Exe cute Process Proc ess Decision Decisi on 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.11 11 Display Disp lay Incident 1.1.8.1.3.1.1.1.2.12 1.1.8.1.3.1.1.1.2.12 Edit Edi t Incident Incid ent 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.13 13 Investigate Investi gate Step 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.14 14 Take Over Inquiry Inquiry Respons Res ponse e 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.15 15 Display Disp lay Generic Process Proce ss Setup 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.16 16 Edit Generic Proces Proc ess s Setup 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.17 17 Display Disp lay Change Documents Docume nts 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.18 18 Create Crea te Generic Gener ic Process Proc ess Setup 1.1.8.1.3.1.1.1.2.19 1.1.8.1.3.1.1.1.2.19 Change Assignee Ass ignee 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.20 20 Assign Ass ign Absence Abse nce to Incide Incident nt 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.21 21 Display Disp lay Person Perso n Details Deta ils 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.2. 1.2.22 22 Display Disp lay PM Notifica Notif ication tion 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3 1.3 Incident Reports Repo rts 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3.1 1.3.1 Review Rev iew Incident Summary Reports Report s 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3.2 1.3.2 Change Paramete Para meters rs for Sending Reports Repo rts 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3.3 1.3.3 Display Disp lay/Edit /Edit Incident Summary Summar y Report Repo rt 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3.4 1.3.4 Create Crea te Incident Report 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3.5 1.3.5 Change Incide Incident nt Report Repo rt 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.3.6 1.3.6 Generate Gener ate Incid Incident ent Report Repo rt 1.1.8.1.3.1.1.1.4 Locations 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.1 1.4.1 Explore Exp lore Loca Locations tions 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.2 1.4.2 Create Crea te Location Loca tion 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.3 1.4.3 Manage Structure 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.4 1.4.4 Import from PM 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.5 1.4.5 Change Attributes Attrib utes 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.6 1.4.6 Display Disp lay Location Loca tion 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.7 1.4.7 Edit Location Loca tion 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.8 1.4.8 Display Disp lay Location Loca tion Structure Structur e 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.9 1.4.9 Edit Location Locatio n Structure Structur e 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.4.10 1.4.10 Display Disp lay Where-Used Where-Use d List 1.1.8.1.3.1.1.1.5 Tasks 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.5.1 1.5.1 Display Disp lay HSS Tasks 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.5.2 1.5.2 Forward Forwa rd Task to Another Another Process Proc essor or 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.5.3 1.5.3 Proces Proc ess s Details Deta ils 1.1.8.1.3.1.1.1.6 Processes 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.6.1 1.6.1 EHS Management Manage ment Task (Technical (Tec hnical Inform Informatio ation) n) 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.6.2 1.6.2 Graphical Grap hical Workflow Workflo w Log 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.6.3 1.6.3 Technical Technic al Workflow Wor kflow Log Log 1.1.8.1.3.1 1.1.8.1.3.1.1. .1.1.6.4 1.6.4 Open Ope n Comment Comme nt 1.1.8.1.3.2 1.1.8.1.3.2 Incident Reporter Repo rter 1.1.8.1.3.2 1.1.8.1.3.2.1 .1 Health Heal th and Safety Safe ty 1.1.8.1.3.2.1.1 Overview 1.1.8.1.3.2.1.1.1 Incidents 1.1.8.1.3.2.1.1.1.1 1.1.8.1.3.2.1.1.1.1 Wor W orkse ksett Map Ma p 1.1.8.1.3.2 1.1.8.1.3.2.1. .1.1.1. 1.1.2 2 Report Repo rt Incident (Simplifie (Simp lified) d) 1.1.8.1.3.2 1.1.8.1.3.2.1. .1.1.1. 1.1.3 3 Report Repo rt Incident Incide nt 1.1.8.1.3.2 1.1.8.1.3.2.1. .1.1.1. 1.1.4 4 Report Repo rt Near Nea r Miss Mis s 1.1.8.1.3.2 1.1.8.1.3.2.1. .1.1.1. 1.1.5 5 Report Repo rt Safety Safe ty Observ Obs ervatio ation n


Page 3 of 82

1.1. 1.1.8.1. 8.1.3.3 3.3 Notification Notificatio n Recipient Recipie nt 1.1.8.1.3.3.1 1.1.8.1.3.3.1 Health Heal th and Safety Safe ty 1.1.8.1.3.3.1.1 Overview 1.1.8.1.3.3.1 1.1.8.1.3.3.1.1. .1.1 1 Work Wor k Overvie Ove rview w 1.1.8.1.3.3.1.1.1.1 Inbox 1.1.8.1.3.3.1.1.2 Incidents 1.1.8.1.3.3.1 1.1.8.1.3.3.1.1. .1.2.1 2.1 Execute Exe cute Proces Proc ess s Decisio Dec ision n 1.1.8.1.3.3.1 1.1.8.1.3.3.1.1. .1.2.2 2.2 Display Disp lay Incide Incident nt 1.1. 1.1.8.1. 8.1.3.4 3.4 Process Proces s Administrator 1.1.8.1.3.4.1 1.1.8.1.3.4.1 Health Heal th and Safety Safe ty 1.1.8.1.3.4.1.1 Overview 1.1.8.1.3.4.1.1.1 Processes 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.1 1.1 Display Disp lay Process Proc ess Definitions 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.2 1.2 Check Workflow System Syste m 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.3 1.3 Check Process Proc ess Definition Definitio n 1.1. 1.1.8.1. 8.1.3.4.1 3.4.1.1 .1.1 .1.4 .4 Display Technical Tec hnical Details for Process Proc ess Definition 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.5 1.5 Check Process Proc ess Instance 1.1. 1.1.8.1. 8.1.3.4.1 3.4.1.1 .1.1 .1.6 .6 Display Technical Tec hnical Details for Process Proc ess Instance 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.7 1.7 Display Disp lay Proces Proc ess s Instances Instance s 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.8 1.8 Technical Technic al Workflow Wor kflow Inbox Inbox 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.9 1.9 Technical Technic al Workflow Wor kflow Log Log 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.10 1.10 Graphica Grap hicall Workflow Wor kflow Log 1.1.8.1.3.4.1 1.1.8.1.3.4.1.1. .1.1.11 1.11 EHS Management Manage ment Task (Technical (Tec hnical Information) Informati on) 1.1.8.1.3.4.1.1.1.12 1.1.8.1.3.4.1.1.1.12 Open Ope n Comme Com ment nt 1.1.8.1.3.5 1.1.8.1.3.5 Environmental Enviro nmental Manager Manage r 1.1.8.1.3.5.1 1.1.8.1.3.5.1 Health Heal th and Safety Safe ty 1.1.8.1.3.5.1.1 Overview 1.1.8.1.3.5.1 1.1.8.1.3.5.1.1. .1.1 1 Work Wor k Overvie Ove rview w


Page 4 of 82

1 Component Extension for SAP Environment, Health, and Safety Management Product Information Product

Component extension for SAP Environment, Health, and Safety Management (SAP EHS Management)

Release

3.0 SP03 or higher

Based On

SAP ERP 6.05 or 6.06 SAP NetWeaver 7.02 or 7 .31

BI Content Release

SAP NetWeaver 7.0 BI Content Add-On 7 Extension for SAP N etWeaver 7.0 BI Content Add-On 7 (dashboards)

Documentation Published

October 2013

Use Component extensi on for SAP Environment, Health, and Safety Management ( SAP EHS Management ) is an add-on to SAP ERP and supp orts your organization in managing business processes related to environment, health, and safety. This component extension provides comprehensive functionality to support you in the following scenarios and their corresponding processes: Health and Safety Managing incidents Managing EHS risk Managing EHS locations Product Safety and Stewardship Managing product c ompliance Managing IMDS compliance This add-on features integration points with other SAP components throughout the solution and a foundation layer that connects the p rocesses of SAP EHS Management to the SAP Business Workflow engine. If you use existing components in SAP EHS Management as part of SAP ERP or SAP Product and REACH Compliance that support these processes, they are still supported. However, further enhancements are developed in this add-on. This component extension for SAP EHS Management is p art of SAP Business Suite. The documentation for this component extension for SAP EHS Management offers a comprehens ive des crip tion of the functional scope and highli ghts the relationship between the application and the underlying technologies.

1.1 Foundation for EHS Management (EHS-MGM-FND) This component provides the required functionality and infrastructure to use SAP EHS Management . You use this component in the following ways: Business Objects Business objects are the basic building blocks that store the data and provide the business l ogic to support your processes. Business objects in SAP EHS Management are implemented using the Business Ob ject Processing Framework (BO PF). You can add new fields and nodes to business objects, control how the fields appear and behave on the user interface, and store documents for a business object. For more information, see Business Objects. Process Foundation The process foundation helps y ou execute your bus iness p rocess es using the SAP Business Workflow, and helps you to manage tasks. You can extend and adapt delivered process specifically for your organization. The process foundation also provides tools and services to make process administration easy. Print Forms and Interactive Forms You can use forms in the components of SAP EHS Management . You can use the forms delivered in the standard sy stem, or adapt forms and add customer-specific ones. Integration There are integration points to other sys tems in SAP EHS Management . This enab les y ou to acc ess data that you already store in other systems and communicate with those systems. Locations You can use locations in SAP EHS Management to repres ent the real plac es, v irtual sp aces , and objec ts at your organization in the sy stem. The location makes i t possib le to harmonize existing ass ets in the Plant Maintenance component and to migrate work areas from the old solution provided b y SAP for managing environment, health, and safety. Chemicals You can use chemical data in your business processes, for example, chemical agents in assessing risk and listed substances in ensuring product compliance. Customer lists and regulatory lists help you group listed substances according to regulatory or company-specific policy and integrate this information into your processes. Analytical Reporting This section provides information about the functionality to support you in generating analytical reports. Roles SAP EHS Management is delivered with roles, work centers, worksets, and iViews to help y ou define how your users can use the app lication. SAP EHS Management provides c ontent in the Business Pack age (portal content) and for the SAP NetWeaver Busines s Client (NWBC).


Page 5 of 82

Integration The foundation of SAP EHS Management is us ed entirely or in part in the following components: Incident Management Risk Assessment Product Compliance (EHS-MGM-PRC)

1.1.1 Business Objects SAP EHS Management is delivered with the following business objects (BOs) to support your business processes. Common objects Action There is an action objec t for each component of SAP EHS Management . It allows you to store data, such as the task p rocess or, the category (action or notification), and p rotection goal. Location (EHFND_LOCATION ) You can use the location in incident management and risk assess ment to represent identified real places, virtual spac es, or objects in the system. For more information about using this business object, see Locations. Chemical (EHFND_CHEMICAL ), regulatory list (EHFND_REGLIST ), and listed substance (EHFND_LISTED_SUBSTANCE ) You can use the chemical to store information for chemical agents in risk assessment, and you can use regulatory lists and listed substances in risk assess ment and product compliance. Process Control Business Ob jects There is one process c ontrol bus iness object (PCBO) for every process supp orted by SAP EHS Management . This b usiness object stores the data that belongs to a process and provides the required functions for executing a process. Business objects for incident management Incident (EHHSS_INCIDENT ) The incident business object allows you to collect all the relevant data for recording incidents, near misses, and safety observations. For more information about this business object, see Incident. Report/forms (EHHSS_INCIDENT_REPORT and EHHSS_INCIDENT_SUMMARY_REPORT ) The report business object stores the data that is relevant to a report or a form, for example, the form name, language, and generation date. Business objects for risk assessment For a list of the business objects used for risk assess ment, see Business Objects for Risk Assessment. Business objects for product compliance For a list of the busi ness objects used for product compliance, see Business Obj ects for Product Compliance

Structure The business objects of SAP EHS Management have been modeled in the Business Ob ject Processing Framework (BO PF). BOPF controls the app lication businesses logic as well as the data retrieval of the buffer and persistency layer. You can display and make yourself familiar with the structure and logic of a business object in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI ).

1.1.1.1 Adding Fields to the User Interface You can add fields to the user interface (UI) of a Web Dynpro application that is based on the integration of the Floorplan Manager and the Business Object Processing Framework (BO PF).

Prerequisites You have experience usi ng data definitions in the ABAP Di ctionary, have some experience with busi ness objects based on BOPF (transaction /BOBF/CUST_UI ), and have ex perience configuring Web D ynpro ABAP user interfaces with the Floorplan Manager for Web D ynpro ABAP (FPM).

Procedure To add fields, you have to perform two main activities: 1. Add the fields to the bus iness objec t 2. Modify the GUIBB configuration to incl ude the fields

Adding Fields to the Business Ob ject

Note Each BO node generally consists of a particular DDIC structure that is used for adding new fields, for example. To add new fields to the business object without modifying it, you have to append a structure to the Extension Include for the corresponding BO node.

1. Call transac tion /BOBF/CUST_UI and select the business object that you want to change. 2. Then select the node structure that you want to enhance. 3. Double-click the Extension Include to display the ABAP Dictionary maintenance for this structure. 4. Then choose

Goto

App end Structure

to display the ABAP Dictionary maintenance for the append structure.

5. In the dialog box, enter the name of the append structure. Then clic k Continue .


Page 6 of 82

6. In the Dictionary maintenanc e for this s tructure, provid e a short descrip tion of the structure. Enter the components (in this c ase, the fields ) that you want to add and specify their type. Then choose Activate to activate the changed structure.

Modifying the GUIBB Configuration

Note The following steps describe how you enhance generic user interface building block (GUIBB) configurations. For more information about adapting GUIBB configurations, see Fitting Web Dynpro to Your Needs. You can determine the name of the Web D ynp ro Appl ication from the technical information in More Field Help on the context menu of the resp ectiv e screen.

1. Start the configuration editor in adminis trator mode. You use the administrator mode of the Web Dynpro Explorer to make modification-free changes to a user interface with the configuration editor for Floorplan Manager. To start the configuration editor in administrator mode, perform the steps described in the Procedure of Administrator Mode. 2. The Component Configuration sc reen is now display ed. Choose Configure UIBB for Form UIBB (1) . 3. On the next screen, c hoose the group to which the new field is to be added. Choose Configure Group . 4. The Configure Group dialog box is displayed. Here you can select which of the available fields s hall be dis played in the G UIBB at runtime. The list of Available Fields should include the previously added component. Select this field and choose Add Fields . You can change the disp lay sequence for the field you just added. Then choose OK . 5. The new field is now display ed on the Component Configuration sc reen. Here you can selec t the field to change the properties of the Attributes Element . Choose Save to sav e your changes to the UIBB. The next time the GUIBB is l oaded, the new fields will be dis play ed.

Note If the new UI field is to be based on a customizable code field, you create additionally a corresponding customizing table and maintenance view using transaction SE54 , and add a corresponding searc h help. You can then define a list of valid entries us ing the maintenance view for the field. In the GUIBB configuration, you can optionally change the UI element of the corresponding field to a dropdown box displaying the list of valid data.

Result You have successfully added the new field to your Web Dynpro application. Since the new field is part of a BO node extension include, the data that was entered is saved and retrieved successfully without any additional changes or modifications to the BO itself. The FBI-based Web Dynpro application itself also handles the data access without you needing to make any changes or modifications to the BO or the UI. This approach to adapt the Web Dynpro screens applies not only to adding fields, but also to other screen changes, for example, renaming labels and changing the sequence of fields and groups.

More Information For more information about the BOPF enhancement framework, see SAP Note 1457235. For more information about FPM, see Floorplan Manager for Web Dynpro ABAP.

1.1.1.2 Field Control This function enables y ou to adapt the user interface to ensure that you record and process ex actly the data that you need in SAP EHS Management . Field control enables you to control the behavior and appearance of the fields, buttons, and groups on the user interface at runtime if a data record fulfills certain conditions. For examp le, if you use SAP EHS Management to record work-related injuries and il lness es, y ou can adapt the user interface to make c ertain fields visible and mandatory for a specific region or country. This function helps organizations to fulfill data recording and regulatory compliance requirements.

Prerequisites You are familiar with the structure of the business objects of SAP EHS Management that are modeled in the Business O bject Processing Framework (BOPF). For more information about the busines s objects of SAP EHS Management , see Business Objects. You have specified field control in Customizing for SAP EHS Management under Specify Field Control

Foundation for EHS Management

Settings for Business Ob jects

.

Features Field control provides the following features: Profiles Field control uses profiles to store the information about both the conditions that a data record must fulfill for field control to apply, and how the system then controls the user interface when field control applies. You can set up a profile to use the following conditions when determining if field control applies: Node Attribute Value You can use profiles that are based on an entered value for a given field (node attribute). For example, when you have entered the value X for the Y field, the corresponding p rofile ap plies. Authorization-Based Profile You can use profiles that adapt the user interface based on a user’s authorizations for the corresponding node level. This way, you can ensure that the sys tem provides data access and the possibility to execute bus iness logic only to authorized users.


Page 7 of 82

Function Class You can use profiles that contain customer-specific logic implemented by classes. This allows you to specify more complicated logic for a field if basing the profile on a node attribute value is not sufficient. You can set up a profile to use the following property settings to control how the system applies field control: Attribute Attr ibute You can sp ecify fields to be enabled (v isib le), read-only, read-only, or mandatory. mandatory. Node You can specify whether instances of the node can be created, read, updated, or deleted. Action You can specify the actions that a user can perform on the data of a corresponding node, for example, change the status, create subnodes, and so on.. on Association Associatio n You can specify other nodes that are associated with the node of your profile. This makes it possible to apply field control settings for a given profile to associated nodes. Such settings specify, for example, if a new data record of an associated node can be created. Merge Strategy When you have two or more profiles whose conditions all apply in parallel for a certain node, but which define contradicting property settings, you can specify a merge strategy. This strategy dictates priorities for contradicting property settings. Propagation You can apply node and association property settings dynamically to all subnodes (to the whole subtree). This saves configuration effort if you want to reuse settings in a field control profile.

1.1.1.3 1.1 .1.3 Docu Documen mentt Storage This function enables y ou to to use the Content Content Management Servi ce to store store documents, suc h as attachments and generated PDF rep orts, in SAP EHS Management . You can define the storage location location for for these documents, for examp le, in the databas e or in an external content server.

Features Document storage provides the following features: The connection to the Content Management Service is specified and implemented by the attachment folder (ATF) object of the Business Object Processing Framework. Such attachment attachment folders folders are assi gned to the corresp corresp onding busines s objects of SAP EHS Management . Print forms and SAP Interactive Forms by Adobe, as well as other attached documents of any format, are stored using such attachment folder objects within the Content Management Service.

More Inf Information ormation For more informatio information n about configuring document document storage fo forr SAP EHS Management , see Customizing Customizing for for SAP EHS Management under Manageme Mana gement nt

Business Busine ss Objects

Specify Docu Document ment Sto Storag rage e

Foundation Foundatio n for for EHS

.

For more information about the Content Management Service, see Content Management Service. Service.

1.1.1. 1.1 .1.4 4 Creation of Chang Change e Documents You can use change documents to trace the changes made to a data record. Change documents enable you to document data changes, and support you in fulfilling your auditing requirements. The following types of change documents are available: Change documents for incident records Change documents for location records Change documents for actions and notifications Change documents for risks Change documents for risk assessments The type of change documents you can access depends on where you are in the application. For example, you can only display change documents for actions and notifications, notifications, if an action or notif notification ication is selec ted on on the Tasks tab.

Features You can acces s chan ge documents by c hoo hoosing sing the relevant entry from the You can also link. Note that that if you want to acc ess c hange documents relevant to a control, contro l, you must choose choose the Dis play Change Documents pus hbutton on the Tasks for Contro Controll dialog box. After After you have entered parameters to limit the changes that are displayed, you can see the following information in the results list: Date and time of the change Type of change, for example, an update or insertion Name of the business object node that stores the change, for example, incident root or involved person role (Old) Value before the change, and the (new) value after the change Affected Affe cted field User who made the change Details about the change action

More Inf Information ormation


Page 8 of 82

For more information about change documents, see SAP Help Portal at http://help.sap.com/nw70/ http://help.sap.com/nw70/.. Cho Choose ose NetWeaver NetW eaver by Key Capability Function Functio n Library

App licatio lication n Platform by Key Capability

Change Document Documents s

ABAP Technology

SAP Library

SAP NetW NetWeaver eaver

ABAP Wo Workbench rkbench (BC-DWB)

SAP

BC Exten Extended ded App licatio lications ns

.

1.1 1 .1.2 .2 Process Foundation (EHS-MGM-FND-WF (EHS-MGM-FND-WF)) The process process fo foundat undation ion is essential to the the business processes supp ort orted ed by SAP EHS Management . It links links the SAP Business Wo Workflo rkflow w engine and the the business objects of SAP EHS Management to togeth gether. er. This This “link” comprises p arts that are are common common to every implementation implementation of a process, namely a p rocess control business object (PCBO) for storing process-relevant information and a process control object (PCO) for communicating with a workflow at runtime. The process foundation provides a general base for the handling of workflows associated with your business object, and makes adapting and extending the processes easy. In addition, the process foundation makes it possible to collect statistical data about tasks and processes as well as monitor them. The system is delivered with processes processes .

Integration The process foundation uses the Workflow Engine of SAP Bus iness Workflow Workflow.

Features The process foundation provides the following features: Easy implementation implementation of your your business processes in the system as p ro rocess cess es You can use processes for internal and external communication, sending notifications, assigning tasks, complying with regulatory requirements, reporting, and so on. Adaptation Adaptatio n of a process to match match country country and region-specific region-specific needs You can create variants of existing processes for a specific country or region. Custom Custo m development capabil ities You can use customer-specific business logic in ABAP Objects to create new process variants. Statistical data collection and monitoring capabilities You can monitor and analyze the progress of your business processes as well as monitor the completion of the tasks associated with processes.

More Inf Information ormation For more information about the processes of incident management that use the process foundation, see Incident Workflows and Tasks. Tasks. For more information about the processes of risk assessment that use the process foundation, see Risk Asses sment Workflo Workflows ws and Tasks. Tasks. For more information about the processes of product compliance that use the process foundation, see Product Compliance Workflows and Tasks

1.1. 1. 1.2.1 2.1 PC PCOs Os and PC PCBOs BOs The following following objec ts make up the process foundation that that was developed for SAP EHS Management . They They p rovide a layer of integration integration between the busines s objects stored stored with the Business O bject Processing Framewo Framework rk (BO PF) and the SAP B usiness Wo Workflo rkflow. w. Process control bus iness object (PCBO) The PCBO is a BO PF b usiness object that represents represents a workflow-driven workflow-driven process in the system. It provides the logic, logic, such as the action action that starts starts the workflo wo rkflow w in SAP Business Wo Workflo rkflow, w, and stores the process-spec ific data, such as the process definit definition ion key. Process control object (PCO) A PCO is an ABAP Ob jects class that represents a process control control business object in the the workflo workflow w for for a spec ific process in SAP EHS Management Management . The PCO makes it technically p ossible to use the BOP F bus iness objects with the workflo workflow w functions functions of SAP Busi ness Workflow. Workflow. The class CL_EHFND_WFF_ROOT_PCO is the most most basic abstract PCO c lass in the foundat foundation ion for for SAP EHS Management . It implements implements all the bas ic functionality needed for all processes. There are also foundation PCO classes for each specific type of process, for example, for inquiries or requests, notifications, and approvals.

Since the SAP Workflow Workflow System can only only communicate with with ABAP O bjects c lasses and b usiness object repository repository (BOR) objects, SAP EHS Management Management uses the PCO as a layer to make BOPF business objects and their functiona functionality lity available to the the workflo workflow w sy stem. For For each PCBO in the BOPF, a corresponding corresponding PCO class exists. The PCBO is valid for the duration of the process and the data is archived. The following sections describe in detail how the PCO and PCBO are used:

Use in Processes The PCO is used for communication from the workflow in SAP Business Workflow to its corresponding PCBO. The PCBO is where the business logic is implemented and the process-relevant data is stored. The workflow can add to and read this data with the help of the PCO. The PCBO also contains a reference to the business object that the process process supp or orts. ts. The graphic below illustrates illustrates how how PCOs and PCBOs help y ou execute processes in SAP EHS Management Management .


Page 9 of 82

PCO and PCBOs in the Process Foundation

You start a process on the user interface of the application, for example, when you add an inquiry in incident management (see Inquiries Inquiries). ). The system creates an instance of the PCBO according to the corresponding process definition, for example, an instance of the inquiry PCBO for the incident inquiry process. The event CREATED is emitted by the call of an action (START_WORKFLOW_ROOT) for the newly created PCBO instance. This starts the workflow in SAP Business Wo Workflo rkflow. w. The PCO acts as a wrapper for the the respective PCBO and implements the ABAP Ob jects interface interface IF_WORKFLOW IF_WORKFLOW.. By implementing this interface, the PCO is recognized as workflow-enabled in the Class Builder, and the Workflow Engine can use it. The PCO calls the business logic from the PCBO that is to be executed in a workflow task, and also reads the data from the PCBO, so the data is available to the workflow. When you change the attributes of a task (for example, the approver of a maintenance notification) on the user interface of the application, the BOPF provides a functionality so the PCBO can read, update, or delete the data automatically.

Use in Monitoring and Analyzing Processes The data about a process that is stored in the PCBO is also used in monitoring and analyzing processes. For more information, see Process Scheduling and Process Monitoring. Monitoring.

More Inf Information ormation ABAP O bjects c lasses SAP B usiness Wor Workflow kflow

1.1.2. 1. 1.2.2 2 Process Conf Configuration iguration SAP EHS Management is delivered with processes and a p ro rocess cess fo foundat undation ion to to support your your business processes. You can extend and adapt these these processes , as well as c reat reate e cus to tomer-specific mer-specific process variants. This This do document cument provides an overview of the the configuratio configuration n p ossibilities.

Prerequisites You have development development experience with ABAP O bjects and have some experience with business objects based on the Business O bject Processing Framework Framework (BOPF) (tra (transaction nsaction /BO BF/CUST_UI ). You have read the topic PCOs and PCBOs. PCBOs .

Activities You can configure processes in the following ways: Adapt existing process You can adapt existing processes delivered in the standard system to suit your customer-specific processes. For more information, see Customizing for SAP EHS Managemen Managementt under

Foundatio Fou ndation fo forr EHS Manageme Management nt

Process Fou Foundatio ndation

Extend and Adapt Processes

.

Add new fields fields to store process-spec ific data You can add new fields to the exis ting PCBO to collect additional proces s-s pec ific data. For more informatio information, n, see Customizing Customizing under Managementt Managemen

Foundat Fou ndation ion fo forr EHS Managemen Managementt

Process Fou Foundat ndation ion

Extend Exten d and Adapt Processes


SAP EHS

and Adding and Adding Fields to the User User Interface Interface..

Page 10 of 82

Note PCO c lasses provide the data data structures of their their PCBOs as p ublic fields. This This means, the SAP Business Wo Workflo rkflow w can read the new fields automatically that you have added. Add new variants variants of a process process You can add a new variant to an existing process. You use a variant of the standard action process, for example, in incident management to handle sending notifications notif ications to integrated sy stems. For more informatio information n about variants , see Customizing Customizing for for SAP EHS Management under Managementt Managemen


Specify Process Definitio Definitions ns

Foundation Foundatio n for for EHS

.

Define logic to control how the system starts a process The system uses an implementation of the BAdI BADI_EHFND_WFF_PCBO_CREATION to create create and start start process process es in SAP EHS Management Management . You You can define customer-specific logic to control how the system starts a process. You do this, for example, when your organization must comply with regulatory requirements in more than one country or region, and you need the system to start a different or separate process for each country or region. For more informatio information, n, see Customizing for SAP EHS Management unde r Initialize Init ialize Process Co Contro ntrol Ob jects (PCBOs)

Foundation Foundatio n fo forr EHS Management

Process Foundation Foundation

BAdI: Create and

.

Create customer-specific logic for a process in the PCO If you do not want to implement customer-specific logic in the PCBO, you can extend or change an existing PCO class to create customer-specific logic for a process. This way, a person with experiencing developing in AB AP O bjects can imp lement this this logic and mus t not extend extend the PCBO. For more more information, informatio n, see Customizing fo forr SA P EHS Management under Processe Pro cesses s

Foundation Foundatio n for EHS Management

Process Foundation Foundation

Extend and Adapt

.

To start a workflow when the CREATED event of the customer-specific PCO class is triggered, you must assign a workflow template to this event. You can do this in the Workflow Builder on the Start Events Events tab in the vers ion-independent bas ic data of of the the relevant workflow workflow templ templ ate.

More Inf Information ormation For more information about changing workflow templates, see Changing Workflow Templates. Templates .

1.1.2.2.1 1.1 .2.2.1 Chan Changing ging Workflow Templates The workflow templates in the standard system for for SAP EHS Management cover the standard proces ses of inci dent management and risk ass ess ment. You can change workflow templates to include new steps or change the process flow.

Prerequisites You have experienc e using the Workflow Builder . Knowledge Knowledge of ABAP programming is an advantage. You have carried out out automatic automatic workflow workflow Customizing. Customizing. For more informatio information, n, see Customizing for SAP EHS Management under Managementt Managemen


Basic Sett Settings ings

Perform Perfo rm Auto Automatic matic Wo Workflo rkflow w Custo Customizing mizing

Foundation Foundatio n for EHS

.

Procedure Copying Existing Workflows To change an existing workflow, copy it into the namespace Z. Choose Cho ose in the SAP menu

Tools To ols

ABAP Wo Workbench rkbench

Overvi ew

Ob ject Navigato Navigatorr

. The wo workflo rkflow w template templates s in the standar standard d sys tem of incident

management manageme nt are available in the package EHHSS_WF_INC .

Changing Workflow Templates 1. To change a wo workflo rkflow w template, choo choose se in the SAP menu Builde Bui lderr

Tools To ols

Business Wo Workflo rkflow w

Development

Definition To Tools ols

Workflo Wo rkflow w Builder

Workflo Wo rkflow w

.

2. Expand the workflow with new steps or change the process flow.

Note If changes to the workflow template also change the business logic, you must extend or change the existing process control object of the process. For more information, information, s ee Process Configuration. Configuration. 3. Save and activate the changed workflow workflow templ templ ate.

Registering Registeri ng Workflow Templates 1. To deactivate the wo workflo rkflow w template in the standar standard d sys tem, choo choose se in the SAP menu

Tools To ols

ABAP Wo Workbench rkbench

Overview

Obj ect Navigator

.

2. Op en the workflow template in the standard sys tem. 3. Go to the Triggering Events tab page that shows event links. To deactiv ate the the workflow workflow templ templ ate of of the the event CREATED, click the green symbol in the Event Creato Creatorr column. The The symb ol appears gray and the event is deactivated. 4. To register the new workflow workflow template, open it, go to to the the Triggering events tab page, and register the new workflow workflow template for for the event CREATED. Transfer Tra nsfer the the values from from the standard standard system workflo workflow w that you used as a template for for the the Ob ject Catego Category ry , Ob ject Type , and Event columns columns . To To activate the workflo workflow w template, click the gray symb ol in the Event creator creator column. The The symb ol appears green and the event is registere registered. d.

Result PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 82

The workflow template includes new steps or the process flow has changed.

Note If you create a new version of the template, any tasks already performed based on the previous version of the template can still be displayed during a search on the Tasks menu or in analytic al dashb oards. However, if you create a new template, any task s created with the prev ious template are no longer display ed in the system.

More Information For more information ab out workflows, see SAP Bus iness Workflow. For more information about configuring processes, see Process Configuration.

1.1.2.3 Task Management This function provides the pers on resp onsibl e for a bus iness p rocess , such as a manager or superv isor, an overv iew of the tasks for the processes of SAP EHS Management , and the abi lity to send notifications to the task p rocess or. You can use task management to monitor the progress of work on task s for the processes supp orted by SAP EHS Management , and to identify and respond quickly to delays in completing tasks.

Features Task management for SAP EHS Management provides the following features: Overvi ew of Tasks The tasks results list displays all relevant information for a task, such as processor or days overdue, and links take you directly to the data record for the referenced object or processor. You can also display the process details for a task to see the task in the business process context. Task O perations You can change task assignments, forward tasks, change the due date for tasks, and set the task status to complete. Queries and Export to Spreadsheet You can use your own queries to search tasks and display an exportable task hit list. If you are responsible for employees that use the system to process tasks, you can display tasks ass igned to your subordinates. Notifications You can notify a task processor directly from the task query hit list to provide a comment or reminder for the task. When you choose to send a notification, the system automatically displays the maintained language (or languages) of the processor, so you can comment in the appropriate language if necessary. The system sends the notification via an e-mail that contains the task details and your comments. You can also display the information for a person involved in a task or process, and send an e-mail directly from the information dialog for the person.

More Information If you have b een assigned tasks in SAP EHS Management , you receive the tasks in the Work O verview . For more information about the functionality available for this inbox (for example, entering substitutions for a planned absence), see SAP Library for SAP ERP on SAP Help Portal at ERP Enhancement Packages for Enterprise App lications

ERP Central Component Enhancement Package 5

Inbox (CA-EPT-IBO)

. Choose

SAP Library

http://help.sap.com/erp

SAP Business Suite

SAP

Processes and Tools

.

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

Changing the Task Processor in the Back-End System You can perform the following procedure to change the task processor in the back-end system. Ensure first that you are authorized to use the workflow tools of SAP EHS Management (authorization object EHFND_WFT ).

Procedure To change the current processor of a task, you can perform the following steps: 1. Disp lay the process details. You can do this in the data record by selecting the status link for a task on the Tasks tab, or in task management by choosing the Disp lay Process Details pushb utton for a task. 2. To disp lay technic al information about the process , navigate to the workflow sy stem by c hoosing the Dis play Workflow Log pus hbutton.


Page 12 of 82

3. Selec t the step for which you want to change the proces sor and choose in the menu 4. In the subs equent screen for the work item, choose in the menu 5. In the change mode (choose in the menu

Edit

Change

Goto

Goto

Work Item

Technical Work Item Disp lay

. .

) of the D ispl ay work item screen, choose the Execute pushb utton for the Forward

service. 6. Enter the user of the new process or. The system forwards the work item as a task to the new processor.

1.1.2.3.2 Continuing Execution of a Process with Errors To continue the execution of a process, you can navigate to the SAP Business Workflow system to continue processing after the erroneous step or to start processing of an erroneous step again. Errors can be caused by temporary problems in the workflow engine or by other exceptions during the execution of a proces s step . You can see the error state in task managem ent or on the Tasks tab of a data record.

Prerequisites You have been assigned the Process Adm inis trator role and the authorization objec t EHFND_WFT . You have configured the proces ses of S AP EHS Management properly in the Customizing activ ities under Management

Process Foundation

SAP EHS Management

Foundation for EHS

.

Procedure To continue the execution of a process, perform the following steps: 1. Dis play the process details . You can do this from the Tasks tab of a data record or from task management. 2. To disp lay technic al information about the process , navigate to the workflow sy stem by c hoosing the Dis play Workflow Log pus hbutton. 3. Select the erroneous step and choose in the menu

Goto

Work Item

4. Activate the administrative functions by choosing in the menu

Extras

. Activate Administration

.

5. You can start the execution of the proces s after the error. Or if you have c orrected the cause of the error, you can als o start execution of the erroneous step again.

More Information You can also continue a workflow that has an error with the standard functionality of SAP Business Workflow. You can display the erroneous workflows in Diagnosis of Work Items Containing Errors (transaction SWI2_DIAG ).

1.1.2.4 Process Tools Process tools enable a process adminis trator to monitor scheduled and recurring proces ses in the appli cation log of SAP EHS Management . You can keep track of the running processes and ac cess the messages logged, suc h as s uccess or failure messages. This helps y ou to pinpoint any p roblems that prevent a process from running properly.

Note This document describes the monitoring functions available for a process administrator in the delivered system. If you are not a process administrator and want basic capabilities to monitor processes and tasks, see Tracking Progress on Tasks and Processes. If you want to monitor and analyze processes using SAP BusinessO bjects Das hboards, see More Information below.

Usage of Processes in the Application The user schedules p rocesses and defines them as recurring in the applic ation on the Tasks tab. There, the user can add an action or notification and spec ify the start and end date/time, as well as when and how often the action or notification recurs. After the user has scheduled the action or notification in the application, the sys tem automatically s chedules the p rogram R_EHFND_SCHEDULER_JOB to start the process for the specified start date/time. The program logs the messages in the application log for you to monitor and analyze.

Prerequisites You have been assigned the Process Adm inis trator role. For more information, see Process Administrator (for Business Package) or Process Administrator (for SAP NetWeaver Business Client). You are authorized to call p rograms in transac tion SE36 .

Features SAP EHS Management is delivered with the following log objects and subobjects to monitor and analyze processes in the applic ation log (transaction SLG1 ): Log Object

Log Subobject

Description

EHFND_FW

WF_SCHEDULER

General Scheduler Log Displays i nformation about the activiti es of the process


Page 13 of 82

scheduler, the i nstances of a process setup, and any errors. EHFND_FW

WF_SCHEDULER_ITEM

Scheduler Item Log Displays detailed information about the execution of the instance of a process setup and about any errors.

You can use the following features of process monitoring and analysis: The system displays the instance of a process setup and its corresponding messages in the application log with green (information), yellow (warnings), and red (error) LED lights. You can use the instance ID of a process setup to disable the process setup in p rogram R_EHFND_PSE_DISABLE_ENTRY . You can set up the system to disable processes that have a given number of errors after a specified date in program

R_EHFND_PSE_DISABLE_ERRONEOUS . You can exclude sp ecific proces s definitions from monitoring and analys is. For more information, see Customizing under Foundation for EHS Management

Process Foundation

Processes

Specify Process Definitions

SAP EHS Management

.

You can exclude p rocess steps from monitoring and analysis by removing the property sap.eh.fw.wff.report_include in the workflow template for a process. By default, the process s teps with an agent assigned are relevant for monitoring and analysis as well as several b ackground steps.

More Information For more information about adding actions and notifications in incident management, see Adding Actions and Notifications. The data for scheduled and recurring processes is stored by the process setup business object. For more information, see Business Objects. For more information about monitoring and analyzing processes in dashboards, see EHS Management

SAP EHS Management – Process Foundation

http://help.sap.com

Xcelsius Dashboards

SAP NetWeaver

BI Content 7.05, SP02

SAP

.

1.1.3 Print Forms and Interactive Forms (EHS-MGM-FND-FRM) You use this component to generate print forms (such as a report) and interactive forms with data from the application. You can add, remove, and modify the standard reports and questionnaires that are delivered.

Implementation Considerations Adobe Document Services (AD S) are required and used to generate the forms and extract the data. They are located in the SAP EHS Management foundation layer.

Integration You can use the legal reports that are delivered with the standard system as they are, without making any changes. For more information, see Reporting to Legal Authorities. You should adapt the questionnaires and internal rep orts that are delivered to your company ’s internal lay out. SAP EHS Management uses the default technology for dev eloping the lay out of a form. Print forms and interactive forms can b e used by several components and processes within SAP EHS Management : Inquiries and questionnaires to gather additional information from another system user or an external person Report forms Control evaluations

Features Questionnaires, l egal reports, and summary reports SAP EHS Managem ent is del ivered with p rint forms and i nteractive forms to request information in a questionnaire, report to authorities, or produce a summary of collected data. You can generate forms directly from the data record and as part of a process. In some cases, the system suggests forms to support you in complying with legal reporting requirements. Send forms via e-mail, print forms, or store forms for offline use You can send forms from the data record via e-mail as part of a proces s. The recipient ca n send the form bac k us ing the Send pus hbutton at the end of the form. Since s ome recipi ents of a form do not have acc ess to the SAP EHS Management sy stem, s ome forms c an be stored on an Intranet to comple te offline, or printed out and filled out by hand. Review data before transferring into a data record You can configure forms to provide a review step. When the form is returned, the system generates a task for the sender to review the returned data. This enables you to preview the contents of the form and select which data you want to transfer into the data record.

Example You can send a PDF-based questionnaire to a witness, asking them to provide additional information about an incident.

More Information For more information about adding new forms, see Adding Print Forms and Interactive Forms and Mapping business objects nodes to Adobe Forms.


Page 14 of 82

1.1.3.1 Adding Print Forms and Interactive Forms You can add additional print forms and interactiv e forms to SAP EHS Management , for examp le, additional legal reports or questionnaires. The framework for form generation in SAP EHS Management consis ts of the following components: Form c ontroller An ABAP O bjects c lass that is the public i nterface to generate forms and extract the data (CL_EHFND_FW_ADS_CONTROLLER ) Form creation c ontroller An ABAP O bjects c lass that is called by the form controller and can be imp lemented for a spec ific form. A form creation controller must implement the interface IF_EHFND_FW_ADS_FORM_CR_CTRL . We recommend using the generic form creation controller of SAP EHS Management :

CL_EHFND_FW_ADS_FORM_CR_CTRL . Data p rovider An ABAP O bjects c lass that obtains the data from the application and fills the interface structure of a form. A data provider must implement the interface

IF_EHFND_FW_ADS_DATA_PROV . Inbound p ersister An ABAP O bjects c lass us ed to store the data of an interactive form automatically in the application. An inbound persister must implement the interface

IF_EHFND_FW_ADS_INBD_PER . Configuration You can configure forms in Customizing for usage in the application. These components are used in the Procedure.

Prerequisites You have exp erience developing in AB AP O bjects, using data definitions in the ABAP Dictionary, and developing interactive forms bas ed on the Adobe software in transaction SFP . To develop the form layout, you have the Adobe Document Services (ADS) installed locally. For more information about ADS, see SAP Service Marketplace at http://service.sap.com/ADOBE .

Procedure The following sections describ e the steps s pecific to SAP EHS Management for adding new forms in the Form Builder (transaction SFP ).

Creating ABAP Dictionary-Based Structures The framework for form proces sing in SAP EHS Management sup ports only one interface struc ture for each form interface. This means, for examp le, if you need to have the data of a person and the data of a release in the form, you must do the following: 1. Create an ABAP Di ctionary-bas ed structure for both types of data (for example, the p erson data and the release data). 2. Create an ABAP D ictionary-b ased struc ture for the interface that contains b oth the pers on and release struc tures.

Note If you create an interactive form, include the structure EHFNDS_FW_ADS_META in the interface structure to provide metadata for the form during inbound processing.

Creating Form Interfaces The form interface defines the data that is available in the form layout, and which data the system must retrieve in the data provider implementation. To create a new form interface, perform the following steps: 1. Create the form interface in transaction SFP . 2. Under Form Interface , double-click the Import node and enter the Parameter Name .

Rec ommendation To use the generic form generation controller, enter INTERFACE_STRUCTURE as the parameter name. If you want to use a customer-specific form generation controller, you must implement the interface IF_EHFND_FW_ADS_FORM_CR_CTRL . 3. Enter the ABAP Dictionary-based structure as the Type Name . If you created an interface structure as described in Creating ABAP Dictionary-Based Structures, you enter the interface structure here.

Creating Forms 1. Create the form name in transaction SFP . 2. Sp ecify the following values for the properties of the form: Description: (form description) (Layout) transl ation: Standard (Layout) technology: XFA (Layout) type: Standard Layout Interface: (enter the form interface from Creating Form Interfaces) Inbound Handler: (optional) To create an interactive form, enter the default inbound handler for SAP EHS Management . Based on this setting, the sys tem generates coding for the extraction of the form data. 3. In the Context tab, enter the form context by dragging and dropp ing the structures from the left side of the screen to the right side. In doing this, y ou make


Page 15 of 82

the data available in the form layout.

Laying Out Forms When you insert new data fields from the Data View in a form, you bind the data to a field in the form layout by performing the following step s: 1. Copy a field into the form using drag and d rop for the data field, for examp le, a text field. 2. Choose the tab

Ob ject

Binding

.

3. Enter the data field value for the default bindi ng.

Data Provider The following methods of the data provider are delivered. They store the data within the form and the form itself. Method

Description

GET_DATA

Extracts the data from the application and returns the filled interface structure This method contains the following: Form information that is configured in Customizing as the importing parameter The process component-specific form context The corresponding rel ation to the process control object if the form is used in a process For more in formation about processes, see Process Foundation.

VALIDATE_DATA

Validates the data that is in the form

GET_FILENAME_SUFFIX

If the form belongs to a specific object (such as the person), the corresponding suffix of the file name can be set. This method is called after generation of a form when the file name i s created.

For more information, see the test data provider CL_EHFND_FW_ADS_TEST_DPROV in the sy stem, or the data providers configured in Customizing under EHS Management


Print Forms and Interactive Forms

Specify Forms

SAP

.

Inbound Persister Implementation (Optional)

Note The inbound persister is needed for SAP Interactive Forms by Adobe only.

The inbound persister must implement the interface IF_EHFND_FW_ADS_INBD_PER that contains the following methods: Method

Description

STORE_DATA

Stores the data of a form

VALIDATE_DATA

Validates the data that is in the form

GET_FILENAME_SUFFIX

If the form belongs to a specific object (such as the person), the corresponding suffix of the file name can be set. This method is called after generation of a form when the file name i s created.

STORE_FORM

Stores the form

GET_COMMENT_OF_FORM

Returns the comments that have been entered in the form

For more information, see the inbound pers isters configured in Customizing under and Interactive Forms

Specify Forms

SAP EHS Management


Print Forms



Specify

.

Form Configuration You can spec ify forms in Customizing under Forms

SAP EHS Management

.

You can sp ecify the groups for forms in Customizing to control the app earance and usage of the forms in the applic ation under Foundation for EHS Management


Specify Forms

SAP EHS Management

.

1.1.3.2 Mapping Business Objects Nodes to Adobe Forms If you want to build your own reports based on Adobe Document Services (ADS), you have to perform the steps described in Adding Print Forms and Interactive Forms. The step Data Provider requires a high lev el of knowledge about how to read data from the bus iness object. This function supp orts y ou in implementing a the data provider class. The Mapping Workbench enables y ou to map busi ness object nodes to nodes that are used in SAP Interactive Forms by Adobe by dragging node elements from the business object tree and dropping them to the form context tree. After mapping the nodes you need, you can generate the corresponding data provider class that reads the data from the business object and provides the data for the interactive form generation.

Prerequisites You have sp ecified forms in Customizing for SAP EHS Management un der Forms



Spec ify

.

You have defined the form interface in transaction SFP .


Page 16 of 82

You are using the business objects delivered in the standard system. You are using a business object node to obtain the data. This node contains all fields that have to be extracted.

Features The M app ing Workbenc h provides the following features: Define field mapping You can create mappings between the business object nodes and the form context nodes by using the drag and drop functionality. The system visualizes the created mapp ings in a separate table and with an icon at the mapped elements.

Note You can map a node from the form context only once. Generate data provider After you have finished the mapping, the system generates all needed code lines for creating or changing the data provider.

Activities While building up the mapping and creating a data provider, the system performs the following activities: The system performs the following compatibility checks, and forbids the mapping in case of errors. Possible errors include the following: The data type of the business object elements it not convertible into the data type of the form context element. The data type of the form context element is not convertible into the data type of the business object element. After you have saved your work, the sys tem saves the created mappings and checks whether existing mappings are consistent. In case of an error, the sys tem generates mapp ing proposals that you can execute by choosing the Propose Mappi ng pushbutton. After you have finished the mapping, you can choose the Generate Data Provider pushb utton, and the system generates the data provider. When you choose the Edit pus hbutton, the sy stem opens a source code editor with which y ou can modify the generated class . When you regenerate a manually modified class, the system can handle the following situations: If you modified or added code line, the system adds the coding to the regenerated code. If you deleted a generated code line, the system adds the coding again if the node is still mapped. If a specific code line is obsolete after regeneration, the system comments it out.

More Information For more information, see Customizing for S AP EHS Management under Forms



Spec ify

.

1.1.4 Integration (EHS-MGM-FND-INT) You can use this c omponent to integrate SAP EHS Management (EHS-MGM) with other components. This enab les y ou to access data in other components from within the EHS-MGM app lic ations and transfer data from EHS-MGM to other components. In addition to sim pli fying work with the app lica tions, integration also ensures c onsistency b y reusing exi sting data in different components. If you use integrated data in EHS-MGM , changes to this data are automaticall y reflected in all applications. You can also use integration to start EHS-MGM proces ses inv olving actions in different components.

Implementation Considerations The integration of other components is only possible if the relevant components are fully installed and configured. Depending on which component you integrate, you can access data that is stored locally or in a remote system, or you can transfer data to a remote system. You specify the destinations for remote systems in Customizing for SAP EHS Management under


Integration

Sp ecify Des tinations for Integration

.

Note It is not possible to access MM and PA-OS data that is managed in a remote system. This data must always be stored locally.

Authorizations If you are responsible for setting up integration, be aware that the following authorization objects are required for the corresponding activities:

S_USER_RFC – Editing RFC connections – Entering RFC connections for PFCG roles in SM59

Features The following table lis ts the integrated components and spec ifies how these components can su pp ort your busines s sc enarios in the SAP EHS Management applications: Component

Function

Usage in SAP EHS Management Incident Management


Risk Assessment

Product Compliance

Page 17 of 82

Personnel Admini stration (PA)

Read person-related data for

X

X



X





Read data for busin ess partners

X

X

X

Change and create data for

X



X

X

X



X

X



X

X



X







X



X

X



Read and create service orders for X





X

X



Read and create internal orders for X





employees and applicants Personnel Time Management (PT)

Read and create absences for employees

(not activated by default) SAP Business Partner (SAP BP)

business partners Organizational Management (PA- Determine relations between OS)

individual persons, positions, and organizations

Plant Maintenance (PM)

Import and read data for PM technical objects Read and create maintenance notifications Read and create maintenance orders for financial tracking Flag PM technical objects for which risk assessment inform ation can be retrieved and communicate risk information

C ustom er Ser vi ce (C S)

R ead an d cr eate serv ice notifications

financial tracking Quality Management (QM)

Read and create quality notifications

Accounting (AC)

financial tracking Materials Management (MM)

Read material data

X

X

X

SAP BusinessObjects

Transfer data to the SAP

X







X



Create a change request and send X

X



governance, risk, and compliance BusinessObjects Risk solutions (GRC solutions)

Management component

(not activated by default) SAP Management of Change

Transfer results of simulated risk assessments to SAP Management of Change

it to SAP Management of Change

Constraints The following data must always be available in the local system: Plants and p lant descriptions Material and material descriptions Currencies and exchange rates Notification types for PM, QS, and CS Business partner roles Marital status texts for HR persons Marital status texts for b usiness partners Attendance and absence types Shift group and shift planning of the organizational unit Organi zational data, including organizational units and persons in PA-O S

Note To make organizational data from PA-OS available in the local sy stem, you can distribute the relevant HR master data between the PA-OS sys tem and the EHS-MGM sys tem. However, since the EHS-MGM applic ations only require specific PA-OS data, distribution limited to the basic infotypes is sufficient. The distributed organizational data cannot be changed from the EHS-MGM applic ations as the system settings only allow read access . For more information about distrib uting HR master data, see the app lication help documentation for SAP ERP at ERP Cross-Ap plication Functions Resources

Scenarios in App lications

Master Data Distribution (Human Resources)

ALE/EDI Business Process es

SAP

Human

.

For more information, see the documentation in Customizing for S AP EHS Management under Des tinations for Integration

http://help.sap.com/erp605/

Library of ALE Business Process es


Integration

Sp ecify

.

More Information For more information about integration in each SAP EHS Management component, see the following documentation:


Page 18 of 82

Incident Management: Integration with Other Components Risk Assessment: Integration with Other Components Product Compliance: Integration

1.1.4.1 Integration for Person Information You can use this function to integrate person-related data from other components with SAP EHS Management (EHS-MGM) . This data can either be s tored locally or in remote systems. The function allows you to access data for HR persons and business partners, organizational information, and time data. You can access pers on information through integration to the corresp onding components: Personnel Administration (PA) SAP Business Partner (SAP BP) Organizational Management (PA-OS) Personnel Time Management (PT)

Note PT integration is only av ailable for the incident management app lication and must b e activated separately.

Prerequisites You have chec ked the settings for the relevant authorization objects as desc ribed in Customizing for SAP EHS Management under Management

Integration

Human Resources Integration

Check Authorizations for Person Information

You have defined the relevant subtyp es for party infotyp es in Customizing for S AP EHS Management under Integration


Specify Relevant Subtypes for a Party Infotype.

Foundation for EHS

. Foundation for EHS Management

.

You have defined the contractual relationships to employee groups and employee subgroups or business partner roles that are relevant for legal reporting. You can make these settings in Customizing for S AP EHS Management under Integration

Specify Person Groups and Contractual Relationships


Integration

Human Resources

.

If you want to integrate data that is s tored in remote sys tems, y ou have set up the integration of the required sys tems in Cus tomizing for SAP EHS Management under


Integration


.

If you want to integrate personnel time data, you have made the application-specific integration settings as described in HR Integration for Absence Assignment.

Features You can use this function to read person information from the components listed above. For the incident management app lication, PT integration and SAP BP integration also allow you to change pers on-related data: You can create new business partners and change the data of existing business partners. If PT integration is ac tivated, you can create HR absences for injured persons.

1.1.4.2 Integration for Notifications You can use this function to integrate notification process es b etween SAP EHS Management (EHS-MGM ) and other components that are either managed locally or in remote sy stems. It allows you to start process es for notifications that must be implem ented in other components directly from the EHS-MGM app lic ations. The EHS-MGM sy stem monitors the status of each notification proces s until it is compl eted. Integration is possible for the following notification categories: Maintenance notifications (PM) Qual ity notifications (QS) Servi ce notifications (CS)

Prerequisites You have speci fied the required notification types in Customizing for SAP EHS Management under Specify Notification Types


Integration

.

If you want to integrate data that is s tored in remote sys tems, y ou have set up the integration of the required sys tems in Cus tomizing for SAP EHS Management under


Integration


.

Features If the circumstances of an event or situation require actions to be taken in other components, you can start processes to communicate and initiate related tasks. For each notification, you can disp lay details including its status directly from the EHS-MGM appli cations. You can use the report Check for Completed Notifications (R_EHHSS_ACT_CHECK_COMPL_EXT_NO ) to check regularly for notifications that have been completed in other components. For all notifications in status Completed , the report triggers the next proces s step . For more information, see the sy stem report documentation.

Note If you schedule notifications as recurring actions, the system starts a notification process for each recurrence.


Page 19 of 82

The notifications sent to integrated systems are logged in the app lic ation log. You can displ ay the log in transaction SLG1 (object EHFND_INTEGRATION , subobject EHFND_EXT_NOTIF ).

1.1.4.3 Check for Completed Notifications You use the report Check for Completed Notifications (R_EHFND_CHECK_COMPL_EXT_NOTIF ) in SAP EHS Management to check if notifications have been completed in the following components: Plant Maintenance (PM) Customer Service (CS) Quality Management (QM)

Integration You use this report when your system is integrated with one or more than one of the components specified under Use.

Prerequisites You have spec ified the destinations of the PM, CS, and QM sy stems in Customizing for SAP EHS Management under Integration

Specify Destinations for Integration


.

You have spec ified the notification types that you use in the appli cation in Customizing for SAP EHS Management under Integration

Specify Notification Types


.

Features The report determines all notifications that are in status In Proces s and check s whether these notifications have been set to Completed in the relevant component. For all notifications that have been completed, the report triggers the next process step to create a task for the approver to complete the notification in the app lication. The system document report actions in the application log (object EHFND_INTEGRATION , subobject EHFND_EXT_NOTIF ).

Activities Dep ending on the busines s proces ses of your company, y ou can sc hedule the report to occur periodical ly, for examp le, once a day, in Customizing for SAP EHS Management under


Integration

Schedul e Job for Notification Status Check

.

1.1.8.1.3.1.1.1.4 Locations You use this component to represent an identified real place, virtual space, or object in the system. The location is a central master data object that can be organized in a structure to represent where a location exists spatially or functionally in a company. Examples of a location are a plant, a piece of equipment, or a work area. The location makes it poss ibl e to utilize exis ting technical objec ts and functional locations from the Plant Maintenance (PM) component, and work areas from exis ting EHS solution in SAP EHS Management . For more information, see Integration. In incident management, locations sp ecify precis ely where an incident took place and, in risk as sessment, locations sp ecify precis ely where hazards exis t. A location could be a hallway, a fire hydrant, or a boiler that produces emissions, for example. When you open a location, the system displays an overview of all location-relevant incidents according to the selected filter criteria. You can access the corresponding incident records directly from this incident overview.

Note The incident overview does not include archived incidents and incidents with the status Void .

For more information about incident management, see Incident Recording

Integration You can create your own locations, or you can import technical objec ts that already ex ist in the Plant Maintenance (PM) component as locations into S AP EHS Management to sav e you the time and effort of entering duplic ate information. You can also integrate existing locations that you have already created in your SAP EHS Management sys tem with technical objects from PM . You can use report R_EHFND_ LOC_ MIGRATE_WA to migrate work areas from the existing SA P solution for managing environment, health, and safety into locations in SAP EHS Management . For more information, see the report documentation.

Features Location details Disp lays detailed information about a location, suc h as the plant, company c ode, and b usiness area to which it is assigned. You can also display the location’s address and geographic coordinates to identify its precise position. This way, you can visualize it on a map that can be integrated into the system


Page 20 of 82

in Customizing. Revisions You can create revisions for recording time-specific versions of a location. For example, if a location is currently assigned to plant 0001 but will be reassigned to plant 0002 tomorrow, then you create a revision with tomorrow’s date and define the new plant there. Revisions ensure that a location’s historic data is retained and not simply overwritten. Status You can sp ecify whether a location is active or inactiv e. You can als o use the Historic status if a location is no longer used, but you need to keep a record of it in the system to document historical in formation. You can use the Historic status, for exampl e, if a location is out of servic e, or has been sold. Location structures You can organize your locations in structures and expand the structure to show any subordinate nodes. Mass changes You can make changes to several locations at once to save time and administrative effort.

More Information Maintaining Locations and the Structure Importing Locations from PM

1.1.5.1 Location An identified real place, virtual spac e, or object. The location is a central master data object that can be organized in a structure to represent where a location exists spatially or functionally in an organization. Examples of a location are a plant, a piece of equipment, or a work area.

You use this business object to recreate the real places, virtual spaces, and objects at your organization in the system. You can organize locations in a structure to show the hierarchical relationships between locations and allow navigation. Once a location exists in the system, you can reference it in data records to describe, for example, where an incident occurred or where a risk assessment will take place.

Structure The location is comprised of the following data: Data

Notes

Identifying information, such as name and ID Integrated techni cal object or functional location via a li nk to the Plant Maintenance

Establishing a link fills the attributes data with data from PM. Data changes in PM appear

(PM) component

automatically in the location. Removing a link allows you to edit the attributes for the location and disables automatic transfer of changes from PM.

Attributes, such as a plant ID and cost center Address information Partner information

If an integrated object has business partner data assigned, the system displays this information in the Partners tab. Otherwise, the tab is not visible.

Positions

If people work at a location, you can assign the positions from HR to the location. The system displays the objects, such as employees or business partners, assigned to the position when you display the details for the position.

Status Values When you create a location, the sys tem assigns the New status. You can edit the location and keep the location in the New status if you have not finished editing. Once you have finished editing, you can set the following status values in the location master data: New -> Active The location data is complete and up-to-date. Active <-> Inactive The location or its data are no longer relevant. You can mak e changes to the location and set the status b ack to Activ e . Inactive -> Historic The location no longer exists. However, the location must remain in the system, because it is assigned to older data records. You cannot edit the master data of historic locations. Regardless of the status, you can ass ign locations (even new, inactive, and his toric locations) to your data records in SAP EHS Management .

Integration You can use locations without integration to other components. However, if you want to link to technical objects and functional locations, you require integration with PM. If you want to assign p ositions to a location, you require integration with the Organizational Management (PA-O S) component.

1.1.5.2 Maintaining Locations and the Structure


Page 21 of 82

You can create and maintain locations in two ways . You can create them manually , or you can imp ort technic al objects from the Plant Maintenance (PM) component as locations. The following information describes how you create a location manually and maintain the location structure. When you create a location, you can define master data such as the plant or company code to which that location belongs. You can also specify the location’s address and geographic coordinates to identify its precise position. You can use the precise position to visualize a location on a map that can be integrated into the sy stem in Customizing for SA P EHS Management under


Locations

Configure Integration of Map

.

You use location structures to organize your locations. You can create locations at different positions within the structure, or change the position of existing locations within the structure using the Insert and Remove , and Cut and Paste functions. You can make mass changes to the attributes of multiple locations in one go. This saves you the time and effort of having to maintain each location individually.

Prerequisites You have enabled PM integration in Customizing for SAP EHS Management under


Locations

Enable/Disable

Locations

Sp ecify Location

PM Integration You have sp ecified location typ es in Customizing for SA P EHS Management under


Types

Procedure You can maintain the locations and structure using the following three procedures:

Creating a Location Manually 1. Choose Locations and in the Servi ces area, choose Manage Structure . If you are creating a new structure, selec t the first node in the table, Location Structure . If you want to add a location to exis ting structure, s elect the position in the structure where you want to add it. Then choose Create Location . 2. Enter the Location Descrip tion and Type for your new location and choose OK . 3. You now see your location in the location structure. Choose Save and then Op en . 4. Enter master data to identify your location and to sp ecify it further. Set the Status and define a Revis ion if you require. 5. When you have finished, choose Save .

Maintaining the Location Structure 1. Choose Locations and in the Servi ces area, choose Manage Structure . To change the position of an existing location in the location structure, selec t the relevant location and then c hoose one of the following functions: Function

Explanation

Insert

Adds a location below the selected position in the structure

Remove

Removes the location from the location structure

Caution Removin g locations from the structure does not delete them. If you remove a location, you can still reference the location and use its data. However, it i s not possible on some screens in the application to select a location that is not in the structure. Cut

Temporarily saves the location so you can insert it using the Paste function

Paste

Pastes the cut location as a subordinate node of the selected location and removes it from its previous place in the hierarchy

Changing Location Attributes 1. Choose Locations and then choose

Services

Change Attributes

.

2. Select the Key Date from which you want the changes to apply . 3. Change the location attributes that you want to change and choose Next . 4. Now select the locations y ou want to change, either b y s earching for them or by adding them from the location structure. To do the latter, s elect one or more locations by holding down the CTRL button and cli ck ing with the primary mouse b utton on the relevant location. To exp and sub ordinate locations, y ou can click the arrows and display the subordinate locations. You can automatically add all subordinate locations by selecting the relevant checkbox. Choose Next . 5. Review the changes that you want to app ly to the location or locations before choosing Change . 6. The sy stem confirms that your changes were made.

Result The locations and their structure are display ed on the Recent Locations and Structure View tabs in the Locations area. The locations can b e used when you report an incident or assess risk.

1.1.5.3 Importing Locations from PM You can search for technical objects from the Plant Maintenance (PM) component and imp ort them as locations into the SAP EHS Management component. The advantage of this is that you do not have to enter duplic ate data; the bas ic data for these locations originates from PM . You can import up to 50 locations into


Page 22 of 82

SAP EHS Management at any one time. Alternatively, you can link locations that already exist in SAP EHS Management with technical objects from PM . In either case, y ou always have the option of removing the PM link at any time. This removes the ass ociation between the technical obj ect and the location. You can then import a completely different location, or import the same location at a different position in the location structure, for example.

Prerequisites You have enabled PM integration in Customizing for SAP EHS Management under


Locations

Enable/Disable

Locations

Sp ecify Location

PM Integration You have sp ecified location typ es in Customizing for SA P EHS Management under


Types

Procedure Importing New Locations from PM 1. Click Locations and then in the Services area, choose Import Locations from PM . 2. Sp ecify your search cri teria for finding the technical objec t you require (detailed search criteria shortens the searc h time) and choose Search . Select the technical object you require and then choose Next .

Note You cannot import a location that is already linked to another location. 3. Dec ide which l ocations you want to import. If a location contains sub ordinate objec ts, c hoose whether you want to imp ort these as well. You can only imp ort subordinate objects together with their parent node. Use the Import As (Location Type) options to define the location type that a location has when it is imp orted. To sp ecify a location type for one or more than one location, choose Import As above the table and selec t the relevant location type. The system applies the selected location type to all of the locations in the table. To sp ecify the location type for only one location in the table, c hoose the relev ant location typ e for the location directly in the table us ing the Import As (Location Type) option. The system app lies the selec ted location type to just this location. Choose Next . 4. Selec t the position in the exis ting location structure below which you want to insert the location (and any subordinate objects). Choose Next . 5. Review the technic al object that you are about to imp ort and its location parent node. Choose Import . The system imports the locations.

Linking Existing Locations to PM 1. Disp lay the location in the location structure by c hoosing Locations and in the Services area, choose Manage Location Structure . 2. Op en the location you want to link to a technical object from PM and choose Establish PM Link .

Note This overwrites the location’s existing master data. 3. Follow steps 2 to 5 above.

Result The system inserts the location into the location structure and you can use it in the application, for example, for reporting incidents.

1.1.6 Chemicals When you work with chemic als, y our organization is sub ject to regulatory requirements that govern the use of chemicals and the exposure to your workers. SAP EHS Management enables you to manage chemi cal data and protect the health and safety of workers that use chemic als, and ensure product and regulatory compliance. The following busines s objects are common to the processes of SAP EHS Management : Chemical Listed substance Regulatory list

Health and Safety You can analyze exposure to chemical agents in risk assess ments, group workers together by their exp osure to chemical agents into similar exposure groups, and monitor exposure to chemical agents with personal exposure profiles. To supp ort these business processes, the common bus iness objects listed above are used in the following ways: Chemical When you create a chemical agent, the chemical b usiness object stores the phy sical and chemical p roperties data for the chemical agent. While the chemical agent references the chemic al data, you work p rimarily with the chemical agent in the health and safety processes . Listed substance You enter listed substances as hazardous ingredients in the chemical agent. You can also create listed substances from within the chemical agent data record. The listed subs tance stores the CAS number and the lis ted subs tance name.


Page 23 of 82

Regulatory list You define occupational exposure limits (OELs) for listed substances in regulatory lists. Each instance of the regulatory list is called a revision and you can enter the current OELs for a listed substance. When regulations change, you can create a new revision of the regulatory list and update the OELs. Since the chemical agent consists of listed substances, the OEL data for the listed substance is available for the chemical agent and for use in health and safety processes.

Product Compliance In handling articles, you use the chemical substances that they contain. For more information, see Regulatory Lists.

More Information For more information about chemical agents, see the business object documentation for Agents.

1.1.6.1 Creating and Revising Regulatory Lists You can use regulatory lists in the application to store a list of substances that are subject to legal or industry-specific regulations, for example, declarable substances or substances for which all uses are prohibited or there are possible exemptions. Regulatory lists also can also provide information about thresholds (such as occupational exposure limits) for listed subs tances. As legal or industry-spec ific regulations c hange, you can create new revisions of regulatory lists. Each instance of a regulatory lis t (even the first instance) is called a revision. The system stores all revisions of a regulatory list and keeps existing references to historical data. This enables you to keep accurate records and helps y ou ensure compliance.

Process In Customizing for SAP EHS Management , you must first make the following settings before creating regulatory lis t revisions in the appl ication: 1. In Customizing under


General Configuration

Create Regulatory Lists and Customer Lists

, configure the

regulatory lists that you want to use in the app lic ation, for examp le, China RoHS . 2. Make further settings for regulatory lis ts in the following Customizing activities as required: Risk Asses sment Product Compliance

Master Data Configuration Regulations

Agents

Specify Regulatory Lists for OELs

Specify Regulatory Lists and Customer Lists

.

.

Regulatory Lists in Health and Safety In the application, perform the following steps to create and revise regulatory lists: 1. In

Health and Safety

Overview

Agents and OELs

, choose the service Create Regulatory List Revisions .

2. Selec t a regulatory lis t and enter data about the new revision. 3. The system copies any existing data in the regulatory list, s uch as listed substances and occupational exposure limits, to the new regulatory lis t revision. You can add new data and update existing data. 4. To use the data from the regulatory list in analyzi ng exp osure to chemi cal agents, release the revis ion.

Note You can only have one inactive revision open at a time. You must first release or delete the currently inactive revision before creating a new revision.

Regulatory Lists in Product and Safety Stewardship For more information about using and managing regulatory lists, see the following topics: Regulatory Lists and their Revisions Regulatory List Management

More Information For more information about using regulatory lists in health and safety, see Defining Occ upational Exposure Limits (OELs).

1.1.6.2 Transferring Data from the Specification Database The component extensi on for SAP EHS Management (the add-on) provides two reports to transfer chemic al data from the spec ification database of SAP EHS Management as part of SAP ERP to the add-on system for use in the risk assessment bus iness p rocess . If you use the s pecification database for managing hazardous substances, you can leverage your existing investment and transfer the chemical data via RFC from a remote EHS system to the add-on system. You can use the reports to replicate data from the following substances for use in the add-on system: Real substance or agent (as a source for the chemical agent) – Report R_EHFND_FILL_CHM_BY_EHS_SUBST Listed substance (as a source for the listed substance and its OEL in the regulatory list) – Report R_EHFND_FILL_REGL_BY_EHS_SUBST You configure the reports in Customizing to specify and map the data sources from the specification database to their corresponding destinations in the add-on system. You save a set of hits in the specification database to provide a preselection of the substances to transfer. The reports then use the Customizing settings to determine the value assignment types and characteristics of the substance in the specification database that contain the data to replicate. Finally, the reports replicate the data as required and create new chemical agents and listed substances (and OELs) in the add-on system. You can run the reports again or regularly as b ackground jobs to update this data, especially if you continue to maintain substances in the sp ecification database.


Page 24 of 82

Prerequisites You have configured the connection from the add-on system to the remote system where the specification data is stored. Enter an RFC destination for the EHS sy stem in Customizing for SAP EHS Management under


Integration

Spec ify Des tinations for Integration

.

You have fulfilled the prerequisites as described in the report documentation to ensure that phrases and Customizing values from the specification database sy stem exi st as required in the add-on system. For more information, see the following reports in the back -end sys tem Creation and Update of Chemical s from EHS Substances (R_EHFND_FILL_CHM_BY_EHS_SUBST ) and Creation and Update of Listed Subs tances from EHS Subs tances (R_EHFND_FILL_REGL_BY_EHS_SUBST ).

Procedure 1. Select subs tances in the speci fication database (in the remote system). Select subs tances by searching and using a set of hits in the spec ification workbench, and then save the results (via

Utilities

Set of Hits

Save

.

You can also modify the set of hits regardless of the search criteria, for example, to reduce the results. Save one set of hits for the data transfer to chemical agents and one set of hits for the data transfer to listed substances. If you plan to regularly transfer data, you can create queries. Otherwise, search and save sets of hits to refresh the results before every transfer to the addon system. 2. Configure the report to transfer chemic als in Customizing for S AP EHS Management under Report to Transfer Chemicals


Chemical s

Configure

. In this activity , you spec ify the data sources that determine the sub stances to transfer as well as the data sources of the

actual values, such as physical-chemical properties The following table provides example settings for the report and does not contain all possible data sources (see the Customizing activity). It lists the data sources in the specification database and how the report uses their data. P ur pose of D ata S ou rce

D ata S ou rce i n S peci fi cati on

Technical Key of Data Source

Characteristic of Value Assignment

Database

D eter mi nes th e su bstan ces to tr an sfer

Type of Data Source

Set of H its – G rou p En try

U ser -defi ned k ey

Not applicable

When you save a set of hits in the specification workbench, you enter a group entry as a unique identifier. Provides Name of chemical business

Identification Listing (for chemical agent) D_IHEXPOS ( Agents in Industrial

object

Not applicable

Hygiene and Safety ) You can display the identification listings and their corresponding ID categories and ID types in Customizin g activity Check Identification Listing in the system for the specification workbench.

Provides Name and CAS Number of Identification Listing for Listed Substance D_DEFAULT ( Standard listing for listed substance busin ess object

Not applicable

identifiers ) The identification listings and their corresponding identification categories and identification types are defined in Customi zing activity Check Identification Listing in the system for the specification workbench. The report uses the identification types within an identification listi ng type that are customized for position 1 and 2.

Provides Color data for the chemi cal

Color

SAP_EHS_1013_008

business object

SAP_EHS_1013_008_VALUE

You can display the technical key of valu e You can display the characteristic nam e assignm ent types in the specification

by selecting the characteristic field that

workbench for a substance by selecting

contains, for example, the color red and

the value assignment type in the property choosing F1 in the specification

Provides Hazard Classification data for

Hazardclassification

the chemical busin ess object

tree and choosing F1.

workbench.

SAP_EHS_1023_043 ( G HS

SAP_EHS_1023_043_CLASS

Classification ) You can display the technical key of valu e assignm ent types in the specification workbench for a substance by selecting the value assignment type in the property tree and choosing F1.

The corresponding data source

Value Assignment Rating

PUBLIC (Released without restrictions)

determines (together with the validity

When you enter value assignment

area) the characteristic to transfer.

inform ation for a property (such as color),

Not applicable

you enter on the Usage tab a [value assignment] rating. The rating specifies the users that can view an identifier or a value assignment. The corresponding data source

Validity Area

REG_WORLD ( World )

Not applicable

determines (together with the value

When you enter value assignment

assignm ent rating) the characteristic to

inform ation for a property (such as color),

transfer.

you enter on the Usage tab a validity area for the corresponding rating.

3. Configure the report to transfer listed subs tances and OELs in Customizing for SAP EHS Management under


Risk Assess ment

Master Data

Page 25 of 82

Configuration

Agents

. In this activity , you sp ecify the data sources that determine the substanc es to transfer as well as the data sources of the actual

values, such as physical-chemical properties. The following table provides example settings for the report. It lists the data sources in the specification database and how the report uses their data. Purpose of Data Source

Determines the

Data Source in

Techn ical K ey of Data

Characteristic

Characteristic ( Value

Characteristic (OEL

Specification Database

Source

(Regulatory List)

Type for OEL)

Value)

Set of Hits – Group Entry

User-defined key

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

Not applicable

substances to transfer

When you save a set of hits in the specification workbench, you enter a group entry as a unique identifier.

Provides Name and CAS Number of listed

Identification Listing (for

D_DEFAULT (Standard

Listed Su bstance)

listing for identifiers)

substance business object

The identification listings and their corresponding identification categories and identification types are defined in Customizing activity Check Identification Listing in the system for the specification workbench.

Provides the occupational

Occupational Ex posure

exposure limit for the

Limit

SAP_EHS_1023_006

SAP_EHS_1023_006_BAS SAP_EHS_1023_006_VAL SAP_EHS_1023_006_VAL E

UE_TYPE

UE_PPM

corresponding li sted substance in the regulatory list.

4. Ensure that you have fulfille d all p rerequisites before executing the following reports. For more information, see the documentation of the following reports in the add–on system: Creation and Update of Chemicals from EHS Sub stances (R_EHFND_FILL_CHM_BY_EHS_SUBST ) Creation and Update of Listed Substances from EHS Subs tances (R_EHFND_FILL_REGL_BY_EHS_SUBST ) 5. Execute the reports as required.

Result You have replicated the data from the specification database to the add-on system. You have created chemical agents (based on real substances or real subs tance groups) and listed subs tances. The listed sub stances app ear in your regulatory lists with their corresponding OELs and the listed sub stances ap pear as hazardous ingredients in the chemical agent. To enable subsequent data transfers, the root node of the chemical business object and listed substance business object contain an attribute to remember the source substance in the specification database from which data was transferred.

Example The following list contains example errors that can occur, their potential causes, and possible solutions: No value for key spec ified Cause: The phrases or Customizing entries used in the specification database do not exist as Customizing entries in the add-on system. To transfer data from the specification database, the system requires that the technical keys of Customizing entries in the add-on system (for example, for color, form, and so on) are identical to the phrase k eys and Customizing entry k eys used in the sp ecification database. Solution: The reports for replicating the data contain instructions for transferring phrases and Customizing entries to the add-on system. Real subs tance was transferred, but a c haracteristic (suc h as color or odor) is missing Cause: The value assignment rating and validity area of the characteristic do not match the value assignment rating and validity area you specified in Customizing activity Configure Report to Transfer Chemical s . Solution: Check the sp ecified v alues in the add-on Customizing (see s tep 2 of the Procedure ) or enter the relevant value for the characteristic in the spec ification database. Note that if you have s pecified a v alidity area, such as REG_WORLD , the sy stem transfers the characteristics with this v alidity area. If no validity area or a different validity area is assigned, the report replicates the real substance without this characteristic.

More Information For more information about hit lists (saving sets of hits) and queries in the specification workbench, see http://help.sap.com/ehs under SAP EHS Management as Part of SAP ERP and your relevant release, then choose Specification Management (EHS-BD-SPE)

SAP Library

Specification Editing

Environment, Health and Safety (EHS)

Basic Data and Tools (EHS-BD)

then Hit List or Query Management .

See also chemical agents.

1.1.7 Analytical Reporting You can use the data that you record in SAP EHS Management in analytic al reports. The foundation for SAP EHS Management provides functionality to extract data, so you can generate analytical reports in the following forms: File-based Spreadsheet SAP BusinessObjects Dashboard


Page 26 of 82

SAP Busi ness Exp lorer (BEx) report

Note You can find spec ific information about analytic al reporting for each proces s component under the corresponding Analy tical Reporting node in the app lication help of the process component (for example, see

Incident Management

Analytical Reporting

).

Implementation Considerations If you want to use SAP BusinessObjects Dashboards with queries, note the following information: To display the dashboards p rovided, you require Adobe Flash Player version 9. Note also the license terms for SAP Bus inessOb jects. To create your own dashboards, you require SAP BusinessObjects Dashboards. For more information, see SAP Note 1486885. Take note of the corresponding license terms. The dashboards and BEx reports use BI content. BI content contains BW modeling/objects, BEx queries (multidimensional reports), and SAP BusinessObjects Dashboards. You can access the BI content documentation on SAP Help Portal at

http://help.sap.com

SAP NetWeaver

BI Content

and then select the

corresponding release (see the release listed in Component Extension for SAP EHS Management).

Features This component offers the following functions to enable analytical reporting: File-Based Reporting Allows you to export data in various file formats and generate analytical reports in your standard office environment. Data extraction to BW Provides a foundation for simplified data extraction in the standard system, and allows you to easily configure analytical reporting to suit your needs. Process monitoring and analysis Analytical reports p rovide an overview of open and closed processes as well as the average time for completing a type of process. You can analyze the type of process and displ ay processes for the specific typ e. You can use dashboards or theprocess monitoring tools in the standard sys tem.

1.1.7.1 File-Based Reporting This function enabl es you to extract data from the BOPF bus iness obj ects in SAP EHS Management and export it to your front-end computer in file formats suc h as CSV, Microsoft Excel 2007, or Microsoft Excel 2010. You can use the extracted data later on for performing analytics.

Prerequisites You have made the settings for file-bas ed reporting in Customizing for SAP EHS Management under Reporting


File-Bas ed

.

You are using the business objects delivered in the standard system. You are using a business object node to get the data. This node contains all fields that have to be extracted.

Features Extraction of BO data in different file formats File-b ased reporting allows you to extract data from bus iness objects in SAP EHS Management in a file format you use in your standard office environment. Support of foreground or background processing Dep ending on your entries in the Customizing activity Define Exp ort Profiles , the export is process ed in either the foreground or the bac kground. E-mail shipment of file-based reports The generated export file is sent to the user by e-mail. If the size of the generated file is too large, the file itself will be stored in the system for downloading. Only the link with the download information is inc luded in the e-mail. You can adopt these settings in the Customizing activ ity Configure General Settings . Use of template files As an additional option, it is possib le to upload predefined Microsoft Excel template files in the Customizing activity Define Export Profiles into the system. These templates are than used for generating export files.

Note You have to save the exported file on your computer before opening it. Otherwise, your file is opened in protected view. If you use pivot tables in your Microsoft Excel template file, the data refresh function may not work correctly. For more information about the support of Microsoft Excel Macro-Enabled Workbooks, see SAP Note 1716252

Activities When you start the generation of an export file, the system performs the following activities depending on the various export possibilities: Export in a CSV file format If only one data selection is selected, the exported file is in CSV format. If several data selections are selected, the exported file is a ZIP archive that includes one CSV file per data selection. Export in a Microsoft Excel 2007/2010 file format without template file


Page 27 of 82

If only one data selection is selected, the exported Microsoft Excel file contains one sheet. If multiple data selections are selected, the exported Microsoft Excel file contains one sheet for each data selection. If errors occur, the Microsoft Excel file contains a separate sheet for error messages. Export in a Microsoft Excel 2007/2010 file format with template file If no sheet exists in the template file with the same technical name as the data selection, a new sheet is created during the export. If a sheet exists with the same technical name as the data selection, the data is exported into this sheet. The formatting of the sheet and the order of the columns remains unchanged. Other sheets with, for example, pivot tables or charts for performing analytics, also remain unchanged.

Note Formulas and functions in your Microsoft Excel template are not updated automatically. You have to start the refresh manually.

If you want to create a template file, proceed as follows: Define an export profile in the Customizing activity Define Export Profiles without a template file. Export data using your newly created export profile. Modify this exported file to your preferences. Save the changed file and upload it as a template to your export profile.

More Information For more information about configuring file-bas ed reporting, see Customizing for SAP EHS Management under Reporting


File-Bas ed

.

1.1.7.2 Data Extraction to BW This function enabl es you to extract data from the BOPF bus iness obj ects in SAP EHS Management and transfer it to SAP NetWeaver Bus iness Warehouse (BW) for use later on reports and dashboards. The function provides a foundation for simplified data extraction in the standard system, and allows you to easily configure analytical reporting to suit your needs. The following graphic depicts where the extractor foundation is used:

Extractor Foundation i n Extractin g to BW

In the source system, the extractor functionality is part of the business object, and the business object contains a node with the fields to be extracted. The extractor foundation reads the data provided by the node from BOPF. The node and additional data is included in the extractor structure. The SAPI interface of the DataSource then receives the data from the extractor foundation and transfers it into BW.

Integration You use the extractor foundation only if you use SAP NetWeaver Business Warehouse (BW) for analytical reporting.

Prerequisites You are using the business objects delivered in the standard system. You are using a BO node to get the data. This node contains all fields that have to be extracted to BW and enables the extractor foundation to use the standard BOPF API for reading the data and sending it to BW via the SAPI interface of the DataSource. A transient node can be used if the DataSource has to provide data from multiple BO nodes. In that case, the transient node’s determination reads data from multiple BO nodes.


Page 28 of 82

Features Easier Implementation The BW service API (SAPI) is the interface solution for data transfer to a DataSource in BW and requires that all extractors in the source system implement specific logic. Since the logic is repeated in each extractor, the extractor foundation implements the logic in a common class that is used by all extractors and fulfills the SAPI requirements. Extensible for Customer-Specific Extraction You can use the extractor foundation in your customer-specific projects. You can adjust and create your own transient node. To get the data for extraction, you implement a determination on the root node to get the data for the transient node. The extractor foundation then handles reading and transferring the data, as well as logging errors. Increased Performance The extractor foundation supports processing mass amounts of data by allowing the extraction of multiple data records in one step.

More Information For more information about configuring extractors for BI analytical rep orting, see Customizing for SAP EHS Management under Management


Foundation for EHS

.

1.1.7.3 DataSources A DataSource is a s et of fields that provide the data for a business unit for data transfer. From a technical persp ective, the DataSource is a s et of logically-related fields that are provided to transfer data to SAP NetWeaver BW and the operational data provider in the backend either in a flat structure (extraction structure) or in multiple flat structures (for hierarchies).

More Information For more information, s earch for DataSource, data staging , and Operational Data Provider in the documentation for SAP NetWeaver at http://help.sap.com.

1.1.7.3.1 Workflow Process Definitions DataSource Transactional Data: 0EHSM_FND_WF_01

You can use this DataSource to extract process definitions from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). You can p rocess the extracted data by using the DataSource object 0EHF_DS04 ship ped with this release.

Technical Data Appli cation Component

SAP EHS Management (EHS-MGM-FND)

Available as of Release

Component Extension 1.0 for SAP EHS Management

Shipment

SAP NetWeaver 7.0 BI Content Add-On 5 SP 02

Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction fr om Archives

No

Verifiable

No

Data Modeling Delta Update The delta update used for this DataSource is AIE (After-Images by Ex tractor) . The deciding field for the update is BW_DELTATIMESTMP . Fields of Or igin for the Extract Structure Fields in the Extract Structure

Description of the Field in the Extract

Table of Origin

Field in the Table of Origin

Structure

EHSM_COMP

Component of EHS Management

EHFNDC_PROCDEF

EHSM_COMPONENT

PURPOSE

Purpose of EHS Management Process

EHFNDC_PROCDEF

PURPOSE

PROC_VARIANT

Name of Process Variant

EHFNDC_PROCDEF

VARIANT

BW_DELTATIMESTMP

BW Delta Time Stamp

-

-

Extractor Logic


Page 29 of 82

The DataSource is implemented by a function module (extraction method F1). The extractor transfers the component, the purpose, and the variant of all process templates from the table containing the process definitions EHFNDC_PROCDEF into SAP NetWeaver BW. The data is not aggregated or transformed.

1.1.7.3.2 Workflow Process Instances DataSource Transactional Data: 0EHSM_FND_WF_02

You can use this DataSource to extract process data from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). You can process the extracted data by using the DataSource object 0EHF_DS05 shipped with this release.





Shipment


Content Versi ons

EHM300

RemoteCube-Capable

No

Delta-Capable

Yes


No

Verifiable

Yes



Table of Origin


Structure

EHSM_COMP


-

-

PURPOSE


-

-

PROC_VARIANT


-

-

CONF_KEY

NodeID

-

-

DATE_CREATED

Field of type DATS

-

-

DATE_COMPLETED

Field of type DATS

-

-

STATUS

Internal Status of PCO

-

-

AGE

Overall Age Of This Item In Number Of

-

-

Days OVERDUE

Num ber of Overdue Processes/Steps

-

-

BW_DELTATIMESTMP

BW Delta Time Stamp

-

-

SUBSTANCE_ID

Substance

-

-

MATERIAL_ID

Material

-

-

CUSTOMER_ID

Customer

-

-

SUPPLIER_ID

Supplier

-

-

BW_RECORDNUMBER

Record Number

-

-

PROD_COMP_ID

Product Component

-

-

PARENT_COMP_ID

Parent Component

-

-

DUPLICATE

Dupli cate Record

-

-

REV_STATUS

Revision Status

-

-

-

-

-

-

ACTIVITY OBJECT_TYPE

Activity Object Type

Extractor Logic The DataSource is implemented by a function module (extraction method F1).

Verification of Key Figures


Page 30 of 82

The process log is checked.

1.1.7.3.3 Workflow Step Definitions DataSource Transactional Data: 0EHSM_FND_WF_03






Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

Yes


No

Verifiable

No



Table of Origin


Structure

EHSM_COMP


-

-

PURPOSE


-

-

PROC_VARIANT


-

-

TEMP_ID

Task ID

-

-

NODE_ID

Node Number

-

-

THRESHOLD

Threshold of Report-Relevant Steps

-

-

BW_DELTATIMESTMP

BW Delta Time Stamp

-

-

Extractor Logic The DataSource is implemented by a function module (extraction method F1). The extractor transfers the component, the purpose, and the variant of the process, the node ID, and the task ID of the step and the threshold configured for each step into SAP NetWeaver BW. The system extracts only those steps which are foreground steps or marked as relevant for reporting.

1.1.7.3.4 Workflow Step Instances DataSource Transactional Data: 0EHSM_FND_WF_04






Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

Yes


No

Verifiable

Yes


Page 31 of 82



Table of Origin


Structure

EHSM_COMP


-

-

PURPOSE


-

-

PROC_VARIANT


-

-

CONF_KEY

NodeID

-

-

TEMP_ID

Task ID

-

-

NODE_ID

Node Number

-

-

WORKITEM_ID

Work item ID

-

-

DATE_CREATED

Field of type DATS

-

-

DATE_COMPLETED

Field of type DATS

-

-

STATUS

Internal Status of PCO

-

-

AGE


-

-

Days OVERDUE

Num ber of Overdue Processes/Steps

-

-

BW_DELTATIMESTMP

BW Delta Time Stamp

-

-

AGE_PROC


-

-

Days

Extractor Logic The DataSource is implemented by a function module (extraction method F1).

Verification of Key Figures The step details are checked.

1.1.7.3.5 Workflow Process Definitions - Text Extraction (Full) DataSource Texts: 0EH_DESCRP_TEXT

You can use this DataSource to extract texts for the workflow process definitions.





Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No

Data Modeling Fields of Or igin for the Extract Structure Fields in the Extract Structure


Table of Origin


Structure

LANGUAGE

Language Key

-

-

EHSM_COMPONENT


-

-

PURPOSE


-

-


Page 32 of 82

VARIANT


-

-

DESCRIPTION

Description (Long)

-

-

1.1.7.3.6 Workflow Reporting - Component Description DataSource Texts: 0EH_COMP_TEXT

You can use this DataSource to extract descriptions of components for the workflow reporting.





Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No



Table of Origin


Structure

LANGUAGE

Language Key

-

-

COMPONENT_ID


-

-

DESCRIPTION

Description (Long)

-

-

1.1.7.3.7 Workflow Reporting - URL Extraction (Full) DataSource Attributes: 0EH_URL_ATTR

You can use this DataSource to extract the full URL for the workflow reporting.





Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

no


No

Verifiable

No



Table of Origin


Structure

SERVER

—

-

-

PORT

System ID

-

-

PATH_PREFIX

—

-

-


Page 33 of 82

1.1.7.3.8 Workflow Step Definitions - Text Extraction (Full) DataSource Texts: 0EH_DESCRS_TEXT

You can use this DataSource to extract texts for the workflow step definitions.





Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No



Table of Origin


Structure

LANGUAGE

Language Key

-

-

DESCRIPTION

Description (Long)

-

-

TEMP_ID

Task ID

-

-

NODE_ID

Node Number

-

-

1.1.7.3.9 Texts for Material ID DataSource Texts: 0EH_MATID_TEXT

You can use this DataSource to extract texts for materials.





Shipment

SAP NetWeaver 7.0 BI Content add-on 6 SP 03

Content Versi ons

EHM200

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No



Table of Origin


Structure

MATNR

Material (Number)

MAKT

-

SPRAS

Language

MAKT

-

MAKTX

Description (short)

MAKT

-

MAKTG

Description (uppercase)

MAKT

-

Extractor Logic When there is no short text maintained for the material, the material number is used.


Page 34 of 82

1.1.7.3.10 Common Objects As of component extension 3.0 for SAP EHS Management , the DataSources for common objects, s uch as the locations, are documented in this structure.

1.1.7.3.10.1 Location Master Data DataSource Attributes: 0EH_LOCATIN_ATTR

You can use this D ataSource to extract mas ter data attributes of locations from SAP EHS Management into SAP NetWeaver Busines s Warehouse (BW). The DataSource extracts the data from the following nodes of the location business object EHFND_LOCATION : ROOT REVISION You can process the extracted data by using the InfoObject 0EH_LOCATIN . The location business object supports multiple revisions of the same location. Thus, the master data attributes are time-dependent.





Shipment

SAP NetWeaver 7.0 BI Content add-on 6 SP 03

Content Versi ons

EHM200

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No

Prerequisites You have configured the DataSource in Customizing in the source system under Analytical Reporting

Configure Extractors

SAP EHS Management


.

The BAdI implementation BADI_EHFND_FW_BI_BOPF_OBJ_LIST must be an active default implementation of the BAdI

BADI_EHFND_FW_BI_OBJ_LIST . For more information, see Customizing in the source system under Management


BAdI: Determination of Ob jects to Extract

SAP EHS Management

Foundation for EHS

.

The BAdI implementation BADI_EHFND_FW_BI_BOPF_EXTRACT must be an active default implementation of the BAdI

BADI_EHFND_FW_BI_EXTRACTOR . For more information, see Customizing in the source system under Management


BAdI: Extraction of One Ob ject

SAP EHS Management

Foundation for EHS

.



Table of Origin


Structure

ID

ID of the location

-

-

COUNTRY

Country of the l ocation

-

-

REGION

Region of the l ocation

-

-

PLANT

Plant of the l ocation

-

-

TYPE

Location Type

-

-

DATEFROM

Start date of validity period of record

-

-

DATETO

End date of validity period of record

-

-

BW_RECORDNUMBER

Serial nu mber of records since one risk can -

-

have multiple records BW_RECORDMODE

Record mode that allows flagging records

-

-

-

-

for deletion in BW BW_DELTATIMESTMP

Time stam p for delta load

Extractor Logic The current extractor logic is implemented as a BOPF determination of the transient node BI_LOCATION of the business object EHFND_LOCATION . Since you can revise a location and store older revisions of a location, the revision data is extracted as time-dependent master data attributes. The REVISION node of the location BO contains a field SPLITDATE that specifies the date when the revision of the location started being valid. The value of this field is extracted


Page 35 of 82

into the field DATEFROM in the extractor structure. The field DATETO of the extractor structure is populated with the value of the SPLITDATE minus one day. You can process the extracted data by using the InfoOb ject 0EH_LOCATIN .

1.1.7.3.10.2 Location Hierarchy DataSource Hierarchy: 0EH_LOCATIN_0001_HIER

You can use this DataSource to extract hierarchy data from SAP EHS Management into SAP NetWeaver Business Warehouse (SAP NetWeaver BW). You can process the extracted data by using the InfoSource 0EH_LOCATIN ship ped with this release.





Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No



Table of Origin


-

-

Structure

OLTPSOURCE

DataSource (OSOA/OSOD)

Extractor Logic The DataSource is implemented by a function module (extraction method F1). The extractor transfers the location hierarchy (header and the different nodes) into SAP NetWeaver BW.

1.1.7.3.10.3 Texts for Location DataSource Texts: 0EH_LOCATIN_TEXT

You can use this DataSource to extract texts for locations.


SAP EHS Management (EHS-MGM-INC)



Shipment


Content Versi ons

EHSM10

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No



Table of Origin


Structure

ID

Business Object ID

-

-

DATEFROM

Valid-From Date

-

-

DATETO

Valid-To Date

-

-

LANGUAGE

Language Key

-

-


Page 36 of 82

Location N ame Description

TEXT

-

-

1.1.7.3.10.4 Texts for Location Type DataSource Texts: 0EH_LOCTYPE_TEXT

You can use this DataSource to extract texts for location types from SAP EHS Management into SAP NetWeaver Bus iness Warehouse (SAP NetWeaver BW).





Shipment


Content Versi ons

EHM200

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No

Prerequisites You have configured location type s in the source sys tem in the Customizing activity for S AP EHS Management under Locations

Specify Location Types


.



Table of Origin


Structure

LANGUAGE

Language

-

-

CODE

Location Type

-

-

DESCRIPTION

Description (Extra Short) of Location

-

-

1.1.7.3.10.5 Texts for Location Authorization Group DataSource Texts: 0EH_LOCAGRP_TEXT

You can use this D ataSource to extract texts for location authorization groups from SAP EHS Management into SAP NetWeaver Bus iness Warehouse (SAP NetWeaver BW).





Shipment


Content Versi ons

EHM200

RemoteCube-Capable

No

Delta-Capable

No


No

Verifiable

No

Prerequisites You have configured location type s in the source sys tem in the Customizing activity for S AP EHS Management under Locations

Specify Authorization Groups


.


Page 37 of 82

Fields of Or igin for the Extract Structure Fields in the Extract Structure


Table of Origin


-

-

-

-

-

-

Structure

Language

LANGUAGE

Authorization Group

CODE DESCRIPTION

Description (Extra Sh ort) of Authorization Group

1.1.8.1.3 Roles In SAP EHS Management , you use spec ific roles in the appli cation to acc ess c ontent. These roles are spec ific to the two different user interfaces s upp orted by the application — SAP NetWeaver Portal and SAP NetWeaver Business Client. The roles for each of these interfaces are described in the following documentation: Business Package (Portal Content) Roles in SAP NetWeaver Business Client All roles are provided without any authorizations ass igned to them. You must assign authorizations using the authorization objects in the back -end system.

Master Roles In addition to these roles, two master roles (PFCG roles in the back-end system) are provided for both user interfaces. These roles contain the complete content of the SAP EHS Management applic ation. SAP_EHSM_MASTER This role contains the complete SAP EHS Management content. SAP_EHSM_MASTER_CLASSIC This role contains content for SAP EHS Management as p art of SAP ERP, which is not covered by the add-on SAP EHS Management . When creating user-defined roles, we recommend you use each master role as a template and you remove the undesired functions. This ensures that no configurations (for example, OBN settings) are lost.

1.1.8.1 Business Package (Portal Content) As of component extension 3.0 for SAP Environment, Health, and Safety Management (SAP EHS Management), the Business Package for EHS Management is av ailable. The enhanced bus iness p ackage allows you to use the functions p rovided in inc ident management, p roduct compliance, ris k as sessment, and in the foundation for SAP EHS Management . For more information, s ee Incident Management, Product Compliance (EHS-MGM-PRC), Risk Assessment, and Foundation for EHS M anagement. Technical Data Availability

As of component extension 3.0 for SAP EHS Management wi th SAP enh ancement package 5 for SAP ERP 6.0 (minimum SP stack 05) and SAP enhancement package 2 for SAP NetWeaver 7.0 (min imum SP stack 08).

Data Source

Component extension 3.0 for SAP EHS Management and SAP enhancement package 5 for SAP ERP 6.0

Browser Recommendation

Microsoft Internet Explorer 7 Microsoft Internet Explorer 8 Mozilla Firefox 3.5 Apple Safari 4 For more information about system prerequisites for these components, see the Product Availability Matrix on SAP Service Marketplace at http://service.sap.com/pam .

Languages Available

SA Arabic ES Catalan CS Czech DE German EN English ES Spanish FI Finnish FR French HE Hebrew HU Hu ngarian IT Italian JA Japanese KO Korean NL Du tch NO Norwegian PT Portuguese RU Russian SK Slovakian SV Swedish TR Turkish ZF Chinese Traditional ZH Chinese Simplified

Support

EHS-MGM-FND-EP


Page 38 of 82

Prerequisites To use the most up-to-date functions delivered for the roles integrated with enhancement package 5 for SAP ERP 6.0 , you have activated the EH&S Continuous Improvement (LOG_EHS_CI2) business function and the Enterprise Extension PLM (EA-PLM switch). If you want to use SAP BusinessObjects Dashboards and SAP Business Explorer (BEx) reports to analyze aggregated data, you need to order the relevant SAP BusinessObjects software. For more information, see SAP Note 1486885. You have all the authorizations required for the back-end system. You have a portal user that is assigned to a user with the required authorizations. This business pack age uses objects from a further business p ackage or packages. These objects are listed in the section Shared Objects in this Business Package. If you intend to use these objects, you must also implement the relevant business package. For more information, see the relevant business pack age documentation.

1.1.8.1.1 Business Package for EHS Management (Enhanced) Technical Data Component extension 3.0 SP03 for SAP Environm ent, Health, and Safety

Pr oduct Version

Management (SAP EHS Management) . Not valid for:

Country Relevance

Spain: If you would like to use this product version in Spain, contact your local SAP representative.

As of component extension 3.0 SP0 3 for SAP EHS Management , the Business Package for EHS Management has been enhanced. The roles for risk assessment and product compliance have been enhanced to include the following new iViews: iView

Application

Edit Recommendation Criteria for Health Surveillance Protocols

Risk Assessment

Edit Health Su rveill ance Protocols

Risk Assessment

Display ProdStewNet Confirmation Import Display ProdStewNet Confirmation Import

Product Compliance

The existing functions for incident management, risk assess ment, product compliance and foundation are also availab le in the business pack age. For more information about the functionality in SAP EHS Managem ent , see the following documentation: Foundation for EHS Management (EHS-MGM-FND) Incident Management (EHS-MGM-INC) Risk Assessment (EHS-MGM-RAS) Product Compliance (EHS-MGM-PRC)

1.1.8.1.2 Configuration Information You use this procedure to make the necessary settings to integrate the Business Package for EHS Management into your SAP NetWeaver Portal.

Prerequisites You have familiarized yourself with the software components required and the implementation strategy. To do this, see the relevant guides on SAP Service Marketplace at http://service.sap.com/instguides.

Note For information about Web browsers, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/pam.

Procedure 1. You set up the sys tem landscap e in the SAP NetWeaver Portal (see Setting Up the Sys tem Landscap e). 2. In the SAP NetWeaver Portal, you ass ign the portal roles to users . You define the following sy stem alias es for the SAP NetWeaver Portal content:

SAP_ECC_EnvironmentHealthSafety for the SAP EHS Management functions SAP_R3_EHS for the environment, health, and safety functions based on SAP ERP You must enter a target system for the entire role for the PFCG roles in the environment, health, and safety processes based on SAP ERP. For more information, s ee Role Maintenance in PFCG. For more information about creating cus tom roles spec ificall y for SAP EHS Management , see Creating Custom Roles. For general i nformation about changing standard roles, see Changing Standard Roles. 3. To open iViews deliv ered with the Business P ack ages of integrated systems , for exampl e, iViews for a material of Material Management (MM) or for a functional location of Plant Maintenance (PM), from within the SAP EHS Management app lication, you must enter a target sy stem for the corresp onding serv ice in the PFCG role. The target sy stems for integrated sy stems are also maintained in Customizing for SAP EHS Management under for EHS Management

Integration

Specify Destinations for Integration

Foundation

.

For more information about entering a target system in the PFCG role, see 5.10 Remote Systems. For more information about the objects from other Business Packages, see Shared Objects.


Page 39 of 82

4. You make the settings as describ ed in Setting Up the Universal Worklist. 5. To integrate incident management into your employee self-s ervic e center, you follow the procedure desc ribed in Adding Incident-Related iViews to the Employee Self-Service Center .

1.1.8.1.2.1 Adding Incident-Related iViews to the Employee SelfService Center You can integrate initial incident recording from SAP EHS Management into the Employee Self-Serv ice (ESS) area in the SAP NetWeaver Portal so that you can record an incident from there. The following information describes how you configure ESS to include initial incident recording.

Procedure 1. In the SAP NetWeaver Portal, choose the Content Administration work center. 2. Choose the Portal Content workset from the structure on the left.

Creating an Incident Reporting iView Using the iView Wizard 1. Choose

New

iView

and then select the iView template – Create an iView from an existing iView template radio button. Then choose Next .

2. Select the Workset Map iView template and choose Next . 3. Complete the following fields. You can either use the exampl e input bel ow or make your own entries: Field

Example Input

Name

Incident Reporting

iView ID

IncidentReporting

iView ID Prefix

com.technidata.hss.ess

Choose Next . 4. Review the summary of your iView and then choose Finish .

Creating a new Report Incident iView Using the iView Wizard 1. Choose the iView template – Create an iView from an existing iView template radio button and then choose Next . 2. Select the SAP Web Dynp ro iView template and choose Next . 3. Complete the following fields. You can either use the exampl e input bel ow or make your own entries: Field

Example Input

Name

Report Incident

iView ID

ReportIncident

iView ID Prefix


Choose Next . 4. Select the Web Dynp ro platform as Web Dynpro for ABAP and choose Next . 5. Complete the following fields. You can either use the exampl e input bel ow or make your own entries: Field

Example Input

System

Q35LNT004

Namespace

SAP

Application Name

EHHSS_INC_REC_GAF

Select Plain HTML as the Web Dynpro Client and choose Next . 6. Review the summary of your iView and then choose Finish .

Creating a New Incident Reporting Page Using the Page Wizard 1. Choose

New

Page

.

2. Complete the following fields. You can either use the exampl e input bel ow or make your own entries: Field

Example Input

Page Name

Incident Reporting

Page ID

IncidentReporting

Page ID Prefix


Description

Offers access to report incidents of different categories. Possible categories are incident, near miss and safety observation.

Choose Next . 3. Select Web Dynpro Proxy Page as the page template and choose Next . 4. Select 1 Column (Full Width) from the Available Layouts and Add to add it to the Selected Layouts . Then choose Next . 5. Review the summary of your page and then choose Finis h . Choose the option to O pen the objec t for editing and choose OK . 6. Op en the page and add the Incident Reporting iView to the page as a delta link.

Creating a New Report Incident Page Using the Page Wizard 1. Choose

New

Page

.


Page 40 of 82


Example Input

Page Name

Report Incident

Page ID

ReportIncident

Page ID Prefix


Description

Offers access to report an incident including persons, assets and releases.

Choose Next . 3. Follow steps 3 to 5 above. 4. Op en the page and add the Report Incident iView to the page as a delta link.

Creating a New Incident Reporting Workset Using the Workset Wizard 1. Choose

New

Workset

.


Example Input

Workset Name

Incident Reporting

Workset ID

IncidentReporting

Workset ID Prefix


Description

Offers access to report incidents of different categories. Possible categories are incident, near miss and safety observation.

Choose Next . 3. Review the summary of the workset and then choose Finish . 4. Op en the workset and add the Incident Reporting and Report Incident pages as delta links.

Adding the Incident Reporting Workset to an Existing Employee Self S ervice Role

Note The following information provides a sample configuration. If incident recording has been implemented in the customer's ESS, the keys and PCD locations will be customer specific. You must use the PCD location in the correct context (the complete path).

1. Call transac tion SPRO and display the Personnel Management structure. 2. Choose

Personnel Management

Resources Component

General Settings

Field

Server

3. Choose

Employee Self-Service

Homepage for Self-Services

Resources

Define Server for

and make the following entries:


Define Resources (Add Entries) Component

Example Configuration

Server

Z_HSS_TEST

Protocol

http

Name and Port

uxai2q35.wdf.sap.corp:50021

Directory Path

sap/bc/webdynpro/sap/ehhss_inc_rec_gaf


General Settings

Field

Resource 1 (Incident Reporting Page)


Resources

Define Resources

and make the following entries: Example Configuration

Resource Object Key

Z_HSS_INCREP_PAG

Description

Incident Reporting Page

URL of PCD Page

ROLES://portal_content/Sandbox/C5111368/com.techni data.hss.ess.roles/com.sap.pct.erp.ess.employee_self_s ervice/com.sap.pct.erp.ess.employee_self_service/com.t echnidata.hss.ess.incidentReporting/com.technidata.hss .ess.incidentReporting

4. Choose


Define Resources (Add Entries) Component


General Settings

Field

Resource 2 (Report Incident Page)


Resources

Define Resources

and make the following entries: Example Configuration

Resource Object Key

Z_HSS_INCREP_SER_INC

Description

Report Incident

Server Definition

Z_HSS_TEST

URL Parameter

sap-client=004&sap-language;=EN

URL of PCD Page

ROLES://portal_content/Sandbox/C5111368/com.techni data.hss.ess.roles/com.sap.pct.erp.ess.employee_self_s ervice/com.sap.pct.erp.ess.employee_self_service/com.t echnidata.hss.ess.incidentReporting/com.technidata.hss .ess.reportIncident

5. Choose


Services (Add Entries) Component


General Settings


Services

Define Services

Define

and make the following entries: Field



Page 41 of 82

Service

Service Key


Service Link Text

Report Incident

Type

Web Dynpro ABAP application

Link Resource


Service Description

Report incident including injured persons, damaged assets and/or rel eases

6. Choose


Subareas


Assign Services to Subareas (Find Entries)

Component


Define Subareas (Add Entries)


Z_HSS_INCREP

Service Key Short (Table Key)


Position

001

General Settings



Z_HSS_INCREP

Subarea Text

Report Incident

General Settings


Field


Subareas

Assign Subareas to


Area Key

Z_HSS_INCREP

Subarea Key

Z_HSS_INCREP

Position

001


General Settings


Areas

Define Areas

Define Areas


Component

Field

Area


Area Key

Z_HSS_INCREP

Area Link Text

Incident Reporting

Link Type

Web Dynpro Java application

Link Resource

Z_HSS_INCREP_PAG

Area Description Summ ary

Pages

Define Subareas


Assign Subarea to Area

10. Choose

Subareas

Subarea Key


Component

(Add Entries)


Field

Assign Sub areas to Areas (Find Entries)

9. Choose

Assign Services to

Subarea Key


Subarea

Areas

Services


Component

8. Choose


Field

Assign Service to Subarea

7. Choose

General Settings




Assign Areas to Area Group Pages (Find Entries)

Component

General Settings

Report Incidents, Near Misses and Safety Observations


Field

Assign Area to Area Group Page

Areas

Assign Areas to Area Group


Area Group Key Area Key Position


SAPDEFAULTESSINEIC_ERP2005 Z_HSS_INCREP 15

1.1.8.1.2.2 Creating Custom Roles Procedure The roles provided with the Business Package for EHS Management contain specific configuration settings, for example, as object-based navigation settings. To create custom roles without losing the configuration settings, proceed as follows: 1. Create your custom PFCG role. 2. Copy the menu structure from either delivery role SAP_EHSM_MASTER or SAP_EHSM_MASTER_CLASSIC . 3. Generate the authorization profile. 4. Ass ign the custom role to end users. For custom portal roles, the following additional steps are required. Either upload the custom role to the SAP NetWeaver Portal using the role upload tool, or create a custom portal role directly in the SAP NetWeaver Portal using the following procedures. For custom roles created from role SAP_EHSM_MASTER : 1. Create the custom portal role as new p ortal role 2. Add the workset SAP_EHSM_MASTER as a delta link. 3. Remove all delta link s to the servic es that you do not want to include in y our custom portal role. 4. Ass ign the custom portal role to end users. For custom roles created from roles SAP_EHMS_MASTER_CLASSIC : 1. Create the cus tom portal role as new role. 2. Add delta-links to the Product Safety and Stewardship and Health and Safety worksets. 3. Remove all delta link s to the servic es that you do not want to include in y our custom portal role. 4. Ass ign the custom portal role to end users.


Page 42 of 82

Note All app lications for which a user should have authorization must exist in a role and the user must be assigned to that role. The applic ations cannot be split over multiple roles. You can use the master roles (SAP_EHSM_MASTER or SAP_EHSM_MASTER_CLASSIC ) for SAP EHS Management as a template.

More Information For more information about configuring roles, see Creating Single Roles. For more information about configuring role menus, see Creating Role Menus Creating Role Menus.

1.1.8.1.2.3 Setting Up the System Landscape Procedure 1. Create a Sys tems folder (if one does not already ex ist) in the SAP NetWeaver Portal. To do so, proceed as follows: 1. Choose

System Administration

System Configuration

System Landscape

. Position your cursor on Portal Content and use the context

menu (right mouse button) to create the new Sys tems folder. 2. Create entries for the logical sy stems listed below in the Systems folder.

Note If you run more than one of the specified logical sys tems in a phy sical sys tem (such as SAP EHS Management and Environment, Health, and Safety in ERP in one system XYZ in client 000), it is sufficient if you create one entry that you assign all the relevant system aliases to. Proceed as follows: 1. Create a portal sy stem for each sys tem by us ing the context menu for the Systems folder (choose

New

System from Template

).

2. Use an SAP sy stem with load balancing as a template. 3. Enter the name of the physical sy stem (such as XYZ/000 ) as the description and ID. Make your company-specific settings to the fields under the following property categories: Connector Internet Transaction Server (ITS) The correct ITS path is /sap/bc/gui/sap/its/webgui Web Application Server (WAS) 4. Assign the spec ified sys tem aliases. Software c omponents: Logical System

System Ali as

Physi cal System

SAP EHS Management

SAP_ECC_EnvironmentHealthSafety

ERP system with SAP EHS Management processes is

EH&S in ERP

SAP_R3_EHS ERP

installed System with EH&S processes in ERP 6.0 is installed

More Information For general information about the system landscape for the SAP NetWeaver Portal, see System Landscape.

1.1.8.1.2.4 Setting Up the Universal Worklist Workflow items of users appear in the default universal worklist in the SAP NetWeaver Portal. For general information about changing configuration settings, see Universal Worklist Configuration.

Prerequisites You have installed the Univers al Worklis t configuration file. You have installed the business package.

Procedure The following procedure provides you with information about setting up system connections for the universal worklist: 1. In the SAP NetWeaver Portal, choose Systems Configuration

System Administration

System Configuration

Universal Worklist and Workflow

Universal Worklist

UWL

.

2. Create the following sys tem connections: System alias: SAP_ECC_EnvironmentHealthSafety Connection type: WebFlowConnector

Note If you have already registered a suitable connector to the system that is connected to the system alias, the existing connector is sufficient and you do not need to register an additional one.


Page 43 of 82

Leave the Web Dynpro Launch Sys tem field blank for all s ystem connections.

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

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

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

Activity

Relevant iView

1. Adds and assigns the investigation step

Edit Incident (00000033)

Risk Assessment Role Required

for evaluating controls to a investigation step responsible. 2. Opens the investigation step to review the controls and add comments for the step responsible. 3. Selects the lin ked hazard name to review Display Risk Assessment (00000169)

X

the hazard for the control. Investigation Step Responsible

4. Opens inbox and selects the evaluation

Inbox (00000048)

task. 5. Chooses the Display Inc. pu shbutton

Display In cident (00000034)

from the inbox. 6. Opens th e task and evaluates the

Investigation Step (00000032)

controls. 7. Selects the lin ked location nam e to view

Display Location (00000015)

the location information. 8. Selects the lin ked hazard name to review Display Risk Assessment (00000169)

X

the risk assessment for the hazard.

More Information For more information about creating custom roles, see Creating Custom Roles.

1.1.8.1.3 Roles 1.1.8.1.3.1 Incident Manager Role: com.sap.pct.eh.role.IncidentManager


Page 44 of 82

The Incident Manager role is assigned to the person who manages and maintains the incident record that was initially created by the incident reporter. This person is responsible for ensuring that all information associated with the incident is properly entered in a timely manner, verified, and approved, and that the record is closed. The incident manager is an expert for incident management and is expected to use the solution on a daily basis. The number of incidents processed strongly depends on the size of the company, the industry, and the number of employees and contractors. Depending on the severity and complexity of an incident, the corresponding incident record may need to remain open for a certain period until the process is completed. It is therefore possible for the incident manager to manage more than one incident at the same time.

The incident manager checks and completes the basic information that is already saved in the initial incident record and enters additional data on, for example, involved persons, assets, damages, or released materials. To provide more detailed background information on specific aspects of an incident, the incident manager can gather statements from involved persons and attach documents to the incident record. The incident management process can also include workflows such as notification and approval, along with actions that might avoid further incidents in the future. After completing and approving an incident record, the incident manager prepares and submits the relevant incident report(s) to the local authorities. For more information about the individual tasks, see the workset descriptions in this documentation.

Integration The incident manager checks and completes the basic information that is initially entered by the incident reporter during initial incident recording. To complete the incident management process, the incident manager has to work in close cooperation with the following people: Injured person (if applicab le) To gather information that must be included in the incident record and in legal reports Other involved persons such as witnesses To gather additional information that must be included in the incident record and in legal reports Responsible human resources administrator To gather organizational information and information on the inv olved p ersons Manager of the plant where the incident occurred This person is the person who is legally responsible Responsible members of management who must be notified

Configuration This role uses object-based navigation. For more information, see Ob ject-Based Navigation.

1.1.8.1.3.5.1 Health and Safety Technical Data Technical Name

00000002

You can use this work center to access the health and safety worksets.

1.1.8.1.3.5.1.1 Overview Technical Data Technical Name

00000003

1.1.8.1.3.5.1.1.1 Work Overview Technical Data Technical Name

00000047

You use this workset to display your tasks.

Features For more information, see the individual iViews.

More Information For more information, s ee Process Foundation (EHS-MGM-FND-WF).

1.1.8.1.3.3.1.1.1.1 Inbox Technical Data


Page 45 of 82

Techn ical N ame of the iView

Techn ical Name of the Appli cation

00000048 Web Dynpro Application: IBO_WDA_INBOX (Parameter: WDCONFIGURATIONID=EHHSS_WDAC_POWL_INBOX) ABAP/Web Dynpro

Run time Techn ology Data S ource or Da ta Store

Data source as specified for the business package

Support

EHS-MGM-FND Availability as specified in the business package

Availability

The iView is invisible in the navigation area.

Visibility

You can use this iView to display the tasks that are assigned to you in an inbox. The inbox displays the task subject, when the task was s ent, and its priority. You can also see the date by which the task must be completed, the status of the task, who forwarded it to you, and a preview of the task. In the preview, you can provide additional notes and add attachments to the task preview. When you choose the task link in your inbox, the system displays the corresponding data record or a screen where you can perform the task. If you want to see the related incident record associated with the task, you can select the task row and choose Display Inc.. From this iView you can also specify that you are not responsible for the work, resubmit it, or end the resubmission. You can forward the work to someone else, or assign it to yourself if it is already assigned to another processor. You can also maintain a substitute who will take over your work in the event of planned or unexpected absences and you can create and activate a rule that assigns tasks to a spec ified assignee. This iView disp lays the tasks in the inbox according to a sp ecified query. You can define and change queries in this iView. You can export the list of tasks in a spreadsheet format.

Prerequisites You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

Configuration If you want to replace the inbox with the universal worklist (UWL), you must create a customer-specific SAP NetWeaver Portal role that includes this iView. To do this, perform the following steps: 1. Copy the role. 2. Include the Universal Worklist iView in the copied role next to the Inbox iView. 3. Delete the Inbox iView from the copied role. 4. To include the standard Services iView, choose Edit for the iView and select Dynamic Navigation in the Disp lay selection box. Then, add the iView to dynamic navigation. 5. Configure the Univers al Worklist iView as the default entry for the folder and to be inv isi ble in navi gation areas 6. Set the parameters s pec ific to the universal worklis t, for exampl e, View , to have the same values as in the configuration XML file. For more information about configuring the UWL, see Universal Worklist Configuration.

1.1.8.1.3.3.1.1.2 Incidents Technical Data Technical Name

00000022

You can use this workset to manage and maintain incident records. This includes various types of data, corrective actions, witness statements, photographs, and other documents .


More Information Incident Management

1.1.8.1.3.1.1.1.2.1 Incident Entry Screen Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000023 Web Dynpro Application: EHHSS_INC_ENTRY ABAP/Web Dynpro

Data S ource or Da ta Store


Support

EHS-MGM-INC


Page 46 of 82

Availability as specified for the business package

Availability


Visibility

You can use this iView to access incident records. You can display a list of the incident records that you used recently and you can search for incident records.



1.1.8.1.3.1.1.1.2.2 Incident Search Technical Data Techn ical N ame of the iView

00000024


Web Dynpro Application: ESH_SEARCH_RESULTS_UI (Parameter: SCOPE_DDLB=EHHSS_INCIDENT&EMBEDDED=X) ABAP/Web Dynpro



Support

EHS-MGM-INC Availability as specified for the business package

Availability


Visibility

You can use this iView to search for data records in incident management with SAP NetWeaver Enterprise Search.

Prerequisites You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations. You have implem ented the Configure Embedded Search for SAP EHS Management activ ity in Customizing for SAP EHS Management under Management

General Configuration

Incident

.

Configuration To make SAP NetWeaver Enterprise Search the default entry on the user interface, you must perform the following steps: 1. In the Incident Entry Screen iView in the SAP_EHSM_MASTER workset, set the default entry for the folder property to No . 2. In the Incident Search iView, set the default entry for the folder property to Yes .

1.1.8.1.3.2.1.1.1.2 Report Incident (Simplified) Technical Data Techn ical N ame of the iView

Techn ical Name of the Appli cation Run time Techn ology

00000046 Web Dynpro Application: EHHSS_INC_REC_QAF (Parameters: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-INC

Availability


You can use this iView to record initial information about an incident that occurred in your organization, for example: A descrip tion of the incident People who were injured during the incident People who witnessed the incident The initial incident information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.

Integration PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 47 of 82

To record more detailed initial information about an incident, you can use the Report Incident iView. The incident record can be reviewed and completed by an authorized user in the Review and Completion of Incident Records step. This iView is called v ia object-based navigation using the method CreateSimple of the business object BPR_INCIDENT . For more information about the business object, see Incident.


More Information Incident Recording

1.1.8.1.3.2.1.1.1.3 Report Incident Technical Data Techn ical N ame of the iView

00000045


Web Dynpro Application: EHHSS_INC_REC_GAF_V3 (Parameters: CHANGE_MODE=C&sap-explanation=X) ABAP/Web Dynpro



Support


Availability

You can use this iView to record initial information about an incident in your organization, for example: A descrip tion of the incident Injured people Witnesses Releases Involved assets The initial incident information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.

Integration To record less detailed initial information about an incident, you can use the Report Incident (Simplified) iView. The incident record can be reviewed and completed by an authorized user in the Review and Completion of Incident Records step. This iView is called v ia object-based navigation using the method create of the business object BPR_INCIDENT . For more information about the business object, see Incident.

Prerequisites Depending on the information you want to record, you have made the relevant settings in Customizing for SAP EHS Management under Management

Incident Recording

Incident

.

You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.


1.1.8.1.3.2.1.1.1.4 Report Near Miss Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation

00000044 Web Dynpro Application: EHHSS_INC_REC_NRM_QAF_V3 (Parameters: CHANGE_MODE=C&sapexplanation=X)

Run time Techn ology

ABAP/Web Dynpro



Support

EHS-MGM-INC

Availability



Page 48 of 82

You can use this iView to record initial information about a near miss that occurred in your organization, for example: A descrip tion of the near miss People who were nearly injured during the near miss The circumstances of the near miss The initial near miss information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.

Integration The incident record can be reviewed and completed by an authorized user in the Review and Completion of Incident Records step.

Prerequisites You have specified the relevant near miss groups in Customizing for SAP EHS Management under Information

Specify Near Miss Groups

Incident Management

Incident Recording

Basic

.


Configuration We recommend that you also make the following setting in Customizing for SAP EHS Management under Information

Incident Management

Incident Recording

Basic

:

Specify the relevant risk types to classify the likelihood of the near miss circumstances c ausing an incident in the future under Specify Estimated Risk Types. Specify the relevant location types under Specify Location Types.


1.1.8.1.3.2.1.1.1.5 Report Safety Observation Technical Data Techn ical N ame of the iView


00000043 Web Dynpro Application: EHHSS_INC_REC_SFO_QAF_V3 (Parameter: CHANGE_MODE=C&sapexplanation=X) ABAP/Web Dynpro



Support


Availability

You can use this iView to record initial information about a safety observation in your organization, for example: A descrip tion of the safety observation The people who were observed The circumstances of the safety observation The initial safety observation information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.


Prerequisites You have specified the relevant safety observation groups in Customizing for SAP EHS Management under Basic Information

Specify Safety Ob servation Groups

Incident Management

Incident Recording

.



Incident Management

Incident Recording

Basic

:

Specify the relevant risk types to classify the likelihood of the near miss circumstances c ausing an incident in the future under Specify Estimated Risk


Page 49 of 82

Types. Specify the relevant location types under Specify Location Types.


1.1.8.1.3.1.1.1.2.7 Display Progress Log for External Notifications Technical Data Techn ical N ame of the iView


00000039 Web Dynpro Application: EHFND_EXT_NOTIF_PROCESS_LOG (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND Availability as specified for the business package

Availability


Visibility

You can use this iView to display the progress log for a process. You can see when each process was sent, its status, and who or what performed the processing. You can also view any comments or attachments for the process step. This iView also enables you to create a print version of the result list as a PDF document or to export the list in a spreadsheet format.

Integration From this iView you can display technical information about the task, and also display the workflow log view showing technical details or a graphical workflow log. This iView is called v ia object-based navigation using the method OpenProgressLog of the bus iness object BPR_FNDEXT using the parameters

EXT_NOTIF_CAT={EXT_NOTIF_CAT} , EXT_NOTIF_ID={EXT_NOTIF_ID} , and WORKITEM_ID={WORKITEM_ID} . For more information about the business object, see Business Objects.

More Information Integration for Notifications Process Foundation (EHS-MGM-FND-WF)

1.1.8.1.3.1.1.1.2.8 Notify Task Processor Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000037 Web Dynpro Application: EHFND_TMG_NOTIFY_PROCESSOR_QAF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND

Availability Visibility

Availability as specified for the business package The iView is invisible in the navigation area.

You can use this iView to send a notification to the person who is responsible for processing a task. You can enter an e-mail text and then send it to the person responsible. An e-mail is sent to the person who is resp onsib le for processing the task.

Integration This iView is called via object-based navigation using the method NotifyProcessor of the business object EH_FND_WFF_OBN using the parameter

SO_GUID={SO_GUID} . For more information about the business object, see Business Objects.



Page 50 of 82

1.1.8.1.3.1.1.1.2.9 Display Application Log Technical Data Techn ical N ame of the iView


00000036 Web Dynpro Application: EHFND_WF_APPL_LOG_OIF (Parameter: CHANGE_MODE=' '&sapexplanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

This iView disp lays the log messages for the process s cheduler, which stores messages in the applic ation log. You see the type of message, the message text, and the time when message was created.

Integration This iView is called v ia object-based navigation using the method Show_Log of the bus iness object BPR_EHFND_APPL_LOG using the parameters

LOG_HDL={LOG_HDL} and LOG_NO={LOG_NO} .


More Information Process Foundation (EHS-MGM-FND-WF)

1.1.8.1.3.3.1.1.2.1 Execute Process Decision Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000035 Web Dynpro Application: EHFND_WFF_DECISION (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND



You can use this i View to make a decision, for example, to approve that an action has b een completed. You acces s this iView by selecting the link in the Category column of a decision task in the Edit Incident iView. After you have made the decision in this iView, the system triggers the next step in the process and displays the Edit Incident iView again. This way, y ou can make decisions directly in an inci dent data record. Alternatively, you can access the decision task in your inbox (Inbox iView).

Integration This iView is called via object-based navigation using the method OpenProgressLog of the business object EH_FND_WFF_OBN using the method

OpenProcessDecision and parameter ID={ID} . For more information about the business object, see Business Objects.

Prerequisites The decision step of the process is assigned to you. If you are not the processor, the link in the Category column is inactive. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.3.1.1.2.2 Display Incident Technical Data


Page 51 of 82



00000034 Web Dynpro Application: EHHSS_INC_REC_OIF_V3 (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to display incident records. For example, the incident record can contain the following information: A descrip tion of the incident Injured people Witnesses Releases Involved assets Investigation details Risk matrix information Financial information Forms, supporting documents, and associated actions and notifications. For more information, s ee Review and Completion of Incident Records.

Integration This iView is called via object-based navigation using the method Display of the business object BPR_INCIDENT using the parameter KEY={Key} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.2.12 Edit Incident Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000033 Web Dynpro Application: EHHSS_INC_REC_OIF_V3 (CHANGE_MODE=U&sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND



You can use this iView to edit incident records. For example, the incident record can contain the following information: A descrip tion of the incident Injured people Witnesses Releases Involved assets Investigation details Risk matrix information Financial information Forms, supporting documents, and associated actions and notifications. For more information, s ee Review and Completion of Incident Records.

Integration This iView is called via object-based navigation using the method Edit of the business object BPR_INCIDENT using the parameter KEY={Key} . For more information about the business object, see Business Objects.



Page 52 of 82

1.1.8.1.3.1.1.1.2.13 Investigate Step Technical Data Techn ical N ame of the iView


00000032 Web Dynpro Application: EHHSS_UI_INC_QAF_INV_STEP (Parameter: CHANGE_MODE=U&sapexplanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to process an online investigation step. For more information, s ee Investigation.

Integration This iView is called via object-based navigation using the method InvestigateStep of the business object BPR_INCIDENT using the parameter

KEY={Key} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.2.14 Take Over Inquiry Response Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000031 WebDynpro Application: EHHSS_INC_REC_ITO_QAF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-INC



You can use this iView to review the data that the recipient of an inquiry has provided offline on the inquiry form. The data is displayed in a table listing the changes that were made. You can decide whether or not to keep these changes. Keeping them transfers the additional information into the incident record. With this iView you can disp lay the data of the inquiry recip ient and injured people us ing the links provided. You use the checkboxes to choose whether or not to keep the changes that were made to the data. Choose Submit to integrate the changes in the record. This iView allows you to display the form that the recipient of the inquiry has completed. You can display the relevant form using the link provided.

Integration This iView is called via object-based navigation using the method TakeOverInquiry of the business object BPR_INCIDENT using the method and the parameters WDCONFIGURATIONID={WDCONFIGURATIONID} and PCBO_KEY={PCBO_KEY} . For more information about the business object, see Incident.

Prerequisites The inquiry recipient has completed and returned the inquiry form. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

More Information Inquiries

1.1.8.1.3.1.1.1.2.15 Display Generic Process Setup PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 53 of 82

Technical Data Techn ical N ame of the iView


00000030 Web Dynpro Application: EHFND_PSE_OIF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to display information about a recurring task. You can see when the task is scheduled, how often the task recurs, and how long the task should run for. You can also see a log of the processes that were started and the log messages from the process scheduler.

Integration This iView is called via object-based navigation using the method Display of the business object BPR_PROC_SETUP using the parameter KEY={Key} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.2.16 Edit Generic Process Setup Technical Data Techn ical N ame of the iView


00000029 Web Dynpro Application: EHFND_PSE_OIF (Parameter: sap-explanation=X&change_mode=D) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to edit information about a recurring task.

Integration This iView is called via object-based navigation using the method Edit of the business object BPR_PROC_SETUP using the parameter KEY={Key} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.2.17 Display Change Documents Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000038 Web Dynpro Application: EHFNDWDC_CH_DOC_SEARCH (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND



You can use this iView to display change documents. You can specify a date range and/or a user and then search for the relevant change documents. The result list displays the following:


Page 54 of 82

Date and time of the changes Type of change that was made Node name Old and new values Field desc ription User who made the changes You can also view additional details about the change by clicking the link in the Action column. This iView is called via object-based navigation using the method Display of the business object BPR_FND_CD using the parameters

OBJECT_ID={OBJECT_ID} and OBJECT_NAME={OBJECT_NAME} .


1.1.8.1.3.1.1.1.2.18 Create Generic Process Setup Technical Data Techn ical N ame of the iView


00000027 Web Dynpro Application: EHFND_PSE_OIF (Parameter: CHANGE_MODE=C&sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to create a recurring task. You can define when the task is scheduled, how often the task recurs, and how long the task should run for.

Integration This iView is called via object-based navigation using the method Create of the bus iness object BPR_PROC_SETUP using the parameters

COMP={Component} and PURPOSE={Purpose} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.2.19 Change Assignee Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation

00000026 Web Dynpro Application: EHFND_PCBO_CHANGE_ASSIGNEE (Parameter: WDCONFIGURATIONID=EHFND_PCBO_CHANGE_ASSIGNEE_QAF&sap-explanation=X)


ABAP/Web Dynpro



Support

EHS-MGM-FND



You use this iView to change the person who should implement an action. It displays the relevant action including its category, type, and a description. You also see the person to whom the action is currently assigned, and you can specify the new assignee who should implement the action.

Integration This iView is called v ia object-based navigation using the method ChangeAssignee of the business object BPR_FNDACT using the parameter

INSTANCEID={instanceID}&OBJECTTYPE={ObjectType} . For more information about the business object, see Business Objects.

Prerequisites


Page 55 of 82


1.1.8.1.3.1.1.1.2.20 Assign Absence to Incident Technical Data Techn ical N ame of the iView


00000053 WebDynpro Application: EHHSS_INC_ASSIGN_INC_ABSENCE (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to assign an absence that has been created for a person in Personnel Time Management (PT) to an incident during which this person was injured. This iView is called when report R_EHHSS_CHECK_HCM_ABS_CHANGED finds absences that have been c hanged in PT. In this iView, you can: Assign the absence to an incident that has already been recorded Create a new incident record to which you want to assign the absence Ignore the absence and cancel the incident assignment

Integration The relevant absence must be created for the injured person by a HR manager in the Personnel Time Management component. This iView is called v ia object-based navigation using the method AbsenceAssign of the business object BPR_INCIDENT using the parameter

Key={Key} . For more information about the business object, see Incident.

Prerequisites The following prerequisites must be met: You are assigned to the incident manager role. You have activated PT integration in Customizing for SAP EHS Management under

Incident Management

Integration


. You have executed report R_EHHSS_CHECK_HCM_ABS_CHANGED to find absences that have been changed in PT. For more information, see the report documentation.

More Information HR Integration for Absence Assignment

1.1.8.1.3.1.1.1.2.21 Display Person Details Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000038 Web Dynpro Application: EHFND_UI_COMN_PER_DETAIL (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND



You can use this iView to display details about a person, such as the gender, date of birth, and address, as well as that person’s communication details (telephone number, e-mail address, and so on). If an e-mail address has been entered, you can use the link to send an e-mail to the person. This iView is called via object-based navigation using the method DisplayPersonDetails of the business object BPR_FND_PD using the parameters

PARTY_ID={PARTY_ID} and EMAIL={EMAIL} .



Page 56 of 82

More Information Integration for Person Information

1.1.8.1.3.1.1.1.2.22 Display PM Notification Technical Data Techn ical N ame of the iView


00000254 Web Dynpro Application: EAMS_WDA_NTF_OIF ABAP/Web Dynpro



Support

EHS-MGM-FND-INT Availability as specified for the business package

Availability


Visibility

You can use this iView to display details about PM notifications. Details can include the following information: General data Location data Organization data Malfunction data Task data

Integration This iView is called via object-based navigation using the method Display of the business object eam_notification using the parameter

FRW_DATA_HANDLE={FRW_DATA_HANDLE}&QMNUM={QMNUM} .

1.1.8.1.3.1.1.1.3 Incident Reports Technical Data Technical Name

00000018

You can use this workset to display incident reports.


More Information For more information about incident reporting, see Incident Reporting.

1.1.8.1.3.1.1.1.3.1 Review Incident Summary Reports Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000019 Web Dynpro Application: POWL (Parameter: WDCONFIGURATIONID=EHHSS_IRT_ISR_POWL_UI_APPL) ABAP/Web Dynpro



Support

EHS-MGM-INC-REP


Availability as specified for the business package This iView is not visible in the Incident Manager role.

You can use this iView to display all of the summary reports that have been created. The report type and the file name is displayed, and you can use the links provided to display the relevant reports in a PDF format. You can also see the relevant plant, location, and organizational unit, as well as the report dates. You can also export the list of reports in a spreadsheet for further processing. You can use the links provided to change the current query or to define a new query.


Page 57 of 82

Integration From this iView you can create a summary report or display and generate a report.


Configuration You can personalize the iView by deleting and/or renaming queries, adding and removing queries to those that are available, or by changing the position of the active queries in the list. You can add a category to the queries or remove a category from them. You can specify whether a query is the default query and change the category description. You can also personalize the layout of the report summary, displaying it either as a tab strip or a link matrix. You can also choose whether or not to enhance the query text with category information.

More Information Incident Reporting

1.1.8.1.3.1.1.1.3.2 Change Parameters for Sending Reports Technical Data Techn ical N ame of the iView


00000063 Web Dynpro Application: EHHSS_INC_REP_CH_SEND_PARAMS (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-INC-REP Availability as specified for the business package

Availability

This iView is not visible in the Incident Manager role.

Visibility

You can use this iView to view and change the settings for sending a report. You can review the recipient, choose whether to send the report by fax or e-mail, and also change the recipient’s e-mail address and fax number.

Integration This iView is called via object-based navigation using the method ChangeReportSendingParams of the business object bpr_rpt_inc with parameter

Key={Key} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.3.3 Display/Edit Incident Summary Report Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation

00000020 Web Dynpro Application: EHHSS_RPT_OIF_V3 (Parameter: WDCONFIGURATIONID=EHHSS_INC_RPT_OIF_V3&sap-explanation=X)


ABAP/Web Dynpro



Support

EHS-MGM-INC-REP



You can use this iView to display and edit an incident summary report. You specify the dates for the report, any additional criteria that is required such as the plant ID and location, and also select which report you want to create. You can then use the relevant buttons to create the report, either in the foreground or in the background. You can also check the report and display any report generation messages that are created. You can also use this iView to display the component


Page 58 of 82

(report) name as a PDF file.

Integration This iView is called via object-based navigation using the method Display of the business object bpr_rpt_inc with the parameters KEY={Key} and

CHANGE_MODE={U} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.3.4 Create Incident Report Technical Data Techn ical N ame of the iView


00000020 Web Dynpro Application: EHHSS_RPT_OIF_V3 (Parameter: CHANGE_MODE=C&WDCONFIGURATIONID=EHHSS_INC_RPT_OIF_V3&sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to create an incident summary report. You specify the dates for the report, any additional criteria that is required such as the plant ID and location, and also select which report you want to create. You can then use the relevant buttons to create the report, either in the foreground or in the background. You can also check the report and display any report generation messages that are created. You can also use this iView to display the component (report) name as a PDF file.

Integration This iView is called via object-based navigation using the method create of the bus iness object bpr_rpt_inc . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.3.5 Change Incident Report Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000041 Web Dynpro Application: EHHSS_UI_REC_OIF_V3 (Parameter: CHANGE_MODE=U&sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-INC-REP



You can use this iView to change an existing incident report. You can change: Basic information about the report such as where and when it occurred The people who were involved in the incident (for example, witnesses, the reporting person, or vehicle driver) and their information, any injuries or illnesses, and treatment that they received as a result of the incident. Information about any assets that were involved in the incident. Information about any releases into the air, ground, or water as a result of the incident and cleanup responses to this. The estimated total expenses and income incurred by the incident. The risk matrix information of the areas affected by the incident, the severity, and the likelihood of them reoccurring. The investigation into the incident and its related documents and tasks. The report forms that are required for the reporting the incident to authorities. Details of any tasks that are related to the incident processing, such as the task schedule. You can also use this iView to check the contents of the record, change the group or regulations that apply to the incident, manage links, and set the status of the


Page 59 of 82

record.

Integration This iView is called via object-based navigation using the method ChangeReport of the business object BPR_INCIDENT with the key KEY={Key},

IS_REPORT={IS_REPORT} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.3.6 Generate Incident Report Technical Data Techn ical N ame of the iView


00000071 Web Dynpro Application: EHHSS_UI_REC_OIF_V3 (Parameter: CHANGE_MODE=U&sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to generate reports. Depending on which report you want to generate, you can specify: Report parameters such as the report language and country Sender information such as the sender ID and insurance number The recipient’s address You can then send the report to the recipient by fax or e-mail, or you can print out the report and ship it manually.

Integration This iView is called via object-based navigation using the method RegenerateReport of the business object BPR_INCIDENT with the parameters

KEY={Key} , IS_REPORT={IS_REPORT} and REGENERATE={regenerate} . For more information about the business object, see Business Objects.


1.1.8.1.3.1.1.1.4 Locations Technical Data Technical Name

00000008

You can use this workset to browse locations and set up all locations in the company.


More Information For more information ab out locations in SAP EHS Management , see Locations.

1.1.8.1.3.1.1.1.4.1 Explore Locations Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation

00000009 Web Dynpro: EHFND_UI_LOC_ENTRY (Parameter: WDCONFIGURATIONID=EHFND_UI_LOC_ENTRY&sapexplanation=X)


Page 60 of 82

ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

Visibility

This service is invisible in the navigation area.

You can use this iView to display the locations that exist in your system. The iView has four tabs: Recent Locations Displays the locations that were recently created. Structure View Displays either the location structure or the organizational structure. Search Enables you to search for a specific location and then to display information about it. Favorites Displays any locations that you added to your favorites.

Prerequisites You have created a location manually or you have imported technical objects from the Plant Maintenance component as locations. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

More Information Locations

1.1.8.1.3.1.1.1.4.2 Create Location Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000011 Web Dynpro Application: EHFND_UI_LOCATION_OIF (Parameter: CHANGE_MODE=C&sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

Visibility


You can use this iView to create organizational information about a location, for example, the plant or company code that the location is assigned to or the address of the location. You can use this iView to link the location to a technical object in the Plant Maintenance component, thereby avoiding the need to enter duplicate data. You can also remove the PM link if necessary. The iView also enables you to set the location’s status, to create a revision for the location that records any changes that were made to its attributes, or to delete a location. If the location is linked to a PM technical object, you also see the Partners tab.

Integration You can also use the iView to display the position of the location on a map in the side panel. If a technical object has been linked to the location, you can use the Equipment ID link to disp lay detailed information about that technical objec t from PM. This iView is called v ia object-based navigation using the method Create of the business object BPR_LOCATION_OBJECT . For more information about the business object, see Business Objects.

Prerequisites Locations exist in your sys tem. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

Configuration For more information about configuring the side panel to display a map, see Customizing for SAP EHS Management under Locations

Configure Integration of Map (EHFND_LO C_MAP)


.


Page 61 of 82

1.1.8.1.3.1.1.1.4.3 Manage Structure Technical Data Techn ical N ame of the iView


00000012 Web Dynpro Application: EHFND_UI_LHR_OIF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC Availability as specified for the business package

Availability


Visibility

You can use this iView to manage the location structure. You can insert a new location into the structure, or remove an existing one from it. You can also cut a location from its existing position in the structure and paste it into a new one. You can also use this iView to create a revision of a location.

Integration You can import technical objects from Plant Maintenance (PM) as locations into SAP EHS Management .


1.1.8.1.3.1.1.1.4.4 Import from PM Technical Data Techn ical N ame of the iView


00000013 Web Dynpro Application: EHFND_LOC_EAMIMP_GAF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

You can use this iView to import technical objects as locations from the Plant Maintenance c omponent into SAP E HS Management . The iView has five s teps: 1. You can search for the technic al objects that you want to import as locations. 2. You then selec t the technic al objects to be imp orted and as which typ e of location they should b e imported. You can ass ign a location type to all technical objects, or else you can assign s eparate location types to each technical object. 3. You can choose the position in the structure below which you want to imp ort the technical objec ts. 4. You can review your selection before you import the technical objec ts. 5. The sy stem confirms your changes.

Integration The iView displays data about the technical objects from Plant Maintenance. This iView is called via object-based navigation using the method ImportEAM of the business object BPR_LOCATION_OBJECT . For more information about the business object, see Business Objects.

Prerequisites Technical objects exist in Plant Maintenance. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

More Information Importing Locations from PM

1.1.8.1.3.1.1.1.4.5 Change Attributes Technical Data Techn ical N ame of the iView

00000014


Page 62 of 82


Web Dynpro Application: EHFND_LOC_BULKCHG_GAF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support


Availability

You can use the iView to update multiple location attributes in one operation, thereby saving time and administrative effort. You can make changes to a location and all of its subordinate locations, if you require. The iView has four steps. In the first step, you define which changes you want to make to multiple locations, and when you want to make them. In the second step, you select the locations that you want to change. In the third step you can review your changes before you make them, while the fourth step confirms your changes.

Integration The iView displays data about the technical objects from Plant Maintenance. This iView is called via object-based navigation using the method MassChange of the business object BPR_LOCATION_OBJECT . For more information about the business object, see Business Objects.

Prerequisites Locations exist in your system, either because you have created them manually or because you have imported them from Plant Maintenance. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

Example You know that three locations will be assigned to a different plant from tomorrow and want to change the assignment accordingly. You specify tomorrow’s date as the key date and select the new plant ID. In the second step in the iView, you select the locations (and their subordinate locations, if required) that should have the new plant ID. You then review your selection, the attributes are changed, and a confirmation message appears. From this iView, you can also follow the link to change additional attributes.


1.1.8.1.3.1.1.1.4.6 Display Location Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000015 Web Dynpro Application: EHFND_UI_LOCATION_OIF (Parameters: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

Visibility


You can use this iView to display organizational information about a location, for example, the plant or company code that the location is assigned to or the address of the location.

Integration If the location is linked to a PM technical object, you also see the Partners tab. You can also use the iView to display the position of the location on a map in the side panel. This iView is called via object-based navigation using the method Display of the business object BPR_LOCATION_OBJECT with parameter KEY={Key} .


More Information PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 63 of 82

For more information about configuring the side panel to display a map, see Customizing for SAP EHS Management under Locations



.

1.1.8.1.3.1.1.1.4.7 Edit Location Technical Data Techn ical N ame of the iView


00000077 Web Dynpro Application: EHFND_UI_LOCATION_OIF ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

Visibility


You can use this iView to edit organizational information about a location such as the plant or company code to which it is assigned or the address of the location. You can use this iView to link the location to a technical object in the Plant Maintenance (PM) component, thereby avoiding the need to enter duplicate data. You can also remove the PM link if necessary. The iView also enables you to change the location’s status, to create a revision for the location which records any changes that were made to its attributes, or to delete a location.

Integration If the location is linked to a PM technical object, you also see the Partners tab. You can also use the iView to display the position of the location on a map in the side panel. You can link a technical object in PM to the location using the Establish PM Link button and selecting the existing technical object you want to link to. When this operation is comp lete, you can use the Equipment ID link to display detailed information about that technic al object from PM. This iView is called via object-based navigation using the method Edit of the business object BPR_LOCATION_OBJECT with parameter KEY={Key} .


More Information For more information about configuring the side panel to display a map, see Customizing for SAP EHS Management under Locations



.

1.1.8.1.3.1.1.1.4.8 Display Location Structure Technical Data Techn ical N ame of the iView

Techn ical Name of the Appli cation Run time Techn ology

00000017 Web Dynpro Application: EHFND_UI_LHR_OIF (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

Visibility


You can use this iView to display the location structure. You can see the location name, its type, status and the technical name that is linked to it. You can also open the location to display more information. You can expand the locations to display their subordinate locations, if any exist.

Integration You can import technical objects from Plant Maintenance (PM) as locations into SAP EHS Management . This iView is called via object-based navigation using the method Display of the business object BPR_LOCATION_HRCHY . For more information about the business object, see Business Objects.

Prerequisites You have all authorizations required in the back-end system.


Page 64 of 82

You have a portal user that is assigned to a user with the required authorizations.


1.1.8.1.3.1.1.1.4.9 Edit Location Structure Technical Data Techn ical N ame of the iView


00000078 Web Dynpro Application: EHFND_UI_LHR_OIF (Parameter: sap-explanation=X&change_mode=U) ABAP/Web Dynpro



Support

EHS-MGM-FND-LOC

Visibility


You can use this iView to edit the location structure. You can insert a new location into the structure, or remove an existing one from it. You can also cut a location from its existing position in the structure and paste it into a new one. With this iView you can also create a revision of a location.

Integration You can import technical objects from Plant Maintenance (PM) as locations into SAP EHS Management . This iView is called via object-based navigation using the method Edit of the business object BPR_LOCATION_HRCHY . For more information about the business object, see Business Objects.



1.1.8.1.3.1.1.1.4.10 Display Where-Used List Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000052 Web Dynpro Application: EHFND_UI_COMN_WHERE_USED_LIST (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-FND



You can use this i View to display the other busi ness objects that use this location, for example, the incident is displayed in the where-used list if an it includes this location and you can navigate directly from there to the incident.

Integration This iView allows you to display detailed information about existing incidents that use the selected location. This iView is called v ia object-based navigation using the method display of the business object BPR_FND_UL using the parameters

OBJECT_ID={OBJECT_ID} and OBJECT_NAME={OBJECT_NAME} .



Page 65 of 82

1.1.8.1.3.1.1.1.5 Tasks Technical Data Technical Name

00000006

You can use this workset to display tasks .


1.1.8.1.3.1.1.1.5.1 Display HSS Tasks Technical Data Techn ical N ame of the iView


00000007 Web Dynpro Application: POWL (Parameters: WDCONFIGURATIONID=EHHSS_POWL_TASK_MGMT) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to query and display tasks of the HSS component. For more information, see Task Management.


Configuration You can personalize the iView by deleting or renaming queries, by adding and removing queries to those that are available, or by changing the position of the active queries in the list. You can add a category to the queries or remove a category from them. You can specify whether a query is the default query and change the category description.

1.1.8.1.3.1.1.1.5.2 Forward Task to Another Processor Technical Data Techn ical N ame of the iView Run time Techn ology

00000140 ABAP/Web Dynpro



Support

EHS-MGM-FND


Availability as specified for the business package The iView is not visible in the Tasks workset.

You can use this iView to forward a task to another processor.

Integration This iView is called vi a object-based navigation using the method ForwardTask of the bus iness object EH_FND_WFF_O BN using the parameter SO_GUID={SO_GUID}. For more information about the business object, see Business Objects.

Prerequisites A task has b een created and assigned to your user.

1.1.8.1.3.1.1.1.5.3 Process Details PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 66 of 82



00000040 Web Dynpro Application: EHFND_WFF_PROGRESS_LOG (Parameter: sapexplanation=X&change_mode=U) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this iView to display the progress log for a process. You can see when each process was sent, its status, and who or what performed the processing. You can also view any comments or attachments for the process step. This iView also enables you to create a print version of the result list as a PDF document or to export the list in a spreadsheet format.

Integration From this iView, you can display technical information about the task, and also display the workflow log view showing technical details or a graphical workflow log. This iView is called v ia object-based navigation using the method OpenProgressLog of the bus iness object EH_FND_WFF_OBN using the parameter

WORKITEM_ID={WORKITEM_ID} . For more information about the business object, see Business Objects.


1.1.8.1.3.4.1.1.1 Processes Technical Data Technical Name

00000082

You can use this workset to monitor the processes in your company.


More Information For more information about processes in SAP EHS Management , see Process Foundation (EHS-MGM-FND-WF).

1.1.8.1.3.4.1.1.1.11 EHS Management Task (Technical Information) Technical Data Techn ical N ame of the iView

00000094


Remote IAC iView on ITS


Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_WI_INF

Support Availability


You can use this i View to display information about a sp ecific task and the corresponding process instance, if ap plicab le. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenWorkitemInfo of the business object EH_FND_WFF_OBN using the parameter

p_wiid={ID} . For more information about the business object, see Business Objects.


Page 67 of 82


1.1.8.1.3.4.1.1.1.10 Graphical Workflow Log Technical Data Techn ical N ame of the iView

00000093




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_GRAPH_WFLG EHS-MGM-FND

Support


Availability

You can use this iView to open the graphical workflow log for a given workflow instance or task ID. The iView displays the progress of a workflow instance. You can see the original workflow template and an overlay of the actual route that the workflow took. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenGraphicalWorkflowLog of the business object EH_FND_WFF_OBN using the parameter p_wiid={ID} . For more information about the business object, see Business Objects.


1.1.8.1.3.4.1.1.1.9 Technical Workflow Log Technical Data Techn ical N ame of the iView

00000092




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_TECH_WFLOG EHS-MGM-FND

Support


Availability

You can use this iView to display the technical workflow log for a given task ID. The technical workflow log displays technical information about a workflow instance. The only parameter you can select is the task ID. This ID can either be the ID of a workflow instance, or the ID of a task. If the ID of a task is passed, the iView displays the corresponding workflow instance. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenTechnicalWorkflowLog of the business object EH_FND_WFF_OBN using the parameter p_wiid={ID} . For more information about the business object, see Business Objects.


1.1.8.1.3.4.1.1.1.12 Open Comment Technical Data Techn ical N ame of the iView Run time Techn ology Data S ource or Da ta Store

00000153 ABAP/Web Dynpro Data source as specified for the business package


Page 68 of 82

EHS-MGM-FND

Support


Availability

You can use this iView to display the comment.

Integration This iView is called via object-based navigation using the method OpenComment of the business object EH_FND_WFF_OBN. For more information about the business object, see Business Objects.

1.1.8.1.3.2 Incident Reporter Role: com.sap.pct.eh.role.IncidentReporter

The Incident Reporter role is assig ned to the person who initially rep orts an incident. This can be any p erson with access to the SAP NetWeaver Portal or SAP NetWeaver Business Client , regardless of their role, position, or task within an organization. For example: An internal employee An external contractor A vendor A customer This person is not expected to use the solution on a regular basis. The incident reporter enters the basic information about an incident in a guided activity in the SAP NetWeaver Business Client or SAP Enterprise Portal , or in a form. The level of detail can vary depending on the incident reporter's position in the company, their level of experience, and the company business process. The incident reporter mainly enters the information as free text. To give additional information on certain aspects of an incident, the incident reporter can add attachments such as photographs, forms, or protocols. For more information about the individual tasks, see the workset descriptions in this documentation.

Integration When the incident reporting process is completed, the data is sent to the incident manager to be further edited and structured.


00000002



00000003


00000022




1.1.8.1.3.2.1.1.1.1 Workset Map PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 69 of 82


com.sap.pct.eh.iview.txTDAGCPW00 ABAP/Web Dynpro


SAP ERP

Support

EHS, EHS-MGM Availability as specified in the business package

Availability

You can use this i View to display the workset map.


1.1.8.1.3.2.1.1.1.2 Report Incident (Simplified) Technical Data Techn ical N ame of the iView


00000046 Web Dynpro Application: EHHSS_INC_REC_QAF (Parameters: sap-explanation=X) ABAP/Web Dynpro



Support


Availability

You can use this iView to record initial information about an incident that occurred in your organization, for example: A descrip tion of the incident People who were injured during the incident People who witnessed the incident The initial incident information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.

Integration To record more detailed initial information about an incident, you can use the Report Incident iView. The incident record can be reviewed and completed by an authorized user in the Review and Completion of Incident Records step. This iView is called v ia object-based navigation using the method CreateSimple of the business object BPR_INCIDENT . For more information about the business object, see Incident.



1.1.8.1.3.2.1.1.1.3 Report Incident Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000045 Web Dynpro Application: EHHSS_INC_REC_GAF_V3 (Parameters: CHANGE_MODE=C&sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-INC

Availability


You can use this iView to record initial information about an incident in your organization, for example: A descrip tion of the incident


Page 70 of 82

Injured people Witnesses Releases Involved assets The initial incident information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.

Integration To record less detailed initial information about an incident, you can use the Report Incident (Simplified) iView. The incident record can be reviewed and completed by an authorized user in the Review and Completion of Incident Records step. This iView is called v ia object-based navigation using the method create of the business object BPR_INCIDENT . For more information about the business object, see Incident.

Prerequisites Depending on the information you want to record, you have made the relevant settings in Customizing for SAP EHS Management under Management

Incident Recording

Incident

.



1.1.8.1.3.2.1.1.1.4 Report Near Miss Technical Data Techn ical N ame of the iView


00000044 Web Dynpro Application: EHHSS_INC_REC_NRM_QAF_V3 (Parameters: CHANGE_MODE=C&sapexplanation=X)


ABAP/Web Dynpro



Support


Availability

You can use this iView to record initial information about a near miss that occurred in your organization, for example: A descrip tion of the near miss People who were nearly injured during the near miss The circumstances of the near miss The initial near miss information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.


Prerequisites You have specified the relevant near miss groups in Customizing for SAP EHS Management under Information

Specify Near Miss Groups

Incident Management

Incident Recording

Basic

.



Incident Management

Incident Recording

Basic

:


More Information


Page 71 of 82

Incident Recording

1.1.8.1.3.2.1.1.1.5 Report Safety Observation Technical Data Techn ical N ame of the iView


00000043 Web Dynpro Application: EHHSS_INC_REC_SFO_QAF_V3 (Parameter: CHANGE_MODE=C&sapexplanation=X) ABAP/Web Dynpro



Support


Availability

You can use this iView to record initial information about a safety observation in your organization, for example: A descrip tion of the safety observation The people who were observed The circumstances of the safety observation The initial safety observation information is stored in an incident record which can be reviewed and completed by an authorized user in a follow-up process.


Prerequisites You have specified the relevant safety observation groups in Customizing for SAP EHS Management under Basic Information

Specify Safety Ob servation Groups

Incident Management

Incident Recording

.



Incident Management

Incident Recording

Basic

:



1.1.8.1.3.3 Notification Recipient Role: com.sap.pct.eh.roles.IncidentNotified

The Notification Recipient role is assigned to the person who is informed if an incident results in a fatality. This person does not have to be involved in the normal incident management process, but they must be informed if a fatality occurs, for example, the CEO. This person is not expected to use the solution on a regular basis. For more information about the individual tasks, see the workset descriptions in this documentation.


00000002


1.1.8.1.3.5.1.1 Overview Technical Data


Page 72 of 82

Technical Name

00000003

1.1.8.1.3.5.1.1.1 Work Overview Technical Data Technical Name

00000047

You use this workset to display your tasks.


More Information For more information, s ee Process Foundation (EHS-MGM-FND-WF).

1.1.8.1.3.3.1.1.1.1 Inbox Technical Data Techn ical N ame of the iView


00000048 Web Dynpro Application: IBO_WDA_INBOX (Parameter: WDCONFIGURATIONID=EHHSS_WDAC_POWL_INBOX) ABAP/Web Dynpro



Support

EHS-MGM-FND Availability as specified in the business package

Availability


Visibility

You can use this iView to display the tasks that are assigned to you in an inbox. The inbox displays the task subject, when the task was s ent, and its priority. You can also see the date by which the task must be completed, the status of the task, who forwarded it to you, and a preview of the task. In the preview, you can provide additional notes and add attachments to the task preview. When you choose the task link in your inbox, the system displays the corresponding data record or a screen where you can perform the task. If you want to see the related incident record associated with the task, you can select the task row and choose Display Inc.. From this iView you can also specify that you are not responsible for the work, resubmit it, or end the resubmission. You can forward the work to someone else, or assign it to yourself if it is already assigned to another processor. You can also maintain a substitute who will take over your work in the event of planned or unexpected absences and you can create and activate a rule that assigns tasks to a spec ified assignee. This iView disp lays the tasks in the inbox according to a sp ecified query. You can define and change queries in this iView. You can export the list of tasks in a spreadsheet format.


Configuration If you want to replace the inbox with the universal worklist (UWL), you must create a customer-specific SAP NetWeaver Portal role that includes this iView. To do this, perform the following steps: 1. Copy the role. 2. Include the Universal Worklist iView in the copied role next to the Inbox iView. 3. Delete the Inbox iView from the copied role. 4. To include the standard Services iView, choose Edit for the iView and select Dynamic Navigation in the Disp lay selection box. Then, add the iView to dynamic navigation. 5. Configure the Univers al Worklist iView as the default entry for the folder and to be inv isi ble in navi gation areas 6. Set the parameters s pec ific to the universal worklis t, for exampl e, View , to have the same values as in the configuration XML file. For more information about configuring the UWL, see Universal Worklist Configuration.


00000022


Page 73 of 82




1.1.8.1.3.3.1.1.2.1 Execute Process Decision Technical Data Techn ical N ame of the iView


00000035 Web Dynpro Application: EHFND_WFF_DECISION (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support


Availability


Visibility

You can use this i View to make a decision, for example, to approve that an action has b een completed. You acces s this iView by selecting the link in the Category column of a decision task in the Edit Incident iView. After you have made the decision in this iView, the system triggers the next step in the process and displays the Edit Incident iView again. This way, y ou can make decisions directly in an inci dent data record. Alternatively, you can access the decision task in your inbox (Inbox iView).

Integration This iView is called via object-based navigation using the method OpenProgressLog of the business object EH_FND_WFF_OBN using the method

OpenProcessDecision and parameter ID={ID} . For more information about the business object, see Business Objects.

Prerequisites The decision step of the process is assigned to you. If you are not the processor, the link in the Category column is inactive. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.3.1.1.2.2 Display Incident Technical Data Techn ical N ame of the iView Techn ical Name of the Appli cation Run time Techn ology

00000034 Web Dynpro Application: EHHSS_INC_REC_OIF_V3 (Parameter: sap-explanation=X) ABAP/Web Dynpro



Support

EHS-MGM-INC



You can use this iView to display incident records. For example, the incident record can contain the following information: A descrip tion of the incident Injured people Witnesses Releases Involved assets Investigation details Risk matrix information Financial information Forms, supporting documents, and associated actions and notifications. For more information, s ee Review and Completion of Incident Records.


Page 74 of 82

Integration This iView is called via object-based navigation using the method Display of the business object BPR_INCIDENT using the parameter KEY={Key} . For more information about the business object, see Business Objects.


1.1.8.1.3.4 Process Administrator Role: com.sap.pct.eh.roles.EHSMAdmin

The Process Administrator role is assigned to an employee in the IT department. This person is responsible for monitoring the SAP EHS Management processes and ensuring that the processes are running properly. If issues occur, the process administrator has to determine the root cause and correct the issue. The process administrator is responsible for the following: Making s ettings in the SAP Business Workflow system Setting up jobs and workflows For more information about the individual tasks, see the workset descriptions in this documentation.

Integration The process administrator works closely with the person who is organizationally responsible for a process. The implementor of a task may also contact the process administrator if there are technical problems with a process.



00000002



00000003

1.1.8.1.3.4.1.1.1 Processes Technical Data Technical Name

00000082

You can use this workset to monitor the processes in your company.


More Information For more information about processes in SAP EHS Management , see Process Foundation (EHS-MGM-FND-WF).

1.1.8.1.3.4.1.1.1.1 Display Process Definitions Technical Data


Page 75 of 82


00000087




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_PRCDEF_LST EHS-MGM-FND

Support


Availability

The iView is not visible in the Process Administrator role.

Visibility

You can use this i View to display a list of available process definitions in the SAP EHS Management component. The system displays the process definitions as a list. From the list, you can do the following: Disp lay a list of process instances for the process definition. Display detailed information about the process definition. Use a report to chec k the process definition for its validity and c onsistency . You do this by choosing the Status traffic light icon in the report. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenProcessDefList of the bus iness object EH_FND_WFF_OBN . For more information about the business object, see Business Objects.

Prerequisites You have specified process definitions in Customizing for SAP E HS Management in the Specify Process Definitions activity (table EHFNDC_PROCDEF ). You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.2 Check Workflow System Technical Data Techn ical N ame of the iView

00000083




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_SYSTEM_CHK EHS-MGM-FND

Support


Availability

You can use this iView to run checks on the system for SAP EHS Management . You can use this iView to find problems in the processes based on the process foundation. The system performs the following checks: Check whether the workflow runtime environment is set up correctly. Check whether all required tasks in transaction SWU3 ( Automatic Workflow Customizing ) are completed. Check whether the collector report for the process foundation statistics is scheduled. Check whether the process definitions in the Customizing activity Specify Process Definitions are maintained. A transaction in the back-end sys tem is called when you acces s this iView.

Prerequisites You have made the settings in the Perform Automatic Workflow Customizing activity in Customizing for SAP EHS Management . You have made the settings in the Specify Process Definitions Customizing activity in Customizing for SAP EHS Management . You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.3 Check Process Definition Technical Data Techn ical N ame of the iView

00000085




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_PRCDEF_CHK

Support Availability



Page 76 of 82


Visibility

You can use this iView to perform checks on a process definition and to display the results. This iView helps a system administrator to detect problems within the processes in the SAP EHS Management component. The system checks the process definition for the following: Check that the process definition entry in the table is consistent. Check that PCO class exists, and is valid for implementing the PCO interface and providing a PCBO key. Check that PCBO exists, is c onsistent, and can be ins tantiated. Check that associated workflow templates exist and have been linked to an event. Check that the Start Processing and End Processing steps exis t in the workflow template. Check that the user has performed these steps and whether there are possible agents for these steps. The iView displays any errors that occurred and any data inconsistencies.

Integration This iView is called via object-based navigation using the method OpenProcessDefCheck of the business object EH_FND_WFF_OBN using the parameters

p_ehsmc={EHSManagementComp} , p_purpo={Purpose} , and p_varia={ProcessVariant} . For more information about the business object, see Business Objects.

Prerequisites You have specified process definitions in Customizing for SAP E HS Management in the Specify Process Definitions activity (table EHFNDC_PROCDEF ). You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.4 Display Technical Details for Process Definition Technical Data Techn ical N ame of the iView

00000086




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_PRCDEF_INF EHS-MGM-FND

Support


Availability


Visibility

You can use this iView to display information about a process definition in the SAP EHS Management component. The iView provides the following information: The process definition key Information about the associated PCO class Information about the associated PCBO (such as keys and the table of the ROOT node) Information about ass ociated workflow templates A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenProcessDefInfo of the bus iness object EH_FND_WFF_OBN using the parameters

p_ehsmc={EHSManagementComp} , p_purpo={Purpose} , and p_varia={ProcessVariant} . For more information about the business object, see Business Objects.

Prerequisites You have maintained the process definition in table EHFNDC_PROCDEF . You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.5 Check Process Instance Technical Data Techn ical N ame of the iView

00000088


Page 77 of 82




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_PROCS_CHK EHS-MGM-FND

Support


Availability


Visibility

You can use this iView to perform various checks on a process instance and to display the results. It helps you to detect any problems within SAP EHS Management processes. The iView checks the following parts of a process definition: Availability of the PCBO instance Associated process definition Associated business object instance Data business object instance Parent PCBO instance Availability of the associated workflow instance Status of the workflow instance Associated PCO Check the current/last step of the workflow instance This iView checks the process instance and displays any errors and problems that have occurred. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called v ia object-based navigation using the method OpenProcessInstCheck of the business object EH_FND_WFF_OBN using the parameter p_pcbok={Key} . For more information about the business object, see Business Objects.

Prerequisites The process instance to be c hecked must be a process based on a PCBO. The PCBO instance must exis t. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.6 Display Technical Details for Process Instance Technical Data Techn ical N ame of the iView

00000089




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_PROCS_INF

Support Availability Visibility

EHS-MGM-FND Availability as specified for the business package The iView is not visible in the Process Administrator role.

You can use this iView to display technical information about an SAP EHS Management process instance. The iView provides information about the following parts of a process instance: Information stored in the PCBO itself (such as the process definition and the creation date) Associated business object PCO class PCBO Workflow template Workflow instance Workflow progress A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenProcessInstInfo of the business object EH_FND_WFF_OBN using the parameter

p_pcbok={Key} . For more information about the business object, see Business Objects.



Page 78 of 82

You have a portal user that is assigned to a user with the required authorizations. The process instance is based on a PCBO.

1.1.8.1.3.4.1.1.1.7 Display Process Instances Technical Data Techn ical N ame of the iView

00000090




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_PROCS_LST EHS-MGM-FND

Support


Availability


Visibility

You can use this iView to display the instances of a process configured for the SAP EHS Management component. The sys tem displays the process instances that are based on a PCBO. From this list, you can display additional information about the selected process instance. To display additional information about the process instance, proceed as follows: Choose the Info i con to disp lay technic al information about the selected proces s instanc e in the report. Choose the Log icon to disp lay the technical workflow log for the selec ted process ins tance in the report. Choose the Grap h icon to disp lay the graphic al workflow log for the selected proces s instanc e in the report. Choose the Check icon to run checks on the selected process ins tance in the report. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called v ia object-based navigation using the method OpenProcessInstList of the bus iness object EH_FND_WFF_OBN using the parameter p_ehsmc={EHSManagementComp} , p_purpo={Purpose} , and p_varia={ProcessVariant} . For more information about the business object, see Business Objects.

Prerequisites You have specified process definitions in Customizing for SAP E HS Management in the Specify Process Definition activity. You have all authorizations required in the back-end system. You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.8 Technical Workflow Inbox Technical Data Techn ical N ame of the iView

00000091




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_TECH_WFIBO

Support Availability Visibility

EHS-MGM-FND Availability as specified for the business package The iView is not visible in the Process Administrator role.

You can use this iView to display a user's tasks. You can also display additional information for a selected task. You select the user inbox that you want to display by entering that user ID in the selection screen. To display additional information about the task, proceed as follows: 1. Choose the Info i con to disp lay additional information about the selected task. 2. Choose the Log icon to disp lay the technical workflow log for the selec ted task . 3. Choose the Grap h icon to disp lay the graphic al workflow log for the selec ted task . A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenTechWfInbox of the business object EH_FND_WFF_OBN using the parameter

p_uname={UserName} . For more information about the business object, see Business Objects.



Page 79 of 82

You have a portal user that is assigned to a user with the required authorizations.

1.1.8.1.3.4.1.1.1.9 Technical Workflow Log Technical Data Techn ical N ame of the iView

00000092




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_TECH_WFLOG EHS-MGM-FND

Support


Availability

You can use this iView to display the technical workflow log for a given task ID. The technical workflow log displays technical information about a workflow instance. The only parameter you can select is the task ID. This ID can either be the ID of a workflow instance, or the ID of a task. If the ID of a task is passed, the iView displays the corresponding workflow instance. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenTechnicalWorkflowLog of the business object EH_FND_WFF_OBN using the parameter p_wiid={ID} . For more information about the business object, see Business Objects.


1.1.8.1.3.4.1.1.1.10 Graphical Workflow Log Technical Data Techn ical N ame of the iView

00000093




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_GRAPH_WFLG EHS-MGM-FND

Support


Availability

You can use this iView to open the graphical workflow log for a given workflow instance or task ID. The iView displays the progress of a workflow instance. You can see the original workflow template and an overlay of the actual route that the workflow took. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenGraphicalWorkflowLog of the business object EH_FND_WFF_OBN using the parameter p_wiid={ID} . For more information about the business object, see Business Objects.


1.1.8.1.3.4.1.1.1.11 EHS Management Task (Technical Information) Technical Data Techn ical N ame of the iView

00000094




Component Extension 1.0 for SAP EHS Management Transaction: EHFND_WFF_WI_INF

Support

EHS-MGM-FND


Page 80 of 82


Availability

You can use this i View to display information about a sp ecific task and the corresponding process instance, if ap plicab le. A transaction in the back-end sys tem is called when you acces s this iView.

Integration This iView is called via object-based navigation using the method OpenWorkitemInfo of the business object EH_FND_WFF_OBN using the parameter

p_wiid={ID} . For more information about the business object, see Business Objects.


1.1.8.1.3.4.1.1.1.12 Open Comment Technical Data Techn ical N ame of the iView

00000153 ABAP/Web Dynpro



Support


Availability

You can use this iView to display the comment.

Integration This iView is called via object-based navigation using the method OpenComment of the business object EH_FND_WFF_OBN. For more information about the business object, see Business Objects.

1.1.8.1.3.5 Environmental Manager Role: com.sap.pct.eh.role.EnvManager

The Environmental Manager role is assigned to employees who are resp onsibl e for ensuring the organization is compliant with environmental regulations and standards. The environmental manager is responsible for ass essing envi ronmental asp ects and impacts , imp lementing risk treatment programs for environmental risks, monitoring environmental performance , and investigating any incident that involves releases into the environment. To ensure compliance with environmental regulations and standards, the environmental manager communicates with employees and performs training courses with regards to potential environmental impacts. For more information about the individual tasks, see the workset descriptions in this documentation.

Integration This role is integrated in the following scenario: Asses sing environmental risks



00000002


1.1.8.1.3.5.1.1 Overview PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 81 of 82

sap ehsm

Recommend Documents