SAP ABAP IMG Activity EHS_MD_120_10_10_0 (Protect Characteristics Within Namespace)
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_10_10_0 Protect Characteristics Within Namespace  
Transaction Code S_SH8_72000946   IMG Activity: EHS_MD_120_10_10_0 
Created on 19990122    
Customizing Attributes EHS_MD_120_10_10_0   Protect Characteristics Within Namespace 
Customizing Activity EHS_MD_120_10_10_0   Protect Characteristics Within Namespace 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_MD_120_10_10_0    

In this IMG activity, you protect characteristics of namespaces whose keys start with EHS_. These define specification management characteristics and distinguish them from all other SAP System applications. This setting prevents conflicts that may occur if you create characteristics in two different clients or systems.

The usage of the EHS namespaces thus enable you to:

  • Centrally define basic settings for characteristics (value assignments). You can then distribute these settings to remote productive systems.
  • Create a protected system area that allows you to import precustomized system configurations.

You also configure the system reaction to the processing of characteristics (error or warning message, no reaction).

Example

You configure specification management in client A while you implement another application (for instance PM) in client B.

The use of an EHS namespace ensures that no name or characteristic conflicts arise in a productive client that contains both the Customizing settings you made in clients A and B.

Standard settings

A default error message is generated whether you have specified a namespace or not.

Further notes

Note the following points:

  1. Characteristics whose key starts with EHS_ should be assigned to class type 100 (value assignments).
  2. If you define a number of namespaces, you should use a unique key for each namespace. Otherwise, the system will always revert to the more general key:
    For example:
    If you define: namespace 1 = EHS_A and namespace 2 = EHS_AB, the system accesses only the namespace 1.
    If you define: namespace 1 = EHS_A and namespace 2 = EHS_B, the system recognizes two different namespaces.

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_10_10_0 0 HLA0003436 O  
SIMG EHS_MD_120_10_10_0 1 ALR0000066 O  
SIMG EHS_MD_120_10_10_0 2 SH10000011 O  
SIMG EHS_MD_120_10_10_0 3 SH10000012 O  
SIMG EHS_MD_120_10_10_0 4 SH10000009 O  
SIMG EHS_MD_120_10_10_0 5 SH10000016 Injury/Illness Log 
SIMG EHS_MD_120_10_10_0 6 /PLMI/E5C0000032  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
ESV_TCGK1 V - View SM30 EHS_01 Protect Characteristics Within Namespace 
History
Last changed by/on SAP  20091006 
SAP Release Created in 46C