Planning guide sap business suite 7 2013 landscape implementation

Planning Guide
SAP Business Suite
Landscape Implementation - Technical Planning Guide
Target Audience°˜ƒÐ ¬
Technical Consultants°˜ƒÐ ¬
System Administrators°˜ƒÐ ¬
Software Architects
PUBLIC
°˜ƒ47c ¢B1!ehEå ™}þÚ)æõljm0ëÃP›ÔùËqû¶~⁄I J ‘ðg>�ó·¸ŸD.^uèk⁄Ÿ Îbt2*UC

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.4
2013-08-13
Revised version for Business Suite 7 Innovations 2013 (BS7i2013)
2/54 PUBLIC 2013-08-13

Table of ContentsChapter 1Goal of this Document..........................................5Chapter 2Introduction..................................................72.1A Short Explanation of Important Terms.............................72.2Overview of the SAP System Landscape..............................122.3Building Blocks for System Landscapes..............................182.3.1Evolution of an SAP System Landscape..............................182.3.2SAP Business Suite 7 Innovations 2013...............................192.3.3SAP Business Suite 7 Innovations 2011...............................202.3.4SAP Business Suite 7 Innovations 2010...............................212.3.5The Role of SAP Solution Manager.................................232.4Introduction to the Recommendation Methodology...................242.4.1General Recommendation........................................252.4.2Reasonable Alternative...........................................262.4.3Possible Exception..............................................272.5Further Information.............................................282.5.1Information in SAP Community Network (SCN)......................282.5.2Information in the Master Guides..................................282.5.3Important SAP Notes............................................29Chapter 3How Do I Plan My System Landscape?.............................313.1Business Requirements Determine the Landscape Structure..............313.1.1How to Determine Which New Business Processes and New Functions You Require.......................................................323.1.2Scenario and Process Component List...............................323.2Process-Oriented and Scenario-Oriented Planning Framework via Solution Manager Content...............................................333.3Selecting Business Functions in Solution Manager......................333.4Function-Oriented Planning Framework via Help Portal and Solution Browser......................................................343.4.1Determining Functions in the Help Portal............................34
2013-08-13 PUBLIC 3/54

3.4.2Determining Functions in the Solution Browser.......................343.5Determining Dependencies on Other Systems.........................343.5.1Basic Installation Procedure.......................................353.5.2Basic Upgrade Procedure.........................................353.5.3Basic Update Procedure..........................................363.5.4Update Support by Landscape Verification for SAP Solution Manager......................................................373.5.5Special Features When Switching from SAP R/3 4.6C to SAP Business Suite.........................................................373.5.6Using Release Notes to Identify Changes.............................37Chapter 4Distribution Scenarios.........................................394.1Version Compatibility Within a System Landscape......................394.2Single Stack System.............................................404.3Use as Hub, Sidecar, or Embedded Deployment........................414.3.1Hub System...................................................414.3.2Sidecar System.................................................434.3.3Embedded Deployment..........................................44Chapter 5Implementation Example.......................................475.1'Employee Self-Service' Process with Enhancement Package 5 for SAP ERP 6.0...........................................................47
4/54 PUBLIC 2013-08-13

1Goal 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 (TCO). 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.
1 Goal of this Document
2013-08-13 PUBLIC 5/54

This page is left blank for documents
that are printed on both sides.

2Introduction
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: „fl÷7 ¾
the organizational structure of the organization„fl÷7 ¾
the expected speed of innovation for implemented applications„fl÷7 ¾
security requirements„fl÷7 ¾
the product and architecture strategy„fl÷7 ¾
the individual requirements for performance and scalability„fl÷7 ¾
the need for required governance processes„fl÷7 ¾
the required availability and the service level agreements needed„fl÷7 ¾
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„fl÷7 ¾
in which the most important aspects of landscape planning are given as balanced a weighting as possible„fl÷7 ¾
which demonstrate the right balance between flexibility, simplicity, and clear structure„fl÷7 ¾
which can be implemented by the majority of customers„fl÷7 ¾
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.1A 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. For the full SAP glossary, see http://help.sap.com/ Additional InformationTerminology and Glossary.
2 Introduction
2.1 A Short Explanation of Important Terms
2013-08-13 PUBLIC 7/54

Building Block
This is the smallest logical unit in a system landscape, such as the parts of an SAP ERP system 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: +ü=f)=
Common system ID (SID) for all application servers and the database+ü=f)=
Common startup framework for AS ABAP and AS Java+ü=f)=
Common database (with different database schemas for ABAP and Java) +ü=f)=
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 and the business functions contained therein, 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.
2 Introduction
8/54 PUBLIC 2013-08-13

Installation
The procedure followed when you install software. This might be the first installation of an SAP product, such as as SAP ERP system. You use the program SAPinst for the installation.
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
For each system, there must be just one relevant ABAP main instance for ABAP-based SAP products.
Maintenance Optimizer
SAP Solution Manager Maintenance Optimizer (MOPZ) is 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. Maintenance Optimizer gets this information from the system landscape of Solution Manager (SMSY), whose data therefore needs to be up to date and correct. The Landscape Verification Wizard can be used to check the consistency of the system landscape.
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 CRM.
Product Instance
This 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.
2 Introduction
2013-08-13 PUBLIC 9/54

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 18].
SAP ERP
Abbreviation for SAP Enterprise Resource Planning. For a short description, see Evolution of an SAP System Landscape [page 18].
SAP NetWeaver
For a short description, see Evolution of an SAP System Landscape [page 18].
SAP PLM
Abbreviation for SAP Product Lifecycle Management. For a short description, see Evolution of an SAP System Landscape [page 18].
SAP SCM
Abbreviation for SAP Supply Chain Management. For a short description, see Evolution of an SAP System Landscape [page 18].
SAP Solution Manager System Landscape
Contains all information about the SAP systems in a landscape. Use transaction SMSY to enter or edit the required data in SAP Solution Manager. Make sure that the information about the system landscape is always up to date. That also applies after an update or upgrade. If the information collected about the system landscape 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 18].
2 Introduction
10/54 PUBLIC 2013-08-13

Software Update Manager (SUM)
This is the unified maintenance tool supporting various implementation processes for SAP NetWeaver- based products such as release upgrades, enhancement package installations, and application of downtime-optimized Support Package Stacks. The Software Update Manager evolved from the previous SAP Enhancement Package Installer (SAPehpi) and SAP upgrade tools (SAPup, SAPJup) and has been renamed to reflect its broader use. SUM is part of the product-independent SL Toolset delivery.
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) are installed in separate 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
2 Introduction
2013-08-13 PUBLIC 11/54

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, and others.
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.2Overview of the SAP System LandscapeFeaturesThe following graphic shows the possible components of an SAP Business Suite landscape schematically:
2 Introduction
2.2 Overview of the SAP System Landscape
12/54 PUBLIC 2013-08-13

“¾¢¶ùY$¦öZóÀ‡ƒB&4Ø´fi’uSAP Business Suite: Possible Components of SAP System Landscape
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.
2 Introduction
2013-08-13 PUBLIC 13/54

Wº{< —ådY¥Ò¦Cj áÓt+‹V°SAP Business Suite: Main Applications (ABAP View Only)
SAP Solution Manager is an important part of the system landscape. This serves as a tool for maintaining system landscapes. The following graphic displays SAP Solution Manager in detail. Wº{< —ådY¥Ò¦Cj áÓu+‹V°SAP Solution Manager
2 Introduction
14/54 PUBLIC 2013-08-13

For more information about SAP Solution Manager, see the section The Role of SAP Solution Manager [page 23].
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 its own system, whereby this system is based technically on AS ABAP and AS Java (or only on AS Java, if you choose the new installation option Advanced Adapter Engine Extended (AEX) that was introduced with PI 7.3 or the variant Process Orchestration (PO) that was introduced with 7.40, this being a joint installation of Business Process Management (BPM) and AEX). 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. aÏ›ô¿‘¬uÞû�†òAòSAP NetWeaver and Its Components
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 followingaÏ› ıF
New processes must be achievable in the existing system landscape or by a step-by-step enhancement of this system landscape.
2 Introduction
2013-08-13 PUBLIC 15/54

jÄÚ·A
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. jÄÚ·A
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. jÄÚ·A
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.
ESR Content (Process Integration/XI Content) runs in higher SAP NetWeaver releases without any adjustments. In addition, it is delivered in the following two formats, starting with SAP ERP 6.0 EHP3, SAP CRM 7.0, SAP SRM 7.0, and SAP SCM 7.0: jÄÚ·.
Format 7.0: ESR content in this format can be imported to higher ES repositories. jÄÚ·.
Format 7.1: As of SAP NW PI 7.1, we recommend that you import ESR content in this format to make use of the entire functionality of SAP NW PI.
For all Business Suite deliveries as of BS7i2013, PI 7.0x and PI 7.1x are no longer supported (this is also valid for BI and Portal). The content is only delivered in the format PI 7.3.
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:
2 Introduction
16/54 PUBLIC 2013-08-13

ÎëEÂ¡
Application-driven innovations ÎëEÂ¡
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.
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 “technology- driven 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 Introduction
2013-08-13 PUBLIC 17/54

2.3Building Blocks for System Landscapes2.3.1Evolution of an SAP System LandscapeFeaturesA 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 OfferingThe 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 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. m“lfl SAP NetWeaverSAP 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. m“lfl 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. m“lfl 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. m“lfl 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
2 Introduction
2.3 Building Blocks for System Landscapes
18/54 PUBLIC 2013-08-13

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. 2.3.2SAP Business Suite 7 Innovations 2013FeaturesSAP Business Suite 7 Innovations 2013 (BS7i2013) is the current version of SAP Business Suite. This version contains SAP enhancement package 7 for SAP ERP 6.0, SAP enhancement package 3 for SAP CRM 7.0, SAP enhancement package 3 for SAP SCM 7.0, SAP enhancement package 3 for SAP SRM, and more. The following states which application-driven and technology-driven innovations are available to you for the core applications of SAP Business Suite, such as SAP ERP. Application-Driven InnovationsApplication-driven innovations are mainly offered to existing customers who are already using productive SAP systems (Enterprise Portal, Business Intelligence, Process Integration) in their landscape. With application-driven innovations, it is usually the case that an SAP enhancement package is installed without the need for a new NetWeaver version. Since BS7i2013 uses new functions of SAP NetWeaver, it is necessary to upgrade or update to SAP NetWeaver AS ABAP 7.40 and to at least SAP NetWeaver AS Java 7.30 as the basis for existing portal, BI and PI systems. Technology-Driven InnovationsCustomers wishing to implement BS7i2013 and also to use the technological innovations of SAP NetWeaver must switch to SAP NetWeaver AS ABAP 7.40 and SAP NetWeaver AS Java 7.40, and make an update for SAP PI (from PI 7.1 or 7.11) or an upgrade (from PI 7.0x) to at least SAP PI 7.30. This is known as technology-driven innovation. The following table gives an overview of which products can be combined with which version in the system landscape:
2 Introduction
2013-08-13 PUBLIC 19/54

Landscape
ABAP Application Systems (ECC, CRM, and So On)
Portal
Process Integration (PI)
Business Intelligence (BI)
TREX
Master Data Management (MDM)
Solution Manager
Supported area
7.40
7.30, 7.31, 7.40
7.30, 7.31, 7.40
7.30, 7.31, 7.40
7.1
7.1
7.01, 7.1
Application-driven
7.40
7.30
7.30
7.30
7.1
7.1
7.01
Technology-driven
7.40
7.40
7.40
7.40
7.1
7.1
7.1
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 application- driven and technology-driven innovations.
With a new installation of ERP Java applications, at least SAP NetWeaver 7.30 is necessary.
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.3SAP Business Suite 7 Innovations 2011FeaturesSAP Business Suite 7 Innovations 2011 contains SAP enhancement package 6 for SAP ERP 6.0, SAP enhancement package 2 for SAP CRM 7.0, SAP enhancement package 2 for SAP SCM 7.0, SAP enhancement package 2 for SAP SRM, and more. The following states which application-driven and technology-driven innovations are available to you for the core applications of SAP Business Suite, such as SAP ERP. Application-Driven InnovationsApplication-driven innovations are mainly offered to existing customers who are already using productive SAP systems (Enterprise Portal, Business Intelligence, Process Integration) in their landscape. With application-driven innovations, an SAP enhancement package is applied. The system landscape for application-driven innovations keeps the SAP NetWeaver 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 3 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. EXAMPLEThe SAP ECC parts of SAP enhancement package 6 for SAP ERP 6.0 are always based on SAP enhancement package 3 for SAP NetWeaver 7.0 (AS ABAP).
2 Introduction
20/54 PUBLIC 2013-08-13

This approach makes additional technological competencies that are required for certain scenarios transparent. SAP enhancement packages for SAP NetWeaver 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 system to SAP NetWeaver 7.03 and to make an update for SAP PI (from PI 7.1 or 7.11) or an upgrade (from PI 7.0x) to at least SAP PI 7.3. This is known as technology- driven innovation.
The following table gives an overview of which products can be combined with which version in the system landscape:
Landscape
Portal
TREX
Solution Manager
Supported area
7.03
7.00, 7.01, 7.02, 7.30
7.00, 7.01, 7.02, 7.10, 7.11, 7.30
7.00, 7.01, 7.02, 7.30
7.00, 7.10
7.10
7.01, 7.10
Application-driven
7.03
7.00
7.00
7.00
7.00
7.10
7.01
Technology-driven
7.03
7.30
7.30
7.30
7.10
7.10
7.10
In the above table, “7.01” stands for SAP enhancement package 1 for SAP NetWeaver 7.0, “7.02” stands for SAP enhancement package 2 for SAP NetWeaver 7.0, and “7.03” stands for SAP enhancement package 3 for SAP NetWeaver 7.0.
With a new installation of ERP Java applications, SAP recommends the use of SAP NetWeaver 7.3.
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.4SAP Business Suite 7 Innovations 2010FeaturesSAP Business Suite 7 Innovations 2010 contains SAP enhancement package 5 for SAP ERP 6.0, SAP enhancement package 1 for SAP CRM 7.0, SAP enhancement package 1 for SAP SCM 7.0, SAP enhancement package 1 for SAP SRM, and more. The following states which application-driven and technology-driven innovations are available to you for the core applications of SAP Business Suite, such as SAP ERP.
2 Introduction
2013-08-13 PUBLIC 21/54

Application-Driven Innovations
Application-driven innovations are mainly offered to existing customers who are already using productive SAP systems (Enterprise Portal, Business Intelligence, Process Integration) in their landscape. With application-driven innovations, an SAP enhancement package is applied.
The system landscape for application-driven innovations keeps the SAP NetWeaver 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 serve as the basis for the applications of the Innovations 2010 version of SAP Business Suite 7. 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 6 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 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 system to SAP NetWeaver 7.02 or 7.03 and to make an update for SAP PI (from PI 7.1 or 7.11) or an upgrade (from PI 7.0x) to at least SAP PI 7.3. This is known as technology-driven innovation.
The following table gives an overview of which products can be combined with which version in the system landscape:
Landscape
Portal
TREX
Supported area
7.02
7.00, 7.01, 7.02
7.00, 7.01, 7.02, 7.10, 7.11, 7.3
7.00, 7.01, 7.02
7.00, 7.10
7.1
Application- driven
7.02
7.00
7.00
7.00
7.00
7.1
Technology- driven
7.02
7.02
7.3
7.02
7.10
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.
2 Introduction
22/54 PUBLIC 2013-08-13

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.5The Role of SAP Solution ManagerFeaturesSAP Solution Manager supports you during the complete life cycle of your applications, starting with the Business Blueprint, during the configuration, and right through to productive operation. It gives you central access to tools, methods and preconfigured content that you can use while evaluating and implementing your systems, as well as during operations. SAP Solution Manager and the information it contains about the system landscape are therefore extremely important for the setup and maintenance of a consistent system landscape. We recommend that you always use the latest 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: õ5‰ö ‚InstallationFor example, this can be the first installation of an SAP system, such as an SAP ECC server. õ5‰ö ‚UpgradeFor 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. õ5‰ö ‚Support Package updateFor 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. õ5‰ö ‚SAP enhancement package updateFor 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 you import SAP enhancement packages, you typically import Support Package Stacks (SPS) at the same time. In SAP Solution Manager you use the maintenance optimizer, for example, when importing Support Package Stacks or SAP enhancement packages, to determine which system-dependent stacks of the software components need to be imported into the relevant target system so that you get the target status you defined. Therefore, SAP Solution Manager must always be of the latest release, must be configured correctly, and must always have up-to-date information on the existing system landscape. How to Use SAP Solution Manager to Import an SAP Enhancement PackageTo give a detailed example of the use of Solution Manager, here is a description of some activities that need to be performed with the maintenance optimizer to import an SAP enhancement package:
2 Introduction
2013-08-13 PUBLIC 23/54

When working 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 stack 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 stack configuration file, Solution Manager relies on the information about the target systems in the SAP Solution Manager system landscape. You implement the new software using Software Update Manager (SUM), which is contained in the SL Toolset 1.0 as of SP03. 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. *¿é°M8Ÿ =˛Ê/¦…Ì`rÒ4Õ&oUsing SAP Solution Manager and Software Update Manager (SUM) to Import an SAP Enhancement Package
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.4Introduction to the Recommendation Methodology
For our recommendations on building a system landscape, we have divided the various options into three categories: *¿éøhñ
General recommendation
2 Introduction
2.4 Introduction to the Recommendation Methodology
24/54 PUBLIC 2013-08-13

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. lÿvmwo
Reasonable alternative
This option is a sensible choice for particular use cases or customer scenarios. It is in keeping with the SAP product strategy. lÿvmwo
Possible exception
This option only makes sense for very specific use cases. There may be considerable restrictions on support offered by SAP.
These three categories help to answer the following questions and derive recommendations from them: lÿvmwo
Does it make sense for these modules to be stored centrally or locally in the system landscape? lÿvmwo
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.1General RecommendationFeaturesThe 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 portal provides users with central, personalized, and role-based access to the application systems (also see the following graphic).
2 Introduction
2013-08-13 PUBLIC 25/54

ªXŁ°Ë¾ aËm û±FVXgù4⁄Í·General Recommendation for SAP NetWeaver Portal2.4.2Reasonable AlternativeFeaturesIn 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.
2 Introduction
26/54 PUBLIC 2013-08-13

!¼ýÂkÿí[áfl P.7W¶âz˝ñ®Reasonable Alternative for SAP NetWeaver Portal2.4.3Possible ExceptionFeaturesFor 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. This document does not provide any further details about such a system landscape. !¼ýÂkÿí[áfl P.7W¶íz˝ñ®Possible Exception for SAP NetWeaver Portal
2 Introduction
2013-08-13 PUBLIC 27/54

2.5Further Information2.5.1Information in SAP Community Network (SCN) FeaturesIf 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, SAP Community Network provides information about landscape design and corresponding recommendations. See http://www.sdn.sap.com/irj/sdn/landscapedesign and http://wiki.sdn.sap.com/wiki/ display/SLGB/Landscape+Recommendations. You can find basic information about SAP Community Network under About SCN Getting Started. 2.5.2Information in the Master GuidesFeaturesThe Master Guide for an SAP solution is the central leading document and should be used as the starting point when implementing the selected SAP solution. It explains 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 third-party 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.
2 Introduction
2.5 Further Information
28/54 PUBLIC 2013-08-13

2.5.3Important 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
Title
Description1388258
Version Interoperability Within the SAP Business Suite1515223SAP NetWeaver Process Integration: Release Recommendation1573180AEX Enablement for SAP Business Suite1468349SAP Business Suite 7 for SAP NetWeaver 7.3 Hub Systems1615463SAP Business Suite 7i 2010 for SAP NetWeaver 7.3 Hub Systems1637629No Process Integration in SAP EHP3 FOR SAP NETWEAVER 7.0
2 Introduction
2.5 Further Information
2013-08-13 PUBLIC 29/54

3How 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.
Ideally, proceed as follows to map your business requirements in your customer-specific system 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.1Business 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 individual 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/ solutions/executiveview/product-development/index.epx; choose R&D Solutions Learn more about
3 How Do I Plan My System Landscape?
3.1 Business Requirements Determine the Landscape Structure
2013-08-13 PUBLIC 31/54

product development Learn more about collaborative procuct development for discrete manufacturingSolution in Detail: Integrated Product Development ) 3.1.1How to Determine Which New Business Processes and New Functions You RequireFeaturesIf you plan to implement new software, you have two options for determining the system landscape required for this: Kn°` ÅYou can select those end-to-end business processes that you require. Kn°` ÅFrom the parts of SAP Business Suite, you can select those components and functions with which you can map an already known business process or upgrade an existing business process to include enhancements. For an initial overview of the business processes and functions available in SAP Business Suite, see SAP Service Marketplace at http://service.sap.com/businesssuite. If you are interested in the ramp-up process, choose http://service.sap.com/rkt. Here you can find all information on Ramp-Up Knowledge Transfer (RKT). Navigate to SAP Business Suite SAP Business Suite Value Scenarios . Here you can find some learning maps, such as one of the topic of “Integrated Product Development”. If you want information about individual core applications 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.2Scenario and Process Component ListFeaturesThe 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: Kn°` Å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? Kn°` Å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 web-based program that is available on SAP Service Marketplace. Choose http://service.sap.com/scl. You then have the following options for accessing the information you require: Kn°` Åvia the SAP scenarios and realization alternatives (SAP Scenarios and Realization Alternatives) or
3.1 Business Requirements Determine the Landscape Structure
32/54 PUBLIC 2013-08-13

<,“…àt
via the SAP software product versions and possible scenarios (SAP Software Product Versions and Possible Scenarios).
Choose go>> to start your selection. 3.2Process-Oriented and Scenario-Oriented Planning Framework via Solution Manager ContentFeaturesIf 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). You can call this using the following link https:// implementationcontent.sap.com/bpr. 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). For information about SAP enhancement packages of the other applications in the SAP Business Suite, see http:// service.sap.com/crm-ehp, http://service.sap.com/plm-ehp, http://service.sap.com/scm-ehp, and http://service.sap.com/srm-ehp. 3.3Selecting Business Functions in Solution ManagerFeaturesIf 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.
3.2 Process-Oriented and Scenario-Oriented Planning Framework via Solution Manager Content
2013-08-13 PUBLIC 33/54

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. 3.4Function-Oriented Planning Framework via Help Portal and Solution Browser
If, instead of choosing a scenario, you require certain functions in SAP applications, perform function- oriented 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.1Determining Functions in the Help PortalFeaturesFor 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 6” or earlier enhancement packages is available in various languages. 3.4.2Determining Functions in the Solution BrowserFeaturesAn 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://service.sap.com/solutionbrowser and then Start Application. Enter the language of your choice. Then choose your application, such as “SAP ERP”, your source release, such as “SAP R/3 4.6C”, your target release, such as “SAP Enhancement Package 6 for SAP ERP 6.0”, the application area, such as “Product Development and Collaboration”, and the required functional area, such as “Product Development”. The solution browser issues a list of changed functions according to the selected search criteria. This list states which features are new, starting from which release, and which advantage implementing this function has. 3.5Determining Dependencies on Other SystemsIn 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
3.4 Function-Oriented Planning Framework via Help Portal and Solution Browser
34/54 PUBLIC 2013-08-13

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 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.1Basic Installation ProcedureFeaturesGood 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 installation2.Preparing the installation3.Performing the installation4.Following up on the installationFor 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.2Basic Upgrade ProcedureFeaturesThe 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
3.5 Determining Dependencies on Other Systems
2013-08-13 PUBLIC 35/54

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:
My Starting Release:
What I Need to Do:
My Target Release in SAP Business Suite 7:
SAP ERP 6.0
Import SAP enhancement package 7 for SAP ERP 6.0
SAP ERP 6.0 plus SAP enhancement package 7 for SAP ERP 6.0
SAP R/3 4.0B and higher
Upgrade to SAP ERP 6.0 and import SAP enhancement package 7 for SAP ERP 6.0
SAP ERP 6.0 plus SAP enhancement package 7 for SAP ERP 6.0
SAP CRM 5.0 and higher
Import SAP enhancement package 3 for SAP CRM 7.0
SAP CRM 7.0 plus SAP enhancement package 3 for SAP CRM 7.0
SAP SRM 4.0 and higher
Import SAP enhancement package 3 for SAP SRM 7.0
SAP SRM 7.0 plus SAP enhancement package 3 for SAP SRM 7.0
SAP SCM 4.1 and higher
Import SAP enhancement package 3 for SAP SCM 7.0
SAP SCM 7.0 plus SAP enhancement package 3 for SAP SCM 7.0
If you want to implement any SAP Business Suite applications delivered in 2013 and later that need an SAP NetWeaver hub, you must perform an upgrade to NetWeaver 7.30 or higher for these hubs.
For the latest information about other enhancement packages, see:http://service.sap.com/crm- ehp, http://service.sap.com/scm-ehp, http://service.sap.com/srm-ehp
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.3Basic Update ProcedureFeaturesAn 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
36/54 PUBLIC 2013-08-13

SRM and SAP CRM, you must use the respective maintenance transactions of the maintenance optimizer. 3.5.4Update Support by Landscape Verification for SAP Solution ManagerFeaturesStarting from an update to SAP enhancement package 4 for SAP ERP 6.0, it is mandatory to use the maintenance optimizer in Solution Manager. To perform its calculations, the maintenance optimizer uses the data of the system landscape that you entered in transaction SMSY in Solution Manager. For this reason, you must ensure that the data on the system landscape is always up to date. You can use the Landscape Verification for SAP Solution Manager (called Landscape Verification Wizard below) to support you with data maintenance in the system landscape and to find inconsistencies in data that was entered manually. You can use this tool to import the current data from the system landscape, check this data, correct it as required, and then transfer it back. The Landscape Verification Wizard can therefore be used to correct data of an existing system landscape and to make preparations for enhancing the system landscape. In detail, the Landscape Verification Wizard checks the following system landscape 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 or add the data manually in the wizard and update the system landscape. 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.5Special Features When Switching from SAP R/3 4.6C to SAP Business SuiteFeaturesGood 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.6Using Release Notes to Identify Changes
2013-08-13 PUBLIC 37/54

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&.
38/54 PUBLIC 2013-08-13

4Distribution 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.1Version 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.
However, this is only valid in certain corridors: -'˘&
To enable customers to use the new possibilities available with JAVA EE 5 and to benefit from the improvements with SAP NetWeaver 7.3, the area for version compatibility of those SAP Business Suite applications with Release to Customer (RtC) in 2013 and later has been shifted upwards. SAP Business Suite 7 Innovations 2013 is thus affected for the first time. -'˘&
For already delivered main applications or enhancement packages of SAP Business Suite 7, SAP Business Suite 7 Innovations 2010, and SAP Business Suite 7 Innovations 2011, the originally defined version compatibility area remains valid within the given maintenance period .
Exceptions in Version Compatibility
All SAP applications are generally compatible with other versions. In practice this is not always possible. The Upgrade Dependency Analyzer (UDA) tool allows you to identify possible exceptions in version compatibility. You can use this tool to determine dependencies for an upgrade. For more information about the Upgrade Dependency Analyzer and other information, see SAP Service Marketplace at http:// service.sap.com/uda.
4 Distribution Scenarios
4.1 Version Compatibility Within a System Landscape
2013-08-13 PUBLIC 39/54

4.2Single 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: ½<Õ3Z¡
Flexibility with regard to Support Package Stacks and releases ½<Õ3Z¡
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.
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: ½<ÕÕ�h%8˜ZkgÁBL Rm@eúeMain 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: ½<Õ3Z¡
Entire box / dark blue box = product ½<Õ3Z¡
Gray box = product instance / system ID ½<Õ3Z¡
Light blue box = comprised components)
4.2 Single Stack System
40/54 PUBLIC 2013-08-13

4.3Use as 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: ÕH
H º
As a hub system, which is used by several application backend systemsÕH
H º
As a sidecar system, which is used by exactly one application systemÕH
H º
Within an application backend system (embedded deployment)
You can find an example of every usage in the following documentation. For example, you can find a description of how to use SAP Self-Service (SAP XSS) with SAP NetWeaver Portal as the hub system, sidecar system, or "embedded deployment".
Implementation Recommendations for SAP Components
For more information about implementation recommendations for the most important components of SAP NetWeaver and SAP Business Suite, see http://wiki.sdn.sap.com/wiki/display/SLGB/ Landscape+Recommendations. 4.3.1Hub 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.
Effects on Entry in System Landscape 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: ÕH
H º
In transaction SMSY you need an own product system to which the technical system can be assigned.
4.3 Use as Hub, Sidecar, or Embedded Deployment
2013-08-13 PUBLIC 41/54

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: À�ÆSÐÀ‚É£oeÁÌ¼"‹;77OEWü¢¨łSAP NetWeaver Portal as Hub SystemEffects on Entries in System Landscape:
In transaction SMSY you must create three product systems for the portal system in the system landscape of Solution Manager (box “SAP NetWeaver: SAP NetWeaver Portal”): À�Æµõ
As SAP NetWeaverÀ�Æµõ
As SAP ERPÀ�Æµõ
As SAP CRMAdvantages of a Hub System: À�Æµõ
You have a simplified system landscape and a central administration. À�Æµõ
You have independent upgrade steps or update steps for the connected systems.
42/54 PUBLIC 2013-08-13

4.3.2Sidecar 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).
Effects on System Landscape
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 Entry in System Landscape of SAP Solution Manager
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: OEk€€ $
In transaction SMSY , you create exactly one entry for a product system. Two technical systems are assigned to this product system. OEk€€ $
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 System
If you implement SAP NetWeaver Portal as a sidecar system in this scenario, your system landscape might be as follows:
2013-08-13 PUBLIC 43/54

ˆh+Ô£vð>ºƒØ©zACxˇłÜi|ÈSAP NetWeaver Portal as Sidecar SystemEffects on Entries in System Landscape:
In transaction SMSY, you must create two technical systems for the upper sidecar system in the system landscape of SAP Solution Manager: ˆh+2yj
As SAP NetWeaver ˆh+2yj
As SAP ERP
In transaction SMSY, you must create two technical systems for the lower sidecar system in the system landscape of SAP Solution Manager: ˆh+2yj
As SAP NetWeaver ˆh+2yj
As SAP CRMAdvantages of a Sidecar System: ˆh+2yj
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.3Embedded Deployment
If you implement an SAP NetWeaver application as embedded deployment, this application runs on the application back-end system.
Effects on System Landscape
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.
44/54 PUBLIC 2013-08-13

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.
As of SAP Business Suite 7 Innovations 2011, SAP NetWeaver PI no longer supports embedded deployment. For more information, see SAP Note 1637629.
Effects on Entry in System Landscape of SAP Solution Manager
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: žðÑ¨6ƒ
In transaction SMSY, you create exactly one entry for a product system. The entry comprises the one technical system. žðÑ¨6ƒ
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: žðÑN O’a¾¥G,dGe4ŠÛÛyˇÐGÄSAP NetWeaver Portal as Embedded DeploymentEffects on Entries in System Landscape:
In transaction SMSY, you must create just one technical system in the system landcape of SAP Solution Manager for each of the two product systems (SAP ERP and SAP CRM): žðÑ¨6ƒ
As SAP ERPžðÑ¨6ƒ
As SAP CRM
2013-08-13 PUBLIC 45/54

5Implementation Example5.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: ¹fi|©Ø‘
In transaction SMSY you have registered your SAP R/3 4.6C system as follows: ¹fi|©Øà
Product: SAP R/3 ¹fi|©Øà
Product version: SAP R/3 4.6C ¹fi|©Øà
Main instance: R/3 server ¹fi|©Ø‘
In transaction SMSY, you have assigned RFC destinations for your SAP R/3 4.6C system. ¹fi|©Ø‘
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. ¹fi|©Ø‘
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 with SAP R/3 4.6C: ¹fi|OýFh E¬9¢Ák2ö¦ìÄ;±NÙ
Example of current system
2.Learn about new functions on SAP Service Marketplace
5 Implementation Example
5.1 'Employee Self-Service' Process with Enhancement Package 5 for SAP ERP 6.0
2013-08-13 PUBLIC 47/54

You can learn about new functions in the area of Human Resources Management on SAP Service Marketplace at http://service.sap.com/businesssuite. See SolutionsHuman Resources for the required information.
3.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 and choose Find. On the next screen, in the results list, choose the Employee Self Service process and then choose Next. Select Implementation in SAP ERP and choose Next.
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: ßJ›ÊÝM
EHP5 FOR SAP ERP 6.0 - SAP E-RecruitingßJ›ÊÝM
EHP5 FOR SAP ERP 6.0 - Central ApplicationsßJ›ÊÝM
EHP5 FOR SAP ERP 6.0 - ERecruitingßJ›ÊÝM
SAP ERP 6.0 - SAP NW - EP CoreßJ›ÊÝM
BP ERP05 COMMON PARTS 1.51 (SW-CV) ßJ›ÊÝM
BPERPESSWDA 1.50 (SW-CV) ßJ›ÊÝM
SAP ERP 6.0 - SAP NW - Search and ClassificationßJ›ÊÝM
SAP ERP 6.0 - SAP SRM - CCM SRM-MDM CatalogßJ›ÊÝM
SAP ERP 6.0 - SAP NW - Adobe Docu. Service
NOTEßJ›ÊÝM
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. ßJ›ÊÝM
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.
4.Plan your system landscape
48/54 PUBLIC 2013-08-13

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 Component or Product VersionSystemDescription
EHP5 FOR SAP ERP 6.0 E-Recruiting
Not to be implemented
In this example you decide not to use this application component for your customer-specific Employee Self-Service process.
EHP5 FOR SAP ERP 6.0 - Central Applications
SAP ECC Server
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.
SAP ERP 6.0 - SAP NW - EP Core
SAP XSS
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.
BP ERP05 COMMON PARTS 1.51
SAP XSS
You install this business package in the SAP XSS system that is based on SAP NetWeaver EP Core.
SAP ERP 6.0 - SAP NW - Search and Classification
In this example you decide not to use any enhanced search functions.
SAP ERP 6.0 - SAP SRM - CCM SRM- MDM Catalog
In this example you decide not to use this application component for your customer-specific Employee Self-Service process.
SAP ERP 6.0 - SAP NW - Adobe Docu. Service
SAP XSS
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-d5ab-b730a95ce923 &overridelayout=true, slides 25-27.
The following graphic shows the system landscape that is derived for this example from the above information:
2013-08-13 PUBLIC 49/54

ªõSÝâ», ¢}’w×ÔmhUìäÝ/EOPlanned System Landscape
The following activities are therefore required: ªõS;Çr
Upgrade: ªõS;Ç˛
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 Self- Service. ªõS;Çr
Installation ªõS;Ç˛
You install the SAP XSS system. This is set up as a sidecar system.
5.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.
6.Register the new systems
Register the new system determined in step 4 in SAP Solution Manager using transaction SMSY.
7.Install the new systems
Install the new SAP XSS system determined in step 4, as follows: ªõS;Çr
Use the SAPinst tool to install the following software units: ªõS;Ç˛
XSS ªõS;Ç˛
EP Core ªõS;Ç˛
AS Java ªõS;Çr
You can also use SAPinst to install most business packages.
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
50/54 PUBLIC 2013-08-13

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 Self- Service:
1.
Use the Software Update Manager (SUM) to perform the upgrade.
2.
In your ERP system, use the switch framework (transaction code SFW5) to activate those 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: SystemSMSY entry
SAP ECC server 6.0 +üKŽ¨
Product: SAP ERP ENHANCE PACKAGE +üKŽ¨
Product version: EHP5 FOR SAP ERP 6.0 +üKŽ¨
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.
2013-08-13 PUBLIC 51/54

Typographic Conventions
Example
Description<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>”. Example Example
Arrows separating the parts of a navigation path, for example, menu optionsExample
Emphasized words or expressionsExample
Words or characters that you enter in the system exactly as they appear in the documentationhttp://www.sap.com
Textual cross-references to an internet address/example
Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web123456
Hyperlink to an SAP Note, for example, SAP Note 123456Example2x� µm
Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. 2x� µm
Cross-references to other documentation or published worksExample2x� µm
Output on the screen following a user action, for example, messages2x� µm
Source code or syntax quoted directly from a program2x� µm
File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database toolsEXAMPLE
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 INCLUDEEXAMPLE
Keys on the keyboard
52/54 PUBLIC 2013-08-13

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 2013 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.
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. National product specifications may vary.
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.
SAP 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.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.
Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides
2013-08-13 PUBLIC 53/54

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com © Copyright 2013 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 7 2013 landscape implementation

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Planning guide sap business suite 7 2013 landscape implementation

Similar to Planning guide sap business suite 7 2013 landscape implementation (20)

Recently uploaded

Recently uploaded (20)

Planning guide sap business suite 7 2013 landscape implementation