Abstract: 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.

Abstract: 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.

Abstract: A system, a method, and a computer program product for detection and extraction of data are disclosed. A query containing a filtering parameter for extracting changed data from a plurality of resources is executed. Using the filtering parameter, first data in the plurality of resources is identified. Based on the identified first data, second data stored in the plurality of resources and associated with the identified first data is identified. The identified first data is contained in a first resource in the plurality of resources and the second data is contained in a second resource in the plurality of resources. Based on the filtering parameter, a determination is made whether at least one of the identified first data and the identified second data contain at least one change. At least one of the identified first data and the identified second data from the plurality of resources is retrieved.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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 organisational centre replication request, and a payment schedule business object.

Abstract: 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.

Abstract: 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.