cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

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

0 Likes
View Entire Topic
ashish25bp
Participant
0 Likes

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