Sap Ag

Stefan Adelmann

Georg Podhajsky

Tao Yu

Thomas Nitschke

Stephan Hetzer

Stefan Franke

Renzo Colle

Jochen Steinbach

Michael Seubert

Paola Sala

Dietmar Nowotny

Werner Gnan

Thilo Kraehmer

Joachim Kenntner

Daniel Bock

Robert Doerner

Andrea Sudbrack

Andre Wagner

Andreas Brossler

Wolfgang Nieswand

Christoph Lehner

Rudolf Winkel

Thomas Bach

Rainer Heun

Axel Kuehl

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Gunther Liebich

Jochen Hirth

Johann Kemmer

Markus A Peter

Gregor Rieken

Toralf Grossmann

Ingo Pfitzner

Andreas Poth

Andreas Bold

Thomas Hoffmann

Matthias Schmitt

Markus Biehler

Klaus Reinelt

Antonia Gross

Volkmar Stegmann

Otto Makris

Andreas F Morsch

Ralf Sievers

Martin Von Der Emde

Stefan Elfner

Thomas Maag

Michael Zoeller

Jochen A Rasch

Steffen Hartig

Andre Wachholz-Prill

Volker Jaeck

Uwe Pyka

Andreas Schneider

Adam Kiwon

Renato Zadro

Frank Thome

Dagmar Schultze

Daniela Schapler

Ruediger Radcke

Karsten Koetter

Volker Ripp

Corinne Kuster

Peer Marschall

Gabriel Alvarez

Stefan A Baeuerle

Yuh-Cherng Wu

Jens Freund

Guenter Pecht-Seibert

Steffen Tatzel

Georg Dopf

Berthold Wocher

Michael Jung

Robert Getzner

Arnulf Schueler

Christopher Ronnewinkel

Andreas Huppert

Thomas Breitling

Christian Haas

Andreas Bettin

Achim Heger

Irena Kull

Dagmar Opitz

Alexander Koegler

Devasena Rajamohan

Benjamin Klehr

Michael Picht

Hamid Moghaddam

Reiner Bildmayer

Robert Reiner

Dietmar Storz

Danny Pannicke

Giovanni Deledda

Alexander Krasinskiy

Nir Pachter

Olivier M Dreidemy

Holger Herrmann

Uwe Herold

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.

Consistent set of interfaces derived from a business object model

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.

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having customer relationship management 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.

Providing customer relationship management application as enterprise services

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing plan-driven procurement. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include an Inbound Delivery Processing process component, a Site Logistics Processing process component, an Inventory Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Purchasing Contract process component, a Supplier Invoice Processing process component, a Demand Forecast Processing process component, a Supply and Demand Matching process component, an External Procurement Trigger and Response process component, and a Logistics Execution Control process component.

Architectural design for plan-driven procurement application software

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing sell from stock software useful to process quotations, capture orders, process delivery and invoice. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include an Accounting process component; a Financial Accounting Master Data Management process component; an Outbound Delivery Processing process component; a Site Logistics Processing process component; an Inventory Processing process component; a Customer Requirement Processing process component; a Supply and Demand Matching process component; a Logistics Execution Control process component; a Due Item Processing process component; a Balance of Foreign Payment Management process component; a Payment Processing process component; a Customer Invoice Processing process component; a Customer Quote Processing process component; and a Sales Order Processing process component.

Architectural design for sell from stock application software

The addition of process agents into an application system allows a much simpler integration between business objects by placing the integrating components into separate, independently updateable process agents. Process agents observe business objects with which they are associated and communicate with other process agents. Alternatively, process agents may be notified by business objects to perform communication activities. Thus, a business object may be designed, operated, or updated with complete independence from the surrounding structure of the application system. The logic, application code, and integration components that require specific changes or design in response to changes in the overall application system or real world conditions are placed in the process agent objects, allowing them to be updated, modified or integrated freely without any changes to business objects within the system.

Process agents for process integration

Growing community of inventors

Mannheim, Germany

Stefan Adelmann