Allow for ABAP dynamic programming in Steampunk Well-known services such as number ranges have been Cloud enabled and were added to the whitelist recently. At least the list of released objects is growing continuously. We got the “small” part right, but are still working on the speed -). Start with a small whitelist (the public stable interface) and grow it responsibly Principal propagation is in the pipeline. Support backend connectivity to on-prem systems and to the Cloudīackend connectivity via HTTP (including OData) and RFC has been enabled with technical users. Stay tuned for SAP TechEd 2019 announcements.
#Steam punk trial
We’ve been offering trial versions, but until today only for some of you, based on invitation. All this input is extremely helpful and has already shaped the latest Steampunk versions. Many customers had dedicated dev angels from the Steampunk team who provided support and collected feedback. The Early Adopter Care program was established immediately in September 2018, and all stakeholders can give feedback via the SAP Influence channels. Set up a program for early adopters and learn from first customers We’ve delivered quarterly versions (1808, 1811, 1902, 19), and we’ve always been able to keep our service level agreements. Deliver ABAP PaaS (= Steampunk) on top of SAP Cloud Platform Let’s try an honest reality check here and compare them to our achievements of the past 12 months. Re-reading our announcement blog from last year, we thought it’s a good idea to have a close look at all our promises again. Reality check – what has happened since September 2018? I’m glad I haven’t accepted any of them, and Steampunk is the main reason.
This is a huge success after less than one year.Īs you’ve probably read in the media, SAP made generous early retirement offers to people like me who’ve been around for a long time.
#Steam punk code
Because of you, people today write relevant Steampunk ABAP code and run it in productive scenarios, turning business data into business value. A huge thanks to all the Steampunk folks who got us where we are today, and to all customers for their trust and continued valid feedback.
The Steampunk team has delivered on their promises, even if we still have a long way to go, and even though important features like partner enablement or trial systems still have room for improvement (stay tuned for TechEd announcements). From a strategy perspective, many customers now use Steampunk and start their journey to decouple extension code, with the goal to keep their digital core stable and clean.
In current typical scenarios, Steampunk apps play a hub role integrating SAP systems, SAP Cloud Platform services and external services. Many customers and partners value Steampunk as an innovation platform, and appreciate the access to technology they don’t have yet in their on-prem landscape, like the new ABAP RESTful Programming Model, or brand-new SAP HANA capabilities. The majority of current Steampunk use cases are extensions to on-prem SAP business systems. And we do eat our own dog food and build SAP SaaS solutions on top of Steampunk, the first one planning to go live within this year.īut what exactly are the first customers actually doing with Steampunk? There are lots of productive customer and partner scenarios in development with a go-live planned for early 2020. There are productive business users out there already, using solutions created on Steampunk and running live on Steampunk. The answer is simple: No, don’t worry, you won’t be. If I go productive with Steampunk now, will I be the first? But before we come to that, let me try to anticipate the main question you might have by now, which probably is: This blog is a short summary of what has happened so far. One year later, Steampunk has grown up (well, at least to teenage level, I’d say -). And we promised a living thing that evolves and that you can influence. No matter whether you want to transform your existing on-prem code or write new Cloud extensions for SAP S/4HANA or others. We promised a minimum viable scope enabling you to write ABAP code in the Cloud, for the Cloud. It’s been almost a year now since our announcement that keeps attracting so much attention. So, in this blog it’s Steampunk, and yes, we love that name, too. In this case we didn’t really mind because SAP Cloud Platform ABAP Environment or even ABAP PaaS are real tongue twisters.
0 kommentar(er)
