Sap Ag

Sap Se

Successfactors, Inc.

Mario Andy Mueller

Stefan A Baeuerle

Thomas Wieczorek

Robert Getzner

Till Oppert

Christoph W Glania

Peter W Engel

Joachim Gaffga

Daniel Goldmann

Johannes Bechtold

Paul P Tanzer

Esther Landes

Joachim Pfeifer

Matthias Klauer

Leif Albers

Jan Brink

Herbert Boche

Oleg Loewen

Matthias Richter

Ulrich Bestfleisch

Thomas Vogt

Paola Sala

Thomas Moser

Markus Wolf

Fabian Guenther

Benjamin Klehr

Stefan Kiefer

Christian Boehrer

Rolf Schimpfky

Oliver Grande

Thomas Witzel

Christine Hoerner

Pramod Sidlaghatta Jaiprakash

Qendrim Kuqi

Qian Chen

Richard Pahner

Heiko Braumann

Thomas Dubiel

Andre Von Rekowski

Klemens Schmid

Elena Gurevitch

Jennifer Kroner

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

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 a message-based communication arrangement, an organizational center replication request, and a payment schedule business object.

Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule

Status of software product(s) may be monitored through the cloud by Extract, Transform, Load (ETL) of status information, in the form of business process status indicators from customer tenants. Examples of such status indicators can include a backlog of tasks to be fulfilled, or a number of business documents present in specific processing states, which describe aspects of the business application and allow an understanding of the overall status of the monitored application. A data extractor component of a customer tenant may extract and transform the status indicators from a plurality of business documents. A data import framework of a central monitoring system may in turn employ mapping to condense that heterogeneous data into a monitoring-specific simplified status model.

Software product management through the cloud

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 a communication system and/or an object identifier mapping business object.

Managing consistent interfaces for communication system and object identifier mapping business objects across heterogeneous systems

Embodiments consistent with the present invention relate to methods and systems for verifying data of an application system. Consistent with exemplary embodiments, such methods and systems may send a message including data copied from a first data set processed by a first processing component and then store outbound messaging data describing the sent message. A second processing component may receive the sent message and store inbound messaging data describing the received message. The methods and systems may then verify a consistency of the data of the first and second processing components according to a comparison of the outbound and inbound messaging data.

Data verification systems and methods based on messaging data

Embodiments consistent with the present invention relate to methods and systems for verifying data or data communication operations of an application system. Consistent with exemplary embodiments, such methods and systems may verify a data communication operation by an application system. The methods and systems may, for example, communicate a message including data copied from a first data set and store messaging data describing the communicated message. As described, the methods and systems may then verify the communication of the message based on the first data set and the stored messaging data.

Systems and methods for verifying a data communication process

Embodiments consistent with the present invention relate to methods and systems for verifying data of an application system. Consistent with exemplary embodiments, the method may generate a first business object and generate a second business object from the data related to the first business object. The method may then access metadata defining content included in the first and second business objects. The method may then verify a consistency of data in the first and second business objects according to a comparison of the first and second business objects based on the accessed metadata.

Data verification systems and methods using business objects

Growing community of inventors

Muehlhausen, Germany

Mario Andy Mueller