Sap Ag

Sap Se

Christiane Kuntz-Mayr

Knut Heusermann

Ingo Bruss

Suresh Babu

Heinz Kagermann

Juan Carlos Martinez

Gerhard Gebhard

Jie Zhao

Ramshankar Venkatasubramanian

Youneng Xiao

Joachim Brechtel

Barbara Wittmann

Steffen Horndacher

Bernd Reimann

An object may be categorized upon distribution of the object from a sender system to a recipient system. The object may be assigned to at least one recipient category in a recipient category hierarchy according to a first predefined mapping from a sender category hierarchy to the recipient category hierarchy. The object is initially assigned to a sender category in the sender category hierarchy. There is applied to the object a second predefined mapping from the recipient category hierarchy to the sender category hierarchy. It is determined whether the first and second predefined mappings converge. If the first and second predefined mappings do not converge, there may be executed a rule-based reassignment algorithm to make the first and second predefined mappings converge.

Categorizing an object

Systems, methods and computer readable media are provided for integrating carrier services. In one implementation, carrier services are integrated into an Enterprise Resource Planning (ERP) system utilizing an integration platform. The integration platform may include a first, second, and third components. The first, second, and third components may interact to utilize within the integration platform services offered by ERP vendors and carriers by discovering, setting up, testing, running and updating these services. As result, typical business scenarios, such as a order-to-cash process, may be enhanced.

Methods, systems and computer program products for integrating carrier services into an enterprise

A tool and graphical user interface (GUI) may be provided for a customer relationship management (CRM) system that enables a user to create, maintain, display and use individual object (iObject) data that relates to a unique asset in a family of assets. A tool or GUI for maintaining information that relates to individual objects may be referred to herein as an 'individual object workbench' (workbench). In general, a workbench may include a selection area for selecting an individual object to be defined, and a definition area in which a user may define information to be associated with the selected individual object. Each individual object may be associated with a unique identifier (e.g., a particular car is associated with a vehicle identification number) as a consistent identifier of an individual asset throughout that asset's lifecycle, which may span multiple owners, for example.

Maintaining individual object data

Methods and apparatuses for interfacing an enterprise customer with a supplier are described herein. In one embodiment, in response to a request received from an enterprise customer via a first interface (e.g., a common or universal interface) of a Web service over the Internet for a service provided by a supplier, processing logic is configured to map the request from a first format compatible with the first interface to a second format compatible with a second interface coupling with a backend system of the supplier. Processing logic invokes a method of the backend system of the supplier via the second interface (e.g., supplier specific interface) to provide the requested service to the enterprise customer using information of the mapped request. The first interface is compatible with the requesting customer and the second interface is a specific interface to the backend system of the supplier. Functionality of mapping and the second interface are maintained by the supplier. Other methods and apparatuses are also described.

Interfaces between enterprise customers and suppliers

Data administration may be managed by receiving in a computer system a first input identifying a data object to be assigned to a control object in the computer system. A second input for the control object is received in the computer system. The second input specifies a relationship between 1) model-level changes to the data object, and 2) instance-level changes to the data object. After the first and second inputs are received, the control object is sent to another computer system. The control object may be accessed to determine whether a system is authorized to make an object change. This access can be by the system about to make the change, or by a system that receives the object change from another system.

Managing data administration

Techniques are provided for individual data objects in an enterprise computing system, where the individual data objects represent unique assets of a family of assets. The individual data objects are used in addition to business partner master data, and also in some cases in addition to generic product master data. The individual data objects are configurable such that attributes for an individual data object change over the lifetime of the unique asset to which the individual data object pertains. Techniques for modeling the lifecycle of an individual object family are described. Techniques also are provided for an integration framework that integrates a software application with an individual object that is used or altered by the software application.

Growing community of inventors

Limburgerhof, Germany

Christiane Kuntz-Mayr