Wednesday, May 30, 2018

The future is now!

Ladies and gentlemen, the future is now!
The future of Customer Engagement is bright! SAP has a very sturdy portfolio with the Hybris products for different customer engagement goals.
On top of that, S/4HANA release 1709 release is now available with the S/4HANA Customer Management component. This is exciting news for those of you who work with an SAP CRM on premise system. It's time to start thinking about a transformation.
You should do so now because now you have the time to properly define a strategy and roadmap towards 2025.
As most of you probably know, general maintenance of SAP CRM 7 on premise will stop in 2025. This means that by then you should have transitioned your SAP landscape.

Wednesday, May 23, 2018

First Steps into Automated Testing

Automated testing is buzzing around everywhere, so I decided to join the party. Below are the results of my first test.

For this test I used Robot Framework with Selenium Library. This is one of the best options to test a web application.

All the downloads and installation instructions can be found here:

Wednesday, May 16, 2018

Address Validation in SAP Hybris Cloud for Customer

In the latest 1805 release of SAP Hybris Cloud for Customer a new feature is available to help sales users plan their visits. For planning their sales visit they now have access to their accounts on a map. Just by dragging an account to the calendar day view they can create a new activity such as a visit.
When you try this new function you would probably ask yourself why you don't see any or just some of the accounts on the map. The reason for this is that only accounts that have a Geo location maintained (Latitude and Longitude) can be used on this map.

When you create a new account you obviously do not enter the GPS coordinates, so how can C4C do this for you? For this you can make use of the Address Validation function. In this blog I will explain how to do this and how you can have a go at it in your own test tenant.

Wednesday, May 9, 2018

Cross deployment unit object creation (Businesspartner – Lead)

In SAP Hybris Cloud for Customer business objects are assigned to a particular Deployment Unit.

When developnig within a business object from the Foundation deployment unit, you will not be able to directly create an instance of a business object assigned to for instance the CRM deployment unit.

This issue has been addressed in the blog Understanding Deployment Units from Stefan Hagen. I encourage anyone who encounters Deployment Unit issues to go through that blog. It explains how to manage working with Custom Business Objects that reside in different Deployment Units.

In this blog I would like to discuss how to deal with situations where you would like to create objects, cross deployment units, from one standard business object to another. Let’s say we need to create a Lead (CRM Deployment Unit) from a Businesspartner (Foundation Deployment Unit). We can move a custom BO to the Leads’ Deployment Unit. This custom Business Object can now create Leads, but It cannot be changed by the Businesspartner to trigger the Lead creation. So what to do?

The Internal Communication object 

In the SDK the Internal Communication object is made available. This special object automatically copies changes done in one custom BO and does the same changes in another custom BO. The two custom BOs do not need to be in the same Deployment unit. So, back to our case. We would like to be able to create a new Lead (CRM Deployment Unit) from a businesspartner (Foundation Deployment Unit). The approach would be to create two custom Helper BOs, one in each deployment units.

The two Helper BOs are connected by the Internal Communication object:

Wednesday, May 2, 2018

Planogram Compliancy Check by SAP Hybris Cloud for Customer and RICOH

In the retail business, placement of your goods is very important to maximize sales and minimize wasted space. For this reason, many retail companies make use of planograms to agree on an optimum display of their goods in the stores.

The next step is then for the sales reps to go and check in the stores and see if the store manager has placed the merchandise as agreed upon in the planogram. In case derivations of the planogram are found, corrective actions in store need to be taken. For example, when a good is out of stock it needs to be placed back on the shelf. Or in case the number of facings (defined as the number of identical products displayed to the customer on a shelf) is not correct, it needs to be corrected, preferably during the store visit of the sales representative.

As you can imagine, checking the placement of your merchandise according to planograms is a very precise and time-consuming job. For this reason, SAP & RICOH have jointly developed a planogram compliance solution that enables a sales rep within a visit, created in SAP Hybris Cloud for Customer, to: capture photos of a retail shelf, analyze the images real-time, identify issues and take corrective actions accordingly.