Sap Ag

Sap Se

Stephan Hetzer

Renzo Colle

Jochen Hirth

Jochen Steinbach

Jens Freund

Daniel Bock

Tao Yu

Thomas Nitschke

Paola Sala

Joachim Kenntner

Andreas Poth

Georg Podhajsky

Stefan Adelmann

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Michael Seubert

Dietmar Nowotny

Werner Gnan

Thilo Kraehmer

Gregor Rieken

Markus A Peter

Johann Kemmer

Achim Clemens

Martin J Wilmes

Toralf Grossmann

Andreas Bold

Andrea Sudbrack

Markus Biehler

Antonia Gross

Matthias Schmitt

Andre Wagner

Andreas Brossler

Klaus Reinelt

Wolfgang Nieswand

Thomas Breitling

Thomas Maag

Ralf Sievers

Irena Kull

Otto Makris

Andreas F Morsch

Stefan Elfner

Rudolf Winkel

Andreas Bettin

Christoph Lehner

Achim Heger

Alexander Koegler

Michael Zoeller

Jochen A Rasch

Steffen Hartig

Axel Kuehl

Volker Jaeck

Reiner Bildmayer

Thomas Bach

Ruediger Radcke

Frank Thome

Daniela Schapler

Dagmar Schultze

Alexander Krasinskiy

Karsten Koetter

Corinne Kuster

Nir Pachter

Peter Latocha

Stefan Kaetker

Gerd Moosmann

Ami Heitner

Arnulf Schueler

Frank Wagner

Robert Doerner

Christian Haas

Martin Von Der Emde

Rainer Heun

Shai Alfandary

Hamid Moghaddam

Stefan Franke

Renato Zadro

Holger Herrmann

Adam Kiwon

Volker Ripp

Olivier M Dreidemy

Volker Wiechers

Gunther Liebich

Bernhard Lokowandt

Ingo Pfitzner

Berthold Wocher

Stefan J Moeller

Thomas Hoffmann

Volkmar Stegmann

Andreas Huppert

Wolfgang Barheine

Andre Wachholz-Prill

Thomas Gross-Boelting

Hans-Ulrich Von Helmolt

Peter Schwarze

Michael Picht

Thorsten Kulick

Simon Dieterich

Christian Baeck

Thomas Friedrich

Yuval Morad

A system includes a suite of business applications and an add-on module coupled to the suite of business applications. The add-on module is configured with Commerce eXtensible Markup Language (cXML) and is operable to enable the suite of business applications to communicate with a network using cXML and a direct web service call to the network. The network is configured to operate using cXML. The direct web service call uses no middleware between the suite of business applications and the network.

System for business suite and network integration

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

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, 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, 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 operations, each being implemented for a respective process component. The process components include an Outbound Delivery 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 Service Request Processing process component, a Service Order Processing process component, and a Service Confirmation Processing process component.

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 inbound delivery request business object.

Consistent interface for inbound delivery request

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing a make to stock process. 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 Accounting process component; a Production process component; a Site Logistics process component; a Confirmation and Inventory process component; a Customer Requirement Processing process component; a Demand Forecast Processing process component; a Supply and Demand Matching process component; a Production Trigger and Response process component; an In-house Requirement Processing process component; a Sales Scheduling Agreement Processing process component; and a Demand Planning process component.

Architectural design for make to stock application software

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 and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supply chain control 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.

Computer readable medium for implementing supply chain control using service-oriented methodology

Methods and apparatus, including systems and computer program products, for a service architecture design that provides enterprise services having logistics execution 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 logistics execution application as enterprise services

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

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing intra-company stock transfer of physical inventory. The application is structured as multiple process components interacting with each other through service operations, each implemented for a respective process component. The process components include a Supply and Demand Matching process, a Customer Requirement Processing process component, a Logistics Execution Control process component, a Site Logistics Processing process component, an Outbound Delivery Processing process component, an Inbound Delivery Processing process component, an Inventory Processing process component, a Production and Site Logistics Auxiliaries process component and a Freight Documents Processing process component.

Architectural design for intra-company stock transfer application software

Embodiments include a system for providing a set of services that retrieve requested data and calculate a requested value. The data retrieval service may traverse a set of related data structures such as data in a document or in a database to accumulate and return requested data. The data calculation service may determine an appropriate algorithm based on the data being processed and return a value. The data calculation service may call the data retrieval service to obtain the necessary data. These services may be independent services separate from other software applications. These services provide standard data determination and calculation functions across multiple applications and are accessible in a common software layer.

Quantity offsetting service

Growing community of inventors

Oestringen-Eichelberg, Germany

Stephan Hetzer