Sap Se

Steffen Witt

Knut Heusermann

Uwe Schlarb

Daniel Figus

Matthias Lehr

Daniel Wachs

Matthias Becker

Torsten Buecheler

Oliver Berger

Christian Hohmann

Stefan A Baeuerle

Martin Haerterich

Bernhard Thimmel

Mukesh Kumar

Thomas Vogt

Rene Dehn

Georg Wilhelm

Daniel Niehoff

Stefan J Moeller

Guang Yang

Mohit V Gadkari

Olga Kreindlina

Santhosh N

Dietmar Henkes

Karsten Fanghaenel

Sophie Kraut

Esther Landes

Walter Zimmermann

Marcus Echter

Albert Neumueller

Ralf Schroth

Xenia Rieger

Thomas Witzel

Karthik Narayanan Mohan

Kritesh Vasing

Marcel Steinleitner

According to one general aspect, a method may include replicating, to a software-as-a-service application, a plurality of pieces of master data from a physically remote master database. The method may also include converting the plurality of pieces of master data into one or more pieces of local data of the software-as-a-service application. The method may include changing one or more of either the pieces of master data or the pieces of local data. The method may further include synchronizing the changed pieces of either master data or local data between the remote master database and the software-as-a-service application.

Integration scenario for master data with software-as-a-service system

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 business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an entitlement product business object.

Consistent interface for entitlement product

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

Growing community of inventors

Heidelberg, Germany

Steffen Witt