{"id":62303,"date":"2019-10-14T08:00:25","date_gmt":"2019-10-14T06:00:25","guid":{"rendered":"http:\/\/e3mag.com\/?p=62303"},"modified":"2022-02-06T01:05:46","modified_gmt":"2022-02-06T00:05:46","slug":"many-ways-lead-to-sap-c-4hana","status":"publish","type":"post","link":"https:\/\/e3mag.com\/en\/viele-wege-fuehren-zu-sap-c-4hana\/","title":{"rendered":"Many roads lead to SAP C\/4HANA"},"content":{"rendered":"

Just over a year ago, SAP announced the C\/4HANA CRM solution package. It is intended to provide companies in the context of commerce, marketing, sales, and service with a uniform view of their customers and end-to-end processes. Not least because of the many different SAP solutions, which often originate from company takeovers, there is a lack of transparency and decision-making ability as to what is the right way to go - especially from the point of view of not only transferring existing processes to the C\/4HANA world. But also to improve them and to use the potential for continuous and integrated solutions (CX). Finding the right approach for your own company is the challenge when introducing C\/4HANA. The Sybit C\/4 Mapping Concept helps to find one's way through the thicket of numerous variants and starts at a decisive point: after the decision to use C\/4HANA and the start of the project. There are three steps in the process.<\/p>\n

First, the old is not the same as the new process<\/h3>\n

In the beginning there was strategic alignment - but where does this lead in concrete terms? And what does it mean for the individual departments? These are questions that IT decision-makers in particular are asking themselves. One thing must be clear: By transferring existing processes 1:1 to the new, digital world, companies create a fancy framework - which only costs a lot of money, but is not goal-oriented. Instead, companies should first scrutinize their existing processes. There are various integration scenarios, depending on the existing and planned IT landscape. These scenarios differ not only in terms of the systems and interfaces, but also in terms of the time frame, (operating) costs, or licensing models.<\/p>

\"\"<\/a><\/div>\n

A simple example can be used to illustrate this. In every company, the lead-to-order process looks a little different, especially in the context of quote creation. Quotes from the opportunity, then directly in the ERP or still in the Sales Cloud? Integration via the SCP via SCI or PI? Is a mobile application or even a configuration engine (e.g. SAP CPQ) used via mash-up or web service connection? Should offers also be visible or merged in the commerce solution or portal? Which replication logic is there (bidirectional, unidirectional, pull, API etc.) - and above all which objects are exchanged? Is the order creation done from the quote? The entire process may also differ for individual companies, entities, roles, and partners. Such a generic process already shows the multitude of possible options.<\/p>\n

But which variant fits your requirements, framework conditions? These options differ significantly and require preparation and evaluation in order to make the right decision. The procedure can be aggregated to a larger level (introduction of the C\/4 Suite) or broken down further to specific (sub-)processes or C\/4-relevant topics.<\/p>\n

The strength of Sybit C\/4 Mapping: It creates an overview and structure, draws an individual map for the company on the way to C\/4HANA.<\/p>\n

Second: From different variants to concrete utility analysis<\/h3>\n

The implementation options are now clearly described and the cost of the necessary IT infrastructure quantified. Which variant is now the best depends on criteria that are relevant for the respective company:<\/p>\n