SAP_Extended_ECM_Solution_Accelerator_for_SAP_EHSM-2

Prévia do material em texto

SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 1 
 
 
 
SAP Extended ECM Solution Accelerator February 2016 
 
Implementing Extended ECM in 
SAP Environment, Health and 
Safety Management (EHSM) 
A sample configuration for Extended ECM for SAP Solutions 
 
 
 
 
 
2.1 
 
 
 
 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 2 
 
 
 
 
Solution Accelerator Disclaimer 
The purpose of a solution accelerator is to give you an example for an implementation. This particular 
solution accelerator relates to OpenText Extended ECM for SAP® Solutions in a specific business 
context. A solution accelerator in most cases consists of documentation and software. A solution 
accelerator is not part of a product and is not covered by product maintenance and support. 
Please be appreciative that OpenText Customer Support is unable to answer questions related to solution 
accelerators. 
 
DISCLAIMER OF WARRANTIES: 
THE EXTENDED ECM SOLUTION ACCELERATOR (SOFTWARE AND DOCUMENTATION) IS 
PROVIDED “AS IS”, AND OPEN TEXT MAKES NO (AND HEREBY DISCLAIMS) ALL WARRANTIES, 
REPRESENTATIONS, OR CONDITIONS, WHETHER WRITTEN, ORAL, EXPRESS, IMPLIED OR 
STATUTORY, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE, AGAINST 
INFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE USE, 
MISUSE, OR INABILITY TO USE THE EXTENDED ECM SOLUTION ACCELERATOR (IN WHOLE OR 
IN PART). OPEN TEXT DOES NOT WARRANT THAT ANY DEFECTS OR ERRORS WILL BE 
REPAIRED OR THAT ALL DEFECTS OR ERRORS CAN BE CORRECTED, OR THAT OPERATION OF 
THE SOLUTION ACCELERATOR IMPLEMENTATION SHALL BE UNINTERRUPTED, DEFECT OR 
ERROR-FREE. 
Open Text Corporation is the owner of the trademarks Open Text, The Content Experts, and Open Text 
ECM Suite (this list is not exhaustive). All other products or company names are used for identification 
purposes only, and are trademarks of their respective owners. All rights reserved. 
 
© Copyright 2016 Open Text. All Rights Reserved. 
 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 3 
 
Summary 
You can enhance your SAP ECC system with OpenText Extended ECM for SAP Solutions® (“Extended 
ECM”) functionality with which you maintain and access unstructured content items and documents 
related to your main EHSM objects in a business workspace on OpenText Content Server. This provides 
you with state-of-the art document management, collaboration and records management capabilities 
which are tightly integrated into SAP EHSM while providing enterprise access to your content via 
productivity tools like Microsoft Windows® and Microsoft Office®. 
The SAP EHSM Solution Accelerator covers one of many possible implementations that use business 
workspaces to manage documents in SAP EHSM; other implementations are possible. 
OpenText continuously improves the Extended ECM solution accelerators. We are very much interested 
in your feedback. Please use the OTDN forum linked to each solution accelerator to give us your 
feedback. 
System Prerequisites 
The following products and components are the basis for this scenario: 
EHSM Classic: 
SAP ERP 6.00 
To display Specifications (BUS1077) in Content Server, you need SAP ERP 6.00 EhP3 (SAP 
Component EA-APPL with SP5). 
EHSM Extension: 
SAP EHS Management Extension 3.0 with SP3 
Extended ECM: 
 SAP Extended ECM 10.0.3 with all its prerequisites 
The most recent solution accelerator transport package that is available on the OpenText 
Knowledge Center at https://knowledge.opentext.com/knowledge/cs.dll/Open/41496620 
 SAP Extended ECM 10.5 SP1 with all its prerequisites 
The most recent solution accelerator transport package that is available on the OpenText 
Knowledge Center at https://knowledge.opentext.com/knowledge/cs.dll/Open/41496620. 
The required additional files for the 10.5 SP1 support are available at 
https://knowledge.opentext.com/knowledge/cs.dll/Open/62014533 
For the prerequisites of Product Safety, see 7.2 Prerequisites on page 59. 
Solution Accelerator Content 
SAP transport 
Content Server category export 
This documentation 
https://knowledge.opentext.com/knowledge/cs.dll/Open/41496620
https://knowledge.opentext.com/knowledge/cs.dll/Open/41496620
https://knowledge.opentext.com/knowledge/cs.dll/Open/62014533
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 4 
 
Package structure 
/OTX/RMEHSM Topmost package containing all EHSM related 
packages 
/OTX/RMEHSM_CLASSIC For Classic EHS. This package is needed only for 
Specification and Waste Management. Installation 
is not necessary for the EHSM extension 
component. 
/OTX/RMEHSM_EXTENSION For the EHSM Extension component. This 
package is needed for Incident Management. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 5 
 
Contents 
 
Summary ...................................................................................................................................................... 3 
System Prerequisites ............................................................................................................................... 3 
Solution Accelerator Content ................................................................................................................... 3 
Package structure .................................................................................................................................... 4 
1 Overview of SAP Environment, Health and Safety Management (SAP EHSM) ............................... 7 
1.1 Specification management ............................................................................................................... 8 
1.2 Incident management ....................................................................................................................... 8 
1.3 Waste management ......................................................................................................................... 9 
1.4 Product Safety ................................................................................................................................ 10 
2 Solution description ............................................................................................................................ 11 
3 New in EHSM Solution Accelerator 2.0 .............................................................................................. 13 
3.1 Specification ................................................................................................................................... 13 
3.2 Incident ........................................................................................................................................... 13 
3.3 Waste Management ....................................................................................................................... 15 
3.4 Additional Icons .............................................................................................................................. 17 
3.5 Product Safety ................................................................................................................................ 17 
4 Customizing Specification .................................................................................................................. 18 
4.1 Overview......................................................................................................................................... 18 
4.2 UI integration .................................................................................................................................. 19 
4.3 Business object declaration........................................................................................................... 20 
4.4 Workspace type in Content Server ................................................................................................ 21 
Icons for business workspaces ...................................................................................................... 21 
4.5 Category and attributes .................................................................................................................. 22 
4.6 Business relationships .................................................................................................................... 22 
4.7 Receiver module events ................................................................................................................. 22 
4.8 Event triggering .............................................................................................................................. 24 
4.9 Testing ............................................................................................................................................ 26 
5 Customizing Incident ........................................................................................................................... 28 
5.1 Overview......................................................................................................................................... 28 
5.2 UI integration .................................................................................................................................. 29 
5.3 Business object declaration ........................................................................................................... 33 
5.4 Workspace type in Content Server ................................................................................................ 34 
Icons for business workspaces ...................................................................................................... 34 
5.5 Category sets and attributes .......................................................................................................... 34 
5.6 Business relationships .................................................................................................................... 36 
5.7 Displaying an SAP business object from Content Server .............................................................. 36 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 6 
 
5.8 Receiver module events ................................................................................................................. 37 
5.9 Event triggering .............................................................................................................................. 40 
5.10 Testing ............................................................................................................................................ 40 
6 Customizing Waste management ....................................................................................................... 44 
6.1 Overview: Waste management ...................................................................................................... 44 
6.2 UI integration .................................................................................................................................. 45 
6.3 Business object declaration ........................................................................................................... 46 
6.4 Workspace type in Content Server ................................................................................................ 48 
Icons for business workspaces ...................................................................................................... 49 
6.5 Category sets and attributes .......................................................................................................... 50 
6.6 Business relationships .................................................................................................................... 50 
6.7 Receiver module events ................................................................................................................. 51 
6.8 Event triggering .............................................................................................................................. 53 
6.9 Testing ............................................................................................................................................ 53 
7 Customizing Product Safety ............................................................................................................... 59 
7.1 Overview......................................................................................................................................... 59 
7.2 Prerequisites for Product Safety .................................................................................................... 59 
7.3 Reports in Product Safety .............................................................................................................. 60 
7.3.1 SOP and MSDS reports .................................................................................................... 60 
7.3.2 Inbound reports ................................................................................................................. 65 
7.4 Exporting raw reports to business workspaces .............................................................................. 67 
7.4.3 Exporting a raw report manually ........................................................................................ 67 
7.4.4 Exporting raw reports automatically .................................................................................. 72 
7.5 Exporting final reports to business workspaces ............................................................................. 74 
7.5.5 Exporting final reports manually ........................................................................................ 74 
7.5.6 Exporting final reports automatically ................................................................................. 80 
7.5.7 Debugging shipping of a final report.................................................................................. 85 
8 About OpenText ................................................................................................................................... 87 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 7 
 
1 Overview of SAP Environment, Health 
and Safety Management (SAP EHSM) 
With the SAP EHSM solution, you can integrate environment, health, and safety (EH&S) compliance 
functions into global business processes. This helps you address EH&S needs proactively, respond to 
unplanned events, reduce risk, and improve performance. 
SAP EHSM supports you in ensuring compliance with regulations for product safety, hazardous 
substances, dangerous goods, and waste management: 
 Hazardous Substance Management 
 Industrial Hygiene 
 Product Safety and Stewardship (Managing product compliance) 
 Incident Management 
 Occupational Health 
 
As SAP EHSM also integrates into key applications such as Plant Maintenance and Manufacturing 
execution systems, all of your compliance related business processes are aligned, auditable, and 
transparent. This enables automated reporting, early identification of deviations, and comprehensive site 
data reporting for enterprise planning and risk management. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 8 
 
 
1.1 Specification management 
Specification management is a basic component that is required for several areas of the SAP EHSM 
component. With the Specification management component, you create specificationsfor EH&S objects 
such as substances, agents, dangerous goods classifications, waste codes, and packaging, and assign 
characteristics to these objects using identifiers. For each specification you enter structured data and text 
information, for example, in the form of phrases. You can find information about Risk and Safety Phrases, 
material safety data sheet requirements, or physical attributes. The SAP system offers you a selection of 
typical properties, known as value assignment types, in a property tree. 
You can assign any number of materials to a specification, thus creating a link to other logistic processes. 
1.2 Incident management 
You use the Incident component in NetWeaver Business Client to initially record and then review and 
complete incidents, safety observations, and near misses to fulfill your environment, health, and safety 
requirements on a regional and global scale. This solution provides various methods for recording the 
data to accommodate online and offline situations as well as skilled and unskilled users. After initial 
recording, you can collect additional information from the people involved, investigate why an incident 
occurred, and track the financial impact on the organization and its assets. You can also assess risk, 
report data internally or externally to fulfill legal, regulatory, and company reporting responsibilities, and 
analyze aggregated incident data. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 9 
 
 
Figure 1-1: Incident management overview 
1.3 Waste management 
In enterprises of all kinds, substances and objects accumulate that can no longer be used in the 
production process and that must be disposed of as waste. Disposal in this sense means either the 
recycling (recovery) or the disposal (dumping) of waste. Laws and regulations regulate disposal and must 
be complied with by enterprises. Moreover, the disposal processes tie up resources (personnel, storage, 
containers, vehicles, and so on) and costs arise for the actual disposal of waste that depend on the 
quantity and level of risk of the waste and on the situation on the disposal market. 
The SAP Waste Management transaction supports you in handling waste disposal processes, complying 
with national and international regulations and laws that are relevant for generation, transport, and 
disposal, and distributing costs proportionally among the departments within the enterprise that generated 
the waste. 
Main waste management pillars: 
Master Data 
Management 
Disposal Processing Disposal Document 
Management 
Reporting 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 10 
 
Maintain data for 
 Waste Generator 
 Waste Disposer 
 Waste 
Transporter 
 Authority 
 Enter waste 
quantities 
 Trigger 
purchase 
orders for 
disposal 
 Post waste 
directly to 
inventory 
management 
 Create, print 
and manage 
disposal 
documents 
 Create various 
reports, such as 
waste life-cycle 
analyses 
1.4 Product Safety 
The Product Safety area covers processes around product safety reporting. This includes creating 
maintaining chemical, physical, safety reports and other data for the substances that are used and 
processed in the EHS Management specification database. 
When the product is available and all of its data is maintained correctly, this data is used to create 
Material Safety Data Sheets (SDSs or MSDSs). These data sheet are managed in the EHS Management 
report information system. They can also be saved in a business workspace. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 11 
 
2 Solution description 
The SAP EHSM Solution Accelerator uses OpenText Content Server workspace technology to define a 
container for each EHSM business object of interest. You can leverage Content Server features to 
provide a rich and effective content management. 
This solution accelerator provides solutions for the following EHSM areas and business objects: 
 
Module Business object 
Specification Management Specification BUS1077 
Incident Management Incident /OTX/RMINC 
Waste management Waste Generator /OTX/RMWAG 
 Waste Distributor /OTX/RMWAD 
 Waste Transporter /OTX/RMWAT 
 Waste Authority /OTX/RMWAA 
 
SAP offers two components for EHS management: 
EHS component Description Business 
Objects 
Package 
EHSM Classic 
 
Is part of SAP ERP Specification 
Waste 
Management 
/OTX/RMEHSM_CLASSIC 
Component extension for 
SAP EHS Management 
Is part of the SAP 
Business Suite as an 
ABAP Add-on 
Incident 
Management 
/OTX/RMEHSM_EXTENSION 
 
The business objects in the scope of this solution accelerator are all stand-alone business objects. 
Therefore, this solution accelerator uses a simple business workspace for each. Documents are directly 
stored in the corresponding business workspace. 
Connections between business objects are also represented as business relationships. They are 
maintained for the workspaces. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 12 
 
Upon creation of an SAP EHSM business object, the corresponding business workspace can be created 
either automatically or manually. 
For more information about the workspace capabilities, refer to the official Extended ECM for SAP 
Solutions documentation which is available in the OpenText Knowledge Center 
(https://knowledge.opentext.com/knowledge/cs.dll/Open/34046660). 
 
 
Basic customizing of Extended ECM 
For details about SAP Extended ECM, see the official product documentation in OpenText Knowledge 
Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/34046660). 
 
https://knowledge.opentext.com/knowledge/cs.dll/Open/34046660
https://knowledge.opentext.com/knowledge/cs.dll/Open/34046660
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 13 
 
3 New in EHSM Solution Accelerator 
2.0 
3.1 Specification 
Update these category attributes on SAP for the business object declaration in the IMG (transaction 
SPRO). 
Category attribute old Category attribute new PP property 
Spec. Type Specification Type SUBCATEGRY 
 Substance Nature SUBCHARACT 
 Note NOTE 
 
3.2 Incident 
For the business object Incident, existing categories were enhanced and re-structured in category sets. 
With this change, customizing of EHSM Solution Accelerator 1.0 has become invalid and must be set up 
again with the new categories. 
As set attributes cannot be used for creating name patterns in the configuration, the property provider 
now provides two stand-alone business attributes INC_ID (Incident ID) and INC_TITLE (Incident title). 
You can use these attributes to create the names for business attachments and business workspaces. 
 
Figure 3-1: Name pattern for business attachments and business workspaces 
Incident category set: 
Category attribute PP property 
 Incident Number ID 
 Title TITLE 
 Incident Category Number CATEGORY 
 Incident Category CATEGORY_DESC 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 14 
 
Category attribute PP property 
 Incident Status STATUS_DESC 
 Incident Groups INC_GROUP_DESC 
 Regulations REGULATIONS_DESC 
 Description of Events DESC_TEXT 
 Immediate Actions IMA_DESC_TEXT 
 Fatal Injury / Illness FATALITY_TS 
 Created By USER_ID_CR 
 Technical Key ROOT_KEY 
 Start Date START_DATE 
 
Location category set: 
Category attribute PP property 
City CITY 
Country COUNTRY_DESC 
Location LOC_ROOT_NAME_REF 
Location Classification LOC_TYPE_DESC 
Location DescriptionLOC_DESC_TEXT 
Organizational Unit ORG_DESC 
Plant PLANT_DESC 
Postal Code POSTAL_CODE 
Region REGION_DESC 
Street / House Number STREET_HOUSE_NUM 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 15 
 
Assets category set: 
Category attribute PP property 
Id ID 
Name ASSET_DESC 
Type TYPE_DESC 
 
Persons Involved category set: 
Category attribute PP property 
Full Name FULL_NAME_DISP 
Role ROLES_SHORT_DESC 
 
Starting with this version, the property provider also delivers asset relationships. 
3.3 Waste Management 
From this version on, there is one common category for Waste Generator, Waste Disposer, Waste 
Transporter and Waste Authority. 
 
Waste Generator (/OTX/RMWAG): 
Category attribute old Category attribute new PP property 
Company-Internal Procedure Company-Internal Procedure WADEPRO 
Contact Person Contact Person WACON 
Date of Last Audit Date of Last Audit WAAUDIT 
Date of Next Audit Date of Next Audit WANAUDIT 
Inspector Inspector WAAUDPERS 
Partner Role Partner Role ID RLTYP 
Partner type Partner Type ID WABPCAT 
Partner type descr. Partner Type WABPCATDES 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 16 
 
Category attribute old Category attribute new PP property 
Role-Dependent Partner Name Partner Name WADESCRPOFG 
 Partner ID PARTNER 
 Plant NAME1 
 
Waste Disposer (/OTX/RMWAD): 
Category attribute old Category attribute new PP property 
Company-Internal Procedure Company-Internal Procedure WADEPRO 
Contact Person Contact Person WACON 
Date of Last Audit Date of Last Audit WAAUDIT 
Date of Next Audit Date of Next Audit WANAUDIT 
Inspector Inspector WAAUDPERS 
Partner Role Partner Role ID RLTYP 
Partner type Partner Type ID WABCAT 
Partner type descr. Partner Type WABPCATDES 
Role-Dependent Partner Name Partner Name WADESCRPOFG 
 Partner ID PARTNER 
 Plant NAME1 
 
Waste Transporter (/OTX/RMWAT): 
Category attribute old Category attribute new PP property 
Company-Internal Procedure Company-Internal Procedure WADEPRO 
Contact Person Contact Person WACON 
Date of Last Audit Date of Last Audit WAAUDIT 
Date of Next Audit Date of Next Audit WANAUDIT 
Inspector Inspector WAAUDPERS 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 17 
 
Category attribute old Category attribute new PP property 
Partner Role Partner Role ID RLTYP 
Partner type Partner Type ID WABPCAT 
Partner type descr. Partner Type WABPCATDES 
Role-Dependent Partner Name Partner Name WADESCRPOFG 
 Partner ID PARTNER 
 
Waste Authority (/OTX/RMWAA): 
Category attribute old Category attribute new PP property 
Contact Person Contact Person WACON 
Partner Role Partner Role ID RLTYP 
Partner type Partner Type ID WABPCAT 
Partner type descr. Partner Type WABPCATDES 
 Partner ID PARTNER 
 
3.4 Additional Icons 
The package now contains additional icons that you can use for the EHSM workspace types in Content 
Server. 
To enable these icons, copy them into the <OPENTEXT CS directory>/support/otsapxecm 
directory. 
3.5 Product Safety 
The solution accelerator now supports the export of product safety reports to a business workspace. You 
can export raw reports as well as final reports, both automatically and manually. 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 18 
 
4 Customizing Specification 
4.1 Overview 
A specification is a detailed description which outlines objects such as substances, agents, dangerous 
goods classifications, waste codes, medical data and packaging. Characteristics of these items, such as 
physical-chemical properties, create date, are defined using identifiers which are a format of structured 
data. 
After creating a specification in transaction CG02, a corresponding workspace is created if customized, or 
it can be created manually. The workspace metadata can be synchronized when a specification is 
changed. The corresponding workspace can be displayed from the specification workbench via Business 
Content window. 
To see the workspace name, which is defined by the [IDENTIFIER] attribute, you maintain a language in 
ID Category=NAM and ID Type=PROD L=users login language. 
Otherwise the identifier will not be used to define the workspace name in Content Server. 
 
Figure 4-1: Specification transaction CG02 with Business Content window 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 19 
 
4.2 UI integration 
 
Figure 4-2: Button to open Business Content window in transaction CG02 
To add a Business Content button in transaction CG02: 
1. Start transaction SPRO. 
2. In the IMG, open Environment, Health & Safety > Basic Data and Tools > Specification 
Management > Menu Exits for Specification Management > Develop Enhancement for 
Menu Exit 1. 
3. Create a new Project Z_PROJ and enter a short text. 
4. Click Enhancement assignments. 
5. Add C1020001 (EHS: Menu Exit 1 of Specification Management). 
6. Click Components. 
7. Double-click Menu exit. Then enter the name of the button in the Function text field. Select 
icon ICON_BUSINAV_DATAMODEL, enter @51@ as icon text and add Info text. Then click 
Copy. 
8. Click Function exit. In the code, double-click ZXC1AU20 next to INCLUDE. 
9. Press Return to confirm message ‘Program names ZX… are reserved for includes of exit 
function groups’ that is displayed in the status bar. Then click Yes to create the object. 
 
10. Press Enter and insert the following code: 
data: 
 lh_window type ref to /otx/rmehsm_cl_bc_embedded, 
 l_id type sibfboriid. 
 
l_id = i_sub_tab-subid. 
 
lh_window = /otx/rmehsm_cl_bc_embedded=>get_instance( 
 pi_bo_type = 'BUS1077' 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 20 
 
 pi_bo_id = l_id ). 
 
lh_window->set_focus( ). 
11. Save and activate the enhancement. 
4.3 Business object declaration 
To configure business workspaces for SAP EHSM business objects, generally proceed as described in 
the OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD): “Configuring Business 
workspaces.” Customize the specific settings for the SAP EHSM objects as follows: 
 
Figure 4-3: Business object declaration for Specification 
1. In the Business Object Declaration dialog, create and configure the following business object 
declarations: 
Object Type – BUS1077 
Properties Provider – /OTX/RMEHSM_WSCI_CL_WSPP_SPEC 
Search Help Name – /OTX/RMEHSM_SH_SPEC 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 21 
 
2. Do the corresponding workspace configuration on Content Server. Proceed here as described in 
the OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD). 
3. Content Server categories are imported in an XML file from a transport package. For more 
information, see OpenText Content Server XML Import and Export Guide 
(https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-
pgd/en/html/_manual.htm). 
 
4.4 Workspace type in Content Server 
The following is a sample workspace type configuration for a Specification. 
 
Figure 4-4: Sample workspace type configuration for specification 
Icons for business workspaces 
You can use the following icons for business workspaces: 
 
Specification 
https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-pgd/en/html/_manual.htm
https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-pgd/en/html/_manual.htm
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M AT I O N M A N A G E M E N T 22 
 
4.5 Category and attributes 
For a list of deprecated category attributes, see 3.1 Specification on page 13. 
Category Attributes Property 
Specification Specification SUBSTANCE 
Identifier IDENTIFIER 
Specification Type SUBCATEGRY 
Material MATERIAL 
Substance Nature SUBCHARACT 
Note NOTE 
4.6 Business relationships 
The following business relationships as implemented in the respective property provider. 
Business Object Is parent to Is child of 
Specification Material 
 
4.7 Receiver module events 
To automatically react on creation, update or even deletion of SAP business objects, you must configure 
the respective Receiver Module Events in the IMG activity Maintain Receiver Module Events. 
To configure Receiver Module Events for SAP business objects, generally proceed as described in 
OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD): “Configuring eventing”. 
Customize the special settings for the SAP business objects as follows: 
Notes: 
 Destination of Receiver is set to NONE: the function module is running in the context of the 
current user. 
 Destination of Receiver is empty: the function module is running as default user wf-batch. In 
this case the wf-batch user has to be available in OTDS and Content Server. 
 Alternatively, you can insert here an RFC destination that contains a dedicated user. As before, 
this dedicated user has to be known by OTDS and Content Server. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 23 
 
 
Figure 4-5: Receiver module event Changed for Specification 
Change 
In the Event Type Linkages dialog, click New Entries to customize the following settings: 
 Object Category – Select BOR Object Type. 
 Object Type – enter BUS1077 
 Event – enter CHANGED.* 
 Receiver Type – enter BUS1077 
 Receiver Call – select Function Module. 
 Receiver Function Module – enter /OTX/RMEHSM_UPD_SPEC. 
 Destination of Receiver – enter NONE. 
 Linkage Activated – select the check box. 
Comment:* 
The business object type BUS1077 only supports the CHANGED event. However if you create a 
specification, you will also get a CHANGED event. The function module 
/OTX/RMEHSM_UPD_SPEC redirects the CHANGED event to the appropriate 
CREATED/CHANGED event according to existing workspaces. 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 24 
 
Deletion 
This action is currently not supported. 
4.8 Event triggering 
Not all BOR objects can trigger all event types by default, therefore in some cases you have to use 
change documents in order to react on different activities. 
Make sure, that change documents are written for all the business objects of interests. 
 To maintain change document events, execute the ECMLink > Maintain Change Document 
Event activity in the IMG. Create the following entries in the Events for Change Document 
list. 
Upon adding new entries, you may get the following message “Key for change doc. object <CHANGE 
DOC> and business object type <BO> are incompatible”. You can ignore this warning. <CHANGE DOC> 
and <BO> are placeholders for concrete values. 
Create 
 Change doc. object – ESSUB 
 Object Category – BOR Object Type 
 Object Type – BUS1077 
 Event – CHANGED 
 Trigger Event – select on Create 
 
Figure 4-6: Create event for Specification 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 25 
 
Change 
 Change doc. object – ESSUB 
 Object Category – BOR Object Type 
 Object Type – BUS1077 
 Event – CHANGED 
 Trigger Event – select on Change 
 
Figure 4-7: Change event for Specification 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 26 
 
4.9 Testing 
Use transaction CG02 to maintain Substances and specification. Create a business workspace from the 
GOS menu. 
 
Figure 4-8: Specification in transaction CG02 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 27 
 
 
Figure 4-9: Business Content window for the specification 
 
 
 
Figure 4-10: Business workspace for the specification in Content Server 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 28 
 
5 Customizing Incident 
5.1 Overview 
Incident management is part of the component extension for EHSM. It is built on the foundation layer of 
EHSM. 
You can create the following types of incidents: 
 Incident 
 Near Miss 
 Safety observation 
From a technical point of view, there is no difference between those types of incidents. However, the type 
determines the follow-up business processes. This solution accelerator supports all types of incidents. 
After you create a new incident, the corresponding business workspace is created or it can be created 
later manually. From this point on, you can leverage all document management features of Content 
Server. If configured, the workspace metadata is synchronized each time the incident is changed. The 
workspace itself is displayed as a separate view in the main incident window beside the regular incident 
views. 
Incidents have a standard document view, which is delivered by SAP. To reduce confusion for the users, 
you can hide this view via customizing. 
If you use the normal incident report for creating an incident, you may attach documents to the incident. 
These documents are managed via the customized attachment folder and are independent from the 
related workspace. 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 29 
 
 
Figure 5-1: Workspace tab in an Incident 
5.2 UI integration 
You can use SAP’s floor plan manger to enhance the component configuration 
EHHSS_INC_REC_OIF_V3 of component FPM_OIF_COMPONENT. Add a new Workspace tab. Use 
the /OTX/RMEHSM_INC_WSP component to display the workspace. 
To integrate the Workspace tab in Incident Management: 
1. Run transaction SE80 and open the FPM_OIF_COMPONENT WebDynpro component. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 30 
 
 
2. Display the EHHSS_INC_REC_OIF_V3 component configuration. 
3. Click Start Configurator. 
4. Use the Other Functions menu to create an enhancement of the current configuration. 
 
5. Open the enhancement in change mode. 
6. Click Add Main View on the right side to add a new tab. 
7. Fill in the fields: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 31 
 
 Mainview ID: WSP_COMP 
 Mainview Name: Workspace 
 
8. Open the tree on the left and fill in the UIBB values. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 32 
 
 
9. In in the IMG, open the node SAP EHS Management > Incident Management > General 
Configuration > Assign Access Level to Tabs. 
10. Add a new entry: 
 Configuration Code: can be any name. 
 Access Level: select Basic Information. 
 Incident Main View: Mainview ID from the Floorplan configuration before. 
 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 33 
 
5.3 Business object declaration 
To configure business workspaces for SAP EHSM business objects, generally proceed as described in 
the OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD): “Configuring Business 
workspaces.” Customize the specific settings for the SAP EHSM objects as follows: 
 
Figure5-2: Business object declaration for Incident 
1. In the Business Object Declaration dialog, create and configure the following business object 
declarations: 
Object Type – /OTX/RMINC 
Properties Provider – /OTX/RMEHSM_WSCI_CL_WSPP_INC 
Search Help Name – /OTX/RMEHSM_SH_INCIDENT 
Workspace name - [INC_ID] - [INC_TITLE] 
2. Do the corresponding workspace configuration on Content Server. Proceed here as described in 
the OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD). 
3. Content Server categories are imported in an XML file from a transport package. For more 
information, see OpenText Content Server XML Import and Export Guide 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 34 
 
(https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-
pgd/en/html/_manual.htm). 
5.4 Workspace type in Content Server 
The following is a sample workspace type configuration for an Incident. 
 
Figure 5-3: Sample workspace type configuration for Incident 
Icons for business workspaces 
You can use the following icons for business workspaces: 
 
Incident 
5.5 Category sets and attributes 
For a list of deprecated category attributes, see 3.2 Incident on page 13. 
https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-pgd/en/html/_manual.htm
https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-pgd/en/html/_manual.htm
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 35 
 
Category set Attributes Property 
Incident Incident Number ID 
 Title TITLE 
 Incident Category Number CATEGORY 
 Incident Category CATEGORY_DESC 
 Incident Status STATUS_DESC 
 Incident Groups INC_GROUP_DESC 
 Regulations REGULATIONS_DESC 
 Description of Events DESC_TEXT 
 Immediate Actions IMA_DESC_TEXT 
 Fatal Injury / Illness FATALITY_TS 
 Created By USER_ID_CR 
 Technical Key ROOT_KEY 
 Start Date START_DATE 
Location Plant PLANT_DESC 
Location LOC_ROOT_NAME_REF 
Location Description LOC_DESC_TEXT 
Location Classification LOC_TYPE_DESC 
Street / House Number STREET_HOUSE_NUM 
Postal Code POSTAL_CODE 
City CITY 
Country COUNTRY_DESC 
Region REGION_DESC 
Organizational Unit ORG_DESC 
Assets Type TYPE_DESC 
Name ASSET_DESC 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 36 
 
Category set Attributes Property 
Id ID 
Persons Involved Role ROLES_SHORT_DESC 
Full Name FULL_NAME_DISP 
5.6 Business relationships 
The following business relationships as implemented in the respective property provider. 
Business Object Is parent to Is child of 
Incident Equipment 
 Functional Location 
 
5.7 Displaying an SAP business object from Content 
Server 
You can use the Display functionality of a business workspace (Function menu > Properties > General > 
Display) to display the corresponding SAP business object. Most objects do not need additional setup; 
however, Incident management requires additional steps. 
Change the display URL of the Configure Business Object Type administration page to the following: 
$SapSystemUrl$/sap/bc/webdynpro/sap/ehhss_inc_rec_oif_v3;?KEY=$attribute:catn
ame=<catid>,attrname=Tech.Key$ 
Replace <catid> with the incident category ID. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 37 
 
 
Figure 5-4: Display URL for business object type 
The Tech.Key attribute must be filled in for a given incident. 
5.8 Receiver module events 
the respective Receiver Module Events in the IMG activity Maintain Receiver Module Events. 
To configure Receiver Module Events for SAP business objects, generally proceed as described in 
OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD): “Configuring eventing”. 
Customize the special settings for the SAP business objects as follows: 
Notes: 
 Destination of Receiver is set to NONE: the function module is running in the context of the 
current user. 
 Destination of Receiver is empty: the function module is running as default user wf-batch. In 
this case the wf-batch user has to be available in OTDS and Content Server. 
 Alternatively, you can insert here an RFC destination that contains a dedicated user. As before, 
this dedicated user has to be known by OTDS and Content Server. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 38 
 
 
Figure 5-5: Receiver module event Created for Incident 
 
Creation 
1. In the Event Type Linkages dialog, click New Entries to customize the following settings: 
 Object Category – Select ABAP Class 
 Object Type – enter CL_EHHSS_PCO_INC_LC 
 Event – enter CREATED 
 Receiver Type – enter /OTX/RMINC 
 Receiver Call – select Function Module 
 Receiver Function Module – enter /OTX/RMEHSM_HND_INC_WFE 
 Destination of Receiver – enter NONE 
 Linkage Activated – select the check box. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 39 
 
 
Figure 5-6: Receiver module event Changed for Incident 
Change 
1. In the Event Type Linkages dialog, click New Entries to customize the following settings: 
 Object Category – Select BOR Object Type 
 Object Type – enter /OTX/RMINC 
 Event – enter CHANGED 
 Receiver Type – enter /OTX/RMINC 
 Receiver Call – select Function Module 
 Receiver Function Module – enter /OTX/RMEHSM_HND_INC_WFE 
 Destination of Receiver – enter NONE 
 Linkage Activated – select the check box. 
Deletion 
This action is currently not supported. 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 40 
 
5.9 Event triggering 
Create 
If the EHSM component is set up correctly, the system automatically triggers the create event. 
Change 
1. Start transaction SPRO and open the following: SAP Customizing Implementation Guide > 
Cross-Application Components > Processes and Tools for Enterprise Applications > 
Reusable Objects and Functions for BOPF Environment > Maintain BO-specific Change 
Document Objects. 
2. Search the entry for Business Object EHHSS_INCIDENT and modify the value according the 
following: 
 Change doc. object: EHHSS_INCIDENT 
 Change Doc. Class: /OTX/RMEHSM_CL_CDCALLBACK 
 
Figure 5-7: Change document adapter for Incident 
5.10 Testing 
1. Open NetWeaver Business Client (transaction NWBC) and log in with an Incident related role, 
for example Incident Manager. 
2. Create a new incident. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 41 
 
 
Figure 5-8: Incident 
3. Click the Business Workspace tab and create a new business workspace. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 42 
 
 
Figure 5-9: Business workspace for the Incident 
4. You can now also view the business workspace in Content Server. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 43 
 
 
 
Figure 5-10: Business workspace for the incident in Content Server 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 44 
 
6 Customizing Waste management 
6.1 Overview: Waste management 
The waste management solution focuses on the integration into waste management master data 
management. The waste management business partner is the central data object for uniformly modeling 
a person, institution, or organizationalunit involved in the generation, transportation, or disposal of a 
waste. You always access master data editing via an involved waste management business partner. The 
solution accelerator delivers integration for the four predefined business partner roles. 
Depending on the customizing, a workspace is created when a new instance of a particular role is created 
or it can be created later manually. If configured, the role properties can be synchronized automatically 
with the workspace after changing a role. The corresponding workspace is displayed on a new separate 
tab in the Role Maintenance transaction. 
 
Figure 6-1: Business workspace for the Waste Generator business object 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 45 
 
6.2 UI integration 
To embed the Business Content window into the waste management transaction, you use the BDT 
framework capabilities. 
1. Start transaction WASS102 to create a new view. 
a) Click New entries and fill in the form as follows: 
View Choose an arbitrary identifier 
Description Business Content 
Application WAM 
Differentiation Type 0 
Data Set BUS000 
Entry view Select 
Dialog view Select 
Program Name /OTX/SAPLRMEHSM_WASTE_MNG 
Screen Number 0100 
Data screen Select 
b) Save the entries. 
2. Start transaction WASS103 to create a new section. 
a) Click the new button and fill in the form as follows: 
Section Any arbitrary section identifier 
Description Business Content 
Title Business Content 
b) Click the Section > Views node on the left side. 
c) Click the new button and fill in the form as follows: 
Item 100 
View Add the newly created view 
d) Save the entries. 
3. Start transaction WASS104 to create a new screen. 
a) Click the new button and fill in the form as follows: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 46 
 
Screen Any arbitrary identifier 
Description Business Content 
Screen title Business Content 
Data screen Select 
BDT Select 
Normal Select 
b) Click the Screen > Sections tree node on the left side. 
c) Click the new button and fill in the form as follows: 
Item 10 
Sect. WAA105 
Item 20 
Sect. Add the newly created section 
 
4. Customize the waste management role: 
Note: Each waste management role can be customized differently. Follow the following steps 
for each role of interest. 
a) Start transaction WASS105. 
b) Mark the screen sequence of interest, for instance Waste Generator. 
c) Click the Screen Sequence > Screens node on the left side. 
d) Click the new entries button and fill in the form as follows: 
Item Any arbitrary item number(the screen order depends on the item 
number) 
Screen Add the newly created screen 
e) Save the entries. 
 
 
6.3 Business object declaration 
To configure business workspaces for SAP EHSM business objects, generally proceed as described in 
the OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD): “Configuring Business 
workspaces.” Customize the specific settings for the SAP EHSM objects as follows: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 47 
 
 
Figure 6-2: Business object declaration for Waste Generator 
1. In the Business Object Declaration dialog, create and configure the following business 
object declarations: 
 For the Waste Generator business object: 
Object Type – /OTX/RMWAG 
Properties Provider – /OTX/RMEHSM_WSCI_CL_WSPP_WAGEN 
Search Help Name – /OTX/RMEHSM_SH_WASTE_GEN 
Workspace name - [PARTNER] - [WADESCRPOFG] 
 
 For the Waste Disposer business object: 
Object Type – /OTX/RMWAD 
Properties Provider – /OTX/RMEHSM_WSCI_CL_WSPP_WADIS 
Search Help Name – /OTX/RMEHSM_SH_WASTE_DISP 
Workspace name - [PARTNER] - [WADESCRPOFG] 
 
 For the Waste Transporter business object: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 48 
 
Object Type – /OTX/RMWAT 
Properties Provider – /OTX/RMEHSM_WSCI_CL_WSPP_WATRA 
Search Help Name – /OTX/RMEHSM_SH_WASTE_TRAN 
Workspace name - [PARTNER] - [WADESCRPOFG] 
 
 For the Waste Authority business object: 
Object Type – /OTX/RMWAA 
Properties Provider – /OTX/RMEHSM_WSCI_CL_WSPP_WAAUT 
Search Help Name – /OTX/RMEHSM_SH_WASTE_AUTH 
Workspace name - [PARTNER] 
2. Do the corresponding workspace configuration on Content Server. Proceed here as described in 
the OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD). 
3. Content Server categories are imported in an XML file from a transport package. For more 
information, see https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-
pgd/en/html/_manual.htm. 
 
6.4 Workspace type in Content Server 
The following is a sample workspace type configuration for a Waste Generator. 
https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-pgd/en/html/_manual.htm
https://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-pgd/en/html/_manual.htm
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 49 
 
 
Figure 6-3: Sample workspace type configuration for a Waste Generator 
Icons for business workspaces 
You can use the following icons for the waste related business workspaces: 
 
Waste Generator 
 
Waste Disposer 
 
Waste Transporter 
 
Waste Authority 
 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 50 
 
6.5 Category sets and attributes 
For a list of deprecated category attributes, see 3.3 Waste Management on page 15. 
Category Attributes Property 
Waste Partner Type ID WABPCAT 
Partner Type WABPCATDES 
Partner Role ID RLTYP 
Partner Name WADESCRPOFG 
Date of Last Audit WAAUDIT 
Date of Next Audit WANAUDIT 
Inspector WAAUDPERS 
Contact Person WACON 
Company-Internal Procedure WADEPRO 
Plant NAME1 
Partner ID PARTNER 
6.6 Business relationships 
The following business relationships as implemented in the respective property provider. 
Business Object Is parent to Is child of 
Waste Generator 
(/OTX/RMWAG) 
Material Waste Generator (depending on partner 
type) 
Waste Generator (depending on 
partner type) 
 
Waste Disposer 
Waste Transporter 
Waste Authority 
Waste Disposer Material Waste Disposer 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 51 
 
(/OTX/RMWAD) 
Waste Generator (depending on 
partner type) 
 
Waste Disposer 
Waste Transporter 
Waste Authority 
Waste Transporter 
(/OTX/RMWAT) 
Material 
Waste Generator (depending on 
partner type) 
 
Waste Disposer 
Waste Transporter 
Waste Authority 
Waste Authority 
(/OTX/RMWAA) 
— — 
 
6.7 Receiver module events 
To automatically react on creation, update or even deletion of SAP business objects, you must configure 
the respective Receiver Module Events in the IMG activity Maintain Receiver Module Events. 
To configure Receiver Module Events for SAP business objects, generally proceed as described in 
OpenText ECMLink for SAP Solutions - Customizing Guide (ERLK-CGD): “Configuring eventing”. 
Customize the special settings for the SAP business objects as follows: 
Notes: 
 Destination of Receiver is set to NONE: the function module is running in the context of the 
current user. 
 Destination of Receiver is empty: the function module is running as default user wf-batch. In 
this case the wf-batch user has to be available in OTDS and Content Server. 
 Alternatively, you can insert here an RFC destination that contains a dedicated user. As before, 
this dedicated user has to be known by OTDS and Content Server.SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 52 
 
 
Figure 6-4: Receiver module event Created for Waste Authority (object type /OTX/RMWAA) 
 
You can create event type linkages for the Created and for the Change event for the following Waste 
management objects: 
 Waste Generator: /OTX/RMWAG 
 Waste disposer: /OTX/RMWAD 
 Waste transporter: /OTX/RMWAT 
 Waste authority: /OTX/RMWAA 
Creation 
1. In the Event Type Linkages dialog, click New Entries to customize the following settings: 
 Object Category – select BOR Object Type 
 Object Type – Waste business object type 
 Event – enter CREATED 
 Receiver Type – Waste business object type 
 Receiver Call – select Function Module 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 53 
 
 Receiver Function Module – enter /OTX/RM_WSC_UPD 
 Destination of Receiver – enter NONE 
 Linkage Activated – select the check box. 
Change 
2. In the Event Type Linkages dialog, click New Entries to customize the following settings: 
 Object Category – Select BOR Object Type 
 Object Type – Waste business object type 
 Event – enter CHANGED 
 Receiver Type – Waste business object type 
 Receiver Call – select Function Module 
 Receiver Function Module – enter /OTX/RM_WSC_UPD 
 Destination of Receiver – enter NONE 
 Linkage Activated – select the check box. 
Deletion 
This action is currently not supported. 
 
6.8 Event triggering 
1. Start transaction WASS106. 
2. Mark the DSAVE event and double-click Event > Function Modules on the left side. 
3. Create a new entry: 
o Choose any arbitrary number for the item 
o Function module name: /OTX/RMEHSM_HND_WASTE_SAVE 
o Call: X 
o Appl.: WAM 
 
 
6.9 Testing 
1. Use transaction WASM101 to access Waste Management. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 54 
 
 
Figure 6-5: Select a role 
2. Select Waste Generator and open a Waste Generator business partner. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 55 
 
 
Figure 6-6: Waste Generator details screen 
3. Open the Business Content tab. 
4. If no automatic creation of business workspaces is configured, right-click the Business 
Workspace node and select Create Business Workspace. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 56 
 
 
Figure 6-7: Create Business Workspace 
The business workspace is displayed. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 57 
 
 
Figure 6-8: Business workspace in Business Content tab 
5. You can now also view the business workspace in Content Server. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 58 
 
 
Figure 6-9: Waste Generator business workspace in Content Server 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 59 
 
7 Customizing Product Safety 
7.1 Overview 
Report generation 
You can use report generation to create any number of multilingual reports that can contain data from the 
substance database. 
Report management 
Report management supports the management and release of reports, for example, material safety data 
sheets and labels. Using status management, you can set up a controlled release process according to 
your own individual needs. By adding data from an actual substance, a report is generated from the 
report template that is created for a certain language and jurisdiction. This report is then available in R/3 
document management for all R/3 users in a company. By transferring current data (such as material 
number, company name and logo) this report is transferred to the final report to be dispatched. The entire 
report request can be triggered manually or automatically. 
Report shipping 
Report shipping is used for shipping finished reports, taking into account the relevant valid legal 
regulations. In addition, you can use report management to trigger the printing of reports at a later point in 
time. As well as the automatic triggering from within SAP R/3 SD Shipping, you can create a shipping 
order for reports manually. Bundling the substance reports according to certain criteria (such as envelope 
used, e-mail size or recipient) is also possible. Subsequent shipping of reports is carried out automatically 
using a date-controlled check routine. Reports can also be subsequently shipped automatically if the 
report has changed because relevant changes were made to substances or phrases. Reports that were 
created as inbound documents can also be shipped. 
Report information system 
You can use the report information system to display all reports for a substance in the form of a report 
tree. The current (released) version of a report is highlighted in the report display. Historical versions of a 
report can also be displayed. The report information system can also be started from a material for which 
reports are to be displayed. This function can also be used from within documents from R/3 Shipping. 
7.2 Prerequisites for Product Safety 
 Prerequisites from EHSM Solution Accelerator 1.0 are met. 
 WWI server and all EHSM configurations are customized for report management and report 
shipment. 
 Check the EHSM prerequisites with your EHSM consultant. 
 To enable the final report solution you need ABAP development knowledge. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 60 
 
 EA-APPL Rel. 605, Level 0005: This solution accelerator needs at least EA-APPL Rel. 605, Level 
0005 in order to fully use the final report functionality with different renditions for final reports. 
If you have EA-APPL < Rel.605, Level 0005, you cannot get another rendition with the EHSM 
function module C14S_DOCUMENT_ORIGINAL_COPY. This would have been important, for 
example in case of LET/FAX. LET/FAX often uses the formats PS or PC”. In OpenText Content 
Server, you would need another format. In this case you have to program more lines of code 
yourself than it is outlined in this solution accelerator. 
7.3 Reports in Product Safety 
This section explains basic information about EHSM Product Safety. EHSM experts can skip this section. 
Principle legal regulations oblige companies to provide data reports for the sold materials to their 
customers. 
7.3.1 SOP and MSDS reports 
The production of the final report which you send to the customer passes several stages. This applies to 
the following: 
 Standard Operating Procedures (SOP) 
 Material Safety Data Sheets (MSDS) 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 61 
 
 
Figure 7-1: Reports in Product Safety 
 
Substance management forms the basis for all other SAP EH&S functions and provides the infrastructure 
for further applications in the SAP system. Using substance management, you can enter and identify all 
kinds of substances (pure substances, preparations, mixtures, polymers, and so on) and describe them 
with properties. The substance properties can be changed both quickly and flexibly. You can also extend 
them and arrange them into properties trees that the user can define. 
1. In transaction CG02 you can see a substance: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 62 
 
 
Figure 7-2: Substance with Property tree 
2. From the menu, select Specification > Reports > CreateReport to create a raw report: 
 
Figure 7-3: Select variant for report creation 
The raw report contains data from the specification, but the parameters and material name are 
still placeholders. 
The generation variant (transaction CG2B) is the link between a report template (transaction CG42) and 
specification data (transaction CG02). The report template defines the layout of your report by using word 
symbols where data should be replaced. 
In the generation variant you define among others: 
 Report template 
 Status the raw report has after its generation 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 63 
 
 Rating/Validity: Priority which data should be used first in raw report: 
In case you have two data sets on a specification parameter: One dataset with classification 
SPECIF, another with classification PUBLIC, define which dataset is used 
In the report information system (transaction CG54, report category = MSDS), you see the raw reports 
that are generated by the WWI server: 
 
Figure 7-4: Raw reports in the report information system 
3. To generate the shipping order of the final report for a raw report, select the raw report. Then 
select from the menu Report > Send. 
4. Select a material and then enter the report shipping parameters: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 64 
 
 
Figure 7-5: Shipping parameters 
You can create a shipping order for a customer (= debtor), Office User (needs an HR-Account) or 
report recipient directly. 
5. In the Edit Shipping Orders screen (transaction CVD1), you see this sort of shipping order with 
the reason = MAN_CALL (manual call): 
 
 
 
If you trigger a shipment for this shipping order, the shipment runs through several stages: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 65 
 
- Checks whether multiple deliveries of the same material are to be shipped to the same customer 
- Checks whether the MSDS is already sent 
- Bundling (e.g. determines how many bytes can contain one email) 
- Generation of the final report by WWI server 
- Generation of the cover sheet 
- Ship to printer/fax/email 
- (Acknowledgement of receipt, only if customized) 
The final report contains the data of the recipient, all parameter symbols are replaced by specification 
data and the material name symbol is replaced by a specific material as well. 
The raw report with its parameter values from transaction CVD1 is the proof for legal regulation that the 
final report is shipped to the customer. 
 Raw reports are never deleted in SAP DMS. In case of new version of raw reports the old reports 
can be set in status “historical”. 
 Final reports are only stored temporarily in SAP DMS. After shipment they are deleted by a job 
after a defined time. Reports are only if the final report flag is disabled. To enable the final 
report flag, see 7.5.6 Exporting final reports on page 80. 
7.3.2 Inbound reports 
Sometimes the companies have their own documents, for example descriptions of production processes. 
These documents can be uploaded in SAP in the Import Single Report screen (transaction CG36VEN) 
with generation variant IBD_MSDS: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 66 
 
 
Figure 7-6: Importing a single report (transaction CG36VEN) 
In transaction CG54 with report category = IBD_MSDS, you see the uploaded documents: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 67 
 
 
Figure 7-7: Uploaded documents (transaction CG54) 
7.4 Exporting raw reports to business workspaces 
Raw reports of report category IBD_MSDS, SOP or MSDS can be stored in a business workspace. For 
this, you export them from the SAP system, either manually or automatically. 
7.4.3 Exporting a raw report manually 
For the manual export of raw reports to a business workspace, you can use the following approaches: 
1. Store raw report in transaction CG54. 
2. Select either menu option 
a. Report > Export > <your user exit> 
b. Utilities > <your user exit> 
7.4.3.1 Export approach 
If you use the Export option, you can select several reports and store them in the respective business 
workspace in Content Server. Drawback of this approach is that you have to enter the material name for 
each selected report, which you actually do not need for a raw report. 
1. In transaction CG54, select one or several documents 
2. From the menu, select Report > Export. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 68 
 
 
Figure 7-8: User exits 
This entry uses the function module /OTX/RMEHSM_EXPORT_DOCS_RAW that creates the raw reports 
in the business workspace of the corresponding specification. 
 The business workspace for the corresponding Specification has to exist in Content Server 
 The default directory in which the report is stored is called Raw Reports.This folder must exist in 
the business workspace. 
 The default format of the raw report is RTF. 
 If the raw report already exists in Content Server, the report is added as a new version. 
You can copy this function module and adapt it to your own needs. 
To configure the Export approach: 
1. In the IMG, go to Environment, Health & Safety > Basic Data and Tools > Basic Settings > 
Manage User Exits: 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 69 
 
 
Figure 7-9: Function module assignment 
2. Create a new entry: 
 User Exit Category: SRE_EXPOMN 
 User Exit: OT_EXPRAW 
 Function Module: /OTX/RMEHSM_EXPORT_DOCS_RAW 
 User Exit Description: Export raw reports to business workspace 
 Function Module: CVE9_RDO_DOKX_EXPORDS_CREATE 
 
7.4.3.2 Utilities approach 
If you use the Utilities approach, you can only store the last selected report in the business workspace. 
However, you are not asked to enter the material name. 
1. In transaction CG54, select one document. Then select from the menu Utilities > Create 
Raw Report in Business Workspace. 
To configure the Utilities approach: 
1. In the IMG, go to Environment, Health & Safety > Product Safety > Report Information 
System > Menue Exits > Develop Enhancement for Menu Exit 1. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 70 
 
 
Figure 7-10: Enhancement for User Exit 
2. Create your project. 
 
3. You can create the menu option for the user exits for Report Management (transaction CG50) 
and for Report Information System (transaction CG54). 
The following explains the customizing for Report Information System. Enhancement for report 
management is similar. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 71 
 
 
 
4. Double-click Menu exit and enter text as required 
 
5. Double-click Function exit: 
 
6. Double-click ZXC1AU12, then press Return. 
7. Enter the following text: 
data: 
ls_estdh type estdh. 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 72 
 
move-corresponding x_leaf_tab to ls_estdh. 
call function '/OTX/RMEHSM_EXPORT_DOC_RAW' 
 exporting 
 i_estdh = ls_estdh. 
7.4.4 Exporting raw reports automatically 
The automatic export of raw reports is done automatically by a daily background job, which you have to 
create. 
This job executes the /OTX/RMEHSM_PROD_SAF_EXP_RAW report, which stores the raw reports with 
state Released (= W7) and of the currentday. 
7.4.4.1 Configuration 
1. Create a daily background job for the report /OTX/RMEHSM_PROD_SAF_EXP_RAW. 
a. Use transation SM36 to define the background job. 
 
Figure 7-11: Create a background job 
b. Enter as step of the job the ABAP program /OTX/RMEHSM_PROD_SAF_EXP_RAW. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 73 
 
 
Figure 7-12: Steps of background job 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 74 
 
7.5 Exporting final reports to business workspaces 
Final reports can be created and stored in a business workspace on Content Server by SD_CALL or by 
export functionality (EXP_CALL) of EHSM. 
7.5.5 Exporting final reports manually 
For the manual export of final reports to a business workspace, this solution accelerator leverages the 
export user exit of the report information system (transaction CG54). 
1. In transaction CG54, select one or several documents. 
2. From the menu, select Report > Export. 
 
Figure 7-13: User Exit 
This entry uses the function module similar to /OTX/RMEHSM_EXPORT_DOCS_FINAL. Eventually you 
have to create your own function module that creates the final report in the business workspace of the 
corresponding material after you shipped it in transaction report shipping orders (transaction CVD1). 
 The business workspace for the material must already exist in Content Server 
 The default folder in which the report is stored is called Final Reports. This folder must exist in 
the business workspace. 
 If the report already exists, a new version is created. 
 
You can modify the function module to meet your needs. 
To create a shipment: 
1. Use transaction CVD1 to edit a shipping order. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 75 
 
 
Figure 7-14: Edit Report Shipping Orders (transaction CVD1) 
2. Press Enter. 
 
Figure 7-15: Released shipping order 
As this order was triggered in transaction CG54 by menu option Report > Export, the export 
reason is EXP_CALL. 
3. Select the order and click Accept. This changes the order status to In Work. 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 76 
 
 
4. Select the order again and click Ship immediately: 
 
5. Confirm the message, click Yes. 
The order is bundled, generated etc.:
 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 77 
 
 
 
 
When the status is Completed, the final report is stored in the business workspace of the 
corresponding material. 
To check the material assignment for a shipping order: 
1. Select a shipping order and click Parameter Values. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 78 
 
 
Figure 7-16: Parameter values for a shipping order 
 
To configure manual export of final reports: 
1. If you have EA-APPL Release 605 Level 0005 do the following: 
a. Copy the function module /OTX/RMEHSM_EXPORT_DOCS_FINAL of package 
/OTX/RMEHSM_CLASSIC to your local area. 
b. Name it z_rmehsm_exports_docs_final 
c. Delete the code remarks after 
„STEP 1: Check preconditions“. 
 
2. Alternatively, do the following: 
a. Copy the function module CVE9_RDO_DOKX_EXPORT from package CVDD in your 
local area. 
b. Copy both the declaration and code between the comments into your function module 
to the respective places. 
“" Begin of the Open Text own storage of the final report.” 
And" End of the Open Text own storage of the final report.” 
c. Delete the dispensable lines (here compare with /otx/rmehsm_export_docs_final). 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 79 
 
3. Insert the respective includes into the top include of your function module. 
Type-pools CVDDS. 
Include CVDD09. 
Include CBUI09. 
Include CVDD08. 
Include CVDD05. 
Include CBUI15. 
4. Check and activate your function module z_rmehsm_exports_docs_final. 
5. In the IMG, go to Environment, Health & Safety > Basic Data and Tools > Basic Settings > 
Manage User Exits 
6. Make Create a new entry with the following parameters: 
Change User Exit Description of entry User Exit Cat. SRE_EXPOMN with User Exit 
DOKX_EXOMN to Shipping Order for Business Workspace. 
 
Figure 7-17: Rename user exit description 
 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 80 
 
 
 
7.5.6 Exporting final reports automatically 
The automatic export of final reports can be triggered by business processes, for example: 
- Material is sold > sales document is created 
- Material is delivered > shipping document is created 
To configure automatic report export: 
If you want to save the final report in a business workspace in addition to the standard shipping, you have 
to do the following: 
1. Copy the corresponding shipping function module and insert after data declaration these 
lines: 
 " Save final report into Open Text Content Server: 
 call function <your created Open Text Final Report function module> 
 tables 
 x_rdo_header_tab = x_rdo_header_tab. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 81 
 
2. Assign corresponding includes to your function group, for example: 
Type-pools CVDDS. 
Type-pools CVDA1. 
INCLUDE CBUI00. 
Include CVDD09. 
Include CBUI09. 
Include CVDD08. 
Include CVDD05. 
Include CBUI15. 
3. Copy subroutines L_CHECK_SPOOL_PRECOND() from package CVDD, function group 
CVEQ. 
4. Save and activate the copy. 
5. In IMG, go to Environment, Health & Safety > Basic Data and Tools > Basic Settings > 
Manage User Exits. 
6. Edit the entry for User Exit Cat. SRE_DIST, User Exit EHS_SEND_L: Enter your copied 
Function module. 
 
 
7. Do the same for User Exits EHS_SEND_F, EHS_SEND_I and EHS_SEND_R. 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 82 
 
The following table gives a suggestion which standard function modules have to be replaced by your 
copied function modules to save the final report not only to the standard communication types but also to 
the business workspace in Content Server. 
Communication Type Standard Function Module 
LET CVEQ_SEND_TO_SPOOL 
FAX CVEQ_RDO_SEND_TO_FAX 
INT CVEQ_RDO_SEND_TO_INTERNET 
RML CVEQ_RDO_SEND_TO_RML 
 
7.5.6.1 Choice of Format 
If you also use LET and FAX for shipping you must also use the Disp./Backup format from your 
LET/FAX communication. The standard output format PS in not useful in Content Server. 
To change the format: 
1. In IMG, go to Environment, Health & Safety > Product Safety > Report Shipping > Basic 
Settings > Specify Communication, for example LET. 
 
Figure 7-18: Change format 
In this case the Disp./Backup format is PDF. However, this format is only generated if you 
customize it for final reports: In IMG, go to Environment, Health & Safety > Product Safety > 
SAP EHSM 
SAP Extended ECM Solution Accelerator 
 
E N T E R P R I S E I N F O R M A T I O N M A N A G E M E N T 83 
 
Report Shipping > Basic Settings > Specify Shipping Reason and set the flag for 
SD_CALL/DELIVERY/MSDS_DIST: 
 
 
Figure 7-19: Set Display and Backup format for final reports 
Only if this flag is set, the special Disp./Backup format is generated, otherwise you only have the 
format of the output format: PS for FAX/LET. 
 
To delete the generated final reports even if the final report flag is set: