Sap Ag

Sap Se

Wolfgang Nieswand

Christoph Lehner

Georg Podhajsky

Tao Yu

Thomas Nitschke

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Renzo Colle

Michael Seubert

Paola Sala

Stephan Hetzer

Werner Gnan

Thilo Kraehmer

Joachim Kenntner

Johann Kemmer

Gregor Rieken

Markus A Peter

Toralf Grossmann

Andreas Bold

Matthias Schmitt

Stefan Adelmann

Antonia Gross

Markus Biehler

Andre Wagner

Andreas Brossler

Rudolf Winkel

Ralf Sievers

Otto Makris

Andreas F Morsch

Thomas Maag

Stefan Elfner

Volker Jaeck

Stefan Franke

Michael Zoeller

Jochen A Rasch

Axel Kuehl

Karsten Koetter

Corinne Kuster

Uwe Pyka

Ruediger Radcke

Daniela Schapler

Andreas Schneider

Frank Thome

Dagmar Schultze

Joerg Hendricks

Wolf Hengevoss

Christine Hofmann

Bernhard Kelnberger

Dominic Poetschke

Jens Zachmann

Theo Zimmerman

Gabriel Alvarez

Gerhard Gschwender

Dietmar Nowotny

Daniel Bock

Robert Doerner

Arnulf Schueler

Volker Ripp

Renato Zadro

Adam Kiwon

Werner Liebold

Gururaj Raman

Reiner Seyler

Christof Weissenberger

Frank Brunswig

Yuh-Cherng Wu

Steffen Tatzel

Jan Heiler

Berthold Wocher

Michael Jung

Ingo Pfitzner

Christopher Ronnewinkel

Andrea Sudbrack

Volkmar Stegmann

Christian Haas

Hamid Moghaddam

Thomas Bach

Alexander Koegler

Andre Wachholz-Prill

Devasena Rajamohan

Dagmar Opitz

Rainer Heun

Steffen Hartig

Olivier M Dreidemy

Uwe Herold

Dietmar Storz

Joachim Barnbeck

Peer Marschall

Martina Lahr

Christoph Engler

Cordula Ude

Theo Zimmermann

Martin Helm

Katja Kasteleiner

Frank Reinemuth

Michael Lesk

Alexandra Mark

Boris Krems

Martina Keller

A first tenant-nonspecific database table on a repository accessible to an application server of a multi-tenant software delivery architecture can maintain a first record designating a first predefined generic field of a plurality of predefined generic fields. The first record can include an organization-specific master data field definition of the first predefined generic field maintained in a first tenant-specific definition field assigned to a first customer tenant of a plurality of customer tenants that are accessible via the application server. Each customer tenant of the plurality of customer tenants can provide a discrete organization-specific business configuration of a core software platform. A second tenant-nonspecific database table maintained on the repository can maintain a second record that can include a key value designating the first tenant, a record designator, and an organization-specific master data value corresponding to the first predefined generic field. A calculation or determination based on master data can be performed that is relevant to the discrete organization-specific business configuration provided by the first customer tenant using the organization-specific master data value.

Persistence of master data in a multi-tenant software delivery architecture

Methods and systems consistent with the present invention provide a data processing system having a business object model reflecting the data used during a business transaction. Consistent interfaces are generated from the business object model. These interfaces are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.

Consistent set of interfaces derived from a business object model

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Providing customer relationship management application as enterprise services

Systems and methods are described that permit objects from runtime environments that are incompatible with one another to be co-executed on a computing machine. Depending on which object can service the request, a generic proxy may send the request to the proxy of the particular runtime environment associated with that object. The proxy may call the appropriate methods of the object therein to service the request. Each runtime environment may be isolated from other runtime environments by a container such that catastrophic errors in one runtime environment do not disrupt the execution of objects in another runtime environment. A first object in a first runtime environment may execute methods in a second object in a second runtime environment by invoking a proxy of the second runtime environment to call the methods of the second object.

Co-execution of objects from divergent runtime environments

Growing community of inventors

Muehlhausen, Germany

Wolfgang Nieswand