Sap Se

Sap Ag

Michael Hartel

Daniel Zoch

Frank Brunswig

Adam Polly

Stefan A Baeuerle

Gerd Ritter

Uwe Schlarb

Jens Freund

Michael Seubert

Tim Kornmann

Thomas Schneider

Marcel Hermanns

Otfried Von Geisau

Werner Gnan

Thilo Kraehmer

Daniel Figus

Cristina Buchholz

Martin J Wilmes

Toralf Grossmann

Stefan J Moeller

Jens Weiler

Nadine Sachs

Dirk A Giebel

Christian Fuhlbruegge

Tilmann David Kopp

Benjamin Ringl

Thomas Friedrich

Ralph Rillig

Martin Schmidt

Sergio Rozenszajn

Frank O Schulz

Doris Karbach

Sabine Worbs

Sabine Seelenmeyer

Thomas Gros-Bölting

A service request to execute an operation on a business object is received. Thereafter, a metadata repository is polled to obtain a modeled association corresponding to the service request. The modeled association involves at least one node of the business object. The at least one node of the business object is then called using the modeled association to respond to the service request. Related apparatus, systems, techniques and articles are also described.

Modeled associations for business object data structures

A service request from a user is received to execute an operation on an instance of a business object. Thereafter, an access control check is performed to confirm whether the user is allowed to execute the requested operation on a type of business object corresponding to the business object specified and based on an access group associated with the user. Subsequently, the user is either provided with access to the instance of the business object to execute the operation if the access control check confirms that the user is allowed to execute the operation on the instance of the business object, or prevented from accessing the instance of the business object to execute the operation on the instance of the business object. Related apparatus, systems, techniques and articles are also described. Related apparatus, systems, techniques and articles are also described.

Role based access management for business object data structures

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

In accordance with aspects of the disclosure, a system and methods are provided for managing business objects in memory. The system and methods may be provided for defining a context of one or more input parameters of data used to determine one or more properties of one or more business objects, defining one or more rules associated with the one or more properties of each business object, and generating a metadata model for each business object based on the context of the one or more input parameters of each business object and the one or more rules associated with the one or more properties of each business object.

Managing business objects

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a goods tag, a production bill of material hierarchy, and/or a release order template business object.

Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems

A computer-implemented system may include one or more storage devices storing first metadata defining an instance of a first metaobject, second metadata defining an instance of a solution supplement metaobject, wherein the second metadata comprises annotations to the first metadata, and wherein the first metaobject and the solution supplement metaobject are instances of a meta-metaobject. Also stored is executable program code of a service to determine merged metadata based on the first metadata and the annotations to the first metadata. A processor is included to execute the executable program code.

Solution-specific business object view

The present disclosure relates to methods, systems, and software for processing or otherwise managing scrap information in a business application. For example, the software can instantiate a planning business object using production model data for production activities. The business object data and scrap information may be used to calculate requirements for a production planning model. The calculations may include adding an activity yield to activity scrap and fixed resource scrap to generate a component quantity. The component quantity can be multiplied by a component scrap ratio to generate additional component requirements. The component quantity may be added to the additional component requirements to determine a total quantity.

Logically centralized scrap management using planning operations

Growing community of inventors

Heidelberg, Germany

Michael Hartel