Planning reliability
In a time of constant growth, it is naturally also important to plan, make provisions and practice controlling. As probably everyone knows: In times of new beginnings and growth, current mistakes and omissions can be concealed by guaranteed future successes.
Was the announcement of C/4 a mistake? Was the application and adaptation of "indirect" use a mistake? Was the original Suite 7 deadline of 2025 a mistake?
We don't know, because in recent years SAP has rushed from one success to the next. The stock market price rose, sales and profits grew - no time for criticism, self-reflection or course correction.
At the moment, we have a new and unknown situation medically, socially and economically. Demanding planning security now seems absurd at first glance. My wife looks over my shoulder as I write and asks, "Which buck do you want to pass to SAP again now?"
Editor-in-chief Färbinger's first name is Peter, so we could sic him on SAP to ask the unpleasant questions. However, I would also be happy to take on this role as an existing customer on behalf of the journalist.
The SAP share price is fluctuating wildly. Sales of on-prem licenses fell by 30 percent in the first quarter. SAP is also plowing through calm seas at the moment. These challenges should be motivation to provide quick and transparent answers to important and independent questions.
The first thoughts about the Suite 7 maintenance extension began as early as last fall. Together with the official announcement at the beginning of this year, there was also a sufficient roadmap for the NetWeaver stacks Abap and Java on the SAP service marketplace - but no perspective on AnyDB.
More than half of all existing Suite 7 customers use Oracle as their database. There is no need to report on the relationship between Larry Ellison and Hasso Plattner here, but the fact that ex-chief technology officer Vishal Sikka is working for Ellison in the meantime seems to me to be absolutely worth mentioning: Will Sikka reveal the Hana secrets to his new boss?
The SAP community has no planning certainty because, on the one hand, AnyDB is on its way to an uncertain future after 2025 and, on the other hand, Hana is being torn between on-prem and cloud.
Finding a platform strategy for a future SAP ERP is almost impossible. SAP would have to publish a comprehensive and consolidated Suite 7 roadmap now, including AnyDB and NetWeaver.
SAP would have to provide clarity regarding the Hana platform as on-prem and cloud version. SAP would have to provide information about a future PKL and "indirect" use.
AnyDB, NetWeaver, PKL, Cloud, etc. demand answers that could all be worked out in the home office. In order to ensure planning security for SAP's existing customers, there is no need for Sapphire or trips on the SAP private jet.
A simple telco on SAP Connect would be sufficient to clarify these issues with DSAG and us existing customers - which is why, even in these uncertain times, I demand sustainable planning security from SAP.
In other words, planning from which new things can grow again, on which the community can realize its digital transformation. This appeal is not directed against SAP, but is intended as encouragement for the entire SAP community.
Whether there will still be a DSAG annual congress in Leipzig this year is naturally uncertain. Whether Germany will remain the world export champion is perhaps also uncertain.
Many unanswered questions dominate our private and professional lives at the moment. However, we should and will have to fulfill our tasks. To do so, the SAP community needs the support of its partners and SAP itself. Planning security is part of the basic equipment of responsible action.
