service.sap.com/instguides strongly recommend that you use the documents available here. The guides are regularly updated. Recommendation The business scenarios that are presented

■

■

© Copyright 2015 SAP AG. All rights reserved.

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

any purpose without the express permission of SAP AG. The information

contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain

proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of

Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5,

System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries,

zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390

Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter,

System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,

OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity,

Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or

registered trademarks of Adobe Systems Incorporated in the United States and/or

other countries.

Oracle is a registered trademark of Oracle Corporation.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and

MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of

W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license

for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet,

PartnerEdge, ByDesign, SAP Business ByDesign, and

other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered

trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and service

names mentioned are the trademarks of their respective

companies. Data contained in this document serves

informational purposes only. National product

specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes

only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

Disclaimer

Some components of this product are based on Java™.

Any code change in these components may cause

unpredictable and severe malfunctions and is therefore

expressively prohibited, as is any decompilation of these

components.

Any Java™ Source Code delivered with this product is

only to be used by SAP’s Support Services and may not

be modified or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet

address:

service.sap.com/instguides

.

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

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

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

<Example

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

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such

as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Upgrade Master Guide for SAP LT 2.0 and SAP TDMS 4.0

4 July 2015

History of Changes

The Upgrade Master Guide is regularly updated on SAP Service Marketplace at the Internet

address http://service.sap.com/instguides.

Make sure you have the latest version of the Upgrade Master Guide by checking SAP Service Marketplace immediately before starting the upgrade.

The following table provides an overview of the most important changes that were made in the latest versions.

Upgrade Master Guide Version Important Changes

1.0 30-September-2011 First version

1.1 10-October-2011 Addition of TDMS-specific content

1.2. 25-October-2011 Reviewed version

1.3 21-March-2013 Updates to reflect SAP Landscape Transformation Version 2 Support Package 04, TDMS 4.0 Support Package 04

1.4 08-August-2013 Updates to reflect SAP Landscape Transformation Version 2 Support Package 05, TDMS 4.0 Support Package 05

1.5 29-January-2014 Updates to reflect SAP Landscape Transformation Version 2 Support Package 06, TDMS 4.0 Support Package 06

1.6 08-July-2014 Updates to reflect SAP Landscape Transformation Version 2 Support Package 07, TDMS 4.0 Support Package 07

1.7 21-January-2015 Updates to reflect SAP Landscape Transformation Version 2 Support Package 08, TDMS 4.0 Support Package 08

1.8 28-July-2015 Updates to reflect SAP Landscape Transformation Version 2 Support Package 08, TDMS 4.0 Support Package 09


July 2015 5

Table of Contents

History of Changes ................................................................................ 4

1 Getting Started .............................................................................. 7

1.1 About this Document ....................................................................... 7

1.2 Related Information ......................................................................... 8

1.2.1 Planning Information .......................................................................... 8

1.2.2 Further Useful Links ........................................................................... 8

1.3 Important SAP Notes ..................................................................... 10

2 SAP LT 2.0 and SAP TDMS 4.0 Upgrade Overview ................... 12

2.1 Scope of the Applications ............................................................. 12

2.2 Upgrade at a Glance ...................................................................... 17

2.3 Upgrade Paths ................................................................................ 18

2.4 Upgrade of Involved Software Components ............................... 20

2.6 System Landscape ......................................................................... 21

3 Application-Wide Topics ............................................................ 26

3.1 SAP Solution Manager ................................................................... 26

3.2 Upgrade Impact on Custom Changes Done in SAP TDMS 3.0 .. 26

3.3 Activities before the Upgrade ....................................................... 27

3.4 Running the Upgrade ..................................................................... 27

3.5 Post-Upgrade Activities ................................................................. 28

4 References ................................................................................... 29

The Main SAP Documentation Types ........................................... 30


6 July 2015

List of Figures

Figure 1: Upgrade at a Glance for SAP LT 2.0 ....................................................................... 17

Figure 2: Upgrade at a Glance for SAP TDMS 4.0 ................................................................. 18

Figure 3 : Upgrade path for DMIS 2011 .................................................................................. 18

Figure 4 : Consolidation of Software Components in SAP TDMS 4.0 .................................... 19

Figure 5 : Upgrade path from DMIS_CNT 2006...................................................................... 19

Figure 6 : Upgrade Path from DMIS_BSC 2008 ..................................................................... 19

Figure 7 : Upgrade Path from DMIS_HR 2008 ....................................................................... 20

Figure 8 : SAP Landscape Transformation work center ......................................................... 20

Figure 9 : SAP Landscape Transformation roadmap .............................................................. 20

Figure 10 : Roadmap chapter Business Blueprint and Mapping............................................. 21

Figure 11 : Overview of System Landscape for SAP LT ......................................................... 22

Figure 12 : Landscape with Control (Solution Manager) and Execution System .................... 22

Figure 13 : Landscape for Client Transfer without Upgrade ................................................... 22

Figure 14 : Landscape for Client Transfer with Upgrade ........................................................ 23

Figure 15 : Overview of System Landscape for SAP TDMS ................................................... 24

Figure 16 : Running the Upgrade ............................................................................................ 28

1 Getting Started

7 October 2011

1 Getting Started This document describes the software upgrade for SAP Test Data Migration Server 4.0 (SAP TDMS 4.0) and for SAP Landscape Transformation 2.0 (SAP LT 2.0). The involved software components for the new release are

SAP TDMS 4.0 – DMIS 2011 and DMIS_CNT 2011

SAP LT 2.0 – DMIS 2011 and SHC_CONT 2011

The relevant notes for performing the upgrade are:

SAP Note 1577441 Installation und Delta-Upgrade of DMIS 2011_1

SAP Note 1577442 Installation und Delta-Upgrade of DMIS_CNT 2011_1

SAP Note 1487845 Release strategy SAP LT (Add-On: SHC_CONT, DMIS)

In this document you find more information about what to do before or after an upgrade.

1.1 About this Document Purpose

This Upgrade Master Guide provides a central starting point for the technical upgrade of SAP Landscape Transformation 2.0 and SAP Test Data Migration Server 4.0. You can find cross-scenario upgrade information as well as scenario-specific information in this guide.

The central starting point for the technical implementation of your SAP application/solution is the Master Guide, which you can find on SAP Service Marketplace at http://service.sap.com/instguides.

Use the Upgrade Master Guide to get an overview of the upgrade paths, the upgrade of the involved software units and scenarios from a technical perspective. The Upgrade Master Guide is a planning tool that helps you to decide what software units you have to upgrade taking into account the dependencies between the software units. It refers you to the required detailed documentation, mainly:

Upgrade notes for single software units

SAP Notes

Configuration documentation

SAP Library documentation

For a general overview of available SAP documentation, see The Main SAP Documentation Types.

You can find the most current information about the technical upgrade of SAP Landscape Transformation 2.0 and SAP Test Data Migration Server 4.0 along with the latest upgrade, installation and configuration guides on SAP Service Marketplace at http://service.sap.com/instguides.

We strongly recommend that you use the documents available here. The guides are regularly updated.

Recommendation

The business scenarios that are presented here serve as examples of how you can use SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Ensure to check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

Out of Scope

This Upgrade Master Guide primarily discusses the overall technical upgrade of SAP Landscape Transformation 2.0 and SAP Test Data Migration Server 4.0, and not their subordinate

1 Getting Started

8 July 2015

components. This means, that additional software dependencies may exist without being mentioned explicitly in this document. You can find more information about component-specific software dependencies in the corresponding upgrade guides.

1.2 Related Information

1.2.1 Planning Information For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace.

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade guides

http://service.sap.com/instguides

SAP Upgrade Info Center - general information about upgrade topics and application-specific upgrade information

http://service.sap.com/upgrade

General information about SAP Landscape Transformation 2.0

http://service.sap.com/saplt

General information about SAP Test Data Migration Server

http://service.sap.com/tdms

SAP Business Maps - information about applications and business scenarios

http://service.sap.com/businessmaps

Sizing, calculation of hardware requirements - such as CPU, disk and memory resource

http://service.sap.com/sizing

Released platforms and technology-related topics such as maintenance strategies and language support

http://service.sap.com/platforms

To access the Platform Availability Matrix directly, enter http://service.sap.com/pam.

Network security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

Performance http://service.sap.com/performance

Information about Support Package Stacks, latest software versions and patch level requirements

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

Information about Unicode technology http://www.sdn.sap.com/irj/sdn/i18n

1.2.2 Further Useful Links The following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Information about creating error messages http://service.sap.com/messages

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (software download and ordering of software)

http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learning Maps

http://service.sap.com/rkt

http://service.sap.com/saplt

http://service.sap.com/tdms

1 Getting Started

July 2015 9

1 Getting Started

10 July 2015

1.3 Important SAP Notes

Read the following SAP Notes before you start the upgrade. These SAP Notes contain the most recent information about the upgrade, as well as corrections to the upgrade documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at

http://service.sap.com/notes.

SAP Note Number Title Description

1577442 Installation/Upgrade DMIS_CNT 2011_1 on NW 7.xy / ERP 6.0

SAP TDMS Installation Note

1577441 Installation/Upgrade DMIS 2011_1 on NW 7.xy / ERP 6.0

SAP TDMS Installation Note

1577504 Upgrade to NW 7.xy / ERP 6.0 with DMIS_CNT 2011_1

SAP TDMS Upgrade Note

1577503 Upgrade to NW 7.xy / ERP 6.0 with DMIS 2011_1

SAP TDMS Upgrade Note

1487845 Release strategy SAP LT (Add-On: SHC_CONT, DMIS)

Info about release strategy

1639232 Add. info about the upgrade to DMIS 2011

Additional information about

the upgrade to DMIS 2011

1632914 SAP TDMS 4.0 : Release Information Note(RIN)

Contains release information for SAP TDMS.

1616211 TDMS 4.0 corrections: Composite Note for TDMS CRM U

Contains the prerequisites and a list of all notes to be applied for the CRM for Utilities solution in SAP TDMS.

1610608 TDMS 4.0 corrections: Composite SAP Note for TDMS SCM

Contains the prerequisites and a list of all notes to be applied in SAP TDMS for SAP SCM.

1613646 TDMS 4.0 corrections: Composite SAP Note for TDMS SRM

Contains the prerequisites and a list of all notes to be applied in SAP TDMS for SAP SRM.

1611674 TDMS 4.0 Composite Note: IS Retail Contains the prerequisites and a list of all notes to be applied for the SAP Retail solution in SAP TDMS.

1611609 TDMS 4.0 - Composite Note For IS Oil & Gas

Contains the prerequisites and a list of all notes to be applied for the SAP Oil & Gas (Downstream) solution in SAP TDMS.

1608754 TDMS 4.0 - Composite Note For IS Utilities

Contains the prerequisites and a list of all notes to be applied for the SAP Utilities solution in SAP TDMS.

1606467 TDMS 4.0 - Composite Note For Banking

Contains the prerequisites and a list of all notes to be applied for the SAP Banking

http://service.sap.com/notes

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














1 Getting Started

July 2015 11

solution in SAP TDMS.

1619059 TDMS HCM Composite Note TDMS HCM Composite Note


2 SAP LT 2.0 and SAP TDMS 4.0 Upgrade Overview

12 July 2015


2.1 Scope of the Applications SAP Landscape Transformation 2.0

SAP Landscape Transformation helps you to make individual transformation projects.

The capabilities in SAP LT 2.0 are:

Company Carve-Out (See details in SAP Note 1462004)

• Transformation covers master data, transaction data, and Customizing data.

• The transformation solution Company Carve-Out (Company Code Deletion) covers the deletion parts in the project.

• It ensures that irrelevant data is deleted, that relevant data (SAP and customer-specific data) is kept, and that the systems remain intact.

Company Code Merge (See details in SAP Note 1589619)


• The participating company codes are merged.

• The descriptions (texts) for company codes can be changed during the conversion.

• It is possible to harmonize CO master data (cost centers and profit centers) by including a related merge or rename functionality.

Controlling Area Merge (See details in SAP Note 1589622)


• The participating controlling areas are merged.

• Controlling Area Merge includes Profit Center Merge and Cost Center Merge.

• The descriptions (texts) for business process, activity types, cost centers, profit centers and controlling areas can be changed during the conversion.

• It is possible to harmonize CO master data (cost centers and profit centers) by including a related merge or rename functionality.

Profit Center Reorganization (See details in SAP Note 1534197)


• Changes the assignment of profit centers to objects (such as material, orders, purchase orders and sales orders) on a key date in the future (start of period). Available scenarios: Merge, Split, Change of Profit Centers.

• Reassigned objects have their balances transferred in the new General Ledger Accounting. All steps are logged and are therefore verifiable.

• Performs the reorganization process in a well defined process using a role based UI in a single point of administration which allows you to involve all related parties.

• Profit center reporting can be performed consistently in the new General Ledger Accounting both before and after the profit center assignment is changed.

Chart of Accounts Conversion (See details in SAP Note 1461700)


• Chart of Accounts can be renamed, restructured, and merged.

• The descriptions (texts) for accounts, chart of accounts can be changed during the conversion.

http://service.sap.com/sap/support/notes/1462004






July 2015 13

• Accounts and cost elements can be converted 1:1 or n:1 (merge), but splitting is not possible.

• Mapping checks, log with messages classified according to severity.

• Related structures such as P&L structure, balance sheet structure, and account groups are checked.

Asset Class Conversion (See details in SAP Note 1589573)


• The descriptions (texts) for asset classes can be changed during the conversion.

• It is possible to rename asset classes (1:1 relation).

• It is possible to merge asset classes (n:1 relation).

Conversion of Asset Account Determination (See details in SAP Note1589574)


• The descriptions (texts) for asset account determination can be changed during the conversion.

• It is possible to rename asset account determinations (1:1 relation).

• It is possible to merge asset account determinations (n:1 relation).

Fiscal Year Conversion (See details in SAP Note 1591805)


• All fiscal years – including past ones – are reduced by one during the fiscal year conversion.

• Reduction of fiscal years by two or increasing the fiscal year by one is also possible.

• A fiscal year conversion can be done either for all company codes in a client or only for selected ones (if all of them use the same fiscal year variant).

Company Code Rename (See details in SAP Note 1589618)


• You can rename company codes (1:1 relationship).

• The descriptions (texts) for company codes can be changed during the conversion.

• A swap of company codes is also possible.

• Example: old company code 0001 will become 0002, while old company code 0002 will become 0003 or old company code 0001.

Controlling Area Rename (See details in SAP Note 1589620)


• You can rename controlling areas (1:1 relationship).

• The descriptions (texts) for controlling areas can be changed during the conversion.

• A swap of controlling areas is also possible. Example: old controlling area 0001 will become 0002, while old controlling area 0002 will become 0003 or old controlling area 0001.

Profit Center Conversion (See details in SAP Note 1589675)


• It is possible to rename profit centers (1:1 relation). Example: Profit center 1000 becomes 2222.

• It is possible to merge profit centers (n:1 relation). Example: Profit centers 1000 and 2000 are merged into a new, joint profit center 3000.

• The descriptions (texts) for profit centers can be changed during the conversion.

• Profit centers can be changed differently in each controlling area.

Cost Center Conversion (See details in SAP Note 1589673)










14 July 2015

• It is possible to rename cost centers (1:1 relation). Example: Cost center 12345678 becomes 23456789.

• It is possible to merge cost centers (n:1 relation). Example: Cost centers 1234567 and 2345678 are merged into a new, joint cost center 1234567.

• The descriptions (texts) for cost centers can be changed during the conversion.

• Cost centers can be changed differently in each controlling area.

Customer Number Conversion (See details in SAP Note 1591808)


• It is possible to rename customer numbers (1:1 relation).

• It is possible to merge customer numbers (n:1 relation).

• You can also move a complete set of customer numbers from one number range to another (predefined rule).

• A combination of predefined rules and individual mapping assignments is possible.

Vendor Number Conversion (See details in SAP Note 1591809)


• It is possible to rename vendor numbers (1:1 relation).

• It is possible to merge vendor numbers (n:1 relation).

• You can also move a complete set of customer numbers from one number range to another (predefined rule).

• A combination of predefined rules and individual mapping assignments is possible.

Material Number Rename (See details in SAP Note 1591807)


• It is possible to rename material numbers (1:1 relation).

• The descriptions (texts) for material numbers can be changed during the conversion.

• You can also move a complete set of material numbers from one number range to another (predefined rule).

• You can convert material numbers to lexicographical display.

• A combination of predefined rules or change to lexicographical display and individual mapping assignments is possible.

SAP ERP HCM System Integration (see details in SAP Note 1830766)

• Integrate your SAP HCM solution into your SAP ERP system (for example in order to simplify your system landscape).

• Transfer HCM data by selecting the relevant HCM tables (an HCM knowledge base is available to identify HCM tables).

SAP ERP HCM System Merge (see details in SAP Note 1830766)

• Merge one or more SAP HCM systems into an existing one.


• Data conversions are typically required.

SAP ERP HCM System Carve-Out (with Different Releases / with Matching Releases- see details in SAP Note 1830766)

• Move your SAP HCM solution from a central SAP ERP system to an empty standalone SAP HCM system

• Transfer HCM data by selecting the relevant HCM tables (an HCM knowledge base is available to identify HCM tables)

• Integrated upgrade is possible








July 2015 15

SAP ERP HCM System Split (with Different Releases / with Matching Releases - see details in SAP Note 1830766)

• Move a subset of SAP ERP HCM data (for example, only certain employee IDs or all employees of a determined organizational unit) from a source system to a target system.


• Integrated upgrade is possible.

SAP ERP HCM Data Deletion (see details in SAP Note 1830768)

• Delete HCM data in the sender system (for example after a HCM Carve-Out or HCM Split).

• You can choose to delete all the HCM tables that were migrated in a previously executed SAP LT HCM transformation project, or adjust the selection.

Client Transfer (See details in SAP Note 1462006 )


• High speed transfer of clients from one or more sender system to a single receiver system (to create a multi-client system).

• Transfer across releases, and from non-Unicode to Unicode is possible (transfer, upgrade, and Unicode conversion within one project).

• NO client merge.

• NO business harmonization.

• Database update is done table by table and can be rolled back in case of errors.

• Go-live can be realized on any weekend, is not related to a key date.

Shell Creation (See details in SAP Note 2030760)

• Create a copy of a system that has a considerably reduced data volume.

• By default, the complete client 000 is copied. Other clients can also be included.

• Any included clients in the new shell system will be exact copies of the original system clients.

• Typically, the new shell system is used as a receiver system for different transformation solutions.

SAP Test Data Migration Server 4.0

SAP Test Data Migration Server (SAP TDMS) is a high-speed data extraction tool that populates the development, test, quality assurance, and training systems with SAP business data from the production environment

SAP TDMS is available for the following applications:

Business Suite

SAP ERP

SAP ERP HCM

SAP CRM

SAP SCM

SAP SRM

Industry Solutions

AFS

Banking (Loans and Deposits)

Oil & Gas (Downstream)







16 July 2015

Utilities

CRM for Utilities

Healthcare

DIMP

Retail

Other

SAP NetWeaver BW

SAP GTS

For more information, see SAP Note 1620121.

Note: Since the software component DMIS 2011 is required for both SAP TDMS 4.0 and SAP LT 2.0, a system in which both these SAP products are in use, an upgrade to TDMS 4.0 will require an upgrade to SAP LT 2.0 and vice versa. Hence, if you are using both SAP LT and SAP TDMS together in a system you have to plan both the upgrade simultaneously.


July 2015 17

2.2 Upgrade at a Glance

SAP Landscape Transformation 2.0

Figure 1: Upgrade at a Glance for SAP LT 2.0

SAP LT 2.0 also includes the functions of SAP LT 1.0.


18 July 2015


Figure 2: Upgrade at a Glance for SAP TDMS 4.0

SAP TDMS 4.0 also includes the features stated under SAP TDMS 3.0 in the above diagram.

2.3 Upgrade Paths

This section describes the upgrade path for the software components DMIS 2011 and DMIS_CNT 2011. While SAP TDMS requires both the components DMIS and DMIS_CNT, SAP LT requires only DMIS.


SAP LT 2.0 is the successor release of SAP LT 1.0.

The software component DMIS is required for both SAP LT 2.0 and SAP TDMS 4.0. Here is an overview of all existing DMIS releases and their upgrade paths to DMIS 2011:

Figure 3 : Upgrade path for DMIS 2011

You can upgrade from both DMIS 2006 and DMIS 2010 to DMIS 2011 in a one step upgrade.


With SAP TDMS 4.0, the underlying software components have been consolidated in comparison to the previous release as shown below.


July 2015 19

Figure 4 : Consolidation of Software Components in SAP TDMS 4.0

(Note : Component DMIS_EXT is NOT technically integrated into the new DMIS_CNT component – the component DMIS_EXT will remain in the system even after an upgrade has been performed. Form a functional perspective – all functions covered by DMIS_EXT are completely covered by the new DMIS_CNT component version)

The software component DMIS is required for both SAP LT 2.0 and SAP TDMS 4.0. The upgrade path for DMIS 2011 is illustrated in figure 3.

For SAP TDMS 4.0, after upgrading to DMIS 2011 you have to upgrade to DMIS_CNT 2011. The following is the overview of DMIS_CNT releases and their upgrade paths to DMIS_CNT 2011.

Upgrade Path if you have installed only DMIS_CNT 2006 and not DMIS_HR or DMIS_BSC:

Figure 5 : Upgrade path from DMIS_CNT 2006

Upgrade path overview if you have installed DMIS_BSC 2008 along with DMIS_CNT 2006:

Figure 6 : Upgrade Path from DMIS_BSC 2008

Upgrade path overview if you have installed DMIS_HR 2008 along with DMIS_CNT 2006:


20 July 2015

Figure 7 : Upgrade Path from DMIS_HR 2008

2.4 Upgrade of Involved Software Components SAP Landscape Transformation 2.0

For SAP LT 2.0, you can start the upgrade for DMIS 2011 and on your Solution Manager system you should install the add-on SHC_CONT, this provides a documentation of SAP LT 2.0 functions, processes and steps:

Figure 8 : SAP Landscape Transformation work center

Click the Display Roadmap pushbutton.

Figure 9 : SAP Landscape Transformation roadmap

Example: Business Blueprint and Mapping


July 2015 21

Figure 10 : Roadmap chapter Business Blueprint and Mapping

Here you have the functions of the Solution Manager to plan, setup and run your individual projects.

Note: Software component DMIS_CNT is not relevant for SAP LT

Software component SHC_CONT is not relevant for SAP TDMS


For SAP TDMS 4.0, you need to install the software components for DMIS 2011 and DMIS_CNT 2011 in all the systems participating in the data migration. Note that the support package levels of the add-ons need to be identical in all the participating systems.

2.6 System Landscape


The following diagram provides an overview of a possible landscape for SAP LT 2.0.

1. Control System and Execution System


22 July 2015

SAP LT - Control System(SAP Solution Manager – 7.0 or 7.1)

Execution Systems(Release 6.20 – 7.10)

SAP_BASIS

SAP_ABA

ST 400DMIS 2010

SHC_CONT

SAP_BASIS

SAP_ABA

DMIS 2010

SAP_BASIS

SAP_ABA

ST 400 (for 7.0)

ST 710 (for 7.1.)

DMIS 2011

SHC_CONT 2011

SAP_ABA

DMIS 2011

…

620 640 700* 710 730 731

DMIS 2011 2011_1_620 2011_1_640 2011_1_700 2011_1_710 2011_1_730 2011_1_731

SHC_CONT 2011 -- -- 2011_1_700 --

* Including all EHPs

Figure 11 : Overview of System Landscape for SAP LT

Solution

Manager /

Control

Execution

System

RFC Type:

DialogRFC Type:

Dialog

RFC Type:

Dialog

Figure 12 : Landscape with Control (Solution Manager) and Execution System

2. Landscape for Client Transfer without Upgrade

Solution

Manager /

Control

Sender

Central

Receiver

RFC Type:

Communication

Figure 13 : Landscape for Client Transfer without Upgrade

3. Landscape for Client Transfer with Upgrade


July 2015 23

Solution

Manager /

Control

Sender Central

Receiver Upgrade

RFC Type:

Communication

Figure 14 : Landscape for Client Transfer with Upgrade

For more information, see the Security Guide for SAP Landscape Transformation 2.0.


24 July 2015


The following diagram provides an overview of the typical system landscape for SAP TDMS 4.0:

Figure 15 : Overview of System Landscape for SAP TDMS

The sender and the receiver systems need to be of the same release level (SAP NW 620 or above)

The TDMS control system needs to be of SAP Basis release NW 7.0 or above as the new UI technology for TDMS Control Center requires SAP WebDynpro capabilities. In case, the control system for SAP TDMS 3.0 is of SAP Basis release is than NW 7.0, then perform either of the following two activities before you start the upgrade.

Upgrade the SAP NetWeaver release of the TDMS Control System to SAP NW 7.0 or above before you start the TDMS upgrade.

Migrate all the TDMS relevant data from the TDMS Control System to another system having SAP NetWeaver release 7.0 or above and make this as the new control system for TDMS. For more information about this procedure, contact SAP for support.

The following table lists the corresponding versions of DMIS 2011 and DMIS_CNT 2011 to be installed depending on the SAP NetWeaver release of the involved system.


July 2015 25

Full Upgrade Matrix for all Releases

The following matrix illustrates all upgrade paths that are possible (Y) or not possible (N):

DMIS

200

6

DMIS

201

0

DMIS

201

1

DMIS

_CNT

2006

DMIS

_CNT

2011

DMIS

_EXT

200

7

DMIS

_BSC

2008

DMIS

_HR 2

008

SHC_CONT 2

010

SHC_CONT 2

011

DMIS

_MOB 2

011

NMI_

CONT 200

6

CWB V

12

DMIS 2006 N N Y N Y Y Y N N N Y Y TDMS 3.0

DMIS 2010 N N Y N Y Y Y Y N Y Y N DMIS 2006

DMIS 2011 N N N Y Y N N N Y Y Y N or DMIS 2010

DMIS_CNT 2006 Y Y N N Y Y Y Y N Y Y Y DMIS_CNT 2006

DMIS_CNT 2011 N N Y N Y N N N Y Y Y N DMIS_EXT 2007 possibly

DMIS_EXT 2007 Y Y Y Y Y Y Y Y Y Y Y Y DMIS_BSC 2008 possibly

DMIS_BSC 2008 Y Y N Y N Y Y Y N Y Y Y DMIS_HR 2008 possibly

DMIS_HR 2008 Y Y N Y N Y Y Y N Y Y Y

SHC_CONT 2010 N Y N Y N Y Y Y N Y Y N TDMS 4.0

SHC_CONT 2011 N N Y N Y Y N N N Y Y N DMIS 2011

DMIS_MOB 2011 N Y Y Y Y Y Y Y Y Y Y N DMIS_CNT 2011

NMI_CONT 2006 Y Y Y Y Y Y Y Y Y Y Y Y DMIS_EXT 2007 possibly

CWB V12 Y N N Y N Y Y Y N N N Y

SAP LT V1

DMIS 2010

compatible Y SHC_CONT 2010

not compatible N

SAP LT V2

DMIS 2011

SHC_CONT 2011

GLM

DMIS 2006

or DMIS 2010

or DMIS 2011

NMI_CONT 2006

3 Application-Wide Topics

26 July 2015


3.1 SAP Solution Manager SAP provides the SAP Solution Manager as a highly recommended platform to efficiently support the implementation of your solution. Using SAP Solution Manager significantly accelerates the implementation process and helps you achieve your business goals. At the same time, SAP delivers Support Services based on the business scenarios designed and documented in SAP Solution Manager. Implementation content for your solution may further accelerate the implementation process. For information about availability of content specifically tailored to your solution, see SAP Service Marketplace at http://service.sap.com/solutionmanager. Caution In the installation or upgrade process, an SAP Solution Manager system is required to generate the SAP Solution Manager Key. Without the SAP Solution Manager Key, you cannot continue the installation process. The generation of the required key is implemented into the SAP Solution Manager as of Release 3.2 SP8. For details, see SAP Service Marketplace at http://service.sap.com/notes, SAP Note 811923.

3.2 Upgrade Impact on Custom Changes Done in SAP TDMS 3.0 The following is the summary of the common custom changes done in SAP TDMS 3.0 and their impact on the upgrade to SAP TDMS 4.0.

3.2.1. Inclusion of Custom Tables in Transfer and New Selection Groups Any customizing that you carried out to include custom tables to the SAP delivered customizing of SAP TDMS 3.0 will be available after the upgrade as well. If you have created new selection groups and added them to the customizing of SAP TDMS 3.0, then these selection groups would be available in the customizing after the upgrade as well.

Example: If you have included custom table ZSALESTYPE to be included in the TDMS reduction logic, by changing the customizing of the TDMS base package, then this change will be reflected after the upgrade to SAP TDMS 4.0 as well without any impact.

3.2.2. Modification of the Transfer Behavior of Tables in SAP-Delivered Customizing Any customizing that you carried out to change the transfer behavior of tables in the SAP delivered customizing of SAP TDMS 3.0 will be available after the upgrade as well.

Example: If you have change the transfer behavior of table KNB1 from ‘Full Transfer’ to ‘No Transfer’ by changing the customizing of the TDMS base package, then this change will be reflected after the upgrade to SAP TDMS 4.0 as well without any impact.

3.2.3. Impact on Custom Scrambling Rules SAP TDMS 4.0 has a new and improvised data scrambling platform in comparison to that of the previous release. Hence all custom scrambling rules that you created in SAP TDMS 3.0 cannot be directly used after the upgrade. You have to create the scrambling rules again in the new scrambling platform after the upgrade. Creation of scrambling rules include the following steps:

Definition of table sets and field sets to be scrambled

Creation of custom ABAP code that defines the scrambling logic

Note that all the SAP delivered scrambling content in SAP TDMS 3.0 including the country specific scrambling content for SAP ERP HCM data will be available for use in SAP TDMS 4.0 as well.


July 2015 27

For more information on data scrambling in SAP TDMS 4.0, read the how-to guide on data scrambling available in www.service.sap.com\instguides

3.2.4. Customizing in the Business Process Library for SAP TDMS (TDMS BPL) You have to manually transfer all customizing changes that you have done to the BPL scenario of SAP TDMS 3.0 after the upgrade to SAP TDMS 4.0. If you have done significant amount of customizing, you can contact the SLO consulting group of SAP to get support during the upgrade.

3.3 Activities before the Upgrade Before you start the upgrade, create a full backup of your system. For SAP TDMS, ensure that the custom scrambling rules, custom selection groups, any customizing done in TDMS BPL and other code changes done for TDMS are backed up before the start of upgrade.

Check if new SPs of the target release are published and include them in the current upgrade procedure.

Consult with your business users before you start an upgrade:

All running analyses and active conversion or migration packages have to be finished. Otherwise the upgrade is not possible.

For SAP LT 2.0, it is not mandatory to finish projects completely, however all steps and solutions that have already been created or started in a given project execution plan shall be completed before an upgrade is performed as the ability to complete the given steps consistently after an upgrade is not ensured. Instead we recommend to add new execution plan steps based on given project templates after an upgrade in order to repeat certain steps in a project. This will be handled by SAP LT content and this makes it possible that older versions of the content can be accessed.

For SAP TDMS 4.0, it will not be possible to continue with the projects created before the upgrade. Hence it is recommended that you complete all active migrations before the upgrade and create new migration projects after the upgrade.

3.4 Running the Upgrade

To enable a unified consumption experience across all SAP application products, it is planned that SAP Solution Manager Maintenance Optimizer automatically downloads the required software logistics tool together with the download of SAP application products.

http://www.service.sap.com/instguides


28 July 2015

Figure 16 : Running the Upgrade

3.5 Post-Upgrade Activities

After the upgrade run transaction SGEN to generate and activate the new load of the SAP system. This avoids compiling while you start the transactions at the first time.

Check if new SPs of the target release are published and install them if you did not include them during the upgrade.

Do not use old project templates from former releases for SAP LT 2.0. The old template itself changes to ‘warning’ if there is a new version of the template provided by the upgrade.

4 References

July 2015 29

4 References List of Documents

The following table lists all documents mentioned in this Upgrade Master Guide.

Title Where to Find

SAP TDMS 4.0 Master Guide service.sap.com/instguides

SAP TDMS 4.0 Solutions Operations Guide


SAP LT 2.0 Master Guide service.sap.com/instguides

SAP LT 2.0 Solution Operations Guide service.sap.com/instguides


The Main SAP Documentation Types

30 July 2015

The Main SAP Documentation Types The following is an overview of the most important documentation types that you need in the various phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

Configuration

DocumentationRelease Notes

Component

Installation Guide

Component

Upgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution Management

Guide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-phase documentation

SAPterm

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

Target group:

Relevant for all target groups

Current version:

Located in the SAP Help Portal at help.sap.com → Additional Information → Glossary (direct Access) or Terminology (available as terminology CD)

In the SAP-System in transaction STERM

SAP Library

The SAP Library is a collection of function- and process-oriented documentation for SAP components. The SAP Library also contains the Business Scenario Descriptions.

Target group:

Consultants

System administrators

Project teams for implementations or upgrades


July 2015 31

Current version:

Located in the SAP Help Portal at help.sap.com

Also located in the SAP Service Marketplace at service.sap.com/ibc (only the Business Scenario

Descriptions)

Implementation Guide (IMG)

The Implementation Guide is a tool for configuring the SAP system to meet customer requirements. Its structure and documentation are component-oriented.

Target group:

Solution consultants


Current version:

In the SAP menu of the SAP system under Tools Customizing IMG

Security Guide

The Security Guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for the SAP NetWeaver technologies like SAP Web Application Server (SAP Web AS). This document contains general guidelines and suggestions about system security. Other technologies and individual applications have a Security Guide of their own.

Target group:

Technology consultants



Current version:

Located in the SAP Service Marketplace at service.sap.com/securityguide

Implementation

Master Guide

The Master Guide is the starting point for implementing an SAP solution. It lists the required SAP components and third party applications that are required for each Business Scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also offers references to other documents, such as Component Installation Guides and SAP Notes.

Target group:



Project teams for implementations

Current version:

Located in the SAP Service Marketplace at service.sap.com/instguides


32 July 2015

Component Installation Guide

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

Target group:



Current version:


Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of its main functions being the configuration of SAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, as well as documentation. Instead of the configuration documentation in SAP Solution Manager, there may be separate Business Scenario Configuration Guides in the SAP Service Marketplace for earlier shipments of the Business Scenarios.

Target group:



Current version:

In SAP Solution Manager

Located in the SAP Service Marketplace at service.sap.com/ibc

Production operation

Solution Management Guide

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

Target group:





Current version:



July 2015 33

Upgrade

Upgrade Master Guide

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

Target group:


Project teams for upgrades

Current version:


Component Upgrade Guide

The Component Upgrade Guide describes the technical upgrade of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.

Target group:



Current version:


Release Notes

Release notes are documents that contain short descriptions of new features or changes in an SAP component since the previous release. Release notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs.

Target group:

Consultants


Current version:

Located in the SAP Service Marketplace at service.sap.com/releasenotes

In the SAP menu of the SAP system under Help Release information