Upload
debsankhaghosh
View
50
Download
2
Tags:
Embed Size (px)
DESCRIPTION
Portal Roles - Roles vs Arthorization
Citation preview
PRTL152:
Portal Roles and Authorizations
Elke Speliopoulos, SAP Labs, LLC
Soledad Alvarado, SAP Labs, LLC.
Vera Gutbrod, SAP AG
Julia Levedag, SAP AG
SAP AG 2004, SAP TechEd / PRTL152 / 3
Learning Objectives
As a result of this workshop, you will be able to:
Understand the two role concepts in SAP NetWeaver Understand the concept of portal roles and authorizations for
backend systems Understand the concept of Portal permissions Understand the concept of User Management Permissions in
the Portal environment
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend SystemPortal Roles and User Management RolesGotchas and Key Points
SAP AG 2004, SAP TechEd / PRTL152 / 5
SAP NetWeaver Powers mySAP SolutionsRole-specific, Easy Access to All Systems
Employee Self Service Role (SAP ERP)
Manager Self Service Role (SAP ERP)
SAP AG 2004, SAP TechEd / PRTL152 / 6
SAP NetWeaver Portal Infrastructure
Role-based,
and web-based
access to any kind of applications, information and
servicesERP CRM
secure
SAP Enterprise Portal 6.0
Authentication
Sales Manager
Line Manager
Business Developer
Docs*
*covered by KM
Single Sign On
SAP AG 2004, SAP TechEd / PRTL152 / 7
Portal Role Concept: Why Create Roles?
Role 2Role 1
User 1Group 1 Group 2
Content 1 Content 5Content 3Content 2 Content 4
By creating roles are you able to assign different pieces of content to different groups of users.
SAP AG 2004, SAP TechEd / PRTL152 / 8
Main Role Concepts in SAP NetWeaver
Single and CompositeRoles in
ABAP-basedSystems
PortalRoles
SAP Enterprise Portal
Roles in ABAP-based Systems(Roles in Transaction PFCG)
SAP AG 2004, SAP TechEd / PRTL152 / 9
Roles in ABAP-Based Systems
A role is a collection of activities and functions that describes a certain work area of an SAP application.
Roles are objects for generating authorizations so that the usercan access the transactions, reports etc. contained in the SAP menu.
The menus available to users after logon are implemented with roles (SAP Easy Access menu).
There are single roles and composite roles. Roles are assigned to users.
Role XYZ
Transaction TA1
Transaction TA2Transaction TA3
Report zzzWeb Link 1
Web Link 2
SAP AG 2004, SAP TechEd / PRTL152 / 10
Portal Roles
A portal role is a container for applications and information that can be assigned to a particular group of users.
The content of a role enables users to perform the tasks in their respective job description.
The content of a portal role is based on the company structure and on the information needs of the portal users in the company.
The portal navigation structure is defined by the sum of the roles assigned to the user.
Technically, a role is a hierarchy of folders containing other portal content objects.
Roles can be assigned to users or groups of users, i.e. the portal role connects users (or groups of users) to the portal content.
Worksets are introduced as a new layer in a role hierarchy.
User Group 2
Role A
User Group 1
Role Assignment
SAP AG 2004, SAP TechEd / PRTL152 / 11
Portal Roles
Roles are the largest semantic units within content objects.
They include folder hierarchies consisting of folders, worksets, pages and iViews.
The role structure also defines the navigation structure of the portal.
Roles are assigned to users.
iViews and Pages
WorksetRole
Folder Page iView
SAP AG 2004, SAP TechEd / PRTL152 / 12
ABAP Roles and Portal Roles: A Comparison (1)
The role content depends on the company structure and the core processes of the company. They are complete job descriptions, not limited to objects of SAP Systems.
The role content depends on the users tasks in the SAP system.
The content of portal roles do not depend on SAP applications, but may include them. They contain different kinds of information (heterogeneous content types).
The content of a role always refer to a single SAP application.
Portal RolesABAP RolesI. Contents of Roles
II. What is defined by Roles?
Top-level navigation and detailed navigation
SAP Easy Access MenuPortal RolesABAP Roles
SAP AG 2004, SAP TechEd / PRTL152 / 13
ABAP Roles and Portal Roles: A Comparison (2)
III. Types of Roles
Roles are not divided into different role types. The portal introduces the concept of "worksets.
There are single and composite roles. Composite roles are optional.
Portal RolesABAP Roles
IV. Administration Environment
Role administration by different web-based tools in the Portal administration environment.
All actions connected with roles are performed in transaction PFCG: role creation and maintenance, role/user assignments and authorization generations.
Portal RolesABAP Roles
SAP AG 2004, SAP TechEd / PRTL152 / 14
ABAP Roles and Portal Roles: A Comparison (3)
A portal role is mainly a content object and not an authorization object. Portal roles cannot be used in the portal environment to create authorizations for the backend systems.
Authorizations must still be maintained in the backend systems.
Roles (single roles) carry the authorization information. Roles are authorization objects. The profile generator is part of role administration in Transaction PFCG.
Portal RolesABAP Roles
V. Authorizations
SAP AG 2004, SAP TechEd / PRTL152 / 15
SAP Enterprise Portal as a Component of SAP NetWeaver Combines the Different Role Concepts
PortalRoles
Roles in ABAP-based
Systems
Both roles concepts can be combined in the portal environment.
Conversion of ABAP-roles and their content into portal content objects
Transfer of portal roles to the ABAP-based system in order to maintain the missing authorizations
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend SystemPortal Roles and User Management RolesGotchas and Key Points
SAP AG 2004, SAP TechEd / PRTL152 / 17
Overview: Roles in the SAP NetWeaver Environment
ROLESPortalRoles
User Management
Users
User Groups
Assignment
End User NavigationTop Level Navigation Detailed Navigation
Definition Portal Content(Portal Content
Directory)
AssignmentWorksets
PagesiViews
ACLs
Authorization Generation
Roles from ABAP based backend systems
Upload
SAP AG 2004, SAP TechEd / PRTL152 / 18
SAP Enterprise Portal as the Leading System
The SAP Enterprise Portal can be used as the leading system for:
Role creation Role maintenance Role/user assignment
All tasks concerning content creation and user assignment can all be done at one place, and this is the SAP Enterprise Portal
Authorization generation must bedone in the backend system !
SAP AG 2004, SAP TechEd / PRTL152 / 19
Portal Roles and Authorizations
Enterprise Portal
SAP Systems
Enterprise Apps
CM Systems
Others
Role Definition
Authorizations
In SAP Enterprise Portal you maintain and create the role definitions. However you do not generate authorization profiles necessary for the backend system in the portalenvironment.
Both SAP Enterprise Portal and the backend system have tools and functions that permit you to link the portal role with the ABAP authorization concept andto link the authorization profile in the backend system with the portal role concept.
If portal roles contain transactions and other objects that access objects in ABAP-based backend systems, you must still generate the authorization profiles in the backend system.
SAP AG 2004, SAP TechEd / PRTL152 / 20
Portal Content and Authorizations in the Backend System
Content objects from ABAP- basedsystems can be converted to Portalcontent objects.From now on object creation and maintenance is done in the Portal!
Role/User assignment can also bemigrated to the Portal
From now on role/user assignment is done in the Portal!
Authorization must be maintained!Assignments roles to users should be synchronous with
assignments in the Portal.
Backend System
Portal
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend SystemPortal Roles and User Management RolesGotchas and Key Points
SAP AG 2004, SAP TechEd / PRTL152 / 22
How to Migrate ABAP Roles and Their Content to SAP Enterprise Portal?
SAP Enterprise Portal
ABAP-Based SAP System
(Role DevelopmentSystem)
Single Role/Composite Role
Portal Role and Portal Content Objects +
role/user assignment
Migrated role andincluded objects +
role/user assignments
Initial Role Upload
Role Upload Tool in SAP Enterprise Portal
Included objects:transactions, MiniApps
etc. androle/user assignments
Authorization Profiles
SAP AG 2004, SAP TechEd / PRTL152 / 23
Role Upload: Availability
Functionality is available for: EP 6.0 SP2 Patch 4 (on Web AS 6.20) SAP NetWeaver 04 Support Package Stack 04 (EP on Web AS 6.40)
SAP AG 2004, SAP TechEd / PRTL152 / 24
Features of Role Upload
Included services (MiniApps or transactions) are converted to iViews.
When objects are uploaded again, you can define whether or not existing objects should be overwritten.
User assignment can be uploaded to the Portal.
Single and composite roles are converted as either Portal roles or worksets with the corresponding menu hierarchy.
First level folders can be set as entry point in the top-level navigation
SAP AG 2004, SAP TechEd / PRTL152 / 25
Prerequisites System Requirements
The following requirements must be fulfilled before you can upload objects to the portal from SAP backend system: Import the SAP Enterprise Portal Plug-In 6.0
You must import the SAP EP Plug-In 6.0 into each backend system from which you want to perform an upload. Only then are all the necessary functions for the upload available.
For a Workplace system landscape, this means that you must import the plug-in to both the Workplace Server and all the component systems from which you want to upload objects.
Authorizations in the backend system In the backend system you need the authorization S_RFC for function group
PWP2.
Configuration of the system landscape in EP In the portal system landscape, you must create a system for each backend
system from which you upload objects. You must define a connection to the backend system for this system.
SAP AG 2004, SAP TechEd / PRTL152 / 26
Converted Objects
Converted objects can be used as Portal objects in order to build portal content.
Single Role R01
Transaction TA1Transaction TA2
Transaction TA3Report R01
Web Link W1Web Link W2
Portal Role R01
iView TA1iView TA2
iViews TA3iView R01
iView W1iView W2
The role/user assignment of a role can also uploaded to the portal. You therefore do not have to make this assignment again in the portal. An uploaded role is automatically assigned to a portal user. Prerequisite: backend user must have a corresponding user in the Portal.
ABAP-based SAP System
SAP Enterprise Portal
SAP AG 2004, SAP TechEd / PRTL152 / 27
Object Storage in Portal Catalog
Migrated and converted objects can be found in the Portal Catalog in a special folder Portal Content-> Migrated Content -> SAP ComponentSystems.
SAP AG 2004, SAP TechEd / PRTL152 / 28
Working with Migrated Roles in the Portal (1)
Single and composite roles have no pages. Therefore pages with iViews must be defined and assigned to the roles.
Role hierarchy and navigation structure must be adjusted. The original migrated roles represent the menu of an ABAP-based SAP system and therefore could have deep navigation structures. It makes sense to remove unnecessary navigation levels.
The top-level navigation must be checked. Single and composite roles often list more than 10 entries on the first level of their navigation structure. A 1:1 conversion in the portal would mean that the top-level navigation would be incomprehensibly large.
SAP AG 2004, SAP TechEd / PRTL152 / 29
Working with Migrated Roles in the Portal (2)
Preliminary consideration should be given as to where the right place for an ABAP role within a portal role structure is. In certain use cases it may be beneficial to migrate roles to worksets and assign them to a portal role.
Sometimes it is better to migrate only single services(transactions) rather than a complete role. In the Portal administration environment these services can be grouped in a different way in a new role structure.
SAP AG 2004, SAP TechEd / PRTL152 / 30
All Content is Created and Maintained in the Portal!
iView Studio:www.iviewstudio.com
ABAP-Based System 1
ABAP-Based System 2
ABAP-Based System 3
Portal Content
RolesWorksets
Pages
iViews
Portal
Upload and Conversion ofContent Objects
Upload and Conversion of Content Objects
Upload and Conversion ofContent Objects
Download ofBusiness Packages
containing Portal Content
SAP AG 2004, SAP TechEd / PRTL152 / 31
Demo
Demo and Exercise Part I
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend SystemPortal Roles and User Management RolesGotchas and Key Points
SAP AG 2004, SAP TechEd / PRTL152 / 33
How to Maintain Authorizations for Portal Content Objects?
Enterprise PortalABAP-based SAP
System
Portal Role Generated authorization role
Repetitive Authorization
Generation
Authorization data
List of transactions, etc.Included objects:iViews accessing
transactions, MiniApps etc. in
the backend system
Generated auth. profiles
Generated authorizations
Role Distribution to the Backend System
Role/user assignment Role/user assignment
SAP AG 2004, SAP TechEd / PRTL152 / 34
Role Distribution in Detail
ABAP-based SAP System Responsible for Creation of Authorization Roles
Portal Role A
System 1 Auth. Role A_1:T1, T2, T6
Auth. Role A_2:T1, T2, T6
System 2 Auth. Role A_3:T3, T4, T5
Auth. Role A_4:T3, T4, T5
SAP Enterprise Portal
Portal Role A
Folder 1
iView ATransaction T1 ---> System 1iView BTransaction T2 ---> System 1iView CTransaction T3 ---> System 2
Folder 2iView DTransaction T4 ---> System 2
iView ETransaction T5 ---> System 2iView F Transaction T6 ---> System 1
SAP AG 2004, SAP TechEd / PRTL152 / 35
Authorizations in ABAP-based Systems: Overview
The following functionality is provided: Distribution of portal role definition from portal to backend systems Creation of corresponding authorization roles in backend system Update/change of user assignment
A tool in the Portal System Administration role enables the system administrator to Transfer role definition to an ABAP-based backend system Transfer role/user assignments to an ABAP-based backend system Report on transfer processes
Transaction WP3R in the ABAB-based system enables the administrator to create authorization roles on the basis of portal roles Transaction WP3R: Follow up processes for portal roles Transaction WP3R is included in the Enterprise Portal Plug-In
SAP AG 2004, SAP TechEd / PRTL152 / 36
Transfer of Portal Roles and User Assignments
Step 1: Transfer portal role information to a dedicated backend system
Step 2: Transfer portal user assignment to a dedicated backend system
SAP AG 2004, SAP TechEd / PRTL152 / 37
Roles Distribution (1)
The following data will be included: Role name including the logical system
nameDependent transactions and servicesMetadata of the content objects
Select the system to which data shall be transferred
Select the roles that are to be transferred
SAP AG 2004, SAP TechEd / PRTL152 / 38
Transaction WP3R: Follow-up Process for Portal Roles (2)
ABAP-basedSAP SystemTransaction WP3R
SAP AG 2004, SAP TechEd / PRTL152 / 39
Transaction WP3R: Generation of Authorization Roles (3)
SAP AG 2004, SAP TechEd / PRTL152 / 40
Transaction WP3R: Authorization Profile Generation (4)
SAP AG 2004, SAP TechEd / PRTL152 / 41
Role/User Assignment Distribution (1)
The user ID will be transferred to the backend system. If user mapping is used, the mapped User ID will be published to the backend system.
SAP AG 2004, SAP TechEd / PRTL152 / 42
Transaction WP3R: Follow-Up Process for Role Assignment (2)
ABAP-basedSAP SystemTransaction WP3R
SAP AG 2004, SAP TechEd / PRTL152 / 43
Transaction WP3R: Authorization Role Assignments (3)
SAP AG 2004, SAP TechEd / PRTL152 / 44
EP 6.0
Scenario: Role Distribution from EP 6.0 to ABAP-based Systems
Role Definition
User Assignment
SAP 4.6BDevelopment System
Creation of Authorization Role
Distribution of Role Definition
SAP 4.6BQuality Assurance System
Test of Authorization Role
RoleTransport
SAP 4.6BProductive System
(SAP CUA or component system)
RoleTransport
Distribution of Role User Assignments
User Assignment
SAP AG 2004, SAP TechEd / PRTL152 / 45
Demo
Demo and Exercise Part II
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend System Portal Roles and User Management RolesGotchas and Key Points
SAP AG 2004, SAP TechEd / PRTL152 / 47
Authorizations & Portal Roles + ACLs & UME Roles
Provide Access to JAVA components
Provide End User Access and various levels of Administration access for portal objects.
Provide Navigation and Access to EP Content and Components
Grant access to ABAP objects
Maintained in User Admin WebConsole
Maintained in EP System Administration Area
Maintained in EP Content Administration Area
Maintained in ABAP System
UME ObjectsMethodology to define permissions for EP objects
PCD ObjectsBackend Authorizations
Part of ABAP Roles
UME RolesACLsPortal RolesPFCG Roles and Authorizations
SAP AG 2004, SAP TechEd / PRTL152 / 48
Preconfigured EP Administration Roles
access on all tools for user administration to create and maintain users, administrate the role-user assignment, user mapping administration, user Replication, Group administration, etc.
User Administrator
access on all tools for system administration such as system configuration, transports, permissions, monitoring, support, portal display
access on all parts of tree hierarchy of Portal Content Catalogs if the right ACLs have been defined
System Administrator
access on all Content Administration tools for creation of roles, worksets, pages, iViews, layouts
access on all editors to maintain content e.g. Permission Editor, Property Editor
access on all parts of tree hierarchy of Portal Content Catalog if the right ACLs have been defined
Content Administrator
assigned to initial SAP* User Full Control access on whole Portal Content Catalog Tree Access on all admin tools
of Content Administrator Role of System Administrator Role of User Administration Role
Super Administrator
FunctionRole
SAP AG 2004, SAP TechEd / PRTL152 / 49
Admin Roles and Portal Content Objects
Content administrators are responsible for content objects in the Portal Catalog. ACLs define the access and
allowed action for content objects like folders, roles, worksets, pages, iViews and templates.
System administrators are responsible for system administration tasks and objects. ACLs define the access and
allowed actions for objects like transport packages or systems.
User administrators are responsible for users related tasks. Role-User Assignment can be
controlled by permissions set for user management role.
Super admin
Content admin 1
Content admin 2
Content admin 3
System admin 1
System admin 2
System admin 3
User admin 1
User admin 2
User admin 3
+ ACL
+ ACL
+ ACL
+ ACL
+ ACL
+ ACL
Set Role
Set Role
Set Role
SAP AG 2004, SAP TechEd / PRTL152 / 50
Permissions and Delegated Administration
The concept of permissions is connected with the principles of delegated administration!
Delegated Administration means to distribute administration tasks within an organization.
You have to distribute and control... Administration and maintenance of content like portal roles Administration and maintenance of system configuration like UM
configuration, monitoring configuration, service configuration, etc. Administration and maintenance of user information (e.g. Users,
Groups, User-Role Assignment, ...)
Delegated Administration is realized by different tools like... Predefined customizable administration roles ACLs on folder hierarchies in the portal content catalog Special UME permissions on the User Administration role
SAP AG 2004, SAP TechEd / PRTL152 / 51
Delegated Administration Scenario Diagram
Permission EditorPortal Catalog
Project 1User managementContent
RolesRole ARole B
Role ListContent Administration
Full ControlPermissionOn Role A
Assigned to Role Content
Administration
Portal Content StudioPortalCatalogRole A
Role Editor
John
John has access to the Content Studio interface since he is assigned to the content administration role.He can edit only Role A according to the permission he got in the permission editor.
Johns Interface of Portal Content Studio
SAP AG 2004, SAP TechEd / PRTL152 / 52
Design Time Permission (Administration)
Administrator Permissions Check during creation
process for objects Check when accessing
objects
Worksets
PagesSystems
Folder & objects visible
Edit object properties Edit assigned delta links Edit permissions
Delete objects Create from
Templates with READ permission
OWNER
Folder & objects visible
Edit object properties Edit assigned delta links
Delete objects Create from
Templates with READ permission
FULL CONTROL
Folder & objects visible
Edit object properties Edit assigned delta links
No delete! Create from
Templates with READ permission
READ/WRITE
Folder & objects visible
Copy objects No Edit
Create from Templates with READ permission
READ
Folder & objects not visible
Folder & objects not visible
NONE
Edit ObjectsCreate/ Delete Objects
ACL Check on Folder Level and on Object Level
Portal Catalog
SAP AG 2004, SAP TechEd / PRTL152 / 53
Runtime Permissions (End User)
End User Permissions Check for Navigation Check for in Personalize
Page Component Check if calling component
via URL
Worksets
PagesSystems
Direct access to an iView USE permission is required
Direct URL access to a component: Users may access portal components through URL without an intermediate iView if they are granted USE permission in the appropriate security zone.
User Interfaces in the end user environment that display the portal content catalog (such as personalize page) only display objects that have end user permission.
Navigation iViews (TLN, detailed navigation, Drag&Relate targets, related links) only display roles and objects that have end-user permission.
For display of objects in navigation the ACL is checked on the object level.
USE
PersonalizationNavigation
ACL Check on Folder Level and on Object Level
Personalize Page
SAP AG 2004, SAP TechEd / PRTL152 / 54
Demo
DemoandExercise Part III
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend SystemGotchas and Key PointsMore Information
SAP AG 2004, SAP TechEd / PRTL152 / 56
Gotchas and Other Good to Knows (1)
Uploading Roles From Backend Systems: Make sure users for whom you want to transfer assignments are
identical in both, SAP EP and backend system.
If you have complex back-end roles, remember the number of entry points you may be creating by setting the Select first folder level as entry point flag. In that case, it may be better to unselect the option.
Make sure that you wait for status: Finished to indicate the role has been completely transported. Roles with deep navigation structure may take additional time to transport.
SAP AG 2004, SAP TechEd / PRTL152 / 57
Gotchas and Other Good to Knows (2)
Distributing the Portal Role to the Backend System: In order for the tool to access the logical systems, make sure there is an
entry in the Table WP3ROLESYS pointing to the logical system name.
Transaction SCC4 shows the client information of the backend system and via double click, the logical system name can be found.
Use transaction SE16 for viewing and creating entries in the table. Make sure that you have the authorization S_RFC for function group
PWP2 in the backend system.
Use Transaction WP3R (which is included in the EP 6.0 Plug-In) to view the role and authorizations instead of PFCG.
(Note: Due to organizational structures, some of these tasksmay fall into the responsibility of an SAP System Administrator)
Role Concepts in SAP NetWeaverAuthorization ConceptsRoles Upload to SAP Enterprise PortalPortal Roles Distribution to the Backend SystemGotchas and Key PointsMore Information
SAP AG 2004, SAP TechEd / PRTL152 / 59
Further Information
Public Web:www.sap.comSAP Developer Network: http://sdn.sap.com Enterprise PortalSAP HELP Portal: http://help.sap.com/nw04
Related Workshops/Lectures at SAP TechEd 2004SCUR01, User Management and Authorizations: Overview, LectureSCUR351, User Management and Authorizations: the Details, Hands-On
Related SAP Education Training Opportunitieshttp://www.sap.com/education/
SAP AG 2004, SAP TechEd / PRTL152 / 60
SAP Developer Network
Look for SAP TechEd 04 presentations and videos on the SAP Developer Network.
Coming in December.
http://www.sdn.sap.com/
SAP AG 2004, SAP TechEd / PRTL152 / 61
Q&A
Questions?
SAP AG 2004, SAP TechEd / PRTL152 / 62
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, 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, and Informix are trademarks or registered trademarks of IBM Corporation 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. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Copyright 2004 SAP AG. All Rights Reserved