SAP for Chemicals Discussions
Ignite conversations about maximizing efficiency, enhancing safety, and innovating in the chemicals industry with SAP. Start a discussion today.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SAP S/4HANA for Product Compliance: How to set up "triggers" for Volume/Mass regulatory limits?

Paulo_Pinto
Participant

a month ago - last edited a month ago

Hello dear community.

I have a challenge that needs to be solved:

Some substances may have volume or mass regulatory limits regarding its business transactions, i.e., my customer is licensed to sell only 1000 kg per year of a certain regulated substance. This is a type of regulatory limit for this substance, albeit company-specific (other companies may have different amount values to which they have to comply).

Is it possible, in SAP S/4HANA for Product Compliance, to set up a stop sales "trigger", regarding this type of regulatory limit? Or does it have to be set up from other SAP functionality?

Many thanks in advance.

6 REPLIES 6

Mark-Pfister
Active Contributor

a month ago - last edited 4 weeks ago

HI @Paulo_Pinto,

In the classic scenario - which is still working under S/4HANA - Substance Volume Tracking can do this for you: Track the substance amounts and then block sales orders and deliveries. See the answer from @MarkoLange.

And this functionality will come in the new "S/4HANA for product compliance" as well.... it is just not fully there yet to my knowledge... 

Were you able to get the substance volume tracking to work in "S/4HANA for product compliance"?

Best

Mark

 

Nathish
Explorer
In response to Mark-Pfister

2 weeks ago

Hi @Mark-Pfister and @MarkoLange 

We are implementing the S/4 HANA public cloud 2402 version, and we explored the SVT scope. 

We found a few more gaps and doubts raised during the client demo. 

1. We were able to monitor the substance quantities but there is no feasibility of having SVT check/blocking functionality to block import and sales doc when the limit is reached. 

2. We can able to maintain the threshold limit based on substance level only not on the legal entity level. Because in standard we were used to maintain the different threshold limit values for multiple legal entities for the same substance. Any clarification, please? 

3. Also we can see only "Confirmed Quantity" only in the substance volume report. Not sure why the "Planned Quantity" was not tracked in the SVT monitor app.

4. In the public cloud the legal entity creation and mapping are master data now. Any possible way is there to import/export to different client (DEV, QA, PROD)

Looking for your valuable replays. Many thanks in advance.

Thanks & Regards,

Nathish

MarkoLange
Advisor
Advisor
In response to Nathish

2 weeks ago

0 Kudos

I do not think that you detected gaps here. In case of difficulties please issue an OSS note since I cannot support your project remotely through this channel.

Sorry and kind rgds

Marko

Nathish
Explorer
In response to MarkoLange

2 weeks ago

0 Kudos

Hi @MarkoLange 

Thanks for the response. Yes, all of these questions were asked during the client demo. If you have inputs for these questions as a standard process please help. It will be much appreciated and also we will raise an OSS note to check.

Thanks in advance.

Regards

Nathish

MarkoLange
Advisor
Advisor

4 weeks ago

Yes this is possible. The functionality is called substance volume tracking. With that you can define various compliance scenarios in parallel. Within those scenarios you define which substances, which Thresholds and which transactions shall be monitored. All depending on the regualtion the sceario is set-up for. Most important in that context are REACH and TSCA but I know customers that do it for more than adozen pf regulations world-wide. Quite powerful and highly recommended.

christoph_bergemann
Active Contributor

2 weeks ago - last edited 2 weeks ago

Hello

the "SVT" solution is from my point of view using SAP roadmap data and other informations from SAP not ready to be used now in "Product Compliance". Please check the corresponding SAP roadmap. SAP has provided a SAP OSS consulting note describing the roadmap of EHS Classic and Product Compliance. This document contains the best knowledge (in combination with the "Roadmap explorer" on the status of SVT iin the new solution

The new SVT solution (based on best knowledge) is having different internal design than EHS SVT classic

C.B

PS: AND YES: if you use a "Cloud Version". you might profit from the fact that here SAP is delivering "faster". For the "On premise" version: we have now to wait 2 years (until roughly november 2025) to get the next major update. 

The "EHS SVT Classic" solution can be used in S/4 HANA envirnment without problems