Sap Ag

Sap Se

Christian Haas

Hamid Moghaddam

Olivier M Dreidemy

Alexander Koegler

Steffen Hartig

Joachim Barnbeck

Attila Orban

Yuh-Cherng Wu

Stephan Hetzer

Jochen Hirth

Berthold Wocher

Matthias Schwarz

Michael Lesk

Alexandra Mark

Frank Brunswig

Gerd Ritter

Renzo Colle

Jens Freund

Peter Latocha

Jochen Steinbach

Ashish Anand

Stefan Kaetker

Gerd Moosmann

Steffen Tatzel

Daniel Bock

Daniel Goldmann

Michael Jung

Ingo Pfitzner

Tao Yu

Thomas Nitschke

Georg Podhajsky

Volkmar Stegmann

Andrea Sudbrack

Wolfgang Nieswand

Klaus Reinelt

Stefan Adelmann

Christopher Ronnewinkel

Christoph Lehner

Irena Kull

Thomas Breitling

Andre Wachholz-Prill

Devasena Rajamohan

Rainer Heun

Dagmar Opitz

Thomas Bach

Stefan Franke

Simon Dieterich

Uwe Herold

Dietmar Storz

Otfried Geisau

Sebastian Pulkowski

Nir Pachter

Thomas Konstandin

Alexander Krasinskiy

Martina Lahr

Peer Marschall

Katja Kasteleiner

Theo Zimmermann

Thomas John

Christoph Engler

Jochen Wickel

Cordula Ude

Helge Schulte

Sascha Zimmermann

Wilfried Merkel

Martina Keller

Boris Krems

Sharad Dixit

Peter Meuer

Uwe Mayer

Ralph Meiswinkel

Sabine Montnacher

Joerg Walzenbach

Tariq Khasawneh

Naci Kalyoncu

Abinash Nanda

Mohannad Ezzo

Prasanth Alapati

Binoo Chandran

Sandra Schmidt

Bernhard May

Andrea Hahn

Disclosed herein are system, method, and computer program product embodiments for extracting customer relationship management (CRM) data from an on-premises database for testing with a cloud-based CRM. The extraction approach simplifies, through the use of a wizard, the selection of relevant customer records and their extraction, along with any dependencies on other records. The extracted records can then be uploaded to the cloud-based CRM for evaluation.

Data migration using transactional data as primary object

A view object is generated in a target deployment unit in a design time environment of a metadata repository. The view object is modeled on a business object of a source deployment unit. The source deployment unit includes process components of a business application that is physically decoupled from the target deployment unit. A subset of attributes of the business object of the source deployment unit is selected. The subset of attributes includes at least an outbound agent and an inbound agent implemented by a generic messaging framework. The view object is modeled in the target deployment unit with the subset of attributes of the business object. The inbound agent of the view object is configured for receiving a replication message from the outbound agent of the business object, and the replication message includes replication data for configuring the view object only with data from the business object.

Declarative view objects

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.

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

A method of designing a knowledge repository includes receiving, in a computer system, a first input to form a configuration template for a knowledge repository. The configuration template describes a class of knowledge entities to be included in the knowledge repository. There is received a second input identifying a document template to be used in displaying instances of the class of knowledge entities. The document template is selected from a predefined group of document templates. The document template is associated with the configuration template in the computer system. The thus designed knowledge repository may be provided with knowledge entities accordingly. Moreover, the created knowledge repository may be used to retrieve specific knowledge.

Knowledge repository using configuration and document templates

Growing community of inventors

Heidelberg, Germany

Christian Haas