ERP Master Guide

Master Guide

mySAP™ ERP 2004 Support Release 1 powered by SAP NetWeaver™ ‘04

Document Version 3.0 February 2005 Material Number 50069200

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

© Copyright 2005 SAP AG. All rights reserved.

JAVA® is a registered trademark of Sun Microsystems, Inc.

No part of this publication may be reproduced or transmitted in any

J2EE™ is a registered trademark of Sun Microsystems, Inc.

form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,

notice.

used under license for technology invented and implemented by Netscape.

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

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

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

MaxDB™ is a trademark of MySQL AB, Sweden

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

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, xApps, mySAP

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

Business Suite, and other SAP products and services mentioned herein ®

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere , TM

Netfinity®, Tivoli®, Informix and Informix® Dynamic Server

are

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

as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

®

ORACLE is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of

Disclaimer

the Open Group.

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe

LINUX is a registered trademark of Linus Torvalds and others.

malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names

Any Java™ Source Code delivered with this product is only to be used

referenced herein are trademarks of Citrix Systems, Inc.

by SAP’s Support Services and may not be modified or altered in any way.

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

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

Typographic Conventions Type Style Example Text

Represents Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation

Example text

EXAMPLE TEXT

Example text

Icons

Emphasized words or phrases in body text, titles of graphics and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text

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

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

EXAMPLE TEXT

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

Icon

Meaning Caution Example Note Recommendation Syntax

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.3 Financials........................................................................................49 6.3.1 Overview........................................................................................................ 49 6.3.2 Technical System Landscape...................................................................... 49 6.3.3 Financial Supply Chain Management ......................................................... 50 6.3.4 Financial Accounting ................................................................................... 51 6.3.5 Management Accounting ............................................................................. 52 6.3.6 Corporate Governance................................................................................. 52

6.4 Human Capital Management .........................................................54 6.4.1 Overview........................................................................................................ 54 6.4.2 Technical System Landscape...................................................................... 54

February 2005

4


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.2 Technical System Landscape...................................................................... 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.2 Technical System Landscape...................................................................... 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.2 Technical System Landscape...................................................................... 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.2 Technical System Landscape...................................................................... 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 6.8.7 Quality Management..................................................................................... 81

7 Information on Software Components .......................................82 7.1 SAP NetWeaver 2004 Components ..............................................82 7.1.1 SAP Web Application Server 6.40 ............................................................... 82 7.1.2 SAP Enterprise Portal (EP) 6.0 .................................................................... 83 7.1.3 SAP NW Exchange Infrastructure (XI) 3.0 .................................................. 85 7.1.4 SAP Business Information Warehouse (BW) 3.5 ....................................... 86 7.1.5 BI Content Add-on (3.5.2 or 3.5.3) ............................................................... 87 7.1.6 PI Basis 2004_1_640..................................................................................... 88

February 2005

5


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

February 2005

6


1 SAP Documentation Types Several documents have been created to assist you in installing, implementing, operating and upgrading your SAP solutions. The Solution Master Guide (this document) is the first document you obtain; it provides a summary of all the information and documentation to be considered for the solution at hand. The following figure displays an overview of the most important documentation types that are needed during the various phases in the life cycle of an SAP solution. Although the various types of documentation shown here are closely related to one another, each documentation type enables you to perform a different task that arises during the course of a different solution phase.

Implementation

Operation

Upgrade

SAPterm

SAP Library

Upgrade Master Guide

Master Guide

Component Upgrade Guide

Component Installation Guide Security Guide Configuration Documentation

Release Notes

Implementation Guide (IMG)

Delta and Upgrade IMG

Solution Operation Guide

Fig. 1: Documentation types in the software life cycle

As shown in the figure, SAPterm, SAP Library and Implementation Guide (IMG) are crossphase documentation. •

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many definitions and glossary entries in English and German. To use SAPterm, visit SAP Service Marketplace at service.sap.com/sapterm.

•

The SAP Library is a collection of function- and process-oriented documentation for SAP components. It is located on SAP Help Portal at http://help.sap.com. SAP Library also contains Business Scenario Descriptions. The Implementation Guide (IMG) is a tool for configuring the SAP system to meet customer requirements. Its structure and documentation are component-oriented. It is located In the SAP menu of the SAP system under Tools → Customizing → IMG.

•

The Security Guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for the SAP NetWeaver technologies like SAP Web Application Server (SAP Web AS). This

February 2005

7


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 at service.sap.com/securityguide. •

The Component Installation Guide describes the technical implementation of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. The Component Installation Guides for the different components can be found on SAP Service Marketplace 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 is a tool with various functions, one of its main functions being the configuration of SAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, as well as documentation. Instead of the configuration documentation in SAP Solution Manager, there may be separate Business Scenario Configuration Guides in SAP Service Marketplace for earlier shipments of the Business Scenarios.

•

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

•

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the Component Upgrade Guides and SAP Notes. Instead of an Upgrade Master Guide, there may be several Business Scenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the Business Scenarios of an SAP solution. The current version is located on SAP Service Marketplace at service.sap.com/instguides.

•

The Component Upgrade Guide describes the technical upgrade of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. The current version is located on SAP Service Marketplace at service.sap.com/instguides.

•

Release notes are documents that contain short descriptions of new features or changes in an SAP component since the previous release. Release notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs. The current version is located on SAP Service Marketplace at service.sap.com/releasenotes or in the SAP menu of the SAP system under Help → Release information.

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

February 2005

8

2 Getting Started

2 Getting Started This Master Guide provides a central starting point for the technical (new) implementation of mySAP ERP 2004. Upgrade-related topics are beyond the scope of this document. They are discussed in the ERP Upgrade Master Guide. To facilitate the implementation process, all information within this document is organized by key functional areas and their respective key capabilities. You can therefore find the information 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 with your security or performance requirements, the infrastructure you implement may differ from 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 the overall upgrade sequences, references to related documentation, SAP Notes, and additional upgrade information.

•

Information about mutual dependencies that affect two or more components within the technical infrastructure.

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

To read the current version of the mySAP ERP 2004 Master Guide and other related installation guides, see SAP Service Marketplace at service.sap.com/erp-inst → mySAP ERP 2004. We recommend that you review the current version of the documents available there; the contents of these documents are updated regularly.

February 2005

9

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 Financials and mySAP ERP Human Capital Management – and the number of processes you wish to implement, you may require different component installation and configuration guides during implementation. 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 functional area. For example, you can review information about SAP NetWeaver components and how they relate to the mySAP ERP solution.

•

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

•

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

•

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

•

Section 8 “Media Information” provides information about the data carriers and the software components contained in them. It should help you identify the DVDs / CDs you need 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 process level and very detailed technical information. It is therefore intended for decision-makers as well as SAP consultants and SAP system administrators with operating system, database, and SAP system knowledge.

February 2005

10

2 Getting Started

2.3 Important SAP Notes You must read these SAP Notes before you start the installation. These Notes contain the most recent information on component installations, possible restrictions and corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service Marketplace at 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 '04

674417

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

February 2005

11

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 of which are at your disposal in SAP Service Marketplace. For example, there are important facts that you should take into account in the planning phase of your installation; these facts are not fully described in the present document. Moreover, many of the reference sources named 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 Resource Planning including news, services, events, demos, education and workshops, see SAP Service Marketplace at service.sap.com/erp.

•

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

•

Planning the System Infrastructure For comprehensive information on technical infrastructure issues and network integration, 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 Service Marketplace 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 and upgrade 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 the execution of the upgrade project, see SAP Service Marketplace at service.sap.com/erp-upgrade. Information on this page is updated on a monthly basis.

•

Support Package Stacks For the latest component version and patch level requirements, see SAP Service Marketplace at service.sap.com/sp-stacks.

•

Product Availability Matrix For technical and release planning information on SAP components for quick reference, see SAP Service Marketplace at service.sap.com/pam. Here you will find information on the availability of SAP component releases and maintenance end dates, as well as on platform, language and country version availability.

February 2005

12

3 History of Changes

3 History of Changes The mySAP ERP Master Guide is regularly updated in SAP Service Marketplace at service.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 recent edition of this document. The following table summarizes the changes that were made in each version of the mySAP ERP 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 sections revised and renumbered. New Section 6 “Media Information” added. New subsection on SAP Direct Store Delivery 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 ERP Business Map. System landscape diagrams revised and changed. Software Component Matrix for each key capability revised and changed. All sections renumbered.

February 2005

13

4 Cross-Solution Topics

4 Cross-Solution Topics 4.1 SAP NetWeaver™ 2004 Components SAP NetWeaver ‘04 provides mySAP ERP with a comprehensive integration platform and delivers the foundation to serve all ERP applications. SAP NetWeaver is built to extend mySAP ERP and to integrate non-SAP systems.

mySAP ERP 2004 Analytics Financials Human Capital Management Procurement & Logistics Execution Product Development & Manufacturing Sales and Service Corporate Services

SAP NetWeaver ‘04

BI Content

Java -.NET Interoperability Content Management and Collaboration

BW Functionality

XI Functionality

Portal Platform

KW Functionality

XI Components Adobe Document Services NW DI

Web AS ABAP

ABAP Stack

Content Server

Portal Runtime for .NET

KW IKS BW Java Components

MI Functionality

BW Precalculation Service

Web AS Java

Java Stack

Search and Classification (TREX)

Visual Composer Server

XI Adapter Engine

XI Adapter Engine (J2SE)

Additional Components

Fig. 2: SAP NetWeaver ‘04 as the foundation of mySAP ERP ‘04

SAP NetWeaver facilitates the integration and alignment of people, information, and business processes across organizational and technological boundaries. SAP NetWeaver easily integrates information and applications from virtually any source. It interoperates with and can be extended using the primary market technologies – Microsoft .NET, Sun’s J2EE, and IBM WebSphere. With SAP NetWeaver ’04 fewer components have to be installed separately, particularly in the ABAP stack. Nevertheless, it bears mention that these components might still have to be patched separately, depending on the requirements of your ERP scenarios or on SAP’s Support Package Stack strategy. The latter states that you should keep all components, which are installed in one system, on a defined stack level. Therefore, it is useful to know the technical

February 2005

14


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

SAP NetWeaver ’04 Software Components BI Content Add-on BI CONT 3.5.2

Enterprise Portal CM + COLLABORATION 6.0_640 PORTAL PLATFORM 6.0_640

BW Java Components BI UDI 350

XI Components XI CONTENT SAP_BASIS 6.40 XI TOOLS 3.0

KW IKS SAP_IKS_100

XI ADAPTER FRAMEWORK 3.0

Adobe Doc. Services

XI ADAPTER FRAMEWORK CORE 3.0

SAP Web AS ABAP

ADOBE DOC. SERVICES 1.00

SAP BW 3.50

NWDI

PI_BASIS 2004_1_640

JDI 6.40

SAP ABA 640

JDI BUILD TOOL 6.40

SAP BASIS 6.40

JDI OFFLINE 6.40

SAP Content Server 6.30 SAP MI Client 2.5

XI Adapter Engine (J2SE) XI CONNECTIVITY SE 3.0

NW Developer Studio

XI Adapter Engine

NW DEVELOPER STUDIO 2.0

SAP Web AS Java SAP J2EE Engine 6.40

ABAP Stack

TREX 6.1

XI CONNECTIVITY SE 3.0

SAP IGS 6.40 SAP KERNEL 6.40

BW ANALYZER PRECALC SERVICE 350

XI ADAPTER FRAMEWORK 3.0 XI ADAPTER FRAMEWORK CORE 3.0

SAP IGS 6.40

SAP J2EE Engine 6.40

Java Stack

Additional Components

Fig. 3: SAP NetWeaver ‘04 software components

The main constituents of SAP NetWeaver are grouped in the ABAP and Java Stacks. The additional components shown in Figure 3 are optional, meaning that you would only have to install them in response to your specific requirements. 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

•

Synchronize data between mobile devices and various backend systems

•

Administer devices, applications and software updates

•

Develop and enhance applications.

The SAP MI Client Component is installed locally on mobile devices and is equipped with a Web server, a database layer and its own business logic. Staff working remotely can therefore work offline and does not have to wait for a network connection to complete timecritical business applications. SAP MI offers tools for synchronization and data replication that make the data of the mobile device consistent with that of the backend system. SAP Mobile Infrastructure supports various device platforms, like Win32, Windows Mobile 2003 or Sharp Linux to run mobile business solutions.

February 2005

15


The Development Toolkit helps mobile application developers to define Smart Synchronization data models that are normally used between the mobile applications on the mobile device and the backend systems. Any SAP NetWeaver-based system can be configured as a Mobile Infrastructure middleware system. Only SAP Web AS (ABAP and Java) is required. On the client side, the Mobile Client component (SAP MI Client 2.5) is required, alongside the mobile applications that your business scenarios demand. Depending on your requirements, you may either install a separate SAP Mobile Infrastructure system 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 new version of SAP Mobile Infrastructure is released and you would like to deploy the new features, you could immediately upgrade a standalone SAP Web AS to the new release. In contrast, you would not enjoy this advantage by using the 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 Service Marketplace 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 be supported 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 are documented.

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

SAP Exchange Infrastructure 3.0 With the role of an Integration Server, SAP Exchange Infrastructure should be installed on a dedicated SAP Web Application Server. However, with some restrictions, it can also share the same SAP Web AS with other applications (for example, SAP ECC). SAP does not recommend this shared operation mode for a production environment. The following restrictions apply: •

You must simultaneously upgrade all components that share the same SAP Web Application Server. SAP XI is normally used with multiple SAP applications {for example, SAP ECC, Master Data Management (MDM), and so on} in a communication network. The release level of SAP XI must correspond to the release level of the newest

February 2005

16


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 (for example, MDM), then an SAP XI upgrade may be required. You may pursue one of two options to carry out the SAP XI upgrade. With the first option, you can simultaneously 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, you must 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 project basis. 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 SAP NetWeaver Master Guide or the individual component installation guides, which are located in SAP Marketplace at service.sap.com/nw04installation.

4.2 SAP NetWeaver Rapid Installer SAP NetWeaver Rapid Installer is an installation and configuration wizard that reduces the implementation of SAP Enterprise Portal along with other software components and selected SAP Business Packages from days to hours. SAP NetWeaver Rapid Installer enables you to lower total cost of ownership by reducing the time required to install, deploy and configure SAP NetWeaver Enterprise Portal and Business Packages to a minimum. SAP NetWeaver Rapid Installer also provides backend connectivity to systems for Enterprise Resource Planning (ERP), Business Warehouse (BW), Customer Relationship Management (CRM) and SAP Computing Center Management Systems (CCMS). It enables you to easily connect to these systems through a pre-configured portal with a minimum of interaction and configuration time. SAP NetWeaver Rapid Installer installs a clearly defined set of business scenarios for mySAP ERP 2004 and mySAP CRM 4.0. Thus the SAP NetWeaver Rapid Installer allows an easy and rapid step into the world of SAP NetWeaver and SAP Enterprise Portal for mySAP ERP and mySAP CRM customers and also for customers who prefer to install SAP Enterprise Portal stand-alone without additional business packages. Two versions of SAP NetWeaver Rapid Installer are available for SAP NetWeaver ‘04:

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

SAP NetWeaver Rapid Installer 2.1 is based on SAP NetWeaver ’04 Support Package Stack 10.

February 2005

17


You cannot use SAP NetWeaver Rapid Installer 2.0 or 2.1 to install components of earlier releases of SAP NetWeaver ’04. Both versions of SAP NetWeaver Rapid Installer comprise the following SAP NetWeaver components:

Portal Platform

Knowledge Management (including Search and Classification [TREX])

Collaboration

SAP Web AS Java 6.40

They also install the following software components:

Business packages with Employee Self Service (ESS) and Manager Self Service (MSS) business scenarios (prerequisite: mySAP ERP 2004 is installed) SAP Self Service (XSS) 5.0 which is based on SAP NetWeaver 04 Java Stack and connects to the backend functions in the ERP system. For more information on SAP XSS, see SAP Service Marketplace at service.sap.com/erp-inst Æ mySAP ERP 2004. Business packages with business scenarios for mySAP CRM (prerequisite: mySAP CRM 4.0 and SAP BW 3.5 is installed)

An SAP System Landscape Directory (SLD) if you want SAP NetWeaver Rapid Installer to 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 this information and check if SAP NetWeaver Rapid Installer 2.0 or 2.1 is a viable alternative for you 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 and software requirements and pre-installation steps. You can find this document and additional information on the SAP NetWeaver Rapid Installer DVD (for both versions) in the folder Documentation.

DVD Order Process Versions 2.0 and 2.1 of SAP NetWeaver Rapid Installer can be ordered from the SAP Software Catalog. To access the SAP Software Catalog, see SAP Service Marketplace at service.sap.com/swdc. In the detailed navigation area, choose Ordering SAP-Software. The SAP Software Catalog opens in a separate window. In the right-hand window, choose SAP NetWeaver → SAP NetWeaver Rapid Installer 2.0 or SAP NetWeaver Rapid Installer 2.1.

February 2005

18


Limitations You can use the SAP NetWeaver Rapid Installer as a viable alternative for installing SAP Enterprise Portal (plus other software components). Note the following limitations: 1. Platform availability One of the following combinations of operating systems and databases are required for installation:

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

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

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. An additional J2EE cluster environment can be set up by using the standard SAPinst installation tool. 3. Scalability and Sizing SAP NetWeaver Rapid Installer installs an SAP Enterprise Portal which is optimized for a small number of business users (about 200 concurrent users). But you are not limited to this scenario: You can scale the system and add new hardware according to the standard portal sizing.

February 2005

19


4.3 Industry Add-ons If an Industry Solution (IS) Add-on is running in your source system, then keep in mind that an 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/3 releases. For more information on the integrated functionality, consult SAP Note 700778 at service.sap.com/notes . Customers who have implemented IS Add-ons should review the industry-specific upgrade guides 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 Industryspecific Component

SAP R/3 3.1I-4.6B

Aerospace & Defense

SAP Aerospace & Defense

Add-on (4.0B, 4.5B)

Aerospace & Defense

SAP Discrete Industries

Apparel & Footwear

SAP R/3 Enterprise 47x110


mySAP ERP 2004

integrated into SAP Discrete Industries

Not supported

Not supported

Not supported

Not supported

Add-on

Add-on

Not supported

Add-on

SAP Apparel & Footwear

Add-on (3.1I, 4.5B)

Add-on

Not supported

Not supported

Add-on

Automotive


Not supported

Add-on

Add-on

Not supported

Add-on

Banking

SAP Banking

Add-on (4.0B, 4.6B)

Add-on

Industry Extension

Industry Extension

Industry Extension

Consumer Products

SAP Beverage

Not supported

Add-on

Not supported

Industry Extension (limited)

Industry Extension (limited)

Consumer Products

SAP Catch Weight Management

Not supported

Not supported

Not supported

Add-on

Not supported

Engineering, Construction & Operations

SAP Engineering & Construction

Add-on (4.5B)


Not supported

Not supported

Not supported

Financial Service Providers

SAP Corp. Finance Management

Not supported

Add-on

Industry Extension

Industry Extension

Industry Extension

Healthcare

SAP Patient Management

Add-on (4.0B)

Add-on

Add-on

Add-on

Not supported

Industry Solution

February 2005

SAP R/3 4.6C

SAP ECC 5.0

20


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

SAP R/3 3.1I-4.6B

High Tech

SAP High Tech

Add-on (4.5B, 4.6B)

High Tech


Higher Education & Research



mySAP ERP 2004


Not supported

Not supported

Not supported

Not supported

Add-on

Add-on

Not supported

Add-on

SAP Campus Management

Not supported

Add-on

Add-on

Add-on

Not supported

Insurance

SAP Insurance FS-CD

Add-on (4.5B, 4.6B)

Add-on

Add-on

Add-on

Not supported

Insurance

SAP Insurance FS-CM

Not supported

Add-on

Add-on

Add-on

Not supported

Insurance

SAP Insurance FS-CS

Not supported

Add-on

Add-on

Add-on

Not supported

Insurance

SAP Insurance FS-RI

Not supported

Add-on

Add-on

Add-on

Not supported

Media

SAP IS-M

Add-on (4.0B)

Add-on

Add-on

Add-on

Not supported

Mill Products

SAP Cable Solution

Add-on (3.1I, 4.5B)

Add-on


Not supported

Not supported

Mill Products

SAP Mill Products

Add-on (4.5B, 4.6B)

Add-on


Not supported

Not supported

Mill Products


Not supported

Not supported

Add-on

Not supported

Add-on

Mining

SAP Mining

Add-on (4.6B)

Add-on

Not supported

Add-on

Not supported

mySAP PLM

SAP Environment, Health & Safety

Add-on (4.5B, 4.6B)

Add-on

Industry Extension

Industry Extension

Industry Extension

Oil & Gas

SAP Oil & Gas – IS-Oil

Add-on (4.0B, 4.6B)

Add-on

Not supported

Add-on

Not supported

Industry Solution

February 2005

SAP R/3 4.6C

SAP ECC 5.0

21


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

SAP R/3 3.1I-4.6B

Oil & Gas

SAP Oil & Gas – JVA

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

Public Sector

SAP Funds Management

Public Sector



mySAP ERP 2004

Add-on

Industry Extension

Industry Extension

Industry Extension

Add-On (4.0B, 4.6B)

Add-on

Industry Extension

Industry Extension

Industry Extension

SAP HR Public Sector

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

Add-on

Industry Extension

Industry Extension

Industry Extension

Public Sector

SAP Public Sector PSCD

Not supported

Add-on

Add-on

Add-on

Not supported

Telecommunication

SAP RM-CA

Add-on (4.6B)

Add-on

Add-on

Add-on

Not supported

Utilities

SAP IS-U/CCS

Add-on (4.6B)

Add-on

Add-on

Add-on

Not supported

Utilities

SAP ISU/FERC

Add-on (4.6B)

Add-on

Add-on

Industry Extension

Industry Extension

Utilities

SAP ISWASTE

Not supported

Add-on

Add-on

Add-on

Not supported

Industry Solution

SAP R/3 4.6C

SAP ECC 5.0

Definitions: •

Industry Extension: Industry-specific component is integrated into and shipped as part of SAP 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 available on 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 Enterprise or SAP ECC releases.

•

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

•

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

Industry-specific functionality is not in scope of the present document. However, whenever possible, this guide mentions industry-specific aspects.

February 2005

22


4.4 SAP Solution Manager SAP provides you with SAP Solution Manager as the platform that will support the implementation and operation of mySAP ERP 2004. Using SAP Solution Manager enables you to take advantage of SAP’s full support and gives you the opportunity to leverage the broad 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 is available with SAP Solution Manager as of Release 3.1 SP20 or SAP Solution Manager Release 3.2 SP4. In your mySAP ERP project, perform the following activities inside SAP Solution Manager •

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, installation and configuration of SAP Solution Manager

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

Benefits and usage scenarios

SAP Solution Manager – Learning Maps available on SAP Service Marketplace at service.sap.com/rkt-solman or service.sap.com/solutionmanager

Additional information

SAP Service Marketplace at service.sap.com/solutionmanager

Central Note for “SAP Solution Manager Key”

SAP Note 805390

Each mySAP ERP (or SAP NetWeaver) system landscape must be assigned to one SAP Solution Manager. SAP Solution Manager is the required platform to efficiently support the implementation and operation of your SAP solution. In the event of a support-relevant incident within your SAP system landscape, SAP Support requires remote access to the SAP Solution Manager that hosts the affected system landscape. SAP Solution Manager plays a key role with regard to supportability and monitoring of system landscapes. We recommend that you get familiarized with this topic, which is discussed in the SAP NetWeaver Master Guide at service.sap.com/nw04installation.

February 2005

23

5 mySAP ERP 2004: Technical Overview

5 mySAP ERP 2004: Technical Overview 5.1 mySAP ERP Components Having discussed SAP NetWeaver, the foundation upon which mySAP ERP is built, we now provide an overview of ERP-relevant components from an application point of view.

mySAP ERP 2004 Software Components Additional Components ABAP Components

Java Components

SAP ITS 6.20 SAP Business Connector 4.7

SAP SRM

Add-ons based on NW ABAP

Java Web Applications

SAP SRM Server 5.0

Learning Solution 3.0 (Frontend)

IPC Web App 4.0

ECC 5.0

SEM-BW 4.0

PI 2004_1_500

FINBASIS 3.0

ISA WAC 4.0

Biller Direct 3.0

EA-IPPE 300 EA-RETAIL 500 EA-PS 500 EA-HR 500

LSO Content Player 3.0

E-Recruiting 3.0 Catalog Content Management 1.0

EA-GLTRADE 500

cProject Suite 3.1

EA-FINSERV 500

WFM Core 110_640

EA-DFPS 500 EA-APPL 500

SAP XSS 5.0

BI CONT 3.5.2

SAP_HR 500 SAP_APPL 500

NW ’04 ABAP Stack

Internet Pricing & Configurator (J2SE) IPC 4.0

Portal Content Business Packages

SAP Solution Manager 3.1

Mobile MI Client 2.5 Mobile Sales for ERP (MRS) 2.0 Mobile Time Sheet 1.6 Mobile Travel Expenses 1.6 Mobile Asset Management 2.5 Mobile Direct Store Delivery 2.0

LSOOP 3.0 Offline Player

Frontend XI Content

LSOAE 3.0

XI Content for Applications

SAP GUI

NW ‘04 Java Stack

NetWeaver ’04 Additional Components

Fig. 4: Overview of the mySAP ERP 2004 components

The constituent parts of ERP Central Component (ECC) 5.0 shown above cannot be installed individually. Nevertheless, support packages for each subcomponent continue to be produced. Therefore, each subcomponent, if needed, can be patched separately. All subsequent figures in this document that display system landscapes solely display one component – SAP ECC 5.0 – which comprises all subcomponents shown in Figure 4, inside the ECC 5.0 box. WFM Core requires a separate license. Note that some Industry Solution add-ons have been integrated into SAP ECC 5.0. For more information on this topic, see SAP Note 700778. The availability of IS-Add-ons and ISExtensions is summarized in Section 4.3. Depending on the key capabilities or business processes you intend to deploy, you will install the add-ons shown within the frame “Add-ons based on NetWeaver ABAP” explicitly. All add-

February 2005

24


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 J2EE components, combined in one single installation tool as ERP Java Components. Therefore, if you want to install one (or more) of these components, you will require the ERP Java Components 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 Plugin enables this integration. R/3 Plug-In releases are downward compatible with all releases of the SAP components still in mainstream maintenance. Therefore, you may also integrate lower releases of these components, which means that existing business scenarios will still be 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 certain constraints, you can install many of these components on a single host, provided that certain prerequisites are fulfilled. In this section, you will find information how to set up a minimal landscape, in which all of the key functional areas can be deployed. Several possibilities exist to distribute these components among various hosts. The distribution depends on many factors such as sizing, security, hardware, and so on. In principle, you can choose almost any distribution of components to hosts between the minimal system landscape – described in this section – and a maximum distributed landscape, 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 you would 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 for test and demonstration purposes only. To ensure performance, scalability, high availability and security, do not use a minimal system landscape as your production landscape. For further information about setting up productive system landscapes, see SAP Service Marketplace at service.sap.com/ti. As you prepare to establish your minimal system landscape, consider the following points. •

You must provide sufficiently sized servers. Technically speaking, with sufficiently sized hardware, it is possible to install all components on a single server. Due to performance requirements, however, it is recommended to use a minimum of three servers. For information about hardware sizing, see SAP Service Marketplace at service.sap.com/sizing.

February 2005

25


•

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.1 require a large amount of memory and make substantial demands on the host performance of the CPU. If you want to implement ADS, EP 6.0, XI and TREX in a minimal landscape, consider the hardware sizing recommendations provided above.

•

Inform yourself about the supported platforms for each component you wish to install. Some components may feature platform restrictions. For more information, refer to SAP Service Marketplace at service.sap.com/platforms .

•

Due to high performance and memory demands it is recommended that you install 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 system as SAP ECC for a productive environment, see below.

•

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

Operating Business Information Warehouse and SAP ERP Central Component (SAP ECC) in the same system and in a production environment is solely supported on a project basis. If you are interested in implementing this setup, contact SAP. The same restriction applies for the joint installation and productive operation of SAP Enterprise Portal with SAP ECC or SAP XI with SAP ECC on a shared SAP Web Application Server. If installed in a shared system, a common client for SAP BW 3.5 and SAP ECC 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, you can manage these users by defining a “User Store” or “UME” (User Management Engine) client in the ERP Central Component system. This client makes all users “known” to J2EE, the Enterprise Portal and the Exchange Infrastructure (XI). To this end, users are created in the UME client and assigned the role SAP_J2EE_GUEST.

•

If you install IPC on the main server, you should install an additional database for it. This is a requirement of the Internet Sales scenario.

The following diagram shows an example of a minimal system landscape for mySAP ERP.

February 2005

26


ERP Host

SRM Host

ABAP Components

SAP ECC

Add-ons based on NW ABAP

SAP ECC 5.0

cProject Suite 3.1

Java J2EE Components Java Web Applications ISA WAC 4.0

SAP SRM Server 5.0

Web AS Java 6.40

Web AS ABAP 6.40

IPC Web App 4.0 WFM Core 110_640

Adobe Document Services 1.0

Catalog Content Management 1.0

RDBMS SAP ITS 6.20

Biller Direct 3.0 SAP XSS 5.0

BI CONT 3.52

LSO Content Player 3.0

E-Recruiting 3.0

SAP Business Connector 4.7

SAP Content Server 6.30 SAP DB

Learning Solution 3.0 (Frontend)

IPC 4.0

XI Content XI Content for Applications

SEM-BW 4.0

EP 6.0 Host

FINBASIS 3.0

BW Components XI Components Web AS ABAP 6.40

Web AS Java 6.40

Business Packages for Applications Content Management & Collaboration 6.0 Portal Platform 6.0

RDBMS

TREX 6.1

Web AS Java 6.40

IPC 4.0 RDBMS

RDBMS

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 installed individually. 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 J2EE components, combined in a single installation as ERP Java Components. The ERP Java Components are installed with the SAPinst tool. If you wish to use any of the Java Web Applications shown in Figure 5, then you must use the ERP Components DVD (see Section 8). All SAP NetWeaver components are part of the ERP solution shipment. The installation sequence for these components is explained in the next section.

Certain business processes described in the next sections require the use of Internet Transaction Server 6.20. This is indicated in the “Remarks” column of the respective Software Component Matrix of each key capability. For additional information, see SAP Service Marketplace at service.sap.com/notes → SAP Note 741821. For business processes that require SAP SRM Server (Supplier Relationship Management) we recommend that you use a separate server. On this server you may also install, for example, SAP Catalog Content Management, SAP Business Connector, ADS, SAP Content Server and IPC.

February 2005

27


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 to obtain a full-fledged system landscape.

Before you start the installation, it is imperative that you know which components are required for the business processes you plan to use. It is not recommended to install all components as a matter of course. Only install those components that are required for the business processes you will use. For more information about the required components, review the software component 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 mySAP ERP 2004. Without this Key, the installation process cannot continue. For further 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 Enterprise Extensions, as shown in Figure 5. The installation also includes the SAP 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 Æ SAP ECC 5.0.

2.

Install the ABAP Add-ons, including BI CONT 3.52 (or 3.53), FINBASIS 300, ERECRUIT 300, SEM-BW 400, LSOFE 300, CPROJECTS 310 and WFMCORE 110_640. Note that FINBASIS 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). Set heap size to 1024MB and PermSize to 256MB. If you plan to operate your SAP Exchange Infrastructure on the SAP ERP Central Component host or if you plan to install your Java Web Applications on this server, you should install SAP J2EE in the add-in mode. (For production use, however, you should operate a separate SAP XI system, and depending on your requirements, a separate J2EE server in standalone mode, where your web applications are installed.) Note that a J2EE add-in installation is mandatory for the XI Java Components. For all other components (Web Applications, Enterprise Portal), we recommend installing a standalone J2EE. service.sap.com/nw04installation Æ Installation Æ Installation Guide Web AS Java 6.40 :

February 2005

28


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 single installation. The BW Java components are optional for the mySAP ERP key capabilities. For more information, see SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Guide - SAP Business Warehouse 3.5.

5.

Install SAP Exchange Infrastructure (XI) 3.0 Java Components and subsequently configure the local SLD (System Landscape Directory). As stated before, the XI Java Components require 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 separate server. For more information, see SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Guide - SAP Exchange Infrastructure 3.0.

6.

Install Search and Classification (TREX) 6.1. For performance reasons, this component is often operated on a separate server. For more information, see SAP Service Marketplace at service.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. This component will be used for certain Internet Sales scenarios, but not for Operational Procurement 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, regarding EBPP/payments, a large number of open items may cause a high consumption of memory and CPU capacity. For more information, see SAP Service Marketplace at service.sap.com/notes Æ SAP Note 741821 (Release restrictions for SAP ERP 2004). The Installation Guide for the ERP Java Components can be found at service.sap.com/erp-inst Æ mySAP ERP 2004 Æ ERP Java Components

9.

Optional: Install SAP GUI 6.20 or 6.40. Actually, this component can be installed at any time, since it is installed on the client(s). Note that SAP GUI is mainly required for administrators and power 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.

February 2005

29


Installation Sequence – Portal Host Software To Be Installed/Sequence 1.

Install SAP Web AS Java 6.40. Install the J2EE in standalone mode (see below). Set heap size to 1024MB and PermSize to 256MB. service.sap.com/nw04installation Æ Installation Æ Installation Guide Web AS Java 6.40 :

2.

Install SAP Enterprise Portal (EP) 6.0, including CMC, if required. Because EP 6.0 currently does not support an add-in installation, and because it requires a large amount of memory and makes substantial demands on the host performance of the CPU, it, too should be installed on a separate server. For installation information, consult SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Æ SAP EP

3.

Install the required Business Packages, which are also referred to as “Portal Content.” They can 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 Service Marketplace 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 technical components 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 you elect to pursue this approach, ensure that you select a platform that is valid for all the components you plan to install. Software To Be Installed/Sequence 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 .

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 Note 705060 (CCM 100 Installation with SAINT).

3.

Install SAP Web AS Java 6.40. If required, install the J2EE in add-in mode. You can also choose to install this J2EE in standalone mode. (As a matter of fact, a standalone installation mode is generally recommended). To maximize performance, set heap size to 1024MB and PermSize to 256MB. For more information, see SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Æ Installation Guide Web AS Java 6.40 :

February 2005

30


4.

Install Adobe Document Services 1.0, noting thereby platform restrictions. For more information, see SAP Service Marketplace at service.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 certain scenarios, like Procurement with SAP SRM, but not for Internet Sales. An additional database 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 a separate 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 it is installed on the client(s). Note that SAP GUI is mainly required for administrators and power users. Moreover, certain mySAP ERP processes, which are not yet entirely portalbased, 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

February 2005

31

6 Key Functional Areas of mySAP ERP

6 Key Functional Areas of mySAP ERP Powered by SAP NetWeaver, the open integration and application platform, mySAP ERP combines core ERP functionality with portal-based collaboration across the extended enterprise. MySAP ERP gives companies better control of their assets as well as business processes such as financial supply chain management, e-recruiting and profitability assessments of employees, departments and customers. MySAP ERP allows companies to regain active control of their whole administrative and operations environment to increase efficiency and profitability. MySAP ERP enables new levels of business process and technology integration while laying the foundation for incremental evolution of the solution. The mySAP ERP Business Map, displayed below, encompasses all key functional areas within 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).

mySAP ERP 2004 End-User Service Delivery Analytics

Strategic Enterprise Management

Financials

Financial Supply Chain Management

Human Capital Management

Sales and Service

Corporate Services

SAP NetWeaver™

Workforce Analytics

Management Accounting

Corporate Governance

Workforce Process Management

Supplier Collaboration

Production Planning

Operations Analytics

Financial Accounting

Talent Management

Procurement and Procurement Logistics Execution Product Development and Manufacturing

Financial Analytics

Inventory & Warehouse Management

Manufacturing Execution

Enterprise Asset Management

Sales Order Aftermarket Sales Professional-Service Management and Service Delivery Real Estate Management

People Integration

Project Portfolio Management

Information Integration

Workforce Deployment

Outbound and Inbound Logistics Product Development

Transportation Management

Life-Cycle Data Management

Global Trade Incentive & Commission Services Management

Travel Management

Environment, Health & Safety

Process Integration

Quality Management

Application Platform

Fig. 6: mySAP ERP 2004 Business Map

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

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

February 2005

32


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) and Employee Self-Service (ESS). The related functionality is used in company-wide business processes, thus extending across almost all mySAP ERP key capabilities. Manager Self-Service is designed for use by line managers, team- and project leaders. It contains 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 business operations to the results from business analytics, thus improving the decision-making process. At the same time, Analytics helps you optimize business processes across functions to improve overall business performance. •

Financials

mySAP ERP Financials provides a complete financial management and accounting solution for a broad range of industries. The solution enables your enterprise to optimize its financial supply 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, and growth. mySAP ERP Financials enables superior control and integration of the financial and business information essential to strategic and operational decision-making. It improves management of internal controls, simplifies financial analysis, and enables adaptive business processes. With mySAP ERP Financials, you can transform finance from an administrative function into a value-focused and strategic business process in its own right. •

Human Capital Management

To compete effectively, you must align all corporate resources – including employees – with business objectives. You must transform traditional HR functions into a comprehensive program for human capital management (HCM). With mySAP ERP Human Capital Management (mySAP ERP HCM), you can maximize the value of your employees and align employee skills, activities, and incentives with business objectives and strategies. mySAP ERP HCM also provides the tools to manage, measure, and reward individual and team contributions. Designed for global business, mySAP ERP HCM supports payroll functions, regulatory requirements, and best practices for more than 50 countries. It integrates with existing business systems and can be customized to meet your requirements. • Procurement and Logistics Execution Using Procurement in mySAP ERP, your enterprise can pursue, for every type of good or service to be procured, the commensurate procurement method – from employee self-service activities to sophisticated plan-driven approaches. Logistics Execution supports processes for Inventory Management and Warehouse Management as well as for Transport Execution.

February 2005

33


• Product Development and Manufacturing Product Development and Manufacturing helps you manage the entire life-cycle of productrelated Master Data, including product structures, routings and documents from invention to phase-out. By ensuring immediate access to the most current data, Product Development and Manufacturing ensures that your production planning and execution activities proceed smoothly. • Sales and Service Sales and Service addresses the sales- and customer-focused processes that your enterprise 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 your service organization maintains customer satisfaction by monitoring service orders and other subsequent activities. •

Corporate Services

Corporate Services supports all functions that directly impact core business processes or that can be applied in several areas – as in the case of Quality Management, for example, which relates 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 following sections contain the software components that are either mandatory or optional for the corresponding key capability. If a component is mandatory for at least one business process of 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 as optional. 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 both mandatory and optional. To avoid confusion, the respective processes are indicated in the “Remarks” column, so that you can determine which processes do (or do not) require which software components. If nothing is indicated in the “Remarks” column, then the component is either mandatory or optional 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 to understand how the different technical components interact, and which dependencies must be considered during the implementation phase. They also demonstrate a typical distribution of components among multiple hosts. The design of an actual system landscape, however, is influenced by individual, customerspecific requirements, such as high availability, security and performance. Such requirements, ultimately determine the dimensions of the infrastructure that you should implement.

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

February 2005

34


6.1 End-User Service Delivery 6.1.1 Overview End-User Service Delivery consists of two functional areas: Manager Self-Service (MSS) and Employee Self-Service (ESS). The related functionality is used in company-wide business processes, thus extending over all key capabilities. From a business management standpoint, customers usually implement ESS and MSS together, in a common system landscape, since both processes can be integrated in the same Enterprise Portal. However, it is also possible to implement only one of these processes or implement them on separate systems (for example, due to performance or security considerations). SAP MSS provides line managers, team leaders and project leaders and department heads throughout the enterprise with tools to help them accomplish their goals quickly and easily. Central departments such as Controlling or HR can present personalized information in the user’s portal, enabling managers to find “their” information in “their” portal, in the right place at the right time. Using SAP ESS, employees maintain their own personal information and control many administrative transactions and other processes handled by HR staff. The goal is to streamline 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 move through life and work changes, by combining applications with support information. Further information about the key capabilities and business processes that comprise this key functional 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 key functional area End-User Service Delivery of mySAP ERP 2004.

February 2005

35


SRM System

NW BW System

SAP SRM

SAP BW

SAP SRM Server 5.0

BI CONT 3.5.2

SAP CCM 1.0 Web AS ABAP 6.40

Web AS ABAP 6.40

RDBMS

RDBMS

ECC System

EP 6.0 Server

SAP ECC

Frontend (PC) BP for MSS Web Browser

SAP ECC 5.0

BP for ESS

Adobe Reader 6.0.2

ERECRUIT 300

Content Management & Collaboration 6.0

Mail Software

Web AS ABAP 6.40

Portal Platform 6.0

Web AS Java 6.40 RDBMS

J2EE Server MSS 100 ESS 100 PCUI_GP 100

RDBMS

Search & Classification

XSS

TREX 6.1

Adobe Document Services 1.0 Web AS Java 6.40 RDBMS

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

It is not recommended to install all components on one host. Rather, the components can be distributed among several hosts, as displayed in Figure 7. Several possibilities are available to distribute the components, so this diagram provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In 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 additionally need 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 SAP Solution 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, for the technical implementation of End-User Service Delivery. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40

SAP ECC 5.0

Mandatory

Optional

x

x

SAP E-Recruiting 3.0

x

SAP SRM Server 5.0

x

February 2005

Remarks Section 7.1.1 To benefit from the new Web Dynprobased Self Services functionality, you must either install SAP ECC 5.0 or upgrade your R/3 to SAP ECC 5.0 (see SAP Note 752312.) Section 7.2.1 Optional for Employee Self-Service (ESS), if you would like to integrate eRecruiting into ESS. Section 7.2.7 Optional for Employee Self-Service, if you want to use the integration with Enterprise Buyer Professional (EBP.) Section 7.2.8

36


Component (cont.)

SAP CCM 1.0 Portal Platform 6.0

Mandatory

x

Remarks SAP Catalog Content Management 1.0 can be installed on any system based on SAP Web AS ABAP 6.40. In the above example it is installed in the SRM system. Section 7.2.6 Section 7.1.2 Optional component of SAP Enterprise Portal. It can be used for the Manager Self-Services. Section 7.1.2 Mandatory for Manager Self-Service (Web Dynpro Services.) For an explanation of the availability of MSS Business Packages, see below. Section 7.1.2

x

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

x x

Content Management & Collaboration 6.0 BP for Manager SelfService (mySAP ERP 2004) 60.1 BP for Employee SelfService (mySAP ERP 2004) 60.1 Search & Classification (TREX) 6.1 SAP Web AS Java 6.40

SAP XSS 500 Adobe Document Services 1.0

x

x x

x x

SAP IGS 6.40

x

Internal SAP ITS

x

February 2005

Section 7.1.8 Section 7.1.1 XSS is absolutely required if you would like to implement the Web Dynpro-based services. XSS consists of the subcomponents MSS 100, ESS 100 and PCUI_GP 100. Subcomponents ESS 100 and PCUI_GP 100 are mandatory for Employee SelfService; subcomponents MSS 100 and PCUI_GP 100 are mandatory for Manager Self-Service. For more information on XSS refer to Section 7.2.11. Mandatory only, if you want to create new Adobe interactive forms. Mandatory for Manager Self-Service, for BW reporting. Section 7.1.4 Mandatory for Manager Self-Service, for BW reporting. Section 7.1.5

x

SAP BW 3.5 BI Content Add-on (3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

SAP GUI 6.20 or 6.40

Optional

x x

x

Section 7.1.4 Required within WAD to display charts. Mandatory for MSS Team Calendar and MSS/ESS Leave Requests and Approvals Section 7.1.11 Not an independent component. It is integral part of SAP Web AS 6.40. Mandatory for Manager Self-Service Report Selection. See SAP Service Marketplace at service.sap.com/sap-its. Required only for displaying ABAP Dynpro-based screens (as in an administrator’s PC.) Section 7.1.10

37


Component (cont.)

Mandatory

Optional

Adobe Reader

x Mail system (for example, Microsoft Outlook)

x

Remarks Mandatory as local installation on the user’s PC to view PDF files of ESS services like Total Compensation Statement, Salary Statement, and so on. Mandatory as local installation on the user’s PC to view Adobe interactive forms for Personnel Change Requests and Recruiting.

Optional for Employee Self-Service

Before installing the Business Package for MSS you should know which services you would like to use. If required, you can combine the worksets of the Business Packages MSS 60.1 (Java Portal Components) with MSS 60.1 (mySAP ERP 2004) in one SAP Enterprise Portal 6.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 to ECC 5.0. Refer to SAP Note 752312. The following table summarizes the existing functionality and worksets of the two MSS Business Packages. MSS 60.1 – Java Portal Components

MSS 60.1 (mySAP ERP 2004) – Web Dynpro

Overview: Attendance Overview, Phone List, Reminder of Dates

Overview: Homepage Concept

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

Attendance: Team Calendar (based on Database of Request), Details can displayed from the Team Calendar

Employee Review: Employee Profile, Team Viewer, Compensation Information, Personnel Development, Employee Documents, Appraisal Overview, Edit Appraisal, Objective Settings and Appraisals

Employee Review: not yet available on Web Dynpro!

Personnel Change Requests: Eleven processes with JSP forms available

Personnel Change Requests: Adobe Interactive Form integration, described in SAP Notes 741821 and 761246

February 2005

38


MSS 60.1 – Java Portal Components (continued)

MSS 60.1 (mySAP ERP 2004) – Web Dynpro

Recruiting: Position Overview, Vacancy request, Applicant Tracking – Integrated with HR-Recruitment Component

Recruiting: E-Recruiting integration. Requisition Request and Status Overview, Candidate Assessment and Status Overview – Integrated with E-Recruiting

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

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

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

Compensation: not yet available on Web Dynpro

Quota Planning and Transfer

Headcount Planning (renamed), Transfer Headcount (renamed)

Depending on the worksets and functions you would like to provide to your managers, you can use 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, you can 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(mySAP ERP 2004).] In contrast, the Employee Review workset is available with MSS 60.1 (Java Portal Components.) To provide your managers with the functionality they need you can create a manager role in EP 6.0 with the Team Calendar and the Reporting workset from the Business Package MSS 60.1 (mySAP ERP 2004) and the Employee Review workset from the Business Package MSS 60.1 (Java Portal Component).

If you would like to use Business Package MSS 60.1 (Java Portal Component), additional or other software components may be required. For more information, see SAP Help Portal at help.sap.com Æ Documentation Æ SAP NetWeaver Æ Release ’04.

February 2005

39


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 specific requirements should ultimately determine the most suitable option. If you decide to install XSS and Enterprise Portal on the same J2EE instance, you should consider using SAP NetWeaver 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 at service.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 (which is part of SAP Web AS 6.40.) Moreover, note that some country-specific scenarios 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 the iViews you plan to use. As for third-party software (for example, Galileo, Amadeus), refer to Section 6.8.5 “Travel Management.” These components may be required to fill iViews belonging to travel selfservice 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 Backend system SAP R/3

Release •

R/3 4.0B – 4.6C

•

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

Remarks BP MSS 60.1 (Java Portal Components) SAP R/3 Enterprise 4.7, Extension Set 2.0 (min. SP2) is only required for iViews that use Enterprise Compensation Management (ECM)

Backend system SAP ECC

•

ECC 5.0

For MSS you can combine the worksets of the Business Packages MSS 60.1 (Java Portal Components) with MSS 60.1 (mySAP ERP 2004) in one Enterprise Portal 6.0.

SAP Enterprise Portal

•

6.0 SP 2

•

6.0 (on 6.40)

Currently, no upgrade from EP 6.0 (SP2) to EP 6.0 (on 6.40) exists

February 2005

40


Component (continued)

Release

Remarks

•

SAP BW 2.1C + Support Package 09 or above (For this release you also need an SAP Internet Transaction Server (ITS) on the same host)

•

SAP BW 3.0B + Support Package 03 or above

•

SAP BW 3.1 Content

•

SAP BW 3.2 Content or above

SAP ITS

•

6.20

You need SAP ITS for SAP BW 2.1C and the reporting iViews Reports and Selection Criteria, for which SAP GUI for HTML is required. You also need SAP ITS for iViews in ESS within the MSS workset.

Business Package for Manager Self-Service

•

60.1 (Java Portal Component)

•

60.1 (mySAP ERP 2004)

This Business Package represents the Java frontend. It runs on the SAP J2EE Engine of SAP Enterprise Portal. For instructions on installing this Business Package, review SAP Note 642775.

•

For backend SAP R/3 4.0B – 4.6C, you need WP-PI 500_46C patch 03 or above

•

For SAP R/3 Enterprise 4.70, you need WP-PI 500_620 patch 03 or above.

•

For SAP ECC you need not to concern yourself with WP-PI since it is included in PI_BASIS 2004_1_640

•

2004.1 with at least SP1

SAP BW

SAP Enterprise Portal Plugin (WP-PI)

SAP R/3 Plug-in (PI)

This system is only required for SAP BW Web Reporting

If you would like to use the Employee Documents iView (available with MSS BP 60.1, Java Portal Components), consult SAP Note 640634. SAP recommends that you install the current support packages to the components listed on the table.

February 2005

41


You are required to implement SAP R/3 Component Organizational Management. Furthermore, it is mandatory to maintain staff assignment (organizational units, positions and assigned persons, O-S-P) with manager positions in Organizational Management. Integration between SAP R/3 Components Organizational Management and Personnel Administration must be active. Also, you must complete the Enterprise Portal installation before you start installing the Business Package. We recommend that you test the portal installation sufficiently before you install the BP MSS. Review composite SAP Note 568576 for 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 ESS services 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 Dynprobased services on a medium-term. The allowed combinations for ESS depend on a number of factors, for example, the R/3 release concerned, and the SAP Enterprise Portal or ESS menu that is used. The table below provides an overview of the components and how they are combined. ESS Release

R/3 Release

Portal / Menu to access ESS

Business package from Service Marketplace

ESS 4.5

R/3 4.5 including ITS

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 including ITS

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

Business package for ESS (4.6C / Enterprise)

ESS Enterprise

R/3 Enterprise including ITS

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

Business package for ESS (4.6C / Enterprise)

ESS 4.6C/ ESS Enterprise

R/3 4.6C including ITS or R/3 Enterprise including ITS 6.20

ESS mySAP ERP 2004

SAP ECC 5.0 (with ITS 6.20, if ITSbased services are used)

Business Package* for ESS (4.6C / Enterprise)

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

Business Package for ESS 60.1

*) Restricted release ESS 4.6B, 4.6C and Enterprise can be used in the Enterprise Portal (EP) 5.0 and EP 6.0. The necessary business packages are can be downloaded from SAP Service Marketplace at service.sap.com/swdc Æ Download Æ Installations and Upgrades

February 2005

42


Æ 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.1 can 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 therefore available 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-Business Procurement (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 least Release 4.6B. The function that enables users to start a service on a different ITS is offered as 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 release the industry solution is based, you can implement all ESS services available for the respective R/3 core release.

Browser Support Browser support depends on the SAP R/3 component system under consideration. For information 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.

February 2005

43


6.2 Analytics Analytics

Strategic Enterprise Financial Analytics Management

Operations Analytics

Workforce Analytics

6.2.1 Overview Analytics provides functionality for strategic enterprise management, financial analytics, operations analytics and workforce analytics. It assists you in adapting your business operations to the results from business analytics, thus improving the decision-making process. At the same time, Analytics helps you optimize business processes across functions to improve overall business performance. Further information about the key capabilities and business processes that comprise this key functional 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). For further information on Analytics, see SAP Service Marketplace at service.sap.com/businessanalytics Æ Analytics in mySAP ERP in Detail.

6.2.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Analytics of mySAP ERP 2004.

NW BW System SAP BW SEM-BW 400 FINBASIS 300

EP 6.0 Server BI CONT 3.5.2

Front end

Web AS ABAP 6.40

BP for BUA Content Management & Collaboration 6.0

Web Browser

RDBMS

Portal Platform 6.0 Web AS Java 6.40

ECC System RDBMS

SAP ECC SAP ECC 5.0


Web AS ABAP 6.40

RDBMS TREX 6.1

Fig. 8: Sample System Landscape for Analytics

February 2005

44


It is not recommended to install all components on one host. Rather, the components can be distributed among several hosts, as displayed in Figure 8. Several possibilities are available to distribute the components, so this diagram provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In 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 additionally need a dedicated system for SAP Solution Manager. 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 a Business Information Warehouse system, you are required to install and activate the BI Content addon. 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 SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document. SAP BW 3.5 and PI Basis 2004.1 are part of the NetWeaver ABAP Stack, i.e. they are included in the upgrade or installation. You also need SAP Internet Graphics Services 6.40 for 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 and Information Note 760874.) Furthermore, a minimum of NW stack 11 for SAP Web AS ABAP 6.40 is required. For more information on SAP’s Stack Strategy, see SAP Service Marketplace at service.sap.com/sp-stacks. For SEM 4.0 installation-specific information, review SAP Note 724418.

February 2005

45


6.2.3 Strategic Enterprise Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Strategic Enterprise Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40

Mandatory x

Optional

SAP ECC 5.0

x

x

SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) FINBASIS 300 SEM-BW 4.0 Portal Platform 6.0 Content Management & Collaboration 6.0 TREX 6.1

x x x x x x x

Internal SAP ITS (part of SAP Web AS 6.40) BEx Web Application Designer (WAD)

x

SAP IGS 6.40

x


x

Adobe Framemaker 7.0 Crystal Reports

x x

February 2005

x

Remarks Section 7.1.1 The process "Legal & Management Consolidation" can be implemented in one of two ways: 1) Using OLAP-based SEM-BCS, SAP ECC 5.0 is not required here. 2) Using R/3-based EC-CS, SAP ECC 5.0 is mandatory in this case. For some implementations, SAP ECC 5.0 is therefore mandatory, while for others it remains optional. Section 7.2.1 Part of SAP NetWeaver ABAP Stack. Section 7.1.4 Section 7.1.5 Section 7.2.5 Section 7.2.4 Section 7.1.2 Section 7.1.2 Section 7.1.8 Optional for “Legal & Management Consolidation.” See SAP Service Marketplace at service.sap.com/sap-its. Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Required to display ABAP Dynpro screens (as in the administrator’s PC.) Section 7.1.10 Optional for the Balanced Scorecard (required only if a “Briefing Book” should be produced from the Balanced Scorecard Data) Third-party software

46


6.2.4 Financial Analytics The following software components are either mandatory or optional, as indicated below, for the technical implementation of Financial Analytics. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) FINBASIS 3.0 SEM-BW 4.0 Portal Platform 6.0 Content Management & Collaboration 6.0 BP for Business Unit Analyst 60.1 BEx Web Application Designer (WAD)

Mandatory x x x

Optional

Remarks Section 7.1.1 Section 7.2.1 Section 7.1.4

x x x x

Section 7.1.5 Section 7.2.5 Section 7.2.4 Section 7.1.2

x

Section 7.1.2 x

Section 7.1.2

SAP IGS 6.40

x

Section 7.1.4 Required within WAD to display charts. Section 7.1.11

SAP GUI 6.20 or 6.40 Power SIM (Simulation) Oros ABC (SAS)

x x x

Section 7.1.10 Third-party software Third-party software

x

6.2.5 Operations Analytics The following software components are either mandatory or optional, as indicated below, for the technical implementation of Operations Analytics. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) SEM-BW 4.0 Portal Platform 6.0 Analytics-related Business Packages (BP for BUA) BEx Web Application Designer (WAD)

February 2005

Mandatory x x x

Optional

x


x

Section 7.1.5 Section 7.2.4 Required if Business Packages are used. Section 7.1.2

x

Section 7.1.2

x

Section 7.1.4

x

47


Component (cont.)

Mandatory

Optional

SAP IGS 6.40 SAP GUI 6.20 or 6.40

x x

Remarks Required within WAD to display charts. Section 7.1.11 Section 7.1.10

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

Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) SEM-BW 4.0 Portal Platform 6.0 BP for BUA BEx Web Application Designer (WAD)

Mandatory x x x

Optional

x x

x

Section 7.1.5 Section 7.2.4 Mandatory, if Business Packages are used. Section 7.1.2 Section 7.1.2

x x

Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.10

x

x

SAP IGS 6.40 SAP GUI 6.20 or 6.40



February 2005

48


6.3 Financials Financials

Financial Supply Chain Management

Financial Accounting

Corporate Governance

Management Accounting

6.3.1 Overview Further information about the key capabilities and business processes that comprise this key functional 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.3.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Financials of mySAP ERP 2004.

NW BW System SAP BW SEM-BW 400 FINBASIS 300 BI_CONT 3.5.2

EP 6.0 Server

ECC System SAP ECC

Front end BP for Credit Management

RDBMS

SAP ECC 5.0

BP for Payer Direct

Web Browser

Web AS ABAP 6.40

SAP Business Connector

Web AS ABAP 6.40

Portal Platform 6.0 RDBMS Web AS Java 6.40

RDBMS

SAP BC 4.7

NW XI System SAP XI J2EE Server XI Content for FINBASIS and PI FSCM Biller Direct 3.0 XI Components Web AS Java 6.40 Web AS ABAP + Java 6.40 RDBMS RDBMS

Fig. 9: Sample System Landscape for Financials

It is not recommended to install all components on one host. Rather, the components can be distributed among several hosts, as displayed in Figure 9. Several possibilities are available to distribute the components, so this diagram provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In 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 additionally need a dedicated system for SAP Solution Manager. Note that a database is always installed together with the stand-alone SAP J2EE 6.40 (SAP Web AS 6.40.) FSCM Biller Direct does not require a database, because it has no persistent data. Depending on your specific requirements, FSCM Biller Direct may also be installed on

February 2005

49


the SAP Web AS (Java) of the SAP ECC system; if you only plan to deploy FSCM Biller Direct 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 a Business Information Warehouse system, you are required to install and activate the BI Content add-on. This component is installed with the SAINT tool. For detailed information on technical configuration or the configuration of business scenarios, refer to the Component Installation Guides and the Configuration Documentation in SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document.

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

Mandatory

Optional

Remarks

SAP Web AS ABAP 6.40 SAP ECC 5.0

x x

x

SAP BW 3.5

x

x

BI Content Add-on (Release 3.5.2 or 3.5.3)

x

x

FINBASIS 3.0

x

Section 7.1.1 Section 7.2.1 Mandatory for “Cash & Liquidity Management”; relevant (but optional) only for “Credit Management,” “Dispute Management”, “Collections Management” and “Treasury & Risk Management.” Section 7.1.4 Relevant (but optional) only for “Credit Management,” “Dispute Management”, “Collections Management” and “Treasury & Risk Management.” Section 7.1.5 Mandatory for “Credit Management”, “Dispute Management” and “Collections Management.” Section 7.2.5 Relevant (but optional) only for “Cash & Liquidity Management.” Section 7.2.4 Mandatory for “Electronic Presentment & Payment.” Section 7.1.1 Mandatory for “Electronic Presentment & Payment” (See SAP Notes 713540 and 713534); only optional for “Dispute Management” and “Collections Management.” Section 7.2.13 Relevant (but optional) only for “Electronic Presentment & Payment.” See SAP Note 571530 Relevant (but optional) only for “Dispute Management” and “Collections Management.” Section 7.1.4

SEM-BW 4.0

x


x

FSCM Biller Direct 3.0

x

x

SAP Business Connector 4.7, Core Fix 3 (minimum)

x

BEx Web Application Designer (WAD)

x

February 2005

50


Component (cont.)

Mandatory

Optional

x

Remarks Required within WAD to display charts. Section 7.1.11 Relevant (but optional) only for “Credit Management” and “Electronic Presentment & Payment.” Section 7.1.2 Mandatory only for “Credit Management.” Section 7.1.3 Relevant (but optional) for “Credit Management.” Section 7.1.3

x

Mandatory only for “Credit Management” Section 7.1.3

x

Section 7.1.10

SAP IGS 6.40

x

Portal Platform 6.0

x

SAP XI 3.0

x

x

XI Adapter Framework 3.0 XI Content for FINBASIS 300 and PI_2004_1_500

x


Using SAP Exchange Infrastructure is mandatory for Credit Management. For all other processes 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 a dedicated 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 Service Marketplace at service.sap.com/nw04installation Æ SAP XI.

6.3.4 Financial Accounting The following software components are either mandatory or optional, as indicated below, for the technical implementation of Financial Accounting. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD) SAP IGS 6.40 Portal Platform 6.0 SAP GUI 6.20 or 6.40

February 2005

Mandatory x x

Optional

x


x

Section 7.1.5

x

Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.2 Section 7.1.10

x x x

51


6.3.5 Management Accounting The following software components are either mandatory or optional, as indicated below, for the technical implementation of Management Accounting. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content 3.5.2 Add-on Bex Web Application Designer (WAD)

Mandatory x x

Optional

x x x

SAP IGS 6.40 Portal Platform 6.0 SAP GUI 6.20 or 6.40

x x x

Remarks Section 7.1.1 Section 7.2.1 Section 7.1.4 Section 7.1.5 Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.2 Section 7.1.10

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

Mandatory

Optional

x

Remarks System Audit Part of the AIS is contained in SAP Web AS 6.40 starting with SP5. Section 7.1.1 Section 7.2.1 Mandatory for “Business Risk Management,” only optional for “Management of Internal Controls” and “Transparency for Basel II.” Section 7.1.4 Mandatory for "Management of Internal Controls" and optional for "Transparency for Basel II." Section 7.2.5 Mandatory for "Business Risk Management" and optional for "Management of Internal Controls" and "Transparency for Basel II." Section 7.2.4 Optional for “Business Risk Management.” Section 7.1.5 Only Mandatory for “WhistleBlower Complaints.” See SAP Service Marketplace at service.sap.com/sap-its.

x

Optional for “Business Risk Management.” Section 7.1.4


x x

SAP BW 3.5

x

x

FINBASIS 3.0

x

x

SEM-BW 4.0

x

x

BI Content 3.5.3 Add-on*

x

x

Integrated SAP ITS (part of SAP Web AS 6.40) BEx Web Application Designer (WAD)

February 2005

52


Component (cont.)

Mandatory

Optional

SAP IGS 6.40

x

Portal Platform 6.0

x

Remarks Required within WAD to display charts. Section 7.1.11 Optional for “Management of Internal Controls” and “Whistle Blower Complaints.” Section 7.1.2


x

Section 7.1.10

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


February 2005

53


6.4 Human Capital Management Human Capital Management

Talent Management

Workforce Process Management

Workforce Deployment


6.4.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Human Capital Management of mySAP ERP 2004. J2EE Server Front End (PC) Authoring Environment

XSS 500

ECC System SAP ECC

LSOCP 300 Content Player

LSOAE 300 JDK

Web AS Java 6.40 SAP ECC 5.0

Web Browser RDBMS

LSOFE 300

EP 6.0 Server BP for Learning Solution

Front End (PC)

ERECRUIT 300

BP for MSS

Web AS ABAP 6.40

Learner Environment

BP for ESS

LSOOP 300 Offline Player


Web Browser

Portal Platform 6.0

RDBMS

Web AS Java 6.40

NW BW System SAP BW

RDBMS

Laptop MTS + MTR 1.6 Mobile Client 2.5

BI CONT 3.5.2

Search & Classification TREX 6.1

NW MI System Web AS ABAP 6.40 Web AS ABAP + Java 6.40

RDBMS

Fig. 10: Sample System Landscape for Human Capital Management

It is not recommended to install all components on one host. Rather, the components can be distributed among several hosts, as displayed in Figure 10. Several possibilities are available to distribute the components, so this diagram provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In 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 additionally need a dedicated system for SAP Solution Manager.

February 2005

54


Neither Content Player (LSOCP) nor XSS have persistent data. The database displayed in the figure belongs to SAP J2EE 6.40 (SAP Web AS Java 6.40.) For detailed information on technical configuration or the configuration of business scenarios, refer to the Component Installation Guides and the Configuration Documentation in SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document.

6.4.3 Talent Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Talent Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

Mandatory x x

Optional

E-Recruiting 3.0 Learning Solution (LSOFE 300)

x

x

x

x


x

x

Content Player (LSOCP) 3.0

x

x

SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

x

x

x

x x

Remarks Section 7.1.1 Section 7.2.1 Mandatory only for “Recruiting.” Section 7.2.7 Mandatory only for “Enterprise Learning.” Section 7.2.7 Only mandatory for “Enterprise Learning.” Section 7.1.1 Only mandatory for “Enterprise Learning.” Section 7.2.7 Optional for all Employee LifeCycle Management processes. Section 7.1.4 Optional for all Employee LifeCycle Management processes. Section 7.1.5

SAP IGS 6.40 Portal Platform 6.0

x x

BP for Learning Solution

x

Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.2 See information below and Section 7.1.2

x

Mandatory for “Recruiting”; optional for “Enterprise Learning.” Section 7.1.2

Content Management & Collaboration (CMC) 6.0

x

TREX 6.1

x

x

Offline Player (LSOOP) 3.0

x

x

Authoring Environment (LSOAE) 3.0

x

x

Mandatory for “Recruiting”; optional for “Enterprise Learning.” Section 7.1.8 Mandatory only for “Enterprise Learning.” Section 7.2.7 Mandatory only for “Enterprise Learning.” Note that a JDK is required for the authoring environment. Section 7.2.7

x

Section 7.1.10


SAP Learning Solution and E-Recruiting are discussed in Sections 7.2.3 and 7.2.7 of this document, in connection with the LSO and ERECRUIT components.

February 2005

55


6.4.4 Workforce Process Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Employee Transaction Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content 3.5.2 Add-on BEx Web Application Designer (WAD)

Mandatory x x

Optional

x x x

SAP IGS 6.40

x


x

XSS 500

x

Portal Platform 6.0

x

BPs for MSS and ESS

x

SAP MI Server 2.5 (included in SAP Web AS 6.40)

x

Remarks Section 7.1.1 Section 7.2.1 Section 7.1.4 Section 7.1.5 Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Required for the SAP J2EE Applications. Section 7.1.1 Required, if self-service applications are used. Refer to the XSS installation options in Section 6.1.2. For more component information see Section 7.2.11

SAP MI Client 2.5 Mobile Time Sheet (MTS) 1.6 Mobile Travel Expenses (MTR) 1.6 Mobile Development Kit 2.5

x x

Section 7.1.2 Required, if self-service applications are used. Refer to Sections 6.1.2 and 7.1.2 Middleware server required if mobile scenarios are planned. Section 4.1 Installed on the mobile clients. Section 4.1 Section 7.2.14-5

x x

Section 7.2.15 Section 4.1


x

Section 7.1.10

February 2005

56


6.4.5 Workforce Deployment The following software components are either mandatory or optional, as indicated below, for the technical implementation of Workforce Deployment. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 Portal Platform 6.0 BP for Employee Self-Service 60.1 SAP Mobile Infrastructure Server 2.5 MI Client 2.5 Mobile Development Kit 2.5 Mobile Time Sheet (MTS) 1.6 Mobile Travel Expenses (MTR) 1.6 SAP GUI 6.20 or 6.40

Mandatory x x

Optional

x

Remarks Section 7.1.1 Section 7.2.1 Section 7.1.2 Refer to Sections 6.1.2 and 7.1.2

x x

Section 4.1 Section 4.1 Section 4.1 Section 7.2.14-5

x x

Section 7.2.15 Section 7.1.10

x

x x

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


February 2005

57


6.5 Procurement and Logistics Execution Procurement

Procurement and Logistics Execution

Supplier Inventory & Warehouse Outbound and Transportation Collaboration Management Inbound Logistics Management


6.5.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Procurement and Logistics Execution of mySAP ERP 2004.

SRM System

NW BW System

J2EE Server

SAP SRM

SAP BW SAP XSS 500

SAP SRM Server 5.0

BI CONT 3.5.2

Adobe Document Services 1.0

SAP CCM 1.0 Web AS ABAP 6.40

Web AS ABAP 6.40

Web AS Java 6.40

IPC 4.0

RDBMS

RDBMS RDBMS

EP 6.0 Server

ECC System SAP ECC

BP for External Procurement

Front End (PC) SAP GUI

SAP ECC 5.0

Web Browser

BP for Supplier Order Collaboration

Adobe Reader 6.0.2

BP for MSS

Mail Software

Web AS ABAP 6.40

BP for ESS

RDBMS


NW XI System

Portal Platform 6.0

SAP XI

Web AS Java 6.40


XI Content: SAP APPL, SRM SERVER and CCM

RDBMS

XI Components Web AS ABAP + Java 6.40

TREX 6.1 RDBMS

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


February 2005

58


Certain business processes require the use of Internet Transaction Server 6.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 SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document.

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

Mandatory

Optional

Remarks


x x

SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3)

x

x

x

x

Section 7.1.1 Section 7.2.1 Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.4


x

Mandatory only if Operations Analytics is used. Section 7.1.4

SAP IGS 6.40

x

Required within WAD to display charts. Section 7.1.11

SAP SRM Server 5.0 SAP Catalog Content Management 1.0

x

x

SAP IPC 4.0 for SRM

Portal Platform 6.0 Content Management & Collaboration (CMC) 6.0

BP for Employee Self-Service

February 2005

x

x

x

x

x

x

x

Mandatory only for “Self-Service Requisitioning” and “Role: Purchasing Agent.” Section 7.2.8 Optional for “Self-Service Requisitioning.” Section 7.2.6 Optional for “Self-Service Requisitioning.” Section 7.2.10 Mandatory only for Role: “Purchasing Agent” Section 7.1.2 Mandatory only for “Self-Service Requisitioning.” Section 7.1.2 Optional for “Self-Service Requisitioning” (within ESS). Section 7.1.2

59


Component (cont.)

Mandatory

BP for Manager Self-Service

Optional

x

BP for External Procurement

x

x


x

x

SAP XSS 5.0 Adobe Document Services 1.0 SAP XI 3.0 (part of SAP Web AS 6.40) XI Content for SAP_APPL 500, SRM_SERVER 5.0, CCM 1.0 (with latest SPs)

SAP ITS internal or external

x

Remarks Optional for “Self-Service Requisitioning” (within MSS). Section 7.1.2 Mandatory only for Role: “Purchasing Agent.” Section 7.1.2 Required for the SAP J2EE applications. Section 7.1.1 Optional for “Self-Service Requisitioning” (within ESS/MSS.) Section 7.2.11

x

x

x

x

Optional for “Self-Service Requisitioning.” Section 7.1.3 Mandatory only for “Self-Service Requisitioning” (within ESS/MSS). See Section 7.1.9 and SAP Service Marketplace at service.sap.com/sap-its.

x

Section 7.1.10

x

x


Mandatory only for Supplier Collaboration Scenario for MRO material. Section 7.1.3

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, for the technical implementation of Supplier Collaboration. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

February 2005

Mandatory x

Optional

Remarks Section 7.1.1

x x

x


x

x

Section 7.1.4

x

Section 7.1.4

60


Component

Mandatory

SAP IGS 6.40

Optional x

x

Remarks Required within WAD to display charts. Section 7.1.11

SAP SRM Server 5.0 SAP Catalog Content Management 1.0

x

x

Section 7.2.6

SAP IPC 4.0 for SRM

x

x

Section 7.2.10

Portal Platform 6.0 Content Management & Collaboration (CMC) 6.0 BP for Supplier Collaboration

x

Section 7.1.2

x x

Section 7.1.2

SAP XI 3.0 (part of SAP Web AS 6.40) XI Content for SAP_APPL 500, SRM_SERVER 5.0, CCM 1.0 (with latest SPs)

x

cProject Suite 310 (cFolders)

x

x


Section 7.2.8

x

Required for the Supplier Collaboration Scenario for MRO material. Section 7.1.3

Section 7.1.3 Required for Development Collaboration. A dedicated server for cFolders is generally used. Section 7.2.9 x

Section 7.1.10

6.5.5 Inventory & Warehouse Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Inventory & Warehouse Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40

Mandatory x

Optional

SAP ECC 5.0

x

SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3)

x

x

x

x

Portal Platform 6.0 BEx Web Application Designer (WAD) SAP IGS 6.40

February 2005

x x

x x

Remarks Section 7.1.1 Section 7.2.1 Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.5 Section 7.1.2 Mandatory only if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11

61


Component (cont.) Web SAP Console

Mandatory

Optional

x

x


x

Remarks Mandatory only if Radio Frequency (RF) transactions for mobile data entry are used. Section 7.1.10

6.5.6 Outbound and Inbound Logistics The following software components are either mandatory or optional, as indicated below, for the technical implementation of Outbound and Inbound Logistics. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40

Mandatory x

Optional

SAP ECC 5.0

x


x

x

x

x

x

x

Portal Platform 6.0

x

SAP IGS 6.40

x

Web SAP Console

x


x x

Remarks Section 7.1.1 Section 7.2.1 Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.5 Mandatory only if Operations Analytics is used. Section 7.1.4 Section 7.1.2 Required within WAD to display charts. Section 7.1.11 Mandatory only if Radio Frequency (RF) transactions for mobile data entry are used. Section 7.1.10

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 chain networks. Moreover, by using RFID your enterprise obtains execution benefits such as process 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 and accurate view of inventory – and greatly enhancing the ability to track and trace goods along the supply chain. The end result: reduced costs, faster response to changing customer demand, and an improved ability to have the right product in the right place at the right time. The technology is so effective that organizations such as Wal-Mart, Metro, and the U.S. Department of Defense now require their suppliers to deliver goods with RFID tags.

Note that RFID enabled Supply Chain Execution Processes within mySAP ERP 2004 are available as separate package (separate license model). The package is called “RFID Solution Package for mySAP ERP 2004.”

February 2005

62


The following software components are either mandatory or optional, as indicated below, for the technical implementation of RFID-enabled Logistics Processes. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40

Mandatory x

OLTP system

x

SAP SCM 4.1 EM (Event Manager)

x


x

Auto ID Infrastructure (AII)

x

Auto ID UI 2.1

x

SAP XI 3.0 (part of SAP Web AS 6.40)

x

XI Adapter Framework 3.0

x

XI Connectivity SE 3.0 XI Content 3.0 (SCM 4.1, SCM BASIS 4.1, AUTO-ID 2.1 and EA-APPL 500)

x


Optional

Remarks Section 7.1.1 On-Line Transaction Processing system (for example, SAP R/3 system, SAP R/3 Enterprise, SAP ECC) that is used in the RFID-enabled supply chain execution environment as backend system. SCM Server is part of the mySAP Supply Chain Management solution suite. It requires a separate license. SAP SCM EM is an integrated component of SAP SCM that offers the possibility to process application objects in various application systems and thereby to track events for individual objects, processes or parts of these throughout the entire supply chain. Required for “Outbound Processing /RFID”. Section 7.1.1 Middleware for RFID and automatic identification integration. Required for “Outbound Processing /RFID”. Note that AutoID Infrastructure is not part of the mySAP ERP shipment. It requires a separate license. Mandatory only for “Outbound Processing /RFID”. Section 7.1.3 Mandatory only for “Outbound Processing /RFID”. Section 7.1.3 Mandatory only for “Outbound Processing /RFID”. Section 7.1.3 Required for “Outbound Processing /RFID. Section 7.1.3

x x

Section 7.1.10

For more information on RFID, see service.sap.com/erp Æ mySAP ERP in Detail Æ mySAP ERP Operations Æ mySAP ERP Operations in Detail Æ Inventory and Warehouse

February 2005

63


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, for the technical implementation of Transportation Management. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BW Front end (BEX, Web Interface Builder)

Mandatory x x

Optional

x

Remarks Section 7.1.1 Section 7.2.1 Mandatory only if Operations Analytics is used. Section 7.1.4

x


x


SAP ITS (internal or external)

x

Required for the Web Transactions “Tendering” and “Transportation Planning in corporation with Ext. Service Providers.” Section 7.1.9

Portal Platform 6.0

x

Section 7.1.2


x

Section 7.1.10


February 2005

64


6.6 Product Development and Manufacturing Product Development and Manufacturing

Production Planning

Manufacturing Execution

Enterprise Asset Management

Product Development

Life-Cycle Data Management


6.6.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Product Development and Manufacturing of mySAP ERP 2004.

NW BW System

NW MI System Web AS ABAP + Java 6.40

ECC System (with cProjects) SAP ECC

SEM-BW 400

SAP ECC 5.0

FINBASIS 300

CPROJECTS 310_640

Laptop or Handheld Mobile Asset Management 2.5 Mobile Client 2.5

SAP BW

BI CONT 3.5.2

WFM Core 110 Web AS ABAP 6.40

SAP CCM 1.0

RDBMS

Web AS ABAP 6.40 RDBMS

Web Browser

NW XI System SAP XI cFolders Server XI Content: SAP APPL, CCM, FINBASIS

EP 6.0 Server

CPROJECTS 310_640 Web AS ABAP 6.40

XI Components

BP for Project & Design Collaboration

Web AS ABAP + Java 6.40

RDBMS BP for Products

Frontend

RDBMS BP for Assets



Portal Platform 6.0

Web Browser

Web AS Java 6.40

TREX 6.1 RDBMS

Fig. 12: Sample System landscape for Product Development and Manufacturing

It is not recommended to install all components on one host. Rather, the components can be distributed among several hosts, as displayed in Figure 12. Several possibilities are available to distribute the components, so this diagram provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In 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

February 2005

65


component runs on its own host, or even on multiple hosts. Note that you will additionally need a dedicated system for SAP Solution Manager. The Mobile Asset Management scenario requires SAP Mobile Infrastructure 2.5 (server and client.) Technically speaking, SAP Web AS of the SAP ECC system could also work as SAP Mobile Infrastructure. On the other hand, planning a dedicated SAP Web Application Server for the mobile infrastructure has advantages. For more information, see Section 4.1. MAM 2.5 depends on Plug-in 2004.1, which contains application-related business logic and customizing. For detailed information on technical configuration or the configuration of business scenarios, refer to the Component Installation Guides and the Configuration Documentation in SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document.

6.6.3 Production Planning The following software components are either mandatory or optional, as indicated below, for the technical implementation of Production Planning. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

Mandatory x x

Optional

SAP BW 3.5 BI Content 3.5.2 Add-on BEx Web Application Designer (WAD)

x x

x x

x

x


x x x

Remarks Section 7.1.1 Section 7.2.1 Required only if Operations Analytics is used. Section 7.1.4 Section 7.1.5 Required only if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.2 Section 7.1.10

6.6.4 Manufacturing Execution The following software components are either mandatory or optional, as indicated below, for the technical implementation of Manufacturing Execution. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

Mandatory x x

Optional

x

x

x

x

x

x

SAP IGS 6.40

x

Portal Platform 6.0

x

February 2005

Remarks Section 7.1.1 Section 7.2.1 Mandatory only if Operations Analytics is used. Section 7.1.4 Section 7.1.5 Mandatory only if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Required for role “Plant Manager.” Section 7.1.2

66


Component (cont.)

Mandatory

BP for Manufacturing 60.1 SAP ITS 6.20 SAP GUI 6.20 or 6.40

Optional x x x

Remarks Required for role “Plant Manager.” Section 7.1.2 Section 7.1.9 Section 7.1.10

6.6.5 Enterprise Asset Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Enterprise Asset Management. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

Mandatory x x

MI Client 2.5 Mobile Asset Management (MAM) 2.5

x

Mobile Development Kit 2.5

x

Remarks Section 7.1.1 Section 7.2.1 Relevant (but optional) only for “Maintenance Execution.” Section 7.2.6 Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.5 Mandatory only if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Technical requirement for SEMBW 400. Section 7.2.5 Section 7.2.4 Dedicated Middleware server. Required for MAM. Section 7.1.1 Required only for MAM. Section 4.1 Optional for “Maintenance Execution.” Section 7.2.16 Required only for MAM. Section 4.1

Portal Platform 6.0 Content Management & Collaboration (CMC) 6.0 SAP GUI 6.20 or 6.40

x

Section 7.1.2

x x


SAP CCM 1.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

Optional

x x

x

x

x x

SAP IGS 6.40

x

FINBASIS 300 SEM-BW 400 SAP MI Server (SAP Web AS ABAP + Java 6.40)

x x

February 2005

x

x

67


6.6.6 Product Development The following software components are either mandatory or optional, as indicated below, for the technical implementation of Product Development. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 cProject Suite 3.10

Mandatory

Optional

x

x x x

Section 7.1.1 Section 7.2.1 Section 7.2.9

x x

WFM Core requires a separate license. Refer to SAP Service Marketplace at service.sap.com/contentserver

x

Section 7.1.4

x x


x

Section 7.1.2

x x


WFM Core 110_640 SAP Content Server 6.30 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) SAP ITS Portal Platform 6.0 Content Management & Collaboration (CMC) 6.0 SAP GUI 6.20 or 6.40

Remarks

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 Processes under 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, for the technical implementation of Life-Cycle Data Management. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

Mandatory

Optional

x x

Remarks

cProject Suite 3.10

x

Section 7.1.1 Section 7.2.1 Optional for “Product Structure Management” and “Change & Configuration Management.” Section 7.2.9

WFM Core 110_640

x

WFM Core requires a separate license.

Portal Platform 6.0

x

Section 7.1.2

February 2005

68


Component (cont.)

Mandatory

Optional

Remarks

Content Management & Collaboration (CMC) 6.0

x

Section 7.1.2

BP for Product, Asset, Project & Design Collaboration

x

TREX 6.1

x

SAP Content Server 6.30

x

Section 7.1.2 Relevant (but optional) only for “Document Management.” Section 7.1.8 Relevant (but optional) for “Document Management.” For component information, see SAP Service Marketplace at service.sap.com/contentserver.

EH&S WWI /Windows Word Integration

x

EH&S Expert 2.1

x

ECL Viewer (Engineering Client)

SAP Easy Document Management 3.0 DMS Connector for KM 60.1 SAP GUI 6.20 or 6.40

x

Frontend component. Mandatory only for “Recipe Management.” Frontend component. Mandatory only for “Recipe Management.” Optional for DMS (“Document Management”) and cFolders (“Design Collaboration”). Component version varies, depending on the platform used. For component information, see the mySAP PLM Master Guide in SAP Service Marketplace at service.sap.com/plm-inst → using cProject Suite 3.10. Relevant (but optional) only for “Document Management”. See SAP Note 668100 and SAP Library at help.sap.com Relevant (but optional) only for “Document Management” (DMS).

x

Section 7.1.10

x

x


February 2005

69


6.7 Sales and Service Sales and Service

Sales Order Management

Aftermarket Sales and Service

ProfessionalService Delivery

Global Trade Incentive & Commission Services Management


6.7.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Sales and Service of mySAP ERP 2004.

Laptop or Handheld NW MI System

MDSD 2.0

Front end

Web AS Java + ABAP 6.40

MRS 2.0

NW BW System

Mobile Client 2.5

SAP BW

Web Browser

BI CONT 3.5.2

Web Browser

Web AS ABAP 6.40

ECC System EP 6.0 Server

SAP ECC

RDBMS

Web Server BP for Sales Web Server Plug-in

SAP ECC 5.0 SAP CCM 1.0

Portal Platform 6.0 Web AS Java 6.40

Product Catalog Files


RDBMS

NW XI System SAP XI

J2EE Server


XI Content for CCM FSCM Biller Direct 3.0

TREX 6.1

Web AS ABAP + Java 6.40

IPC Web App. 4.0 RDBMS Internet Sales Web Applications 4.0

Internet Pricing & Configurator

Adobe Server

Web AS Java 6.40

Adobe Document Services 1.0 RDBMS

IPC 4.0 RDBMS


Fig. 13: Sample System Landscape for Sales and Service

It is not recommended to install all components on one host. Rather, the components can be distributed among several hosts, as displayed in Figure 13. Several possibilities are available to distribute the components, so this diagram provides just one example. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In

February 2005

70


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 additionally need 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 SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document.

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

Mandatory

Optional

Remarks

SAP Web AS ABAP 6.40

x

Section 7.1.1

SAP ECC 5.0

x

SAP BW 3.5

x

x

BI Content 3.5.2 Add-on

x

x


x

x

SAP IGS 6.40

x

x


x

x

Internet Sales WAC 4.0

x

Section 7.2.1 Mandatory only for “Role: Internal Sales Representative” and if Operations Analytics is used. Section 7.1.4 Mandatory only for “Role: Internal Sales Representative” and if Operations Analytics is used. Section 7.1.5 Mandatory only for “Role: Internal Sales Representative” and if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Mandatory only for "Internet Sales with mySAP ERP” and if the Portal Platform is used. Section 7.1.1 Mandatory only for “Internet Sales with mySAP ERP.” Section 7.2.12 Optional for “Internet Sales in mySAP ERP” only. Section 7.2.10

SAP IPC 4.0 SAP MI 2.5 Server (included in SAP Web AS 6.40) SAP MI 2.5 Client Mobile Sales for mySAP ERP (MRS) 2.0

February 2005

x x

Mandatory only for “Field Sales.”

x

Mandatory only for “Field Sales.” Mandatory only for “Field Sales.” Section 7.2.17

x

71


Component (cont.)

Mandatory

TREX 6.1

x

Remarks Optional for “Field Sales.” Mass shipment of MDSD is planned for Q3 2005. See Sections 7.2.18 and 7.5.7.1 Required for “Role: Internal Sales Representative.” Section 7.1.9 Mandatory only for “Role: Internal Sales Representative.” Optional for all other processes. Section 7.1.2 Required for “Role: Internal Sales Representative.” Section 7.2.1 Optional for “Internet Sales with mySAP ERP” only. Section 7.1.8


x

Section 7.1.10

SAP Direct Store Delivery 2004 (using MDSD 2.0)

Optional

x

SAP ITS 6.20

x

x

Portal Platform 6.0

x

x

BP for Sales 60.1

x

x

SAP Direct Store Delivery SAP Direct Store Delivery (DSD) is a business process often used in the Consumer Products industry (CP) to sell and distribute goods directly to the customer’s store bypassing the retailer’s warehouses. The Manufacturer gets in direct contact with the customer’s store at the Point-of-Sale. He can use this contact to improve customer retention and customer relationship through personal service. Besides this, he can realize additional sales opportunities and obtain first hand information about the market. With SAP DSD, CP customers have a great opportunity to position their brand against competitors 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 the indirect sales scenario. Key success factors for the high margins in SAP DSD are: •

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

•

Excellent alignment between sales force and distribution through integrated scheduling

•

Low distribution costs through efficient visit control.

The comprehensive closed-loop solution includes end-to-end process integration between the sales force, logistics operations and delivery personnel including the related backend and mobile applications. The SAP DSD mobile application addresses the needs of drivers in any direct-store-delivery situation. It is a tailored solution that enables drivers to perform an array of route transactions on mobile devices in disconnected mode. At the beginning and end of the day, users can seamlessly exchange data between their mobile devices and SAP ECC 5.0 as the respective SAP DSD backend system. The mobile application MDSD 2.0 offers an efficient, intuitive user interface that gives an integrated view of all necessary activities to support delivery personnel and sales representatives in their daily business: e.g. processing tours, visit and visit activities, delivery

February 2005

72


and order processing, invoicing and payment collection, recording driver expenses and ontruck inventory management. It effectively manages transactions in a closed-loop cycle. The following diagram provides an overview of the system landscape for SAP Direct Store Delivery.

ECC System Mobile Device

SAP ECC 5.0

http / https

SAP ECC 5.0, Stack 05 (including DSD Connector, DSD Connector Cockpit, DSD Pricing Data Extractor)

MDSD 2.0 * (Front end) SAP MI Client 2.5 DB2

Web AS ABAP 6.40 (including MI Server 2.5) RDBMS

RFC J2EE Server DSD Admin Console *

*) Included in SAP Mobile DSD 2.0


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

The DSD Connector and the DSD Connector Cockpit, as well as the DSD Pricing Data Extractor, 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 components additionally. Prerequisite is, however, that your SAP ECC 5.0 system is at least on support package stack 5 level (see also service.sap.com/sp-stacks.) The following software components are either mandatory or optional, as indicated below, for the technical implementation of SAP Direct Store Delivery. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 DSD connector, DSD connector cockpit DSD Pricing Data Extractor

Mandatory x x x x

SAP Mobile Infrastructure 2.5 SAP Web AS Java 6.40 SAP Mobile Infrastructure Client 2.5

x x

SAP Mobile DSD (MDSD) 2.0

x

DB2 Everyplace (Mobile database)

x

DSD Administration Console

x

February 2005

x

Optional

Remarks Section 7.1.1 Section 7.2.1 Contained in ECC 5.0 as from Support Package Stack 5 Contained in PI 2004.1 Part of SAP Web AS 6.40 (ABAP). Section 4.1 Section 7.1.1 Section 4.1 General availability planned for Q3 2005. Section 7.2.18 DB2 Everyplace is the only mobile database currently supported Contained in MDSD 2.0. To be installed on the J2EE Engine

73


6.7.4 Aftermarket Sales and Service The following software components are either mandatory or optional, as indicated below, for the technical implementation of Aftermarket Sales and Service. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP CCM 1.0

Mandatory x x

Optional

x

SAP BW 3.5

x

x


x

x

BW Front end (BEX, Web Interface Builder)

x

x

SAP XI 3.0 (part of SAP Web AS 6.40) XI Content for CCM Internal ITS (part of SAP Web AS 6.40) Portal Platform 6.0 SAP GUI 6.20 or 6.40

x x x x x

Remarks Section 7.1.1 Section 7.2.1 Section 7.2.6 For some implementations, this component is mandatory, while for others it is optional. 1) If Operations Analytics is used, then this component is mandatory. 2) If Operations Analytics is not used, then this component is optional. Section 7.1.4. For some implementations, this component is mandatory, while for others it is optional. 1) If Operations Analytics is used, then this component is mandatory. 2) If Operations Analytics is not used, then this component is optional. Section 7.1.5. For some implementations, this component is mandatory, while for others it is optional. 1) If Operations Analytics is used, then this component is mandatory. 2) If Operations Analytics is not used, then this component is optional. Section 7.1.4. Section 7.1.3 Section 7.1.3 See SAP Service Marketplace at service.sap.com/sap-its. Section 7.1.2 Section 7.1.10

If you plan to implement Aftermarket Sales and Service processes that use additional functionality within SAP ERP Enterprise Asset Management – for example, MAM – then additional requirements may exist. See Section 6.6.5.

February 2005

74


6.7.5 Professional Service Delivery The following software components are either mandatory or optional, as indicated below, for the technical implementation of Professional Service Delivery. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

Mandatory x x

Optional

Remarks Section 7.1.1 Section 7.2.1


x

Section 7.1.4

x

Section 7.1.5

cProject Suite 310

x

WFM CORE 110_640 Portal Platform 6.0 SAP GUI 6.20 or 6.40

x x x

x

Section 7.1.4. Required for ‘Project Planning and Scoping’ and ‘Project Resource Planning’. Section 7.2.9 Optional for 'Project Planning and Scoping' and 'Project Resource Planning'. WFM CORE requires a separate license. SAP Note 718626 Section 7.1.2 Section 7.1.10

6.7.6 Global Trade Services The following software components are either mandatory or optional, as indicated below, for the technical implementation of Global Trade Services. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

SAP GTS 3.0

x

Remarks Section 7.1.1 Section 7.2.1 SAP Global Trade Services (for SAP Web AS 6.40) is an add-on that can be installed on the SAP Web AS of the SAP ECC system or on a dedicated SAP Web AS (standalone). This add-on provides additional functions to the Foreign Trade functionality contained in SAP ECC. For more information on SAP GTS, review service.sap.com/gts.


x

Section 7.1.4

x

Section 7.1.5

February 2005

Mandatory x x

Optional

x

Section 7.1.4.

75


Component (continued) Portal Platform 6.0 SAP GUI 6.20 or 6.40

Mandatory

Optional x x

Remarks Section 7.1.2 Section 7.1.10

6.7.7 Incentive & Commission Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Incentive & Commission Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD) SAP IGS 6.40 SAP GUI 6.20 or 6.40

Mandatory x x

Optional

x


x

Section 7.1.5

x


x x


February 2005

76


6.8 Corporate Services Real Estate Management

Corporate Services

Project Portfolio Management

Environment, Travel Management Health & Safety

Quality Management


6.8.2 Technical System Landscape The following diagram shows an example of a full-fledged system landscape for the key functional area Corporate Services of mySAP ERP 2004. Laptop MTS + MTR 1.6 MI Client 2.5

NW MI System Web AS Java + ABAP 6.40

SAP Business Connector

cFolders Server

CPROJECTS 310_640

SAP BC 4.7

Web Browser


ECC System (with cProjects) SAP ECC

EP 6.0 Server

Front end

BP for Products

Web Browser

BP for Assets

SAP ECC 5.0

BP for Design Collaboration

CPROJECTS 310_640 WFM Core 110


SAP CCM 1.0

Portal Platform 6.0

Web AS ABAP 6.40

Web AS Java 6.40

RDBMS RDBMS

NW BW System SAP BW

TREX 6.1 SAP Content Server 6.30 SAP Gateway

BI CONT 3.5.2

NW KW System Web AS Java + ABAP 6.40

Optional


SAP ITS 6.20

Fig. 15: Sample System Landscape for Corporate Services


February 2005

77


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 SAP Solution Manager, referred to in Section 4.4. See also the documentation overview provided in Section 1 of this document.

6.8.3 Real Estate Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Real Estate Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

Mandatory x x


Optional

x


x

Section 7.1.5

x

Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.2 Section 7.1.10

x x x

6.8.4 Project Portfolio Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Project Portfolio Management. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40

SAP ECC 5.0

SAP CCM 1.0

February 2005

Mandatory x

Optional x

x

x

x

Remarks Section 7.1.1 Required for SAP Project System (“Project Planning”, “Project Execution”, “Program Management” and “Interfaces”). Optional for cProject Suite (“Design Collaboration” and “Collaborative Project Management.”) Section 7.2.1 Optional for SAP Project System. Section 7.2.6

78


Component (cont.)

Mandatory

Optional

SAP BW 3.5

x

x


x

x

BW Front end (BEX, Web Interface Builder)

x

x

Remarks Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.5 Mandatory only if Operations Analytics is used. Section 7.1.4

cProject Suite 3.10

x

Section 7.2.9

WFM Core 110_640 Portal Platform 6.0 Content Management & Collaboration (CMC) 6.0

x x

SAP Note 718626 Section 7.1.2

x

Section 7.1.2 Relevant (but optional) only for cFolders (“Design Collaboration.”) Section 7.1.2 Frontend component. Relevant (but optional) only for SAP Project System (“Interfaces”) Optional for cFolders (“Design Collaboration.”) Version varies, depending on the platform used. For component information, consult the mySAP PLM Master Guide in SAP Service Marketplace at service.sap.com/plm-inst → using cProject Suite 3.10. Section 7.1.10

BP Product, Asset, Project & Design Collaboration

x

OpenPS for MS Project

x

ECL Viewer (Engineering Client)

x


x

For more information, see Master Guide “SAP cProject Suite” at service.sap.com/plminst.

6.8.5 Travel Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Travel Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

SAP Business Connector 4.7, Core Fix 3 (minimum)

February 2005

Mandatory x x

x

Optional

Remarks Section 7.1.1 Section 7.2.1 Required for connecting to HRS or Deutsche Bahn Portal (BIBE). For component information, see SAP Service Marketplace at service.sap.com/notes → SAP Note 571530.

79


Component (cont.) SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD) SAP IGS 6.40 Portal Platform 6.0 Content Management & Collaboration (CMC) 6.0 SAP MI Server 2.5 SAP MI Client 2.5 Mobile Travel Expenses (MTR) 1.6 Mobile Development Kit 2.5 SAP GUI 6.20 or 6.40 Galileo Gateway Software Amadeus Proprinter Software Amadeus JCO SAP Gateway Add-on

Mandatory

Optional x

Remarks Section 7.1.4

x

Section 7.1.5

x x x


x x x

Section 7.1.2 Section 4.1 Section 4.1

x x x

Section 7.2.14-15

x x x

Section 7.1.10 Mandatory only if Galileo is used. Relevant (but optional) only if Amadeus is used. Mandatory only if Amadeus is used

6.8.6 Environment, Health & Safety The following software components are either mandatory or optional, as indicated below, for the technical implementation of Environment, Health & Safety. (References to componentspecific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0 SAP BW 3.5 BI Content Add-on (Release 3.5.2 or 3.5.3) BEx Web Application Designer (WAD)

x

x

x

x

SAP IGS 6.40

x

x

Remarks Section 7.1.1 Section 7.2.1 Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.5 Mandatory only if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11

x x


Portal Platform 6.0 SAP GUI 6.20 or 6.40

February 2005

Mandatory x x

Optional

x

x

80


6.8.7 Quality Management The following software components are either mandatory or optional, as indicated below, for the technical implementation of Quality Management. (References to component-specific information are displayed in italics.) Section 6 explains how to read the chart. Component SAP Web AS ABAP 6.40 SAP ECC 5.0

Mandatory x x

Optional

cProject Suite 3.10

x

x


x

x

x

x

x

x

SAP IGS 6.40 Portal Platform 6.0

x x

SAP KW 7.0

x

SAP Easy Document Management 3.0 SAP ITS SAP GUI 6.20 or 6.40

x x x

Remarks Section 7.1.1 Section 7.2.1 Mandatory only for “Quality Engineering (APQP).” Section 7.2.9 Mandatory only if Operations Analytics is used. Section 7.1.4 Mandatory only if Operations Analytics is used. Section 7.1.5 Mandatory only if Operations Analytics is used. Section 7.1.4 Required within WAD to display charts. Section 7.1.11 Section 7.1.2 Relevant (but optional) only for “Quality Engineering (Quality Manual).” Component is part of SAP Web AS ABAP. Section 7.1.7 Relevant (but optional) only for “Quality Engineering (Quality Manual).” See SAP Note 668100 and SAP Library at help.sap.com Section 7.1.9 Section 7.1.10


February 2005

81

7 Information on Software Components

7 Information on Software Components This section provides information on the most important software components of mySAP ERP 2004.

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

7.1 SAP NetWeaver 2004 Components If you would like to know more about SAP NetWeaver and its components, we recommend that you read the corresponding Master Guide, which is located in SAP Service Marketplace at 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 NetWeaver and with this of the mySAP Business Solutions. It provides the technological foundation for all other 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 variants is that you can either operate both the ABAP stack and the Java stack, only the ABAP stack or 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 a runtime environment for ABAP and/or Java applications. SAP Web AS includes a platform for quickly developing and deploying dynamic and collaborative Web applications or other thin-client applications (WAP, PDA, and so on) and includes all proven SAP programming models and technologies. With SAP Web AS, SAP natively supports open Internet standards, including such protocols as HTTP, HTTPS, and SMTP, as well as Internet document standards like HTML and XML. Open integration capabilities provide access to existing SAP and non-SAP applications. All integration facilities supported by SAP are available with SAP Web AS. The Java Connector or the .NET Connector give ABAP applications access to Java or .NET components and vice versa. In addition, the Internet Communication Framework (ICF) of SAP Web AS enables ABAP-written programs to process and distribute HTTP requests directly. As a consequence, SAP Web AS can serve both as an HTTP server and client. It serves as an HTTP server for bringing applications to the user via a Web browser either directly or via a standard Web server. It serves as an HTTP client to access other Web applications for collecting information and data. To complete Web connectivity, SAP Web AS provides full support for sending and receiving e-mails via SMTP.

February 2005

82


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 for the Java cluster.

Database instance SAP Web AS Java has a separate database schema. As a result, a database instance is also 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 Java schema get installed in the same database.

Exception: If your SAP system is running on Informix, a separate MaxDB or IBM DB2 UDB 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 server processes

•

SAP Web AS ABAP + Java system and SAP Web AS ABAP system: gateway and 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 Marketplace at service.sap.com/nw04installation Æ Installation. Refer also to the SAP NetWeaver Master Guide available at the same location.

7.1.2 SAP Enterprise Portal (EP) 6.0 SAP Enterprise Portal consists of the following components: • Portal Platform • Content Management & Collaboration • Search and Classification (TREX) (see Section 7.1.8) • Predefined content (Business Packages) and tools for creating content. With SAP Enterprise Portal, you receive the Portal Platform and Knowledge Management & Collaboration. With the Portal Platform, you get the tools to build portals for your target users,

February 2005

83


while the Knowledge Management platform makes it possible to provide access to documents and multimedia objects that are stored in an organization's distributed document repositories. Collaboration enables virtual teams to work together in synchronous and asynchronous ways, directly within SAP Enterprise Portal. SAP Enterprise Portal provides a role-based, secure and web-based interface to any kind of information, application and services. To run the portal, you need a standard browser on the desktop; no additional software components are required. As part of SAP Enterprise Portal, the Portal Infrastructure provides a secure access to any kind of structured data coming from any kind of business applications, such as SAP, nonSAP, data warehouses, or databases. As a key technology of the Portal Infrastructure, iViews allow an access for reading purposes or for carrying out an operation, such as submitting a form for supplies. A set of portal services is provided to enable iViews to interact with each other such as portal navigation (for example, Dynamic Navigation or the patented Drag&Relate technology), portal eventing, or WorkProtect mode. Portal roles structure and deliver targeted content to each end user. Thanks to the role-based user interface, a company can structure its business processes and deliver business content according to the needs of certain user groups. Besides the role concept, Portal Infrastructure provides 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 user groups ranging from business experts to developers.

mySAP ERP Business Packages Business Packages consist of pre-assembled Portal content that enables your enterprise to complete business tasks. In essence, Business Packages provide out-of-the-box portal applications that can be easily modified to suit a customer's needs. The following table summarizes the Business Packages that are available for the mySAP ERP 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 BP INVENTORY ANALYSIS 60.2 BP MSS 60.1 BP PROCUREMENT ANALYSIS 60.1 BP PRODUCTION ANALYSIS 60.1 BP PROFESSIONAL SERVICES 50.3 BP SALES ANALYSIS 60.1 BP ENV. HEALTH & SAFETY 50.1* BP ASSET SERVICES 50.2 BP SUBCONTRACTING 50.2 BP CUSTOMER CREDIT MGMT. 60.1

February 2005

84


Business Package (continued) BP PRODUCTS 50.3 BP 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 the SDN (Software Developers Network) Portal Content Portfolio. The corresponding address is http://www.sdn.sap.com/ Æ NW Business Content Æ Portal Content Portfolio. There you can also find further information on planned and available BPs, guidelines, and so on. If you prefer, you can also download BPs directly from SAP Service Marketplace at service.sap.com/swdc . We recommend that you always archive the downloaded BPs locally to ensure that you have access to those releases later.

Several objects originating from EP 5.0 Business Packages cannot be displayed in EP 6.0 / NW ‘04. An Import Filter allows you to migrate the EP 5.0 BP objects that are able to run on EP 6.0. See SAP Note 642999. In addition to the Business Packages, SAP provides a number of tools that customers can use to enhance and customize content, including tools for end users, for content administrators, for business users with no coding experience, and for professional programmers.


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

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

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

7.1.3 SAP NW Exchange Infrastructure (XI) 3.0 Based on a native Web infrastructure that leverages open standards, SAP Exchange Infrastructure (SAP XI) makes it possible to manage the broad diversity of highly heterogeneous components from a multitude of vendors and running in various technology environments. The integration capabilities capture shared business semantics and act as a mediator between the services and their technical realizations. It includes technical functions, such as queuing, mapping, and routing. It also establishes an infrastructure for business process management and high-performance execution within and across organizational boundaries.

February 2005

85


Process integration based on SAP XI removes the problems of direct connections by extracting shared collaboration knowledge. These shared business semantics ease the integration of both external and internal components. Instead of directly coding point-to-point interfaces for each new component, the exchange infrastructure allows instant plug-in of new components once per component. This provides the future flexibility needed in today’s fastchanging business world, and it reduces integration costs compared to the direct connection approach. In order to use your SAP NetWeaver system as Exchange Infrastructure system you may need to install the corresponding XI components shown in Figure 2. This depends on your specific requirements. For more information, refer to the related documentation. See also Section 4.1 of this document. XI Content Several SAP Applications make use of XI and deliver XI content which is shipped as part of the application. Process patterns, business scenarios, mapping programs, message interfaces and data types are available in a steadily growing number. The following ERPrelevant XI content is currently available: Component Name and Version XI CONTENT SAP_APPL 500 XI CONTENT EA-APPL 500 XI CONTENT PI 2004_1_500 XI CONTENT PI_BASIS 2004_640 XI CONTENT SAP_BASIS 640 XI CONTENT FINBASIS 300 XI CONTENT CATALOG CCM 1.0 XI CONTENT SRM SERVER 5.0 XI CONTENT BI CONT 3.52

Description XI Content for SAP ECC 5.0 XI Content for Extension Set APPL 5.0 XI Content for Plug-in 2004 XI Content for Plug-in Basis 2004 6.40 XI Content for SAP Basis 6.40 XI Content for Financial Basis 3.0 XI Content for SAP Catalog Content Management 1.0 XI Content for SAP SRM Server 5.0 XI Content for BI Content 3.5.2

Related Documentation: For more information on SAP Exchange Infrastructure, see SAP NetWeaver Master Guide in SAP Service Marketplace at service.sap.com/nw04installation. Also, review SAP Help Portal at help.sap.com (search for XI Content.)

7.1.4 SAP Business Information Warehouse (BW) 3.5 Definition Today’s decision makers urgently need accurate information – a complete and up-to-date picture of their business and their business environment. However, that information is spread over a wide variety of platforms and applications throughout the corporate IT structures. This can make obtaining vital facts and figures a complex and time-consuming task. SAP Business Information Warehouse (SAP BW) is a robust and scalable data warehouse. The reporting tools within SAP BW offer a quick and easy way to gain access to the information you need. SAP BW warehouse management tools let you integrate and store data from sources throughout the organization and beyond – sources that contribute to strategic analysis and decision-making.

February 2005

86


SAP BW largely consists of three functional areas: •

Front end -

•

Administrator’s workbench -

•

•

Report definition and Web publishing Data analysis in BEx Analyzer and a Web browser plus integration of analytical applications into mySAP Enterprise Portals Organization of reports Information distribution 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 document header and document item information. ODS (operation data storage) objects for purchase orders, confirmations, invoices, contracts, bid invitations, and bids have been defined on the basis of ODS technology of the BW.

•

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

Related Documentation: For more information on SAP Business Information Warehouse, see SAP NetWeaver Master Guide in SAP Service Marketplace at service.sap.com/nw04installation.

7.1.5 BI Content Add-on (3.5.2 or 3.5.3) BI Content Add-on (BI CONT 3.5x) delivers predefined, role-based and task-oriented information models (Business Content) for SAP BW. SAP Business Content’s objective is to make relevant information available to specific roles within an enterprise so as to provide these users with exactly the information they need to fulfill their daily tasks within their business. SAP provides a comprehensive set of business content to integrate and analyze all relevant information from a variety of sources and across various applications and industries. Business Content supports Measuring and Analyzing, Planning, Monitoring and Controlling, Optimizing. It enables companies to improve business processes and quickly respond to changing market dynamics by providing business information to executives, analysts and information consumers. The wide-range of Business Content enables customers to shorten the implementation time significantly and helps them to create their own analytical

February 2005

87


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


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 SAP Note discusses incompatible changes to objects delivered with BI Content 3.5.2 Addon.

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 Stack and does not require an explicit installation.

From SAP Basis 6.40 forward, SAP Basis Plug-In includes Enterprise Portal Plug-in, formerly known as Workplace Plug-in (WP-PI). This means that the latter 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 set up 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 and business processes, helping you reduce your costs. In addition, the possibilities to reuse, supplement, and continually update SAP content offers great savings potential. SAP KW provides an information repository for companies of all sizes - including global multilingual companies - with facilities to model structures according to their corporate and market structure. Use SAP KW to adjust and create documentation, manuals and training materials of varying media. Tailor the materials to your specific business processes using the editors and office products your employees know. If you wish, SAP can deliver SAP KW with current SAP materials so that you can immediately begin training your project team and end users and edit the corresponding documentation. SAP KW is shipped with the following content created specifically for SAP solutions: •

Standard delivery: Documentation (context-sensitive online application help)

February 2005

88


•

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 are some other KW-related optional components that you may install, depending on your specific requirements.


For more information, see SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Guide - SAP Knowledge Warehouse.

See also SAP NetWeaver Master Guide in SAP Service Marketplace at service.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 both structured and unstructured text. TREX is based on client/server architecture. The client software is integrated into the application 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 documents and 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 ensure that enough memory exists for all components. Moreover, you must ensure that TREX can use the required main memory space exclusively.


For more information, see SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Guide – Search and Classification (TREX).

7.1.9 SAP Internet Transaction Server The SAP Internet Transaction Server (SAP ITS) combines existing Internet technology with SAP technology and provides reliable access to SAP functions from the Internet or intranets. SAP ITS is an SAP technology component. It is a gateway between one or more Web servers and one or more SAP application servers. Typically, the Web server is an HTTP server, but other protocols such as FTP or Gopher may also be supported. SAP ITS mainly generates HTML pages and enables end users to interact with different SAP systems using a Web browser. SAP ITS also acts as the server component for the SAP GUI

February 2005

89


for HTML and various application scenarios, such as SAP Employee Self-Service or SAP CRM. 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 used with all previous SAP system releases. As a result, older SAP systems can also benefit from the 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 GUI release instead of patching an existing one. The SAP GUI maintenance strategy takes advantage of this feature. In many problem situations, the recommendation is to install a new SAP GUI release, because patches cannot always be provided for previous SAP GUI releases 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 Web Application Server. But SAP GUI 6.20 is basically compatible with mySAP ERP 2004 and most 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 SAP GUI to display Dynpro-based screens (ABAP). It this context, note that some new mySAP ERP functionality does not run under SAP GUI – it requires 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 an SAP Enterprise Portal is installed.

With the localized version of Windows, SAP GUI 6.20 does not work for Unicode and the double byte languages Japanese, Korean, simplified Chinese, and traditional Chinese. Therefore, Asian customers using Unicode must install SAP GUI 6.40. For more information, see SAP Note 508854

Related Documentation: For additional information, see SAP Service Marketplace at service.sap.com/nw04installation Æ Installation Æ SAP Web AS Æ SAP Front end Installation Guide or SAP Components Æ SAP Frontend Components (ITS / GUI Æ SAP GUI for Windows.

February 2005

90


7.1.11 SAP Internet Graphics Services Internet Graphics Service (IGS) constitutes the infrastructure to enable the application developer to display graphics in an Internet browser with a minimum of effort. IGS provides a server architecture where data from an SAP system or another source can be used to generate graphical or non-graphical output. Objectives of the IGS •

Platform independence

•

Extensibility: - Easy integration of new components - Easy integration of new protocols (listeners) that react to new data streams

•

Accessibility: - Using RFC and HTTP (XML) - Data sent from R/3 or system external to R/3

•

Support for a variety of data formats, for example, XML

• Improved scalability/monitoring Examples Examples of components supported by the IGS include: •

• •

Charts For more information on charts read about the Chart Engine. For information about customizing charts read about the Chart Designer. BW-GIS A Geographical Information System solution for the Business Information Warehouse Image Conversion A service for converting one graphic format (for example, GIF) into another (for example, TIFF)


For additional information, see SAP Service Marketplace at service.sap.com/notes → SAP Note 458731 (Internet Graphics Service: Main Note).

February 2005

91


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 successor component of SAP R/3 Enterprise (SAP R/3 4.7) and contains the functionality of SAP R/3 Enterprise (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 Industry Solution 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 of the SAP components still in mainstream maintenance. Therefore, you may also integrate lower releases of these components, which means that existing business scenarios will still be 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.


See SAP Service Marketplace at service.sap.com/erp-inst → mySAP ERP 2004 → SAP ECC 5.0 Æ Installation Guide – SAP ECC 5.0 on :

February 2005

92


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 not require an explicit installation.) R/3 Plug-in (PI) is an interface, which enables the exchange of data between one or several SAP ECC systems and other SAP components. R/3 Plug-in supplies the SAP components with transaction data and master data in real time. It also makes it possible to use SAP application components like SAP SCM or SAP CRM together with certain SAP industryspecific 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 components based on SAP R/3 4.6B or higher SAP R/3 releases. You can order the most recent Plug-in releases free of charge or download it from the SAP Service Marketplace.


For more information, or to download, see SAP Service Marketplace at service.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 of managing and integrating business and learning processes and supporting both e-learning and classroom training, as well as synchronous and asynchronous collaboration. It is fully integrated with mySAP ERP, and includes content authoring, content management, and learning management capabilities, as well as a learning portal. For more information on SAP Learning Solution, see SAP Service Marketplace at service.sap.com/learningsolution. Installation- and upgrade-related information can be found at service.sap.com/erpinst Æ mySAP ERP 2004 Æ SAP Learning Solution 3.0.

Components of SAP Learning Solution SAP Learning Solution consists of the following components: •

LSO (Backend)*

•

LSOFE (Learners Front end)

•

LSOCP (Content Player)

•

LSOOP (Offline Player)

•

LSOAE (Authors Environment)

*) As from mySAP ERP 2004, this functionality is called LSOTM = Learning Solution Training Management) The backend component LSO was a separate add-on required for the Learning Solution Releases 1.0 and 2.0. Now the functionality originally contained in this add-on has been integrated into SAP ECC so that it does not require a supplemental CD anymore (see SAP

February 2005

93


Notes 503468 and 700778). LSO 300 Backend provides you with the following modules: Training Management, Personnel Development, HR Master Data, and Organizational Management. Training Management stores all application data and business functions. This includes, among others, course participants’ master data, learner account, course catalog, 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 a separate Web Application Server (standalone installation). Refer to SAP Notes 529063 and 503907. LSOFE contains a Web-based Learning Portal that provides the learners with personalized access to information and functions. The Learning Portal Front End is based on Business Server Pages (BSPs). SAP ECC communicates with SAP Web AS via RFC, and provides the dynamic content of the BSPs. Note that a Business Package for Learning Solution 2.0 (50.2) is available. This component is optional for LSO 3.0 and can be used with SAP Enterprise Portal 6.0 (NW ’04.) You require this BP if you would like to set up the access to the Learning Portal of LSO 3.0 through SAP Enterprise Portal. LSOCP (Content Player) is a server application that enables you to process the learning content on a particular client PC. The Learning Portal provides Content Player with an appropriate URL, which contains a Content Management (CM) path and additional information (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. When the learner has finished playing the learning unit, LSOCP saves the current course status in the learner account. You may have to install plug-ins in addition to an Internet browser to be able to use the learning 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 own J2EE 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 (Instructional Element Editor, Test Author), and testing (integrated Content Player) course content. It is installed 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) and the central Content Repository (CM or WebDAV server). When you check in the contents, the Publisher Database in the SAP ECC backend system is provided with data. You need Java Development Kit (JDK) for the Authoring Environment. As this component is not part of the SAP shipment, you must download and install it separately. For the recommended JDK versions for your platform and how to obtain them, see SAP Note 709140. Note that you require a Content Management System for your Learning Solution.

Other Components for SAP Learning Solution Aside from the LSO components, the following components can be used with SAP Learning Solution: • • •

SAP Enterprise Portal (including Knowledge Management and Collaboration) Search and Classification (TREX) SAP BW (Business Information Warehouse) 3.5

SAP Enterprise Portal enables access to the Learning Portal, which is a BSP-based (Business Server Pages) application within the LSOFE Add-on. To set up this access, a Business Package for Learning Solution is required (see Section 10.3.1.2.) In addition, SAP Enterprise Portal provides collaboration capabilities and it can be used as a repository for storing and managing static course content using its Knowledge Management functionality. If you do not want to use the Content Management System (CMS) from SAP Enterprise Portal,

February 2005

94


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

A WebDAV-compatible Web server heavily restricts the functions of saving meta data and searching. Therefore, you should only use it as content repository if absolutely necessary. CMS saves extensive attributes to the content files, which can be searched (using tools like TREX).TREX 6.1 provides enhanced search capabilities for authors. By using TREX it is possible to search for content more quickly and easily. Install SAP GUI 6.20 / 6.40 on every computer that needs to access the administrative backend. For the setup of the LSO system landscape you should take the following aspects into account: •

Security: Do you have any security concerns about giving all learners access to your SAP ECC system? If yes, you should run LSOFE on a separate SAP Web Application Server. 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 TCO because you need fewer servers. No additional administration is necessary. If you are using a separate HR system connected to your LSO system, this HR system does not require 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 as installation prerequisite.


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

February 2005

95


7.2.5 FINBASIS 3.0 FINBASIS 3.0 is an Add-On, which can be installed on the NW BW System or any other system that is based on NetWeaver ’04, more precisely, SAP Web AS ABAP. FINBASIS is a technical 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 for procurement 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 data SAP Catalog Search Engine 1. Define views 2. Publish catalog 3. View catalog

You do not necessarily require SAP SRM Server to use SAP Catalog Content Management (SAP CCM.) SAP CCM can be installed on any system based on SAP Web AS ABAP. Although SAP CCM is primarily used in SRM-related scenarios (like “Create Shopping Carts”), you can also use it within mySAP ERP. For example, you can call SAP CCM from a Create Order screen (e.g. maintenance order) within the SAP ECC system.


For more information, see SAP Service Marketplace at service.sap.com/notes → SAP Note 705060 (CCM 100 Installation with SAINT).

7.2.7 SAP E-Recruiting 3.0 Qualified staffing remains a critical success factor for all enterprises, and there is worldwide competition for the best personnel. This “search for the best” places a difficult burden on human resource (HR) directors, many of whom are being deluged with unsolicited resumes.

February 2005

96


How can companies cope with today’s reality while preparing for tomorrow’s? Answer: By combining cost-cutting strategies (for example, employing freelance and part-time talents) with a streamlined, Internet-based recruiting process. SAP E-Recruiting, the new fully Webenabled, end-to-end recruiting solution of SAP, offers companies the recruiting management functions they need to locate appropriate talent. SAP E-Recruiting offers scenarios – for example, employment searches and applications– to external parties via web services. Technical Information: Depending on your requirements, you will choose either to install ERECRUIT as an add-on for 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 NW BW systems, provided that you have implemented BI content at release 3.5.2 or 3.5.3. Before you begin to set up your E-Recruiting system landscape, you should consider the following issues: •

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

•

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

Search and Classification (TREX) is a mandatory component for SAP E-Recruiting (refer to Section 7.1.8). If you already have a TREX 6.0 (with at least SP1) installation, a normal upgrade to version 6.1 is not possible since architecture, configuration files and index structures changed considerably in TREX 6.1. Instead, you need to perform a migration. You will find the corresponding Migration Guide in SAP Service Marketplace at service.sap.com/nw04upgrade Æ Cross NW Æ Component Migration Guide – Search and Classification (TREX). For installation-related information on Search & Classification (TREX) 6.1, see SAP Service Marketplace 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. The following queries are available: •

Requisitions Created

•

Requisition Status Changes

•

Application Sourcing

•

Number of Open Requisitions

•

Time-to-fill

•

Offer vs. Acceptance Rate

•

Application Submittals vs. Offers

•

Candidates’ Qualifications

In addition, E-Recruiting can also be integrated with the new MSS Manager Role and Employee Self-Service. For this integration, you require an SAP Enterprise Portal 6.0 (on SAP Web AS Java 6.40) and the Business Packages MSS and ESS, as well as the Java component XSS 500. A further prerequisite of the MSS integration is that the required mySAP ERP 2004 components should be at a minimum stack level of 4 (consult SAP Service Marketplace at service.sap.com/sp-stacks.)

February 2005

97


Basic System Architecture The following diagram shows the system architecture of a minimal E-Recruiting (standalone) setup.

Internet

Intranet

DMZ

System Administrator (SAP GUI)

Internal Users (Browser - SSO optional)

HTTP(S)

External Users (Web Browser)

SMTP (Mail)

Application Gateway / Proxy Gateway

TREX

E-Recruiting RFC

HTTP(S)

RFC (ALE)

SAP HR / SAP ECC / NW BW

RDBMS

SMTP (Mail)

Firewall

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

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


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 SAP NetWeaver 04 with ERECRUIT 300).

7.2.8 SAP SRM Server 5.0 The SAP Supplier Relationship Management Server (SAP SRM Server) was formerly known as SAP Enterprise Buyer Professional (SAP EBP). SAP SRM Server 5.0 is the leading component of the mySAP SRM 4.0 Solution. Within mySAP ERP, SAP SRM Server 5.0 is required only for certain processes (see also note below). SAP SRM Server, based on SAP Web Application Server, is an application and database instance installation released on several database and operating systems platforms. (See SAP Service Marketplace at service.sap.com/platforms Æ Product Availability Matrix. It enables easy, full-cycle, inter-enterprise procurement. You can create and process

February 2005

98


requisitions, purchase orders, and reservations with or without electronic catalogs; approve and 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 purchasing operations. This helps you streamline requisition processes and, therefore, your entire indirect procurement processes, cutting the overall cost of procurement while providing the purchasing department with visibility and control across the entire procurement chain.

Note that the mySAP ERP 2004 license only covers Self-Service Procurement (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 :

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 to use the cProjects application, then it is most expedient to install cProject Suite on the SAP Web AS of the SAP ECC system. If you are already using cProject Suite 310_620, then upgrade to cProject Suite 310_640.

If you were operating cProject Suite separately from your R/3 system and you plan to upgrade both systems to mySAP ERP 2004, be advised that you cannot merge these two systems into one. You must continue to run both systems separately.

Design Collaboration with cFolders cFolders is a web-based collaboration platform that is dedicated to promoting communication and collaboration among groups of people who work in product development within crossenterprise processes. cFolders enables teams to set up joint virtual work areas on the Internet, in which they can exchange structured information as BOM or CAD models. This approach not only saves on costly travel expenses, but also improves data consistency and significantly reduces project runtimes. cFolders in mySAP PLM offers two processes – the first collaborative, the second competitive. While the collaborative process enables all internal and external parties involved in product development to cooperate in a single joint work area, the competitive process allows you to establish separate work areas for rival suppliers who participate in competitive bidding. It is also possible to connect cFolders in mySAP PLM with end-to-end e-sourcing processes, such as those provided by mySAP SRM.

February 2005

99


cFolders enables SAP customers to communicate with their partners and suppliers via backend objects, without exposing their R/3 or ECC system to them. For instance, suppliers and partners 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 from cFolders to the R/3 or SAP ECC system.

Collaboration Projects cProjects offers a web-based, easy-to-use interface and constitutes a powerful tool for operative project management. cProjects enables you to realize innovative ideas in all kinds of projects, e.g., development projects, projects to simplify internal processes, to implement recognized 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 and quality checks, through to the completion of the project. It also allows you to communicate with external partners or lead customers. cProjects incorporates internationally recognized standards (QS-9000) and is based on methods like for example Advanced Product Quality Planning (APQP) developed in the automobile industry.

Related Documentation: 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 processes product configurations and calculates product prices. SAP Internet Pricing and Configurator (IPC 4.0) requires its own database for Internet Sales scenarios. This IPC cannot be used for SRM procurement. SAP Internet Pricing and Configurator (IPC 4.0) for SRM Procurement does not require a database. 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 two different IPC’s in case you want to use the SRM Procurement scenario and the Internet Sales scenarios simultaneously. You need one IPC for the SRM Procurement scenario (in which the IPC connects to the SRM system) and another IPC for the Internet Sales scenario (in which 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 application, which is deployed with the ERP Java Components package. The most important components of Internet Pricing and Configurator are •

Sales Configuration Engine (SCE, also part of the mobile client installation)

•

Sales Pricing Engine (SPE, also part of the mobile client installation)

•

IPC User Interface (UI)


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

February 2005

100


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

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

Both MSS and ESS require PCUI_GP; neither component can be used without PCUI_GP. If your specific situation demands that you implement Manager Self-Service or Employee Self-Service alone, then you may deploy MSS 100 and PCUI_GP 100 or ESS 100 and PCUI_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 the ERP Release and Information Notes. Note that 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 specific requirements should ultimately determine the most suitable option. If you decide to install XSS and Enterprise Portal on the same J2EE instance, you should consider using SAP NetWeaver 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 at service.sap.com/nw-ri. XSS has been implemented based on SAP Web AS 6.40 technology using the Web Dynpro programming model. This programming model largely replaces the current ESS model that is based on ITS technology. XSS is required only if you would like to use the Business Packages MSS 60.1 (mySAP ERP 2004) 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 backend functions in the SAP ECC System.


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

7.2.12 Internet Sales Web Application (ISA WAC) 4.0 SAP Internet Sales enables you to sell your products and services via the Internet, creating a new, strategic sales channel (E-Selling). You can provide your customers with personalized, interactive, and easy-to-use sales and self-services in a Web shop environment, optimizing

February 2005

101


your sales operations. You can support your consumers in carrying out their business transactions 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 -- without the need for a CRM deployment. You can also develop and manage an effective online sales catalog. And provide customers with online product configuration, easy-to-use shopping basket 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 order processing -- and by reducing human intervention in order-taking and status-checking. Since the solution is quick and easy to implement, you reduce project risk and achieve rapid return on investment. Since it leverages your existing IT infrastructure, you avoid capital expenditures and enjoy lower total cost of ownership. ISA WAC is a J2EE Web application, which is deployed with the package “ERP Java Components.“ Due to its persistence layer, a migration is required, if you have already installed Internet Sales R/3 Edition based on SAP J2EE 6.20 and you would like to upgrade to mySAP ERP 2004. For more information, refer to the ERP Upgrade Master Guide in SAP Service Marketplace at service.sap.com/erp-upgrade .

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



For information on the scenario “Internet Sales in mySAP ERP”, review SAP Service Marketplace 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.0 Instead of sending printed bills, vendors can electronically send bills to their customers and share account information with them. Customers can then pay their invoices on a vendor’s Web site. The bills are paid electronically by credit card or direct debit. Financial Supply Chain Management (FSCM) Biller Direct not only reduces media fragmentation, it also allows vendors to interact with their customers, for example, when processing insufficient payments or providing customer service. FSCM Biller Direct cuts costs and boosts customer retention, giving companies a competitive edge by providing up- and cross-selling options. The new Biller Direct solution of mySAP ERP provides customers with all these benefits and takes the strategy a step further. While most Biller Direct solutions generally only present bill data to customers, the FSCM Biller Direct solution allows bill recipients to check their account balance and view their overall status with the vendor. Biller Direct (BD) is a J2EE Web application, which is deployed with the ERP Java Components package.

February 2005

102


FSCM Biller Direct itself has no own persistence. The database of the SAP ECC backend system 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 the SAP ECC Backend System. A File System is used for storing web.xml-/application-config.xml data and JSPs adapted by customers.



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 the components 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 on laptop computers wherever they are. The laptops do not require a connection to SAP ECC for time 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 their working times. They can save their working time data on the laptop and then transfer it to SAP ECC when they are able to set up a connection. Working time data recorded by users in Mobile Time Sheet can be synchronized with SAP ECC 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 using any 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/erpinst Æ mySAP ERP 2004 Æ Mobile Infrastructure Components

For additional information on Mobile Infrastructure and Mobile Time & Travel for Laptop, consult the Master Guide for SAP NetWeaver, which is located in SAP Service 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).

February 2005

103


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 the 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 and receipts offline regardless of location, using mobile devices (laptops). A connection to the SAP system is not required for offline data entry and editing. The user can enter all of the trip details and receipts information required for trip cost reporting offline and save them on their laptop. They can then transfer these trips to SAP Travel Expense Management when they next have access to the online system.


See Installation Guide in SAP Service Marketplace at service.sap.com/erpinst Æ mySAP ERP 2004 Æ Mobile Infrastructure Components.

For additional information on Mobile Infrastructure and Mobile Time & Travel for Laptop, consult the Master Guide for SAP NetWeaver, which is located in SAP Service 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 rolebased 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 part of the Enterprise Asset Management and Customer Service capabilities within mySAP ERP. Representing a full offline mobile application, MAM provides ready-made scenarios that help field technicians perform their daily activities at customer sites and within plants. MAM 2.5 will integrate into RFID (Radio Frequency Identification), a cross component application that allows 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 or Maintenance orders) and notifications created and assigned to engineers on the ECC server or in the front end. The MAM application targets different roles in an organization. These roles 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 mobile device with connection capability for wireless synchronization. On the mobile device, the Mobile Infrastructure Client 2.5 and the MAM 2.5 application and the MRI component reside. The user can establish connectivity to the Web Server via either HTTP or HTTPS protocols using a wireless WAN or a wireless LAN connection. Upon connectivity, the user can synchronize the data from the backend server and/or from and to the device. This scenario requires the Mobile Infrastructure 2.5 server component, which is part of NetWeaver 2004 as the middleware. In addition, MAM 2.5 is dependent on the Plug-in 2004.1, which contains application related business logic and customizing. The client component is installed via WAR using the Web Console.

February 2005

104



See Installation Guide in SAP Service Marketplace at service.sap.com/erpinst Æ 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 to access front- and back-office business processes and to manage critical sales activities in the field using standard-based personal digital assistants, other popular handheld devices, laptops as well as devices enabled with barcode scanners. The business scenarios provide functions that focus on sales activities for sales representatives. The SAP Mobile sales with mySAP ERP is based on the SAP Mobile Infrastructure, which is a 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 enables synchronization of data from/to the backend system. Also the application requires a client database 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 related business 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.0 A description of the SAP Direct Store Delivery business processes can be found in Section 6.7.3 of this document. The technical component SAP MDSD 2.0 consists of two subcomponents: •

SAP Mobile DSD 2.0 front end component

•

DSD Administration Console

Although delivered together in one technical component, these subcomponents must be installed on different places. Whereas the front end component must be installed on a mobile device (PDA), the DSD Administration Console must be installed on an SAP J2EE Engine 6.40. SAP Mobile DSD 2.0 (front end) runs on PDAs in disconnected mode using the SAP Mobile Infrastructure synchronization mechanism to transfer data between the mobile devices and the SAP ECC 5.0 backend system. There are other components in the backend systems that are equally required for SAP DSD processes to run. However, these components do not need a separate installation: DSD Connector, DSD Connector Cockpit and DSD Pricing Data

February 2005

105


Extractor are part of SAP ECC 5.0; SAP Mobile Infrastructure Server 2.5 is part of SAP Web AS 6.40 (ABAP). SAP MDSD 2.0 requires the SAP Mobile Infrastructure Client 2.5 and the client database on the mobile device. The currently supported mobile database is DB2 Everyplace. 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 be connected to any lower SAP R/3 release.


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

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

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

February 2005

106

8 Media Information

8 Media Information Software Components and DVD / CD Structure This section summarizes the exact location of the required software components on the corresponding DVD(s) and CD(s) shipped with the mySAP ERP 2004 package. If appropriate, references to other sources are also included.

The material numbers of the corresponding DVDs and CDs may change as new updates become necessary. Therefore, make certain that you always use 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 the current version of the installation documentation. For SAP NetWeaver ’04, you can find the relevant 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 SAP Service Marketplace at service.sap.com/swdc. Within the SAP Software Distribution Center, you can download any SAP software component(s) to which your enterprise is entitled. The corresponding authorizations are automatically generated from the licenses. To obtain the software you require, you can either download the corresponding files directly (by simply clicking on the file name) or you can use the SAP Download Manager.

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

February 2005

107

6 Media Information

SAP NetWeaver ’04 SR1 Components

DVD / CD Label

Description / Additional Information

SAP ERP 2004, SAP NetWeaver ‘04 SR1, SAP ECC 5.0 SR1, SAP SRM 4.0 SR1 Installation Master DVD 1

The Installation Master is the starting point for installing Web Application Server ABAP System (including SAP Business Information Warehouse, SAP Mobile Infrastructure Server, SAP Exchange Infrastructure, SAP Knowledge Warehouse and PI Basis). It is also used to install new dialog instances and IGS instances.

SAP NetWeaver ‘04, Support Release 1, Installation Export

Contains required installation files for SAP Web Application Server in folders EXP1-EXP3.

SAP NetWeaver ‘04, Support Release 1 [Unicode] Upgrade Master CD, 2

The Upgrade Master is the starting point for upgrading to Web Application Server ABAP System (including SAP Business Information Warehouse, SAP Mobile Infrastructure Server, SAP Exchange Infrastructure, SAP Knowledge Warehouse and PI Basis).

SAP NetWeaver ‘04, Support Release 1, Upgrade Export

Contains required upgrade files for SAP Web Application Server in folders UPG1-UPG3.

SAP NetWeaver ‘04, Support Release 1, Languages

Contains the language files for SAP Web Application Server in folders LANG1-LANG3.

SAP NetWeaver ‘04, Support Release 1, SAP [Unicode] Kernel 6.40, 2

Contains SAP Kernel files for Web Application Server ABAP System, ECC 5.0 SR1 and SRM 4.0 SR1 (for installation and upgrade).

SAP NetWeaver ‘04, Support Release 1, SAP Web AS Java, SAP NetWeaver Developer Studio, IGS

Contains Internet Graphics Services (IGS) files required for Web Application Server (for installation and upgrade).

,

Media for database software

,

Database documentation (available for Oracle and Informix only)

SAP ERP 2004, SAP NetWeaver ‘04 SR1, SAP ECC 5.0 SR1, SAP SRM 4.0 SR1 Installation Master DVD

The Installation Master is the starting point for installing Web Application Server Java System.


Contains files needed for installation of SAP Web Application Server Java System for different platforms and SAP Internet Graphics Services (IGS).

SAP Web Application Server ABAP System 6.40 including SAP Business Information Warehouse 3.5 (ABAP part) SAP Mobile Infrastructure Server 2.5 SAP NW Exchange Infrastructure (XI) 3.0 (ABAP part) SAP Knowledge Warehouse 7.0 SAP PI Basis 2004.1 SAP Internet Graphics Services 6.40

SAP Web Application Server Java System 6.40 Including SAP Internet Graphics Services 6.40

Media for database software ,

SAP NetWeaver ’04 Developer Studio 2.0


1/2

Note for customers with Database INFORMIX 1 Database MaxDB 7.5 for J2EE Engine is part of the shipment 2 Database DB2/UDB for J2EE Engine available only on request Installation of SAP NetWeaver Developer Studio (folder DEVST)

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 108

6 Media Information

SAP NetWeaver ’04 SR1 Components (continued) Adobe Document Services 1.0 SAP Business Information Warehouse (BW) 3.5 (Java component)

DVD / CD Label



Starting point for installation of NetWeaver Java components (SAP Enterprise Portal, SAP Business Information Warehouse, SAP Exchange Infrastructure, Adobe Document Services and TREX).

SAP NetWeaver ‘04, Support Release 1, NetWeaver Components

Contains installation files for NetWeaver components (SAP Enterprise Portal, SAP Business Information Warehouse, SAP Exchange Infrastructure, Adobe Document Services and TREX).

SAP NetWeaver ‘04, Support Release 1, NetWeaver Components

Contains additional installations of NetWeaver components for SAP Business Information Warehouse, SAP Exchange Infrastructure, SAP Mobile Infrastructure and SAP Knowledge Warehouse.

BI CONT 3.5x, BI Content, Version 3.5x, Installation and Upgrade DVD

Contains ABAP Add-On installation and upgrade of BI Content 3.5.x for SAP Business Information Warehouse 3.5.

SAP NetWeaver ‘04, SAP GUI for Windows 6.40, SAP GUI for Java 6.30, SAP ITS 6.2, Presentation, Server Components, Content Server

Contains installation of SAP GUI for Windows release 6.40 (folder PRES1) and SAP GUI for Java (PRES2) as well as SAP Gateway and SDKs (folder PRES3), SAP Server Components including ITS 6.20 (folder SERV1), SAP Content Server 6.30 (folder CS), SAPDB for Content Server on UNIX (folder CS_SAPDB) and Adobe Designer 6.0 (folder ADOBE_LC_DES).

SAP NetWeaver ‘04, SAP NetWeaver '04 SP Stack x, including BI Content 3.5.x, HTML-Help for Windows, Standard HTML (Plain HTML)

Documentation for NetWeaver ’04 including BI Content 3.5.x in HTML Help for Windows and Standard HTML (Plain HTML)

Mercury LoadRunner 8.0, Windows Installation

Installation of Mercury LoadRunner 8.0 (Windows)

Mercury LoadRunner 8.0, UNIX & Linux Load Generator Installation

Installation of Mercury LoadRunner 8.0 (Unix and Linux)

SAP NW Exchange Infrastructure (XI) 3.0 (Java components) SAP NW Exchange Infrastructure (XI) 3.0 Adapter Engine SAP Enterprise Portal 6.0 SAP Content Management + Collaboration 6.0 SAP Search and Classification (TREX) 6.1 SAP BW Analyzer PreCalc Service 3.5 SAP Mobile Infrastructure (MI) 2.5 SP9 (Mobile Infrastructure Client) SAP KW IKS 1.00 SAP XI 3.0 Partner Connectivity Kit 1.0 SAP XI Content for SAP NetWeaver ‘04 Visual Composer 6.0 SAP BI Content 3.5.x Add-On SAP GUI for Windows 6.40 SAP GUI for Java 6.30 SAP Server Components including SAP Internet Transaction Server 6.20 SAP Content Server 6.30 Adobe Designer 6.0 Documentation for SAP NetWeaver ’04 Support Release 1

Mercury LoadRunner 8.0


6 Media Information

SAP NetWeaver ’04 SR1 Components (continued)

DVD / CD Label


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

WILY Introscope files

SAP License keys for SAP Systems, System Measurement Guide, License Administration Workbench

SAP License Keys & License Audit contains the complete documentation as well as important information about the license auditing tools and the preparations you need to make for license auditing.

WILY Introscope Entpr Mgr 5.3 WILY Introscope Agent 5.3 WILY Introscope Webview 5.3 SAP License Keys & License Audit


6 Media Information

mySAP ERP 2004 SR1 Components

DVD / CD Label



The Installation Master is the starting point for installing SAP ECC 5.0 SR1. It is also used to install new dialog instances and IGS instances.

SAP ERP 2004, SAP ECC 5.0 SR1, Installation Export DVD

Contains required installation files for SAP ECC 5.0 SR1 folders EXP1EXP8.

SAP ERP 2004, SAP ECC 5.0 SR1, SAP [Unicode] Upgrade Master CD. 2

The Upgrade Master is the starting point for upgrading to SAP ECC 5.0 SR1.

SAP ERP 2004, SAP ECC 5.0 SR1, Upgrade Export DVD

Contains required upgrade files for SAP ECC 5.0 SR1on 2 DVDs in folders UPG1-UPG11.

SAP ERP 2004, SAP ECC 5.0 SR1 Language, DE, EN, FR, IT, PT, DA, ES, FI, NL, NO; SV, CS, EL, HR, HU, PL, SK; AR, BG, RO, SU, SH, SL, TR, UK; JA, KO, TH, ZF, ZH

Contains language files for installation and upgrade of SAP ECC 5.0 SR1 in folders LANG1-LANG6.


Contains SAP Kernel files for Web Application Server ABAP System, ECC 5.0 SR1 ABAP System and SRM 4.0 SR1 ABAP System (for installation and upgrade).


Contains IGS files required SAP ECC 5.0 SR1, SRM 4.0 SR1 (for installation and upgrade).

,


,

Database documentation (available for Oracle and Informix)

SAP ERP 2004, SR1 Components DVD / Add-On Support Packages, SEM-BW, FINBASIS, E-Recruiting, WFM, Learning Solution, c-Projects, Mobile Components, XI Content, XSS, IPC, FSCM Biller Direct, ISA-WAC

The ERP Components DVD contains the ABAP Add-On installations and upgrades for SEM-BW 4.0 (folder SEMBW), FINBASIS 3.0 (folder FINBASIS), E-Recruiting 3.0 (folder ERECRUIT), Learning Solution 3.0 (LSOFE), cProject Suite 3.10 (folder CPROJECTS) and WFM Core 1.10 (folder WFMCORE) as well as Support Packages for Add-On Components cProjects, FINBASIS, E-Recruiting, LSOFE, WFMCORE, SEM-BW on folder ADDON-SP.


Starting point for installing mySAP ERP Java components

SAP ERP Core Component (ECC) 5.0 including Plug-In (PI) 2004.1

mySAP ERP 2004 ABAP Add-On Components: SAP Strategic Enterprise Management (SEM-BW) 4.0 SAP Financial Basis (FINBASIS) 3.0 SAP E-Recruiting 3.0 SAP Learning Solution ABAP part (LSOFE) 3.0 SAP cProject Suite 3.10 SAP Workforce Management Core 1.10 mySAP ERP 2004 Java Components: SAP Self Services (XSS) 5.0 SAP FSCM Biller Direct 3.0 SAP Learning Solution Content Player (LSOCP) 3.0 SAP IPC Web Application 4.0 SAP Internet Sales Web Application (ISA WAC) 4.0 SAP Internet Pricing and Configurator (IPC) Server 4.0 SAP Learning Solution Authors Environment (LSOAE) 3.0


SAP Learning Solution Offline Player (LSOOP) 3.0

The ERP Components DVD contains the installation files for Java components Self Services (ESS/MSS), Biller Direct, Learning Solution Content Player, Internet Sales, IPC Web Application in folder JAVACOMP Starting point for installation of SAP IPC Server 4.0 (folder IPCSERV), SAP Learning Solution Authors Environment 3.0 (folder JAVACOMP Æ LSOAE) and SAP Learning Solution Offline Player 3.0 (folder JAVACOMP Æ LSOOP).


6 Media Information

mySAP ERP 2004 SR1 Components (continued)

DVD / CD Label



The Installation Master is the starting point for installing SAP SRM 4.0 SR1. It is also used to install new Dialog instances and IGS instances

SAP SRM 4.0, Support Release 1, Installation Export DVD

Contains required installation files for SAP SRM 4.0 SR1 in folders EXP1EXP3

SAP SRM 4.0, Support Release 1, SAP [Unicode] Upgrade Master CD. 2

The Upgrade Master is the starting point for upgrading to SAP SRM 4.0 SR1

SAP SRM 4.0, Support Release 1, Upgrade Export DVD

Contains required upgrade files for SAP SRM 4.0 SR1in folders UPG1UPG4

SAP SRM 4.0, Support Release 1, Language DVD

Contains language files for installation and upgrade of SAP SRM 4.0 SR1 in folders LANG1-LANG3


Contains SAP Kernel files for Web Application Server ABAP System, ECC 5.0 SR1 ABAP System and SRM 4.0 SR1 ABAP System (for installation and upgrade)


Contains IGS files required SAP SRM 4.0 (for installation and upgrade)

SAP SRM Server 5.0 (leading component of SAP SRM 4.0)

,


,


SAP SRM 4.0, Support Release 1, Components CD, Internet Pricing Configurator, Live Auction Cockpit, XI Content

Contains installation files for Internet Pricing and Configurator Server (IPC) 4.0


The ERP Components DVD contains the mySAP ERP Mobile Components SAP Mobile Time Sheet and SAP Mobile Travel Expenses (folder MTRMTS_1.6), SAP Mobile Sales for mySAP ERP (folder MSR_2.0) and SAP Mobile Direct Store Delivery 2.0 (folder DSD_2.0). The software SAP Mobile Asset Management can be downloaded from SAP Service Marketplace.

SAP Catalog Content Management (SAP CCM) 1.0

SAP Catalog Cont. Mgmt. 1.0, Add-On Installation, based on Web AS 6.40

Contains SRM Add-On Installation of SAP Catalog Content Management 1.0 and XI Content for SAP CCM.

Requisite Catalog Software

Requisite BugsEye 4.0, Requisite eMerge 4.0 (for Oracle and MS SQL or SAPDB)

Only upgrade-relevant and only if Requisite Catalog BugsEye is used

SAP Internet Pricing and Configurator (IPC) Server 4.0 (for SRM) mySAP ERP 2004 Mobile Components: SAP Mobile Time Sheet (MTS) 1.6 SAP Mobile Travel Expenses (MTR) 1.6 SAP Mobile Sales for mySAP ERP (MSR) 2.0 SAP Mobile Asset Management (MAM) 2.5 3 SAP Mobile Direct Store Delivery 2.0


6 Media Information

mySAP ERP 2004 SR1 Components (continued)

DVD / CD Label


SAP XI Content for mySAP ERP 2004


The ERP Components DVD contains the mySAP ERP 2004 XI Content in folder XI_CONT.

Business Packages for mySAP ERP 2004 3

mySAP ERP Business Packages for SAP Enterprise Portal can be downloaded from SAP Software Delivery Center (service.sap.com/swdc Æ Download Æ Installations and Upgrades Æ Entry by Application Group Æ SAP Application Components Æ SAP ERP Æ SAP ERP 2004 Æ SAP Business Packages).

SAP Business Connector 4.6C / 4.7

See Note 571530 in service.sap.com/notes.

Documentation for mySAP ERP 2004 components



SAP Solution Manager 3.2 Documentation

SAP ERP 2004, SAP ECC 5.0 SR1, HTML-Help for Windows, Standard HTML (Plain HTML)

Documentation for SAP ECC 5.0 SR1 in HTML Help for Windows and Standard HTML (Plain HTML)

Documentation SAP SEM 4.0, SEM-BCS / SEM-BW Release 4.0, Standard HTML (Plain HTML), HTML-Help for Windows

Documentation for SAP SEM 4.0 covering SEM-BCS and SEM-BW in HTML Help for Windows and Standard HTML (Plain HTML)

Documentation SAP CPROJECT SUITE 3.10, HTML-Help for Windows, HTML-Help for Windows

Documentation for SAP cProject Suite 3.10 in HTML Help for Windows and Standard HTML (Plain HTML)

Documentation SAP SRM 4.0 SR1, HTML-Help for Windows, Standard HTML (Plain HTML)

Documentation for SAP SRM 4.0 in HTML Help for Windows and Standard HTML (Plain HTML)

DVD / CD Label


SAP Solution Manager 3.2, Installation Master DVD

The Installation Master is the starting point for installing SAP Solution Manager 3.2 including SAP Kernel.

SAP Solution Manager 3.2, Installation Export, Language

Contains required installation files (folders EXP1-EXP5) and language files (folder LANG) for SAP Solution Manager 3.2

,


,


SAP Solution Manager 3.2, mySAP Technology Components, Release 6.20, HTML-Help / Standard HTML

Documentation for SAP Solution Manager 3.2 in HTML Help for Windows and Standard HTML (Plain HTML)

SAP Solution Manager Content 3

Can be downloaded from SAP Service Marketplace


ERP Master Guide

Recommend Documents