Sap Se

Sap Ag

Christian Fuhlbruegge

Uwe Schlarb

Rene Dehn

Georg Wilhelm

Daniel Wachs

Karsten Schaser

Christian Holzer

Daniel Niehoff

Fabian Fellhauer

Timm Falter

Klaus Herter

Otfried Von Geisau

Marcel Hermanns

Karsten K Bohlmann

Archim Heimann

Thomas Wieczorek

Michael Hartel

Nadine Sachs

Dieter Krisch

Volker Faisst

Silke Massmann

Tobias Melcher

Steffen Springborn

Steffen Weinstock

Cornelia Haase

Thomas Henn

Karlheinz Agsteiner

Mike Hirsch

Matthias Herchenroether

Andre Doerfler

Arno Mielke

Alexander Stefan Adam

Thomas Kretz

Dorothea Martin

Katharina Sorge

Doris Karbach

Sabine Worbs

Ulrich Spinola

Werner Sottong

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

Generation of an engineering change case is initiated by associating an identified problem for a product with an engineering change case template. The engineering change case can include a plurality of structured folders that can be populated with content characterizing the identified problem as well as proposed solutions to the identified problem with each folder being assignable to one or more users and having associated deliverables for such users. The various users populate the folders with content associated with the deliverables with at least a portion of the deliverables being delegable and requiring completion in a sequential order. Thereafter, generation of the engineering case can be finalized when an indication is received that all deliverables requiring approval have been completed. Otherwise, the engineering change case can be canceled. Related apparatus, systems, techniques and articles are also described.

Collaborative environment to assess, design, and implement product changes

The present disclosure relates to methods, systems, and software for processing or otherwise managing scrap information in a business application. For example, the software can instantiate a planning business object using production model data for production activities. The business object data and scrap information may be used to calculate requirements for a production planning model. The calculations may include adding an activity yield to activity scrap and fixed resource scrap to generate a component quantity. The component quantity can be multiplied by a component scrap ratio to generate additional component requirements. The component quantity may be added to the additional component requirements to determine a total quantity.

Logically centralized scrap management using planning operations

Growing community of inventors

Spechbach, Germany

Christian Fuhlbruegge