Generate MSDS document from another system

[Former Member]

Dear All,

We have one EHS system (HQ) with all the report templates & variants for MSDS document in place.

Now we're going to implement roll out EHS in another server (country).

The MSDS report must be control and same with the one in the HQ.

But we don't want to manually maintain the report template & variant in the country server but read it from the HQ system instead.

Is it possible to do this?

Or any better idea to achieve this?

Thanks.

[christoph_bergemann · Accepted solution]

Hello Peer

I did not catch your question. I will try to answer the other way around:

Assuming you have two SAP Systems in which EH&S is "fully" customized and regarding customizing identical and assuming that you create the raw reports only in one of the systems you have two options:

1.) prepare an ALE scenario between system A and B and transfer the MSDS (only released and historic one) from A to B. Now you can use the system B to perform report shipping as well as system A.

Pro: the MSDS are generated once in one system using the same data and using one WWI logic etc. and only distributed in the other system

Contra: you need to check ALE as ongoing process (generation variants etc. must be present in system B too !)

2.) You can use SAP System A and system B (both full customized in EH&S),.Now you have the option by using one customizing parameter to prepare a RFC call to system A to retrieve the MSDS. We have no experince in using this parameter but it should work (please check !!). PLease check SAP documentation regarding the parameter etc.

Pro: No ALE scenario necessary; documents stay in System A

Contra: regarding any MSDS process in system B you will always ! have a RFC call to system A. In any case if you plan to do report shipping from system B the "Final" report must be stored in system, B

In most cases scenario 1.) is more stable on a long term perspective

With best regards

C.B.

PS: there is normally no need to prepare a further SAP EH&S system if you are planing a "roll out". Normally you would seperate country eg. DE and BE by using different access roles etc. and in many cases you need the same data (e.g. density). Therefore: Please check your approach

Edited by: Christoph Bergemann on Sep 14, 2011 1:48 PM

Edited by: Christoph Bergemann on Sep 14, 2011 1:51 PM

Edited by: Christoph Bergemann on Sep 14, 2011 1:51 PM

Edited by: Christoph Bergemann on Sep 14, 2011 1:52 PM

Edited by: Christoph Bergemann on Sep 14, 2011 1:53 PM

[Former Member · Accepted solution]

Hi CB,

Thanks for your reply.

Yes this is what we're trying to achieve.

We're more to the option 1 which to synchronize the MSDS released from system A to B.

Do you have detail on this?

We did test using DOCMAS idoc and I can see the MSDS document is created in system B from system A.

The thing now is we're still not find a way to sync the report variant.

What are the other things that we need to bring over to system B in order to able to print the MSDS document from system A?

Thanks.

[christoph_bergemann · Accepted solution]

Hello Peer

assuming you would like to use system B to use "report shipping" functionalities you need to consider these topics:

1:) first you must distribute your substance (REAL_SUB) using SUBMAS (ALE)

2.) second you must distribute PHRASMAS (ALE) (you need phrases to prepare accompanying leter)

3.) You must distribute the materials from REAL_SUB to B

4.) you must distribute the Business partner information from A to B

5.) You must link WWI servers on system B

6.) You must make available corresponding GENVARs manually ! (if you do not change the number of GENVARs this need ot be done only once) and you must prepare report symbols (chapter 1 !)

7.) You must prepare the "accompanying" letter in system B

PLease refer to SAP EHS documentation (how to perform ALE transfer)

As explained: it is very important and critical that the EHS customizing of A and B must be the same and you need a DMS/DVS or Archive in system, B as well !

Furthermore you must prepare the whole EHS customizing to do the report shipping topic; schedule jobs (report shipping) , assign printers etc. etc. prepare access concepts (so that e.g. cg50/cg54 can be used)

If you have performed the necessary set up in most cases keep this in mind: you must actively mark a substance (REAL_SUB) as ALE relevant. There is to my knowledge no automatism. Therefore if new REAL_SUBs are generated with materials having MSDS which need to be distributed from system A to B then you must perform this activity manually.

In any case: the set up described above is possible and stable. You can use the ALE( there are some Exits there) to make sure that only MSDS which are valid in e.g. FR must be distributed and not all MSDS etc.

With best regards

C.B.

Edited by: Christoph Bergemann on Sep 15, 2011 4:47 PM

Edited by: Christoph Bergemann on Sep 15, 2011 4:47 PM

Edited by: Christoph Bergemann on Sep 15, 2011 4:48 PM

Edited by: Christoph Bergemann on Sep 15, 2011 4:48 PM

Edited by: Christoph Bergemann on Sep 15, 2011 4:49 PM

Edited by: Christoph Bergemann on Sep 15, 2011 4:49 PM

Edited by: Christoph Bergemann on Sep 15, 2011 4:50 PM

[Former Member · Accepted solution]

Hi CB,

Thank you very much for the details. It's really helpful.

We will go through your steps and see how is the outcome.

PLease refer to SAP EHS documentation (how to perform ALE transfer)

--> Do you have this? any link will do.

Best Regards.

[christoph_bergemann · Accepted solution]

Hello Peer

please check:

http://help.sap.com/erp2005_ehp_05/helpdata/en/c1/eda0f591ec12408b25e7a1b369ca45/frameset.htm

Chapter:

Basic Data and Tools (EHS-BD)

sub chapter:

Distribution (ALE) of Specifications, Phrases, and Report

Be aware of the fact that in ALE there are a nunber of user exits which can be used to "enhance" the ALE topic if the standard selection options are not sufficient.

By standard you distribute the objects using a "hit list" which is not dynamic. Specifcations and reports are distributed via hitlist; phrases can be distributed "more" dynamic (you need only to define e.g. phrase group etc.)

Therefore if you need some "dynamic" in your approach: you must do the job by yourself.

With best regards

C.B.

Edited by: Christoph Bergemann on Sep 16, 2011 2:13 PM

Edited by: Christoph Bergemann on Sep 16, 2011 2:14 PM

Edited by: Christoph Bergemann on Sep 16, 2011 2:14 PM

[Former Member · Accepted solution]

Hello CB,

Thank You very much for your kind response.

We will take note of your suggestion during the implementation and I will post here for any query.

Best Regards.