Sap Ag

Christoph Engler

Ingo Pfitzner

Andrea Sudbrack

Andre Wachholz-Prill

Martina Lahr

Georg Podhajsky

Thomas Nitschke

Tao Yu

Stefan Adelmann

Volkmar Stegmann

Rainer Heun

Thomas Bach

Peer Marschall

Cordula Ude

Katja Kasteleiner

Helge Schulte

Wilfried Merkel

Yuh-Cherng Wu

Jens Freund

Jochen Steinbach

Stephan Hetzer

Paola Sala

Gunther Liebich

Dietmar Nowotny

Steffen Tatzel

Jochen Hirth

Daniel Bock

Joachim Kenntner

Michael Jung

Andreas Poth

Berthold Wocher

Christopher Ronnewinkel

Wolfgang Nieswand

Christian Haas

Martin Von Der Emde

Achim Heger

Christoph Lehner

Steffen Hartig

Hamid Moghaddam

Stefan Franke

Wolfgang Gentes

Reiner Bildmayer

Michael Picht

Dagmar Opitz

Alexander Koegler

Devasena Rajamohan

Dietmar Storz

Olivier M Dreidemy

Uwe Herold

Holger Herrmann

Theo Zimmermann

Joachim Barnbeck

Jochen Wickel

Karina Herrmann

Ralf Reinke

Wilhelm Zwerger

Boris Krems

Uwe Mayer

Michael Lesk

Alexandra Mark

Martina Keller

Priya Mohana

Shadab Shafiq

Naga Chandra Sekhar Hota

Joerg Walzenbach

Tariq Khasawneh

Naci Kalyoncu

Christian Ihrig

Gerhard Maier

Imme Henningsen

Martin Wunsch

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 ad-hoc goods movement. 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, for example, a lead processing process component that handles the potential interests of a business partner and the interactions with the business partner over a certain timeframe; an opportunity processing process component that handles the development, processing, and monitoring of opportunities; a customer quote processing process component that handles the processing of quotes to customers offering the delivery of goods according to specific terms; and a sales order processing process component that handles the processing of customers' requests to seller for delivery of goods, on a specific date, for a specific quantity, and for a specific price.

Architectural design for opportunity management application software

Growing community of inventors

Walldorf, Germany

Christoph Engler