Sap Se

Sap Ag

Georg Wilhelm

Uwe Schlarb

Rene Dehn

Daniel Wachs

Daniel Niehoff

Daniel Figus

Michael Acker

Juergen Remmel

Rainer Andreas Dattke

Christian Fuhlbruegge

Karsten Schaser

Steffi Kramer

Sigrun Wintzheimer

Christian Holzer

Fabian Fellhauer

Stefan A Baeuerle

Timm Falter

Martin Hartig

Bernhard Thimmel

Frank Stienhans

Knut Heusermann

Thomas Fiedler

Hilmar Demant

Reiner P Hammerich

Marcel Hermanns

Karsten K Bohlmann

Frank Seeger

Thomas Wieczorek

Matthias Lehr

Steffen Witt

Tobias Melcher

Steffen Weinstock

Ralf Schroth

Cornelia Haase

Jutta Bindewald

Felix Wente

Thomas Henn

Mike Hirsch

Matthias Herchenroether

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 embodiment, a method stores extension logic for a business context for an application in a backend database system. The extension logic is stored with respect to a database table, business logic to handle transactions in the backend system, and an application programming interface to the application. A request for a custom field is received through a runtime version of the application, the custom field specifying a business context in which the custom field is associated. The method determines the extension logic associated with the business context in the backend database system. Further, the method uses the extension logic to extend the database table with the custom field, extend the business logic to handle transactions for the custom field in the backend system, and extend the application programming interface to the application. The custom field is extended during runtime of the application.

Field extension in database system

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

An extension naming approach for avoiding naming collisions in de-normalized view on a business object can include accessing a reference field bundle, which includes reference field(s) corresponding to a core business object defined in a core software platform of a software architecture, from a metadata repository. A user can define an extension to the business object based on the core business object, for example via a development environment. The reference field(s) can include a defined path from a node in a peripheral object to a corresponding node in the core business object. A unique and reproducible name for the extension field can be generated based on the reference field, and the extension field with the unique and reproducible name can be added to the business object and to a data model of the peripheral object.

Naming algorithm for extension fields in de-normalized views

Methods and apparatus, including computer program products, providing and using composite extension definitions. A composite extension definition has one or more extension definitions, each of which can be either an atomic or a non-atomic extension definition. In one aspect, a program has instructions to create a composite extension definition, to generate composite metadata that represents the composite extension definition, and to store the composite metadata for later use. The program can include instructions to receive input specifying dependency relationships between or among extensions defined by the extension definitions and to include the relationships in the composite metadata. Composite extension definitions can be created by an application developer for use by customers to guide them in implementing and deploying extensions to a computer program application.

Composite computer program extensions

The description includes methods and apparatus, including computer program products, for detecting and handling changes to back-end systems. Configuration data for a pattern is received. The pattern includes a predefined arrangement of user interface elements and specifies predefined actions that can be performed using the user interface elements. The configuration data includes a first version identification and specifies associations between one or more of the user interface elements and one or more entities in a back-end system. The back-end system is accessed and a second version identification is obtained. If the first version identification does not match the second version identification, the configuration data is modified based on information about the back-end system.

Detecting and handling changes to back-end systems

Methods and apparatus, including computer program products, for implementing extensions for computer program applications. A program according to one aspect of the invention has instructions to receive an application call to an extension method defined in an extension object definition, the extension object definition having associated extension object implementations, the extension object implementations providing extension method implementations of the extension method; instructions operable to obtain results by calling multiple extension method implementations of the extension method; and instructions operable to respond to the application call using the results obtained from the extension method implementations. A method according to another aspect includes the steps of deploying multiple extension method implementations for an extension method; and executing the multiple extension method implementations to determine the results of calling the extension method.

Automatically upgradeable extension of software

Growing community of inventors

Kronau, Germany

Georg Wilhelm