SAP ABAP IMG Activity EHS_MD_120_30_2 (Set Up Classes)

Hierarchy

☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS (Application Component) Environment, Health and Safety
     ⤷ CBIMG1 (Package) EH&S: IMG Migration

IMG Activity

ID	EHS_MD_120_30_2	Set Up Classes
Transaction Code	S_SH8_72001024	IMG Activity: EHS_MD_120_30_2
Created on	19990122
Customizing Attributes	EHS_MD_120_30_2	Set Up Classes
Customizing Activity

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	EHS_MD_120_30_2

Required Classes

Generate a list of all classes (property tables) that are to be managed in EH&S. In this phase, you do not have to specify exact characteristics for a class. Define the properties by name and description. Examples of possible properties are:

• Melting point
• Flash point
• First aid measures
• Ecotoxicity

Note the following: several data records within a class can no longer be processed selectively. The granularity of the class structure also determines the selectivity.

Example:

If you create a class "status changes," you can no longer treat the "melting point" or "boiling point" data records in this class selectively. In a report, melting points and boiling points can therefore no longer be listed in separate chapters within a report. They can only be listed together in sequence.

If you display melting points and boiling points in two separate classes, you can output them separately. The smaller the granularity, the more selectively you can process your data.

General selectivity in EH&S reporting is controlled via class. You can enhance selectivity via "usage." The example above, however, remains valid under "usage."

Constructing Class Hierarchies

By constructing class hierarchies, characteristics and their attributes, like possible class values, for example, can be inherited by other classes. You can define a "super type" for similar classes and use it to define subordinate classes. You can enter the following data for subordinate classes:

• Additional characteristics
• Different permitted values

To construct possible class hierarchies, the classes must be checked to ensure that the characteristics are consistent. Characteristics should be consistent semantically as well as in type. Characteristics common to classes that can be merged can then be merged into their own classes. Characteristics that do not appear in different classes remain in their original class.

Examples for Setting Up Class Hierarchies

• Example "status change"
• Definition without hierarchy:
Class melting point with characteristics: value, method, env. pressure
Class boiling point with characteristics: value, method, env. pressure
• Definition with hierarchy:
Class status change with characteristics: value, method, env. pressure
Class melting point: all characteristics inherited via class status change
Class boiling point: all characteristics inherited via class status change
• Example "toxicity"
• Definition without hierarchy:
Class acute toxicity with characteristics: type (LD50, LD10,...), species, dose
Class chronic toxicity with characteristics: type (semi-acute, chronic, ...), species, dose, exposure time
• Definition with hierarchy:
Class toxicity with characteristics: type, species, dose
Class acute toxicity: all characteristics are inherited via class toxicity
Class chronic toxicity: all characteristics of the class toxicity, the characteristic exposure time remains directly in the class chronic toxicity
• Contrasting example:

  Dynamic and kinetic viscosity can be described in terms of value, method, environmental temperature. For dynamic viscosity, the value is defined in Pascal seconds. Kinetic viscosity uses square meters/second. This could not be made into a hierarchy.

Standard settings

Default settings are delivered.

Activities

Create the required classes in Classification. Enter 100 as the class type.

Business Attributes

ASAP Roadmap ID	203	Establish Master Data
Mandatory / Optional	2	Optional activity
Critical / Non-Critical	1	Critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	EHS_MD_120_30_2	0	HLA0003436 O
SIMG	EHS_MD_120_30_2	1	ALR0000066 O
SIMG	EHS_MD_120_30_2	2	SH10000009 O
SIMG	EHS_MD_120_30_2	3	SH10000011 O
SIMG	EHS_MD_120_30_2	4	SH10000012 O
SIMG	EHS_MD_120_30_2	5	SH10000016	Injury/Illness Log
SIMG	EHS_MD_120_30_2	6	/PLMI/E5C0000032

Maintenance Objects

Maintenance object type

History

Last changed by/on	SAP	20091006
SAP Release Created in	46C