Brownfield Conversion from EHS Product Safety (ECC) to S/4HANA Product Compliance Classic

[duc_minh]

Hello expert, 

we are planning a brownfield conversion from EHS Product Safety (Dangerous goods and SDS management in ECC) to S/4HANA Product Compliance Classic Functionalities. 

Aside from the activities for the conversion of the SDS Receiver in ECC to Business Partner in S/4, are there other activities to be planned?

I mean necessary activities, so that the following data from ECC will be availble in S/4HANA without any problems: 

• SDS Cover sheet
• uploaded SDS WWI templates from 3E content via CG34
• WWI raw reports of e.g. SDS's (Table DRAO, DRAW)
• initiator of the SDS shipment
  • for example if the ID of the Sales Org/Initiator has been changed for the conversion. For example: in ECC it was Initiator 1000, in S/4 the same initiator has now the ID 2000
• SDS shipment history 
  • if the ID of the Sales Org/Initiator has been changed after the conversion, then the iniator displayed in the SDS shipping history in S/4 needs to be changed as well (to the new ID of the initiator)
    

    Thank you in advance

[christoph_bergemann]

Hello

you have used the term/sentence "Since for Product compliance it is not easy to find all information, I posted the question here in hope to gain more insight. I want to make sure that I do not forget anything so that the conversion will go smoothly. "

This is not a "good story". The issue is the term "Product Compliance". This term is misleading (or can be misleading).

In R/3 you are using EHS Classic. try to avoid to use the term "product compliance" (there are many conflicts to list if needed).

in S/4 you can use EHS classic or you can use  the new solution called: "Product Compliance" if you believe that the current version satisfies your needs.

I assume: You still will se EHS classic in S/4.

Honestly It is not a good idea only to "migrate" with out the check of: can i "improve/simplify etc." processes. But this depends on your project scope...

Anyhow: i wish you the best or your project

C.B.

[christoph_bergemann]

Hello

regarding your topic as:

• CG02 specification (realsub and so on)
• Material Master
• WWI Template 
• generated SDS raw WWI reports
• SDS shipment history (CVD1)
• Customer master data (SDS receiver)

During the S/4 Brownfield Conversion, how would the data cleansing activities look like?

• Will the data be copied during the ECC-to-S4-Conversion and obsolete EHS data can be filtered out with transition tools?
• Or is the only way to do clean up by having an empty S4 system and data need to be manually migrated into the S4 system after cleanup?
• Or do we delete data in the source system by setting deletion marks? So that during the data copy of the ECC-to-S4-Conversion only validated data will be taken over?

As mentioned: the "exact process depends on mand things. In your list i would miss "phrases".

Anyhow: based on your story:

You have an "old" landscatp and you would to use a new landscape

There;

• Will the data be copied during the ECC-to-S4-Conversion and obsolete EHS data can be filtered out with transition tools? 

I am sorry: there is no transition tool

Option one: extract the data via "export" and do "import" in the new system. THIS IS ONLY POSSIBLE IF SET UP IS IDENTICAL

And this is the problem.. in most of the case you would like to ge rid of "useless" data etc.

I am sorry: here we do not have any SAP tool which "really" helps (i skip some suboptions)

Regarding:

• Or is the only way to do clean up by having an empty S4 system and data need to be manually migrated into the S4 system after cleanup?

As i have understood: you will start with an "empty" system: so yes you must migrate (i will not call this "full" manual; but many steps are "afterwork" steps

Regarding:

• Or do we delete data in the source system by setting deletion marks? So that during the data copy of the ECC-to-S4-Conversion only validated data will be taken over?

This helsp to get rid of "unneeded" data before data migration; but still you need to move the data

As mentioned: i am sorry: the exact (may be best approch) depends on many factors

Luckily: Of you just "google": many companies can help fo EHS data migration

I wish you the best

C.B

[christoph_bergemann]

Hello

your list is in my opinion incomplete

Hence, we identified the following master data. If this list is not complete according to your experience, then any remarks are highly appreciated and thank you in advance 

• CG02 specification (realsub and so on)
• Material Master
• WWI Template 
• generated SDS raw WWI reports
• SDS shipment history (CVD1)
• Customer master data (SDS receiver)

I am missing e.g. "phrases" and for a SDS you need chater 14 and therefore you need "DG" set up. (could be that you are referring to "realsub and so on): but DG data is important

Never have seen a company using EHS only for report shipment..

MOst of the companies are using it with "DG", "SVT" and "GLM". Only then you have benefit

As explained: the "trick" is to define the scope (and aprahc of data migration) of the project carefully

So we have "e.g. greenfield". Using greenfield I would only migrate the "needed data"; ideally: data cleansing is done before (ore afterwards)

But the "exact" approach depends: is the company still using "3e" content; are they planing to use "3E" content?

and many other topics

from practical point of view: the IT process will work; but the business do not understand the "project" (e.g. data validation is not done or not done carefully by the customer).

At the end: the customer can then have "mess" in the system. But old system is still "shut down". So they have to use the new system. in 80% of the cases i know: a 1 uptto 2 year "data cleansing" project must be started after the migration as the migration was not done carefully.

The "most" primitive version is: target system has same set up as source system; no data cleansing done.

But as this type of projcets is a "high invest": i propose to prepare good data migration path.

Any how: i wish you success

C.B.

PS i have not listed here an "IT tool" for migration. The reason is: only you can define the "best" tool/approach; the list of variants: how to do the job.. is simply to long to discuss this here

[christoph_bergemann]

Hello

in context of:

Hence, we identified the following master data. If this list is not complete according to your experience, then any remarks are highly appreciated and thank you in advance 

CG02 specification (realsub and so on)

• Material Master
• WWI Template 
• generated SDS raw WWI reports
• SDS shipment history (CVD1)
• Customer master data (SDS receiver)

This is "surprising". I am really missing "Dangerous goods" aspect (and clearly Label and SVT topics).

Any how:

As mentioned: the "trick" is: how to do the migration

Let us start with "material master".

The "easiest" option could be: set up an ALE between old and new system and just "push" the data (matrial master) to the new system

Option 1:) ignore data cleansing and just "push all"

Option 2:)  do an analysis: was it really used in SAP MM, PP, SD processes and push only that to the new system

BUT the topic depends on: do you a "wave approach" or a "big bang" (all in one run)

WWI template: this is "easy" Identify what template you need; do a "download" in old system and an uplod in new system (and little bit afterwork): generation variants need to be handled anyhow manually

Generated Raw report: this "can" be easy. You need first the specification (refer later) and then you can do an ALE as well between source and Target system. You can only moe the "release" one to the new system (but same problem as before. Big bang or wave approach etc.)

SDS Shipment history. here we are lacking of SAP tools.

Option 1.) start in the system "from scratch"

Option 2:) you need to do "programming" if you plan to migrate data from CVD1. I am not aware of any standard function to "upload" CVD1 data. So Option 1) is easy and still fulfills legal requirements (customer will get "more" SDS at the beginning, but why not?)

Customer Mater data: here i am not experienced. Clearly you need to check the effect here. But the effect is higher for SAP SD, MM etc. as for EHS.

And last but not least: you need the specifiations and phrases. Here as well "ALE" can be a solution

But the options listed above is a "pure" migration (without any optimization etc.)

So you have the choice (which option is the best (and yes: you can list more options with different "pros" and "cons").

The topic depends a little bit as well on "size" of EHS system (topic of "risk" handling)

E.g. anything below 50.000 specs is "ok" (low risk). between 50.000 and 100.000 risk is higher; and starting 100.000 risk is clearly higher.

Therefore: the "trick" can be (but this is not a must) to do clean up before using the data in the new system

And the "right" option: If you use 3E content the scenario should be different

Wish you success

C.B

[christoph_bergemann]

Hello

reading between the lines you will use this approach

You have an ECC landscape (DEV(QUAL/PROD); then you will prepare a new landscape DEV/QUAL/PROD for S/4 HANA

Step 1. UNDERSTAND THE SIMPLIFICAITON LIST FOR EHS CLASSIC AND S/4

Step 2: then the problem with "Cover Sheet" etc. is "peanuts" as you must first migrate the data (there is much more to look at)

Step 3; to do the job... find a service provider which will help you

I can not list here all the topics you have to "pay attention" on. The list is to huge

I wish you success

C.B.

[duc_minh]

Hi CHristoph,

[duc_minh]

Hi Christoph,

thank you for your answer. I am actually from a service provider company.

Since for Product compliance it is not easy to find all information, I posted the question here in hope to gain more insight. I want to make sure that I do not forget anything so that the conversion will go smoothly. 

- I have checked all Simplification items for Product Compliance Classic. The customer is not affected from functionalities which are discontinued in S/4

- As far as I understood, in a brownfield conversion the master data will be copied from the ECC system to the S/4 System. If there are master data which cannot be copied and has to be migrated manually, then I would really appreciate if you could list them here

- In terms of activites to be done before and after the conversion I have only found this in the SAP Notes: the activities for the conversion of the SDS Receiver in ECC to Business Partner in S/4. (SAP Note 2267461)

If you know are aware of more conversion activites, please share them here. 

Thank you in advance

Duc  

[christoph_bergemann]

Hello

the issue is the term "- As far as I understood, in a brownfield conversion the master data will be copied from the ECC system to the S/4 System. If there are master data which cannot be copied and has to be migrated manually, then I would really appreciate if you could list them here"

more specific: Copy the master data

This the "trouble"; and it is a good idea to do data cleansing befor: therefore: do a copy of master data only if it is "active" and needed. This reduces the amount of data a lot (KEEP IN MIND: even if you just "copy" the data: somebody must "validate" that the copy is "ok"

And the "amount of copy" depends on the current used solutions. E.g. do you use the "full EHS classic" ? In most of the cases:

SVT, GLM DG, HSM and Report Shipment are the "core" functions used very often. Therefore: What data exactly has to be "copied": only you can define this (and how to do it.. this is next topic)

And you have a huge liste of versions/options how to do the "copy". Some of them is supported by SAP; some other you must do manually. And the amonf oof work to be foreseen for EHS data migration is BIG (much bigger as e.g. Material Master Data) and risks are huge (a lot of risks to list).

And in most of the projects i know.. a wave approach is used this makes the "migration part" more complex

IN a nutshell. If you come from EHS classic and you go on with EHS Classic.. this is possible, But sometimes other (so called workstreams) change their set up as e.g. SAP SD, PP etc. and as a fact of that you must do afterwork in EHS classic

Wish You the best

C.B.

[duc_minh]

Hello Christoph,

many thanks for your input.

The Customer is using mainly the specification database (CG02), SDS generation via WWI, and the automatic SDS shipment.
Hence, we identified the following master data. If this list is not complete according to your experience, then any remarks are highly appreciated and thank you in advance 🙂

• CG02 specification (realsub and so on)
• Material Master
• WWI Template 
• generated SDS raw WWI reports
• SDS shipment history (CVD1)
• Customer master data (SDS receiver)

During the S/4 Brownfield Conversion, how would the data cleansing activities look like?

• Will the data be copied during the ECC-to-S4-Conversion and obsolete EHS data can be filtered out with transition tools?
• Or is the only way to do clean up by having an empty S4 system and data need to be manually migrated into the S4 system after cleanup?
• Or do we delete data in the source system by setting deletion marks? So that during the data copy of the ECC-to-S4-Conversion only validated data will be taken over?

Thank you