Sap Se

Michael Hettich

Andre Klahre

Nitish Kumar

Alexander Koenig

Christine Schaefer

Systems and methods include reception of a first object instance of a first object type from a second system and, in response to receipt of the first object instance, determination of a plurality of run types associated with the first object type, the plurality of run types including a first validation run type, a first migration run type and a first execution run type, execution of the respective plurality of tasks of the first validation run type, execution, if no errors occurred during execution of the first validation run type, of the respective plurality of tasks of the first migration run type, and execution of the respective plurality of tasks of the first execution run type to integrate the first object instance of the first object type into one or more object instances of one or more object types of the system.

System integration using run types

In an example embodiment, asynchronous message processing is performed in a PLM system integration (PLMSI), at least for large message payloads. A processing decision is made as to whether to process a payload synchronously versus asynchronously. In the case of asynchronous processing, this processing can be started in a separate thread from the synchronous communication connection used to transmit the message and payload. The synchronous communication connection (which may be implemented in, for example, Hypertext Transfer Protocol (HTTP)) can be closed after the message was successfully received to prevent connection timeouts.

Asynchronous processing of product lifecycle management (PLM) integration messages

In some implementations, there is provided a computer-implemented method including initiating an upgrade of a service; performing the upgrade of the service by at least checking a system table including an indication of whether the upgrade of the service causes at least one data to be incompatible with the service after the upgrade is completed; in response to the indication indicating the upgrade of the service causes the at least one data to be incompatible, the method further comprises: continuing with the upgrade of the service, without converting the at least one data; detecting a first usage of the service; and in response to the detecting of the first usage, converting the at least one data that is incompatible with the service. Related systems, methods, and articles of manufacture are also disclosed.

Product lifecycle management of data migration during a system update

Systems and methods include reception of an indication of a first event associated with a first object instance. In response to the indication of the first event, a first process chain comprising a first process associated with an object instance of a first meta domain model object type, a second process associated with an object instance of a second meta domain model object type, and a first process step adapter to map a response to a request are determined, the first process is executed based on a request associated with an object instance of the first meta domain model object type to generate a first response associated with an object instance of the first meta domain model object type, the first process step adapter is executed to map the first response associated with an object instance of the first meta domain model object type to a first request associated with an object instance of the second meta domain model object type, and the second process is executed based on the first request associated with an object instance of the second meta domain model object type to generate a second response associated with an object instance of the second meta domain model object type.

Process sequencing using meta domain model

In a scenario involving a primary and secondary server, resource requests can be managed to avoid sending multiple requests to the secondary server. In particular, requests for data object attributes can be queued when another request has already been made. Hashkey and locking mechanisms can be used to support scenarios involving multiple users and multiple data object instances. Performance of the overall system landscape can thus be improved by effectively consolidating resource requests.

Growing community of inventors

Heidelberg, Germany

Michael Hettich