Sap Ag

Sap Se

Sap Aktiengeselleschaft

Jochen Steinbach

Stephan Hetzer

Andreas Poth

Renzo Colle

Jens Freund

Jochen Hirth

Klaus Reinelt

Martin J Wilmes

Achim Clemens

Jaakob Kind

Stefan Adelmann

Vladimir Shapiro

Andreas Bettin

Achim Heger

Irena Kull

Reiner Bildmayer

Nir Pachter

Matthias Kaiser

Roman Rommel

Gunther Liebich

Kai Richter

Bernhard Lokowandt

Thomas Nitschke

Tao Yu

Frank Wagner

Georg Podhajsky

Thomas Hoffmann

Andrea Sudbrack

Thomas Breitling

Martin Von Der Emde

Thomas Bach

Rainer Heun

Steffen Hartig

Shai Alfandary

Alexander Krasinskiy

Holger Herrmann

Katja Kasteleiner

Cordula Ude

Peter Latocha

Guenter Pecht-Seibert

Michael Seubert

Gerd Moosmann

Paola Sala

Stefan Kaetker

Dietmar Nowotny

Werner Gnan

Joachim Kenntner

Thilo Kraehmer

Daniel Bock

Jochen Mayerle

Georg Dopf

Stephan Kohlhoff

Ingo Pfitzner

Holger Knospe

Ami Heitner

Stefan J Moeller

Robert Doerner

Andre Wagner

Volkmar Stegmann

Andreas Huppert

Andreas Brossler

Rudolf Winkel

Wolfgang Barheine

Christian Haas

Ulrich Keil

Stefan Franke

Thomas Gross-Boelting

Hamid Moghaddam

Alexander Koegler

Andre Wachholz-Prill

Axel Kuehl

Joachim Fessler

Marianne Brosche

Benjamin Klehr

Michael Picht

Robert Reiner

Olivier M Dreidemy

Yuval Morad

Matthias Schwarz

Christian Baeck

Otfried Geisau

Thorsten Kulick

Thomas Friedrich

Giovanni Deledda

Danny Pannicke

Simon Dieterich

Attila Orban

Jochen Wickel

Peer Marschall

Tim Gaiser

Theo Zimmermann

Christoph Engler

Tesfaldet Negash

Martina Lahr

Karina Herrmann

Andreas Leukert-Knapp

Martin Schorr

Sergio Rozenszajn

Joachim Barnbeck

Martin Gaub

The disclosure generally describes methods, software, and systems for providing solution descriptions. A problem description of a problem is received, from a client, at a cloud-based reasoning service. A solution description for a solution to the problem is received. Case metadata for a case defining the problem and solution are generated by the cloud-based reasoning service. The case metadata, including the problem description and solution description, are stored by the cloud-based reasoning service in a cases repository associating solutions with problems. A new problem is received at the cloud-based reasoning service. An automated analysis of the new problem is performed, and a comparison is made of the new problem with existing solutions in the cases repository to identify solutions matching the new problem. A new solution description is provided that is based on a match between the new problem description and the problem description and using the problem solution.

Case-based reasoning as a cloud service

Technologies are described for creating activity object instances corresponding to collection object instances, and for conducting tests between activity object instances and collection objects instances, and within a set of activity object instances. Tests can include determining whether collection object instances have counterpart activity object instances, and evaluating a collection object instance with respect to a corresponding activity object instance. Activity object instances can be set to be performed in a sequence, and a test can determine whether the sequence is consistent with sequencing rules. When activity object instances are automatically created from collection object instances, a user can be presented with a graphical user interface that includes representations of activity object instances, and the user can manipulate the graphical user interface to provide precedence information.

Automated generation and consistency checking of software objects

An interface provides decision support in complex problem environments. An interface engine selectively communicates with a database to display (e.g., in tree form) proposed decisions and various corresponding outcomes resulting from cause-effect relationships of selected decisions. Structured data objects store state information (e.g., current/projected/target) of multi-faceted, inter-connected entities. Object metadata can include entity attributes and/or entity relationship details. The interface allows traversing the tree to explore the cause-effect relationships and/or validate various solution paths. The tree (including the proposed decisions, outcomes, and solution paths) may be initially generated up front, based upon particular problem scenario characteristics. Limited subsequent interaction between the interface engine and the underlying backend data store may enhance speed/performance/user experience. Roundtrip interaction with the underlying database may take place where a user seeks to adjust a decision with specific metrics and simulate the result, and/or create an execution plan/activity based upon a solution path previously designed.

Interface providing decision support in complex problem environment

Example methods and systems are directed to dispatching database tasks. An application may access data associated with a task. The data may indicate features (e.g., processing functionality) that will be used to complete the task. The application may determine whether all such features are implemented in the database layer. The application may dispatch the task to the database layer if all features are implemented therein. The application may perform the task in the application layer if one or more of the features are not available in the database layer. In some example embodiments, the task involves materials requirements planning. Such a task may include determining, for a given bill of materials ('BOM'), the quantity of materials available on-hand, the quantity available from suppliers, the transport or delivery time for the various quantities, and other data regarding the BOM.

Database dispatcher

Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature. The navigation pane display can expand at a selected user interface element to display additional user interface elements corresponding to process features involved in completion of the process feature corresponding to the selected first user interface element.

Linear visualization for overview, status display, and navigation along business scenario instances

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

A system and method are described for intelligently sourcing demand forecasts within a supply chain management ('SCM') system based on a constrained supply chain model, in light of material and resource constraints. For example, a computer implemented method according to one embodiment of the invention comprises: calculating a demand forecast identifying anticipated demand for a product over a specified time period; identifying current sales orders for the product with delivery dates scheduled during the specified time period; generating an open forecast for the product based on the current sales orders and the anticipated demand; and sourcing different percentages of the open forecast from different plants, the percentages selected based on supply chain material and/or resource constraints. In addition, after the demand forecast is sourced, one embodiment of the invention employs additional techniques for intelligently sourcing new sales orders entering the SCM system.

System and method for sourcing a demand forecast within a supply chain management system

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

Computer-implemented methods, and associated computer program products and systems, for checking availability of a ware in a time interval, a resource to produce the ware being associated with the ware. The computer-implemented method can include obtaining capacity supply information comprising a capacity supply for each date of the time interval and capacity demand information comprising a capacity demand for each date of the time interval. The first date of the time interval is set to a later date, there is determined for each date from the first date to the later date whether capacity supply is unused. If capacity supply is unused, the method includes eliminating the specific amount from the capacity supply information. In response to demand information representing a demand having a requested date, availability of the resource on the requested date is determined using the capacity supply information and the capacity demand information.

Availability check for a ware

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

Growing community of inventors

Bad Schoenborn, Germany

Jochen Steinbach