Status
Owner	ROUT-ext, Praksh
Stakeholders	FLOURIE, Marie

Issue

Syensqo currently uses the following SAP functionalities in ECC to cover HSE requirements relating to Safety Datasheets, Labelling, Dangerous Goods

Management, Substance Volume Tracking and Compositions.

Composition
Product Classification
Company Substance Management
Raw Materials Management
Mass Upload / Modification (User Accessible)
Other Documents Authoring
SDS Template and Generation
SDS Authoring Automation Algorithm (“Expert Rules”)
SDS Distribution
Poison Center Notification
SVT(Substance Volume Tracking
SVHC(Substance of Very High Concern)
Dangerous Goods Management

These SAP functionalities can be supported either through standard features or with enhancements in SAP Product Compliance within S/4HANA.

S/4HANA offers the option to implement these functionalities in 'Classic Version' or 'New Version' for SAP Product Compliance. A decision is required, which functionality fall under which version of S/4HANA Product Compliance (NEW or CLASSIC) should be implemented.

S/4HANA provides the flexibility to implement these functionalities either in the ‘Classic Version’ or the ‘New Version’ of SAP Product Compliance. A decision needs to be made regarding which functionalities should be implemented under which version (Classic or New) based on the specific requirements.

Recommendation

Recommendation:

Name of the Functionality	CLASSIC vs NEW Recommendation	Recommendation to replicate or not Custom Enhancements from ECC to S4 Classic
Composition	CLASSIC - Since the BOMBOS Interface is not available in the NEW version, it should be maintained in CLASSIC. Then it needs to be transferred back to the NEW system in order to be utilized in Compliance Requirements.	We will replicate the ECC custom expert rules related to composition management to maintain the high level of automation already achieved. This includes rules such as ZCP_BOMBOS (copy of BOMBOS output → Exact Composition), ZCP_STD (Standard Composition Calculation), ZCP_RM_WRS (Worst Case Composition based on REAL_SUB_E), and ZCP_STDRSE (Worst Case Standard Composition for RSE).
Product Classification	CLASSIC - Since the Product Classification functionality not available in S4 NEW.
Company Substance Management	NEW	No replication of custom developments. "Own registration" in NEW should cater for the use case. Assumption that current custom reporting can be performed with off the shelf or else (e.g in datasphere)
Raw Materials Management	CLASSIC + NEW	Some custom enhancements will be replicated to S4 CLASSIC from ECC (raw materials data management based on suppliers SDSs) to keep the high level of automation achieved and follow 3E VSDS Loader transition roadmap from CLASSIC to NEW. However back to standard for functionalities related to data quality and cleansing.
Mass Upload / Modification (User Accessible)	CLASSIC	Replicate in S4 CLASSIC from ECC to allow User execute the SDS authoring task in mass
Other Documents Authoring	CLASSIC - Since the Authoring functionality not mature in S4 NEW (also SAP recommendation as per our project's timeline)	Replicate RDS (Regulatory Data Summaries) authoring in S4 CLASSIC from ECC but Certificates authoring in WWI will be discontinued (other standard functionalities may be leveraged for this).
SDS Template and Generation	CLASSIC - Since the SDS Template(WWI) & Generation functionality not available in S4 NEW.	Replicate the ECC custom templates to S4 CLASSIC with Migration of WWI templates and the associated specific characteristics (and some function modules), as they are except for: CH1 address, logo and emergency telephone numbers, where recommendation is to go back to standard
SDS Authoring Automation Algorithm (“Expert Rules”)	CLASSIC - Since the SDS authoring functionality not available in S4 NEW.	Replicate the ECC custom expert rules related to SDS authoring to S4 CLASSIC to maintain high level of automation already achieved
SDS Availability Check	NEW - SDS availability check functionality in S/4HANA NEW is mature and ready for implementation.
SDS Distribution	NEW - SDS distribution functionality in S/4HANA NEW is mature and ready for implementation.
Product Marketability	NEW - Product Marketability functionality in S/4HANA NEW is ready for implementation.
Poison Center Notification	CLASSIC - For S4 NEW Opesus currently evaluating specifically regarding availability timelines and any related documentation. For S4 CLASSIC Opesus has officially confirmed support for the classical solution in S/4HANA.
SVT(Substance Volume Tracking)	CLASSIC - Since the SVT functionality is NEW does not cover notifications for quantity limits yet (also SAP recommendation as per our project's timeline)
SVHC(Substance of Very High Concern)	NEW - via standard marketability features	Assumption that current custom reporting can be performed with off the shelf or else (e.g in datasphere)
Dangerous Goods Management	NEW - DG functionality in S/4HANA NEW is mature and ready for implementation.

Background & Context

Please refer the previous KDD KDD037 - SAP S/4HANA Version for Product Compliance

Assumptions

Customer is migrating to or already using S/4HANA Product Compliance (New).

It is assumed that:

SAP currently indicates that nearly all features from SAP Product Safety and SAP Product and REACH Compliance are available in S4 NEW version.
Any impacts arising from this KDD on other SyWay Project EHS KDDs will be addressed through subsequent KDDs related to the respective SyWay Project EHS components.
The SyWay Project will not result in an unsupported platform, following platform license negotiations, and a supported S/4HANA version will serve as the core platform (see related KDDs listed under 'References').

Constraints

Functional Gaps and Feature Limitations
Migration Complexity and Data Consistency
Custom logic via BAdIs might increase implementation effort and complexity.
There’s no UI-based Rule Editor as intuitive as the CG02 Expert Rule Editor.
A decision for 'Classic Version' would need to consider that a reimplementation of Product Compliance will be required before 2036 for a
greenfield implementation of 'New Version' for S/4 HANA Product Compliance.
SAP have not been able to provide clear guidance on the roadmap and alignment beyond 2025 of S/4HANA features at the time of writing.

Impacts

Impacts of using the hybrid adapter include:

Users may need to work with a dual data model, increasing complexity.
Dependence on 3E technology and its future roadmap introduces potential risks.
Potential misalignment of regulatory content between the New and Classic versions could lead to inconsistencies.

Business Rules

Business rules may be required to ensure alignment between the New and Classic versions of Product Compliance—for example, in areas such as SDS Version Management, Composition Management.

Options considered

Hybrid (CLASSIC + NEW)

The Hybrid approach leverages selected capabilities from both the Classic and New Versions of Product Compliance within a single S/4HANA system, with the 3E Hybrid Adapter facilitating data synchronization between the two data models.

The 3E Adapter, an ABAP add-on, connects processes in the New Version to those in the Classic Version by replicating data from the Classic data model into the New one.
Both data models can coexist in the same S/4HANA system—no separate system landscape is required.
The solution includes embedded regulatory content and a multi-lingual phrase library.
Capabilities are gradually transitioned from the Classic to the New Version in a phased manner, helping to bridge existing functionality gaps.
This approach supports smaller, incremental implementations over time instead of a single large-scale transition ("Big Bang").
User impact is minimized, as users will continue working within the same S/4HANA system, using familiar SAP GUI and Web Dynpro applications for Classic functionality

Based on the functionalities outlined above, the following approach is recommended for adoption:

Name of the Functionality	Recommended Product Compliance Version	Rational
Composition	CLASSIC	We will replicate the ECC custom expert rules related to composition management to maintain the high level of automation already achieved. This includes rules such as ZCP_BOMBOS (copy of BOMBOS output → Exact Composition), ZCP_STD (Standard Composition Calculation), ZCP_RM_WRS (Worst Case Composition based on REAL_SUB_E), and ZCP_STDRSE (Worst Case Standard Composition for RSE).
Product Classification	CLASSIC	Since the Product Classification functionality not available in S4 NEW.
Company Substance Management	NEW	No replication of custom developments. "Own registration" in NEW should cater for the use case. Assumption that current custom reporting can be performed with off the shelf or else (e.g: in Datasphere)
Raw Materials Management	CLASSIC + NEW	Some custom enhancements will be replicated to S4 CLASSIC from ECC (raw materials data management based on suppliers SDSs) to keep the high level of automation achieved and follow 3E VSDS Loader transition roadmap from CLASSIC to NEW. However back to standard for functionalities related to data quality and cleansing.
Mass Upload / Modification (User Accessible)	CLASSIC	Replicate in S4 CLASSIC from ECC to allow User execute the task in mass
Other Documents Authoring	CLASSIC	Since the Authoring functionality not mature in S4 NEW (also SAP recommendation as per our project's timeline) Replicate RDS (Regulatory Data Summaries) authoring in S4 CLASSIC from ECC but Certificates authoring in WWI will be discontinued (other standard functionalities may be leveraged for this).
SDS Template and Generation	CLASSIC	Since the SDS Template(WWI) & Generation functionality not available in S4 NEW. Replicate the ECC custom templates to S4 CLASSIC with Migration of WWI templates and the associated specific characteristics (and some function modules), as they are except for: CH1 address, logo and emergency telephone numbers, where recommendation is to go back to standard
SDS Authoring Automation Algorithm (“Expert Rules”)	Classic	Since the SDS authoring functionality not available in S4 NEW. Replicate the ECC custom expert rules related to SDS authoring to S4 CLASSIC to maintain high level of automation already achieved
SDS Availability Check	NEW	SDS availability check functionality in S/4HANA NEW is mature and ready for implementation.
SDS Distribution	NEW	SDS distribution functionality in S/4HANA NEW is mature and ready for implementation.
Product Marketability	NEW	Product Marketability functionality in S/4HANA NEW is ready for implementation.
Poison Center Notification	CLASSIC	For S4 NEW Opesus currently evaluating specifically regarding availability timelines and any related documentation. For S4 CLASSIC Opesus has officially confirmed support for the classical solution in S/4HANA.
SVT(Substance Volume Tracking)	CLASSIC	Since the SVT functionality is NEW does not cover notifications for quantity limits yet (also SAP recommendation as per our project's timeline)
SVHC(Substance of Very High Concern)	NEW	Using Standard Marketability Features Assumption that current custom reporting can be performed with off the shelf or else (e.g in Datasphere)
Dangerous Goods Management	NEW	DG functionality in S/4HANA NEW is mature and ready for implementation.

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

	Hybrid (CLASSIC + NEW)
Compliance	Pro: Synchronization between classic and new version. Pro: Implementation projects are expected to be of smaller scale due to phased approach.
Risk	Pro: Disengaging the timeline of SyWay project from Classic to New version roadmap minimizes the risk. Pro: Means smaller scale implementations spread over time rather than 'Big Bang' from Classic to New Version.
Business Impact	Pro: The recommendation enables Syensqo to implement newly available S/4HANA Product Compliance functionality based on business readiness. Con: User impact potentially dealing with two different S/4HANA versions on day-to-day basis
Complexity	Pro: Functionalities implemented from Classic to New Version in phased approach bridging capability gaps. Pro: Business benefit of new features to cover future requirements without having to cover scope gaps with additional enhancements. Pro: Alignment between new and classic version via RFC connection. Con: Additional complexity of migrating from ECC to classic and new version. Con: Version management alignment between new and classic version
Integration	Pro: Combination of embedded data as well as optimizing integration between new and classic version with regards to functionality and data.
Longevity	Pro: Business benefit of new features to cover future requirements without having to cover scope gaps with additional enhancements. Pro: Full scope available until 2036 with standard maintenance for 'Classic Version' features