Show TOC

  Data Selection by Usage

When you call the EH&S Expert, one or more usages (rating and validity area) are specified as selection criteria for the specification data to be read. See the documentation on the IMG activity Extend Entry in Secondary Data Determination . Only the data whose usage matches the global requirement is read.

It is, however, also possible to define differing usages in a set of rules as selection criteria for certain facts, records, or compositions in mapping using the /USAGE option. An example could be a set of rules that is to read data with the usage PUBLIC REG_WORLD as a general rule, but for a specific fact should only read data from PUBLIC DE (for example, German water pollution class).

Configuration

The possible validity areas and their hierarchy are specified in Customizing. As from EH&S Release 2.5B SP4 and 2.7A or newer, the EH&S Expert reads the Customizing settings directly from the SAP system. Any changes in Customizing only come into effect when the EH&S Expert server process is restarted because, for performance reasons, the data is read only once at the start.

Local Configuration

In older EH&S Releases, the information cannot be read directly from the SAP system. In this case it must be stored locally on the Expert PC.

Setting up a local configuration of this type is basically done in two steps:

  • Exporting the table TCG93 from the respective client of the SAP EH&S system and adapting the configuration file in accordance with the specified syntax

  • Setting the registry parameters for the EH&S Expert using the EH&S Expert Administration Tools

Exporting the Table TCG93
  1. Start the transaction se11 (Dictionary Initial Screen).

  2. Display the database table TCG93 .

  3. To display the table contents unfiltered, choose Start of the navigation path Utilities Next navigation step Table contents End of the navigation path .

  4. To export the table unconverted, choose Start of the navigation path System Next navigation step List Next navigation step Save Next navigation step Local file End of the navigation path .

  5. Assign a file name.

Structure of the Configuration File

The name of the configuration file can be chosen as required. The syntax of the configuration file is described below. The | character is used as a separator between the columns. Any spaces between the column separators and the codes are ignored. The example shows the structure of the configuration file for an EH&S 2.7 system.

Line

<Comment>

or

|<rvlid>|<land>|<region>|[<detail_rvlid>|]

<Comment>

A comment is introduced by the number sign # at the beginning of the line.

<rvlid>

Code for an EH&S validity area , for example, REG_EU

<land>

Country code that is assigned to a validity area, for example, US for United States

<region>

Code that, together with the country code, describes a region that is assigned to an EH&S validity area, for example, DE and 08 for Germany, Baden-Wuerttemberg

<detail_rvlid>

EH&S code that describes a plant , which is assigned to an EH&S validity area

Example of a Configuration File

#################################################################

# Purpose: Customizing of the val. area codes within EH&S#

# to enable local usages within EH&S Expert sets#

# of rules other than the global read usage. #

# #

# Parameters: #

# RVLID EH&S validity area code, e.g. REG_EU #

# LAND1 Country code, e.g. DE #

# REGIO Region code, e.g. Bavaria #

# DETAIL_RVLID Code describing organizational units #

# (EH&S version >= 2.7) #

# #

# System : SH1 #

# Client : 011 #

# #

#--------------------------------------- #

#|RVLID |LAND |REGIO|DETAIL_RVLID| #

#--------------------------------------- #

#################################################################

|49CFR |US | | |

|BAVARIA |DE |09 | |

|BE |BE | | |

|BW |DE |08 | |

|CN |CN | | |

|DE |DE | | |

|DK |DK | | |

|FI |FI | | |

|FR |FR | | |

|GB |GB | | |

|NWÜRTT |DE |08 | |

|OALB |DE |08 | |

|REG_EU |AT | | |

|REG_EU |BE | | |

|REG_EU |DE | | |

|REG_EU |DK | | |

|REG_EU |ES | | |

|REG_EU |FI | | |

|REG_EU |FR | | |

|REG_EU |GB | | |

|REG_EU |GR | | |

|REG_EU |IE | | |

|REG_EU |IT | | |

|REG_EU |LU | | |

|REG_EU |NL | | |

|REG_EU |PT | | |

|REG_EU |SE | | |

|SSCHW |DE |08 | |

|US |US | | |

|US-O |US |WY | |

#---------------------------------------

Registry Parameters

The Customizing table TCG93 is system-specific and client-specific. The following scenarios are therefore possible:

  • Using the registry parameter UsageData_<Mandant> for the destination that corresponds to the SAP system in the EH&S Expert administration tool, the configuration file is assigned to one client only within an SAP system, where < Mandant > is the number of the SAP client.

  • If the contents of the table is identical in all clients of an SAP system, the same configuration file can always be used by using the registry parameter UsageData for the destination that corresponds to the SAP system in the EH&S Expert administration tool.

  • By setting the registry parameter UsageData in the Global Settings tab in the EH&S Expert administration tool, it is possible to use a central configuration file for all SAP systems served by this EH&S Expert server PC that do not have a different setting for their destination.

  • With the optional registry parameter ReadUsageOffline = Yes , the EH&S Expert can be forced to also read the data from a local configuration file in all cases for EH&S systems with Release 2.5B SP4 or 2.7A or newer. You can set this parameter on the SAP Destinations tab page and on the Global Settings tab page.

Example : EH&S Expert is called for the destination EHS_EXPERT_SHC from client 040. In this case the Expert searches first for the registry parameter UsageData_040 under the respective destination. If it cannot find it, it searches for the UsageData parameter under the respective destination. If this parameter could not be found either, the Expert searches for the UsageData parameter. Only when this parameter could not be found either does the Expert abort the execution of the set of rules with an error in an EH&S Release prior to 2.5B SP4 or 2.7A.