Sap Ag

Sap Se

Toralf Grossmann

Gerd Ritter

Michael Seubert

Thilo Kraehmer

Matthias Schmitt

Andreas F Morsch

Andreas Neumann

Daniel Buchmann

Gunther Stuhec

Renzo Colle

Stephan Hetzer

Paola Sala

Werner Gnan

Joachim Kenntner

Gregor Rieken

Johann Kemmer

Markus A Peter

Andreas Bold

Thomas Nitschke

Georg Podhajsky

Tao Yu

Markus Biehler

Wolfgang Nieswand

Andreas Brossler

Antonia Gross

Andre Wagner

Stefan Elfner

Ralf Sievers

Andreas Bettin

Rudolf Winkel

Christoph Lehner

Thomas Maag

Otto Makris

Volker Jaeck

Michael Zoeller

Jochen A Rasch

Axel Kuehl

Karsten Koetter

Corinne Kuster

Uwe Pyka

Ruediger Radcke

Daniela Schapler

Andreas Schneider

Frank Thome

Dagmar Schultze

Timo Wolf

Gerhard Gschwender

Joerg Hendricks

Wolf Hengevoss

Christine Hofmann

Bernhard Kelnberger

Dominic Poetschke

Jens Zachmann

Theo Zimmerman

Gabriel Alvarez

Dietmar Nowotny

Daniel Bock

Robert Doerner

Arnulf Schueler

Stefan Adelmann

Stefan Franke

Renato Zadro

Volker Ripp

Adam Kiwon

Werner Liebold

Reiner Seyler

Stefan A Baeuerle

Bare Said

Uwe Schlarb

Horst Schaude

Bernd Schmitt

Michael Neumann

Daniel Figus

Marita Kruempelmann

Michael Meyringer

Dirk Henrich

Michael Hartel

Andreas Huppert

Ingo Bruss

Santhosh N

Erwin Pinter

Joachim Pfeifer

Silke Storch

Michael Bauer

Gunter Schmitt

Robert B Fuhge

Christoph Lange

Frank Reinemuth

Joachim Puteick

Martin Rogge

Hendrik Geipel

Florian Rehfeld

Michael Oemler

Patrick Gross

Ashwin Reddy Yeddula

Frank Kohler

Marc-Oliver Genter

Bernd Otte

Nitesh Pai

Armulf Schueler

The present disclosure involves computer-implemented methods, software, and systems for determining a most suitable address for a master data object instance for a given usage in a business transaction document, master data object, or business process. A computer-implemented method includes determining, using at least one computer, an address determination sequence, applying the address determination sequence to available address instances of a master data object instance, identifying a most suitable address from among the available instances, and retrieving an address value from the identified most suitable address instance.

Determination of a most suitable address for a master data object instance

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

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 an address snapshot and an approval process definition business object.

Consistent interface for address snapshot and approval process definition

The present disclosure involves computer-implemented methods, software, and systems for efficiently handling address data in business transaction documents. A computer-implemented method includes receiving a modification to address data associated with an existing address instance, receiving, using at least one computer, an indication of a modification type, creating a new snapshot instance, associating the modified address data with the new snapshot instance, retrieving a unique reference value for the new address snapshot instance, and associating the unique reference value identifying the new address snapshot instance with the address instance.

Efficient handling of address data in business transaction documents

Methods and systems consistent with the present invention provide a data processing system having a business object model reflecting the data used during a business transaction. Consistent interfaces are generated from the business object model. These interfaces are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.

Consistent set of interfaces derived from a business object model

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having foundation layer functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Foundation layer for services based enterprise software architecture

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 Currency Conversion and Date and Time business objects.

Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems

Growing community of inventors

Nussloch, Germany

Toralf Grossmann