After having talked with Volker Hildebrand about the future of SAP CRM and whether or not there will be a CRM component in S/4HANA at CRM evolution 2017 I now had the chance to follow up with some folks back at SAP in Walldorf.
Volker told me that, unsurprisingly, SAP is working actively on adding CRM functionality into S/4HANA. In fact, they are merging SAP CRM into it. This is in my eyes meanwhile also the preferred of the two possible options; the other one would be marrying SAP Hybris C4C into S/4HANA. This is the approach which I originally preferred as it would lead to a cleaner code base. I changed my mind, putting customer friendliness reasons over technological cleanliness. The main advantages of merging SAP CRM into S4/HANA over SAP Hybris C4C are that this approach
a) Opens a future roadmap for current SAP CRM customers that stretches beyond 2025. These customers else are at risk of defecting.
b) Provides the continued chance for customers to run their SAP instance on-premise. According to Volker there are still a good number of customers that do not want to run their instance in the cloud. The key word here is choice.
c) It simplifies the system landscape and its operation
And this approach works, in spite of SAP apparently having severa studies that lay out in detail that SAP CRM could in no way artwork as a part of an ERP.
As stated, SAP is merging SAP CRM into S/4HANA. This will no longer be a smooth merge however CRM turns into and Add On to S/HANA.
This in itself is an thrilling go with the flow, due to the truth this way it isn't always viable to maintain the usage of an current SAP CRM in a standalone style. And there are a few customers taking walks SAP CRM without an ERP integration. I am still curious approximately the licensing affects of this bypass. Some customers might not truely have an SAP ERP, others might be too conservative to move on from SAP ERP to S/4HANA.
The roadmap suggests that SAP will begin with turning in carrier capability as a part of this CRM add on, which makes sense as S/4HANA is sorely lacking customer support as of now. This functionality shall have an RTC early 2018 primarily based absolutely upon the S/4HANA 1709 release. While particularly relying on S/4HANA grasp data items, as a part of this S/4HANA may even revel in the a lot stronger industrial enterprise companion that SAP CRM has, in comparison to ERP and the present day S/4HANA.
There is a few reluctance to decide to a specific scope currently, just that it's miles going to be center provider capability specifically focused on shared offerings and utilities industries. As it seems there'll no longer be important migration system with this primary launch.
2018 then is dedicated to handing over center sales functionality. Here we can once more see a sturdy use of S/4HANA devices, apart from the bendy organizational version that CRM brings with it and an brilliant wide sort of CRM associated devices that S/4HANA simply doesn?T have, like leads, opportunities, territory, loyalty, to call however some.
Order, configuration, pricing, and billing may be brought via the S/4HANA center in a flow that, on the outset, makes experience.
This one year can even see the development of migration gear.
In short: No. After the discharge of the profits middle 2019 will see a focus on rounding off the income and carrier functionality and the addition of loyalty management.
And with SAP Hybris Marketing SAP already has a advertising solution that may be used on premise and on call for.
SAP is calling at the person corporation items and identifying for my part which object to apply, and how. Objects gets harmonized with a view to avoid high-priced redundancies and to keep away from CRM Middleware ? With a motive to remain, by way of way of the way.
Especially the in particular normalized one-order version gets denormalized, using the prevailing index tables that were given delivered to get a few standard performance into the CRM Order model. This can even gain the HANA DB which strongly prefers extensive tables over joins. I am no longer completely clean about what because of this even as putting the S/4HANA order into the aggregate, despite the fact that.
S/4HANA makes use of a Fiori UI. SAP CRM doesn?T. However, it is viable to make the CRM Web UI appearance just like a Fiori UI. This can be augmented by way of using delivering Fiori apps for review pages and some selected local Fiori apps in conjunction with Fiori Launch Pad integration. I don't forget this being similar to the modern UI on SAP Hybris Marketing.
As said earlier than I suppose that it's miles a extraordinary skip to merge SAP CRM into S/4HANA. The collection of gadgets for this mere additionally makes exceptional sense even though a few clients could probable select a much broader footprint right from the start. On the other hand there can be no real pressure for them to migrate now. SAP maintains help thru 2025 and it is a superb concept to maintain benefitting from the stabilizing effect that the purchaser pushed innovation strategy has and to wait till migration tools are there and operating.
And agencies which can be contemplating to transport to S/4HANA need to finish this migration first, anyhow. Harmonizing the statistics fashions glaringly manner that a migration from SAP CRM to ?S/4CRM? Is a migration assignment, for which a stable S/4HANA is a precondition.
What remains a venture for me is the website of ?S/4CRM? Versus the SAP Hybris set of cloud solutions. There is a great overlap in capability. The messaging of when SAP recommends which solution in reality wishes to be labored upon for you to avoid confusion. Grey zones must emerge as minimal.
The solution appears to be there for Marketing, wherein there may be simplest one answer going in advance. But how about loyalty control (exists in CRM and as a cloud model), change selling manipulate (exists simplest in CRM), retail execution (is especially a cloud solution), or configuration and pricing? S/4HANA has the latter and with the SAP Hybris Revenue Cloud there can be every other get right of entry to (even though belated) into the CPQ (Configure, Price, Quote) market.
An technique for solving this lies in distinguishing amongst systems of report and structures of engagement wherein gradual-changing, mature capability is centered in the S/four international and faster shifting engagement functionality is encapsulated in engines that would get deployed on website online and on premise ? Or only be used on call for. Coupling structures of file and systems of engagement then can also want to manifest thru micro services, however need to show up on a platform- in area of utility degree to house for system mastering competencies.
Comments
Post a Comment