Sap Se

Sap Ag

Daniel Wachs

Udo Peter Klein

Uwe Schlarb

Georg Wilhelm

Daniel Niehoff

Daniel Figus

Christian Fuhlbruegge

Karsten Schaser

Christian Holzer

Bernhard Thimmel

Matthias Lehr

Fabian Fellhauer

Stefan A Baeuerle

Timm Falter

Martin Hartig

Knut Heusermann

Thomas Fiedler

Rene Dehn

Steffen Witt

Gregor Karl Frey

Reinhold Kautzleben

Thomas Schneider

Marcel Hermanns

Karsten K Bohlmann

Thomas Wieczorek

Johann Kemmer

Andreas Wildhagen

Joerg Weller

Karsten Fanghaenel

Tobias Melcher

Steffen Weinstock

Ralf Schroth

Cornelia Haase

Thomas Henn

Mike Hirsch

Matthias Herchenroether

Roland Brechter

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

The present disclosure involves systems, software, and computer implemented methods for enabling data source extensions for individual customers of a cloud platform. One example method includes receiving an extension request, from a particular customer, to extend a data source used to populate an application output. A selection is received of at least one field to be included in a data source extension that extends the data source. Extensibility metadata is stored, in association with the particular customer, that defines the data source extension. The extensibility metadata identifies the data source, the particular customer, and the selected at least one field. A data request is received, from a client device of a user of the customer, for a field included in the data source extension. The data source extension is used to retrieve a field value for the field and the field value is provided in response to the data request.

Enabling data source extensions

In one aspect, there is provided a method. The method may include performing, by a sequencer, one or more validations of a plurality of extensions to a core service of a business system; controlling, by the sequencer, execution of a sequence including the plurality of extensions and the core service to enable an action to be performed at the business system; and performing, by the sequencer, one or more post-processing checks of the plurality of extensions. Related systems, methods, and articles of manufacture are also disclosed.

Sequencing of business object logic extensions to ensure data consistency across layers

Software solutions in a business software framework can expose their data via web services, which can readily provide access to all non-customized fields of objects included as part of the default installation of the software solution. However, customer-added extensions, such as for example custom fields and the like, added to customize the software solution for a specific business or business use can be difficult to add to web services by a typical business user who lacks technical abilities. Described herein are approaches to enabling addition of custom fields to web services via an intuitive interface that does not require technical understanding of the software solution, the business software framework, web services, etc.

Self service propagation of custom extension fields into web services

A multi-tenant environment can support field extensibility via extension tables. An in-memory, columnar database can store a core table being extended as well as the corresponding extension table. Transactional and analytical processing can be performed on the extension fields. A business-objects-based system can take advantage of the technologies to provide greater flexibility, security, and performance improvements.

Field extensibility in a multi-tenant environment with columnar database support

In one aspect, there is provided a computer-implemented method. The method may including selecting an existing business object for extension in an extensibility integrated development system; generating, in the extensibility integrated development system, a page highlighting one or more nodes of the existing business object to allow selection of the one or more nodes for modification; selecting, in the extensibility integrated development system, at least one of the one or more nodes, when highlighted; modifying, in the extensibility integrated development system, the selected one or more nodes by adding at least one attribute to the at least one of the selected one or more nodes; and storing, in a repository, the modified node including the added at least one attribute. Related apparatus, systems, methods, and articles are also described.

Extensibility integrated development environment for business object extension development

A system and method for creating extension fields for business objects are described. In various embodiments, a system includes modules to display business processes and business objects thereof in graphical user interface screens. In various embodiments, the system propagates created extension fields to other business objects via metadata derived from selections in the graphical user interface. In various embodiments, a method for propagating extension fields from one business object to another business object via a data flow between the two business objects is presented. In various embodiments, the method receives instructions from a graphical user interface for the propagation of an extension field and sends instructions to a backend module to propagate the extension field from the source business object to the other business object.

Propagating business object extension fields from source to target

Systems and techniques for extending data flows are thus described. In one aspect, an article includes one or more machine-readable media storing instructions operable to cause one or more machines to perform operations. The operations can include receiving extension information identifying an extension of a first object in a data processing system landscape, accessing data flow information to identify one or more data flows that involve the first object, and extending, on the basis of identifying the one or more data flows as involving the first object, at least some of the one or more data flows so that information in the extension is conveyed between instances of the first object and instances of a second object during data processing in the data processing system landscape. The identified data flows convey stored information from one object to another.

Extending data flows

Growing community of inventors

Mannheim, Germany

Daniel Wachs