Sap Se

Sap Ag

Andre Klahre

Wolfgang E Walter

Michael Hettich

Thorsten Bender

Nitish Kumar

Melanie Kientz

Adelheid Fischer

Barbara Freund

Nicolai Jordt

Claus Kollmannsperger

Alexander Koenig

Christine Schaefer

Maren Mester

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.

Performance-enhancing cross-system request handling via shared memory cache

Configuration setting management is facilitated by setting data in a multisystem environment. A system having a configuration setting, in a multisystem environment having a test system and a production system, may identify the type for the setting based on a type identifier. The system may maintain the setting based on the type. Maintaining the setting may include, for a first type, making a primary location for the setting the production system, where the setting is initialized and editable in the production system. Maintaining the setting may include, for a second type, making the setting independent between the test system and the production system, where the setting is not transferred between the two systems and is editable at each system. Maintaining the setting may include, for a third type, making a primary location for the setting the test system, where the setting is initialized and editable in the test system.

Configuration management in a multisystem environment

A system, a method, and a computer program product for deriving target attribute values based on source attributes defined by a hierarchical data mode are disclosed. An attribute value derivation function to change a target attribute data value corresponding to a source attribute stored in a hierarchical data model and an instruction corresponding to the source attribute are provided. The attribute value derivation function is defined by an attribute value derivation header containing metadata describing hierarchical data model and an attribute value derivation instruction for deriving the target attribute based on the source attribute. Using the attribute value derivation function, a target attribute data value is derived. A user interface is generated to display the derived target attribute data value.

Attribute value derivation

A method, a system, and a computer program product for performing maintenance actions and user-specific settings of the attribute value derivation instructions set user interface are disclosed. A maintenance function is provided for changing a target attribute data value corresponding to a source attribute stored in a hierarchical data model. An instruction corresponding to the source attribute is also provided. Using the maintenance function, the target attribute data value is changed. Based on at least one user setting, a user interface for displaying the hierarchical data model and the changed target attribute data value is generated.

Maintenance actions and user-specific settings of the attribute value derivation instruction set user interface

A system, a method, and a computer program product for monitoring of events and key figures are disclosed. An event in a plurality of events associated with a business process is identified. The identified event is monitored. A business value of the identified event is determined in real time. Based on the determined real-time business value, at least one key figure associated with the monitored event is retrieved and displayed in a user interface.

Monitoring of events and key figures

A framework can provide function execution services. The framework can comprise a controller layer, a wrapper layer, and a function layer. The controller layer can be configured to process function definition requests and function execution requests, and return results. The wrapper layer can be configured to query the function layer to determine function definitions and pass function execution requests and results with the function layer. The function layer can comprise functions and/or features. A function execution request can be performed by determining a step execution sequence, executing the step execution sequence, and returning results of the execution of the step execution sequence. The step execution sequence can comprise setup steps, execute steps, and/or finalize steps.

Function execution framework wrapper layer

A framework can provide describe definitions for use cases. The framework can comprise a controller layer, a wrapper layer, and a function layer. The controller layer can be configured to receive describe requests and return describe results. The wrapper layer can be configured to call describe methods of functions that implement the use cases. The function layer can comprise functions that implement the use cases. A function execution request can be received, a customized function execution sequence can be determined for the function execution request, the customized function execution sequence can be executed, and results of the execution can be returned. The customized function execution sequence can comprise an indication of execution order for a plurality of functions.

Growing community of inventors

Schwetzingen, Germany

Andre Klahre