Sap Se

Sap Ag

Uwe Schlarb

Stefan A Baeuerle

Bernhard Thimmel

Volker Driesen

Rene Dehn

Daniel Niehoff

Georg Wilhelm

Daniel Figus

Matthias Lehr

Daniel Wachs

Immo-Gert Birn

Christian Stork

Welf N Walter

Ulrich Auer

Ralf-Juergen Hauck

Andrea Neufeld

Torsten Ziegler

Christian Fuhlbruegge

Karsten Schaser

Karsten Fanghaenel

Karsten Fanghänel

Christian Holzer

Frank Brunswig

Juergen Specht

Daniel Zoch

Olaf Meincke

Kerstin Hoeft

Steffen Witt

Fabian Fellhauer

Klaus Rauer

Gerd Ritter

Timm Falter

Martin Hartig

Ioannis Grammatikakis

Frank Jentsch

Knut Heusermann

Thomas Fiedler

Gregor Karl Frey

Markus Viol

Wasim Sadiq

Volker Wiechers

Frank Michael Kraft

Marcel Hermanns

Karsten K Bohlmann

Adam Polly

Ralf Dentzer

Thomas Wieczorek

Toralf Grossmann

Maic Wintel

Anne Jacobi

Andreas Bold

Michael Hartel

Hans-Juergen Hennrich

Martin Müller

Dirk Richtsteiger

Friedhelm Krebs

Steffen Weinstock

Cornelia Haase

Tobias Melcher

Bertram Vielsack

Ralf Schroth

Thea Hillenbrand

Jutta Bindewald

Thomas Henn

Frank Beunings

Mike Hirsch

Johannes Haselberger

Matthias Herchenroether

Matthias Lebr

Oliver Klamenz

Jurgen Specht

Thilo Böhm

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 key pattern management. One example method includes receiving a query for a logical database table from an application. A determination is made as to whether the query is a write query. In response to determining that the query is a write query, a determination is made as to whether the query complies with a key pattern configuration that describes keys of records included in a physical database table that is part of a logical table implementation. The physical table includes records of the logical database table that are allowed to be written by the application. The write query is redirected to the physical database table in response to determining that the query complies with the key pattern definition. The query is rejected in response to determining that the query does not comply with the key pattern configuration.

Key pattern management in multi-tenancy database systems

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

The present disclosure teaches solutions for transitioning between database system sharing types. In one example, a tenant container includes a read-only table, a first writable table, and a mixed table for storing read-only and writable data. When transitioning to a sharing setup, a shared container is created and a shared table is created in the shared container. Data is copied from the read-only table to the shared table and the read-only table is dropped. A read-only view is created in the tenant container and a second shared table is created in the shared container. Read-only mixed data is copied from the mixed table to the second shared table and deleted from the mixed table, and after the deletion, the mixed table is renamed as the second writable table. A union view is created that provides unified access to the second shared table and the second writable table.

Transitioning between system sharing types in multi-tenancy database systems

The present disclosure involves systems, software, and computer implemented methods for deploying changes to key patterns in database systems. One example method includes receiving a new shared container that includes a new key pattern for a logical split table and an updated read-only-portion physical table for a logical split table. The updated read-only-portion physical table includes records that match a complement of the new key pattern. Records that match the new key pattern are identified in the read-only-portion physical table of the logical split table in a current shared container. The identified records are moved from the read-only-portion physical table in the current shared container to a writable-portion physical table in a tenant container. Records not matching the new key pattern are deleted from the writable-portion physical table of the logical split table in the tenant container.

Deploying changes to key patterns in multi-tenancy database systems

The present disclosure involves systems, software, and computer implemented methods for enabling multiple system sharing types in multi-tenancy database systems. One example method includes determining a system sharing type configuration for a database system. The system sharing type configuration is one of standard, shared, tenant, or simulated. Tables are created in the database system based on the system sharing type configuration and the table sharing type of each table. Content is deployed to created tables in the database system based on the system sharing type configuration and the table sharing type of each table. Access is provided to at least one application to the database system based on the system sharing type configuration and the table sharing type of each table.

System sharing types in multi-tenancy database systems

The present disclosure involves systems, software, and computer implemented methods for data separation and write redirection in multi-tenancy database systems. One example method includes providing access to at least one application to a database system. A query is received from an application. A determination is made that the query is associated with a union view that provides unified access to a first read-only table in a shared database container and a first writable table in a tenant database container. A determination is made as to whether the query is a read query or a write query. In response to determining that the query is a read query, the query is processed using the union view. In response to determining that the query is a write query, the query is modified to use the first writable table and the query is processed using the writable table.

Data separation and write redirection in multi-tenancy database systems

The present disclosure involves systems, software, and computer implemented methods for exchanging shared containers and adapting tenants in database systems. One example method includes receiving a request to deploy a new version of a database system. A deployment package is received that includes new version data. A new shared container is installed in parallel to a current shared container. The new version is deployed to each of multiple tenant containers. Each of the tenant containers is individually linked to the new shared container, including dropping at least one view in each respective tenant container to shared content in the current shared container and adding at least one view in each respective tenant container to the updated shared content in the new shared container. Changed tenant content is deployed to each tenant container. The current shared container is dropped after deployment to each of the multiple tenant containers has completed.

Exchanging shared containers and adapting tenants in multi-tenancy database systems

The present disclosure involves systems, software, and computer implemented methods for deploying changes in a multi-tenancy database system. One example method includes upgrading at least one tenant database container in a database system. Table structure differences and table sharing type differences are determined by comparing tables in a current-version shared container to tables in a next-version shared container. A current key pattern configuration in the current-version shared container is compared to an updated key pattern configuration in the next-version shared container to identify key pattern configuration differences. Each table in the at least one tenant database container is upgraded based on the table structure differences, the table sharing type differences, and the key pattern configuration differences.

Deploying changes in a multi-tenancy 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

According to some embodiments, a business service provider may define a stable user interface anchor entity associated with a business object data structure. A reference field may be associated with the stable user interface anchor, the reference field representing a path to a persistent node of the business object data structure. An end user adaptation to a user interface may then be applied in connection with the business object data structure, the adaptation referencing the stable user interface anchor entity.

Stable anchors in user interface to support life cycle extensions

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

Growing community of inventors

Oestringen, Germany

Uwe Schlarb