Sap Se

Sap Ag

Gerd Ritter

Tim Kornmann

Rene Gross

Frank Brunswig

Toralf Grossmann

Dirk Stumpf

Daniel Buchmann

Gunther Stuhec

Renzo Colle

Michael Seubert

Stephan Hetzer

Paola Sala

Werner Gnan

Thilo Kraehmer

Joachim Kenntner

Gregor Rieken

Johann Kemmer

Markus A Peter

Pradeep Kumar Singh

Georg Podhajsky

Thomas Nitschke

Andreas Bold

Tao Yu

Wolfgang Nieswand

Andre Wagner

Andreas Brossler

Volkmar Stegmann

Markus Biehler

Antonia Gross

Matthias Schmitt

Rudolf Winkel

Andreas Bettin

Christoph Lehner

Ralf Sievers

Stefan Elfner

Dirk A Giebel

Andreas F Morsch

Thomas Maag

Otto Makris

Jochen A Rasch

Axel Kuehl

Michael Zoeller

Volker Jaeck

Karsten Koetter

Andreas Neumann

Uwe Pyka

Frank Thome

Dagmar Schultze

Daniela Schapler

Timo Wolf

Andreas Schneider

Ruediger Radcke

Corinne Kuster

Theo Zimmerman

Dominic Poetschke

Gabriel Alvarez

Gerhard Gschwender

Joerg Hendricks

Wolf Hengevoss

Christine Hofmann

Stefan A Baeuerle

Dietmar Nowotny

Daniel Bock

Robert Doerner

Arnulf Schueler

Stefan Adelmann

Stefan Franke

Renato Zadro

Thomas Konstandin

Adam Kiwon

Volker Ripp

Uwe Schlarb

Jens Freund

Guenter Pecht-Seibert

Ashish Anand

Thomas Fiedler

Daniel Zoch

Baré Said

Thomas Gauweiler

Reiner P Hammerich

Pavan Kumar

Wolfgang M Koch

Steffen Tatzel

Adam Polly

Marita Kruempelmann

Michael Meyringer

Carsten Thiel

Cristina Buchholz

Ingo Pfitzner

Carsten Brandt

Jens Weiler

Michael Hartel

Jens Kisker

Christian Haas

Erwin Pinter

Ralf Helmut Philipp

Olivier M Dreidemy

Noam Tamarkin

Joachim Pfeifer

René Gross

Disclosed herein are system, method, and computer program product embodiments for extracting customer relationship management (CRM) data from an on-premises database for testing with a cloud-based CRM. The extraction approach simplifies, through the use of a wizard, the selection of relevant customer records and their extraction, along with any dependencies on other records. The extracted records can then be uploaded to the cloud-based CRM for evaluation.

Data migration using transactional data as primary object

Systems and methods to select an object instance from a database storage to archive to an external storage based on an archiving configuration and attribute values of the object instance, transmit the selection to an application associated with the object instance, determine, based on a response received from the application, to archive the object instance, mark the object instance as ready for archiving, identify the object instance as ready for archiving, convert the object instance to an object notation format, transmit the converted object instance to a cloud application for storage in an external storage, in response to a determination that the storage in the external storage is successful, create an index object in the database storage including a subset of fields of the object instance and a link to the converted object instance stored in the external storage, and mark the object instance in the database storage as archived.

Systems and tools for data archiving

In response to a request to present a first user interface to a first user, a first user interface adaptation associated with the first user interface is determined, a first control flag associated with the first user interface adaptation and with a first condition is determined, the first condition based on a value of first master data, and the value of the first master data for the first user is determined, the first control flag is evaluated based on the value of the first master data for the first user. If the first control flag evaluates to True, the first user interface adaptation is applied to the first user interface and the adapted first user interface is presented to the first user and, if the first control flag evaluates to False, the first user interface is presented to the first user.

Master data-dependent user interface adaptation

A synchronization protocol is provided that can be used to resolve synchronization errors encountered while trying to synchronize versions of data objects between a client device and a remote computing system. The protocol includes a client device, in an offline processing mode, handling user interface ('UI') manipulation actions on one or more UI elements of one or more UI screens. The handling of the UI manipulation actions modifies or creates a local version of a data object stored on the client device. The UI manipulation actions are stored by the client device and sent to the remote computing system. The client device receives a synchronization error notification from the remote computing system. After receiving the notification, the client device displays, in one of the UI screens, the local version of the data object and one or more indications of a synchronization error.

Data synchronization error resolution based on UI manipulation actions

An enterprise system which facilitates synchronization of offline data. Offline data created during an offline session or sessions (collectively an offline session) prior to synchronization is assigned a temporary key. Changes of offline data created during an offline session is assigned the temporary key of the data to which the change is associated. The temporary key is mapped to a new created backend key and stored in a mapping table. Using the mapping table, temporary keys associated with the changes are swapped with backend keys which the temporary keys are mapped. This maintains data persistency of newly created and change data during an offline session.

Synchronization of offline instances

A system includes reception of a query input by a user into a user interface, determination, in response to reception of the query, of a plurality of query results, each of the query results associated with a respective object instance of one of a plurality of object types, where the plurality of object types comprise a master data object type and a report object type, and presentation of the plurality of query results to the user, the plurality of query results comprising a first indicator of a first query result associated with an instance of the report object type and a second indicator a second query result associated with an instance of the master data object type, where the first indicator is selectable by the user to cause execution of the instance of the report object type to create a report and presentation of the report to the user, and where the second indicator is selectable by the user to cause retrieval and presentation of the instance of the master data object type to the user.

Enterprise object search and navigation

Extensibility tools are provided to customers for defining custom restriction rules for enhanced access controls. In an example method, a listing of restriction rules available for a business role are presented. The restriction rules include predefined restriction rules and at least one custom restriction rule placeholder, wherein the predefined restriction rules are delivered with the enterprise software system the at least one customer restriction rule placeholders are associated with a link to custom code developed as a customer-specific restriction rule. A selection of a particular custom restriction rule is received and associated with the particular business role. When evaluating the restriction rule, the custom code and a set of master data defined in the custom code is accessed to determine restrictions for each of the end users associated with the business role. A set of access objects are derived for each user based on the information.

Extensibility tools for defining custom restriction rules in access control

A system and method include detection of a set of sequential interactions with a user interface, storage of a recording comprising data associated with a set of sequential calls to a user interface entry point application programming interface of a server application caused by the set of sequential user interface interactions, association of the recording with an incident identifier, reception of a request to analyze an incident associated with the incident identifier, and, in response to the request, initiation of playback of the recording, wherein playback of the recording comprises reading of the data of the recording and, based on the read data, issuing the set of sequential calls to the user interface entry point application programming interface of the server application.

Replication of user interface events

A synchronization protocol is used to transfer information from a remote computing system to a client device. At the remote computing system, synchronization configuration information is retrieved. The synchronization configuration includes a synchronization rule specifying a data object schema to which the synchronization rule will apply, truncation criteria, and a truncation threshold. The truncation threshold specifies a maximum amount of shared data object instances of the data object schema that may be sent to the client device during a synchronization task. The remote computing system analyzes metadata of a plurality of shared data object instances of the data object schema. Relevant shared data object instances of the plurality of shared data object instances meeting the truncation criteria are determined by the remote computing system. The relevant data object instances are sent from the remote computing system to the client device until the truncation threshold is met.

Truncated synchronization of data object instances

Techniques are described for dynamically synchronizing applications executed on a client device with backend systems. An example method includes identifying a triggering event associated with a request to perform a synchronization of a client application, where the request is associated with a request for a partial synchronization of the client application. A set of information defining a request context associated with the request is obtained. A set of potential partial synchronization scenarios are identified, where each of the potential partial synchronization scenarios associated with a predefined synchronization context. The request context is compared to the predefined synchronization contexts of the set of potential partial synchronization scenarios to identify a particular partial synchronization scenario corresponding to the request context. In response to identifying the particular partial synchronization scenario corresponding to the request context, a set of synchronization operations defined in the identified partial synchronization scenario are performed.

Flexible configuration of offline synchronization scope

Disclosed herein are system, method, and computer program product embodiments for the detection and resolution of conflicts in data synchronization. An embodiment operates by receiving an upload from a user device of one or more changes to a local copy of a master document. A conflict is identified between the one or more uploaded changes and one or more previous changes to the master document. A super user is notified of the conflict. A resolution of the conflict is received. The resolution to resolve the conflict is applied.

Detection and resolution of conflicts in data synchronization

Disclosed herein are system, method, and computer program product embodiments for the automatic detection, retry, and resolution of errors in data synchronization. An embodiment operates by receiving one or more changes to a local copy of a master document. An error is detected during a synchronization of the one or more changes with the master document. A count is incremented and the synchronization is retried until either the synchronization completes or a threshold has been reached.

Automatic detection, retry, and resolution of errors in data synchronization

A method includes initiating, at backend server, a process for synchronization of a data record stored locally on a client computing device with a corresponding data record stored in a backend database. The synchronization process includes comparing the hash value of the data record stored locally on the client computing device and the hash value of the corresponding data record stored in the backend database, and based on the comparing, sending information about the corresponding data record stored in the backend database to the client computing device, if needed for updating the data record stored locally on the client computing device.

Synchronization of offline data

Approaches are presented for temporary highlighting of selected fields of a document. For example, a user can select which fields of a document or class of documents he wishes to have highlighted. The user can also select (a) when he wishes the selected fields to be highlighted, for example, if a field exceeds a threshold and/or (b) how he wishes the selected fields to be highlighted, e.g., overlay the field with a contrasting color. When the user performs a specified action, for example, opens a document, the selected field is selectively highlighted according to the rules for when and how to highlight the selected field. This can help a user quickly recognize important fields in the context of the document.

Temporary highlighting of selected fields

Growing community of inventors

Heidelberg, Germany

Gerd Ritter