Sap Se

Sap Ag

Daniel Figus

Uwe Schlarb

Daniel Niehoff

Stefan A Baeuerle

Rene Dehn

Georg Wilhelm

Daniel Wachs

Bernhard Thimmel

Matthias Lehr

Steffen Witt

Knut Heusermann

Sebastian Droll

Toralf Grossmann

Michael Hartel

Karsten Fanghaenel

Hans-Juergen Hennrich

Ralf Schroth

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

Software solutions in a business software framework can expose their data via web services, which can readily provide access to all non-customized fields of objects included as part of the default installation of the software solution. However, customer-added extensions, such as for example custom fields and the like, added to customize the software solution for a specific business or business use can be difficult to add to web services by a typical business user who lacks technical abilities. Described herein are approaches to enabling addition of custom fields to web services via an intuitive interface that does not require technical understanding of the software solution, the business software framework, web services, etc.

Self service propagation of custom extension fields into web services

A multi-tenant environment can support field extensibility via extension tables. An in-memory, columnar database can store a core table being extended as well as the corresponding extension table. Transactional and analytical processing can be performed on the extension fields. A business-objects-based system can take advantage of the technologies to provide greater flexibility, security, and performance improvements.

Field extensibility in a multi-tenant environment with columnar database support

An extension node can be defined in a second layer of a software architecture for a first business object existing in a first layer and originally having an association with a second business object that is also in the first layer. The extension node can be defined to have an association with the second business object existing in a second layer of the software architecture. The association of the second business object can be altered from the first business object to the extension node so that at run time, metadata defining one or more nodes of the first business object and the extension node can be read from a metadata repository and a run time version of the first business object can be constructed at run time in a run time business object load based on the metadata.

Layering of business object models via extension techniques

An extension naming approach for avoiding naming collisions in de-normalized view on a business object can include accessing a reference field bundle, which includes reference field(s) corresponding to a core business object defined in a core software platform of a software architecture, from a metadata repository. A user can define an extension to the business object based on the core business object, for example via a development environment. The reference field(s) can include a defined path from a node in a peripheral object to a corresponding node in the core business object. A unique and reproducible name for the extension field can be generated based on the reference field, and the extension field with the unique and reproducible name can be added to the business object and to a data model of the peripheral object.

Naming algorithm for extension fields in de-normalized views

Various embodiments of systems and methods to provide multi-client generic persistence for extension nodes are described herein. A standard field value and an extension field value specific to a client of a business data object are separated. Further, an extension node instance key associated with the extension field value is segregated. Furthermore, the standard field value and associated standard node instance key are stored in a standard persistence unit, and the extension field value is stored in an extension data persistence unit. Also, the extension node instance key and a relation between the standard node instance key and the extension node instance key are stored in an extension key persistence unit.

Multi-client generic persistence for extension nodes

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 delta handler can allow calculation of difference between an already generated set of backend entities and a set of new entities necessary to support a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture. Improved stability and robustness can be provided via an approach in which a target list of activities relating to creating, changing, or deleting of entities in backend repositories necessary to support the affected primary object is created and a sequence for performance of the activities in the target list is determined in a manner that can allow handling of such activities in a unified manner rather than on a per object type basis. Related methods, systems, articles of manufacture, and the like are described.

Generation framework for mapping of object models in a development environment

Access to a networked application can be provided to multiple users while allowing user-specific extension fields to be created and maintained for exclusive access by the user creating the extension field. A user-customized data object that includes a standard field value of a standard field of a standard data object defined by the networked application and a user-specific extension field value of a user-specific extension field that modifies operation of the networked application for the user and that is not available to other users of the plurality of users can be received from a user for writing to memory. The user-specific extension field value can be separated from the standard field value. The standard field value and the user-specific extension field value can be persisted in a first database table and a second database table, respectively. Related systems, methods, and articles of manufacture are also provided.

Multi-client generic persistence for extension fields

A system and method for creating notes for business object instances are described. In various embodiments, a system includes modules to receive note data and bind notes to business object instances. In various embodiments, the system saves notes to a database via a dedicated database connection in a dedicated transaction. In various embodiments, a user interface is provided for creating and modifying notes on business content. In various embodiments, a method for creating notes in a user interface and attaching the notes to one or more positions in a user interface screen displaying business content in an enterprise information system is presented.

Growing community of inventors

Wallduern, Germany

Daniel Figus