Kontakt

Ansicht
Dokumentation

R_EHFND_MIGRATE_CHM - Program R_EHFND_MIGRATE_CHM

R_EHFND_MIGRATE_CHM - Program R_EHFND_MIGRATE_CHM

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

When you convert from releases 2.0 or 3.0 for the component extension for SAP EHS Management to Environment, Health, and Safety, you must run this report before using a chemical in the application due to changes in the data model for chemicals.

Integration

Prerequisites

You have converted from releases 2.0 or 3.0 for the component extension for SAP EHS Management to Environment, Health, and Safety. You have assigned hazard statements to hazard classes/hazard categories in the Customizing activity Assign Hazard Statements to Hazard Classes/Categories.

Features

In Environment, Health, and Safety, it is possible to create revisions of a chemical. To enable the use of revisions, a new revision node was added to the business object (BO) structure directly under the root node. The report creates a revision note for chemicals used in releases 2.0 and 3.0, moves all other existing nodes under this revision node and sets the status of the revisions node to the status stored at the root node.
Note: As of Environment, Health, and Safety, the status field of the root note is no longer used; it is marked as deprecated.

Selection

You can select the following options if you run the report in interactive mode:

  • Run in Test Mode: If you select this checkbox the report does not convert any data but creates a list with messages to give an overview about warnings or errors occurred during processing.
  • Chemicals per Bundle: You can enter a number of chemicals that are processed together in one bundle. After finishing processing the specified number of chemicals, the system moves the data into the new structure. Then, the next bundle is processed.
    If an error occurs within the processing of a bundle, the report creates an error message and discards all detected changes to be made for the processed chemicals.
    Regardless of the entered value for a chemical bundle, the report always converts all existing chemicals used in releases 2.0 and 3.0.

Standard Variants

Output

Due to the change in the data model for chemicals, the report makes the following adoptions to chemical data used in releases 2.0 and 3.0 for the component extension for SAP EHS Management:

  • Converting hazard classifications
In releases 2.0 and 3.0, the hazard classification could be used to classify chemicals according 67/548/EEC or 1999/45/EC, or according to the Globally Harmonized System regulation (GHS). In Environment, Health, and Safety, these classifications are divided into different sections. During processing, the report moves the data used in releases 2.0 or 3.0 to the hazard classification according to GHS.
Note: If you have used these Customizing tables for other classification data than for GHS classification, your data will not be converted by the report; you have to enter the data manually in the application.
  • Assigning hazard statements to hazard classes/categories
In releases 2.0 and 3.0, there was no technical relationship between hazard classes/hazard categories and hazard statements. In Environment, Health, and Safety, the hazard statements are assigned to hazard classes/hazard categories in the Customizing activity Assign Hazard Statements to Hazard Classes/Categories.
During processing, hazard statements have to be assigned to a hazard class/category. To create an assignment, the report checks the hazard statements and the hazard classes/hazard categories for a chemical used in releases 2.0 and 3.0 and compares this data with the assignments made in Customizing activity Assign Hazard Statements to Hazard Classes/Categories. Depending on the data for a chemical used in releases 2.0 and 3.0, assignments are made in Environment, Health, and Safety as follows:
  • If a hazard statement used in releases 2.0 and 3.0 is assigned in the Customizing to a hazard class/category that is also used in the chemical, the hazard statement is assigned to this hazard class/hazard category.

  • If a hazard statement used in releases 2.0 and 3.0 is assigned in the Customizing to multiple hazard classes/categories and these are used in the chemical, the hazard statement is assigned to the hazard class/category that is processed first.

  • If a hazard statement used in releases 2.0 and 3.0 is assigned in the Customizing to a hazard class/category that is not used in the chemical, this hazard class/category is added to the chemical and the hazard statement is assigned to this newly added hazard class/hazard category.

  • If a hazard statement used in releases 2.0 and 3.0 is assigned in the Customizing to multiple hazard classes/categories and none of them are used in the chemical, the hazard class/category that is processed first is added to the chemical and the hazard statement is assigned to this newly added hazard class/hazard category.

  • If a hazard statement used in releases 2.0 and 3.0 is not assigned in the Customizing to any hazard class/category, the report creates an error message and discards all detected changes to be made for the processed chemicals.

Note: If a chemical used in releases 2.0 and 3.0 contains hazard classes/categories and no hazard statements, the hazard classes/categories will be converted without any hazard statement assignment.

  • Handling attached documents
In releases 2.0 and 3.0, the node used for attaching documents was under the basic information node. For Environment, Health, and Safety, this attachment folder node has been moved directly under the root node and outside the revision node to handle documents revision independent from chemical revisions. During processing, the report moves the attachment folder node under the root node. All documents stored in the attachment folder node remain untouched.
In the new structure, links are not actively supported any more. If you have entered links instead of documents, the links will be converted to the new structure during processing, they will be displayed in the application, but it will not be possible to enter new links.

  • Setting chemical types
In Environment, Health, and Safety, a new field for the type of a chemical is implemented. Chemicals used in releases 2.0 and 3.0 do not have such information. During the conversion, the report set the chemical type to "undefined". When you open the chemical in the application, you will be asked to decide whether this chemical is a substance or a mixture. The system uses this information to determine if special chemical identifiers, like CAS number or IUPAC name, need to be provided.
  • Handling additional information for hazards
In releases 2.0 and 3.0, a chemical agent provided the following additional information for hazard and impacts related to the chemical:
  • Attributes IMPACTS_DESC, HAZARD_CATEGORY, and AGENT_SOURCE in BO node BASIC_INFORMATION

  • All attribute in BO node IMPACT


This information was used for integration into the health and safety management component. Since Environment, Health, and Safety provides an extended integration into the health and safety management component, these fields are no longer used. Information stored in these fields will not be converted into the new data structure.

Activities

Run the report just after the conversion from release 2.0 or 3.0 for the component extension for SAP EHS Management to Environment, Health, and Safety. Run the report after configuring the Customizing for chemicals but before using the chemicals in application.

You can restart the report as often as you like. The report detects chemicals that were used in releases 2.0 and 3.0 by the node structure in the business objects: for these chemicals, the basic information node in is linked to the root node, while the basic information node of chemicals used in Environment, Health, and Safety is linked to a revision node in the BO. Chemicals that have the revision node will not be changed by the report.

After finishing the conversion of the chemicals to the new structure, you get a list of all messages that occur during processing. You can check the messages to see how the system converted the data for your chemicals.

Note:After a conversion from releases 2.0 and 3.0 to Environment, Health, and Safety, it is necessary to build the index for the search function for chemicals. Therefore, this report automatically calls the report R_EHFND_CHM_SEARCH_IDX_CREATE if any chemical has been converted.

Example

You used 10 000 chemicals in component extension 3.0 for SAP EHS Management and want to convert these chemicals to the new structure of Environment, Health, and Safety.
You set the value for chemicals per bundle to 10 000 and start the report. An error occurs after processing 9000 chemicals, the report will be terminated and all chemicals remain unchanged.
If you set the value for chemicals per bundle to 100 before starting the report and the error occurs after processing 9000 chemicals, the report will also be terminated. But 8900 chemicals were converted to the new structure and only 1100 chemicals will remain unchanged.






General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 11339 Date: 20240520 Time: 131628     sap01-206 ( 216 ms )