Upgrade and Update Guide SAP ERP 6.0 Including Enhancement Package 5 Java
Target Audience System Administrators Technology Consultants
PUBLIC ÜÂ4ÐLáÔá¸îgjÂJì-:abù]`Jãx
Document History
CAUTION Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/ instguides.
The following table provides an overview of the most important document changes.
Version Date Description 1.0 2012-04-02 First version
2/38 PUBLIC 2012-04-02
Table of Contents
Chapter 1 Getting Started ...... 5 1.1 Essential Information: Required Documentation ...... 5 1.2 Important SAP Notes ...... 6 1.3 Naming Conventions ...... 6
Chapter 2 Planning ...... 9 2.1 Supported Source Releases ...... 9 2.2 Checking Prerequisites ...... 10 2.3 Upgrade Scope for ERP Java Components ...... 11 2.4 Upgrade of Multiproduct Java Systems ...... 13
Chapter 3 Preparation ...... 15 3.1 Free Space Requirements ...... 15 3.2 Preparing the Upgrade of Internet Sales (R/3 Edition) Web Application Components ...... 15 3.3 Cleaning Up the Universal Worklist Cache ...... 16 3.4 Undeploying the Software Component NetWeaver Mobile Administration (NWMADMIN) ...... 17
Chapter 4 Follow-Up Activities ...... 19 4.1 Performing Follow-Up Activities for the E-Commerce User Management ...... 19 4.2 Additional Follow-Up Activities for SAP E-Commerce ...... 20 4.2.1 Upgrading the Shop Management Data ...... 20 4.2.2 Performing Adjustments to Java Class Changes ...... 21 4.2.3 Checking the Login Configuration ...... 23 4.2.4 Replacing the Catalog Replication Mechanism ...... 24 4.2.5 Adjusting XCM Configuration and Creating Shops for New Scenarios ...... 24 4.3 Adjusting the XCM Configuration ...... 24 4.4 Migrating XCM Configuration Data Manually ...... 27 4.5 Performing Follow-Up Activities for Adobe Document Services ...... 28
2012-04-02 PUBLIC 3/38
4.6 Performing Follow-Up Activities for the System Landscape Directory ...... 29 4.7 Performing Follow-Up Activities for BI Java ...... 30 4.8 Checking the KMC Installation ...... 31 4.9 Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) ...... 33
4/38 PUBLIC 2012-04-02 1 Getting Started 1.1 Essential Information: Required Documentation 1 Getting Started
This section of the guide contains important information that you need to read before starting your update or upgrade process.
1.1 Essential Information: Required Documentation You are currently reading the Upgrade and Update Guide – SAP ERP 6.0 Including Enhancement Package 5 Java. This guide only contains information specific to SAP ERP, but you need additional information to be able to perform your upgrade/update correctly.
NOTE Specifically, you need to use the following guide in parallel to the Upgrade and Update Guide – SAP ERP 6.0 Enhancement Package 5 Java: Update Guide – Update of SAP Systems Using Software Update Manager
Additional required documents: WA Make sure that you have downloaded the latest version of the Master Guide – SAP Enhancement Package 5 for SAP ERP 6.0 from the SAP Service Marketplace at: http://service.sap.com/erp-inst SAP ERP 6.0 SAP Enhancement Packages for SAP ERP 6.0 SAP Enhancement Package 5 for SAP ERP 6.0 . WA For SAPJup tool:Upgrade Guide – SAP ERP 6.0 Including SAP Enhancement Package 5 - Technical Usage “Central Applications”. You can download it from http://service.sap.com/erp-inst SAP ERP 6.0 SAP Enhancement Packages for SAP ERP 6.0 SAP Enhancement Package 5 for SAP ERP 6.0 Upgrade Guides - SAP ERP 6.0 EHP5 SAP ERP Java Components
More Information You can access online documentation for all maintained product releases on SAP Help Portal.
2012-04-02 PUBLIC 5/38 1 Getting Started 1.2 Important SAP Notes
Target Release Documentation The documentation for the target release is not available online in your system until you have completed the upgrade/update and the installation procedure for the online documentation. Before the upgrade/update, make sure that you can read the documentation DVD offline. After the upgrade/update, you need to install the documentation for the target release. You can find the SAP Library documentation for SAP ERP 6.0 including SAP enhancement package 5 on SAP Help Portal at: http://help.sap.com SAP Business Suite SAP ERP SAP ERP Central Component SAP Enhancement Package 5 for SAP ERP 6.0 .
1.2 Important SAP Notes
SAP Notes for Preparing the Upgrade/Update You must request the following SAP Notes from SAP Support Portal before you start the upgrade/ update process: % Central Software Update Manager Note (referenced in Update Guide – Update of SAP Systems Using Software Update Manager
Other SAP Notes As well as the SAP Notes you need for the preparation, this document refers you to other SAP Notes that contain additional information. The following list contains these SAP Notes:
Note Number Title Comment 1267573 Central Note: Upgrade to systems based on SAP Contains central information about the Java NetWeaver 7.0 EHP 2 Java upgrade 1484460 EHP 5 for SAP ERP 6.0 SP Stacks – Release and Contains information and references to SAP Information Note Notes for applying Support Package (SP) Stacks of SAP Enhancement Package 5 for SAP ERP 6.0. 998833 Release Restrictions SAP ERP 6.0 - Enhancement Provides information about the limitations for Packages SAP enhancement packages for SAP ERP 6.0
1.3 Naming Conventions
SAP System ID In this document, the SAP system ID is abbreviated as “SAPSID” or “sapsid”. If “
6/38 PUBLIC 2012-04-02 1 Getting Started 1.3 Naming Conventions
Instance Name In this document,
2012-04-02 PUBLIC 7/38 This page is left blank for documents that are printed on both sides. 2 Planning 2.1 Supported Source Releases 2 Planning
This section of the guide contains important information that you need to read before starting your update or upgrade process.
2.1 Supported Source Releases This section provides an overview of the supported upgrade and update paths for SAP ERP. Before the update/upgrade, your SAP system must have one of the source releases that have been released for this update/upgrade and apply to all databases.
CAUTION If you have to apply Support Packages to your source release shortly before the update/upgrade, check whether the equivalent Support Package for the target release is already available. Otherwise, this may delay your update/upgrade schedule.
The following source release versions are supported by the Software Update Manager tool:
;*ð0|LÓO³ÏHÂ¿ß kþÉ´Pea m ç x_I¯ûæ^]6ÒT¶ ;* SAP NetWeaver 7.0 SPS 05 (or higher) and SAP NetWeaver 7.0 including enhancement package 1 with the following usage types: ;* Application Server Java (AS Java) ;* Enterprise Portal (EP) ;* EP Core (EPC) ;* Process Integration (PI) ;* Mobile Infrastructure (MI) ;* BI Java Components (BI-Java) ;* SAP ERP 6.0 (including the SAP enhancement packages up to 4) with the following Java components (technical usages): ;* Biller Direct ;* Self Services (XSS) ;* ERP Business Packages (Portal Content) ;* Extended E-Selling Components (XECO) ;* Learning Solution (Content Player) ;* Utility Customer E-Services (UCES) ;* Retail Store Applications (IS-R-SRS) ;*ú0tLOüÏXÂäHß3kôÉN´We` mBçDX_I¯û§
2012-04-02 PUBLIC 9/38 2 Planning 2.2 Checking Prerequisites
The following source release versions are supported by the SAPJup tool: `6tDtB=AÇ} <ì'ºÊL SAP Web Application Server Java 6.40 SPS 09 (or higher) SAP Portal Platform 6.0_640 SPS 09 (or higher) SAP Exchange Infrastructure 3.0 SPS 09 (or higher) SAP BI 3.5 Java Components (Universal Data Integration / Meta Model Repository) SPS 09 (or higher) SAP Mobile Infrastructure 2.5 SPS 09 (or higher) Adobe Document Services 1.0 SPS 09 (or higher) SAP Knowledge Warehouse 7.0 (Internet Knowledge Servlet 1.0) ISA R/3 Edition (Internet Sales Web Application Components) 4.0 SAP ESS 100 (Employee Self Service) SAP MSS 100 (Manager Self Service) SAP PCUI_GP 100 (Floor Plan Manager) Biller Direct 3.0 Learning Solution (Content Player) 3.0 IPC Web Application Components 4.0 `6tD|BBrA×}G<
2.2 Checking Prerequisites Procedure
Checking the Add-On Compatibility If you have add-ons installed in your system, check if the add-ons are released for enhancement package 5 for SAP ERP 6.0. For information about the add-on compatibility, see SAP Note 1318299.
Checking the Required Target Support Package Stack When you update your SAP system with an enhancement package, you have to include a minimum Support Package stack for the target release into the update. If your source release system has the most recent Support Package Stack level, make sure that this equivalent Support Package stack for the target release is already released. Proceed as follows: 1. Check SAP Notes 1064635 and 1440337 for the required Support Package stacks. 2. Check the Support Package stack schedule on SAP Service Marketplace at http:// service.sap.com/sp-stacks SP Stack Schedule for release date of the Support Package Stack you require.
NOTE Do not apply the latest Support Package stack to the system that you want to update shortly before an update.
10/38 PUBLIC 2012-04-02 2 Planning 2.3 Upgrade Scope for ERP Java Components
*-?[ýûN[f£?7'+cüúNííBg-
2.3 Upgrade Scope for ERP Java Components The upgrade program detects which ERP Java components are installed in your source release system. The versions of the ERP Java components in the target release system depend on your selections in the SAP Solution Manager Maintenance Optimizer. Based on your decision on the ERP usage types that you want to bind with SAP enhancement package 5 into the upgrade, the upgrade program either deploys the ordinary ERP 6.0 component versions, or the enhanced component versions. Since the upgrade program always deploys complete usage types, you may have a larger amount of software components installed in your target release system than in the source release system.
NOTE Since parts of SAP ERP 6.0 including SAP enhancement package 5 - technical usage “Central Applications” Java are deployed on your system, ensure that the corresponding ABAP back end is also enhanced.
Biller Direct Biller Direct 3.0 is upgraded to Biller Direct 6.0 or 6.04. The deployment of the usage type Biller Direct includes the SAP Java Data Dictionary since it contains the XCM database tables.
Self Services (XSS) In SAP ERP 2004, the Self Services (XSS) comprises the software components SAP ESS 100, SAP MSS 100 and SAP PCUI_GP 100. If the upgrade program detects one of these components in the source release system, it deploys the following components: *- SAP ESS (SAP Employee Self Service) 603 *- SAP MSS (SAP Manager Self Service) 600 *- SAP PCUI_GP (SAP Floor Plan Manager) 600 or 603 *- SAP PSS (SAP Project Self Service) 600 *- SAP ASR (SAP HCM Administrative Services) 600 *- IS-HER-CSS (SAP for Higher Education and Research Industry Solution) 600 If SAP Enterprise Portal 6.0 and ERP 2004 Business Packages are installed in the same system as Self Services (XSS), the portal is upgraded by default to SAP NetWeaver 7.0 including enhancement package 2 usage type Enterprise Portal and the ERP 2004 Business Packages are upgraded to the new ERP Business Packages (Portal Content, Portal Content Common and Portal Content Self Services). If no Enterprise Portal and no Business Packages are present on the Self Services host, then the upgrade program automatically installs SAP NetWeaver 7.0 including enhancement package 2 usage type EP Core and ERP Business Packages (Portal Content, Portal Content Common, and Portal Content Self Services).
2012-04-02 PUBLIC 11/38 2 Planning 2.3 Upgrade Scope for ERP Java Components
For more information about the upgrade strategies for Self Services and ERP Business Packages, see the Upgrade Master Guide – SAP ERP 6.0 on SAP Service Marketplace at http://service.sap.com/erp- inst. For information about the upgrade of a distributed ERP 2004 system landscape, see SAP Note 879335.
CAUTION Be aware of the following restrictions: If you upgrade Self Services (XSS), you must also upgrade the SAP ERP Central Component (SAP ECC). You cannot run the upgraded Self Services with SAP ECC 5.0. As of SAP NetWeaver 7.0, the wdDoExit() plug is no longer supported for navigating between Web Dynpro applications within the portal. This might effect Business Packages like Employee Self Services that are still using this functionality on top of SAP NetWeaver ´04. After the upgrade to SAP NetWeaver 7.0 including enhancement package 2, applications based on Web Dynpro might not work properly. You either need to use the new navigation mechanism, or run the Web Dynpro application on a separate SAP NetWeaver ´04 system. For more information, see SAP Note 895224.
ERP Business Packages (Portal Content, Portal Content Common, and Portal Content Self Services If the upgrade program detects an Enterprise Portal and ERP Business Packages installed in the source release system, the Enterprise Portal is upgraded to SAP NetWeaver 7.0 including enhancement package 2 usage type Enterprise Portal and the ERP 2004 Business Packages are upgraded to the new ERP Business Packages (Portal Content, Portal Content Common and Portal Content Self Services). If ERP Business Packages are installed in your source release system but usage type Enterprise Portal is not installed, the upgrade program automatically installs SAP NetWeaver 7.0 including enhancement package 2 usage type EP Core and upgrades the ERP Business Packages.
Extended E-Selling Components (XECO) The Extended E-Selling Components (XECO) are the successors of SAP Internet Sales R/3 Edition (Internet Sales Web Application Components) 4.0 and Internet Pricing and Configurator Web Applications (IPC-WAC) 4.0.
NOTE SAP Internet Sales (R/3 Edition) has been renamed to SAP E-Commerce for SAP ERP.
If the upgrade program detects one of these predecessor components and you bind Extended E-Selling Components (XECO) into the upgrade, it deploys the following components included in XECO: SAP Shared Java Applications 7.0 SAP Java Data Dictionary 7.0 CRM IPC Mobile 7.0 ERPXECOUT 6.04
12/38 PUBLIC 2012-04-02 2 Planning 2.4 Upgrade of Multiproduct Java Systems
CAUTION If you want to run SAP E-Commerce 5.0 with a back-end release between SAP R/3 4.6C and SAP ECC 5.0 and want to use the Internet Pricing and Configurator, you have to install SAP NetWeaver 7.0 Application Server ABAP including SAP Application Platform (SAP AP). This is due to the architectural changes of the Internet Pricing and Configurator, which is no longer a separate server but part of SAP AP and processed on ABAP application servers. To install SAP NetWeaver 7.0 Application Server ABAP and SAP AP, proceed as described in the following documentation: n× Installation Guide – SAP NetWeaver 7.0
Learning Solution (Content Player) Learning Solution 3.0 is upgraded to Learning Solution 6.0 or 6.04, which does not include any further components.
Utility Customer E-Service (UCES) The deployment of the usage type SAP Utility Customer E-Service (UCES) 6.05 includes the SAP Java Data Dictionary since it contains the XCM database tables.
Retail Store Applications (IS-R-SRS) The usage type SAP Retail Store Applications (IS-R-SRS) 602 is needed to run the industry scenario “SAP Retail Store Application”. n×o å¼oÈûógP¸ÙM
2.4 Upgrade of Multiproduct Java Systems The upgrade program can now handle the upgrade of multiproduct Java systems based on SAP NetWeaver 7.0. If you use SAP ERP 6.0 together with other Business Suite applications on a central Java system based on SAP NetWeaver 7.0 and you want to upgrade the non-ERP application or implement SAP enhancement package 5 for SAP ERP 6.0, familiarize yourself with SAP Note 1267054.
2012-04-02 PUBLIC 13/38 This page is left blank for documents that are printed on both sides. 3 Preparation 3.1 Free Space Requirements 3 Preparation
This section of the guide contains important information about preparatory tasks that you need to do before starting your update or upgrade process.
3.1 Free Space Requirements Make sure that at least the following free space is available in the system that you want to update (upgrade):
Upgrade/Update Directory Approximately 10 GB Download Directory (temporary space requirement) Approximately 10 GB Free space in the database Approximately 15 GB
GaÃ.æZ"] ÓºãQfB-ÚkúÁ ÆàiÓ 6®õâqd²,SOcû(8ãú©Å¿A}'x
3.2 Preparing the Upgrade of Internet Sales (R/3 Edition) Web Application Components The default upgrade process is to first copy your SAP Internet Sales (R/3 Edition) system and then upgrade this copy to SAP E-Commerce 5.0. If you follow this procedure, your source release system is kept as a backup. If you do not want to create a system copy, you have to make sure that the XML files that contain the shop data are not stored in a directory within SAP Web AS.
NOTE During the upgrade, the Internet Sales Web Application Components 4.0 are undeployed.
Procedure
Creating a System Copy Create a system copy as described in the documentation Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP Web Application Server Java 6.40 SR1. The documentation is available on SAP Service Marketplace at http://service.sap.com/ instguides SAP NetWeaver Releases ´04 Installation SAP Web AS SAP Web AS 6.40 SR1 and Related Documentation .
Preserving Shop Data In Internet Sales (R/3 Edition) 4.0, the data of the Shop Management Web Application was stored in XML files in the file system. In SAP E-Commerce 5.0, this data is stored in the database of SAP NetWeaver
2012-04-02 PUBLIC 15/38 3 Preparation 3.3 Cleaning Up the Universal Worklist Cache
AS Java. After you have performed the upgrade, you have to import the XML files manually (see section Upgrading the Shop Management Data [page 20]).
NOTE You only have to perform the steps below if you want to upgrade your system without performing a system copy first.
Before you start the upgrade, make sure that the XML files that contain the shop data are not stored in a directory within SAP Web AS. The path to these files is defined in the Extended Configuration Management (XCM) of the Shop Management Application. Perform the following steps to make sure that your data is not deleted during the upgrade: 1. Log on to the XCM of the Shop Management Web Application by entering http://
3.3 Cleaning Up the Universal Worklist Cache Before the upgrade, you must clean up the UWL cache since otherwise the UWL database upgrade fails.
Prerequisites This step is only required if Knowledge Management and Collaboration is installed in your source release system.
16/38 PUBLIC 2012-04-02 3 Preparation 3.4 Undeploying the Software Component NetWeaver Mobile Administration (NWMADMIN)
Procedure 1. Log on to the Portal with role Super Administrator. 2. Choose System Administration System Configuration Universal Worklist and Workflow Universal Worklist Administration . 3. Choose All Systems from the drop-down list and then Clear Cache. 0pºw¹¢7«äüxÈ&¢·åçn· ÏÊç'PP 0p°w¹¢?«½ü7È6Ô¢ûåËn½ WÏÉç%P¡Ñ[<\£+WGN5 IÎxY
3.4 Undeploying the Software Component NetWeaver Mobile Administration (NWMADMIN)
NOTE This section only applies if your source release system is based on SAP Web AS 6.40.
If your source release system has a Support Package Stack level 6.40 SPS 15 or higher, and you have the software unit Mobile Infrastructure (MI) installed with the option "Old Technology", you must undeploy the software component NetWeaver Mobile Administration (NWMADMIN) before you start the upgrade procedure.
Procedure 1. Log on to the SAP system. 2. Start the SDM GUI and logon to the SDM Server. 3. Choose the Undeployment tab page. 4. Select the following components: 0 tc/mobile/admin/ea 0 tc/mobile/admin/mds/service 0 tc/mobile/admin/services 0 tc/mobile/admin/ui 0 tc/mobile/admin/ump 0 tc/mobile/monitor/ui 5. Choose Start Undeployment and confirm the undeployment. 0pºw¹¢7«äüxÈ&¢·å÷n© ÏÝç3PG¡Q[\Ç¢£ +TJ
2012-04-02 PUBLIC 17/38 This page is left blank for documents that are printed on both sides. 4 Follow-Up Activities 4.1 Performing Follow-Up Activities for the E-Commerce User Management 4 Follow-Up Activities
This section of the guide describes application-specific steps that have to be done after the update or upgrade process is complete.
¦Sn2ÿùï·'°³]ý4³«³ ¯B/Òx»¹dF¡Gµ¶sc!¸vÉ}%%ǬÕzAIGRf¡I!D nkk/µ£ JΣ 4.1 Performing Follow-Up Activities for the E-Commerce User Management As of SAP E-Commerce 5.0, new user roles are provided. The old user roles are no longer supported. For each Web application, a service user role and at least one Internet user role are available. For more information about the available roles, see the documentation in the Solution Manager. Due to these changes, you have to perform updates in the user management as outlined below. Procedure Updating Customized User Roles Adjust your user role copies according to the authorizations provided in the new application user roles. We recommend to create role copies and to refine authorizations with own authorization values. Creating Service Users It is now possible to have a service user for each application. You have to create service users and to assign them the appropriate service user role. You also have to create new customer JCO components in the Extended Configuration Management (XCM) of your E-Commerce applications, which you can then select in the user settings of your XCM application configurations. Assigning Roles to Web-Based User Management You have to assign new user roles to the Web-based user management by using the following IMG activity: CRM E-Commerce Basic Settings for E-Commerce Internet User Web-Based User Management Set up Roles for Web-based User Management Furthermore adjust the role mapping to Enterprise Portal roles if your E-Commerce applications run in an Enterprise Portal. For more information, see SAP Note 713472. Assigning Roles to the Reference User You have to assign new user roles to the reference users created for the E-Commerce Business-to- Consumer (B2C) application or for the Web-based user management application. 2012-04-02 PUBLIC 19/38 4 Follow-Up Activities 4.2 Additional Follow-Up Activities for SAP E-Commerce Internet User You have to assign new user roles to your existing Internet users for the E-Commerce applications they have to use. To apply mass user changes, use the User Mass Maintenance (transaction SU10). CTG5×IN$rØøàÿ¶8,K!|ÕÝý«òÙ¢èGÝ 3ð®7ÎÝæ29ã¸Xì4·À ²Â[£P¬BºbîWrD#ã CTM5×I$=Øèà¤ú8K!;ÕÉý¥òÏýèGä }ð 7ýÝÅ2zã¹´Xÿ4¸ C²ý[¯P¿ Bµbì\&(DmãØèºÅhǸ¥âYG 4.2 Additional Follow-Up Activities for SAP E-Commerce In addition to adjusting the XCM configuration [page 24] and the user management [page 19], you have to perform the following follow-up activities for SAP E-Commerce for SAP ERP: C Upgrading the Shop Management Data [page 20] C Performing Adjustments to the Java Class Changes [page 21] C Checking the Login Configuration [page 23] C Replacing the Catalog Replication Mechanism [page 24] C Adjusting XCM Configuration and Creating Shops for New Scenarios [page 24] CTM5×I$=Øèà¤ú8K!;Õ 4.2.1 Upgrading the Shop Management Data In SAP E-Commerce 5.0, the customizing data of the Shop Management Application is stored in the database of SAP NetWeaver AS Java, while in previous releases the shop data was stored in the file system in xml format. Prerequisites C You have access to the files that contain the shop data from ISA (R/3 Edition) 4.0. C You have created an XCM application configuration for the Shop Management Web Application (Shopadmin). The Shop Management Web Application is automatically installed with SAP E- Commerce 5.0. The parameter object-path of the shop component must contain the path to the XML files that contain the shop data from ISA (R/3 Edition) 4.0. Procedure 1. Call the SAP E-Commerce Administration Console of the web application Shopadmin in the upgraded system. To do so, enter http:// 20/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.2 Additional Follow-Up Activities for SAP E-Commerce NOTE The shops are stored in such a way that they depend on the ERP system ID and client. Therefore, you might have to migrate the shop data from the file system to the NetWeaver Application Server database more than once, depending on how many systems and clients you are using in your landscape. w8÷RQÀÛë-K®ç¹^Æ 4.2.2 Performing Adjustments to Java Class Changes The following sections describe changes that have been made to Java classes. If you have modified these classes in the source release, you have to adjust your modifications to the new developments. As a prerequisite to run SAP E-Commerce 5.0, you must install the R/3 Plug-In 2004 SP10 for SAP R/3 4.6C and R/3 Enterprise. The former Plug-In function modules are an integral part of mySAP ERP 2004 and SAP ERP 6.0. Obsolete Classes In SAP Internet Sales (R/3 Edition) 3.1 and 4.0, some specific back-end classes and algorithm classes had been used if no R/3 Plug-In was available or if the R/3 release was SAP R/3 4.6C or lower. These classes are not used anymore. However, they are still delivered for documentation reasons: w8 com.sap.isa.backend.r3.shop.ShopR3 w8 com.sap.isa.backend.r3.salesdocument.rfc.CCardStrategyR340b w8 com.sap.isa.backend.r3.salesdocument.rfc.CreateStrategyR340B w8 com.sap.isa.backend.r3.salesdocument.rfc.CreateStrategySimRFC w8 com.sap.isa.backend.r3.salesdocument.rfc.DetailStrategyR340b w8 com.sap.isa.backend.r3.salesdocument.rfc.DetailStrategyR3PI40 Incompatible Java Changes in Back-End Classes for SAP E-Commerce for SAP ERP This section is only relevant if you have implemented extensions in the back-end classes for SAP E- Commerce for SAP ERP. These back-end classes are included in the following packages (or subpackages of these packages): w8 com.sap.isa.backend.r3base w8 com.sap.isa.backend.r3 w8 com.sap.isa.user.backend.r3 w8 com.sap.isa.businesspartner.backend.r3 The following classes are affected: w8 Class ChangeStrategy Method public boolean dequeueDocument has a new parameter of type SalesDocumentR3. In releases SAP R/3 4.6C to mySAP ERP 2004, an update is performed for this sales document to remove all locks. The same was performed in SAP Internet Sales (R/3 Edition) 4.0, but at a different place. 2012-04-02 PUBLIC 21/38 4 Follow-Up Activities 4.2 Additional Follow-Up Activities for SAP E-Commerce In SAP ERP 6.0, the ChangeStrategy class has been reimplemented. This new implementation is called com.sap.isa.backend.r3.salesdocument.rfc.ChangeStrategyERP. It enables a better lock handling performance. t# Class Extension The Extension class has been moved from com.sapmarkets.isa.backend.r3.salesdocument to com.sapmarkets.isa.backend.r3base. t# Class ServiceR3IPC t# Method protected void customerExitBeforeDocumentCreation now uses the Map class instead of the HashMap class. t# Method protected void customerExitAddKNVVParameters has been removed. Instead, a new exit protected void customerExitBeforeHeaderAttributeCall is available. Note that the function module ISA_PRICING_HDRDATA_GET is now used to read the header attributes. This function module reads more attributes than only those from table KNVV. t# Class ShopBase Method protected Set readSalesAreas() now returns the Set class instead of the Map class. t# Class StatusStrategyR3 t# An additional parameter of type ReadStrategy has been introduced in the constructor of StatusStrategyR3. This change also applies to the derived class StatusStrategyR3PI. t# ClassStatusStrategy is no longer used for the search of sales documents, since a new search framework has been implemented. t# Class WriteStrategyR3 A new parameter of type JCoConnection has been introduced for method protected String convertProductIds. This parameter was necessary because of a new back-end call that converts material numbers from internal to external format and the other way round. The method also issues a back-end exception now. This change also applies to method protected void setItemProductInfo. Changes in Functionality of Class WriteStrategyR3 t# Method public void setPartnerInfo: In 3.1 and 4.0, a manually entered ship-to address in B2B got the sold-to ID as key and not the underlying ship-to ID. In SAP E-Commerce for SAP ERP 5.0, this behavior has been changed. If you create a new ship-to address in the basket on the basis of an existing ship-to address, it gets the ship-to ID as key in the ERP order. EXAMPLE Sold-to ID is 1000, ship-to ID is 1010. The ship-to address is “Becker Berlin, 12 Lagerhausstrasse”. The end-user changes this address to “Becker Berlin, 20 Lagerhausstrasse”. As a result, a manual address will appear in the ERP order (on header or on item level) with key 1010. 22/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.2 Additional Follow-Up Activities for SAP E-Commerce ñ Method protected void shipToDataToRFCSegment: A manually entered ship-to address gets its language from the shop and not from the master data ship-to address (as in release 4.0). 4.2.3 Checking the Login Configuration As of SAP E-Commerce 5.0, we recommend that you use the SU01-based login configurations. Check the following sections if you have used an SU05-based login configuration in your source release. Procedure B2B XCM Default for Login Configuration The default user configuration for ERP E-Commerce has changed from SU05 (R3_SU05Customer_LoginCustomerNo) to SU01 (R3_SU01UserContactPerson) in XCM. If you have not changed the default setting, you will use the SU01-based configuration. Review your login configuration settings in XCM (usertype) at Application configurations Customer Role Assignment for Anonymous SU05 User SAP E-Commerce 5.0 introduces special authorization roles. Authorization roles have been defined that contain the SD authorization objects and new E-Commerce specific objects, for example, to view certain documents in ERP E-Commerce. When ERP E-Commerce runs with an SU01-based login configuration, you have to assign certain roles to the actual E-Commerce user (for example, SAP_ISA_B2B_FULL) and some to the anonymous user that is defined in XCM (for example SAP_ISA_B2B_RFC). For more information about the available roles, see the configuration documentation for ERP E-Commerce User Management in SAP Solution Manager. You cannot assign authorization roles to SU05 users. In that case, all checks are performed against the anonymous user. Make sure that the anonymous user that you define in XCM has the corresponding role for the RFC user (for example, SAP_ISA_B2B_RFC or SAP_ISA_B2C_RFC) and also the necessary application roles (for example, SAP_ISA_B2B_FULL). User migration from SU05 to SU01 You can migrate your existing SU05 user accounts to SU01. After you have migrated the accounts, the system generates an SU01 user the first time an SU05 user logs on to the upgraded ERP E-Commerce application. For detailed information about the migration procedure, see the configuration documentation for ERP E-Commerce User Management in the SAP Solution Manager. Note that you must assign the authorization role SAP_ISA_UADM_MANAGER to the anonymous RFC user for the migration period in addition to the already assigned roles. Otherwise, no new SU01 accounts can be created. 2012-04-02 PUBLIC 23/38 4 Follow-Up Activities 4.3 Adjusting the XCM Configuration 4.2.4 Replacing the Catalog Replication Mechanism As of E-Commerce 5.0, an ABAP report replicates the ERP product catalogs to Search and Classification (TREX). It replaces the trexr3 J2EE application. The report provides a Business Add-In (BAdI) which you can use to adapt the retrieval and formatting of catalog data individually. The catalog data is transferred directly from the ERP system to TREX using an RFC protocol. This means that the J2EE Engine is not involved in the replication process and the running applications are not affected, neither in terms of memory usage, nor in terms of CPU usage on the J2EE Engine. Procedure To start the report, call transaction ISA_CAT_REPLICATION. You can also schedule the report as a job. 4.2.5 Adjusting XCM Configuration and Creating Shops for New Scenarios If you are running the scenarios “Business-On-Behalf” and “Catalog and Order Management for Internal Users”, you have to perform adjustments in the XCM configuration and create new shops. Both scenarios have in common that the sold-to party is selectable during the order creation process. Procedure Adjusting XCM Configuration Change the parameter shopdata as follows: ê- If you run the “Business-On-Behalf” scenario, change it to r3shop_bob ê- If you run the “B2B for internal users”, change it to r3shop_agent Creating Shops You cannot use existing shops for the two new scenarios. Instead, you have to create new shops as follows: 1. Create a new shop. 2. Specify the scenario. 3. Copy the shop data from an existing shop that you have uploaded as described in Upgrading the Shop Management Data [page 20]. ê-V-eýhõwf×|¥4w@){àÕÕæ*-«eZ¬æèXgv(yu ë~µëD¿N=´ÀùÝi®»iá£Gs·¨P¶3pzö©çÅ ê-V'eýhõLÏw=×Ö|4}@a{çÕÔæ;-ôe¬Ö èKg$(Hp ëµµë¿i^=´ÂùËiÑ®iä°Gb·¢P3Wpñ©ÚÅBàð ãëëÃJeÛÉ 4.3 Adjusting the XCM Configuration In SAP ERP 2004, the Extended Configuration Management (XCM) has been used to configure the applications. The customizing data was stored in XML files (scenario-config.xml and config- data.xml) in the file system. As of SAP ERP 6.0, the customizing data is stored in the database of SAP 24/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.3 Adjusting the XCM Configuration NetWeaver AS Java. You have to check and adjust the configuration settings after the upgrade. For information about using the Extended Configuration Management (XCM) Administration tool, see the document Installation Guide - SAP ERP Procedure Entering Passwords If you used the secure storage to encrypt passwords in the source release system, you have to reenter each password after the upgrade. Whenever XCM data was modified, the secure storage was used. Performing Adjustments to New Connection Concept In the new release, each session is by default switched to https. To be able to log on to a web application, you have to check the XCM settings. Proceed as described below and adjust the XCM configuration: 1. Access the admin area of your web application (http:// NOTE To be able to switch to the https connection, you have to enable https by using the Visual Administrator of your NetWeaver Application Server Java. Checking the XCM Configuration In the new release, some new parameters and components are required in the XCM configuration. Furthermore, some of those that have been used on the source release are no longer required. Those parameters, that are no longer used are highlighted in yellow and their description starts with ‘OBSOLETE’. The description also contain information about what is used instead, or why the parameter is no longer required. You have to check the complete configuration of each web application and perform all required configuration steps. 2012-04-02 PUBLIC 25/38 4 Follow-Up Activities 4.3 Adjusting the XCM Configuration NOTE You do not have to remove the obsolete parameters or components from the configuration. fºï/ SóxRãaª¨\ý/ñÛF¡s§9UB£ïe ^añ·6? E-Service Configuration Parameters For E-Service, the table below provides you with an overview of all parameters that were used in CRM 4.0 and the parameters that are used in CRM 5.0 and higher: CRM 4.0 CRM 5.0 and higher ATTACHMENTS attachments — available_functions COMPLAINT complaint — email FORGOT_PASSWORD_FORM forgot_password IBASE ibase ims ims jco jco — live_web_collaboration — login MINE_TYPES_ICONS mines_types_icons PRODUCT_CATALOG product_catalog PRODUCT_REGISTRATION product_registration PRODUCT_SELECTION product_selection REGISTER register SERVICE_CONTRACT service_contract SERVICE_REQUEST service_request SOLUTION_SEARCH solution_search — store_locator — transaction — ui SAP_API — FIRST_FUNCTION — IBASE_SELECTION — ICSS_LWC_ENABLE — REQUEST — USER_ID — EMAILSIZE — FUNCTION_AVAILABLE — fºå/ [ªx ã:ªä\×/ÇÛûFçs*U£®eà 26/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.4 Migrating XCM Configuration Data Manually Replacing Component UI Configuration The SAP configuration __backwardcompability_only__ for the component UI is no longer supported as of SAP E-Commerce 5.0. If you are using this component configuration or your own customer configuration, which derives from this configuration, you have to create a new configuration for the component UI derived from the SAP configuration default or default-hom. 7ÓMþÑá_¡à(Äë9:Öקº»¦íuà©/ó¯ßW UÙc{fdèÇ Dú½Ã1 ¶ÞoÅDV XÚ$QÄ|¶·ÎÓ½ÐuÌ< ±ðε, 7ÓGþÑ áîà8Ä°9vÖ맺ü¦ùuà¿/¬¯öWpUüc`fiàÇ ¦½§¶Þ~Å6D5 NÚ[$KQë~¶µÎAÓÞÐdÌ°<í±Êλ,¹d¤Lù¹i 4.4 Migrating XCM Configuration Data Manually The Software Update Manager migrates the XCM configuration data automatically from the file system to the database of SAP NetWeaver Application Server Java. In case of an error, this data might not be available after the upgrade and you have to upload the data manually. Prerequisites You have access to the directory, where the configuration files from the source release web applications are stored. Procedure 1. Access the SAP E-Commerce Administration Console of the web application for which you want to import the configuration (http:// 2012-04-02 PUBLIC 27/38 4 Follow-Up Activities 4.5 Performing Follow-Up Activities for Adobe Document Services â/@i°è/låXõÍÌ <¨ÔZNØÀ7E ÆRÔ½Û,de¹öVIO¾ù;`Û 4.5 Performing Follow-Up Activities for Adobe Document Services To use Adobe Document Services after the upgrade, you must perform certain follow-up activities. The follow-up activities mainly depend on the situation in your source release, that is, whether ADS was configured in your source release or not. The Adobe Document Services Configuration Guide is available in SAP Library at http://help.sap.com/ netweaver SAP NetWeaver 7.0 including Enhancement Package Procedure â/ ADS was not configured in your source release (SAP NetWeaver 2004) Perform the complete ADS configuration as described in the Adobe Document Services Configuration Guide. â/ ADS was configured in your source release Perform the following configuration steps: â/ Create a new http destination to SAP NetWeaver Application Server ABAP with the name FP_ICF_DATA_ 28/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.6 Performing Follow-Up Activities for the System Landscape Directory 0s´x«Àé6 àGMQ {ɧÊ[#A] 4.6 Performing Follow-Up Activities for the System Landscape Directory 0s´x«Àé6 àGMQ {ɧÊ[#A]¼áÒ¯!ÜÄ[tÊù, NOTE If you used the PI-specific configuration wizard to automate a number of certain follow-up activities, yo do not need to perform this follow-up step. It has been covered by the wizard. 0s´r«Àé>Üà MA ÑÉÊM#]¹ëÒ®!Ä The follow-up activities that you have to perform for the System Landscape Directory (SLD) depend on the situation in your source release system, that is, whether SLD was configured or not. Procedure 0s If the SLD was configured in your source release system, you must only perform the following two actions to enable the use of SLD in the upgraded system: 0s Configure the user management Define security roles and assign users to these roles. Proceed as described in the SAP Library for your target release at: http://help.sap.com/ netweaver SAP NetWeaver 7.0 including Enhancement Package 2012-04-02 PUBLIC 29/38 4 Follow-Up Activities 4.7 Performing Follow-Up Activities for BI Java Proceed as described in the SAP NetWeaver Library at: http://help.sap.com/netweaver SAP NetWeaver 7.0 including Enhancement Package 4.7 Performing Follow-Up Activities for BI Java If you have already used Information Broadcasting (IB) in the source release system, you only have to perform configuration steps for two new components – BI Reporting and Planning and BI Webdynpro ALV. If you have not configured Information Broadcasting in the source release, you have to perform the complete BI Javaconfiguration, that is, the configuration of BI Information Broadcasting, BI Reporting and Planning, and BI Webdynpro ALV. As of SAP NetWeaver 7.0, BI Universal Data Integration (BI UDI) is an integral part of SAP NetWeaver Application Server. BI UDI allows the integration of external data sources by using BI Java Connectors. You need to complete the necessary follow-up activities and configuration tasks to make use of the connectors. Procedure Configuration of BI Information Broadcasting For information about the configuration of BI Information Broadcasting, see the SAP Implementation Guide (IMG) at SAP NetWeaver Business Warehouse Settings for Reporting and Analysis Settings for Information Broadcasting 30/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.8 Checking the KMC Installation Configuration of BI Reporting and Planning You have to create a RFC connection to the Adobe Server. For detailed information, see IMG at SAP NetWeaver Business Intelligence Settings for Reporting and Analysis and SAP NetWeaver Business Intelligence BI Integrated Planning Configuration of BI Web Dynpro ABAP ALV You have to create RFC destinations and Web Service destinations as described in the IMG at Application Server Web Dynpro for ABAP Set-Up Printing for Web Dynpro ABAP ALV . Configuration of BI UDI For information about the configuration of BI UDI, see the IMG at SAP NetWeaver Business Intelligence UDI Settings by Purpose. §ì>V3¥)ÆåþÅgP5vôà §ì>V3¥!å±JÅÎgl!v@ôàõ¯+§ò°µl3YNI&yVñ 4.8 Checking the KMC Installation As of SAP NetWeaver 7.0, Knowledge Management and Collaboration is an integral part of usage type Enterprise Portal. The Software Update Manager automatically installs KMC during the upgrade if it has detected an Enterprise Portal 6.0_640 installation plus installation of the component PDK for MS.NET in the source release system. After the upgrade has finished, you can perform some checks to see whether the KMC installation succeeded. Use the KM Content iView and the KM Component Monitor to find out whether you can start up the system without any errors. If you find errors, then check the deployment and the log files. Procedure Checking the KM Content iView 1. Log on to the portal as a user with the super administrator role. 2. Choose Content Administration KM Content and check whether any errors are displayed. Checking the Component Monitor 1. Log on to the portal as a user with the super administrator role. 2. Choose System Administration Monitoring Knowledge Management Component Monitor . 3. For Filters, Repository Managers, Repository Services and Services, check whether all subentries have the status green. The colors beside the entries indicate the following: §ì Green shows the object is functioning well. §ì Red shows the object cannot be started or is configured incorrectly. §ì Yellow indicates that one or more lower-level items are red. 4. If an object has the status red, read the error message. Try to correct the error in the system configuration. 2012-04-02 PUBLIC 31/38 4 Follow-Up Activities 4.8 Checking the KMC Installation For more information about the configuration, see the online documentation at http:// help.sap.com/netweaver SAP NetWeaver 7.0 including Enhancement Package Checking the Deployment If the portal does not start up after the installation, or you notice errors in the Content Management component monitor, then check the deployment. When you check the deployment, examine both the application and content files. 1. Switch to the directory that contains the deployment files for the Content Management and Collaboration applications: t¨» ²ÚfSMØbB0 øèàp /usr/sap/ t¨»²ÚnSØ-B t¨» ²ÚfSMØbB0 øèàpæ¬ /usr/sap/ t¨»²ÚnSØ-B Î ´è t¨» ²ÚfSMØbB0 øèàpæ¬ t¨»²ÚnSØ-B Î 2. Check whether any of the following files have the extension .err: t¨ com.sap.km.* t¨ com.sap.netweaver.* t¨ com.sap.workflow.* If any files have the ending .err this indicates that the deployment was executed, but an error occurred. In this case, find out the reason for the error in the corresponding log file. The log file has the same name as the .err file, but the extension is .log. 3. Switch to the directory that contains the files for the deployment of CM and Collaboration content: t¨» ²ÚfSMØbB0 øèàp /usr/sap/ t¨»²ÚnSØ-B t¨» ²ÚfSMØbB0 øèàpæ¬ /usr/sap/ t¨»²ÚnSØ-B Î ´è 32/38 PUBLIC 2012-04-02 4 Follow-Up Activities 4.9 Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) KÓ1ý0f²SAég ù1¹>3´_¬? KÓ;ý0n² A¦gùj 4. Check whether any of the following files have the extension .err: K com.sap.km.* K com.sap.netweaver.* K com.sap.workflow.* If any of the com.sap.km* files have the ending .err, check the corresponding .log file to find out what caused the error. Also check the AS Java log files mentioned below. Checking the Log Files If the portal does not start up after the installation of Content Management and Collaboration or you notice errors in the KM Content iView, then check the available trace file. 1. Switch to the directory: KÓ1ý0f²SAég ù1¹>3´_¬? KÓ;ý0n² A¦gùj KÓ1ý0f²SAég ù1¹>3´_ /usr/sap/ KÓ;ý0n² A¦g KÓ1ý0f²SAég ù1¹>3´_¬?Õý /usr/sap/ KÓ;ý0n² A¦gùjõ> 2. Open the file defaultTrace.*.trc with the most recent date. If errors appear in the trace file, try to solve them and then restart the AS Java. NOTE You can also view the trace file using the Log Viewer that is available in the SAP NetWeaver Administrator. KÓ;ý0n² A¦gùjõ>´K¬xÁý4 Ã)ì:>«ªï/ KÓ1ý0f²SAég ù1¹>3´_¬?Õý: Ãvl:²>I«ï3Ò×°B1 4.9 Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) The follow-up activities for Knowledge Management and Collaboration are different depending on whether you have used KMC in the source release or not. 2012-04-02 PUBLIC 33/38 4 Follow-Up Activities 4.9 Performing Follow-Up Activities for Knowledge Management and Collaboration (KMC) Procedure KMC Was Not Configured in SAP NetWeaver 2004 To be able to use the basic features from Knowledge Management and Collaboration, you have to perform the minimal configuration tasks. These steps are also required if you want to use the Running an Enterprise Portal scenario. ã For Knowledge Management, see the following documentation for the basic configuration tasks: http://help.sap.com/netweaver SAP NetWeaver including Enhancement Package KMC Was Configured in SAP NetWeaver 2004 ã Check whether the link to the Collaboration Launch Pad is available in the tool area of the portal masthead. If the link is not available, you need to activate it. For more information, see the SAP NetWeaver Library at: http://help.sap.com/netweaver SAP NetWeaver including Enhancement Package 34/38 PUBLIC 2012-04-02 Typographic Conventions Example Description 2012-04-02 PUBLIC 35/38 SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com © Copyright 2012 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, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/ OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. 36/38 PUBLIC 2012-04-02 Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. 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. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap.com/instguides 2012-04-02 PUBLIC 37/38 SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com © Copyright 2012 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.