Want to connect MSDGen tool legacy data to SAP EHS (Master data upload)

[satya11719]

Hi ,

I just want to upload the complete data from MSDGen tool legacy data to SAP EHS (Master data upload).

MSDGen Tool having connection with ADM(Ariel already)

following things i'm going to do,

Division of substances REAL,PURE & LIST .

Upload phrase libraries & phrases

Templates upload.

Here to upload the data or connect the legacy system what are the possible ways i checked with OCC.

i was downloaded that from market place.. what are the next things to do can i download it into local PC ? how is will be used in group cause im new to SAP OCC

[christoph_bergemann · Accepted solution]

Dear Satya

you never received an answer for your last question. Sorry. To make it short:

EHS set up start with the "components" first (e.g. LIST_SUB, PURE_SUB, sometimes REAL_SUB) (but it is possible to set up first REAL_Sub and assign the REAL_SUB to Material number); you need as well not only "components" but e.g. "LS_UN_SUB" and "DG_CL_SUB"; the whole process depends a little bit: do you start

a.) from scratch?

b.) do you have a "legacy system" you would like to get rid of

c.) etc.

Check may be: https://blogs.sap.com/2017/09/04/data-migration-in-ehs-classic/

If you have the "PURE_SUB" / "LIST_SUB" in place:

then you create "compositions" or "spec listings" using the new spec ids

Example: REAL_SUB should describe coffee + milk + sugur (including water)

1.) create first "Coffee", "Milk" and "Sugur" and "Water" (as e.g. PURE_SUB)

2.) then write down the "spec id"s of all of them (including values of content like 10% etc.)

3.) Then decide: which property to go (e.g. STANDARD COMPOSITION); define as well "usage" for upload

And then by using spec id of REAL_SUB and of spec Ids of e.g. PURE_SUB" "Coffee", "Milk" and "Sugur" you can use either "OCC" or SAP Standard import so that the REAL_SUB does have a "composition"

10% Milk, 10% sugur and 10% "Coffee" (and may be 70% water) as a composition

C.B.

PS: it should be clear. for the EHS set up: you do not need only "components"; you need phrases as well and a lot of other stuff (e.g. customzing like: Regulatory list, User Defined TExt, Identifers etc. etc.)