Sap Ag

Daniel Bock

Stephan Hetzer

Dietmar Nowotny

Joachim Kenntner

Thomas Nitschke

Renzo Colle

Jens Freund

Michael Seubert

Paola Sala

Jochen Hirth

Werner Gnan

Thilo Kraehmer

Markus A Peter

Georg Podhajsky

Robert Doerner

Tao Yu

Stefan Adelmann

Thomas Breitling

Stefan Walz

Otto Makris

Rudolf Winkel

Jochen A Rasch

Axel Kuehl

Adam Kiwon

Frank Thome

Corinne Kuster

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Peter Latocha

Stefan Kaetker

Gerd Moosmann

Gunther Liebich

Michael Meyringer

Gregor Rieken

Johann Kemmer

Toralf Grossmann

Andreas Bold

Antonia Gross

Andre Wagner

Matthias Schmitt

Markus Biehler

Andreas Brossler

Wolfgang Nieswand

Andrea Sudbrack

Dieter Krisch

Andreas F Morsch

Stefan Elfner

Ralf Sievers

Christoph Lehner

Thomas Maag

Stefan Franke

Volker Jaeck

Michael Zoeller

Thomas Bach

Alexander Koegler

Ralf Klein

Andreas Schneider

Holger Herrmann

Dagmar Schultze

Volker Faisst

Daniela Schapler

Karsten Koetter

Uwe Pyka

Ruediger Radcke

Volker Ripp

Renato Zadro

Jochen Steinbach

Otfried Von Geisau

Bernd Schmitt

Georg Dopf

Michael Conrad

Daniel Goldmann

Dirk Henrich

Ingo Pfitzner

Berthold Wocher

Andreas Poth

Arnulf Schueler

Volkmar Stegmann

Kai-Michael Roesner

Christian Haas

Peter Von Zimmermann

Martin Von Der Emde

Udo Laub

Andreas Reccius

Achim Heger

Markus Klein

Steffen Hartig

Michael Picht

Karsten Soegaard Egetoft

Reiner Bildmayer

Ralf Dinkel

Rainer Heun

Andre Wachholz-Prill

Hamid Moghaddam

Otfried Geisau

Michael Hohendorf

Giovanni Deledda

Sebastian Pulkowski

Olivier M Dreidemy

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing customer returns handling. 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 Customer Return Processing process component, a Sales Order Processing process component, a Customer Invoice Processing process component, a Due Item Processing process component, a Balance of Foreign Payment Management process component, a Payment Processing process component, a Supply and Demand Matching process component, an Inventory Processing process component, a Site Logistics Processing process component, and an Inbound Delivery Processing process component.

Architectural design for customer returns handling application software

A business object model, which reflects data that 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.

Consistent set of interfaces derived from a business object model

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.

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service request and order management. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include an Outbound Delivery process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Service Request Processing process component, a Customer Quote Processing process component, a Service Order Processing process component, a Service Contract process component, and a Service Confirmation Processing process component.

Architectural design for service request and order management application software

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having accounting 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 accounting software 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 an internal projects application useful for planning and executing internal projects and measures, including network scheduling, resource staffing, cost estimation and management, time confirmation, and progress monitoring. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include a Costing process component that maintains project cost estimates; an Accounting process component that records relevant business transactions; a Project Processing process component that structures, plans and executes simple, short-term measures and complex projects; and a Time and Labor Management process component that supports the definition of employees' planned working times as well as the recording of the actual working times and absences and their evaluation.

Architectural design for internal projects application software

A method and system handles cost and revenue allocation for service orders. For a service order, there is allowed to be created planned rules for allocation of costs to one or more service providers and for allocation of expected revenues to be received from one or more service receivers, which are forwarded in electronic form, if created, to a cost accounting system. After receipt of a confirmation that the service order has been executed wherein the confirmation includes information about costs actually incurred in executing the service order, there is allowed the creation of revised or newly created rules for allocation of the incurred costs to the one or more service providers and for the allocation of the revenues to be received from the one or more service receivers, which are forwarded in electronic form, if created or revised, to the cost accounting system.

Flexible cost and revenue allocation for service orders

Techniques for error handling are described for errors detected by a computer application that receives and processes application transaction data generated by a different computer application. A determination is made as to the type of error that has been detected. Based on the determination, error correction guidance is displayed to a user for use in using the computer application that received the application transaction data to correct the error. In response to receiving an indication that the error has been corrected by the user, processing of the application transaction data by the receiving computer application is initiated.

User-guided error correction

Techniques for error handling are described for errors detected by a computer application that receives and processes application transaction data generated by a different computer application. A determination is made as to whether an error can be corrected through the use of the receiving computer application. If not, an indication of the error is sent to the computer application that generated the application transaction data so that the error may be corrected using that computer application. If the error can be corrected by using the receiving computer application, an error correction component stores information so that the error can be corrected through the use of the receiving computer application.

Error handling in enterprise information technology systems

Growing community of inventors

Heidelberg, Germany

Daniel Bock