Sap Se

Sap Ag

Successfactors, Inc.

Daniel Goldmann

Frank Brunswig

Udo Peter Klein

Jan Teichmann

Stefan A Baeuerle

Joachim Fitzer

Daniel Hutzel

Thomas Gauweiler

Steffen Tatzel

Mario Andy Mueller

Jens Weiler

Dirk A Giebel

Matthias Klauer

Esther Landes

Joachim Pfeifer

Heiko Steffen

Oleg Loewen

Bare Said

Oliver Klemenz

Bernhard Thimmel

Michael Seubert

Marcel Hermanns

Dietmar Nowotny

Werner Gnan

Thilo Kraehmer

Daniel Bock

Joachim Kenntner

Markus A Peter

Robert Doerner

Robert Getzner

Christian Haas

Rudolf Winkel

Otto Makris

Karsten Soegaard Egetoft

Jochen A Rasch

Axel Kuehl

Lukas Melzer

Otfried Geisau

Giovanni Deledda

Adam Kiwon

Frank Thome

Corinne Kuster

Thomas John

Burkhard Weiss

Achim Seubert

Dirk Becker

Michael Redmann

Qendrim Kuqi

Philippe Drouin

Werner Laber

Patrick Gross

Arndt Koester

Thomas Witzel

Sandra Schmidt

Qian Chen

Ralf Dielschneider

Andreas Krompholz

Ramesh Nn

Jan Stephan

Sergej Stotz

Klemens Schmid

Klaus Akemann

Michael Frauenkron

A method for configurable in-application event logging may include receiving, from a client device, one or more user inputs specifying at least one of an event of interest associated with an operation of a software application and a data to collect in response to the event of interest. A logging agent may be configured, based on the user inputs, to respond to the specified event of interest by generating one or more log messages including the specified data. The logging agent may be as a first programming code embedded within a second programming code implementing the software application such that the logging agent is able to access a context of each executing instance of the software application. Related systems and computer program products are also provided.

Configurable in-application event logging service

An Application Program Interface (API) manages synchronization and replication of master data of a system with different consumers. An API engine is configured to receive from the third party, a query including content information and date-relevant information including a start date, an end date, and a date of last synchronization. The API engine processes the query to access the database and produce a query result replicating only data changes affecting that period or a previous time. The consumer thus specifies the time period in which to consider changes to the stored database data, and the API calculates the delta according to that period. In this manner complex, time-dependent delta calculation and filtering logic can be implemented in the API without requiring substantial logic or additional data persistence in middleware. Particular embodiments may facilitate efficient synchronized replication of employment data to outside (e.g., payroll, benefits) providers.

Application program interface managing synchronized data replication

A system, a method, and a computer program product for replication of data changes are disclosed. Based on a received data query, at least one attribute of stored data is identified for replication. The attribute corresponds to at least one parameter of the received query. Data stored at a first time and data stored at a second time are retrieved. The second time is subsequent to the first time. Data stored at the first time is compared to the data stored at the second time to determine a delta difference between the data stored at the first and second times. The computed delta difference is selected for the identified attribute. The selected computed delta difference is replicated in response to the received query.

Delta replication

Methods and apparatus, including computer program products, are provided for providing a query language based on a model. In one aspect, there is provided a computer-implemented method. The method may include receiving a first query; generating, based on a model including metadata representing a data structure, a second query specific to the data structure stored in a database; and sending the second query to the database. Related apparatus, systems, methods, and articles are also described.

Query language based on business object model

A view object is generated in a target deployment unit in a design time environment of a metadata repository. The view object is modeled on a business object of a source deployment unit. The source deployment unit includes process components of a business application that is physically decoupled from the target deployment unit. A subset of attributes of the business object of the source deployment unit is selected. The subset of attributes includes at least an outbound agent and an inbound agent implemented by a generic messaging framework. The view object is modeled in the target deployment unit with the subset of attributes of the business object. The inbound agent of the view object is configured for receiving a replication message from the outbound agent of the business object, and the replication message includes replication data for configuring the view object only with data from the business object.

Declarative view objects

A computer system includes instructions recorded on a computer-readable storage medium and executable by at least one processor. The computer system includes a process component of a first deployment unit and a component module. The process component has a handling module and an object module. The handling module is operatively coupled to the object module. The handling module is operatively coupled to the component module. The handling module is configured to receive a message from a second deployment unit.

Systems and methods for sending and receiving communications

A business object model, which reflects data that 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.

Consistent set of interfaces derived from a business object model

A system and method of improving error handling in a development environment created by a platform provider in which a third party developer develops applications for use by customers The method includes storing business objects and error messages, where the error messages corresponds to potential errors during run time processing of the plurality of business objects. The method further includes receiving a first user input regarding an error situation, where the error situation includes a resolution of the error situation, and receiving a second user input that associates the error situation with a sub-subset of a subset of the error messages. In this manner, the usability of the platform is improved.

System and method of error handling in a platform as a service environment

A bulk service interface can be instantiated for each of at least one service provider providing a plurality of business objects using a stored definition of a plurality of metadata properties relating to generation of a user interface that incorporates content of a plurality of business objects. The bulk service interface can query the stored definition and access, in a bulk metadata access process, dynamic metadata required for instantiation of the plurality of business objects. If the stored definition has not previously been received, a default bulk services access process that queries an existing dynamic metadata access interface of each of the plurality of business objects can be initiated to retrieve the dynamic metadata from each of the plurality of business objects. An instance of the user interface can be generated using dynamic metadata accessed by the bulk service interface and/or the retrieved by the default bulk services access process.

Bulk access to metadata in a service-oriented business framework

Embodiments of the present invention relate to creating a new change pointer to indicate a change to be made to data on a database. For a receiver of the data, it may be determined whether the receiver requires historical data, and if so, an image of the data may be created before changing it. The historical data, in the form of an image or images, may be subsequently 'pulled' (requested and received) by the receiver, or 'pushed' (sent without being requested) to the receiver.

Method and system for maintaining historical data for data receivers

Growing community of inventors

Mannheim, Germany

Daniel Goldmann