exercise 1: how to use enterprise services - sap

EXERCISE 1: HOW TO USE ENTERPRISE SERVICES – EXPLORE, TEST, AND INTEGRATE EXERCISES / SOLUTIONS SAP Discovery System version 3 In this exercise, the Purchase Order confirmation page of the procurement scenario is extended. The goal is to display additional information of the Purchase Order like “PO date” and “transfer location” which exists only in the ERP backend and therefore will be consumed by the UI layer using an Enterprise Service. This will be accomplished leveraging Enterprise Services from end to end, how to find the relevant enterprise service, how to test it and finally how to integrate it to the process using “SAP Guided Procedures” and “SAP Visual Composer”.

Legend Users, Passwords “bold with double quotes”

Screen Elements used for navigation Bold

Variables Italic

Values to be entered “Italic with Quotes”

How to Use Enterprise Services Exercise

Table of Contents 1. Finding the “Read Purchase Order” Enterprise Service............................................................................3 2. Testing and Consumption of the READ Purchase ORDER Enterprise Service ...........................................6 3. Mapping of the Read PO Step Inside the Procurement Process..............................................................13 4. Create a UI for Displaying Purchase Order Details ................................................................................16 5. Add the Visual Composer Screen to the Guided Procedure Process ......................................................26 6. PARAMETERS MAPPING OF THE SHOW PO DETAILS UI...........................................................................29 7. CONSOLIDATE THE PROCESS ROLES ........................................................................................................37 8. RUN THE PROCESS ...................................................................................................................................38

1. Finding the “Read Purchase Order” Enterprise Service IN THIS SECTION, YOU WILL SEARCH FOR ENTERPRISE SERVICE THAT CAN PROVIDE DATA ON EXISTING PURCHASE ORDERS IN THE ERP SYSTEM.

You first need to login to the ES Workplace and find the relevant Enterprise Service

1.1 Login to the ES Workplace using http://iwdfvm2160.wdf.sap.corp:51080/socoview In case a login windows appears then type in user “Admin” and password “Admin” You will see the home page of the ES Workplace.

1.2 In the ES Workplace home page, click on the link Enterprise Services by Process Components. You will see the following screen specifying the different process components.

FYI – The ES workplace is a one-stop enterprise SOA information and evaluation environment where you can browse, test-drive and use productized enterprise services. It represents the public Enterprise Services Repository and uses the service registry which is an advanced UDDI 3.0 implementation. ES workplace closes the gap between Information Technology and Business by providing both the business capabilities and the technical definition of Enterprise Services

http://iwdfvm2160.wdf.sap.corp:51080/socoview�


1.3 To understand the details of an existing purchase order from the ERP system, click on the Purchase Order Processing link in the Process Components in ERP section.

1.4 Click on the Manage Purchase Order In link

1.5 You now find the needed Enterprise Service: Read Purchase Order. Click on the Read Purchase Order link

1.6 In the following screen you can see all the technical information of the service. To see what is the input and output of the service click on the detailed field description link

1.7 Click on the Click To Toggle Details links of the Input Message and Output Message to find out which parameters this service expects as input and what is the response the service returns

1.8 Now you are ready to see the technical WSDL file of the service. Click back on the browser window

1.9 Click on the link ECC_PURCHASEORDER002QR that will show you the WSDL file of the service directly from the ERP

system of the Discovery System

1.10 You have successfully found your needed Enterprise Service. Save the URL of the WSDL file since you will need it later on in the exercise


2. Testing and Consumption of the READ Purchase ORDER Enterprise Service IN THIS SECTION, YOU WILL CREATE A GUIDED PROCEDURES WEB SERVICE CALLABLE OBJECT FOR THE “READ PURCHASE ORDER” ENTERPRISE SERVICE AND TEST IT.

Overview After finding the “Read Purchase Order” Enterprise Service, you will integrate it to the Guided Procedures procurement scenario and display additional purchase order details. You will need to add 2 additional steps to the process:

- Read PO - The consumption of the “Read Purchase Order” Enterprise service which will be executed as a background step. - Show PO Details – UI step that will show the PO details retrieved by the Enterprise Service consumption step.

Parameter Mapping Overview In order to move data from one step to another, you will need to map input parameters from one step to the output parameters of the next step. During runtime the parameters values will flow between the steps.

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step

Read PO Bkg Step

Show PO Details UI Step

Read PO Bkg Step


You will create and add 2 new steps in order to display some Purchase Order data

Existing Steps New Steps

• UI Step is a step that can be seen by the user at runtime.

• Bkg Step is a step that runs in the background and cannot be seen

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step

Read PO Bkg Step


Inputs/Outputs Mapping

2.1 Open a browser window and navigate to the portal using: http://iwdfvm2160:51000/irj/portal

- Login into the portal using user: “proc_agent0X.” X is a number assigned to you at the beginning of the workshop

E.g. proc_agent01 or proc_agent02 etc. … The user password is “sap123”

2.2 Go to the tab Guided Procedure and to the Design Time tab

2.3 Now you are going to work on existing process.

In the Guided Procedure (GP) gallery, select the folder Teched07 Exercise.

In the folder Teched07 Exercise: - Select the folder StudentX (X is the number assigned to you) - Select the process called: StudentX Ex1 Procurement Without Approval Without PoDetails V3 - Click on the Open button at the bottom-right.

FYI: Guided Procedure (GP) is the SAP tool for composing custom user-centric business processes. The Design Time tab is for editing a process

http://iwdfvm2160:51000/irj/portal�


Now you see the business process that you are going to edit. It currently has 3 blocks: Analyze, Get Quote, and Create/Read PO.

2.4 Select the process object, the one at the top of the table named : StudentX Ex1 Procurement…. (See above)

If you don’t see these buttons next to the save button then click on the toggle button to switch to the editable mode. If you get popup window shown below, click on Yes:

Now you are ready to edit the process. Your goal is to consume the READ PURCHASE ORDER Enterprise Service from this process. We will consume this Enterprise Service after the step that creates the purchase order.

Action Creation (process step) for consuming the Read Purchase Order Enterprise Service

2.5 Select the Create/Read PO block in the table 2.6 If you don’t see these buttons next to the save button then click on the toggle button

(first from the left) to switch to the single editable mode.

2.7 Click on the icon for creating a new Action (process step), by default it will create an Action with the name Action1

2.8 Select the Action1 and go to the Basic Data tab at the bottom of the screen.

2.9 Rename the Action Name Action1 to ReadPODetails

Callable Object Creation for consuming the READ PO Enterprise Service

2.10 Click on the icon for creating a new Callable Object (CO) 2.11 Now you need to choose the type of your Callable Object (CO), you want to consume an Enterprise Service.

Choose a callable object of type Web Service (see picture below)

2.12 Enter a CO name ReadPO_WS_CO and any description text.

2.13 Click Next (bottom of the screen)

FYI: A callable object (CO) a “proxy” to a service or to a UI screen. A callable object (CO) can be a background step or a UI screen. By building this callable object you can add an UI or a background step into your user-centric GP process.


2.14 Copy/paste the WSDL URL of the READ PURCHASE ORDER Enterprise Service you found on the previous section and click go

http://iwdfvm2160:51080/sap/bc/srt/xip/sap/ECC_PURCHASEORDER002QR?sap-client=200&wsdl=1.1

2.15 Select the WS properties PurchaseOrderByIDQueryResponse_In, the second item in the picture below

If you wish you can see the input and output interfaces by clicking on the Input and Output tabs 2.16 Click 3 times Next and then Finish

Testing the Enterprise Service through the Callable Object You have just created a Web Service Callable Object in GP that consume the Read Purchase Order Enterprise Service. Now we want to test the CO to make sure that it consumes properly the Enterprise Service.

2.17 Before testing save your process. Select the process object (at the top of the table ) and click Save All

FYI – It is also possible to test the Enterprise Service using the Web Service Navigator page of NetWeaver. In this exercise, you will test the service using Guided Procedures test tool

http://iwdfvm2160:51080/sap/bc/srt/xip/sap/ECC_PURCHASEORDER002QR?sap-client=200&wsdl=1.1�

2.18 Select the ReadPO_WS_CO Callable object (inside the Create PO block) and select the Test tab:

Now we need to enter an input value to the Read PurchaseOrder service. Enter the Purchase Order number “4500000350” in the simpleContent field and click execute:


2.19 You should get similar results (as seen as below).

FYI :The Read Purchase ORDER Enterprise Service response structure is complex and not flat. Within one Purchase Order multiple items can be listed.

3. Mapping of the Read PO Step Inside the Procurement Process IN THIS SECTION, YOU WILL MAP THE READ PURCHASE ORDER STEP TO THE GUIDED PROCEDURES PROCUREMENT SCENARIO

The Enterprise Service consumption works. In the next step you need to map the Purchase Order number coming from the create Purchase Order step to the input of the READ PURCHASE ORDER Enterprise Service. We need to do this mapping so during runtime the Purchase Order number will be passed to the ReadPODetails step that you just built.

3.1 Select the Create/Read PO block and click on the Parameters tab. Here you see the list of inputs and outputs of all steps that exist inside the Create/Read PO block.

Create PO Step

Read PO Step

Po number


3.2 Select the Purchase Order number that comes out of the CREATE PURCHASE ORDER Web Service (CreatePO_WS_V3) and map it to the Purchase Order number input parameter of the READ PURCHASE ORDER Enterprise Service (ReadPODetails). Select the parameters shown below and keep pressing the Ctrl-key for making a multiple selection.

3.3 Click on the Group button , rename the group name with “poNum” and click on Create Edit the technical name of the Read PO input and output structure FYI: You will edit the technical name of the Read PO input and output. This will be useful later on in the exercise when you will need to map the output of the Read PO step to the input of the Show Details UI step. By having meaningful technical names, it will help us to find the right parameters to map. 3.4 Your Create/Read PO block has to be selected 3.5 Select the Parameters tab and click on the Show Details button

3.6 Edit the Technical Name: o replace Input_Parameters for ReadPODetails by “ReadPO Input_Parameters” o replace Return_Parameter for ReadPODetails by “ReadPO Return_Parameter”

(See picture below) 3.7 Save your process. Select the process object (at the top of the table ) and click Save All

You finished this part of the exercise. You found an Enterprise Service, you consumed it from GP and add it as step into a user-centric business process and you mapped its input parameter element. In the next section you will build a UI screen for displaying PO data.

You can close your Internet Explorer Browser.

Edit the technical name


4. Create a UI for Displaying Purchase Order Details IN THIS SECTION, YOU WILL CREATE A VISUAL COMPOSER MODEL THAT WILL DISPLAY THE PURCHASE ORDER DETAILS Now you want to build a second step in our process. You will use the Visual Composer (VC) tool for creating a form that will display the data that came back from the Read PO Enterprise Service. This UI will be inserted inside our business process as a step. The UI at runtime will be based on the SAP Web Dynpro technology. In this section you will need to:

A. Create the input parameters of the step B. Create UI elements to display the data C. Create an output parameter D. Compile and deploy the model

Open the VC model

4.1 Open your browser and go to the URL: http://iwdfvm2160:51000/VC 4.2 Login as proc_admin0X, password: sap123

4.3 From the toolbar menu on the top, select Open Model. 4.4 Open StudentX_PO_Details_exer1.mdl VC model that is under the folder Public->Procurement_V3 (see

picture below) by double clicking on it.

Outputs: - Po number

Inputs: - Po number - Po Date - Product Name - Quantity - Transfer Location


FYI: An empty VC model is already provided; its name is StudentX_PO_Details_exer1 (when X is the number assigned to you).

http://iwdfvm2160:51000/VC�

Compiler setting: In the menu , select Tools and then Options

Select Web Dynpro as a runtime and check the “Add Guided Procedure information”.

FYI: These 2 setting will allow the UI that you are going to build to have the Web Dynpro look &feel and the capability to be integrated to CAF Guided Procedure composition tool


4.5 Click on the Compose button on the right 4.6 Drag the iView component to your design page (see picture below)

4.7 Rename the iView name to “PO Details” 4.8 Double-click on the iView 4.9 Drag a Form view into the design area

Create the input parameters of the step

4.10 Drag a Start component to the design area: 4.11 Double-click on the Start component and you will see on the bottom-right an input parameters window:


4.12 In the Input Parameter window, click on the ”+” sign and create a parameter of type Date and name

“poDate” (see picture below): 4.13 Create 5 more parameters of Data type Text , see the name of the parameters in the picture below:

4.14 Connect the Start point to the Form1 input by dragging a line from the left point of the start component to the in plug of the Form1 component.

FYI: - Now we are going to create input parameters. These input parameters will be available later in GP when we will add this UI as a step in our GP process. - We adjusted the compiler settings to deploy models as WebDynpro. It is possible to choose in Visual Composer between Adobe Flash output and WebDynpro output. Also, we set the parameter to add Guided Procedure information.

Create UI Elements to Display the Data

4.15 Select the form component Form1 and on the bottom-right click on Select All (see picture below). This will add these parameters as TextField UI element on the Form layout.


4.16 Add a Button of type Pushbutton to the Field list by click on the + sign.

Create an Output Parameter

4.17 Select your form component and drag from the output of the form an End point (see picture below) and select poNum as output (see second picture below):

FYI: Once this UI will be as a step in GP, this button will be used for completing this UI step in GP.

4.18 Select the Form View component. 4.19 Double-click on the Finish field in the Field window (bottom-right). 4.20 In the Control Properties window, select the Action tab; select the System action radio button and Submit form as System action. 4.21 Select the line that connects the Form to the End point and select from the Event name: drop-down, the “submit”

entry.

FYI: In GP, when the button will be pressed it will trigger the event submit and go to the end point and will complete the step.


4.22 Click on the link between the form and the end point. On right side, replace the event name “evt1” by the “submit” event.

UI Layout Design 4.23 Save your model. 4.24 Click on the tab Layout, you will the input parameters as UI InputField element. Now you need to edit the

InputField label and size. Double-click on the field, go to Display tab and edit the label and the label position to Long Label (see picture below).

If the labels seem to be truncated after changing the label position, fix it by dragging the labels to the right.

Compile and Deploy the Model

4.25 Once you finished to set the UI, save your model. 4.26 Now you are ready to compile and deploy your VC model. On the right side, click on deploy icon. 4.27 Click on Deploy button.

You should get the following results:

You finished this part of the exercise. You create a form using Visual Composer. You defined inputs and output to the form and you deployed it. In the next chapter you will add this form as a step in the GP process. You can close you Internet browser.

FYI: The VC model was deployed as WD4VC component; it means at runtime, the application will have the same Look and Feel as a Web Dynpro UI.


5. Add the Visual Composer Screen to the Guided Procedure Process IN THIS SECTION, YOU WILL ADD THE VISUAL COMPOSER SCREEN TO THE GUIDED PROCEDURES PROCUREMENT PROCESS You finished building a screen for displaying to PO values. Now you need to add this screen into the GP process, the one that you edited at the beginning of this exercise.

5.1 Go the portal: http://iwdfvm2160:51000/irj/portal Login into the portal using user: “proc_agent0X”, when X is a number assigned to you at the beginning of the workshop. The user password is “sap123”

5.2 Go to the tab Guided Procedure and to the Design Time tab

5.3 In the Guided Procedure (GP) gallery, select the folder Teched07 Exercise.

In the folder Teched07 Exercise: - Select the folder StudentX (X is the number assigned to you) - Select the process called: StudentX Ex1 Procurement Without Approval Without PoDetails V3 - Click on the Open button at the bottom-right. Now you see the business process that you are going to edit

5.4 Select the process object, the one at the top of the table named: StudentX Ex1 Procurement…. (See above)

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step


Read PO Bkg Step


You add your UI screen to the GP process

Existing Steps New Step

http://iwdfvm2160:51000/irj/portal�

5.5 Click on the toggle button to switch to the editable mode. 5.6 If you get a popup window shown below, click on yes:

5.7 We will create a block and inside it we will add the UI that you built previously as a step. 5.8 Click on the new icon for creating a new Sequential Block 5.9 Click on Select

5.10 Select the new block created (Block1) and renames it to PO Details in the Basic Data tab at the bottom.

5.11 Click on the new icon for creating a new action.

5.12 Select the new action created (Action1) and renames it also to PO Details in the Basic Data tab at the bottom

5.13 Click on the new icon for creating a new Callable Object. 5.14 Select from the CO type list , WD4VC (Wed Dynpro for Visual Composer) and name the CO as “showPODetails_WD4VC_CO”

FYI: Your VC model was deployed as WD4VC component, that’s why we need to create a CO of type WD4VC for exposing in GP the VC UI that you previously built.


5.15 Click Next. Select the VC model that you previously deployed. The one with “StudentX” (when X is the number assigned to you)

5.16 Click Next, Next again, and click Finish

6. PARAMETERS MAPPING OF THE SHOW PO DETAILS UI IN THIS SECTION, YOU WILL MAP THE OUTPUT PARAMETERS OF THE SHOW PO DETAILS STEP TO INPUT PARAMATERS OF PREVIOUS STEPS You have created a step in GP that will display the “PO Details” form. In order to be able to see values inside the form during runtime, you need to map the input parameters of the PO Details to the relevant output parameters. This is what you are going to do in this section.

6.1 Select the process object (at the top of the table) , click the Save All button

6.2 Select the Parameters tab

Product Name Parameter Mapping

6.3 Scroll down in the parameter list until you find the Input_Parameters of PO Details parameter:

You will map the productName group existing in the GP context to the input of the PO Details UI Step

productName output

productName input

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step

Read PO Bkg Step


Existing Steps New Steps that you have added

Guided Procedure Context . ProductName variable

(Group in GP)


6.4 Click on the arrow to expand the node. You will under this node the parameter productName :

Select the productName parameter that is under the Input_Parameters of PO Details

6.5 For multi row selection. Press the Ctrl key on your keyboard and select the ProductName Group. 6.6 Once both rows are selected, click on the Add to Group button

PO Date Parameter Mapping The PO date is an output that is returned by the Read PO Enterprise Service. You will need to map it to the PO Date input parameter of the PO Details Step.

6.7 In the Parameters tab, click on the button Show Details

6.8 Now you can see the Technical Name column in the table. Look in the parameter table for the Return Parameter

with technical name equal to ReadPO Return_Parameter

6.9 Click on the arrow to expand the first node and immediately expand Purchase Order node. (see picture below)

6.10 Select the parameter called PurchaseOrderDate (see picture below)

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step

Read PO Bkg Step


PurchaseOrderDate output

poDate input

Mapping


Select the poDate Input Parameter of the PO Details Step Now you want to select the parameter that is an input of the PO Details step. 6.11 Scroll down to the parameter Input_Parameters defined for PO Details (do not select the row) 6.12 Click on the arrow to expand the node, press the Ctrl key on the keyboard (for multi row selection) and select

the parameter called poDate (select the row). Now we have 2 parameters selected poDate and PurchaseOrderDate

6.13 Now the button Group should enable, click on it. Leave the name as poDate and click on Create

TransferLocationName Parameter Mapping Now you will map the transferLocation parameter from the output of the Read PO Enterprise Service to the input of the PO Details UI step. Select the TransferLocation Output Parameter of the Read PO Step 6.14 In the Parameters tab, click on the button Show Details

6.15 ow you can see the Technical Name column in the table. Look in the parameter table for the Return Parameter

with technical name equal to ReadPO Return_Parameter 6.16 Click on the arrow to expend the nodes :

6.17 Expand the first node Return Parameter.

Expand Purchase Order node.

Expand DeliveryTerms Expand Incoterms

6.18 Select the parameter called TransferLocationName (see picture above)

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step

Read PO Bkg Step


transferLocation output transferLocation

input

Mapping


Select the transferLocation Input Parameter of the PO Details Step Select the parameter that is an input of the PO Details step. 6.19 Look for the parameter Input_Parameters defined for PO Details (do not select the row) 6.20 Click on the arrow to expand the node, press the Ctrl key on the keyboard (for multi row selection) and select

the parameter called transferLocation (select the row). Now we have 2 parameters selected.

6.21 The button Group should enable, click on it. Leave the name as transferLocation and click on Create.

PO Number Parameter Mapping Display the PO number that was created by the Create PO background step. To do so, you need to map the poNum output parameter of the CreatePO Bkg step to the poNum input parameter of the PO Details UI step. 6.22 In the parameter tab, make sure that the button Show Details is pressed. 6.23 Look for the parameter named Return Parameter with CreatePO_WS Return_Parameter as technical name.

(see picture below) 6.24 Expand the node by clicking on the arrow 6.25 Select the Response parameter row of the Create PO (see picture below)

6.26 Look for the parameter named Input_Parameter defined for PO Details. (see picture below) 6.27 Expand the node by clicking on the arrow 6.28 Press the Ctrl key on the keyboard (to perform multi row selection ) , Select the poNum parameter row of the PO

Details (see picture below)

6.29 With both rows selected, click on the Group button, give the name “poNum” and click on Create.

Create PO Bkg Step

GetQuote UI Step

GetSupplier UI Step

Analyze UI Step

Read PO Bkg Step


poNum output

poNum input

Mapping


6.30 You finished the mapping of the parameters. Click the Save All button 6.31 In the parameter table. You need to uncheck all the checkbox in the column Exposed in.

Make sure that you drill-down with the scrollbar and unchecked all the Exposed in checkboxes.

.

FYI: If a parameter has the “Exposed in” checkbox selected, then it means that this input parameter will be exposed outside of the process and you will be required to input a value when the process will be initialized.

7. CONSOLIDATE THE PROCESS ROLES IN THIS SECTION, YOU WILL CONSOLIDATE THE PROCESS ROLES TO MAKE SURE IT WILL RUN SMOOTHLY BY THE PROCUREMENT AGENT To each step a user role can be assigned. In our case we have only one user and it is the proc_agent. For avoiding the need to assign the proc_agent to each GP step, we can consolidate all the steps into a group. Then a user can be assigned to the group. In our case, by default, the process initiator will be the one assigned to the group.

7.1 Go to the role tab 7.2 Select the 2 rows as shown in the table below 7.3 Type into the “consolidate to” text field the value “Procurement Agent” 7.4 Click on the Go button 7.5 Click the Save button.


8. RUN THE PROCESS IN THIS SECTION, YOU WILL RUN THE PROCESS AND SEE THE RESULTS OF YOUR PREVIOUS SECTIONS Save All and Activate the process

8.1 Click on the “Save All” button and then on the “Activate”

You will see warning messages in the bottom of the screen stating that some of the objects are deprecated. Ignore these messages. Initiate the process

8.2 In the portal, go to the Runtime tab.

8.3 In the middle of the page, click on Initiate a New Process.

8.4 Select your process that is under Teched07 exercise - studentX (X is your number) - StudentX Ex1 Procurement….

8.5 Click Next 8.6 Click Initiate

The process will start after less than a minute, go through all the steps: .

Step 1: Analyze stock, select the material group “Gadgets” and then select product “COOL TOOL”. Click on start purchase button Step 2: Select one supplier Step3: Enter amount to order and click next

Step4: Now in the background, the CreatePO Enterprise Service and the Read PO Enterprise Service are executed. Click on the refresh button until you get the UI showing the PO details. Step5: The last step of the process is the PO Details UI that you created showing the PO Number, PO Date, Product Name, and transfer location. The screen that you built displays the data coming from the Create PO Enterprise Service, from the Read PO Enterprise Service and data coming from the GP process context.


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 changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors. Microsoft, Windows, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe 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 or registered

trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,

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 invented and

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 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 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. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement 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 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 limitation shall 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 these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

SAP assumes no responsibility for errors or omissions in these materials

exercise 1: how to use enterprise services - sap

Documents