Wednesday, May 31, 2017

Creating tables with the AET in SAP CRM

Most of us are aware of the AET, the Application Enhancement Tool. It can be used to add fields to standard SAP objects in a safe and flexible way. It is also possible to create new relations with 1-to-many relationships to standard SAP Objects with the AET.

It has been possible for a long time to enhance the Genil model of standard SAP objects with new 1-to-many relations. The process however can be a bit cumbersome. One good overview can be found here. We need to write quite a bit of code and customizing, which can be error prone to get just right.

When you use the AET to create a new table, most of this work will be done automatically. We will walk through the process and discuss alternatives.

Wednesday, May 24, 2017

Attaching a Barcode to a Sales Order Form in Cloud for Customer

In this scenario, the requirement is to have a barcode on a Sales Order Pdf Form for each product. This barcode is based on an own specific customer product ID number. In this case, the customer can scan the delivered products into their own system via hand scanner.

Wednesday, May 17, 2017

How to switch off standard SAP C4C email notifications

For many customers there is a need to send notifications by email to the respective users. For example when a transaction has been created or when it has reached a certain status.

As many of you probably already know, this is very easily configurable by using workflow rules. These workflow rules can be set up in such a way that it meets your business needs perfectly. You can define the email subject and content text as you wish and it is possible to add different attributes like object ID, business partner name etc.

So far, so good; however in most SAP Hybris C4C projects there are certain settings that are 'switched on' – when you are defining your project scope – which is usually executed long before the actual go-live. One of those switches contains the setting that the system automatically sends out an email notification as soon as a transaction has been created.

By the time you have created all the new workflow email notifications and the system is completely set up, you realize that there is already an email notification that is sent to the users à result: double the amount of email notifications in the recipient inbox à result: unhappy users.

The content of this automatic email notification is very basic:

It is also not possible to influence the content of that email. Therefore it would be best to make sure the users do not receive this email anymore.

There are two ways to do this:
1. Users 'unsubscribe' themselves from email notifications
2. Switch off the standard email notification completely

I will describe both ways, by using the example of a newly created service ticket.

Wednesday, May 10, 2017

BOL programming tips

When you program in the Business Object Layer you often use class CL_CRM_BOL_CORE e.g. for starting up the BOL or retrieve a Root Object. The latter is done using method GET_ROOT_ENTITY and requires the internal GUID of the object. Method GET_ACCESS_ENTITIES however retrieves objects using business keys like shown in the BOL Model Browser. This method can handle Access Objects, like the name suggests, but also Root Objects.

Wednesday, May 3, 2017

CRM add-on for S/4HANA: The end of SAP CRM. And now what?

Yes, the end of SAP CRM is near! With the latest announcement of SAP about the CRM add-on on S/4HANA we can conclude that the end of SAP CRM as an independent CRM system is coming. This process was already started with products (e.g. SAP Hybris C4C (yC4C) and yMarketing) from the SAP Hybris suite and with the introduction of YAAS and its related products; Service Engagement Center and Next Generation Order Management. But do I have to fear as an existing SAP CRM user? Absolutely not! This blog will explain the 4 options you have; continue, replace, transform or consolidate.