Sap Ag

Sap Se

Volkmar Stegmann

Tao Yu

Gerd Ritter

Ingo Pfitzner

Rainer Heun

Uwe Herold

Georg Podhajsky

Thomas Nitschke

Stefan Adelmann

Andrea Sudbrack

Andre Wachholz-Prill

Thomas Bach

Thomas Konstandin

Balaji Vummiti

Martina Lahr

Christoph Engler

Cordula Ude

Peer Marschall

Katja Kasteleiner

Olaf Schulte

Wilfried Merkel

Adam Stollarski

Yuh-Cherng Wu

Jens Freund

Jochen Steinbach

Paola Sala

Stephan Hetzer

Gunther Liebich

Dietmar Nowotny

Steffen Tatzel

Jochen Hirth

Daniel Bock

Joachim Kenntner

Andreas Poth

Berthold Wocher

Michael Jung

Wolfgang Nieswand

Christopher Ronnewinkel

Christoph Lehner

Martin Von Der Emde

Christian Haas

Achim Heger

Michael Picht

Steffen Hartig

Dagmar Opitz

Hamid Moghaddam

Reiner Bildmayer

Stefan Franke

Devasena Rajamohan

Alexander Koegler

Holger Herrmann

Olivier M Dreidemy

Dietmar Storz

Theo Zimmermann

Joachim Barnbeck

Jochen Wickel

Karina Herrmann

Ralf Reinke

Wilhelm Zwerger

Uwe Mayer

Michael Lesk

Alexandra Mark

Boris Krems

Helge Schulte

Martina Keller

Christian Ihrig

Gerhard Maier

Imme Henningsen

Martin Wunsch

Joerg Walzenbach

Tariq Khasawneh

Naci Kalyoncu

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

A system may include reception of an instruction to create a next meeting based on a source meeting, the source meeting associated with a first plurality of meeting particulars, and automatically creation, in response to the instruction, of the next meeting in association with a second plurality of meeting particulars, wherein at least one of the second plurality of meeting particulars provides an indication of the source meeting.

Systems and methods to create follow-up meetings

Systems and methods are described that permit a user to configure an identification strategy at run time to facilitate user input of data. The identification strategy may include a parsing grammar and a search algorithm. The parsing grammar may be used to parse user input, and the search algorithm may be used to search a database for the user input. A configuring user may configure the parsing grammar at run time to accept data in a customized form to suit the user's input style. The search algorithm may be configured accordingly as well.

Configurable search strategy

In a computing system, an operation is performed on an instance of a data object. One of several persistence models that are available for the data object is identified for the instance using the performed operation, where each of the several persistence models defines how the data object is to be persisted in a database. The instance is stored in the database according to the identified persistence model. The persistence model may be identified at run time in a manner transparent to a user. A first persistence model may be identified for a first instance of the data object and a second persistence model, different from the first persistence model, may be identified for a second instance of the data object. An object instance may later be stored according to another persistence model.

Dynamic assessment and persistence of object instances

Growing community of inventors

Altlussheim, Germany

Volkmar Stegmann