Issue

Succinctly describe the issue or problem statement that this Decision addresses. Why is a decision required? What business or technical problem does it address?

S/4 HANA offers the option to implement 'Classic Version' of 'New Version' for Product Compliance as part of the ERP Rebuild project.  A decision is required, which S/4 HANA version should be implemented considering scope, timelines as well as licensing.  

Recommendation

Optionally supplement with additional details or diagrams if required, else delete this 'Details' section.

Based on the evaluation as per 'Details' section, the recommendation is to implement the 'Classic Version' of S/4 HANA Product Compliance.  The recommendation is mainly driven by the fact that the 'New Version' is available for implementation from 2027 with limited scope only.  

A decision for 'Classic Version' needs to consider that an new ERP project will be required additional green field impl

Background & Context

Explain the context in which the decision is being made.

S/4 HANA Product Compliance includes the following components:

1. Dangerous Goods Management (incl. Substance Volume Tracking)
2. Product Marketability and Component Compliance (Product Safety)
3. Compliance Document Management (Product Safety)

S/4 HANA EHS includes the following components:

1. Emissions Management
2. Waste Management
3. Incident Management
4. Industrial Hygiene
5. Occupational Health

S/4 HANA for Product Compliance offers two sets of capabilities in Private Cloud.  S/4 SAP EHS and Sustainability do not offer different sets of capabilities in Private Cloud.

1) Existing (classic) capabilities - Classic Version

• All features of the SAP ERP based product safety and product compliance solutions
• SAP GUI and Web Dynpro transactions
• Specification database, workbench approach
• Full scope, no functional enhancements

2) New capabilities - New Version

• 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

Assumptions

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited. 

Constraints

Capture any additional constraints that the chosen alternative (i.e. the decision made) might impose on other parts of the overall design, solution, or processes.

Impacts

Describe the impact of the decision on processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.

Licencing

All capabilities of business area "Product Compliance" are available in S/4HANA, but the exact scope may vary compared to the ECC-based products.  Options are:

• You have licensed "SAP S/4HANA" and "SAP S/4HANA for product compliance": you have the choice to either use the so-called "classic functionality" or the "new functionality". For more details please check the attached presentation.
• You have subscribed to "SAP S/4HANA Cloud, private edition" and "SAP S/4HANA Cloud for product compliance, private edition": you have the choice to either use the so-called "classic functionality" or the "new functionality". For more details please check the attached presentation.
• You have subscribed to "SAP S/4HANA Cloud, public edition" and "SAP S/4HANA Cloud for product compliance, public edition": you can use the Product Compliance "new functionality".

Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 

Options considered

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Option A: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option B: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option C: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option D: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

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.

	Weight	Option A	Option B	Option C	Option D
Compliance and Regulatory		Pro Con	Pro Pro	Pro Con	Pro Con
Business Impact		Pro Con	Con	Pro Pro	Con Con
Risk		Pro Con
Complexity		Pro Con Pro	Pro Con	Pro Con	Pro Con
Integration		Pro Con
Longetivity		Pro Con

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

SAP OSS Note Product Compliance: Strategy and Roadmap Overview:  3015382_E_20240627 (sap.com)

SAP presentation as per SAP workshop at Walldorf June 2024:  

Change log

Workflow history