S/4HANA for Customer Management 1.

0
introduction from technical point of view
 How to get it?
 Some FAQ
o 1. Which technique is used to develop S/4HANA for Customer Management UI?
o 2. Any difference between Sales & Service scenario in S/4HANA for Customer and
SAP CRM?
o 3. Continue with question 2: for a given scenario, any technical implementation
difference in S/4HANA for Customer Management and SAP CRM？
o 4. Any changes on One Order Model in S/4HANA for Customer Management
compared with SAP CRM?
o 5. I am an SAP CRM consultant. Will I lose job in the future?
 Further Reading and update
 Technical comparison between S4CRM and C4C
John Burton has mentioned in his blog Explaining SAP’s portfolio of “CRM” and “Customer
Engagement & Commerce” products that S/4HANA for Customer Management will be released on
February 28, 2018.

Now it is time for celebration! With the hard work of my colleagues in SAP Global(including
development team in SAP Labs Chengdu), this miracle offering is finally delivered in time. A part of
Sales & Service functionalities available in SAP CRM On-Premises(called as SAP CRM for short in
this blog) are now integrated into S/4HANA. Being a member of this great development team, I am

also proud of such amazing achievement

In traditional SAP system integration deployment architecture, SAP ERP is connected with SAP
CRM by CRM Middleware. There might be some trouble during the data exchange between these
two systems in case of incorrect or incomplete customizing.

Fortunately CRM Middleware is widely used by SAP customers all over the world and there are lots
of documentation available which can help partners when they encounter all kinds of Middleware
error messages.
I have also contributed 31 blogs in SAP community regarding CRM Middleware knowledge share.
For your reference I have assembled them together into this link.

Nevertheless some partners still have headaches in Middleware trouble shooting process. Now good
news for them: such troubles in data exchange between SAP ERP and SAP CRM could be
eliminated in S/4HANA for Customer Management from design perspective, simply because Sales &
Service scenario now is directly running on S/4HANA itself, no need of data exchange at all.

How to get it?

It is available in SAP Download Center via this url.
More detail about supported Sales & Service scenario in S/4HANA for Customer Management 1.0,
please refer to SAP help documentation.
Let’s have a glance at its UI first. Click the corresponding tile in Fiori Launchpad to start the explore:
If the parameter CRM_UI_PROFILE is maintained with value “*” in user profile, a list of all available
business roles will be displayed as below once tile is pressed:
Now I will play with the interaction center scenario by logging on with role S4C_SRV_ICAG.

Suppose a customer named Jerry called interaction center and would like to raise a service request
based on a product he has bought with ID 11.

The agent picked up the call and had to identify Jerry as a valid customer first. The identity could be
confirmed via various approach like the Account ID in the system, or contact information such as
email address or mobile phone number etc( all supported account identify method are listed as fields
in “Identify Account” region in below picture).

In this example the agent identified Jerry by Account ID provided by Jerry.

Search by Account ID and click Confirm button:
And then searched the Product by ID 11, and created a new service order based on this product:
Here below is the created service order:
I received lots of questions from local partners in China asking about details of S/4HANA for
Customer Management. Here I try to answer some of them:
1. Which technique is used to develop S/4HANA for Customer
Management UI?
Jerry: SAP CRM WebClient UI, not SAP UI5.

This is good news for partners who have already gained enough expertise on WebClient UI: this
expertise will not turn obsolete but instead continue to bring them success in their future work in
S/4HANA.

On the other hand, for those who would like to try something new in UI development, the
combination of CDS View plus Smart Template can satisfy them.

I have also tried to build UI in S/4HANA by leveraging this new technology introduced in S/4 HANA
and documented what I have learned in 13 blogs in SAP Community.

I have assembled them into one link for your convenience:

2. Any difference between Sales & Service scenario in S/4HANA

for Customer and SAP CRM?
Jerry: Scenarios in S/4HANA for Customer Management are a subset of the ones in SAP CRM.
More features will be supported in subsequent versions.

3. Continue with question 2: for a given scenario, any technical

implementation difference in S/4HANA for Customer
Management and SAP CRM？
Jerry: Although a given scenario, take product search for example, looks nothing different but just a
click of search button in UI from end user perspective, there are indeed difference in regard to the
technical implementation under the hood.

The discrepancy mainly lies in the green area below: Genil Interaction Layer, the persistence models
and the API operating on those models.
It is easiest to understand the necessary change of underlying database table in S/4HANA for
Customer Management: in CRM there is some concept which has its counterpart in S/4HANA, for
example “Product” in CRM and “Material” in ERP.

In CRM a product could be created in tcode COMMPR01 and stored in tables with naming
convention COMM_, while in S/4HANA, we create a material in tcode MM01 instead and store the
data in corresponding table like MARA.

In this situation, during the integration of SAP CRM Sales & Service scenario into S/4HANA, we
have to make a decision which data model should be used. The adopted guideline here is: stick to
the model in S/4HANA.

This principle leads to the necessary change to be applied in the API used originally in SAP CRM,
where the manipulation on CRM model should be adapted to use S/4HANA model instead.

Take an example to illustrate the API change. Previously it is mentioned that in CRM a product is
stored in table COMM_PRODUCT. In S/4HANA for Customer Management now the product is
stored in MARA instead.

The product search in S/4HANA for Customer Management is developed by SAP Chengdu
development team. We don’t simply figure out all occurrence of “COMM_PRODUCT” in API source
code and replace them with “MARA”.

Instead we utilize the recommended modelling approach in S/4HANA: a new CDS view
CRMS4V_PRODUCT is introduced to serve the product search which is ultimately built on top of
MARA.
In this way, we managed to adhere to the “Code Push Down” best practice, ensuring to put logic
execution into database layer as much as possible.
If you have more interest in CDS view, you might have a look at my CDS view self study tutorial.

4. Any changes on One Order Model in S/4HANA for Customer

Management compared with SAP CRM?
Jerry: In CRM a order’s data is spread among a series of database tables. The most well-known one
should be CRMD_ORDERADM_H for header data and CRMD_ORDERADM_I for item data. The
“ADM”(Administration) in the table name acts as a hint: most of business data are NOT stored in
either of them, but persisted in other dedicated tables.

The rectangles below with different colors represents different nodes in One Order model in SAP
CRM. Each node has a dedicated persistence table. There exists relationship among those nodes,
for example, one ORDERADM_I can have multiple PARTNER nodes with different role(ship-to party,
sold-to party etc). Such relationship is maintained by CRMD_LINK.
Such kinds of One Order Model in CRM consists of more than 200 database tables for persistence
and is proven to be very successful: it works as the foundation of SAP CRM and perfectly serves
SAP CRM Customers all over the world.

In Analytics scenario, it should collaborate with another index table CRMD_ORDER_INDEX. As the
name indicates, the employ of CRMD_ORDER_INDEX actually reflect a design strategy about trace-
off between storage and execution time — Some data from dedicated tables are replicated to this
index table in order to accelerate the analytics application at the cost of additional storage wasted.
And in S/4HANA for Customer Management the One Order model is dramatically simplified. All
aspect of a order’s header level data(such as ID, description, order type, creator, creation
timestamp, involved parties, organization, pricing etc) are stored in a new table CRMS4D_SERV_H.
And for item level data, a sole table CRMS4D_SERV_I accordingly.

A CDS view constructed on top of such flattened table can reduce joins among database tables to
the maximum degree so that it can serve analytics scenario by fully utilizing the powerful data
processing capability of SAP HANA. Time to say farewell to CRMD_ORDER_INDEX now.

This simplified model enables us to realize the miracle that to have the same data model serve both
transactional and analytics application. The CDS view built on top of simplified model can ensure
S/4HANA for Customer Management to benefit from the continuous innovation done in S/4HANA.

Thanks to the elegant layering design done in SAP CRM One Order API, its signature can remain
unchanged regardless of the fundamental model change in persistence layer. It means suppose you
have already been familiar with using One Order API in SAP CRM, you don’t have to learn anything
new —— the One Order API usage in S4HANA for Customer Management 1.0 is EXACTLY the
same as in SAP CRM.
5. I am an SAP CRM consultant. Will I lose job in the future?
Jerry: if you are patient enough to read here, I guess you might already have answer in heart.

On the one hand, the custom development in S/4HANA for Customer Management still consists of
WebClient UI as UI technology and One Order API in the backend. You are already an expert on
both and you can CONTINUE with them in your future work.

My personal experience regarding learning a new technique or product is: we either learn new stuff
in our daily work( so called on-job study ) or self study in our spare time. In on-job study there is
enough chance to practice what we have learned, so it’s far more efficient compared with simply
going through learning materials without practice and forget them completely after periods of time
later.

In my opinion it is a great opportunity for SAP CRM consultants in S/4HANA for Customer
Management since they can not only enlarge their technical / business knowledge on Sales &
Service scenario but also can embrace and learn S/4HANA in their daily work, which can bring
fantastic value to their career.

Further Reading and update

 CRM One Order Model Redesign in S/4HANA for Customer Management 1.0 – Part 1 – this
blog give you more detail about One Order Model Redesign and how One order read works
under this new adapted model in S/4HANA.
 Part 2 – continue with Part 1, focus on write scenario.
 Create Mass Products by code in S4HANA for Customer Management – this blog briefly
introduces how CRM Product works in S/4HANA for Customer Management and provides
the example how to create product using ABAP code.
 Create Mass Service document in S4HANA for Customer Management – How to create a
huge volume of Service Order, Service Confirmation and Service Request by One Order
function module
 One order extensibility in S4HANA for Customer Management – explain how to create
extension field in S/4HANA for Customer Management using S/4 extension tool instead of
Application Enhancement Tool(AET) originally used in SAP CRM
 One Order Partner Component model in S/4HANA for Customer Management – it is well
known that in service document header and each item, it is possible to maintain multiple
partners with different party roles. How is it handled in the new world?
 Step by step to create custom partner function in S4HANA for Customer Management
 One Order Status Component in S4HANA for Customer Management
 Best Practices for SAP S/4HANA for customer managementTwo processes are supported:
(1) Service Order Management
(2) IC Service Request ManagementThe package provides all accelerators needed to set up
and test a system with these processes configured and ready to use.
It provides customers, partners and SAP the possibility to explore the solution quickly.
The package is also the basis for a engineered implementation service.
 How to create employee in S/4HANA for Customer Management
 Paging Implementation in S/4HANA for Customer Management

Technical comparison between S4CRM

and C4C
Detail comparison could be found from my blog.
 I hope the series of these blogs can give you a very rough understanding on S/4HANA for Customer
Management 1.0. As I still work on it, I will continue to share my knowledge on it in the future.

Thank you very much for reading. Any comments or questions are highly appreciated!





 Alert Moderator

Assigned tags
 SAP Customer Relationship Management
 CRM Middleware
 CRM Sales
 CRM Service
 SAP Commerce integration with SAP CRM
View more...

Related Blog Posts

 Create Mass Service document in S/4HANA for Customer Management
By Jerry Wang, Mar 05, 2018

 CRM One Order Model Redesign in S4HANA for Customer Management 1.0 – Part 2
By Jerry Wang, Mar 05, 2018

 Step by step to create custom partner function in S4HANA for Customer Management
By Jerry Wang, Mar 07, 2018

Related Questions
 Availability Checks in CRM 7.0 using S/4 HANA
By Alaa Hassan, Feb 10, 2019

 S/4 Customer Management service contract item with billing plan

By Florian Preuss, Jun 18, 2019

 Slow query performance with SAP Hana Studio

By Former Member, Aug 07, 2017

72 Comments

You must be Logged on to comment or reply to a post.

Aseem Baruaole

February 28, 2018 at 4:25 pm

Is this ad on available now for existing S/4HANA EM on premise user and partner? If yes, how.

o Like(0)

Jerry Wang Post author

March 1, 2018 at 2:46 am

Hi Aseem,

Thanks a lot for reading. Yes it is officially released. You can download it via the url:

https://launchpad.support.sap.com/#/softwarecenter/template/products/_APP=00200682500
000001943&_EVENT=NEXT&HEADER=Y&FUNCTIONBAR=Y&EVENT=TREE&NE=NAVIG
ATE&ENR=73554900100800001009&V=INST&TA=ACTUAL/SAP%20S4HANA%20FOR%2
0CUST%20MGMT
Best regards,

Jerry

 Like(0)

Klaus Löhnert

March 1, 2018 at 4:23 pm

Hi Jerry,

when I try to download S/4HANA for Customer Management 1.0, Iget the error message “No Data
Available”

Best regards

Klaus

 Like(0)

Jerry Wang Post author

March 2, 2018 at 2:32 am

Hi Klaus,

It works from my side. Can you please kindly retry or raise an incident to SAP?

Best regards,

Jerry
  Like(0)

Carsten Kasper

March 2, 2018 at 8:15 am

Hi Klaus!

I tested with different S-User. It depends on the access rights your user has.
In case you are not allowed to download this page appears. Otherwise you
get a 4 GB file to download.

More interesting in my opinion is the information on the INFO tab.This

information is (hopefully) available here as well given some
time: https://help.sap.com/viewer/p/SAP_S4HANA_FOR_CUSTOMER_MAN
AGEMENT

SAP TPM with S4 HANA

FollowRSS feedLike
1 Li ke 3,461 Vi ews 2 C omments

I am all geared up to write my first SAP Blog after SAP SDN community has taken its transformation.
Although, I thought my first post would be on SAP BCM a.k.a Contact Center but I’d rather decided
to write a blog on SAP TPM (Trade Promotion Management) to help one of my LinkedIn friend.
Since, this being my first post I wouldn’t be perfect but please leave your feedback/suggestions/tips
so I can improvise.

Tip: If you are interested in writing a new blog you need to aware of the new rules of SDN to write a
blog which I will cover in a separate topic later or you have check this below link and also follow my

blog https://blogs.sap.com/2016/12/06/navigating-blogger-levels-new-sap-community/

This blog will cover only what’s new with SAP S4 HANA in accordance with SAP CRM-TPM. Before
you start reading ,You need to understand that SAP HANA has impact only on classic ECC and BW
system but there is no HANA in CRM technically.

For the easy read of this blog. Henceforth, when I mention S4 HANA, it means SAP ERP system
with HANA.

1.In S4 HANA system, you don’t have the Tcode – VBo1 meaning, you cannot create your Rebate
agreement in S4 system (Cool tip: To identify whether the T-code is supported in S4 or not, you
enter the T-code and press enter key it gives a dump error which means it’s not support in S4
system) Having said, that you can still you use the T-code VBo2 & VBo3, what is that means ? It
means, you can create Rebate Agreement in SAP CRM-TPM and transfer to S4 HANA system
where the rebate agreement can be viewed in S4 HANA. If that is possible, then your rebate is
applied to your sales transaction documents as well.
2. Conditional Contract Settlement – If you interest knowing this in detail , I would request you read
this below blog from the SAP Experts for all the technicality on 1511 and 1610

https://blogs.sap.com/2016/08/26/simplification-item-rebate-management-replaced-by- condition-
contract-settlement/

https://blogs.sap.com/2017/02/17/settlements-management-in-s4-hana/

3. This might be not have direct impact with TPM/SD integration but you need to know because you
need to fulfill your delivery to complete the integration testing till invoice.In S4 HANA there
is no MB1C, meaning you cannot add stock using this T-code instead you use MIGO for adding
stock.

Apart from this, you need to know to how select which planning tool you need to choose, whether
you need to go with BPS, BPC or BW-IP. It to say to go with BPC or BWIP with HANA but you need
be very careful in your selection to make sure which you need to choose to meet your business
/client needs.

Each one has it’s own plus and minus, it really depends on your business needs and which one suits
to satisfy your customer needs. Before we jump in, let see of difference between BPS Vs BWIP.

The simple difference between the BPS and BW-IP. In BPS use key figure planning, where we use
Planning profile group and which will have planning profile (and many would have mastered it so, I
don’t have literate it), coming to BW-IP which uses Key figure planning with PAK (Planning
application kit) which can work with ATPM(2.0) IMP (In-memory planning). In BW-IP , instead of
using the Keyfigure planning node in SPRO you will be using Key-figure planning with PAK and
everything is query based meaning you will need to select the right queries to fetch your planning
data. Nothing fancy, you need to know which query will satisfy your needs and you use them
accordingly. For example if you want day, week or month level planning then you need to choose the
respective query accordingly.

Examples of few queries as follows:

Master: BP with Product Group and Product (Day Level) (0TPM_AC03_IRQ0081)

Planning by BP w/ Product Category and Product (Day Level) (0TPM_AC03_IRQ0052)
TPM Read Query (Day Level) (0TPM_DS01_Q0003)

Similarly, the key-figures may be different from BPS so you need to know what Key-figures you need
to maintain.

Examples of few key figures as follows:

 Discount (%) per Sales Unit (0BON_OIPSU)

 Bill Back (%) per Sales Unit (0BON_BBP)
 Variable Promotion Discount (Invoice Markdown) per SU (0OFFR_DCSU)
 Every Day Low Price (Off-Invoice) per Sales Unit (0EDLP_OINV)
 Rebate (Amount) per Sales Unit of Measure (0BON_SHSU)

Comparison with BPS, BPC and BWIP:

BPS:
SAP has already communicated it would stop supporting BPS but when? It all depends on what
version of SAP Netweaver you have, let say if you are using SAP Netweaver 7.50 then the
Mainstream maintenance will offered through December 2025.

Keep in mind, BPS can offer Free Goods and TGR off-invoice.

BPC: When it comes with BPC, you need to make sure which version of BPC you are using. BPC
has two version.

1. Standard version
2. Embedded version. In order to use TPM you would need Embedded version and these
would lead to licensing issues so make sure what version of BPC you are using. Because
standard and Embedded has different licensing. If you are interested to understand in depth
of the difference you can check out the below
link https://blogs.sap.com/2014/10/21/concepts-compared-bpc-standard-and-bpc-embedded/

BW-IP(In memory Planning):

1. Resource challenges. You will have issues finding a right candidate for this role, who is an
expert in BWIP, not many have master this module.
2. It uses FOX programming and not ABAP programming, so again you need to know someone
who can handle FOX programming and not many would be able to support this.
3. Even though, the products has been released since 2012, according to me it needs
improvements. It has many limitations which may or may not satisfy all your customer
business needs.

To list a few as follows:

1. If you decide to use rates origin as ‘CRM’ then Tiered Growth Rebates(TGR) will not
support.Technically, TPM -TGR will act as a Standard Rebates offering the total Rebate
discount amount so it is not very useful even if you are using BPS as well. However, to
overcome you can use TGR Off-invoice(in BPS) if you need or SD themselves can gave
scale based discount on the sale volume either would satisfy your customer needs.
2. Free Goods will not be supported. If your client wishes to give Free Goods based on Trade
promotion well then it would not be supported with BWIP.