Sap Ag

Thomas Nitschke

Georg Podhajsky

Stephan Hetzer

Tao Yu

Stefan Adelmann

Renzo Colle

Michael Seubert

Paola Sala

Werner Gnan

Daniel Bock

Thilo Kraehmer

Joachim Kenntner

Andrea Sudbrack

Andreas Brossler

Wolfgang Nieswand

Andre Wagner

Christoph Lehner

Rudolf Winkel

Thomas Bach

Axel Kuehl

Stefan Franke

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Dietmar Nowotny

Markus A Peter

Johann Kemmer

Gregor Rieken

Toralf Grossmann

Andreas Bold

Robert Doerner

Antonia Gross

Markus Biehler

Matthias Schmitt

Otto Makris

Stefan Elfner

Andreas F Morsch

Thomas Maag

Ralf Sievers

Alexander Koegler

Jochen A Rasch

Rainer Heun

Volker Jaeck

Michael Zoeller

Andreas Schneider

Frank Thome

Dagmar Schultze

Daniela Schapler

Uwe Pyka

Karsten Koetter

Corinne Kuster

Ruediger Radcke

Peer Marschall

Gabriel Alvarez

Gerhard Gschwender

Joerg Hendricks

Wolf Hengevoss

Christine Hofmann

Bernhard Kelnberger

Jochen Steinbach

Gunther Liebich

Jochen Hirth

Andreas Poth

Ingo Pfitzner

Berthold Wocher

Arnulf Schueler

Volkmar Stegmann

Thomas Breitling

Steffen Hartig

Andre Wachholz-Prill

Adam Kiwon

Volker Ripp

Renato Zadro

Holger Herrmann

Yuh-Cherng Wu

Jens Freund

Steffen Tatzel

Georg Dopf

Michael Jung

Thomas Hoffmann

Christopher Ronnewinkel

Klaus Reinelt

Christian Haas

Martin Von Der Emde

Achim Heger

Devasena Rajamohan

Michael Picht

Benjamin Klehr

Hamid Moghaddam

Reiner Bildmayer

Robert Reiner

Dagmar Opitz

Dietmar Storz

Olivier M Dreidemy

Danny Pannicke

Giovanni Deledda

Uwe Herold

Jochen Wickel

Andreas Leukert-Knapp

Martin Gaub

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, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing customer returns handling. 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 Customer Return Processing process component, a Sales Order Processing process component, a Customer Invoice Processing process component, a Due Item Processing process component, a Balance of Foreign Payment Management process component, a Payment Processing process component, a Supply and Demand Matching process component, an Inventory Processing process component, a Site Logistics Processing process component, and an Inbound Delivery Processing process component.

Architectural design for customer returns handling application software

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing selling standardized services. 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 a Customer Quote Processing process component; a Sales Order Processing process component; a Service Confirmation Processing process component; a Financial Accounting Master Data Management processing component; a Customer Invoice Processing process component; an Accounting process component; a Balance of Foreign Payment Management process component; a Due Item Processing process component; and a Payment Processing process component.

Architectural design for selling standardized services application software

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

Growing community of inventors

Nussloch, Germany

Thomas Nitschke