EHS Master Data & Migration from Legacy System

[#1]

Hi EH&S experts,

Can you please provide the inputs regarding the EC and  EH&S (PS, DG,WM,REACH,IHS and OHS) master data and what can be part of EH&S specification database of  that master data?

What is the best way to migrate the data from legacy to SAP EHS(Pi,LSMW, Dataeditor)?

How the EC-master data to be handled?

Background:  Client want to migrate the all legacy data into SAP before implementing the EHS modules.

Thanks in advance for all EHS experts.

Regards,

Viveka

[Ralph_P]

Hi Viveka,

The best way to migrate data into EH&S is using the DataEditor. As a rule of thumb, you can migrate everything that you can see in the specification workbench plus phrases/phrase sets/phrase set assignments.Prerequisite is, of course, that the necessary classes and characteristics exist already in the system, so migrating before implementation of EH&S will not work.

Ralph

[Former Member]

Ralph,

Thank you for the response.

Can you provide more details regarding basic configuration required for data migration, master data details and process of migration?

Also if you have any documentation, that would be great help.

Thanks,

Viveka

[Ralph_P]

Hi Viveka,

if you migrate only standard characterstics, they are all you need. Additionally, phrases/phrase sets/phrase set assignments either have to exist already or they need to be imported first. So the system configuration is standard plus anything customer-specific you need.

For the migration process itself there are basically three steps:

1. export from the old system
2. data cleansing/mapping
3. import

The whole process is pretty much straight forward. I have no documentation about it, please ask for details via mail to [email protected].

Ralph

[christoph_bergemann]

Dear Viveka

regarding EC I can not help.

Regarding PS, DG, WM etc.

Normally EH&S Projects are started with PS topics. And therefore migration starts with this sub module.

Ralph explained the most important facts. The highest effort is involved in "mapping" and preparation of mapping. The export and import is in most cases done very easy and smooth.

On the top DG topics are introduced. As DG is base ond PS data: normally if PS data is prepared there is no need to transfer legacy data

IHS and OHS are introduced very late in a project. Regarding IHS you should may be think of the new solution (component extension Version 2.0 available now)

I do not know the DataEditor and the topins provided; principly EH&S does have some "lacks" in support of import mainly in IHS and OHS. LSMW is a tool which is not suitable in most cases regarding EH&S. I have never used PI to perpare "transfer" form old to new system.

Regarding REACH perspective: here we have two "solutions" which are part of Reach solution of SAP. EH&S SVT and SAP Product and Compliance workbench. Never had a project in the past to migrate data regarding these solutions. The same is true regarding EH&S Waste. Never had a project to migrate data in this context.

By the way: what is your defintion of "legacy data"? Normally EH&S is defined as "legacy data" as well.

With best regards

C.B.

[Former Member]

Thank you Ralph and C.B for valuable inputs.

Is there any format file to import the specifications to SAP?

Thanks,

Viveka

[christoph_bergemann]

Dear Viveka

plase refer to:

http://help.sap.com/erp2005_ehp_06/helpdata/en/a7/2879200a6c11d28a220000e829fbbd/content.htm

Chapter: Import and Export

You will find description: how to import phrases, specifications and the related data, and reports (PDF, RTF etc.); format of file, how to do it etc. etc.

Be aware of the fact that in higher SAP release new structures are available mainly in the area of DG.  These are not supported by EH&S import interface.

Make always sure that you use proper "Character fonts", what in most cass you use "UNIX" as the operating system and this might give trouble (in this FORUM you will find many threads regarding import topics in EH&S).

In the SAP EH&S help you will find on the top assistance regarding "ALE" topics (if you would like to use later XI or PI)

Most important fact: before you start migration you should make sure tha you have prepared the encessary "target" data base structure. Therefore in most case you need to check phrases, identifiers, properties etc. and then you need to "map" old strucutre to new structure.

The preparation of customizing,. phrases and the mapping is the most time consuming activity (80% of your time will go here); the import (if you have prepared all the stuff) is not the time consuming task because the system ist doing the whole stuff

With best regards

C.B.

[Former Member]

Thank you C.B for the link and information.Very valuable information.

Regards,

Viveka

[Former Member]

Hello Viveka,

Did you get any information about data migration from '[email protected]", if yes could you please share it with me.

Regards

Kamlakar