Sap Ag

Andre Wachholz-Prill

Ingo Pfitzner

Andrea Sudbrack

Martina Lahr

Christoph Engler

Georg Podhajsky

Tao Yu

Thomas Nitschke

Stefan Adelmann

Volkmar Stegmann

Rainer Heun

Thomas Bach

Peer Marschall

Cordula Ude

Katja Kasteleiner

Helge Schulte

Wilfried Merkel

Yuh-Cherng Wu

Jens Freund

Jochen Steinbach

Stephan Hetzer

Paola Sala

Gunther Liebich

Steffen Tatzel

Dietmar Nowotny

Jochen Hirth

Joachim Kenntner

Daniel Bock

Berthold Wocher

Andreas Poth

Michael Jung

Marcus Dill

Christopher Ronnewinkel

Roman Hayer

Wolfgang Nieswand

Christian Haas

Christoph Lehner

Martin Von Der Emde

Jens Weidner

Achim Heger

Steffen Hartig

Hamid Moghaddam

Stefan Franke

Wolfgang Gentes

Reiner Bildmayer

Michael Picht

Dagmar Opitz

Alexander Koegler

Devasena Rajamohan

Dietmar Storz

Markus Kupke

Olivier M Dreidemy

Uwe Herold

Holger Herrmann

Theo Zimmermann

Joachim Barnbeck

Jochen Wickel

Karina Herrmann

Ralf Reinke

Wilhelm Zwerger

Boris Krems

Stefan Busch

Martin Diewald

Uwe Mayer

Michael Lesk

Alexandra Mark

Martina Keller

Martin Wunsch

Priya Mohana

Shadab Shafiq

Naga Chandra Sekhar Hota

Stefan Zern

Wolfgang Meurer

Joerg Walzenbach

Tariq Khasawneh

Naci Kalyoncu

Christian Ihrig

Gerhard Maier

Imme Henningsen

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

Navigating from an alert related to a state of a data object to a source of the alert includes displaying alerts in a portal environment. The portal environment has an analytical portal application associated with an analytical data store and a transaction portal application associated with a transaction data store. One of the alerts includes a transaction alert that is associated with a data object in the transaction data and another of the alerts includes an analytical alert that is associated with a data object. An indication of a transaction alert or an analytical alert is received from a user. When the indication is an indication of an analytical alert, navigation occurs to the analytical portal application. When the indication is an indication of the transaction alert, navigation occurs to the transaction portal application.

Providing portal navigation for alerts

A method comprises determining a rule type needed for selecting an action to be performed with regard to a data object, identifying an access procedure associated with the rule type, retrieving query attributes from a context associated with the data object, searching an attribute database with a query attributes, and, if the query attributes match a first attribute set, accessing a first rule that belongs to the rule type and that is identified by the first attribute set. Each of a plurality of rules in a rule database is capable of being identified by any attribute set in the attribute database. Input functions for modeling the rules and creating the databases may be provided. Use of the rules can be simulated.

Modeling and using business rules

Growing community of inventors

Bellheim, Germany

Andre Wachholz-Prill