web crm1 dv esoa webservicetool

7/27/2019 Web CRM1 DV eSOA WebServiceTool

http://slidepdf.com/reader/full/web-crm1-dv-esoa-webservicetool 1/46

SAP CRM 2007Detailed View

SAP CRM 2007

Web Service Tool



Disclaimer

This Presentation is a preliminary version and not subject to your licenseagreement or any other agreement with SAP. This document contains

only intended strategies, developments, and functionalities of the

SAP® product and is not intended to be binding upon SAP to any

particular course of business, product strategy, and/or development.

Please note that this document is subject to change and may be

changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document.



© SAP 2007 /

1. Web Service Tool

2. Defining a Web Service

3. Consuming a Web Service

4. Wrap-up

What we will cover



COMPREHENSIVESIMPLE FLEXIBLE

SAP Delivers CRM Without Compromise

Delivering on SAP’s Enterprise SOA Roadmap

SAP CRM 2007 provides enterpr ise services

Delivering on SAP CRM’s promise to deliver flexible CRM solution

SAP CRM 2007 provides Web Service Tool enhancements

Delivering on SAP’s Enterprise SOA and SAP

CRM’s Roadmap: SAP CRM 2007



Web Service Tool for SAP CRM

Special

CRM Market

Needs

Model-Driven Workbench

Quick Service Definition and

Provision

Flexible Service Management

Service Cuts as You Need Them

Flexibility

Speed

Innovation



Web Service Tool: Technical Overview

Wizard-based service object definition

with Web Service Tool based on

CRM’s BOL

Function module creation for eachservice operation

Web service creation with SAP

NetWeaver’s service environment

SAP CRM 2007

GENIL layer

Business object l ayer

SAP NetWeaver 2004s

Design layer Design tool

Transformation layer

Function module generation

Web service generation



Web Service Tool: General Overview

Coding-free service

modeling

Customer BOL

objects can

be leveraged

Reuse of given

service definitions

Main objects will

be enabled

User-friendly

definition process

Only four steps to

define a service

Technical complexity

is hidden

Allows rapid service

deployment

Usage of compound

services

Service objects are

transformed into

function modules

Web services are

built on top

SAP NetWeaver Web

Service infrastructureis leveraged

Based on CRM

Business Object Layer (BOL)

Model-driven servicedefinition

Embedded into SAPNetWeaver

Service

Tool

Service

Tool



Tool Characteristics

Web Service Tool: Basic Characteristics

Supported Methods Service Characteristics

Basic queries

Read operations

Create operations

Change operations

Stateless services

Synchronous

services

Limited to one given

BOL object

Services follow the

World Wide Web

Consort ium (W3C)

standards(e.g., XML and SOAP)

Wizard-based

Based on CRM’s BOL

Security settings

Default values

Access to Web

Service Definition

Language

(WSDL) file Test environment



Feedback from Accenture

First xApp built with CRM

Web Services Tool by AccentureConsulting

Fully service-based

Uses Adobe Forms

Flexible adjustable

Short time-to-market

SAP and Partners

“ “ The Web Services Tool improvesand advances the creation of Web

services signi ficantly.

It accelerates the development of

CRM projects because it:

Requires less knowledge

Is easy to use and understand

Is transparent

The Web Services Tool works

logically and intuitively through the

process of creating Web services

based on the CRM Business Object

Layer.”

Arno Huhn, Accenture



© SAP 2007 /

1. Web Service Tool



4. Wrap-up

What we will cover



Individual Service Definition has Never

Been Easier

Select the objects that are the basis for the Web service

Select all needed attributes for the Web service

Maintain the selected attributes and assign default values

Generate the modeled Web service

Web service and WSDL can be tested and then be ready

for consumption

Model-driven definition of Web services without any extra coding



Web Service Creation in SAP CRM

Create Web

Services in four simple steps

Create WebServices for

almost anytransaction inSAP CRM

ex: Quotation,

Order, Lead,Opportunity,Service

Request etc..

Creation doesnot require any

coding



Start Screen: Object Overview List

From each screen you can switch to Expert Mode to view technical informationof the objects

Basic information about the current screen, your options,and the proposed steps is displayed on each screen

Search for a service object

Use filter criteriaGo to object details

Create, copy, or delete anobject

Filter error information after you have transported anobject*

* New with CRM2007



Wizard Screen 1: Select Objects

The wizard offers easy navigation with the Next and Previous buttons or with a direct click on the wizardsteps (numbers)

Specify a name and select theneeded usage type for the object

Choose needed service operati

Select the business and mainobject (root object) for the servic

Select the required query objectfor the service

Select a component set to creatservices that contain more thanone business object *

* New with CRM2007



Wizard Screen 2: Select Attributes

Experienced users can display technical BOL names for further information

Choose the respective relationon the left side of the split screen

Select the needed attributes onthe right side

You can select one, all, or several attributes per relation

After finalizing a relation, clickConfirm Selection; then choosethe next relation

Choose expert mode to gethelpfull information on the required

fields for your serviece *

* New with CRM2007



Wizard Screen 3: Maintain Attributes

Maintain your service object to adapt it to your specific needs

* New with CRM2007

Replace the attribute name withreference name for the WSDL

Maintain or exclude the attributof the query objects

Predefine default values for attributes as proposals for theservice consumer or as pre-defined values that can not bechanged by the consumer any-more

Export the structure of your ser

object to MS Excel for further documentation *



Wizard Screen 4: Final Object Settings

Start the service test environment and expose the WSDL file

Security settings can be assignto the service object

For service objects, only theservice-specific settings have tobe given

Perform a consistency check fothe defined objects

Activate a service object to creathe respective Web serviceinterface

Set an object to “Productive” to

indicate that it is in active use anto freeze its definition

Information about the availabilitin the respective clients isdisplayed *

* New with CRM2007



Wizard Screen 4: Testing and WSDL Exposure

Launch the SAP NetWeaver test environment and expose the WSDL file

Test your service right after creation Extract the WSDL file for direct consumption



Enhancements: Web Services Tool - CRM2007

Compound Services

With CRM2007 it is possible to build services (read and change) thatcontain more than one business object. Thus, you can now get thebusiness partner address details within a service call against a salesorder.

Display of mandatory fieldsWith CRM2007 the web service tool displays all mandatory fields for the

service objects in the wizards screen two

Excel exportWith CRM2007 you can export the structure of your service object into anExcel sheet, including your personal settings regarding default values andreference fields

Attributes for better usabilityWith CRM2007 the web service tool provides further technical details for the user, such as the client information where the service is released



Status and Lifecycle Management of a

Service Object

Draft

Acti vated

Productive

Not productive

Service object states

Service objects can have four

different states. Depending on

the status of the object, youcan edit or change object.

To test or consume a service,you must activate it.

Further changes to the object

are permitted as long as it

has not been set to productive.

Service objects can have four

different states. Depending on

the status of the object, you

can edit or change object.

To test or consume a service,

you must activate it.Further changes to the object

are permitted as long as it

has not been set to productive.

Status: Draft

Initial and edit status All kinds of changes are permitted

Objects are saved and can be enhanced later on

Status: Active Web service created and available for testing and

WSDL export

Object changes are permitted by setting the statusback to draft (edit mode)

Web services and WSDL are overwrittenautomatically during next activation

Status: Productive Status indicates active use of service interface

Object cannot be changed, but it can be copied

Status: Not productive Status indicates that service is not used

Object can be set back to productive, deleted, copied



© SAP 2007 /

1. Web Service Tool



4. Wrap-up

What we will cover



Consumption of Web Services

Customers and partners can easily build composite applications on

top of predefined CRM enterprise services or their individualgenerated Web services

The services can be consumed from any system that follows the service-orientation

approach and allows the consumption of Web services such as Microsoft Word or Adobe

Interactive Forms

As an example, the following slides

illustrate the basic steps that are

needed to create an interactive form

that consumes CRM services

… based on your individual

Web services

Build your composites …



Examples for Service Consumption

Adobe Interactive Forms

Microsoft Excel & Word

User Interfaces

Mobile Devices

Widgets

Integration Scenarios

....



SAP CRM Consuming

Service Interfaces

Word Integration

(Standard Integration)

Use Case for Leveraging Services



MS-Word Integration based on SAP CRM

Services – Design Time

Design , save

and re-useyour template

at the click of

a button

Drag drop

object

attributes intostatic text for

dynamic

compilation of

documents

Connectivity is

done based on

CRM services



MS-Word Integration based on SAP CRM

Services – Run Time

Launch the

templatecompiled with

the object

attributes at

the click of a

button

Enjoy the

automatic re-sizing of the

tabular data

Edit the

system

compiled

document to

fit your needs

Save the

changed copy

as an

attachment



SAP CRM

Adobe Integration

(Example)

Use Case for Leveraging Services



Adobe Forms Leveraging Services

Export CRM data to

Adobe Forms

Enable offl ine scenarios

Replace manual s teps

by leveraging services

Adobe Forms



Processes

People and roles

Example: Service Request Processing with

External Service Provider*

CRM CRM

Problem

call

interactioncenter

Create

service

request

Schedule

on-site visit

Inform

service

provider

View taskConfirm

on-site

work

Send info Confirmation Invoice

Today’s business problem

After assigning external service providers toservice requests, thedata transfer process must betriggered manually

Service request data cannot be

transferred appropriately Confirmation data must be written on paper

and then entered manually intothe CRM system

Complete process is time consuming anderror-prone

Solution: Adobe leveragingservices

Replaces inefficient and error-proneprocess

Enables very short time-to-value

Enables easy adjustments

Exchanges all relevant information inelectronic form to speed up the processand avoid errors

Interaction

center agent

Customer Service resource

planner

External service

provider

Service manager

(optional)

Billing clerk

(optional)

Offline

* Remark: Presented Adobe is not part o f regular CRM shipments



Adobe Interactive Form: Service Requests

with External Service Provider

* Remark: Presented Adobe is not part of regular CRM shipments



Adobe Lifecycle Designer

Example: Consuming CRM Web Services with

Adobe Form Designer



Step 1: Testing the Web Service

CRM services can be easily tested with the wsadmin transaction

or directly from the Web Service Tool

* Enterprise services are also maintained in ESR and Enterprise SOA exploration workplace (SDN)



Step 1: Testing the Web Service (cont.)






Step 2: Generating the WSDL File

The WSDL of a service can be easily generated and stored



Step 3: Consuming the Web Service

Example: Form Designer

The WSDL can be easily imported into the Adobe Interactive Forms Designer




Example: Form Designer (cont.)

The service request and response messages are displayed in the data view

of the designer

Now the form can be built by dragging and dropping the attribute fields




Example: Form Designer (cont.)

After building the

basic structure of theform, graphical

elements can be

added and field

attributes can be set



Result: Adobe Form Consuming CRM Services

After rendering the

XML document, thePDF is ready for

use



Adobe Form Consuming CRM Services



7 Key Points to Take Home

Build your individual service in a few minutes

Change or copy given services “on the fly”

Define services exactly as you need them

Use comfortable wizard for service definition

Manage default values for service attributes

Reach ROI much faster for your Service-Oriented Architecture (SOA)

projects

Leverage SAP NetWeaver’s Web service infrastructure



Interested ?

For further details on the Web Services Tool, please have a look at the CRMEXpert

March Edition for a general overview on functions and features

August/ September Edi tion to get technical background information



© SAP 2007 /

Further information - SOA

SAP Developer Network on Enterprise SOA:

www.sdn.sap.com/irj/sdn/developerareas/esa

SAP Developer Network on Web Services

www.sdn.sap.com/irj/sdn/developerareas/esa/webservices

SAP Developer Network on Enterprise Services

Community

www.sdn.sap.com/irj/sdn/developerareas/esa/esc

World Wide Web Consortium on Services

www.w3.org

http://www.sdn.sap.com/irj/sdn/developerareas/esa

http://www.sdn.sap.com/irj/sdn/developerareas/esa/webservices

http://www.sdn.sap.com/irj/sdn/developerareas/esa/esc

http://www.w3.org/

http://www.w3.org/

http://www.sdn.sap.com/irj/sdn/developerareas/esa/esc

http://www.sdn.sap.com/irj/sdn/developerareas/esa/webservices

http://www.sdn.sap.com/irj/sdn/developerareas/esa



© SAP 2007 /

Further information – SAP CRM

SAP CRM - Roll-Out Map

https://portal.wdf.sap.corp/go/crm-rollout-map

SAP CRM - Ramp-Up Knowledge Transfer (RKT)http://service.sap.com/rkt-crm

SAP CRM – Demo Portal

http://crmportal.wdf.sap.corp:1080

SAP CRM – WiKihttps://wiki.wdf.sap.corp/display/SAPCRMHub/Home

SAP CRM - Help Portal

http://help.sap.com/crm

SAP Public Web

http://www.sap.com/crm


http://service.sap.com/rkt-crm

http://crmportal.wdf.sap.corp:1080/

https://wiki.wdf.sap.corp/display/SAPCRMHub/Home





https://wiki.wdf.sap.corp/display/SAPCRMHub/Home

http://crmportal.wdf.sap.corp:1080/

http://service.sap.com/rkt-crm




© SAP 2007 /

Copyright 2007 SAP AG

All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkteund S ervicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignungf ür einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftungf ür Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzlicheHaftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

web crm1 dv esoa webservicetool

Documents