All articles

When you're communicating with an external SAP system, you should use the released BAPIs if you can.

I don't use RFCs and BAPIs that often, so one thing that struck me today was that BAPIs don't refresh their buffer when you call them.

My expectation was: BAPIs are for external calls, so they should make sure you always get the most-up-to-date data and handle the buffer themselves.

I was wrong.

BAPIs will default to accessing the buffer, which makes sense performance-wise.

In case you were looking to include a new tab in a business object that displays related sales orders for a customer, you might have stumbled across the standard screen /BYD_COD/SalesOnDemand/SalesOrder/UI/COD_SALESORDER_EC.EC.uicomponent.

The problem with this screen was that the "RequestFireOnInitialization" flag was set to false - the standard would fire the inport from the customer screen, so didn't need this setting.

I've raised an incident regarding this and with the latest C4C hotfix (1911.03) SAP have set the above mentioned flag to true.

Most C4C users are certainly aware that SAP has switched off HTML5 with the 1911 release and that it is - according to SAP - "technically impossible" to re-enable HTML5 from 1911 onwards.

I did have some doubts if a) that is really true (it's "only" a frontend) or if that was just to encourage customers to switch to Fiori (which they should - takes some getting used to, but I've come to like it better) and b) if it is a good idea to make it technically impossible to switch back as they will have certainly forgotten some features.

When I read this article recently, I was instantly reminded of the problems my customers face when SAP makes yet another unannounced change. The facts in the article are:

TL;DR: If you are asking yourself whether you need two solutions, you don't. If you do need two solutions, you will not be asking yourself this question.

I read some articles yesterday that largely discussed the sense and non-sense of SAP providing ABAP as a programming language in SAP Cloud Platform.

SAP & Psychology?

When I studied economics, the discipline that most fascinated me was behavioral economics. Fascinating because it contradicts classical economic theory quite heavily by claiming that human beings are generally not able to behave rational (in the sense of being consistent in your choices) and do not always optimize their utility (in the sense that decisions you make are not always good for you).  And it explains why, using psychology.

So easy and yet so difficult: If you're using the Drupal default front-page it displays a list of all articles in a chronological order, the classic blog home page. However, the front-page does not have a page title, so that your tab title will read " | <your site name>".

In fact, this is quite easy to change:

While the official Drupal 8 setup guide is quite comprehensive, it is also a bit overwhelming. So here I'm sharing my steps:

Notes 

I'm on a Debian Linux Server with Apache2 and PHP 7.0 and assume that those are setup accordingly. 

I also assume that Composer and Drush are already set up in a globally accessible location, e.g. /usr/local/bin (I will write a later article that explains their setup.)

Little known to the larger audience, C4C does not behave the same to all customers.

When switching from on-premise to the cloud we all needed to learn that standard modifications and skipping upgrades are in the past. Every three months, SAP upgrades C4C to a new release, with hotfixes inbetween. And we all have to live with them. Or do we?