Sap Se

Sap Ag

Karsten K Bohlmann

Stefan Bresch

Volker Wiechers

Christian Stork

Gunther Stuhec

Masoud Aghadavoodi Jolfaei

Edgar Willi Lott

Helmut Prestel

Andreas Blumenthal

Ralf Dentzer

Stefan Kusterer

Welf N Walter

Thilo Boehm

Frank Mock

Frank Radmacher

Tobias Stein

Klaus Nottbohm

Thorsten Marcus Dunz

Christoph H K Wedler

Uwe Schlarb

Rene Dehn

Marcel Hermanns

Georg Wilhelm

Thomas Wieczorek

Rolf Hammer

Gerd G Forstmann

Daniel Wachs

Daniel Niehoff

Kai Baumgarten

Michael Schneider

Christian Fuhlbruegge

Karsten Schaser

Holger Koser

Fabian Fellhauer

Christian Holzer

Steffen Huester

Thomas Henn

Matthias Herchenroether

Sven Kobler-Morris

Thomas Alexander Ritter

Eric Westenberger

The present disclosure involves systems, software, and computer implemented methods for ensuring seamless lifecycle stability for extensions to standard software products. One example method includes determining a requested change to a software feature of a software object. The software feature has been designated as an extensible software feature and is associated with a lifecycle stability contract that identifies aspects of the extensible software feature that are designated to remain stable across different releases of the software object. The lifecycle stability contract is used to perform a compatibility check for the requested change to determine whether the requested change complies with the lifecycle stability contract. The requested change is permitted in response to determining that the requested change complies with the lifecycle stability contract and the requested change is denied in response to determining that the requested change violates the lifecycle stability contract.

Seamless lifecycle stability for extensible software features

A core system including different program components performing distinct tasks in a workflow sequence that are initiated through status field updates of objects in database may be modified to define a new status triggering additional processes in an action management system. Once the additional processes are completed, the status field may be changed to an original status provided by the core system to trigger a second program component in the workflow sequence. The action management system may contain user customized processes that may be modified and changed independent of the functionality provided by the core system.

Extensibility of business process and application logic

A business application backend system, such as an Advanced Business Application Programming backend can receive and respond to representational state transfer (RESTful) service requests via both HTTP and Remote Function Call (RFC) protocols. In particular, the backend system extracts the RESTful service requests and fulfills the extracted requests using a protocol-independent resource controller. Related apparatus, systems, techniques and articles are also described.

Representational state transfer communications via remote function calls

A mesh structure can be a type concept that extends internal tables or other data structures of a business programming languages (e.g., ABAP) by associations, as known from a data object meta-model. A mesh can include a set of operations, such as for example iteration via an iterator object and selection of instances expressed by a path language. A mesh structure can be optimized for read access and traversal, and can provide a working area that is processed with statements in the business programming language to implement one or more core services directly from the mesh data structure. Related methods, computer program products, and systems are described.

Native language support for intra-and interlinked data collections using a mesh framework

In an embodiment, a method of computer program compilation is presented. In this method, a compiler for a first programming language is provided. In one example, the first programming language allows a data assignment to depend on a result of a previous data assignment. Source code including a first portion written in the first programming language and a second portion written in a second programming language is accessed, with the second portion representing a data transformation from a first data structure accessible in the first portion to a second data structure accessible in the first portion. In one example, the second programming language prevents a data assignment that depends on a result of a previous data assignment. The source code is compiled using the compiler to generate executable code to be executed by an engine for the first programming language, which includes an interpretation engine to interpret the second portion.

Embedding of a non-imperative programming language for data transformation operations within an imperative programming language

Methods and systems of monitoring events occurring in a computer system are provided. An event monitoring instruction including a condition is parsed, the event monitoring instruction expressed using syntax defined in source code, the parsing resulting in an event channel to monitor and the condition. Then execution of an application is paused. The event channel is monitored until an event occurs on the event channel. Then an event handler for the event is run in response to the event occurring on the event channel. The condition is evaluated to determine whether the condition is satisfied. Execution of the application is resumed in response to the condition being satisfied.

Programming language conditional event dispatcher

Processing a received message includes receiving a message that includes within the message a plurality of values and a plurality of context values. Each of the values is associated with a respective data element. The method includes identifying a first context value and those first data elements that are relevant to the first context value. The method includes selecting first rules that are specific for the first context value and applying the first rules to the values associated with the first data elements. The process includes identifying a second context value and those second data elements that are relevant to the second context value and omitting first data elements that are relevant to the second context value. The method includes selecting second rules that are specific to the second context value and applying the second rules to values associated with the second data elements.

Processing a received message

Processing a received message includes receiving a message that includes a plurality of values associated with respective data elements that assign an information category to each of the values. The message further includes a plurality of context values belonging to respective context categories. The method includes identifying, in a relevance record and for a first one of the context categories in the message, at least one of the data elements that is relevant for the context value of the first context category. A rule associated with the context value of the first context category is applied to the value of the identified at least one data element. A system includes a message receiving module, a context value module and a processing module.

An application system includes a first process configured to execute an application program, wherein the application program is operable to use a set of data structures. The application system also includes a second process configured to interpret a markup language document. A transformation template is configured to specify a symmetric mapping between the markup language document and the set of data structures. A transformation virtual machine runs in association with the first process and is operable to execute the transformation template. The transformation virtual machine is operable to perform a symmetric transformation between the markup language document and the set of data structures to allow the first process and the second process to exchange information.

Symmetric transformation processing system

Growing community of inventors

Rauenberg, Germany

Karsten K Bohlmann