Hazardous Substance Check in GTS with SAPEH&S

[former_member380918]

http://help.sap.com/saphelp_gts101/helpdata/en/40/ef2d1b7a774addb6f988a0c499f409/content.htm?framese...

Hi,

We need to integrate SAP EHS(EHP-6) with GTS and got below details.

This document mainly provide details about extending material master view to WE and other Hazardous substance configuration configurations with WM.

Currently We do not maintain hazardous substances and Warehouse execution view.

Our requirement is simply to pass some parameter to GTS and update their Hazardous substance check flag if material identified as hazardous.

Is it possible without activating hazcom indicator in WE view and integrating with WM.

Regards

NS

[former_member191252]

I need to add few points:

1. If you are planning any filling for the Hazardous Substance Management from the spec.database, you need the WM or WM Execution tab, they act as pre requisities.

2. You need to maintain those vies in MM.

3. If you need to pass some values from GTS to Materials Master, you need to have WM/WME views for sure.

4. We did with out WM, as we are not licensed for that one, but our requirement was just SARA, so not necessarily nee to activate that view and built the custom solution. We maintain all Hazmat values in Spec itself and wrote the code on that spec database values.

--

[former_member380918]

Thanks for response.

This is similar situation we are in. We do not have WE view and do not want WM integration.

That is the reason we need to have custom solution with HAZ values maintained in specification and determine the criteria to update Flag in GTS.

Any advise.

[Former Member]

Hi,

Thank you all for your great inputs. Special mention to C.B. and Mr. EHSM.

I am Siva and Naveen & I work together for EHS projects.

Taking inputs from C.B. & Mr. EHSM, and what Naveen has pointed out,

We have separate instances of ECC and GTS and both are configured and actively supporting business.

We plan to implement the DG integration with Distribution & Logistics AND GTS integration to meet our Compliance and Customs business requirements (we are at very early stage of the project now).

Coming to the GTS integration:

We definitely do not have any requirement or plan for WM extension and prefer to stay away from complete hazardous substance management implementation with WM and material extension.

Yes we need to figure out an identifier or value assignment in Specification to define a Substance as Hazrdous/Hazardness - Any suggestion here is appreciated.

Now we will need to utilize a standard Exit to define our custom logic to determine a material associated with such a hazardous Substance used in a GTS relevant document (Sales order, Outbound delivery etc.) and trigger the RFC call with GTS to update the document in GTS and mark it as blocked (which will also activate the hazardous flag in GTS monitor). This document should be reviewed and released manually in GTS for further processing.

Highly appreciate if you can provide some idea to achieve this

Thanks in advance

Siva

[former_member191252]

If you do not have any planning for WM/WME, better go with the custom option, so you will keep info on the spec and code will written on Spec/MM tables.

Please close this thread as answered/helpful.

--

[christoph_bergemann]

Dear Sivakumar

I still have doubts that you have understood the tool/Technique/process.

In context of:

Yes we need to figure out an identifier or value assignment in Specification to define a Substance as Hazrdous/Hazardness - Any suggestion here is appreciated.

=> please ignore the term "hazardous"; it is a temr whcih can "mislead".

Please check my reply. This is the SAP "story":

These product-specific checks cover the following areas for hazardous substances:

• Import bans for substances from specific countries in import-relevant documents
• Quantity restrictions for substances in import-relevant documents
• Export bans for substances to specific countries in export-relevant documents
• Quantity restrictions for substances in export-relevant documents
• 
  

1.) in EHS you can prepare value assignement types and data records there you can store informaiotn about e.g. quantity restrictions, bans etc; as well you can buy "content" to get data populated

I am sorry to say: you need to "deeply" the SAP EHS STANDARD tree to identify proper value assignment type to store information as mentioned above. It is not possible to describe here the many potentiontia value assignments which can be used to manage the data.

Now normally the data looks like: there is a "ban" for "country" for"this" reason. Now GTS can read this data and will get data back to set the "hazardous" flag. But this hazardous flagis completed something different in comparision to the "Hazard substance management".So the discussion regarding  WM/eWM is not "helpful". You can not compare these two solutions. Some fo the restrictions as mentioned abvoe (e.g. quantity restrictions mainly) are processed normally using SAP EHS SVT. Some quantity restrcitions can be processed in GTS as well (this is a quite long stroy how to set this up properly).

Regarding:

now we will need to utilize a standard Exit to define our custom logic to determine a material associated with such a hazardous Substance used in a GTS relevant document (Sales order, Outbound delivery etc.) and trigger the RFC call with GTS to update the document in GTS and mark it as blocked (which will also activate the hazardous flag in GTS monitor). This document should be reviewed and released manually in GTS for further processing.

High level: these are the steps:

1.) SAP ERP replicate logistic document to SAP GTS

2.) SAP GTS process the document and determine relevant regulations

3.) if for one of the regulations determined a "hazardous" check should be done SAP GTS calls SAP ERP usng RFC

4.) now in SAP ERP a "exit" is called in which you can doe whatsoever code (e.g. read some data in EHS etc. etc.); the basic information which is generated is, that the material (which is related o normally a REAL:SUB) can be "hazardous"; this informaiotn goes back to SAP GTS and it is stored there

5.) now additional SAP GTS standard processing is executed; at the end if needed SAP GTS send infromation back to SAP ERP to "block" process (this is the same if you would not have the "hazardous check" active

Therefore: the "only" difference here is that normally SAP GTS uses only master data stored in SAP GTS to check what should be done; if hazardous check is active some on top data is read from SAP ERP and the result is stored in customs document

As long as you do not define "what doeas hazardous means" (whcih data to read in SAP ERP) you should not try to implement the process but you should stick simply to SAP GTS standard process

C.B.

[Former Member]

Thank you C.B.

I will go through in detail and find the exact definition (instead of 'hazardous')

Meanwhile, can you please advise the name of the 'Exit' that you have mentioned in ECC (step #4)

[christoph_bergemann]

Dear Sivakumar

just check SAP online help:

• You have configured the settings for hazardous substance checks in the Implementation Guide (IMG) of the system where you installed SAP ERP EH&S. The settings are located under Environment, Health & Safety Hazardous Substance Management .
• 
  
• Just check IMG (simply speaking)
• 
  
• C.B.
• 
  
• PS:Online help provide this "high level" info:
• 
  

1. SAP ERP EH&S calculates the check results and SAP GRC GTS saves them as a status value in the customs document.
   1. If the substances of the products in a business transaction lie within the quantity limits and the substances have been registered officially, the process in SAP GRC GTS is complete. The logistics process in SAP ERP continues uninterrupted.
   2. If you have configured the system such that blocked customs documents automatically interrupt the corresponding logistics processes in the feeder system, then SAP GRC GTS blocks the underlying logistics document.
   3. 
      
   4. PPS: Small hint of "warning (term hazardous !!): check this document: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0e8c107-0435-2e10-a5bc-e295ed040...
   5. 
      
   6. This is called as well "hazardous check" but is the eWM check (as discussed here); therefore in this case SAP has used the same term (Hazardous) for different meanings and this can lead to confusion
      

[christoph_bergemann]

Dear Sivakumar

may be check these threads. They might help you to define (together with customer) what you are looking for to get. If you just search here you will find more of these types of threads.

C.B.

[Former Member]

Thank you C.B.!!

We will check and get back for any further question regarding this

[christoph_bergemann]

Dear Naveen

I am not sure if you have the "right" picture about SAP ERP / GTS integration (and the EH&S integration as well) and the "Hazardous substance check". My feeling is that you may be mix terms.

The term "hazardous check" in context of this Online SAP help is a little bit "misleading". It does (in most cases) not take care about "hazard" but other topics. The online help provides this explanation:

These hazardous substance checks help you meet the requirements posed, for example, in the European Union's REACH (Registration, Evaluation, Authorization of CHemicals, REACH) program.

These product-specific checks cover the following areas for hazardous substances:

• Import bans for substances from specific countries in import-relevant documents
• Quantity restrictions for substances in import-relevant documents
• Export bans for substances to specific countries in export-relevant documents
• Quantity restrictions for substances in export-relevant documents

So on ,ost cases it is not a "hazardnous check" but a check for "restriction" (to sell, buy, etc.) something

The topic as such is not discussed often here. But you will find some threads (refer below). I try to help you shortly

1.) forget about "WM" topic; The SAP ERP / GTS integration is not related to the WM topic; therefore you don't need the "hazardous substance master" which you would need for WM/eWM checks; the link you have used does not talk about a "WM integration"

2.) Don't mix the SAP ERP GTS integration with the "notification status check" (little bit different topic)

These would be my questions to you

1.) we need to integrate SAP EHS(EHP-6) with GTS and got below details. => why do you would like to integrate? what is the business background? Sometimes only a SVT related solution might be sufficient

2.) Do you yet use SAP GTS and therefore SAP ERP <=> SAP GTS integration is active?

3.) which SAP GTS release do you use?

4.) Which processes are still active in SAP GTS?

PLease read cross:

C.B.

PS: may be check

[former_member380918]

Thank you Christoph for your response and sharing documents.

Current business requirement to update GTS Hazardous Check Flag for Hazardous materials identified in ECC by EHS.

Our GTS version is 10.1

We are looking for some custom solution to determine hazardous material based on criteria defined by business and then updates hazcom indicator in GTS compliance.

[christoph_bergemann]

Dear Naveen

1.) current GTS Version is I believe 11.0; so you are one majorrelease "!ower"

2.) I have still problems in understanding your objective

I try the other way: Normally the set up is like: you have a seperate SAP ERP system and a SAP GTS system. You do a configuration in SAP ERP and SAP GTS. IN the "daily" business master data is replciated from SAP ERP to SAP GTS (e.g. material master data, business partner data) but as well nay kind of"logistic document (based on set up). E.g. purchase order, sales order... Now in SAP GTS a process is running ro find relevant regulations. If set zp is done properly the the "Hazardous check" comes in place. In this case a RFC call from SAP GTS is done to SAP EHS some data is collected and this data is passed back to SAP GTS; then the "hazardous flag" is "set" or not (and process later in SAP ERP is stopped or not)

Conclusion: the SAP general set up is: you don't need a customs solution; the "only" topic is to decide which kind of checks shouldbe doen on SAP ERP process during the SAP GTS call

Therefore: yes you are right: the criteria" for hazardness are defined by business but overall I would not use the term "customs solution" but a SAP based solution (as you use a kind of "exit" to determine the "hazardness" ; and Exists are standard. The code is clealry customer specific)

C.B.

PS: The online help explain the process quite well ( I have marked the relevant part) (this is only a part of the explanation; please check online help)

The results of the checks in SAP EH&S are saved as status values in the customs documents in SAP GRC GTS, which are created as replicates for the following logistics documents:

• Sales documents (SD0A)
• Outbound deliveries (SD0B)
• Purchasing documents (MM0A)

When the hazardous substance check sends a status to SAP GRC GTS that prevents further processing of the business transaction, the system blocks the corresponding customs document.

[former_member380918]

Christoph,

Thanks for your valuable inputs. These inputs helps in really deriving discussion with business and GTS further.