Dear Experts,

Please look into the issue.

I am in the process of creating new template for Incident Management. In incident management we have Root Cause hierarchy.

How do we get the selected cause in WWI report.

Valuable input will be highly appreciated.

Thanks..

Lax..

Dear experts

we are facing a performance issue on some projects in transaction CBIHM2,

when are changing the status of a project to "RELEASED".

The performance issue is caused by logic going (for unknown reason) multiple times into risk management check

in

include: LCBIH_ER30F10

form: L_QTY_SET_EPQUANTSET

4.384         SELECT * FROM cciht_erh

4.385                INTO CORRESPONDING FIELDS OF TABLE l_riskass_iotab

4.386                FOR ALL ENTRIES IN i_api_erqtexist_tab

4.387                WHERE recn = i_api_erqtexist_tab-recnroot

4.388                  AND delflg = ' '

4.389                  AND ( ( valfr <= i_api_erqtexist_tab-valfr AND

4.390                          valto >= i_api_erqtexist_tab-valfr   ) OR

4.391                        ( valfr <= i_api_erqtexist_tab-valto AND

4.392                          valto >= i_api_erqtexist_tab-valto   ) OR

4.393                        ( valfr >= i_api_erqtexist_tab-valfr AND

4.394                          valto <= i_api_erqtexist_tab-valto  )  ).

We have similar projects without this issue and without this risk management check logic.

Could me anybody give a hint about this?

Thank you

Imrich

Regarding SAP EHS Incident Management.

Could you provide some documentation on how the e-mail address of Investigation Lead is determined. E-mail address of the investigation lead is taken from his SAP username (the one assigned in SU01). But in case this user is linked with employee through InfoType 0105 Subtype 0001, the e-mail address is not retrieved. Even if the same user has e-mail address assigned in the same InfoType under Subtype 0010.

As soon as the investigation is started the standard workflow WS00500031 is called and PCO object is created. The parameter PCO.MS_INVESTIGATION.INV_LEAD_EMAIL is blank if the SAP user is also an employee. This causes problem when custom notifications needs to be sent externally to investigation leads. Most likely the person assigned as investigation lead will also be an employee. How could this issue be addressed?

Thank you!

Hi Experts

I am getting the Error of " Cannot create the Value File" while previewing the report

please suggest me

Balajee

Dear experts,

I am in the process of creating new template for Incident Management. In incident management we have Root Cause hierarchy.

Now i need to capture that root cause into my WWI report .

Is there any way to get it?

Pls guide me

Waiting for your valuable inputs

Thanks & regards

Laxman

Hello!

Regarding SAP EHS Incident Management.

Could you provide some documentation on how the e-mail address of Investigation Lead is determined. E-mail address of the investigation lead is taken from his SAP username (the one assigned in SU01). But in case this user is linked with employee through InfoType 0105 Subtype 0001, the e-mail addres is not retrieved. Even if the same user has e-mail address assigned in the same InfoType under Subtype 0010.

As soon as the investigation is started the standard workflow WS00500031 is called and PCO object is created. The parameter PCO.MS_INVESTIGATION.INV_LEAD_EMAIL is blank if the SAP user is also an employee. This causes problem when custom notifications needs to be sent externally to investigation leads. Most likely the person assigned as investigation lead will also be an employee. How could this issue be addressed?

Thank you

Hi All

can you please resolve below issue  if anyone is implemented Incident management EHSM CE 3.0. 

We are error of “CL_EHHSS_PCO_INC_LC” having syntax error of report “%_JJ_TESTFRAME_CLASS”. while executing the Standard work flow WS00500001.

is there any SAP Note is available which is applicable to SAP_Basis 731 Release  for resolving this issue? We are already refereed two notes 983212 & 1100966 which is applicable for  SAP_Basis 700 Release only.

Balajee

Experts can you please help define steps or checks to be
performed to set up the portal workflow for EHSM Incident Management.

I did the following:

1. The configuration is done tasks assigned
2. I created a User concept and assigned roles and
   assigned.
3. Roles were assigned to the test users and linked
   with people in the Org structure.

     
I then created Incidents with the Reporter/Initiator role and expect it to send a
workflow to the Incident Investigator in the portal but this did not happen.

How can I check what happens in the backend to see if the workflow was send off
correctly?

One other thing I noticed is that the portal role Reporter/Initiator used to create
the Incident locked access to for Incident Investigator.

I am not sure why this happen and need some guidens on what to check.

I used SWI2_FREQ - Work Items per Task to check
and did see workflow kicked off for EH&S but it went into error.

Dear all,

we are facing an issue that SDS are sent out to customers by email without having an SR partner function assigned.

My assumption is that every customer is selected by this prcess that has an email adress maintained on the Bill-To-Party level.

Is this assumption correct or has anybody faced the same issue?

Thank you n advance for your support!

Best regards,

Christoph

Hello,

We are trying to setup an SPRC 2.0 system. A few details about the landscape:

• We have our ERP system which is an ERP 6.0 EHP6 system, with latest version of SPRC installed (TDAGBCA 200_600).
  • EHS product safety is already configured and running without problem on the system, with a full CED phrase catalog installed.
  • All basic SPRC configuration has been done, necessary phrase sets are created, and RCS phrases have been installed.
• Enterprise Portal system is 7.30, with latest SPRC 2.0 components installed (all TDAG* components).
  • SSO with ERP system is configured and working properly.
  • Both RFC destinations needed for SPRC (TDAG_RCS_APP& TDAG_RCS_IMG) are defined and working properly.

The issue we have is, when we try to launch most SPRC portal applications (e.g. REACH Material Assessment), we receive the following error:

de.technidata.rcs.common.exception.RCSUncheckedException: FATAL RCS2200 Phrase group SAP_RCS_TRISTATE is incomplete. Tristate values cannot be handled until customizing is corrected., #0:*, * R3=null ID=USER.PRIVATE_DATASOURCE.un:esptde, #1:null, #2:null, #3:null

I have been searching for a long time what could be wrong, without success. No mention of this error anywhere on the web, nor in the SAP notes database. Here's what I have tried already:

• I have checked of course that this phrase set existed, and that it contained the expected phrases, it seems OK.
• I have verified that the connection to ERP system is OK by doing an RFC trace, I can see a few function modules are called successfully.
• I have made sure connection to ERP system was done in English, to verify it was not a phrase translation issue.

If you have any idea at all, I am interested. I am very near opening a SAP message.

Thanks in advance.

Thomas

Hi All,

Need help on WWI template. Like in ABAP, to comment on a line, * (asterisk) can be inserted to comment the whole line, similarly is there a way to comment a line of code in WWI template. I want to comment a piece of code for now in a REACH template and make that code active later.

Any input will be appreciated.

Thanks,

Akash 

What is Business Add-In(BADI)?

A business add-in (BADI) is a source code plug-in provided by SAP to enhance existing ABAP code. The enhancement technique uses the object-oriented method and business add-ins to map the specific requirements involved in business process. These are customer specific, and are not provided by standard code in SAP. BADIs allow the system landscape to be multilevel (country-specific, industry-specific, partner-specific, customer-specific, etc.) and hence accommodate a wider range of solutions without affecting the original source code of the object.

1) BAdi :Create and Initialize PCBO (Process control business objective)

You can use this BAdI to implement customer-specific logic to adapt the processes in the system. You can use this BAdI, for example, if your organization must comply with regulatory requirements in more than one country or region. You can create a variation of the process for a specific country or region.

Requirements

You have specified process definitions in the Customizing activity specify process definitions for Foundation of SAP EHS Management.

You have performed a consistency check without errors in the Customizing activity List configured processes for Foundation of SAP EHS Management.

Standard settings

This BAdI does not have a default implementation

2) BAdi : Definition of Process Steps

You can use this BAdI to define the persons that are involved in the process step of a given work process.

The process can contain the following people:

• Responsible Person
• Implementor
• Approver

In the components of SAP EHS Management, there are specific processes that involve action. In these processes, workflow tasks are used to perform the work. You can use this BAdI to return the specific workflow task and to integrate your business processes.

Standard settings

In the standard system, the following BAdI implementations are activated:

• EHHSS_ACTION_BADI_IMPL (implementation for incident management)
• BADI_IMPL_EHHSS_RAS_ACTION (implementation for risk assessment)

The BAdI is filter-dependent and not designed for multiple use.

3) BAdi : Determination of Objects to Extract

You can use this BAdI to adjust the existing extractors or implement your own extractors. The extractors extract data to use in analytical reporting.You can also create a customer-specific BAdI implementation with logic, for example, to extract only the objects that have been changed since the last extraction of multiple objects.

Requirements

Each BAdI implementation corresponds to one or more DataSources. You have created the corresponding DataSources in RSA2.

You have configured the extractor for each DataSource in the Customizing activity configure extractors for SAP EHS Management under Foundation for EHS Management.

Standard settings

The BAdI definition is called once at the beginning of an extraction process.The BAdI definition contains the following methods:

• INITIALIZE

  This method implements the actual logic to determine the objects to extract. 

• GET_ITERATOR

This method returns an iterator object to iterate through the determined objects for further extraction of the objects' data.

BAdI Implementations

• BADI_EHFND_FW_BI_BOPF_OBJ_LIST

This implementation enables you to extract data from only one business object. The default implementation supports full loads by selecting all instances of the configured business object. The default implementation also supports delta loads by checking which instances of the configured business object have been changed since the last extraction.

3) BAdi : Extraction of One Object

You can use this BAdI to adjust the existing extractors or implement your own extractors. The extractors extract data to use in analytical reporting. You can also create a customer-specific BAdI implementation with logic, for example, to extract the data of one business object instance.

Requirements

Each BAdI implementation corresponds to one or more DataSources. You have created the corresponding DataSources in transaction RSA2.

You have configured the extractor for each DataSource in the Customizing activity configure Extractors for SAP EHS Management under Foundation for EHS Management.

Standard settings

The BAdI definition is called once for each business object instance to extract.The BAdI definition contains the following methods:

     INITIALIZE

This method enables you to perform any required initializations, for example, to evaluate the configuration. 

   EXTRACT_NEXT_OBJECT

This method reads and returns the data of one business object instance.

BAdI Implementations.

BADI_EHFND_FW_BI_BOPF_EXTRACT

The default implementation enables you to extract data from one node of a BOPF business object. You can use the BAdI, for example, to read data from multiple business objects nodes or from any other source, and combine the data in a transient node. The BAdI can then extract data from the transient node.

Note: You must create a customer-specific BAdI implementation for this extractor if you want to extract data from business objects that were not modeled with BOPF, or if you want the extractor to extract data from multiple nodes of a BOPF object that cannot be handled with one transient node.

4) BAdi : Electronic Report Shipment

You can use this BAdI to implement customer-specific logic for electronically shipping reports to a receiving party, for example, a legal authority, such as the Indian workers' compensation association. The BAdI allows you to adapt the report shipment process to company-specific requirements by enabling the use of different exchange formats and different channels of communication. You can, for example, use the BAdI if you want to send incident reports in an XML format via a Web service.

This BAdI is called before a report is sent to determine if a BAdI implementation exists for that type of report. If an implementation exists, you can choose to send the report electronically, and the system calls the BAdI again in the report shipment process. The BAdI then uses the SEND_REPORT method to do the following:

• Generate the report in the correct output format
• Ship the report to the receiving party
• Complete the shipment process by reporting the success or failure of the shipment back to the system.

Requirements

• You have configured the process foundation in Customizing for SAP EHS Management under Foundation for EHS Management -> Process Foundation. Ensure that the event linkage is active in activity Aciticate linkage for scheduled processes.
• You have configured the processes used in incident management, specifically the following process definition, in Customizing activity Configure process definitions:

  Component: HSS 

Purpose: INC_REPORT

Variant: STANDARD

• You have specified task recipients in Customizing activity assign default roles to workflow tasks.

Standard settings

The standard system does not include a default implementation for the BAdI.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

5) Integration of Financial Transaction Objects:

You can use this BAdI to enable access to cost collectors in other components for financial tracking. The components can either be managed locally or in a remote system.

This BAdI is delivered with active implementations for the following types of cost collectors:

• Internal order (Accounting (AC))
• Maintenance order (Plant Maintenance (PM))
• Service order (Customer Service (CS))

To enable access to other cost collectors, you can create additional BAdI implementations. The following methods are available:

• ADD_FIN_TRANS_OBJECT (Add Financial Transaction Object)

This method is executed when you add a financial transaction to an incident record. 

• DETAILS_FIN_TRANS_OBJECT (Display Details for Financial Transaction Object)
  This method is executed when you display the details for a financial transaction object.
• REFRESH_FIN_TRANS_OBJECT (Refresh Data for Financial Transaction Object)
  This method is executed when you refresh the list of financial transaction objects.

If this BAdI is implemented, you can assign cost collectors from integrated components as financial transactions to an incident record.

Note

If you have defined an enhancement including customer-defined dialog boxes for the application configuration EHHSS_INC_REC_OIF_V3, you can use implementations of the BAdI methods ADD_FIN_TRANS_OBJECT and DETAILS_FIN_TRANS_OBJECT to specify which dialog boxes are called when you assign cost collectors to an incident.

Requirements

• In the Customizing activity Specify Financial Transaction Categories, you have added a financial transaction category for each cost collector type that you want to use for financial tracking. You have selected the IntegrObj checkbox for these categories.
• If you want to use cost collectors in components that are managed in a remote system, you have defined the required RFC destinations in the Customizing activity Specify Destinations for Integration.

Standard settingsBAdI Implementations

• BADI_EHHSS_FIN_TR_INT_ORDER

This BAdI implementation enables access to internal orders that exist in Accounting.

• BADI_EHHSS_FIN_TR_MAINT_ORDER

This BAdI implementation enables access to maintenance orders that exist in Plant Maintenance. 

• BADI_EHHSS_FIN_TR_SRV_ORDER

This BAdI implementation enables access to service orders that exist in Customer Service.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

6) Check Readiness for Action

You can use this BAdI to perform checks on the following actions:

• Set status of a data record to Closed
• Set status of a data record to Void
• Set status of an incident investigation to Closed
• Set status of an investigation step to Closed

For each action, a BAdI implementation is delivered that you can use to perform the corresponding check in the standard system. If necessary, you can also deactivate the standard implementations and implement customer-specific checks instead. 

If you implement customer-specific checks, you must ensure that these are complete in terms of data consistency and legal requirements, for example, when generating legal reports based on the incident data.

Standard settings

The BAdI is active in the standard system.

BAdI Implementations

BADI_RDY_FOR_ACT_INC_CLOSE

You use this BAdI implementation to perform the following checks before the status of an incident is set to Closed:

• Check if the Restricted Access attribute for the incident is set to Yes or No
• Check if an incident group is assigned
• Check if the Investigation Required attribute is set to Yes or No
• If an investigation is required, check if the investigation is completed
• If the incident is an occupational incident, check if at least one involved person has the Injured Person role
• If the incident is classified as Release, check if at least one release is assigned
• Check if the Reporting Required attribute for a release is set to Yes or No
• Check if risk matrix entries are complete and confirmed
• If the incident is classified as a notice of violation, check if at least one notice of violation is assigned
• If the incident has actions assigned, check if all actions that are not recurring are complete
• Check if all inquiry processes are complete
• For any injured person, check if the Required in Summary Report attribute is set to Yes or No
• For any release of incident, check if the Reporting Required attribute is set to Yes or No

BADI_RDY_FOR_ACT_NM_CLOSE:

  You use this BAdI implementation to perform the following checks before the status of a near miss is set to Closed :

• If the near miss has actions assigned, check if all non-recurring actions are complete
• Check if all inquiry processes are complete

BADI_RDY_FOR_ACT_SO_CLOSE

  You use this BAdI implementation to perform the following checks before the status of a safety observation is set to Closed: 

• If the safety observation has actions assigned, check if all non-recurring actions are complete
• Check if all inquiry processes are complete

BADI_RDY_FOR_ACT_INC_VOID

BADI_RDY_FOR_ACT_NM_VOID

BADI_RDY_FOR_ACT_SO_VOID

You use these BAdI implementations to implement customer-specific checks that you want to perform before an incident, near miss, or safety observation is set to Void. The implementations do not perform any checks in the standard system. 

BADI_RDY_FOR_ACT_INV_CLOSE

You use this BAdI implementation to perform the following checks before the status of an investigation is set to Closed:

• Check if the Investigation Required attribute is set to Yes or No

• Check if an investigation lead is assigned

• Check if a major root cause is selected

• Check if all investigation steps are complete (status Closed, Void, or Completed)

  BADI_RDY_FOR_ACT_STEP_CLOSE 

You use this BAdI implementation to perform the following check before the status of an investigation step is set to Closed: 

For investigation steps with the step category EHHSS_ST_CAT_ROOTCAUS, check if all assigned actions are complete (status Closed, Void, or Completed).

7) Check Incident Reports

You can use this BAdI to perform checks for data completeness in incident reports.If you implement customer-specific checks , you must ensure that these are complete in terms of data consistency and legal requirements, for example, when generating legal reports based on the incident data.

If you deactivate or change a check, you must also ensure that all actions are complete or are in the process of completing.

Standard settings

  The BAdI is active in the standard system

8: BAdI : Investigation Lead Determination

By default, the investigation lead is automatically set to the current incident manager.You can use this BAdI to change how the default investigation lead is determined.

BADI : Determination of FTE and Working Time from PT

You can use this BAdI implementation to activate or deactivate the integration of Personnel Time Management (PT) for analytical reporting in SAP EHS Management(EHS-MGM). If you activate the BAdI implementation, the system determines the key figure values for Full-Time Equivalents and Working Time per organizational unit and calendar day from PT.

As only employee data is managed in PT, no key figure values are determined for external persons or business partners. To include key figures for external persons or business partners in analytical reports, you can create a customer-specific implementation of the Business Add-In Determination of FTE and Working Time.You can also use an implementation of this BAdI to determine key figure values according to company-specific determination rules.

Note

If you activate this implementation and an implementation of the BAdI Determination of FTE and WorkingTime, the system combines the results of both determination runs per employee, if appropriate.

Requirements

You have made the required settings for analytical reporting using the SAP NetWeaver Business Warehouse.

Standard settings

The BAdI implementation is active in the standard system.

9) BAdI: Determination of FTE and Working Time:

You can use this BAdI to determine the key figure values for Full-Time Equivalents and WorkingTime according to customer-specific rules. The key figures are determined for reporting purposes:

• Full-Time Equivalents: analytical reporting
• Working Timeanalytical reporting and legal reporting, for example, OSHA reporting

Note 

The key figure values for Full-Time Equivalents and Working Time values are always determined per organizational unit and date period. The system takes into account all objects (for example, employees or business partners) that are directly assigned to an organizational unit or that are assigned to a subordinate organizational unit.

Requirements

The following prerequisites must be met:

• You have made the required settings for analytical reporting using the Business Information Warehouse.
• You have specified the required forms for legal reporting in the Customizing activity Specify Formsfor Foundation for EHS Management.

Standard settings

The BAdI is not active in the standard system.

10 ) BAdI: Transfer of Incident Data to GRC

You can use this BAdI to transfer incident data from the incident management application to a remote SAP BusinessObjects governance, risk, and compliance solutions (GRC solutions), especially to the SAP BusinessObjects Risk Management component.

Use

This Business Add-In (BAdI) is used in the SAP EHS Management (EHS_MGM) component. You can use this BAdI to transfer incident data from the incident management application to a remote SAP BusinessObjects governance, risk, and compliance solutions (GRC solutions), especially to the SAP BusinessObjects Risk Management component.

To report incidents to GRC solutions, the BAdI proceeds as follows:

1. 1. It uses the method START_GRC_WORKFLOW to determine all incidents that must be reported:

a) It determines all incidents that have not yet been reported to GRC solutions.

b) It restricts the number of relevant incidents according to the selection criteria specified in the Customizing activity Specify Selection Criteria for Data Transfer.

Note: This method is delivered with the standard system and must not be changed.

1. 2. It uses the method SET_GRC_DATA to fill the predefined data structure and transfer the relevant data for each incident to the GRC solutions system.

The BAdI is called when you save an incident record.

Requirements

You have enabled integration with GRC solutions by activating the BAdI implementation BADI_EHHSS_INC_GRC_INT.

Standard settings

The BAdI is not active in the standard system.

11) BAdI: Finalization of Initial Creation of EHS Incident

12) BAdI: Creation of EHS Incident

13) BAdI: Creation of Attachment Folder for EHS Incident

14) BAdI: Creation of Release for EHS Incident:

15) BAdI: Creation of Involved Party for EHS Incident

16) BAdI: Finalization of Initial Creation of EHS Incident

17) BAdI: Creation of EHS Incident

18) BAdI: Creation of Attachment Folder for EHS Incident

19) BAdI: Creation of Release for EHS Incident

20) BAdI: Creation of Involved Party for EHS Incident

You can use this BAdI if you use an enterprise service for recording incidents. This BAdI changes or extends the data transferred through the message interface EHSIncidentFinaliseInitialCreationRequestConfirmation_In that is part of the EHS Incident Processing process component.

Standard settings

The BAdI is intended for multiple uses and is not filter-dependent.This BAdI uses the following methods:

• INBOUND_PROCESSING

  To enable you to integrate your own conversions, this method is called after the default mapping of the service-oriented architecture (SOA) request message to the EHS Incident. 

• OUTBOUND_PROCESSING

To enable you to integrate your own conversions, this method is called after the default mapping of the EHS Incident to the SOA confirmation message.

  This BAdI definition uses the IF_EHHSS_INC_FICRTRC_IN interface.

21) BAdI: Check Readiness for Action

You can use this BAdI to perform checks on the following actions:

• Set status of a data record to Closed

• Set status of a data record to Void

• Set status of an incident investigation to Closed

• Set status of an investigation step to Closed

For each action, a BAdI implementation is delivered that you can use to perform the corresponding check in the standard system. If necessary, you can also deactivate the standard implementations and implement customer-specific checks instead.

Caution If you implement customer-specific checks, you must ensure that these are complete in terms of data consistency and legal requirements, for example, when generating legal reports based on the incident data.

Standard settings

The BAdI is active in the standard system.

22) BAdI: Check Incident Reports

You can use this BAdI to perform checks for data completeness in incident reports.If you implement customer-specific checks , you must ensure that these are complete in terms of data consistency and legal requirements, for example, when generating legal reports based on the incident data.

Caution If you deactivate or change a check, you must also ensure that all actions are complete or are in the process of completing.

Standard settings

  The BAdI is active in the standard system

23) BAdI: Calculate Risk Rating and Determine Risk Icon

You can use this BAdI to adapt the standard logic to calculate risk ratings and to determine the risk icons that are displayed. The risk icons are set according to the risk rating. The risk rating is calculated for each affected area based on configurable scores for the following risk parameters: severity, likelihood to reoccur, frequency and duration. The calculated value can be manually overwritten by the user. The default logic for calculating risk ratings and determining risk icons is as follows:

• The scores of the affected areas are added.
• The rating is determined according to the lower and upper limit of the sum of scores.
• The risk icon is determined according to the risk rating configuration.

  The BAdI method calculate_risk receives the relevant risk type (initial or residual), the precalculated sum of risk scores, the distinctive scores for severity, likelihood to reoccur, frequency and duration, and returns the value for the risk icon.

Requirements

You have made the following settings in the Customizing for SAP EHS Management under Incident Management

Specify Affected Areas

Specify Severity

Specify Likelihood

Specify Frequency

Specify Duration Classifications

Specify Risk Ratings

Standard settings

This BAdI is active in the standard system:

24) BAdI: Data Transfer to Follow-Up Assessment

You can use this BAdI to copy data from an existing risk assessment to a follow-up risk assessment. The BAdI is called when you create a follow-up assessment, for example, to reassess identified risks after a regulation has changed.

The BAdI uses the method COPY_ALL_RISK to copy all relevant data. It creates a new risk revision for each risk that is copied to the follow-up assessment. This allows you to edit risk data in a follow-up assessment without changing the data that was originally recorded for the selected risk

Standard settings

The BAdI implementation EHHSS_COPY_ASSESSMENT_IMPL is delivered with the standard system

25) BAdI: Risk Level Calculation:

You can use this BAdI to determine the risk value and the risk level for an identified risk.

The BAdI uses the method CALCULATE_RISK to determine the risk level:

• It calculates the risk value by using a mathematical operator to combine the risk scores of the individual risk matrix dimensions:

• Severity
• Likelihood
• Exposure frequency

  Note: If you use a graphical risk matrix, the BAdI automatically determines the risk values for all possible combinations of risk scores that are included in the risk matrix. 

It determines the risk level that is specified for the calculated risk value in the Customizing activity Specify Risk Levels

Standard settings

The BAdI implementation EHHSS_RISK_LEVEL_CALC_IMPL is delivered with the standard system. This BAdI implementation calculates the risk value by multiplying the risk scores that have been specified for the individual risk matrix dimensions.

26) BAdI: Automatic Control Evaluation:

You can use this BAdI to provide automatic evaluation of the effectiveness of controls. In the application, the user can choose to evaluate the effectiveness automatically instead of manually entering the effectiveness or requesting a control evaluation be performed.

Standard settings

This BAdI does not have a default implementation.

The BAdI has the two following exporting parameters:

• Date of effectiveness evaluation (EHFND_DATE)
• Effectiveness code (EHHSS_CTRL_EFFECTIVN_CODE)

Common problems that BAdIs solve:

● Standard software – the customer wants specific changes but modifications cause problems.

The solution is a BAdI, a type of enhancement with a well-defined interface; BAdIs are more robust to changes than source code plug-ins.

● Different country and industry solutions need their own specific solution of a specified problem.

The solution is to create a BAdI definition in the core and the different countries can add their own implementations.

● You want to add and later choose parts of code dynamically.

The solution is to create an internal BAdI and add the different parts in different implementations. The BAdI and its implementations may belong to different software layers.

● As an SAP developer, you have a program in the SAP standard and want to give customers the chance to add some specific code of their own.

The solution is to include BAdI calls in the standard software. The customer can add the implementations of these objects later.

● You have a program which needs specific implementations for different countries.

The solution is to put the country-specific parts in BAdI implementations. These implementations can be overwritten later for the respective countries without modifying the original program that contains the BAdI calls.

● You want to program a registry.

It is possible to use the BAdI infrastructure to build a high-performance registry. In that case, the filter is used as selection criteria for the registry.

Edward.

Dear EHS Experts,

Please enlighten me if a dedicated PC is a necessity in installing WWI Generation Server? I have read that it is and I just wanted to know if it also can be made in windows server. During my testing, i have noticed that you can't completely save the template without error if you have edited it in the different windows PC. For example, you installed WWI generation server in PC1.a and you tried creating and saving the template in PC1.b. The creation and saving should be done in PC1.a to avoid the error. This is only my observation and if I'm going to relate it using windows server, the creation and saving should also be done there. Hope to hear from you. Thanks in advance!

Kind regards,

Mark

Hi all,

I have an Excel file of specifications that I would like to convert into a "hit list" in CG02. There is no criteria i can use in CG02 to reproduce this hit list, so at the moment, I only have it externally. I could not see a way to paste in all the specifications. Does anyone have an idea?

thanks

Hello,

We are facing a short dump- while executing the expert rules for e.g. ZEHS_GHS. It seems that some data conversion issue is there and the short dump indicated the affected FM is C1E7_BUS1077_GETDETAIL and the error it shows in details as Conversion error "IDENT_HEADER" from character set 4102 to character set 1100.

When I tried to delete Z4/Z6/Z3/Z5 language from the assigned HIS which is maintained as identifier. Then it worked correctly and there was no short dump.

Z3= Belgian French, Z4=Belgian Dutch, Z5= Brazilian Portugues, Z6=Puetro Rica Spanish.

Our SAP System is Unicode system and the expert rules was working for many year. Surprisingly the same issue is not seen in Dev and PPD environments. I tried to check number of OSS notes but nothing found which is close to this issue.

Please let me know if you have faced similar issue or having any inputs.

Regards,
Sachin

What is subtemplate in WWI layout templates? How do dependent WWI layout templates work? What is the difference between dependent and independent layout? how to test them both?

Hi Folks,

Can you please let me know what setting i need to do so that when ever i am in Tcode-CBGL_MP01 & do a label preview it would directly open in MS word application instead of word open in SAP window? Purpose of this is to get more print option as we get in our normal MS word documents as compared to when it it opened in SAP window.

I am aware of some setting which are applicable for DMS- INPLACE & OUTPLACE which are used to open thye DMS documents in & Out of the SAP in window but not sure if same would be applied here or if there are any setting in GLM for this?

Regards

Nishant.

Introduction

It seems to be that it is time to have a document in place for beginners in SAP EHS Management. This FORUM has showed that there is a regular need to support beginners. On High Level the most important Tipps and Tricks or Information should be collected and published.

Sustainability

SAP EHS Management as described here:

http://help.sap.com/erp2005_ehp_06/helpdata/en/a5/3adda043be11d188fe0000e8322f96/frameset.htm

is part of a bunch of applications of the SAP Sustainibility approach as described here:

http://www.sap.com/corporate-en/sustainability/index.epx

Training/Certification

• Trainings are offered e.g. by SAP or by other providers  (please check e.g. https://training.sap.com/v2/course/sus310-sap-ehs-management---essentials-and-functions-eef-classroom-096-de-de/)
• There is no certification regarding SAP EHS Management
  

SAP Marketplace

SAP EHS Management can be found easily in SAP marketplace. You can search for OSS Notes, try to understand differences between SAP EHS releases (e.g. based on different support package etc.)  and try to understand the use of Business Functions in SAP EHS.  Most important are OSS notes of type "Consulting", "Additional Information" or which deals with upgrades/updates.

There are some "must to read" OSS notes available regarding e.g.

1. WWI Cookbook
2. Report distribution
3. SVT installation
   

Licence model

SAP EHS Management is part of SAP ERP.  To understand the license model is not easy. Therefore use your SAP contacts for help to get better understanding.

SAP EHS Management Core

SAP EHS Management is implemented as an "SAP Extension" from technical point of view and therefore you need to prepare the software in your SAP ERP system and activate the extension before you can use SAP EHS Management. After activation you can activate further EHS relevant business functions (actually up to Enhancement Package 6 Business functions in the area of SAP EHS Management are available).

SAP EHS Management

There is no version number used in context of SAP EHS Management any more. It is part of SAP ERP. But there is some "conflict" with naming convention by SAP. Now SAP delivers as well a "Component Extension 3.0 (Component Extension 4.0 will come next) for SAP EHS Management" which does have actually a "version" number but is not the same as SAP EHS Management. This Component Extention is sometimes abbreviated as "EHSM" sometimes SAP EHS Management is called "EHSM". From technical point of view: you can not compare the old SAP EHS Management with the Component Extension solution.

SAP Best Practices for Chemicals

The use of the SAP Best Practise approach as shown here: http://help.sap.com/bp-chem can help to speed up if there if the need to prepare a "general" set up regarding SAP EHS Management. Therefore it can help to check as well: http://help.sap.com/bp_chem603/Chem_DE/HTML/index.htm

"Naming conflict"/"History"

Years ago there was a different term used. "EH&S". Generally you should now always use the term "SAP EHS Management" and you should not use the term EH&S any  more.

History of SAP EHS Management

SAP EHS Management is now part of SAP ERP as extension. In former times SAP EH&S (name used in the past) has been developed by TechniData. Here a short list of history (not intended to be complete)

• Completely part of: SAP ERP 6.0 EnhPack 6
• Completely part of: SAP ERP 6.0 EnhPack 5
• Completely part of: SAP ERP 6.0 EnhPack 3
• Completely part of ?: SAP ERP 2005
• Completely part of ?: SAP ERP 2004
• SAP EH&S 3.2 (SAP Enterprise Extension 2.0)
• SAP EH&S 3.1 (SAP Enterprise Extension 1.1)
• SAP EH&S 2.7b
• SAP EH&S 2.7a
• SAP EH&S 2.5b
• SAP EH&S 2.5a
• SAP EH&S 2.2b
• SAP EH&S 2.2a
• SAP EH&S 2.1b
• SAP EH&S 2.1a
  

For those who love history here some links (you will find more of that type):

May be check this link:

http://www.stechno.net/sap-notes.html?view=sapnote&id=122400

Books regarding SAP EHS Management

Only one book is available and only in german to deal with SAP EHS Management. Refer to: http://scn.sap.com/thread/3337768

Use of SAP EHS Management

SAP EHS Management is integrated very well in the SAP ERP processes. Normally it is not used as a "standalone" application/module. It support companies to be compliant regarding chemical products. The main integration points are:

1. SAP MM
2. SAP DMS
3. SAP SD
4. SAP PP
5. SAP QM
   

SAP EHS Management uses as well the SAP class/characteristic system.

For those who would like to start with SAP EHS Management these modules are of importance and therefore you should invest some time to understand the use of them and the relation to SAP EHS Management:

1. SAP MM (definition of the material master, assignment of material to specification; use of material classes)
2. SAP SD (basic know how needed because of e.g. SDS/MSDS distribution and Dangerous Goods Management integration)
3. SAP DMS (basic know how needed to understand how e.g.  WWI reports are managed (stored) in SAP; it is recommended that you should have basic know how in the area of "ArchiveLink" and similar solutions
   

Further links regarding Sustainability

Check may be:

• http://www54.sap.com/solution/lob/r-and-d/software/overview/highlights.html
• http://www54.sap.com/solution/lob/sustainability/software/overview/highlights.html
• http://www54.sap.com/solution/lob/sustainability/software/overview/supply-chain.html

Sustainability Solutions

This section is intended to provide short links to SAP documentation. It is not intended to be complete etc.

Basic Data and Tools

To start with SAP EHS Management one need to understand submodele called EHS-BD. I found this nice link helping to understand the "basics":

http://www.authorstream.com/Presentation/rsasirao-112369-sap-ehs-basic-data-tools-education-ppt-powerpoint/

Frequently Asked Questions

This section is intended to help beginners to find easily a thread in this FORUM which might help regarding the issue. This section will grow step by step. Ideas of topics which should be collected can be added based on feedback of community.

Reference to other documents in SCN

Blog Posts

Component Extension for SAP EHS Management

Component Extension for SAP EHS Management is a new bundle of functions. This new solution can not be compared with SAP EHS Management "classic" and is implented different. The scope and the technology used is different but scope does have some overlap with old solution sof SAP. To a certain extent part of SAP EHS Management "classic" can be used if you start with the Component Extension. Discussion in several threads in this FORUM showed that SAP will "reorganize" their applications. Therefore some old functions will not be developped any more but money / time etc. will be invested in the Component Extension. Please check carefully this FORUM. A number of useful hints are provided regarding installation of the new solution, migration topics etc.

GLM

Discussion in thie FORUM showed that SAP is restercturing, enhancing the GLM solutions. Last update has been done with Enhancement Package 7. Some TechniData solutions seems to be still supported by SAP using the SAP Consulting service. Especially the new options in Enhancement Package 7 are worth to be studied if you need to implement GLM. Especially the topic "how to install WWI ocrrect" is a "problem" in this context. Because of recent dicussions in this FORUM some links to "Bar Code" discussion taking place in this FORUM has been added.

MSDS/SDS/XML

On an irregular level discussion is coming up if it is possible to "convert" a WWI related MSDS/SDS into XML for data exchange. To make it short: there are options to do so but there is lack of availability of XML schemata. Here I have the feeling that people believe XMl is something like "TXT", "DOC", "PDF" etc. To a certain extent this is correct but in context of MSDS/SDS and data exchange this is wrong. The main "issue" here is: data exchange can be only done if sender and receiver talk the same language. Examples of data interchange options via XML is the "IUCLID" format. Here you need to prepara a XML data stream according to the rules of ECHA. And this is the "crucial" issue in exchange of data using XML. The XML file content must "fit" a XML schemata. (there is a "rule" to do so). But there is a trend on chemistry / legislation etc. to use XML as the "data format (but per "legislation" there is a different rule in place) and clearly if you look close on SAP functionality you can generate XML (there are n number of options to do so).. But e.g. if you would like to exchange a US related MSDS and an European MSDS via XML you have a different internal structure etc. Here we have now to a certain extent the link to WWI. WWI is used to "collect" together the dat for US MSDS and EU MSDS. Using XML in theory you can do the same but because of lack of "common" rules (as with the IUCLID format) you can not use XML generally to exchange MSDS/SDS data.

Dear EHS Community: please go on in preparing documents and blogs !

Any idea to improve this section is appreciated. Please provide ideas regarding topic or subtopic so that may be beginner can find more easily the answer.

Please help to improve so that Beginners in SAP EHS Management are supported. What do you Beginner in SAP EHS Management need as a "starter package"?

This is my personal list of those topics which are asked for very often:

• WWI (layout topics, server installation)
• How to use WWI to define e.g. MSDS/SDS layout
• MSDS generation (e.g. what are the steps required etc.)
  
• Report distribution (e.g. general set up; distribution of inbound documents)
• Dangerous Goods (filling, checks)`
• GLM (e.g. label scenario); GLM Bar Code printing; synchronous WWI server
• CG02 extensions (e.g. use of output variants)
• Where used list (compositions)
• CG50/CG54 (e.g. download by mass of documents, portal solutions)
  
• Regulatory content; how to use etc.
• How to start with EHS? What are the customizing steps etc.
• Use of "Component Extension" (how to install etc.)

It is recommended to use the "search" functionality in SDN to check if your problem has been discussed yet. It is not intended to have a "100 % "FAQ section here and not 100 % quality (that means a thread can appear e.g. twice etc. in one section).

Introduction

In context of SAP EHS Management (classic) changes in the software are delivered by SAP using either a:

• Support Package
• or Enhancement Package

The strategy of SAP is "easy" but sometimes misinterpreted.

A support package combines simply:

• a list of error fixes
• and can contain new software based on legal demand (e.g. REACh...)

An Enhancement Package contains "add on software" which enhances the functionality but is not legal driven.

By experience:

SAP is roughly providing two support packages per year. Regarding new "Enhancement Package": roughly once a year a new EnhancementPpackage is available but this neednot always enhance EHS (e.g. no extension happened in Enhancement Package 1 and 4 regarding EHS).

The test approach regarding the delivery of a "Support Package" and an "Enhancement Package" is different. Regarding an Enhancement Package a more intensive test of the new software is done and a ramp up phase is used.

In context of SAP EHS Management new features are delivered with:

• Enhancement Package 3
• Enhancement Package 5
• Enhancement Package 6
• Enhancement Package 7 (not available yet for customers; SAP online Docu is up to date !)

Any of these "lines" does have a "separate" line of Support Packages (please check SAP marketplace and check the corresponding line and availability of a support package)). Therefore to get "state of the art" software (including legal changes) you need "only" download the recent combination of Enhancement Package / Support Package. There is only one important "but":

To make use of the new features, you must activate via customizing the corresponding Business Function. After doing that you can get updates in customizing; delivered are sometimes "default" implementations of the new features but not in all cases. Only within a project you can make sure which of the new features should be used and how etc. If you are planning to use one of the new feature you need to have a "plan" to analyse what is new, how to use the new feature; then to develop test etc. the new stuff.

Now what are the reasons to use the functionality (in theory you can use SAP ECC 6.0 with out any ! Enhancement Package and you can still fulfill all legal requirements):

Main drivers are the new features. If you use them properly you can gain new benefits and save money.

If you check: http://help.sap.com/erp2005_ehp_06/helpdata/en/bf/57cec7cb1343f4877cb762029876ce/content.htm?frameset=/en/46/4afb86d8d551ede10000000a114a6b/frameset.htm

Chapter "Environment, Health and Safety" and subchapters you will realize that there are these business functions available:

Especially the improvements in the area of GLM, SVT and CG02/CG02BD but DG as well are reasons why a company should check if there is a benefit in installing the software and activating the business function.

At the end you need a project to select the right function to be used and to describe how it should be used etc.

Component Extension

Regarding enhancement options here: please check: http://scn.sap.com/docs/DOC-45836#comment-386163

I have run t_code: ehfnd_wff_system_chk and all is ok.

1. error for http destination for SAP_EH_FW_WFF_REPORT_TARGET - what settings are required in sm59 for this?

2. All setting seem ok,but after nwbc is excuted with html file, I get an error when I wan to edit the incident (incident recording is working fine). Error on browser: "SET_IN_PROCESS_ROOT" is not enabled. Exception occurred: Error calling the function module to create the fo

Cannot find any sap notes on this. Does anyone come across this? Please assist if you.

Thanks