Navigating the Detailed Discovery

For new implementations with SAP S/4HANA Cloud Public Edition, the Detailed Discovery gathers information about integrations with other SAP cloud solutions the customer may already have or be planning to purchase, localizations, SAP Best Practice business process requirements, and details about individual business processes.

To make it easier for customers to select the right business processes across the different line of business areas, there are pre-selection packages for the following scenarios:

• Baseline, which covers key end-to-end processes for a company in the areas of Sales, Finance, and Procurement. Core processes include Invoice to Cash, Order to Fulfill, Record to Report and Procure to Receipt. This is also the bundle of processes that would be activated if a customer chooses to purchase the optional add-on service called Baseline Activation Service for SAP S/4HANA Cloud to get a public cloud system up and running within four weeks.
• Finance-Led ERP, which covers key financial management best practices to run administrative ERP, including procurement and sales capabilities.
• Service Centric ERP, which includes the Finance-Led ERP bundle, in addition to project and service-related capabilities with industry-specific capabilities to support service-oriented industries for midsize and large companies.
• Product Centric ERP, which includes all capabilities required to run make-to-stock-based production followed by selling the produced goods from stock.

The partner or SAP internal sales person works through each line of business area with the customer decision makers. For each individual business process, the priority and rollout phase can be selected, and questions or notes can be added to provide follow-up information.

Each three-digit link (2LH, BNX, etc.) points to the source documentation of the process in Signavio Process Navigator.

After all business processes have been reviewed, additional requirements related to the processes can be entered, and detailed project and scope-related questions are completed, such as the target customer go-live date.

The completed Detailed Discovery is submitted to the Brand Guardian team who reviews the final solution recommended by the Digital Discovery Assessment and either confirms or changes the recommendation based on their deep knowledge and experience. An email notification is sent with the final solution recommendation for the customer.

When you navigate back to the Supply Chain of Selling app after completing the Detailed Discovery, additional information will become available.

For example, the Scope Localization tab displays a mapping between the selected business processes and countries/regions. Not all business processes are available for all countries/regions, and this tab shows you where those differences are. It also shows which business processes are included in the SAP Best Practices content, and which will require some additional localization effort because they will need to be customer-specific. This is valuable information for the implementation team who later works on this project.

Another important tab is Effort Estimation, where the future implementation team can get a general idea of how many days it will take to configure business processes in each line of business area. This is valuable for the project manager staffing the project, as they can staff more implementation experts for the areas with higher effort estimations.

For new implementations with SAP S/4HANA Cloud Private Edition, the Detailed Discovery gathers information about integrations with other SAP cloud solutions the customer may already have or be planning to purchase, localizations, business capability requirements, and details about individual business capabilities.

To make it easier for customers to select the right business processes across the different line of business areas, there are pre-selection packages for the following scenarios:

• Enterprise Management Layer, which provides a global template for customers operating in multiple countries. It includes a large set of business capabilities based on the SAP Best Practices content documented in Signavio Process Navigator.
• Swift Implementation - Finance Only Package, which provides a template for any size company that would like to start their implementation with finance or has a smaller spinoff that is a seller of services who wants to start off with a finance-first approach. This company would probably have external sales representatives working on a commission basis and would be looking to have any logistics activities in a future phase of implementation. The goal of this template is to get SAP S/4HANA Cloud Private Edition live as quickly and inexpensively as possible and grow from that success.
• Swift Implementation - Extra Small Package, which provides a template for a typical small company that is a distributor or seller of services with a small product line working out of a small number of locations in a single country, with that country being the United States, Canada, or Mexico. They might have internal sales representatives or external sales representatives, but would have a very simple compensation plan that is commission based. They have a small purchasing team responsible for all procurement activities, and warehousing functionality is basic.
• Swift Implementation - Small Package, which provides a template for a typical small company that might be a manufacturer, distributor, or seller of services with a small product line working out of a small number of locations in one country. This company would probably have external sales representatives working primarily on a commission basis and would have a small purchasing team responsible for most of the procurement activities. Any warehousing or quality management function the company has would be basic.
• Swift Implementation - Medium Package, which provides a template for a manufacturer, distributor, or seller of services of somewhere between 500-900 million USD working out of up to ten plants in one country, but having a small number of legal entities (1-3). This company might sell their own products designed and developed in house, might sell software bundled with hardware and services, and may provide service for a product they sell. This company would likely have a mix of internal and external sales representatives.
• Swift Implementation - Large Package, which provides a template for a manufacturer, distributor, or seller of services of somewhere between 900 million and 1.5 billion USD working out of multiple plants in one country but having a small number of legal entities (1-10). This company might sell their own products designed and developed in house (full lifecycle) which might have a simple configurable component. The company's product line could be extensive. There may be a centralized procurement function responsible for procurement for all plants and corporate.

The partner or SAP internal sales person works through each line of business area with the customer decision makers. For each individual business capability, the priority and rollout phase can be selected, and questions or notes can be added to provide follow-up information.

If available, SAP Best Practices are linked to each business capability to show the actual business process that would be implemented.

Each three-digit link (1GA, 1K2, etc.) points to the source documentation of the process in Signavio Process Navigator.

After all business processes have been reviewed, additional requirements related to the processes can be entered, and detailed project and scope-related questions are completed, such as the target customer go-live date.

The completed Detailed Discovery is submitted to the Brand Guardian team who reviews the final solution recommended by the Digital Discovery Assessment and either confirms or changes the recommendation based on their deep knowledge and experience. An email notification is sent with the final solution recommendation for the customer.

When you navigate back to the Supply Chain of Selling app after completing the Detailed Discovery, additional information will become available.

For example, the Public vs. Private tab displays a graphic that shows the percentage of capabilities available in SAP S/4HANA Cloud Public Edition versus those only available in SAP S/4HANA Cloud Private Edition. If only a small percentage of business capabilities are Private Edition-only, we could potentially find an SAP cloud line of business solution that addresses those capabilities and instead recommend the customer implement SAP S/4HANA Cloud Public Edition as their cloud ERP.

For example, if additional sales capabilities are what's holding the customer back from Public Edition, look into the CRM and Customer Experience solutions. Instead of SAP S/4HANA Cloud Private Edition, consider selling the customer SAP S/4HANA Cloud Public Edition and SAP Sales Cloud. With two public cloud solutions, the customer will have a lower total cost of ownership, and systems that are always on the latest release.

For system conversions, the focus is on gathering information related to the customer's current solution scope and ensuring all required functionality is addressed with SAP S/4HANA Cloud Private Edition.

Instead of completing a Detailed Discovery, information about the customer's current system release, partner add-on requirements, preferred hyperscaler, and data sovereignty requirements are gathered.