Sap Ag

Klaus Reinelt

Jochen Steinbach

Renzo Colle

Stephan Hetzer

Jochen Hirth

Bernhard Lokowandt

Andreas Poth

Achim Clemens

Thomas Hoffmann

Stefan Adelmann

Thomas Breitling

Irena Kull

Reiner Bildmayer

Thomas Gross-Boelting

Steffen Hartig

Nir Pachter

Alexander Krasinskiy

Arno Eifel

Jens Freund

Michael Seubert

Gunther Liebich

Werner Gnan

Thilo Kraehmer

Georg Dopf

Georg Podhajsky

Thomas Nitschke

Robert Doerner

Tao Yu

Andre Wagner

Andreas Brossler

Andrea Sudbrack

Andreas Huppert

Achim Heger

Rudolf Winkel

Christian Haas

Andreas Bettin

Martin Von Der Emde

Stefan Franke

Benjamin Klehr

Thomas Bach

Alexander Koegler

Rainer Heun

Axel Kuehl

Hamid Moghaddam

Robert Reiner

Simon Dieterich

Danny Pannicke

Matthias Schwarz

Giovanni Deledda

Olivier M Dreidemy

Martin Schorr

Cordula Ude

Katja Kasteleiner

Theo Zimmermann

Andreas Leukert-Knapp

Martin Gaub

Tesfaldet Negash

Joachim Barnbeck

Attila Orban

Michael Lesk

Alexandra Mark

Ralph Meiswinkel

Ralf Reinke

Tanjana Preiser-Funke

Frank Krueger

Yongbin He

Sabine Montnacher

Frank Reinemuth

Klaus Schlappner

Michael Sylvester

Robert Bieber

Bernhard May

Andrea Hahn

Sergey Alekseev

Manfred Muench

Sandra Boehringer

Daniel Pascariu

Anil Joshi Jetti

Christian Saalfrank

Sunsil S Parvatikar

Martin Von Der Emder

Ralf Schliehe-Diecks

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.

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

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 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 The process components include an RFQ Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Purchasing Contract Processing process component, a Supplier Invoice Processing process component, a Supply and Demand Matching process component, an External Procurement Trigger and Response process component, and a Customer Requirement Processing process component.

Architectural design for make-to-specification application software

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

In various implementations, a sales order are received from a sales order requester for at least one good, wherein the sales order includes product options for ordered goods via a sales product requirement specification object. A sales order confirmation is generated at least partially based on the sales order and a plan for production of the ordered goods. The ordered goods to be produced based on the plan are allowed. And an outbound delivery request defined by a planning product requirement specification object is generated, wherein the ordered goods are delivered to the sales order requestor based on the delivery request.

Make-to-specification process and data model

An electronic data structure, tangibly embodied in an electronic information carrier, models a manufacturing process, and a computer-implemented method that generates and that uses the data structure. The data structure includes a header structure comprising planned time duration information for a defined manufacturing operation of the manufacturing process. The data structure also includes a resource capacity requirement structure linked to the header structure. The resource capacity requirement structure includes, firstly, planned resource capacity requirement information for a defined resource used in the manufacturing operation, and secondly, planned time refinement information that defines, within the header time duration information, a further refined timeframe during which the defined resource is estimated to be consumed.

Rough-cut manufacturing operations for use in planning

Growing community of inventors

Kraichtal, Germany

Klaus Reinelt