Using backend ERP with multiple clients and EHSM?

[cindy_holden1]

Hello EHSM Experts!

I'm hoping someone can help clarify this for me as I understand when using EHSM it requires to have 1 backend ERP?  Does this stipulate one SAP ERP instance with one client or can it be the same SAP ERP instance with multiple clients? 

The reason i'm asking is that my installation involves 3 separate companies in one EHSM portal however each compnay has their own unique PERNRs and object ID's like positions and org units.  We are afraid of duplication so are considering multiple clients as possible solution.

Appreciate any feedback!

Thanks,

Cindy Holden

[christoph_bergemann · Accepted solution]

Dear Cindy

I did not completly catch your question. Therefore I try the other way around.

a.) If you use SAP ERP you have some software in place

b.) using this software you can prepare the set up in such a way that e.g. company A is using client 100; company B is using client 200 etc. From perspective of data maintenance this is a "bad" choice as any master data is "client specific". E.g. if Company A and B "share" the material Z then you must prepare material Z in both clients and in most cases you get the materials in "sync" only using manual actions (e.g. if you need more Ums etc.)

c.) regarding EHS/EHSM it is the same. This is one software layer and per client you can "differentiate" the maintenance; but the issue is nearly the same. IF you have material Z in place you must get both clients in "sync" regarding that from EHS/EHSM perspective by "manual" activities)

Clearly there are a lot of options to do it better (that means prepare better technical set up).

It is well known that many companies (because of thatever reasons) use these scenarios:

a.) One SAP ERP with one client (any company is using the same client)

b.) One SAP ERP with many clients; per client one company (or more than one) is acting

c.) Two or more SAP ERP systems; per company/Companies one SAP ERP is used

d.) and many combinations of this

Topic of "duplication"... We need to differentiete "technical" and "business" aspects.

As mentioned above: If you use the same material Z in two companies and both use a different client in the same SAP ERP then you "duplicate" the data; But if you e.g. use one SAP ERP system as "master data" system you maintain once the data and e.g by using ALE you can distribute the data. In this scenario you don't duplicate the data from "business" point of view, but from technical point of view (you replicate it (or the IT tool ALE is doing that)).

I am not sure If this helps you. But if you would explain your system set up "better" may be this might help.

C.B.

PS: the use of several SAP ERPs (or clients within SAP ERP) is a "challenge" regarding master data management (e.g. vendors,.customers, materials etc.); but this set up is well know (e.g. check this link to check "options": SAP NetWeaver Master Data Management (MDM) 7.1 – SAP Help Portal Page

I am not the expert for MDM but this is a new option devilvered by SAP to help you to get master data in "sync"

PPS: generally many companies using SAP has started in the last years initiatives to get rid of that many SAP ERPs or clients they use to increase efficiency in master data management; I am pretty sure that SAP is willing (or any other company) to help you to identify options regarding master data management

[cindy_holden1 · Accepted solution]

Hi Christopher,

Thank you very much for your very thorough response!

I agree with you that if the master data is the same across all cleints this would be a poor choice.

In my case the master data is not shared by the different companies therefore not having one source of master data.  The only similiarity would be the configuration of EHSM which would be client independent and the same for all companies.

So knowing this, would you agree that EHSM with multiple clients could work and the backend ERP could source the master data accordingly?

thanks for your help!

Cindy

[christoph_bergemann · Accepted solution]

Dear Cindy

I have to accept your answer; but I have never heard about one "group of companies" not sharing master data. So your scenario seems to be this:

a.) you would like to use one SAP ERP for all companies

b.) per client one or more companies will act

c.) in the SAP ERP you have prepared EHS/EHSM

So the answer is simply: yes you can use thise scenario but as with SAP ERP SAP EHS does have the need to prepare client specific set up. Therefore only to give you some ideas why this is a "bad" choice some list of issues:

a.) per client you have to prepare EHS/EHSM customizing

b.) per client you need to load data (e.g. if you use an external data provider)

c.) per cllient you need to prepare suitabale user roles (access concept)

d.) per client you need to establish e.g. MSDS/SDS distribution etc. etc.

e.) per clienty ou need to prepare WWI server set up as well as Expert server (if needed)

f.) etc. etc. etc.

So conclusion: (this will be the feeling of the  EHS/EHSM set up etam which do the job)

Depending on the number of clients this is a "bad" choice/option. to make it quite clear:

"the backend ERP could source the master data accordingly?"

This does mean: you have client 100 (as example) there company A is acting (you maintain in client 100 master data). And then you as well establish EHS/EHSM in same client; then the same for client 200 etc. BUt per client you will need "similar" customizing in SAP ERP as well.

Personally I can not believe that there is no overlap in vendor/customer etc  between the different company which act. But you need to decide. Technically: you can install a lot of clients in the same system; but e.g.you need to replicate your access concept per client (as you need the "same" SAP MM/SD etc. process in most cases by client). Depending on the number of clients you would like to install/prepare this can get a "disaster".

C.B.

PS: not sure about your remark: The only similiarity would be the configuration of EHSM which would be client independent and the same for all companies.

This is technically not possible. Per client you have one EHS/EHSM customizing. If you have two clients you need to execute the EHS customizing twice.

[cindy_holden1 · Accepted solution]

Hi there Christoph,

You have been very helpful and i will try and shed some more light on my dilemna i'm facing hence why i'm suggesting multiple clients.

These are truly separate companies with their own SAP systems and financial reporting (company codes).  Unfortunately they are coming together to use EHSM as one unit.

So all 3 companies would contiue to maintain their own SAP system and their master data required for EHSM will be sent via ALE so they will continue to have one system of record.  The problem i see is the possible overlapping of object id's like positon and org unit.  Similar to your point of overlap with vendor/customer info.  This is one of the main reasons i am thinking of multiple clients....aside from the fact if i put the other 2 external companies in one of the existing SAP systems, would have a huge impact on changing existing interfaces/programs to exclude them.

With this concept we did account for ALE of master data, security roles and possibility of specific EHSM configuration specific to each company.  What I did NOT account for is the main configuration of EHSM which you are saying has to be done individually in each client even though each company would inherit same configuration set-up therefore my comment about client independent.

so if you are saying each cleint would have to have all the EHSM configuration done separately and that if cannot be done as client indendent tables in the main ERP client 100 for example, then yes i was not aware of this.

if you have suggestions to implement given my situation i am open 🙂

Truly appreciate your feedback!

thank you,

Cindy

[christoph_bergemann · Accepted solution]

Dear Cindy

first some question to you:

which EHSM/EHS module you would like to use? (for explanation see: Environment, Health and Safety (EHS) - SAP Library)

My list would be:

a.) EHS-BD

b.) EHS-SAF

c.) EHS-DGP

d.) EHS-SAF-GLM (may be)

e.) EHS-HSM (may be)

f.) EHS-WA (less probability)

g.) EHS-HEA  (less probability)

h.) EHS-IHS (may be) (or do you would like to use "Component Extension for SAP EHS Management?)

Regarding your scenario:

So all 3 companies would contiue to maintain their own SAP system and their master data required for EHSM will be sent via ALE so they will continue to have one system of record.

Depending on the answers to the question above you might go in "wrong" direction. Especially if you need EHS-DGP and EHS-SAF-SVT or EHS-SAF-RSH this is a "bad" option. You should ask for help SAP or a SAP partner definiing a suitable SAP Landscape.

I have the feeling that you do not understand all aspects of EHS. E.g. the topic of "vendor", "Customer", "Material" data is very critical for EHS and anything here must be "unique".

Let us assume now this example:

You have four SAP Systems

SAP System 1 does use client 100; SAP system 2 does have as well client 100; same for SAP System 3. Now If I understand you correct you would like to establis SAP system 4 as well with one client (let us use first simple example); once again this might be done in client 100.

Now you would like to establish ALE distribution from SAP System 1, 2, 3 to SAP System 4 regarding master data (e.g. materials etc.). SAP system 4 would be used as a "master data reference system" for EHS/EHSM management. The main issue with this approach is: you need EHS data as well in SAP system 1,2,3 especially if you need to use or would like to  use EHS-DBP; that means you need to establish backward ALE starting SAP system 4 to 1,2,3 in regards of DG management;  And now comes the "bad" news: to do the backward ALE you need to establish basic EHS customizing in SAP system 1, 2, 3.

First conslusion: in this sceerio you will execute at least basic EHS customizing in four SAP systems (may be you feel now like: )

Conclusion: your SAP landscape is a "nightmare" (and not only for EHS/EHSM set up):. Therefore: ask SAP or a SAP partner to help you to consolidate your SAP landscape or to think about suitable options in regards of EHS/EHSM set up; on long term you will not get happy with this situation.

C.B.

PS: please refer to this general SAP Note as referenced in this link for classic EHS installation: EH&S installation: Composite SAP Note

This is a must to read note. If you need on the top "Component Extenstion for SAP EHS MAnagement:

PLease check:

You will find a lot of references to other threads regarding the "Challenge" in the use of "Component Extension for SAP EHS Management)

PPS: good luck for you and your team; this is a quite challenging IT project

[cindy_holden1 · Accepted solution]

Hi Christoph,

sorry i should have told you we are looking at using EHSM v.4.0 in regard to Incident Management, Safety Observations and Risk Assessment in a system integrated with SAP HCM only.  I know EHSM is a cross-application component however we will not be using for this purpose.

we are also working with SAP and i certainly do plan on brainstoring with them to come up with the best solution.

Again i appreciate all your great feedback.

regards,

cinddy

[christoph_bergemann · Accepted solution]

Dear Cindy

this will simplifies your problem. The challenge is now clearly lower to you. In this scenario the risks are lower. But may be you should use current/recent version which is EHSM 5.0. In any case: there are a lot of links in this FORUM related to this solution. Check:;

You will find a lot of references to the EHSM solution; e.g. topic of data migration, set up etc.

In my opinion regarding dublicating of master data and the other risks you have mentioned. the riks is low.

Good luck in installation/preparation.

C.B.

[cindy_holden1 · Accepted solution]

Thanks very much Christoph!

I will review that document you suggested.  I'm glad you have a better idea of my solution and feel better you believe the risk is lower now.

Thanks again for all your help along the way.

Regards,

Cindy