Planning Guide SAP Business Suite

Planning Guide SAP Business Suite
Landscape Implementation - Technical Planning Guide

Target Audience Technical Consultants System Administrators Software Architects
PUBLIC Document version: 1.2 2011-05-12
Document History
CAUTION
Before you begin with the implementation, ensure that you have the current version of this document. You can see the current version here: http://service.sap.com/instguides. The following table contains an overview of the most important changes to the document.
Version Date Description
1.2
2011-05-12
Revised version with corrections/enhancements from ramp-up phase
2/72
PUBLIC
2011-05-12
Table of Contents
Chapter 1 Chapter 2 2.1 2.2 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.2 2.4.3 2.5 2.5.1 2.5.2 2.5.3 Chapter 3 3.1 3.1.1 3.1.2 3.2 3.3 3.4 3.4.1 3.4.2 3.5
Goal of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 A Short Explanation of Important Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview of the SAP System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Building Blocks for System Landscapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Evolution of an SAP System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 SAP Business Suite 7 Innovations 2010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 The Role of SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Introduction to the Recommendation Methodology . . . . . . . . . . . . . . . . . . . 22 General Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Reasonable Alternative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Possible Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Information in the SAP Developer Network (SDN) . . . . . . . . . . . . . . . . . . . . . 26 Information in the Master Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 How Do I Plan My System Landscape? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Business Requirements Determine the Landscape Structure . . . . . . . . . . . . . . How to Determine Which New Scenarios and New Functions You Require . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Scenario and Process Component List . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process-Oriented and Scenario-Oriented Planning Framework via Solution Manager Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting Business Functions in Solution Manager . . . . . . . . . . . . . . . . . . . . . . Function-Oriented Planning Framework via Help Portal and Solution Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Functions in the Help Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Functions in the Solution Browser . . . . . . . . . . . . . . . . . . . . . . . Determining Dependencies on Other Systems . . . . . . . . . . . . . . . . . . . . . . . . . 29 29 30 30 31 31 32 32 32 32
2011-05-12
PUBLIC
3/72
3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 Chapter 4 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 Chapter 5 5.1 5.2 5.3
Basic Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Support by Landscape Verification for SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Features When Switching from SAP R/3 4.6C to SAP Business Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Release Notes to Identify Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribution Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version Compatibility Within a System Landscape . . . . . . . . . . . . . . . . . . . . . . Single Stack System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hub, Sidecar, or Embedded Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sidecar System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Embedded Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 'Employee Self-Service' Process with Enhancement Package 5 for SAP ERP 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Design Scenario (Integrated Product Development (IPD)) with Enhancement Package 5 for SAP ERP 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 'Collaborative Demand Management' Scenario with Enhancement Package 5 for SAP ERP 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33 33 34 34 35 35 37 37 37 38 39 41 42 45 45 50 57
Chapter A A.1
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4/72
PUBLIC
2011-05-12
Goal of this Document
1 Goal of this Document
This document provides an overview of SAP Business Suite and its possible system landscapes. You will find out what SAP recommends with regard to building system landscapes, and gain an understanding of the overall implementation procedure for a system landscape. In addition, you will be introduced to tools that enable you to plan and build your own individual system landscape. We will demonstrate the implementation of a system landscape based on concrete examples. Note that in the system landscapes shown here, we are keeping things simple by ignoring the division of a system landscape into development systems, test systems, and productive systems.
Mastering and Reducing Landscape Complexity
An optimized and future-proof system landscape can mean a sustained reduction in total cost of ownership. This applies to newly-created system landscapes as well as to future planning for the development of an existing landscape. In addition it is also possible to reduce the complexity of an existing landscape.
Who is this Document Aimed At?
This document is a technical planning document aimed above all at technical consultants as well as system administrators and software architects who want to plan and build a system landscape.
Your Feedback is Important to Us!
We are very interested in the continuous improvement of our documentation and are happy to receive your comments and suggestions regarding this document. Please send your feedback to our SAP EHP Technology Backoffice at ehp-tech@sap.com. Include the title of this document in the subject line of your e-mail.
2011-05-12
PUBLIC
5/72
This page is left blank for documents that are printed on both sides.
2 2.1
Introduction A Short Explanation of Important Terms
2 Introduction
The implementation options for the various systems and components of SAP Business Suite within a system landscape offer a high level of flexibility, allowing you to realize a range of system landscape layouts. But what does the optimum landscape layout for a specific customer look like? Here, you need to take into account many different factors. These include: the organizational structure of the organization the expected speed of innovation for implemented applications security requirements the product and architecture strategy the individual requirements for performance and scalability the need for required governance processes the required availability and the service level agreements needed the costs of running the landscape However, it is still possible to reduce the large number of technically possible landscape layout combinations to a few alternatives that are best suited to the majority of typical application cases. Based on these alternatives it should be possible to recommend landscape layouts in which the most important aspects of landscape planning are given as balanced a weighting as possible which demonstrate the right balance between flexibility, simplicity, and clear structure which can be implemented by the majority of customers which complement the SAP product strategy and will therefore be of long-term benefit The solution is to define a general methodology that can be applied to all central product modules, such as SAP NetWeaver Portal, SAP NetWeaver Process Integration (PI), or SAP ECC Server, but also to smaller modules such as Adobe Document services (ADS), in cases where smaller modules also play an important role in landscape layout planning. However, before we come to the recommendations, it is important that you familiarize yourselves with the main terminology, gain an overview of what makes up an SAP system landscape, and understand the methodology.
2.1 A Short Explanation of Important Terms

So that you can familiarize yourself with the terminology, the most important terms used in this document are defined below. The comprehensive SAP glossary is found at http://help.sap.com/.
2011-05-12
PUBLIC
7/72
2 2.1
Building Block
This is the smallest logical unit in a system landscape, such as the parts of SAP ERP if they can also be used individually.
Component
A technical unit of software and thereby the smallest unit that can be separately produced, delivered, installed, and maintained.
Dual Stack System
An SAP system in which both the Application Server ABAP (AS ABAP) and the Application Server Java (AS Java9) are installed. This is the case in SAP Solution Manager, for example. A dual stack system has the following characteristics: Common system ID (SID) for all application servers and the database Common startup framework for AS ABAP and AS Java Common database (with different schemas for ABAP and Java) The SAP User Management Engine (UME ) on the AS Java is connected to the AS ABAP in the dual stack system.
Embedded Deployment
This term is used when you run an SAP NetWeaver application within an application system. Example: You install SAP Biller Direct and CRM Content in an SAP NetWeaver Portal that is running in a system together with the SAP ECC server.
End-to-End Scenario
A sequence of different inter-linked sequential and logical processes that map an entire business process that bridges functional areas and completes the whole cycle.
Enhancement Package
From a functional point of view, an SAP enhancement package (EHP) is a collection of new and improved functions (business functions). After installation of an enhancement package for the Business Suite, you only need to activate the new business functions that you really want to use. From a technical point of view, an SAP enhancement package is a collection of certain versions of software components that belong to a defined SAP product version (for example SAP ERP 6.0), are delivered together, and can be installed if required. When implementing an SAP enhancement package you can choose which parts of it you actually want to install. The smallest installable units of an SAP enhancement package are the software components grouped together as a technical usage.
Hub System
We speak about a hub system when an SAP NetWeaver application is set up as an independent system, and several application backend systems use this system together.
8/72
PUBLIC
2011-05-12
2 2.1
Installation
The procedure followed when you install software. This can be the first installation of an SAP product, such as SAP ERP, during which you set up completely new systems. You can use the SAPinst tool for installations.
Instance
The combination of several logical systems with different client roles, which together describe the development landscape of an SAP component. The logical systems can be in one or several SAP systems.
Landscape Verification Wizard
A tool that enables you to check the consistency of and, if necessary, to correct system landscape data contained in the SMSY. This is an add-on for SAP Solution Manager (official name: Landscape Verification for SAP Solution Manager).
Sidecar System
We talk about a sidecar system (as opposed to a hub system) when an SAP NetWeaver system is used by exactly one application system. If you use an SAP NetWeaver application as a sidecar system, this application runs in a separate system (as with a hub system), but it is used solely by the connected application system. Other application systems cannot use the SAP NetWeaver application.
Main Instance
See Product Instance.

Maintenance Optimizer
A part of SAP Solution Manager that allows you to configure activities relating to upgrades, updates, and maintenance. The maintenance optimizer leads the user through the activities to be performed in each system in the system landscape. To do this it requires exact information about the system landscape. The maintenance optimizer retrieves the information from the SMSY. Since some of the information on the system landscape must be entered manually in the SMSY, you can check the consistency of SMSY data using the landscape verification wizard.
Product
A unit that is deliverable by SAP and visible to the customer. A product has the following characteristics: Consists of smaller building blocks and generally addresses business tasks. Examples of products are SAP ERP and SAP NetWeaver.
Product Instance
A product instance (or main instance) is part of a product version and includes several technically dependent software component versions. Product instances are the smallest installable units that can be installed and run under their own system identification (SID). Examples of product instances are SAP ECC Server, SAP NW Enterprise Portal, SAP NW EP Core, SAP XSS (Self Services) and SAP NetWeaver Business Warehouse.
2011-05-12
PUBLIC
9/72
2 2.1
Product System
A grouping of technical systems in Solution Manager on which a version of every product contained therein is installed. A product system can comprise a maximum of one ABAP-based technical system and several non-ABAP-based technical systems. The term "product system" is used in Solution Manager in the SMSY transaction.
Product Version
A particular status of a product, whose components can be installed. Each product version has a defined maintenance period. There are full product versions (for example SAP ERP 6.0) and add-on product versions, which require the installation of existing product versions (for example SAP enhancement package 5 for SAP ERP 6.0).
SAP CRM
Abbreviation for SAP Customer Relationship Management. For a short description, see Evolution of an SAP System Landscape [page 17].
SAP Enhancement Package Installer (SAPehpi)
The tool with which you implement SAP enhancement packages in the system. It can considerably reduce downtime compared to previous installation methods. SAPehpi reads the software components to be implemented from the stack configuration file. For more information and the newest version of this tool, see http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/16746.
SAP ERP
Abbreviation for SAP Enterprise Resource Planning. For a short description, see Evolution of an SAP System Landscape [page 17].
SAP NetWeaver
For a short description, see Evolution of an SAP System Landscape [page 17].
SAP PLM
Abbreviation for SAP Product Lifecycle Management. For a short description, see Evolution of an SAP System Landscape [page 17].
SAP SCM
Abbreviation for SAP Supply Chain Management. For a short description, see Evolution of an SAP System Landscape [page 17].
SAP Solution Manager System Landscape (SMSY)
Contains all information about the SAP systems in a landscape. SMSY is also the name of the transaction code in SAP Solution Manager. SMSY has central importance for the maintenance and further development of every system landscape. Be careful to keep the information in SMSY up to date at all
10/72
PUBLIC
2011-05-12
2 2.1
times. That also applies after an update or upgrade. If the information collected in SMSY is false or incomplete, the maintenance optimizer cannot deliver correct results.
SAP SRM
Abbreviation for SAP Supplier Relationship Management. For a short description, see Evolution of an SAP System Landscape [page 17].
Scenario
A (business) scenario is a group of related business processes that describe a business task comprehensively at macro level. A business scenario usually refers to a business area, a central function, or a profit center in an organization, and can also include other organizations as business partners. It requires one or several SAP components and possibly non-SAP software as well.
Single Stack System
A single stack installation - as opposed to a dual stack installation - means that the Application Server ABAP (AS ABAP) and the application server Java (AS JAVA) run as separate individual systems.
Solution
Consists of one or several products. In a solution you can group together systems and related business processes according to your requirements, in order to monitor your productive businesses processes via the corresponding systems in operative areas, and to improve the lifecycle of your most important business processes.
Stack Configuration File
The Stack Configuration File (stack.xml) is generated by the maintenance optimizer in XML format. Depending on the software components installed in a system, the maintenance optimizer determines the software components that need to be installed in order to achieve a previously defined target configuration.
Support Package (SP)
This is a collection of corrections for a software component version. Support packages are made available several times a year. They are shipped as part of support package stacks (SPS) and can be imported via SAP Solution Manager.
Support Package Stack
A combination of several aligned support packages and patches for a certain release at a specific point in time (usually quarterly).
System Landscape Directory (SLD)
An application that is installed in every SAP NetWeaver Java system. You can use the SLD to collect all information about the Java and ABAP systems in a landscape and thus update Solution Manager
2011-05-12
PUBLIC
11/72
2 2.2
Introduction Overview of the SAP System Landscape
automatically (transaction SMSY). It is therefore recommended to use a central SLD for the entire SAP system landscape.
Target System
The SAP system into which you import new software.

Technical Usage
A logical grouping unit that comprises interdependent product instances. In SAP ERP enhancement packages, business functions are depicted as technical usages. In this way an SAP enhancement package consists of several optionally-installable technical usages. These consist of one or several product instances and can only be installed as a new instance or on to an existing product instance. Examples: Central Applications, Human Capital Management, Financial Services, Retail.
Update
In an update you can import corrections in the form of support packages (SPs), or new functions in the form of enhancement packages. Existing processes must not be affected. Furthermore, no migration or upgrade effort is allowed to occur. An update changes the version of a software component, but not the release. An update can also be either an SP update or an enhancement package update: An SP update means the installation of a support package stack, for example the change from SAP ECC 6.0 SPS 15 to SAP ECC 6.0 SPS 16. SPs only contain corrections. An enhancement package update means the import of a new enhancement package, for example the change from SAP enhancement package 4 for SAP ERP to SAP enhancement package 5 for SAP ERP. When you install SAP enhancement packages, you typically install support packages (SPs) at the same time.
Upgrade
In an upgrade you install new or changed functions in the form of a new software release. Existing processes may change as a result of the installation. Migration effort (for example new hardware and tests) may also arise. An upgrade can be the upgrade to a subsequent release, for example, like switching from SAP R/3 4.6C or SAP ECC 5.0 to SAP ECC 6.0. The tools SAPup and SAPJup are available for performing upgrades.
2.2 Overview of the SAP System Landscape

Features
The following graphic shows the possible components of an SAP Business Suite landscape schematically:
12/72
PUBLIC
2011-05-12
2 2.2
Figure 1:
The following examines the individual components of SAP Business Suite in more detail. SAP ERP (including PLM), SAP CRM, SAP SCM, and SAP SRM form the core of SAP Business Suite. You only ever install and use those parts of SAP Business Suite that you actually require. All core applications of SAP Business Suite are based technically on the Application Server ABAP (AS ABAP) or Application Server Java (AS JAVA), and each have their own database. In addition to SAP SCM, SAP liveCache and SCM Optimizer Geocoding are implemented, which also run on their own database. The following graphic displays the core applications of SAP Business Suite in detail.
2011-05-12
PUBLIC
13/72
2 2.2
Figure 2:
SAP Solution Manager is also an important part of the system landscape. This serves, among other things, as a tool for maintaining system landscapes. The following graphic displays SAP Solution Manager in detail.
Figure 3:
14/72
PUBLIC
2011-05-12
2 2.2
For more information about SAP Solution Manager, see the section The Role of SAP Solution Manager [page 20]. SAP NetWeaver as a technological basis comprises the Java-based components Enterprise Portal (EP) and Adobe Document Server (ADS). For reporting for Business Intelligence (BI), separate systems are set up for Application Server ABAP and Application Server Java (AS Java). Process Integration (PI) also runs in a separate system, whereby this system is based technically on AS ABAP and AS Java. The components TREX and Master Data Management (MDM) serve as search functions in the applications and as a catalog for SAP SRM. The following graphic displays the individual components of SAP NetWeaver in detail.
Figure 4:
For the various components of an SAP Business Suite to produce a consistent system landscape, the conditions described in the following must be fulfilled.
General Requirements for a Consistent System Landscape
A consistent and sustainable system landscape must meet some basic prerequisites. This includes the following New processes must be achievable in the existing system landscape or by a step-by-step enhancement of this system landscape. In many cases, a new version of an SAP application can be integrated with every other version of every other SAP application. This compatibility applies to the technology used and the applications themselves. For more information, see SAP Note 1388258.
2011-05-12
PUBLIC
15/72
2 2.2
After you have upgraded or updated an SAP application, you can continue to use all scenarios that you implemented only in this system without restriction. If you upgrade cross-system scenarios, you should use the Upgrade Dependency Analyzer (UDA) to check the dependencies. For more information, see SAP Service Marketplace at http://service.sap.com/uda and SAP Community Network at http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15730. The content (Enterprise Portal (EP), Business Intelligence (BI), and Process Integration (PI)) of an SAP NetWeaver Hub system based on SAP NetWeaver 7.x can be run in higher SAP NetWeaver releases, either without any adjustment or with only slight adjustment.
Innovation Drivers and Landscape Options
Depending on an existing system landscape with its systems and their release levels, as well as the underlying SAP NetWeaver release, you can choose between various options to attain a consistent system landscape that meets your functional requirements. Thereby, all landscape options provided by SAP aim to minimize the effort you require to structure a consistent system landscape.
EXAMPLE
If you implement an SAP ECC 6.0 system with a connected SAP NetWeaver Portal 7.00, you do not need to update the enhancement package for your SAP NetWeaver Portal 7.00 when installing SAP enhancement package 5 for SAP ERP 6.0. However, you may need to import a particular Support Package Stack (SPS). A consistent system landscape is formed from the cooperation between applications (SAP Business Suite with SAP NetWeaver) and the cooperation between the applications and the underlying technology (for example, SAP NetWeaver AS ABAP or SAP NetWeaver AS Java). In most cases, a reciprocal dependency of applications and technology is given since the applications were developed in a particular version of the technology (such as SAP NetWeaver AS ABAP 7.00), for example. However, with the interaction of SAP Business Suite and SAP NetWeaver, you can ideally choose between two possible approaches for supplementing the systems in a landscape: Application-driven innovations Technology-driven innovations
Application-Driven or Suite-Driven Innovations of the System Landscape
Application-driven innovations are referred to if new applications (for example, a new release of SAP ERP) are to be used without having to adjust the underlying technology (SAP NetWeaver). This approach is suitable for customers who are already using SAP ERP 6.0 with connected SAP NetWeaver applications. Ideally, the development rules and compatibility rules ensure that you can update the systems individually as required. This means that if you only require the most recent SAP enhancement package for SAP ERP or also for SAP CRM, for example, you do not also need to provide the SAP NetWeaver systems with an SAP enhancement package.
16/72
PUBLIC
2011-05-12
2 2.3
Introduction Building Blocks for System Landscapes EXAMPLE
Although SAP enhancement packages are imported in the back end (for example, SAP ECC Server 6.0), ideally customers can retain their portal in their existing SAP NetWeaver AS Java 7.00 environment. The Java applications as well as the portal content are provided for SAP NetWeaver Portal 7.0 as well as for all SAP NetWeaver Portal 7.0 SAP enhancement package versions. Therefore, this option is called application-driven innovation of a landscape since SAP NetWeaver systems connected here are not provided with new functions.
Technology-Driven or SAP NetWeaver-Driven Innovations of a System Landscape
Technology-driven innovations are referred to if a new technology (for example, a new portal release) is to be used without having to adjust the connected application systems. This approach can be suitable for customers who are still using a lower release than SAP NetWeaver 7.0, such as SAP NetWeaver 2004. Since in most cases these customers will need to upgrade anyway to renew the implemented technology, they can take this opportunity to switch to the latest SAP NetWeaver 7.x systems directly. The technology-driven innovation is also recommended for new customers since this ensures that they are able to use the most recent functions directly. Therefore, this option is called technologydriven innovation of a landscape. These two innovation options are two proposals for advancing the development of a landscape. It is also possible to combine both innovation options. Each customer must individually describe and implement his or her optimized landscape. Other factors such as the maintenance period of an application must thereby also be included in planning. The following sections explain the individual components of SAP Business Suite with SAP NetWeaver and with SAP Solution Manager as well as the various specifications of system landscapes.
2.3 Building Blocks for System Landscapes 2.3.1 Evolution of an SAP System Landscape
Features
A system landscape comprises a range of products such as SAP CRM or SAP ERP and their components that can be implemented as building blocks (depending on the scenario) both individually and together. The following describes the individual components of an SAP system landscape in more detail.
SAP Business Suite As a Complete Offering
The complete SAP Business Suite (with SAP NetWeaver as the technological platform) technically comprises individual product instances and these comprise software components. Which product instances of an application must be created from this depends on the respective business process or the scenario that you selected to cover your requirements. The following briefly describes the most
2011-05-12
PUBLIC
17/72
2 2.3
Introduction Building Blocks for System Landscapes
important components of SAP Business Suite. For general information about SAP Business Suite, see http://www.sap.com/solutions/business-suite/index.epx and http://service.sap.com/ businesssuite. For more information about the individual components of SAP Business Suite, see the relevant links. SAP NetWeaver SAP NetWeaver is the basis of SAP Business Suite and also the platform for all partner solutions and customer-specific applications. For more information, see http://www.sdn.sap.com/irj/ sdn/netweaver. Life Cycle Management (LCM) provides the technology required for the entire life cycle of a solution from the implementation through production operations to continuous changes and upgrades. For more information about Life Cycle Management, see http:// www.sdn.sap.com/irj/sdn/lcm. SAP Enterprise Resource Planning (ERP) SAP ERP is the core of SAP Business Suite, which you can use to map and optimize the processes in your enterprise with SAP ERP Financials, SAP ERP Human Capital Management, SAP ERP Operations, SAP ERP Corporate Services, and so on. Technically, SAP ECC server is the product instance of SAP ERP. For more information, see http://service.sap.com/erp. SAP Customer Relationship Management (CRM) SAP CRM is the application that you can use to optimize all customer-related processes in Sales, Marketing, and Service. Technically, SAP CRM Server ABAP is the product instance of SAP CRM. For more information, see http://service.sap.com/crm. SAP Supply Chain Management (SCM) SAP SCM is the application for controlling and coordinating your existing procurement networks, production networks, and distribution networks as well as the planning, organization, and execution of all supply processes along your networked value chains. Technically, SAP SCM Server ABAP is the product instance of SAP SCM. For more information, see http://service.sap.com/ scm. SAP Product Lifecycle Management (PLM) SAP PLM is the application for supporting all product-related processes from the first product idea through production to product service. Technically, large parts of SAP PLM are based on the product instance SAP ECC Server ABAP. For more information, see http://service.sap.com/ plm. SAP Supplier Relationship Management (SRM) SAP SRM is the application for performing your procurement activities for material, goods, and services continuously from requirements determination through order assignment to payment. Technically, SAP SRM Server ABAP is the product instance of SAP SRM. For more information, see http://service.sap.com/srm.
18/72
PUBLIC
2011-05-12
2 2.3
2.3.2 SAP Business Suite 7 Innovations 2010

Features
SAP Business Suite 7 Innovations 2010 is the current version of SAP Business Suite (this version contains SAP enhancement package 5 for SAP ERP 6.0, for example). The following states which applicationdriven and technology-driven innovations are available to you for the core applications of SAP Business Suite, such as SAP ERP.
Application-Driven Innovations
Application-driven innovations are mainly offered to existing customers who are already using productive SAP NetWeaver 7.0 hub systems (Enterprise Portal, Business Intelligence, Process Integration) in their landscape. Even if you do not currently use any hub systems, you can use application-driven innovations by importing an SAP enhancement package. The system landscape for application-driven innovations keeps the SAP NetWeaver hub system stable on Release 7.0 just as this release was provided with SAP Business Suite 7. AS ABAP and AS Java in SAP enhancement package 2 for SAP NetWeaver 7.0 are the basis for the applications of the current version of SAP Business Suite. This component is always updated automatically as an inseparable part of the SAP enhancement package implementation.
EXAMPLE
The SAP ECC parts of SAP enhancement package 5 for SAP ERP 6.0 are always based on SAP enhancement package 2 for SAP NetWeaver 7.0 (AS ABAP). This approach makes additional technological competencies that are required for certain scenarios transparent. SAP enhancement packages for SAP NetWeaver hub systems are not required to be able to use the same range of functions as before.
Technology-Driven Innovations
Customers who want to use the technological innovations in the SAP enhancement packages of SAP NetWeaver can choose to update their hub system to SAP NetWeaver 7.01 or 7.02 and to make an update for SAP PI (from PI 7.1 or 7.11) or an upgrade (from PI 7.0x) to SAP PI 7.3. This is known as technologydriven innovation. The following table gives an overview of which products can be combined with which version in the system landscape:
ABAP Application Systems (ECC, CRM, and So On) Master Data Management (MDM)
Landscape
Portal
Process Integration (PI)
Business Intelligence (BI) TREX
Supported area
7.02
7.00, 7.01, 7.00, 7.01, 7.02, 7.00, 7.01, 7.02 7.02 7.10, 7.11, 7.3
7.00, 7.10 7.1
2011-05-12
PUBLIC
19/72
2 2.3
Introduction Building Blocks for System Landscapes ABAP Application Systems (ECC, CRM, and So On)
Landscape
Portal
Process Integration (PI)
Business Intelligence (BI) TREX
Master Data Management (MDM)
Applicationdriven Technologydriven
7.02 7.02
7.00 7.02
7.00 7.3
7.00 7.02
7.0 7.10
7.1 7.1
In the above table, 7.01 stands for SAP enhancement package 1 for SAP NetWeaver 7.0, and 7.02 stands for SAP enhancement package 2 for SAP NetWeaver 7.0. The row Supported area states all possible combinations. The lower two rows state which variants are application-driven or technology-driven. It is of course also possible to combine applicationdriven and technology-driven innovations. If you use SAP NetWeaver Process Integration (PI), we recommend that you always use the highest version. For more information, see SAP Notes 1515223 and 1388258.
2.3.3 The Role of SAP Solution Manager

Features
SAP Solution Manager supports you during the complete life cycle of your applications, from the Business Blueprint through the configuration to productive operation. SAP Solution Manager provides central access to tools, methods and preconfigured content that you can use while evaluating and implementing your systems, as well as during operations. Therefore, for structuring and upholding a consistent system landscape, SAP Solution Manager with the information it contains about the system landscape is of central importance. We recommend that you always use the most recent release of Solution Manager. For more information, see http://service.sap.com/solutionmanager. SAP Solution Manager plays a central role in the installation process; regardless of which software you install or import. Therefore you must use SAP Solution Manager for the following activities: Installation For example, this can be the first installation of an SAP system, such as an SAP ECC server. Upgrade For example, this can be the upgrade to a follow-on release, such as the switch from SAP ECC 5.0 to SAP ECC 6.0. Support Package update For example, this can be importing a Support Package Stack (SPS), such as switching from SAP ECC 6.0 SPS 15 to SAP ECC 6.0 SPS 16. SAP enhancement package update For example, this can be implementing a new SAP enhancement package, such as switching from SAP enhancement package 4 for SAP ERP 6.0 to SAP enhancement package 5 for SAP ERP 6.0. When
20/72
PUBLIC
2011-05-12
2 2.3
you import SAP enhancement packages, you typically import Support Package Stacks (SPS) at the same time. In SAP Solution Manager you implement the maintenance optimizer, for example, when importing Support Package Stacks or SAP enhancement packages to determine the system-dependent stacks of the software components that are to be imported into the relevant target system to attain the target status that you defined. Therefore, SAP Solution Manager must always be of the most recent release, must be configured correctly, and must always have the up-to-date information on the existing system landscape.
How to Implement SAP Solution Manager to Import an SAP Enhancement Package
As a detailed example of implementing Solution Manager, the following describes some activities with the maintenance optimizer that are necessary when importing an SAP enhancement package: As part of the activities with the maintenance optimizer, you must choose the required technical usages in the maintenance optimizer. The maintenance optimizer determines a list of objects that you need to install in one or more target systems. This list is saved in a package configuration file (stack.xml). The maintenance optimizer stores all objects to be installed in your download basket to facilitate an optimized download of all required objects. To determine the package configuration file, Solution Manager relies on the information about the target systems in SAP Solution Manager System Landscape (SMSY) and from the System Landscape Directory (SLD). You use the SAP enhancement package installer (SAPehpi) to implement the new software. This tool imports the software components into the relevant target system. For example, the target system can be an SAP ECC system or an SAP NetWeaver system (for example, portal system or Business Intelligence system). See the following graphic for an example.
2011-05-12
PUBLIC
21/72
2 2.4
Introduction Introduction to the Recommendation Methodology
Figure 5:
Solution Manager can also support you in selecting business function sets or individual business functions; see the section Select Business Functions in Solution Manager.
2.4 Introduction to the Recommendation Methodology

For our recommendations on building a system landscape, we have divided the various options into three categories (see also the graphic below): General recommendation This option is the best choice for the majority of typical use cases. It is recommended by the SAP product strategy and matches the requirements of a broad customer base. Reasonable alternative This option is a sensible choice for particular use cases or customer scenarios. It is in keeping with the SAP product strategy. Possible exception This option only makes sense for very specific use cases. There may be considerable restrictions on support offered by SAP.
22/72
PUBLIC
2011-05-12
2 2.4
Figure 6:
These three categories allow us to answer the following questions and derive recommendations from them: Does it make sense for these modules to be stored centrally or locally in the system landscape? Do you want to install them in the same technical system as other modules, or rather in a separate system? In particular for portal functions, it is important to check what makes more sense for a specific application with regard to system landscape planning: A central portal, via which you can access diverse application systems (hub), or several local portal systems, where each portal is responsible for a particular application system and all portal systems are interconnected (sidecar). In addition, you need to decide whether you want to install the portal functions (or more precisely, the SAP NetWeaver usage types EP or EP Core) as a separate technical system (with its own system ID) or together with the application system (for example with the same system ID as the SAP ECC system). If you use an SAP NetWeaver Portal, you can find some example recommendations for the Portal in the following section. For more examples of recommendations without the use of an SAP NetWeaver Portal, see http:// www.sdn.sap.com/irj/sdn/landscapedesign.
2.4.1 General Recommendation

Features
The general recommendation is to set up a central application portal as a separate technical system that can be used by multiple SAP Business Suite application systems at the same time. For example, this
2011-05-12
PUBLIC
23/72
2 2.4
portal provides users with central, personalized, and role-based access to the application systems (also see the following graphic).
Figure 7:
2.4.2 Reasonable Alternative

Features
In certain use cases there might be reasons for wanting to set up an additional local portal. For example, this may be the case for customers who want a specific HR portal that provides the infrastructure for Employee Self-Services (ESS) and is directly linked to an HR application system for Human Capital Management (HCM). This is shown in the following graphic. The basic procedure when setting up a reasonable system landscape is therefore to set up a central portal first of all and then decide whether an additional local portal makes sense for certain applications or Web Dynpro Java UIs. Customer experience has shown that landscapes with many different portals that need to access the same data do not lead to a balanced ratio between flexibility and administration costs.
24/72
PUBLIC
2011-05-12
2 2.4
Figure 8:
2.4.3 Possible Exception

Features
For reasons mentioned above, the following example of a Federated Portal Network (see graphic) is no longer recommended as the typical structure of a system landscape, rather it should be considered as a possible exception only.
Figure 9:
2011-05-12
PUBLIC
25/72
2 2.5
Introduction Further Information
2.5 Further Information 2.5.1 Information in the SAP Developer Network (SDN)
Features
If you have defined your required processes in accordance with the recommendations in the section "Introduction to the Recommendation Methodology" and you know which software you need to install for these processes, you specify the layout of your system landscape. This means that you determine how many systems you require and how you want to use each of these systems. You need to consider numerous aspects and adhere to rules for the landscape structure, independently of whether you want to group functions in a system or distribute them across multiple systems. For example, the dependencies between usage types, the interoperability of a hub system, operation and maintenance of the landscape, as well as security aspects play an important role to specify exactly the landscape layout that best meets your individual requirements. To support you with these tasks, in SAP Community Network the pages of SAP Developer Network (SDN) contain information on landscape design. See http://www.sdn.sap.com/irj/sdn/landscapedesign. Here, the Knowledge Center in the Getting Started area contains basic information and the Distribution Models area contains detailed information about the architecture of a system landscape with the respective implementation options.
2.5.2 Information in the Master Guides

Features
The Master Guide for an SAP solution (for example, for SAP ERP 6.0, see http://service.sap.com/ ~form/sapnet?_SHORTKEY=01100035870000671158&) is the starting point for implementing the chosen SAP solution. It outlines the basic idea of the underlying software concept, and provides an overview of the implementation process. It lists the required SAP components as well as the applications of thirdparty providers that are required for the relevant business scenarios. The Master Guide provides you with scenario-specific descriptions for the preparation, execution, and the follow-up activities of an implementation. The Master Guide provides you with important information about the installation sequence and the components to be installed. It contains links to all other documents that you require to implement a scenario. Furthermore, the Master Guide refers to other documents such as the Component Installation Guides and important SAP Notes. Important links to Master Guides: For the current versions of all available Master Guides, see SAP Service Marketplace (SMP) at http://service.sap.com/instguides. For the available releases of the application SAP ERP, choose http://service.sap.com/erp-inst directly. For information about the SAP enhancement packages for SAP ERP 6.0, choose http://service.sap.com/erp-ehp directly.
26/72
PUBLIC
2011-05-12
2 2.5
Introduction Further Information
2.5.3 Important SAP Notes

The following SAP Notes contain important information for planning your system landscape. Ensure that you always use the latest version of an SAP Note. You can find this on SAP Service Marketplace at http://service.sap.com/notes.
List of Important SAP Notes
SAP Note 1388258 1515223 1573180
Title Version Interoperability Within the SAP Business Suite SAP NetWeaver Process Integration: Release Recommendation AEX Enablement for SAP Business Suite
Description
2011-05-12
PUBLIC
27/72
3 3.1
How Do I Plan My System Landscape? Business Requirements Determine the Landscape Structure
3 How Do I Plan My System Landscape?
When planning your own system landscape, you need to consider all the factors that were described in the previous section on SAP system landscapes. In particular, the above-mentioned SAP Community Network (SCN) offers important support for landscape design. In general terms, the following is an ideal path from your business requirements to your customerspecific landscape: 1. Define your strategic direction based on your product roadmap and your business processes and scenarios. 2. Note the general SAP recommendations for landscape planning. 3. Consider the individual requirements in your organization. 4. Determine the appropriate SAP scenario based on the previous steps. 5. Use the SAP tools to derive your concrete landscape from the chosen scenario. As an alternative to this scenario-oriented view, you can also plan in a function-based way, for example so that you can use particular functions after an upgrade of SAP components. However, at the core of your planning must always be your business requirements, which determine how your system landscape is put together. It is also possible to start with a small landscape that you can enhance in the future.
3.1 Business Requirements Determine the Landscape Structure

Large-volume projects in which huge software packages are implemented over a long period of time, going live in a sort of big bang, are no longer what customers are looking for. Customers today are driven by their business scenarios, requiring multiple smaller projects with a short implementation phase. After a short implementation phase, the implemented software must be able to map the scenario. The individual implementations must be independent of each other but they must also enhance one another so that a more complex and therefore more useful scenario can be mapped every time a project is completed successfully. With the SAP Business Suite, SAP provides individual industry-based end-to-end scenarios that can be deployed in implementable steps in the context of a strategic roadmap. An example of an end-to-end scenario is Integrated Product Development, which uses SAP Business Suite to map the areas of Product Development and Product Design, Procurement, Production, and Quality Assurance above and beyond the areas involved. (For an overview, see http://www.sap.com/
2011-05-12
PUBLIC
29/72
3 3.1
How Do I Plan My System Landscape? Business Requirements Determine the Landscape Structure
solutions/executiveview/product-development/index.epx) An example of an implementable step
in this end-to-end scenario is Product Design. The implementation time for an implementable step is usually 1-3 months.
3.1.1 How to Determine Which New Scenarios and New Functions You Require
Features
If you plan to implement new software, you have two options for determining the system landscape required for this: From the end-to-end scenarios you can select a scenario that maps your required business processes. From the parts of SAP Business Suite you can select those components and functions with which you can map an already known scenario or upgrade an existing scenario to include enhancements. For an initial overview of the scenarios available in SAP Business Suite, see SAP Service Marketplace at http://service.sap.com/businesssuite. Choose End-to-End Process Across Lines of Business to find out more about end-to-end scenarios. If you want to increase your knowledge of a scenario such as Integrated Product Development, you can access the corresponding information in Ramp-Up Knowledge Transfer (RKT). To do so, choose http://service.sap.com/rkt. There you navigate to SAP Business Suite SAP Business Suite Value Scenarios . If you want information about individual components of SAP Business Suite and their range of functions, http://service.sap.com/ businesssuite contains this information. For this, choose the section SAP Business Suite Applications.
3.1.2 The Scenario and Process Component List

Features
The scenario and process component list represents the connection between the business view with its scenarios and processes and the technical view of the corresponding SAP products and SAP components. The scenario and process component list can provide the required information in two directions: Which applications and components do I need to implement a selected scenario or individual processes of this scenario? Which different implementation methods do I have available? Which processes are possible if I already implement a combination of applications and components? Which processes are also possible after an upgrade? The scenario and process component list is a tool that is available on SAP Service Marketplace. Choose http://service.sap.com/scl. For more information, see the application documentation.
30/72
PUBLIC
2011-05-12
3 3.2
How Do I Plan My System Landscape? Process-Oriented and Scenario-Oriented Planning Framework via Solution Manager Content
3.2 Process-Oriented and Scenario-Oriented Planning Framework via Solution Manager Content
Features
If you have already selected your scenario, you can use the SAP Solution Manager functions for planning. For this purpose, you can use the Implementation Content that is available in the Business Process Repository (BPR). To call the BPR, in SAP Service Marketplace (http://service.sap.com/ solutionmanager), choose SAP Solution Manager in Detail Implementation Content . On this page you can use the link https://implementationcontent.sap.com/bpr to call the Implementation Content. The BPR is the central storage location for elements that are used to structure solutions in SAP Solution Manager. These elements include structural elements such as organizational units, master data, processes, and process steps, as well as assignments to structural elements such as transactions or Customizing activities. In the BPR you can display the available scenarios for each SAP application or solution (such as SAP ERP), for example, Procurement and Logistics Execution Processes in ERP. Depending on the release version (for example, SAP ECC 6.0), you can display the related processes, for example, Processing Purchase Orders in ERP. The BPR also displays which SAP products and SAP product versions are required for a scenario. In the mentioned sample scenario you require SAP NetWeaver Portal 7.0, SAP SRM Server 5.0, and SAP SCM Server 5.0 in addition to SAP ECC 6.0. If the BPR states that you need an SAP enhancement package, you can determine which business functions are available in this SAP enhancement package on the page SAP Enhancement Packages for SAP ERP (http://service.sap.com/erp-ehp).
3.3 Selecting Business Functions in Solution Manager

Features
If you also require an SAP enhancement package with business functions for your scenario, the SAP Solution Manager system can support you with this. The functions for selecting the business functions of an SAP enhancement package that you require are integrated into the work center Implementation/ Upgrade of SAP Solution Manager. Based on the logical components that you chose, you can have SAP Solution Manager display the available business function sets and individual business functions, and from this you can select the range of business functions that you want. For the SAP Solution Manager proposals for the range of business functions, see Business Function Scope. You can copy the list of business functions to the switch framework cockpit with or without change.
2011-05-12
PUBLIC
31/72
3 3.4
How Do I Plan My System Landscape? Function-Oriented Planning Framework via Help Portal and Solution Browser
3.4 Function-Oriented Planning Framework via Help Portal and Solution Browser
If, instead of choosing a scenario, you require certain functions in SAP applications, perform functionoriented planning, not scenario-oriented planning. This involves determining which functions are available in which release and which components and product versions are required.
3.4.1 Determining Functions in the Help Portal

Features
For an overview and description of all functions in a product (for example, SAP ERP) and the related releases, see SAP Help Portal at http://help.sap.com. Information about the functions of SAP ERP, for example, is located here. There are various versions for the different releases, SAP enhancement packages, and Support Packages. For example, documentation for ERP Central Component enhancement package 4 is thus available in various languages.
3.4.2 Determining Functions in the Solution Browser

Features
An alternative central point of access for SAP ERP existing customers is the solution browser that you can use as an initial overview to determine the functional differences to your starting release. To call the solution browser, choose http://erp.fmpmedia.com. There, you enter your starting release, for example, SAP R/3 4.6C, your target release, for example, SAP enhancement package 5 for SAP ERP, as well as the area, for example, Product Development and Manufacturing, and the component you want, for example, PP. The solution browser issues a list of changed functions according to the selected search criteria. This list states starting from which release a new function is available, which features are new, and which advantage implementing this function has.
3.5 Determining Dependencies on Other Systems

In SAP Business Suite, products such as SAP ERP, SAP CRM, or SAP SCM are parts of a system landscape that consists of several interconnected systems. Business processes, too, run across several systems. If you are planning an upgrade to a single system in your landscape, it is important to know whether this upgrade will affect other systems in the landscape. If that is the case, you must also take into account the respective effects in the systems in question. You can check the effects of an upgrade in one system on the other systems using the "Upgrade Dependency Analyzer" (UDA). You can find it in the Service Marketplace: http://service.sap.com/uda. Here you can enter a component that you want to upgrade, and the Upgrade Dependency Analyzer checks dependencies with the components you are
32/72
PUBLIC
2011-05-12
3 3.5
How Do I Plan My System Landscape? Determining Dependencies on Other Systems
already using. Since the Upgrade Dependency Analyzer can only check pairs of components at one time, it is wise to check all combinations of systems that are connected from a technical or functional point of view.
3.5.1 Basic Installation Procedure

Features
Good planning is essential for a rapid installation without problems. The technical prerequisites and the landscape design must be clarified in advance. The Installation Guides provide the relevant support for installations. It is important to plan the installation so that it runs as efficiently as possible. Each installation of your SAP products should therefore generally comprise the following steps: 1. Planning the installation 2. Preparing the installation 3. Performing the installation 4. Following up on the installation For each phase of the installation, you should specify the strategic procedure as a roadmap in advance, and during the installation you should use a checklist to document each step. For more information about installation with detailed Installation Guides, see http://service.sap.com/instguides.
3.5.2 Basic Upgrade Procedure

Features
The upgrade procedure is similar to that for an installation: Planning, preparing, performing, and following up. Furthermore, consider any effort for migration and modification adjustments as well as the possibility that existing processes may change as a result of the upgrade. For more information about upgrades, see SAP Upgrade Info Center at http://service.sap.com/ upgrade. If you are particularly interested in information about ERP upgrades, choose http:// service.sap.com/erp-upgrade. For up-to-date information on SAP enhancement packages for SAP ERP, see SAP Enhancement Packages for SAP ERP at http://service.sap.com/erp-ehp. There, for many ERP components you can determine which new functions are available in the respective SAP enhancement packages, to which business function the new functions are assigned, and which process or processes are assigned to the respective business function. If you know which scenario or which process you need for a chosen business function, you can use the scenario and process component list to determine the related SAP components. The following table gives an overview of the upgrade paths and upgrade options for SAP Business Suite 7:
2011-05-12
PUBLIC
33/72
3 3.5
How Do I Plan My System Landscape? Determining Dependencies on Other Systems My Target Release in SAP Business Suite 7:
My Starting Release:
What I Need to Do:
SAP ERP 6.0 SAP R/3 4.0B and higher SAP PLM 4.0 and higher SAP CRM 4.0 and higher SAP SRM 3.0 and higher SAP SCM 4.1 and higher
Import SAP enhancement package 4 for SAP ERP 6.0 Upgrade to SAP ERP 6.0 and import SAP enhancement package 4 for SAP ERP 6.0 Upgrade to SAP ERP 6.0 and import SAP enhancement package 4 for SAP ERP 6.0 Upgrade Upgrade Upgrade
SAP ERP 6.0 plus SAP enhancement package 4 for SAP ERP 6.0 SAP ERP 6.0 plus SAP enhancement package 4 for SAP ERP 6.0 SAP PLM 7.0 SAP CRM 7.0 SAP SRM 7.0 SAP SCM 7.0
If you already implement multiple SAP Business Suite products (such as SAP ERP, SAP SRM, and SAP CRM) and want to perform an upgrade, for example, from SAP Business Suite 2004 with SAP NetWeaver 640 to SAP Business Suite 7 Innovations 2010 with SAP enhancement package 2 for SAP NetWeaver 7, you must perform the upgrade separately for each product. For the upgrade, use the SAP tool SAPup (ABAP) or SAPJup (Java).
3.5.3 Basic Update Procedure

Features
An update requires less effort than an upgrade. However, you must specify the scope of the update: You need to decide whether you only want to import corrections as part of an SP update, or if in addition to the SPs, you want to update your SAP enhancement package to additionally implement new business functions. For example, if you use the maintenance transaction in the maintenance optimizer to install an SAP enhancement package for SAP ERP, the system suggests selected technical usages as the default setting for SAP SRM and SAP CRM and you cannot supplement these with further technical usages. With the technical usages from these default settings, the previously installed components of SAP SRM and SAP CRM are each supplemented with SAP enhancement package 1. For further technical usages for SAP SRM and SAP CRM, you must use the respective maintenance transactions of the maintenance optimizer.
3.5.4 Update Support by Landscape Verification for SAP Solution Manager

Features
Starting from an update to SAP enhancement package 4 for SAP ERP 6.0, it is mandatory to use the maintenance optimizer in Solution Manager. Since the information in the maintenance optimizer
34/72
PUBLIC
2011-05-12
3 3.5
How Do I Plan My System Landscape? Determining Dependencies on Other Systems
comes from SMSY, it can only be correct if the data on the existing system landscape is up-to-date and correct in SMSY. You can use the Landscape Verification Wizard for SAP Solution Manager (called Landscape Verification Wizard below) to support you with data maintenance in SMSY and to find inconsistencies in manually entered system landscape data. You can use this tool to import the current data from SMSY, check this data, correct it as required, and then transfer the corrected data back to SMSY. The Landscape Verification Wizard thus serves the correction of the SMSY data for an existing system landscape as well as the preparation for supplementing the system landscape. In detail, the Landscape Verification Wizard checks the following SMSY data for completeness and consistency: product systems, product instances, and technical systems. If the Landscape Verification Wizard identifies incorrect or missing information, you can correct the data manually in the wizard, or supplement it and update the SMSY. The Landscape Verification Wizard and its basic functions are available as an add-on for Solution Manager as of SAP enhancement package 1 for Solution Manager 7.0.
3.5.5 Special Features When Switching from SAP R/3 4.6C to SAP Business Suite
Features
Good planning and preparation is particularly important for switching from SAP R/3 4.6C to the complex landscape of SAP Business Suite. SAP R/3 4.6C comprises one product only with the related SAP basis and the application components based on this, with any additional industry solutions. However, since its first version, SAP Business Suite consists of a complex system landscape that requires appropriate upgrade planning.
3.5.6 Using Release Notes to Identify Changes

Features
When you are planning your upgrade and you want to know which functional changes (deltas) are available in a particular release compared with the previous release, you can consult the release notes for information. The release notes for the SAP products are grouped on SAP Service Marketplace at http://service.sap.com/releasenotes. For example, if you want to get an overview of the new and changed functions in the SAP enhancement packages for SAP ERP 6.0, you can access the relevant section directly: http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000668896&.
2011-05-12
PUBLIC
35/72
4 4.1
Distribution Scenarios Version Compatibility Within a System Landscape
4 Distribution Scenarios
As a customer, you have several ways of running SAP applications and distributing them in your system landscape. This chapter describes the various distribution scenarios (use of an SAP application as a hub system, sidecar system, or embedded employment) and mentions other aspects that are important for the distribution of your system, for example: How are the different product instances distributed across the landscape? Which product instances run in the same SAP system? In addition, at the beginning of the chapter two central concepts are described which are the foundation of any SAP system landscape and which faciliate the administration of your system landscape: version compatibility and single stack systems.
4.1 Version Compatibility Within a System Landscape

SAP aims to structure the various SAP applications so that they are compatible with as many versions as possible. For example, if you, as a customer, operate an SAP R/3 system and an SAP BW system, and you want to upgrade to an SAP ERP 6.0 ECC server, you should not be forced to also automatically upgrade your SAP BW system.
Exceptions in Version Compatibility
All SAP applications are generally compatible with other versions. In practice this is not always possible. To identify possible exceptions in version compatibility, you have the tool Upgrade Dependency Analyzer (UDA) available. You can use this tool to determine dependencies for an upgrade.
4.2 Single Stack System

Depending on the system type, an installation was previously possible as a single stack system and as a dual stack system (for a definition of single stack and dual stack, see A Short Explanation of Important Terms [page 7]). Experience has shown that the use of single stack systems is clearly the preferred variant for managing an SAP system landscape, provided that this is technically possible. The most important advantages of a single stack system are as follows: Flexibility with regard to Support Package Stacks and releases Optimal resource consumption An assumed advantage of a dual stack system is lower effort for database administration. However, the MCOD concept (multiple components in one database) also enables this for single stack systems.
2011-05-12
PUBLIC
37/72
4 4.3
Distribution Scenarios Hub, Sidecar, or Embedded Deployment
Single Stack Systems in SAP Business Suite
The following graphic shows the main applications of SAP Business Suite 7, which all run as a single stack system on an Application Server (AS) ABAP:
Figure 10:
Main Applications of Business Suite As Single Stack System
Graphic Legend: The SAP ERP example explains the meaning of the individual parts of a graphic. This meaning applies to all other graphics in this document: Entire box / dark blue box = product Gray box = product instance / system ID Light blue box = comprised components)
4.3 Hub, Sidecar, or Embedded Deployment

If you want to implement an SAP NetWeaver application (for example SAP NetWeaver Portal) with one or more SAP Business Suite applications, you can classify the SAP NetWeaver application in the following ways: As a hub system, which is used by several application backend systems As a sidecar system, which is used by exactly one application system Within an application backend system (embedded deployment) The following documentation contains an example of each implementation option, describing how you can implement SAP Self-Service (SAP XSS) with SAP NetWeaver Portal as a hub system, a sidecar system, or as embedded deployment.
Implementation Recommendations for SAP Business Suite Components
For more information about implementation recommendations for the most important SAP Business Suite components, see the SAP Developer Network (SDN) page, under http://www.sdn.sap.com/irj/
38/72
PUBLIC
2011-05-12
4 4.3
scn/go/portal/prtroot/docs/library/uuid/b0ba44a6-8d55-2b10-f6b5-8c6cb7b6f0c8? QuickLink=index&overridelayout=true:
SAP Business Suite Components SAP SRM SAP SCM SAP CRM SAP PLM
Slide on SDN Page Above Slide 11 Slide 12 Slide 13 Slide 14
Implementation Recommendations for SAP NetWeaver Components
For further information on implementation recommendations for the most important SAP NetWeaver components, see the following SAP Developer Network (SDN) pages:
SAP NetWeaver Link on SDN Page Components SAP NetWeaver http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50a3d9fb-b6ea-2b10Portal d5ab-b730a95ce923&overridelayout=true, Slides 15-23 SAP NetWeaver http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70b3f2c0-cbea-2b10Business ef9e-90f61c39c1fb&overridelayout=true, Slides 15-23 Warehouse SAP NetWeaver http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/001b590f-bbea-2b10Process Integration 8aa9-def024bc6ec5&overridelayout=true, Slides 26-27 Enterprise Services http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/001b590f-bbea-2b10Repository 8aa9-def024bc6ec5&overridelayout=true, Slides 15-24 Adobe Document http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50a3d9fbServices b6ea-2b10-d5ab-b730a95ce923?QuickLink=index&overridelayout=true, Slides 25-27
4.3.1 Hub System

If you implement an SAP NetWeaver application as a hub system, this application runs on a standalone system and multiple application back-end systems can use this hub system, for example as a central portal system.
Effects on the System Landscape
It is possible to perform an upgrade or update for application systems and hub systems (technology part) independently of one another. An upgrade or update of an application system usually has no effect on the technology part of the hub system, and vice-versa. However, it might be necessary to perform an upgrade/update on the hub system or to import application-specific content. Such content includes BI Content (on SAP BW), Portal Content (for SAP Portal) and XI Content/ESR Content (for SAP PI).
NOTE
The maintenance optimizer calculates all options for updating and enhancing the systems.
2011-05-12
PUBLIC
39/72
4 4.3
Effects on the Entry in Transaction SMSY in SAP Solution Manager
If you use an SAP NetWeaver application as a hub system, this hub system is used in multiple product systems. This means that the technical system thus appears more than once in the landscape of SAP Solution Manager. In more detail, this means the following: In transaction SMSY you need an own product system to which the technical system can be assigned. This is necessary so that you can perform maintenance transactions exclusively for the hub system. For each application back-end system you require a further product system. An application back-end system and the application part on the hub system are assigned to each of these further product systems. If you upgrade such a product system, the local technology stack (ABAP stack or Java stack) of the application back-end system is upgraded to the most recent release but the technology stack on the hub system remains stable. It might be necessary to import a support package into the hub system since a certain minimal support package level is a prerequisite.
Example: SAP XSS with SAP NetWeaver Portal As Hub System
You implement SAP Self-Service (SAP XSS) and SAP Customer Relationship Management. If you use SAP NetWeaver Portal as the hub system that is used as a central portal by both an SAP ERP system and an SAP CRM system, your system landscape might be as follows:
Figure 11:
Effects on the Entry in Transaction SMSY: In transaction SMSY you must create three entries for the portal in the system landscape of Solution Manager (box SAP NetWeaver: SAP NetWeaver Portal): As SAP NetWeaver As SAP ERP As SAP CRM Advantages of a Hub System:
40/72
PUBLIC
2011-05-12
4 4.3
You have a simplified system landscape and a central administration. You have independent upgrade steps or update steps for the connected systems.
4.3.2 Sidecar System

If you use an SAP NetWeaver application as a sidecar system, this application runs in a separate system (in the same way as a hub system), but it is used solely by a single connected application back-end system. Other application back-end systems cannot use the SAP NetWeaver application, meaning that they cannot use the SAP NetWeaver Portal either. You therefore have two identical systems, the only difference being the installed application component (ERP or CRM).
If you implement an SAP NetWeaver application as a sidecar system, you must keep the relevant Support Package Stacks and the enhancement package levels at the same level for the technical systems involved; it is not possible to upgrade the systems independently of each other.
Effects on the Entry in SMSY
If you implement an SAP NetWeaver application as a sidecar system, you need exactly one entry for a product system in the system landscape of SAP Solution Manager (transaction SMSY), consisting of two technical systems. In more detail, this means the following: In transaction SMSY , you create exactly one entry for a product system. Two technical systems are assigned to this product system. The maintenance transactions for the technical systems are coupled via the product system. The system processes them synchronously. Both systems must thus be on the synchronous version defined by SAP.
Example: SAP XSS with SAP NetWeaver Portal As Sidecar
If you implement SAP NetWeaver Portal as a sidecar system in this scenario, your system landscape might be as follows:
2011-05-12
PUBLIC
41/72
4 4.3
Figure 12:
Effects on the Entry in Transaction SMSY: In transaction SMSY, you must create two entries for the upper sidecar system in the system landscape of SAP Solution Manager: As SAP NetWeaver As SAP ERP In transaction SMSY, you must create two entries for the lower sidecar system in the system landscape of SAP Solution Manager: As SAP NetWeaver As SAP CRM Advantages of a Sidecar System: You have exclusive use of SAP NetWeaver Portal for the relevant application back-end system. You do not have to consider any dependencies across product boundaries.
4.3.3 Embedded Deployment

If you implement an SAP NetWeaver application as embedded deployment, this application runs on the application back-end system.
In this variant, all components run in one technical system (in contrast to the sidecar system), meaning that you must keep all involved software components that run in this system in sync with one another. In other words, they must have the same support package stack.
42/72
PUBLIC
2011-05-12
4 4.3
Embedded deployments that use a dual stack are not recommended and cannot be installed as of SAP Business Suite 7. For more information, see SAP Note 855534.
Effects on the Entry in Transaction SMSY
If you implement an SAP NetWeaver application as embedded deployment, you need exactly one entry for a product system in the transaction SMSY, consisting of a technical system. In more detail, this means the following: In transaction SMSY, you create exactly one entry for a product system. The entry comprises the one technical system. Since a maintenance transaction can only be applied to the entire product system, all applications that are merged in this product system are kept in sync with one another. Therefore, if you import enhancement package 5 for SAP ERP, for example, this means that you have to update all contained SAP NetWeaver components so that they have the same version, in this case Version 7.02.
Example: SAP XSS with SAP NetWeaver Portal As Embedded Deployment
If you implement SAP NetWeaver Portal as embedded deployment, your system landscape may be as follows:
Figure 13:
2011-05-12
PUBLIC
43/72
5 5.1
Example Implementations 'Employee Self-Service' Process with Enhancement Package 5 for SAP ERP 6.0
5 Example Implementations
5.1 'Employee Self-Service' Process with Enhancement Package 5 for SAP ERP 6.0
Prerequisites
You are a customer running an SAP R/3 4.6C system and would like to use new functions for Employee Self-Services, which are available in SAP enhancement package 5 for SAP ERP 6.0. In this example, it is assumed that you have already completed the following activities in SAP Solution Manager: In transaction SMSY you have registered your SAP R/3 4.6C system as follows: Product: SAP R/3 Product version: SAP R/3 4.6C Main instance: R/3 server In transaction SMSY, you have assigned RFC destinations for your SAP R/3 4.6C system. In transaction SMSY, you have created a logical component for your SAP R/3 product and assigned your SAP R/3 system to this logical component. In transaction SOLMAN_WORKCENTER, you have created a solution and assigned your already-created logical component to it.
Procedure
Perform the following steps: 1. Starting point: Your current system landscape You are running an SAP R/3 4.6C system and using Human Resources Management (software component SAP_HR 4.6C). The following graphic shows the system landscape with SAP R/3 4.6C:
Figure 14:
2.
Learn about new functions on SAP Service Marketplace You can learn about new functions in the area of Human Resources Management on SAP Service Marketplace at http://service.sap.com/businesssuite. You can find the necessary
2011-05-12
PUBLIC
45/72
5 5.1
3.
information when you choose End-to-End Processes and look in the Human Resources Drive Efficient HR Operations section. You decide to use new Self-Services functions that are depicted in the Employee Self-Service process. But you are not interested in new SAP E-Recruiting functions. Determine the required application components and product versions via SCL On SAP Service Marketplace at http://service.sap.com/scl, call the scenario component list (SCL). Call the Employee Self-Service process.
NOTE
To find the process directly, on the Scenario & Process Component List screen, choose Start Application and on the next screen choose SAP Scenarios and Realization Alternatives. Enter "Employee Self Service" as the search term. The Employee Self-Service process belongs to the SAP ERP Key Capability End-User Service Delivery solution. In the SCL, the system shows a variety of options you can use to install the Employee Self-Service process. For each option, all application components and product versions that you can install and upgrade to are listed. For more information on the Employee Self-Service process, see the SAP ERP Master Guide. Since you have only been running SAP R/3 4.6C up to now, and are therefore only using one system, there cannot be any dependencies on other productive SAP systems in the case of an upgrade. You therefore choose the option with SAP enhancement package 5 and the latest versions of the Application Server (AS) ABAP and AS Java available in this scenario, in other words AS ABAP 7.02 and AS Java 7.02. This option contains the following application components and product versions: EHP5 FOR SAP ERP 6.0 - SAP E-Recruiting EHP5 FOR SAP ERP 6.0 - Central Applications EHP5 FOR SAP ERP 6.0 - SAP XSS (Self-Services) SAP ERP 6.0 - SAP NW - EP Core BP ERP05 SELF-SERV ADMIN 1.0 BP ERP05 COMMON PARTS 1.51 BP TECHNICAL INFORMATION 1.51 BP ERP05 ESS 1.41 SAP ERP 6.0 - SAP NW - Search and Classification SAP ERP 6.0 - SAP SRM - CCM SRM-MDM Catalog SAP ERP 6.0 - SAP NW - Adobe Docu. Service
NOTE
This is the list containing all possible application components and project versions for implementing the process. Depending on the process you require, you do not have to install all of these application components and product versions. To familiarize yourself with the individual application components, choose the relevant link in the SCL. These links provide you with, among other things, information about
46/72
PUBLIC
2011-05-12
5 5.1
4.
which product version the application component is based on and which components it contains. Plan your system landscape In step 3, you generated all the application components and product versions you may need for the Employee Self-Service process. You must now determine how you want to distribute the application components and product versions across your systems, that is, exactly how you want your system landscape to look. In the following table, you can see the system on which a particular application component runs. The Description column contains more details.
NOTE
With all optional application components and product versions, customers must determine for themselves whether they actually need the application component or product version for their scenario or process. When it says in the following that an application component or product version is "not to be implemented", it refers to a decision that is only relevant in this example.
Application System Component or Product Version EHP5 FOR SAP ERP 6.0 Not to be E-Recruiting implemented EHP5 FOR SAP ERP 6.0 SAP ECC Server - Central Applications Description
EHP5 FOR SAP ERP 6.0 SAP XSS - SAP XSS (SelfServices)
SAP ERP 6.0 - SAP NW SAP XSS - EP Core BP ERP05 SELF-SERV SAP XSS ADMIN 1.0 BP ERP05 COMMON SAP XSS PARTS 1.51 BP TECHNICAL SAP XSS INFORMATION 1.51
In this example you decide not to use this application component for your customer-specific Employee Self-Service process. This application component runs on the SAP ECC server, in other words you perform an upgrade from your SAP R/3 4.6C system to SAP ECC 6.0 including the ECC parts of enhancement package 5 for SAP ERP 6.0. We recommend that you install this application component in its own system based on SAP NetWeaver EP Core. SAP no longer supports new dual stack installations with EP Core. In this example, SAP XSS is deployed as a sidecar, in other words the EP Core system is run as a sidecar system. You must install this application component in the SAP XSS system, as SAP XSS requires SAP NetWeaver EP Core to be in the same system. This business package belongs to SAP XSS. In this example you therefore install it in the SAP XSS system that is based on SAP NetWeaver EP Core. You install this business package in the SAP XSS system that is based on SAP NetWeaver EP Core. You install this business package in the SAP XSS system that is based on SAP NetWeaver EP Core.
2011-05-12
PUBLIC
47/72
5 5.1
BP ERP05 ESS 1.41
SAP XSS
SAP ERP 6.0 - SAP NW - Search and Classification SAP ERP 6.0 - SAP SRM - CCM SRMMDM Catalog SAP ERP 6.0 - SAP NW - Adobe Docu. Service
Not to be implemented Not to be implemented SAP XSS
This business package belongs to SAP XSS. In this example you therefore install it in the SAP XSS system that is based on SAP NetWeaver EP Core. In this example you decide not to use any enhanced search functions. In this example you decide not to use this application component for your customer-specific Employee Self-Service process. We recommend that you install this application component in the SAP XSS system based on SAP NetWeaver EP core. For more information, see http://www.sdn.sap.com/irj/scn/
index?rid=/library/uuid/50a3d9fb-b6ea-2b10-d5abb730a95ce923&overridelayout=true, slides 25-27.
The following graphic shows the system landscape that is derived for this example from the above information:
Figure 15:
5.
6.
The following activities are therefore required: Upgrade: You upgrade your SAP R/3 4.6C system to SAP ECC 6.0 including the ECC parts of enhancement package 5 for SAP ERP 6.0 and including the technical usage HCM SelfService. Installation You install the SAP XSS 6.05 system. This is set up as a sidecar system. Check dependencies using the Upgrade Dependency Analyzer (UDA) Since you have only been running SAP R/3 4.6C up to now, and are therefore only using one system, there cannot be any dependencies on other productive SAP systems in the case of an upgrade. Consequently, it is necessary here to use the Upgrade Dependency Analyzer to check dependencies. Register the new systems Register the new system determined in step 4 in SAP Solution Manager using transaction SMSY as follows:
48/72
PUBLIC
2011-05-12
5 5.1
System SAP XSS System
SMSY entry Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: SAP XSS (Self-Services)
7.
Install the new systems Install the new SAP XSS 6.05 system determined in step 4, as follows: Use the SAPinst tool to install the following software units: XSS EP Core AS Java You can also use SAPinst to install most business packages. If you cannot do this, install the business package with the JSPM tool. 8. Create a maintenance transaction for the upgrade In SAP Solution Manager, in transaction SOLMAN_WORKCENTER > Change Management, create a maintenance transaction for the upgrade of your SAP R/3 4.6C system to SAP ECC 6.0 with the ECC parts of enhancement package 5 for SAP ERP 6.0. The maintenance optimizer uses this maintenance transaction to calculate the files needed for the upgrade/update and to put them them in the download basket. 9. Required upgrade activities The following steps are necessary for the upgrade of your SAP R/3 4.6C system to SAP ECC 6.0 with the ECC parts of enhancement package 5 for SAP ERP 6.0 including the technical usage HCM SelfService: 1. Perform the upgrade using the SAPup tool. 2. On your SAP ECC Server 6.05, use the switch framework (transaction code SFW5) to activate the business functions in enhancement package 5 for SAP ERP 6.0 that you want to use. 10. Update the system configuration Use transaction SMSY to update your system data in SAP Solution Manager. Proceed as follows: 1. Delete the entry for your SAP R/3 4.6C system. 2. Create the following new entry:
System SMSY entry SAP ECC Product: SAP ERP ENHANCE PACKAGE Server 6.05 Product version: EHP5 FOR SAP ERP 6.0 Main instance: Central applications: for this entry, set the Relevant indicator. Human Capital Management; for this entry, set the Also installed in Relevant ABAP Main Instance indicator.
2011-05-12
PUBLIC
49/72
5 5.2
Example Implementations Product Design Scenario (Integrated Product Development (IPD)) with Enhancement Package 5 for SAP ERP 6.0
5.2 Product Design Scenario (Integrated Product Development (IPD)) with Enhancement Package 5 for SAP ERP 6.0
Prerequisites
You are a customer using SAP ECC Server 6.0 (part of SAP ERP 6.0) and SAP NetWeaver 2004 Business Warehouse (SAP BW 3.5). You now want to use the new Integrated Product Development (IPD) scenario. In this example, it is assumed that you have already completed the following activities in SAP Solution Manager: For SAP ECC 6.0: You have registered your SAP ECC 6.0 system in transaction SMSY as follows: Product: SAP ERP Product version: SAP ERP 6.0 Main instance: SAP ECC server You have assigned RFC destinations for your SAP ECC 6.0 system in transaction SMSY. In transaction SMSY, you have created a logical component for your SAP ERP product and assigned your SAP ECC system to this logical component. In transaction SOLMAN_WORKCENTER, you have created a solution and assigned your already-created logical components to this solution. For SAP NetWeaver 2004 BW 3.5: You must register your SAP NetWeaver BW 3.5 system twice in transaction SMSY; once as an SAP NetWeaver system and once as an SAP ERP system: SAP NetWeaver: Product: SAP NETWEAVER Product version: SAP NETWEAVER 04 Main instance: BUSINESS INTELLIGENCE SAP ERP Product: SAP ERP Product version: SAP ERP 2004 Main instance: SAP NW - Business Intelligence You have assigned RFC destinations for your SAP BW 3.5 system in transaction SMSY. In transaction SMSY, you have created an additional logical component for your SAP NetWeaver product and assigned your SAP NetWeaver BW 3.5 system to this logical component. You have assigned the logical component to the solution that you created above for SAP ECC 6.0. This dual registration in transaction SMSY in Solution Manager is necessary to first make the ABAP instance known to the system and then make the Java instance known. The logical component mentioned above serves to combine the two instances once again.
Procedure
Perform the following steps:
50/72
PUBLIC
2011-05-12
5 5.2
1.
Starting point: Your current system landscape You use SAP ECC 6.0 and SAP NetWeaver 2004 Business Warehouse (SAP BW 3.5). You can see the current system landscape in the following graphic:
Figure 16:
2.
3.
Learn about new functions on SAP Service Marketplace You can learn about new functions in the area of Product Lifecycle Management on SAP Service Marketplace at http://service.sap.com/businesssuite. Go to End-to-End Processes and then Product Development Manufacturing to find this information. You decide to use Integrated Product Development. Determine the required application components and product versions via SCL On SAP Service Marketplace at http://service.sap.com/scl, call the scenario component list (SCL). From the SCL, call the Product Design scenario.
NOTE
To find the scenario directly, on the Scenario & Process Component List screen, choose Start Application and on the next screen choose SAP Scenarios and Realization Alternatives. Enter "Product Design" as the search term. The Product Design scenario is part of the Cross-Application Implementation Packages Key Capability Integrated Product Development for Discrete Industries solution. In the SCL, the system shows a variety of options you can use to install the Product Design scenario. For each option, all application components and product versions that you can install and upgrade to are listed. Since there are no dependencies for systems based on SAP NetWeaver 7.0, use the option with SAP enhancement package 5 and the highest version of the application server (AS) for ABAP and Java available in this scenario (AS ABAP 7.02 and AS Java 7.02). This option contains the following application components and product versions: EHP5 FOR SAP ERP 6.0 - Central Applications SAP NETWEAVER 7.0 - Business Intelligence SAP RPM 4.5 - BI Content EHP5 FOR SAP ERP 6.0 - PLM Core SAP PLM I. TO INVENTOR ED 1.0 - PLM I. To Inventor E-Desktop EHP5 FOR SAP ERP 6.0 - SAP Product Vizualization
2011-05-12
PUBLIC
51/72
5 5.2
SAP ERP 6.0 - SAP NW - Adobe Docu. Service SAP ERP 6.0 - SAP NW - Search and Classif. SAP ERP 6.0 - SAP NW - EP Core BP ERP05 COMMON PARTS 1.51 BP ERP05 SELF-SERV ADMIN 1.0 BP_PROJ_PORT_DESIGNCOLL 5.0 70BP TECHNICAL INFORMATION 1.51 BP_PLMWD 1.51 SAP RPM 4.5 - RPM Core
NOTE
4.
This is the list with the largest number of possible application components and project versions for implementing the scenario. Depending on the process you required, you do not have to install all of these application components and product versions. To familiarize yourself with the individual application components, choose the relevant link in the SCL. These links provide you with, among other things, information about which product version the application component is based on and which components it contains. Plan your system landscape In step 3, you generated all the application components and product versions you may need for the Product Design scenario. You must now determine how you want to distribute the application components and product versions across your systems, that is, how you want your system landscape to look. In the following table, you can see the system on which a particular application component runs. In the "Description" column, you see an explanation of why the application components and product versions must run on that system.
Application Component/ Product Version EHP5 FOR SAP ERP 6.0 - Central Applications System SAP ECC server Description
SAP NETWEAVER 7.0 - Business Intelligence
This application component runs on the SAP ECC server, so you implement enhancement package 5 for SAP ERP 6.0 (SAP ECC server 6.05) (update from SAP ECC 600 to SAP ECC 6.05). SAP NetWeaver The primary recommendation is to run these Business application components on two separate Warehouse ABAP systems, one with AS ABAP and one with AS Java. (referred to For more information, see http://www.sdn. hereafter as SAP sap.com/irj/scn/index?rid=/library/uuid/ NetWeaver BW 70b3f2c0-cbea-2b10-ef9e-90f61c39c1fb ABAP) &overridelayout=true, slides 14-23. SAP NetWeaver The following applies for this example: Since you Business already use SAP BW 3.5 (running on AS ABAP), Warehouse Java you must upgrade to SAP BW 7.0 with the BW (referred to portions of enhancement package 2 for SAP
52/72
PUBLIC
2011-05-12
5 5.2
hereafter as SAP NetWeaver BW Java)
SAP ERP 6.0 - SAP NW - EP Core
SAP NetWeaver BW Java
BP ERP05 COMMON PARTS 1.51
SAP NetWeaver BW Java SAP NetWeaver BW Java SAP NetWeaver BW Java SAP NetWeaver BW Java SAP NetWeaver BW Java
BP ERP05 SELF-SERV ADMIN 1.0
BP_PROJ_PORT_DESIGNCOLL 5.0 70 BP TECHNICAL INFORMATION 1.51 BP_PLMWD 1.51
SAP ERP 6.0 - SAP NW - Search and SAP TREX Classif. SAP RPM 4.5 - BI Content SAP NetWeaver BW ABAP
EHP5 FOR SAP ERP 6.0 - PLM Core SAP ECC server
SAP RPM 4.5 - RPM core (SAP RPM SAP ECC server stands for SAP Resource and Portfolio Management (SAP RPM)) SAP PLM I. TO INVENTOR ED 1.0 - Is not PLM I. To Inventor E-Desktop implemented
NetWeaver 7.0, that is, you must upgrade to SAP BW 7.02. You must reinstall the SAP NetWeaver BW system on AS Java (this SAP NetWeaver BW system will then contain SAP NetWeaver EP Core and SAP NetWeaver EP). For this system landscape, you need an SAP NetWeaver BW Java system (for reasons why, see the row above entitled "SAP NETWEAVER 7.0 Business Intelligence"). As a result, you use SAP NetWeaver EP Core on the SAP NetWeaver BW Java system because an SAP NetWeaver BW Java system contains SAP NetWeaver EP core and SAP NetWeaver EP. You install this business package on the SAP NetWeaver BW Java system, which requires SAP NetWeaver EP core and SAP NetWeaver EP. You install this business package on the SAP NetWeaver BW Java system, which requires SAP NetWeaver EP core and SAP NetWeaver EP. You install this business package on the SAP NetWeaver BW Java system, which requires SAP NetWeaver EP core and SAP NetWeaver EP. You install this business package on the SAP NetWeaver BW Java system, which requires SAP NetWeaver EP core and SAP NetWeaver EP. You install this business package on the SAP NetWeaver BW Java system, which requires SAP NetWeaver EP core and SAP NetWeaver EP. You generally install this application component as a separate system. BI Content is delivered as an add-on for SAP NetWeaver Business Warehouse. You must therefore install this application component on the SAP NetWeaver BW ABAP system. Product Lifecycle Management (PLM) core includes the following components: SAP_APPL 6.05 EA-APPL 6.05 EA-IPPE 4.05 PLM WUI (PLM web user interface) These components are contained on the SAP ECC server 6.05. You install this application component on the SAP ECC server. You decide not to use this application component.
2011-05-12
PUBLIC
53/72
5 5.2
EHP5 FOR SAP ERP 6.0 - SAP Product Vizualization SAP ERP 6.0 - SAP NW - Adobe Docu. Service
Is not implemented SAP BW Java System
You decide not to use this application component. We recommend that you install this application component on the SAP system based on SAP NetWeaver EP core. For more information, see
http://www.sdn.sap.com/irj/scn/index? rid=/library/uuid/50a3d9fb-b6ea-2b10d5ab-b730a95ce923&overridelayout=true,
slides 25-27.
Figure 17: NOTE
The red box under TREX represents a standalone engine. The following activities are therefore required: Update: You integrate the ECC server parts of enhancement package 5 for SAP ERP 6.0 and RPM Core into your SAP ECC server. Upgrade You upgrade your SAP NetWeaver 2004 Business Warehouse (SAP BW 3.5) system to SAP NetWeaver 7.0 Business Intelligence, including the SAP BW parts of enhancement package 2 for SAP NetWeaver 7.0 (SAP BW 7.02). New installation: You install a system with SAP NetWeaver 7.0 Business Intelligence Java including the SAP BW Java parts of enhancement package 2 for SAP NetWeaver 7.0 (SAP BW Java 7.02).
54/72
PUBLIC
2011-05-12
5 5.2
5.
6.
You install a TREX system as a standalone system. Check dependencies using the Upgrade Dependency Analyzer (UDA) On SAP Service Marketplace, under http://service.sap.com/uda, call the Upgrade Dependency Analyzer tool and perform the following checks: Check for dependencies between the update to enhancement package 5 for SAP ERP 6.0 (SAP ECC server 6.05) and the SAP NetWeaver 2004 Business Intelligence (SAP BW 3.5) system Check for dependencies between the SAP ECC 6.0 system (part of SAP ERP 6.0) and the upgrade to SAP NetWeaver Business Intelligence including the SAP BW parts of enhancement package 2 for SAP NetWeaver 7.0 (SAP BW 7.02) The check shows that there are no dependencies. Register the new systems Register the new systems determined in step 4 in SAP Solution Manager using transaction SMSY as follows:
System SAP BW Java 7.02 SMSY entry For this system, you must create two entries in transaction SMSY: As SAP ERP: Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: BI Java As SAP NetWeaver: Product: SAP NetWeaver Product version: SAP EHP2 FOR SAP NetWeaver 7.0 Main instance: BI Java For this system, you must create two entries in transaction SMSY: As SAP ERP: Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: SAP NW - Search and Classification Engine As SAP NetWeaver: Product: SAP NetWeaver Product version: SAP EHP2 FOR SAP NetWeaver 7.0 Main instance: Search and Classif. (TREX)
SAP TREX
7.
Install the new systems Install the new systems determined in step 4 as follows: SAP BW Java 7.02: Using the tool SAPinst, you install an SAP system with the following software units: BW Java EP Core EP AS Java Adobe Document Services
2011-05-12
PUBLIC
55/72
5 5.2
You can also use SAPinst to install most business packages. If you cannot do this, install the business package with the JSPM tool. TREX: You install the TREX system with the SAPinst tool. 8. Create a maintenance transaction for the upgrade In SAP Solution Manager, go to transaction SOLMAN_WORKCENTER and create one maintenance transaction for the following two activities: Implementation of the SAP ECC Server parts of enhancement package 5 for SAP ERP 6.0 in the SAP ECC Server 6.0 system. Upgrade of your SAP NetWeaver 2004 Business Intelligence (SAP BW 3.5) system to SAP NetWeaver 7.0 Business Intelligence including the SAP BW parts of enhancement package 2 for SAP NetWeaver (SAP BW 7.02) and the SAP BW parts of enhancement package 5 for SAP ERP 6.0. The maintenance optimizer uses this maintenance transaction to calculate the files needed for the upgrade or update and to put them in the download basket. 9. Required upgrade/update activities Implementation of the SAP ECC Server parts of enhancement package 5 for SAP ERP 6.0 in the SAP ECC Server 6.0 system. Proceed as follows: 1. Use the SAPehpi tool to install the SAP ECC server parts of enhancement package 5 for SAP ERP 6.0. 2. Activate the required business functions in your SAP ECC Server 6.05 system using the Switch Framework (transaction SFW5). Upgrade to SAP BW ABAP 7.02 Upgrade your SAP BW 3.5 system to SAP BW ABAP 7.02 with the SAPup tool. 10. Update the system configuration Use transaction SMSY to update your system data in SAP Solution Manager. Proceed as follows: 1. Delete the entry for your SAP ECC Server 6.0 system and the entry for your SAP BW 3.5 system. 2. Create the following new entries:
System SAP ECC Server 6.05 SMSY entry Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: Central applications For this system, you must create two entries in transaction SMSY: As SAP ERP: Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: ABAP Technology for ERP As SAP NetWeaver: Product: SAP NetWeaver
SAP BW 7.02
56/72
PUBLIC
2011-05-12
5 5.3
Example Implementations 'Collaborative Demand Management' Scenario with Enhancement Package 5 for SAP ERP 6.0
Product version: SAP EHP2 FOR SAP NetWeaver 7.0 Main instance: Business Intelligence
5.3 'Collaborative Demand Management' Scenario with Enhancement Package 5 for SAP ERP 6.0
Prerequisites
You are a customer running SAP ECC Server 6.0, NetWeaver 7.0 Business Warehouse (SAP BW 7.0), and SAP NetWeaver 7.0 Process Integration (SAP PI 7.0). You now want to use the current scenario Collaborative Demand Management. In this example, it is assumed that you have already completed the following activities in SAP Solution Manager: SAP ECC server 6.0: In transaction SMSY, you have registered your SAP ECC 6.0 Server system as follows: Product: SAP ERP Product version: SAP ERP 6.0 Main instance: SAP ECC Server In transaction SMSY, you have assigned RFC destinations for your SAP ECC Server 6.0 system. In transaction SMSY, you have created a logical component for your SAP ERP product and assigned your SAP ECC Server system to this logical component. In transaction SOLMAN_WORKCENTER, you have created a solution and assigned your already-created logical component to it. SAP BW 7.0: In transaction SMSY, you have created the following two entries for your SAP BW 7.0 system: As SAP ERP: Product: SAP ERP Product version: SAP ERP 6.0 Main instance: SAP NW - Business Intelligence As SAP NetWeaver: Product: SAP NetWeaver Product version: SAP NetWeaver 7.0 Main instance: Business Intelligence In transaction SMSY, you have assigned RFC destinations for your SAP BW 7.0 system. In transaction SMSY, you have created an additional logical component for your SAP ERP product and assigned your SAP NetWeaver BW 7.0 system to this logical component. You have assigned the logical component to the solution that you created above for SAP ECC Server 6.0. For SAP PI 7.0:
2011-05-12
PUBLIC
57/72
5 5.3
In transaction SMSY, you have created the following entries for your SAP PI 7.0 system: As SAP ERP: Product: SAP ERP Product version: SAP ERP 6.0 Main instance: SAP NW - Process Integration As SAP NetWeaver: Product: SAP NetWeaver Product version: SAP NetWeaver 7.0 Main instance: Process Integration (PI/XI) In transaction SMSY, you have assigned RFC destinations for your SAP PI 7.0 system. In transaction SMSY, you have created an additional logical component for your SAP ERP product and assigned your SAP PI 7.0 system to this additional logical component. You have assigned the logical component to the solution that you created above for SAP ECC 6.0.
Procedure
Perform the following steps: 1. Starting point: Your current system landscape You are running an SAP ECC server 6.0, SAP BW 7.0 and SAP PI 7.0. You can see the current system landscape in the following graphic:
Figure 18:
2.
3.
Learn about new functions on SAP Service Marketplace On SAP Service Marketplace, under http://service.sap.com/businesssuite End-to-End Processes Supply Chain Collaborative Demand and Supply Planning , you research the new functions and decide to implement the Collaborative Demand Management scenario. Determine the required application components and product versions via SCL
58/72
PUBLIC
2011-05-12
5 5.3
On SAP Service Marketplace at http://service.sap.com/scl, call the scenario component list (SCL). From there, call the Collaborative Demand Management scenario.
NOTE
To find the scenario directly, on the Scenario & Process Component List screen, choose Start Application and on the next screen choose SAP Scenarios and Realization Alternatives. Enter "Collaborative Demand Management" as the search term. The Collaborative Demand Management scenario belongs to the Cross-Application Implementation Packages Key Capability Collaborative Demand and Supply Planning solution. In the SCL, the system shows a variety of options you can use to install the Collaborative Demand Management scenario. For each option, all application components and product versions that you can install and upgrade to are listed. You do not want to use SAP Duet Java or SAP Supply Chain Performance Management. You therefore choose the alternative with the following application components/product versions: EHP5 FOR SAP ERP 6.0 - Central Applications EHP1 FOR SAP CRM 7.0 - CRM Application Server ABAP EHP1 FOR SAP SCM 7.0 - SCM Server SAP SCM 7.0 - SAP liveCache EHP1 FOR SAP SCM 7.0 - SCM Optimizer SAP EHP2 FOR SAP NETWEAVER 7.0 - Business Intelligence SAP NETWEAVER 7.0 - Process Integration (PI/XI) EHP1 FOR SAP SCM 7.0 - XI Content
NOTE
4.
This is the list with the largest number of possible application components and project versions for implementing the process. Depending on the process you require, you do not have to install all of these application components and product versions. To familiarize yourself with the individual application components, choose the relevant link in the SCL. These links provide you with, among other things, information about which product version the application component is based on and which components it contains. Plan your system landscape In step 3, you identified all the application components and product versions you may need for the Collaborative Demand Management scenario. You must now determine how you want to distribute the application components and product versions across your systems, that is, how exactly you want your system landscape to look. In the following table, you can see the system on which a particular application component runs. In the "Description" column, you see an explanation of why the application components and product versions must run on that system.
2011-05-12
PUBLIC
59/72
5 5.3
Application System Description Component/ Product Version EHP5 FOR SAP SAP ECC server This application component/product version runs on the SAP ECC ERP 6.0 - Central server, in other words you implement the SAP ECC Server parts of Applications enhancement package 5 for SAP ERP 6.0 (update from SAP ECC Server 6.0 to SAP ECC Server 6.05). EHP1 FOR SAP Not to be You decide not to use SAP CRM Server 7.0 for the Collaborative Demand CRM 7.0 - CRM implemented Management scenario with enhancement package 5 for SAP ERP 6.0. Application Server ABAP EHP1 FOR SAP SAP SCM server The SAP SCM server is an independent system. As a rule, you can SCM 7.0 - SCM install the three SAP SCM application components that belong to Server this scenario (SAP liveCache, SCM Server, SCM Optimizer) in one of the following ways: Each in its own system, in other words each with its own system ID All three on the SAP SCM server, in other words with a common system ID You choose the second variant. EHP1 FOR SAP SAP SCM Server See description of "EHP1 FOR SAP SCM 7.0 - SCM Server" SCM 7.0 - SCM Optimizer SAP SCM 7.0 SAP SCM Server See description of "EHP1 FOR SAP SCM 7.0 - SCM Server" SAP liveCache SAP EHP2 FOR SAP BW ABAP The primary recommendation is to run these application SAP components on two different systems, one with AS ABAP and one NETWEAVER 7.0 with AS Java. For more information, see http://www.sdn.sap.com/ - Business irj/scn/index?rid=/library/uuid/70b3f2c0-cbea-2b10-ef9eIntelligence 90f61c39c1fb&overridelayout=true, slides 14-23. The following applies for this example: Since you are already running SAP BW 7.0 (running on an AS ABAP), you must implement the SAP BW parts of enhancement package 2 for SAP NetWeaver 7.0. SAP SAP PI This application component runs on SAP PI. NETWEAVER 7.0 - Process Integration (PI/ XI) EHP1 FOR SAP SAP PI This application component runs on SAP PI. SCM 7.0 - XI Content
60/72
PUBLIC
2011-05-12
5 5.3
Figure 19:
5.
6.
The following activities are therefore required: Update: You implement the SAP ECC Server parts of enhancement package 5 for SAP ERP 6.0 in your SAP ECC Server 6.0 system. You implement the XI content of enhancement package 5 for SAP ERP 6.0 in your SAP NetWeaver PI 7.0 system. In your SAP BW 7.0 system, you implement the BW parts of enhancement package 2 for SAP NetWeaver 7.0 and the BW parts of enhancement package 5 for SAP ERP 6.0. New installation: You install SAP SCM Server 7.0, SAP liveCache 7.0 and SAP SCM Optimizer 7.0 including the SCM Server and SCM Optimizer parts of enhancement package 1 for SAP SCM 7.0 together as an SAP system. You implement the XI content of enhancement package 1 for SAP SCM 7.0 in your SAP NetWeaver PI 7.0 system. Check dependencies using the Upgrade Dependency Analyzer (UDA) On SAP Service Marketplace, under http://service.sap.com/uda, call the Upgrade Dependency Analyzer tool. Check whether there are dependencies between the update to enhancement package 5 for SAP ERP 6.0 based on the SAP ECC Server, and the update of the SAP BW parts of enhancement package 2 for SAP NetWeaver 7.0 for the SAP BW system 7.0. The check shows that there are no dependencies. Register the new systems Register the new system determined in step 4 in SAP Solution Manager using transaction SMSY as follows:
2011-05-12
PUBLIC
61/72
5 5.3
System SAP SCM 7.01
SMSY entry Product: SAP SCM ENHANCE PACKAGE Product version: EHP1 FOR SAP SCM 7.0 Main instance: Make the following entries: SCM Server SAP liveCache SCM Optimizer For all main instance entries, set the Relevant indicator.
7.
8.
9.
Create a maintenance transaction for the upgrade/update In SAP Solution Manager, in transaction SOLMAN_WORKCENTER, create exactly one maintenance transaction for the following activities: Installation of the SAP ECC Server parts of enhancement package 5 for SAP ERP 6.0 in the SAP ECC Server 6.0 system. Installation of the SAP BW parts of enhancement package 2 for SAP NetWeaver 7.0 and enhancement package 5 for SAP ERP 6.0 in your SAP BW 7.0 system The maintenance optimizer uses this maintenance transaction to calculate the files needed for the upgrade or update and to put them them in the download basket. Install the new systems Install the new system determined in step 4 as follows: SAP SCM 7.01: Using the tool SAPinst, you install an SAP system with the following components: SCM Server SAP liveCache SCM Optimizer Import the XI content of enhancement package 1 for SAP SCM 7.0 into the Integration Repository of the SAP NetWeaver PI 7.0 system. Required upgrade/update activities Implement the SAP ECC Server parts of enhancement package 5 for SAP ERP 6.0 in the SAP ECC Server 6.0 system. Proceed as follows: 1. Use the SAPehpi tool to implement the SAP ECC Server parts of enhancement package 5 for SAP ERP 6.0 in your SAP ECC Server 6.0 system. 2. Activate the required business functions in your SAP ECC Server 6.05 system using the Switch Framework (transaction code SFW5). Update to SAP NetWeaver BW ABAP 7.02 Using the SAPehpi tool, implement the SAP BW parts of enhancement package 2 for SAP NetWeaver 7.0 and of enhancement package 5 for SAP ERP 6.0 in your SAP BW 7.0 system Update SAP NetWeaver PI 7.0
62/72
PUBLIC
2011-05-12
5 5.3
Import the XI content of enhancement package 5 for SAP ERP 6.0 into the Integration Repository of the SAP NetWeaver PI 7.0 system. 10. Update the system configuration Use transaction SMSY to update your system data in SAP Solution Manager. Proceed as follows: 1. Delete the following entries: Those relating to your SAP ERP 6.0 system (SAP ECC Server 6.0) Those relating to your SAP NetWeaver BW 7.0 system (AS ABAP 7.00) for your SAP NetWeaver PI 7.0 system 2. Create the following new entries:
System SAP ECC Server 6.05 SMSY entry Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: Central applications For this system, you must create two entries in transaction SMSY: As SAP ERP: Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: ABAP Technology for ERP As SAP NetWeaver: Product: SAP NetWeaver Product version: SAP EHP2 FOR SAP NetWeaver 7.0 Main instance: Business Intelligence For this system you must create three entries in transaction SMSY: As SAP ERP: Product: SAP ERP ENHANCE PACKAGE Product version: EHP5 FOR SAP ERP 6.0 Main instance: Conventional XI Content As SAP SCM: Product: SAP SCM ENHANCE PACKAGE Product version: EHP1 FOR SAP SCM 7.0 Main instance: XI Content As SAP NetWeaver: Product: SAP NetWeaver Product version: SAP NetWeaver 7.0 Main instance: Process Integration (PI/XI)
SAP BW ABAP 7.02
SAP PI 7.0
2011-05-12
PUBLIC
63/72
A A.1
Reference The Main SAP Documentation Types
A Reference
A.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software.
Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many glossary entries in English and German. Target group: Relevant for all target groups Current version: On SAP Help Portal at http://help.sap.com Glossary In the SAP system in transaction STERM SAP Library is a collection of documentation for SAP software covering functions and processes. Target group: Consultants System administrators Project teams for implementations or upgrades Current version: On SAP Help Portal at http://help.sap.com (also available as documentation DVD) 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 SAP NetWeaver. This document contains general guidelines and suggestions. SAP applications have a security guide of their own. Target group: System administrators Technology consultants Solution consultants Current version: On SAP Service Marketplace at http://service.sap.com/securityguide
Implementation
The master guide is the starting point for implementing an SAP solution. It lists the required installable units for each business or IT scenario. It provides scenario-specific descriptions of preparation,
2011-05-12
PUBLIC
65/72
A A.1
execution, and follow-up of an implementation. It also provides references to other documents, such as installation guides, the technical infrastructure guide and SAP Notes. Target group: Technology consultants Project teams for implementations Current version: On SAP Service Marketplace at http://service.sap.com/instguides The installation guide describes the technical implementation of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Target group: Technology consultants Project teams for implementations Current version: On SAP Service Marketplace at http://service.sap.com/instguides Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle platform. One of its main functions is the configuration of business scenarios, business processes, and implementable steps. It contains Customizing activities, transactions, and so on, as well as documentation. Target group: Technology consultants Solution consultants Project teams for implementations Current version: In SAP Solution Manager The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing activities and their documentation are structured from a functional perspective. (In order to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.) Target group: Solution consultants Project teams for implementations or upgrades Current version: In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers
66/72
PUBLIC
2011-05-12
A A.1
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. Target group: System administrators Current version: On SAP Service Marketplace at http://service.sap.com/instguides The application operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. Target group: System administrators Technology consultants Solution consultants Current version: On SAP Service Marketplace at http://service.sap.com/instguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes 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 upgrade guides and SAP Notes. Target group: Technology consultants Project teams for upgrades Current version: On SAP Service Marketplace at http://service.sap.com/instguides The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Target group: Technology consultants Project teams for upgrades Current version: On SAP Service Marketplace at http://service.sap.com/instguides Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG). Target group:
2011-05-12
PUBLIC
67/72
A A.1
Consultants Project teams for upgrades Current version: On SAP Service Marketplace at http://service.sap.com/releasenotes In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
68/72
PUBLIC
2011-05-12
Typographic Conventions
Example
<Example>
Description
Example Example Example

Example
Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard
http://www.sap.com /example
123456 Example
Example
EXAMPLE
EXAMPLE
2011-05-12
PUBLIC
69/72
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.
70/72
PUBLIC
2011-05-12
Documentation in the SAP Service Marketplace
You can find this document at the following address: http://service.sap.com/instguides
2011-05-12
PUBLIC
71/72
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Planning Guide SAP Business Suite

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Planning Guide SAP Business Suite

Enviado por

Direitos autorais:

Formatos disponíveis

Planning Guide SAP Business Suite

Landscape Implementation - Technical Planning Guide

PUBLIC Document version: 1.2 2011-05-12

Revised version with corrections/enhancements from ramp-up phase

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Goal of this Document

1 Goal of this Document

Introduction A Short Explanation of Important Terms

2.1 A Short Explanation of Important Terms

Introduction A Short Explanation of Important Terms

Introduction A Short Explanation of Important Terms

See Product Instance.

Introduction A Short Explanation of Important Terms

Introduction A Short Explanation of Important Terms

Introduction Overview of the SAP System Landscape

The SAP system into which you import new software.

2.2 Overview of the SAP System Landscape

Introduction Overview of the SAP System Landscape

Introduction Overview of the SAP System Landscape

Introduction Overview of the SAP System Landscape

Introduction Overview of the SAP System Landscape

Introduction Building Blocks for System Landscapes EXAMPLE

Introduction Building Blocks for System Landscapes

Introduction Building Blocks for System Landscapes

2.3.2 SAP Business Suite 7 Innovations 2010

Process Integration (PI)

Business Intelligence (BI) TREX

7.00, 7.10 7.1

Process Integration (PI)

Business Intelligence (BI) TREX

Master Data Management (MDM)

2.3.3 The Role of SAP Solution Manager

Introduction Building Blocks for System Landscapes

Introduction Introduction to the Recommendation Methodology

2.4 Introduction to the Recommendation Methodology

Introduction Introduction to the Recommendation Methodology

2.4.1 General Recommendation

Introduction Introduction to the Recommendation Methodology

2.4.2 Reasonable Alternative

Introduction Introduction to the Recommendation Methodology

2.4.3 Possible Exception

Introduction Further Information

2.5.2 Information in the Master Guides

Introduction Further Information

2.5.3 Important SAP Notes

SAP Note 1388258 1515223 1573180

3 How Do I Plan My System Landscape?

3.1 Business Requirements Determine the Landscape Structure

solutions/executiveview/product-development/index.epx) An example of an implementable step

3.1.2 The Scenario and Process Component List

3.3 Selecting Business Functions in Solution Manager

3.4.1 Determining Functions in the Help Portal

3.4.2 Determining Functions in the Solution Browser

3.5 Determining Dependencies on Other Systems

How Do I Plan My System Landscape? Determining Dependencies on Other Systems

3.5.1 Basic Installation Procedure

3.5.2 Basic Upgrade Procedure

What I Need to Do:

3.5.3 Basic Update Procedure

3.5.4 Update Support by Landscape Verification for SAP Solution Manager

How Do I Plan My System Landscape? Determining Dependencies on Other Systems

3.5.6 Using Release Notes to Identify Changes