/RPM/MIGRATION_2_CP_PROJECTS - xRPM Migration: Transfer xRPM 2.0 to cProjects 4.0 Project data

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Purpose

The purpose of this step is to migrate the SAP xRPM 2.0 projects to cProjects.

Integration

Prerequisites

  1. You have completed the migration of global role to role function prior to executing this migration program.
  2. You have completed the migration of project to project item prior to executing this migration program.
  3. In SAP xRPM 4.0, the project manager will become the portfolio item owner which you can maintain andreview through the authorizations tray in the portfolio item details. Portfolio items make use of access control ists. This migration was already done in the previous migration step where portfolio items were created.
In cProjects 4.0, a project manager is defined through defining a project role first, then assigninga user to this project role and at the end, assigning this project role to the Responsible Rolefield within the cProjects project details.
The role type for the project manager role must be configured prior to the execution of this migration program.
You configure the role type by choosing Collaboration Projects -> Resource Management -> Basic Settings for Project Roles -> Define Project Role Types.
You configure the project type by choosing Collaboration Projects -> Structure -> Define Project Types.
You configure the phase type by choosing Collaboration Projects -> Structure -> Define Phase Types.
You configure the task type by choosing Collaboration Projects -> Structure -> Define Task Types.
  1. In addition to the role type, you have reviewed and maintained the additional configuration steps forcProjects where necessary prior to the execution of this migration program. You configure cProjects by choosing Collaboration Projects.

Features

Authorizations

  • 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

SAP xRPM Objects Migrated to cProjects

Project Tasks

Existing SAP xRPM 2.0 tasks will be migrated to project tasks in cProjects. The whole SAP xRPM 2.0 taskstructure will be created under an artificial phase 'TASK HIERARCHY' in cProjects irrespective of whether an SAP xRPM 2.0 task is assigned to an SAP xRPM 2.0 phase or not.

Project Roles

Existing SAP xRPM 2.0 project roles will be migrated to project roles in cProjects.

Project Resource Assignment

  • Existing SAP xRPM 2.0 project resource to role assignments will be migrated to resource to project role assignments in cProjects ('cProjects BuPa-Links')
  • Booking status: In SAP xRPM 2.0, the booking status (soft-booked/hard-booked) has been maintainedon a project resource level, independent of the roles to which a resource was assigned. In SAP xRPM4.0, the corresponding cProjects project will store this information on the resource to role assignmentwhich gives more flexibility and a clearer definition, if a resource is committed hard-booked to all project roles in question.

Object Links

Existing SAP xRPM 2.0 Object links for Projects and Tasks will be migrated to corresponding object links in cProjects

Selection

General Settings

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 will be 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 projects subcategories will be migrated.
  • Project External ID
Select a single project ID or a range of project ID's from the dropdown list. If you leave this field blank, all projects will be migrated.

Project Manager Role Settings

  • Role ID for Project Manager
The system proposes the default role ID PROJECT_MANAGER. However, you can overwrite the default if desired.
  • Role Description
The system proposes the role description for the project manager role. However, you can overwrite the default if desired.
  • Role Type for Project Manager
Select the project role type defined for cProjects from the dropdown list.
  • Role Type for Others
  • Project Type
Select the project type defined for cProjects from the dropdown list.
  • PhaseType
Select the phase type defined for cProjects from the dropdown list.
  • Task Type
Select the task type defined for cProjects from the dropdown list.

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 xRPM2.0 phases. If the SAP xRPM 2.0 top level task is assigned to an SAP xRPM 2.0 phase, then the top leveltask structure is migrated to cProjects and will fall under the cProjects phase that corresponds to the SAP xRPM 2.0 phase.

Standard Variants

Output

Based on the selection options, SAP xRPM 2.0 projects data is migrated to cProjects.

Activities

Example



RFUMSV00 - Advance Return for Tax on Sales/Purchases   Vendor Master (General Section)  
This documentation is copyright by SAP AG.


Length: 6702 Date: 20120523 Time: 165351     triton ( 266 ms )