Sap Ag

Jochen Wickel

Jochen Hirth

Jens Freund

Stephan Hetzer

Daniel Bock

Uwe Mayer

Peter Latocha

Jochen Steinbach

Michael Seubert

Stefan Kaetker

Paola Sala

Gerd Moosmann

Gunther Liebich

Dietmar Nowotny

Werner Gnan

Thilo Kraehmer

Joachim Kenntner

Andreas Poth

Ingo Pfitzner

Berthold Wocher

Orit Harel

Tao Yu

Georg Podhajsky

Thomas Nitschke

Robert Getzner

Volkmar Stegmann

Stefan Adelmann

Andrea Sudbrack

Achim Heger

Christian Haas

Martin Von Der Emde

Rainer Heun

Steffen Hartig

Michael Picht

Hamid Moghaddam

Reiner Bildmayer

Andre Wachholz-Prill

Thomas Bach

Alexander Koegler

Yuval Morad

Olivier M Dreidemy

Sebastian Pulkowski

Thomas Hammer

Matthias Schwarz

Pablo Roisman

Holger Herrmann

Joachim Barnbeck

Attila Orban

Karina Herrmann

Martina Lahr

Christoph Engler

Peer Marschall

Cordula Ude

Katja Kasteleiner

Andre Adam

Waldemar Kramer

Eli Pripaz Cohen

Elad Heart

Peter Meuer

Tanjana Preiser-Funke

Sabine Montnacher

Wilfried Merkel

Ralf Reinke

Wilhelm Zwerger

Monica Reidl

Claudia Diesner

Volker Vogelmann

Hofit Koren

Michele Kemp

Lars Hoenig

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

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 business document message monitoring view, a customs arrangement, and/or a freight list business object.

Managing consistent interfaces for business document message monitoring view, customs arrangement, and freight list business objects across heterogeneous systems

Growing community of inventors

Wiesloch, Germany

Jochen Wickel