ERP Master Guide

7/31/2019 ERP Master Guide

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

Document Version 3.0

February 2005

Mater ia l Num ber 50069200





Typograph ic Convent ions 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 programming

language, when surrounded bybody 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 names

of installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation

Icon MeaningCaution

Example

Note

Recommendation

Syntax



Master Guide: mySAP ERP 2004

Contents

1 SAP Documentation Types ...........................................................7

2 Getting Started ...............................................................................9

2.1 How to Use the mySAP ERP Master Guide ................................................... 10

2.2 Target Audience............................................................................................... 10

2.3 Important SAP Notes....................................................................................... 11

2.4 Further Information ......................................................................................... 12

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

4 Cross-Solution Topics................................................................14

4.1 SAP NetWeaver™ 2004 Components ..........................................14

4.2 SAP NetWeaver Rapid Installer ....................................................17 4.3 Industry Add-ons ...........................................................................20

4.4 SAP Solution Manager...................................................................23

5 mySAP ERP 2004: Technical Overview......................................24

5.1 mySAP ERP Components .............................................................24

5.2 Minimal System Landscape..........................................................25

5.3 Overall Installation Sequence.......................................................28 6 Key Functional Areas of mySAP ERP .......................................32

6.1 End-User Service Delivery ............................................................35 6.1.1 Overview........................................................................................................ 35

6.1.2 Technical System Landscape...................................................................... 35

6.2 Analytics .........................................................................................44

6.2.1 Overview........................................................................................................ 44 6.2.2 Technical System Landscape...................................................................... 44

6.2.3 Strategic Enterprise Management............................................................... 46

6.2.4 Financial Analytics ....................................................................................... 47

6.2.5 Operations Analytics.................................................................................... 47

6.2.6 Workforce Analytics..................................................................................... 48




6.4.3 Talent Management ...................................................................................... 55

6.4.4 Workforce Process Management................................................................ 56

6.4.5 Workforce Deployment ................................................................................ 57

6.5 Procurement and Logistics Execution ........................................58 6.5.1 Overview........................................................................................................ 58


6.5.3 Procurement.................................................................................................. 59

6.5.4 Supplier Collaboration ................................................................................. 60

6.5.5 Inventory & Warehouse Management......................................................... 61

6.5.6 Outbound and Inbound Logistics ............................................................... 62

6.5.7 Transportation Management ....................................................................... 64

6.6 Product Development and Manufacturing...................................65 6.6.1 Overview........................................................................................................ 65


6.6.3 Production Planning..................................................................................... 66

6.6.4 Manufacturing Execution............................................................................. 66

6.6.5 Enterprise Asset Management .................................................................... 67

6.6.6 Product Development................................................................................... 68

6.6.7 Life-Cycle Data Management....................................................................... 68

6.7 Sales and Service...........................................................................70 6.7.1 Overview........................................................................................................ 70


6.7.3 Sales Order Management............................................................................. 71

6.7.4 Aftermarket Sales and Service .................................................................... 74

6.7.5 Professional Service Delivery ..................................................................... 75

6.7.6 Global Trade Services.................................................................................. 75

6.7.7 Incentive & Commission Management....................................................... 76

6.8 Corporate Services ........................................................................77 6.8.1 Overview........................................................................................................ 77


6.8.3 Real Estate Management ............................................................................. 78

6.8.4 Project Portfolio Management..................................................................... 78

6.8.5 Travel Management ...................................................................................... 79

6.8.6 Environment, Health & Safety ..................................................................... 80




7.1.7 SAP Knowledge Warehouse (KW) 7.0......................................................... 88

7.1.8 Search and Classification (TREX) 6.1 ......................................................... 89

7.1.9 SAP Internet Transaction Server................................................................. 89

7.1.10 SAP GUI ....................................................................................................... 90

7.1.11 SAP Internet Graphics Services................................................................ 91

7.2 mySAP ERP Components .............................................................92 7.2.1 SAP ECC 5.0.................................................................................................. 92

7.2.2 PI 2004_1_500 ............................................................................................... 93

7.2.3 SAP Learning Solution (LSO) 3.0 ................................................................ 93

7.2.4 SEM-BW 4.0................................................................................................... 95

7.2.5 FINBASIS 3.0 ................................................................................................. 96

7.2.6 SAP Catalog Content Management (CCM) 1.0 ........................................... 96

7.2.7 SAP E-Recruiting 3.0 .................................................................................... 96

7.2.8 SAP SRM Server 5.0 ..................................................................................... 98

7.2.9 cProject Suite 3.10........................................................................................ 99

7.2.10 SAP IPC 4.0 ............................................................................................... 100

7.2.11 SAP XSS 500 ............................................................................................. 101

7.2.12 Internet Sales Web Application (ISA WAC) 4.0 ...................................... 101

7.2.13 FSCM Biller Direct 3.0 .............................................................................. 102

7.2.14 Mobile Time Sheet (MTS) 1.6 ................................................................... 103

7.2.15 Mobile Travel Expenses (MTR) 1.6.......................................................... 104

7.2.16 SAP Mobile Asset Management (MAM) 2.5 ............................................ 104

7.2.17 SAP Mobile Sales for mySAP ERP (MSR) 2.0 ........................................ 105 7.2.18 SAP Mobile Direct Store Delivery (MDSD) 2.0........................................ 105

8 Media Information ......................................................................107

Software Components and DVD / CD Structure................................................ 107




1 SAP Documentation TypesSeveral documents have been created to assist you in installing, implementing, operating andupgrading your SAP solutions. The Solution Master Guide (this document) is the firstdocument you obtain; it provides a summary of all the information and documentation to beconsidered for the solution at hand. The following figure displays an overview of the mostimportant documentation types that are needed during the various phases in the life cycle ofan SAP solution. Although the various types of documentation shown here are closely relatedto one another, each documentation type enables you to perform a different task that arises

during the course of a different solution phase.

Implementation

Master Guide

ConfigurationDocumentation

Release Notes

ComponentInstallation Guide

ComponentUpgrade 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-phase documentation.

• SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over30 languages, as well as many definitions and glossary entries in English and




document contains general guidelines and suggestions about system security. Other

technologies and individual applications have a Security Guide of their own.

The current version of the Security Guide is located on SAP Service Marketplace atservice.sap.com/securityguide.

• The Component Installation Guide describes the technical implementation of anSAP component, taking into account the combinations of operating systems anddatabases. It does not describe any business-related configuration. The ComponentInstallation Guides for the different components can be found on SAP ServiceMarketplace at service.sap.com/instguides.

• The Configuration Documentation is contained in the SAP Solution Manager,which is mentioned in a separate section of this document. SAP Solution Manager isa tool with various functions, one of its main functions being the configuration of SAPsolutions and Business Scenarios. It contains IMG activities, transactions, and so on,as well as documentation. Instead of the configuration documentation in SAPSolution Manager, there may be separate Business Scenario Configuration Guides inSAP Service Marketplace for earlier shipments of the Business Scenarios.

• The Solution Operation Guide is the starting point for operating an SAP solution.The guide refers users to the tools and documentation that are needed to carry outvarious tasks, such as monitoring, backup/restore, master data maintenance,transports, and tests. It also refers users to other documents, for example the SAPLibrary, the Master Guide, and the Component Management Guides. The currentversion is located on SAP Service Marketplace atservice.sap.com/instguides.

• The Upgrade Master Guide is the starting point for upgrading the BusinessScenarios of an SAP solution. It provides scenario-specific descriptions of

preparation, execution, and follow-up of an upgrade. It also refers to otherdocuments, such as the Component Upgrade Guides and SAP Notes. Instead of anUpgrade Master Guide, there may be several Business Scenario Upgrade Guides ora Solution Upgrade Guide for earlier shipments of the Business Scenarios of an SAPsolution. The current version is located on SAP Service Marketplace atservice.sap.com/instguides.

• The Component Upgrade Guide describes the technical upgrade of an SAPcomponent, taking into account the combinations of operating systems anddatabases. It does not describe any business-related configuration. The current

version is located on SAP Service Marketplace atservice.sap.com/instguides.

• Release notes are documents that contain short descriptions of new features orchanges in an SAP component since the previous release. Release notes aboutABAP developments enable the SAP system to generate delta and upgrade IMGs.The current version is located on SAP Service Marketplace at

http://service.sap.com/securityguide

http://service.sap.com/instguides














2 Getting Started

2 Getting StartedThis Master Guide provides a central starting point for the technical (new) implementation ofmySAP ERP 2004. Upgrade-related topics are beyond the scope of this document. They arediscussed in the ERP Upgrade Master Guide.

To facilitate the implementation process, all information within this document is organized bykey functional areas and their respective key capabilities. You can therefore find theinformation required for the technical implementation of each key capability within a separate

corresponding section of this document. The terms “key functional area” and “key capability”are explained in Section 6.

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 scenarios to be implemented, and in accordance withyour security or performance requirements, the infrastructure you implement may differfrom these examples.)

• Information about the versions of the required components.

• Information about the overall installation sequence and subsequent steps.

• References to related installation and configuration guides.

• References to the Upgrade Master Guide. This guide provides information about theoverall upgrade sequences, references to related documentation, SAP Notes, andadditional upgrade information.

• Information about mutual dependencies that affect two or more components within thetechnical infrastructure.

The Master Guide at hand primarily discusses the technical implementation ofmySAP ERP overall, rather than its subordinate components. This means thatadditional software dependencies may exist without being mentioned explicitlyin this document. You can find more information about component-specificsoftware dependencies in the corresponding installation guides.

To read the current version of the mySAP ERP 2004 Master Guide and otherrelated installation guides, see SAP Service Marketplace at

service.sap.com/erp-inst → mySAP ERP 2004 .

W d h i h i f h d

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




2 Getting Started

2.1 How to Use the mySAP ERP Master Guide

Depending on the key functional area(s) you require – for example, mySAP ERP Financialsand mySAP ERP Human Capital Management – and the number of processes you wish toimplement, you may require different component installation and configuration guides duringimplementation.

The mySAP ERP Master Guide explains which components and which guides are required

during the implementation phase.•

•

•

•

•

Section 4 provides technical information that is independent of any specific key functionalarea. For example, you can review information about SAP NetWeaver components andhow they relate to the mySAP ERP solution.

In Section 5 you will find a general solution-related installation sequence, plus anexample of how a minimal system landscape could be set up for test, training anddemonstration purposes.

Sections 6.1 through 6.8 explain the Software Component Matrix that is relevant for thekey capabilities that belong to each corresponding functional area. Each matrix alsostates whether the software components therein are mandatory or optional.

Section 7 provides some more detailed information on the most important technicalcomponents required for mySAP ERP. It also contains references to relateddocumentation that may be useful.

Section 8 “Media Information” provides information about the data carriers and thesoftware components contained in them. It should help you identify the DVDs / CDs youneed for the installation or upgrade of the required software components.

2.2 Target Audience

This documentation contains both high level information on solution and business processlevel and very detailed technical information. It is therefore intended for decision-makers aswell as SAP consultants and SAP system administrators with operating system, database,

and SAP system knowledge.



2 Getting Started

2.3 Important SAP Notes

You must read these SAP Notes before you start the installation. These Notes contain themost recent information on component installations, possible restrictions and corrections tothe installation documentation.

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

Important Related SAP Notes for mySAP ERP

SAP Note Title

760874 ERP: Support Package Stacks Release and Information Notes

741821 Release restrictions for SAP ERP 2004

740930 Java Components for mySAP ERP 2004

707730 Release Restrictions of SAP NetWeaver '04674417 Release restrictions plug-in basis 2004.1

670733 Installation/upgrade of Basis Plug-In (PI_BASIS) 2004.1

571530 Availability of SAP Business Connector

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

Add-on-related SAP Notes

SAP Note Title

718626 Installation/delta upgrade WFMCORE 110_620/110_640

718624 Installing the LSOFE 300 add-on with transaction SAINT

718457 FINBASIS 300 installation (with Transaction SAINT)

718456 SEM-BW 400 installation (with Transaction SAINT)

717802 Installing ERECRUIT 300

705060 CCM 100 Installation with SAINT

717650 cProject Suite 310: Installation and Upgrade

700778 Add-ons integrated into SAP ECC 500

http://service.sap.com/notes




2 Getting Started

2.4 Further Information

As your enterprise makes final preparations to begin the actual implementation (or upgrade),we recommend that you familiarize yourself with the following sources of information, all ofwhich are at your disposal in SAP Service Marketplace. For example, there are importantfacts that you should take into account in the planning phase of your installation; these factsare not fully described in the present document. Moreover, many of the reference sourcesnamed below provide additional information that you may wish to consider to ensure that you

complete your installation 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, seeSAP Service Marketplace at service.sap.com/erp.

• Hardware Sizing

For detailed information about the calculation of hardware requirements (such asCPU, disk and memory resources), including access to the SAP Quick Sizer, seeSAP Service Marketplace at service.sap.com/sizing.

• Planning the System Infrastructure

For comprehensive information on technical infrastructure issues and networkintegration, see SAP Service Marketplace at service.sap.com/ti.

For guidelines and recommendations that pertain to system and network security,see SAP Service Marketplace at service.sap.com/securityguide.

For a complete overview of platform and technology-related topics, see SAP ServiceMarketplace at service.sap.com/platforms.

• 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 andupgrade guides for the individual components, see SAP Service Marketplace at

service.sap.com/erp-inst → mySAP ERP 2004 .

• mySAP ERP Upgrade

For tailored information to facilitate the preparation of the upgrade decision and theexecution of the upgrade project, see SAP Service Marketplace atservice.sap.com/erp-upgrade.

Information on this page is updated on a monthly basis.

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/ti

http://service.sap.com/sizing

http://service.sap.com/erp



3 History of Changes

3 History of ChangesThe mySAP ERP Master Guide is regularly updated in SAP Service Marketplace atservice.sap.com/erp-inst.

Before starting the implementation, we recommend that you immediately visit

SAP Service Marketplace to ensure that you have reviewed the most recentedition of this document.

The following table summarizes the changes that were made in each version of the mySAPERP Master Guide.

Version Publication Date Nature of Revision

1.00 June 2004 First Version

2.00 August 2004 Feedback from ramp-up projects incorporated.All sections revised.

2.10 November 2004 Feedback from ramp-up projects incorporated. All sectionsrevised and renumbered. New Section 6 “MediaInformation” added. New subsection on SAP Direct StoreDelivery added. System landscape diagrams changed(J2EE Engine replaced by SAP Web AS Java).

3.00 February 2005 Document adapted to the new version of the mySAP ERPBusiness Map. System landscape diagrams revised andchanged. Software Component Matrix for each keycapability revised and changed. All sections renumbered.





4 Cross-Solution Topics


4.1 SAP NetWeaver™ 2004 Components

SAP NetWeaver ‘04 provides mySAP ERP with a comprehensive integration platform anddelivers the foundation to serve all ERP applications. SAP NetWeaver is built to extend

mySAP ERP and to integrate non-SAP systems.

SAP NetWeaver ‘04

m ySAP ERP 20 04Analytics

Financials

Human Capital Management

Procurement & Logistics Execution

Product Development & Manufacturing

Sales and ServiceCorporate Services

ABAP StackAdditional

Components

KW Functionality

MI Functionality

XI Functionality

BW Functionality

BI Content

Web AS ABAP

Java Stack

BW Java Components

XI Components

Adobe DocumentServices

NW DI

Web AS Java

Content Managementand Collaboration

Portal Platform

KW IKS

Java -.NETInteroperability

Visual ComposerServer

XI Adapter Engine

XI Adapter Engine(J2SE)

Search andClassification

(TREX)

Portal Runtimefor .NET

Content Server

BW PrecalculationService




components of SAP NetWeaver for which support packages or patches continue to be

produced.

Java StackABAP Stack

AdditionalComponents

PI_BASIS2004_1_640

SAP ABA 640

SAP BASIS 6.40

SAP BW 3.50

SAP IGS 6.40

SAP KERNEL 6.40

BI Content Add-on

SAP Web AS Java

SAP J2EE Engine 6.40

SAP IGS 6.40

SAP Web AS ABAP

NWDI

JDI 6.40

JDI BUILD TOOL6.40

JDI OFFLINE 6.40

NW Developer

Studio

NW DEVELOPERSTUDIO 2.0

Adobe Doc. Services

ADOBE DOC.SERVICES 1.00

BW Java Components

BI UDI 350

Enterprise Portal

PORTAL PLATFORM

6.0_640

CM +COLLABORATION

6.0_640XI Components

XI CONNECTIVITYSE 3.0

XI ADAPTER

FRAMEWORKCORE 3.0

XI ADAPTERFRAMEWORK 3.0

XI TOOLS 3.0

XI CONTENT

SAP_BASIS 6.40

KW IKS

SAP_IKS_100

BW ANALYZERPRECALC

SERVICE 350BI CONT 3.5.2

SAP MI Client 2.5

TREX 6.1

SAP ContentServer 6.30

SAP NetWeaver ’04 Software Components

XI CONNECTIVITYSE 3.0

XI Adapter Engine(J2SE)

XI Adapter Engine

XI ADAPTERFRAMEWORK 3.0

XI ADAPTERFRAMEWORK

CORE 3.0

SAP J2EE Engine6.40

The main constituents of SAP NetWeaver are grouped in the ABAP and Java Stacks. Theadditional components shown in Figure 3 are optional, meaning that you would only have toinstall them in response to your specific requirements.

Fig. 3: SAP NetWeaver ‘04 software components

Note the following important points regarding the SAP NetWeaver components:

SAP Mobile Infrastructure 2.5

SAP Mobile Infrastructure (SAP MI) provides the framework for mobile applications to

• Run platform-independently by providing standard services




The Development Toolkit helps mobile application developers to define Smart

Synchronization data models that are normally used between the mobile applications on themobile device and the backend systems.

Any SAP NetWeaver-based system can be configured as a Mobile Infrastructure middlewaresystem. Only SAP Web AS (ABAP and Java) is required. On the client side, the Mobile Clientcomponent (SAP MI Client 2.5) is required, alongside the mobile applications that yourbusiness scenarios demand.

Depending on your requirements, you may either install a separate SAP Mobile Infrastructuresystem to 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 first option, especially in view of future upgrade scenarios; if a newversion of SAP Mobile Infrastructure is released and you would like to deploy the newfeatures, you could immediately upgrade a standalone SAP Web AS to the new release. Incontrast, you would not enjoy this advantage by using the SAP Web AS of your ECC system,for you would have to wait until the corresponding ECC upgrade became available.

For comprehensive information on SAP Mobile Infrastructure, see SAP

Service Marketplace at service.sap.com/nw-mi.

Detailed information is also provided in the SAP NetWeaver Master Guide; see SAP ServiceMarketplace at service.sap.com/nw04installation Installation .

SAP Business Information Warehouse (SAP BW 3.5)

A restriction exists if you wish to operate Business Information Warehouse and ERP Central

Component in the same system. In a production environment, this setup can only besupported on a project basis. If you are interested in implementing this setup, contact SAP.Nevertheless, a common client for SAP BW 3.5 and SAP ECC 5.0 is not supported.

SAP Enterprise Portal 6.0

Currently, only a new installation of EP 6.0 (NW ’04) is available. An upgrade from EP 5.0(SP 6) and EP 6.0 (SP 2) is planned to be available at a later date. For additional information,consult SAP Service Marketplace at service.sap.com/nw-ep.

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 samesystem for production purposes, contact SAP. This can only be supported on

j t b i

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

http://service.sap.com/nw04installation

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

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


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




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 to upgrade a different application that runs on a separate system (forexample, MDM), then an SAP XI upgrade may be required. You may pursue one oftwo options to carry out the SAP XI upgrade. With the first option, you cansimultaneously upgrade both SAP XI and the application (for example, SAP ECC)that shares the same SAP Web AS with SAP XI. If this first option cannot be pursued,you must use the second option to upgrade SAP XI. With the second option, youmust migrate SAP XI to a separate SAP Web AS. Otherwise, you cannot upgrade

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

production purposes, contact SAP. This can only be supported on a projectbasis.

Note that the present guide deals with ERP-specific implementation situations. Therefore,when SAP NetWeaver components are affected, always refer at the same time to the SAPNetWeaver Master Guide or the individual component installation guides, which are locatedin SAP Marketplace at service.sap.com/nw04installation .

4.2 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 selectedSAP Business Packages from days to hours. SAP NetWeaver Rapid Installer enables you tolower total cost of ownership by reducing the time required to install, deploy and configureSAP NetWeaver Enterprise 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 easilyconnect to these systems through a pre-configured portal with a minimum of interaction andconfiguration time.

SAP NetWeaver Rapid Installer installs a clearly defined set of business scenarios formySAP ERP 2004 and mySAP CRM 4 0 Thus the SAP NetWeaver Rapid Installer allows an






You cannot use SAP NetWeaver Rapid Installer 2.0 or 2.1 to installcomponents of earlier releases of SAP NetWeaver ’04.

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

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)business scenarios (prerequisite: mySAP ERP 2004 is installed)

SAP Self Service (XSS) 5.0 which is based on SAP NetWeaver 04 Java Stack andconnects to the backend functions in the ERP system. For more information on SAPXSS, see SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP 2004 .

Business packages with business scenarios for mySAP CRM (prerequisite: mySAP CRM4.0 and SAP BW 3.5 is installed)

An SAP System Landscape Directory (SLD) if you want SAP NetWeaver Rapid Installerto install a new SLD.

CCMS agents to enable monitoring in the Portal

Product Information and Documentation

You can find detailed product information at service.sap.com/nw-ri. Read thisinformation and check if SAP NetWeaver Rapid Installer 2.0 or 2.1 is a viable alternative foryou to install SAP Enterprise Portal based on SAP NetWeaver ‘04.

Before installing the software, read the SAP NetWeaver Rapid Installer Installation Guide available for both versions and describing in detail the installation procedure, hardware andsoftware requirements and pre-installation steps. You can find this document and additionalinformation on the SAP NetWeaver Rapid Installer DVD (for both versions) in the folderDocumentation .

DVD Order Process






Limitations

You can use the SAP NetWeaver Rapid Installer as a viable alternative for installing SAPEnterprise Portal (plus other software components).

Note the following limitations:

1. Platform availability

One of the following combinations of operating systems and databases are required forinstallation:

Microsoft Windows Server 2000/2003 operating system with Microsoft SQL Server2000 Enterprise Edition

Microsoft Windows Server 2000/2003 operating system with Oracle 9.2.0.4 64-bitdatabase

Sun Solaris SPARC 8 or 9 operating system with Oracle 9.2.0.4 64-bit database

2. Installation Type: One node installation

SAP NetWeaver Rapid Installer supports a one node installation on the same server. Anadditional J2EE cluster environment can be set up by using the standard SAPinstinstallation tool.

3. Scalability and Sizing

SAP NetWeaver Rapid Installer installs an SAP Enterprise Portal which is optimized for asmall number of business users (about 200 concurrent users). But you are not limited to thisscenario: You can scale the system and add new hardware according to the standard portalsizing.




4.3 Industry Add-ons If an Industry Solution (IS) Add-on is running in your source system, then keep in mind thatan upgrade to SAP ECC 5.0 is not supported for several IS Add-ons. On the other hand,some IS Add-on functionality has been integrated into SAP ECC 5.0, and even into lower R/3releases. For more information on the integrated functionality, consult SAP Note 700778 atservice.sap.com/notes .

Customers who have implemented IS Add-ons should review the industry-specific upgradeguides which are located at service.sap.com/instguides.

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

Aerospace &Defense

SAPAerospace &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 &

SAPEngineering &

Add-on(4.5B)

integratedinto SAP

Notsupported

Notsupported

Notsupported











SAP R/33.1I-4.6B

SAP R/34.6C



SAP ECC5.0

High Tech SAP HighTech

Add-on(4.5B, 4.6B)

integratedinto SAPDiscreteIndustries

Notsupported

Notsupported

Notsupported

High Tech SAP DiscreteIndustries

Notsupported


Add-on

Higher Education &Research

SAP CampusManagement

Notsupported

Add-on Add-on Add-on Notsupported

Insurance SAP Insurance

FS-CD

Add-on

(4.5B, 4.6B)

Add-on Add-on Add-on Not

supported

Insurance SAP InsuranceFS-CM

Notsupported


Insurance SAP InsuranceFS-CS

Notsupported


Insurance SAP InsuranceFS-RI

Notsupported


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


Mill Products SAP CableSolution

Add-on(3.1I, 4.5B)

Add-on integratedinto SAPDiscreteIndustries

Notsupported

Notsupported

Mill Products SAP Mill

Products

Add-on

(4.5B, 4.6B)

Add-on integrated

into SAPDiscreteIndustries

Not

supported

Not

supported

Mill Products SAP DiscreteIndustries

Notsupported

Notsupported

Add-on Notsupported

Add-on

Mining SAP Mining Add-on Add-on Not Add-on Not







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 Public

Sector PSCD

Not

supported

Add-on Add-on Add-on Not

supported

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 ofSAP R/3 Enterprise or SAP ECC.

• Add-on: Industry-specific component is shipped as an add-on to SAP R/3, SAP R/3

Enterprise or SAP ECC.

• Not Supported: means that the add-on or industry extension in question is not availableon top of the corresponding R/3 or ECC release.

Furthermore, note the following:

• Releases of industry specific add ons may not be available for all SAP R/3 SAP R/3




4.4 SAP Solution ManagerSAP provides you with SAP Solution Manager as the platform that will support theimplementation and operation of mySAP ERP 2004. Using SAP Solution Manager enablesyou to take advantage of SAP’s full support and gives you the opportunity to leverage thebroad spectrum of SAP's support and continuous improvement offerings.

During the installation process an SAP Solution Manager system is required to generate the“SAP Solution Manager Key” for the installation/upgrade of mySAP ERP 2004. Without this

key, the installation process cannot continue. The generation of the required key isavailable with SAP Solution Manager as of Release 3.1 SP20 or SAP Solution ManagerRelease 3.2 SP4.

In your mySAP ERP project, perform the following activities inside SAP SolutionManager

• Define your Solution Landscape

• Connect existing systems to enable EarlyWatch Alert

• Define those business processes that are affected by mySAP ERP 2004

Furthermore, SAP recommends:

• Document, configure and test the previously defined business processes• Train end users via SAP Solution Manager

If you are using SAP components based on the JAVA stack:

• Install and use Solution Manager Diagnostics for root cause analysis.

The following table summarizes the information sources available for SAP Solution Manager:

Topic Where to Find More Information

System infrastructure, scenarios, installationand configuration of SAP Solution Manager

Master Guide – SAP Solution Manager available on SAP Service Marketplace atservice.sap.com/instguides SAP Components SAP Solution Manager Installation Guides

Benefits and usage scenarios SAP Solution Manager – Learning Mapsavailable on SAP Service Marketplace atservice.sap.com/rkt-solman orservice.sap.com/solutionmanager

Additional information SAP Service Marketplace atservice.sap.com/solutionmanager


http://service.sap.com/rkt-solman

http://service.sap.com/solutionmanager




http://service.sap.com/rkt-solman




5 mySAP ERP 2004: Technical Overview

5 mySAP ERP 2004: TechnicalOverview

5.1 mySAP ERP Components

Having discussed SAP NetWeaver, the foundation upon which mySAP ERP is built, we nowprovide an overview of ERP-relevant components from an application point of view.

mySAP ERP 2004 Software Components

ECC 5.0

SAP_HR 500

SAP_APPL 500

EA-APPL 500

EA-DFPS 500

EA-FINSERV500

EA-GLTRADE

500

EA-HR 500

EA-PS 500

EA-RETAIL 500

EA-IPPE 300

PI 2004_1_500

WFM Core110_640

Learning

Solution 3.0(Frontend)

SEM-BW 4.0

FINBASIS 3.0

BI CONT 3.5.2

E-Recruiting 3.0

cProject Suite3.1

ABAP Components

NW ’04 ABAP Stack

Internet Pricing& Configurator

(J2SE)

SAP XSS 5.0

LSO ContentPlayer 3.0

Biller Direct 3.0

IPC Web App 4.0

ISA WAC 4.0

Java WebApplications

Java Components

NW ‘04 Java Stack

IPC 4.0

Catalog ContentManagement 1.0

SAP SRM

Server 5.0

Add-ons basedon NW ABAP

SAP SRM

Portal Content

BusinessPackages

Additional Components

MI Client 2.5

SAP ITS 6.20

SAP Business Connector4.7

XI Content

XI Content forApplications

SAP Solution Manager 3.1

Mobile Time Sheet 1.6

Mobile Travel Expenses 1.6

LSOOP 3.0 Offline Player

Mobile

Frontend

LSOAE 3.0

SAP GUI

Mobile Sales for ERP (MRS)2.0

Mobile Asset Management2.5

Mobile Direct Store Delivery 2.0

NetWeaver ’04

Additional Components

Fig. 4: Overview of the mySAP ERP 2004 components




ons are installed using the SAINT tool. In the following figures showing system landscapes,

we display the add-on component(s) required by the key functional areas.The components included in the Java Web Applications frame are independent J2EEcomponents, combined in one single installation tool as ERP Java Components. Therefore, ifyou want to install one (or more) of these components, you will require the ERP JavaComponents installation, which is performed by the SAPinst tool.

The Mobile Direct Store Delivery component will be available as from Q3 2005.

To see what is inside the NetWeaver ’04 Additional Components box, see Figure 3.

Integrating other SAP Business Suite Components with SAP ECC 5.0

You may integrate other SAP Business Suite components with SAP ECC 5.0, for example,SAP CRM, SAP SCM, and so on, provided that you have the required license. The R/3 Plug-in enables this integration. R/3 Plug-In releases are downward compatible with all releases ofthe SAP components still in mainstream maintenance. Therefore, you may also integratelower releases of these components, which means that existing business scenarios will stillbe available after upgrading to SAP ECC 5.0.

For more information, refer to service.sap.com/r3-plug-in Integration of SAP R/3 / Enterprise and SAP Components SAP ERP Central Component .

5.2 Minimal System Landscape

The mySAP ERP solution consists of ABAP and non-ABAP components. With certainconstraints, you can install many of these components on a single host, provided that certainprerequisites are fulfilled. In this section, you will find information how to set up a minimallandscape, in which all of the key functional areas can be deployed.

Several possibilities exist to distribute these components among various hosts. Thedistribution depends on many factors such as sizing, security, hardware, and so on. Inprinciple, you can choose almost any distribution of components to hosts between theminimal system landscape – described in this section – and a maximum distributedlandscape, where every component runs on its own (or even multiple) host(s).

If you plan to implement a minimal landscape, you must know which business processes youwould like to run and then install the components you need for those business processes

only. Therefore, it may not be necessary to install all components described in this section.

We strongly recommend that you use a minimal system landscape fortest and demonstration purposes only.

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





• The XI installation requires an add-in installation of SAP J2EE 6.40. In addition,

the system must be Unicode.• The components ADOBE DOCUMENT SERVICES 1.0 (ADS), Enterprise Portal

6.0, Exchange Infrastructure 3.0 and Search and Classification (TREX) 6.1require a large amount of memory and make substantial demands on the hostperformance of the CPU. If you want to implement ADS, EP 6.0, XI and TREX ina minimal landscape, consider the hardware sizing recommendations providedabove.

• Inform yourself about the supported platforms for each component you wish to

install. Some components may feature platform restrictions. For moreinformation, refer to SAP Service Marketplace atservice.sap.com/platforms .

• Due to high performance and memory demands it is recommended that youinstall ADS, Enterprise Portal and TREX on separate hosts for production use.

• An add-in installation of SAP Enterprise Portal is currently supported for demo,training and test systems. If you would like to install SAP EP in the same systemas SAP ECC for a productive environment, see below.

• For Business Information Warehouse reporting purposes, you should reserve adedicated backend client. In that client, activate BI CONT as required.

Operating Business Information Warehouse and SAP ERP CentralComponent (SAP ECC) in the same system and in a production environmentis solely supported on a project basis. If you are interested in implementingthis setup, contact SAP.

The same restriction applies for the joint installation and productive operationof SAP Enterprise Portal with SAP ECC or SAP XI with SAP ECC on a sharedSAP Web Application Server.

If installed in a shared system, a common client for SAP BW 3.5 and SAPECC 5.0 is not supported. SAP XI must also be set up in a dedicated client.

•

In a minimal landscape setup, because a low number of users is assumed, youcan manage these users by defining a “User Store” or “UME” (User ManagementEngine) client in the ERP Central Component system. This client makes all users“known” to J2EE, the Enterprise Portal and the Exchange Infrastructure (XI). Tothis end, users are created in the UME client and assigned the roleSAP_J2EE_GUEST .






LearningSolution 3.0(Frontend)

SEM-BW 4.0

FINBASIS 3.0

E-Recruiting 3.0

WFM Core110_640

BI CONT 3.52

cProject Suite3.1

Add-ons basedon NW ABAP

SAP ECC 5.0

SAP ECC

Web AS ABAP 6.40

SAP XSS 5.0LSO Content

Player 3.0

Biller Direct 3.0

IPC Web App 4.0

ISA WAC 4.0

Java WebApplications

Java J2EEComponents

Web AS Java 6.40

XI Content

XI Content forApplications

ABAP Components

ERP Host

Web AS ABAP 6.40

SAP SRM Server 5.0

SRM Host

Catalog ContentManagement 1.0

Web AS Java 6.40

Adobe DocumentServices 1.0

SAP ITS 6.20


SAP BusinessConnector 4.7

RDBMS

RDBMSTREX 6.1

Web AS Java 6.40

RDBMS

EP 6.0 Host

Business Packagesfor Applications

IPC 4.0RDBMS

SAP DB IPC 4.0

Portal Platform 6.0

Content Management &Collaboration 6.0

XI Components

BW Components

Fig. 5: Example of a minimal mySAP ERP system landscape

As stated in Section 5.1, the constituent parts of SAP ECC 5.0 cannot be installedindividually. In contrast, all add-ons displayed within the frame “Add-ons based on NW ABAP”are installed individually, using the SAINT tool.

The Java Web Applications shown in Figure 5 are essentially independent J2EEcomponents, combined in a single installation as ERP Java Components. The ERP JavaComponents are installed with the SAPinst tool. If you wish to use any of the Java WebApplications shown in Figure 5, then you must use the ERP Components DVD (see Section8).

All SAP NetWeaver components are part of the ERP solution shipment. The installationsequence for these components is explained in the next section.

Certain business processes described in the next sections require the use of




5.3 Overall Installation Sequence The following table not only describes the installation steps for a sample minimal landscape;it also describes the suggested sequence of installation steps that you should perform toobtain a full-fledged system landscape.

Before you start the installation, it is imperative that you know whichcomponents are required for the business processes you plan to use. It is not

recommended to install all components as a matter of course. Only installthose components that are required for the business processes you will use.

For more information about the required components, review the softwarecomponent matrix for each key capability.

During the installation process an SAP Solution Manager system is required

to generate the “SAP Solution Manager Key” for the installation of mySAPERP 2004. Without this Key, the installation process cannot continue. Forfurther information please refer to Section 4.4.

Installation Sequence – “ERP Host”

Software To Be Installed/Sequence

1. Install the SAP ECC 5.0 system, which includes PI 2004.1, SAP HR and the EnterpriseExtensions, as shown in Figure 5.

The installation also includes the SAP NetWeaver components SAP_BASIS 640, SAP_ABA640, SAP_BW 350 and PI BASIS 2004_1_640.

For more information, see SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP 2004 SAP ECC 5.0 .

2. Install the ABAP Add-ons, including BI CONT 3.52 (or 3.53), FINBASIS 300, ERECRUIT300, SEM-BW 400, LSOFE 300, CPROJECTS 310 and WFMCORE 110_640. Note thatFINBASIS is a technical prerequisite for SEM-BW. WFMCORE requires a separate license.

For more information, see SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP 2004 ERP ABAP Add-On Components .

3. Install SAP Web AS Java 6.40. If required, install the J2EE in add-in mode (see below). Setheap size to 1024MB and PermSize to 256MB.








4. Install the BW Java components. Both components – MMR 3.50 = Metamodel Repository

(MMR) 3.50 and Universal Data Integration (UDI) 3.50 – are delivered together, in a singleinstallation. The BW Java components are optional for the mySAP ERP key capabilities.

For more information, see SAP Service Marketplace atservice.sap.com/nw04installation Installation Guide - SAP Business Warehouse 3.5 .

5. Install SAP Exchange Infrastructure (XI) 3.0 Java Components and subsequently configurethe local SLD (System Landscape Directory). As stated before, the XI Java Componentsrequire an add-in installation of the J2EE.

If you operate a separate SAP XI system, you may elect to run a central SLD on a separateserver.

For more information, see SAP Service Marketplace atservice.sap.com/nw04installation Installation Guide - SAP Exchange Infrastructure 3.0 .

6. Install Search and Classification (TREX) 6.1. For performance reasons, this component isoften operated on a separate server.

For more information, see SAP Service Marketplace atservice.sap.com/nw04installation Inst. Guide - Search and Classification

(TREX). Alternatively, see SAP Service Marketplace at service.sap.com/notes SAP Note 745115 (Installing TREX 6.1 SP4).

7. Install Internet Pricing and Configurator (IPC) 4.0, along with a database for it. Thiscomponent will be used for certain Internet Sales scenarios, but not for OperationalProcurement with SAP SRM.

For more information, see SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP 2004 ERP Java Components IPC 4.0 Server Installation Guide .

8. Install the following ERP Java Applications on the SAP J2EE Engine:

• FSCM Biller Direct 3.0

• XSS 500

• Internet Sales (ISA WAC) 4.0 for ERP

• IPC Web App. 4.0

• LSO Content Player 3.0 (for SAP Learning Solution)

These Java components are combined in a single installation as ERP Java components.

Note that important restrictions apply to a minimal setup. For example, regardingEBPP/payments, a large number of open items may cause a high consumption of memoryand CPU capacity. For more information, see SAP Service Marketplace atservice.sap.com/notes SAP Note 741821 (Release restrictions for SAP ERP2004)
















Installation Sequence – Portal Host


1. Install SAP Web AS Java 6.40. Install the J2EE in standalone mode (see below). Set heapsize to 1024MB and PermSize to 256MB.

service.sap.com/nw04installation Installation Installation Guide Web AS Java 6.40 <Platform>: <Database>

2. Install SAP Enterprise Portal (EP) 6.0, including CMC, if required. Because EP 6.0 currentlydoes not support an add-in installation, and because it requires a large amount of memoryand makes substantial demands on the host performance of the CPU, it, too should beinstalled on a separate server.

For installation information, consult SAP Service Marketplace atservice.sap.com/nw04installation Installation SAP EP

3. Install the required Business Packages, which are also referred to as “Portal Content.” Theycan be downloaded from service.sap.com/swdc Download Installations and Upgrades Entry by Application Group SAP Application Components SAP ERP SAP ERP 2004 SAP Business Packages

For more information about Business Packages, see Section 6.1.2 and SAP ServiceMarketplace at service.sap.com/ep-content.

Installation Sequence – “SRM Host”

If you desire a minimal setup, you may install SAP SRM Server 5.0 and other technicalcomponents on a third server – that is, separate from the ERP and Enterprise Portal hosts.This approach succeeds in minimizing the demands that are placed on the ERP host. If youelect to pursue this approach, ensure that you select a platform that is valid for all thecomponents you plan to install.


1. Install SAP SRM Server 5.0.

This installation also includes NetWeaver components SAP_BASIS 640, SAP_ABA 640,SAP_BW 350 and PI BASIS 2004_1_640.

For more information, see SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP 2004 SRM Server 5.0 Installation Guide - SAP SRM Server 5.0 <operation system> .

2. Install SAP Catalog Content Management 1.0 (CCM 100) by using the SAINT tool.

For more information see SAP Service Marketplace at service.sap.com/notes SAP

O



http://service.sap.com/swdc

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












4. Install Adobe Document Services 1.0, noting thereby platform restrictions.

For more information, see SAP Service Marketplace atservice.sap.com/nw04installation Installation Dev Env .Installation Guide – Adobe Document Services

5. Install Internet Pricing and Configurator (IPC) 4.0. This IPC will be used for certainscenarios, like Procurement with SAP SRM, but not for Internet Sales. An additionaldatabase is not required. In contrast, see installation step 7 of the ERP host.

For more information, see SAP Service Marketplace at service.sap.com/erp-inst

mySAP ERP 2004

ERP Java Components

IPC 4.0 Server Installation Guide . 6. Install SAP Business Connector (SAP BC) 4.7, Core Fix 3 (minimum).

For more information, see SAP Service Marketplace at service.sap.com/notes SAP Note 571530 (Availability of SAP Business Connector).

7. Install SAP ITS 6.20. Normally, in a production landscape you will operate this ITS on aseparate server.

For more information, see SAP Service Marketplace at service.sap.com/sap-its

Downloads .

8. Install SAP Content Server 6.30. Note that an SAP DB is required for this component.

For more information, see SAP Service Marketplace at service.sap.com/instguides SAP Components SAP Content Server Release 6.30 .

9. Install SAP GUI 6.20 or 6.40. Actually, this component can be installed at any time, since itis installed on the client(s). Note that SAP GUI is mainly required for administrators andpower users. Moreover, certain mySAP ERP processes, which are not yet entirely portal-based, still require SAP GUI.

The installation of front ends for the SAP system is described separately in the SAP Front End Installation Guide which can be found at service.sap.com/instguides Installation and Upgrade Guides SAP Components SAP Front End Components

6 K F ti l A f SAP ERP




http://service.sap.com/sap-its











6 Key Functional Areas of mySAP ERP

6 Key Functional Areas of mySAP ERPPowered by SAP NetWeaver, the open integration and application platform, mySAP ERPcombines core ERP functionality with portal-based collaboration across the extendedenterprise. MySAP ERP gives companies better control of their assets as well as businessprocesses such as financial supply chain management, e-recruiting and profitabilityassessments of employees, departments and customers.

MySAP ERP allows companies to regain active control of their whole administrative andoperations environment to increase efficiency and profitability. MySAP ERP enables new

levels of business process and technology integration while laying the foundation forincremental evolution of the solution.

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

at service.sap.com/businessmaps → Cross-Industry Maps → Enterprise Resource Planning (ERP).

m ySAP ERP 2004End-User Service Delivery

AnalyticsStrategic Enterprise

ManagementFinancial Analytics Operations Analytics Workforce Analytics

Financials Corporate Governance

Human CapitalManagement

Talent Management Workforce Process Management Workforce Deployment

Procurement andLogistics Execution

ProcurementSupplier

CollaborationInventory & Warehouse

ManagementOutbound and

Inbound LogisticsTransportationManagement

ProductDevelopment andManufacturing

ProductionPlanning

ManufacturingExecution

ProductDevelopment

Life-Cycle DataManagement

Sales and ServiceSales OrderManagement

Aftermarket Salesand Service

Professional-ServiceDelivery

Global TradeServices

SAP NetWeaver™ People Integration Information Integration Process Integration Application Platform

Financial Supply ChainManagement

Financial AccountingManagementAccounting

Incentive & CommissionManagement

Corporate Services

Real Estate

Management

Project Portfolio

Management

Travel

Management

Quality

Management

Environment,

Health & Safety

Enterprise AssetManagement

Fig. 6: mySAP ERP 2004 Business Map


http://service.sap.com/businessmaps





The Master Guide at hand is structured according to the key functional areas of mySAP ERP

2004, 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 businessprocesses, thus extending across almost all mySAP ERP key capabilities.

Manager Self-Service is designed for use by line managers, team- and project leaders. Itcontains a wide 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,travel management and country-specific processes, like tax forms and pension statements.

• Analytics

Analytics provides functionality for strategic enterprise management, financial analytics,operations analytics and workforce analytics. It assists you in adapting your businessoperations to the results from business analytics, thus improving the decision-makingprocess. At the same time, Analytics helps you optimize business processes across functionsto improve overall business performance.

• Financials

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

With mySAP ERP Financials, your enterprise can realize secure and transparent accounting,

improve its analytical capability, and proactively manage business performance, profit, andgrowth.

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

• Human Capital Management

To compete effectively, you must align all corporate resources – including employees – withbusiness objectives. You must transform traditional HR functions into a comprehensiveprogram for human capital management (HCM).

With mySAP ERP Human Capital Management (mySAP ERP HCM), you can maximize thevalue of your employees and align employee skills, activities, and incentives with business





• Product Development and Manufacturing

Product Development and Manufacturing helps you manage the entire life-cycle of product-related Master Data, including product structures, routings and documents from invention tophase-out. By ensuring immediate access to the most current data, Product Developmentand Manufacturing ensures that your production planning and execution activities proceedsmoothly.

• Sales and Service

Sales and Service addresses the sales- and customer-focused processes that yourenterprise requires to sell products and provide aftermarket services. Sales and Service

enables your sales organization to manage the sales cycle smoothly; it also ensures that yourservice organization maintains customer satisfaction by monitoring service orders and othersubsequent activities.

• Corporate Services

Corporate Services supports all functions that directly impact core business processes or thatcan be applied in several areas – as in the case of Quality Management, for example, whichrelates both to Manufacturing Execution and to Outbound and Inbound Logistics.

How to read the following charts (Software Component Matrix)

The charts displaying the Software Component Matrix of each key capability in the followingsections contain the software components that are either mandatory or optional for thecorresponding key capability. If a component is mandatory for at least one business processof the key capability in question, then it is recorded as such in the chart.

In contrast, if a component is optional for at least one business process, then it is recorded asoptional. In the event that the component is mandatory for at least one process of the key

capability, but merely optional for another, then that component is recorded as bothmandatory and optional.

To avoid confusion, the respective processes are indicated in the “Remarks” column, so thatyou can determine which processes do (or do not) require which software components. Ifnothing is indicated in the “Remarks” column, then the component is either mandatory oroptional for all processes belonging to the corresponding key capability.

System Infrastructure Diagrams (Technical System Landscape)

The technical infrastructure diagrams within each key functional area enable you tounderstand how the different technical components interact, and which dependencies mustbe considered during the implementation phase. They also demonstrate a typical distributionof components among multiple hosts.

The design of an actual system landscape, however, is influenced by individual, customer-specific requirements such as high availability security and performance Such





6.1 End-User Service Delivery

6.1.1 Overview

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 businessprocesses, thus extending over all key capabilities.

From a business management standpoint, customers usually implement ESS and MSStogether, in a common system landscape, since both processes can be integrated in thesame Enterprise Portal. However, it is also possible to implement only one of theseprocesses or implement them on separate systems (for example, due to performance orsecurity considerations).

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 theuser’s portal, enabling managers to find “their” information in “their” portal, in the right place atthe right time.

Using SAP ESS, employees maintain their own personal information and control manyadministrative transactions and other processes handled by HR staff. The goal is tostreamline approval processes and tasks like checking vacation time or choosing benefits.SAP ESS not only grants better access to personal data, it informs employees as they movethrough life and work changes, by combining applications with support information.

Further information about the key capabilities and business processes that comprise this keyfunctional area is available in the mySAP ERP Business Map, located in SAP Service

Marketplace at service.sap.com/businessmaps → Cross-Industry Maps → Enterprise Resource Planning (ERP).

6.1.2 Technical System Landscape

The following diagram shows an example of a full-fledged system landscape for the keyfunctional area End-User Service Delivery of mySAP ERP 2004.







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)

Adobe Reader 6.0.2

Mail Software

Web Browser

J2EE Server


Web AS Java 6.40

Search &

Classification

TREX 6.1

Web AS Java 6.40

EP 6.0 Server

Portal Platform 6.0


BP for ESS

BP for MSS

RDBMS

RDBMS

MSS 100

ESS 100

PCUI_GP 100

XSS

It is not recommended to install all components on one host. Rather, the components can bedistributed among several hosts, as displayed in Figure 7. Several possibilities are availableto distribute the components, so this diagram provides just one example. The distribution

depends on many factors, such as sizing, security, available hardware, and so on. Inpractice, any distribution of components among hosts is possible – from the minimal systemlandscape described in Section 5.2 to a maximum distributed landscape, where everycomponent runs on its own host, or even on multiple hosts. Note that you will additionallyneed a dedicated system for SAP Solution Manager.

For detailed information on technical configuration or the configuration of business scenarios,refer to the Component Installation Guides and the Configuration Documentation in SAPSolution Manager, referred to in Section 4.4. See also the documentation overview provided

in Section 1 of this document.The following software components are either mandatory or optional, as indicated below, forthe technical implementation of End-User Service Delivery. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.

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




y y

Component (cont.) Mandatory Optional Remarks

SAP CCM 1.0 x

SAP Catalog Content Management 1.0can be installed on any system based onSAP Web AS ABAP 6.40. In the aboveexample it is installed in the SRM system.Section 7.2.6

Portal Platform 6.0 x Section 7.1.2

Content Management &Collaboration 6.0 x

Optional component of SAP EnterprisePortal. It can be used for the ManagerSelf-Services. Section 7.1.2

BP for Manager Self-Service (mySAP ERP2004) 60.1 x

Mandatory for Manager Self-Service (WebDynpro Services.) For an explanation ofthe availability of MSS BusinessPackages, see below. Section 7.1.2

BP for Employee Self-Service (mySAP ERP2004) 60.1 x

Mandatory for Employee Self-Service(Web Dynpro Services.) Section 7.1.2

Search & Classification(TREX) 6.1 x Section 7.1.8

SAP Web AS Java 6.40 x Section 7.1.1

SAP XSS 500 x

XSS is absolutely required if you wouldlike to implement the Web Dynpro-basedservices. XSS consists of thesubcomponents MSS 100, ESS 100 andPCUI_GP 100.

Subcomponents ESS 100 and PCUI_GP100 are mandatory for Employee Self-

Service; subcomponents MSS 100 andPCUI_GP 100 are mandatory forManager Self-Service. For moreinformation on XSS refer to Section 7.2.11.

Adobe DocumentServices 1.0 x

Mandatory only, if you want to create newAdobe interactive forms.

SAP BW 3.5 xMandatory for Manager Self-Service, forBW reporting. Section 7.1.4

BI Content Add-on(3.5.2 or 3.5.3) x

Mandatory for Manager Self-Service, forBW reporting. Section 7.1.5

BEx Web ApplicationDesigner (WAD) x Section 7.1.4

Required within WAD to display charts.Mandatory for MSS Team Calendar and





Adobe Reader

x

Mandatory as local installation on theuser’s PC to view PDF files of ESSservices like Total CompensationStatement, Salary Statement, and so on.Mandatory as local installation on theuser’s PC to view Adobe interactive formsfor Personnel Change Requests andRecruiting.

Mail system (forexample, MicrosoftOutlook) x Optional for Employee Self-Service

Before installing the Business Package for MSS you should know which services you wouldlike to use. If required, you can combine the worksets of the Business Packages MSS 60.1(Java Portal Components) with MSS 60.1 (mySAP ERP 2004) in one SAP Enterprise Portal6.0 (see below).

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 toECC 5.0. Refer to SAP Note 752312.

The following table summarizes the existing functionality and worksets of the two MSSBusiness Packages.

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 onAttendance / Absence infotypeinformation), Attendance Details

Attendance: Team Calendar (based on Databaseof Request), Details can displayed from the TeamCalendar




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, CandidateAssessment and Status Overview – Integratedwith E-Recruiting

Reporting: Report selection based onMDT customizing (external ITSneeded), BW Cockpits: Headcount,Overtime and Illness, SkillsManagement

Reporting: Report selection based on MDTcustomizing (internal ITS needed), BW Cockpits:Headcount, Overtime and Illness, SkillsManagement

Compensation: Compensation Planningand Approval, CompensationInformation; Enterprise CompensationManagement (ECM) -> Planning andApproval, Compensation Information

(ECM)

Compensation: not yet available on Web Dynpro

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

Depending on the worksets and functions you would like to provide to your managers, youcan use the new Web Dynpro-based Manager Self-Services [MSS 60.1 (mySAP ERP 2004).]Additionally, for the worksets and functions that are not yet available on Web Dynpro, youcan use the workset of the MSS 60.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(mySAPERP 2004).] In contrast, the Employee Review workset is available with MSS 60.1 (JavaPortal Components.) To provide your managers with the functionality they need you cancreate a manager role in EP 6.0 with the Team Calendar and the Reporting workset from theBusiness Package MSS 60.1 (mySAP ERP 2004) and the Employee Review workset fromthe Business Package MSS 60.1 (Java Portal Component).




You may install and operate XSS (or any of its subcomponents) and Enterprise Portal 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 installXSS and Enterprise Portal on the same J2EE instance, you should consider using SAPNetWeaver Rapid Installer 2.0, which is an installation and configuration wizard described inSection 4.2 of this document. For further information, consult SAP Service Marketplace atservice.sap.com/nw-ri. For more details on SAP XSS, consult Section 7.2.11.

Note that you need SAP ITS 6.20 if you would like to run ITS-based ESS

services. These services are not supported with the internal SAP ITS (whichis part of SAP Web AS 6.40.) Moreover, note that some country-specificscenarios are not available on Web Dynpro in mySAP ERP 2004.

For additional information, see SAP Service Marketplace at

service.sap.com/notes → SAP Note 758035 .

The installation of the Portal Platform is mandatory for End-User Service Delivery, whereas

the installation of the Knowledge Management Platform – including Content Management &Collaboration and Search and Classification (TREX) 6.1 – is optional and depends on theiViews you plan to use.

As for third-party software (for example, Galileo, Amadeus), refer to Section 6.8.5 “TravelManagement.” These components may be required to fill iViews belonging to travel self-service processes.

Valid Combinations and Source Releases

Business Package Manager Self-Service:

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(minimum 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)


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






Component (continued) Release Remarks

SAP BW • SAP BW 2.1C + SupportPackage 09 or above(For this release youalso need an SAPInternet TransactionServer (ITS) on thesame 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

SAP ITS • 6.20 You need SAP ITS for SAP

BW 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 Portal

Component)• 60.1 (mySAP ERP

2004)

This Business Packagerepresents the Java frontend.It runs on the SAP J2EEEngine 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 need

WP-PI 500_46C patch03 or above

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




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

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

Business Package Employee Self-Service:

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

However, be advised that you should plan to replace the ITS-based services by Web Dynpro-based services on a medium-term.

The allowed combinations for ESS depend on a number of factors, for example, the R/3release concerned, and the SAP Enterprise Portal or ESS menu that is used. The table belowprovides an overview of the components and how they are combined.

ESS Release R/3 Release Portal / Menu toaccess ESS

Business packagefrom ServiceMarketplace

ESS 4.5 R/3 4.5 includingITS

ESS Menu (PZM1) Not available

ESS 4.6B R/3 4.6B including

ITS

Enterprise Portal 5.0

or ESS Menu(PZM2)

Business package for

ESS (4.6B)

ESS 4.6C R/3 4.6C includingITS

Enterprise Portal 5.0,Enterprise Portal 6.0or ESS Menu(PZM3)

Business package forESS (4.6C / Enterprise)

ESS Enterprise

ESS 4.6C/ ESS Enterprise

R/3 Enterprise

including ITS

R/3 4.6C includingITS or R/3E t i i l di

Enterprise Portal 5.0,

Enterprise Portal 6.0(SAP Web AS 6.20)or ESS Menu(PZM3)

Enterprise Portal 6.0(SAP W b AS 6 20)

Business package for

ESS (4.6C / Enterprise) Business Package* forESS (4.6C / Enterprise)




Entry by Application Group SAP Application Components SAP ERP SAP ERP 2004 SAP Business Packages .

Note that you can use ESS BP version 50.4 in EP 5.0 and in EP 6.0. ESS BP version 60.1can only work with SAP Enterprise Portal 6.0 in combination with SAP ECC 5.0.

Procurement

Until R/3 Release 4.5, the purchasing function was part of R/3 core delivery and thereforeavailable within Employee Self-Service (ESS). As of R/3 Release 4.6B and above,

purchasing is offered via SAP Business-to-Business Procurement (now SAP SRM Server).To use the purchasing function within ESS, you must first install Business-to-BusinessProcurement (SAP SRM Server 5.0) and then connect to the SRM server from within ESS.You must ensure that the ITS version for both ESS and Business-to-Business is at leastRelease 4.6B. The function that enables users to start a service on a different ITS is offeredas of ITS Release 4.6B. For additional details, consult the SAP ITS documentation.

Industry Solutions

Industry solutions are based on the core R/3 system. Depending on which core R/3 releasethe industry solution is based, you can implement all ESS services available for therespective R/3 core release.

Browser Support

Browser support depends on the SAP R/3 component system under consideration. Forinformation on ESS browser dependency, see SAP Note 380457 (Netscape 6.x Support for

ESS 4.6C) and Note 375809 (Browser Dependencies for ESS.

Implementation Sequence:

If required, review the overall implementation sequence on page 28.




6.2 AnalyticsStrategic Enterprise

ManagementWorkforceAnalytics

OperationsAnalytics

Financial AnalyticsAnalytics

6.2.1 Overview

Analytics provides functionality for strategic enterprise management, financial analytics,operations analytics and workforce analytics. It assists you in adapting your businessoperations to the results from business analytics, thus improving the decision-makingprocess. At the same time, Analytics helps you optimize business processes across functionsto improve overall business performance.



For further information on Analytics, see SAP Service Marketplace atservice.sap.com/businessanalytics Analytics in mySAP ERP in Detail.


The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Analytics of mySAP ERP 2004.

SAP BW

NW BW System

RDBMS

Web AS ABAP 6.40

Web Browser

BI CONT 3.5.2

FINBASIS 300

SEM-BW 400

EP 6.0 Server


BP for BUA

Portal Platform 6 0

Front end



http://service.sap.com/businessanalytics

http://service.sap.com/businessanalytics




It is not recommended to install all components on one host. Rather, the components can bedistributed among several hosts, as displayed in Figure 8. Several possibilities are availableto distribute the components, so this diagram provides just one example. The distributiondepends on many factors, such as sizing, security, available hardware, and so on. Inpractice, any distribution of components among hosts is possible – from the minimal systemlandscape described in Section 5.2 to a maximum distributed landscape, where everycomponent runs on its own host, or even on multiple hosts. Note that you will additionallyneed a dedicated system for SAP Solution Manager.

SAP Business Warehouse is an integral part of the SAP NetWeaver 2004 ABAP Stack anddoes not need to be installed explicitly. To deploy an SAP NetWeaver System as a Business

Information Warehouse system, you are required to install and activate the BI Content add-on. This component is installed using the SAINT tool.

If you plan to use the Enterprise Portal 6.0, the following additional components are available:

Content Management & Collaboration 6.0

Search and Classification (TREX) 6.1

BP for Business Unit Analyst 60.1 (BUA)

For detailed information on technical configuration or the configuration of business scenarios,refer to the Component Installation Guides and the Configuration Documentation in SAPSolution Manager, referred to in Section 4.4. See also the documentation overview providedin Section 1 of this document.

SAP BW 3.5 and PI Basis 2004.1 are part of the NetWeaver ABAP Stack, i.e. they areincluded in the upgrade or installation. You also need SAP Internet Graphics Services 6.40for the involved processes. This component is also included in SAP Web AS ABAP 6.40.Note that no separate SAP Web AS Java is required (in addition to the one required for SAP

Enterprise Portal.)

SEM-BW and FINBASIS demand a minimum SP-stack of 07 (consult the SAP Release andInformation Note 760874.) Furthermore, a minimum of NW stack 11 for SAP Web AS ABAP6.40 is required. For more information on SAP’s Stack Strategy, see SAP ServiceMarketplace at service.sap.com/sp-stacks .

For SEM 4.0 installation-specific information, review SAP Note 724418.


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




6.2.3 Strategic Enterprise ManagementThe following software components are either mandatory or optional, as indicated below, forthe technical implementation of Strategic Enterprise Management. (References tocomponent-specific information are displayed in italics .) Section 6 explains how to read thechart.

Component Mandatory Optional Remarks

SAP Web AS ABAP 6.40 x Section 7.1.1

SAP ECC 5.0 x x

The process "Legal & ManagementConsolidation" can be implemented inone of two ways:1) Using OLAP-based SEM-BCS, SAPECC 5.0 is not required here.2) Using R/3-based EC-CS, SAP ECC5.0 is mandatory in this case.For some implementations, SAP ECC5.0 is therefore mandatory, while for

others it remains optional. Section 7.2.1

SAP BW 3.5 xPart of SAP NetWeaver ABAP Stack.Section 7.1.4

BI Content Add-on(Release 3.5.2 or 3.5.3) x Section 7.1.5

FINBASIS 300 x Section 7.2.5

SEM-BW 4.0 x Section 7.2.4


Content Management &Collaboration 6.0 x Section 7.1.2

TREX 6.1 x Section 7.1.8

Internal SAP ITS (part ofSAP Web AS 6.40) x

Optional for “Legal & ManagementConsolidation.” See SAP Service Marketplace at service.sap.com/sap-its.


SAP IGS 6.40 xRequired within WAD to display charts.Section 7.1.11

SAP GUI 6.20 or 6.40 x

Required to display ABAP Dynproscreens (as in the administrator’s PC.)Section 7.1.10 Optional for the Balanced Scorecard










6.2.4 Financial AnalyticsThe following software components are either mandatory or optional, as indicated below, forthe technical implementation of Financial Analytics. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.



SAP ECC 5.0 x Section 7.2.1

SAP BW 3.5 x Section 7.1.4 BI Content Add-on (Release3.5.2 or 3.5.3) x Section 7.1.5

FINBASIS 3.0 x Section 7.2.5



Content Management &Collaboration 6.0 x Section 7.1.2

BP for Business Unit Analyst60.1 x Section 7.1.2


SAP IGS 6.40 xRequired within WAD to displaycharts. Section 7.1.11

SAP GUI 6.20 or 6.40 x Section 7.1.10

Power SIM (Simulation) x Third-party softwareOros ABC (SAS) x Third-party software

6.2.5 Operations Analytics

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Operations Analytics. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x Section 7.1.4







6.2.6 Workforce Analytics

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Workforce Analytics. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x Section 7.1.4 BI Content Add-on (Release3.5.2 or 3.5.3) x Section 7.1.5


Portal Platform 6.0 xMandatory, if Business Packagesare used. Section 7.1.2

BP for BUA x Section 7.1.2

BEx Web Application

Designer (WAD) x Section 7.1.4








6.3 Financials

ManagementAccounting

FinancialAccounting

Financial SupplyChain Management

CorporateGovernance

Financials

6.3.1 Overview




The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Financials of mySAP ERP 2004.

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 CreditManagement

BP for Payer Direct

Portal Platform 6.0

Web AS Java 6.40

J2EE Server

RDBMS

FSCM Biller Direct 3.0

Web AS Java 6.40

RDBMS

RDBMS

XI Content forFINBASIS and PI

RDBMS

Front end






the SAP Web AS (Java) of the SAP ECC system; if you only plan to deploy FSCM BillerDirect 3.0. SAP Business Warehouse is an integral part of the SAP NetWeaver 2004 ABAP

Stack and does not need to be installed explicitly. To deploy an SAP NetWeaver System as aBusiness Information Warehouse system, you are required to install and activate the BIContent add-on. This component is installed with the SAINT tool.


6.3.3 Financial Supply Chain Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Financial Supply Chain Management. (References tocomponent-specific information are displayed in italics .) Section 6 explains how to read thechart.


SAP Web AS ABAP 6.40 x x Section 7.1.1 SAP ECC 5.0 x Section 7.2.1

SAP BW 3.5 x x

Mandatory for “Cash & LiquidityManagement”; relevant (butoptional) only for “CreditManagement,” “DisputeManagement”, “CollectionsManagement” and “Treasury &Risk Management.” Section 7.1.4

BI Content Add-on (Release3.5.2 or 3.5.3) x x

Relevant (but optional) only for“Credit Management,” “DisputeManagement”, “CollectionsManagement” and “Treasury &Risk Management.” Section 7.1.5

FINBASIS 3.0 x

Mandatory for “CreditManagement”, “DisputeManagement” and “CollectionsManagement.” Section 7.2.5

SEM-BW 4.0 x

Relevant (but optional) only for“Cash & Liquidity Management.” Section 7.2.4

SAP Web AS Java 6 40 x

Mandatory for “ElectronicPresentment & Payment.”Section 7 1 1






Portal Platform 6.0 x

Relevant (but optional) only for“Credit Management” and“Electronic Presentment &Payment.” Section 7.1.2

SAP XI 3.0 x xMandatory only for “CreditManagement.” Section 7.1.3

XI Adapter Framework 3.0 xRelevant (but optional) for “CreditManagement.” Section 7.1.3

XI Content for FINBASIS 300and PI_2004_1_500 x x

Mandatory only for “CreditManagement” Section 7.1.3


Using SAP Exchange Infrastructure is mandatory for Credit Management. For all otherprocesses in this key functional area, it is optional. SAP XI is used for outbound XML-based

messaging and / or to establish a connection to non-SAP planning or execution systems.

With the role of an Integration Server, SAP Exchange Infrastructure normally requires adedicated SAP Web Application Server. For additional information, consult Section 4.1.

The SAP XI system must be on Unicode. For more information, refer to SAP ServiceMarketplace at service.sap.com/nw04installation SAP XI .

6.3.4 Financial Accounting

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Financial Accounting. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.





BI Content Add-on (Release3.5.2 or 3.5.3) x Section 7.1.5


SAP IGS 6 40Required within WAD to displaycharts Section 7 1 11






6.3.5 Management AccountingThe following software components are either mandatory or optional, as indicated below, forthe technical implementation of Management Accounting. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.





BI Content 3.5.2 Add-on x Section 7.1.5

Bex Web ApplicationDesigner (WAD) x Section 7.1.4




6.3.6 Corporate Governance

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Corporate Governance. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.


SAP Web AS ABAP 6.40 x

System Audit Part of the AIS iscontained in SAP Web AS 6.40starting with SP5. Section 7.1.1


SAP BW 3.5 x x

Mandatory for “Business RiskManagement,” only optional for“Management of InternalControls” and “Transparency forBasel II.” Section 7.1.4

FINBASIS 3.0 x x

Mandatory for "Management ofInternal Controls" and optional for"Transparency for Basel II."Section 7.2.5 Mandatory for "Business RiskManagement" and optional for






Portal Platform 6.0 x

Optional for “Management ofInternal Controls” and “WhistleBlower Complaints.” Section 7.1.2


*) Note that Corporate Governance is the only key capability explicitly requiring BI Content3.5.3. Nevertheless, this component is only optional.






6.4 Human Capital Management

6.4.1 Overview




The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Human Capital Management of mySAP ERP 2004.

Front End (PC)

AuthoringEnvironment

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

Front End (PC)

LearnerEnvironment

Web Browser

LSOOP 300

Offline Player

Talent Management Workforce Process Management Workforce DeploymentHuman CapitalManagement






Neither Content Player (LSOCP) nor XSS have persistent data. The database displayed inthe figure belongs to SAP J2EE 6.40 (SAP Web AS Java 6.40.)


6.4.3 Talent Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Talent Management. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.




E-Recruiting 3.0 x xMandatory only for “Recruiting.”Section 7.2.7

Learning Solution (LSOFE300) x x

Mandatory only for “EnterpriseLearning.” Section 7.2.7

SAP Web AS Java 6.40 x xOnly mandatory for “EnterpriseLearning.” Section 7.1.1

Content Player (LSOCP) 3.0 x xOnly mandatory for “EnterpriseLearning.” Section 7.2.7

SAP BW 3.5 x x

Optional for all Employee Life-Cycle Management processes.Section 7.1.4


Optional for all Employee Life-Cycle Management processes.Section 7.1.5




BP for Learning Solution x See information below and Section 7.1.2

Content Management &Collaboration (CMC) 6.0 x x

Mandatory for “Recruiting”;optional for “EnterpriseLearning.” Section 7.1.2

M d f “R i i ”




6.4.4 Workforce Process Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Employee Transaction Management. (References tocomponent-specific information are displayed in italics .) Section 6 explains how to read thechart.




SAP BW 3.5 x Section 7.1.4 BI Content 3.5.2 Add-on x Section 7.1.5



SAP Web AS Java 6.40 xRequired for the SAP J2EEApplications. Section 7.1.1

XSS 500 x

Required, if self-serviceapplications are used. Refer tothe XSS installation options inSection 6.1.2. For morecomponent information seeSection 7.2.11


BPs for MSS and ESS x

Required, if self-serviceapplications are used. Refer to

Sections 6.1.2 and 7.1.2

SAP MI Server 2.5 (includedin SAP Web AS 6.40) x

Middleware server required ifmobile scenarios are planned.Section 4.1

SAP MI Client 2.5 xInstalled on the mobile clients.Section 4.1

Mobile Time Sheet (MTS) 1.6 x Section 7.2.14-5 Mobile Travel Expenses(MTR) 1.6 x Section 7.2.15

Mobile Development Kit 2.5 x Section 4.1





6.4.5 Workforce DeploymentThe following software components are either mandatory or optional, as indicated below, forthe technical implementation of Workforce Deployment. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.




Portal Platform 6.0 x Section 7.1.2 BP for Employee Self-Service60.1 x

Refer to Sections 6.1.2 and7.1.2

SAP Mobile InfrastructureServer 2.5 x Section 4.1

MI Client 2.5 x Section 4.1

Mobile Development Kit 2.5 x Section 4.1

Mobile Time Sheet (MTS) 1.6 x Section 7.2.14-5

Mobile Travel Expenses(MTR) 1.6 x Section 7.2.15


You should also consider using SAP xApp Resource and Program Management (SAPxRPM), which unifies project management, time tracking, financial data, and employee skillsinformation in a portfolio management paradigm. For more information, see SAP ServiceMarketplace at service.sap.com/xapps.

Implementation Sequence:If required, review the overall implementation sequence on page 28.


http://service.sap.com/xapps

http://service.sap.com/xapps



6.5 Procurement and Logistics Execution

6.5.1 Overview




The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Procurement and Logistics Execution of mySAP ERP 2004.

SAP BW

NW BW System

RDBMS

Web AS ABAP 6.40

BI CONT 3.5.2

Front End (PC)

SAP GUI

Adobe Reader 6.0.2

Mail Software

Web Browser

J2EE Server

SAP XSS 500

RDBMS


Web AS Java 6.40

Search &Classification

SAP XI

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 ExternalProcurement

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

Procurement andLogistics Execution

Procurement SupplierCollaboration

Inventory & WarehouseManagement

Outbound andInbound Logistics

TransportationManagement






Certain business processes require the use of Internet Transaction Server6.20. For more information on this topic, see SAP Service Marketplace at

service.sap.com/notes → SAP Note 741821.

For detailed information on technical configuration or the configuration of business scenarios,refer to the Component Installation Guides or the Configuration Documentation in SAPSolution Manager, referred to in Section 4.4. See also the documentation overview providedin Section 1 of this document.

6.5.3 Procurement

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Procurement. (References to component-specific informationare displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x xMandatory only if OperationsAnalytics is used. Section 7.1.4


Mandatory only if OperationsAnalytics is used. Section 7.1.4

BEx Web Application

Designer (WAD) x

Mandatory only if Operations

Analytics is used. Section 7.1.4


SAP SRM Server 5.0 x x

Mandatory only for “Self-ServiceRequisitioning” and “Role:Purchasing Agent.” Section 7.2.8

SAP Catalog ContentManagement 1.0 x

Optional for “Self-ServiceRequisitioning.” Section 7.2.6

SAP IPC 4.0 for SRM xOptional for “Self-ServiceRequisitioning.” Section 7.2.10

Portal Platform 6.0 x x

Mandatory only for Role:“Purchasing Agent”Section 7.1.2







BP for Manager Self-Service x

Optional for “Self-ServiceRequisitioning” (within MSS).Section 7.1.2

BP for External Procurement x x

Mandatory only for Role:“Purchasing Agent.”Section 7.1.2

SAP Web AS Java 6.40 x xRequired for the SAP J2EEapplications. Section 7.1.1

SAP XSS 5.0 x

Optional for “Self-ServiceRequisitioning” (withinESS/MSS.) Section 7.2.11

Adobe Document Services1.0 x

SAP XI 3.0 (part of SAP WebAS 6.40) x x

Mandatory only for SupplierCollaboration Scenario for MROmaterial. Section 7.1.3

XI Content for SAP_APPL

500, SRM_SERVER 5.0,CCM 1.0 (with latest SPs) x

Optional for “Self-ServiceRequisitioning.” Section 7.1.3

SAP ITS internal or external x x

Mandatory only for “Self-ServiceRequisitioning” (withinESS/MSS). See Section 7.1.9 and SAP Service Marketplace at service.sap.com/sap-its.


For further information regarding the business processes that involve SAP SRM Server,consult the SAP SRM Master Guide at service.sap.com/instguides mySAP

SRM Using SAP SRM Server 5.0 .

6.5.4 Supplier Collaboration

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Supplier Collaboration. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.


SAP W b AS ABAP 6 40 S ti 7 1 1












SAP SRM Server 5.0 x Section 7.2.8

SAP Catalog ContentManagement 1.0 x x Section 7.2.6

SAP IPC 4.0 for SRM x x Section 7.2.10


Content Management &Collaboration (CMC) 6.0 x Section 7.1.2

BP for Supplier Collaboration x

SAP XI 3.0 (part of SAP WebAS 6.40) x x

Required for the SupplierCollaboration Scenario for MROmaterial. Section 7.1.3

XI Content for SAP_APPL500, SRM_SERVER 5.0,CCM 1.0 (with latest SPs) x Section 7.1.3

cProject Suite 310 (cFolders) x

Required for DevelopmentCollaboration. A dedicated serverfor cFolders is generally used. Section 7.2.9


6.5.5 Inventory & Warehouse Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Inventory & Warehouse Management. (References tocomponent-specific information are displayed in italics .) Section 6 explains how to read thechart.





BI Content Add on (Release Mandatory only if Operations





Web SAP Console x xMandatory only if RadioFrequency (RF) transactions formobile data entry are used.


6.5.6 Outbound and Inbound Logistics

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Outbound and Inbound Logistics. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x x

Mandatory only if Operations

Analytics is used. Section 7.1.4 BI Content Add-on (Release3.5.2 or 3.5.3) x x


BEx Web ApplicationDesigner (WAD) x x



SAP IGS 6.40 x

Required within WAD to display

charts. Section 7.1.11

Web SAP Console x xMandatory only if RadioFrequency (RF) transactions formobile data entry are used.


RFID-enabled Logistics Processes

Radio frequency identification (RFID) is a powerful new technology that is helping companies

to improve visibility into their inventory data and increase accuracy across supply chainnetworks. Moreover, by using RFID your enterprise obtains execution benefits such asprocess automation and hands-free work. When RFID tags are attached to products, boxes,and pallets, the items can be followed automatically as they move, providing a real-time andaccurate view of inventory – and greatly enhancing the ability to track and trace goods alongthe supply chain The end result: reduced costs faster response to changing customer




The following software components are either mandatory or optional, as indicated below, forthe technical implementation of RFID-enabled Logistics Processes. (References to

component-specific information are displayed in italics .) Section 6 explains how to read thechart.



OLTP system x

On-Line Transaction Processingsystem (for example, SAP R/3system, SAP R/3 Enterprise,SAP ECC) that is used in the

RFID-enabled supply chainexecution environment asbackend system.

SAP SCM 4.1 EM (EventManager) x

SCM Server is part of the mySAPSupply Chain Managementsolution suite. It requires aseparate license. SAP SCM EMis an integrated component ofSAP SCM that offers the

possibility to process applicationobjects in various applicationsystems and thereby to trackevents for individual objects,processes or parts of thesethroughout the entire supplychain.

SAP Web AS Java 6.40 x

Required for “OutboundProcessing /RFID”. Section

7.1.1

Auto ID Infrastructure (AII) x

Middleware for RFID andautomatic identificationintegration. Required for“Outbound Processing /RFID”.Note that AutoID Infrastructure isnot part of the mySAP ERPshipment. It requires aseparate license.

Auto ID UI 2.1 x

SAP XI 3.0 (part of SAP WebAS 6.40) x

Mandatory only for “OutboundProcessing /RFID”. Section 7.1.3 Mandatory only for “Outbound


M Fi d h SAP RFID M G id




Management. Find the SAP RFID Master Guide at service.sap.com/instguides SAP Components SAP RFID Solution Package Using SAP Auto-ID Infrastructure .

6.5.7 Transportation Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Transportation Management. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.


SAP Web AS ABAP 6.40 x Section 7.1.1 SAP ECC 5.0 x Section 7.2.1

SAP BW 3.5 x


BI Content Add-on (Release3.5.2 or 3.5.3) x


BW Front end (BEX, WebInterface Builder) x


SAP ITS (internal or external) x

Required for the WebTransactions “Tendering” and“Transportation Planning incorporation with Ext. ServiceProviders.” Section 7.1.9










6.6 Product Development andManufacturing

6.6.1 Overview




The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Product Development and Manufacturing of mySAP ERP 2004.

SAP BW

NW BW System

Web AS ABAP 6.40

Search &

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

ContentManagement&

BP for Products

BP for Assets

BP for Project &

Design Collaboration

RDBMS

NW MI System

Web AS

ABAP + Java 6.40

Frontend

cFolders Server

CPROJECTS310_640

Web AS ABAP

6.40

RDBMS

RDBMS

CPROJECTS 310_640

WFM Core 110

Product Developmentand Manufacturing

Enterprise AssetManagement

ProductDevelopment

ProductionPlanning

ManufacturingExecution

Life-Cycle DataManagement


component runs on its own host or even on multiple hosts Note that you will additionally





component runs on its own host, or even on multiple hosts. Note that you will additionallyneed a dedicated system for SAP Solution Manager.

The Mobile Asset Management scenario requires SAP Mobile Infrastructure 2.5 (server andclient.) Technically speaking, SAP Web AS of the SAP ECC system could also work as SAPMobile Infrastructure. On the other hand, planning a dedicated SAP Web Application Serverfor the mobile infrastructure has advantages. For more information, see Section 4.1. MAM2.5 depends on Plug-in 2004.1, which contains application-related business logic andcustomizing.


6.6.3 Production Planning

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Production Planning. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x xRequired only if OperationsAnalytics is used. Section 7.1.4

BI Content 3.5.2 Add-on x x Section 7.1.5 BEx Web ApplicationDesigner (WAD) x x

Required only if OperationsAnalytics is used. Section 7.1.4




6.6.4 Manufacturing Execution

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Manufacturing Execution. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.


SAP Web AS ABAP 6 40 x Section 7 1 1





BP for Manufacturing 60.1 xRequired for role “PlantManager.” Section 7.1.2

SAP ITS 6.20 x Section 7.1.9


6.6.5 Enterprise Asset Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Enterprise Asset Management. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.




SAP CCM 1.0 x

Relevant (but optional) only for“Maintenance Execution.”Section 7.2.6




BEx Web ApplicationDesigner (WAD) x



FINBASIS 300 xTechnical requirement for SEM-BW 400. Section 7.2.5

SEM-BW 400 x Section 7.2.4

SAP MI Server (SAP Web ASABAP + Java 6.40) x

Dedicated Middleware server.Required for MAM. Section 7.1.1

MI Client 2.5 x

Required only for MAM. Section

4.1 Mobile Asset Management(MAM) 2.5 x

Optional for “MaintenanceExecution.” Section 7.2.16

Mobile Development Kit 2.5 xRequired only for MAM. Section 4.1




6.6.6 Product DevelopmentThe following software components are either mandatory or optional, as indicated below, forthe technical implementation of Product Development. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.

Component Mandatory Optional RemarksSAP Web AS ABAP6.40 x Section 7.1.1

SAP ECC 5.0 x Section 7.2.1 cProject Suite 3.10 x x Section 7.2.9

WFM Core 110_640 x WFM Core requires a separate license.SAP Content Server6.30 x

Refer to SAP Service Marketplace atservice.sap.com/contentserver


BI Content Add-on(Release 3.5.2 or 3.5.3) x Section 7.1.5

SAP ITS x Section 7.1.9


Content Management &Collaboration (CMC) 6.0 x Section 7.1.2


Note that cProject Suite consists of the application components cProjects and cFolders. The

technical name of cProject Suite is CPROJECTS. Depending on how you set up your system,you would activate either cProjects or cFolders.

Find more information on Collaborative Product Development in Cross-Enterprise Processesunder service.sap.com/plm Life-Cycle Collaboration and Analytics Design Collaboration .

6.6.7 Life-Cycle Data Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Life-Cycle Data Management. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.


http://service.sap.com/contentserver



http://service.sap.com/plm






Content Management& Collaboration (CMC)6.0 x Section 7.1.2

BP for Product, Asset,Project & DesignCollaboration x Section 7.1.2

TREX 6.1 xRelevant (but optional) only for“Document Management.” Section 7.1.8

SAP Content Server6.30

x

Relevant (but optional) for “DocumentManagement.” For componentinformation, see SAP ServiceMarketplace at service.sap.com/contentserver.

EH&S WWI /WindowsWord Integration x

Frontend component. Mandatory onlyfor “Recipe Management.”

EH&S Expert 2.1 x

Frontend component. Mandatory only

for “Recipe Management.”

ECL Viewer(Engineering Client)

x

Optional for DMS (“DocumentManagement”) and cFolders (“DesignCollaboration”). Component versionvaries, depending on the platform used.For component information, see themySAP PLM Master Guide in SAPService Marketplace at

service.sap.com/plm-inst →

using cProject Suite 3.10 .

SAP Easy DocumentManagement 3.0 x

Relevant (but optional) only for“DocumentManagement”. See SAP Note 668100 and SAP Library at help.sap.com

DMS Connector forKM 60.1 x

Relevant (but optional) only for“Document Management” (DMS).








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

http://help.sap.com/






6.7 Sales and Service

6.7.1 Overview




The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Sales and Service of mySAP ERP 2004.

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

FSCM Biller Direct 3.0

IPC Web App. 4.0

RDBMS

Web Browser

ProductCatalog

Files

Web Server

Web ServerPlug-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.40Front end

RDBMS

Sales andService

Sales OrderManagement

AftermarketSales and

Service

Professional-ServiceDeliver

Global TradeServices

Incentive & CommissionManagement


practice, any distribution of components among hosts is possible – from the minimal system





landscape described in Section 5.2 to a maximum distributed landscape, where every

component runs on its own host, or even on multiple hosts. Note that you will additionallyneed a dedicated system for SAP Solution Manager.

For detailed information on technical configuration or the configuration of business scenarios,refer to the Component Installation Guides or the Configuration Documentation in SAPSolution Manager, referred to in Section 4.4. See also the documentation overview providedin Section 1 of this document.

6.7.3 Sales Order Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Sales Order Management. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x x

Mandatory only for “Role: InternalSales Representative” and ifOperations Analytics is used.Section 7.1.4

BI Content 3.5.2 Add-on x x




SAP IGS 6.40 x xRequired within WAD to displaycharts. Section 7.1.11

SAP Web AS Java 6.40 x x

Mandatory only for "InternetSales with mySAP ERP” and ifthe Portal Platform is used.

Section 7.1.1

Internet Sales WAC 4.0 x

Mandatory only for “InternetSales with mySAP ERP.” Section 7.2.12 Optional for “Internet Sales in





SAP Direct Store Delivery2004 (using MDSD 2.0) x

Optional for “Field Sales.” Massshipment of MDSD is plannedfor Q3 2005. See Sections 7.2.18 and 7.5.7.1

SAP ITS 6.20 x xRequired for “Role: Internal SalesRepresentative.” Section 7.1.9

Portal Platform 6.0 x x

Mandatory only for “Role: InternalSales Representative.” Optionalfor all other processes. Section 7.1.2

BP for Sales 60.1 x xRequired for “Role: Internal SalesRepresentative.” Section 7.2.1

TREX 6.1 xOptional for “Internet Sales withmySAP ERP” only. Section 7.1.8


SAP Direct Store Delivery

SAP Direct Store Delivery (DSD) is a business process often used in the Consumer Productsindustry (CP) to sell and distribute goods directly to the customer’s store bypassing theretailer’s warehouses.

The Manufacturer gets in direct contact with the customer’s store at the Point-of-Sale. He canuse this contact to improve customer retention and customer relationship through personal

service. Besides this, he can realize additional sales opportunities and obtain first handinformation about the market.

With SAP DSD, CP customers have a great opportunity to position their brand againstcompetitors due to the direct contact with customers such as retailers, restaurants and pubs.

SAP DSD enables quick distribution of beverages and fresh products such as bread, flowers,newspapers and leads to higher margins for the consumer products company than theindirect sales scenario.

Key success factors for the high margins in SAP DSD are:

• An integrated mobile solution to support sales and distribution activities of salesrepresentatives or delivery personnel.

• Excellent alignment between sales force and distribution through integratedscheduling


and order processing, invoicing and payment collection, recording driver expenses and on-truck inventory management It effectively manages transactions in a closed loop cycle



truck inventory management. It effectively manages transactions in a closed-loop cycle.

The following diagram provides an overview of the system landscape for SAP Direct StoreDelivery.

SAP ECC 5.0

Web AS ABAP 6.40

(including MI Server 2.5)

RDBMS

SAP ECC 5.0, Stack 05(including

DSD Connector,

DSD Connector Cockpit,DSD Pricing Data Extractor)

ECC System

J2EE Server

RDBMS

DSD AdminConsole *

Web AS Java 6.40

Mobile Device

MDSD 2.0 *(Front end)

SAP MI Client 2.5

http / https

RFC

DB2

*) Included in SAP Mobile DSD 2.0

The DSD Connector and the DSD Connector Cockpit, as well as the DSD Pricing DataExtractor, are integral parts of SAP ECC 5.0. More precisely, the DSD Pricing Data Extractor

is contained in PI 2004.1. Therefore, you do not have to install these componentsadditionally. Prerequisite is, however, that your SAP ECC 5.0 system is at least on supportpackage stack 5 level (see also service.sap.com/sp-stacks.)

Fig. 14: Sample System Landscape for SAP Direct Store Delivery

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of SAP Direct Store Delivery. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.



SAP ECC 5.0 x Section 7.2.1 DSD connector, DSDconnector cockpit x

Contained in ECC 5.0 as from Support Package Stack 5

DSD Pricing Data Extractor x Contained in PI 2004 1






6.7.4 Aftermarket Sales and Service

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Aftermarket Sales and Service. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.



SAP CCM 1.0 x Section 7.2.6

SAP BW 3.5 x x

For some implementations, thiscomponent is mandatory, whilefor others it is optional.1) If Operations Analytics is used,then this component ismandatory.2) If Operations Analytics is notused, then this component isoptional.Section 7.1.4 .

BI Content Add-on (Release

3.5.2 or 3.5.3) x x

For some implementations, thiscomponent is mandatory, whilefor others it is optional.1) If Operations Analytics is used,then this component is

mandatory.2) If Operations Analytics is notused, then this component isoptional.Section 7.1.5 .

BW Front end (BEX, WebInterface Builder)

x x

For some implementations, thiscomponent is mandatory, whilefor others it is optional.1) If Operations Analytics is used,

then this component ismandatory.2) If Operations Analytics is notused, then this component isoptional.


6.7.5 Professional Service Delivery



y

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Professional Service Delivery. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.




SAP BW 3.5 x Section 7.1.4 BI Content Add-on (Release3.5.2 or 3.5.3) x Section 7.1.5 BW Front end (BEX, WebInterface Builder)

xSection 7.1.4 .

cProject Suite 310 x

Required for ‘Project Planningand Scoping’ and ‘ProjectResource Planning’. Section 7.2.9

WFM CORE 110_640 x

Optional for 'Project Planning andScoping' and 'Project ResourcePlanning'. WFM CORE requires aseparate license. SAP Note 718626



6.7.6 Global Trade Services

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Global Trade Services. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.



SAP Global Trade Services (forSAP Web AS 6.40) is an add-onthat can be installed on the SAP


Component (continued) Mandatory Optional Remarks

Portal Platform 6 0 x Section 7 1 2





6.7.7 Incentive & Commission Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Incentive & Commission Management. (References tocomponent-specific information are displayed in italics .) Section 6 explains how to read thechart.






BEx Web Application

Designer (WAD) x Section 7.1.4








6.8 Corporate Services

6.8.1 Overview




The following diagram shows an example of a full-fledged system landscape for the keyfunctional area Corporate Services of mySAP ERP 2004.

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


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

NW KW System

Web AS Java


TREX 6.1

SAP Gateway

RDBMS

Optional

RDBMS

cFolders Server

CPROJECTS310_640

Web AS ABAP6.40

RDBMS

SAP BusinessConnector

SAP BC 4.7

WFM Core 110

CPROJECTS 310_640

CorporateServices

Real EstateManagement

Project PortfolioManagement

TravelManagement

Environment,Health & Safety

QualityManagement


If you plan to use Enterprise Portal, the following additional Business Packages are available,which may be relevant for this key functional area: BP for Products, Assets and Projects and





Design Collaboration.For detailed information on technical configuration or the configuration of business scenarios,refer to the Component Installation Guides or the Configuration Documentation in SAPSolution Manager, referred to in Section 4.4. See also the documentation overview providedin Section 1 of this document.

6.8.3 Real Estate Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Real Estate Management. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.





BI Content Add-on (Release3.5.2 or 3.5.3) x Section 7.1.5 BEx Web ApplicationDesigner (WAD) x Section 7.1.4




6.8.4 Project Portfolio Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Project Portfolio Management. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.


SAP Web AS ABAP 6.40 x x Section 7.1.1 Required for SAP Project System(“Project Planning”, “ProjectExecution”, “ProgramManagement” and “Interfaces”)











Portal Platform 6.0 x Section 7.1.2 Content Management &Collaboration (CMC) 6.0 x Section 7.1.2

SAP MI Server 2.5 x Section 4.1

SAP MI Client 2.5 x Section 4.1

Mobile Travel Expenses(MTR) 1.6 x Section 7.2.14-15

Mobile Development Kit 2.5 x


Galileo Gateway Software x Mandatory only if Galileo is used.

Amadeus Proprinter Software x Relevant (but optional) only ifAmadeus is used.

Amadeus JCO SAP GatewayAdd-on x

Mandatory only if Amadeus isused

6.8.6 Environment, Health & Safety

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Environment, Health & Safety. (References to component-specific information are displayed in italics .) Section 6 explains how to read the chart.








Mandatory only if OperationsAnalytics is used. Section 7.1.4 Required within WAD to display


6.8.7 Quality Management



6.8.7 Quality Management

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Quality Management. (References to component-specificinformation are displayed in italics .) Section 6 explains how to read the chart.




cProject Suite 3.10 x x

Mandatory only for “QualityEngineering (APQP).”Section 7.2.9

SAP BW 3.5 x x Mandatory only if OperationsAnalytics is used. Section 7.1.4





SAP IGS 6.40 x Required within WAD to displaycharts. Section 7.1.11


SAP KW 7.0 x

Relevant (but optional) only for“Quality Engineering (QualityManual).” Component is part of SAP Web AS ABAP. Section 7.1.7

SAP Easy DocumentManagement 3.0 x

Relevant (but optional) only for

“QualityEngineering (Quality Manual).”See SAP Note 668100 and SAP Library at help.sap.com

SAP ITS x Section 7.1.9




7 Information on Software Components






This section provides information on the most important software components of mySAPERP 2004.

Only a subset of these components is required for the implementation of aspecific business scenario or process. For a key capability-specific overviewof components, consult the software component matrix of each key functionalarea.

7.1 SAP NetWeaver 2004 Components

If you would like to know more about SAP NetWeaver and its components, we recommendthat you read the corresponding Master Guide, which is located in SAP Service Marketplaceat sap.com/nw04installation Installation .

7.1.1 SAP Web Application Server 6.40

Definition

SAP Web Application Server (SAP Web AS) is the application platform of SAP NetWeaverand with this of the mySAP Business Solutions. It provides the technological foundation for allother SAP components.

For SAP Web AS, different basic system variants exist. It can be installed as ABAP + Java

system , as ABAP system or as Java system . The difference between these system variantsis that you can either operate both the ABAP stack and the Java stack, only the ABAP stackor only the Java stack in your SAP Web AS.

Until SAP R/3 4.6D, SAP Web Application Server was named SAP Basis.

Use

Since SAP Web AS contains the ABAP stack, the Java stack or both stacks, it provides aruntime environment for ABAP and/or Java applications.

SAP Web AS includes a platform for quickly developing and deploying dynamic andcollaborative Web applications or other thin-client applications (WAP, PDA, and so on) andincludes all proven SAP programming models and technologies. With SAP Web AS, SAPnatively supports open Internet standards, including such protocols as HTTP, HTTPS, andSMTP ll I t t d t t d d lik HTML d XML


Building Blocks





SAP Web AS 6.40 consists of the following main building blocks: Central instance Central service instance

The central services instance forms the basis of communication and synchronization forthe Java cluster.

Database instance

SAP Web AS Java has a separate database schema. As a result, a database instance isalso a mandatory installation component for the installation of an SAP Web AS Java

system.

For the installation of an SAP Web AS ABAP+Java system, both the ABAP and the Javaschema get installed in the same database.

Exception:If your SAP system is running on Informix, a separate MaxDB or IBM DB2UDB for UNIX and Windows is required for the Java database schema.

Dialog instances, if required

Dialog instances are SAP instances that include only:

• Dispatcher, IGS, and CCMS agents

• SAP Web AS ABAP + Java system and SAP Web AS Java system: Java serverprocesses

• SAP Web AS ABAP + Java system and SAP Web AS ABAP system: gatewayand certain ABAP work processes (dialog, batch, spool, or update)

Dialog instances are installed on application servers.

The dialog instances of SAP Web AS Java systems are called Java dialog instances.

SAP GUI

See separate component description in Section 7.1.10.

Related Documentation:

The installation guides for SAP Web AS 6.40 are located in SAP Service Marketplaceat service.sap.com/nw04installation Installation . Refer also to the SAP


while the Knowledge Management platform makes it possible to provide access todocuments and multimedia objects that are stored in an organization's distributed documentrepositories. Collaboration enables virtual teams to work together in synchronous and





p g yasynchronous ways, directly within SAP Enterprise Portal.

SAP Enterprise Portal provides a role-based, secure and web-based interface to any kind ofinformation, application and services. To run the portal, you need a standard browser on thedesktop; no additional software components are required.

As part of SAP Enterprise Portal, the Portal Infrastructure provides a secure access to anykind of structured data coming from any kind of business applications, such as SAP, non-SAP, data warehouses, or databases.

As a key technology of the Portal Infrastructure, iViews allow an access for reading purposesor for carrying out an operation, such as submitting a form for supplies. A set of portalservices is provided to enable iViews to interact with each other such as portal navigation (forexample, Dynamic Navigation or the patented Drag&Relate technology), portal eventing, orWorkProtect mode.

Portal roles structure and deliver targeted content to each end user. Thanks to the role-baseduser interface, a company can structure its business processes and deliver business contentaccording to the needs of certain user groups. Besides the role concept, Portal Infrastructureprovides additional personalization features such as iView, page or layout personalization.

To create and develop portal content, SAP provides a set of tools targeted to different usergroups ranging from business experts to developers.

mySAP ERP Business Packages

Business Packages consist of pre-assembled Portal content that enables your enterprise tocomplete business tasks. In essence, Business Packages provide out-of-the-box portalapplications that can be easily modified to suit a customer's needs.

The following table summarizes the Business Packages that are available for the mySAPERP Solution.

Business Package

BP BUSINESS UNIT ANALYST 60.2

BP COMPENSATION SPECIAL. 60.2

BP CREDIT MANAGEMENT 60.1

BP ESS (ERP 2004) 60.2

BP EXTERNAL PROCUREMENT 60.2

BP HR EXEC. ANALYT. (ERP) 60.3

BP MSS (ERP 2004) 60.1

BP MANUFACTURING 60.1

BP SALES 60.1


Business Package (continued)



BP PRODUCTS 50.3BP ASSETS 50.3

BP PROJECTS 50.3

BP COLL. BY CFOLDERS 2.0 50.1

BP SUPPLIER ORDER COLL. 60.1

BP DESIGN COLLABORATION 60.1

BP PAYER DIRECT 60.1

*) Please contact Marcus Freiheit ([email protected]), if you would like to download this Business

Package.

Note that the iView Studio, from which you could download BPs, has been replaced by theSDN (Software Developers Network) Portal Content Portfolio. The corresponding address ishttp://www.sdn.sap.com/ NW Business Content Portal Content Portfolio .There you can also find further information on planned and available BPs, guidelines, and soon.

If you prefer, you can also download BPs directly from SAP Service Marketplace atservice.sap.com/swdc .

We recommend that you always archive the downloaded BPs locally to ensure that you haveaccess to those releases later.

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

In addition to the Business Packages, SAP provides a number of tools that customers canuse to enhance and customize content, including tools for end users, for contentadministrators, for business users with no coding experience, and for professionalprogrammers.


The Enterprise Portal installation guide is located in SAP Service Marketplace atservice.sap.com/nw04installation SAP EP.

For information on the installation of Content Management & Collaboration, see SAPNote 720298.

For more information on business packages, see SAP Service Marketplace atservice.sap.com/ep-content.

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







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




SAP BW largely consists of three functional areas:

• Front end



- Report definition and Web publishing

- Data analysis in BEx Analyzer and a Web browser plus integration of analyticalapplications into mySAP Enterprise Portals

- Organization of reports

- Information distribution

• Administrator’s workbench

- Data management

- Monitoring

- Scheduling

• Data extraction

- SAP BW extractors in SAP components

- Openness to external systems

- Integration of extraction, transformation, and loading (ETL) tools

• Planning

Use

SAP BW provides both operational and strategic analyses:

• For operational analysis, the data is provided on individual document level with documentheader and document item information. ODS (operation data storage) objects forpurchase orders, confirmations, invoices, contracts, bid invitations, and bids have beendefined on the basis of ODS technology of the BW.

• Data is provided on aggregated level for strategic analysis. It is possible to analyze dataaggregated according to time, vendor, product, and product category, as well asaccording to account assignments. The InfoCubes defined for this are supplied with theinformation from the ODS objects.


For more information on SAP Business Information Warehouse, see SAP NetWeaverMaster Guide in SAP Service Marketplace at

service.sap.com/nw04installation .

7 1 5 BI Content Add on (3 5 2 or 3 5 3)


applications that best fit their business requirements (e.g. by enhancing and adjusting thedelivered content.)

Related Documentation







See SAP Service Marketplace at service.sap.com/notes → SAP Note 717812 (Installation and Upgrade to BI_CONT 3.52.)

Also, see SAP Service Marketplace at service.sap.com/notes → SAP Note 703759 (BI Content 3.5.2: Incompatible changes with release upgrade.) This SAPNote discusses incompatible changes to objects delivered with BI Content 3.5.2 Add-on.

7.1.6 PI Basis 2004_1_640

The SAP Basis Plug-in (PI_BASIS 2004_1_640) is part of the SAP NetWeaver ABAP Stackand does not require an explicit installation.

From SAP Basis 6.40 forward, SAP Basis Plug-In includes Enterprise PortalPlug-in, formerly known as Workplace Plug-in (WP-PI). This means that thelatter is no longer a separate component.


See SAP Service Marketplace at service.sap.com/notes → SAP Note 670733

{Installation/upgrade of Basis Plug-In (PI_BASIS) 2004.1}.

Also, see SAP Service Marketplace at service.sap.com/notes → SAP Note 674417 (Release restrictions plug-in basis 2004.1).

7.1.7 SAP Knowledge Warehouse (KW) 7.0

SAP Knowledge Warehouse (SAP KW) delivers the technical infrastructure you need to setup and manage your own enterprise-specific knowledge base in the areas of documentation,training, and manuals. For project teams and end users, SAP KW streamlines training andbusiness processes, helping you reduce your costs. In addition, the possibilities to reuse,supplement and continually update SAP content offers great savings potential


Quality management manual template - EN ISO 9000 and 14000 compliant• Optional package:

Training materials (includes course materials and instructor guides)











The KW functionality is substantial part of the SAP Web AS ABAP component. There aresome other KW-related optional components that you may install, depending on your specificrequirements.


For more information, see SAP Service Marketplace atservice.sap.com/nw04installation Installation Guide - SAP Knowledge

Warehouse .

See also SAP NetWeaver Master Guide in SAP Service Marketplace atservice.sap.com/nw04installation .

7.1.8 Search and Classification (TREX) 6.1

Search and Classification (TREX), provides intelligent search and text mining functions as

well as automatic classification. The powerful engines retrieve information from bothstructured and unstructured text.

TREX is based on client/server architecture. The client software is integrated into theapplication that uses the TREX functions, and allows communication with the TREX servers.

The TREX servers execute the requests of the clients: They index and classify documentsand respond to search queries.

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

If TREX is running on the same host as other components, you must ensurethat enough memory exists for all components. Moreover, you must ensurethat TREX can use the required main memory space exclusively.


For more information, see SAP Service Marketplace atservice sap com/nw04installation Installation Guide – Search


for HTML and various application scenarios, such as SAP Employee Self-Service or SAPCRM.

SAP ITS has been integrated into SAP Web AS 6 40 This ITS is sometimes referred to as









SAP ITS has been integrated into SAP Web AS 6.40. This ITS is sometimes referred to as“internal ITS” as opposed to the “external” ITS 6.20.

Note that some mySAP ERP business processes still require using an ITS 6.20.


Review the SAP@Web 6.20 Installation Guide on SAP Service Marketplace at

service.sap.com/instguides → SAP Components → SAP Web Application

Server → Release 6.20 .

Also, review SAP Help Portal at help.sap.com → Documentation → SAP

NetWeaver → SAP Web Application Server.

7.1.10 SAP GUI

Generally, the latest release of the SAP GUI software (such as SAP GUI 6.40) can be usedwith all previous SAP system releases. As a result, older SAP systems can also benefit fromthe features that are only available in the most recent SAP GUI releases (for example,support of Windows 2000.)

The benefit of this downward compatibility is that you can simply install a new SAP GUIrelease instead of patching an existing one. The SAP GUI maintenance strategy takesadvantage of this feature. In many problem situations, the recommendation is to install a newSAP GUI release, because patches cannot always be provided for previous SAP GUIreleases even if SAP still maintains the SAP system with the same release number.

The SAP front end software release should always be at least the same as SAP WebApplication Server. But SAP GUI 6.20 is basically compatible with mySAP ERP 2004 andmost transactions will run in SAP GUI 6.20 (however, see Unicode restriction below).

Note that SAP GUI is mainly required for administrators and power users. You require SAPGUI to display Dynpro-based screens (ABAP).

It this context, note that some new mySAP ERP functionality does not run under SAP GUI – itrequires a portal-based environment, such as the new role-based scenarios and Manager

Self-Service and Employee Self-Service. This functionality will not be available, unless anSAP Enterprise Portal is installed.

With the localized version of Windows SAP GUI 6 20 does not work for








7.2 mySAP ERP Components



7.2.1 SAP ECC 5.0

SAP ECC 5.0 is the central component of the mySAP ERP 2004 solution. It is the successorcomponent of SAP R/3 Enterprise (SAP R/3 4.7) and contains the functionality of SAP R/3Enterprise (Core and Extensions) and additional new functionality.

SAP ECC 5.0 is structured into the following subcomponents:

Core Components:

• SAP_APPL 500

• SAP_HR 500

Extension Set:

• EA-RETAIL 500

• EA-PS 500

• EA-HR 500• EA-GLTRADE 500

• EA-FINSERV 500

• EA-DFPS 500

• EA-APPL 500

• EA-IPPE 300

Plug-in:

• PI 2004_1_500

The SAP ECC 5.0 system is based on SAP Web AS ABAP 6.40. Note that some IndustrySolution add-ons have been integrated into SAP ECC 5.0. For more information on this topic,see SAP Note 700778 and refer to Section 4.3 of this document.

Integrating other SAP Business Suite components with SAP ECC 5.0

You may integrate other SAP Business Suite components with SAP ECC 5.0, for example,SAP CRM, SAP SCM, and so on, provided that you have the required license. R/3 Plug-in

enables this integration. R/3 Plug-In releases are downward compatible with all releases ofthe SAP components still in mainstream maintenance. Therefore, you may also integratelower releases of these components, which means that existing business scenarios will stillbe available after upgrading to SAP ECC 5.0.

F i f ti f t i / 3 l i I t ti f SAP R/3 /


7.2.2 PI 2004_1_500





R/3 Plug-in PI 2004_1_500 is part of the SAP ECC 5.0 installation (in other words, it does notrequire an explicit installation.)

R/3 Plug-in (PI) is an interface, which enables the exchange of data between one or severalSAP ECC systems and other SAP components. R/3 Plug-in supplies the SAP componentswith transaction data and master data in real time. It also makes it possible to use SAPapplication components like SAP SCM or SAP CRM together with certain SAP industry-specific components. All SAP industry-specific components based on SAP R/3 4.6B or higher

require an R/3 Plug-in.R/3 Plug-in is shipped with SAP application components (SAP ECC, SAP SCM, SAP BW,SAP BBP, SAP SRM, SAP CRM, and SAP SEM) and with industry-specific SAP componentsbased on SAP R/3 4.6B or higher SAP R/3 releases. You can order the most recent Plug-inreleases free of charge or download it from the SAP Service Marketplace.


For more information, or to download, see SAP Service Marketplace atservice.sap.com/r3-plug-in .

See SAP Service Marketplace at service.sap.com/notes → SAP Note 181255 (Overview: Notes on R/3 Add-ons PI and PI-A).

7.2.3 SAP Learning Solution (LSO) 3.0

SAP Learning Solution provides a comprehensive enterprise learning platform capable ofmanaging and integrating business and learning processes and supporting both e-learningand classroom training, as well as synchronous and asynchronous collaboration. It is fullyintegrated with mySAP ERP, and includes content authoring, content management, andlearning management capabilities, as well as a learning portal.

For more information on SAP Learning Solution, see SAP Service Marketplace atservice.sap.com/learningsolution .

Installation- and upgrade-related information can be found at service.sap.com/erp-

inst mySAP ERP 2004 SAP Learning Solution 3.0 .

Components of SAP Learning Solution

SAP Learning Solution consists of the following components:


Notes 503468 and 700778). LSO 300 Backend provides you with the following modules:Training Management, Personnel Development, HR Master Data, and OrganizationalManagement. Training Management stores all application data and business functions. This

includes, among others, course participants’ master data, learner account, course catalog,lifi i l d d il d d h i di id l



http://service.sap.com/learningsolution





http://service.sap.com/learningsolution





qualification catalog, and detailed data on the individual courses.

LSOFE continues to be an add-on that can be installed on the SAP ECC system or on aseparate Web Application Server (standalone installation). Refer to SAP Notes 529063 and503907. LSOFE contains a Web-based Learning Portal that provides the learners withpersonalized access to information and functions. The Learning Portal Front End is based onBusiness Server Pages (BSPs). SAP ECC communicates with SAP Web AS via RFC, andprovides the dynamic content of the BSPs.

Note that a Business Package for Learning Solution 2.0 (50.2) is available. This component isoptional for LSO 3.0 and can be used with SAP Enterprise Portal 6.0 (NW ’04.) You requirethis BP if you would like to set up the access to the Learning Portal of LSO 3.0 through SAPEnterprise Portal.

LSOCP (Content Player) is a server application that enables you to process the learningcontent on a particular client PC. The Learning Portal provides Content Player with anappropriate URL, which contains a Content Management (CM) path and additionalinformation (such as the course strategy). The learner account is read in the SAP ECC

system to determine the course status before the learner starts with the learning unit. Whenthe learner has finished playing the learning unit, LSOCP saves the current course status inthe learner account.

You may have to install plug-ins in addition to an Internet browser to be able to use thelearning unit, depending on the sort of content you would like to process.

From a technical perspective, LSOCP is based on Java Server Pages. It uses SAP’s ownJ2EE Engine, which is integrated in the SAP Web AS, as the Servlet Engine.

LSOAE (Authoring Environment) is used to develop courses. It combines several tools that

provide the functions for structuring (Instructional Design Editor), editing (InstructionalElement Editor, Test Author), and testing (integrated Content Player) course content. It isinstalled locally on your PC. You can use the Authoring Environment offline on your local PC,and online through direct data exchange between the Publisher Database (SAP ECC) andthe central Content Repository (CM or WebDAV server). When you check in the contents, thePublisher Database in the SAP ECC backend system is provided with data.

You need Java Development Kit (JDK) for the Authoring Environment. As this component isnot part of the SAP shipment, you must download and install it separately. For therecommended JDK versions for your platform and how to obtain them, see SAP Note709140.

Note that you require a Content Management System for your Learning Solution.

Other Components for SAP Learning Solution


you can instead use a WebDAV-compatible Web server such as Apache WebDAV-Server orMicrosoft IIS as the repository.



A WebDAV-compatible Web server heavily restricts the functions of savingmeta data and searching. Therefore, you should only use it as contentrepository if absolutely necessary.

CMS saves extensive attributes to the content files, which can be searched (using tools likeTREX).TREX 6.1 provides enhanced search capabilities for authors. By using TREX it ispossible to search for content more quickly and easily.

Install SAP GUI 6.20 / 6.40 on every computer that needs to access the administrativebackend.

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

• Security: Do you have any security concerns about giving all learners access to yourSAP ECC system? If yes, you should run LSOFE on a separate SAP Web ApplicationServer. If you are already 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 TCObecause you need fewer servers. No additional administration is necessary. If you areusing a separate HR system connected to your LSO system, this HR system does notrequire an upgrade to SAP ECC 5.0.


See SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP

2004

SAP Learning Solution 3.0 See SAP Service Marketplace at service.sap.com/notes → SAP Note 718624

(Installing the LSOFE 300 add-on with transaction SAINT).

7.2.4 SEM-BW 4.0

This component is installed as an add-on to the SAP Business Warehouse 3.5 functionality,

which is part of the NetWeaver 2004, SAP Web AS ABAP. It requires FINBASIS 3.0 asinstallation prerequisite.


For more information, see SAP Service Marketplace at service.sap.com/sem.


7.2.5 FINBASIS 3.0

FINBASIS 3 0 i Add O hi h b i t ll d th NW BW S t th



http://service.sap.com/sem






FINBASIS 3.0 is an Add-On, which can be installed on the NW BW System or any othersystem that is based on NetWeaver ’04, more precisely, SAP Web AS ABAP. FINBASIS is atechnical prerequisite for SEM-BW 400.


For more information, see SAP Service Marketplace at service.sap.com/notes

→ SAP Note 718457 {FINBASIS 300 installation (with Transaction SAINT)}.

Also, see SAP Service Marketplace at service.sap.com/sem.

7.2.6 SAP Catalog Content Management (CCM)1.0

The SAP Catalog Content Management can be installed as add-on for the SAP ECC system,

the SAP SRM system or any SAP NetWeaver ‘04 system (ABAP stack). It is used forprocurement functions.

The Catalog and Content Management consist of the following tools:

Authoring Tool

1. Filters and maps products to catalog schema

2. Enriches product data

3. Approves product dataSAP Catalog Search Engine

1. Define views

2. Publish catalog

3. View catalog

You do not necessarily require SAP SRM Server to use SAP Catalog ContentManagement (SAP CCM.) SAP CCM can be installed on any system basedon SAP Web AS ABAP. Although SAP CCM is primarily used in SRM-relatedscenarios (like “Create Shopping Carts”), you can also use it within mySAPERP. For example, you can call SAP CCM from a Create Order screen (e.g.


How can companies cope with today’s reality while preparing for tomorrow’s? Answer: Bycombining cost-cutting strategies (for example, employing freelance and part-time talents)with a streamlined, Internet-based recruiting process. SAP E-Recruiting, the new fully Web-

enabled, end-to-end recruiting solution of SAP, offers companies the recruiting managementfunctions they need to locate appropriate talent







functions they need to locate appropriate talent.

SAP E-Recruiting offers scenarios – for example, employment searches and applications– toexternal parties via web services.

Technical Information:

Depending on your requirements, you will choose either to install ERECRUIT as an add-onfor your SAP ECC 5.0 system or as an add-on for a dedicated SAP Web AS ABAP Server

6.40 (standalone installation). The standalone installation can be connected to HR and NWBW systems, provided that you have implemented BI content at release 3.5.2 or 3.5.3. Beforeyou begin to set up your E-Recruiting system landscape, you should consider the followingissues:

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

• Total Cost of Ownership (TCO): Installing ERECRUIT on SAP ECC 5.0 reduces TCObecause you 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 a standalone operation mode. See SAP Note 717803.

Search and Classification (TREX) is a mandatory component for SAP E-Recruiting (refer toSection 7.1.8). If you already have a TREX 6.0 (with at least SP1) installation, a normalupgrade to version 6.1 is not possible since architecture, configuration files and indexstructures changed considerably in TREX 6.1. Instead, you need to perform a migration. You

will find the corresponding Migration Guide in SAP Service Marketplace atservice.sap.com/nw04upgrade Cross NW Component Migration Guide – Search and Classification (TREX).

For installation-related information on Search & Classification (TREX) 6.1, see SAP ServiceMarketplace at service.sap.com/nw04installation Installation Cross NW Installation Guide – Search and Classification (TREX).

Furthermore, you can integrate your E-Recruiting with NW BW for reporting purposes. Thefollowing queries are available:

• Requisitions Created

• Requisition Status Changes

• Application Sourcing


Basic System Architecture

The following diagram shows the system architecture of a minimal E-Recruiting (standalone)

setup.

http://service.sap.com/nw04upgrade



http://service.sap.com/nw04upgrade



Internal Users(Browser - SSO

optional)

SystemAdministrator

(SAP GUI)

SMTP (Mail)

Internet

HTTP(S)

External Users(Web Browser)

SAP HR / SAPECC / NW BWRFC

RFC (ALE)

TREX

E-Recruiting

DMZ Intranet

ApplicationGateway /

ProxyGateway

SMTP (Mail)

RDBMS

HTTP(S)

Firewall

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 uponABAP/OO, Business Partner and Knowledge Provider (KPRO).


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

For installation information, consult SAP Service Marketplace at

service.sap.com/notes → SAP Note 717802 (Installing ERECRUIT 300).

For upgrade information, consult SAP Service Marketplace at

service.sap.com/notes → SAP Note 717803 (Add. info. on upgrade to SAPNetWeaver 04 with ERECRUIT 300).


requisitions, purchase orders, and reservations with or without electronic catalogs; approveand reject purchases; receive and enter service information at the desktop; and use status,invoicing, and reporting functions. End users can purchase goods and services straight from

their workplace, leaving purchasing departments free to focus on strategic purchasingoperations. This helps you streamline requisition processes and, therefore, your entire







ope at o s s e ps you st ea e equ s t o p ocesses a d, t e e o e, you e t eindirect procurement processes, cutting the overall cost of procurement while providing thepurchasing department with visibility and control across the entire procurement chain.

Note that the mySAP ERP 2004 license only covers Self-ServiceProcurement (classic scenario) and the Supplier Collaboration Scenario for

MRO (Maintenance Repair and Operations).


See SAP Service Marketplace at service.sap.com/instguides → mySAP

Business Suite Solutions → mySAP SRM → Using SAP SRM Server 5.0 → Installation Guide - SAP Supplier Relationship Management Server 5.0 ABAP on <platform>:<database>

7.2.9 cProject Suite 3.10

SAP cProject Suite 3.10 includes two applications:

• cProjects: A project management application.

• cFolders: A collaboration platform.

CPROJECTS 3.10_640 (the technical name for cProject Suite) is an add-on for SAP Web

AS. If you are implementing cProject Suite for the first time or, in particular, if you only wish touse the cProjects application, then it is most expedient to install cProject Suite on the SAPWeb AS of the SAP ECC system. If you are already using cProject Suite 310_620, thenupgrade to cProject Suite 310_640.

If you were operating cProject Suite separately from your R/3 system and youplan to upgrade both systems to mySAP ERP 2004, be advised that you

cannot merge these two systems into one. You must continue to run bothsystems separately.

Design Collaboration with cFolders


cFolders enables SAP customers to communicate with their partners and suppliers via back-end objects, without exposing their R/3 or ECC system to them. For instance, suppliers andpartners of the SAP customer can change or modify a bill of materials in cFolders, and a

back-end user can subsequently import these changes in a reconciliation process fromcFolders to the R/3 or SAP ECC system.





y

Collaboration Projects

cProjects offers a web-based, easy-to-use interface and constitutes a powerful tool foroperative project management. cProjects enables you to realize innovative ideas in all kindsof projects, e.g., development projects, projects to simplify internal processes, to implementrecognized quality standards, and to reduce costs incurred by errors. It is a cross-industry

application that supports the entire process of your project, from conception to planning andquality checks, through to the completion of the project. It also allows you to communicatewith external partners or lead customers. cProjects incorporates internationally recognizedstandards (QS-9000) and is based on methods like for example Advanced Product Quality Planning (APQP) developed in the automobile industry.


For more information on Collaborative Product Development in Cross-Enterprise Processes,consult SAP Service Marketplace at service.sap.com/plm Life-Cycle Collaboration

and Analytics Design Collaboration.

For more information on cProject Suite, consult the mySAP PLM Master Guide in SAP

Service Marketplace at service.sap.com/plm-inst → using cProject Suite 3.10

7.2.10 SAP IPC 4.0

IPC (Internet Pricing and Configurator) is a standalone Java application, which processesproduct configurations and calculates product prices.

SAP Internet Pricing and Configurator (IPC 4.0) requires its own database for Internet Salesscenarios. This IPC cannot be used for SRM procurement.

SAP Internet Pricing and Configurator (IPC 4.0) for SRM Procurement does not require adatabase. This IPC cannot be used for Internet Sales scenarios.

Since the IPC can only connect to one backend system (SAP ECC or SRM) you need twodifferent IPC’s in case you want to use the SRM Procurement scenario and the Internet Salesscenarios simultaneously. You need one IPC for the SRM Procurement scenario (in whichthe IPC connects to the SRM system) and another IPC for the Internet Sales scenario (inwhich the IPC connects to the SAP ECC system).

IPC Web Application 4 0 is also required for the Internet Sales scenarios It is a J2EE


Also, see SAP Service Marketplace at service.sap.com/erp-inst → mySAP

ERP 2004 → ERP Java Components → Install ERP Java Components .

SAP XSS









7.2.11 SAP XSS 500

XSS 500 consists of the subcomponents MSS 100, ESS 100 and PCUI_GP 100. You mayeither install XSS in its entirety (using the ERP Java installer, which is the default mode) ordeploy each of these subcomponents individually (with SDM).

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

If your specific situation demands that you implement Manager Self-Service or EmployeeSelf-Service alone, then you may deploy MSS 100 and PCUI_GP 100 or ESS 100 andPCUI_GP 100 individually, provided that you plan to use the Web-Dynpro-based services.

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

Note that you may install and operate XSS (or any of its subcomponents) and EnterprisePortal on a common server, on the same J2EE instance, or on separate servers. Yourspecific requirements should ultimately determine the most suitable option. If you decide toinstall XSS and Enterprise Portal on the same J2EE instance, you should consider using SAPNetWeaver Rapid Installer 2.0, which is an installation and configuration wizard described in

Section 4.2 of this document. For further information, consult SAP Service Marketplace atservice.sap.com/nw-ri.

XSS has been implemented based on SAP Web AS 6.40 technology using the Web Dynproprogramming model. This programming model largely replaces the current ESS model that isbased on ITS technology.

XSS is required only if you would like to use the Business Packages MSS 60.1 (mySAP ERP2004) and / or ESS 60.1 (mySAP ERP 2004), both of which are Web Dynpro-based

SAP XSS 5.0 is a J2EE application component, which is deployed with the ERP Java Components package. This is the default installation mode.

SAP XSS is based on SAP NetWeaver 2004 Java Stack and connects to the backendfunctions in the SAP ECC System.


your sales operations. You can support your consumers in carrying out their businesstransactions within a business-to-business or business-to-consumer selling scenario.

With SAP Internet Sales, you can run your complete sales process on the Internet -- withoutthe need for a CRM deployment. You can also develop and manage an effective online salescatalog And provide customers with online product configuration easy to use shopping






catalog. And provide customers with online product configuration, easy-to-use shoppingbasket features, product availability checks, secure transactions, order status and tracking,and after-sales service.

SAP Internet Sales helps you lower the cost of sales by reducing transaction costs in orderprocessing -- and by reducing human intervention in order-taking and status-checking. Sincethe solution is quick and easy to implement, you reduce project risk and achieve rapid returnon investment. Since it leverages your existing IT infrastructure, you avoid capitalexpenditures and enjoy lower total cost of ownership.

ISA WAC is a J2EE Web application, which is deployed with the package “ERP JavaComponents.“ Due to its persistence layer, a migration is required, if you have alreadyinstalled Internet Sales R/3 Edition based on SAP J2EE 6.20 and you would like to upgradeto mySAP ERP 2004. For more information, refer to the ERP Upgrade Master Guide in SAPService Marketplace at service.sap.com/erp-upgrade .

ISA WAC has not yet been integrated with SAP Catalog ContentManagement (CCM). This integration will be enabled at a later date. For thetime being, you create or maintain the product catalog in the same way youdid for the SAP Online Store; in other words, directly in the SAP R/3 or SAPECC system.


See SAP Service Marketplace at service.sap.com/erp-inst → mySAP ERP 2004 → ERP Java Components → Install ERP Java Components .

For information on the scenario “Internet Sales in mySAP ERP”, review SAP ServiceMarketplace at service.sap.com/isa-r3 and the mySAP ERP Upgrade Master

Guide at service.sap.com/erp-upgrade .

7.2.13 FSCM Biller Direct 3.0Instead of sending printed bills, vendors can electronically send bills to their customers andshare account information with them. Customers can then pay their invoices on a vendor’sW b i Th bill id l i ll b di d di d bi


FSCM Biller Direct itself has no own persistence. The database of the SAP ECC backendsystem is used for storing data (FI-AR or FI-CA).

Customers can store data of users for BD in LDAP as an alternative to storing users in theSAP ECC Backend System. A File System is used for storing web.xml-/application-config.xmldata and JSPs adapted by customers



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



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





data and JSPs adapted by customers.


See SAP Service Marketplace at service.sap.com/erp-inst → mySAP ERP

2004 → ERP Java Components → Install ERP Java Components .

7.2.14 Mobile Time Sheet (MTS) 1.6

The SAP Mobile Time and Travel 1.6 scenario for laptop on the client device includes thecomponents Mobile Time Sheet (MTS) 1.6 and Mobile Travel Expenses (MTR) 1.6.

Mobile Time Sheet enables employees in your company to record their working times onlaptop computers wherever they are. The laptops do not require a connection to SAP ECC fortime recording. It is aimed primarily at employees who have to travel a lot and cannot always

have a connection to SAP ECC.

Mobile Time Sheet users can use an intuitive user interface in a Web browser to record theirworking times. They can save their working time data on the laptop and then transfer it toSAP ECC when they are able to set up a connection.

Working time data recorded by users in Mobile Time Sheet can be synchronized with SAPECC at intervals of the users’ choice. As soon as the data has been transferred to SAP ECC,you can process it in the same way as you would process data records that are entered usingany other Time Sheet user interface. Mobile Time Sheet uses the same business logic and

the same database table (CATSDB) as the other user interfaces of the Time Sheet.


See Installation Guide in SAP Service Marketplace at service.sap.com/erp-

inst mySAP ERP 2004 Mobile Infrastructure Components

For additional information on Mobile Infrastructure and Mobile Time & Travel forLaptop, consult the Master Guide for SAP NetWeaver, which is located in SAPService Marketplace at service.sap.com/nw04installation Installation .

Also, consult SAP Service Marketplace at service.sap.com/notes SAP Note 721799 (Mobile Time Sheet 1.6 for Laptop - Composite Note).


7.2.15 Mobile Travel Expenses (MTR) 1.6

The SAP Mobile Time and Travel 1.6 scenario for laptop on the client device includes thecomponents Mobile Time Sheet (MTS) 1 6 and Mobile Tra el E penses (MTR) 1 6













components Mobile Time Sheet (MTS) 1.6 and Mobile Travel Expenses (MTR) 1.6.

The Mobile Travel Expenses component application allows users to enter and edit trips andreceipts offline regardless of location, using mobile devices (laptops). A connection to theSAP system is not required for offline data entry and editing. The user can enter all of the tripdetails and receipts information required for trip cost reporting offline and save them on theirlaptop. They can then transfer these trips to SAP Travel Expense Management when they

next have access to the online system.Related Documentation:


inst mySAP ERP 2004 Mobile Infrastructure Components .

For additional information on Mobile Infrastructure and Mobile Time & Travel forLaptop, consult the Master Guide for SAP NetWeaver, which is located in SAPService Marketplace at service.sap.com/nw04installation Installation .

Also, consult SAP Service Marketplace at service.sap.com/notes SAP Note 721796 (Mobile Travel Expenses 1.6 for Laptop - Composite Note).

7.2.16 SAP Mobile Asset Management (MAM) 2.5

The Mobile Asset Management application delivers anywhere, anytime access to critical role-based information and services. MAM consists of a suite of tools tailored to the needs of

Plant Maintenance and Customer Service field engineers—functional areas that are both partof the Enterprise Asset Management and Customer Service capabilities within mySAP ERP.

Representing a full offline mobile application, MAM provides ready-made scenarios that helpfield technicians perform their daily activities at customer sites and within plants. MAM 2.5 willintegrate into RFID (Radio Frequency Identification), a cross component application thatallows the integration of data from RF tags into the MAM 2.5 processes on the front end side.This scenario is a cross industry scenario and is based on work orders (Service orMaintenance orders) and notifications created and assigned to engineers on the ECC serveror in the front end. The MAM application targets different roles in an organization. Theseroles are the Field Service Engineer, Field Technician and the MAM administrator/planner.

SAP MAM is a full offline mobile application that runs on Personal Digital Assistants (PDAs)or Laptops. In this scenario, the field engineers can use a Pocket PC 2003 based mobiled i i h i bili f i l h i i O h bil d i h




inst mySAP ERP 2004 Mobile Infrastructure Components

Also, consult SAP Service Marketplace at service.sap.com/notes SAP Note

















723380 (Mobile Asset Management 2.5 - Composite Note).

7.2.17 SAP Mobile Sales for mySAP ERP (MSR)2.0

The SAP Mobile Sales with mySAP ERP (SAP MSR) provides sales representatives toaccess front- and back-office business processes and to manage critical sales activities in thefield using standard-based personal digital assistants, other popular handheld devices,laptops as well as devices enabled with barcode scanners. The business scenarios providefunctions that focus on sales activities for sales representatives.

The SAP Mobile sales with mySAP ERP is based on the SAP Mobile Infrastructure, which isa part of SAP NetWeaver ‘04. SAP MSR 2.0 requires the SAP Mobile Infrastructure client

component installed on the mobile devices. The Mobile Infrastructure client enablessynchronization of data from/to the backend system. Also the application requires a clientdatabase on the mobile device. The currently supported mobile database is DB2 Everyplace.

SAP Plug-in 2004.1, which is part of SAP ECC 5.0, enables using the application relatedbusiness logic.


See Installation Guide in SAP Service Marketplace at service.sap.com/erp-inst

mySAP ERP 2004

Mobile Infrastructure Components

Also consult SAP Service Marketplace at service.sap.com/notes SAP Note 723437 .

7.2.18 SAP Mobile Direct Store Delivery (MDSD)

2.0A description of the SAP Direct Store Delivery business processes can be found in Section6.7.3 of this document. The technical component SAP MDSD 2.0 consists of twosubcomponents:


Extractor are part of SAP ECC 5.0; SAP Mobile Infrastructure Server 2.5 is part of SAP WebAS 6.40 (ABAP).

SAP MDSD 2.0 requires the SAP Mobile Infrastructure Client 2.5 and the client database onthe mobile device. The currently supported mobile database is DB2 Everyplace.

The DSD Administration Console is a web-based integrated monitoring tool








The DSD Administration Console is a web based integrated monitoring tool.

SAP Mobile DSD 2.0 can only run against SAP ECC 5.0 and cannot beconnected to any lower SAP R/3 release.


For additional information on installation and configuration of the scenario “SAPDirect Store Delivery”, consult SAP Solution Manager.

Also consult SAP Note 755712 (Release restrictions / information on DSD 2004) atservice.sap.com/notes

For information on SAP Mobile Infrastructure, see service.sap.com/mi .

8 Media Information

8 Media InformationS ft C t d DVD / CD St t


http://service.sap.com/mi

http://service.sap.com/mi




Software Components and DVD / CD Structure

This section summarizes the exact location of the required software components on thecorresponding DVD(s) and CD(s) shipped with the mySAP ERP 2004 package. Ifappropriate, references to other sources are also included.

The material numbers of the corresponding DVDs and CDs may change asnew updates become necessary. Therefore, make certain that you alwaysuse the most up-to-date version of the indicated data carrier(s).

The following tables list the software components in accordance with whether they belong to

SAP NetWeaver ’04, mySAP ERP 2004 or SAP Solution Manager.

Before you attempt to install any of the following components, ensure that you are using thecurrent version of the installation documentation. For SAP NetWeaver ’04, you can find therelevant guides at service.sap.com/nw04installation Installation ; the ERP

installation guides are located at service.sap.com/erp-inst mySAP ERP 2004 .

Furthermore, we recommend that you visit the SAP Software Distribution Center in SAPService Marketplace at service.sap.com/swdc. Within the SAP Software Distribution

Center, you can download any SAP software component(s) to which your enterprise isentitled. The corresponding authorizations are automatically generated from the licenses. Toobtain the software you require, you can either download the corresponding files directly (bysimply clicking on the file name) or you can use the SAP Download Manager.

mySAP ERP 2004 Support Release 1 (SR1) is based on Support PackageStack 5. For more information on Support Package stacks, consult SAPService Marketplace at service.sap.com/sp-stacks . Also review thecorresponding Release and Information Notes (RIN). For your convenience,SAP Note 760874 lists all RINs that have been issued for mySAP ERP.













6 Media Information

SAP NetWeaver ’04 SR1 Components

(continued)DVD / CD Label Description / Additional Information

WILY Introscope Entpr Mgr 5.3

WILY Introscope Agent 5.3

WILY Introscope Webview 5 3

WILY Introscope Entpr Mgr 5.3, WILY Introscope Agent 5.3,WILY Introscope Webview 5.3

WILY Introscope files



1 Same CD/DVD for Unicode / Non-Unicode;2 Different CD/DVD for Unicode / Non-Unicode;3 Only available via download from SAP Service Marketplace;4 Only available on request

110

WILY Introscope Webview 5.3

SAP License Keys & License AuditSAP License keys for SAP Systems, System MeasurementGuide, License Administration Workbench

SAP License Keys & License Audit contains the complete documentation aswell as important information about the license auditing tools and thepreparations you need to make for license auditing.









ERP Master Guide

Documents