ssm10 sem migration guide

Migration GuideSEM to SAP BusinessObjects Strategy Management 10.0 Series

Target Audience ■ Technology Consultants ■ System Administrators

PUBLICDocument version: 1.0 – 2011-06-16

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

2/24 PUBLIC 2011-06-16

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguidesEPM-STM

2011-06-16 PUBLIC 3/24

http://service.sap.com/instguidesEPM-STM

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>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://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 Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

4/24 PUBLIC 2011-06-16

http://www.sap.com

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version on SAP Service Marketplace http://service.sap.com/

instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.0 2011-06-16 First version – no changes.

2011-06-16 PUBLIC 5/24

http://service.sap.com/instguides

http://service.sap.com/instguides

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

1.2 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1 Setting Java System Properties in SAP NetWeaver . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 5 Migration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1 SEM and the Strategy Management Application Data Mapping . . . . . . . . . . . . 15

5.2 Importing SEM Data into the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6.1 Completing the Scorecard Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6.2 Completing the Initiatives Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

A.1 How Data Is Mapped from SEM to the Application . . . . . . . . . . . . . . . . . . . . . 19

6/24 PUBLIC 2011-06-16

1 Introduction

This Guide explains how to migrate your SEM balanced scorecard data into the SAP BusinessObjects

Strategy Management system.

Prerequisites

SEM balanced scorecard data is in SEM proprietary XML format as defined by SEM XML schema.

You have installed and configured the application.

1.1 About this Document

This document explains how to migrate your SEM application data to the application.

This document contains the following sections:

■ Planning

■ Preparation

■ Migration

■ Follow-Up Activities

1.2 Before You Start

1.2.1 Naming Conventions

In this documentation, the following naming conventions apply:

Variables Description

<nw_server>:<port> Server name or IP address and port where SAP NetWeaver is installed and strategy management application components are deployed

1 Introduction

1.1 About this Document

2011-06-16 PUBLIC 7/24

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

2 Quick Guide

This section includes a checklist with all actions you have to perform. The actions are in chronological

order, so that you can work through them like a checklist.

Checklist

Planning

☐ ■ Ensure that the SEM data file is in SEM proprietary XML format as defined by the SEM Export

XML schema.

☐ ■ Make sure that the application is installed and configured.

Preparation

☐ ■ In SAP NetWeaver Administrator, modify global properties used by the Transporter for SEM

importing.

Upgrade Process

☐ ■ In the strategy management Transporter tool, import the SEM data file into the strategy

management database.

Follow-Up Activities

☐ ■ In the administration application, update the imported SEM contexts.

☐ ■ In the application, update the imported initiatives.

2 Quick Guide

2011-06-16 PUBLIC 9/24

3 Planning

SEM to the Application Data Mapping

The import function in the strategy management Transporter tool only maps SEM data that has a

counterpart in the application. Default values may be assigned if the data is not contained in the SEM

data file but is required by the administration application.

The original SEM data file and the data that is not mapped or imported are stored in the SAP NetWeaver

System database for the application for auditing purposes.

For more information, see How Data Is Mapped from SEM to the Application [page 19].

Ensuring the SEM Data File Format

Before you can import SEM data into the SAP NetWeaver System database for the strategy management

application, you must make sure the SEM data file is in SEM proprietary XML format as defined by the

SEM Export XML schema.

Installed and Configured Strategy Management Application

You have a fully functioning strategy management application running.

3 Planning

2011-06-16 PUBLIC 11/24

4 Preparation

4.1 Setting Java System Properties in SAP NetWeaver

Strategy management definitions are stored in tables in the SAP NetWeaver System Database. This topic

explains how to set the following Java System Properties in SAP NetWeaver Administrator to prepare

for the SEM migration:

■ Specify the name of the table in the SAP NetWeaver System Database where you want to store the

SEM data.

■ Define an initial role containing the administrator user for your first access into the SEM context

in the administration application.

■ Define the tabs available to the initial application group.

Prerequisites

You are an administrator of SAP NetWeaver.

Procedure

1. Start the SAP NetWeaver Administrator and log on as administrator.

2. Click Configuration.

3. Click the Infrastructure tab.

4. Select Java System Properties.

5. In the Templates section, select the template that corresponds to your strategy management

installation.

6. Click the Applications tab.

7. Filter on strategy to find the strategy management application.

8. Select the name xapps~cpm~sm~strategymanagement.

9. In the Extended Details section, click inside the Name text box and type the property you want to

modify. Then specify the value. The table below shows the properties, description, and values.

Java System Property Description

sem.dbname Specify the default data namespace for the SEM import. The default value is sem.

dataload.group.defaultPermissions Enter a 1 to enable a permission and enter a 0 to disable a permission.Default values are:CreateInitiative=1,

CreateComment=0,

CreateContext=0,

CreateStrategy=0,

4 Preparation


2011-06-16 PUBLIC 13/24

Java System Property DescriptionCreateScorecard=0,

To perform post-import configuration steps in the administration application, the user doing the import must be the strategy management administrator.For information about these strategy management permissions, see the Installation Guide on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Actions For Roles.

sem.appgroup.name Specify sem, which is the default name of the role.This creates a role in the administration application named sem. Initially, the user who imports the data (the strategy management administrator) is a member of this role.

sem.appgroup.tabs Specifies the application tabs available to the sem role.Specify a 1 to enable a tab and enter a 0 to make the tab unavailable.Default values are:ViewHome=1,

ViewStrategy=1,

ViewInitiatives=1,

ViewScorecard=1

PwDatabase sem

10. When you return to the Extended Details section, save your changes.

4 Preparation


14/24 PUBLIC 2011-06-16



5 Migration Process

5.1 SEM and the Strategy Management Application Data Mapping

The import function in the strategy management Transporter tool only maps SEM data that has a

counterpart in the application. Default values may be assigned if the data is not contained in the SEM

data file but is required by the administration application.

The original SEM data file and the data that is not mapped or imported are stored in the SAP NetWeaver

System database for the application for auditing purposes.

The following table shows a summary of the mapped items.

SEM Item Mapped to this Application Item

Hierarchy node Context

PerspectiveRef/Global Perspective Perspective

ObjectiveRef/Global Objective Objective

MeasureRef/Global Measure KPI

Initiative Initiative

Milestone Milestone

PerspectiveList (global) Library perspectives

ObjectiveList (global) Library objectives

MeasureList (global) Library KPIs

For more information, see How Data Is Mapped from SEM to the Application [page 19].

5.2 Importing SEM Data into the Application

The application installation includes a Transporter utility to import and export business-related data

objects between system instances. Use the Transporter tool to import your SEM data into the SAP

NetWeaver system database for the application. All application objects created in SEM are saved in

records in the SAP NetWeaver System Database.

Prerequisites

You have completed the tasks in the Planning and Preparation sections of this Guide.

You are a strategy management administrator.

5 Migration Process

5.1 SEM and the Strategy Management Application Data Mapping

2011-06-16 PUBLIC 15/24

Procedure

1. Start the Tools page by typing the following URL in a Web browser:

http://<nw_server>:<port>/strategy/tools

2. Click Transporter.

3. In the section for performing an SEM transport, browse for the SEM transport file and click Import

Into Database.

5 Migration Process

5.2 Importing SEM Data into the Application

16/24 PUBLIC 2011-06-16

6 Follow-Up Activities

6.1 Completing the Scorecard Definitions

Use the administration application to add the information not provided in the import that is required

to use the context in the application.

(Required) Initially, the sem role contains only the user who imported the SEM data. This user is the

strategy management administrator.

To add other users to the sem role, use SAP NetWeaver Administrator. For information, see the Installation

Guide on SAP Service Marketplace at http://service.sap.com/instguidesEPM-STM. Then choose Users

and Roles.

Appendix A shows all the items that are imported.

Prerequisites

You have imported SEM data into the SAP NetWeaver System database for the application.

You are the strategy management administrator.

Procedure

1. Start the administration application and log on as the administrator if you are prompted.

http://<nw_server>:<port>/strategy/administration

2. SEM global perspectives, objectives and measures are mapped to strategy management library

perspectives, objectives, and KPIs respectively.

Update the library perspectives, objectives, and KPIs as necessary.

3. Use Context Management Manage Contexts to add information to your imported contexts as

needed, such as specifying the model connection for each imported context.

4. Use Context Management Manage Scorecards Scorecard Defaults to update the scorecard defaults as

needed.

5. Use Context Management Manage Scorecards Define Scorecards to edit each imported KPI and do the

following:

■ Add index values and trend values.

■ Select the measure from the dimensional model that contains actual values for the imported

KPI. The remaining drop-down list boxes are automatically populated with the correct

measures.

■ Add other information as needed.

6. Use Context Management Manage Scorecards Define Scorecards to select each imported objective

and then make sure the following is defined:


6.1 Completing the Scorecard Definitions

2011-06-16 PUBLIC 17/24


The KPI associations for this objective.

The SEM calculation method is imported and mapped as follows:

SEM Strategy Management Application

Average Arithmetic average

Best case Greatest value

Worst case Least value

Others Ignore

7. Use Context Management Manage Scorecards Define Scorecards to select each imported perspective

and then make sure the imported perspectives and add other information as needed.

6.2 Completing the Initiatives Definitions

Use the application to add the information not provided in the import that is required to complete the

initiatives definitions.

Appendix A shows all the items that are imported, ignored, and missing but required.

Prerequisites

You have imported SEM data into the SAP NetWeaver System database for the application.

Your role has access to the Initiatives tab.

Procedure

1. Start the application and log on if you are prompted.

2. Select the Initiatives tab. Select each initiative, edit it, and do the following:

■ Change the default role from sem to a more applicable one.

■ Change the author or owner from the user who performed the import to a more applicable

one.

■ Update the initiative definitions as needed.

3. Select each milestone and submilestone, edit it, and do the following:

■ Change the Start Date to the actual milestone start date rather than the initiative start date.

■ Change the author from the user who performed the import to a more applicable one.

■ Update the milestone definitions as needed.

4. Go to the Scorecard tab to display the imported objectives and perspectives and KPIs.

For information about using the applications, see SAP Library for SAP BusinessObjects Strategy

Management at http://help.sap.com/epm Strategy Management SAP BusinessObjects Strategy

Management . Choose Application Help.


6.2 Completing the Initiatives Definitions

18/24 PUBLIC 2011-06-16

http://help.sap.com/epm

A Appendix

A.1 How Data Is Mapped from SEM to the Application

This table shows the items that are imported. You need to access the administration application to

further define imported items.

Top-Level Summary

SEM Items Mapped to this Strategy Management Item:

Hierarchy Ignored

Hierarchy node ContextSee table below for more details.

Scorecard ScorecardSee table below for more details.

PerspectiveRef/Global Perspective PerspectiveSee table below for more details.

ObjectiveRef/Global Objective ObjectiveSee table below for more details.

MeasureRef/Global Measure KPISee table below for more details.

Initiative InitiativeSee table below for more details.

Milestone MilestoneSee table below for more details.

StatusList Ignored

StategyList Ignored

PerspectiveList (global) Library perspectives

ObjectiveList (global) Library objectives

MeasureList (global) Library KPIs

Mapping Details for Hierarchy Node


Attributes

Id If the current SEM hierarchy node is empty (no scorecard), the node is mapped to an empty strategy management context. In this case, the Id attribute is mapped to the strategy management context name. This attribute is ignored if the hierarchy node is not empty.An empty context may be deleted by user manually in a later phase of the migration process.

Text Ignored

A Appendix


2011-06-16 PUBLIC 19/24


ScorecardId (see details for Scorecard)

Scorecard

Owner Ignored

Owner Text Ignored

Nested level Indent level of context

Mapping Details for Scorecard


Attributes

Id Ignored

Owner Ignored

OwnerText Ignored

StatGen Ignored

StatCalc Ignored

Text Name

Period Ignored

Child Elements

PerspectiveRefs (see details for PerspectiveRef) Perspectives

StrategyRef Ignored

CauseAndEffectList Ignored

Mapping Details for PerspectiveRef/Global Perspective


Attributes

Id Ignored

(Global Perspective) Text Name

OwnerText Ignored

StatGen Ignored

StatCalc Ignored

Weight Name

Child Elements

(Global Perspective) Description Description

ObjectiveRefs (see details for ObjectiveRef) Objectives

Mapping Details for ObjectiveRef/Global Objective


Attributes

Id Ignored

(Global Perspective) Text Name

OwnerText Ignored

StatGen Ignored

A Appendix


20/24 PUBLIC 2011-06-16


StatCalc ■ Average (measures) ■ Best case (measures) ■ Worst case (measures) ■ Others

Aggregation method ■ Arithmetic average ■ Greatest value ■ Least value ■ Ignored

Child Elements


MeasureRefs (see details for MeasureRef) KPIs

Initiatives (see details for Initiative) Initiatives

Values that are not in the import that are required by the strategy management application:

■ UseScorecard: 1

■ UseStratplan: 1

■ IndexValue: 1-2-3-4-5

Mapping Details for MeasureRef/Global Measure


Attributes

Id Ignored

Global Text Name

Owner Ignored

OwnerText Ignored

StatGen Ignored

Weight Ignored

ValueFieldList Ignored

GraphicsList Ignored

Child Elements



■ TypeId: 3

■ IndexVal (performance): 1-2-3-4

■ IndexVal (trend): 1-2

Mapping Details for Initiative


Attributes

Id Ignored

Text Name

Owner Ignored

OwnerText Ignored

A Appendix


2011-06-16 PUBLIC 21/24


StatGen Ignored

Weight Ignored

DurationFrom StartDate

DurationTo TargetEndDate

Priority Ignored

Child Elements

MilestoneList (see details for Milestone) Milestones

TeamMemberList Ignored


■ Role: default is sem

■ Author: user who starts the import session

■ Owner: user who starts the import session

NOTE

The objective-initiative relationship in SEM import is also preserved.

Mapping Details for Milestone


Attributes

Text Name

Description Description

DueDate TargetEndDate

EndDate ActualEndDate


■ StartDate: SEM initiative StartDate

■ Author: user who starts the import session

A Appendix


22/24 PUBLIC 2011-06-16

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

ssm10 sem migration guide

Documents