Sap Se

Fabian Fellhauer

Karsten Schaser

Timm Falter

Uwe Schlarb

Rene Dehn

Marcel Hermanns

Georg Wilhelm

Daniel Wachs

Christian Fuhlbruegge

Christian Holzer

Thomas Henn

Mike Hirsch

Matthias Herchenroether

Karsten K Bohlmann

Thomas Wieczorek

Daniel Niehoff

Matthias Becker

Tilmann David Kopp

Steffen Weinstock

Cornelia Haase

Tobias Melcher

Fee Grauf

Kolja Gross

Boyan Boychev

Victoria Kosten

Shyam Balachandran

Martin Bretzer

Volker Drees

Ranzo Colle

Arunkumar S

Steffen Mattes

Briefly, embodiments of a system, method, and article for receiving a user input requesting that an initial application container compatible with a first programming model be modified to generate an adjusted application container compatible with a second programming model. The second programming model is different from the first programming model. A first set of development artifacts may be determined for the initial application container. A first subset of the first set of development artifacts may be automatically adjusted to enable compatibility with the second programming model. automatically generate One or more behavior definitions associated with the automatically adjusted first subset may be automatically generated. The adjusted application container comprising the initial application container and the one or more behavior definitions may be generated.

Programming model migration tool

An enterprise database server may store enterprise information. An application layer server, coupled to the enterprise database server, may use an application programming language (e.g., ABAP) to access the enterprise information. The application layer server may execute a plurality of domain runtimes, each associated with a domain service (e.g., transactional, SQL, analytical, search, etc.). The application layer server may also access, by a first domain runtime, a first data service entity in an infrastructure for data modelling (e.g., CDS) that enables data models to be defined and consumed on the enterprise database server. Similarly, the application layer server may access, by a second domain runtime, a second data service entity in the infrastructure for data modelling. According to some embodiments, the first data service entity includes a first provider contract and the second data service entity includes a second provider contract (different than the first provider contract).

Domain specific provider contracts for core data services

Implementations of the present disclosure include receiving, by a parser, a view source file and an extension source file, the view source file defining a view on data stored in a database, the extension source file defining an extension to the view, parsing, by the parser, the view source file to provide a view abstract syntax tree (AST) and the extension source file to provide an extension AST, providing, by the parser, a merged AST based on the view AST and the extension AST, generating a mixed runtime data object using the merged AST, and providing the mixed runtime data object for consumption by at least one runtime component.

Lightweight extension of core data services

The present disclosure involves systems, software, and computer implemented methods for ensuring seamless lifecycle stability for extensions to standard software products. One example method includes determining a requested change to a software feature of a software object. The software feature has been designated as an extensible software feature and is associated with a lifecycle stability contract that identifies aspects of the extensible software feature that are designated to remain stable across different releases of the software object. The lifecycle stability contract is used to perform a compatibility check for the requested change to determine whether the requested change complies with the lifecycle stability contract. The requested change is permitted in response to determining that the requested change complies with the lifecycle stability contract and the requested change is denied in response to determining that the requested change violates the lifecycle stability contract.

Seamless lifecycle stability for extensible software features

Growing community of inventors

Oestringen, Germany

Fabian Fellhauer