SAP Fiori apps rapid-deployment solution
Document Version: 1.0 – 2015-01-26
Software and Delivery Requirements
CUSTOMER
Typographic Conventions
Type Style
Description
Example
Words or characters quoted from the screen. These include field names, screen titles, pushbuttons
labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
2
Example
Emphasized words or expressions.
EXAMPLE
Technical names of system objects. These include report names, program names, transaction codes,
table names, and key concepts of a programming language when they are surrounded by body text,
for example, SELECT and INCLUDE.
Example
Output on the screen. This includes file and directory names and their paths, messages, names of
variables and parameters, source text, and names of installation, upgrade and database tools.
Example
Exact user entry. These are words or characters that you enter in the system exactly as they appear in
the documentation.
<Example>
Variable user entry. Angle brackets indicate that you replace these words and characters with
appropriate entries to make entries in the system.
EXAMPLE
Keys on the keyboard, for example, F 2 or E N T E R .
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Typographic Conventions
Document History
Version
Date
Change
1.0
14.07.2014
First version.
2.0
04.09.2014
Restructuring and enhancements.
3.0
31.11.2014
Restructuring and enhancements.
Software and Delivery Requirements
Document History
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
3
Table of Contents
1
Purpose ............................................................................................................................................................................... 5
2
General Project Prerequisites .............................................................................................................................................. 6
3
3.1
3.3
3.4
3.5
Technical Requirements ...................................................................................................................................................... 7
Software Products Versions .........................................................................................................................................7
3.1.1
SAP NetWeaver Gateway ............................................................................................................................7
3.1.2
SAP Web Dispatcher .................................................................................................................................. 8
3.1.3
Requirements for Factsheet and Analytical Apps ........................................................................................ 8
3.1.4
SAP Fiori – Application Specific Components ............................................................................................. 9
3.1.4.1
Application Specific Components for Transactional Apps/Factsheets.......................................................... 9
3.1.4.2
Application Specific Components for Analytical Apps (SAP Smart Business) ..............................................12
3.1.5
SAP Identity Management (Optional) ........................................................................................................ 13
3.1.6
SAP Fiori – Portal Integration (Optional) .................................................................................................... 13
3.1.7
SAP Lumira Server (Optional)....................................................................................................................14
3.1.8
Browser Requirements ..............................................................................................................................14
SAP Notes .................................................................................................................................................................14
3.2.1
Package Specific Note ...............................................................................................................................14
3.2.2
General SAP Notes ....................................................................................................................................14
3.2.3
SAP Release Notes .................................................................................................................................... 15
3.2.4
SAP Notes for Factsheet Implementation ..................................................................................................16
3.2.5
SAP Notes for Portal Integration ............................................................................................................... 17
SAP Solution Manager and SAP Solution Manager Content Add-on ........................................................................... 17
Connectivity ..............................................................................................................................................................18
Authorizations ...........................................................................................................................................................18
4
Related Information .......................................................................................................................................................... 20
3.2
4
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Table of Contents
1
Purpose
This document contains all information around:
o
SAP software components and versions that need to be available in customer landscape as a prerequisite to RDS
implementation.
o
SAP software components and versions that need to be installed during or before RDS implementation
The installation procedures for relevant/required software components are explained in Package Configuration Guide.
Caution
In case of a regular RDS implementation, it needs to be figured out which Software Components are installed by the
customer and which are implemented by the service provider. There are different service options available. Check the
statement of work (SOW) to identify who needs to install which software components.
Software and Delivery Requirements
Purpose
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
5
2
General Project Prerequisites
The following prerequisites need to be in place before an implementation project can start.
Prerequisite
Responsibility
Kick off and workshop dates, location, and attendees agreed
Customer
Customer team allocated with correct skills and training in place
Customer
Project sponsors and stakeholder identified
Customer
Hardware fully commissioned
Customer
Software licenses in place
Customer
Infrastructure team can respond to requests quickly enough for example: CSS notes,
BW content, patches, user requests, authorization changes and transports
Customer
User interfaces agreed for example: SAPGUI, NetWeaver Business Client, or Portal
Customer
Remote access is in place for SAP consultants and SAP Active Global Support
Customer
Decision made whether pre-assembled delivery will be used
Customer
Decision made whether SAP Best Practices Solution Builder will be used to activate
content.
Customer
Decision made whether Solution Manager will be used. Solution Manager set up with
any relevant templates.
Customer
Tool for project repository and collaboration agreed
Customer
Test management tool agreed
Customer
6
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
General Project Prerequisites
3
Technical Requirements
The SAP Fiori apps require an SAP NetWeaver Gateway System as a frontend system. This can be either the embedded
Gateway System in case of SAP NetWeaver 7.40 of the backend system, or the hub solution (the used Gateway system is a
different system as the backend system). In case of a hub solution, the Gateway system can be either an SAP NetWeaver
System 7.31 or 7.40. In case of an SAP NetWeaver 7.31 system, additional software components must be installed in this
Gateway system (see grey highlighting below).
Recommendation
The decision to choose the hub solution or use the embedded Gateway system depends on the use case on customer
site. Find background information on pros and cons for each option on help.sap.com. In any case, this decision should
be discussed for each customer individually with the assigned system architects.
3.1
3.1.1
Software Products Versions
SAP NetWeaver Gateway
The following software products and versions are required. You can use either the SAP NetWeaver 7.31 (SAP EHP1 FOR SAP
NETWEAVER 7.3) or the 7.40 (SAP NETWEAVER 7.4):
Product
Product Version / Software
Component Version
Support Package Level
Relevance
SAP NetWeaver Gateway
SAP NETWEAVER GATEWAY 2.0
SP 08
All Scope Items
SAP NetWeaver
SAP EHP1 FOR SAP NETWEAVER
7.3
SP 10
All Scope Items
SAP IW BEP 200
latest Support Package for
all components
SAP UI add-on INFRA V1.0
SAP UI2 FOUNDATION V1.0
SAP UI2 IMPL. FOR NW 7.00 V1.0
SAP UI2 IMPL. FOR NW 7.01 V1.0
Software and Delivery Requirements
Technical Requirements
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
7
SAP UI2 IMPL. FOR NW 7.02 V1.0
SAP UI2 IMPL. FOR NW 7.31 V1.0
SAP UI2 Services V1.0
SAPUI5 CLIENT RT aS ABAP
1.00
SAP NetWeaver
SAP NETWEAVER 7.4
SP05
All Scope Items
No additional software
components required
For more information regarding SAP NetWeaver AS ABAP, see http://help.sap.com/nw_platform.
3.1.2
SAP Web Dispatcher
The SAP Web dispatcher is required for all scope items except the following cases:

You deploy only transactional apps and access them only via your intranet zone. No Web Dispatcher or reverse proxy is
required in this case.

Once you deploy only transactional apps and want to access them via internet you can use any reverse proxy, for
example the SAP Web Dispatcher can be used as a reverse proxy as well.
For all other Scope Items the SAP Web Dispatcher is mandatory.
Product
Product Version / Software
Component Version
Support Package Level
Relevance
SAP NetWeaver
SAP WEB Dispatcher 7.40
Latest SP
All Scope Items
(Exception explained
above)
3.1.3
Requirements for Factsheet and Analytical Apps
The required components described in this section are required for all Factsheets and Analytical apps. However, in addition
app-specific components are required. Check chapter ‘SAP Fiori – Application-specific Components‘ section to identify the
app-specific requirements.
Product
Product Version / Software
Component Version
Support Package Level
Relevance
SAP HANA Platform Edition
SAP HANA, platform edition 1.0
SP08, revision 81
SAP Fiori Analytical
Apps Deployment
8
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Technical Requirements
Note
SAP Fiori Factsheet
Apps Deployment
SAP HANA Platform is a
prerequisite for the RDS
implementation (not
mandatory required for
transactional apps).
KPI Modeler
KPI Modeler S 100
SAP Fiori Smart
Business Enablement
SP04
Note
SAP Fiori Analytical
Apps Deployment
SAP Fiori Smart
Business Enablement
Needs to be installed on
the HANA Server.
Only required for
Analytical Apps.
KPI Modeler
UISKPI01 100
SP04
Note
SAP Fiori Analytical
Apps Deployment
SAP Fiori Smart
Business Enablement
Needs to be installed on
the Frontend Server (SAP
Gateway).
Only required for
Analytical Apps.
3.1.4
SAP Fiori – Application Specific Components
The following chapter explains how to find the required app specific software requirements. In case of Transactional Apps and
Factsheets always a UI specific add-on is required (installed on the SAP Gateway) and in some cases an integration component
add-on (installed in the respective Backend system – in most cases the integration add-on is already installed since the content
is included in the core component of the Backend system like SAP APPL).
Analytical Apps require a UI specific add-on, an integration add-on (which is usually already installed) and SAP HANA content.
3.1.4.1
Application Specific Components for Transactional
Apps/Factsheets
Software and Delivery Requirements
Technical Requirements
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
9
You can derive the required Software Components using the SAP Fiori apps reference library.
Within two examples for transactional apps the usage of the SAP Fiori apps reference library is being explained:
Example 1:
Figure out which Software Component Versions need to be installed to deploy the app Track Sales Orders:
1.
Open the reference library using this link: SAP Fiori apps reference library
2.
Enter Track Sales Orders and select the Magnifier Glass
3.
Extract the Installation Section on the right detail pane
4.
Derive the required Software Components:
Front End Server (SAP Gateway): UIX01EAP 100
Backend-End Components (ABAP): SRA18 600
5.
The Required Product Versions section under the section Back-End Components (ABAP) provides the details which,
backend versions are supported:
Example 2: My Opportunities
Figure out which Software Component Versions need to be installed to deploy the app My Opportunities:
a.
2.
10
Open the reference library using this link: SAP Fiori apps reference library
Enter My Opportunities and select the Magnifier Glass
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Technical Requirements
3.
Extract the Installation Section on the right detail pane
4.
Since the CRM Apps were downported to lower CRM Versions a switch Latest Back-End Version is available. For the
latest CRM version the following Software Component Versions are applicable:
Front End Server (SAP Gateway): UICRM001 100
Backend-End Components (ABAP): BBPCRM 713
5.
The required Backend Versions are in this case:
6.
Switch now to Lower Back-End Version:
7.
The following Software Component Versions are applicable then:
Front End Server (SAP Gateway): UIX02CRM 100
Backend-End Components (ABAP): GBX02CRM 713
Note
It is possible to get an aggregated information by selecting multiple apps:
o
Choose the
Software and Delivery Requirements
Technical Requirements
button.
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
11
o
3.1.4.2
Then you can select multiple apps in the list and you get an aggregated result list:
Application Specific Components for Analytical Apps (SAP
Smart Business)
You can derive the required Software Components using the SAP Fiori apps reference library.
Example:
Figure out which Software Component Versions need to be installed to deploy the SAP analytical app Customer Reports:
1.
Open the reference library using this link: SAP Fiori apps reference library
2.
Enter Customer Reports and select the Magnifier Glass
3.
Extract the Installation Section on the right detail pane
4.
The following Software Component Versions are applicable then:
SAP Smart Business for CRM 1.0. This requires the installation of the following Software Component versions:
Front End Server (SAP Gateway): UISCRM01 100
12
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Technical Requirements
HANA XS Content:
HCO_HBA_A_CRMHLQ_S 100
(this is the SAP HANA Live content which contains the required VDMs)
Backend-End Components (ABAP):
3.1.5
BBPCRM 713
SAP Identity Management (Optional)
The SAP Identity Management is only used in case the Advanced Security Setup was selected.
Product
Product Version
Support Package Level
Relevance
SAP NetWeaver Identity
Management
SAP NetWeaver Identity
Management 7.2
SP08
Advanced Network
and Security
Configuration
3.1.6
SAP Fiori – Portal Integration (Optional)
See the following list of the required components to integrate the SAP Fiori apps or/and the SAP Fiori launchpad into the SAP
Portal.
Product
Product Version
Support Package Level
Relevance
SAP NetWeaver
SAP EHP1 FOR SAP NETWEAVER
7.3
SP 13
SAP Fiori Integration
with SAP Enterprise
Portal
SP 08
SAP Fiori Integration
with SAP Enterprise
Portal
Usage type: SAP EHP1 FOR SAP
NETWEAVER 7.3 - EP Core Application Portal
SAP NetWeaver
SAP NetWeaver 7.4
Usage type: SAP NETWEAVER 7.4
- EP Core - Application Portal
Note
Make sure that you implement SAP Note 2053012 so the Launchpad integration works.
Software and Delivery Requirements
Technical Requirements
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
13
3.1.7
SAP Lumira Server (Optional)
Product
Product Version
Support Package Level
Relevance
SAP Lumira Server
SAP Lumira Server 1
SP 20
SAP Fiori Smart
Business Enablement
3.1.8
Browser Requirements
This section is in continuous change due to the fast changes in browser business. Check SAP Note 1935915 for the current
requirements. For a more detailed view on general or technical release information, see the Product Availability Matrix
(https://service.sap.com/sap/support/pam).
3.2
SAP Notes
The following SAP Notes need to be considered.
3.2.1
Package Specific Note
SAP Note No
Content
Comments
Relevance
2076403
This SAP Note contains
critical information for
implementing the SAP Fiori
apps rapid-deployment
solution V5.20.
Before you start the
activation of the rapiddeployment solution,
check the latest versions of
this SAP Note.
All Scope Items
Comments
Relevance
3.2.2
General SAP Notes
SAP Note No
Content
1931156
General Information: SAP
NetWeaver Gateway 2.0
1931157
General Information: UI
Infrastructure Components
14
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
All Scope Items
For setting up the system
landscape to run SAP Fiori
All Scope Items
Software and Delivery Requirements
Technical Requirements
SAP Note No
Content
Comments
Relevance
apps, this notes states the
relevant prerequisites and
fixes for User Interface
add-on 1.0 for SAP
NetWeaver 7.31 or User
Interface Technology for
SAP NetWeaver 7.4.
3.2.3
SAP Release Notes
The following table consists of the release notes of the different areas. Within the release notes links to subsequence notes are
provided.
SAP Note No
Content
Comments
Relevance
1914499
Release Information Note: UI
FOR EHP7 FOR SAP ERP 6.0
This note is the entry point
for central notes and
application-specific notes.
SAP Fiori Transactional Apps
Deployment
This note is the entry point
for central notes and
application-specific notes.
SAP Fiori Transactional Apps
Deployment
This note is the entry point
for central notes and
application-specific notes.
SAP Fiori Transactional Apps
Deployment
Release Information Note
for UI for Access Control
10.1
SAP Fiori Transactional Apps
Deployment
This note is the entry point
for central notes and
application-specific notes.
SAP Fiori Transactional Apps
Deployment
Release information for
the new UI of 'SAP SNC
USABILITY EXT 1.0'. This
note is the entry point for
central notes and
application-specific notes.
SAP Fiori Transactional Apps
Deployment
Release information for
'SAP Fiori for SAP SCM
1.0'. This note is the entry
point for central notes and
application-specific notes.
SAP Fiori Transactional Apps
Deployment
1914502
1914501
1929930
1964761
1914553
2001729
Release Information Note: UI
FOR EHP3 FOR SAP SRM 7.0
Release Information Note: UI
FOR EHP3 FOR SAP CRM 7.0
Release Information Note for
UI for Access Control 10.1
Release Information Note:
SAP FIORI FOR SAP ILM 1.0
Rel. Info for Mobile UI ext. for
SAP SNC USABILITY EXT 1.0
Release Information Note:
SAP Fiori for SAP SCM 1.0
Software and Delivery Requirements
Technical Requirements
SAP Fiori Factsheet Apps Deployment
SAP Fiori Factsheet Apps Deployment
SAP Fiori Factsheet Apps Deployment
SAP Fiori Factsheet Apps Deployment
SAP Fiori Factsheet Apps Deployment
SAP Fiori Factsheet Apps Deployment
SAP Fiori Factsheet Apps Deployment
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
15
SAP Note No
Content
1987796
Release Information Note:
SAP Fiori for EHS
Management
1931160
Release Information Note for
SAP Fiori Approve Requests
1956429
MDG Gateway Service for
Fiori Applications
3.2.4
Comments
Relevance
SAP Fiori Transactional Apps
Deployment
This is the release
information note for FIORI
APPROVE REQUESTS X1
1.0. This note contains the
minimum required fixes
that must be installed
either on the UI application
component or on the Task
Gateway Service, as well as
recommended upgrades.
SAP Fiori Transactional Apps
Deployment
SAP Fiori Transactional Apps
Deployment
SAP Notes for Factsheet Implementation
SAP Note No
Content
2084340
ES-Models: No import for
non-editable SWC
SAP Fiori Factsheet Apps Deployment
2085001
ES: Improvements for model
update from client 000
SAP Fiori Factsheet Apps Deployment
2084536
ES-InA: Corrections
SAP Fiori Factsheet Apps Deployment
2086070
SNOTE: Schedule SW Comp.
import job only if needed
SAP Fiori Factsheet Apps Deployment
2086223
ES: Prepare model data for
connector creation
SAP Fiori Factsheet Apps Deployment
2073214
ES: Dynamic configuraton of
Interactive Navigation
SAP Fiori Factsheet Apps Deployment
2089381
ES-Modeler: Texts missing on
creation of nodes
SAP Fiori Factsheet Apps Deployment
2090135
ES-Modeler: Import of EPMdemo content fails
SAP Fiori Factsheet Apps Deployment
2071965
ES-InA: Corrections
SAP Fiori Factsheet Apps Deployment
2093151
SNOTE: Schedule SW Comp.
Import job only if needed (2)
SAP Fiori Factsheet Apps Deployment
2104525
SNOTE: SW Comp. Import Limitation to SW Comp. is
SAP Fiori Factsheet Apps Deployment
16
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Comments
Relevance
Software and Delivery Requirements
Technical Requirements
SAP Note No
Content
Comments
Relevance
ignored
2109588
Enterprise Search: Import des
Datentyps FIPOS schlägt fehl
3.2.5
SAP Fiori Factsheet Apps Deployment
SAP Notes for Portal Integration
SAP Note No
Content
Comments
Relevance
2031108
SAP Fiori Integration with
SAP Enterprise Portal Central note
This note is the central
note for SAP Fiori
integration in SAP
Enterprise Portal.
SAP Fiori Integration with SAP Enterprise
Portal
3.3
SAP Solution Manager and SAP Solution Manager Content Add-on
For the implementation of the solution package, SAP Solution Manager is recommended.
Product
Product Version
Comments
SAP Solution Manager
SAP Solution Manager 7.0 Enhancement
Package 1
If using SAP Solution Manager 7.0 with SP
below 24, see SAP Note 1579267.
SP18 or higher
Or
SAP Solution Manager 7.1
SP01 or higher
Or
SAP Solution Manager 7.1 on HANA (ST
712)
SP00 or higher
For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates.
The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the
latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at
service.sap.com/swdc.
For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note 1726649 and SAP Note
1686668 respectively.
In the ST-RDS 100 content add-on, access the template in the following way:
o
If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below.
o
If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name/names in the table below.
Software and Delivery Requirements
Technical Requirements
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
17
Template ID and
Template Name
RDS_FIORI_NWG20V5 - SAP Fiori Apps Rapid-Deployment Solution_V5
Solution Package
Name(S)
SAP Fiori apps rapid-deployment solution_V5
3.4
Connectivity
This section gives an overview of the required RFC destinations that have been created and used for this package.
RFC Destination
Description
Connection
Type
Created in
Building Block
Logon Data
Comment
<system id
>CLNT<Client>
RFC
Destination
to SAP
Server
3
SAP Fiori
Technical
Foundation
Configuration
UserID
For more details, see
chapter ‘Gateway
System: Creating
Trusted RFC in
NetWeaver Gateway to
SAP Business Suite’
<system id
>CLNT<Client>
RFC
Destination
to SAP
NetWeaver
Gateway
Server
3
SAP Fiori
Technical
Foundation
Configuration
UserID
For more details, see
chapter ‘Defining Trust
between SAP Business
Suite and SAP
NetWeaver Gateway’
Note
You can check the RFC destinations using transaction SM59.
3.5
Authorizations
This section provides an overview of the users required for this solution package.
Purpose
User ID
User Type
Created in
Initial Password
Authorization
Profile
Administration
user in SAP
NetWeaver
Gateway
System
User ID is defined
by your system
administrator
Dialog (Type
A)
SAP
NetWeaver
Gateway
System
Password is
defined by your
system
administrator
Authorization is
defined by your
system
administrator
18
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Technical Requirements
Purpose
User ID
User Type
Created in
Initial Password
Authorization
Profile
Administration
user in the
connected SAP
backend
system/s
User ID is defined
by your system
administrator
Dialog (Type
A)
Connected ERP
backend
system/s
Password is
defined by your
system
administrator
Authorization is
defined by your
system
administrator
Note
You can check the users in transaction SU01.
Software and Delivery Requirements
Technical Requirements
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
19
4
Related Information
Content
Location on SAP Service Marketplace
Latest versions of installation and
upgrade guides
http://service.sap.com/instguides
Sizing, calculation of hardware
requirements - such as CPU, disk, and
memory resource - with the Quick Sizer
tool
http://service.sap.com/quicksizer
Released platforms and technologyrelated topics such as maintenance
strategies and language support
http://service.sap.com/platforms
Network security
http://service.sap.com/securityguide
High Availability
http://www.sdn.sap.com/irj/sdn/ha
Performance
http://service.sap.com/performance
Information about Support Package
Stacks, latest software versions and
patch level requirements
http://service.sap.com/sp-stacks
General Information on SAP Fiori for SAP
Business Suite
http://help.sap.com/fiori
20
To access the Platform Availability Matrix directly, enter
http://service.sap.com/pam
CUSTOMER
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Software and Delivery Requirements
Related Information
www.sap.com/contactsap
© 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP
affiliate company.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National
product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or SAP
affiliate company 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.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective
companies. Please see www.sap.com/corporateen/legal/copyright/index.epx for additional trademark information and
notices.
Material Number: