CRM and CX Blogs by Members
Find insights on SAP customer relationship management and customer experience products in blog posts from community members. Post your own perspective today!
cancel
Showing results for 
Search instead for 
Did you mean: 
KAnandh
Participant
0 Kudos

Would sCRM (the name To-Be Decided) co deployed with S/4
HANA make paradigm shift in Enterprise software deployment and running it?

Simple answer would be yes. But that needs to become
reality, there are lot of aspects on the product to be made clear. The Roadmap
for sCRM is listed out below.  
 
 
Source: SAP Roadmap for S/4 HANA

Traditionally SAP CRM deployed as an independent unit having
separate schema ID. This gives a flexibility of deploying it standalone or
integrated with SAP ECC.This flexibility comes at cost of maintaining duplicate
maintenance of some master data ( Customer, Products etc.,) and interface
structure ( SAP CRM Middleware ) for data transfer among SAP CRM, SAP ECC and
SAP BW.

This duplicate master data maintenance brings in additional
confusion for deciding on leading system to create data (Customer Master).

Will the upcoming sCRM co deployment do away with this
bottleneck?

It is still not clear on the roadmap of sCRM. However the
hope is very high on Simple, Lean and Agile application which would excite both
customers as well as SI vendors. On that premise, Will the co deployment fuses
the common database tables mainly between CRM and ECC i.e., Customer Data
Model, Product (Material), Sales order Data model etc.? If the co deployment of
CRM and ECC achieves this and brings seamless interconnection between CRM
processes (Customer facing processes) and ECC Processes (Fulfilment processes),
this would greatly reduce the pain of CRM middleware monitoring and periodic
interventions.

SAP CRM depends on lot of other SAP Products to carry out
business transactions. i.e., Campaign Management or TPM needs Planning
application to maintain planning values. This Planning application reside in BW
and this has multitude of versions (BW-BPS, BI-IP, BPC & IBP (on HANA)). Moreover
the options available for single planning can be done in either BW-BPS or
BI-IP. Hope, this will get realigned and would be single application for
planning purposes common to CRM, APO and ECC.

Nowadays trend is towards customer experience with the help
of Omni channel. SAP CRM web channel is in distributed format at present. SAP
CRM is interfaced with Hybris which has separate schema. This distributed
format would need data exchange between these two systems to achieve near
customer experience in the Omni channel world. When sCRM is the Product, would
we expect CRM and Hybris would merge into single system?

On the User Experience front, there were different UIs for
CRM and ECC. Will sCRM along with S/4 HANA have harmonized uniform User
Experience?

If this co deployment would do away with duplicate data
maintenance and middleware tweaking, how this would help deploying sCRM as
standalone (without S/4 HANA as backend). So sCRM should address the deployment
options with great agility.

1 Comment