Abstract: Techniques and solutions are described for copying data from a source client to a target client. It may be selected, such as by a user, whether a full copy or a partial copy of a set of source client data should be made. If a partial copy is selected, a set of file types is provided. The file types can be used to define files that should be included in, or excluded from, the copy. A data source of the source client is analyzed to determine data associated with a file type that is to be included in a copy, or is associated with a file type that is not indicated as to be excluded from the copy. The determined data is copied from the source client to the target client.

Abstract: Techniques and solutions are described for copying data from a source client to a target client. It may be selected, such as by a user, whether a full copy or a partial copy of a set of source client data should be made. If a partial copy is selected, a set of file types is provided. The file types can be used to define files that should be included in, or excluded from, the copy. A data source of the source client is analyzed to determine data associated with a file type that is to be included in a copy, or is associated with a file type that is not indicated as to be excluded from the copy. The determined data is copied from the source client to the target client.

Abstract: A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.

Abstract: Methods and system are disclosed that build or generate an enterprise mobile apps. In an aspect, a project package including multiple plugins, common functionalities, some functionalities, graphical user interface elements, etc., may be generated at a mobile application development framework (MADF). Further, the MADF may receive a request for building or generating an enterprise mobile app. The MADF may reuse the components of the project package and integrate with the application functionalities to generate a corresponding enterprise mobile app.

Abstract: A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

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 request for information, a request for information response, a supplier assessment profile, a supplier questionnaire assessment, and/or a supplier transaction assessment business object.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.