Upgrade Master Guide

SAP xApp Resource

and Portfolio
Management (xRPM)
4.0 powered by SAP
NetWeaver™
Document Version 1.40 – July, 2007
 SAP AG
Neurottstraße 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com

© Copyright 2005 SAP AG. All rights reserved. product and service names mentioned are the trademarks
of their respective companies. Data contained in this
No part of this publication may be reproduced or transmitted in any form document serves informational purposes only. National
or for any purpose without the express permission of SAP AG. The product specifications may vary.
information contained herein may be changed without prior notice.
These materials are subject to change without notice.
Some software products marketed by SAP AG and its distributors contain These materials are provided by SAP AG and its affiliated
proprietary software components of other software vendors. companies ("SAP Group") for informational purposes
only, without representation or warranty of any kind, and
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks SAP Group shall not be liable for errors or omissions with
of Microsoft Corporation. respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, the express warranty statements accompanying such
AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, products and services, if any. Nothing herein should be
z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix construed as constituting an additional warranty.
are trademarks or registered trademarks of IBM Corporation in the
United States and/or other countries.
Disclaimer
Oracle is a registered trademark of Oracle Corporation. Some components of this product are based on Java™.
Any code change in these components may cause
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open unpredictable and severe malfunctions and is therefore
Group. expressively prohibited, as is any decompilation of these
components.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks of Any Java™ Source Code delivered with this product is
Citrix Systems, Inc. only to be used by SAP’s Support Services and may not
be modified or altered in any way.
HTML, XML, XHTML and W3C are trademarks or registered
trademarks of W3C®, World Wide Web Consortium, Massachusetts SAP Library document classification: PUBLIC
Institute of Technology.
Documentation in the SAP Service Marketplace
Java is a registered trademark of Sun Microsystems, Inc. You can find this documentation at the following address:
http://service.sap.com/ instguides

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

under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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
Typographic Conventions Icons

Type Style Represents Icon Meaning

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

Cross-references to other Recommendation

documentation
Example text Emphasized words or phrases Syntax
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.
Upgrade Master Guide: SAP xRPM

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

Implementation Operation Upgrade

SAPterm

SAP Library

Master Guide Upgrade Master Guide

Component Component
Installation Guide Upgrade Guide

Security Guide

Configuration
Release Notes
Documentation

Implementation Guide (IMG) Delta and Upgrade IMG

Solution Management
Guide

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 Service Marketplace at service.sap.com/sapterm
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
• Current version:
{ Located in the SAP Help Portal at help.sap.com

4 July 2007
 Upgrade Master Guide: SAP xRPM

{ Located also 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
{ Project teams for implementations or upgrades
• 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
{ Solution consultants
{ Project teams for implementations or upgrades
• 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:
{ Technology consultants
{ System administrators
{ Project teams for implementations
• Current version:
Located in the SAP Service Marketplace at service.sap.com/instguides
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:
{ Technology consultants

July 2007 5
Upgrade Master Guide: SAP xRPM

{ Project teams for implementations

• Current version:
Located in the SAP Service Marketplace at service.sap.com/instguides
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:
{ Solution consultants
{ Project teams for implementations
• 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:
{ System administrators
{ Technology consultants
{ Solution consultants
{ Project teams for implementations or upgrades
• Current version:
Located in the SAP Service Marketplace at service.sap.com/instguides

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:
{ Technology consultants
{ Project teams for upgrades

6 July 2007
 Upgrade Master Guide: SAP xRPM

• Current version:
Located in the SAP Service Marketplace at service.sap.com/instguides
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:
{ Technology consultants
{ Project teams for upgrades
• Current version:
Located in the SAP Service Marketplace at service.sap.com/instguides
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
{ Project teams for upgrades
• 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

July 2007 7
Upgrade Master Guide: SAP xRPM

History
The Upgrade Master Guide is regularly updated in SAP Service Marketplace at
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.00 ( October 24, 2005 ) Initial Version
1.10 ( April 11, 2006) New section: Custom iView Migration
1.20 (September 26, 2006) New section: Migrating cRoom for Projects to
Portfolio Items
1.30 (April 2007) New section: Performing Backup
1.40 (July 2007) Changed sections: General Upgrade Information,
Post-Upgrade Activities

8 July 2007
 Upgrade Master Guide: SAP xRPM

Contents
1 Introduction ..................................................................................10
1.1 Target Audience .............................................................................11
1.2 Before You Start.............................................................................11
1.2.1 SAP Notes .......................................................................................... 11
1.2.2 Further Information ........................................................................... 11
1.2.3 Checking Integration Features and Restrictions............................ 12
1.2.4 Performing Backup ........................................................................... 12
2 Solution Overview ........................................................................13
2.1 Business Scenario Overview ........................................................13
2.2 Software Component Matrix .........................................................13
3 Upgrade.........................................................................................14
3.1 General Upgrade Information.............................................................. 14
3.1.1 Technical System Landscape .......................................................... 16
3.1.2 Upgrade Sequence............................................................................ 17
3.1.3 Post-Upgrade Activities.................................................................... 18
3.1.3.1 Configuration Migration ........................................................................................18
3.1.3.1.1 Migrating Global Roles to Role Functions..........................................................18
3.1.3.1.2 Migrating Locations and Priority Groups............................................................20
3.1.3.1.3 Migrating Global Settings for Capacity Management.........................................21
3.1.3.1.4 Migrating Object Link Type Definitions ..............................................................22
3.1.3.2 Project Migration....................................................................................................24
3.1.3.2.1 Migrating Project Categories/Subcategories......................................................25
3.1.3.2.2 Migrating Projects to Portfolio Items ..................................................................29
3.1.3.2.3 Migrating Projects to cProjects...........................................................................37
3.1.3.2.4 Undo – Migration Master Data ...........................................................................44
3.1.3.2.5 Migrating cRoom for Projects to Portfolio Items.................................................46
3.1.3.2.6 Attachment Migration Tool .................................................................................47
3.1.3.3 Custom iView Migration ........................................................................................49
4 References ....................................................................................51
4.1 Documentation ...............................................................................51

July 2007 9
1 Introduction

1 Introduction
The Upgrade Master Guide provides a central starting point for the technical upgrade of your
SAP solution.
To facilitate the upgrade process, all information within this document is grouped under
scenario-based aspects. You can choose from several business scenarios and find all the
information that is relevant for the technical upgrade of a specific business scenario in an
enclosed section.

Overview of the Main Sections

The Upgrade Master Guide comprises the following main sections:
• Before You Start
This section contains information about how to use this document, and references to
related documentation and SAP Notes.
• Overview
This section contains:
{ A short introduction to the solution
{ Information about mandatory and optional software components and their
minimum releases
{ Information on how to set up a minimal system landscape for test and demo
purposes
• Scenario-based sections
These sections contain the following information for each business scenario:
{ An overview of the technical infrastructure including information about how the
different components interact, and what protocols and interfaces are used
Depending on the amount of business functions and other aspects, such as
security or performance, the production infrastructure may be different.
{ Information about the overall upgrade sequence and subsequent steps
{ Preparations and post-upgrade activities, if necessary
{ References to related component upgrade guides
• References
This section contains an overview of additional guides which, depending on the amount
of business functions, are required to upgrade specific business scenarios.

See Also
For the most up-to-date information about the technical upgrade of this SAP solution, and the
latest installation and upgrade guides, see SAP Service Marketplace at
service.sap.com/instguides.
We strongly recommend that you use the documents that are available on these pages.
These guides are updated on a regular basis.
The technical implementation of this SAP solution is described in the documentation Project
and Portfolio Management Master Guide. Refer to this documentation for information on new
business scenarios and implementation options. It is available on SAP Service Marketplace
at service.sap.com/instguides.

10 August 2005
 Upgrade Master Guide

1.1 Target Audience

This documentation contains both high-level information on solution and business scenario
level and detailed information. It is therefore intended for decision-makers as well as SAP
consultants and SAP system administrators with operating system, database, and SAP
system knowledge.

1.2 Before You Start

1.2.1 SAP Notes

You must read these SAP Notes before you start the upgrade. They contain the most recent
information on 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 in the
SAP Service Marketplace at service.sap.com/notes.
SAP Note Title Description
Number
869091 xRPM 4.0 Master Note This note serves as a central note for SAP
xRPM 4.0. Several other important notes
are attached to this note, including those
listed below.
853692 Installing CPRXRPM 400 on This note describes how to install the ABAP
Basis Release 700 add-on component CPRXRPM 400 on SAP
NetWeaver 2004s.
853694 Upgrade SAP Basis Release This note describes how to upgrade the
700 with CPRXRPM 400 ABAP add-on component CPRXRPM 400 to
SAP Netweaver 2004s.
817189 Additional info. This note describes how to upgrade SAP
xRPM 4.0 to run on SAP Web Application
Server 6.40 (SAP NetWeaver 04).
858789 Migration of SAP xRPM 2.0 to This note describes how to migrate date
SAP xRPM 4.0: New from SAP xRPM 2.0 to SAP xRPM 4.0.
Installation support
858718 CPRXRPM: Support Packages This note contains information about all
support packages for the ABAP add-on
component CPRXRPM.

1.2.2 Further Information

The following list contains links to crucial information in SAP Service Marketplace for
implementing Project and Portfolio Management.

Description Quick Link

Product availability matrix pam

July 2007 11
Upgrade Master Guide

SAP Notes notes

Released platforms platforms
System sizing sizing
Installation documentation instguides
Security information for SAP applications security
Security guides secuityguide
Technical system infrastructure ti
Network integration network

1.2.3 Checking Integration Features and

Restrictions
Integration features and restrictions is a central tool which provides you with information on
available features and restrictions in cross-combination of software releases or software
components.
Checking planned combinations of software releases or components beforehand especially
makes upgrade projects much easier and effective.
In addition to that, the provided information may also affect your decisions or plans for special
combinations of older SAP R/3 releases with newer SAP products.
You can access the tool on SAP Service Marketplace at service.sap.com/ifr.

1.2.4 Performing Backup

We recommend to perform a backup of the SAP xRPM 2.0 system data and the SAP xRPM
4.0 system data at various points in time during the upgrade and the migration procedure. If
there are any issues arising out of upgrade or migration program runs, you can always revert
back by playing the corresponding backup file. We recommend backup files of the system
data for the following instances in time:
• Before the SAP xRPM 2.0 system is upgraded to SAP xRPM 4.0
• After you perform the upgrade to SAP xRPM 4.0, and before executing the migration
runs on configuration related data in the SAP xRPM 4.0 system.
• After you perform the migration runs on configuration in the SAP xRPM 4.0 system.
• After you perform the migration of SAP xRPM 2.0 categories/subcategories to SAP
xRPM 4.0 portfolio structures in the SAP xRPM 4.0 system.
• After you perform the migration of SAP xRPM 2.0 projects/proposals to SAP xRPM
4.0 items in the SAP xRPM 4.0 system.

12 July 2007
 Upgrade Master Guide

2 Solution Overview

2.1 Business Scenario Overview

SAP xApp Resource and Portfolio Management (SAP xRPM) is designed to manage the
capacity and deployment of human capital assets across multiple projects. SAP xRPM
integrates information from existing project management, human resources, and financial
systems to provide a complete overview of an organization’s project portfolio with easy
drilldown to details for portfolio managers, project managers, and resource managers.
• SAP xRPM 2.0 offers operational project management features such as task overview
and task management, role demand planning, and resource assignment
• SAP xRPM 4.0 utilizes project management business scenarios of cProjects to cover
operational project management features

2.2 Software Component Matrix

The software component matrix lists all required and optional components and specifies the
minimum release of each component.
For more information, see the Project and Portfolio Management Master Guide on SAP
Service Marketplace at service.sap.com/instguides → SAP xApps → SAP xApp
Resource and Portfolio Management → SAP xRPM 4.0.

July 2007 13
Upgrade Master Guide

3 Upgrade
Upgrading SAP xRPM from 2.0 to 4.0 involves:
• Installing the xRPM ABAP component (CPRXRPM)
• Installing the xRPM Java component (CPRXRPM_UI)
• Transferring operational project data from SAP xRPM business objects to cProjects
business objects
The following sections outline the steps you need to take to execute the upgrade and the
post-upgrade migration process.

3.1 General Upgrade Information

Before you can migrate SAP xRPM 2.0 operational project data to cProjects 4.0 business
objects, you must transfer configuration data. The configuration data is transferred within the
SAP xRPM system. After upgrade, all objects needed to transfer data to cProjects 4.0 objects
are in the SAP xRPM system.
When you run a migration program, the activities performed for each object instance are
recorded in a history table called /RPM/OBJ_MIGR. This history data is used by subsequent
migration programs. Recorded information includes:
• The key of the SAP xRPM 2.0 object instance
• The new key to which the object was migrated
• The purpose of the migration
This is necessary because converting SAP xRPM 2.0 objects can require multiple
conversions of programs that are run for various purposes.
The upgrade of a SAP xRPM 2.0 system to a SAP xRPM 4.0 system can be classified into
two types based on the means by which the upgrade has been performed:
• One box scenario
• Two box scenario

One Box Scenario

When the upgrade of the SAP xRPM 2.0 system is performed, so that the same SAP xRPM
2.0 system is upgraded to SAP xRPM4.0 system, then the SAP xRPM 2.0 system and the
SAP xRPM 4.0 system are one and the same.
Most migration reports have the RFC destination field. This parameter should not be
specified if it is a one box scenario

Two Box Scenario

When the SAP xRPM 2.0 system (henceforth called the sub-system) and the SAP xRPM 4.0
system are two different systems, this is a two box scenario. In this case the SAP xRPM 4.0
system is totally new.
Most migration reports have the RFC destination field. You should specify the sub system
SAP xRPM 2.0 as RFC destination.
When doing this, all configuration tables of the RFC destination must be replicated to the
system where you execute the migration program. Also, the business partner IDs and
assignments to corresponding users and employee ID.

14 July 2007
 Upgrade Master Guide

To execute the RFC option, certain function modules must be available in the
SAP xRPM 2.0 system. For more information, see SAP Note 858789.

If you perform an upgrade from SAP xRPM 2.0 to SAP xRPM 4.0 based on a
completely new SAP xRPM 4.0 system, you must fulfill certain requirements
such as identical configuration for all SAP xRPM configuration possibilities,
identical user replication.
If you are performing a new SAP xRPM 4.0 installation, you need to process the activities in
the sections of the SAP xRPM Implementation Guide (IMG) listed below.
• To activate Business Content data sources, go to SAP xApp Resource and Portfolio
Management (SAP xRPM) → Activate Business Content Data Sources
• For SAP Human Capital Management data distribution, go to SAP xApp Resource
and Portfolio Management (SAP xRPM) → Base System Interfaces → SAP Human
Capital Management Integration
• For SAP Financial and Controlling data distribution, go to SAP xApp Resource and
Portfolio Management (SAP xRPM) → Base System Interfaces → SAP Financial
and Controlling Integration
You can copy configuration from an xRPM 2.0 system to a new SAP xRPM 4.0 system by
using a client comparison and adjustment feature available in the view maintenance
transaction SM30. To do this, choose Utilities → Adjustment in the new SAP xRPM 4.0
system. xRPM 2.0 configuration in the SAP xRPM Implementation Guide (IMG) is as follows:
• Global settings:

Go to SAP xApp Resource and Portfolio Management (SAP xRPM) → Global

Customizing → Global Settings → Override Default Global Settings

View V_RPM_SET_VAL_C (transaction SM30)

• Category customizing:

Go to SAP xApp Resource and Portfolio Management (SAP xRPM) → Global

Customizing → Project Settings → Define Project Categories

View cluster V_RPM_CAT_CUST (transaction SM34)

• Project geographical locations:

Go to SAP xApp Resource and Portfolio Management (SAP xRPM) → Global

Customizing → Project Settings → Define Project Geographical Locations
• Project locations:

Go to SAP xApp Resource and Portfolio Management (SAP xRPM) → Global

Customizing → Project Settings → Define Project Physical Locations
• If you want to use the xRPM 2.0 priority definition in the operational SAP xRPM 4.0
project data, which is now stored and processed using cProjects project
management functionality, priority group customizing should be available:

Go to SAP xApp Resource and Portfolio Management (SAP xRPM) → Global

July 2007 15
Upgrade Master Guide

Customizing → Project Settings → Define Project Alerts

View V_RPM_PROJ_PRGRP (transaction SM30)

• If you are using object links (for example for project integration processes or direct
object link maintenance on xRPM 2.0 project objects), define object links:

Go to SAP xApp Resource and Portfolio Management (SAP xRPM) → Base System
Interfaces → Application Object Settings > Define Business Object Links
The following sections describe the migration steps needed to make use of the various new
features available in SAP xRPM 4.0.
In SAP xRPM 4.0, you also need to :
• Restrict the available time units to those which are really needed in portfolio processes.
In a two box scenario, all available SAP xRPM 2.0 allocation units should also be
present in the SAP xRPM 4.0 system:
{ You review available units of measurement in Customizing by choosing SAP
xApp Resource and Portfolio Management (SAP xRPM) → Global Settings →
Define Units of Measurement
{ You define to which units portfolio processes should be restricted to in
Customizing by choosing SAP xApp Resource and Portfolio Management (SAP
xRPM) → Portfolio Independent Setting → Define Capacity Units
• Restrict the available currency units to those which are really needed in portfolio
processes
{ You define to which units portfolio processes should be restricted to in
Customizing by choosing SAP xApp Resource and Portfolio Management (SAP
xRPM) → Portfolio Independent Setting → Define Currency Units

You should review the following Customizing sections to evaluate the new
features available in SAP xRPM 4.0 and find out what you need to do before
creating the SAP xRPM 4.0 portfolio structure:
ƒ SAP xApp Resource and Portfolio Management (SAP xRPM) -> Global
Settings
ƒ SAP xApp Resource and Portfolio Management (SAP xRPM) -> Portfolio
Independent Settings
ƒ SAP xApp Resource and Portfolio Management (SAP xRPM) -> Process and
Service Settings
• Owner Activity:
{ If the activity 'Owner' is not already defined in the system, you need to define it
in the view settings V_ACO_ACTIVITY.

3.1.1 Technical System Landscape

The following graphic shows the main components of SAP xRPM and the communication
paths between them.

16 July 2007
 Upgrade Master Guide

SAP
SAPEnterprise
EnterprisePortal
Portal7.0
7.0
http (SAP
(SAPNetWeaver
NetWeaver2004s)
2004s) http

JCO/RFC

SAP
SAPBW
BW7.0
7.0 SAP
SAPxRPM
xRPM SAP
SAPcProjects
cProjects
(SAP
(SAPNetWeaver
NetWeaver
2004s) 4.0
4.0 4.0
4.0
2004s)

ALE
ALE/ /RFC
RFC/ /SAP
SAPXI
XI

SAP
SAPxApp
xApp
SAP
SAP SAP
SAP Product
Product Project
Project Time
Time
FI/CO
FI/CO HCM
HCM Definition
Definition Management*
Management* Management**
Management**
(xPD)
(xPD)2.0
Base 2.0
Systems
*SAP Project System (PLM PS); SAP cProjects; Microsoft Project; Microsoft Project Server
** SAP CATS; Available through usage of standard SAP Employee Self Service (ESS) in SAP Enterprise Portal

3.1.2 Upgrade Sequence

Before performing the migration, you must install the ABAP component
(CPRXRPM) and the Java component (CPRXRPM_UI).

Configuration Migration
Step Action Remarks
1 Transfer SAP xRPM global roles to Required, because the result is
cProjects 4.0 role functions used in migration of SAP xRPM
2.0 master data migration
programs.
2 Transfer SAP xRPM 2.0 geographical Required, because the result is
location, physical location configuration, and used in migration of SAP xRPM
priority groups to corresponding cProjects 2.0 project/proposal migration
4.0 configuration tables. programs.
3 Transfer SAP xRPM 4.0 capacity Required if capacity
management configuration data management processes were
used in SAP xRPM 2.0.
4 Transfer SAP xRPM 2.0 object link type Required, because the result is
configuration data to cProjects 4.0 used in migration of SAP xRPM
configuration tables 2.0 project/proposal migration
programs.

Master Data Migration

July 2007 17
Upgrade Master Guide

Step Action Remarks

1 Transfer SAP xRPM 2.0 categories and Required
subcategories to a portfolio structure in SAP
xRPM 4.0.
2 Transfer SAP xRPM 2.0 projects to portfolio Required. But if the cProjects
items in SAP xRPM 4.0. Link SAP xRPM project already exists, based on
2.0 projects to the newly-created portfolios. the option selected, the
Create cProjects headers in cProjects 4.0 migrated item is linked to this
for the SAP xRPM 2.0 projects. cProjects project.
3 Create a cProjects project structure based Optional
on operational SAP xRPM 2.0 project data.
4 Undo master data migration runs. Optional
This step enables you to rerun
the master data migration
programs

3.1.3 Post-Upgrade Activities

For post-upgrade information about the ABAP component (CPRXRPM) and the
Java component (CPRXRPM_UI), see the relevant documentation:
ƒ For more information about the ABAP component, see SAP Note 853692
ƒ For more information about the Java component, see the SAP xRPM
Java Component Installation Guide on SAP Service Marketplace at:
service.sap.com/instguides → SAP xApps → SAP xApp
Resource and Portfolio Management → SAP xRPM 4.0

3.1.3.1 Configuration Migration

3.1.3.1.1 Migrating Global Roles to Role Functions

Purpose
Migrate SAP xRPM 2.0 global roles to SAP xRPM 4.0 role functions.

Prerequisites
None.

Limitations
• If the SAP xRPM 2.0 global role ID is longer than 15 characters, it is truncated and
written to the SAP xRPM 4.0 role function key

In this case, a warning message is written to the log.

• Duplicate role functions are skipped.

18 July 2007
 Upgrade Master Guide

This may occur due to the truncation of the global role key. In this case, an error
message is written to the log.
• In xRPM 4.0, global roles as used in xRPM 2.0 have been improved:

o In xRPM 2.0, a global role could be used as a template to create project roles,
thereby making the role template redundant. In SAP xRPM 4.0 a role type and a role
function can be used together to define a cProjects role.
o The hierarchical grouping of roles within global roles available in SAP xRPM 2.0 has
been simplified in SAP xRPM 4.0. It is now sufficient to define role function as a flat
list.
o The purpose of a role function in SAP xRPM 4.0 is restricted to classification of
unstructured project roles. The role function assigned to a project role is the basis for
integrating operational project role demand data into portfolio resource demand
planning processes
Selection Options
• Test mode (no DB-update)

• If this option is checked, no database updates occur

• If this option is unchecked, the database is updated and logs are stored
• Only roles without children

If you select this option, only the lowest level global role is migrated. Parent global
roles are not converted to role functions.
• Overwrite existing entries

If you select this option, existing role functions are overwritten.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. In the Program field, enter /RPM/MIGRATION_GLOBAL_ROLE and choose Execute.
3. Enter your selection options and select Execute.
4. Review the log file for possible errors and make corrections if required.
5. To validate or manually change the migrated role functions, select Change Data.
From the table maintenance of table view V_DPR_ROLE_FUNC, you can do the
following:

a. To view the role functions, choose Display

b. To add, delete or modify the functions, choose Maintain
c. If necessary, you can also include the role functions in a transport request
Additional Information
You can also configure role functions manually in the cProjects Customizing by choosing
Collaboration Projects → Resource Management → Basic Settings for Project Roles →
Define Project Role Functions.

Result
SAP xRPM 2.0 global roles are migrated to SAP xRPM 4.0 role functions. To review the
result, start transaction SM30 and display table view V_DPR_ROLE_FUNC.

July 2007 19
Upgrade Master Guide

3.1.3.1.2 Migrating Locations and Priority Groups

Purpose
Migrate xRPM 2.0 project physical locations and project geographical locations to cProjects
4.0 locations and areas.
The xRPM 2.0 priority group configuration is also migrated to a cProjects priority
configuration. In a cProjects project, the value of the attribute Priority is based on the xRPM
2.0 project priority group.
An SAP xRPM 4.0 portfolio item still has the priority group as an attribute and the
configuration of that priority group remains the same as in xRPM 2.0.

Prerequisites
None

Selection Options
• Test mode (no DB-update)

• If this option is checked, no database updates occur

• If this option is unchecked, the database is updated and logs are stored
• Overwrite existing entries

If you select this option, existing locations, areas and priority groups are overwritten.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. In the Program field, enter /RPM/MIGRATION_PROJ_ATTRIBUTES and choose Execute.
3. Enter the selection options and choose Execute.
4. Review the log file for possible errors and make corrections if required.
5. To validate and/or manually change the locations that have been migrated, choose
Change Data for Location.

From the table maintenance of table view V_DPR_LOCATION, you can:

{ Choose Display to view the locations
{ Choose Maintain to add, delete or modify locations
{ You can also include the locations in a transport request.
6. To validate and/or manually change the areas that have been migrated, choose Change
Data for Area.

The table maintenance view is V_DPR_AREA.

7. To validate and/or manually change the priority group definitions that have been
migrated, choose Change Data for Priority.

The table maintenance view is V_DPR_PRIORITY.

Additional Information

20 July 2007
 Upgrade Master Guide

• You can also configure locations and areas manually via the following IMG steps
{ SAP xApp Resource and Portfolio Management (SAP xRPM) → Global
Customizing → Project Settings → Define Areas
{ SAP xApp Resource and Portfolio Management (SAP xRPM) → Global
Customizing → Project Settings → Define Locations
• In SAP xRPM 2.0, customers defined project physical locations and project
geographical locations and assigned the physical location to a geographical location.
The relevant tables are:
xRPM 2.0 physical location RPM_PROJ_LOCAT
RPM_PROJ_LOCAT_T
xRPM 2.0 geographical location RPM_PROJ_GEOGR
RPM_PROJ_GEOGR_T
• In cProjects 4.0, the definition of locations and areas has been moved to cProjects.
The new tables are:
cProjects 4.0 Location DPR_LOCATION
DPR_LOCATION_T
cProjects 4.0 Area DPR_AREA
DPR_AREA_T
• In xRPM2.0, customers can assign priorities to projects based on the priority groups
settings. The relevant tables are:
xRPM 2.0 priority groups RPM_PROJ_PRGRP and RPM_PROJ_PRGRP T
• In cProjects 4.0, you can define a priority in the following new tables:
cProjects 4.0 Priority View: V_DPR_PRIORITY
Tables: DPR_PRIORITY and DPR_PRIORITY_T

Result
SAP xRPM 2.0 project physical locations and project geographical locations are migrated to
cProjects 4.0 locations and areas.
The cProjects priority configuration table is based on SAP xRPM 2.0 priority group definitions.
The migration program /RPM/MIGRATION_2_CP_PROJECTS creates a cProjects project
based on an xRPM 2.0 project and the priority of that cProjects project is based on the
priority group maintained on the xRPM 2.0 project.

3.1.3.1.3 Migrating Global Settings for Capacity Management

Purpose
Migrate SAP xRPM 2.0 global settings for capacity management to a new table in cProjects
4.0.
• In SAP xRPM 2.0, the global settings contained an area (0001) for configuration of
capacity management. SAP defined default values, but you were able to override these
entries
• In SAP xRPM 4.0, the capacity management configuration has been moved to table
maintenance view V_DPR_DIST_VAL, which contains SAP standard settings and
customer settings

July 2007 21
Upgrade Master Guide

Only customer-specific configuration is converted and moved to the new table in

the customer name range (scope = Z). If no customer-specific configuration
exists in the global settings, this conversion is not required.

Selection Options
• Test mode (no DB-update)

• If this option is checked, no database updates occur

• If this option is unchecked, the database is updated and logs are stored
• Overwrite existing entries

If you select this option, existing locations and areas are overwritten.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. Enter /RPM/MIGRATION_GLOBAL_SET in the Program field and choose Execute.
3. Enter the selection options and choose Execute.
4. Review the log file for possible errors and make corrections if required.
5. To validate and/or manually change the capacity management settings that have been
migrated, choose Change Data.

From the table maintenance of table view V_DPR_DIST_VAL, you can:

{ Choose Display to view the locations
{ Choose Maintain to add, delete or modify locations

You can switch the Type of Setting field between SAP Basic Setting and
Customer Setting. You can find the migrated data under Customer Setting. If no
customer settings exist, the system uses the SAP basic settings as a default.
{ You can also include the locations in a transport request.

Additional Information
You can also configure global settings for capacity management in the cProjects Customizing
by choosing Collaboration Projects → Resource Management → Basic Settings for Project
Roles → Make General Settings for Distribution.
• In SAP xRPM 2.0, you can find customer-specific global settings in the table
RPM_SET_VAL_C (capacity management is area 0001)
• In SAP xRPM 4.0, this configuration is stored in the table DPR_DIST_VAL

Result
SAP xRPM 2.0 global settings for capacity management are migrated to the new table view
V_DPR_DIST_VAL.

3.1.3.1.4 Migrating Object Link Type Definitions

Purpose

22 July 2007
 Upgrade Master Guide

In SAP xRPM 4.0, the configuration of object link types has been integrated with cProjects,
so the purpose of this program is to:
- Migrate object link type configuration to a new configuration table DPR_OBL_OBTYP

All object link types in the customer name range are copied
- Update each object link type entry with the RFC destination based on information from
the SAP xRPM 2.0 table RPM_RFCSYS
- Convert business object types to object link type groupings

All objects in the customer name range are migrated.

Limitations
• Standard object link types modified by the customer (that is, those with names that
start with 0) are copied, if the logical system or HTTP destination has been maintained
• Standard types from SAP xRPM 2.0, which do not exist in SAP xRPM 4.0, are created

Prerequisites
None

Selection Options
• Test mode (no DB-update)

• If this option is checked, no database updates occur

• If this option is unchecked, the database is updated and logs are stored
• Overwrite existing entries

If you select this option, existing object link types and object link type groupings are
overwritten.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. Enter /RPM/MIGRATION_OBJ_LINKS in the Program field and choose Execute.
3. Enter the selection options and choose Execute.
4. Review the log file for possible errors and make corrections if required.
5. Verify the object link types:

To validate and/or manually change the object link types, choose Change Object Link
Type. The view cluster is VC_RPM_OBL_OBTYP. Here, you should verify the following:
{ Existence of all required object link types (standard types as well as those in the
customer name range)
{ See the details of each object link type and check that the destination and HTTP
destination are correct (in the detailed navigation, see Settings for Integration
Processes)
{ Verify the grouping (previously business object type)

6. Verify the object link type grouping:

To validate and/or manually change the object link type grouping, chose Change Object

July 2007 23
Upgrade Master Guide

Groupings.

From the table maintenance of table view V_DPR_OBGRP_INT, you can:

{ Choose Display to view the settings
{ Choose Maintain to add, delete or modify settings

You can also to include the settings in a transport request from the relevant
view or view cluster.

Additional Information
• You can configure object link types in Customizing by choosing SAP xApp Resource
and Portfolio Management (SAP xRPM) → Base System Interfaces → Application
Object Settings → Define Object Link Types
• Object link types are stored in the cProjects configuration table DPR_OBL_OBTYP

This table also contains the destination and the HTTP destination (previously stored in
the SAP xRPM 2.0 specific table RPM_RFCSYS). To continue to provide additional
features in SAP xRPM 4.0, the attributes Application and Logical System remain in the
SAP xRPM-specific table RPM_OBL_OBTYP.
• You can configure object link type groupings in Customizing by choosing SAP xApp
Resource and Portfolio Management (SAP xRPM) → Base System Interfaces →
Application Object Settings → Define Object Link Type Groupings

You can find this information in the table DPR_OBL_OBGRP. As of SAP xRPM 4.0, table
RPM_RFCSYS is obsolete.

Result
• Object link types are migrated to the new table DPR_OBL_OBTYP, including the
destination and the HTTP destination
• Business object types are converted to object link type groupings (table
DPR_OBL_OBGRP)

3.1.3.2 Project Migration

These migration programs enable you to use SAP xRPM 2.0 project data in two SAP xRPM
4.0 processes. You can:
• Use portfolio structure processes for strategic portfolio decision processes
• Use cProjects 4.0 for operational project planning
You should review the new configuration possibilities offered for both areas by reading all
relevant documentation such as:
• Release notes, Master Guides, and other documentation available on SAP Service
Marketplace at service.sap.com
• Implementation guides (IMG) available for:
o SAP xApp Resource and Portfolio Management (SAP xRPM) 4.0
o cProjects (Collaboration Projects) 4.0

24 July 2007
 Upgrade Master Guide

3.1.3.2.1 Migrating Project Categories/Subcategories

Purpose
Migrate SAP xRPM 2.0 project categories and subcategories to the SAP xRPM 4.0 portfolio
structure.
Project categories and subcategories remain as attributes of portfolio items in SAP xRPM
4.0, but the structure of each portfolio is now defined as a more complex bucket hierarchy.

Prerequisites
Before executing this migration program, you must configure portfolio types.
You can do this in Customizing by choosing SAP xApp Resource and Portfolio Management
(SAP xRPM) → Global Customizing → Portfolio Dependent Settings → Define Portfolio
Types.
A portfolio type is an important grouping criterion for portfolios. It defines how services for a
particular portfolio item are processed.
Services depending on the portfolio type include:
• Navigation
• Financial categories and groups
• Capacity categories and groups
• Field configurations on the user interface
Before migrating the xRPM 2.0 categories to an SAP xRPM 4.0 portfolio structure, you
should review these services and configure them accordingly.

SAP delivers example configuration. If this configuration is not available in the

client where xRPM is set up, check the available SAP example configuration in
client 000.
Navigation
In xRPM 2.0, navigation was configurable for a project. SAP xRPM 4.0 offers an extended
range of navigation options. For each object such as portfolio item, review and collection
object, you can now define the navigation for each portfolio and each role.
You can configure the navigation configuration in Customizing by choosing SAP xApp
Resource and Portfolio Management (SAP xRPM) → Global Customizing → Process and
Service Settings -> Define Navigation.

SAP delivers example configuration. If this configuration is not available in the

client where xRPM is set up, check the available SAP example configuration in
client 000.

Financial/Capacity Categories Groups and Views

Financial/capacity categories and groups for each portfolio item and bucket are a new feature
of SAP xRPM 4.0. This needs to be configured.

July 2007 25
Upgrade Master Guide

You define financial/capacity categories and groups in Customizing by choosing SAP xApp
Resource and Portfolio Management (SAP xRPM) → Global Customizing → Portfolio
Independent Settings -> Define Financial and Capacity Categories.
You define financial/capacity views in Customizing by choosing SAP xApp Resource and
Portfolio Management (SAP xRPM) → Global Customizing → Portfolio Independent Settings
-> Define Financial and Capacity Views.
The categories and groups available for an item depend on the portfolio type, to which the
item is assigned.
You assign portfolio types to categories/groups and views in Customizing by choosing SAP
xApp Resource and Portfolio Management (SAP xRPM) → Global Customizing → Portfolio
Dependent Settings -> Define Portfolio Types.

SAP delivers example configuration. If this configuration is not available in the

client where xRPM is set up, check the available SAP example configuration in
client 000.

Field Configuration
• In xRPM 2.0, it was only possible to customize fields displayed in the user interface by
configuring the iView parameters for each portal role
• In SAP xRPM 4.0, extended field configuration capability is available:

You can now define which fields should be displayed in the user interface (including
properties such as required and read-only) for each object such as portfolio item,
bucket, portfolio, and review.

Since this can also be done for each portfolio type, it supports the requirement to offer
different fields within different portfolios.
SAP delivers a standard setup, but you can customize global field handling in Customizing by
choosing SAP xApp Resource and Portfolio Management (SAP xRPM) → Global
Customizing -> Global Field Settings -> Define Custom Field Configuration.
In the in Customizing by choosing SAP xApp Resource and Portfolio Management (SAP
xRPM) → Global Customizing → Portfolio Dependent Settings -> Define Portfolio Types; you
can override further settings as follows:
• In Portfolio Fields Override, you can overwrite the global field configuration with a
portfolio type-specific field configuration for each object portfolio, bucket, item and
review.
• In Portfolio Items Override, you can specify whether an attribute of an item of a
particular item type is a required field or not.
• In Portfolio Item-Decision Point Override, you can specify whether an attribute of a
decision point of a particular item type is a required field or not.
Before executing the category to portfolio migration process, you should also
get an overview of the portfolios you want to create. For each portfolio, you
should decide:
ƒ Which navigation you want
ƒ Whether you want to use the capacity and financial planning feature – if yes,
you must set up the desired capacity and financial planning groups
accordingly

26 July 2007
 Upgrade Master Guide

ƒ Which fields you want to display on the portfolio, bucket, item and review
user interface
Two Box Scenario:
To transfer data from xRPM 2.0 to SAP xRPM 4.0 when SAP xRPM 2.0 is in a different
system to SAP xRPM 4.0, proceeed as follows:
1. In the SAP xRPM 4.0 system, call transaction SM30.
2. To transfer project categories, enter the view V_RPM_PROJ_CAT and choose
Maintain.
3. Choose Utilities → Adjustment.
4. Select the xRPM 2.0 system from which you want to retrieve data, and choose
Choose.
5. Select the data that you want to transfer and choose Adjust.
6. The Detail View: Adjust screen appears.
7. Choose Edit → Adjust → Copy All Entries.
8. Save your entries.
Repeat the above steps for project subcategories, by entering the view V_RPM_PROJ_SUBCT
in step two above.
...

Selection Options
General Options
• Test mode (no DB-update)

• If this option is checked, no database updates occur

• If this option is unchecked, the database is updated and logs are stored
Migration Options
Option Effect Remarks
1 In this case: Most frequently-
used option
• SAP xRPM 2.0 project categories are migrated to
SAP xRPM 4.0 portfolios
• SAP xRPM 2.0 project subcategories are migrated
to SAP xRPM 4.0 buckets within the respective
portfolio
2 In this case, a new portfolio is created: Rarely used
• SAP xRPM 2.0 project categories are migrated to
SAP xRPM 4.0 buckets
• SAP xRPM 2.0 project subcategories are migrated
to SAP xRPM 4.0 subbuckets
Parameters:
• Portfolio external ID
To allow you to create a new portfolio, you must
enter an external ID. The field length is limited to 24
characters.
Portfolio name

July 2007 27
Upgrade Master Guide

• You must enter a name for the new portfolio. The

field length is limited to 40 characters.
3 In this case: Rarely used
• SAP xRPM 2.0 project categories are eliminated
• SAP xRPM 2.0 project subcategories are migrated
to SAP xRPM 4.0 portfolios

Additional Options
• Project categories:

You can define which project categories should be migrated. You can enter single
project categories or a range of project categories.
• Portfolio/bucket owner:

To facilitate the authorizations of the portfolio/bucket, you must specify the

portfolio/bucket owner, but you can manually update this at any time.
• Portfolio/bucket administrator:

To facilitate the authorizations of the portfolio/bucket, you must specify the

portfolio/bucket administrator, but you can manually update this at any time
• Portfolio types:

A portfolio type identifies a group of portfolios that follow the same strategy and is a
required attribute of a portfolio definition. Select the portfolio type you want to be
assigned to the portfolios during the migration from the search help.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. Enter /RPM/MIGRATION_CATEGORIES in the Program field and choose Execute.
3. Enter the selection options and choose Execute.

If you require a rerun, start the program /RPM/MIGRATION_AUX_TOOLS.

The option Delete the complete Portfolio deletes the specified portfolio. After
execution of this program, you can re-create the portfolio by running the
program /RPM/MIGRATION_CATEGORIES.

4. To check that the migration of all SAP xRPM 2.0 categories and subcategories was
successful, log on to the portal and choose Portfolio Management → Administration.
Then, select the migrated portfolios from the Portfolio Dashboard and select and review
all buckets and subbuckets in the portfolio.
5. To review the configuration possibilities in the SAP xRPM 4.0 frontend application, you
can review the navigation definition in Customizing by choosing SAP xApp Resource and
Portfolio Management (SAP xRPM) → Process and Service Settings → Define
Navigation.

To make sure that the back-end configurations are correctly replicated in the portal
environment, reload the xRPM cache, which contains the replicated configuration

28 July 2007
 Upgrade Master Guide

options. To do this, go to Portfolio Management → Administration → Cache

Administration and choose Invalidate Entire Cache.

Always execute the program /RPM/MIGRATION_CATEGORIES for a category or

a range of categories so that all subcategories under each category are
processed to form an SAPxRPM 4.0 portfolio structure. Do not leave out a
subcategory assuming that you would like to do the migration of this
subcategory later.

Result
SAP xRPM 2.0 project categories and subcategories are migrated to SAP xRPM 4.0
portfolios, buckets and subbuckets.

Attributes from SAP xRPM 2.0 migrated to SAP xRPM 4.0

Object SAP xRPM 2.0 Attributes SAP xRPM 4.0 Attributes
Category to • Category (for example, • Portfolio external ID (for example,
Portfolio 1111) 1111)
• Project category text (for • Portfolio name (eg:Migration_Category)
example,
Migration_Category)
Subcategory • Project subcategory (for • Bucket external ID (for example, 1111-
to Buckets example, 0001) 0001)
• Project subcategory text (for • Bucket name (for example,
example, Migration_SubCategory)
Migration_SubCategory)

3.1.3.2.2 Migrating Projects to Portfolio Items

Purpose
Migrate SAP xRPM 2.0 projects to SAP xRPM 4.0 portfolio items.

Prerequisites
Item Types
• In SAP xRPM 2.0, a project was either a proposal or an approved project
• In SAP xRPM 4.0 a portfolio contains portfolio items which can be grouped by item
types

Item types are attributes of items that you can configure in Customizing. They define
general processes for portfolio items.
You must configure item types before executing this migration program. You can do this in
Customizing by choosing SAP xApp Resource and PortfolioManagement (SAP xRPM) →
Global Customizing → Portfolio Independent Settings → Define Portfolio Item Types.
In the item type configuration, you can decide if a cProjects project will be created
automatically as and when an item is created. This configuration of an item type is taken into
account in the migration report and decides whether a cProjects project has to be created or
not, when the SAP xRPM 2.0 project is migrated to an SAP xRPM 4.0 item.

July 2007 29
Upgrade Master Guide

But, if the SAP xRPM 2.0 project has tasks or a task structure associated to it, then
irrespective of the item type, a cProjects Project header will be created.
Portfolio Structure
You must create the portfolio structure before executing this migration program.
For more information, see the section Project Category/Subcategory to Portfolio Structure
above.
Geography/Location
You must convert physical locations and geographical locations before running this migration
program.
For more information, see the section Area/Location and Priority Group above.
Object Link Type Definitions
You must migrate object link types before executing this migration program. It is important
that the definition for every object link type used in a project exists in the new configuration
tables.
For more information, see the section Object Link Type Definitions above.
Customer Attribute Definitions for SAP xRPM 2.0 Projects

In SAP xRPM 2.0, customer-specific fields may have been added to the project structure.
Transferring these fields to SAP xRPM 4.0 depends whether they are related to:
• Strategic portfolio management

In this case, you must add the fields to a new customer include structure, which is
available for portfolio items.
To do this, you must create the structure CI_RPM_ITEM_ATT and manually add all
fields from the SAP xRPM 2.0 project structure CI_RPM_TS_PROJECT_ATT that are
relevant to strategic portfolio management processes to the structure (using the ABAP
Dictionary transaction se11).
• Operational project management

In this case, you must add the fields to a new customer include structure, which is
available for cProjects projects.
To do this, you must create the structure CI_DPR_PROJECT and manually add all
fields from the SAP xRPM 2.0 project structure CI_RPM_TS_PROJECT_ATT that are
relevant to operational project management processes to the structure (using the
ABAP Dictionary transaction se11).

The migration programs transfer the values of the customer fields for each project
automatically (as long as those fields have exactly the same names).
For more information about how to define customer includes in SAP xRPM 4.0, see in
Customizing by choosing SAP xApp Resource and PortfolioManagement (SAP xRPM) →
Business Add-Ins and Customer Includes → Customer Includes.
cProjects Project Type

In SAP xRPM 4.0, the operational data of a project previously maintained in an xRPM 2.0
project (tasks, roles, resource assignments) is now available for maintenance using a
cProjects project. Each SAP xRPM 4.0 item has a corresponding cProjects project, which is
directly assigned to the portfolio item.

30 July 2007
 Upgrade Master Guide

The project to item migration program creates a cProjects project for each xRPM 2.0 project
and links it to the SAP xRPM 4.0 item. When the cProjects project is created, a cProjects
project type must be assigned to it.
SAP delivers a default cProjects project type, which you should use when creating the
cProjects project for each item. You can review this configuration in Customizing by choosing
SAP xApp Resource and PortfolioManagement (SAP xRPM) → Global Customizing → Check
Global Settings.
You can review the settings of the cProjects project type in the cProjects Customizing by
choosing Collaboration Projects → Structure -> Define Project Types.
If you want to use a different cProjects project type, you can define a customer-specific
default project type in Customizing by choosing SAP xApp Resource and
PortfolioManagement (SAP xRPM) → Global Customizing → Override Default Global
Settings (area 0009, name 0002). Enter the cProjects project type ID in the Settings Value
Field.
Optional Steps
SAP xRPM 4.0 portfolio processes offer new features and functions for a portfolio item,
including decision points, questionnaires, and scoring models. You can add all of these to a
portfolio item later, but if you want to do this directly after upgrade, see the following steps in
Customizing and make the configuration as required:
• For questionnaire and scoring model definitions, go to SAP xApp Resource and
Portfolio Management (SAP xRPM) → Global Customzing → Process and Service
Settings
• To define globally which standard attributes should contain the results of portfolio
item services like questionnaires and scoring models and which standard attributes
should be utilized by a portfolio item, go to SAP xApp Resource and Portfolio
Management (SAP xRPM) → Global Customizing → Global Field Settings → Check
SAP Field Configuration
• To define globally which customer-specific attributes should contain the results of
portfolio item services like questionnaires and scoring models and which customer-
specific attributes should be used by a portfolio item, go to SAP xApp Resource and
Portfolio Management (SAP xRPM) → Global Customizing → Global Field Settings
→ Define Customer Field Configuration
To make use of these optional features, you should review the portfolio structure buckets
created in the previous step. You can define which questionnaires and scoring models should
be used by items within a particular bucket.
To review the bucket settings, log on to the portal and choose Portfolio Management →
Administration.
Decision Points Status
In SAP xRPM 4.0, you can define decision points for an SAP xRPM 4.0 item,based on the
item type. You can link the decision points to an item type, allocate the different decision
point statuses for each decision point by choosing SAP xApp Resource and Portfolio
Management (SAP xRPM) → Global Customizing → Portfolio Independent Settings → Define
Portfolio Item Types
In SAP xRPM 2.0, you can define phases for a category in the view V_RPM_PROJ_PHASE.
SAP xRPM 4.0 decision points and SAP xRPM 2.0 phases can be considered synonymous,
hence the need to migrate SAP xRPM 2.0 phases to SAP xRPM 4.0 decision points.
Based on the option chosen in the selection screen for ‘Decision Point Status from Approval
Status’, the following needs to be performed:

July 2007 31
Upgrade Master Guide

If you have set the indicator:

• Create as many decision points and an extra decision point for the SAP xRPM 4.0 item
type as there are SAP xRPM 2.0 phases for the assigned category. For example, if there
are four SAP xRPM 2.0 phases then assign five decision points to the corresponding item
type. The first decision point corresponds to a Proposal.
• For the first decision point which is flagged as Proposal, create as many decision point
statuses as there are SAP xRPM 2.0 approval statuses. The decision point status ID
need not necessarily be the same as that of the SAP xRPM 2.0 approval status ID as the
mapping between the approval status and the decision point status happens based on
the order and not the IDs.
• If the SAP xRPM 2.0 object happens to be a Proposal, then the first decision point is set
to Active and based on the SAP xRPM 2.0 approval status, the corresponding SAP xRPM
4.0 decision point status is set based on the order of occurrence. The other decision
points get a status that corresponds to the Start Status.
• If the SAP xRPM 2.0 object happens to be a Project and the project is not assigned to a
phase, then the first decision point is set to a status based on the SAP xRPM 2.0
approval status.The second decision point is set to Active, status is set to Start Status. All
other future decision points do not have a status set.
• If the SAP xRPM 2.0 object happens to be a Project and the project is assigned to a
phase, such as phase 2, assuming there are four phases and hence five decision points,
then the first decision point, such as decision point 1, is set to a status based on the SAP
xRPM 2.0 approval status.The third decision point, such as decision point 3, is set to
Active. All previous decision points, such as decision point 2, have status set to a status
that corresponds to the End Status. The currently active decision point, such as decision
point 3 and other decision points, such as decision point 4, decision point 5, are set to a
status that corresponds to the Start Status.

If you have not set the indicator:

• Create as many decision points for the SAP xRPM 4.0 item type as there are SAP xRPM
2.0 phases for the assigned category. For example, if there are four SAP xRPM 2.0
phases then assign four decision points to the corresponding item type.
• If the SAP xRPM 2.0 object happens to be a Project/Proposal and the SAP xRPM 2.0
object is not assigned to a phase, then the first decision point is set to Active and the
status of the first decision point and other decision points are set to a status that
corresponds to the Start Status.
• If the SAP xRPM 2.0 object happens to be a Project/Proposal and the SAP xRPM 2.0
Object is assigned to a phase, such as phase 3, assuming there are four phases and
hence four decision points, the third decision point, such as decision point 3 is set to
Active. All previous decision points, such as decision point 1, decision point 2, have
status set to a status that corresponds to the End Status. The currently active decision
point, such as decision point 3 and the other decision points, such as decision point 4, are
set to a status that corresponds to the Start Status.
Once migration is complete, you may manually adjust the decision points.
To review or change the decision points available to the portfolio item, log on to the Portal
and select Portfolio Management → Item Management. Then, on the Object Info pane, select
the migrated portfolios from the list provided.

Item Status:
The SAP xRPM 2.0 execution status for an SAP xRPM 2.0 project can be assigned to the
status of SAP xRPM 4.0 item. For this to be done, the number of SAP xRPM 2.0 execution
statuses must equal the number of item statuses. A one-to-one mapping is done between the
execution status and the item status based on the order in which it occurs.

32 July 2007
 Upgrade Master Guide

Two Box Scenario

To transfer data from SAP xRPM 2.0 to SAP xRPM 4.0 when SAP xRPM 2.0 is in a different
system to SAP xRPM 4.0, proceeed as follows:
1. In the SAP xRPM 4.0 system, call transaction SM30.
2. To transfer project categories, enter the view V_RPM_PROJ_APST and choose
Maintain.
3. Choose Utilities → Adjustment.
4. Select the xRPM 2.0 system from which you want to retrieve data, and choose
Choose.
5. Select the data that you want to transfer and choose Adjust.
6. The Detail View: Adjust screen appears.
7. Choose Edit → Adjust → Copy All Entries.
8. Save your entries.
9. Performed the above mentioned steps for the Views: V_RPM_PROJ_EXST and
V_RPM_PROJ_PHASE

Selection Options
General Options
• Test Mode (no DB-update)

o If you set the indicator, database updates will not occur.

o If you do not set the indicator, the database will be updated and logs will be
stored.
Project Selection
• Project category:
{ Select a project category from the dropdown list. If you leave this field blank, all
project categories are migrated.
• Project subcategory:
{ Select a single project subcategory or a range of project subcategories from the
dropdown list. If you leave this field blank, all project subcategories are
migrated.
• Project external ID:
{ Select a single project ID or a range of project IDs from the dropdown list. If you
leave this field blank, all projects are migrated.

Portfolio and Bucket Assignment

• Assign according to conversion
{ During the previous migration step (project category/subcategory to portfolio
structure), the category/subcategory objects and their corresponding portfolio
structure objects were stored in a conversion mapping table. This mapping is
used to assign newly created items to a portfolio and bucket. If no mapping is
found, then the item cannot be created.
• Manually assign

July 2007 33
Upgrade Master Guide

{ The new item is assigned to the portfolio and bucket identified on the selection
screen.

Item Type Selection

• Item type for project
{ Select the item type defined for the project from the dropdown list. This field is
mandatory.
• Item type for proposal
{ Select the item type defined for proposal from the dropdown list. This field is
mandatory.

Item/Decision Point Status

• Item Status from Execution status
{ The SAP xRPM 4.0 portfolio item status is populated based on a one to one
mapping with the SAP xRPM 2.0 execution status. If you don't set this indicator,
item statuses are not processed.Decision Point status from Approval status

• Decision Point Status from Approval Status

{ The SAP xRPM 4.0 decision point statuses are populated based on the
approval status of the SAP xRPM 2.0 object which can be a proposal or a
project. Refer to the explanation on Decision Point Status in the previous page.
{ If you set this indicator, you maintain the same item type for proposal and
project in the area Item Type Selection.

cProjects Project Already Exists

This is possible only in the two box scenario. You use the Link Item to cProjects Project
indicator in the following situation:

• You have uploaded a cProjects project for the SAP xRPM 2.0 project and you have
carried out this upload through integration with a cProjects system (in other words,
you link the SAP xRPM 2.0 project to a cProjects project).
•
The xRPM 2.0 project will be migrated as an item to the cProjects system respective
client and since the cProjects project already exists, only a link is established
between the item and the cProjects project and no new cProjects project is created.
Setting this indicator will have the following effect:

• A new cProjects project is not created.

• The SAP xRPM 2.0 project is migrated to the SAP xRPM 4.0 item.
•
The existing cProjects project in cProject 4.0 is linked to this migrated SAP xRPM
4.0 item.
This selection parameter is only valid for a two-box upgrade - meaning that the SAP xRPM
2.0 system is different from the SAP xRPM 4.0 system.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. Enter /RPM/MIGRATION_ITEMS in the Program field and choose Execute.
3. Enter the selection options and choose Execute.

34 July 2007
 Upgrade Master Guide

4. To check that the migration of all SAP xRPM 2.0 projects to portfolio items was
successful, log on to the portal and choose Portfolio Management → Portfolio
Management. Then, on the Object Info pane, select the migrated portfolios from the list
and select the migrated portfolio item from the Item Dashboard.
To make sure that the back-end configurations are correctly replicated in the portal
environment, reload the xRPM cache, which contains the replicated configuration
options. To do this, go to Portfolio Management → Administration → Cache
Administration and choose Invalidate Entire Cache.

If you require a rerun, start the program /RPM/MIGRATION_AUX_TOOLS.

The Delete all Portfolio Items option deletes the portfolio items along with the
cProject project headers for the specified portfolio or portfolio items. After you
have executed this program, you can recreate the portfolio items by running the
program /RPM/MIGRATION_ITEMS.

Additional Information
Authorizations
During the execution of this migration program, authorizations previously assigned to the
stakeholder in the SAP xRPM project are automatically assigned to the SAP xRPM 4.0
portfolio item as follows:
• SAP xRPM 2.0 project manager is assigned as the OWNER and ADMIN of the
portfolio item
• SAP xRPM 2.0 approver is assigned to the portfolio item with WRITE permission
• SAP xRPM 2.0 reviewer is assigned to the portfolio item with READ permission
• The user executing the migration program is assigned to the portfolio item with
ADMIN permission
• You can change portfolio item authorization assignments manually after the migration
has been completed. Log on to the portal and choose Portfolio Management →
Portfolio Management. Then, on the Object Info pane, select the migrated portfolios
from the list and select the migrated portfolio item from the Item Dashboard. Open
the authorizations tray and make the required changes.
cProjects Header
During the execution of this migration program, an item and a cProjects header are
automatically created.The cProjects header later contains the operational data of the SAP
xRPM 2.0 project, for example roles and tasks. The migration program, which is described in
the following section, migrates this operational data to the cProjects header created in this
step.
To check that the creation of the cProjects project header was successful, call the cProjects
application and open the created cProjects projects (the IDs are the same as the xRPM 2.0
project IDs).

Collection
When you execute this migration program, if the project in SAP xRPM 2.0 is a master
project, the system automatically generates a portfolio item and a collection in SAP xRPM
4.0. If the master project in SAP xRPM 2.0 has projects associated with it, the corresponding
portfolio items are assigned to the collection that is created in SAP xRPM 4.0. The portfolio
item created for a master project in SAP xRPM2. is also assigned to the collection that is
created in SAP xRPM 4.0.

July 2007 35
Upgrade Master Guide

To review the collection available to the portfolio item, log on to the portal and choose
Portfolio Management → Portfolio Management. In the Object Info pane, choose Change,
and select the migrated portfolios from the list. To display the collections created, select
Collections. The collection has the same name as that of the portfolio item, but the external
ID is different.
Authorizations for the collection are similar to its corresponding portfolio item.
• SAP xRPM 2.0 project manager is assigned as the OWNER and ADMIN of the
collection
• SAP xRPM 2.0 approver is assigned to the collection with WRITE permission
• SAP xRPM 2.0 reviewer is assigned to the collection with READ permission
• The user executing the migration program is assigned to the collection with ADMIN
permission

If you use the report /RPM/MIGRATION_ITEMS to select a master project in

SAP xRPM 2.0, you must also select all the subprojects of this master project.
If you do not select all subprojects of the master project, the system displays an
error message.

Project Template
Project templates from SAP xRPM2.0 are not transferred to SAP xRPM 4.0 as a part of
migration process.

Attributes from SAP xRPM 2.0 migrated to SAP xRPM 4.0

Object Attributes in SAP xRPM 2.0 Attributes in SAP xRPM 4.0
/cProjects 4.0
Project in • Project name • Item name
xRPM 2.0
to item in • Project ID • Item external ID
xRPM 4.0 • Project description • Description
• Subcategory • Bucket name
• Indicator showing if project is a • Proposal indicator is selected
proposal
• Proposal indicator is not selected
• Indicator showing if project is not a
proposal • Geography

• Geography • Location

• Location • Probability of commercial success

• Probability of commercial success • Probability of commercial success

• Probability of technical success • Currency

• Currency • Unit

• Allocation unit • Plan start date

• Planned start date • Plan finish date

• Planned end date • Actual start date

• Actual start date • Actual finish date

• Actual end date • Comments

36 July 2007
 Upgrade Master Guide

• Comments • Item Status

• Execution Status

Project in • Project ID • cProject Project Name

xRPM 2.0
to project • Project ID • cProject Project Number
header in
cProjects
4.0

Result
Projects in SAP xRPM 2.0 are migrated to portfolio items in SAP xRPM 4.0 and project
headers in cProjects. If master projects exist in SAP xRPM 2.0, they are migrated to
collection objects.

3.1.3.2.3 Migrating Projects to cProjects

Purpose
Migrate the SAP xRPM 2.0 project data to cProjects.

Prerequisites
• Before executing this migration program, the migration of global roles to role functions
must be complete. For more information, see section 3.1.6.1.1.
• Before executing this migration program, the migration of projects to portfolio items
must be complete. For more information, see section 3.1.6.2.2.
• In SAP xRPM 2.0, a project manager was defined via the Stakeholder processes of a
project. Technically, the stakeholder definitions were specific attributes of a project. In
SAP xRPM 4.0, project managers become portfolio item owners and are reviewed and
maintained via the Authorizations tray in the Portfolio Item Details. Portfolio items make
use of access control lists. This migration was already done in the previous migration
step to create portfolio items.

In cProjects 4.0, a project manager is defined by defining a project role first, then
assigning a user to this project role and, finally, assigning this project role to the
Responsible Role field within the cProjects Project Details.

Before executing this migration program, you must configure the role type for the
project manager. You can do this in the cProjects Customizing by choosing
Collaboration Projects → Basic Settings for Project Roles → Define Project Role
Types.

July 2007 37
Upgrade Master Guide

• Perform additional configuration steps for cProjects if necessary in Customizing of

Collaboration Projects.
• The cProjects project updated in this migration step contains the xRPM 2.0 project
task, role and resource assignment information. In this case, the cProjects project is
updated by the SAP xRPM 4.0 project integration scenarios (through upload of project
data from Microsoft Project, SAP PLM PS Project or cProjects. Special attention needs
to be paid to the status network of the cProjects project. If you want to be able to delete
tasks when reuploading project data from a base project system, you must define a
special status profile and assign it to the tasks in cProjects. In standard cProjects
processing, tasks having a certain status cannot be deleted, but you can enable this by
adding a user status, which allows this.

You can define the required status profiles and user status values in Customizing by
choosing Collaboration Projects → Basic Settings → Create/Change Status Profile for
User Status.

When you have defined a status profile that allows deletion of tasks in any status, the
tasks created during the migration need to have the status profile added as an
attribute.

To define which status profiles should be taken on task creation in the migration
process, you can define a default task status profile:

SAP delivers a default status profile entry which you should use when creating
cProjects tasks. You can review this configuration in Customizing by choosing SAP
xApp Resource and PortfolioManagement (SAP xRPM) → Global Customizing →
Check Global Settings.

If you want to use a different status profile, you can define a customer-specific default
status profile in Customizing by choosing SAP xApp Resource and
PortfolioManagement (SAP xRPM) → Global Customizing → Override Default Global
Settings (area 0009, name 0001). Enter the status profile ID in the Settings Value
field.

The status profile configuration is optional, if:

{ No project integration processes were set up
{ Tasks should never be deleted within the project integration upload process
• Phase, task and role processing

When creating the corresponding cProjects phase, task and role objects based on
xRPM 2.0 tasks and roles, you must specify which task and role type values should be
used for the corresponding attributes of tasks and roles.

SAP delivers default phase, task and role types. You can review this configuration in
Customizing by choosing SAP xApp Resource and PortfolioManagement (SAP xRPM)
→ Global Customizing → Check Global Settings (area 0009, name 0002 – 0005).

You define the phase, task and role type values in cProjects Customizing by choosing:
{ Collaboration Projects → Basic Settings → Structure → Define Phase Types
{ Collaboration Projects → Basic Settings → Structure → Define Task Types
{ Collaboration Projects → Basic Settings for Project Roles → Define Project Role
Types

38 July 2007
 Upgrade Master Guide

• If you want to use a different type for each cProjects object, you can define a customer-
specific default type in Customizing by choosing SAP xApp Resource and
PortfolioManagement (SAP xRPM) → Global Customizing → Override Default Global
Settings (area 0009, name 0002 – 0005). Enter the type ID in the Settings Value field.
Process Definition Through Phase Type:
The SAP xRPM 2.0 category-dependent phase configuration is transferred as cProjects
phases to the cProjects project linked to the SAP xRPM 4.0 portfolio item.
Role Type Definition
• In SAP xRPM 2.0, you could document project demand on a project role. Resources
were assigned to these roles according to the period breakdown of the corresponding
role.
• In cProjects 4.0, the same process is available for cProjects project roles. The
configuration of the project role type must be as follows:
{ Staffed by: Resource Manager by Authorization
{ Distribution: X
{ Edit in Parallel:X
• In this case, the cProjects project role offers the same processes as an xRPM 2.0
project role.
• Therefore, you must have a project role type defined in the global settings table, for
which the configuration was maintained.

This is valid for all project roles, except the project manager role. The project
manager role does not have to have any such restrictions.
Status Profile
• When you release an object (for example, project, task, or role) in cProjects 4.0, you
cannot delete the object.To override this function, you must create a status profile that
allows you to delete an object that has been released.

Configuration of the status profile is optional if:

You have not set up any project integration processes.
You do not want to delete objects during the project integration upload
process.
• You define the following status profile in Customizing for Collaboration Projects, by
choosing Basic Settings → Create/Change Status Profile for User Status. Perform the
following steps:
a. Add a new status profile RPMTEST.
b. Enter the following data for the status profile you created above:
Field Data
Status Number 0001
Short Text Allow deletion
Initial Status Select indicator
Lowest Status No. 1

July 2007 39
Upgrade Master Guide

Highest Status No. 1

Position 1
Priority 1
c. For the user status, select the following object types: Business Partner, Project
Defnition, Project Role, Task, Phase, Checklist, Checklist Item.
d. To determine the user status, choose Goto → Transaction Control.
e. For the business transaction Delete, select the Allowed and No Action.

Separate Systems
To transfer data from SAP xRPM 2.0 to SAP xRPM 4.0 when SAP xRPM 2.0 is in a different
system to SAP xRPM 4.0, proceeed as follows:
...

1. In the SAP xRPM 4.0 system, call transaction SM30.

2. To transfer project categories, enter the view V_RPM_TASK_EXST and choose
Maintain.
3. Choose Utilities → Adjustment.
4. Select the SAP xRPM 2.0 system from which you want to retrieve data, and choose
Choose.
5. Select the data that you want to transfer and choose Adjust.
6. The Detail View: Adjust screen appears.
7. Choose Edit → Adjust → Copy All Entries.
8. Save your entries.

Selection Options
General Options
Test Mode (no DB-update)
• If you set the indicator, database updates will not occur.
• If you do not set the indicator, the database will be updated and logs will be stored.

Project Selection
• Project category:
{ Select a project category from the dropdown list. If you leave this field blank,all
project categories are migrated.
• Project subcategory
{ Select a single project subcategory or a range of project subcategories from the
dropdown list. If you leave this field blank, all project subcategories are
migrated.
• Project external ID:
{ Select a single project ID or a range of project IDs from the dropdown list. If you
leave this field blank all projects are migrated.

Project Manager Role Settings

• Role ID for project manager:
o The default role ID PROJECT_MANAGER is proposed, but you can overwrite this value.

40 July 2007
 Upgrade Master Guide

• Role description:
o The default role description Project Manager Role is proposed, but you can
overwrite this value.
• Role type for project manager:
o Select the role type defined for the Project Manager role.
• Role type for others:
o Select the project role type for other roles defined for cProjects.
• Project type:
o Select the project type defined for cProjects
• Phase type:
o Select the phase type defined for cProjects
• Task type:
o Select the task type defined for cProjects

Transfer Integration Based SAP xRPM 2.0 Task Structure

• Under a dummy cProjects phase:
{ If you set this indicator, the system creates a whole SAP xRPM 2.0 task
structure under an artificial phase 'TASK HIERARCHY' in cProjects. No other
phases are created in cProjects.
{ If you do not set this indicator, the system creates phases in cProjects based on
the SAP xRPM 2.0 phases. If the SAP xRPM 2.0 top level task is assigned to an
SAP xRPM 2.0 phase, then the top level task structure is migrated to cProjects
and will fall under the cProjects phase that corresponds to the SAP xRPM 2.0
phase.

Procedure
1. Start transaction SA38 or choose System → Services → Reporting.
2. Enter /RPM/MIGRATION_2_CP_PROJECTS in the Program field and select Execute.
3. Enter the selection options and choose Execute.
4. To verify the projects that have been migrated to cProjects, log on to the Portal, select
Projects and then select the project from the Project Dashboard.

If you require a rerun, start the program /RPM/MIGRATION_AUX_TOOLS.

The option Delete cProjects Projects Only deletes all cProjects projects created
for a previously migrated category. After execution of this program, you can re-
create the portfolio by running the program
/RPM/MIGRATION_2_CP_PROJECTS.

Additional Information
Authorizations
During execution of this migration program, authorizations previously assigned to the
stakeholder in the SAP xRPM project are automatically assigned to the project in cProjects
as follows:

July 2007 41
Upgrade Master Guide

• SAP xRPM 2.0 approved is assigned to the project in cProjects with WRITE
permission
• SAP xRPM 2.0 reviewer is assigned to the project in cProjects with READ permission
• SAP xRPM 2.0 resource manager is assigned to the resource manager authorization
in cProjects
• Project managers in SAP xRPM 2.0 are assigned to the authorization ADMIN in
cProjects.
• To review the migrated cProjects authorization assignments, log on to the Portal,
select Projects and select the project from the Project Dashboard. In the project,
select the Authorization tab.

SAP xRPM Objects Migrated to cProjects

• Project phases:
{ Existing SAP xRPM 2.0 phases are migrated to phases in cProjects 4.0, if
ƒ There are no integration-based SAP xRPM 2.0 tasks.
ƒ There are integration-based SAP xRPM 2.0 tasks and if there are top
level SAP xRPM 2.0 tasks assigned to SAP xRPM 2.0 phases and the
Under a Dummy cProjects Phase indicator is not set.
{ If the project in SAP xRPM 2.0 is assigned to a phase (for example, phase two),
then this phase is set to the Released status in cProjects 4.0. The phases that
come before this phase, for example, phase one, are set to the Completed
status. Phases after the current phase, for example, phase three, are set to
Created.
If the project is not assigned to a phase in SAP xRPM 2.0, all phases are set to
the Created status in cProjects 4.0.
{ If a task structure is present in the SAP xRPM 2.0 project through integration
base, such as an upload from a PS system, and if top level SAP xRPM 2.0
tasks are not assigned to SAP xRPM 2.0 phases. Then the whole task structure
is transferred to cProjects under an artificial phase ‘TASK HIERARCHY’. No
other phases are created in cProjects.
{ If a task structure is present in the SAP xRPM 2.0 project through integration
base, such as upload from a PS system, and if the top level SAP xRPM2.0
tasks are assigned to xRPM2.0 phases:
{ If you set the Under a Dummy cProjects Phase indicator, the system creates a
whole SAP xRPM 2.0 task structure under an artificial phase 'TASK
HIERARCHY' in cProjects. No other phases are created in cProjects.
{ If you do not set the Under a Dummy cProjects Phase indicator, the system
creates phases in cProjects based on the SAP xRPM 2.0 phases. If the SAP
xRPM 2.0 top level task is assigned to an SAP xRPM 2.0 phase, then the top
level task structure is migrated to cProjects and will fall under the cProjects
phase that corresponds to the SAP xRPM 2.0 phase.
• Project tasks:
{ To handle tasks, see Project Phases above.
• Project roles:
{ Existing SAP xRPM 2.0 project roles are migrated to project roles in cProjects.
A project manager role is also created.
• Project resource assignments:

42 July 2007
 Upgrade Master Guide

{ Existing SAP xRPM 2.0 project resource to role assignments are migrated to
resource to project role assignments in cProjects (cProjects BuPa links)
{ Booking status:
ƒ In xRPM 2.0, the booking status (soft-booked or hard-booked) was
maintained on project resource level (independent of the roles to which a
resource was assigned)
ƒ In SAP xRPM 4.0, the corresponding cProjects project stores this
information on the resource to role assignment, which gives more
flexibility and a clearer definition if a resource is hard-booked to all
project roles in question
• Object links:
{ Existing SAP xRPM 2.0 object links for projects, tasks and roles are migrated to
corresponding object links in cProjects
• Stakeholders:
{ xRPM 2.0 project managers are transferred to a project role Project
Manager (including the assignment of the person to that role and the
assignment of that role to the Responsible field in cProjects)
{ xRPM 2.0 resource managers are transferred to a corresponding access
control/authorization list entry on the project header (activity type Resource
Manager)

Note the following details regarding the authorization hierarchy in cProjects:

Case 1 - If in SAP xRPM 2.0 you have the authorization Project Manager,
Approver, and Reviewer, in cProjects, the user should be given the
authorizations Admin, Write, and Read. However, Admin authorization overrules
Write and Read authorizations. This means that the user receives only Admin
authorization.
Case 2 - If in SAP xRPM 2.0 you have the authorization Approver and
Reviewer, in cProjects, the user should be given the authorizations Write and
Read. However, Write authorization overrules Read authorization. This means
that the user receives Write authorization.
Case 3 - If in SAP xRPM 2.0 you have Reviewer authorization, in cProjects, the
user receives Read authoriozation.

Attributes from SAP xRPM 2.0 migrated to SAP xRPM 4.0

Object Attributes in xRPM Attributes in xRPM 4.0 / cProjects 4.0
2.0
Project in • Project description • Description
xRPM 2.0 to
project in • Subcategory • Bucket name
cProjects • Planned start date • Dates: Start, start date
4.0
• Planned end date • Dates: Finish, finish date
• Geography • Area
• Location • Location
• Time unit • Period type

July 2007 43
Upgrade Master Guide

• Allocation Unit • Distribution unit

Phase in • Phase ID (for • Phase number (for example, 0001)
xRPM 2.0 to example, 0001)
project • Phase name (for example, Research)
phase in • Phase text (for
cProjects example,
4.0 Research)

Task in • Task ID (for • Task name

xRPM 2.0 to example, 0001)
project task • Dates: Earliest start, latest start, start date
• Planned start date
in cProjects • Dates: Earliest finish, latest finish, finish date
4.0 • Planned end date
• Actual start date
• Actual start date
• Actual end date
• Actual end date
• Milestone – Indicator is set
• Milestone –
Indicator is set
Role in • Role name • Role name
xRPM 2.0 to
project role • Role ID • Project role ID
in cProjects • Global role name • Function
4.0
• Required from • Start
• Required to • Finish
• Working days • Working days
• Total demand day • Required capacity
• Allocated • Allocated
• Unallocated • Available
• Geography • Area
• Location • Location
• Allocation unit • Time unit
Resource • Resource name • Resource name
managemen
t in xRPM • Assigned from • Start date
2.0 to • Assigned to • End date
project
resource • Allocation unit • Unit
managemen • Booking status • Res. (Indicator is set => Soft booked)
t in cProjects
4.0 • ‘Total’ allocation • Required capacity
summary

Result
Project data in SAP xRPM 2.0 is migrated to a project structure in xProjects.

3.1.3.2.4 Undo – Migration Master Data

44 July 2007
 Upgrade Master Guide

Purpose
You use this function to undo the migration of the following master data:
o Project categories and subcategories in SAP xRPM 2.0 to the portfolio structure in
SAP xRPM 4.0
o Projects in SAP xRPM 2.0 to portfolio items in SAP xRPM 4.0
o Project data in SAP xRPM 2.0 to SAP cProjects 4.0

Prerequisites
Before you use the undo programs to rerverse the migration, the following conditions must be
met:
o To undo the migrated portfolio structure, the portfolio structure must already exist.
Furthermore, the portfolio structure must have been created by the migration process.
o To undo the migrated portfolio items, the portfolio items must already exist.
Furthermore, the portfolio items must have been created by the migration process.
o To undo the migrated project structure cProject project stucture, the cProject Project
structure must already exist. Furthermore, the project structure in cProjects must have
been created by migration process.

Selection Options
• Test mode (no DB update)
• Delete Portfolio with Items
• Select the portfolio for which you want to undo the migration process.This field is
mandatory.
• Delete Item(s)
• Select the item or range of items for which you want to undo the migration
process. If you do not enter any items, the program reverses the migration of all
items that fall under the portfolio.
• If you do enter items, you must select the Delete All Portfolio Items or Delete
cProjects Projects.
• Delete Complete Portfolio
• Deletes all the migrated objects that refer to the portfolio you selected above. If
the portfolio has buckets, items, collections, and projects in cProjects, all these
objects are deleted.
• Delete Portfolio Item(s)
• Deletes the migrated portfolio items and cProjects projects that belong to the
portfolio you selected above.
• Delete cProjects Projects
• Deletes the migrated cProjects projects that belong to the portfolio you selected
above.

Procedure
1. Call transaction SA38 or choose System → Services → Reporting.
2. In the Program field, enter /RPM/MIGRATION_AUX_TOOLS and choose Execute.
3. Enter the required selection options and choose Execute.

July 2007 45
Upgrade Master Guide

4. Review the log file for possible errors and make corrections if required.

Additional Information
Collections
If you select Delete Portfolio Item(s) in the selection options and you enter an item ID that is
part of the collection object, this item is removed from the collection object but the collection
still exists. To delete the collection, you must run the undo migration program without
selecting anything in the Delete Portfolio Item(s) section.

Deleting Projects in cProjects

If you select Delete cProjects Projects the report deletes the entire cProjects project structure
(for example, phases, tasks, roles, resources and the cProjects header). However, at the end
of the run, the program creates a new cProject project header.

Result
The migrated objects you select in the report are deleted in SAP xRPM 4.0.

3.1.3.2.5 Migrating cRoom for Projects to Portfolio Items

Purpose
Migration of cRoom for xRPM 2.0 projects to cRoom for portfolio items in SAP xRPM 4.0.

Prerequisites
o Migration is possible in case of one box upgrade (for example both systems are
deployed on the same portal server)
o Migration is not possible in case of two box upgrade (for example both systems are
deployed on different portal servers).
o Migrate xRPM 2.0 projects to portfolio items in SAP xRPM 4.0 before cRoom
migration.

Selection Options
General Options
• Test mode (no DB-update)
{ If this option is checked, no database updates occur.
{ If this option is unchecked, the database is updated and logs are stored.

Project Selection
• Project category:
{ Select a project category from the dropdown list. If you leave this field blank,
cRoom for all projects are migrated.
• Project subcategory:
{ Select a single project subcategory or a range of project subcategories from the
dropdown list. If you leave this field blank, cRoom for all projects under the
selected categories are migrated.
• Project external ID:

46 July 2007
 Upgrade Master Guide

{ Select a single project ID or a range of project IDs from the dropdown box. If
you leave this field blank, cRoom for all projects are migrated.

Destination
Select the xRPM 2.0 RFC destination string.

Procedure
...

1. Start transaction SA38 or choose System → Services → Reporting.

2. Enter /RPM/MIGRATION_CROOM in the Program field and choose Execute.
3. Enter the selection options and choose Execute.

To migrate cRoom again, run first the program /RPM/MIGRATION_AUX_TOOLS.

This will undo item migration and the cRoom migration. The Delete all Portfolio
Items option deletes the portfolio items, cProject project headers for the
specified portfolio items, and cRoom attached to the portfolio items.
When you have executed this program, you can re-create the portfolio items by
running the program /RPM/MIGRATION_ITEMS. To migrate cRoom once
again, then run the report program /RPM/MIGRATION_CROOM.

Result
cRoom for Projects in SAP xRPM 2.0 are migrated as cRoom for portfolio items in SAP
xRPM 4.0.

3.1.3.2.6 Attachment Migration Tool

Purpose
The Attachments Migration Tool helps in transferring the SAP xRPM 2.0 documents
(attached to projects, roles and tasks) to SAP PPM 4.0. The documents attached to tasks
and roles will be migrated to the corresponding tasks and roles of the associated cProjects
project. The documents that were attached to the main project object can be transferred to
Portfolio Management System and/or cProjects system. This choice is provided in the
Attachments Migration Tool view.

Prerequisites
• Make sure that all the projects, tasks, roles objects of SAP xRPM 2.0 have been
successfully migrated to SAP PPM 4.0.
• Configure Web-Dav repository to the SAP xRPM 2.0 Knowledge Management System.
This has to be done as per the following instructions:
{ Step1: Define a System
Login to the SAP xRPM 4.0 portal with Super Admin role and navigate to
System Administration Æ System Configuration.
In the Detailed Navigation area on the left side, expand the node Knowledge
Management Æ Content Management. Navigate to Global Services Æ System
Landscape Definitions Æ Systems Æ HTTP System.
Click New. Click the link Show Advanced Options.
Give the values to the following properties:

July 2007 47
Upgrade Master Guide

SystemID Unique identifier for this HTTP system. Give a name of your
choice.
Description Description for this system. Give a description of your choice.
Same User Check this box only if the 2.0 KM and the PPM 4.0 are
Domain running on machines on the same domain.
Server URL URL of the portal where the SAP xRPM 2.0 KM is running.
This should be in the format http://SERVER:PORT
User User ID of a user to the above system who has System
Admin and Content Admin rights
Password Password for the above user
After giving the above details, Save the data.
{ Step 2: Define a cache
In the Detailed Navigation area on the left side, expand the node Knowledge
Management Æ Content Management. Navigate to Utilities Æ Caches Æ
Memory cache.
Click New.
Specify a Name, Capacity (around 500 entries) and Assumed Entry Size (for
example 2000) for the cache. Save the data.
{ Step 3: Configure WebDav repository
In this step, you create a WebDav repository that points to the KM repository of
your xRPM 2.0 system. Follow the steps below to configure the WebDav
repository:

In the Detailed Navigation area on the left side, expand the node Knowledge
Management Æ Content Management. Navigate to Repository Managers Æ
WebDAV repository.
Click New.
To see all the options, click the link Show Advanced Options .
Specify a Name and Prefix for the repository. Take a note of this repository
prefix, since you need it later while configuring the iView for the Attachments
Migration Tool.
Select the checkbox Active.
In the System ID dropdown, choose the above created System. In the System
Path text box, specify the path to the documents folder in SAP xRPM 2.0 KM
(For example,
/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/RPMProjects)
Save the data.

Any subsequent changes to this WebDav repository require restarting the J2EE
engine so that the changes are reflected.
{ Step 4: Verify the settings
Under the Detailed Navigation area on the left side, you find Related Links area.
Here, click the link Repositories.

48 July 2007
 Upgrade Master Guide

The repository that was created above should be listed with the name of the
repository prefix. When you click it, the KM content on that system should be
displayed.

You see the list of documents in the WebDav repository only, if you are logged
in as a Super Admin user.

{ Step 5: Configure Attachments Migration Tool

Navigate to Content Administration Æ Portal Content. Expand the node for the
SAP xRPM 4.0 Business Package (Proj. Port. Mgmt. and Design Coll.). Open
iViews Æ Portfolio Management Æ Attachments Migration. Open the iView in
Edit mode. Configure the following properties appropriately:
i. Webdav repository that contains the RPM 2.0 attachments to be
migrated: Specify the repository prefix that you specified in Step 3 above.
ii. System alias for SAP xRPM 4.0 system as configured in the Portal
System Configuration: Specify the alias of the system that is configured
to the PPM 4.0 back-end system. This configuration is done in the
System Administration area in the portal. The value of this property is
SAP_RPM by default.
iii. RFC destination to the SAP xRPM 2.0 system: Specify the RFC
destination that is configured to the SAP xRPM 2.0 system. This
configuration has to be done only if SAP xRPM 2.0 and SAP xRPM 4.0
are running on two different systems.
iv. CM Location to store the PPM documents: If you want to transfer the
project-related documents to the Portfolio Management System 4.0 also,
then specify the CM location for the same.
v. Object link type used to track CM documents in SAP xRPM: Specify the
object link type that has to be used to store the PPM 4.0 documents.
This is also required if the project-related documents need to be
transferred to Portfolio Management System as well.

Procedure
4. Navigate to Portfolio Management Æ Administration Æ Migrate Attachments.
5. Choose the Category and Subcategory under which the documents need to be
migrated.
6. Choose whether to migrate project-related documents to Portfolio Management System
and/or Project Management System (cProjects).
7. Click Start Migration.
8. Check the log to see whether the documents have migrated successfully.

3.1.3.3 Custom iView Migration

Purpose
When you have developed some custom iViews in xRPM 2.0 and you want to use some
standard APIs of xRPM 2.0 in SAP xRPM 4.0, the information below helps you to migrate
xRPM 2.0 custom iViews to SAP xRPM 4.0 environment.

July 2007 49
Upgrade Master Guide

Procedure
1. Get the current Portfolio GUID in SAP xRPM 4.0
xRPM 2.0 SAP xRPM 4.0
Functionality Get current Project ID Get current Portfolio GUID
APIs Use Use getPortfolioGUID() in
getProjectID(IportalComponent com.sap.xapps.cprxrpm.common
Request request) in .cache; class
com.sap.pct.rpm.util.Util; class
Example String currentProjectID = Util. CacheObject _rpmCache = new
getProjectID(request); CacheObject();
byte[] currentPortfolioGuid =
_rpmCache.
getPortfolioGUID();
2. Get the current object in SAP xRPM 4.0.
In SAP xRPM 4.0, application navigation changes current object in the context. The
current object could be Portfolio, Bucket, item, review, decision points and so on. To
retrieve current Object GUID, ID, type or name in current context, you can use the
following methods in com.sap.xapps.cprxrpm.common.cache; class.
Functions Methods
Get current object GUID getRPMObjectGUID()
Get current object ID getRPMObjectID()
Get current object type getRPMObjectType()
Get current object name getRPMObjectName()
3. Place custom iViews on the portal navigation panel in SAP xRPM 4.0.
In SAP xRPM 4.0, you can place custom iViews on the portal navigation panel by using
the same portal configuration as in xRPM 2.0.

50 July 2007
 Upgrade Master Guide

4 References

4.1 Documentation
The following table lists other relevant documentation.
Document Location
Project and Portfolio Management Master SAP Service Marketplace at:
Guide service.sap.com/instguides Æ SAP
xApps Æ SAP xApp Resource and Portfolio
Management Æ SAP xRPM 4.0
ABAP Component Installation Note SAP Note 853692
SAP xRPM 4.0 Java Component Installation SAP Service Marketplace at:
Guide service.sap.com/instguides Æ SAP
xApps Æ SAP xApp Resource and Portfolio
Management Æ SAP xRPM 4.0
Security Guide SAP Service Marketplace at
service.sap.com/securityguide
SAP xRPM Java Component Installation SAP Service Marketplace at
Guide service.sap.com/instguides → SAP
xApps → SAP xApp Resource and Portfolio
Management 4.0
ABAP Component Upgrade Note SAP Note 853694
Upgrade Master Guide: cProject Suite SAP Service Marketplace at
service.sap.com/instguides
ERP Master Guide SAP Service Marketplace at
service.sap.com/instguides
ERP Solution Operations Guide SAP Service Marketplace at
service.sap.com/instguides

July 2007 51