Sap Ag

Alexander Krasinskiy

Renzo Colle

Stephan Hetzer

Jochen Steinbach

Jochen Hirth

Klaus Reinelt

Irena Kull

Thomas Breitling

Steffen Hartig

Nir Pachter

Daniel Zoch

Tao Yu

Thomas Hoffmann

Stefan Adelmann

Henrik Saterdag

Andrea Sudbrack

Andreas Huppert

Andreas Bettin

Christian Haas

Martin Von Der Emde

Thomas Bach

Alexander Koegler

Rainer Heun

Hamid Moghaddam

Simon Dieterich

Matthias Schwarz

Olivier M Dreidemy

Joachim Barnbeck

Attila Orban

Cordula Ude

Katja Kasteleiner

Theo Zimmermann

Amit Yaniv

Michael Lesk

Alexandra Mark

Ralph Meiswinkel

Ralf Reinke

Frank Krueger

Bernhard May

Andrea Hahn

Zoya Pronyakova

Amir Baruch

Sandra Boehringer

Daniel Pascariu

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

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

Communication with a status management component of a computer system is enabled. A status adapter is provided to a processing runtime environment for use in accessing a status management runtime environment. The processing runtime environment includes data object node instances resident in computer memory and enables access to persistent storage for data object node instances. The status management runtime environment is configured to provide status-related information. The status adapter is configured to 1) accept input from the processing runtime environment, 2) provide, to the status management runtime environment, the input in a form that the status management runtime environment is able to use, 3) receive, from the status management runtime environment, an output including status-related information, and 4) provide, to the processing runtime environment, the output in a form that the processing runtime environment is able to use.

Communicating with a status management component in a computer system

Growing community of inventors

Sandhausen, Germany

Alexander Krasinskiy