cancel
Showing results for 
Search instead for 
Did you mean: 
JohannesReichel
Employee
Employee

Summary

You are currently using Product Compliance (Product Safety and/or Product and REACH Compliance) in SAP ECC. You are now considering to move to SAP S/4HANA.

Business Requirements

Product Compliance comprises the following main components:

  • Product Marketability and Chemical Compliance: ensure compliant products for certain markets
  • Dangerous Goods Management: ensure compliant transport
  • Safety Data Sheet and Label Management: ensure compliant hazard communication
JohannesReichel_0-1669644892753.png

Please note: The classic Product Compliance solutions in SAP ECC have been re-named:

  • SAP EHS Management Product Safety => SAP Product Safety
  • SAP EHS Management Product and REACH Compliance for Discrete Industries  => SAP Product and REACH Compliance

Solution Options

When moving to SAP S/4HANA the following options are available for Product Compliance:

  1. "New functionality": SAP S/4HANA for product compliance
  2. "Classic functionality": SAP Product Safety and SAP Product and REACH Compliance
  3. "Compatibility Scope": continue using classic functionalities as part of the SAP S/4HANA compatibility scope

Characterization of the Solution Options

Option 1: "New functionality": SAP S/4HANA for product compliance

SAP S/4HANA for product compliance is a complete renewal to make best use of the capabilities that come with the S/4HANA platform:

  • New process model
  • SAP Fiori apps
  • New data model, CDS-based
  • New integration into product master, sales, delivery, procurement, transportation
  • No full scope yet, Innovation roadmap

Option 2: "Classic functionality": SAP Product Safety and SAP Product and REACH Compliance

  • (Almost) All features of “SAP Product Safety”  and “SAP Product and REACH Compliance” (not available anymore: Waste Management, MSDS Maker, Genifix) 
  • SAP GUI transactions
  • Specification database, Workbench approach
  • Full scope, No functional enhancements

Option 3: "Compatibility Scope": continue using classic functionalities as part of the SAP S/4HANA compatibility scope

  • All features of “SAP Product Safety”  and “SAP Product and REACH Compliance”
  • Full scope, no functional enhancements
  • End of usage right by end of 2025

Please note:

For Option 1 and Option 2, the product compliance capabilities are technically part of the corresponding SAP S/4HANA on-premise or cloud options (option 2 only in private cloud), but require a separate license. This means that there is no need to implement a separate add-on for product compliance. However, the product compliance capabilities in SAP S/4HANA are not covered by the SAP S/4HANA user licenses.

Availability, Use rights, and Mainstream maintenance

Option 1: "New functionality": SAP S/4HANA for product compliance

  • Available in current SAP S/4HANA release (cloud and on-premise), no additional add-on
  • Full functional scope planned by 2026
  • additional license necessary
  • Maintenance follows general SAP S/4HANA maintenance

Option 2: "Classic functionality": SAP Product Safety and SAP Product and REACH Compliance

  • Available in current SAP S/4HANA release (only private cloud and on-premise), no additional add-on
  • switch of license necessary
  • SAP S/4HANA release 2029 will be last supported release for classic functionalities. 

Option 3: "Compatibility Scope": continue using classic functionalities as part of the SAP S/4HANA compatibility scope

  • usage only possible until end of 2025

Criteria to determine the most suitable target solution

Deployment Preference

  • Public Cloud: Only Option 1: "New functionality" is currently available 
  • Private Cloud: all options are available, however,  the infrastructure for WWI-Server and EHS-Expert servers are not included. This must be either handled by the customer himself or customer needs to ask SAP / hyperscaler to handle this in addition.
  • On-Premise: all options are available

Functional Scope

  • Option 1 does not yet cover the full scope of product compliance capabilities compared to Option 2 and 3.
  • Therefore, evaluate what product compliance functionalities are required today and in future and compare the evaluation with the different options while considering the innovation roadmap for Option 1.

Time of SAP S/4HANA Transition

  • Before 2026: compare functional scope and in case Option 1 does not cover critical and required capabilities consider Option 2 or Option 3 (end of usage right end of 2025!)
  • After 2026: full scope of Option 1 might be available, consider moving to new functionalities as part of Option 1

Level of Process Redesign

  • Brownfield, i.e. no or only limited level of process redesign: Option 2 or Option 3 (end of usage right end of 2025!)
  • Greenfield, i.e. high level of process redesign: Option 1 (if functional scope available). Alternatively, Option 2, however, latest after SAP S/4HANA release 2029 a transition to Option 1 is mandatory.

Decision Tree

 

JohannesReichel_0-1669645885171.png

 

Conclusion

From a strategic roadmap perspective, Option 1 with the new functionalities is the right option. However, as the functional scope might not yet cover all requirements, Option 2 could be an alternative for an interim period until SAP S/4HANA 2029. 

Version history
Last update:
‎11-28-2022 6:36 AM
Updated by:
Contributors