RF Framework

Overview

Amar Kumar, Supply Chain Management

May 2009

confidential
 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. How to design a new RF transaction
6. Glossary

© SAP 2008 / Page 2 confidential

 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. How to design a new RF transaction
6. Glossary

© SAP 2008 / Page 3 confidential

 Objectives

Enables the system to display SAP application data on selected presentation devices such as
handheld barcode reader.

Decoupling of business logic from the physical presentation of application data on a selected
presentation device.

Enable personalized menus, screens and verification profiles.

Enable flexible and user-friendly screen and flow logic generation and modification.

Receiving resource’s input (e.g. verification/input data, keystroke, logon request) and call the
appropriate service.

Supporting large variety of device sizes, presentation device types and data entry types.

Selecting the appropriate form of data presentation according to the application data, device
capabilities and user preferences.

© SAP 2008 / Page 4 confidential

 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. Glossary

© SAP 2008 / Page 5 confidential

 Starting an RF transaction in EWM

A free resource must be available

Start RF with transaction /SCWM/RFUI
Logon to the resource & presentation device
Select the menu entry you want

Users can be potentially logged onto two different resources

© SAP 2008 / Page 6 confidential

 Navigation in RF Menu

Standard Navigation

Direct/Virtual Navigation

© SAP 2008 / Page 7 confidential

Navigation within a transaction

Verification field
Input field

Function keys

Shortcut field

Normally the transaction should work without any manual input

The data entry done by barcode scanning includes an automatic ENTER
Usage of mouse or the TAB key for navigation in a graphical UI not possible
Use ENTER after each input field or verification field

Shortcut field enter exception

© SAP 2008 / Page 8 confidential

 Field Verifications

Verification is done to reduce process errors.

Verification is a comparison of two values.

Verification value is normally entered via barcode scanning.

Input field is 50 characters long but only one visible.

The system will inform if the verification field did not match the comparison field.

Standard verification fields are:

Storage bin (full field or /CSWM/LAGP-VERIF)
HU
Material (material number or EAN number)
Quantity

© SAP 2008 / Page 9 confidential

 Function Keys

Standard function keys:

Are not displayed in the function key line
F5 = More (Display next pushbutton sequence)
F6 = Clear (Clear input field / Clear all input fields)
F7 = Back (Returns to previous screen / step)
F8 = List (Display possible data for the current field)
F9 = Full message (Display message on separate screen)

Transaction specific function keys:

Are displayed in the function key line
If more than 4 keys the “>” indicator is displayed
Used to trigger “not standard” processes/work.

Each function key should have a shortcut defined (e.g. 01 for F1, 08 for F8).

© SAP 2008 / Page 10 confidential

 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. How to design a new RF transaction
6. Glossary

© SAP 2008 / Page 11 confidential

 Presentation & Personalization Profile

Presentation Profile is defined on the warehouse level

Controls the access to the RF menus, Logical transaction flows, Screens
Default for standard transactions is ‘****’
Defined via IMG Menu EWM Mobile Data Entry Define Steps in Logical Transaction
Assigned to Warehouse via IMG Menu EWM Mobile Data Entry Assign Presentation
Profile to Warehouse

Personalization Profile is defined on user level

Controls the access to the RF menus, Screens
Default for standard transactions is ‘**’
Defined via IMG Menu EWM Mobile Data Entry Define Steps in Logical Transaction
Maintained for Presentation Profile
Assigned to User via SAP Easy Access Menu EWM Master Data Resource
Management Maintain Users

© SAP 2008 / Page 12 confidential

 Display Profile

Various RF devices are available with different display/screen characteristics

Display Profile is used to define the different display characteristics

Controls the Screens selected for RF transactions
Default for standard transactions is ‘**’
Screen size: 8 X 40 characters
Templates defined in program /SCWM/SAPLRF_TMPL; screen 0001 & 0002
Length of push buttons: 8 characters
Maximum Push Buttons on a screen: 4
Menu length: 40 characters
Error Messages are shown on the bottom of the screen
Defined via IMG Menu EWM Mobile Data Entry RF Screen Manager
Assigned to Presentation Devices via SAP Easy Access Menu EWM Master Data
Maintain Presentation Devices

© SAP 2008 / Page 13 confidential

 Logical Transactions

Logical transaction defines the set of the processed actions from beginning to end
could imply screen changes and several postings including COMMIT WORK
have no corresponding entries in SE93.
can only be called from the RF menu or the RF logon step
can also be called using method /SCWM/CL_RF_BLL_SRVC=>START_LTRANS (e.g.
from another logical transaction)
Defined via IMG Menu EWM Mobile Data Entry Define Steps in Logical Transaction

Step-Flows for logical transactions

defines the business process flow and the corresponding content provider function
modules
only function modules can be used
steps can be defined to be called in foreground or background
foreground steps need a screen to be assigned to
background steps are used for dynamic flow definitions

© SAP 2008 / Page 14 confidential

 Architecture

Logon/logoff/user input Screen Layout

Application Data
R
Presentation Management e
s
o
Display Render Verify Input u
personalized menu personalized screen r
c
Menu Management Step Flow Screen layout e
Execute
function code
Fetch Data M
Verify Input a
Get Personalization
Execute function code Get authorizations n
Get default a
Presentation Management Interface presentation device g
e
m
Distribute Data Fetch Data e
Application structures
n
t

Content provider (EWM/Others)

© SAP 2008 / Page 15 confidential
 Presentation Building-Bricks

Presentation Management Content Provider

User Main Menu Presentation Device Application

Data

Menu Tree

Logical Transaction

Personalization Display profile

Step Flow

Step

Verification Profile Function Code Profile

States

Physical screen

Display Screen
© SAP 2008 / Page 16 confidential
 Display of RF Menu

RF Menu is defined for a presentation and personalization profile

It is built as a tree structure with components either as sub-menus or logical transactions
Standard menu is delivered for presentation profile ‘****’ and personalization profile ‘**’

Loading
Personalization
Profile

Pick by voice

© SAP 2008 / Page 17 confidential

 Display of Main Menu -Technical

Personalization Profile

Logical transaction catalog

Menu item catalog

Menu hierarchy definition

© SAP 2008 / Page 18 confidential

 Menu builder - /SCWM/RFMENU

1 2 3 4 5 6 7 8 9 A B C D E F G H I

1 = Display menu tree

2 = Add entry as subnode
3 = Add entry at same level
4 = Change menu item
5 = Create menu
6 = Change menu
7 = Delete menu
8 = Change object text
9 = Refresh

A = Expand note
B = Collapse note
C = Next hierarchy level
D = Previous hierarchy level
E = Move selected item up
F = Move selected item down
G = Delete selected item
H = Display text of RF objects
I = Set default object size

© SAP 2008 / Page 19 confidential

 Selection of a Logical Transaction from Menu

Logical Transaction SHDLSI

Initial Step SHDLSL

Step-flow: Pres. Profile (whse) + Log. Trans +

Step + Func. Code FM + Next Step

FM? Call mention FM

Yes
No

Next Step in
Display Screen
foreground? Yes

No

Next Func. Code from

Screen or Background

© SAP 2008 / Page 20 confidential

 Selection of Required Menu Item - Technical

Menu hierarchy definition

Transaction Catalog

Step catalog

© SAP 2008 / Page 21 confidential

 Step Flow - Technical

INIT is always the first processed Verification by Processing mode of the

function code (triggered by the framework). the framework successor step
Like PBO of the first screen of a transaction 0 = defined dynamically by CP
1 = processed in background
2 = processed in foreground
Function module called
by the framework

© SAP 2008 / Page 22 confidential

 Advantages of Flow Logic

Table driven program logic Can be changed without leading to modification

Decoupling business logic from presentation logic
Mapping of one logical transaction step to several physical screen formats
Mapping of presentation state specific functions to customized pushbuttons and
function key profiles

© SAP 2008 / Page 23 confidential

 Display of Screen

Foreground Yes Get function defined for

Step? the step

Build pushbuttons for the

step

Build Verification Profile

User Resource
Presentation Device
Display Profile

Get Template for the

display profile

Get sub-screen for Pres.

Profile (whse) + Persn.
Profile (user) + Disp.
Profile (device)

Display Screen

© SAP 2008 / Page 24 confidential

 Automatic Filling of Fields

The Content Provider is responsible for filling out the appropriate fields with content.
It also handles scenarios where automatic filling of fields is required. Examples:
One HU on the bin
One HU containing the requested material
One batch on a bin, which has to be reported during picking
Assigned picking HU
The application can identify the parameters’ type to specify if the field should be open or
closed for input.

The presentation management is responsible for displaying the fields and values by
the required type (i.e. close/open/invisible) as determined by the content provider

© SAP 2008 / Page 25 confidential

 Navigation Options

Shortcut field for navigation and exceptions

Support of devices without function keys
Support of Exception Handling

Three navigation options at end of transaction

Start with the same logical transaction
Return to menu
User choice

© SAP 2008 / Page 26 confidential

 Lifetime of Variables, Tables and Enqueues

Equeue/Dequeue
Content provider responsibility
Initiated by the function, which is determined in the step flow or further ahead in the
process

Commit Work
Content provider responsibility

Variables and Tables

Main program keeps the Display profile, Personalization profile and authorizations until
user Logoff
Each Logical Transaction will end with LEAVE TO TRANSACTION to assure initialization
of the roll area
Required user and presentation information will be imported from memory
In case the user already logged on, the first Logon step will be skipped

© SAP 2008 / Page 27 confidential

 Display of Screen - Technical

Table /SCWM/TDPRF_CAT

Subscreen

© SAP 2008 / Page 28 confidential

 Function Code Profile - Technical

© SAP 2008 / Page 29 confidential

 Verification Profile – Verification Profile

Table /SCWM/TVERIF_PRF

© SAP 2008 / Page 30 confidential

 Interface to Content Providers

FUNCTION /scwm/rf_pickpt_pisrpt_pbo.
*"--------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" CHANGING
*" REFERENCE(TT_PICKPT) TYPE /SCWM/TT_RF_PICKPT
*" REFERENCE(PICKPT) TYPE /SCWM/S_RF_PICKPT
*"--------------------------------------------------------------------
* Read all open picking TO from /SCWM/ORDIM_O for selected warehouse
* order. Only the unassigned TO are taken into account.
* TO are sorted by lgnum whoseq pathseq tanum to reflect the way thru
* the warehouse.
* The first TO is locked for processing.

© SAP 2008 / Page 31 confidential

 Logon

User Presentation Management Presentation Content provider

Interface (Resource Management)

Logon
to
system

Identify Display profile of

Default device ID
Logon to device ID
application
(Identify device ID Logon and Personalization
automatically or User/Resource data User Authorizations
manually-optional*) fetch

Logon
user to
application

* Options for identifying the display profile:

• Presentation device identification (manually/automatically)
• Default presentation device at user level (if option 1 was not utilized)

© SAP 2008 / Page 32 confidential

 Request Work/Inquiries - Invoking Transaction

User Presentation Management Presentation Content provider

Invoke Interface (TO, Customization EA)
transaction Logical Transaction
from the menu with initial step & function code
tree
Determine next step
(foreground/background) based
on Step Flow Execute function code or
Process before next step
(Application data) or
Get application data/Execute
Process next step
function code
(in background)
Verification profile (foreground) Verification profile
based on step, personalization (foreground)
and based on content provider based on execution area
parameters (e.g. execution area) and BAdI

Function Profile (foreground)

function code/pushbuttons based
on Personalization, Display Profile
& authorizations
Physical Screen layout
(foreground)
Step layout and template

Display screen

© SAP 2008 / Page 33 confidential

 Execute work - Step Flow

User Presentation Management Presentation Content provider

Interface (TO, Customization EA)
Input data and Logical Step, Function code,
Process next step
function code Input data (state)

Determine next step

(foreground/background) based
Execute function code or
on Step Flow
Process before next step
Get application data/Execute (Application data) or
function code Process next step
(in background)
Verification profile (foreground) Verification profile
based on step, personalization (foreground)
and based on content provider based on execution area
parameters (e.g. execution area) and BAdI
Function Profile (foreground)
function code/pushbuttons based
on Personalization, Display Profile
& authorizations
Physical Screen layout
(foreground)
Step layout and template

Display screen

© SAP 2008 / Page 34 confidential

 Conversion Tool for Screen Generation

Goal: Enable fast and easy screen generation

Solution: Conversion Tool for Screen Generation

Enables automatic screen generation by the required display profile (i.e. screen size) and
maximum quantity of pushbuttons.
Analyzes conversion opportunities prior to the screens generation.
User friendly interface.
Enables generation of all sub-screens and templates of a required function group at once.

© SAP 2008 / Page 35 confidential

 Screen manager; Selection and Profile
creation

© SAP 2008 / Page 36 confidential

 Screen manager; Adjust screens

1 2 3 4 5 6 7 8

1 = Create ... 2 = Copy ... 3 = Change ... 4 = Delete Customizing

5 = Edit ... 6 = Display ... 7 = Convert ... 8 = Copy Screen

© SAP 2008 / Page 37 confidential

 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. How to design a new RF transaction
6. Glossary

© SAP 2008 / Page 38 confidential

 Why a Wizard?

Complex customizing
19 DB table entries required to set up an RF transaction
Difficult to locate the logical transaction and step related to the screen
Any change results in update of many DB table entries
Not easy for both consultants and customers

Screen Enhancement Wizard

identifies the screen to be changed
changes according to the specified criteria the screen
automatically updates the related customizing

© SAP 2008 / Page 39 confidential

 Triggering the Screen Enhancement Wizard

Navigate to the screen which needs to be enhanced

Trigger the wizard using <CTRL> + <SHIFT> + <F1>
Follow the wizard to make the required enhancements

© SAP 2008 / Page 40 confidential

 Screen Enhancements

Options:
Modify Screen
Split Screen
Undo Modifications
Start Screen Painter
Start Menu Manager

© SAP 2008 / Page 41 confidential

 Screen Enhancement Process

RF Simulate the Navigate to the Launch the

Transaction process screen wizard

Follow the
wizard
End of Choose the option
wizard to split or modify
Modify on the
screen painter

© SAP 2008 / Page 42 confidential

 Modify Screen Wizard

Here are the Here are the current

available fields displayed fields

© SAP 2008 / Page 43 confidential

 Split Screen Wizard

© SAP 2008 / Page 44 confidential

 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. How to design a new RF transaction
6. Glossary

© SAP 2008 / Page 45 confidential

 New RF transaction – I

Visualize the steps (Visio / Word / PowerPoint / Excel / …)

Paint each screen with fields
Will lead to the identification of the screen data container
If no standard data container is useful, a custom container should be created

Link the screens to steps

Each screen to have step identifier

Identify the functions keys for each screen

For each screen at least the basic framework functions like F7 (Back) and ENT (Enter)
should be defined
Further custom functions for push-buttons need be identified

Identify the flow between screens

Function Modules for verification of screen inputs
Navigation upon selection function key

© SAP 2008 / Page 46 confidential

 New RF transaction – II

FM: ZSTOPS_PBO
Query Route – Logical Transaction ZROUTE

FM: ZROUTE_PBO FM: ZLEG_PBO

SEQ STOP

1 ..

2 ..

From WHSE 3 ..
Route

To CUST1
Step: Z3
ENTER
FM: ZCAL_PBO
F1 Stops F2 Cal

Step: Z1 Step: Z2

FM: ZROUTE_PAI
Step: Z4

Possible Functions: Possible Functions:

F8: List F1: Stop
F7: Back to Menu F2: Calendar
ENT: Enter F7: Back to Prev Step

© SAP 2008 / Page 47 confidential

 Agenda

1. Objectives of the RF Framework

2. Basics
3. Architecture
4. RF Screen Wizard
5. How to design a new RF transaction
6. Glossary

© SAP 2008 / Page 48 confidential

 Glossary (1)

Application - /SCWM/TAPPL_CAT
Highest organizational level

Menu – /SCWM/TMENU_CAT & /SCWM/TMENU_HIER

Part of personalized data determining scope of work and relevant inquiries. The menu is dependent on user
and managerial preferences.

Logical transaction – /SCWM/TTRNS_CAT

Self-contained unit that is carried out in the mobile environment, for example, manual Picking selection by
WO.

Transaction step – /SCWM/TSTEP_CAT & /SCWM/TSTEP_FLOW

Represents the logical step of a transaction that includes data processing. Each step executed in
foreground mode has a corresponding physical screen.
For example the steps of picking transaction are: Bundle assignment, pick confirmation, and transfer
confirmation.

State – /SCWM/TSTAT_CAT
Identifies a specific scenario within a specific step (e.g. before/after step confirmation), which may have an
impact on the displayed screen.

© SAP 2008 / Page 49 confidential

 Glossary (2)

Resource – /SCWM/RSRC
A resource is mentioned as a synonym for user/equipment, which can carry out the
operational work in the warehouse. It does not represent an additional entity in WME.

Presentation device – /SCWM/TPRDV_CAT

A device, used by a resource, that physically presents application data and enables online
interaction with the system.

Presentation device type

Represents a type of presentation device (e.g. Character, Graphic).

Data entry type

Identifies the technology used for input data (e.g. keyboard, barcode reader, voice
recognition).

Data container – /SCWM/TPARAM_CAT

Definition of used structures and tables for data transfer between RF framework and Content
provider.

© SAP 2008 / Page 50 confidential

 Glossary (3)

Function profile – /SCWM/TFCOD_CAT & /SCWM/TFCOD_PRF

Defines the function codes used in the transaction steps. All function codes that are available
in foreground mode are assigned to pushbuttons and function keys.

Verification profile – /SCWM/TVERIF_PRF

A personalized set of fields to be verified per personalization profile and transaction step.

Display profile – /SCWM/TDPRF_CAT

Determines the physical presentation screens and the format of screen elements.

Personalization profile – /SCWM/TPRSN_PRF

Represents a particular group of presentation settings for one or more users. All data that is
displayed on the screen is adjusted to meet the requirements of particular users or groups of
users.

© SAP 2008 / Page 51 confidential

 Exercise

Create a personalized menu for yourself

Steps:
1. Create a personalization profile ## under the standard presentation profile ‘****’
2. Create a menu for the personalization profile ## with the following structure:
Main Menu
– Stock by Bin – Logical transaction INSTBI
– Stock by Product – Logical transaction INSTPR

3. Assign the personalization profile ## to your user (EWMCON-##)

4. Test by logging on to RF transaction
Create a new logical transaction
Steps:
1. Create a new logical transaction ZMON## with the transaction /SCWM/MON
2. Add the logical transaction to the personalized menu
3. Test by logging on to RF transaction

© SAP 2008 / Page 52 confidential

 Thank you!

© SAP 2008 / Page 53 confidential

 Grid

© SAP 2008 / Page 54 confidential

 Definition and halftone values of colors

SAP Blue SAP Gold SAP Light Gray SAP Gray SAP Dark Gray
Primary color palette
RGB 4/53/123 RGB 240/171/0 RGB 204/204/204 RGB 153/153/153 RGB 102/102/102 100%

Dove Petrol Warm Green Warm Red Violet/Mauve

RGB 68/105/125 RGB 21/101/112 RGB 85/118/48 RGB 119/74/57 RGB 100/68/89 Secondary color palette
100%

RGB 96/127/143 RGB 98/146/147 RGB 110/138/79 RGB 140/101/87 RGB 123/96/114 85%

RGB 125/150/164 RGB 127/166/167 RGB 136/160/111 RGB 161/129/118 RGB 147/125/139 70%

RGB 152/173/183 RGB 154/185/185 RGB 162/180/141 RGB 181/156/147 RGB 170/152/164 55%

RGB 180/195/203 RGB 181/204/204 RGB 187/200/172 RGB 201/183/176 RGB 193/180/189 40%

Cool Green Ocher Cool Red Warning Red

RGB 73/108/96 RGB 129/110/44 RGB 132/76/84 Tertiary color palette RGB 158/48/57
100%

RGB 101/129/120 RGB 148/132/75 RGB 150/103/110 85%

RGB 129/152/144 RGB 167/154/108 RGB 169/130/136 70%

RGB 156/174/168 RGB 186/176/139 RGB 188/157/162 55%

RGB 183/196/191 RGB 205/197/171 RGB 206/183/187 40%

© SAP 2008
2007 / Page 55 confidential
 Copyright 2008 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.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP 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 and associated 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 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. 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

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 durch
SAP 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, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie 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ähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. 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 anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit 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 Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, 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.

© SAP 2008 / Page 56 confidential