New Hana roadmap

Recently on a Deutsche Bahn train from Munich East to Salzburg Central Station:

"Our train is currently delayed by 25 minutes, due to a technical defect the train left Munich Central Station ten minutes late; road works on the line are causing further delays."

Short pause in the announcement, then we continued:

"Due to the construction sites, there will be a changed schedule - according to the new schedule, we will only have a five-minute delay."

Needless to say, the timetable to Salzburg was adapted in such a way that we finally arrived in Salzburg on time!

Deutsche Bahn has been awarded an "innovation prize" for the dynamic adaptation of the timetable during a train journey depending on any disruptions that occur.

SAP could adopt this "business process" for its roadmaps and thus avoid a lot of stress for existing customers. "Deadline 2025" would then be just SAP's wishful thinking, but no longer a sword of Damocles for existing customers.

SAP adapts the time parameter, sets a new year count for the greater Walldorf area, and "Deadline 2025" is then celebrated by the SAP community in the real year 2030, right?

Things will not be as easy and simple on the Hana roadmap as they are on the train from Munich to Salzburg: SAP has already scheduled the database contracts with IBM, Oracle and Microsoft. It's a lot like Brexit.

The AnyDB exit date has been set for a long time. After 2025, there can and will be no more database support from SAP for IBM, Oracle and Microsoft.

AnyDBexit? It is hard to imagine SAP CEO Bill McDermott making a pilgrimage to the three partners and asking for forgiveness and a postponement. He will not want this loss of face.

It would certainly be amusing if McDermott were to knock on Larry Ellison's door together with Professor Hasso Plattner to ask for an AnyDBexit extension. No, for such tasks there is currently a sweeper on the SAP Executive Board who gets all the unpleasant tasks shoved at him: SAP Chief Operating Officer Christian Klein.

This young board member is already allowed to take care of the delicate integration of all cloud purchases into the ERP. So why not this impossible task as well? Board member Christian Klein:

"It's 2030 and we've hit the 2025 deadline on the dot with SAP's dynamic roadmap!"

Naturally, it is extremely risky to say anything at all coming about the SAP database Hana, especially if it concerns the future. As part of the large-scale response, SAP has also laid off numerous Hana and Abap experts and programmers, including an entire Hana lab in California with about 250 employees.

Who is now to drive out all the anomalies from the database and provide the emergency patches in the future is uncertain. Perhaps Bill McDermott can get help and advice from Deutsche Bundesbahn?