SAP C/4 HANA – inside view
In this blog, I would like to highlight the features of C/4 HANA from a Solution and technical perspective.
The solutions that are offered by SAP C/4HANA portfolio:
•SAP Marketing Cloud
•SAP Commerce Cloud
•SAP Sales Cloud
•SAP Service Cloud
•SAP Customer Data Cloud
C/4HANA solution landscape; source: SAP
C/4 HANA system is based on consumer, while existing legacy offering is based on Sales.
There are five clouds that make up SAP C/4HANA. However what makes it a suite is
– one data model
– extension framework with a micro services through SAP Cloud Platform
the micro services architecture, minimizes innovation cycles and allows for simpler adoption of best-of-breed functionality, with ROI and adaptability of suite.
With an in-memory platform that takes advantage of the SAP Cloud Platform, the C/4HANA customer experience software offers abundant microservices for extension and integration
Customer data, machine learning technology, and microservices are present side by side to propel real-time customer engagements across sales, service, marketing, commerce and more.
Fiori as a user interface enables a consistent user experience. A chat bot infrastructure and the ability to run on all relevant screen sizes with one UI architecture pave the way towards keeping the user experience consistent.
The SAP Cloud Platform also provides services like IoT and Blockchain
To truly deliver a complete view of the customer, you need to bring the back-office to the forefront.
Customer engagement and business operations are the two parts that must work together to deliver a great customer experience. SAP has tried to invest in services layer between customer engagement and the back office.
SAP’s Front-office YaaS (Hybris-as-a-Service) was focusing on delivering a business platform to commercialize packages of microservices & UIs. SAP Cloud Platform is a Platform As a Service portion which offered Cloudfoundry capabilities to customers. SAP ended up with sunset of Yaas platform.
The successor to YaaS is aligned with SAP Cloud Platform and is powered by Kyma, a microservices based extension platform that takes the concepts from YaaS to the enterprise space. It is an open source project that allows customers to easily mix and match their services, offering speed, agility, openness and seamless integration across applications. Kyma is the latest microservices architecture that lets businesses be far more granular and powerful in their application pairings and provides continuous delivery, rapid time to value and scalability. Kyma’s mission is to equip enterprise software users with agile, open-source tools to connect, customize and extend any API-enabled application and tailor it to their specific business needs.
Kyma eases the development and operation of microservices-based solutions by providing a consistent service consumption layer, which blurs the boundaries between legacy enterprise software and the large variety of cloud services that originate from different providers. To achieve this, Kyma leverages the standard Kubernetes Service Catalog and expands it further by using the Open Service Broker (OSB) standard. Kubernetes is a framework that allows seamless management through modularity, as well as lays the foundation for cloud-native applications. The other major advancement by Kyma is the implementation of end-to-end flows, triggered by business events in existing enterprise solutions, resulting in extension modules being executed in Kyma.
Points to ponder on –
How will the integration between the CallidusCloud solutions especially with the Sales Cloud, the Service Cloud and the Commerce Cloud work. The statement is that CPQ and CLM of CallidusCloud will become modules within the SalesCloud. Since last year there is a first version of an integration, which however does not show up as integration content in the SCP.
CLM does not yet have an own integration into the SalesCloud
SAP had a CPQ solution before acquiring CallidusCloud. The challenge is that the existing (old) SAP CPQ is compatible with the SAP Variant Configurator as well as ERP- and S/4HANA pricing. And the Variant Configurator has around 1,500 customers; it is an important asset in SAP’s kit.
The most possible way forward, is the (old) SAP Product Configurator will be made available as a Micro Service via the SAP API Hub. It essentially becomes an add-on to the CallidusCloud-based. This way, the CallidusCloud-based CPQ can be used including variant configuration in front-end scenarios.
On the Marketing Cloud frontier we do see the steadily maturing Marketing Cloud itself and LeadRocket from CallidusCloud. SAP might merge the LeadRocket’s functionality that is not in the Marketing Cloud yet into it, and fast. There should be a special focus on web site tracking and the conversion of anonymous profiles to known individuals.
The addition of the SAP Customer Data Cloud hints into the direction of providing a customer data hub as a single version of the truth of things customer.