Sap Ag

Sap Se

Rainer Heun

Tao Yu

Andrea Sudbrack

Thomas Bach

Thomas Nitschke

Volkmar Stegmann

Stefan Adelmann

Steffen Hartig

Katja Kasteleiner

Cordula Ude

Jochen Steinbach

Stephan Hetzer

Jochen Hirth

Ingo Pfitzner

Berthold Wocher

Georg Podhajsky

Thomas Breitling

Martin Von Der Emde

Alexander Koegler

Andre Wachholz-Prill

Uwe Herold

Martina Lahr

Christoph Engler

Peer Marschall

Theo Zimmermann

Wilfried Merkel

Ralf Reinke

Yuh-Cherng Wu

Jens Freund

Renzo Colle

Paola Sala

Gunther Liebich

Dietmar Nowotny

Steffen Tatzel

Joachim Kenntner

Daniel Bock

Andreas Poth

Michael Jung

Thomas Hoffmann

Andreas Huppert

Wolfgang Nieswand

Christopher Ronnewinkel

Klaus Reinelt

Christoph Lehner

Achim Heger

Andreas Bettin

Irena Kull

Christian Haas

Dagmar Opitz

Stefan Franke

Hamid Moghaddam

Devasena Rajamohan

Reiner Bildmayer

Michael Picht

Thomas Konstandin

Holger Herrmann

Balaji Vummiti

Dietmar Storz

Olivier M Dreidemy

Nir Pachter

Alexander Krasinskiy

Joachim Barnbeck

Jochen Wickel

Karina Herrmann

Helge Schulte

Adam Stollarski

Martina Keller

Olaf Schulte

Wilhelm Zwerger

Frank Krueger

Rudolf Gentner

Boris Krems

Uwe Mayer

Michael Lesk

Alexandra Mark

Joerg Walzenbach

Tariq Khasawneh

Naci Kalyoncu

Christian Ihrig

Gerhard Maier

Imme Henningsen

Martin Wunsch

Sandra Boehringer

Daniel Pascariu

Nicola Nola

Uma Kale

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 an appointment activity business object.

Consistent interface for appointment activity business object

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 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

Growing community of inventors

Reilingen, Germany

Rainer Heun