Upgrade Master Guide ERP 2004

8/9/2019 Upgrade Master Guide ERP 2004

http://slidepdf.com/reader/full/upgrade-master-guide-erp-2004 1/113

Upgrade Master Guide

mySAP

TM

ERP 2004

Support Release 1

powered by SAP

NetWeaver™ ‘04

Using SAP

®

ECC 5 0

Document Version 1.00 – February 2005

Material Number 50072740



SAP AG

Neurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www sap com

© Copyright 2005 SAP AG. All rights reserved.

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.

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

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,

xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,

Tivoli, and Informix are trademarks or registered trademarks of IBM

Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems, Inc.

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.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

SAP Library document classification: PUBLICJava 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.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http://service sap com/ instguides

MaxDB is a trademark of MySQL AB, Sweden.



Typographic Conventions Icons

Type Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded by

body text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Exampl e t ext Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampl et ext>

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (such

as F2) or the ENTER key.

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



Contents

1 SAP Documentation Types ...........................................................6

2 Gett ing Started ...............................................................................8

2.1 How to Use the mySAP ERP Upgrade Master Guide...................................... 9

2.2 Target Audience................................................................................................. 9

2.3 Important SAP Notes ....................................................................................... 10

2.4 Further Information ......................................................................................... 11

2.5 Media Information ............................................................................................ 12

3 History of Changes ......................................................................13

4 Solut ion Overview ........................................................................14

4.1 Sample Upgrade Scenarios ............................................................................ 17

4.2 Software Component Matrix ........................................................................... 18

4.3 Valid Source Releases .................................................................................... 20

5 Upgrade.........................................................................................23

5.1 Selective Upgrade of System Landscapes .................................................... 24

5.2 R/3-only Upgrade ............................................................................................. 24

5.3 Upgrade Roadmap........................................................................................... 25

5.4 SAP Solution Manager for mySAP ERP 2004................................................ 25

6 Cross-Solution Topics .................................................................26

6.1 SAP NetWeaver™ Components ..................................................................... 26

6.2 Using Industry Add-ons .................................................................................. 29

6.3 Upgrading Mobi le Components...................................................................... 32

6.4 Upgrading Business Packages ...................................................................... 32

6.5 SAP NetWeaver Rapid Installer ...................................................................... 34

7 End-User Service Delivery...........................................................36

7.1 Target System Landscape .............................................................................. 36

7.2 Upgrade Sequence .......................................................................................... 37

7.3 Sample Upgrade Scenarios ............................................................................ 40

7.3.1 Manager Self-Service (MSS) ......................................................................................41 7.3.2 Employee Self-Service (ESS).....................................................................................46

8 Analytics .......................................................................................49



8.3 Sample Upgrade Scenarios ............................................................................ 51 8.3.1 Strategy Management.................................................................................................51 8.3.2 Legal Management Consolidation ..............................................................................53

9 Financials......................................................................................55



4 February 2005



Upgrade Master Guide mySAP ERP 2004

9.3 Sample Upgrade Scenario .............................................................................. 58 9.3.1 Electronic Bill Presentment & Payment (EBPP).........................................................58

10 Human Capital Management .....................................................61

10.1 Target System Landscape ............................................................................ 61 10.2 Upgrade Sequence ........................................................................................ 62

10.3 Sample Upgrade Scenarios .......................................................................... 67 10.3.1 Enterprise Learning (SAP Learning Solution)...........................................................67 10.3.2 E-Recruiting ..............................................................................................................70

11 Procurement and Logistics Execution .....................................74

11.1 Target System Landcape .............................................................................. 74

11.2 Upgrade Sequence ........................................................................................ 75

11.3 Sample Upgrade Scenarios .......................................................................... 80 11.3.1 Self-Service Procurement and Supplier Order Collaboration...................................80

12 Product Development and Manufacturing ...............................83 12.1 Target System Landcape .............................................................................. 83


12.3 Sample Upgrade Scenario ............................................................................ 86 12.3.1 Development Collaboration ......................................................................................86

13 Sales and Service.......................................................................89

13.1 Target System Landscape ............................................................................ 89


13.3 Sample Upgrade Scenarios .......................................................................... 93 13.3.1 Internet Sales in mySAP ERP ..................................................................................93

14 Corporate Services ....................................................................97

14.1 Target System Landscape ............................................................................ 97


14.3 Sample Upgrade Scenarios ........................................................................ 100 14.3.1 Travel Management................................................................................................100 14.3.2 Project Execution with cProjects.............................................................................102

15 Data Migrations ........................................................................105

15.1 FlexGL........................................................................................................... 105

15.2 Treasury ........................................................................................................ 105

15.3 Real Estate ................................................................................................... 105

15.4 Other Migrations .......................................................................................... 105

16 References ................................................................................106

16.1 Documentation ...........................................................................106

16.2 SAP Notes ...................................................................................107

17 Appendix ...................................................................................109

Post-Upgrade Activi ties for Internet Sales ........................................................ 109

February 2005 5



1 SAP Documentation TypesSeveral documents have been created to assist you in installing, implementing, operating andupgrading your SAP solutions. The Upgrade Master Guide (this document) is the first document youshould consider in the upgrade phase; it provides a summary of all the information and documentationto be considered for upgrading the solution at hand. The following figure displays an overview of themost important documentation types that are needed during the various phases in the life cycle of anSAP solution. Although the various types of documentation shown here are closely related to oneanother, each documentation type enables you to perform a different task that arises during the courseof a different solution phase.

Implementation

Master Guide

ConfigurationDocumentation

Release Notes

Component

Installation Guide

Component

Upgrade Guide

Upgrade Master Guide

Operation Upgrade

Solution Operation Guide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Fig. 1: Documentation types in the software life cycle

As shown in the figure, SAPterm, SAP Library and Implementation Guide (IMG) are cross-phasedocumentation.

• SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30

languages, as well as many definitions and glossary entries in English and German.To use SAPterm, visit SAP Service Marketplace at ser vi ce. sap. com/ sapterm.

• The SAP Library is a collection of function- and process-oriented documentation for SAPcomponents. It is located on SAP Help Portal at ht t p: / / hel p. sap. com. SAP Library also

contains Business Scenario Descriptions.

• The Implementation Guide (IMG) is a tool for configuring the SAP system to meet customerrequirements. Its structure and documentation are component-oriented. It is located In the SAP

menu of the SAP system under Tools → Customizing → IMG.

The Security Guide describes the settings for a medium security level and offers suggestions forraising security levels. A collective security guide is available for the SAP NetWeaver technologies likeSAP Web Application Server (SAP Web AS). This document contains general guidelines and

suggestions about system security. Other technologies and individual applications have a SecurityGuide of their own.

6 February 2005

http://service.sap.com/sapterm

http://help.sap.com/





Upgrade Master Guide mySAP ERP 2004

• The current version of the Security Guide is located on SAP Service Marketplace atser vi ce. sap. com/ secur i t ygui de.

The Component Installation Guide describes the technical implementation of an SAP component,taking into account the combinations of operating systems and databases. It does not describe any

business-related configuration. The Component Installation Guides for the different components canbe found on SAP Service Marketplace at ser vi ce. sap. com/ i nst gui des.

The Configuration Documentation is contained in the SAP Solution Manager, which is mentioned ina separate section of this document. SAP Solution Manager is a tool with various functions, one of itsmain functions being the configuration of SAP solutions and Business Scenarios. It contains IMGactivities, transactions, and so on, as well as documentation. Instead of the configurationdocumentation in SAP Solution Manager, there may be separate Business Scenario ConfigurationGuides in SAP Service Marketplace for earlier shipments of the Business Scenarios.

The Solution Operation Guide is the starting point for operating an SAP solution. The guide refersusers to the tools and documentation that are needed to carry out various tasks, such as monitoring,backup/restore, master data maintenance, transports, and tests. It also refers users to otherdocuments, for example the SAP Library, the Master Guide, and the Component Management Guides.

The current version is located on SAP Service Marketplace at ser vi ce. sap. com/ i nst gui des.

The Master Guide is the starting point for implementing an SAP solution. It lists the required SAPcomponents and third-party applications that are required for each Business Scenario. It providesscenario-specific descriptions of preparation, execution, and follow-up of an implementation. It alsooffers references to other documents, such as Component Installation Guides and SAP Notes. Thecurrent version is located on SAP Service Marketplace at ser vi ce. sap. com/ i nst gui des.

The Component Upgrade Guide describes the technical upgrade of an SAP component, taking intoaccount the combinations of operating systems and databases. It does not describe any business-related configuration. The current version is located on SAP Service Marketplace atser vi ce. sap. com/ i nst gui des.

Release notes are documents that contain short descriptions of new features or changes in an SAP

component since the previous release. Release notes about ABAP developments enable the SAPsystem to generate delta and upgrade IMGs. The current version is located in SAP ServiceMarketplace at ser vi ce. sap. com/ r el easenot es or in the SAP system under the menu path Help

Release information.

Upon reviewing this description of the supplementary information sources at your disposal, you will beready to get started.

February 2005 7

http://service.sap.com/securityguide


http://service.sap.com/instguides





http://service.sap.com/releasenotes

http://service.sap.com/releasenotes








2 Getting Started

2 Getting StartedThe Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP

solution. It provides an overview of all software components that are required to run respective SAPSolutions – both for key functional areas and for process levels. While providing this overview, theUpgrade Master Guide also refers to other documents, such as the Component Upgrade Guides andSAP Notes. For prior shipments of the Business Scenarios of an SAP Solution, an Upgrade MasterGuide may not be available. In these cases, a Solution Upgrade Guide or several Business ScenarioUpgrade Guides may have been published instead.

To facilitate the upgrade process, all information within this document is organized by key functionalarea. (For an explanation of the term key functional area, see Section “Solution Overview”.) For eachkey functional area, specific “model upgrade scenarios” are discussed in detail. You can therefore findthe information required for each model upgrade scenario within a separate corresponding section ofthis document.

The contents of this document include:

• An overview of all related technical components, whether mandatory or optional.

• Technical infrastructure examples to illustrate how these components may be distributed.(Depending on the actual business processes to be implemented, and in accordance with yoursecurity or performance requirements, the infrastructure you implement may differ from theseexamples.)

• Information about the versions of the required components.

• Information about the upgrade sequence and subsequent steps.

• References to related upgrade and configuration guides.

• References to the Solution Master Guide. This guide provides information about the overallimplementation sequence, references to related documentation, SAP Notes, and additional

installation information.

• Information about mutual dependencies that affect two or more components within the technicalinfrastructure.

• Finally, this document also provides information on permitted component combinations and thesupported source releases.

The Upgrade Master Guide at hand primarily discusses the upgrade-relevantprocesses, rather than its subordinate components. This means that additionalsoftware dependencies may exist without being mentioned explicitly in this document.You can find more information about component-specific software dependencies in the

corresponding Component Upgrade Guides.

To read the current version of the mySAP ERP 2004 Upgrade Master Guide and other

related upgrade guides, see SAP Service Marketplace at ser vi ce. sap. com/ erp-

i nst → mySAP ERP 2004.

We recommend that you review the current version of the documents available there;the contents of these documents are updated regularly.

8 February 2005

http://service.sap.com/erp-inst






2 Getting Started

2.1 How to Use the mySAP ERP Upgrade MasterGuideThe present document describes the upgrade of system landscapes that consist of more than onetechnical component. For each individual component, the upgrade process is explained in acorresponding Component Upgrade Guide. However, business processes usually require multiplecomponents, each of which interact with one another. Therefore, SAP delivers the Upgrade MasterGuide to facilitate (simultaneous) upgrades for each of your several components and to ensure, oncethe upgrade to mySAP ERP 2004 is complete, that all business processes you have implementedcontinue running smoothly.

Depending on the business processes you wish to upgrade, you may require different componentupgrade and configuration information, both before and during the upgrade process. The informationyou will need is available in SAP Solution Manager.

The mySAP ERP Upgrade Master Guide explains which components are affected by an upgrade and

which guides are required during the upgrade process.•

•

•

Section 6 provides technical information that is independent of any specific business process. Forexample, you can review information about SAP NetWeaver components and how these relate tothe mySAP ERP solution.

Sections 7 through 14 contain descriptions of the technical system landscape for each keyfunctional area in mySAP ERP 2004, including the necessary and optional software componentsand an example of a complete system infrastructure. In the sections dealing with model upgradescenarios, you will find more specific information like source releases, dependencies andrestrictions.

Section 15 discusses situations, for which data migrations are required.

2.2 Target AudienceThis documentation contains not only general information at solution and business process levels, butalso very detailed technical information within specific key functional areas. It is therefore intended notonly for decision-makers, but also for SAP consultants and SAP system administrators with detailedknowledge of databases, operating systems, and SAP systems.

February 2005 9



2 Getting Started

2.3 Important SAP NotesYou must read these SAP Notes before you start the upgrade. These Notes contain the most recent

information on the upgrade, 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 SAPService Marketplace at ser vi ce. sap. com/ not es.

List of Important SAP Notes

SAP Note Title

Note 805390 Preparation: ERP 2004 Inst. only with SAP Solution Manager

Note 760874 ERP: Support Package Stacks Release and Information Notes

Note 741821 Release Restrictions of SAP ERP 2004

Note 740930 Java Components for mySAP ERP 2004

Note 707730 Release Restrictions of SAP NetWeaver ‘04

Note 674417 Release Restrictions Plug-in Basis 2004.1

Note 663258 Corrections for R3up version 640

Note 623723 Upgrade: Application-specific problems

10 February 2005

http://service.sap.com/notes

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=805390&



















2 Getting Started

2.4 Further Information As your enterprise makes final preparations to begin the actual upgrade (or implementation), we

recommend that you also familiarize yourself with the following sources of information, all of which areat your disposal in SAP Service Marketplace. For example, there are important facts that you shouldtake into account in the planning phase of your upgrade; these facts are not fully described in thepresent document. Moreover, many of the reference sources named below provide additionalinformation that you may wish to consider to ensure that you complete your upgrade successfully.

• General Information on mySAP ERP

For information about business and technical aspects of mySAP Enterprise ResourcePlanning including news, services, events, demos, education and workshops, see SAP

Service Marketplace at ser vi ce. sap. com/ erp.

• Hardware Sizing

For detailed information about the calculation of hardware requirements (such as CPU, disk

and memory resources), including access to the SAP Quick Sizer, see SAP ServiceMarketplace at ser vi ce. sap. com/ si z i ng.

• Planning the System Infrastructure

For comprehensive information on technical infrastructure issues and network integration, see

SAP Service Marketplace at ser vi ce. sap. com/ t i .

For guidelines and recommendations that pertain to system and network security, see SAPService Marketplace at ser vi ce. sap. com/ secur i t ygui de.

For a complete overview of platform and technology-related topics, see SAP Service

Marketplace at ser vi ce. sap. com/ pl at f orms.

• mySAP ERP 2004 - Installation and Upgrade Information

For installation and upgrade information in addition to the mySAP ERP Master Guide,including the Upgrade Master Guide, Solution Operation Guide, and installation and upgradeguides for the individual components, see SAP Service Marketplace at

ser vi ce. sap. com/ er p- i nst → mySAP ERP 2004.

• mySAP ERP Upgrade

For tailored information to facilitate the preparation of the upgrade decision and the execution

of the upgrade project, see SAP Service Marketplace at ser vi ce. sap. com/ er p- upgrade.

Information on this page is updated on a monthly basis.

• Support Package Stacks

For the latest component version and patch level requirements, see SAP Service Marketplaceat ser vi ce. sap. com/ sp- st acks.

• Product Availability Matrix

For technical and release planning information on SAP components for quick reference, see

SAP Service Marketplace at ser vi ce. sap. com/ pam. Here you will find information on the

availability of SAP component releases and maintenance end dates, as well as on platform,language and country version availability.

• Safeguarding Services for Upgrade

During the project planning phase, SAP Safeguarding for Upgrades analyzes your upgradesituation with the SAP GoingLive Functional Upgrade check. The result is a service plan thatrecommends advanced services to facilitate your upgrade and keep you informed of the latest

February 2005 11

http://service.sap.com/erp

http://service.sap.com/sizing

http://service.sap.com/ti


http://service.sap.com/platforms


http://service.sap.com/erp-upgrade

http://service.sap.com/sp-stacks

http://service.sap.com/pam












2 Getting Started

SAP upgrade offerings. See SAP Service Marketplace atser vi ce. sap. com/ saf eguar di ngupgrade.

• Appl ication-speci fic Upgrade act iv it ies (so-cal led ASU Guides)

Application-specific upgrade activities are documented in special SAP Notes.To find theseNotes, simply ssearch for them in application area XX-PROJ-IMS-UPGR in SAP Service

Marketplace, at ser vi ce. sap. com/ not es.

• Upgrade adjustments wi th SPAU / SPDD

For information on transactions SPAU and SPDD, which help customers retain the objectsmodified in a previous release, see SAP Service Marketplace at servi ce. sap. com/ spau.

• High Availability

For information and documentation on high availability issues for a multitude of areas – forexample, SAP systems, databases, and tools – see SAP Service Marketplace atser vi ce. sap. com/ ha.

• SAP Upgrade Info CenterThe SAP Upgrade Info Center is your central point of access for all SAP upgrade information.It provides upgrade news, application-specific upgrade information and details on SAP

upgrade offerings. See SAP Service Marketplace at ser vi ce. sap. com/ upgrade.

2.5 Media InformationIn a separate section entitled “Media Information”, the mySAP ERP Master Guide displays in tabularform the content of the data carriers (DVDs and CDs) that are delivered with the mySAP ERP 2004package. The software components are listed in accordance with whether they belong to SAPNetWeaver ’04, mySAP ERP or SAP Solution Manager. The mySAP ERP Master Guide is available in

SAP Service Marketplace at ser vi ce. sap. com/ er p- i nst .

12 February 2005

http://service.sap.com/safeguardingupgrade


http://service.sap.com/spau

http://service.sap.com/ha


http://service.sap.com/upgrade



http://service.sap.com/upgrade







3 History of Changes

3 History of ChangesThe Upgrade Master Guide is regularly updated in SAP Service Marketplace atser vi ce. sap. com/ erp- upgrade.

Before starting the upgrade, we recommend that you immediately visit SAP ServiceMarketplace to ensure that you have reviewed the most recent edition of thisdocument.

The following table summarizes the changes that were made in each version of the Upgrade MasterGuide.

Upgrade Master Guide Version Important Changes

Version 1.00 – February 2005 First version

13 February 2005






4 Solution Overview

4 Solution OverviewPowered by SAP NetWeaver, the open integration and application platform, mySAP ERP combinescore ERP functionality with portal-based collaboration across the extended enterprise. mySAP ERPgives companies better control of their assets by optimizing business processes such as financialsupply chain management, e-recruiting and profitability assessments of employees, departments andcustomers.

mySAP ERP allows companies to regain active control of their entire administrative and operationsenvironment, thus substantially increasing efficiency and profitability. Equally, mySAP ERP enablesoptimal integration of established business processes with new technology, thus ensuring maximumoperational efficiency throughout the enterprise.

The mySAP ERP Business Map, displayed below, encompasses all key functional areas withinmySAP ERP. The mySAP ERP Business Map is located in SAP Service Marketplace at

ser vi ce. sap. com/ busi nessmaps Cross-Industry Maps Enterprise Resource Planning(ERP).

mySAP ERP 2004

End-User Service Delivery

Analy tic sStrategic Enterprise

ManagementFinancial Analytics Operat ions Analytics Workforce Analytics

Financials Corporate Governance

Human Capital

Management

Tal en t Man ag emen t Wo rk fo rc e Pro ces s Man ag emen t Wo rk fo rce Depl oy men t

Procurement andLogistics Execution

ProcurementSupplier

Collaboration

Inventory & Warehouse

Management

Outbound and

Inbound Logistics

Transportation

Management

ProductDevelopment and

Manufacturing

ProductionPlanning

ManufacturingExecution

ProductDevelopment

Life-Cycle DataManagement

Sales and ServiceSales Order

Management

Aftermarket Sales

and Service

Professional-Service

Delivery

Global Trade

Services

SAP NetWeaver™ People Integrat ion Informat ion Integrat ion Process Integrat ion Appl icat ion Plat form

Financial Supply Chain

ManagementFinancial Accounting

Management

Account ing

Incentive & Commission

Management

Corporate ServicesReal Estate

Management

Project Portfolio

Management

Travel

Management

Quality

Management

Environment,

Health & Safety

Enterprise Asset

Management

Fig. 2: Business Map of the mySAP ERP 2004 solution

In the left column of Figure 2, the key functional areas of mySAP ERP – including SAP NetWeaverfunctionality – are displayed. Among the fields at right, the key capabilities of mySAP ERP arerepresented. Each key capability comprises a number of business processes. Using the mySAP ERPBusiness Map in SAP Service Marketplace, you can navigate among these key capabilities to attain adetailed description at the business process level.

Note that End-User Service Delivery is also considered a key functional area, althoughit extends across almost all key capabilities belonging to other key functional areas.

14 February 2005

http://service.sap.com/businessmaps




4 Solution Overview

The Upgrade Master Guide at hand is structured according to the key functional areas of mySAP ERP2004, each of which is briefly described separately below.

• End-User Service Delivery

End-User Service Delivery consists of two functional areas: Manager Self-Service (MSS) andEmployee Self-Service (ESS). The related functionality is used in company-wide business processes,thus extending across almost all mySAP ERP key capabilities.

Manager Self-Service is designed for use by line managers, team- and project leaders. It contains awide range of services for managers who exercise budget and personnel responsibilities.

Employee Self-Service covers employee-specific processes, such as time management,compensation (salary statement), career management (personal skills), personal information, travelmanagement and country-specific processes, like tax forms and pension statements.

•

Analytics Analytics provides functionality for strategic enterprise management, financial analytics, operationsanalytics and workforce analytics. It assists you in adapting your business operations to the resultsfrom business analytics, thus improving the decision-making process. At the same time, Analyticshelps you optimize business processes across functions to improve overall business performance.

• Financials

mySAP ERP Financials provides a complete financial management and accounting solution for abroad range of industries. The solution enables your enterprise to optimize its financial supply chainand improve internal control processes for effective corporate governance.

With mySAP ERP Financials, your enterprise can realize secure and transparent accounting, improveits analytical capability, and proactively manage business performance, profit, and growth.

mySAP ERP Financials enables superior control and integration of the financial and businessinformation essential to strategic and operational decision-making. It improves management of internalcontrols, simplifies financial analysis, and enables adaptive business processes. With mySAP ERPFinancials, you can transform finance from an administrative function into a value-focused andstrategic business process in its own right.

• Human Capital Management

To compete effectively, you must align all corporate resources – including employees – with businessobjectives. You must transform traditional HR functions into a comprehensive program for humancapital management (HCM).

With mySAP ERP Human Capital Management (mySAP ERP HCM), you can maximize the value ofyour employees and align employee skills, activities, and incentives with business objectives and

strategies. mySAP ERP HCM also provides the tools to manage, measure, and reward individual andteam contributions.

Designed for global business, mySAP ERP HCM supports payroll functions, regulatory requirements,and best practices for more than 50 countries. It integrates with existing business systems and can becustomized to meet your requirements.

• Procurement and Logistics Execution

Using Procurement in mySAP ERP, your enterprise can pursue, for every type of good or service to beprocured, the commensurate procurement method – from employee self-service activities tosophisticated plan-driven approaches. Logistics Execution supports processes for InventoryManagement and Warehouse Management as well as for Transport Execution.

February 2005 15



4 Solution Overview

• Product Development and Manufacturing

Product Development and Manufacturing helps you manage the entire life-cycle of product-relatedMaster Data, including product structures, routings and documents from invention to phase-out. Byensuring immediate access to the most current data, Product Development and Manufacturingensures that your production planning and execution activities proceed smoothly.

• Sales and Service

Sales and Service addresses the sales- and customer-focused processes that your enterprise requiresto sell products and provide aftermarket services. Sales and Service enables your sales organizationto manage the sales cycle smoothly; it also ensures that your service organization maintains customersatisfaction by monitoring service orders and other subsequent activities.

• Corporate Services

Corporate Services supports all functions that directly impact core business processes or that can beapplied in several areas – as in the case of Quality Management, for example, which relates both toManufacturing Execution and to Outbound and Inbound Logistics.

16 February 2005



4 Solution Overview

4.1 Sample Upgrade Scenarios

Aside from discussing upgrade-related issues for each key functional area, this document alsoaddresses a number of examples to illustrate possible upgrade scenarios. In this document, suchexamples are named “sample upgrade scenarios.”

The following table shows the key functional areas of mySAP ERP 2004 for which a sample upgradescenario is discussed.

In mySAP ERP 2004, certain business processes have been re-named. For yourconvenience, we summarize the previous names of the affected business processesbelow (where applicable), alongside the current names.

Business ProcessesKey Functional Area(mySAP ERP 2004) Previous Name Current Name (in mySAP ERP 2004)

End-User ServiceDelivery

• Manager Self-Service

• Employee Self-Service

• Manager Self-Service

• Employee Self-Service

Analytics • Strategy Management

• BusinessConsolidation

• Strategy Management

• Legal Management Consolidation

Financials Bill to Cash Electronic Bill Presentment & Payment

Human CapitalManagement• Learning Solution• E-Recruiting

• Enterprise Learning• E-Recruiting


• Self-ServiceRequisitioning

• Supplier Self-Service

• Self-Service Procurement

• Supplier Order Collaboration

Product Developmentand Manufacturing

Design Collaboration Development Collaboration

Sales and Service Internet Sales for R/3 Internet Sales in mySAP ERP

Corporate Services • Travel Management

• Program & ProjectManagement: ProjectPlanning*

• Travel Management

• Project Planning with cProjects

*) Process defined in the Solution Map of the mySAP PLM Solution

17 February 2005



4 Solution Overview

4.2 Software Component MatrixThis section summarizes which key functional area of mySAP ERP 2004 uses which component. Notethat only the target component releases are listed here. If a technical upgrade (or migration) guideexists for a given component, then that component is shaded. If a component is not shaded, then oneof the following three conditions applies to it.

a. The component is new

b. Alternatively, the component can only be replaced (that is, overwritten) by a new installation

c. Alternatively, the new component version must be installed again, while the existing versionmust be de-installed.

The following table contains a high-level overview of the corresponding software components; it does

not, however, indicate whether a given component is optional or mandatory. You will find thisinformation in the mySAP ERP Master Guide in SAP Service Marketplace atser vi ce. sap. com/ er p- i nst .

Key Fuctional Areas of mySAP ERP 2004

Software Component End-UserServiceDelivery

Analytics Finan-cials

HumanCapital

Manage-ment

Procure-ment &

LogisticsExec.

ProductDev. &Manu-

facturing

Salesand

Service

Corpo-rate

Services

SAP ECC 5.0

LSO Front end 300

SEM-BW 400

FINBASIS 300

ERECRUIT 300

SAP Catalog ContentManagement 100

CPROJECTS 310_640

WFM CORE 110_640

SAP SRM SERVER 5.0

BI CONT 352 or 353

Internet Sales WAC 4.0

IPC 4.0

FSCM Biller Direct 3.0

XSS 5.0 (Self-Services)

LSO Content Player 3.0

LSO Offline Player 3.0

LSO AuthoringEnvironment 3.0

Mobile Time & Travel

1.6 (MTR + MTS)

18 February 2005





4 Solution Overview

Key Fuctional Areas of mySAP ERP 2004

Software Component End-UserServiceDelivery

Analytics Finan-cials

HumanCapital

Manage-ment

Procure-ment &

LogisticsExec.

ProductDev. &Manu-

facturing

Salesand

Service

Corpo-rate

Services

Mobile AssetManagement (MAM)2.5

Mobile Direct StoreDelivery (MDSD) 2.0

Mobile Sales forHandheld (MSR) 2.0

XI Content

Portal Content1

SAP NetWeaver Components

SAP WEB AS ABAP6.40

SAP WEB AS JAVA6.40

SAP BW 3.52

SAP XI 3.02

SAP MI 2.52

MI CLIENT 2.5

SAP KW 7.02

SAP EP 6.03

TREX 6.1

Adobe DocumentServices 1.0

SAP GUI 6.20 / 6.404

Other

SAP ITS 6.205

SAP BusinessConnector 4.7

SAP Solution Manager

1) Several objects originating from EP 5.0 Business Packages cannot be displayed in EP 6.0 / NW ’04. An Import Filter allows you to migrate the EP 5.0 BP objects that are able to run on EP 6.0. See SAPNote 642999; 2) Part of SAP Web AS; 3) Currently, only a migration from EP 5.0 to EP 6.0 (NW ’04) isavailable; 4) Required only for displaying (ABAP) dynpro-based screens; 5) Required for ITS-basedESS services, see Section 7.

The Industry Solution Add-ons are briefly discussed in Section 5.2 of this document.

February 2005 19



4 Solution Overview

4.3 Valid Source ReleasesThe following table summarizes the valid source releases of mySAP ERP 2004 and SAP NetWeavercomponents, along with the component release that your enterprise will target during its upgrade tomySAP ERP 2004.

ERP-relevant Component Valid Source Releases Target Release

SAP R/3 • R/3 3.1I

• R/3 4.0B

• R/3 4.5B

• R/3 4.6B

• R/3 4.6C

• R/3 Enterprise 4.7 with Extension Set 1.10

• R/3 Enterprise 4.7 with Extension Set 2.00

SAP ECC 5.0

SAP Learning Solution(LSOFE)

• 100 (based on SAP Web AS ABAP 6.20)

• 200 (based on SAP Web AS ABAP 6.20)

See also SAP Note 718625

LSOFE 300

SAP SEM (Strategic

Enterprise Management)

• 3.0A (with BW 2.1C)

• 3.1B (with FINBASIS 1.0B and BW 3.0B)

• 3.2 (with FINBASIS 1.5 and BW 3.1Content)

• 3.5 (with FINBASIS 2.0 and BW 3.1Content)

See also SAP Notes 718455 and 724419

SEM-BW 400

SAP FINBASIS (FinancialBasis)

• 200 (with R/3 Enterprise 1.1 / 2.0)

• 200 ( based on SAP Web AS ABAP 6.20)


FINBASIS 300

ERECRUIT (SAP E-Recruiting)

• 200 ( based on SAP Web AS ABAP 6.20)


ERECRUIT 300

SAP EBP (Enterprise BuyerProfessional)

• SAP EBP 1.0 (Business-to-BusinessProcurement 2.0B, Support Release 2)

• SAP EBP 2.0

• SAP EBP 3.0 Support Release 1

• SAP EBP 3.5

• SAP SRM Server 4.0

SAP SRMServer 5.0

20 February 2005



4 Solution Overview

ERP-relevant Component Valid Source Releases Target Release

BI_CONT • 3.5.1

• 3.5.2

BI_CONT 3.5.3

CPROJECTS • 310_620

Note that upgrades from CPROJECTS 200 toCPROJECTS 310 are not supported. See SAPNote 717650.

CPROJECTS310_640

WFM Core • 100 (based on SAP Web AS ABAP 6.20)

• 110_620 (based on SAP Web AS ABAP

6.20) A separate license for WFM Core is required.

WFM Core110_640

Internet Sales Web Applications (ISA WAC)

• ISA-WAC (based on J2EE 6.20).Migration is required (see Section 15.4)

ISA-WAC 4.0

Internet Pricing andConfigurator (IPC)

• IPC 3.0, SP13 (or lower SP-level)

• IPC 3.0 , SP14 (or higher SP-level)

Consult ser vi ce. sap. com/ i nst gui des

mySAP CRM SAP CRM 4.0 UpgradeGuides.

IPC 4.0

Requisite eMerge / BugsEye See SAP Note 485884

SAP NetWeaver™Component

Valid Source Releases Target Release

SAP Web AS • 4.6D

• 6.10

• 6.20 (ABAP only)

• 6.30 (Java only)

SAP Web AS6.40

SAP BW • 2.0B SP26

• 2.1C SP18

• 3.0B SP03

• 3.1 Content with BI_CONT 3.10 – 3.30

SAP BW 3.5

SAP XI • 2.0

For information on the required supportpackage level, see SAP Note 696034

Note that a direct migration from SAP XI 1.0 toSAP XI 3.0 is not possible.

SAP XI 3.0

SAP Mobile Engine Server • 2.1 SAP MI (MobileInfrastructure)2.5

February 2005 21





4 Solution Overview

NetWeaver Component(cont.) Valid Source Releases Target Release

SAP Enterprise Portal A migration from SAP EP 5.0 (SP 6) to SAPEP 6.0 (NW ’04) is available. For more

information, refer to ser vi ce. sap. com/ nw-howt ogui des Portal KW and

Collaboration.

A migration from SAP EP 6.0 (SP 2) to SAPEP 6.0 (NW ’04) is planned to be available at alater date.

SAP EP 6.0(most recent SPlevel)

Search and Classification(TREX)

• 6.0 (Migration is required) TREX 6.1

22 February 2005

http://service.sap.com/nw-howtoguides






5 Upgrade

5 UpgradeCustomers can be motivated to upgrade for many reasons, including the wish to:

Close functional gaps in the existing environment

Benefit from the latest technology

Reduce interfaces and costs

Improve solution management

It is important to note a fundamental assumption that many customers share before beginning theirupgrade, namely that the business processes they have successfully implemented in the sourcesystem landscape will work in an equivalent (if not improved) manner once the upgrade to the newsystem landscape is complete. To ensure that this assumption is fulfilled, SAP recommends that you

consider the following points:• In the event that you plan to use your mySAP ERP 2004 upgrade as an opportunity to implement

new processes, you will have to install new components or upgrade existing ones. In many cases,you will need to upgrade existing components and install new ones simultaneously.

• Before you begin the upgrade, you should therefore have a clear picture of the new processes youwould like to implement. Based on this decision, you will then determine which components need tobe considered and how your target system landscape should appear.

• With this view of your target system landscape in mind, inform yourself about the softwarecomponents you require for the business processes you plan to implement, then plan your targetsystem landscape accordingly. Also consider the planning activities described in the individualupgrade or installation guides.

As a rule, SAP recommends that you start planning your upgrade at least two to threeweeks in advance. The Upgrade Roadmap in SAP Solution Manager can be useful inthe planning phase of your upgrade project. For details, consult Section 5.3.

Information on the components and versions required for mySAP ERP 2004 processes can be found

in the ERP Solution Master Guide in SAP Service Marketplace at ser vi ce. sap. com/ er p- i nst .

The technical infrastructure diagrams within each of the following sections enable you to understandhow the different technical components interact, and which dependencies must be considered duringthe upgrade (or implementation) phase. They also demonstrate a typical distribution of componentsamong hosts.

To ensure secure data transfer between the Web application and the SAP ECCsystem, you should use Secure Network Communications (SNC).For detailed information on the use of SNC, see the SAP Service Marketplace at

ser vi ce. sap. com/ secur i t y → Security in Detail → Secure System Management.

As you plan your target system landscape, do not forget to consider infrastructural requirements, suchas high availability, security and performance. Such requirements ultimately determine the dimensionsof the infrastructure to be implemented.

February 2005 23


http://service.sap.com/security

http://service.sap.com/security




5 Upgrade

For comprehensive information on technical infrastructure issues and networkintegration, see SAP Service Marketplace at ser vi ce. sap. com/ t i .

5.1 Selective Upgrade of System Landscapes According to SAP’s Release Strategy, a new SAP application release can be seamlessly integratedwith all releases of other applications that are still in mainstream maintenance or extendedmaintenance. After an application is upgraded, all previously used scenarios are still available.However, if you want to take full advantage of a new scenario, or of the current version of an existingscenario, you might have to upgrade more than one SAP application within your landscape. Find outmore about SAP’s Release Strategy in SAP Service Marketplace atser vi ce. sap. com/ rel easest r ategy.

Bear in mind that important prerequisites must be met before deciding to upgrade a given componentand leave others untouched in your system landscape. For example, you should make sure that nodependency exists between the new and the old versions (or patch levels) of the interactingcomponents. Moreover, the business process you would like to run must explicitly allow combinationsof new and old releases.

Before making a decision, an analysis of possible dependencies and restrictions must be carried out toclarify the feasibility of the desired combination. If you are in doubt, turn to SAP Support for assistance.

If you run several components on the same SAP Web AS, be advised that all of thesecomponents must be upgraded at the same time.

For the sake of simplicity, the present guide assumes that you will upgrade all required technicalcomponents to the releases or versions defined for mySAP ERP 2004.

In addition and for your convenience, this document includes information on valid releasecombinations.

5.2 R/3-only UpgradeMany business processes run entirely within the R/3 (or R/3 Enterprise) system, so that in manycases, an R/3 system is sufficient to satisfy the business needs of a company. Provided that you donot plan to implement any new functionality, a simple upgrade of your existing R/3 system to SAP ECC5.0 can be carried out and no additional components have to be implemented. Your currentfunctionality will still be available after the upgrade; in other words, SAP ECC 5.0 contains all R/3functionality and additional new functionality.

As a rule, a simple upgrade of your R/3 system to SAP ECC 5.0 is sufficient, provided that you do notplan to implement new mySAP ERP 2004 processes that would require additional technicalcomponents. For detailed information about which processes require which technical components,consult the ERP 2004 Master Guide at ser vi ce. sap. com/ er p- i nst .

Keep in mind that you require an SAP Solution Manager Key to perform an upgrade of your R/3system (see Section 5.4).

Multi-Display Multi-Processing (MDMP) or Blended Codepage

SAP supports the process of upgrading an existing R/3 MDMP or Blended Codepage to SAP ECC

MDMP or Blended Codepage. However, SAP recommends that you convert to Unicode in the long

24 February 2005


http://service.sap.com/releasestrategy



http://service.sap.com/releasestrategy




5 Upgrade

term. If you operate an SAP ECC MDMP or Blended Codepage, you should expect this to involveadditional time and effort as well as some limitations. For more information, consult SAP Note 747036.

5.3 Upgrade Roadmap As a central guide for the entire project team, the SAP Upgrade Roadmap (Version 2.0) provides thelatest upgrade methodologies for the planning and execution of an SAP upgrade project. It bundlesbest practices from SAP for project management with functional and technical considerations forupgrading an entire SAP system landscape.

By using the Upgrade Roadmap in concert with the SAP Solution Manager, your enterprise can enjoyadditional benefits, such as tailored access to specific upgrade information and project trackingcapabilities. For further information, download the current Upgrade Roadmap content in SolutionManager format (as a transport request) from SAP Service Marketplace; seeser vi ce. sap. com/ sol ut i onmanager Downloads Other Content.

5.4 SAP Solution Manager for mySAP ERP 2004Using the SAP Solution Manager throughout the lifecycle of your mySAP ERP solution leads to fasterimplementation and more efficient operation, because all implementation and upgrade content for keyproject activities and business processes enabled by SAP applications is provided. In addition, SAPSolution Manager renders projects more transparent, since up-to-date central project documentation isavailable in one place at any point of time. Transparency of business processes and projectdocumentation is key for a successful application management and supportability of mySAPsolutions.To ensure the availability of this application management platform, an SAP Solution Managersystem (minimum requirement 3.1 SP20 or Release 3.2, SP03) is required for any upgrade orinstallation of mySAP ERP 2004.

To perform the upgrade to mySAP ERP 2004, an SAP Solution Manager Key isrequired.

For more information on this topic, refer to SAP Note 805390. Also, consult the section on SAPSolution Manager in the ERP 2004 Master Guide, located in SAP Service Marketplace atser vi ce. sap. com/ er p- i nst .

Each mySAP ERP (or SAP NetWeaver) system landscape must be assigned to one SAP SolutionManager. SAP Solution Manager is the required platform to efficiently support the implementation andoperation of your SAP solution. In the event of a support-relevant incident within your SAP system

landscape, SAP Support requires remote access to the SAP Solution Manager that hosts the affectedsystem landscape.

SAP Solution Manager plays a key role with regard to supportability and monitoring of systemlandscapes. We recommend that you get familiarized with this topic, which is discussed in the SAP

NetWeaver Master Guide at ser vi ce. sap. com/ nw04i nst al l at i on.

February 2005 25




http://service.sap.com/nw04installation






6 Cross-Solution Topics

6 Cross-Solution TopicsMost of the upgrade-relevant ERP processes described in this document are based on componentsthat belong to SAP NetWeaver. In this section the most important SAP NetWeaver components arebriefly discussed from the upgrade perspective.

Be advised, however, that this guide cannot provide as much detail as the corresponding SAPNetWeaver Upgrade Master Guide. Therefore, we recommend that you consult the latter to obtainmore specific information on upgrading SAP NetWeaver components. The SAP NetWeaver Upgrade

Master Guide is located at ser vi ce. sap. com/ nw04upgrade.

Additional cross-solution topics that are discussed in this chapter include:

• Using Industry Solution Add-ons

• Upgrading Mobile Components

• Upgrading Business Packages

This chapter deals with these topics as well.

Consider that the present guide deals with ERP-specific upgrade situations. Therefore, when SAPNetWeaver components are affected, always refer at the same time to the SAP NetWeaver UpgradeMaster Guide or the individual component upgrade guides, which are located in SAP Marketplace at

ser vi ce. sap. com/ nw04upgrade.

6.1 SAP NetWeaver™ Components As you are planning to upgrade the ERP business processes described in this guide, you will find that

some of the components that belong to SAP NetWeaver may have to be upgraded too. In general, thefollowing SAP Net Weaver ’04 components are most likely to require an upgrade:

• SAP Business Information Warehouse (SAP BW)

• SAP Exchange Infrastructure (SAP XI)

• SAP Web Application Server – Development Environment (SAP Web AS)

• SAP Mobile Infrastructure (SAP MI)

• SAP Knowledge Warehouse (SAP KM)

Sections 7 through 14 of this document discuss the ERP processes whose upgrade simultaneouslyrequires that one or more of these SAP NetWeaver components be upgraded. The respective software

component matrix indicates whether the components are required for the corresponding ERP process.

For mySAP ERP, the most important SAP NetWeaver components to consider are SAP BW, SAPWeb AS (ABAP and Java), SAP XI and SAP MI. In addition, other components, such as Search andClassification (TREX) and SAP Enterprise Portal (EP), may also play a role in the upgrade process.

In some cases it is possible to upgrade the aforementioned components separately from the ERPcomponents. In other words, the upgrades can be carried out in parallel.

Take note of the following important points regarding the SAP NetWeaver components:

SAP Business Information Warehouse:

A restriction exists if you wish to operate Business Information Warehouse and ERP CentralComponent in the same system. In a production environment, this setup can only be supported on a

26 February 2005

http://service.sap.com/nw04upgrade







project basis. If you are interested in implementing this setup, contact SAP. Nevertheless, a commonclient for SAP BW 3.5 and SAP ECC 5.0 is not supported.

SAP Exchange Infrastructure:

With the role of an Integration Server, SAP Exchange Infrastructure should be installed on a dedicatedSAP Web Application Server. However, with some restrictions, it can also share the same SAP Web AS with other applications (for example, SAP ECC). SAP does not recommend this shared operationmode for a production environment.

The following restrictions apply:

• You must simultaneously upgrade all components that share the same SAP Web Application Server .

SAP XI is normally used with multiple SAP applications {for example, SAP ECC, Master DataManagement (MDM), and so on} in a communication network. The release level of SAP XImust correspond to the release level of the newest application connected to this SAP XI

instance. This may lead to the following situation:

If you operate SAP XI together with a second application (for example, SAP ECC) and wish toupgrade a different application that runs on a separate system (for example, MDM), then anSAP XI upgrade may be required. You may pursue one of two options to carry out the SAP XIupgrade. With the first option, you can simultaneously upgrade both SAP XI and theapplication (for example, SAP ECC) that shares the same SAP Web AS with SAP XI. If thisfirst option cannot be pursued, you must use the second option to upgrade SAP XI. With thesecond option, SAP XI must be migrated to a separate SAP Web AS. Otherwise, you cannotupgrade SAP XI separately.

• If installed in a shared system, SAP XI must always be set up in a dedicated client.

• SAP XI is only supported on Unicode.

• A J2EE add-in is required for the SAP XI Java components.

If you wish to operate SAP XI and SAP ECC in the same system for productionpurposes, contact SAP. This can only be supported on a project basis.

SAP Mobile Infrastructure:

Depending on your requirements, you may either install a separate SAP Mobile Infrastructure systemto function as middleware (consisting of SAP Web AS ABAP and Java 6.40) or use the SAP Web Application Server of your ERP Central Component system. Nevertheless, SAP recommends the firstoption, especially in view of future upgrade scenarios; if a new version of SAP Mobile Infrastructure isreleased and you would like to deploy the new features, you could immediately upgrade a standalone

SAP Web AS to the new release. In contrast, you would not enjoy this advantage by using the SAPWeb AS of your ECC system, for you would have to wait until the corresponding ECC upgradebecame available.

February 2005 27




SAP Enterprise Portal:

A migration from SAP EP 5.0 (SP 6) to SAP EP 6.0 (NW ’04) is available. For more information, referto SAP Service Marketplace at ser vi ce. sap. com/ nw- howt ogui des Portal KW and

Collaboration.

A migration from SAP EP 6.0 (SP 2) to SAP EP 6.0 (NW ’04) is planned to be available at a later date.

Also refer to SAP Note 707730, in which the release restrictions of SAP NetWeaver ’04 aredocumented.

If you wish to operate SAP Enterprise Portal and SAP ECC in the same system forproduction purposes, contact SAP. This can only be supported on a project basis.

28 February 2005






6.2 Using Industry Add-onsIf an Industry Solution (IS) Add-on is running in your source system, then keep in mind that an upgradeto SAP ECC 5.0 is not supported for several IS Add-ons. On the other hand, some IS Add-onfunctionality has been integrated into SAP ECC 5.0, and even into lower R/3 releases. For more

information on the integrated functionality, consultSAP Note 700778 at ser vi ce. sap. com/ not es.

Customers who have implemented IS Add-ons should review the industry-specific upgrade guides

which are located at ser vi ce. sap. com/ i nst gui des.

The following table summarizes the availability of industry-specific add-ons and extensions.

Availability of SAP R/3, SAP R/3 Enterprise and SAP ECC Add-ons

mySAPERP 2004Industry Solution Industry-specificComponent

SAP R/33.1I-4.6B SAP R/34.6C SAP R/3Enterprise47x110

SAP R/3Enterprise47x200

SAP ECC5.0

Aerospace &Defense

SAP Aerospace &Defense

Add-on(4.0B, 4.5B)

integratedinto SAPDiscreteIndustries

Notsupported

Notsupported

Notsupported

Aerospace &Defense

SAP DiscreteIndustries

Notsupported

Add-on Add-on Notsupported

Add-on

Apparel & Footwear SAP Apparel &

Footwear

Add-on

(3.1I, 4.5B)

Add-on Not

supported

Not

supported

Add-on

Automotive SAP DiscreteIndustries

Notsupported


Add-on

Banking SAP Banking Add-on(4.0B, 4.6B)

Add-on IndustryExtension

IndustryExtension

IndustryExtension

Consumer Products SAP Beverage Notsupported

Add-on Notsupported

IndustryExtension(limited)

IndustryExtension(limited)

Consumer Products SAP CatchWeightManagement

Notsupported

Notsupported

Notsupported

Add-on Notsupported

Engineering,Construction &Operations

SAPEngineering &Construction

Add-on(4.5B)


Notsupported

Notsupported

Notsupported

Financial ServiceProviders

SAPCorporateFinanceManagement

Notsupported


IndustryExtension

IndustryExtension

Healthcare SAP PatientManagement

Add-on(4.0B)

Add-on Add-on Add-on Notsupported

February 2005 29









mySAPERP 2004Industry Solution

Industry-specificComponent

SAP R/33.1I-4.6B

SAP R/34.6C



SAP ECC5.0

High Tech SAP HighTech

Add-on(4.5B, 4.6B)


Notsupported

Notsupported

Notsupported

High Tech SAP DiscreteIndustries

Notsupported


Add-on

Higher Education &

Research

SAP Campus

Management

Not

supported

Add-on Add-on Add-on Not

supported

Insurance SAP InsuranceFS-CD

Add-on(4.5B, 4.6B)


Insurance SAP InsuranceFS-CM

Notsupported


Insurance SAP InsuranceFS-CS

Notsupported


Insurance SAP InsuranceFS-RI

Notsupported


Media SAP IS-M Add-on(4.0B) Add-on Add-on Add-on Notsupported

Mill Products SAP CableSolution

Add-on(3.1I, 4.5B)

Add-on integratedinto SAPDiscreteIndustries

Notsupported

Notsupported

Mill Products SAP MillProducts

Add-on(4.5B, 4.6B)

Add-on integratedinto SAPDiscreteIndustries

Notsupported

Notsupported

Mill Products SAP DiscreteIndustries

Notsupported

Notsupported

Add-on Notsupported

Add-on

Mining SAP Mining Add-on(4.6B)

Add-on Notsupported

Add-on Notsupported

mySAP PLM SAPEnvironment,Health &Safety

Add-on(4.5B, 4.6B)


IndustryExtension

IndustryExtension

Oil & Gas SAP Oil & Gas – IS-Oil

Add-on(4.0B, 4.6B)

Add-on Notsupported

Add-on Notsupported

30 February 2005





mySAPERP 2004Industry Solution

Industry-specificComponent

SAP R/33.1I-4.6B

SAP R/34.6C



SAP ECC5.0

Oil & Gas SAP Oil & Gas – JVA

Add-on(4.0B, 4.5B,4.6B)


IndustryExtension

IndustryExtension

Public Sector SAP FundsManagement

Add-On(4.0B, 4.6B)


IndustryExtension

IndustryExtension

Public Sector SAP HRPublic Sector

Add-on(4.0B, 4.5B,4.6B)


IndustryExtension

IndustryExtension

Public Sector SAP PublicSector PSCD

Notsupported


Telecommunication SAP RM-CA Add-on(4.6B)


Utilities SAP IS-U/CCS Add-on(4.6B)


Utilities SAP IS-U/FERC

Add-on(4.6B)

Add-on Add-on IndustryExtension

IndustryExtension

Utilities SAP IS-WASTE

Notsupported


Definitions:

• Industry Extension: Industry-specific component is integrated into and shipped as part of SAP R/34.7 Enterprise or SAP ECC 5.0.

• Add-on: Industry-specific component is shipped as an add-on for SAP R/3, SAP R/3 4.7 Enterpriseor SAP ECC 5.0.

• Not supported: means that the add-on or industry extension in question is not available on top of

the corresponding SAP R/3 or SAP ECC release.Furthermore, note the following:

• Releases of industry-specific add-ons may not be available for all SAP R/3, SAP R/3 Enterprise orSAP ECC releases.

• Releases that went into customer-specific maintenance before the end of December 2003 are notlisted in the table.

• Industry solutions that are realized through SAP R/3 Core, SAP R/3 Enterprise Core and SAPECC Core are not listed in the table.

Industry-specific functionality does not lie in the scope of the present document. However, wheneverpossible, this guide mentions industry-specific aspects of selected upgrade scenarios.

February 2005 31




6.3 Upgrading Mobile ComponentsThe upgrade of mobile components may involve the following parts:

• R/3 Backend system (including R/3 Plug-in)

• Mobile Engine Server, which is part of SAP Web AS (an upgrade of the Web Console on theJ2EE client may also be involved)

• Middleware, which is also part of SAP Web AS

• Mobile Engine Client for mobile applications (also known as “disconnected applications”)

• Mobile Application Component (war .file on the mobile device)

To ensure that your upgrade is successful, evaluate the aforementioned components before you startthe actual upgrade process. Note that dependencies may exist between component versions – for

example, between the Mobile Engine Client and the R/3 Plug-in version. Moreover, inform yourselfabout the supported platforms.

An existing (old) SAP MI (or ME) Client should never exchange data or besynchronized with a new SAP MI Server Component.

Note the following nomenclature change:

Previous Name New Name

Mobile Engine Client or Server

(with SAP Web AS 6.20)

Mobile Infrastructure Client or Server

(with SAP Web AS 6.40*, being part of SAPNetWeaver ’04)

*) Both ABAP and Java stacks are required.

After an upgrade of the Middleware (included in SAP Web AS), generate the Synchronization BusinessObjects once more and reset the Replication Database. As a rule of thumb, remember that an upgradeor a new installation of the SAP Web AS will always require you to perform an update of the front endcomponents.

For installation and upgrade information, see SAP Service Marketplace at

ser vi ce. sap. com/ i nst gui des SAP Components SAP Solutions for Mobile Business. In

addition, consult SAP Note 670644, in which all SAP MI upgrade-relevant notes are documented.

6.4 Upgrading Business Packages

Business Packages consist of pre-assembled Portal content that enables your enterprise to completebusiness tasks. In essence, Business Packages provide out-of-the-box portal applications that can beeasily modified to suit a customer's needs.

32 February 2005






After upgrading a Business Package its minor release changes for example from 60.1 to 60.2.

Release versioning of Business Packages has been defined as follows:<major>.<minor>.<support package>. The major package release follows the PortalPlatform release (for example, 60.x runs only on Enterprise Portal 6.0.) The minorrelease number applies to the upgrade package (for example, 60.2 is the upgradepackage of 60.1.) Support packages only contain corrections for iViews (for example,

60.1.1.) For more information, see ser vi ce. sap. com/ ep- content Presentations, Development News, Delta Feature List, Licensing Info Overview Maintenance Strategy for Business Packages.

The upgrade of a Business Package can consist of the following content:

• New languages

• New iViews or iViews with changed functions

• New or changed pages

• New or changed worksets

• New or changed roles

• New or changed dependencies to the backend system, for example:

o New Plug-in version (in case of plug-in-based Business Packages)

o New Support Package for the backend system

o New backend releaseDue to the dependencies between Business Packages and the backend system, it is particularlyimportant to read the section Technical Description in the documentation of the respective BusinessPackage and, in response, to take these dependencies into account. The upgrade of a BusinessPackage is often related to a backend system or plug-in upgrade, to ensure that all functions can beused to the maximum extent. Therefore, consider this in the planning phase of your upgrade project.

Note that the iView Studio, from which you could download BPs, has been replaced by the SDN(Software Developers Network) Portal Content Portfolio. The corresponding address is

ht t p: / / www. sdn. sap. com/ NW Business Content Portal Content Portfolio. There you can

also find further information on planned and available BPs, guidelines, and so on.

If you prefer, you can also download BPs directly from SAP Service Marketplace at

ser vi ce. sap. com/ swdc.

We recommend that you always archive the downloaded BPs locally to ensure that you have access tothose releases later.

Several objects originating from EP 5.0 Business Packages cannot be displayed in EP6.0 / NW ‘04. An Import Filter allows you to migrate the EP 5.0 BP objects that are ableto run on EP 6.0. See SAP Note 642999.

February 2005 33

http://service.sap.com/ep-content

http://www.sdn.sap.com/

http://service.sap.com/swdc







6.5 SAP NetWeaver Rapid InstallerSAP NetWeaver Rapid Installer is an installation and configuration wizard that reduces theimplementation of SAP Enterprise Portal along with other software components and selected SAPBusiness Packages from days to hours. SAP NetWeaver Rapid Installer enables you to lower totalcost of ownership by reducing the time required to install, deploy and configure SAP NetWeaverEnterprise Portal and Business Packages to a minimum.

SAP NetWeaver Rapid Installer also provides backend connectivity to systems for EnterpriseResource Planning (ERP), Business Warehouse (BW), Customer Relationship Management (CRM)and SAP Computing Center Management Systems (CCMS). It enables you to easily connect to thesesystems through a pre-configured portal with a minimum of interaction and configuration time.

SAP NetWeaver Rapid Installer installs a clearly defined set of business scenarios for mySAP ERP

2004 and mySAP CRM 4.0. Thus the SAP NetWeaver Rapid Installer allows an easy and rapid stepinto the world of SAP NetWeaver and SAP Enterprise Portal for mySAP ERP and mySAP CRMcustomers and also for customers who prefer to install SAP Enterprise Portal stand-alone withoutadditional business packages.

Two versions of SAP NetWeaver Rapid Installer are available for SAP NetWeaver ‘04:

SAP NetWeaver Rapid Installer 2.0 is based on SAP NetWeaver ’04 SR1.

SAP NetWeaver Rapid Installer 2.1 is based on SAP NetWeaver ’04 Support Package Stack 10(including SR1).

No upgrade is possible from version 2.0 to version 2.1. Version 2.1 is a complete new installation.

You cannot use SAP NetWeaver Rapid Installer 2.0 or 2.1 to install components ofearlier releases of SAP NetWeaver ’04.

Both versions of SAP NetWeaver Rapid Installer comprise the following SAP NetWeaver components:

Portal Platform

Knowledge Management (including Search and Classification [TREX])

Collaboration

SAP Web AS Java 6.40

They also install the following software components:

Business packages with Employee Self Service (ESS) and Manager Self Service (MSS) businessscenarios (prerequisite: mySAP ERP 2004 is installed)

SAP Self Service (XSS) 5.0 which is based on SAP NetWeaver 04 Java Stack and connects to thebackend functions in the ERP system. For more information on SAP XSS, see SAP Service

Marketplace at ser vi ce. sap. com/ er p- i nst mySAP ERP 2004.

Business packages with business scenarios for mySAP CRM (prerequisite: mySAP CRM 4.0 andSAP BW 3.5 is installed)

An SAP System Landscape Directory (SLD) if you want SAP NetWeaver Rapid Installer to install anew SLD.

CCMS agents to enable monitoring in the Portal

34 February 2005






Product Information and Documentation

You can find detailed product information at ser vi ce. sap. com/ nw- r i . Read this information and

check if SAP NetWeaver Rapid Installer 2.0 or 2.1 is a viable alternative for you to install SAPEnterprise Portal based on SAP NetWeaver ‘04.

Before installing the software, read the SAP NetWeaver Rapid Installer Installation Guide available forboth versions and describing in detail the installation procedure, hardware and software requirementsand pre-installation steps. You can find this document and additional information on the SAPNetWeaver Rapid Installer DVD (for both versions) in the folder Documentation.

DVD Order Process

Versions 2.0 and 2.1 of SAP NetWeaver Rapid Installer can be ordered from the SAP SoftwareCatalog.

To access the SAP Software Catalog, see SAP Service Marketplace at ser vi ce. sap. com/ swdc. In

the detailed navigation area, choose Ordering SAP-Software. The SAP Software Catalog opens in a

separate window. In the right-hand window, choose SAP NetWeaver → SAP NetWeaver RapidInstaller 2.0 or SAP NetWeaver Rapid Installer 2.1.

February 2005 35

http://service.sap.com/nw-ri






7 End-User Service Delivery

7 End-User Service DeliveryFrom a business management standpoint, customers usually implement ESS and MSS together, in acommon system landscape, since both processes can be integrated in the same Enterprise Portal.However, if you would like to implement only one of these processes or implement them on separatesystems (due to performance or security considerations), refer to Section 7.3.1 (for MSS) or Section7.3.2 (for ESS), which separately discuss the components to upgrade or install for each process.

7.1 Target System LandscapeFigure 3 shows an example of a full-fledged system landscape for the key functional area End-UserService Delivery of mySAP ERP 2004. Depending on your initial situation and requirements, this couldbe a target landscape for your upgrade.

SAP BW

NW BW System

RDBMS

Web AS ABAP 6.40

BI CONT 3.5.2

SAP SRM

Web AS ABAP 6.40

RDBMS

SAP SRM Server 5.0

SRM System

SAP CCM 1.0

SAP ECC

Web AS ABAP 6.40

RDBMS

SAP ECC 5.0

ECC System

ERECRUIT 300

Frontend (PC)

Ado be Reader 6.0.2

Mail Software

Web Browser

J2EE Server

Ado be Doc umen t

Services 1.0

Web AS Java 6.40

Search &

Classification

TREX 6.1

Web AS Java 6.40

EP 6.0 Server

Portal Platform 6.0

Content Management &Collaboration 6.0

BP for ESS

BP for MSS

RDBMS

RDBMS

MSS 100

ESS 100

PCUI_GP 100

XSS

Fig. 3: Sample System Landscape for End-User Service Delivery

Several possibilities are available to distribute the components, so this diagram provides just oneexample. The distribution depends on many factors, such as sizing, security, available hardware, andso on. In practice, any distribution of components among hosts is possible – from a minimal systemlandscape to a maximum distributed landscape, where every component runs on its own host, or evenon multiple hosts. Note that you will require a dedicated system for SAP Solution Manager.

The installation of the Portal Platform is mandatory for End-User Service Delivery, whereas theinstallation of the Knowledge Management Platform – including Content Management & Collaboration6.0 and Search and Classification (TREX) 6.1 – is optional, and depends on the iViews you plan touse.

36 February 2005




For more information about the mandatory or optional character of the components for End-UserService Delivery, consult the ERP Master Guide in SAP Service Marketplace at

ser vi ce. sap. com/ er p- i nst mySAP ERP 2004.

7.2 Upgrade SequenceThe following table describes the suggested sequence of upgrade or installation steps that you shouldperform to obtain a full-fledged system landscape.

For information about the required component versions and patch levels, see theSoftware Component Matrix and the current Support Package Stacks in SAP Service

Marketplace at ser vi ce. sap. com/ sp- st acks.

The Release and Information Notes (RIN) also document the required componentversions and patch levels for every Support Package Stack. For your convenience,SAP Note 760874 lists all RINs that have been issued for mySAP ERP.

SAP recommends that you adhere to the component versions and patch levelsdocumented in the latest ERP Release and Information Note.

Step Action

[Corresponding Documentation]

Remarks and subsequent steps


1 Upgrade your R/3 System to SAP ECC 5.0[ECC 5.0 Upgrade Guide: <OperatingSystem> + SAP Note 689574]

• R/3 PI 2004.1 is included in theupgrade. No PI supplement CD isrequired; see SAP Note 700779 and the subsequent step.

• During the upgrade (BIND_PATCHphase), you should bind all ABAPsupport packages that areavailable for SAP ECC 5.0 and R/3PI.

To benefit from the new

Web Dynpro-based SelfServices functionality, youmust upgrade your R/3 toSAP ECC 5.0; see SAPNote 752312.

2 Upgrade the SAP R/3 Plug-in

For more information, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736 (Release restrictions R/3 Plug-in 2004.1).

Also, consult SAP Service

Marketplace at servi ce. sap. com/ r3-

This step is only required if your R/3system is not upgraded to SAP ECC5.0, in which case the Web Dynpro-based Self-Services are not available.

February 2005 37



http://service.sap.com/r3-plug-in







pl ug- i n.

3 Optional: Install ERECRUIT 300 either onthe SAP ECC System or on a standaloneserver.

[See SAP Note 717802]

Required to integrate E-Recruiting inMSS:

The decision to install ERECRUIT on aseparate server depends on yourrequirements. Consult the mySAP ERPMaster Guide atser vi ce. sap. com/ er p- i nst ; also

review Section 10.3.2 of this document.

4 Install SAP Web AS Java 6.40 • SAP Web AS Java includes SAPJ2EE Engine 6.40, SAP JavaConnector (JRFC), SAP Java TechServices

• If the source release of your J2EEEngine is 6.20, you must first de-install the 6.20 version, then installJ2EE 6.40. For more information,refer to the SAP NetWeaverUpgrade Master Guide atser vi ce. sap. com/ nw04upgrade.

• If you are using J2EE Engine 6.30,you can directly import SupportPackage 04. By doing this, you willattain the 6.40 version. Note that

XSS 500 can only be installed onan SAP Web AS Java 6.40.

If you decide in favor of a newinstallation, see:

servi ce. sap. com/ nw04i nst al l ati on Installation SAP Web AS

Installation Guide <operating system>

5 Install XSS 500

[Installation Guide – Java Components on

mySAP ERP 2004]

• XSS consists of the subcomponentsMSS 100, ESS 100 and PCUI_GP100. You may either install XSS inits entirety (using the ERP Java

installer, which is the default mode)or deploy each of thesesubcomponents individually (withSDM).

Both MSS and ESSrequire PCUI_GP;neither component canbe used withoutPCUI_GP. See alsoSections 7.3.1 and7.3.2.

38 February 2005















• Correspondingly, you will findpatches for each of thesesubcomponents in SAP ServiceMarketplace.

• XSS is required only if you wouldlike to use the Business PackagesMSS 60.1 (mySAP ERP 2004) and /or ESS 60.1 (mySAP ERP 2004),both of which are Web Dynpro-based

Depending on the process(es) youwould like to implement, considerusing the SAP NetWeaver Rapid

Installer , which is an installationand configuration wizarddocumented in Section 6.5. Usingthis tool, you can install severalcomponents at once, including SAPEnterprise Portal, BusinessPackages, XSS, and so on. Formore information on SAP NW RapidInstaller, reviewser vi ce. sap. com/ nw- r i .

6 Optional: Install Adobe DocumentServices (ADS) 1.0.

[Installation Guide – Adobe DocumentServices NW ’04 SR1]

ADS is mandatory if you would like touse Adobe forms.

7 Optional: Upgrade SAP BusinessInformation Warehouse

[Component Upgrade Guide SAP BusinessInformation Warehouse 3.5: <OperatingSystem>]

PI BASIS 2004_1_640 is included in theupgrade to SAP BW 3.5

8 Optional: Install BI_CONT (Release 3.5.2 or3.5.3)

See SAP Note 717812 or 774933(BI_CONT 3.5.3)

9 Install (or migrate to) SAP EnterprisePortal 6.0 (based on SAP Web AS 6.40)

[Component Installation Guide SAPEnterprise Portal on SAP Web AS 6.40]

CMC (Content Management &Collaboration) is included in the Portalinstallation.

A migration from SAP EP 5.0 (SP 6) toSAP EP 6.0 (NW ’04) is available. Formore information, refer to Section 6.1.

A migration from SAP EP 6.0 (SP 2) toSAP EP 6.0 (NW ’04) is planned to beavailable at a later date.

For installation information, consultservi ce. sap. com/ nw04i nst al l ati on Installation SAP EP.

Refer also to Section 6.5.

10 Import Business Packages for MSS andESS (60.1 or above)

[ser vi ce. sap. com/ ep- content ]

For MSS you can combine the worksetsof the Business Packages MSS 60.1

(Java Portal Components) with MSS

February 2005 39














60.1 (mySAP ERP 2004) in oneEnterprise Portal 6.0.

BPs can be downloaded from PortalContent Portfolio at

ht t p: / / www. sdn. sap. com/ NW

Business Content Portal ContentPortfolio, or

from SAP Service Marketplace directly:


11 Install Search and Classification (TREX)6.1.Use the following parameters during theinstallation:

• Perform the installation steps to set upan RFC connection.

• Automatic language recognition is notrequired. You can adopt the defaultsettings for document languagesduring the installation of Search andClassification (TREX).

• No Python extensions are required.

[Installation Guide: Search & Classification(TREX) 6.1]

A migration is necessary if you alreadyhave TREX 6.0 (SP1) running in yoursystem landscape. The migrationprocedure does not change the existing

system. You install the new TREXsystem parallel to the existing systemand carry out a migration of the existingindexes, queues, and configuration filesfor the new system.

[Component Migration Guide – Searchand Classification (TREX)]

12 Optional: Upgrade SAP SRM Server

[Component Upgrade Guide – SAP SRMServer 5.0: <Operating System>]

13 Optional: Install SAP Content CatalogManagement (CCM) 1.0

[SAP Note 705060]

SAP CCM 1.0 can be installed on anysystem based on SAP Web AS ABAP6.40. In the above example it is installedon the SRM system.

Many of the upgrade or installation steps listed above can be carried out in parallel – as can forexample the upgrade or installation of SAP BW and SAP EP, Search & Classification and SAP Web AS Java for the J2EE applications.

7.3 Sample Upgrade Scenarios As stated above, several components are required to benefit fully from mySAP ERP functionality.Nevertheless, it is also possible to establish a system landscape that covers minimum requirements forMSS or ESS as standalone processes. The following sections describe how such system landscapescould appear.

40 February 2005








7.3.1 Manager Self-Service (MSS)7.3.1.1 Overview

SAP MSS provides line managers, team leaders and project leaders and department headsthroughout the enterprise with tools to help them accomplish their goals quickly and easily.

Central departments such as Controlling or HR can present personalized information in the user’sportal, enabling managers to find “their” information in “their” portal, in the right place at the right time.

Empowering managers to execute human capital and finance management strategies for budgeting,recruitment, compensation, and cost management also delivers a significant return on investment forthe finance and HR departments. SAP MSS reduces the number of phone calls and requests made bymanagers to various departments and, in doing so, frees up HR and finance staff to focus on strategic

activities. The tools automate paper-based processes, such as requests for master data changes orperformance appraisals. They also enhance HR and financial backend systems by making pertinentinformation available to managers throughout the enterprise.

MSS Business Packages

As of mySAP ERP 2004 forward, SAP offers Web Dynpro-based Self-Services. For the role“Manager”, the following two Business Packages are delivered with mySAP ERP 2004:

• MSS 60.1 – Java Portal Components

• MSS 60.1 (mySAP ERP 2004) – Web Dynpro

If you wish to use Web Dynpro-based Self-Services you must upgrade to ECC 5.0.Refer to SAP Note 752312.

The following table summarizes the existing functionality and worksets of the two MSS BusinessPackages.

MSS 60.1 – Java Portal Components MSS 60.1 (mySAP ERP 2004) – Web Dynpro

Overview: Attendance Overview, PhoneList, Reminder of Dates

Overview: Homepage Concept

Attendance: Team Calendar (based on Attendance / Absence infotype information), Attendance Details

Attendance: Team Calendar (based on Database ofRequest), Details can displayed from the TeamCalendar

Employee Review: Employee Profile, TeamViewer, Compensation Information,Personnel Development, EmployeeDocuments, Appraisal Overview, Edit Appraisal, Objective Settings and Appraisals

Employee Review: not yet available on Web Dynpro!

Personnel Change Requests: Elevenprocesses with JSP forms available

Personnel Change Requests: Adobe Interactive Formintegration, described in SAP Notes 741821 and761246

February 2005 41




MSS 60.1 – Java Portal Components(continued)

MSS 60.1 (mySAP ERP 2004) – Web Dynpro

Recruiting: Position Overview, Vacancyrequest, Applicant Tracking – Integratedwith HR-Recruitment Component

Recruiting: E-Recruiting integration. RequisitionRequest and Status Overview, Candidate Assessmentand Status Overview – Integrated with E-Recruiting

Reporting: Report selection based on MDTcustomizing (external ITS needed), BWCockpits: Headcount, Overtime and Illness,Skills Management

Reporting: Report selection based on MDT customizing(internal ITS needed), BW Cockpits: Headcount,Overtime and Illness, Skills Management

Compensation: Compensation Planningand Approval, Compensation Information;

Enterprise Compensation Management(ECM) -> Planning and Approval,Compensation Information (ECM)

Compensation: not yet available on Web Dynpro

Quota Planning and Transfer Headcount Planning (renamed), Transfer Headcount(renamed)

Depending on the worksets and functions you would like to provide to your managers, you can use thenew Web Dynpro-based Manager Self-Services [MSS 60.1 (mySAP ERP 2004).] Additionally, for theworksets and functions that are not yet available on Web Dynpro, you can use the workset of the MSS60.1 (Java Portal Components) Business Package.

Example: You would like to provide the following services to your managers:

• Team Calendar

• Employee Review

• Reporting

Team Calendar and Reporting functionality is available on Web Dynpro [MSS 60.1(mySAP ERP2004).] In contrast, the Employee Review workset is available with MSS 60.1 (Java PortalComponents.) To provide your managers with the functionality they need you can create a managerrole in EP 6.0 with the Team Calendar and the Reporting workset from the Business Package MSS60.1 (mySAP ERP 2004) and the Employee Review workset from the Business Package MSS 60.1(Java Portal Component.)

42 February 2005




7.3.1.2 Technical System Landscape

The following table shows an example of a minimal system landscape for MSS.

System Host Name (example) Component(s)

1 SAP ECC System • SAP ECC 5.0

• SAP Web AS ABAP 6.40

2 NW BW System • BI Content 3.5.2


3 Enterprise Portal Server • Business Package for MSS 60.1(mySAP ERP 2004)

• Portal Platform 6.0

• MSS 100

• PCUI_100

• SAP Web AS Java 6.40

Before installing the BP for MSS you should know which services you would like to use. If required,you can combine the Worksets of the Business Packages MSS 60.1 (Java Portal Components) withMSS 60.1 (mySAP ERP 2004) in one Enterprise Portal 6.0; refer to the example in the previoussection. If you do not wish to use the Web Dynpro-based services, you do not need to install XSS (ormore precisely, MSS and PCUI_GP as in the above system landscape.)

XSS 500 consists of the subcomponents MSS 100, ESS 100 and PCUI_GP 100. You may eitherinstall XSS in its entirety (using the ERP Java installer, which is the default mode) or deploy each ofthese subcomponents individually (with SDM).

Both MSS and ESS require PCUI_GP; neither component can be used withoutPCUI_GP.

If your specific situation demands that you implement Manager Self-Service alone, then you maydeploy MSS 100 and PCUI_GP 100 individually, provided that you plan to use the Web Dynpro-basedservices.

Since MSS 100 and PCUI_GP 100 can be patched individually, make sure that theyare kept on the same patch level. Always consult the ERP Release and InformationNotes.

Note that you may install and operate XSS (or any of its subcomponents) along with SAP EnterprisePortal on a common server, on the same J2EE instance, or on separate servers. Your specificrequirements should ultimately determine the most suitable option. If you decide to install XSS andSAP Enterprise Portal on the same J2EE instance, you should consider using SAP NetWeaver RapidInstaller, which is an installation and configuration wizard documented in Section 6.5. Furthermore,

consult SAP Service Marketplace at ser vi ce. sap. com/ nw- r i .

February 2005 43






Note that a restriction exists if you wish to operate Business Information Warehouse and SAP ERPCentral Component (ECC) in the same system. In a production evironment, this setup can only be

supported on a project basis. If you are interested in implementing this setup, contact SAP.

If you already have an SAP Business Information Warehouse system installed (2.1C or 3.0), you donot necessarily need to upgrade it to SAP BW 3.5.

7.3.1.3 Valid Combinations and Source Releases

The following system requirements apply for the Business Package for Manager Self-Service:

Component Release Remarks

Backend system SAP R/3 • R/3 4.0B – 4.6C

•

SAP R/3 Enterprise 4.7,Extension Set 1.1 ; R/3Enterprise 4.7,Extension Set 2.0 (min.SP2).

BP MSS 60.1 (Java PortalComponents)

SAP R/3 Enterprise 4.7,Extension Set 2.0 (min. SP2)is only required for iViewsthat use EnterpriseCompensation Management(ECM)

Backend system SAP ECC • ECC 5.0 For MSS you can combinethe worksets of the BusinessPackages MSS 60.1 (JavaPortal Components) withMSS 60.1 (mySAP ERP2004) in one Enterprise

Portal 6.0.

SAP Enterprise Portal • 6.0 SP 2

• 6.0 (on 6.40)

Currently, you cannotupgrade from EP 6.0 (SP2)to EP 6.0 (on 6.40)

SAP BW • SAP BW 2.1C + SupportPackage 09 or above.For this release you alsoneed an SAP InternetTransaction Server(ITS) on the same host.

• SAP BW 3.0B +

Support Package 03 orabove.

• SAP BW 3.1 Content

• SAP BW 3.2 Content (orabove).

This system is only requiredfor SAP BW Web Reporting

44 February 2005




Component (continued) Release Remarks

SAP ITS • 6.20 You need SAP ITS for SAPBW 2.1C and the reportingiViews Reports and SelectionCriteria, for which SAP GUIfor HTML is required. Youalso need SAP ITS for iViewsin ESS within the MSSworkset.

Business Package forManager Self-Service

• 60.1 (Java PortalComponent).

• 60.1 (mySAP ERP2004).

This Business Packagerepresents the Java frontend.It runs on the SAP J2EE

Engine of SAP EnterprisePortal. For instructions oninstalling this BusinessPackage, review SAP Note642775.

SAP Enterprise Portal Plug-in (WP-PI)

• For backend SAP R/34.0B – 4.6C, you needWP-PI 500_46C patch03 or above.

• For SAP R/3 Enterprise4.70, you need WP-PI500_620 patch 03 orabove.

• For SAP ECC, you neednot to concern yourselfwith WP-PI since it isincluded in PI_BASIS2004_1_640

SAP R/3 Plug-in (PI) • 2004.1 with at least SP1

If you would like to use the Employee Documents iView (available with MSS BP 60.1, Java PortalComponents), consult SAP Note 640634.

SAP recommends that you install the current support packages to the components listed on the table.

You are required to implement SAP R/3 Component Organizational Management. Furthermore, it ismandatory to maintain staff assignment (organizational units, positions and assigned persons, O-S-P)with manager positions in Organizational Management.

Integration between SAP R/3 Components Organizational Management and Personnel Administrationmust be active. Also, you must complete the Enterprise Portal installation before you start installing theBusiness Package. We recommend that you test the portal installation sufficiently before you install theBP MSS. Review composite SAP Note 568576 for current information on the BP MSS (My Staff).

February 2005 45




7.3.2 Employee Self-Service (ESS)7.3.2.1 Overview

Using SAP ESS, employees maintain their own personal information and control many administrativetransactions and other processes handled by HR staff. The goal is to streamline approval processesand tasks like checking vacation time or choosing benefits. SAP ESS not only grants better access topersonal data, it informs employees as they move through life and work changes, by combiningapplications with support information.


The following table shows an example of a minimal system landscape for ESS.

Server Host Name (example) Component(s)



2 Enterprise Portal Server • Business Package for ESS 60.1

• Portal Platform 6.0

• ESS 100

• PCUI_GP 100

• SAP Web AS Java 6.403 SAP ITS 6.20 • SAP ITS 6.20

To implement ESS you require the corresponding business package (BP for Employee Self-Service60.1.) If you do not want to use the Web-Dynpro-based services, you do not need to install XSS (or,more precisely, ESS and PCUI_GP as in the above system landscape.)

XSS 500 consists of the subcomponents MSS 100, ESS 100 and PCUI_GP 100. You may eitherinstall XSS in its entirety (using the ERP Java installer, which is the default mode) or deploy each ofthese subcomponents individually (with SDM).

Both MSS and ESS require PCUI_GP; neither component can be used withoutPCUI_GP.

If your specific situation demands that you implement Employee Self-Service alone, then you maydeploy ESS 100 and PCUI_GP 100 individually, provided that you plan to use the Web Dynpro-basedservices.

Since ESS 100 and PCUI_GP 100 can be patched individually, make sure that they arekept on the same patch level. Always consult the ERP Release and Information Notes.

Moreover, you need SAP ITS 6.20 (see below), which is usually installed on a separate server.

46 February 2005




Note that you need SAP ITS 6.20 only if you would like to run ITS-based ESS services.These services are not supported with the internal ITS (part of SAP Web AS 6.40).Moreover, note that some country-specific processes are not available on Web Dynproin mySAP ERP 2004. For additional information, see SAP Service Marketplace at

ser vi ce. sap. com/ not es SAP Note 758035.

Note that you may install and operate XSS (or any of its subcomponents) along with SAP EnterprisePortal on a common server, on the same J2EE instance, or on separate servers. Your specificrequirements should ultimately determine the most suitable option. If you decide to install XSS andSAP Enterprise Portal on the same J2EE instance, you should consider using SAP NetWeaver RapidInstaller, which is an installation and configuration wizard documented in Section 6.5. Furthermore,

consult SAP Service Marketplace at ser vi ce. sap. com/ nw- r i .

The ESS processes do not require an SAP BW system.

7.3.2.3 Valid Combinations and Source Releases

Although based on different technologies, it is possible to deploy ITS-based ESS services togetherwith Web Dynpro-based ESS services at the same time.

However, be advised that in the medium term you should plan to replace the ITS-based services withWeb Dynpro-based services.

The permissible combinations for ESS depend on a number of factors, for example, the R/3 releaseconcerned, and the Enterprise Portal or ESS menu that is used. The following table summarizes thecomponents and how they are combined.

ESS Release R/3 Release Portal / Menu toaccess ESS

Business Package fromService Marketplace

ESS 4.5 R/3 4.5 including ITS ESS Menu (PZM1) Not available

ESS 4.6B R/3 4.6B includingITS

Enterprise Portal 5.0 orESS Menu (PZM2)

Business Package forESS (4.6B)

ESS 4.6C R/3 4.6C includingITS

Enterprise Portal 5.0,Enterprise Portal 6.0 orESS Menu (PZM3)

Business Package forESS (4.6C / Enterprise)

ESS Enterprise

ESS 4.6C/ESS Enterprise

R/3 Enterpriseincluding ITS

R/3 4.6C includingITS or R/3 Enterpriseincluding ITS 6.20

Enterprise Portal 5.0,Enterprise Portal 6.0(SAP Web AS 6.20) orESS Menu (PZM3)

Enterprise Portal 6.0(SAP Web AS 6.20) orESS Menu (PZM3)

Business Package forESS (4.6C / Enterprise)

Business Package* forESS (4.6C / Enterprise)

ESS mySAP ERP2004

SAP ECC 5.0 (withITS 6.20, if ITS-basedservices are used)

Enterprise Portal 6.0(on SAP Web AS 6.40)

Business Package forESS 60.1

*) Restricted release

February 2005 47









8 Analytics

8 Analytics

8.1 Target System LandscapeFigure 4 shows an example of a full-fledged system landscape for the key functional area Analytics ofmySAP ERP 2004. Depending on your initial situation and requirements, this could be a targetlandscape for your upgrade.

SAP ECC

Web AS ABAP 6.40

RDBMS

SAP ECC 5.0

ECC System

SAP BW

NW BW System

RDBMS

Web AS ABAP 6.40

Search &

Classification

TREX 6.1

Web Browser

BI CONT 3.5.2

FINBASIS 300

SEM-BW 400

RDBMS

EP 6.0 Server


BP for BUA

Portal Platform 6.0

Web AS Java 6.40

Frontend

Several possibilities are available to distribute the components, so this diagram provides just one

example. The distribution depends on many factors, such as sizing, security, available hardware, andso on. In practice, any distribution of components among hosts is possible – from a minimal systemlandscape to a maximum distributed landscape, where every component runs on its own host, or evenon multiple hosts. Note that you require a dedicated system for SAP Solution Manager.

For more information about the mandatory or optional character of the components for Analytics,

consult the ERP Master Guide in SAP Service Marketplace at ser vi ce. sap. com/ er p- i nst

mySAP ERP 2004.

Analytics Strategic EnterpriseManagement

Financial Analytics Operations Analytics Workforce Analytics

Fig. 4: Sample System Landscape for Analytics

February 2005 49





8 Analytics






Step Action




1 Upgrade SAP Business InformationWarehouse with the add-ons FINBASISand SEM-BW.


The upgrade is described in SAP Note724419.

FINBASIS is technical requirement for

SEM-BW.

2 Perform a delta upgrade of BI Content toRelease 3.5.2 or 3.5.3

Refer to SAP Note 717812 or 774933(BI_CONT 3.5.3)

3 Upgrade your R/3 system to SAP ECC 5.0

[ECC 5.0 Upgrade Guide: <OperatingSystem> + SAP Note 689574]

• Mandatory if SEM-BCS (R/3-based) or EC-CS is used for Legaland/or Management Consolidation.

• R/3 PI 2004.1 is included in theupgrade. No PI supplement CD isrequired; see SAP Note 700779

and subsequent step.

• During the upgrade (BIND_PATCHphase), you should bind all ABAPsupport packages that areavailable for SAP ECC 5.0 and R/3PI.

4 Optional: Upgrade SAP R/3 Plug-in to PI2004.1

For more information, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736

Only relevant if SEM-BCS (R/3-based)or EC-CS with BW reporting is usedand R/3 is not upgraded to SAP ECC5.0.

50 February 2005





8 Analytics

(Release restrictions R/3 Plug-in 2004.1).

See also the information in SAP ServiceMarketplace at servi ce. sap. com/ r3-pl ug- i n.

5 Optional: Install (or migrate to) SAPEnterprise Portal 6.0 (based on SAP Web AS 6.40)

Optional: Install Content Management andCollaboration 6.0




For installation information, consultservi ce. sap. com/ nw04i nst al l at

i on

Installation

SAP EP. Also, refer to Section 6.5.

6 Optional: Import Business Package forBusiness Unit Analyst (mySAP ERP2004)


BPs can be downloaded from SAPService Marketplace atser vi ce. sap. com/ swdc.

7 Optional: Install Search & Classification(TREX) 6.1


[ser vi ce. sap. com/ nw04i nst al l ati on Cross NW]

8.3 Sample Upgrade ScenariosThis section discusses sample upgrade scenarios for Strategy Management and Legal ManagementConsolidation.

8.3.1 Strategy Management

8.3.1.1 Overview

The Strategy Management process is used to analyze the current strategy of your business. You use

the key figures from SAP Strategic Enterprise Management – Corporate Performance Management(SEM-CPM), which have been processed as a Balanced Scorecard. You can develop alternativestrategies and compare them with your current strategy. If needed, you can adapt your businessstrategy as well as the target values for key business figures to optimize business performance. Youcan communicate these adapted goals and figures to all organizational units throughout the company,using top-down distribution. You can also monitor the accomplishment of your business strategy with awide range of check tools offered by SEM-CPM.

February 2005 51





















8 Analytics

8.3.1.2 Technical System Landcape

The following table shows an example of a minimal system landscape for Strategy Management.


1 SEM-BW System • SEM-BW 400

• FINBASIS 300

• BI_CONT 352

• SAP Web AS ABAP 6.40(including SAP BW 3.5)

SAP BW 3.5 and PI Basis 2004.1 are part of the SAP NetWeaver ABAP Stack; in other words, thesecomponents are included in the upgrade or installation. You also need SAP Internet Graphics Services6.40 for this process. This component is included in SAP Web AS ABAP 6.40. Note that no SAP Web AS Java is required.

SEM-BW and FINBASIS demand a minimum SP-stack of 07; consult the SAP Release andInformation Note 760874. Furthermore, for SAP Web AS 6.40 (ABAP), NW stack 11 is required as aminimum. For more information on SAP’s Stack Strategy, see SAP Service Marketplace atser vi ce. sap. com/ sp- st acks.

For information that specifically addresses the installation of SEM 4.0, review SAP Note 724418.

8.3.1.3 Valid Combinations

If you combine your SEM-BW system with R/3, you do not necessarily need to upgrade R/3 to SAPECC 5.0, as long as it operates at Release 4.5B – 4.7. As far as your NW BW system is concerned, noother component combinations are possible, with one exception; Release 3.5.3 of BI Content may alsobe used.

8.3.1.4 Source Releases

The following source releases are supported:

• SAP SEM 3.0A/SAP_BW 2.1C

• SAP SEM 3.0B/SAP_BW 2.1C

• SAP SEM 3.1B/SAP_BW 3.0B

• SAP SEM 3.2/SAP_BW 3.10


For more information on SEM upgrade, see SAP Note 724419.

52 February 2005





8 Analytics

8.3.2 Legal Management Consolidation8.3.2.1 Overview

This process enables you to fulfill statutory requirements in accordance with multiple GAAPs and toprovide up-to-date information to management. It includes comprehensive accounting functionsoperate on multi-dimensional data structures. Organizational units (for example, companies, businessareas, and profit centers) are customer-definable. Legal Management Consolidation provides supportfor matrix organizations. Moreover, the entire process, from data collection through consolidation, canbe monitored and controlled graphically.

8.3.2.2 Technical System Landcape

The following tables show minimal system setups for:

Legal and Management Consolidation with SEM-BCS (BW-based):


1 NW BW System • SEM-BW 400

• FINBASIS 300

• BI_CONT 352 or 353


Legal and Management Consolidation with SEM-BCS (R/3-based):




2 NW BW System • SEM-BW 400

• FINBASIS 300

• BI_CONT 352 or 353


Legal and Management Consolidation with EC-CS:




SEM-BW and FINBASIS demand a minimum SP-stack of 07 (consult the SAP Release andInformation Note 760874.) Furthermore, for SAP Web AS 6.40 (ABAP), NW stack 11 is required as a

February 2005 53



8 Analytics

minimum. For more information on SAP’s Stack Strategy, see SAP Service Marketplace at

ser vi ce. sap. com/ sp- st acks.


As far as your NW BW system is concerned, no other component combinations are possible, with oneexception; Release 3.5.3 of BI Content may also be used.



• SAP SEM 3.0A/SAP_BW 2.1C

• SAP SEM 3.0B/SAP_BW 2.1C

• SAP SEM 3.1B/SAP_BW 3.0B



For more information on the SAP SEM upgrade, see SAP Note 724419.

54 February 2005





9 Financials

9 Financials

9.1 Target System LandscapeFigure 5 shows an example of a full-fledged system landscape for the key functional area Financials ofmySAP ERP 2004. Depending on your initial situation and requirements, this could be a targetlandscape for your upgrade.

SAP XI

Web AS ABAP + Java 6.40

XI Components

NW XI System

Web Browser

SAP BW

NW BW System

Web AS ABAP 6.40

BI_CONT 3.5.2

FINBASIS 300

SEM-BW 400

SAP BusinessConnector

SAP BC 4.7

SAP ECC

Web AS ABAP 6.40

SAP ECC 5.0

ECC System

RDBMS

EP 6.0 Server

BP for Credit

Management

BP for Payer Direct

Portal Platform 6.0

Web AS Java 6.40

J2EE Server

RDBMS


Web AS Java 6.40

RDBMS

RDBMS

XI Content for

FINBASIS and PI

RDBMS


example. The distribution depends on many factors, such as sizing, security, available hardware, andso on. In practice, any distribution of components among hosts is possible – from a minimal systemlandscape to a maximum distributed landscape, where every component runs on its own host, or evenon multiple hosts. Note that you will require a dedicated system for SAP Solution Manager.

For more information about the mandatory or optional character of the components for Financials,

consult the ERP Master Guide in SAP Service Marketplace at ser vi ce. sap. com/ er p- i nst

mySAP ERP 2004.

CorporateGovernance

Financial SupplyChain Management

Financial Management Accounting

Financials Accounting

Fig. 5: Sample System Landscape for Financials

February 2005 55





9 Financials

9.2 Upgrade Sequence

The following table describes the suggested sequence of upgrade or installation steps that you shouldperform to obtain a full-fledged system landscape.





Step Action




1 Upgrade your R/3 to SAP ECC 5.0


• R/3 PI 2004.1 is included in theupgrade.

• During the upgrade (BIND_PATCHphase), you should bind all the ABAP Support Packages that areavailable for SAP ECC 5.0 and R/3PI.

2 Upgrade R/3 Plug-in to PI 2004.1. If youcannot upgrade your IS Add-on system, thisactivity is required. This step only applies tothe FI-CA process variant.

See SAP Notes 704564, 704565,704566. Also, refer to SAP Note181255, the general SAP Note for R/3PI.

If you decide not to upgrade your R/3 system to SAP ECC 5.0, then you mustupgrade R/3 PI to PI 2004.1.

3 Install SAP Web AS Java 6.40 • SAP Web AS Java includes SAP

J2EE Engine 6.40, SAP JavaConnector (JRFC) and SAP JavaTech Services.

• As described in section 9.3.1.2.1, ifyou only plan to deploy FSCM BillerDirect 3.0, then you may also usethe SAP Web AS (Java) of the SAPECC system.

4 Install FSCM Biller Direct 3.0 See SAP Notes 713540 and 713534and the sample scenarios describedbelow.

56 February 2005





9 Financials

5 Optional: Install SAP Business Connector4.7, Core Fix 3

This step only applies to the FI-AR processvariant of Electronic Bill Presentment andPayment.

See SAP Note 571530.

6 Optional: install (or migrate to) SAPEnterprise Portal 6.0 (based on SAP Web AS 6.40).



For installation information, review

servi ce. sap. com/ nw04i nst al l ati on Installation SAP EP.

Also, refer to Section 6.5.

7 Upgrade SAP Business InformationWarehouse with the add-ons FINBASISand SEM-BW.

[Component Upgrade Guide SAP Business

Information Warehouse 3.5: <OperatingSystem>]

The upgrade is described in SAP Note724419.

8 Perform a delta upgrade of BI Content to

Release 3.5.2 or 3.5.3.

Refer to SAP Note 717812 or 774933

(BI_CONT 3.5.3).9 Install SAP Exchange Infrastructure (XI)

3.0.

[Component Installation Guide SAPExchange Infrastructure: <OperatingSystem>]

Using SAP XI is mandatory for CreditManagement. For all other processes inthis key functional area, it is optional.SAP XI is used for outbound XML-based messaging and / or to establish aconnection to non-SAP planning orexecution systems.

With the role of an Integration Server,SAP Exchange Infrastructure normallyrequires a dedicated SAP Web Application Server. For additional

information, consult Section 6.1.This system must be on Unicode.

Seeservi ce. sap. com/ nw04i nst al l ati on SAP XI.

10 Install XI Content for FINBASIS 300 andPI_2004_1_500

Required for Credit Management.

February 2005 57













9 Financials

9.3 Sample Upgrade ScenarioThis section deals with the sample process Electronic Bill Presentment and Payment, formerly knownas Bill to Cash.

If you desire a minimal setup, you may run your Electronic Bill Presentment and Payment processvariant in the corresponding system landscape described below. Of course, you can enjoy the benefitof greater functionality in the Financials key functional area of mySAP ERP 2004. On the other hand,this additional functionality would require a larger system infrastructure with more components asdescribed in the ERP Solution Master Guide, located in SAP Service Marketplace at

ser vi ce. sap. com/ er p- i nst .

9.3.1 Electronic Bi ll Presentment & Payment (EBPP)

9.3.1.1 Overview

This process enables your enterprise to present invoices and account information to customers orsuppliers. Electronic Bill Presentment & Payment also enables you to provide self-service functions viathe Internet.


Depending on the technical components to be used, you may implement one of the following twoprocess variants:

• EBPP with Accounts Receivable Accounting (FI-AR)

• EBPP with Contract Accounts Receivable and Payable (FI-CA)

The EBPP process variant you run on your source system infrastructure determines how the targetsystem landscape should be set up. Whereas the process variant FI-AR requires no additional add-on,FI-CA typically needs the FI-CAX Add-on or an Industry Solution Add-on belonging to one of thefollowing solutions: mySAP Utilities, mySAP Telecommunications, mySAP Public Sector, mySAPMedia or mySAP Insurance.

9.3.1.2.1 EBPP with Accounts Receivable Accounting (FI-AR)

The following table shows an example of a minimal system landscape for EBPP with FI-AR.


1 SAP ECC System • SAP ECC 5.0 (incl. PI 2004.1)

• FSCM Biller Direct 3.0 (on SAPWeb AS Java)

• SAP Web AS ABAP + Java 6.40

FSCM Biller Direct 3.0 may run on the SAP ECC 5.0 host. If you do not upgrade your R/3 system toSAP ECC 5.0, you would need a separate J2EE Server, since SAP Web AS Java 6.40 is aprerequisite for FSCM Biller Direct 3.0.

58 February 2005





9 Financials

You may also install SAP Business Connector (4.7, Core Fix 3 at least) on this server. If you choose toinstall SAP Business Connector, note that it features platform restrictions, as described in SAP Note

571530.

If you use FI AP/AR (Accounts Payable; Accounts Receivable Accounting) functionality and youoperate on R/3 release 4.64 or 4.7, an upgrade to Biller Direct 3.0 is possible and makes sense, evenif you cannot upgrade your R/3 backend to SAP ECC 5.0. An important prerequisite, however, must befulfilled; you must upgrade the R/3 plug-in to PI 2004_1. The Plug-in version 2004.1 contains the FI AP/AR backend functionality that Biller Direct 3.0 requires to work properly. For additional information,see SAP Note 713534.

FSCM Biller Direct does not have persistent data. The database system depicted in the figure of thefull-fledged system landscape is required for the SAP J2EE installation.

If you would like to install SAP Enterprise Portal 6.0 (on SAP Web AS Java 6.40), plan to set up aseparate server for it.

9.3.1.2.2 EBPP with Contract Accounts Receivable and Payable (FI-CA)

The following table shows an example of a minimal system landscape for EBPP with FI-CA.


1 IS or FI-CA BackendSystem

• IS / FI-CA Add-on 4.64, 4.71,4.72

• PI 2004.1

• SAP BASIS, ABA , APPL 4.6C /SAP Web AS 6.20 (for 4.7x)

2 J2EE Server • FSCM Biller Direct 3.0


Although several IS Add-ons have been integrated into SAP ECC 5.0 (or R/3 releases at or below 4.7),the functionality that is required for EBPP has not yet been integrated into the core component, nor dothe required IS Add-ons support the upgrade to SAP ECC 5.0. In cases where you operate an IS Add-on system in your landscape, it will remain in the landscape as it is (for example, on release 4.64 or4.71-2).

One optional component in this minimum system landscape is SAP Enterprise Portal 6.0, which wouldrequire a separate server. BP for Payer Direct and BP for Credit Management are the Business

Packages available for Financial Supply Chain Management.If you choose to obtain more functionality by implementing other financial processes, refer to the ERPSolution Master Guide. Note that not all of the additional software components for the Financials keyfunctional area are upgrade-relevant. After planning your scenarios and the corresponding systemlandscape, you should ascertain whether any upgrade-relevant steps exist for the components youplan to use.

February 2005 59



9 Financials


Aside from the main combination SAP ECC 5.0 with FSCM Biller Direct 3.0, the following combinationsare valid.

FI-CA Variant (see SAP Note 713536)

Component Releases With

• IS-M = Media

• IS-T = Telecommuncations

• IS-U / CCS = Customer Care & Services

• INSURANCE = SAP Insurance

• FI-CAX = Extended FI-CA

• FI-CA = Financial Contract AccountsReceivable and Payable

• IS-PS-CA = IS Public Sector Contract Accounting

4.72

4.71

4.64


FI-AR Variant (see SAP Note 713534)

Component Releases With

R/3 4.6C

4.7


For more detailed information (for example, minimum required SP-levels), refer to the mentioned SAPNotes.


FSCM Biller Direct: since Java component FSCM Biller Direct has no persistence layer, no upgrade isrequired. FSCM Biller Direct 3.0 is a new installation. It requires SAP Web AS Java 6.40. For moreinstallation-specific information, refer to SAP Note 713540 and the installation documentation in

ser vi ce. sap. com/ er p- i nst mySAP ERP 2004 ERP Java Components.

FI-CA variant: no upgrades to SAP ECC 5.0 are supported for the aforementioned add-ons (IS and FI-

CA.)FI-AR variant: upgrades from 4.6C and 4.7 to SAP ECC 5.0 (with PI 2004.1) are available.

60 February 2005





10 Human Capital Management


10.1 Target System LandscapeFigure 6 shows an example of a full-fledged system landscape for the key functional area HumanCapital Management of mySAP ERP 2004. Depending on your initial situation and requirements, thiscould be a target landscape for your upgrade.

Frontend (PC)

Author ingEnvironment

LSOAE 300

Search &

Classification

TREX 6.1

SAP BW

NW BW System

Web AS ABAP 6.40

BI CONT 3.5.2

RDBMS

Web Browser

SAP ECC

Web AS ABAP 6.40

SAP ECC 5.0

ERECRUIT 300

LSOFE 300

ECC System

RDBMS

J2EE Server

XSS 500

LSOCP 300

Content Player

Web AS Java 6.40

EP 6.0 Server

Portal Platform 6.0

BP for MSS

BP for ESS

Web AS Java 6.40

Content Management &

Collaboration 6.0

RDBMS

BP for Learning

Solution

RDBMS

NW MI System

Web AS ABAP

+ Java 6.40

Laptop

MTS + MTR 1.6

Mobile Client 2.5

JDK

Frontend (PC)

Learner Environment

Web Browser

LSOOP 300

Offline Player


example. The distribution depends on many factors, such as sizing, security, available hardware, andso on. In practice, any distribution of components among hosts is possible – from a minimal systemlandscape to a maximum distributed landscape, where every component runs on its own host, or evenon multiple hosts. Note that you will require a dedicated system for SAP Solution Manager.

For more information about the mandatory or optional character of the components for Human CapitalManagement, consult the ERP Master Guide in SAP Service Marketplace atser vi ce. sap. com/ er p- i nst mySAP ERP 2004.

Talent Management Workforce Process Management Workforce DeploymentHuman CapitalManagement

Fig. 6: Sample System Landscape for Human Capital Management

February 2005 61












Step Action






• R/3 PI 2004.1 is included in theupgrade.


• ERECRUIT 300 and LSOFE 300: Ifthese add-ons were installed in theR/3 system, the standard upgradeprocess prompts you for anadditional CD or upgrade packagefor ERECRUIT and LSOFE. Formore information, see SAP Note717803 (ERECRUIT) and SAPNote 718625 (LSOFE)

• For information on the standaloneor integrated operation modes ofERECRUIT and LSOFE, reviewthe sections that discuss thecorresponding system landscape.

• LSO: from SAP ECC 5.0 forward,the LSO TM Add-on (backend part)is integral part of the system.

• LSO: SAP Note 748338 must beapplied before the upgrade.

[You can find the upgrade

62 February 2005






documentation in SAP ServiceMarketplace at

ser vi ce. sap. com/ er p- i nst mySAP ERP 2004 SAP ECC 5.0]

2 Install (or migrate to) SAP EnterprisePortal 6.0 (based on SAP Web AS 6.40).

[Component Installation Guide SAPEnterprise Portal 6.0 on SAP Web AS6.40]





Include Content Management &Collaboration in the installation.

3 Optional: Import Business Packages forMSS and ESS (optional: BP for LearningSolution; see Section 10.3.1.2)


For information on the ESS and MSSBusiness Packages, also see Section 7.

BPs can be downloaded from PortalContent Portfolio atht t p: / / www. sdn. sap. com/ NW

Business Content Portal ContentPortfolio, or from SAP ServiceMarketplace at


4 If you used TREX 6.0, migrate to version6.1. Otherwise install TREX 6.1.

[Component Migration Guide – Search andClassification (TREX)]

or

[Component Installation Guide – Searchand Classification (TREX)]

• The use of TREX is optional forLSO.

• E-Recruiting: For more informationon supported TREX versions for E-Recruiting, consult SAP Note568853.

[You can find the documentationin SAP Service Marketplace atser vi ce. sap. com/ nw04upgrade

Cross NW,

or (for a new installation):

servi ce. sap. com/ nw04i nst al l ati on Cross NW]

5 Activate TREX Python extensions. For more information, see SAP Note700771.

6 Install SAP Web AS Java 6.40. Apply the latest Support Packages.

• For source release 6.20, youmust first de-install the 6.20version. Follow the instructionsprovided for the target release

by the SAPi nst tool.

To install the new J2EE Engine

February 2005 63























6.40, see the documentationInstallation Guide – SAP Web

Application Server Java on<Platform>: <Database>.

For information on the overallmigration procedure, review theonline documentation underSAP NetWeaver ApplicationPlatform J2EE Technologyin SAP Web Application Server Migration Manual.

• For source release 6.30, youcan directly import Support

Package 04. For Information onimporting Support Package 04,see the documentation SAPWeb Application ServerSupport Package Guide630SP2 to 640SP4. Forinformation on importing furtherSupport Packages, consult thedocumentation SupportPackage Stack Guide – SAPNetWeaver ́ 04: Stack <xx>.

[You can find the documentationin SAP Service Marketplace atservi ce. sap. com/ nw04i nst al l ati on Installation (Source Release

6.20)

or

servi ce. sap. com/ nw04i nst al l ati on SAP Components SAP Web

Application Server Release 6.30 andservi ce. sap. com/ nw04i nst al l at

i on Operations (Source Release

6.30)]

For information on new installations,

review:



7 Install Java component LSOCP 300.

[Java Components for mySAP ERP 2004 –Course Content Player (LSOCP) 300]

[Review the documentation in SAPService Marketplace atser vi ce. sap. com/ er p- i nst

mySAP ERP mySAP ERP 2004 SAP Learning Solution 3.0]

64 February 2005






















8 Install XSS 500

[Installation Guide – Java Components onmySAP ERP 2004]

• XSS consists of the subcomponentsMSS 100, ESS 100 and PCUI_GP100. You may either install XSS inits entirety (using the ERP Javainstaller, which is the default mode)or deploy each of thesesubcomponents individually (withSDM).



• XSS is required only if you wouldlike to use the Business PackagesMSS 60.1 (mySAP ERP 2004) and /

or ESS 60.1 (mySAP ERP 2004),both of which are Web Dynpro-based

Depending on the process(es) youwould like to implement, considerusing the SAP NetWeaver RapidInstaller , which is an installationand configuration wizarddocumented in Section 6.5. Usingthis tool you can install severalcomponents at once, including SAPEnterprise Portal, BusinessPackages, XSS, and so on. Formore information on SAP NW RapidInstaller, reviewser vi ce. sap. com/ nw- r i .

9 Optional: If you are using SAP BusinessInformation Warehouse: Upgrade to SAPBusiness Information Warehouse 3.5 withBI_CONT Add-on.

[Component Upgrade Guide – SAPBusiness Information Warehouse 3.5:<Operating System> ]

The required Basis plug-in (PI_Basis) isincluded in the upgrade.

Enterprise Portal plug-in (WP-PI) isincluded in the Basis plug-in as of SAPWeb AS 6.40. For more information,refer to SAP Note 789554.

You must update the BI_CONT Add-onduring the SAP BW server upgrade.

The upgrade process prompts you for

February 2005 65






the required CD at the appropriate pointin time. This prompt also appears if the

add-on is not installed in your system,which is the case if your source releaseis 3.0B or below. For more informationon the upgrade to BI_CONT 3.5.2, referto SAP Note 717812 and 774933(BI_CONT 3.5.3).

After the upgrade is complete, thesystem will not display the SAP Easy Access Menu automatically. For moreinformation on manually maintaining theSAP Easy Access Menu for SAP BW,consult SAP Note 725184.

You can find the relevantdocumentation in SAP ServiceMarketplace atser vi ce. sap. com/ nw04upgrade

SAP NetWeaver Release 04 Upgrade SAP BW

and

servi ce. sap. com/ bw SAP BW

3.5 BI Content 3.5.2 (or 3.5.3) – Add-On

10 Install add-on LSOAE 300 Authoring

Environment on each computer used forauthoring.

[Installation and Upgrade Guide – AuthoringEnvironment (LSOAE) 300]

• Before you install the new Add-on

version, de-install Add-on versionsLSOAE 100 or 200 (AuthoringEnvironment) on each computerused for authoring.

You can find the relevantdocumentation in SAP ServiceMarketplace atser vi ce. sap. com/ er p- i nst

mySAP ERP 2004 SAP LearningSolution 3.0

• Java Development Kit (JDK) isrequired for the AuthoringEnvironment. Because SAP doesnot ship this component, you mustdownload and install it separately.To determine the recommendedJDK versions for your platform andlearn how to obtain them, see SAPNote 709140.

11 Upgrade LSOOP 300 (Offline Player.)

[Installation and Upgrade Guide – OfflinePlayer (LSO-OP) 300]

For more information on upgradingOffline Player, see the ImplementationGuide (IMG) of the SAP LearningSolution under SAP Learning Solution Learning Portal Offline Player .

66 February 2005


http://service.sap.com/bw








You can find further documentation inSAP Service Marketplace atser vi ce. sap. com/ er p- i nst

mySAP ERP 2004 SAP LearningSolution 3.0

12 Optional: Install SAP Web AS 6.40 on aseparate server

If you plan to run mobile processes, yourequire an SAP NetWeaver MobileInfrastructure system (MiddlewareServer) consisting of SAP Web AS(ABAP and Java) 6.40. For informationon the possible installation modes ofSAP MI, refer to Section 6.1.

Find the relevant installation information

atservi ce. sap. com/ nw04i nst al l ati on Installation SAP Web AS


13 Optional: Install Mobile Time & Travelcomponents (MTS & MTR 1.6) on themobile devices

See ser vi ce. sap. com/ er p- i nst

mySAP ERP 2004 MobileInfrastructure Components

10.3 Sample Upgrade ScenariosIn the following section, Enterprise Learning and E-Recruiting are discussed in detail.

10.3.1 Enterprise Learning (SAP Learning Solution)

10.3.1.1 Overview

SAP Learning Solution provides a comprehensive enterprise learning platform capable of managingand integrating business and learning processes and supporting both e-learning and classroomtraining, as well as synchronous and asynchronous collaboration. It is fully integrated with mySAPERP, and includes content authoring, content management, and learning management capabilities, aswell as a learning portal.

For more information on SAP Learning Solution, see SAP Service Marketplace at

ser vi ce. sap. com/ l earni ngsol ut i on.

Installation- and upgrade-related information can be found at ser vi ce. sap. com/ er p- i nst

mySAP ERP 2004 SAP Learning Solution 3.0.

10.3.1.2 Components of Enterprise Learning (Learning Solution)

SAP Learning Solution consists of the following components:

• LSOAE (Authors Environment)

• LSOCP (Content Player)

February 2005 67





http://service.sap.com/learningsolution











• LSOFE (Learners Front end)

• LSOOP (Offline Player)

• LSO (Backend)*

*) As of mySAP ERP 2004, this functionality is s named Learning Solution Training Management,or LSOTM.

The backend component LSO was a separate add-on required for the Learning Solution Releases 1.0and 2.0. The functionality originally contained in this add-on is now integrated into SAP ECC, so that asupplemental CD is no longer required. For additional information, consult SAP Notes 503468 and700778.

LSOFE remains an add-on that can be installed on the SAP ECC system or on a separate Web Application Server as a standalone installation. Refer to the following section, as well as SAP Notes529063 and 503907.

Note that a Business Package for Learning Solution 2.0 (50.2) is available. This component is optionalfor LSO 3.0 and can be used with SAP Enterprise Portal 6.0 (NW ’04). Your system will require this BPif you wish to establish access to the Learning Portal of LSO 3.0 through SAP Enterprise Portal.


For the setup of the LSO system landscape you should take the following aspects into account:

• Security: Do you have any security concerns about giving all learners access to your SAP ECCsystem? If yes, you should run LSOFE on a separate SAP Web Application Server. If you arealready using this option, upgrade your SAP Web AS to Release 6.40.

• Total Cost of Ownership (TCO): Installing LSOFE on SAP ECC 5.0 reduces TCO because you

need fewer servers. No additional administration is necessary. If you are using a separate HRsystem connected to your LSO system, this HR system does not require an upgrade to ECC 5.0.

If you use SAP Learning Solution separately from your HR system – for expample,because of different release versions – and you would like to upgrade both systems tomySAP ERP 2004, be advised that you cannot merge these two systems into one.You must continue to run both systems separately.

The following table shows an example of a minimal system landscape for LSO.


1 Backend System • LSOFE 300

• SAP ECC 5.0 (including theLSOTM backend functionality)


2 J2EE Server • LSOCP 300


3 Content ManagementSystem

• For example: KnowledgeManagement of SAP EnterprisePortal 6.0

68 February 2005







LSO Add-on

SAP Note 503468 documents the supported source releases for LSO (backend). The following sourcereleases are valid:

R/3 Release LSO Add-on Release

4.6C LSO 100

4.7x110 LSO 200

4.7x200 LSO 200

Consult SAP Note 503468 for information on the minimum Support Package levels and other

requirements or prerequisites.

As of SAP ERP Central Component 5.0, the functions of the LSO Add-on are contained in SAP ECC.The upgrade to SAP ECC 5.0 or above can be carried out for all LSO source releases directly. Noadditional LSO CD is required.

It is imperative that you refer to SAP Note 748338 before you carry out the LSOupgrade.

LSOFE Add-on

SAP Note 503907 indicates the following valid source releases for LSOFE (frontend).

SAP Web AS Release LSOFE Add-on Release

6.20 LSOFE 100

6.20 LSOFE 200

LSOCP (Content Player):

If you have already implemented a previous version of LSO Content Player (100 or 200), werecommend that you de-install the previous J2EE version and install SAP Web AS Java 6.40.Subsequently, install Content Player 300 with SAPinst and carry out the configuration steps asdescribed in the installation documentation.

10.3.2 E-Recruit ing

10.3.2.1 Overview

E-Recruiting is a comprehensive recruitment process that supports talent relationship managementand applicant tracking for your company. It offers advanced support for planning, attracting, sourcing,qualifying, closing, and retaining talent.

You can find a detailed overview of the process scope in SAP Solution Manager, along with thefunctions and benefits.

70 February 2005





Depending on your requirements, you will choose either to install ERECRUIT as an add-on for yourSAP ECC 5.0 system or as an add-on for a dedicated SAP Web AS ABAP Server 6.40 (standaloneinstallation). The standalone installation can be connected to HR and NW BW systems, provided thatyou have implemented BI content at release 3.5.2 or 3.5.3. Before you begin to set up your E-Recruiting system landscape, you should consider the following issues:

• Security: do you have security concerns about connecting your SAP ECC system to the Internet?If so, you should run E-Recruiting on a separate server.

• Total Cost of Ownership (TCO): Installing ERECRUIT on SAP ECC 5.0 reduces TCO becauseyou need fewer servers. Neither ALE (for example, distribution of organizational data into the E-Recruiting system) nor additional administration is necessary.

• Upgrading an existing system: if you have an operative E-Recruiting system and want to upgrade

to SAP NetWeaver ’04 with E-Recruiting 3.0, your choice will be to keep E-Recruiting in astandalone operation mode. See SAP Note 717803.

The following table shows an example of a minimal system landscape for Recruiting. In this example,the ERECRUIT add-on is installed on its own server.


1 E-Recruiting System • ERECRUIT 300


2 TREX Server•

Search & Classification (TREX)6.1 (SP3 or above)

You must update the ERECRUIT add-on while you upgrade the server component. For moreinformation on updating add-ons during the upgrade, see the SAP Web Application Server upgradedocumentation and the SAP Notes mentioned in the upgrade sequence.

You must bind at least SAP Basis 6.40 Support Package 03 in the upgrade.

After the upgrade, be certain to review SAP Note 739929. It contains information on all post-upgradeactivities to perform before you can use E-Recruiting productively.

If you already have a TREX 6.0 installation (with at least SP1), a normal upgrade to version 6.1 is not

possible, since architecture, configuration files and index structures changed considerably in TREX6.1. You must therefore perform a migration instead. You will find the corresponding Migration Guide in

SAP Service Marketplace at ser vi ce. sap. com/ nw04upgrade Cross NW Component

Migration Guide – Search and Classification (TREX).

For a productive system – and sometimes for development systems, depending onyour requirements – SAP recommends that you install Search & Classification on aserver of its own.

February 2005 71








Internal Users

(Browser - SSOoptional)

System

Administrator(SAP GUI)

SMTP(Mail)

Internet

HTTP(S)

External Users(Web Browser)

SAP HR / SAP

ECC / NW BWRFCRFC (ALE)

TREX

E-Recruiting

DMZ Intranet

ApplicationGateway /

Proxy

Gateway

SMTP(Mail)

RDBMS

HTTP(S)

Firewall

Fig. 7: Basic System Architecture of E-Recruiting (standalone mode)

In the presentation layer, the following techniques are used: Business Server Pages (BSPs), HTML,HTMLB and JavaScript. In terms of business logic, E-Recruiting relies upon ABAP/OO, BusinessPartner and Knowledge Provider (KPRO).


Aside from the E-Recruiting / TREX combination specified here, no other combinations are supported.For more details on the combination of SAP E-Recruiting and Search & Classification (TREX), reviewSAP Note 568853.

If you would like to integrate your HR system with E-Recruiting, you will require a minimum HRRelease of 4.0B.


ERECRUIT: the upgrade path from SAP Web AS 6.20 with ERECRUIT 200 to SAP Web AS 6.40 withERECRUIT 300 is the only one supported. As stated in SAP Note 717803, when upgrading the E-Recruiting add-on system to SAP NetWeaver ’04 (SAP Web AS 6.40), the system recognizes that theERECRUIT add-on is installed and demands an additional CD or upgrade package for it. That bringsERECRUIT to the 300 version during the standard upgrade of SAP Web AS.

For more details on upgrading the E-Recruiting Add-on, refer to SAP Note 717803.

Search and Classification (TREX) 6.1: a migration guide is available, in the event that you would like tomigrate from TREX 6.0 (SP1) to TREX 6.1. You can find it in SAP Service Marketplace at

ser vi ce. sap. com/ nw04upgrade

Cross NW.

February 2005 73





11 Procurement and Logistics Execution


11.1 Target System LandcapeFigure 8 shows an example of a full-fledged system landscape for the key functional area Procurementand Logistics Execution of mySAP ERP 2004. Depending on your initial situation and requirements,this could be a target landscape for your upgrade.

SAP BW

NW BW System

RDBMS

Web AS ABAP 6.40

BI CONT 3.5.2

Frontend (PC)

SAP GUI

Adob e Reader 6.0.2

Mail Software

Web Browser

J2EE Server

SAP XSS 500

RDBMS

Adob e Docu ment

Services 1.0

Web AS Java 6.40

Search &

Classification

TREX 6.1

SAP XI

Web AS ABAP + J ava 6.40

RDBMS

XI Components

NW XI System

XI Content: SAP APPL,

SRM SERVER and CCM

Web AS Java 6.40

EP 6.0 Server

Portal Platform 6.0


BP for ESS

BP for MSS

RDBMS

BP for Supplier Order

Collaboration

BP for External

Procurement

SAP ECC

Web AS ABAP 6.40

SAP ECC 5.0

ECC System

RDBMS

SAP SRM

Web AS ABAP 6.40

RDBMS

SAP SRM Server 5.0

SRM System

SAP CCM 1.0

IPC 4.0


For more information about the mandatory or optional character of the components for Procurementand Logistics Execution, consult the ERP Master Guide in SAP Service Marketplace atser vi ce. sap. com/ er p- i nst mySAP ERP 2004.


Procurement SupplierCollaboration

Inventory & WarehouseManagement

Outbound andInbound Logistics

TransportationManagement

Fig. 8: Sample System Landscape for Procurement and Logistics Execution

74 February 2005











Step Action






• R/3 PI 2004.1 is included in theupgrade. No PI supplemental CD isrequired; see SAP Note 700779 and subsequent step.


To benefit from the newWeb Dynpro-based SelfServices functionality,you must upgrade theR/3 system to SAP ECC

5.0; see SAP Note752312.

2 Optional: Upgrade SAP R/3 Plug-in For more information, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736 (Release restrictions R/3 Plug-in 2004.1). Also consult SAP ServiceMarketplace at servi ce. sap. com/ r3-pl ug- i n.

This step is only required if your R/3system is not upgraded to SAP ECC5.0.

3 Install (or upgrade to) SRM Server 5.0

February 2005 75










[Component Installation Guide – SAP SRMServer 5.0: <Operating System>]

or[Component Upgrade Guide – SAP SRMServer 5.0: <Operating System>]

4 Install SAP Catalog ContentManagement (CCM) 1.0

For installation information, see SAP Note705060.

New installations should use SAP CCMinstead of Requisite BugsEye.

Upgrade customers already usingRequisite BugsEye can either installSAP Catalog Content Management andSearch and Classification (TREX) orcontinue to use Requisite BugsEye andSAP Integrated Catalog.

SAP CCM 1.0 can be installed on anysystem based on SAP Web AS ABAP6.40. In the above example it is installedon the SRM host.

5 Optional: Upgrade Requisite BugsEye andeMerge

[BugsEye and eMerge 4.0 Installation andUpgrade Guide]

If you already use Requisite BugsEyeand do not want to install SAPCatalog Content Management, youmust upgrade Requisite BugsEye to therequired version.

For detailed information on theavailability and release strategy ofRequisite BugsEye and eMerge, see

SAP Note 485884.

6 Optional: Upgrade SAP Integrated Catalog

To review the upgrade procedure, see SAPNote 620461.

If you plan to continue using RequisiteBugsEye, rather than installing SAPCatalog Content Management, thenupgrade SAP Integrated Catalog.

If you have installed SAP IntegratedCatalog 3.0 on SAP J2EE Engine 6.20you can migrate to SAP J2EE Engine6.40 and deploy SAP IntegratedCatalog on this SAP J2EE Engine.However, this step is optional; SAPIntegrated Catalog may also remain on

J2EE Engine 6.20. For moreinformation, see SAP Note 718953.

7 De-install your existing release of SAPInternet Pricing and Configurator andinstall version 4.0 (with at least SP6).

[Upgrade Guide SAP Internet Pricing andConfigurator 4.0]

IPC 4.0 can be installed for example onthe SRM host

76 February 2005






For a new installation, see:



11 Install XSS 500

[Installation Guide – Java Components onmySAP ERP 2004]

• XSS consists of the subcomponentsMSS 100, ESS 100 and PCUI_GP100. You may either install XSS inits entirety (using the ERP Javainstaller, which is the default mode)or deploy each of thesesubcomponents individually (withSDM).



• XSS is required only if you wouldlike to use the Business PackagesMSS 60.1 (mySAP ERP 2004) and /or ESS 60.1 (mySAP ERP 2004),both of which are Web Dynpro-based

Depending on the process(es) youwould like to implement, considerusing the SAP NetWeaver RapidInstaller , which is an installationand configuration wizarddocumented in Section 6.5. Using

this tool you can install severalcomponents at once, including SAPEnterprise Portal, BusinessPackages, XSS, and so on. Formore information, reviewser vi ce. sap. com/ nw- r i .

12 Optional: Install Adobe DocumentServices 1.0.

[Installation Guide – Adobe DocumentServices NW ’04 SR1]

13 Upgrade SAP Business Information

Warehouse to Release 3.5

PI BASIS 2004_1_640 is included in the

upgrade to SAP BW 3.5.

78 February 2005












14 Install BI_CONT 3.5.2 or 3.5.3 See SAP Note 717812 or 774933(BI_CONT 3.5.3).





For installation information, consult

servi ce. sap. com/ nw04i nst al l ati on Installation SAP EP.


16 Optional: Install Content Management andCollaboration 6.0 [Component Installation Guide SAPEnterprise Portal on SAP Web AS 6.40]

17 Import Business Packages for ExternalProcurement, Supplier Order Collaboration60.1, MSS and ESS (60.1)



18 Install (or migrate to) Search andClassif ication (TREX) 6.1.Use the following parameters during theinstallation:

• Perform the installation steps to set upan RFC connection.

• Automatic language recognition is notrequired. You can adopt the defaultsettings for document languagesduring the installation of Search andClassification (TREX).

• No Python extensions are required.


A migration is necessary if you alreadyhave TREX 6.0 (SP1) running in yoursystem landscape. The migrationprocedure does not change the existingsystem. You install the new TREXsystem parallel to the existing systemand carry out a migration of the existingindexes, queues, and configuration filesfor the new system.

[Component Migration Guide – Searchand Classification (TREX)]

Many of the upgrade or installation steps listed above can be carried out in parallel – for example, theupgrade or installation of SAP XI, SAP BW and SAP EP, Search & Classification and the SAP Web ASJava for the J2EE applications.

February 2005 79















11.3.1 Self-Service Procurement and Supplier OrderCollaboration

11.3.1.1 Overview

Self-Service Procurement and Supplier Order Collaboration processes are designed to help youreduce costs through controlled access to approved vendors and materials.

Supplier Order Collaboration provides the procurement organization with a service offering forsuppliers, to speed up the process of buying, shipping and invoicing through supplier collaboration. It

facilitates more effective business interaction by enabling the purchaser to be more responsive tocustomer needs. In addition, the Business Package for Supplier Order Collaboration promotes thelong-term establishment of supplier relationships.

By deploying Self-Service Procurement and Supplier Order Collaboration you will improve yourapproval process automation and enable the necessary documents to be exchanged while usingPortal technology. It will help you realize quick, significant and sustainable cost savings.

For more information, refer to the SRM Master Guide in SAP Service Marketplace at

ser vi ce. sap. com/ i nst gui des mySAP Business Suite Solutions mySAP SRM using SAP

SRM Server 5.0.


The following table shows an example of a minimal setup for Self-Service Procurement and SupplierOrder Collaboration.


1 ECC System • SAP ECC 5.0 (min. SP4)


2 SRM System • SRM Server 5.0 (min. SP3)

• SAP CCM 1.0 (min. SP3)


• IPC 4.0 (min. SP6)

3 NW BW System • BI Content 3.5.2 (min. SP4) or BIContent 3.5.3


80 February 2005






Server(cont.)

Host Name (example) Component(s)

4 NW XI System • XI Content [SAP_APPL 4.70,patch 16 (min.); SRM_SERVER5.0, SP3 (min.); CCM 1.0, SP3(min.)]

• SAP Web AS ABAP 6.40(including SAP XI 3.0)

5 Enterprise Portal Server • Business Package for SupplierOrder Collaboration 60.1, (min.SP2); and BP for External

Procurement 60.2, (min. SP2)

Basic System Architecture

Figure 9 shows the basic system architecture of Self-Service Procurement.

FI / CO

R/3 Plug-In

ECC System

MM

Firewall

RFC

NW BW 3.5

Application Gateway

HTTP(S)

SRM System

PI_BASIS*

SAP Enterprise Portal

BI_CONT 3.52

IGS* SAP CCM 1.0

ITS*

IPC

TREX

RFC

TCP / IP

*) Integrated in SAP Web AS 6.40

SRM SERVER 5.0

EBP

Application component

Technical component(mandatory)

Transfer protocol type

Technical component (optional)

Fig. 9: Basic System Architecture of Self-Service Procurement

The basic architecture of Supplier Order Collaboration is shown in the diagram below. It describes thedeployment option that is supported for the Self-Service Process. You implement the SAP EnterpriseBuyer system and one or more SAP ECC systems. The entire Material Management (MM) is mappedin the ECC system. Additionally, Accounting (FI) and Controlling (CO) tasks are processed in the ECCsystem.

Self-Service Procurement supports purchase order processing using in-house, sell-side or no catalog

at all.

February 2005 81




FI / CO

Firewall

RFC

NW BW 3.5

R/3 Plug-In

Application Gateway

HTTP(S)

SRM SERVER 5.0

ECC System

MMIDOC

PI_BASIS*

SAP Enterprise Portal 6.0

BI_CONT 3.52

IGS*

RFC

HTTP(S)TCP / IP

XML IDOC

XI Content

SRM Server NW XI 3.0

SRM SystemIPC

SRM SERVER 5.0

SUS

*) Integrated in SAP Web AS 6.40

Application component

Technical component

(mandatory)

Transfer protocol type

Technical component (optional)

Fig. 10: Basic System Architecture of Supplier Order Collaboration

The leading purchase order resides in the SAP ECC system. Goods receipt (confirmation) andinvoices can be entered in the SUS- SRM system. Purchase order data is updated in the backend

system from the SUS – SRM system. Goods receipt and invoice data is updated from the backendsystem.


These processes can only be implemented with the combination SAP SRM Server 5.0 and SAP ECC5.0. If you would like to use IPC, make sure that you select the 4.0 version.

SAP recommends that you install SAP Catalog Content Management 1.0. However, if you are alreadyusing Requisite BugsEye and do not want to install SAP Catalog Content Management, you mustupgrade Requisite BugsEye to the required version; see SAP Note 485884.

If you plan to continue using Requisite BugsEye, rather than installing SAP Catalog Content

Management, then upgrade SAP Integrated Catalog. If you have installed SAP Integrated Catalog 3.0on SAP J2EE Engine 6.20, then you may migrate to SAP J2EE Engine 6.40 and deploy SAPIntegrated Catalog on this SAP J2EE Engine. However, this step is optional; SAP Integrated Catalogmay also remain on J2EE Engine 6.20. For more information, see SAP Note 718953.

Both NW XI (Exchange Infrastructure) and NW BW (Business Information System) must run on thereleases defined for SAP NetWeaver ’04 (3.0 and 3.5, respectively). You may use BI Content 3.5.2 or3.5.3.


Upgrades to SAP ECC 5.0 are supported for the R/3 backend systems 3.1I – 4.7. For additionalinformation, refer to Section 4.3.

82 February 2005



12 Product Development and Manufacturing

12 Product Development andManufacturing

12.1 Target System LandcapeFigure 11 shows an example of a full-fledged system landscape for the key functional area ProductDevelopment and Manufacturing of mySAP ERP 2004. Depending on your initial situation andrequirements, this could be a target landscape for your upgrade.

SAP BW

NW BW System

Web AS ABAP 6.40

Search &

Classification

TREX 6.1

BI CONT 3.5.2

FINBASIS 300

SEM-BW 400SAP ECC

Web AS ABAP 6.40

ECC System

(with cProjects)

SAP CCM 1.0

SAP ECC 5.0

RDBMS

SAP XI


XI Components

NW XI System

XI Content:

SAP APPL, CCM,

FINBASIS

Laptop or Handheld

Mobile Asset

Management 2.5

Mobile Client 2.5

Web Browser

EP 6.0 Server


Portal Platform 6.0

Web AS Java 6.40

BP for Products

BP for Assets

BP for Project &

Design Collaboration

RDBMS

Web Browser

RDBMS

NW MI System

Web AS

ABAP + J ava 6.40

Frontend

cFolders Server

CPROJECTS

310_640

Web AS ABAP

6.40

RDBMS

RDBMS

CPROJECTS 310_640

WFM Core 110


For more information about the mandatory or optional character of the components for ProductDevelopment and Manufacturing, consult the ERP Master Guide in SAP Service Marketplace atser vi ce. sap. com/ er p- i nst mySAP ERP 2004.

Product Developmentand Manufacturing

Enterprise AssetManagement

ProductionPlanning

ManufacturingExecution

ProductDevelopment

Life-Cycle DataManagement

Fig. 11: Sample System Landscape for Product Development and Manufacturing

February 2005 83











Step Action








To benefit from the newWeb Dynpro-based SelfServices functionality,you must upgrade theR/3 system to SAP ECC

5.0; see SAP Note752312.

2 Optional: Upgrade the SAP R/3 Plug-in toPI 2004.1.For more information, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736 (Release restrictions R/3 Plug-in 2004.1). Also, consult SAP Service

Marketplace at servi ce. sap. com/ r3-pl ug- i n.


3 Install SAP Catalog Content SAP CCM 1.0 can be installed on any

84 February 2005










Management (CCM) 1.0.


system based on SAP Web AS ABAP6.40. In the above example it is installed

on the SAP ECC host.

4 Install cProject Suite 310, either on adedicated SAP Web Application Server 6.40or on the SAP Web AS of the SAP ECCsystem. For further information, see SAPNote 781760.


SAP cProject Suite 3.10 includes twoapplications:

• cProjects: A project managementapplication.

• cFolders: A collaboration platform.

CPROJECTS 3.10_640 (the technicalname for cProject Suite) is an add-onfor SAP Web AS.

If you are implementing cProject Suite

for the first time or, in particular, if youonly wish to use the cProjectsapplication, then it is most expedient toinstall cProject Suite on the SAP Web AS of the SAP ECC system.

If you are already using cProject Suite310_620, then upgrade to cProjectSuite 310_640.

If you were operatingcProject Suite

separately from your R/3system and you plan toupgrade both systems tomySAP ERP 2004, beadvised that you cannot merge these twosystems into one. Youmust continue to runboth systemsseparately.

5 Optional: Install WFM Core 110_640


You may install WFM Core (with at leastSP01) on the SAP ECC system. Like

CPROJECTS, WFM Core is an add-onfor SAP Web AS. Note that a separatelicense is required for WFM Core.

6 Upgrade SAP Business InformationWarehouse to Release 3.5 with the add-ons FINBASIS and SEM-BW.



The upgrade process is described inSAP Note 724419.

7 Perform a delta upgrade of BI Content toRelease 3.5.2 or 3.5.3

Refer to SAP Note 717812 or 774933(BI_CONT 3.5.3).

February 2005 85










9 Optional: Install Content Management andCollaboration 6.0


10 Optional: Import Business Packages forProject & Design Collaboration, Products, Assets



11 Optional: Install Search & Classifi cation (TREX) 6.1



12 Optional: Install SAP ExchangeInfrastructure (SAP XI) 3.0

[Component Installation Guide SAPExchange Infrastructure 3.0: <OperatingSystem>]

Also, review Section 6.1 of thisdocument.

13 Optional: Install Mobile AssetManagement 2.5

Only relevant for Enterprise AssetManagement.

12.3 Sample Upgrade Scenario

12.3.1 Development Collaboration

12.3.1.1 Overview

Development Collaboration is part of the process group Product Development. As shown in theBusiness Map of mySAP ERP 2004, located in Section 4 of this document, the process group ProductDevelopment in turn belongs to the key functional area Product Development and Manufacturing.

86 February 2005

















“Development Collaboration” as defined in the mySAP ERP 2004 Business Mapcorresponds to “Life-Cycle Collaboration & Analytics: Design Collaboration” in themySAP PLM 2004 Business Map.

cFolders is a web-based collaboration platform that is dedicated to promoting communication andcollaboration among groups of people who work in product development within cross-enterpriseprocesses. cFolders enables teams to set up joint virtual work areas on the Internet, in which they canexchange structured information as BOM or CAD models. This approach not only saves on costlytravel expenses, but also improves data consistency and significantly reduces project runtimes.

cFolders in mySAP PLM offers two processes – the first collaborative, the second competitive. Whilethe collaborative process enables all internal and external parties involved in product development tocooperate in a single joint work area, the competitive process allows you to establish separate work

areas for rival suppliers who participate in competitive bidding.. It is also possible to connect cFoldersin mySAP PLM with end-to-end e-sourcing processes, such as those provided by mySAP SRM.

cFolders enables SAP customers to communicate with their partners and suppliers via back-endobjects, without exposing their R/3 or ECC system to them. For instance, suppliers and partners of theSAP customer can change or modify a bill of materials in cFolders, and a back-end user cansubsequently import these changes in a reconciliation process from cFolders to the R/3 or SAP ECCsystem.

For more information on Collaborative Product Development in Cross-Enterprise Processes, consultSAP Service Marketplace at ser vi ce. sap. com/ pl m Life-Cycle Collaboration and Analytics

Design Collaboration.

February 2005 87

http://service.sap.com/plm





12.3.1.2 System Architecture of cFolders

The following diagram shows a sample system architecture of cFolders.

External

Partners

Technical

documents(drawings,

structure

information)

Server A

HTTPS / SOAP / RFC

cFolders

(part ofcProject Suite 3.10)

R/3 DMS documents, material, BOM

HTTPS

WGate

AGate

ITSHTTPS

RFC

RFC

(SNC)

Server B

Optional

NW BW

RFC

RFC

Optional

RFC (SNC)

SAP ECC

Plug-In

Optional

SAP Content

Server

Firewall Firewall

SAP Web AS 6.40

SAP Web Appl ication

Server

cProjects

(part ofcProject Suite 310)

Web AS 6.40RDBMS


Server

RDBMS

RDBMS

SAP Content

Server SAP DB

HTTPS

Optional

Internal

Employees

RDBMS

Fig. 12: Sample System Architecture of cFolders

Note that cProject Suite consists of the application components cProjects and cFolders. The technicalname of cProject Suite is CPROJECTS. Depending on how you set up your system, you wouldactivate either cProjects, or cFolders, or both components.

12.3.1.3 Valid Combinations, Source Releases

Refer to the Master Guide mySAP PLM using cProject 3.10. To review this document, visit SAP

Service Marketplace at ser vi ce. sap. com/ pl m- i nst using cProject Suite 3.10.

88 February 2005

http://service.sap.com/plm-inst

http://service.sap.com/plm-inst



13 Sales and Service


13.1 Target System LandscapeFigure 13 shows an example of a full-fledged system landscape for the key functional area Sales andService of mySAP ERP 2004. Depending on your initial situation and requirements, this could be atarget landscape for your upgrade.

SAP BW

NW BW System

Web AS ABAP 6.40

BI CONT 3.5.2

SAP XI


XI Content for CCM

NW XI System

J2EE Server


Internet Sales Web

App lic atio ns 4.0

Web AS Java 6.40

IPC Web App. 4.0

RDBMS

Web Browser

Product

Catalog

Files

Web Server

Web Server

Plug-in

Web AS Java 6.40

EP 6.0 Server

BP for Sales

Portal Platform 6.0

RDBMS

SAP ECC

Web AS ABAP 6.40

SAP ECC 5.0

ECC System

SAP CCM 1.0

RDBMS

Search &

Classification

TREX 6.1

Laptop or Handheld

MRS 2.0

Mobile Client 2.5

Web Browser

MDSD 2.0NW MI System

Web AS Java

+ ABAP 6.40

Internet Pricing

& Configurator

RDBMS

RDBMSIPC 4.0

Frontend

RDBMS

Ado be Server

RDBMS

Ado be Docu ment

Services 1.0

Web AS Java 6.40


For more information about the mandatory or optional character of the components for Sales and

Service, consult the ERP Master Guide in SAP Service Marketplace at servi ce. sap. com/ erp-

i nst mySAP ERP 2004.

Sales andService

Sales OrderManagement

AftermarketSales and

Service

Incentive & CommissionManagement

Professional-ServiceDeliver

Global TradeServices

Fig. 13: Sample System Landscape for Sales and Service

February 2005 89














Step Action




1 Upgrade R/3 to SAP ECC 5.0



• During the upgrade(BIND_PATCH phase), you shouldbind all the ABAP SupportPackages that are available forSAP ECC 5.0 and R/3 PI.

2 Optional: Upgrade SAP R/3 Plug-in to PI2004.1.For more information, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736 (Release restrictions R/3 Plug-in 2004.1).

Also, consult SAP Service

Marketplace at servi ce. sap. com/ r3-pl ug- i n.




SAP CCM 1.0 can be installed on anysystem based on SAP Web AS ABAP6.40. In the above example it is installedon the SAP ECC host.

4 Upgrade SAP Business InformationWarehouse to Release 3.5

[Component Upgrade Guide SAP BusinessInformation Warehouse 3.5: <Operating

PI BASIS 2004_1_640 is included in theupgrade to SAP BW 3.5.

90 February 2005










System>]

5 Install BI_CONT 3.5.2 or 3.5.3 See SAP Note 717812 or 774933(BI_CONT 3.5.3).

6 Upgrade SAP ExchangeInfrastructure (XI) to SAP XI 3.0.

[Upgrade Master Guide – SAPNetWeaver ´04, section SAPExchange Infrastructure]

[Upgrade Guide – SAP ExchangeInfrastructure 3.0]

You can upgrade SAP XI and SAP ECCin parallel. Afterward, it is absolutelynecessary that you configure SAP XIanew.

If you use SAP XI 1.0, werecommend that you perform anew installation and configureSAP XI anew. There is no

direct migration from SAP XI1.0 to SAP XI 3.0.

With the role of an IntegrationServer, SAP XI normallyrequires a dedicated SAP Web Application Server. SeeSection 6.1 of this document.

7 Import the XI Content for SAP CatalogContent Management 1.0.

If you have modified your XI 2.0content, you can reuse it for XI 3.0. Ifyou have made no modifications, we

recommend that you import the new XIContent for SAP XI 3.0.

8 Install SAP Web AS Java 6.40 on the J2EEServer.

• SAP Web AS Java includes SAPJ2EE Engine 6.40, SAP JavaConnector (JRFC), SAP Java TechServices

• If the source release of your J2EEEngine is 6.20, you must first de-install J2EE 6.20, then install J2EE6.40. For more information, refer tothe SAP NetWeaver Upgrade

Master Guide atser vi ce. sap. com/ i nst gui desNW04 Upgrade.

• If you are using J2EE Engine 6.30,you can directly import SupportPackage 04. By doing this, you willattain the 6.40 version.

If you decide in favor of a newinstallation, see:



February 2005 91

http://service.sap.com/instguidesNW04











9 Install FSCM Biller Direct 3.0, InternetSales 4.0, IPC Web Applications 4.0.

Refer to the installation guide of the ERPJava Components atser vi ce. sap. com/ er p- i nst mySAP

ERP 2004 ERP Java Components.

If you are already using an earlierversion of Internet Sales WAC (i.e.based on J2EE 6.20), refer to themigration guide atser vi ce. sap. com/ er p- i nst

mySAP ERP 2004 ERP JavaComponents.

Also refer to the appendix of thisdocument, in which important post-upgrade activities for Internet Sales inmySAP ERP are described.

10 Install IPC 4.0

Refer to the installation guide of the ERP

Java Components atser vi ce. sap. com/ er p- i nst mySAP

ERP 2004 ERP Java Components.





For installation information, consultservi ce. sap. com/ nw04i nst al l at

i on

Installation

SAP EP. Also, refer to Section 6.5.

12 Optional: Import Business Package forSales.

[For general information on Portal content,

see ser vi ce. sap. com/ ep- content ]


13 Optional: Install (or migrate to) Search &Classification (TREX) 6.1



14 Optional: Install Adobe DocumentServices 1.0 on a separate SAP Web ASJava server.

ADS is mandatory, if you would like touse Adobe forms.

92 February 2005























15 Optional: Install the mobile components onthe mobile clients:

• Direct Store Delivery (MDSD) 2.0

• Mobile Sales for Hand Held (MRS) 2.0

ser vi ce. sap. com/ er p- i nst mySAP

ERP 2004 Mobile InfrastructureComponents.

MDSD is required for the SAP DirectStore Delivery process. For moreinformation, refer to the ERP 2004Master Guide in SAP ServiceMarketplace atser vi ce. sap. com/ er p- i nst .

MRS is required for the Field Salesprocess.


13.3.1 Internet Sales in mySAP ERP

For information on Internet Sales in mySAP ERP, refer to SAP Service Marketplace atser vi ce. sap. com/ i sa- r 3.

Note that “ SAP Internet Sales in mySAP ERP” corresponds to “ SAP Internet Sales(R/3 Edition) 4.0.”

13.3.1.1 Overview

Before implementing a complete CRM solution, many organizations choose to deploy an entry-level E-Selling solution that enables them to rapidly extend their sales processes to the Web for fast return oninvestment. Internet Sales in mySAP ERP provides an e-commerce platform for mySAP ERPcustomers to rapidly turn the Internet into a profitable sales and interaction channel – without having toimplement a full CRM solution. The solution supports end-to-end order-to-cash processes by providingeasy-to-use, interactive selling and additional self-service, while leveraging existing mySAP ERPfunctionality and current IT investments. With Internet Sales in mySAP ERP, companies have an easyupgrade path to a full mySAP CRM solution.

Configuration information for SAP Internet Sales (R/3 Edition) 4.0 is described in detail in SAP SolutionManager, which also provides links to required customizing steps in the IMG and furtherdocumentation. For your convenience, SAP provides an extract of the SAP Solution Manager contentfor SAP Internet Sales (R/3 Edition) 4.0 as a PDF file. The new guide can be downloaded from SAP

Service Marketplace at ser vi ce. sap. com/ i sa- r 3. Also refer to SAP Note 722053.

February 2005 93



http://service.sap.com/isa-r3










The following table shows a minimal setup for Internet Sales for mySAP ERP 2004.


1 ECC System • SAP ECC 5.0


2 J2EE Server • ISA WAC 4.0

• IPC WAC 4.0


3 Web Server • Web Server with Web ServerPlug-in

The Web server is required as a connection between the Web browser and the Internet Sales Web Application.

The Web front-end connects directly with the Web server, as described in the subsequent section. Onthe Web server, a specific plug-in enables communication to the J2EE Engine in SAP Web AS Java. At press time, MS Internet information Server with the J2EE IIS Extension and Apache on UNIX aresupported.

The Web server is also used to deliver static catalog content, such as product images.

In addition to the components shown above, you should also evaluate whether you need to implement

Search and Classification (TREX) and IPC (Internet Pricing and Configurator). For example, you mustuse the latter, if you are dealing with configurable products. If you choose to install IPC 4.0, bear inmind that it needs a local database in the Internet Sales process.

The Java component ISA WAC has not yet been integrated with SAP Catalog ContentManagement (CCM). This integration will be enabled at a later date. For the time being,you create or maintain the product catalog in the same way you did for the SAP OnlineStore; in other words, directly in the SAP R/3 or SAP ECC system.

FSCM Biller Direct is also an optional component of the Internet Sales process. The two technicalcomponents complement each other: ISA WAC is used for order management through the Internet;

Biller Direct manages invoicing and payment through the Internet.

For reporting purposes, you may also consider using SAP Business Information Warehouse.

13.3.1.2.1 Basic System Architecture

The following diagram shows the basic system architecture of a small productive scenario for InternetSales in mySAP ERP.

94 February 2005




IMS

Internet DMZ Intranet

Middleware Server

Firewall

Browser

TREX

TREX

ECC System

ECC 5.0

ABAP

Firewall

SAP IPC Server

NW BW

SystemSAP Web AS Java 6.40

Internet Sales WAC 4.0

SAP IPC Dispatcher

RDBMS

RDBMS

Web Server

Web Server

Plug-in

Product

Catalog

Files

IPC- WAC 4.0Web AS 6.40

Fig. 14: Basic System Architecture of Internet Sales in mySAP ERP

The smallest production system consists of at least two hosts, one for the Web server and another forthe Web middleware and backend systems, separated by a firewall. In the example shown above, theWeb server and middleware layer are kept separate from the SAP ECC system. The networkconnection to the Internet is established through a leased line or frame relay with an appropriaterouter. This component is not shown in the graphic.

To enhance security, you should place a firewall in front of the Web server. Configure the firewall sothat it passes incoming HTTP(S) requests to the Web server and blocks all other requests, exceptthose for other Internet-enabled applications.

A second firewall separates the Web server from the internal network; the Web server is located in aso-called demilitarized zone (DMZ). Such a server is sometimes called a bastion host. No user requestcan go directly from the Internet into the internal network.

You should take special care while configuring the Web server’s operating system. For example, keepthe network services that the server offers to a bare minimum - in other words, only those services thatare needed to operate the server. Refer to the operating system documentation for information on how

to secure the Web server.

The Web server receives requests and passes them to the Web server plug-in, which again forwardsthe requests to the J2EE Engine in SAP Web AS Java. The extension can forward using HTTP orHTTPS.

For an Internet shop, you have to leave a user ID and password on the middleware server, which hasaccess to the R/3 (or SAP ECC) system, so that anonymous access to the shop is possible. This iswhy the middleware host should not be located in the DMZ, but rather in the internal network. Additionally this user should have only very limited permissions in the backend system.

For enhanced security, you can implement a multi-stage firewall concept and place another firewallbetween the middleware host and the internal backend systems like SAP CRM, SAP R/3, SAP APOand SAP BW.

February 2005 95




This setup can be used for production systems with up to a few hundred users. It is well suited for abusiness-to-business (B2B) scenario, where the number of users is limited and controlled. The

demand for high availability is not as crucial as in the business-to-consumer (B2C) scenario, becausebusiness partners are more likely to tolerate service disruptions than the average Internet shopper.

If you want to use this setup as a starting point for productive e-business, you should have a clearvision of your probable hardware demands in the near future. You can then react quickly once thebusiness model succeeds and the demands increase.


Technically speaking, it is possible to combine ISA WAC 4.0 on J2EE 6.20 with SAP ECC 5.0.However, in that case, you cannot use TREX 6.1, since this component cannot communicate with a6.20 version of the J2EE Engine. For this reason, and also because several installation and monitoringimprovements have been made in SAP Web AS Java 6.40, SAP recommends that you install or

migrate to ISA WAC 4.0 on SAP Web AS 6.40.

ISA WAC can be combined with the R/3 releases 3.1I – 4.7. Again, to take advantage of the newfeatures, you should select the ISA WAC version based on SAP NetWeaver ’04. Refer also to SAPNote 622049, in which prerequisites for using the Internet Sales R/3 Edition are documented (forexample, Support Package levels.)

If you are using SAP Online Store (R/3 4.0B – 4.6C) and would like to upgrade to Internet Sales inmySAP ERP, you can keep the product catalog in R/3 or ECC, but must replace the ITS Server with aJ2EE Server.


R/3 source releases 3.1I – 4.7 are valid. The source release for Internet Sales WAC is 3.1 and 4.0,both based on J2EE 6.20. The corresponding migration guide (to ISA WAC 4.0 on 6.40) can be found

in SAP Service Marketplace at ser vi ce. sap. com/ er p- i nst mySAP ERP 2004 ERP Java

Components.

13.3.1.5 Post-Upgrade Activit ies

The post-upgrade activities for Internet Sales are documented in the appendix of this document.

96 February 2005





14 Corporate Services


14.1 Target System LandscapeFigure 15 shows an example of a full-fledged system landscape for the key functional area CorporateServices of mySAP ERP 2004. Depending on your initial situation and requirements, this could be atarget landscape for your upgrade.

Laptop

MTS + MTR 1.6

SAP BW

NW BW System

Web AS ABAP 6.40

BI CONT 3.5.2

MI Client 2.5

Web Browser

BP for Products

Web AS Java 6.40

EP 6.0 Server

Portal Platform 6.0

Content Management &

Collaboration 6.0

BP for Assets

BP for Design

Collaboration

Web Browser

NW MI System

Web AS Java

+ ABAP 6.40

SAP ECC

Web AS ABAP 6.40

SAP ECC 5.0

SAP CCM 1.0

ECC System

(with cProjects)Front end

RDBMS

NW KW System

Web AS Java

+ ABAP 6.40

SAP Content

Server 6.30

TREX 6.1

SAP Gateway

SAP ITS 6.20

RDBMS

Optional

RDBMS

cFolders Server

CPROJECTS310_640

Web AS ABAP

6.40

RDBMS

SAP BusinessConnector

SAP BC 4.7

WFM Core 110

CPROJECTS 310_640


For more information about the mandatory or optional character of the components for Corporate

Services, consult the ERP Master Guide in SAP Service Marketplace at ser vi ce. sap. com/ erp-i nst mySAP ERP 2004.

CorporateServices

Real EstateManagement

Project PortfolioManagement

TravelManagement

Environment,Health & Safety

QualityManagement

Fig. 15: Sample System Landscape for Corporate Services

97 February 2005













Step Action







• During the upgrade(BIND_PATCH phase), you shouldbind all the ABAP SupportPackages that are available forSAP ECC 5.0 and R/3 PI.

2 Optional: Upgrade SAP R/3 Plug-in to PI2004.1.For more information, see SAP Notes704564 (R/3 plug-in: PI 2004.1installation/delta upgrade) and 708736 (Release restrictions R/3 Plug-in 2004.1).

Also, consult SAP ServiceMarketplace at servi ce. sap. com/ r3-pl ug- i n.




SAP CCM 1.0 can be installed on anysystem based on SAP Web AS ABAP6.40. In the above example it is installedon the ECC host.

4 Install cProject Suite 310, either on adedicated SAP Web Application Server 6.40or on the SAP Web AS of the SAP ECCsystem. For further information, see SAP

Note 781760.

SAP cProject Suite 3.10 includes twoapplications:

• cProjects: A project managementapplication.

98 February 2005










For installation information, see SAP Note

717650.

• cFolders: A collaboration platform.

CPROJECTS 3.10_640 (the technicalname for cProject Suite) is an add-onfor SAP Web AS.

If you are implementing cProject Suitefor the first time or, in particular, if youonly wish to use the cProjectsapplication, then it is most expedient toinstall cProject Suite on the SAP Web AS of the SAP ECC system.

If you are already using cProject Suite310_620, then upgrade to cProjectSuite 310_640.

If you were operatingcProject Suiteseparately from your R/3system and you plan toupgrade both systems tomySAP ERP 2004, beadvised that you cannot merge these twosystems into one. Youmust continue to runboth systemsseparately.

5 Optional: Install WFM Core 110_640

Installation information: SAP Note 605649.

You may install WFM Core (with at least

SP01) on the SAP ECC system. WFMCore requires a separate license.

6 Upgrade SAP Business InformationWarehouse to Release 3.5


PI BASIS 2004_1_640 is included in theupgrade to SAP BW 3.5.

7 Install BI_CONT 3.5.2 or 3.5.3 See SAP Note 717812 or 774933(BI_CONT 3.5.3.)






February 2005 99









9 Optional: Import Business Package forProducts, Assets and Design Collaboration,depending on the processes you want toimplement.

[For general information on Portal content,

see ser vi ce. sap. com/ ep- content ]


10 Optional: Install SAP Business Connector4.7, Core Fix 3

SAP BC is only mandatory if aconnection to HRS or Deutsche BahnPortal (BIBE) is required.

See SAP Note 571530.

11 Optional: install the mobile components

MTR and MTS 1.6 on the mobile clients.

ser vi ce. sap. com/ er p- i nst mySAP

ERP 2004 Mobile InfrastructureComponents.

14.3 Sample Upgrade ScenariosCorporate Services covers a wide range of functionality; in the following sections, we will discussTravel Management and Project Execution with cProjects.

The key capability Project Portfolio Management consists of several processes, such as ProjectPlanning, Project Execution, Project Accounting, and Time & Ressource Management, all of which use

SAP cProject Suite. Therefore, by describing “Project Execution with cProjects”, we provide you with arepresentative example for the processes within Project Portfolio Management.

“Project Planning with cProjects” as defined in the mySAP ERP 2004 Business Mapcorresponds to “Program & Project Management: Project Planning” in the mySAP PLMBusiness Map.

14.3.1 Travel Management

14.3.1.1 Overview

Travel Management provides integrated functions to support all of the processes that are required toplan trips, and links these to the corresponding settlement, taxation and payment processes. TravelManagement supports the request, planning and booking of trips, as well as the settlement of travelexpenses and the transfer of settlement results to other business function areas. The integrationenabled by SAP Travel Management guarantees the benefits of synergies that increase efficiency andreduce process costs.

100 February 2005













R/3 source releases 3.1I – 4.7 are valid.

14.3.2 Project Execution with cProjectsNote that Project Execution with cProjects is only one of the processes covered by the key capabilityProject Portfolio Management.

14.3.2.1 Overview

SAP cProject Suite consists of the components cProjects and cFolders. cProjects offers a web-based,easy-to-use interface and constitutes a powerful tool for operative project management.

You can use the business process Project Execution with cProjects to carry out a planned project witha defined start and end date. You can monitor and control how the project is executed using a numberof different mechanisms. Using project management methods improves your overview of the activitiesto be carried out and the effect they have on the schedule. Moreover, Project Execution helps youreact quickly to any deviations from the project plan.


cProject Suite can be installed to run in a standalone mode on a dedicated SAP Web ApplicationServer. It is also possible to install it on the SAP Web AS infrastructure of SAP ECC 5.0. However, thisis optional and depends on your specific requirements. A joint installation with SAP ECC makes sensefor new implementations and if you only want to use the cProjects application.

The following table shows an example of a minimal system landscape for cProjects.


1 SAP cProject Suite 3.10Server

• CPROJECTS 3.10_640

• SAP Web AS ABAP 6.40(minimum SP03)

2 SAP GUI (forCustomizing and Administration only)

• SAP GUI 6.40

All other components (for example, SAP ECC 5.0, SAP BW 3.5, WFM Core, and so on) are optional.They are described in the cProject Suite 3.10 Master Guide. In addition, a Business Scenario Guide

and a Configuration Guide are available in SAP Service Marketplace at ser vi ce. sap. com/ pl m-i nst .

14.3.2.3 System Archi tecture of cProjects

The following diagram depicts a sample system architecture of cProjects.

102 February 2005








External

Partners

Technical

documents

(drawings,

structure

information)

Server B

HTTPS / SOAP / RFC

cFolders

(part of

cProject Suite 3.10)

R/3 DMS documents, material, BOM

HTTPS

WGate

AGate

ITSHTTPS

RFC

RFC(SNC)

Server A

Optional

NW BW

RFC

RFC

Optional

RFC (SNC)

SAP ECC

Plug-In

Optional

SAP Content

Server

Firewall Firewall

SAP Web AS 6.40

RDBMS

SAP Web Application

Server

cProjects

(part of

cProject Suite 310)

SAP Web AS 6.40

RDBMS


Server

RDBMS

RDBMS

SAP Content

Server SAP DB

HTTPS

OptionalInternal

Employees

Fig. 16: Sample System Architecture of cProjects, Including optional Components


cProject Suite 3.10 has been defined as part of the mySAP ERP 2004 solution and is now included inthe mySAP ERP shipment. Nevertheless, up to now, cProject Suite has been a standalone softwarecomponent that was installed on a dedicated SAP Web Application Server. It has not been part of R/3Enterprise or earlier releases of SAP R/3.

If you already use cProject Suite separately from your R/3 system and you plan toupgrade both systems to mySAP ERP 2004, be advised that you cannot merge thesetwo systems into one. You must continue to run both systems separately.

On the other hand, if you plan a new installation of SAP cProject Suite 3.10, you may perform it on theSAP ECC 5.0 system, that is, on the same SAP Web Application Server, as described in SAP Note781760.

Of course, a cProject Suite standalone installation is compatible with other mySAP ERP 2004components such as SAP ECC 5.0, in the same manner as before, for example, with R/3 4.6 or R/34.7 Enterprise.

The following Integration scenarios between cProject Suite and other mySAP ERP components areavailable:

• Accounting integration (creating internal orders in SAP ECC to collect project-related costs)

• Object links (link from cProjects to existing business objects in SAP ECC or other systems)

• Data extraction to SAP BW

February 2005 103




The required steps to achieve this integration are described in the cProjects Online Help, at:

hel p. sap. com

Documentation

SAP cProject Suite.



• SAP cProjects 3.0 / SAP Web AS 6.20

• SAP cProjects 3.1 / SAP Web AS 6.20

Note that an upgrade from cProject Suite 2.00 to cProjects 3.10 (SAP Web AS 6.40) is not supported.However, cProject Suite 3.00 or 3.10 on SAP Web AS 6.20 can be smoothly upgraded to cProjects3.10 on SAP Web AS 6.40.

For more information on cProject Suite upgrade (and installation), see SAP Notes 717650 and 781760.

104 February 2005





15 Data Migrations

15 Data Migrations

15.1 FlexGLmySAP ERP 2004 offers a new General Ledger functionality which is more flexible than itspredecessor, and hence carries the name “FlexGL”. At the moment there is no standard migration pathto FlexGL. However, if you would like to migrate to FlexGL and if you are aware of the releaserestrictions documented in SAP Note 741821, then SAP can provide you with selected migrationprograms upon request. If required, these programs may be extended or supplemented, according tothe specific project requirements. If necessary, this can be done with the support of SAP Development.

15.2 TreasuryThe data model of the Transaction Manager has been changed so that you have to convert parts ofcustomizing, master data, flow data of the Transaction Manager, if you upgrade to SAP Enterprise,Extension Set 2.0 or above. Consult SAP Note 706952, which provides information about the dataconversion with transaction TPM_MIGRATION. It also points to other sources of information,particularly to the migration guide.

The migration guide for ERP can be found in SAP Service Marketplace at ser vi ce. sap. com/ f scm Media Library Documentation SAP Treasury & Risk Management.

15.3 Real Estate As of Release 1.10 of SAP R/3 Enterprise Extension, SAP delivers a new Real Estate Management,called “RE-FX,” which offers extended and more flexible functions. Functional enhancements weremade in Release 2.00 of the SAP R/3 Enterprise Extension, and since the conversion to mySAP ERP,RE-FX functionality has been further developed in an extension of SAP ECC (EA-FIN). For details onRE-FX functions in specific releases, refer to SAP Note 517673.

The migration to RE-FX is not yet supported with standard tools. Nevertheless, a migration can still becarried out. For more information, see SAP Note 443311.

15.4 Other MigrationsMigration guides exist for the components Search and Classification (TREX), SAP Web AS, SAP XI,

SAP Enterprise Portal and SAP Internet Sales. The respective documents for these SAP NetWeavercomponents are available in SAP Service Marketplace at ser vi ce. sap. com/ nw04upgrade

Upgrade Cross-NW. You will find instructions on how to migrate SAP EP 5.0 (SP 6) to SAP EP 6.0

(NW ’04) at ser vi ce. sap. com/ nw- howt ogui des Portal, KM and Collaboration. A migration

from SAP EP 6.0 (SP 2) to SAP EP 6.0 (NW ’04) is planned to be available at a later date.

The migration guide fro Internet Sales is available at ser vi ce. sap. com/ er p- i nst mySAP ERP

2004 ERP Java Components.

February 2005 105



http://service.sap.com/fscm
















16 References

16 References16.1 DocumentationThe following table lists the documentation that is mentioned in this Upgrade Master Guide.

Title Where to find

All installation and upgrade guides ht t p: / / servi ce. sap. com/ i nst gui des

ERP 2004 Master Guide ht t p: / / servi ce. sap. com/ er p- i nst

ERP 2004 Upgrade Master Guide ht t p: / / ser vi ce. sap. com/ er p- upgrade

All ERP-related Component Installation

Guides

ht t p: / / servi ce. sap. com/ er p- i nst

All ERP-related Component Upgrade (andMigration) Guides

ht t p: / / ser vi ce. sap. com/ er p- upgrade

SAP NetWeaver Installation Guides(including Master Guide)

ht t p: / / ser vi ce. sap. com/ nw04i nst al l at i on

SAP NetWeaver Upgrade (and Migration)Guides

ht t p: / / ser vi ce. sap. com/ nw04upgr ade

SAP Terminology Database ht t p: / / servi ce. sap. com/ sapt erm

General Information on mySAP ERP ht t p: / / ser vi ce. sap. com/ er p

Hardware Sizing ht t p: / / servi ce. sap. com/ si z i ngPlanning the System Infrastructure(Technical Infrastructure)

ht t p: / / ser vi ce. sap. com/ t i

Security Guide ht t p: / / ser vi ce. sap. com/ secur i t ygui de

Overview of platform and technology-related topics

ht t p: / / ser vi ce. sap. com/ pl at f orms

Support Package Stack Strategy ht t p: / / ser vi ce. sap. com/ sp- st acks

Product Availability Matrix ht t p: / / servi ce. sap. com/ pam

Safeguarding Services for Upgrade ht t p: / / servi ce. sap. com/ saf eguar di ngupgrade

Upgrade Adjustments with SPAU / SPDD ht t p: / / ser vi ce. sap. com/ spauHigh Availability ht t p: / / ser vi ce. sap. com/ ha

SAP Note Search ht t p: / / servi ce. sap. com/ not es

ERP Business Map ht t p: / / ser vi ce. sap. com/ busi nessmaps

SAP Enterprise Portal Information ht t p: / / servi ce. sap. com/ nw- ep

Upgrade Road Map (latest version) ht t p: / / ser vi ce. sap. com/ sol ut i onmanager Downloads Other Content

Software / Support Package Download Area

ht t p: / / ser vi ce. sap. com/ swdc

R/3 Plug-in ht t p: / / servi ce. sap. com/ r3- pl ug- i n.

106 February 2005





















http://service.sap.com/nw-ep

http://service.sap.com/solutionmanager





http://service.sap.com/solutionmanager

http://service.sap.com/nw-ep























16 References

Title Where to find

SAP Enterprise Portal Content ht t p: / / ser vi ce. sap. com/ ep- content

SAP NetWeaver Rapid Installer ht t p: / / servi ce. sap. com/ nw- r i

SAP Business Information Warehousedocumentation

ht t p: / / ser vi ce. sap. com/ bw

SAP Learning Solution documentation ht t p: / / ser vi ce. sap. com/ l ear ni ngsol ut i on

SAP Product Lifecycle Management ht t p: / / ser vi ce. sap. com/ pl m

SAP Internet Sales in mySAP ERP ht t p: / / ser vi ce. sap. com/ i sa- r 3

Treasury Migration Guide ht t p: / / servi ce. sap. com/ f scm Media Library

Documentation SAP Treasury & Risk Management.

16.2 SAP NotesThe following table lists all SAP Notes mentioned in this documentation.

SAP Note Title

Note 805390 Preparation: ERP 2004 Inst. only with SAP Solution Manager

Note 789554 Upgrade to SAP Basis 640 and higher with WP-PI

Note 781760 Installation of cProjects and XRPM in system

Note 774933 Installation and upgrade to BI_CONT 3.53

Note 761246 ERP 2004 SP Stack 2: Release and Information Note

Note 760874 ERP: Support Package Stacks Release and Information Notes

Note 758035 ITS-based ESS services for mySAP ERP 2004

Note 752312 ESS / MSS in mySAP ERP 2004 basing on Web Dynpro

Note 748338 Upgrade LSO 2.0 to LSO 3.0 (table LSO_CUSTOMIZE_C)

Note 741821 Release Restrictions of SAP ERP 2004

Note 740930 Java Components for mySAP ERP 2004

Note 739929 Postprocessing installation/upgrade of ERECRUIT 300

Note 725184 BW area menu not displayed (BW 3.50)

Note 724419 Upgrade to SAP SEM Release 4.0

Note 724418 Installation SAP SEM Release 4.0

Note 722053 Configuration of SAP Internet Sales (R/3 Edition)

Note 718625 Additions upgrade NetWeaver 2004 with LSOFENote 718455 SEM-BW 400 and FINBASIS 300: Upgrade to NetWeaver 04

Note 717812 Installation and upgrade to BI_CONT 3.52

Note 717803 Enhancements to the SAP NetWeaver 04 ERECRUIT 300

Note 717802 Installing ERECRUIT 300

Note 717650 cProject Suite 310: Installation and Upgrade

Note 717510 Release Restrictions SAP Mobile Infrastructure 2.5

Note 713540 SAP Biller Direct 3.0 installation note (Java component)

Note 713536 SAP Biller Direct 3.0: Installation (FI-CA component)

Note 713534 SAP Biller Direct 3.0: Installation (Component FI-AR)

Note 709140 Recommended JDK and VM Settings for the WebAS630/640

February 2005 107







































































16 References

SAP Note(continued)

Title

Note 708736 Release restrictions R/3 Plug-In 2004.1Note 707730 Release Restrictions of SAP NetWeaver ‘04

Note 706952 Data migration for CFM-TM or TR-TM

Note 705060 CCM 100 Installation with SAINT

Note 704565 Upgrade to R/3 4.6C/4.70x110/4.70x200 with PI 2004.1

Note 704564 R/3 plug-in: PI 2004.1 installation/delta upgrade

Note 700779 Upgrading to SAP ECC 500 with PI/PI-A/SLL_PI

Note 700778 Add-ons integrated into SAP ECC 500

Note 700771 TREX 5.0/6.0/6.1: How to activate a TREX extension

Note 696034 Initial release for XI20 - XI30 migration

Note 689574 Add. info. on upgrading to SAP ERP Central Component

Note 687695 Upgrade ISA R/3 3.1 -> 4.0 : Transformation of shop filesNote 674417 Release Restrictions Plug-in Basis 2004.1

Note 670644 UPGRADE: SAP Mobile Infrastructure 2.5 - Composite Note

Note 663258 Corrections for R3up version 640

Note 645436 Database changes for the Javabasket from 40 SP01 to SP02

Note 642999 Import Filter

Note 642775 Composite SAP Note for Business Packages as of EP 6.0 SP1

Note 640634 KM compatibility package

Note 623723 Upgrade: Application-specific problems

Note 622049 R/3 prerequisites for using Internet Sales R/3

Note 620461 Upgrading Integrated Catalog

Note 609451 Database changes for the Javabasket from 31 SP04 to SP05Note 605649 Installation of WFMCORE 100 (transaction SAINT)

Note 594370 Build tool for adjusting Internet Sales Web Applications

Note 571530 Availability of SAP Business Connector

Note 568853 Supported TREX versions in SAP E-Recruiting

Note 568576 Composite SAP note: Manager Self-Service (My team)

Note 529063 Overview: Notes for the Learning Solution add-on

Note 517673 Flexible Real Estate Management: Release restrictions

Note 503907 Release strategy for add-on LSOFE

Note 503468 Release strategy for R/3 add-on LSO

Note 485884 Information : Requisite eMerge and BugsEye delivery

Note 443311Enterprise extension SAP Real Estate: technical basics

Note 380457 Netscape 6.x support for ESS 4.6C

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

108 February 2005











































































17 Appendix

17 AppendixPost-Upgrade Activities for Internet Sales

Activating the Monitor ing Featu res

After you have upgraded the components of your mySAP ERP system landscape, you should refer tothe Solution Operation Guide for instructions on activating the monitoring features of the softwarecomponents in your ERP landscape.

Updating the Internet Sales Database

UseIn Release 4.0 some database tables have been extended to improve functionality. Therefore thestructure of the database changed slightly. To avoid loss of data, you have to perform some manualupgrade steps for the database.

Prerequisites

• Your source release is Internet Sales 3.1.

• The database is already up and running on the host you want to connect to the Internet Salesapplication.

• You have already set up a valid database user for Internet Sales with appropriate rights (forexample creating tables, deleting tables.)

• The database schema for Internet Sales is set up and running as well.

• You have backed up the Internet Sales database schema before upgrading the tables.

Procedure...

1. Open the Enterprise Manager of the MS SQL Server to check if Internet Sales databaseschema is assigned to the Internet Sales database user as default schema. If not, assign it tothe user.

2. Open the SQL Query Analyzer of the MS SQL-Server as Internet Sales database user tocreate database tables. Make sure that you are in the Internet Sales database schema.

3. Open and execute the files cr eat e_basket s_t abl e. sql , cr eat e_i tems_t abl e. sql ,

and cr eat e_busi nesspar t ner s_t abl e. sql which are delivered with Internet Sales.

4. Depending on the source release you may check if the tables EXTDATAHEADER andEXTDATAITEM already exist in your database.

5. If these tables do not exist, open the files cr eat e_ext dataheader_t abl e. sql and

cr eat e_ext dat ai t em_t abl e. sql with the SQL Query Analyzer and execute them.

6. Check that the contents of the table BUSINESSPARTNERS have not been modified by theupgrade.

For more information, see SAP Notes 645436 and 609451.

February 2005 109





17 Appendix

Changed Interface Methods

Public Interface Change Remark(See Java documentation)

CCardStrategy No changes

ChangeStrategy Not used in 3.1

CreateStrategy

public ReturnValuecreateDocument

New parameter documentType: R/3type of the newly created documentFirst parameter changes fromOrderData to SalesDocumentData.

Public ReturnValuesimulateDocument

New parameter transactionType: R/3type of the newly created document.Second parameter changes from OrderData to SalesDocumentData.

Both changes are due to thesupport of inquiry creation in ISA

R/3 with 4.0

DetailStrategy No changes

ReadStrategy No changes

StatusStrategy No changes

public voidsetSalesDocumentStatus

renamed to

public voidsetSalesDocumentChangeStatus

Not relevant for 3.1 since changingdocuments was not supported andtherefore it did not make sense tooverwrite that method.

WriteStrategy

Removed

public JCO.FunctioncallRfcSd_SalesDocument_Create

Removed

public void setIPCInformation

No longer an interface method.Now available inCreateStrategyR3 as protectedmethod. The first parameter isSalesDocumentData instead ofOrderData. Two new stringparameters are available now.

No longer an interface method. Stillavailable as public method inWriteStrategyR3.

February 2005 111



17 Appendix

New Interface Methods

Public Interface New Remark(See Java documentation)

CCardStrategy No new methods.


CreateStrategy public boolean checkMaterialInR3 Extended OCI support in 4.0.

CreateStrategy public ReturnValue copyDocumentNew: Orders with reference to aquotation.

DetailStrategy public void addPossibleShipTos

Reads the master data ship-toparties and adds them to thecurrent document. For order

change support.ReadStrategy

public booleanaddAllMessagesToBusinessObject

ReadStrategy public void getDocumentFlowNew: Document flow on headerlevel.

ReadStrategy public TechKey getTextItemId New: free text handling.

ReadStrategy public void getTexts New: free text handling.

WriteStrategy public void checkConfiguration New: order change.

WriteStrategy public void setAddressData New: order change.

WriteStrategy public void setItemInfo

Was not exposed as aninterface method in 3.1(protected method inBaseStrategy)

WriteStrategy public void setTexts New: free text handling

Protected Class Methods

Public Interface Change Remark(See Java documentation)

CCardStrategy No changes.


CreateStrategyR

3

protected voidprepareInvalidBasket

gets an additional parameterbasketService.

For converting the R/3 product IDinto the UI format (in the standard:

cut leading zeros.)

DetailStrategyR3 No changes

ReadStrategyR3 No changes

112 February 2005



17 Appendix

Public Interface(cont.) Change Remark(See Java documentation)

StatusStrategyR3

protected String setFilterCriteria

has been renamed to

protected String setSearchCriteria

protected void setHeaderStatus

has been renamed to

protected void

setHeaderChangeStatus

Not relevant for 3.1 sincechanging documents was notsupported and therefore it did notmake sense to overwrite thatmethod. The same applies to

protected void setItemStatus.

WriteStrategyR3Removedprotected voidperformCustExitBeforeR3Call

Available now inCreateStrategyR3.

Converting Shop Files

Use

If you are upgrading from release 3.1 to 4.0 you must convert the shop list file

( _obj ect Li st . xml ) and the files representing the shops (<shopi d>. xml ) since their formats have

been changed in release 4.0.Procedure

For information about the procedure, see SAP Note 687695.