Sap Ag

Sap Se

Ingo Pfitzner

Andrea Sudbrack

Volkmar Stegmann

Andre Wachholz-Prill

Martina Lahr

Christoph Engler

Berthold Wocher

Tao Yu

Thomas Nitschke

Georg Podhajsky

Stefan Adelmann

Thomas Bach

Rainer Heun

Cordula Ude

Katja Kasteleiner

Peer Marschall

Helge Schulte

Wilfried Merkel

Gerd Ritter

Yuh-Cherng Wu

Jens Freund

Jochen Steinbach

Stephan Hetzer

Paola Sala

Gunther Liebich

Steffen Tatzel

Dietmar Nowotny

Jochen Hirth

Daniel Bock

Joachim Kenntner

Markus Wolf

Andreas Poth

Michael Jung

Wolfgang Nieswand

Christopher Ronnewinkel

Achim Heger

Guang Yang

Christoph Lehner

Martin Von Der Emde

Christian Haas

Alexander Koegler

Olga Kreindlina

Thorsten Bender

Devasena Rajamohan

Steffen Hartig

Michael Picht

Hamid Moghaddam

Dagmar Opitz

Wolfgang Gentes

Reiner Bildmayer

Torsten Buecheler

Stefan Franke

Uwe Herold

Olivier M Dreidemy

Holger Herrmann

Dietmar Storz

Theo Zimmermann

Joachim Barnbeck

Jochen Wickel

Karina Herrmann

Martina Keller

Sascha Zimmermann

Ralf Reinke

Wilhelm Zwerger

Stephan Naundorf

Boris Krems

Uwe Mayer

Michael Lesk

Alexandra Mark

Tariq Khasawneh

Naci Kalyoncu

Christian Ihrig

Gerhard Maier

Imme Henningsen

Martin Wunsch

Priya Mohana

Shadab Shafiq

Naga Chandra Sekhar Hota

Stefan Mazur

Carsten Scheuch

Joerg Walzenbach

Systems and methods for using a semantic search to address business entities that fulfill certain criteria are provided. A free search term may be determined by a user for the semantic search. The free search term may include any object type, element or parameter the user would like to search for. An ontology which relates to a specific business or industry may be used for the semantic search. The ontology may include various business classes, roles, and individuals. In some implementations, the ontology may be generated from metadata of business objects. The semantic search may be conducted across the entire ontology to obtain search results that match the free search term. As a result, business entities that fulfill the free search term may be retrieved and provided to the user.

Semantic search for business entities

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 opportunity business object.

Consistent interface for opportunity

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 ad-hoc goods movement. 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, for example, a lead processing process component that handles the potential interests of a business partner and the interactions with the business partner over a certain timeframe; an opportunity processing process component that handles the development, processing, and monitoring of opportunities; a customer quote processing process component that handles the processing of quotes to customers offering the delivery of goods according to specific terms; and a sales order processing process component that handles the processing of customers' requests to seller for delivery of goods, on a specific date, for a specific quantity, and for a specific price.

Architectural design for opportunity management 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

In a complex network of computer systems and computing devices, the same data may be accessible by more than one computer program. Each computer program may be able to structure and arrange the date for use with a particular computing environment. A single reference address that is independent of the computer program used to structure and arrange the business data may be used to access business data. The location-independent reference address is translated to a reference address associated with a computer programs that is able to access the business data in the desired format. The translation of the single reference address is based on information about the computing environment from which the request was made. The translation of the single reference address also may be based on user preferences.

Accessing data in a computer network

In a complex network of computer systems and computing devices, the same data may be stored in multiple locations and may be structured and arranged in a particular location for use with a particular computing environment. A single reference address that independent of the various physical locations in which the business data may be located may be used to access business data. The location-independent reference address is translated to a reference address associated with the business data in the desired format and the desired storage location. The translation of the single reference address is based on information about the computing environment from which the request was made. The translation of the single reference address also may be based on user preferences.

Accessing data stored in multiple locations

A redirection service directs, based on a received reference address and user identity information, a user to an appropriate version of a document or an application program. When the user is an author of the document, the user is directed to a version of the document that is undergoing revision. When the user is not an author of the document, the user is directed to a version of the document that is not undergoing revision. Similarly, when the user is a software developer, the user is directed to a version of an application program that is being developed; otherwise, the user is directed to a production version of the application program.

Accessing data based on user identity

Growing community of inventors

Berlin, Germany

Ingo Pfitzner