xRPM_Upgrade Master Guide

Upgrade Master Guide

SAP xApp Resource and Portfolio Management (xRPM) 4.0 powered by SAP NetWeaver™

Document Version 1.00 – October, 2005

Material Number 50075486

© Copyright 2005 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. 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

product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. SAP Library document classification: PUBLIC Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/ instguides

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

Typographic Conventions

Type Style Represents

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

Cross-references to other documentation

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

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

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

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

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

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

4 August 2005

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

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

ConfigurationDocumentation Release Notes

ComponentInstallation Guide

ComponentUpgrade Guide


OperationOperation UpgradeUpgrade

Solution ManagementGuide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-phase documentation SAPterm

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

• Target group:

Relevant for all target groups

• Current version:

Located in the SAP 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:

o Consultants

o System administrators

o Project teams for implementations or upgrades


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

Upgrade Master Guide: SAP xRPM

October 2005 5

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

Implementation Guide (IMG)

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

• Target group:

o Solution consultants



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:

o Technology consultants




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:



o Project teams for implementations


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:


6 August 2005




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:




o In SAP Solution Manager

o 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:







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:


o Project teams for upgrades


October 2005 7



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:





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:

o Consultants



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

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

8 August 2005

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


October 2005 9

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

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 .......................................................... 14 3.1.2 Upgrade Sequence............................................................................ 15 3.1.3 Post-Upgrade Activities.................................................................... 15

3.1.3.1 Configuration Migration ........................................................................................17 3.1.3.2 Project Migration....................................................................................................23

4 References....................................................................................36 4.1 Documentation ...............................................................................36

1 Introduction

10 August 2005

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:

o A short introduction to the solution

o Information about mandatory and optional software components and their minimum releases

o 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:

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

o Information about the overall upgrade sequence and subsequent steps

o Preparations and post-upgrade activities, if necessary

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


October 2005 11

1.1 Target Audience This documentation contains both high level information on solution and business scenario level and very 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 Number

Title Description

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 Basis Release 700

This note describes how to install the ABAP add-on component CPRXRPM 400 on SAP NetWeaver 2004s.

853694 Upgrade SAP Basis Release 700 with CPRXRPM 400

This note describes how to upgrade the 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 xRPM 2.0 to xRPM 4.0: New Installation support

This note describes how to migrate date from SAP xRPM 2.0 to SAP xRPM 4.0.

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


12 August 2005

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


October 2005 13

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 cProjects project management business scenarios 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 further 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.


14 August 2005

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

You must install the SAP xRPM ABAP and Java components before upgrading.

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.

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

BaseSystems

SAP Enterprise Portal 7.0(SAP NetWeaver 2004s)

SAP Enterprise Portal 7.0(SAP NetWeaver 2004s)

JCO/RFC

http http

SAP BW 7.0(SAP NetWeaver

2004s)

SAP BW 7.0(SAP NetWeaver

2004s)

SAP xRPM4.0

SAP xRPM4.0

SAP cProjects4.0

SAP cProjects4.0

*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

SAPHCMSAPHCM

SAPFI/COSAP

FI/COProject

Management*Project

Management*Time

Management**Time

Management**

SAP xAppProduct

Definition(xPD) 2.0

SAP xAppProduct

Definition(xPD) 2.0

ALE / RFC / SAP XIALE / RFC / SAP XI


October 2005 15

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 cProjects 4.0 role functions

Required, because the result is used in migration of SAP xRPM 2.0 master data migration programs.

2 Transfer SAP xRPM 2.0 geographical location and physical location configuration to corresponding cProjects 4.0 configuration tables

Required.

3 Transfer SAP xRPM 4.0 capacity management configuration data

Required if capacity management processes were used in SAP xRPM 2.0.

4 Transfer SAP xRPM 2.0 object link type configuration data to cProjects 4.0 configuration tables

Required.

Master Data Migration Step Action Remarks

1 Transfer SAP xRPM 2.0 project category and sub-categories to a portfolio structure.

Required.

2 Link SAP xRPM 2.0 projects to the newly created portfolios.

Required.

3 Create a cProjects project structure based on operational SAP xRPM 2.0 project data.

Required.

4 Undo master data migration runs. Optional.

This step enables you to re-run 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 details about the ABAP component, see SAP Note 853692 For details 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


16 August 2005

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.

Optional Features To test SAP xRPM 2.0 upgrade data, the migration programs are designed to read the data from a sub-system.

To make use of this functionality, specify the RFC destination in all applicable migration programs. When doing this, all configuration tables of the RFC destination must be replicated to the system where you execute the migration program. This includes business partner IDs and assignments to corresponding users and employee ID.

To execute the RFC option, certain function modules must be available in the SAP xRPM 2.0 system. For further information, see SAP Note 858789. Do not use this option in a production environment.

If you use this feature and run the undo program /RPM/MIGRATION_AUX_TOOLS, flag the parameter Items created from sub-system to delete previously created SAP xRPM 4.0 migration objects.

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 xRPM 4.0 installation, you need to process the activites in the sections of the SAP xRPM Implementation Guide (IMG) listed below. In this case, migration is not possible.

• 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 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 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


October 2005 17

Customizing → Global Settings → Override Default Global Settings View V_RPM_SET_VAL_C (transaction SM30)

• Category customzing: 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 opertional 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 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 only supported migration process is upgrade from SAP xRPM 2.0 to SAP xRPM 4.0. You should only perform migration of an existing SAP xRPM 2.0 system to a new SAP xRPM 4.0 system, enabled by the migration program through the parameter RFC destination (test only) as a test feature to reduce the system downtime for the actual migration process.

The following sections describe the migration steps needed to make use of the various new features available in 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


18 August 2005

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 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 xRPM 4.0 only a role template can be used to create a project role (using project role templates as defined in cProjects)

o The hierachical grouping of roles within global roles available in SAP xRPM 2.0 has been simplified in xRPM 4.0. It is now sufficient to define global roles as a flat list.

o The purpose of a global role/role function in 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

o SAP Business Information Warehouse (BW) reporting capabilities linked to a global role remain the same

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. To validate and/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


October 2005 19

Additional Information You can also configure role functions manually via the cProjects IMG step 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.

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



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


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:

o Choose Display to view the locations

o Choose Maintain to add, delete or modify locations

You can also to 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.


20 August 2005

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 • You can also configure locations and areas manually via the following IMG steps

o SAP xApp Resource and Portfolio Management (SAP xRPM) → Global Customizing → Project Settings → Define Areas

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


October 2005 21

• 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

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.

Prerequisites None




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.



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: o Choose Display to view the locations

o 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 to include the locations in a transport request.

Additional Information You can also configure global settings for capacity management via the cProjects IMG step 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


22 August 2005

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 In 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 desitionation has been maintained

• Standard types from SAP xRPM 2.0, which do not exist in SAP xRPM 4.0, are created

Prerequisites None




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.



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:


October 2005 23

o Existence of all required object link types (standard types as well as those in the customer name range)

o 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)

o 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 Groupings. From the table maintenance of table view V_DPR_OBGRP_INT, you can: o Choose Display to view the settings

o Choose Maintain to add, delete or modify settings You can also to include the settings in a transport request from the relvant view or view cluster.

Additional Information • You can configure object link types via the IMG step 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 via the IMG step 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 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


24 August 2005

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

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 via the IMG step 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 xRPM 4.0 portfolio structure, you should review these services and configure them accordnigly.

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. xRPM 4.0 offers an extended range of navigation options. For each portfolio item, review and collection object, you can now define the navigation for each portfolio and each role.

You can configure the navigation configuration via the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Global Customizing → Process and Service Settings -> Define Navigation.


October 2005 25


Financial/Capacity Categories and Groups

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

You define financial/capacity categories and groups via the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Global Customizing → Portfolio Independent Settings -> Define Financial and Capacity Categories.

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 and groups via the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Global Customizing → Portfolio Dependent Settings -> Define Portfolio Types.


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 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 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 the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Global Customizing -> Global Field Settings -> Define Custom Field Configuration.

In the IMG step 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.

In xRPM 4.0, you can also:

• Restrict the available time units to those which are really needed in portfolio processes:


26 August 2005

o To review available units of measurement, go to the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Global Settings → Define Units of Measurement

o To define to which units portfolio processes should be restricted to, go to the IMG step 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

o To define to which units portfolio processes should be restricted to, go to the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Portfolio Independent Setting → Define Currency Units

In general, you should review the following IMG sections to evaluate the new features available in xRPM 4.0 and find out what you need to do before creating the 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 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

Which fields you want to display on the portfolio, bucket, item and review user interface

Selection Options

General Options

• Test mode (no DB-update)


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

Migration Options

Option Effect

1 In this case, a new portfolio is created:

• 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 sub-buckets

Parameters:

• Portfolio external ID In order to facilitate the creation of a new portfolio, an entry must be made for the external ID. The field length is limited to 24 characters.


October 2005 27

• Portfolio Name A name must be entered for the new portfolio. The field length is limited to 40 characters.

2 In this case:

• 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

3 In this case:

• 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 dropdown list.


2. Enter /RPM/MIGRATION_CATEGORIES in the Program field and choose Execute.


If you require a re-run, 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 sub-buckets in the portfolio.


28 August 2005

5. To review the configuration possibilities in the SAP xRPM 4.0 frontend application, you can review the navigation definition via the IMG step SAP xApp Resource and Portfolio Management (SAP xRPM) → Process and Service Settings → Define Navigation. To make sure that the backend 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.

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

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 the IMG. They define general processes for portfolio items.

You must configure item types before executing this migration program. You can do this via the IMG step SAP xApp Resource and PortfolioManagement (SAP xRPM) → Global Customizing → Portfolio Independent Settings → Define Portfolio Item Types.

Portfolio Structure

You must create the portfolio structure before executing this migration program.

For further 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 further 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 further 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:


October 2005 29

• 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 further information about how to define customer includes in SAP xRPM 4.0, see the IMG step SAP xApp Resource and PortfolioManagement (SAP xRPM) → Business Add-Ins and Customer Includes → Customer Includes. cProjects Project Type

In 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 xRPM 4.0 item has a corresponding cProjects project, which is directly assigned to the portfolio item.

The project to item migration program creates a cProjects project for each xRPM 2.0 project and links it to the 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 the IMG step 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 IMG step 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 the IMG step 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, questionaires, 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 IMG steps 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


30 August 2005

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.

Selection Options

General Options




Project Selection

• Project external ID:

o 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 category:

o Select a project category from the dropdown list. If you leave this field blank, all project categories are migrated.

• Project subcategory:

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

Portfolio and Bucket Assignment

• Assign according to conversion

o 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

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

Item Type Selection

• Item type for project

o Select the item type defined for the project from the dropdown list

• Item type for proposal


October 2005 31

o Select the item type defined for proposal from the dropdown list


2. Enter /RPM/MIGRATION_ITEMS in the Program field and chooset Execute.


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 backend 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 re-run, 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_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 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.

Decision Points

During the execution of this migration program, decision points are automatically generated for the portfolio item. Manual adjustment is required once the migration is completed.

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.

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 (roles, tasks, …). The migration program, which is described in the following section, migrates this operational data to the cProjects header created in this step.


32 August 2005

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

Result SAP xRPM 2.0 projects are migrated to SAP xRPM 4.0 portfolio items

3.1.3.2.3 Migrating Projects to cProjects Purpose Migrate the SAP xRPM 2.0 projects to cProjects.

Prerequisites • Before executing this migration program, the migration of global roles to role functions

must be complete. For further information, see section 3.1.6.1.1.

• Before executing this migration program, the migration of projects to portfolio items must be complete. For further 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 via the cProjects IMG step Collaboration Projects → Basic Settings for Project Roles → Define Project Role Types.

• Perform additional configuration steps for cProjects if necessary IMG step 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 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 re-uploading 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 additing a user status, which allows this. You can define the required status profiles and user status values in the IMG step 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 prtofile:


October 2005 33

SAP delivers a default status profile entry which you should use when creating cProjects tasks. You can review this configuration in the IMG step 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 the IMG step 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:

o No project integration processes were set up

o 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 the IMG step 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 the following cProjects IMG chapters:

o Collaboration Projects → Basic Settings → Structure →Define Phase Types

o Collaboration Projects → Basic Settings → Structure →Define Task Types

o Collaboration Projects → Basic Settings for Project Roles → Define Project Role Types

If you want to use a different type for each cProjects object, you can define a customer-specific default type in the IMG step 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:

In xRPM 2.0, phases were attributes of project. In xRPM 4.0, you can transfer the possible phases and the currently set phase value of a project to the cProjects project.

The xRPM 2.0 category-dependent phase configuration is transferred to the cProejcts project linked to the xRPM 4.0 portfolio item.

The decision processes available in xRPM 2.0 are thus transferred to cProjects project phase processing, which offers a more extensive approval process than available in xRPM 2.0.

Role Type Definition

In 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. However, the period breakdown is enabled on a cProjects project role only if a project role type is assigned to a project role, and if the configuration of this project role type is as follows:

o Staffed by: Resource Manager by Authorization


34 August 2005

o Distribution: X

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

Selection Options

General Options




Project Selection

• Project external ID:

o 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 category:

o Select a project category from the dropdown list. If you leave this field blank,all project categories are migrated.

• Project subcategory

o 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 Manager Role Settings

• Role ID for project manager:

o The default role ID PROJECT_MANAGER is proposed, but you can overwrite this value.

• Role description:

o The default role description Project Manager Role is proposed, but you can overwrite this value.

• Project role type:

o Select the project role type defined for cProjects from the dropdown list.


2. Enter /RPM/MIGRATION_2_CP_PROJECTS in the Program field and select Execute.

3. Enter the selection options and chosoe 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 re-run, start the program /RPM/MIGRATION_AUX_TOOLS. The option Delete cProjects Projects Only deletes all cProjects projects created for a previously ligrated category. After execution of this program, you


October 2005 35

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:

• SAP xRPM 2.0 approver 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

• 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 tasks:

o Existing SAP xRPM 2.0 tasks are migrated to project tasks in cProjects

• Project roles:

o Existing SAP xRPM 2.0 project roles are migrated to project roles in cProjects

• Project resource assignments:

o Existing SAP xRPM 2.0 project resource to role assignments are migrated to resource to project role assignments in cProjects (cProjects BuPa links)

o 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 xRPM 4.0, the corresponding cProjects project stores this information on the resource to role assignment, which gives more flaxibility and a clearer definition if a resource is hard-booked to all project roles in question

• Object links:

o Existing SAP xRPM 2.0 object links for projects and tasks are migrated to corresponding object links in cProjects

• Stakeholders:

o 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)

o xRPM 2.0 resource managers are transferred to a corresponding access control/authorization list entry on the project header (activity type Resource Manager)

Result SAP xRPM 2.0 projects are migrated to cProjects


36 August 2005

4 References

4.1 Documentation The following table lists other relevant documentation.

Document Location

Project and Portfolio Management Master Guide

SAP Service Marketplace at: 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 Guide

SAP Service Marketplace at: 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 Guide

SAP Service Marketplace at 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

xRPM_Upgrade Master Guide

Documents

object info

object link

upgrade master

object link

database updates

sap netweaver

single project

start transaction