Kontakt

Ansicht
Dokumentation

Creating Extended Safety Data Sheets (Changed) ( RELNEHS_606_EHSCI3_ESDB )

Creating Extended Safety Data Sheets (Changed) ( RELNEHS_606_EHSCI3_ESDB )

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Creating Extended Safety Data Sheets (Changed)

Use

As of SAP enhancement package 6 for SAP ERP 6.0 (EA-APPL 606), you can create extended safety data sheets (eSDS) that comply with European REACH and GHS legislation. In addition to the main part, these safety data sheets contain an annex with the exposure scenarios that can be filtered for specific customers or materials.

The following components have been extended to include new functions for creating extended safety data sheets:

  • Substance Workbench
  • Report Definition
  • Report Administration
  • Report Shipping

In the Substance Workbench, the uses and exposure scenarios that are relevant for a substance are specified in the Use and Exposure Scenario (SAP_EHS_1027_001) value assignment type of the standard property tree. This data is included in the annex of the extended safety data sheet.

Report Definition component:

The following functions for supporting the creation of extended safety data sheets have been added to the Edit Report Templates (CG42) transaction:

  • Data output is controlled by a master group with instance control (MIC repeating group) and possibly an MIC:POS repeating group (master group - positions of instance control).
  • The master group with instance control (MIC repeating group) initially subjects the value assignment instances to a usage check. Instance control is then carried out when the report body and final report are generated:
  • As with master groups (M), all of the value assignment instances are initially selected for inclusion in the report when the report body is generated. All of the specification symbols contained in the MIC repeating group are resolved. At the same time, a control structure is created to carry out the instance control for the report body.

  • The instance control takes place when the final report is generated: All of the value assignment instances output when the report body was generated are evaluated by certain output rules. You can choose these output rules by selecting a report view in the Maintain Report View and Object Key dialog box (see comments on the Report Administration component). Depending on the result of the evaluation, the characteristic values output when the report body was generated are not included in the final report. The value assignment instances that are output are evaluated using the values stored in the control structure.

  • Output of the exposure scenarios defined for the substance is controlled in the report template by means of the MIC:POS repeating group. The MIC positions that are assigned to the value assignment instances in the Use and Exposure Scenario value assignment type are output in the report.
  • Using the symbols for instance control, you specify in the report template the position in the extended safety data sheet at which the data for the exposure scenarios is listed.. These symbols are nested in MIC repeating groups or MIC:POS repeating groups.
  • The master group with instance control is supported by the WWI wizard. When you select the With Instance Control checkbox in the WWI wizard, an MIC repeating group (master group with instance control) is inserted in the report template instead of a repeating group of type M.

Report Administration component:

New functions for creating extended safety data sheets (eSDS) are provided as symbols in the report administration report tree:

  • Symbol Display eSDS on Front End - Does Not Contain Customer-/Material-Specific Data: The report and eSDS annex are displayed in Microsoft Word. To display the report, you have to choose a report view in the Maintain Report View and Object Key dialog box. The parameter values for Customer and Material are not taken into consideration when the data is output.
  • Symbol Display eSDS on Front End - Contains Customer-/Material-Specific Data: The report and eSDS annex are displayed in Microsoft Word. To display the report, you have to choose a report view in the Maintain Report View and Object Key dialog box and enter parameter values for the Customer and Material.

You use the Maintain Report View and Object Key dialog box to generate the final reports for extended safety data sheets and control the structure and layout of the final report using report views. For this purpose, the report must no longer have Report Request (RA) status and the report template must contain an MIC repeating group (see comments for the Report Definition component).

Depending on the report view selected in the Maintain Report View and Object Key dialog box and the output rules defined for the report views, you can hide certain uses and dependent exposure scenarios when the final report is generated. In this case, these do not appear in the final report. The output rules relate to value assignment instances that contain information about uses and dependent exposure scenarios and apply only to objects that are output by means of a master group with instance control (MIC repeating group; see comments on the Report Definition component). The final contents of the report, therefore, are not defined until the final report is generated.

In the standard system, the data is filtered according to specific characteristics of the value assignment type Use and Exposure Scenario (SAP_EHS_1027_001), depending on the report view, when the final report is generated.

The following report views are available:

Parameter Value Description of the Report View
ALL eSDS annex with all data
NON Main part (no eSDS annex)
OWN eSDS annex with own uses
STD eSDS annex with standard uses
CUS eSDS annex with customer-dependent uses
MAT eSDS annex with material-dependent uses

Report Shipping component:

  • It a report contains sections or annexes with contents that can be controlled, you have choose a report view in the Maintain Report View and Object Key dialog box when you send a report manually. An instance control uses this report view to control which data is output in the final report (see comments on the Report Definition component).
  • In the following cases, the report view is set automatically to Customer-Dependent (CUS). This means that customer-specific and/or material-specific uses are output in the eSDS annex:
  • When the automatic report shipping order is generated

  • When a report is shipped subsequently for which the report view has not been defined

  • When the report shipping order is checked (exit type CHECK), the standard function modules take into consideration the report view for automatic report shipping (SD interface). This means that all reports that have the same version but a different report view are enabled for shipping. The relevant standard function modules have been extended.
  • If a report shipping order without a report view has already been sent when the report shipping order for automatic report shipping is checked, the report view is not taken into account in the check. In this case, a report is not sent twice by the automatic report shipping function.
  • The Report Shipping Orders screen contains the search function Shipping Order with Exposure Scenario in the Restricting Search Criteria group box. This search function takes into account only shipping orders that contain final reports and in which the specifications are output as an exposure scenario and for a use. The search for shipping orders with an exposure scenario, however, only functions if the exposure scenario was output in the final report with a repeating group with instance control. This search function is provided by the user exit SRS_QUERY SRS_EXP in the standard system.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

  • The standard system features a BAdI implementation for the value assignment type Use and Exposure Scenario(SAP_EHS_1027_001), which implements the report view for the eSDS generation. The instance control must be implemented for each value assignment type using the BAdI BAdI: Implementations for Repeating Groups with Instance Control and the associated BAdI methods.
  • The update of the control structure for generating the final report can be activated or deactivated in the Customizing activity Specify Environment Parameters using the environment parameter REP_IC_NOCSUPDATE.
  • Customizing activity Manage User Exits: To initialize the search function Shipping Order with Exposure Scenario, use the user exit SRS_QUERY SRS_EXP.
  • The following settings are provided in Customizing:

The contents of the specified tables must be synchronized with all clients in which extended safety data sheets are created.

Further Information

  • SAP Note 1146700 - Transferring the standard database structure: This SAP Note describes how the changes to classes and class types in the value assignment type Use and Exposure Scenario are transferred to the relevant clients.
  • For more information, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com under
  • SAP ERP Central Component -> Logistics -> Environment, Health and Safety (EHS) -> Basic Data and Tools (EHS-BD) -> Specification Management (EHS-BD-SPE) -> Specification Editing -> Value Assignment

  • SAP ERP Central Component -> Logistics -> Environment, Health and Safety (EHS) -> Basic Data and Tools (EHS-BD) -> Report Definition (EHS-BD-RDF)

  • SAP ERP Central Component -> Logistics -> Environment, Health and Safety (EHS) -> Product Safety (EHS-SAF) -> Report Management (EHS-SAF-REP)

  • SAP ERP Central Component -> Logistics -> Environment, Health and Safety (EHS) -> Product Safety (EHS-SAF) -> Report Shipping (EHS-SAF-RSH)






Addresses (Business Address Services)   General Material Data  
This documentation is copyright by SAP AG.

Length: 15025 Date: 20240520 Time: 222655     sap01-206 ( 246 ms )