| Status | |
| Owner | The person responsible for driving this decision and documenting it. Type @ to mention people by name |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Issue
There are several SAP development system configuration approaches available for the project, each offering different levels of pre-configured settings and customization. This document aims to evaluate and recommend the most suitable approach for the project based on its specific requirements, complexity, and business goals. The available options are:
- From Client 000: A basic starting point that involves copying the initial, out of the box config client
- From SAP Best Practices: A pre-configured solution based on SAP’s industry-standard templates, offering a fast and efficient way to implement best practices for various business functions.
- From standard EML (Enterprise Management Landscape): A configuration based on a standard SAP best practice setup, providing a predefined structure and set of business processes commonly used across various industries
- From ChemDirect by Accenture: A specialized solution developed by Accenture for the chemical industry based on the SAP best practice, offering a highly tailored configuration designed for businesses in this sector.
This document will assess the advantages, limitations, and suitability of each approach to determine the best fit for the project’s scope and objectives.
Recommendation
Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.
Background & Context
SAP Client 000: is initial and base client created during the SAP S/4HANA system setup. It is the starting point for system configuration and administration tasks. It provides basic, unconfigured environment to start configuring the system, typically without any business-specific data. The customizations in this client are provided out of the box by SAP for a model company. The client can then to copied to other client for company specific config and customizations. Following are some of the uses:
- System Administration: Used by SAP Basis and system administrators for tasks like system configuration, user setup, and client management.
- Development Setup: As the initial client in the system, it can serve as the foundation from which other clients are created for different purposes(e.g., development, data, testing etc.).
- Testing and Troubleshooting: In some cases, Client 000 can be used for initial testing and troubleshooting before applying specific business configurations to other clients.
This client has been in existence since R3 version and SAP has incrementally delivered the content. Therefore this client contains configuration used for ECC which is not in line with SAP recommended usage of S/4HANA.
SAP Best Practices Client: provides a valuable set of industry-aligned templates and pre-configured processes that enable organizations to implement SAP solutions quickly, efficiently, and with lower risk. These best practices serve as a solid foundation for businesses looking to adopt SAP software, particularly for those who want to follow industry standards while maintaining flexibility for further customization. By leveraging SAP Best Practices, organizations can ensure smoother transitions to SAP environments, whether on-premise or in the cloud, while optimizing their business processes from the outset.
SAP EML: provides a ready-to-use global template with standard end-to-end business processes, based on leading best practices and real-life implementation experience.
Accenture ChemDirect: ChemDirect is a system built on SAP best practices
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 constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.
Impacts
Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
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
Following are the options considered
Option A: SAP Client 000
SAP Client 000 is the default base client created during the SAP S/4HANA system installation. It serves as the foundational environment for initial system setup, administration, and configuration. Delivered by SAP with standard settings and templates, this client is devoid of any business-specific data, allowing administrators to configure and customize the system as required. Client 000 can be copied to create additional clients, which are tailored for specific business purposes, such as development, testing, or production environments.
Uses of Client 000
System Administration: Client 000 is heavily utilized by SAP Basis consultants for essential system administration tasks, including system configuration, user creation, and client management.
Development Setup: As the initial client, it serves as the baseline from which other clients can be created for diverse purposes, such as development, testing, or production.
Testing and Troubleshooting: In some scenarios, Client 000 is used for basic testing and troubleshooting before deploying configurations to other clients.
Client 000 has all the basic configs since R3 and therefore easier for the functional consultants and development team to configure. However, it also has a lot of redundant configs that not relevant/optimised for S/4 Hana. Stricter governance process is required to make sure that the non-relevant config is not used as part of ERP Rebuild project.
Client strategy in this option:
Client | Usage | Config | Process Models | Test Scripts |
|---|---|---|---|---|
000 | Base client. The client is locked and no config/data is allowed | No config allowed | Not available | Not available |
050 | Copy of client 000. Client used for Development , Data and testing. | Base config copied from 000 Additional/Syensqo specific Config to be done by the consultants using SPRO. | Not available | Not available |
Option B: SAP Best Practise
The SAP Best Practices Client is designed to provide organizations with a set of industry-aligned templates and pre-configured processes. These templates simplify and accelerate the implementation of SAP systems, offering a robust foundation for businesses to follow industry standards while retaining the flexibility to customize. There are a total of 349 unique best practice processes relevant for S/4 HANA 2023 and 193 are valid for Syensqo (refer to the attachments for more details).
Uses of the SAP Best Practices Client
Rapid Deployment: Pre-configured settings reduce the time required to deploy SAP systems.
Industry Standards: Ensures organizations align their processes with globally recognized best practices.
Customizable Foundation: While providing ready-made templates, businesses can modify them to meet unique operational needs.
SAP Best Practices content configures a client with automatic content activation. It contains only essential configuration settings for the selected scope. There are 2 options of enabling the best practices content
Best Practices Client - configuration tables that are not covered by the Best Practices content are empty.
Merged Client - with all client 000 config and the config from Best Practices
Alternative | Name | Best Practice Content | Client 000 Content | Initial Configuration Effort in Areas Covered by BP | Initial Configuration Effort in Areas Not Covered by BP | Risk of having non-Relevant config in the system |
|---|---|---|---|---|---|---|
1 | Best Practices client (BP Client) | Yes | No | Lower | Higher - 2 | Lower |
2 | Merged client (with all client 000 reference settings and BP content) | Yes | Yes | Lower | Lower | Higher |
Based on the above, following is the recomendation provided by SAP
If the project scope is large and is not covered by Best Practices content: choose a merged client
If the Best Practices content covers all or nearly all of project requirements (based on a review of the delivered process flows): choose a Best Practices client
Client Strategy in this option
Client | Usage | Config | Process Models | Test Scripts |
|---|---|---|---|---|
000 | Base client. The client is locked and no config/data is allowed | No config allowed | Not available | Not available |
050 | Best Practises Client | BP Content is activated | Available | Available |
100 | Development Client based on the best practices client | BP Content is activated Additional/Syensqo specific Config to be done by the consultants using SPRO. | BP process models should be updated based on the Syensqo specific config | BP test scripts should be updated based on the Syensqo specific config |
Option C: SAP EML
SAP EML delivers a global, ready-to-use template that includes standard end-to-end business processes based on SAP’s best practices and real-world implementation experience. It is designed to serve as a universal foundation for businesses across various industries, ensuring streamlined adoption of SAP solutions.
Uses of SAP EML
Global Template: Offers a single configuration that can be used across multiple geographies.
End-to-End Processes: Covers a comprehensive range of business processes, including procurement, sales, finance, and logistics.
Scalability: Ideal for large organizations operating in multiple regions with diverse business requirements.
EML is built in an SAP internal staging area based on customer requirements that are communicated to SAP in a questionnaire and then deployed in Syensqo environment via the database backup / restore technology.
Hence, the enterprise management layer can only be deployed as an appliance (or system), it cannot be activated or partially activated based on transports or BC sets. It cannot be combined with a legacy system nor with already activated SAP Best Practices in a system.
Following are all the processes which are not covered as part of best practices and are available in EML as service items
- Intercompany Processes (between 2 countries)
- Cross-plant stock transfers within 1 county of your choice
- Project System for Accounting
- Engineering Projects
- Billing of Projects (within 1 country) for fixed price and resource-related billing
- Intercompany Billing of Projects (between 2 countries) for fixed price and resource-related billing
- Intercompany Billing of Services
Client Strategy in this option
| Client | Usage | Config | Process Models | Test Scripts |
|---|---|---|---|---|
000 | Base client. The client is locked and no config/data is allowed | No config allowed | Not available | Not available |
| 100 | EML delivered Config & sample master data | No config allowed | Available | Available |
| 400 | Config only Use for Syensqo specific configuration | Allowed | EML process models should be updated based on the Syensqo specific config | EML test scripts should be updated based on the Syensqo specific config |
| 050 | Backup of client 100 Use as a safety net, to review original status of configuration and master data. | No config allowed | Available | Available |
| 010 | Embedded BI / Copy of client 000 Purely technical client, required for Fiori app functionality. Can be used to set up embedded BI. | No config allowed | Not available | Not available |
Option D: Accenture ChemDirect
Accenture ChemDirect is a specialized solution built on SAP Best Practices, tailored specifically for the chemical industry. It addresses the unique requirements of chemical companies, including compliance with industry regulations, handling hazardous materials, and managing complex supply chains.
Uses of ChemDirect
Chemical-Specific Processes: Provides pre-built workflows and templates designed for chemical manufacturing and distribution.
Compliance Management: Helps ensure adherence to industry regulations and standards.
Supply Chain Optimization: Streamlines the handling of complex supply chains common in the chemical sector.
Evaluation
Following is the comparison and evaluation of all the options.
| Option A: SAP Client 000 | Rating | Option B: SAP Best Practise | Rating | Option C: SAP EML | Rating | Option D: Accenture ChemDirect | Rating | |
| Functionally Coverage | Basic SAP out of the box config | Low | Covers around 349 unique scope items including Inventory, EWM, GTS etc.. | High | EML contains a subset of SAP best practices ~308. EML coverage is finance heavy | Medium | A subset of best practices ~209 and 57 scenarios that Accenture built. | Medium |
| Applicability for Syensqo | A lot of config still exists in Client 000 which is not relevant for Syensqo. | Low | 193 scope items are applicable for Syensqo | High | 170 out of 193 scope items are available in EML | Medium | 154 out of 193 scope items are available in Accenture. Out of these 47 scenarios are enhanced with WREFUMS 2 of 57 scenarios developed by Accenture are applicable for Syensqo out of the box. All the other scenarios require some development / additional configuration 3 of 47 scenarios developed by Accenture are applicable for Syensqo. The others are not applicable or built in wron technology ex: Datasphere is used for reporting in Syensqo and a majotity of the reports are built in S/4 or BW. GUI transactions are enhanced where syensqo uses Fiori | Medium |
| Speed of deployment - Instances | Available out of the box - No additional downtime required | High | Scope items needs to be activated. | Low | EML is installed as an appliance and therefore no downtime | Medium | Transports needs to imported | Medium |
| Quality of the scope items | Not all configuration is tested by SAP | Low | No tested thoroughly by SAP | Medium | Tested by EML team before the appliance is deployed | High | Tested by Accenture team | High |
| Config Effort | 80% -Most of the config has to be done by the consultants from Scratch | Low | 70% - Some of the config provided out of the box can be re-used. Missing config needs to be copied from Client 000 | Low | 70% - Some of the config provided out of the box can be re-used. Missing config needs to be copied from Client 000 | Low | 70% - Some of the config provided out of the box can be re-used. Missing config needs to be copied from Client 000 | Low |
| Additional rework by consultants | None | High | Minimal amount of rework - Majority of the config delivered is not disruptive Test scripts, Documentation will also need to be changed based on the changes in the config | Medium | Maximum rework - A lot of pre-delivered content has be enhanced from the best practise content and will need additional effort to clean it up if not used by Syensqo Test scripts, Documentation will also need to be changed based on the changes in the config | Low | Maximum Rework - Multiple enhancements and pre delivered content that needs to be cleaned-up or updated based on Syensqo scenarios Test scripts, Documentation will also need to be changed based on the changes in the config | Low |
| Documentation - Process Models | No documentation available | Low | Process models available in Signavio, however different module are represented at different levels | High | Process models available in Signavio, however different module are represented at different levels | High | Process models are drawn in Visio - BPMN format not followed | Low |
| Test Scripts | No test scripts | Low | Test scripts available for out of box best practise scenarios | High | Test scripts available | High | Test scripts available | High |
| Localization | Localization existing in out of the box config - However not very consistent | Low | Cover 42 countries | Medium | 43 countries with full scope and 6 countries with a reduced, Finance-centric scope that covers statutory requirements | High | Not known | N/A |
| Risks | Might cause issues with upgrades if compatibility items config i.e. old ECC config exists | Medium | No issues with upgrades | High | No issues with upgrades | High | Might cause issues with upgrades if compatibility items config i.e. old ECC config exists | Medium |
| Cost | No additional cost | High | No additional cost | High | Additional Cost | Low | Additional Cost | Low |
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.
