Technical Articles
Steampunk released ABAP API, first draft is up
Steampunk will expand into S/4 HANA Cloud and S/4 on-premise, as an ABAP developer in Steampunk it is only possible to use released objects when creating applications.
ABAP developers should strive towards using released objects, also in old code on on-premise systems. However, until now, it has been tedious to lookup information about released objects.
Should I use SPRAS or LANGU? STRING_TT, STRING_TAB, or STRING_TABLE?
I hereby introduce abapedia.org, which contains an un-official self-contained partial description of the ABAP API implemented in Steampunk 2111, STRINGTAB example:
Continuous Integration
The definition of the ABAP API is self-contained, and together with language syntax, it is possible to have static analysis tools guide the development towards Steampunk compatibility.
As an example, we are working on making abap2xlsx Steampunk compatible, see the current status and findings in https://github.com/abap2xlsx/abap2xlsx/pull/925. Note that only the core logic is checked for compatibility, not the demo programs.
As always, bug reports, ideas etc. welcome on GitHub. Happy Steampunk’ing ðŸ¤
Cool domain name 😀
Had to put it somewhere that can is easy to remember 🙂 Got too many domains...
Seriously. Thanks for this, Lars. This will really help me a lot.
I like the idea of working with released objects only a lot... I find it really great to have all the classes, interfaces, function groups, function modules and so on in the repository but for a lot of business cases, I just use the BAPIs for well known reasons 🙂
Since this list keeps growing, do we have this list available in any DATA SOURCE in the system like we have ARS_W_API_STATE for the release contract & release info of the objects ? From that list, I would like to understand what is the differentiating indicator for STEAMPUNK objects Vs other Released objects for the Cloud.