Sap Ag

Sap Se

Tao Yu

Stephan Hetzer

Georg Podhajsky

Thomas Nitschke

Stefan Adelmann

Renzo Colle

Paola Sala

Joachim Kenntner

Wolfgang Nieswand

Volkmar Stegmann

Christoph Lehner

Rainer Heun

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Michael Seubert

Dietmar Nowotny

Werner Gnan

Thilo Kraehmer

Daniel Bock

Gregor Rieken

Markus A Peter

Johann Kemmer

Toralf Grossmann

Andreas Bold

Markus Biehler

Andre Wagner

Andreas Brossler

Antonia Gross

Andrea Sudbrack

Matthias Schmitt

Thomas Maag

Stefan Elfner

Otto Makris

Rudolf Winkel

Ralf Sievers

Andreas F Morsch

Axel Kuehl

Volker Jaeck

Stefan Franke

Michael Zoeller

Thomas Bach

Jochen A Rasch

Frank Thome

Dagmar Schultze

Karsten Koetter

Corinne Kuster

Uwe Pyka

Ruediger Radcke

Daniela Schapler

Andreas Schneider

Uwe Herold

Gabriel Alvarez

Gerhard Gschwender

Joerg Hendricks

Wolf Hengevoss

Christine Hofmann

Bernhard Kelnberger

Dominic Poetschke

Jens Zachmann

Jochen Steinbach

Jochen Hirth

Ingo Pfitzner

Arnulf Schueler

Robert Doerner

Martin Von Der Emde

Steffen Hartig

Andre Wachholz-Prill

Volker Ripp

Renato Zadro

Thomas Konstandin

Balaji Vummiti

Adam Kiwon

Werner Liebold

Yuh-Cherng Wu

Jens Freund

Gunther Liebich

Steffen Tatzel

Andreas Poth

Berthold Wocher

Michael Jung

Thomas Hoffmann

Andreas Huppert

Christopher Ronnewinkel

Klaus Reinelt

Christian Haas

Achim Heger

Thomas Breitling

Andreas Bettin

Irena Kull

Dagmar Opitz

Michael Picht

Hamid Moghaddam

Reiner Bildmayer

Alexander Koegler

Devasena Rajamohan

Dietmar Storz

Alexander Krasinskiy

Nir Pachter

Olivier M Dreidemy

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

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

Consistent interface for email activity business object

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.

Consistent set of interfaces derived from a business object model

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

Wiesloch, Germany

Tao Yu