SAP EHS Component reimplementation

[ashish25bp]

Dear Experts,

Here I am not seeking resolution to any error but just need a thought that can be helpful. The scenario is, one of my clients parted out from another company but during implementation, probably lift & shift sort, it inherited the previous orgs FM's/ codes/ programs and may be some config as well. Now there are multiple issues that are being faced for e,g expert rules issues (while writing data) , duplication of data, some redundant data which is likely to be inherited from former one. As a solution to this issue they want to go with the approach of reimplement EHS Component again (' clean slate') instead of keep resolving issues. Here is where there are multiple unanswered questions are lingering.

1) While other modules (MM, SD, PP, FICO etc) are running in parallel, is it possible to do a reimplementation of only SAP EHS ?

2) Or is it advisable to go and resolve issues module by module (Product safety- SVT, rep mgmt, Templates, DG, Waste Mgmt. etc.)and clean the system. But here it will be complex task to identify the unwanted data and programs.

3) While going through reimplementation, how can this be achieved in production while other business process are running. Only DG, Rep shipping are integrated with logistic. SVT is still not live due to issues.

4) Even in that case also, Is it possible to clean slate every thing at one go ? Here may be the customization can be copied from a prototype environment and reload the master data again. The major challenge here is integrated functionalities will be on hold till that time.

5) Imp question: Is there any other approach that any one has done it before for such situation.

Not sure if all this questions can be answered, but a small thought / suggestion can be helpful.

Regards,

Ashish

[ashish25bp]

Hello Experts,

Since the topic is associated with the same requirement, I am putting my question in continuation with the same thread.

As I have stated earlier, entire activity is to extract the data from existing SAP EHS system, transform it and reload in the new series of Specification (Real & Pure sub). But when the data is extracted in excel format the expanded volume is too big to handle it manually for cleaning and preparing load files. There are definitely good chances of human errors and risk of wrong data getting loaded.

On exploring further, I found some possible ways to address this issue. But never used it.

1) Use of SAP BODS for ETL (Extract, transform and Load). I have not used this before but what I learnt is, this can be an effective method for the entire ETL activity.

2) Through SQL database queries. I hope, using this method I can prepare my excel load files more easily. But here as well, I have not used this earlier.

Just want to check if anyone has used either of it for SAP EHS and are they really useful.

Regards,

Ashish

[Mark-Pfister]

Hello Ashish,

I would recommend a different approach:

There is no need to migrate the data for the PURE_SUBs that a content provider can provide - or that can be calculated by a rule-set like the GHS classification.

Therefore focus on the properties that have been manually maintained - and only migrate these (after the clean-up).

Same for the REAL_SUBs: only migrate manually maintained data like Composition, PhysChem or Tox data - and let the rest be recalculated using expert rules.

In order to achieve a Go-Live, migrate the existing SDBs - and let the customer over time re-create the data on the REAL_SUBs and release new SDS ...

This approach has proven itself to work...

Best

Mark

[ashish25bp]

Exactly ! we are also going the same way, in fact I forgot to mentioned above that we have sorted out those properties that will be updated through LIST_SUB, LS_UN_SUB or which are update through expert rules resulting into reducing the data maintenance. But even after considering that, there are still much more manually maintained properties; so was checking how can I convert it smartly reducing human efforts.

But any way thanks for suggestions this helps that I am in right direction.

Thanks

[ashish25bp]

Hi Christoph,

With my statement I mean that, I compiled data (for Pure_sub) from various tables e.g ESTRH, ESTVH, ESTVA , AUSP, ESTDU , ESTPP in one master excel sheet in such a format, that my data team can use that as reference to prepare the data load template files (excel) that can be converted into .text and then.dat file using OCC tool.

For e,g. the above said master sheet consists of fields like:

Spec Id, VAT , VAT Description , Characteristic, Phrase ID, Rating, Validity area, Phrase description etc.

Here my intension is to create new Pure / Real sub with clean data. And therefor, this compiled excel file can work as single point reference book. Referring that, we can eliminate unwanted values, identify where we need new phrase, which data can be retained as is etc. and prepare a clean files.

But in practice this is not easy as the volume of the file is too big. That's why I just want to check if there is any other more efficient way.

Ashish

[christoph_bergemann]

Dear Ashish

we can only imagine your starting position...

What exactly is part of this .. ?

"To do this, I got an extract of data in excel from existing system."

What is the content of the EXCEL? How is this EXCEL structured?

Only if we understand better your "starting position": we can may be help

C.B.

[ashish25bp]

Dear Experts,

I have a doubt pertaining to the same subject therefore putting the related addon question here since this thread is still open.

My requirement is to create a clean data for the client. The existing data contains unwanted phrases and references inherited from previous mother company which has now separated. Therefore as an approach, we decided to create new Pure sub, Real_sub and reload the clean data again. But here we want to use 60% of data as is from existing system (phrases etc) and 40% of new data(Replace new Phrases etc) and upload that into new Pure sub OR Real_sub.

To do this, I got an extract of data in excel from existing system. for e.g. There are 500 Pure sub's and there are approx. 1000 characteristics are such for which I have to compile existing and new data and upload. If I take the OCC tool approach, It will be a huge task to create data load templates for 1000 characteristics. Plus this 1000 characteristics will have data/ phrases into it and that multiple will shoot up volume to thousands of entries. This leads to a huge, time consuming and cumbersome activity.

I just want to know if there is any other approach, other then OCC, that can be considered to load the data in new Pure & Real sub specs.

What can be the other tool/ method which will be easier to handle this activity.

Ashish

[ashish25bp]

Thank you Christoph for the helpful suggestions.

Considering the risk and complexity to cleanse the system while other business process are live, it is preferable to go in step by step approach is what it seems. ' Clean Slate ' at one go may not be plausible.

Further Impact analysis is needed for

Identifying Unwanted data and deleting that (like there are many unwanted Phrases lying in specifications that were inherited)

OR

Either to create new Pure_sub, Real_sub, Real_Grp, DG_classificaiton with new number range ( needs to be analyzed further)

2) There are many Programs and FM's not needed, deletion of that need to be checked with Impact analysis.

3) Report symbols and wwi code cleansing expected in Labels.

We are further checking on this and welcome any more thoughts.

[christoph_bergemann]

Hello

i am not 100% sure if i have understood your challenge.

Therefore: this is what i can read between the lines
- SAP MM, SD etc are all up and running well

- SAP EHS Seems to have a huge list of issues

- In "scope" is:

-- DG process

-- Report shipping process

-- and the corresonding "ehs master data

- potentially later in scope: SVT

Coming to you topic:

The "most" important link of EHS and MD, SD etc. is the "material REAL_SUB" link.

Assuming that the "property tree" is fine (correct custmizing etc.), the "phrases" are fine etc.

It seems to be that you need to start from "scratch" (at least partially)

So you have to start with "LIST_SUB" / "PURE_SUB" you must may be "clean" up property tree; you must clean up "WWI reports" etc. etc.

Let us start with "SD" process. here we have two important links: the "DG" process and the "SDS shipment" process

So the may be first step is: get "rid" of the SAP SD EHS DG integration.

Then SAP SD will just "run" (without DG checks)

Then you have to do proper Material REAL_SUB Link and you must prepare "DG" data (on material level). Now you could activeta SAP SD / EHS integration for DG

For "Safety Data Sheet". You need the propert data in property tree; (assumption: you can delete any data and you could do a complete "reimport". The you could get rid of "SDS" (released) and "regenerate the SDS

etc.

BUt it is clearly not an easy task to handle all the issues (reading between the lines) and the company acting would be "inclompliant" (no real DG check, not SDS per EHS process)

So anything very risky. But according to what i read between the lines: there is no other option

C.B.