Sap Ag

Sap Se

Successfactors, Inc.

Philipp Suenderhauf

Christoph Zakwieja

Christiane Konstandin

Jan Piechalski

Peter Latocha

Andreas Bold

Fabian Guenther

Dirk Richtsteiger

Matthias Richter

Simon Dieterich

Tobias Lukas Bader

Anna-Lena Wingert

Guy Cases-Langhoff

Matthias Tebbe

Thomas Moser

Frank Schuhmacher

Wilko Dann

Marcus Philipp

Walter Koller

Peter Sieber

Ralf Philipp

Jan Penning

Helgi Thorleifsson

Jens Ruths

Volker Paul

Detlef Pluemper

Stefan Gerard

Ricardo Bustamante

Anna-Lena Spaegele

Horst Vaeth

Silke A H Gruber

Marc Moesges

Jasmin Haas

Technologies are described for replicating selected changes to planned working time from a first system, such as an HR system, to a second system, such as a payroll system. For example, upon receiving an indication of a change to a planned working time for one or more workers on one or more days, the first system can evaluate the change to determine whether it should be replicated to the second system. The determination can be based on whether the change is a temporary change, as well as based on information read from a data replication configuration object, a data replication period object, and/or an in-sync work schedule object. Upon determining that the change should be replicated to the second system, a data replication proxy object can be created based on the change and used to transmit data regarding the change for replication at the second system.

Replication of planned working time information

Performing data replication from a time management system. The method includes reading, by a replication controller, a replication configuration upon creation, modification, or deletion of a first data object. The configuration references a replication scenario of a defined set of replication scenarios, the replication scenario having one or more associated replication scenario objects. The method further includes creating, or changing a status of, a data replication proxy object if the first data object is an associated replication scenario object of the replication scenario, the data replication proxy object referencing the first data object. The method further includes receiving a query requesting instances of the data replication proxy object having a status of out of sync or deleted. The method further includes responding to the query with the instances of the data replication proxy object having the status of out of sync or deleted.

Systems and methods for configurable replication of time data

Methods and apparatus, including computer program products, are provided for document synchronization. The method may include generating, by a controller, a first proxy object for a first document at a first system, the first system including the controller and the first proxy object; updating, by the controller, the first proxy object to include a replication status of the first document, when a creation, an update, and/or a deletion occurs at the first document. Related apparatus, systems, methods, and articles are also described.

Synchronizing document replication in distributed systems

A current time associated with a first received notification of a new object in a data set of a first system is accessed and a replication time is set to the current time. For each notification received regarding a new object in the data set of the first system, the new object is added to the replication queue. The new objects added to the queue are assigned the replication time until a specified maximum number of new objects have been added to the replication queue. Afterwards, new objects are added to the queue with no assigned replication time. When the objects in the queue are to be replicated, only the objects with the assigned replication time are copied from the queue to a second system. A new replication time is set to a new current time associated with confirmation of receipt of the copied objects received from the second system.

Sequential replication with limited number of objects

Methods, systems, and apparatuses, including computer program products, for implementing a software architecture design for a software application implementing personnel events functionality. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include a personnel administration process component, a payroll processing process component, an expense and reimbursement management process component, a time and labor process component, a compensation management process component, an employee payroll administration process component, and numerous country-specific employer regulatory compliance process components.

Architectural design for personnel events application software

Methods and apparatus, including systems and computer program products, for a service architecture design that provides enterprise services having human capital 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 human capital management software application as enterprise services

Methods and apparatus, including systems and computer program products, for a service architecture design that provides enterprise services having payroll 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 payroll software application as enterprise services

The subject mater herein relates to human resources data processing and, more particularly, to separation of employee data for different applications, such as personnel administration applications. Various embodiments provide systems, software, and methods that maintain a first set of employee data in an employee object, wherein the first set of employee data is valid across one or more other objects, and executing a process of a business object requiring at least a portion of the first set of employee data. In some embodiments, the business object obtains the portion of the first set of employee data from the employee object and maintains a second set of employee data that is not valid across all other objects.

Separation of employee data for different applications

Growing community of inventors

Leimen, Germany

Philipp Suenderhauf