SRM30_SUG_26

Solution Upgrade Guide

mySAPTM

Supplier Relationship Management powered by SAP NetWeaverTM

Using SAP® Enterprise Buyer 4.0

Document Version 1.15 - November 11, 2003

Material Number 50064008

SAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

JAVA® is a registered trademark of Sun Microsystems, Inc. © Copyright 2003 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.

J2EE™ 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.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, mySAP Business Suite, 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.

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®, Informix and Informix® Dynamic Server

TM are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation. 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 expressively prohibited, as is any decompilation of these components.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of the Open Group.

LINUX is a registered trademark of Linus Torvalds and others. 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.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/instguides

Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply.

For the HTTPClientStack library, the following conditions apply:

HTTPClientStack - a library to enable an easy programmatic access to the

HTTP protocol stack

Copyright © 2001 Ronald Tschalär

This library is free software; you can redistribute it and/or modify it under the

terms of the GNU Lesser General Public License as published by the Free

Software Foundation; either version 2 of the License, or (at your option) any

later version.

This library is distributed by in the hope that it will be useful, but WITHOUT

ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See

the GNU Lesser General Public License for more details.

SAP’s warranty and liability is subject to your end user license with SAP.

These warranties and liabilities are only on SAP’s behalf and not on behalf of

any other contributors. On behalf of all Contributors all liability for damages,

including direct, indirect, special, incidental and consequential damages, such

as lost profits is expressly excluded.

You should have received a copy of the GNU Lesser General Public License

along with this library; if not, write to the Free Software Foundation, Inc., 59

Temple Place, Suite 330, Boston, MA 02111-1307 USA

Ronald Tschalär

[email protected]

You should also get your employer (if you work as a programmer) or your

school, if any, to sign a "copyright disclaimer" for the library, if necessary.

Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a

library for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990

Ty Coon, President of Vice

For the Jakarta Apache tool, the following conditions apply:

This product includes software developed by the Apache Software Foundation

(http://www.apache.org/).

The Apache Software License, Version 1.1

Copyright © 2000 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this

list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,

this list of conditions and the following disclaimer in the documentation

and/or other materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must

include the following acknowledgment:

"This product includes software developed by the Apache Software

Foundation (http://www.apache.org/)."

Alternately, this acknowledgment may appear in the software itself, if and

wherever such third-party acknowledgments normally appear.

4. The names "Apache" and "Apache Software Foundation", "Jakarta-Oro"

must not be used to endorse or promote products derived from this

software without prior written permission. For written permission, please

contact [email protected].

5. Products derived from this software may not be called "Apache" or

"Jakarta-Oro", nor may "Apache" or "Jakarta-Oro" appear in their name,

without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on

behalf of the Apache Software Foundation. For more information on the

Apache Software Foundation, please see http://www.apache.org/.

Portions of this software are based upon software originally written by Daniel

F. Savarese. We appreciate his contributions.

SAP and/or its distributors may offer, and charge a fee for, warranty, support,

indemnity or liability obligations to one or more recipients of the software.

However, SAP and/or its distributors may do so only on its/their own behalf,

and not on behalf of the Apache Software Foundation or its contributors.

For the JDom tool, the following conditions apply:

This product includes software developed by the JDOM Project

(http://www.jdom.org/)."

Copyright © 2000 Brett McLaughlin & Jason Hunter.

All rights reserved.




list of conditions, and the following disclaimer.


this list of conditions, and the disclaimer that follows these conditions in

the documentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products

derived from this software without prior written permission. For written

permission, please contact [email protected].

4. Products derived from this software may not be called "JDOM", nor may

"JDOM" appear in their name, without prior written permission from the

JDOM Project Management ([email protected]).

In addition, we request (but do not require) that you include in the end-user

documentation provided with the redistribution and/or in the software itself an

acknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project

(http://www.jdom.org/)."

Alternatively, the acknowledgement may be graphical using the logos available

at http://www.jdom.org/images/logos.
















behalf of the JDOM Project and was originally created by Brett McLaughlin

([email protected]) and Jason Hunter ([email protected]). For more information

on the JDOM Project, please see http://www.jdom.org/.

For the Jython tool, the following conditions apply:

HISTORY OF THE SOFTWARE

JPython was created in late 1997 by Jim Hugunin. Jim was also the primary

developer while he was at CNRI. In February 1999 Barry Warsaw took over as

primary developer and released JPython version 1.1.

In October 2000 Barry helped move the software to SourceForge where it was

renamed to Jython. Jython 2.0 is developed by a group of volunteers.

The standard library is covered by the BeOpen / CNRI license. See the

Lib/LICENSE file for details.

The oro regular expresion matcher is covered by the apache license. See the

org/apache/LICENSE file for details.

JYTHON CHANGES SOFTWARE LICENSE

Copyright © 2000, Jython Developers

All rights reserved.



- Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

- Neither the name of the Jython Developers nor the names of its

contributors may be used to endorse or promote products derived from

this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

JPYTHON SOFTWARE LICENSE.

IMPORTANT: PLEASE READ THE FOLLOWING AGREEMENT

CAREFULLY.

BY CLICKING ON THE "ACCEPT" BUTTON WHERE INDICATED, OR

BY INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE,

YOU ARE DEEMED TO HAVE AGREED TO THE TERMS AND

CONDITIONS OF THIS AGREEMENT.

JPython version 1.1.x

1. This LICENSE AGREEMENT is between the Corporation for National

Research Initiatives, having an office at 1895 Preston White Drive,

Reston, VA 20191 ("CNRI"), and the Individual or Organization

("Licensee") accessing and using JPython version 1.1.x in source or

binary form and its associated documentation as provided herein

("Software").

2. Subject to the terms and conditions of this License Agreement, CNRI

hereby grants Licensee a non-exclusive, non-transferable, royalty-free,

world-wide license to reproduce, analyze, test, perform and/or display

publicly, prepare derivative works, distribute, and otherwise use the

Software alone or in any derivative version, provided, however, that

CNRI's License Agreement and CNRI's notice of copyright, i.e.,

"Copyright ©1996-1999 Corporation for National Research Initiatives;

All Rights Reserved" are both retained in the Software, alone or in any

derivative version prepared by Licensee.

3. Alternatively, in lieu of CNRI's License Agreement, Licensee may

substitute the following text (omitting the quotes), provided, however,

that such text is displayed prominently in the Software alone or in any

derivative version prepared by Licensee: "JPython (Version 1.1.x) is

made available subject to the terms and conditions in CNRI's License

Agreement. This Agreement may be located on the Internet using the

following unique, persistent identifier (known as a handle): 1895.22/1006.

The License may also be obtained from a proxy server on the Web using

the following URL: http://hdl.handle.net/1895.22/1006."

In the event Licensee prepares a derivative work that is based on or

incorporates the Software or any part thereof, and wants to make the

derivative work available to the public as provided herein, then Licensee

hereby agrees to indicate in any such work, in a prominently visible way,

the nature of the modifications made to CNRI's Software.

4. Licensee may not use CNRI trademarks or trade name, including JPython

or CNRI, in a trademark sense to endorse or promote products or services

of Licensee, or any third party. Licensee may use the mark JPython in

connection with Licensee's derivative versions that are based on or

incorporate the Software, but only in the form "JPython-based

___________________," or equivalent.

5. CNRI is making the Software available to Licensee on an "AS IS" basis.

CNRI MAKES NO REPRESENTATIONS OR WARRANTIES,

EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT

LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY

REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR

FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE

OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY

RIGHTS.

6. CNRI SHALL NOT BE LIABLE TO LICENSEE OR OTHER USERS

OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL OR

CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING,

MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY

DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY

THEREOF. SOME STATES DO NOT ALLOW THE LIMITATION OR

EXCLUSION OF LIABILITY SO THE ABOVE DISCLAIMER MAY

NOT APPLY TO LICENSEE.

7. This License Agreement may be terminated by CNRI (i) immediately

upon written notice from CNRI of any material breach by the Licensee, if

the nature of the breach is such that it cannot be promptly remedied; or

(ii) sixty (60) days following notice from CNRI to Licensee of a material

remediable breach, if Licensee has not remedied such breach within that

sixty-day period.

8. This License Agreement shall be governed by and interpreted in all

respects by the law of the State of Virginia, excluding conflict of law

provisions. Nothing in this Agreement shall be deemed to create any

relationship of agency, partnership, or joint venture between CNRI and

Licensee.

9. By clicking on the "ACCEPT" button where indicated, or by installing,

copying or otherwise using the Software, Licensee agrees to be bound by

the terms and conditions of this License Agreement.

For the RegEX Apache tool, the following conditions apply:


(http://www.apache.org/)."


Copyright © 1999 The Apache Software Foundation. All rights

reserved.









include the following acknowlegement:



Alternately, this acknowlegement may appear in the software itself, if and

wherever such third-party acknowlegements normally appear.

4. The names "The Jakarta Project", "Jakarta-Regexp", and "Apache

Software Foundation" must not be used to endorse or promote products

derived from this software without prior written permission. For written


5. Products derived from this software may not be called "Apache" nor may

"Apache" appear in their names without prior written permission of the

Apache Group.













OUT

OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE









For SAX, the following conditions apply:

SAX 2.0

I hereby abandon any property rights to SAX 2.0 (the Simple API for XML),

and release all of the SAX 2.0 source code, compiled code, and documentation

contained in this distribution into the Public Domain. SAX comes with NO

WARRANTY or guarantee of fitness for any purpose.

David Megginson, [email protected]

2000-05-05

For the Struts Apache tool, the following conditions apply:


(http://www.apache.org/).


Copyright © 1999-2001 The Apache Software Foundation. All rights reserved.









include the following acknowlegement:



Alternately, this acknowlegement may appear in the software itself, if and

wherever such third-party acknowlegements normally appear.

4. The names "The Jakarta Project", "Struts", and "Apache Software

Foundation" must not be used to endorse or promote products derived

from this software without prior written permission. For written


5. Products derived from this software may not be called "Apache" nor may

"Apache" appear in their names without prior written permission of the

Apache Group.






















Typographic Conventions Icons Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text>

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the Enter key.

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Solution Upgrade Guide mySAP SRM using SAP EBP 4.0

10 November 2003

Contents Solution Upgrade Guide mySAP SRM using SAP Enterprise Buyer 4.0 ..........................................................................................11

1 Before You Start................................................................................12 1.1 SAP Notes............................................................................................. 12 1.2 Further Information .............................................................................. 13

2 History of Changes ...........................................................................14 3 Solution Overview.............................................................................15

3.1 Software Component Matrix................................................................ 15 4 The Upgrade ......................................................................................17

4.1 Self-Service Procurement.................................................................... 17 4.1.1 Technical System Landscape.....................................................................................17 4.1.2 Upgrade Sequence.....................................................................................................19

4.2 Plan-Driven Procurement .................................................................... 22 4.2.1 Technical System Landscape.....................................................................................22 4.2.2 Upgrade Sequence.....................................................................................................23

4.3 Strategic Sourcing ............................................................................... 26 4.3.1 Technical System Landscape.....................................................................................26 4.3.2 Upgrade Sequence.....................................................................................................27

4.4 Supplier Enablement............................................................................ 30 4.4.1 Technical System Landscape.....................................................................................30 4.4.2 Upgrade Sequence.....................................................................................................31

3.4 Catalog Content Management............................................................. 35 4.5.1 Technical System Landscape.....................................................................................35 4.5.2 Upgrade Sequence.....................................................................................................35

4 Appendix............................................................................................39 4.1 Migrating Requisite BugsEye and eMerge from JRun to SAP J2EE Engine ............................................................................................... 39 4.2 Troubleshooting................................................................................... 42

4.2.1 Problems With Sending Internet Mails........................................................................42 5 References.........................................................................................43

5.1 SAP Notes............................................................................................. 43 5.2 Documentation ..................................................................................... 44

Solution Upgrade Guide mySAP SRM using SAP EBP 4.0

Solution Upgrade Guide mySAP SRM using SAP Enterprise Buyer 4.0 This documentation gives you an overview of the upgrade of mySAP SRM. The information herein is ordered under business sceanario aspects. The documentation deals with the following aspects:

• Which prerequisites have to be met, and which preparations have to be made before the upgrade?

• Which components have to be upgraded, to which release, and in which sequence?

• Are there important dependencies between the components that have to be taken into consideration?

• Which documentation and SAP Notes are required?

Structure of the Solution Upgrade Guide • Before You Start [on page 12]contains important SAP Notes and references to related

information crucial to the upgrade.

• In Solution Overview [on page 15]a short introduction is given to mySAP SRM. The Software Component Matrix [on page 15] shows you in a condensed form what components are required for what scenario and what are the required minimum releases of these components.

• The Upgrade [on page 17] section contains a subsection for each business scenario. For each business scenario, you will find information about the overall upgrade sequence and additional information on planning, preparations and post-upgrade steps, if necessary.

• In the References [on page 43] section, you can find an overview of all SAP Notes and Documentation referenced in this Solution Upgrade Guide.

You can find the most current information about the technical upgrade of this mySAP Business Suite solution and the latest upgrade, installation and configuration guides in SAP Service Marketplace at the Internet address: service.sap.com/instguides

We strongly recommend that you use the documents available there. The guides are regularly updated.

The technical implementation of mySAP SRM is described in the documentation Master Guide – mySAP SRM – Using SAP EBP 4.0. Refer to this documentation for information on new business scenarios and implementation options. You can find it on SAP Service Marketplace at the Internet address: service.sap.com/instguides.

November 2003 11

1 Before You Start

1.1 SAP Notes

1 Before You Start 1.1 SAP Notes You must read the following SAP Notes before you start the upgrade. These SAP notes contain the most recent information on the upgrade / installation, as well as corrections to the documentation.

SAP Notes, especially upgrade Notes, are subject to change. They contain the most recent information regarding the upgrade procedure, as well as corrections to the upgrade documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service Marketplace at the Internet address service.sap.com/notes

SAP Note No.

Title Description

608082 Solution Upgrade Guide mySAP SRM using SAP EBP 4.0

Remarks, annotations and corrections discovered after publication of the Solution Upgrade Guide are subject of this note.

596514 Additions Upgrade to SAP CRM 4.0 / SRM Server 4.0

Information on problems, fixes, and changes to the upgrade procedure and documentation.

590953 Master Guide my SAP SRM using SAP EBP 4.0

Remarks, annotations and corrections discovered after publication of the Master Guide are subject of this note.

12 November 2003

1 Before You Start

1.2 Further Information

1.2 Further Information The following list contains links to crucial information for upgrading this mySAP Business Suite solution.

Content Location in SAP Service Marketplace

Released platforms service.sap.com/platforms Availability of SAP components in Detail mySAP SRM

Hardware sizing service.sap.com/sizing

Network security SAP Security Guide

service.sap.com/securityguide

Network Integration Guides

service.sap.com/network

Technical infrastructure service.sap.com/ti

SAP Solution Manager service.sap.com/solutionmanager

Information about releases, availability, upgrading the R/3 plug-in, and integrating the mySAP.com components

service.sap.com/R3-plug-in

November 2003 13

2 History of Changes

2 History of Changes The Solution Upgrade Guide is regularly updated in SAP Service Marketplace at the Internet address service.sap.com/instguides.

Make sure you have the latest version of the Solution Upgrade Guide by checking SAP Service Marketplace immediately before starting the upgrade.

The following table provides an overview on the most important changes that were made in the latest versions.

Solution Upgrade Guide Version Important Changes

1.00 – June 18, 2003 --- first version ---

1.05 – August 05, 2003 Supplier Enablement: Information on adjustment of customizing settings added

1.10 – September 04, 2003 Live Auction Web Presentation Layer (LACWPS) added to the Strategic Sourcing business scenario.

1.15 – November 10, 2003 Note number deleted.

14 November 2003

3 Solution Overview

3.1 Software Component Matrix

3 Solution Overview

3.1 Software Component Matrix This section provides an overview of which business scenario of this mySAP Business Suite solution uses which component.

Note that there are software requirements for each component below which are not explicitly mentioned in this documentation. They are documented in the relevant installation guides. You can find all related implementation guides listed in the section Documentation [on page 44].

For latest component version and patch level requirements, see the corresponding SAP Note that is available for each SAP SRM Server Support Package. You can find the number of the latest released Support Package and the corresponding SAP Note in SAP Note 608082.

For information on the Support Package schedule, see on the SAP Service Marketplace under the Internet address service.sap.com/patches SAP Support Packages in Detail Schedules for Support Packages BBP/EBP and CRM Support Package Schedule EBP 4.0 (SRM 3.0) Support Package Schedule.

Business Scenario / Software Component Matrix (M = mandatory / O = optional)

Business Scenario Software Component

Self-

Serv

ice

Proc

urem

ent

Plan

-Driv

en

Proc

urem

ent

Stra

tegi

c So

urci

ng

Supp

lier

Enab

lem

ent

Cat

alog

& C

onte

nt-

Man

agem

ent

SAP SRM Server 4.0

(based on SAP Web Application Server 6.20, comprises SAP Enterprise Buyer and SAP Bidding Engine)

M M M M

M

SAP IPC 4.0 M M M M --

SAP BW 3.1C O O O O --

Requisite BugsEye® Catalog 3.5 O O O O O

Requisite eMerge™ 3.5 -- -- -- -- O

SAP Integrated Catalog 3.0 O O O O O

SAP User Management Engine 3.0 O O O O O

SAP Enterprise Portal 5.0

(planned to be available with Support

O O O O O

November 2003 15

3 Solution Overview

3.1 Software Component Matrix

Package 02 of mySAP SRM)

SAP Internet Transaction Server (as of 6.10 C1)

M M M M M

SAP Supplier Self-Services 2.0 (SAP SUS) consisting of:

• BBPCRM 4.0

• SAP SUS Web Presentation Server (SAP SUS WPS)

-- -- -- M --

Live Auction Web Presentation Layer 1.0 (LACWPS)

-- -- O -- --

SAP Exchange Infrastructure 2.0 (SAP XI)

O O O M M

Integration of SAP Systems (M = mandatory / O = optional)

Business Scenario SAP System

Self-

Serv

ice

Proc

urem

ent

Plan

-Driv

en

Proc

urem

ent

Stra

tegi

c So

urci

ng

Supp

lier

Enab

lem

ent

Cat

alog

& C

onte

nt-

Man

agem

ent

SAP R/3 OLTP as of 3.1I or SAP R/3 Enterprise 4.70

(SAP R/3 4.6C recommended)

M M O O --

SAP R/3 Plug-In 2003.1 or higher version if one is available

M M O O --

16 November 2003

4 The Upgrade

4.1 Self-Service Procurement (Indirect Procurement)

4 The Upgrade

4.1 Self-Service Procurement (Indirect Procurement) 4.1.1 Technical System Landscape The following graphics show the underlying architecture of Self-Service Procurement including existing connections.

Architecture of Self-Service Procurement / Classic & Extended Classic Deployment

Firewall

Requisite BugsEye R/3 (MM & FI/CO)

SAP GUI / RFCHTTPS / OCI

TCP / IP

ISAP / NSAPI / CGI

BW

Integrated Catalog

RFC

IPC

ITS AGate

BBPCRM(EBP)

http Web Server

RFC

ITS WGate

BBPCRM

EBP

November 2003 17

4 The Upgrade


Architecture of Self-Service-Procurement / Standalone Deployment

Firewall

Requisite BugsEye

SAP GUI / RFCHTTPS / OCI

TCP / IP

ISAP / NSAPI / CGI

IPCBBPCRM(EBP)

RFC

BW

http Web Server

ITS WGate

RFC

ITS AGate

Integrated Catalog

BBPCRM

EBP

For both graphics, see the following legend:

Integrated Catalog

IPC

BBPCRM(EBP)

<Protocol> Transfer protocol type

ABAP based software component

JAVA based software component

Optional software component

Document format type

Legend

JCo Java Connector

TCP / IP Transmission Control Protocol overInternet Protocol

CGI Common Gateway Interface

HTTPS HyperText Transmission Protocol, Secure

OCI Open Catalog Interface

RFC Remote Fucntion Call

IDOC Intermediate Document

XML Extensible Markup Language

Exchange Infrastructure layer

Application layer

XML

18 November 2003

4 The Upgrade


4.1.2 Upgrade Sequence Perform the upgrade/installation steps in the specified order. Rows containing optional components are highlighted in grey. The scenario can function without this optional components; but they provide additional functions.



For information on where to find the corresponding documentation, see section Documentation [page 44]

Upgrade Sequence

Step Action

[Corresponding Documentation]

Remarks / Subsequent steps

1 Upgrade of the SAP Exchange Infrastructure

Guides:

Upgrade Overview – SAP Exchange Infrastructure 2.0 within mySAP SRM 3.0

For orders sent directly from the EBP system with XML, you require an SAP Business Connector (SAP BC) or the SAP Exchange Infrastructure. As of mySAP SRM 2.0 the SAP Exchange Infrastructure is used as central messaging platform. In the course of this the SAP Exchange Infrastructure replaces the communication platform SAP Business Connector. New mySAP SRM Business Scenarios as well as enhancements of existing scenarios are developed exclusively using the SAP Exchange Infrastructure. However, for mySAP SRM 2.0 and 3.0, the existing SAP BC-based integration scenarios that you did implement with SAP EBP 3.0 are still supported. You can continue to use all functions of your existing SAP BC-based scenarios that were available with SAP EBP 3.0. You can use existing scenarios based on SAP BC in parallel to SAP Exchange Infrastructure based scenarios. If you want to continue using SAP Business Connector, see SAP Service Market Place under the Internet address service.sap.com/connectors SAP Business Connector if you need to upgrade SAP BC. You can find the required upgrade guide at the same address under SAP Business Connector in Detail →

November 2003 19

4 The Upgrade


Documentation. Take notice also of the information about mySAP SRM Business Packages that is provided there under Tools & Services → Adapters and Add-ons.

2 Upgrade of SAP R/3 Plug-In

For more information, see SAP Note 181255: Overview: SAP Notes on the R/3 Add-Ons PI and PI-A and SAP Note 601105 Release Restrictions R/3 Plug-in 2003.1.

See also the information on SAP Service Marketplace under the Internet address service.sap.com/r3-plug-in.

3 Upgrade of the SRM Server

Guide:

Component Upgrade Guide – SAP CRM 4.0/SRM Server 4.0: <Operating System>

4 Deinstallation of the old release of the SAP Internet Pricing and Configurator and Installation of the required version.

Guides:

Upgrade Guide SAP Internet Pricing and Configurator 4.0 and additional guides referenced within the upgrade guide.

SAP IPC is

• optional for Self-Service Classic Procurement (*see below for restrictions)

• mandatory for Self-Service Classic Extended and Self-Service Lean Procurement

5 Installation of SAP Internet Transaction Server

Guide:

SAP@Web Installation Guide

6 Upgrade of Requisite BugsEye

Guide:

BugsEye and eMerge 3.5 Installation and Upgrade Guide

For detailed information about the availability and the release strategy of Requisite BugsEye®, see SAP Note 485884.

The following upgrade path exists:

3.5.3.29 → 3.5.3.29a → 3.5.6.8 → 3.5.7.4.

If you want to migrate from JRun to SAP J2EE Engine, see the procedure Migrating Requisite BugsEye and eMerge from JRun to SAP J2EE Engine [on page 39].

7 Upgrade of SAP Integrated Catalog

Guide:

SAP Note 620461

8 Installation/deployment of SAP User Management Engine

Only required if you use SAP Enterprise Portal.

20 November 2003

4 The Upgrade


Guide:

Component Installation Guide SAP User Management Engine 3.0

After you have installed SAP User Management 3.0, you can migrate the users from your previous EBP user management into the new component. You can migrate the users by using mass notification, or by downloading them from the EBP system and importing them into the SAP User Management Engine. For more information about this procedure, see the documentation Administrator's Guide SAP User Management Engine 3.0.

9 Upgrade of SAP Business Information Warehouse, if necessary

Guide:

Component Upgrade Guide SAP BW: <Operating System>

Basis plug-in PI_BASIS 2002.2_620 is included in the upgrade to SAP BW 3.1C.

10 Installation of SAP Enterprise Portal

Guide:

Installation Guide Enterprise Portal 5.0

For information about availability, see the Platform Availability Matrix in the SAP Service Marketplace: service.sap.com/sapportals → Products → Enterprise Portal → Enterprise Portal 5.0 → Platform Availability Matrix.

SAP MarketSet Adapter is now part of the SAP Exchange Infrastructure installation. You do not need to install it separately.

* If you operate Self-Service Classic Procurement without SAP IPC, the following restrictions apply:

• You can select the products are normally from a catalog. In addition, you are still able to choose products from the product master or user-defined text items.

• The product price must remain in the /1CN/CBPSAP118 master record table.

• Contracts and in particular discounts are not taken into account.

• You cannot use interlinkages and scales.

• Currency changes can only happen on the item level, and not on the document level.

November 2003 21

4 The Upgrade

4.2 Plan-Driven Procurement (Direct Procurement)

4.2 Plan-Driven Procurement (Direct Procurement) 4.2.1 Technical System Landscape The following graphic shows the underlying architecture of Plan-Driven Procurement including existing connections.

Architecture of Plan-Driven Procurement

Firewall

R/3 (MM & FI/CO)

SAP GUI / RFC

TCP / IP

BW

RFC

IPC

ITS AGate

BBPCRM

RFC

ITS WGate

http Web Server

ISAP / NSAPI / CGI

EBP

IDOC

For this graphic, use the same legend as in section 4.1 Self-Service Procurement [on page 17].

22 November 2003

4 The Upgrade


4.2.2 Upgrade Sequence Perform the upgrade/installation steps in the specified order. Rows containing optional components are shaded in grey. The scenario can function without this optional components; but they provide additional functions.



For information on where to find the corresponding documentation, see section Documentation [page 44].

Upgrade Sequence

Step Action Remarks

1 Upgrade of SAP Exchange Infrastructure up to the point when you have to start the upgrades of the application systems.

Guides:


As of mySAP SRM 2.0 the SAP Exchange Infrastructure is used as central messaging platform. In the course of this the SAP Exchange Infrastructure replaces the communication platform SAP Business Connector. New mySAP SRM Business Scenarios as well as enhancements of existing scenarios are developed exclusively using the SAP Exchange Infrastructure. However, for mySAP SRM 2.0 and 3.0, the existing SAP BC-based integration scenarios that you did implement with SAP EBP 3.0 are still supported. You can continue to use all functions of your existing SAP BC-based scenarios that were available with SAP EBP 3.0. You can use existing scenarios based on SAP BC in parallel to SAP Exchange Infrastructure based scenarios.

If you want to continue using SAP Business Connector, see SAP Service Market Place under the Internet address service.sap.com/connectors

SAP Business Connector if you need to upgrade SAP BC. You can find the required upgrade guide at the same address under SAP Business Connector in Detail → Documentation. Take notice also of the information about mySAP SRM Business Packages that is provided there under Tools & Services → Adapters and Add-ons.

November 2003 23

4 The Upgrade


2 Upgrade SAP R/3, if necessary

(SAP R/3 4.6C recommended)

Upgrade SAP R/3 Plug-In

For more information, see SAP Note 181255 and SAP Note 601105 Release Restrictions R/3 Plug-in 2003.1.

See also the information in SAP Service Marketplace under the Internet address service.sap.com/r3-plug-in.

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.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.

3 Upgrade SRM Server

Guide:

Component Upgrade Guide – SAP CRM / SRM Server 4.0: <Operating System>

If you use the extended classic scenario and the SAP SRM Server 4.0 in combination with a backend system from SAP R/3 Release 4.6B onwards, you must also transfer a purchasing group when your create a backend purchase order. For details about the required configuration activities, see the documentation Business Scenario Configuration Guide – SRM Plan Driven Procurement with Plant Maintenance 3.0, section Defining Backend Systems and the Extended Classic Scenario.

4 Deinstallation of the old release of SAP Internet Pricing Configurator and installation of the required release.

Guides:


5 Installation of SAP Internet Transaction Server

Guide: SAP@Web Installation Guide

6 Installation of Requisite BugsEye.

Guide: BugsEye® and eMerge™ Installation and Upgrade Guide


7 Installation of SAP Integrated Catalog

Guide:

Installation Guide – SAP Integrated Catalog

The SAP Integrated Catalog is an alternative user interface for Requisite BugsEye that is integrated into SAP EBP.

24 November 2003

4 The Upgrade


8 Installation of SAP User Management Engine

Guide:


If you use SAP Enterprise Portal, you require SAP User Management Engine 3.0.


9 Upgrade of SAP BW

Guide:

Component Upgrade Guide - SAP BW <Release>: <Operating System>]



Guide:

Installation Guide SAP Enterprise Portal 5.0


11 Complete the SAP Exchange Infrastructure upgrade.

Guide: Upgrade Overview – SAP Exchange Infrastructure 2.0 within mySAP SRM 3.0

To enable the user to read and create business documents in Enterprise Buyer, make sure that the role SAP_BBP_STAL_PURCHASER is assigned to XIAPPLUSER.

SAP MarketSet Adapter is now part of the SAP Exchange Infrastructure installation. You do not need to install it separately.

As well as in mySAP SRM 2.0, you can optionally integrate SAP APO 3.1 in the Plan-Driven Procurement business scenario.

November 2003 25

4 The Upgrade

4.3 Strategic Sourcing

4.3 Strategic Sourcing 4.3.1 Technical System Landscape The following graphic shows the underlying architecture of Strategic Sourcing including existing connections.

Architecture of Strategic Sourcing

Firewall

SAP GUI / RFC

TCP / IP

BW

http Web Server

ITS AGate

IPC

RFC

ITS WGate

BBPCRM

RFC

HTTPS

EBP

Sourcing Cockpit

Bidding Engine

Firewall

SAP GUI / RFC

TCP / IP

BW

http Web Server

ITS AGate

IPC

RFC

ITS WGateITS WGate

BBPCRM

RFC

HTTPS

EBP

Sourcing Cockpit

Bidding Engine

IDOCIDOC

Architecture of Strategic Sourcing (with Live Auction)

26 November 2003

4 The Upgrade


SAP GUI / RFC

TCP / IP

BW

http Web Server

ITS AGate

IPC

RFC

ITS WGate

ISAP / NSAPI / CGI

BBPCRM

RFC

HTTPS

EBP

Bidding Engine

JCo

UME LACWPS

Firewall

HTTPS

IDOC

For these graphics, use the same legend as in section 4.1 Self-Service Procurement [on page 17].




For information on where to find the corresponding documentation, see section Documentation [page 44]

November 2003 27

4 The Upgrade


Step Action Remarks

1 Upgrade of SAP Exchange Infrastructure

Guide:


2 Upgrade SAP R/3 Plug-In



3 Upgrade of SRM Server

Guide:

Component Upgrade Guide – SAP CRM / SRM Server 4.0: <operating system>

4 Deinstallation of the old version of SAP Internet Pricing and Configurator and installation of the required version.

Guides:


5 SAP Internet Transaction Server

Guide:

SAP@Web Installation Guide

6 Installation or Upgrade of Requisite BugsEye.

Guide:

BugsEye® and eMerge™ Installation and Upgrade Guide



3.5.3.29 → 3.5.3.29a → 3.5.6.8 → 3.5.7.4.


7 Installation of SAP Integrated Catalog

Guide:


The SAP Integrated Catalog is an alternative user interface for Requisite BugsEye that is integrated into SAP EBP.

8 Installation of Live Auction Web Presentation Server (LACWPS).

28 November 2003

4 The Upgrade


Guide:

Installation Guide - Live Auction


Guide:


SAP User Management Engine is mandatory, if you want to use SAP Enterprise Portal.

8 Upgrade of SAP Business Information Warehouse

Guide:

Component Upgrade Guide – SAP Business Information Warehouse <Release>: <Operating System>



Guide: Installation Guide – SAP Enterprise Portal

November 2003 29

4 The Upgrade

4.4 Supplier Enablement

4.4 Supplier Enablement 4.4.1 Technical System Landscape The following graphics show the underlying architecture of Supplier Enablement including existing connections.

Architecture of Supplier Enablement SUS-MM

XI

JCo

Integration Engine

IDoc Adapter

R/3 (MM)

ITS AGate

IPC

SUS WPS

Firewall

XI Integration Engine

XI Proxy Framework

UME

BBPCRM

SUS

IDoc XML

30 November 2003

4 The Upgrade


Architecture of Supplier Enablement SUS-EBP

JCo

Firewall

Requisite BugsEye

XI Proxy Framework


Integrated Catalog

ITS AGate


XI Proxy Framework

XI

BBPCRM (SUS)

SUS WPS

Plain HTTP/S


IPC

UME

IPC

BBPCRM

SUS

BBPCRM (EBP)

BBPCRM (SUS)BBPCRM

EBP

httpAdapter

XML XML


4.4.2 Upgrade Sequence Perform the upgrade / installation steps in the specified order. Rows containing optional components are shaded in grey. The scenario can function without this optional components; but they provide additional functions.




November 2003 31

4 The Upgrade


Upgrade Sequence

Step Action

[Corresponding Documentation]

Subsequent Steps / Remarks

1 Upgrade the SAP Exchange Infrastructure up to the point when you have to start the upgrades of the application systems.

Guides:


Upgrade of SAP SRM Server

Guide:

Component Upgrade Guide – SAP CRM 4.0 / SRM Server 4.0: <Operating System>

Required for SUS-EBP.

Deinstallation of the old release of SAP Internet Pricing Configurator and installation of the required release.

Guide:

Upgrade Guide SAP Internet Pricing & Configurator 4.0 and additional guides referenced within the upgrade guide.


2a

Installation of SAP Internet Transaction Server for EBP.

Guide: SAP@Web Installation Guide.


2b Upgrade of SAP R/3 Back End Plug-In



Required for SUS-MM.

3 Upgrade of BBPCRM for SAP SUS.

Guide:

Component Upgrade Guide SAP CRM 4.0/SRM Server 4.0: <Operating System>

32 November 2003

4 The Upgrade


Deinstallation of the old release of SAP Internet Pricing Configurator and installation of the required release.

Guide:


4 Upgrade of Requisite Bugs Eye to the recommended patch level.

Guide:




3.5.3.29 → 3.5.3.29a → 3.5.6.8 → 3.5.7.4.


5 Upgrade of SAP Integrated Catalog.

Guide: SAP Note 620461

6 Upgrade of SAP SUS Web Presentation Server (SAP SUS WPS)

Guide:

Installation Guide SAP Supplier Self-Services

7 Upgrade of SAP Business Information Warehouse

Guide:

Component Upgrade Guide - SAP BW <Release>: <Operating System>



Guide:

Installation Guide SAP Enterprise Portal 5.0




10 Adjust the Customizing settings for the Supplier Enablement business scenario. For detailed information, see Adjusting SUS Customizing Settings [on page 34].

November 2003 33

4 The Upgrade


Since the same version of the SAP User Management Engine is used as in mySAP SRM 2.0, no upgrade activities are required for this component.

Adjusting Customizing Settings Adjusting Status Profiles

1. Log on to client 000.

2. Call transaction BS02.

3. Assign all status profiles with key CRMSUS* to a transport request.

4. Log on to your production client.

5. Call transaction SCC1.

6. Copy the status profiles from the transport contained in the transport request.

Adjusting Viewcluster and Views Adjust the following viewclusters and views to the delivery client 000:

Viewcluster or View Entry Transaction Code

CRMV_TIMEPROF SUS_HEADER01 SM34

CRMV_TIMEPROF SUS_ITEM01 SM34

CRMV_TIMEPROF SUS_RM_ITEM1 SM34

CRMV_M1O_STATUS SUS ORDER* SM30

CRMV_PROCESS_MA SUS* SM34

CRMV_ITEM_MA SUS* SM34

CRMV_IT_ASSIGN SUS* SM30

34 November 2003

4 The Upgrade

4.5 Catalog Content Management

4.5 Catalog Content Management 4.5.1 Technical System Landscape The following graphic shows the underlying architecture of Catalog Content Management including existing connections.

Architecture of Catalog Content-Management

Firewall

RFC Adapter

ITS AGate

BBPCRM (EBP)

XI


Firewall optional

SAP GUI / RFC

TCP / IP

RFC

RFC

File Adapter

Requisite BugsEye

Requisite eMerge

Integrated Catalog

HTTPS / OCI

CatalogsFileSystemBBPCRM (EBP)

BBPCRM (SUS)BBPCRM

EBP

Plain HTTP/S

httpAdapter


XIM

XML



November 2003 35

4 The Upgrade




Step Component Action

1 Installation/ Upgrade of SAP Exchange Infrastructure up to the point when you have to start the upgrades of the application systems

Guides:


As of mySAP SRM 2.0 the SAP Exchange Infrastructure is used as central messaging platform. In the course of this the SAP Exchange Infrastructure replaces the communication platform SAP Business Connector. New mySAP SRM Business Scenarios as well as enhancements of existing scenarios are developed exclusively using the SAP Exchange Infrastructure. However, for mySAP SRM 2.0 and 3.0, the existing SAP BC-based integration scenarios that you did implement with SAP EBP 3.0 are still supported. You can continue to use all functions of your existing SAP BC-based scenarios that were available with SAP EBP 3.0. You can use existing scenarios based on SAP BC in parallel to SAP Exchange Infrastructure based scenarios.

If you want to continue using SAP Business Connector, see SAP Service Market Place under the Internet address service.sap.com/connectors SAP Business Connector if you need to upgrade SAP BC. You can find the required upgrade guide at the same address under SAP Business Connector in Detail → Documentation. Take notice also of the information about mySAP SRM Business Packages that is provided there under Tools & Services → Adapters and Add-ons.

After the upgrade of SAP BC, the Access Control List (ACL) for the service pub.sap.transport.RFC:InboundProcess is reset to Internal. You must change the ACL to SAPUsers, to enable SAP BC to acceppt incoming RFC calls from SAP EBP. To change the ACL setting, see the SAP Business Connector Administration Guide under Managing Server Security → Controlling Access to Services and Files with ACLs → Assigning ACLs to Services and Folders.

For more information, see SAP Note 523131.

36 November 2003

4 The Upgrade


2 Upgrade of SRM Server

Guide:

Component Upgrade Guide – SAP CRM / SRM Server 4.0: <Operating System>

3 Installation of SAP ITS

Guide: SAP@Web Installation Guide

4 Installation / Upgrade of Requisite eMerge

Guide:

BugsEye® and eMerge™ 3.5 Installation and Upgrade Guide

The installation of Requisite eMerge is independent of the upgrade of SAP EBP. This means that you can install it before, during, or after the upgrade to SRM Server 4.0.


3.5.2.26 → 3.5.2.26a → 3.5.4.4 → 3.5.5.4.


5 Upgrade of Requisite BugsEye

Guide:




3.5.3.29 → 3.5.3.29a → 3.5.6.8 → 3.5.7.4.


6 Installation / Upgrade of SAP Integrated Catalog

Guide:


SAP Note 620461


Guide:


If you use SAP Enterprise Portal, you require SAP User Management Engine 3.0.


9 Installation of SAP Enterprise P t l 5 0

For information about availability, see the Pl tf A il bilit M t i i th SAP S i

November 2003 37

4 The Upgrade


Portal 5.0

Guide:

Installation Guide Enterprise Portal 5.0

Platform Availability Matrix in the SAP Service Marketplace: service.sap.com/sapportals → Products → Enterprise Portal → Enterprise Portal 5.0 → Platform Availability Matrix.



To enable the user to read and create business documents in Enterprise Buyer, make sure that the role SAP_BBP_STAL_PURCHASER is assigned to XIAPPLUSER.

38 November 2003

4 Appendix

4.1 Migrating Requisite BugsEye and eMerge from JRun to SAP J2EE Engine

4 Appendix 4.1 Migrating Requisite BugsEye and eMerge from JRun to SAP J2EE Engine Use To migrate Requisite BugsEye and eMerge from JRun to SAP J2EE Engine you must install the Requisite software on an SAP J2EE Engine and then adapt the settings of the web.xml file on the SAP J2EE Engine. This is necessary to enable a connection to the database with the old schema. JRun uses the web.xml file that is located under the path <DRIVE>:\...\JRun\servers\default\default-app\WEB-INF for storing information about connections. This information is required later to deploy the *.ear file of your Requisite application.

As a subsequent step, you must correct some parameters in the database. After the migration, you can upgrade your Requisite BugsEye or eMerge version to the required version.

Prerequisites 1. Your old Requisite BugsEye or eMerge version runs on JRun.

2. You must have the following additional documents at your disposal:

SAP J2EE Engine Installation / Dialog Instance Installation / Standalone Gateway Installation on <operating system> - For SAP Systems based on SAP Web Application Server 6.20

SAP J2EE Engine Deployment Guide for Requisite eMerge and BugsEye

Plug-in guide delivered with Microsoft Internet Information Server plug-in (MS IIS plug-in)

3. You must have the installation CDs for the following software at your disposal:

MS IIS plug-in for SAP J2EE

SAP J2EE Engine 6.20 with at least Support Package level 11

Procedure 1. Install and configure the SAP J2EE Engine including the MS IIS plug-in:

a. Install the SAP J2EE Engine with at least Support Package 11 as described in the documentation SAP J2EE Engine Installation / Dialog Instance Installation / Standalone Gateway Installation on <operating system>. Additional information is available in the SAP J2EE Engine Deployment Guide for Requisite eMerge and BugsEye.

b. Change the port of the SAP J2EE Engine (to 50000, for example).

c. Remove the JRun plug-in from MS IIS.

d. Install the SAPJ2EE Engine plug-in on MS IIS as described in the corresponding guide delivered with the plug-in.

2. Migrate the Requisite software. For the following steps, refer to the SAPJ2EE Deployment Guide for eMerge and BugsEye for detailled information. The corresponding sections are mentionend for each step.

a. Prepare your deployment directory (see page 2).

November 2003 39

4 Appendix


b. Copy *.jar files to your additional lib folder of your SAP J2EE Engine (see page 3, step 4).

c. Modify the library.txt file of your SAP J2EE Engine (see page 3, step 5). Make sure to use semicolons for separating the *.jar-files.

d. Modify the reference.txt file (see page 3, step 6).

e. Check your source Requisite folder (on JRun) and remove everything you do not need anymore (old libraries and folders, for example). This is necessary because you cannot deploy large *.ear files. Delete the subfolders upload and files that are located under your Requisite sap folder. Move the folder images if it is large-size and restore it afterwards in your deployed directory.

f. Create the *.war file out of all files contained in your source Requisite folder (see page 4, section Assembling steps for the commands).

g. Create the *.ear file (see page 5).

Check in the application.xml file in which you have renamed the display name.

h. Deploy your *.ear-file using SAP J2EE Deploy Tool as described in the SAP J2EE Deployment Guide for eMerge and BugsEye.

i. Adapt the web.xml in the root directory of your newly deployed Requisite application (dbUser, dbPassword, configName, dbFlavor, dbHost, dbPort).

j. Restart the SAP J2EE Engine.

3. Perform the following additional actions:

a. Adapt all URLs that have changed during migration. You must adapt the entry for the default login.htm of your Requisite folder in table BUGSEYE_CONFIG in the database. You can use the following SQL statement: select * from bugseye_config where value like '%http://%'

b. Adapt webrootPath in the bugseye database. You can use the following SQL statement: select * from bugseye_config where name like '%webrootPath%'

c. Adapt the Customizing of your Requisite applications.

d. Copy back all folders to your Requisite root directory that you have moved under the above mentioned step 2e.

e. Adapt the catalog URL in the Catalog Call Structure, if necessary:

i. Log on to your SAP SRM server.

ii. Call transaction SPRO and choose IMG → Supplier Relationship Management → SRM Server → Master Data → Define External Web Services.

iii. Mark the check box Requisite.

iv. Choose Standard Call Structure.

v. Change the catalog URL to http://<Host>/Requisite/BugsEyeSAP

40 November 2003

4 Appendix


The easiest way to get the correct URL is to log on to the catalog using the log in page and then copy the URL from the address bar of the browser. Just copy the URL, not the session information.

f. Restart the SAP J2EE Engine and log on to your migrated Requisite application.

4. Upgrade your Requisite application on your SAP J2EE Engine.

5. Deinstall JRun if you do not use it anymore.

November 2003 41

4 Appendix

4.2 Troubleshooting

4.2 Troubleshooting 4.2.1 Problems With Sending Internet Mails Use After the upgrade problems with sending Internet mails may occur in your Plan-Driven Procurement or Self-Service Procurement scenario. This may due to lost configuration settings.

Procedure If you encounter problems with sending Internet mails, see the corresponding Business Scenario Configuration Guide, section Configuration for Sending Internet Mails for the correct configuration settings.

42 November 2003

5 References

5.1 SAP Notes

5 References 5.1 SAP Notes The following table lists all SAP Notes mentioned in this documentation.

SAP Note Number Title

608082 Solution Upgrade Guide mySAP SRM using SAP EBP 4.0

590953 Master Guide my SAP SRM using SAP EBP 4.0

596514 Additions Upgrade to SAP CRM 4.0 / SRM Server 4.0

181255 Overview: SAP Notes on the R/3 Add-Ons PI and PI-A

485884 Information : Requisite eMerge and BugsEye delivery

441892 Integration of External Requirements from PS/PM/MRP in EBP 3.5/4.0.

601105 Release restrictions R/3 Plug-in 2003.1

620461 Upgrading Integrated Catalog

523131 Access Denied messages after Upgrade 4.0.1 to 4.6

November 2003 43

5 References

5.2 Documentation

5.2 Documentation The following table lists the documentation that is mentioned in this Solution Upgrade Guide.

• Guides that are marked with (*) are also available in SAP Service Marketplace at

the Internet address: service.sap.com/instguides

• For the Ramp-Up of mySAP SRM, no mySAP SRM Documentation CD is available. Therefore, the guides are only available in SAP Service Marketplace.

Title Where to find

Master Guide mySAP SRM Using SAP EBP 4.0 (*)

mySAP SRM Documentation CD-ROM

Component Upgrade Guide SAP CRM 4.0 /SRM Server 4.0 <Operating System> (*)


SAP@Web Installation Guide (*) Server Components CD

BugsEye® and eMerge™ 3.5 Installation and Upgrade Guide (*)

Requisite Technology BugsEye® CD

Upgrade Overview – SAP Exchange Infrastructure 2.0 Within mySAP SRM 3.0 (*)


Component Installation Guide: SAP User Management Engine 3.0 (*)


Administrator's Guide SAP User Management Engine 3.0(*)


Installation Guide SAP Enterprise Portal 5.0 SAP Service Marketplace under service.sap.com/instguides → Enterprise Portal

Upgrade Guide SAP Internet Pricing and Configurator 4.0 (*)


Component Upgrade Guide - SAP BW <Release>: <operating system>

SAP Service Marketplace under

service.sap.com/instguides → mySAP Business Intelligence → Using SAP BW <Release>

Component Installation Guide: SAP Integrated Catalog 3.0


Installation Guide SAP Supplier Self-Services


SAP Business Connector Administration Guide

SAP Service Marketplace under service.sap.com/connectors SAP Business Connector SAP Business Connector in Detail Documentation

SAP J2EE Engine Installation / Dialog Instance Installation / Standalone Gateway Installation on <operating system> - For SAP

SAP Service Marketplace at the Internet address service.sap.com/instguides

SAP Web Application Server SAP Web

44 November 2003

5 References

5.2 Documentation

November 2003 45

Systems based on SAP Web Application Server 6.20

Application Server 6.20

SAP J2EE Engine Deployment Guide for Requisite eMerge and BugsEye

SAP Service Marketplace at the Internet address service.sap.com/ocs-download

Archive for old Support Packages BBP/EBP and CRM Support Packages BBP/EBP: Requisite Products: BugsEye and eMerge

Plug-In Guide for MS IIS Pllug-In Delivered with Microsoft Internet Information Server plug-in

Business Scenario Configuration Guides for <mySAP SRM Business Scenario>

SAP Service Marketplace at the Internet address service.sap.com/ibc-srm

Documents

SRM30_SUG_26