Sap Ag

Uwe Mayer

Jens Freund

Stephan Hetzer

Jochen Hirth

Daniel Bock

Jochen Wickel

Peter Latocha

Jochen Steinbach

Paola Sala

Gerd Moosmann

Stefan Kaetker

Gunther Liebich

Dietmar Nowotny

Joachim Kenntner

Ingo Pfitzner

Berthold Wocher

Andreas Poth

Tao Yu

Thomas Nitschke

Georg Podhajsky

Andrea Sudbrack

Volkmar Stegmann

Stefan Adelmann

Martin Von Der Emde

Achim Heger

Christian Haas

Michael Picht

Hamid Moghaddam

Reiner Bildmayer

Andre Wachholz-Prill

Thomas Bach

Alexander Koegler

Rainer Heun

Steffen Hartig

Olivier M Dreidemy

Sebastian Pulkowski

Matthias Schwarz

Holger Herrmann

Joachim Barnbeck

Attila Orban

Peer Marschall

Karina Herrmann

Martina Lahr

Christoph Engler

Cordula Ude

Katja Kasteleiner

Peter Meuer

Sabine Montnacher

Wilfried Merkel

Ralf Reinke

Wilhelm Zwerger

Christian Ihrig

Gerhard Maier

Imme Henningsen

Martin Wunsch

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service request and order management. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include an Outbound Delivery process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Service Request Processing process component, a Customer Quote Processing process component, a Service Order Processing process component, a Service Contract process component, and a Service Confirmation Processing process component.

Architectural design for service request and order management application software

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

Growing community of inventors

Erligheim, Germany

Uwe Mayer