SAP AG 1

SAP AG 2005
SRM 6.0
Upgr ade
SAP AG 2
SAP AG 2006
Obj ec t i ves
Contents
mySAP SRM Upgrade
Objectives
At the end of this chapter, you will be able to:
Plan your upgrade from the information you obtain from the
Master Guide
Describe the SRM specific upgrade sequence
Describe the SRM specific upgrade tasks
SAP AG 3
SAP AG 2006
How t o use t he Gui des
Master Guide mySAP SRM
Section Technical Overview describes the
Installation Sequence per Technical
Landscape
Section Key Functional Areas describes in
which Functional Areas the Instance SAP
SRM is used
Section Software Components Overview
describes which technical subcomponents
(IPC, LAC, PI ) are required for the instance
SAP SRM
Upgrade Master Guide
Describes the installation of each usage
type step-by-step
Already available fr SRM Server 6.0 and
the mySAP SRM 6.0 components
SAP AG 4
SAP AG 2005
SRM Upgrade
LAC WPS Upgrade
Optional installation means, that the installation is only required for certain SRM scenarios. In addition, a
component might also be optional within a certain SRM scenario. See chapter SRM Architecture for
details.
SAP AG 5
SAP AG 2006
Upgr ade Roadmap
The Upgrade Roadmap (/nRMMAIN) is shipped with Solution Manager 3.2
It is a very useful tool planning upgrade projects.
The major part of it is generic, but it also contains some SRM-specific content.
Make sure, that ST-ICO 150 PL1 or higher is installed on your Solution Manager.
The Upgrade Roadmap (/nRMMAIN) is shipped with Solution Manager 3.2
It is a very useful tool planning upgrade projects.
The major part of it is generic, but it also contains some SRM-specific content.
Make sure, that ST-ICO 150 PL1 or higher is installed on your Solution Manager.
Call transaction /nRMMAIN to launch the upgrade roadmap in the SAP Solution Manager
SAP AG 6
SAP AG 2006
SRM Upgr ade Pr er equi si t es
Source Release Minimum Support Package Level
BBPCRM
SP
SAP_BASIS
SP
SAP_ABA
SP
SAP EBP 2.0B SR2
(BBPCRM2.0B)
SP05 46C SP07 46C SP07
SAP SRM 2.0
(BBPCRM3.5)
SP04 620 SP28 620 SP28
SAP SRM 3.0
(BBPCRM4.0)
SP04 620 SP28 620 SP28
SAP SRM 4.0 SR1
(BBPCRM5.0)
SP04 640 SP09 640 SP09
For further details, see SAP Notes 826487 and 852894
For further details, see SAP Notes 826487 and 852894
SAP EBP 2.0C SR1
(BBPCRM2.0C)
SP02 46D SP07 46D SP07
SAP EBP 3.0 SR1
(BBPCRM3.0)
SP06 610 SP06 610 SP06
Systems with MDMP (Multi-Display-Multi-Processing) codepage are not supported for SRM Server.
Customers who are using an SRM System on MDMP basis have to convert to Unicode. SRM goes here in
line with the mySAP ERP strategy.
For additional information on this topic, see SAP Notes 79991 and 896144
SAP AG 7
SAP AG 2006
Pr er equi si t es f or Bac k end Syst ems
The following prerequisite patch levels apply, depending on the
release of the SAP R/3 System:
SAP R/3 3.1I: SAPKH31I97 and SAPKE31I87
SAP R/3 4.0B: SAPKH40B72
SAP R/3 4.5B: SAPKH45B50
SAP R/3 4.6B: SAPKH46B49
SAP R/3 4.6C: SAPKH46C39
SAP R/3 Enterprise 4.70: SAPKH47008
See also SAP Note 441892 Integration of External Requirements
from PS/PM/MRP in EBP 3.5/4.0.
SAP AG 8
SAP AG 2006
SRM Upgr ade & Mi gr at i on (1)
In case an old, standalone IPC is used: Uninstall the old release of
SAP Internet Pricing Configurator. For upgrade information see:
SAP Note 844816
SAP Note 844817
SAP Note 809820
Configure SAP Internet Transaction Server (7.00)
You have to use the internal SAP ITS which is integrated into the
SRM Server (SAP ITS 7.0)
Please note that the external ITS is not supported anymore for SRM
For further details, see the Upgrade Master Guide
For further details, see the Upgrade Master Guide
SAP AG 9
SAP AG 2006
Upgr ade Sequenc e (1)
1. Upgrade PI (former XI)
a) You may upgrade SRM and PI in parallel
b) PI requires a separate WebAS (AS-ABAP and AS-JAVA)
2. Import the XI Content for the following components:
a) XI Content for SRM Server 6.0
b) XI Content for SAP BI Content 7.0.3
c) XI Content for SAP SRM-MDM Catalog 1.0 (optional)
3. Upgrade SAP R/3 Plug-In
a) see SAP Notes 704564 and 708736
4. Upgrade to SAP SRM Server 6.0
5. Uninstall the old version of SAP Internet Pricing and
Configurator
a) see SAP Notes 844816, 844817 and 809820
For further details, see the Upgrade Master Guide
SAP AG 10
SAP AG 2006
Upgr ade Sequenc e (2)
6. Configure SAP Internet Transaction Server (7.00)
7. Install SAP SRM-MDM Catalog 1.0
a. see SAP Note 967088
8. Install SAP NetWeaver 2004s TREX
a. Perform the installation steps to set up an RFC connection
b. Automatic language recognition is not required. You can adopt
the default settings for document languages during the course
of this installation step
c. No Python extensions are required
9. Upgrade SRM Server for SAP SUS
10.Upgrade to SAP Live Auction Cockpit Web Presentation
Server (LACWPS) 6.0
a. The upgrade procedure migrates data and updates the database
For further details, see the Upgrade Master Guide
SAP AG 11
SAP AG 2006
Upgr ade Sequenc e (3)
11.Upgrade to SAP NetWeaver BI 7.0
a. Basis plug-in PI_BASIS 2005_1_700 is included in the upgrade to
SAP BI 7.0.
b. After the BI ABAP upgrade, you should install the Java parts of BI
(BI-Java) to take advantage of all new functionality.
12.Install or Upgrade SAP Enterprise Portal 7.0
13.Import the following Business Packages into Enterprise Portal:
a. Business Package for SRM 6.0
b. Business Package for Category Management (optional)
For further details, see the Upgrade Master Guide
SAP AG 12
SAP AG 2006
Pl ug-I n I nf o
Question: For SRM 6.0 implementation, what backend R/3 releases
will be supported? Is 3.1H still being supported with SRM 5.0
release or is that already at the end of maintenance?
What is the latest R/3 Plug-In required to run SRM 5.0?
Answer: 3.1i to ERP 2.0 is supported, but we recommend a backend
release higher than 46C. The latest R3 PI would be PI 2004.1 and no
further PI's would be delivered separately. It would be integrated
into ECC 60 and higher henceforth.
For further information on PI, pls refer to
https://sapneth6.wdf.sap.corp/r3-plug-in
Additional note: SRM 5.0 Prerequisites 851597
SAP AG 13
SAP AG 2006
Upgr ade and Rest r i c t i ons
One-client architecture will be available only to new
customers.
Existing mySAP SRM customers (< mySAP SRM 5.0) must
upgrade to mySAP SRM Server 6.0 and mySAP SRM Plus 6.0.
Available as standalone server architecture.
SAP tools will not support moving from a standalone mySAP
SRM server to one-client architecture.
One-client architecture for 2006 does not have multiple
backend capabilities.
Customers currently using SRM 3.0/4.0 who wish to keep the
current functionality but focus on an upgrade to SAP ECC can
do so but need some adjustments to mySAP SRM, which will
be provided.
The PDA solution (SAP ECC goods receipt) is available as a
consulting note.
SAP AG 14
SAP AG 2005
SRM Upgrade
LAC WPS Upgrade
Optional installation means, that the installation is only required for certain SRM scenarios. In addition, a
component might also be optional within a certain SRM scenario. See chapter SRM Architecture for
details.
SAP AG 15
SAP AG 2006
Upgr ade Li ve Auc t i on Coc k pi t
Only valid for: SAP SRM SRM Live Auction Cockpit (SRMLAC)
Determining Existing Modifications
If you have customized your existing Live Auction Cockpit
installation, it is recommended that before performing the upgrade,
you determine which modifications you plan to also make in the Live
Auction Cockpit 6.0 system.
Since there is no automatic migration of customized settings, these
will have to be manually redone in the new system. For more
information, refer to the guide
Migrating Resource Customizations from Live Auction Cockpit 5.0
SAP AG 16
SAP AG 2006
LAC - Chec k i ng J CO Set t i ngs
Important: Perform these steps before you upgrade LAC WPS
Logon as J2EE Administrator to your Live Auction Cockpit 5.0
system
If the property jco.client.user is set to SRMLA_RFCUSER, then
change the user name
If you do not make this change, the upgrade tool overwrites the
property setting with a different default value, preventing
successful data migration post-upgrade
If you used the default value SRMLA_RFCUSER for the jco.client.user property when defining JCo client
settings in your Live Auction Cockpit 5.0 system, you must change the user name via the J2EE visual
administrator, or J2EE engine Configuration Adapter Tool, prior to upgrading your system.
For information on how to modify JCo property values, see the Post-Installation Steps for Live Auction
Cockpit 6.0 section of the Installation Guide SAP SRM 6.0 available on the SAP Service Marketplace
at service.sap.com/instguides mySAP Business Suite Solutions mySAP SRM Using SRM Server 6.0
Please note:
It is essential that you change the user name so that the upgrade tool recognizes this property value as
being customized, and, thus, will copy the setting. If you do not make this change, the upgrade tool
overwrites the property setting with a different default value, preventing successful data migration post-
upgrade.
SAP AG 17
SAP AG 2006
LAC Mi gr at i ng Resour c e Cust omi zat i ons
The Live Auction Cockpit 6.0 system includes application properties
They are preserved during the upgrade process
But it does not reflect any resource setting customizations in your LAC 5.0
installation
Determine if copying customizations from LAC 5.0 to LAC 6.0 is required
If yes, identify the changes and the corresponding resource files in LAC 5.0
Image Files
Resource Bundles
Adjust the values of the following properties to either 1 or 2 so that your
customized files will be used by LAC 6.0:
applet.initiator.archive
applet.respondent.archive
applet.archive.selection
For more information, go to SAP Solution Manager and navigate to the scenario Strategic Sourcing with
Live Auction, business process Conducting Live Auctions, configuration references Configuring the Live
Auction Cockpit User Interface and Managing Live Auction Cockpit Properties.
The Live Auction Cockpit 6.0 system includes application properties preserved during the upgrade
process; however, it does not reflect any resource setting customizations you may have performed in your
LAC 5.0 installation.
Before copying any customizations from your LAC 5.0 system to your LAC 6.0 system, we recommend
that you first launch the Live Auction Cockpit 6.0 to evaluate and determine if those changes are still
required.
Please Note:
Due to the unknown number and types of customizations you may have in your existing system, the
following is intended as a reference guide rather than an exact procedure for migrating those
customizations.
We recommend that you always create your own resource files rather than replacing or modifying those
shipped with LAC to avoid overwriting your modifications whenever a patch is deployed.
Once you have determined that copying customizations from LAC 5.0 to LAC 6.0 is required, identify
what changes were made in LAC 5.0 and where in the resource files they were made. For more
information, see Determining Existing Customizations.
Image Files
A number of image files that were used in LAC 5.0 have been renamed or removed in LAC 6.0. Review
your customized images and see if they are affected.
There are also several new image files that are introduced in LAC 6.0; you may wish to review those as
well.
SAP AG 18
Resource Bundles
A number of resource bundles that were used in LAC 5.0 have been renamed or
removed in LAC 6.0. Please review your customized resource bundles and if they are
affected.
If you plan to carry over customized resource texts, make sure the file names and the
resource keys of the original resource bundle files are unchanged.
Store all your customized resource files under:
<INSTDIR>:/usr/sap/<sapsid>/SYS/global/srmla/resources
Adjust the values of the following properties to either 1 or 2 so that your customized files
will be used by LAC 6.0:
applet.initiator.archive
applet.respondent.archive
applet.archive.selection
SAP AG 19
SAP AG 2006
LAC Mi gr at i ng Dat a f r om LAC 5.0
After the upgrade, you need to migrate auction data and update the
database to initialize new database fields that have been added as a result
of new functionality in Live Auction Cockpit 6.0. To do so, you must
manually execute two post-upgrade reports.
Please Note
If you have a great amount of existing auction data in your system, it may
take a long time to execute each report. In this case, we recommend
scheduling a background job to run these reports to avoid time-outs.
In the EBP system, go to transaction SE38.
1) Execute report BBP_LA_DATA_MIGRATION.
2) Execute report BBP_Z090_XPRA_AUCTIONS_XPRA550.
Please Note:
You can only run this report after the successful execution of report
BBP_LA_DATA_MIGRATION
SAP AG 20
SAP AG 2006
Summar y
Contents
mySAP SRM Upgrade
Now you are able to:
Plan your upgrade from the information you obtain from the
Master Guide
Describe the SRM specific upgrade sequence
Describe the SRM specific upgrade tasks
SAP AG 21
SAP AG 2006
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.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C

, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are
the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without
the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP

product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links,
or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the
implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of
these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot
links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
Copyr i ght 2006 SAP AG. Al l Ri ght s Reser ved