Sap Ag

Thomas Roesch

Andreas Huber-Buschbeck

Joachim Fiess

Igor Becker

Eugen Hermann

Fahmi Cheikhrouhou

Gerlinde Graewe

Michael Schweitzer

Sven Hader

Andreas Schoknecht

Ruediger Fritz

Torsten Schmitt

Ahmed Daddi Moussa

Oliver Dannat

Jozsef Murvai

Zoltan Biro

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 a freight order, a maintenance plan, a maintenance task list, a request for supplier freight quote, and/or a supplier freight quote business object.

Managing consistent interfaces for business objects across heterogeneous systems

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. Specifically, example business objects include DemandPlanningScenario, DemandPlanningScenarioTemplate, and DemandPlanningView.

Managing consistent interfaces for demand planning business objects across heterogeneous systems

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. Specifically, example business objects include DemandPlan, DemandPlanningCharacteristicValueCombination, and DemandViewOfPromotion.

Managing consistent interfaces for demand business objects across heterogeneous systems

Methods and apparatuses enable creating a stateful simulation process with stateless messages. A stateless message instantiates a simulation object for a system to be simulated. The simulation object is identified by an identifier. Activity request messages, which are stateless, identify the simulation object identifier and can thus be associated with the simulation object. Results of execution of requested activities are stored in the simulation object, and thus persisted in the simulation object. In one embodiment, the persisting of simulation results in the simulation object allows the simulation data to be isolated from the active system data. In one embodiment, results of the execution of the simulation are merged in whole or in part with the active backend data.

Simulation business object for service oriented architecture

Growing community of inventors

Sandhausen, Germany

Thomas Roesch