Sap Se

Sap Ag

Tim Kornmann

Gerd Ritter

Rene Gross

Dirk Stumpf

Thomas Biesemann

Pradeep Kumar Singh

Cristina Buchholz

Jens Kisker

Daniel Zoch

Thomas Gauweiler

Steffen Tatzel

Marcel Hermanns

Michael Meyringer

Carsten Brandt

Michael Hartel

Dirk A Giebel

Ralf Helmut Philipp

Thomas Konstandin

Alexander Fuerbach

René Gross

Lambert Boskamp

Tobias Stolzenberger

Dirk Stumpt

A method may include receiving, at a search engine, an indication that a first data object was created. The search engine may fetch metadata associated with the first data object, the metadata including a description of the first data object and a binding expression including relational information between the first data object and at least one other data object. The search engine may add data from the at least one other data object to the first data object. The search engine may store the metadata and the first data object in an index of the search engine, the index associated with the first data object. The search engine may receive a search phrase. The search engine may generate a search result that includes the relational information retrieved from the index. Related systems and articles of manufacture, including computer program products, are also provided.

Metadata based bi-directional data distribution of associated data

Briefly, embodiments of a system, method, and article for receiving data from one or more clients, where the data indicates user interactions with one or more user interfaces (UIs) of an application. The data may be analyzed with machine learning to identify how users of the one or more clients interact with the UIs of the application. One or more parameters may be generated based, at least in part, on the identification of how the users of the one or more clients interact with the UIs of the application. One or more objects of the application may be modified based, at least in part, on the parameters to reduce user interactions with the one or more UIs.

Machine learning process to enhance user experience

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 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

A method includes providing a cloud-side database storing data, an objects model of the data, and a user interface (UI) model of the data. The method further involves providing an instance of an application server coded in JavaScript, for example, in a Node.js cross-platform runtime environment. The instance of the application server coded in JavaScript includes the logic of an application coded to process the data. The application logic is executed (and data processed) on either the client-side or on the cloud-side. The execution of the application logic (and processing of the data) is dynamically switchable between the client-side and the cloud-side.

Computing platform agnostic application server

A system and method for modeling properties of data and events of a business application is presented. The system include a user interface frontend system that displays a user interface, and a user interface backend system that hosts a business application that generates the user interface for display in the user interface frontend system. The system further includes an enterprise service framework comprising one or more data processors that define one or more properties of data and/or events related to the business application, and model each of the one or more properties as a data field of the business application. A dynamic properties calculator includes one or more data processors that access a set of transformation logic representing data transformation rules for each of the data fields of the business application, and apply the transformation rules to the data fields that represent the one or more properties.

Modeling properties of data and events as transformations of document data and system values

A service request from a user is received to execute an operation on an instance of a business object. Thereafter, an access control check is performed to confirm whether the user is allowed to execute the requested operation on a type of business object corresponding to the business object specified and based on an access group associated with the user. Subsequently, the user is either provided with access to the instance of the business object to execute the operation if the access control check confirms that the user is allowed to execute the operation on the instance of the business object, or prevented from accessing the instance of the business object to execute the operation on the instance of the business object. Related apparatus, systems, techniques and articles are also described. Related apparatus, systems, techniques and articles are also described.

Role based access management for business object data structures

A method and system, the method may include determining a user interface to be displayed, the user interface including a user interface data element associated with a service input parameter. Information about the service input parameter may be provided to a field transformation as a transformation input, and a transformation output may be received from the field transformation.

Field transformations for user interface data elements

According to one general aspect, a method of retrieving data entities from a backend data device may include maintaining a data model of data entities employed by a user interface. The data model may include a hierarchical relationship between a leading data entity and at least one child data entity. The method may also include authorizing, with an authorization device, when retrieving the leading data entity. The method may include instructing the authorization device that data retrievals of subsequent data entities are to be authorized based upon the authorization of the leading data entity. The method may also include retrieving at least one child data entity of the leading data entity without providing additional authorization credentials.

User interface model driven data access control

A computer-implemented system may include reception of an instruction to create an association for an element of a UI component model, determination of a first business object model of the association, determination of a second business object model of the association, definition of foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model, reception of an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model, and creation of metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

Virtual business object node associations

A computer-implemented system may include reception of a user interface request corresponding to two or more chained operations associated with one or more service calls to a backend service layer, determination of whether to update a backend buffer after execution of each of the one or more service calls, execution, if it is determined to update the backend buffer after execution of each of the one or more service calls, of each of the one or more service calls, and a read service call after execution of each of the one or more service calls, and execution, if it is determined not to update the backend buffer after execution of each of the one or more service calls, of each of the one or more service calls in sequence, and a bulk read service call only after execution of all of the one or more service calls.

Modeled chaining of service calls

A computer-implemented system may include reception, from a user interface client application, of a user interface request conforming to a user interface component model, translation of the user interface request from the user interface component model to a business object model, execution of interactions associated with the translated request with a backend service layer, the interactions conforming to the business object model, determination of business object node changes and business object property changes conforming to the business object model and corresponding to the interactions, translation of the business object node changes and the business object property changes to user interface data changes and user interface event property changes conforming to the user interface component model, and provision of the user interface data changes and user interface event property changes to the user interface client.

Growing community of inventors

Reilingen, Germany

Tim Kornmann