demonstrating caf

Demo Scenario - First Day Composite Application for SAP NetWeaver 7.0-Java-VMware-Trial

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2007 SAP AG 1

Demo Scenario - First Day Composite Application for SAPNetWeaver 7.0-Java-VMware-Trial

SummaryThe business case of this story is to add a new step for the new employee’s manager in order to let him getan overview of the items the employee registered in his self-assessment. This requires a service-enabling ofthe registration application (Part 2), the creation of a new UI (Part 3) and the extention of the existing GuidedProcedure (Part 4).

Author: Alexander Bruch, Peder HelleCompany: SAP AG, GermanyCreated on: 1th Februar, 2007



© 2007 SAP AG 2

Table of ContentsDemo Scenario Overview............................................................................................................ 2

Story Outline ...........................................................................................................................2Roles....................................................................................................................................... 2Users ......................................................................................................................................3Duration (of movie) ..................................................................................................................3

Detailed Storyboard ....................................................................................................................3Demo Part 1 - Guided Procedure “My First Day” ......................................................................3

Overview..............................................................................................................................3Detailed navigation...............................................................................................................3

Demo Part 2 – Service enabling the CAF application ...............................................................6Overview..............................................................................................................................6Detailed navigation...............................................................................................................7

Demo Part 3 – Creating a Visual Composer application ......................................................... 16Overview............................................................................................................................ 16Detailed navigation............................................................................................................. 16

Demo Part 4 – Extending the Guided Procedure.................................................................... 27Overview............................................................................................................................ 27Detailed navigation............................................................................................................. 27

Copyright .................................................................................................................................. 40

Demo Scenario Overview

Story OutlineThe business case of this story is to add a new step for the new employee’s manager in order to let him getan overview of the items the employee registered in his self-assessment. This requires a service-enabling ofthe registration application (Part 2), the creation of a new UI (Part 3) and the extention of the existing GuidedProcedure (Part 4).

The demo starts with the existing Guided Procedure for a new employee’s first day.

This documentation assumes you will be working directly on the operating system – all references to theWeb Application Server therefore refer to “ivml2005”.

Roles

DESIGNATION NAME COMMENTS

End user Miller, Jamie A new employee at IteLO

Manager CTB_ADMIN The administrator is also usedas manager of Jamie Miller (inPart 4)



© 2007 SAP AG 3

Users

Predefined users Password Comments

CTB_ADMIN sap123 Administrator for WebAS, EnterprisePortal and Visual Composer – used fordesign time and development purposes

<NW Developer Studio> welcome1 SDM deployment from the IDE

14132 sap123 User (Jamie Miller) for differentscenarios

Duration (of movie)

DESCRIPTION

Demo Part 1: (3 min) – Guided Procedure “My First Day”

Demo Part 2: (5 min) – Service enabling the CAF Core application

Demo Part 3: (8 min) – Creating a Visual Composer application based on the CAF Core service

Demo Part 4: (8 min) – Extend the Guided Procedure with the new Visual Composer UI

Detailed Storyboard

Demo Part 1 - Guided Procedure “My First Day”

OverviewThis demo serves as an entry point for the subsequent 3 demo parts. It demonstrates how an employee’sfirst day in a company is made easier with the usage of Guided Procedures as a user interface basedprocess. Instead of navigation through different pages within the portal (as with Employee Self Service), thenew employee is guided through all steps required to get up-to-speed quickly.

Detailed navigation

Steps



© 2007 SAP AG 4

Log on to the portal as an administrator(CTB_ADMIN).

Start a new Guided Procedure processby clicking on the link „Start My FirstDay“.

Notice: In a productive system, thisprocess would be automatically triggeredby a HR-system, e.g. at the day theemployee joins the company.

Notice: The second link „Start My FirstDay (after)“ is a predefined processwhere all sessions in this document havealready been implemented. You can usethis in case you just want to show theresult.

Log off the portal.

The new employee opens the portal andin the inbox sees all tasks waiting forhim. One of the is the „First Day“ GuidedProcedure.Log on to the portal as an employee(14132).Navigate to the workset „Work“.

To open the process, click on the link“Welcome to ITeLO” in the UniversalWork List (UWL).

The employee is welcomed by a screentelling him the next steps and giving himbackground information on the company.All the personalized information (nameetc) is based on the user informationretrieved from the portal context. Thismeans, when Jamie runs the process,the name of Jamie will be displayed.

Click on the button ”Start my first dayprocedure” to continue.



© 2007 SAP AG 5

Jamie gets the information already storedin the HR system (which is based on thedata from his job application). Necessarychanges to the data can be done beforeconfirming.

Click on the button „Confirm“.

Similar to the address data screen, thebank data is retrieved from the HRsystem and displayed. Again, changescan be made and confirmed.


The Hardware Registration screen isdifferent from the other screen – this isan entirely custom made applicationsince these information cannot be storedelsewhere (e.g. ERP). To Jamie this isjust another step in the process, though.The business case for the application isto make a self-assessment of all devicesand hardware handed out on the firstday. These data are stored in the CAFapplication itself.

Jamie can add some new equipment,save and continue with the button“Complete”.

Notice: The development scenario forthis application can be found in the “How-To-Guide” for CAF Core.



© 2007 SAP AG 6

As part of the policy at ITeLO, Jamie hasto agree on the confidentialityobligations. The agreement document isautomatically produced and filled with theuser’s name and displayed as an AdobeInteractive Form. Jamie can print out theform, sign it and send it to the HRdepartment.One of the benefits of having this screenas part of the Guided Procedure is thatthe responsible manager now knows thatall new employees must have seen theagreement upon running the process.There is no way around by saying “I’venever seen that document, so I couldn’tagree to it”…

Proceed with the button “Complete”.

Note: The adobe application might timeout the first time it is started after aserver restart. Click on the link in theactivities navigation (left side) to startagain. Eventually you will have to log offand on the portal and open the task inthe inbox again.

The process has now been completed.In a productive environment, otherscreens and information would perhapsbe added to the process making it evenmore comprehensive. How to do so isthe focus of the subsequent sessions.

Log off the portal.

Demo Part 2 – Service enabling the CAF application

OverviewThis part of the demo covers how to make an existing CAF application ready to be used in otherenvironments. This is accomplished by creating Web Services from the application. The application is acustom made application which handles all aspects around administrating objects – in this case hardwareand devices registered on an employee. Amongst others, the persistency of the objects and the life-cycle



© 2007 SAP AG 7

methods (create, read, update, delete) as well as integration to other systems are topics covered by theapplication.

For more information on the development of the CAF core application, see the document“HowTo_CAF_Core”

Detailed navigation

Steps

Before you start: Notice that you have to run through this session at least once in order to run thenext two sessions.

The CAF application “Hardwareregistration” is implemented with the SAPDeveloper Studio. It contains all entitymodels, service integration and accessmethods required to make it a full-blownapplication with own business logic andpersistency. So far, only the internal WebDynpro project has been used as an UI.The goal of this demo session is to makethe application also available to other (UI)technologies by creating Web Serviceinterfaces from the methods.

On the operating system’s desktop,double-click on the icon „SAPNetWeaver Developer Studio“.

Open the perspective “CompositeApplications” from the window menu incase it isn’t open already.

The project used in this demo is called“basis.core.register (sap.com)”.Expand the root node.

Notice: In case the project is closed (bysomebody else), go the tab page“Navigator”. A CAF core project consistsof 6 subprojects (identified by name“basis.core.register…”) – select them alland open them from the context menu.Then go back to the tab page “ServiceExplorer”.



© 2007 SAP AG 8

To recapture the entity models and theirrelationship, open the Entity “Employee”.

The core of the application is an entitycalled “Employee”. This employee objecthas a 0...n relationship to “Equipments”(hardware). In words, this means anemployee can have 0 or more equipmentitems registered.



© 2007 SAP AG 9

On the tab page “Operations” you willfind the automatically created life-cycleoperations as well as the custom madeoperation “findByPersonalID”.These operations are used by thebusiness logic (the “application services”)of the CAF application.

Now, back to the service enabling of thisapplication. The logic is implemented inthe application service “RegisterApp” indifferent operations. Some of this will nowbe service enabled.

Double-click on the application service“RegisterApp” to open it.



© 2007 SAP AG 10

On the tab page “Operations” you canfind all implemented service operations ofthe application. These are all potentialcandidates to be exposed as webservices, but in our case we will need onlytwo of them:“FindEmployeeOnlyByPersonalID”

and“FindEquipmentOnlyByPersonalID”

These operations will later be used in amanager’s UI (created with VisualComposer) to retrieve the informationstored by the employee.

To actually enable the application tocreate Web Services, the application mustbe marked accordingly.

Go back to the tab page “General” andcheck-mark the option “Remote EnabledService”.

Notice: This is a one-time effort – the nexttime you run the demo, both options willhave the checkmark and be disabled.



© 2007 SAP AG 11

Save the metadata before you continue

(click on ).

To create the interfaces, select theapplication service „RegisterApp“ andopen the context menu.Select “Web Service“ and then “New“.

Select the inputfield “Web ServiceName“ and type in the name“RegisterAppBasisWS“.

Continue with „Next“.

Notice: The next time you run this demoyou will have to choose another name –e.g.“RegisterAppBasisWS1“. Rememberthis when you select the Web Service inthe next demo session.



© 2007 SAP AG 12

All available service operations are listed.From this list, first “Deselect All” and thenselect the two operations“FindEmployeeOnlyByPersonalID”

and“FindEquipmentOnlyByPersonalID”

Continue with “Next”.

The definition of the interface is createdautomatically.Leave the defaults and press „Finish“.

All interfaces and descriptions will now becreated.



© 2007 SAP AG 13

The result can be found in the “WSDeployment Description Editor” which isopened automatically after creation.

Notice: In case you already created WebServices, these will also be listed here.

The project is now ready to be build anddeployed.

From the project root, open the contextmenu, select ”Development Component”and then ”Build”.

Confirm any popup and wait until theproject has been build.

To deploy the application, again select theproject root, open the context menu andselect “Deploy to J2EE engine”.



© 2007 SAP AG 14

Eventually, you will be asked for the SDMpassword (which is found in chapter 0Users).

The deployment is ready when all 5projects have been deployed.

To test the newly created web services,open a browser and from the start pageselect the link: ”Web ServicesNavigator”.

Notice: The start page ishttp://ivml2005:50000/index.html

http://ivml2005:50000/index.html



© 2007 SAP AG 15

From the Web Services Navigator page,scroll down to Web Service you justdefined – e.g. RegisterAppBasisWS –and open it.

The overview page gives you informationabout the service like the WSDL (neededin the next demo session).

To test the service, click on the link„Test“.



© 2007 SAP AG 16

The two operations can now be testeddirectly.Click on the link“FindEmployeeOnlyByPersonalID_R”.

Enter the personalID “14132” and click on“Send” and watch the response.

The Web Service is now ready for use.

Demo Part 3 – Creating a Visual Composer application

OverviewThis demo session shows how to create a new user interface for the manager’s overview page based onexisting web services.

The session covers the steps of creating a new application by integrating the Web Service and creates auser interface based on these web service operations. This is done using Visual Composer and finally, theapplication will be made ready for use in a Guided Procedure.

Detailed navigation

Steps

Before you start: Notice that this session requires that Web Services have already been created (seeDemo Part 2).



© 2007 SAP AG 17

Optional step: As an introduction to thesession you can recapture the last step ofDemo Part 2 to show the Web Servicebeing tested.

To test the newly created web services,open a browser and from the start pageselect the link ”Web Services Navigator”.

Notice: The start page ishttp://ivml2005:50000/index.html.

Optional step:From the Web Services Navigator page,scroll down to Web Service you justdefined – e.g. RegisterAppBasisWS –and open it.

http://ivml2005:50000/index.html



© 2007 SAP AG 18

Optional step:The overview page gives you informationabout the service like the WSDL (neededin the next demo session).

To test the service, click on the link„Test“.

Optional step:

The two operations can now be testeddirectly.Click on the link“FindEquipmerntByPersonalID_R”.

Optional step:Enter the personalID “14132” and click on“Send” and watch the response.



© 2007 SAP AG 19

Log on to the Visual Composerapplication as an administrator(CTB_ADMIN).

Notice: Link http://ivml2005:50000/VC.

From the Menu “Model” select “NewModel”.

Use “HardwareOverview” as name of themodel.Confirm with “OK”.

Notice: Select another name in case thishas already been used, but remember thisname for the next session.

From the Components overview, select“iView” and drag-and-drop this onto theVisual Composer canvas.

http://ivml2005:50000/VC



© 2007 SAP AG 20

Rename the iView to “iViewOverview” (orchoose a name of your own).Double-click the iView-component toaccess the next level (inside the iView).

Start with integrating the Web Servicecreated in the previous session.

From the Menu “Tools”, select “DefineWeb service system”.

Name the system and the system alias“CAF_BasisWS2”.

Notice: If already used, select anothername and alias, but remember to use thiswhen selecting a data service later in thissession.

Shift back to the browser and from theWS Navigator you used before, selectthe WSDL link.



© 2007 SAP AG 21

Shift back again to the Visual Composerapplication and paste the WSDL link intothe field “Web Service URL”.Be aware of any spaces after the “wsdl”!

Check-mark the option “URL requiresuser and Password” and enter theadministrator (CTB_ADMIN) as user.

Confirm with “Create”.

Notice: This system is now defined in thesystem landscape of the portal and canbe administrated from there.

Now click the button “Find Data” andselect the system you defined from thelist of Data Services.

Press “Search” to get a list of all availableoperations.

Select the first operation and Drag-and-Drop it onto the canvas.Repeat it for the next operation.

The operations are now available as“Data Services”.

All meta data around the operations likeinput/output-parameters are retrievedautomatically.



© 2007 SAP AG 22

You can test the service directly from thecanvas to check if everything is ok.

Select the Data Service and from thecontext menu, select “Test Data Service”.

In the field “PersonalID”, enter “14132”.

Press “Execute” and watch the response.

Press “Close” when finished.

You can now repeat this for the otherData Service.

Now that the Data Services have beenidentified and tested, the UI developmentcan start.

Select the node “Input” from the first DataService and Drag-and-Drop a line fromthis node.When you release the left mouse, youwill find a context menu, from where youselect “Start Point”.

Notice: This start point is where theinformation of a Guided Procedure stepwill be passed in to this application – e.g.a user’s ID. In case a user interaction isrequired, an “Input Form” could be usedas an additional input source.



© 2007 SAP AG 23

Check-mark the field “personalID” andconfirm with “OK”.

The information is retrieved from themetadata of the Data Service and showsall available parameters as options for thestart point. The input parameter of thestart point is created automatically basedon this selection. The same would countfor an Input Form in case this type wouldhave been selected.

From the other Data Service, select thenode “Input” and Drag-and-Drop a line tothe same Start Point.

Later, when this application is called froma Guided Procedure step, the start pointwill automatically call both Data Servicesand pass its parameter (the “personalID”).

To display the result of a Data Servicecall, select the “Response” node form thefirst Data Service and Drag-and-Drop aline from this node.Select “Add Form View” from the contextmenu.Rename the view to “Employee”.



© 2007 SAP AG 24

From the second Data Service, select the“Response Equipment R” node andDrag-and-Drop a line from this node.

Select “Add Table View” from the contextmenu.

Rename the view to “Equipments”.

To optimize the layout of the iView, selectthe tab page “Layout” and redesign thetwo components as appropriate.

The layout could look similar to thescreenshot to the right.

To enable the Guided Procedure to usethe start point of this application as atarget for mapping, this application has toprovide some Guided Procedure specificinformation.Form the “Tools” Menu, select “Options”.



© 2007 SAP AG 25

On the tab page “Compiler”, check-markthe option “Add Guided ProcedureInformation”.

Confirm with “OK”.

The final step is to deploy the applicationto the Web Application Server.

Select the button “Deploy”.

If the deployed succeeds, you have theoption to run the iView directly. Butremember that the application doesn’thave any input parameter at this time, sothe response will be empty.You can change this by either make adefault entry for the start point parameteror add an input form in parallel to the startpoint to manually enter the personalID.

The Visual Composer application is now ready, but there is one more step to do before theapplication can be used in a Guided Procedure. And this is to add the iView to a specific portal userrole.



© 2007 SAP AG 26

Log on to the Enterprise Portal as anadministrator (CTB_ADMIN) and selectthe Workset “Content Administration”.

In the folder “Portal Content”, select“SAP Discovery System”, then“Composite Toolbox” and finally “Roles”.

Open the role “ToolboxManagerRole”(right click and “Open Object”).

Now, navigate to the folder“Visual Composer/ Models/HardwareOverview/iViews”and select the iView “iViewOverview”.

Select the role “ToolboxManagerRole”again and from the context menu, select“Add iView to Role” and then “DeltaLink”.

The Visual Composer iView is nowassigned to the ToolboxManagerRole.You will see why in the next session.



© 2007 SAP AG 27

Demo Part 4 – Extending the Guided Procedure

OverviewAt this time, all components have been created and enabled and can be used in the existing GuidedProcedure.

The focus of this session is to show how to create an extension to an existing Guided Procedure with theusage of existing building blocks and development of new Guided Procedure objects.

Detailed navigation

Steps

Before you start: It is recommended to have a clean working folder, so in case you didn’t do so aftera previous session – do it now…The folder is „CompositeToolbox/Basis/ xDemo“.

Log on to the Enterprise Portal as anadministrator (CTB_ADMIN).

Open the Workset „Guided Procedure“and the „Design Time“.

In the Guided Procedure „Gallery“, selectthe folder„CompositeToolbox/Basis/xDemo“.

All new GP-objects will be created in thisfolder.

Notice: All other components needed forthe demo in part 1 are spread around theother folders „Actions“, „Blocks“ and soon. These components will be reusedhere.



© 2007 SAP AG 28

From the Gallery, select the link „CreateProcess“.Press „Create“ on the popup-screen.

Notice: A new process is created for tworeasons: 1. To not interfere with theexisting one (the basis) and 2. two beable to show both at the same time.

Change the name of the process to„MyFirstDay_after“.

Save the changes.

Add the existing block from the basisprocess.

Press the button .



© 2007 SAP AG 29

From the folder„CompositeToolbox/Basis/Blocks“, selectthe block „Welcome“.

Press the button „Select“.

Now, create a new block which later willcontain the new UI.

Press the button .

Press „Select“ on the popup-screen.



© 2007 SAP AG 30

Rename the block to „Information“.

Save the changes.

While keeping the block „Information“selected, press the button to add anew „action“ to the block.



© 2007 SAP AG 31

Select the line “Action 1“.

Rename the action to “HardwareInfos“.

Save the changes.

While keeping the action“HardwareInfos“ selected, press thebutton to add a new „callable object“to the action.

From the folder ”User Interface”, selectthe callable object type ”Portal iView orPage”.

Name and description of the callableobject should be ”CO_HardwareInfo”.

Continue with ”Next”.



© 2007 SAP AG 32

In the list of available roles, scroll downto the role „ToolboxManagerRole“ andselect it.

All assigned iViews and pages areshown under the role.

Select the (only) iView „iViewOverview“.


Based on the information from this iView– and in particular from the applicationunderneath the iView – all availableparameters are shown. Remember theparameter „personalID“ which wasprovided by the Data Service in thesession 3.





© 2007 SAP AG 33

Add a “Result State Button” with name“Complete“.

Notice: This button is rendered on thecallable object to enable the user tocontinue in case the object behind thecallable object doesn’t trigger it itself.This is the case for the Visual Composerscreen created earlier.

Press “Finish“ to complete the definitionof the callable object.

Save all changes again.

At this point, all existing and newcomponents are added to the GuidedProcedure. The next thing to do is tomap the parameter between the blocks.

Select the process „MyFirstDay_after“and select the tab page „Parameters“.



© 2007 SAP AG 34

From the liste of parameters, select the„User/userID“ from „Welcome“ and„Input_Parameters/personalID“ from„Information“.

Press the button „Group“.Name it „Map_Welcome_Information“and uncheck the “Exposed in” and“Exposed out” checkboxes.Save the changes.

We now have a mapping between theinformation retrieved in the first block –the portal-ID of the user – and the inputof the Visual Composer UI created in thelast session.

To clean up some information, the rolesof the different actions can beconsolidated into a single role.

Keep the process „MyFirstDay_after“selected and select the tab page„Roles“.

Check-mark all roles except for the lastone – the „Processor of HardwareInfos“.

Type in „Processor of Actions“ andpress „Go“ to consolidate into one singleaction (which later will be assigned to theemployee user).

Save all changes.



© 2007 SAP AG 35

To keep the demo as simple as possible,we can assign default users to all of theactions. In real life, some of them wouldhave to be assigned at runtime and otherwould be assigned to portal roles.

Select the tab page ”Default Roles”.

Select the ”Processor of Actions” andpress ”Add Default”.

From the „Add Users“ view, search for„14132“ and „Add“ this user to thedefault role.

Add the user „CTB_ADMIN“ to the restof the default roles including the role„Processor of HardwareInfos“.

In this demo, „CTB_ADMIN“ is bothacting as an administrator and as theemployee’s manager“.

Save all changes.The process is now ready for use andcan be activated.

Press the button to do so.



© 2007 SAP AG 36

To test the new process, it can be starteddirectly from the Design Time of theGuided Procedure.

Open the last tab page – „Instantiation“.

Check-mark the option „Start ProcessAutomatically“.

Press the button „Generate InstantiateURL“.

And press the button „Open InstantiateApplication“ to actually run the process.

A popup screen tells you that theprocess has been started and is readyfor processing.

At this point we are back to where westarted the demo, but the process is anew one.

Log on to the portal as an employee(14132).

Navigate to the workset „Work“ and thenclick on the link “Welcome to ITeLO”.



© 2007 SAP AG 38

This step becomes now more relevant tothe process. All equipments nowregistered by Jamie will be shown later

Add some equipments, save andcontinue with the button “Complete”.

Proceed with the button “Complete”.

The process has now been completed -at least for Jamie.

Let’s log on as a administrator again, but this time CTB_ADMIN will act as the manager of Jamie.

Navigate to the workset „Work“.There will be a task waiting for themanager. This is the new step created inthis session – the Hardware info screen.Click on the link “HardwareInfos”.



© 2007 SAP AG 39

The application created in session 2 isnow called and the parameter from theemployee’s step is passed on to theapplication and subsequently to the CAFapplication.

And the result is exactly those itemsJamie added a few seconds ago –displayed in another UI and added to anexisting process with an additional role.

Press the button “Complete”.



© 2007 SAP AG 40

Copyright© 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 theexpress permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software componentsof other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli,Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks ofIBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks ofAdobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology inventedand implemented by Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentionedare the trademarks of their respective companies. Data contained in this document serves informationalpurposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warranty of anykind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.These materials are provided “as is” without a warranty of any kind, either express or implied, including butnot limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, orconsequential damages that may result from the use of these materials.SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other itemscontained within these materials. SAP has no control over the information that you may access through theuse of hot links contained in these materials and does not endorse your use of third party web pages norprovide any warranty whatsoever relating to third party web pages.Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples andare not intended to be used in a productive system environment. The Code is only intended better explainand visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and



© 2007 SAP AG 41

completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by theusage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

demonstrating caf

Documents