Sap Ag

Sap Se

Bernhard Thimmel

Uwe Schlarb

Stefan A Baeuerle

Frank Michael Kraft

Wasim Sadiq

Matthias Lehr

Guenter Pecht-Seibert

Patrick Josef Bardroff

Klaus Meyer

Gregor Schilberth

Karsten Fanghänel

Karsten Fanghaenel

Volker Driesen

Juergen Specht

Jens Lemcke

Olaf Meincke

Rene Dehn

Daniel Figus

Daniel Niehoff

Daniel Wachs

Andreas Friesen

Robert Getzner

Piergiorgio Bertoli

Friedhelm Krebs

Marco Pistore

Klaus Rauer

Frank Brunswig

Udo Peter Klein

Bare Said

Ioannis Grammatikakis

Frank Jentsch

Markus Viol

Gregor Karl Frey

Qian Liu

Daniel Zoch

Jan Teichmann

Martin Scholz

Otfried Von Geisau

Ralf Dentzer

Adam Polly

Georg Wilhelm

Daniel Goldmann

Anne Jacobi

Andreas Bold

Steffen Riemann

Olaf Duevel

Dirk Richtsteiger

Steffen Witt

Otfried Geisau

Jacques Duparc

Bertram Vielsack

Johannes Haselberger

Heike Klews

Tobias Poeppke

Johannes Fenzl

Matthias Lebr

Jurgen Specht

A method may include generating a first user interface for providing, to a client, a first selection of inputs for attributes of a rule scenario for defining a rule. The rule may be applied to modify a data processing functionality of the application. Parameters of the rule may be determined based on the rule scenario and a first input from the first selection of inputs being selected via the first user interface. The parameters of the rule may correspond to data objects affected by the application of the rule. A second user interface for providing, to the client, a second selection of inputs for defining a condition of the rule may be generated. The condition of the rule may evaluate the parameters of the rule. The rule may be generated based on a second input from the second selection of inputs being selected via the second user interface.

Rule scenario framework for defining rules for operating on data objects

In one aspect, there is provided a method. The method may include performing, by a sequencer, one or more validations of a plurality of extensions to a core service of a business system; controlling, by the sequencer, execution of a sequence including the plurality of extensions and the core service to enable an action to be performed at the business system; and performing, by the sequencer, one or more post-processing checks of the plurality of extensions. Related systems, methods, and articles of manufacture are also disclosed.

Sequencing of business object logic extensions to ensure data consistency across layers

According to some embodiments, a business service provider may define a stable user interface anchor entity associated with a business object data structure. A reference field may be associated with the stable user interface anchor, the reference field representing a path to a persistent node of the business object data structure. An end user adaptation to a user interface may then be applied in connection with the business object data structure, the adaptation referencing the stable user interface anchor entity.

Stable anchors in user interface to support life cycle extensions

According to some embodiments, information about a delta change package may be received. The delta change package may be, for example, associated with a customer extension project to be applied to content from a business service provider. A description tag for the delta change package may be received from a user, and the delta change package may be associated with the description tag in a repository of the business service provider.

Managing extension projects with repository based tagging

Methods, systems, and computer-readable storage media for evaluating a validity of an extended status and action management (SAM) schema. In some implementations, actions include receiving the extended SAM schema, the extended SAM schema being stored as a computer-readable document in memory and being an extension of a core SAM schema, providing one or more goals, each goal representing an intention of the core SAM schema, the one or more goals being provided in a computer-readable document stored in memory and comprising one or more primary goals that each express an intention of a process underlying the core SAM schema, and processing the one or more goals using a computer-executable model checking tool for evaluating the validity of the extended SAM schema.

Checking compatibility of extended and core SAM schemas based on complex goals

Methods, systems, and computer-readable storage media for evaluating a validity of a status and action management (SAM) schema. In some implementations, actions include receiving the SAM schema, the SAM schema being stored as a computer-readable document in memory, providing one or more goals, each goal representing an intention of the SAM schema, the one or more goals being provided in a computer-readable document stored in memory and including one or more primary goals and one or more recovery goals that each express an intention of a process underlying the SAM schema, and processing the one or more goals using a computer-executable model checking tool for evaluating the validity of the SAM schema.

Verification of status schemas based on business goal definitions

Transporting of flexibility changes of customer content between tenants in a multi-tenant computing system can be performed by exporting customer content from a first tenant of the multi-tenant computing system, transporting the customer content exported from the first tenant to a second tenant of the multi-tenant computing system, importing the customer content into a staging area in the second tenant to enable a user associated with second tenant to access the customer content via the staging area based on a content extraction trigger, and activating selected customer content from the staging area in a productive component of the second tenant. The content extraction trigger can characterize an extraction of at least some of the customer content from the staging area. Related methods, systems, and articles of manufacture are also disclosed.

Transport of customer flexibility changes in a multi-tenant environment

A computer system includes instructions recorded on a computer-readable storage medium and executable by at least one processor. The computer system includes a process component of a first deployment unit and a component module. The process component has a handling module and an object module. The handling module is operatively coupled to the object module. The handling module is operatively coupled to the component module. The handling module is configured to receive a message from a second deployment unit.

Systems and methods for sending and receiving communications

Methods and apparatus, including computer program products, are provided for providing value help. In one aspect, there is provided a computer-implemented method. The method may include receiving, at a code list provider, a request from a user interface for code list value help; determining, based on the request, whether to access at least one of a cache and a secondary storage; accessing, by the code list provider, a cache including at least a first code list, the cache implemented in memory, when the determination results in access to the cache; accessing a secondary storage including at least a second code list, when the determination results in access to the secondary storage; and sending, by the code list provider, at least one of the first code list and the second code list to a user interface to enable the user interface to provide code list value help. Related apparatus, systems, methods, and articles are also described.

Practical code list cache for value help

A system and method for creating extension fields for business objects are described. In various embodiments, a system includes modules to display business processes and business objects thereof in graphical user interface screens. In various embodiments, the system propagates created extension fields to other business objects via metadata derived from selections in the graphical user interface. In various embodiments, a method for propagating extension fields from one business object to another business object via a data flow between the two business objects is presented. In various embodiments, the method receives instructions from a graphical user interface for the propagation of an extension field and sends instructions to a backend module to propagate the extension field from the source business object to the other business object.

Propagating business object extension fields from source to target

A computer implemented method for providing code list extensibility includes providing a first code data type representation. The first code data type representation corresponding to a first code data type and having a first code value representation for at least one code value. The at least one code value associated with a corresponding code value issuing entity. The method may also include providing a second code data type representation. The second code data type representation corresponding to the first code data type and having a second code value representation for the at least one code value. The second code value representation including a unique identifier associated with the code value issuing entity. The method also may include mapping the first code data type representation and the second code data type representation based at least in part on the unique identifier associated with the code value issuing entity.

Providing code list extensibility

A system may include presentation, to a user, of a consuming business entity including a reference field of a business object, reception of an instruction from the user to add an extension field to the consuming business entity based on the reference field of the business object, determination of a second consuming business entity including the reference field of the business object, and presentation of the second consuming business entity to the user.

Facilitation of extension field usage based on reference field usage

A design-time status schema model is defined at design-time and includes a core status schema group and an. a status schema model. The status schema model includes a core status schema group and an extended status schema group. The status schema model also includes a precondition included in one of the status schema groups. The precondition identifies how a status affects whether an action included in the other of the status schema groups is to be allowed to be performed at runtime by a data object node instance having the status. Based on a status schema instance, the status of a data object node instance is monitored to determine whether the action is allowed to be performed by the data object node instance. In response to a determination that the action is allowed, enabling the action to be executed.

Extending status models in a computer system

A system may include acquisition of metadata defining a first object model including extensible entities, the first object model comprising an instance of a metaobject, acquisition of metadata defining an extension object model, the extension object model to extend at least one of the extensible entities of the first object model, and merging of the object model and the extension object to create metadata defining an extended object model, the extended object model comprising an instance of the metaobject.

Extensibility of metaobjects

A design-time status schema model describes the progress of a data object through a computing process. The status schema model includes status variables, processing actions and constraints for performing actions. The status schema model also may describe permitted changes to a status variable in response to performing an action. At runtime, the status schema model is used to control processing performed by, or on, an instance of a data object corresponding to the status schema model.

Using status models with state guards in a computer system

Growing community of inventors

Edingen-Neckarhausen, Germany

Bernhard Thimmel