configuration content for sap xrpm 4.0 sp0 (from sdn)

Configuration Content for SAP xRPM

Release 4 .0

AD

DO

N.C

G_

XA

PP

S

SAP Online Help 22.10.2005

Configuration Content for SAP xRPM 4.0 2

Copyright © Copyright 2004 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.



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

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

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and 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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



Contents Configuration Content for SAP xRPM ............................................................................................. 7

Activating Business Content Data Sources ................................................................................. 8 Global Customizing...................................................................................................................... 9

Global Settings ....................................................................................................................... 10 Checking Global Settings ................................................................................................... 11 Overriding the Default Global Settings ............................................................................... 13 Defining Employee Name Format ...................................................................................... 15 Assigning Status Icons to Customer Fields ........................................................................ 17 Defining Units of Measurement .......................................................................................... 18 Activating Workflows........................................................................................................... 20

Portfolio Independent Settings ............................................................................................... 22 Defining Portfolio Item Types.............................................................................................. 23 Defining Financial and Capacity Categories....................................................................... 25 Defining Capacity Units ...................................................................................................... 27 Defining Currency Units...................................................................................................... 28 Defining Period Types ........................................................................................................ 29 Defining Portal Roles .......................................................................................................... 30

Process and Service Settings ................................................................................................ 31 Defining Object Search....................................................................................................... 32 Defining Services................................................................................................................ 34 Defining Questionnaires ..................................................................................................... 36 Defining Scoring Models..................................................................................................... 37 Defining Navigation............................................................................................................. 38

Global Field Settings .............................................................................................................. 40 Checking Object Types and Supported Structures ............................................................ 41 Checking SAP Field Configuration ..................................................................................... 42 Defining Custom Field Configuration.................................................................................. 43

Portfolio Dependent Settings.................................................................................................. 44 Defining Portfolio Types...................................................................................................... 45

Project Settings ...................................................................................................................... 47 Defining Project Categories ................................................................................................ 48 Defining Areas .................................................................................................................... 50 Defining Locations .............................................................................................................. 51 Defining Project Alerts ........................................................................................................ 52

Base System Interfaces ............................................................................................................. 54



Application Object Settings .................................................................................................... 55 Defining RFC Connections ................................................................................................. 56 Defining Logical Ports......................................................................................................... 58 Defining Logical Systems ................................................................................................... 59 Defining the Web Server Alias............................................................................................ 60 Defining Object Link Type Groupings................................................................................. 61 Defining Object Link Types................................................................................................. 62 Assigning Base System Applications to Application Areas ................................................ 63 Assigning Object Link Type Groupings to Applications...................................................... 64 Defining Field Mapping ....................................................................................................... 65

SAP Product Lifecycle Management - Project System Integration ........................................ 66 Data Distribution from SAP PLM PS to SAP xRPM ........................................................... 68

Uploading Work Centers From SAP PLM PS................................................................. 69 SAP cProjects Integration ...................................................................................................... 70 SAP xApp Product Definition Integration ............................................................................... 72

Mapping Templates to Item Types and Decision Points .................................................... 75 Mapping Metrics and Value Types ..................................................................................... 76

Microsoft Project Integration................................................................................................... 77 Configuring Microsoft Project Server 2003......................................................................... 81

SAP Human Capital Management Integration ....................................................................... 84 Common System Configuration and SAP HCM ALE Setup............................................... 86 SAP HCM System ALE Setup ............................................................................................ 87

Maintaining the Distribution Model.................................................................................. 88 Distributing Customizing Data......................................................................................... 89

SAP xRPM System ALE Setup for SAP HCM.................................................................... 91 Checking Supported Message Types and IDoc Types................................................... 92 Mapping Message Types................................................................................................ 93 Mapping IDoc Types ....................................................................................................... 94 Changing Inbound Parameter of Partner Profile............................................................. 95 Setting up SAP HCM Integration with SAP cProjects..................................................... 96

SAP xRPM System Customizing for SAP HCM ................................................................. 97 Setting Up Business Partners ......................................................................................... 98 Qualifications Catalog ..................................................................................................... 99

Distributing Data to SAP xRPM by ALE Customizing ............................................... 100 Distributing Data to SAP xRPM by Client Comparison ............................................. 101 Distributing Data to SAP xRPM by Direct Entry ........................................................ 102

Employee Data Configuration ....................................................................................... 103



Defining Permitted Relationships .............................................................................. 104 Assigning Subprofiles to Business Partners ............................................................. 105

Data Distribution from SAP HCM to SAP xRPM .............................................................. 106 Creating Evaluation Paths............................................................................................. 107 Checking iDoc Status.................................................................................................... 109 Checking Inbound Processing ...................................................................................... 110 Mapping Personnel Areas to Locations ........................................................................ 111

SAP Financial and Controlling Integration ........................................................................... 112 Common System Configuration and SAP FI-CO ALE Setup ........................................... 113 SAP FI-CO System ALE Setup......................................................................................... 114

Maintaining the Distribution Model................................................................................ 115 SAP xRPM System ALE Setup for SAP FI-CO ................................................................ 116

Checking Inbound Process Code Settings ................................................................... 117 Changing Inbound Parameter of Partner Profile........................................................... 118

SAP xRPM System Customizing for SAP FI-CO.............................................................. 119 Customizing the Organization Type.............................................................................. 120 Customizing Value Types ............................................................................................. 121

Data Distribution from SAP FI-CO to SAP xRPM............................................................. 122 Checking IDoc Status.................................................................................................... 123 Checking Inbound Processing ...................................................................................... 124 Updating Project Cost and Budget in SAP xRPM......................................................... 125

User Management ................................................................................................................... 126 Creating SAP xRPM Roles................................................................................................... 127 Creating SAP xRPM Users .................................................................................................. 128

Utilities...................................................................................................................................... 130 Displaying Project Data ........................................................................................................ 131 Employee Overview ............................................................................................................. 132 Updating Project Dashboard Data ....................................................................................... 134

Business Add-Ins ..................................................................................................................... 135 Customer Includes ................................................................................................................... 136



Configuration Content for SAP xRPM



Activating Business Content Data Sources Use Here, you activate the Business Content data sources for the SAP xRPM source system.

Procedure In the SAP xRPM Implementation Guide, go to Activating Business Content Data Sources and execute the following activities: ...

1. Transfer Application Component Hierarchy

In this step, you transfer and activate the application component hierarchy delivered by SAP and, if applicable, any partner application hierarchies.

2. Transfer Business Content DataSources

In this step, you transfer and activate the data sources delivered by SAP as well as partner data sources delivered in your own namespace, if applicable.

For all connected SAP Business Information Warehouse (BW) systems, you can then extract and transfer data from data sources activated and replicated into the current SAP BW.

For further information, see the relevant documentation on SAP Help Portal: ...

1. Go to http://help.sap.com → Documentation → SAP NetWeaver.

2. Select appropriate release.

3. Choose Information Integration → SAP Business Information Warehouse.



Global Customizing Purpose This process describes the necessary steps for SAP xRPM global customizing.

Process Flow ...

1. Global Settings [Page 10]

2. Portfolio Independent Settings [Page 22]

3. Process and Service Settings [Page 31]

4. Global Field Settings [Page 40]

5. Portfolio Dependent Settings [Page 44]

6. Project Settings [Page 47]



Global Settings Purpose This process describes how to define global settings.

Process Flow Go to the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Global Settings and follow the instructions in the steps below: ...

1. Checking Global Settings [Page 11]

2. Overriding the Default Global Settings [Page 13]

3. Defining Employee Name Format [Page 15]

4. Assigning Status Icons to Customer Fields [Page 17]

5. Defining Units of Measurement [Page 18]

6. Activating Workflows [Page 20]



Checking Global Settings Use In this step, you can check the global settings delivered by SAP.

You do not normally need to change these settings, but you can override some of them with your own values.

For further information, see Overriding the Default Global Settings [Page 13].

Procedure To view the SAP default values, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Global Settings → Check Global Settings.

The SAP default settings are as follows:

Area Description Setting Description SAP Default

0001 Weekly calendar heading W

0002 Monthly calendar heading M

0003 Default allocation unit H

0004 Calendar breakdown MONTH

0009 Hours per day for FTE definition

8

0010 Default factory calendar ID 99

0001 Capacity Management

0011 Standard unit for hour H

0002 Master Switches

0002 Resource pools No default value

0003 IT0007<#> - value used to calculate FTE

5

0004 Default position of HCM system

99999999

0003 HR Integration

0005 Employee role of business partner

BUP003

0001 Default role SAP_RPM_PROJECT_MEMBER

0002 Default user group RPMUSER

0004 User Management

0003 Create user during HCM ALE distribution

No default value

0001 Person ID I

0002 Name format, default country US

0006 User Interface Settings

0003 Name format, default format ID

00



0001 Currency exchange rate type M 0007 General Default Values

0002 Exchange rate RFC destination

No default value

0001 Default Status Profile for Portfolio Item Project Plan

RPMTEST

0002 Default cProjects Project Type

000000000000RPM

0003 Default cProjects Task Type

000000000000RPM

0004 Default cProjects Role Type

000000000000RPM

0009 Portfolio Item Project Integration

0005 Default cProjects Phase Type

000000000000RPM



Overriding the Default Global Settings Use In this step, you can override the default global settings delivered by SAP with your own preferred values.

Procedure ...

1. In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Global Settings → Override Default Global Settings.

2. Choose New Entries.

3. In the Area and Name columns, enter an area and a name or choose values from the dropdown lists.

4. In the Settings Value column, enter the value you want to use to override the default.

5. Save your entries.

Default Settings and Possible Values

Area 0001 - Capacity Management:

Setting Description SAP Default Possible Values

0001 Weekly calendar heading W

0002 Monthly calendar heading M

0003 Default allocation unit H Any unit defined in table T006.

0004 Calendar breakdown MONTH WEEK

MONTH

0009 Hours per day for FTE definition 8

0010 Default calendar ID 99

0011 Standard unit for hour H

For further information about maintaining factory calendar IDs, see Maintaining the Calendar [External].

For further information about allocation units, see Defining Units of Measurement [Page 18].

Area 0002- Master Switches:


0002 Resource pools No default value

No value

X

Area 0003- HR Integration:


0003 IT0007 value used to calculate FTE 5



0004 Default position in SAP HCM System 99999999

0005 Employee role of business partner BUP003

Area 0004- User Management:


0001 Default role SAP_RPM_PROJECTMEMBER

0002 Default user group RPMUSER

0003 Create user during HCM ALE distribution

No default value No value

X

Area 0006- User Interface Settings:


0001 Person ID I No ID

I (employee ID)

B (business partner ID)

U (user)

0002 Name format, default country US

0003 Name format, default format ID 00

Area 0007- General Default Values:


0001 Currency exchange rate type M M

0002 Exchange rate RFC destination No default value

For further information about maintaining the currency exchange rate type, go to the SAP Reference IMG and choose General Settings → Currencies → Check exchange rate types.

For further information about defining the RFC destination to get the currency exchange rate, see Defining Target Systems for RFC Calls [Page 56].

If you do not define an exchange rate type or an RFC destination for determining the exchange rate, the currency conversion function module RPM_GET_CURRENCY_EXCHANGERATES uses standard values.

Area 0009 – Portfolio Item Project Integration:


0001 Default Status Profile for Portfolio Item Project Plan

RPMTEST

0002 Default cProjects Project Type 000000000000RPM

0003 Default cProjects Task Type 000000000000RPM

0004 Default cProjects Role Type 000000000000RPM

0005 Default cProjects Phase Type 000000000000RPM



Defining Employee Name Format Use In this step, you define the format of employee names for each country.

SAP delivers predefined employee name formats, so you can either accept the standard settings or define your own.

If you do not make any changes, the standard setting applies.

Procedure ...

1. In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Global Settings → Define Employee Name Format.

2. Create the required name formats or change the existing name formats.

Creating a Name Format ...


2. In the Cty column, enter a country value.

3. In the Format column, enter a format number.

4. Select the new name format and double-click on Name Format Fields.


6. In the Position column, enter a position for the field.

7. In Field Name column, select the field you want to see in that position from the dropdown list.

8. Choose Save.

Changing an Existing Name Format ...

1. Select the name format you want to change.

2. Double-click on Name Format Fields.

3. To add more fields, choose New Entries and enter appropriate values in the Cty and Format columns.

4. To change existing fields, select the field you want to change and select a different field from the dropdown list.

5. Choose Save.

Example The US 01 name format could contain the following fields:

Position Field Name

1 Title

2 First Name



3 Middle Initial

4 Last Name

In this case, all US names would be formatted like Mr. Michael R. Willis.



Assigning Status Icons to Customer Fields Use In this step, you assign status icons to customer fields.

SAP delivers a standard set of status icons.

Prerequisites The customer fields must already be defined.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Global Settings → Assign Status Icons to Customer Fields.

2. For each status icon you want to assign to a custom field: ...

a. In the Table Name column, select a valid custom structure from the dropdown list box.

b. In the Field Name column, select a custom field name from the dropdown list box.

c. In the Field Value column, select a field value from the dropdown list box.

This is the field to which an icon is to be assigned.

d. In the Icon column, select a status icon from the list of icons in the dropdown list box.

e. Save your entries.



Defining Units of Measurement Use In this step, you define units of measurement to calculate quantities and physical units for internal display and internal conversion purposes. In the standard delivery system, units of measurement are defined according to the international system of units (SI), which is based on seven basic units of measurement. All other units are derived from these seven basic units. Units of measurement that measure the same quantity (and can therefore be converted to each other) are included in one dimension. The SAP system holds units of measurement centrally for all applications. The conversion factors are stored in the system with a unique internal key. The external display specifications are language-specific for each unit of measurement. For each language, there should be a three-character business key and a six-character technical key.

If you intend to perform cross-company data exchange, be aware that units of measurement with company-specific characteristics may have an adverse effect.

• For initial installations, units of measurement are delivered in all clients

• For upgrades, new units of measurement are delivered only in client 000.

You must then transport these new units to your production clients.

Procedure Check that the delivered dimensions and the associated units of measurement are complete. If you are using EDI, you should also check the ISO codes.

To do this, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Global Settings → Define Units of Measurement and then follow the appropriate steps below.

Dimensions ...

On the initial screen, choose Dimensions. • To see the definition for a dimension, select the dimension and choose Details.

• To create a dimension, choose New Entries.

Units of Measurement ...

On the initial screen, choose Units of measurement. • To see the definition for a unit of measurement, select the unit of measurement and choose

Details.

• To create a unit of measurement according to the international system of units (SI), choose Create.

Here you have to enter details in the following boxes:

Display

Measurement unit text

Conversion



This does not apply to units of measurement without dimensions.

ALE/EDI

This is optional.

Application parameters

ISO Codes ...

On the initial screen, choose ISO codes. To create a new unit of measurement according to the international system of units (SI), choose Create.

To create an ISO code, choose New Entries.



Activating Workflows Use In this step, you activate SAP xRPM workflow processes.

Workflows start as reactions to events triggered by the application. To define the organizational responsibility for processing, you must specify an agent for each workflow. If a scenario requires a workflow, you must assign this workflow to an agent.

If you want to establish the link between an event and a workflow or tasks defined by SAP, you must activate this link.

Prerequisites Central workflow customizing must be complete.

For further information, go to the SAP Help Portal at http://help.sap.com and choose Documentation → SAP NetWeaver → <release> → Application Platform → Business Services → SAP Business Workflow → Role Documentation → Roles in Workflow → Workflow System Administrator → Business Workflow Administration → Workflow System Administration.

• For information about workflow customizing, choose Automatic Workflow Customizing

• For information about classifying tasks, choose Customizing for Tasks and Workflows

Procedure ... ...

1. In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Global Settings → Activate Workflows.

2. Select the application component XAP-RPM.

3. Perform the following main steps:

Assign agents to tasks

Activate links between events and tasks

Assigning Agents to Tasks ... ...

1. Choose Assign Agents.

2. Select a task for processing.

3. Choose Create agent assignment.

This determines the total number of persons who are allowed to process this task.

You can make multiple assignments or you can classify a task as a general task.

4. Select an agent.

You have the following options:

Job

Organizational unit

Position

Role

Task



User

Work center

Activating Links Between Events and Tasks ...

1. Choose Activate event linking.

2. Select a task or workflow for processing.

Only some workflows and tasks have triggering events. This is indicated by the symbol in front of the name.

3. Activate the link.

This determines which of the links you want to use.

Usually, you assign an organizational unit, a job or a position to a workflow, so if personnel changes occur in the organizational plan, no changes are required in the workflow components.



Portfolio Independent Settings Purpose This process describes how to define portfolio independent settings.

Process Flow Go to the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Portfolio Independent Settings and follow the instructions in the steps below: ...

1. Define Portfolio Item Types [Page 23]

2. Define Financial and Capacity Categories [Page 25]

3. Define Capacity Units [Page 27]

4. Define Currency Units [Page 28]

5. Define Period Types [Page 29]

6. Define Portal Roles [Page 30]



Defining Portfolio Item Types Use Here, you can define portfolio item types and link them to one or more decision points.

• A portfolio item type is a grouping of portfolio items, which follow the same process

For example, one portfolio item type could cover portfolio items that are associated with the same base system or share the same phases. In this case, you could assign each portfolio item type to a specific application.

• A decision point is a phase through which each portfolio item type passes

Possible decision points could be Specification, Design, or Implementation.

Each decision point can have up to five possible status values that you can configure in the frontend application. Examples of status values include:

Not Active

In Preparation

In Progress

For Review

Approved

Interaction of decision points and status values:

When a portfolio item type has passed through all the stages of a decision point and the status value is set to Approved, the current decision point becomes inactive. At the same time, the next decision point becomes active and its status value is set to In Preparation.

The status value of a decision point is set to Not Active only if the portfolio item type is passing through a decision point for the first time.

Prerequisites There is no default configuration. Portfolio item types and decision points are freely definable and you can link portfolio item types to as many decision points as you like.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Independent Settings → Define Portfolio Item Types.

You can:

• Define portfolio item types

• Edit portfolio item types

Defining Portfolio Item Types ...


2. In the Item Type column, enter an item type.

3. In the Area column, select the base system to which you want to assign the item type.

4. If you want to define the item type as a proposal, check the box in the Proposal column.



Doing this means that all portfolio items assigned to this item type are displayed on the Proposals tab of the Item Dashboard in the frontend application.

5. Select the item type and double-click on Link Item Type and Decision Point.

6. In the Decision Point and Decision Point Name columns, enter a decision point and a suitable description.

7. Save your changes.

Editing Portfolio Item Types • To edit a portfolio item type description, overwrite the existing text

• To edit the decision points attached to a portfolio item type, select the portfolio item type and double-click on Link Item Type and Decision Point

To add a new decision point to the portfolio item type, choose New Entries, and enter a decision point and a suitable description

To edit an existing decision point, overwrite the existing decision point name

Always save your changes.



Defining Financial and Capacity Categories Use Here, you define financial categories and capacity categories:

• A financial category is a monetary grouping such as costs or revenue

• A capacity category is a resource grouping such as development, quality management, or product management

You can link financial categories to any number of financial groups and capacity categories to any number of capacity groups.

• A financial group is a subordinate grouping of a financial category

• A capacity group is a subordinate grouping of a capacity category

There is no default configuration. Financial categories and capacity categories are freely definable.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Independent Settings → Define Financial and Capacity Categories.

You can:

• Define financial categories

• Edit financial catagories

• Define capacity categories

• Edit capacity categories

Defining Financial Categories ... ...


2. In the Financial Category and Category Text columns, enter a financial category and a suitable description.

3. Select the financial category and double-click on Financial Groups.

4. In the Financial Group and FI Group Text columns, enter a financial group and a suitable description.


Editing Financial Categories

• To edit a financial category text, overwrite the existing text

• To edit the financial groups attached to a financial category, select the financial category and double-click on Financial Groups

To add a new financial group to the financial category, choose New Entries, and enter a financial group and a suitable description

To edit an existing financial group, overwrite the existing group text.




Defining Capacity Categories ...


2. In the Capacity Category and Category Text columns, enter a capacity category and a suitable description.

3. Select the capacity category and double-click on Capacity Groups.

4. In the Capacity Group and Capacity Group Text columns, enter a capacity group and a suitable description.


Editing Capacity Categories

• To edit a capacity category text, overwrite the existing text and save your changes

• To edit the capacity groups attached to a capacity category, select the capacity category and double-click on Capacity Groups

To add a new capacity group to the capacity category, choose New Entries, and enter a capacity group and a suitable description

To edit an existing capacity group, overwrite the existing group text.




Defining Capacity Units Use Here, you can define capacity units.

Capacity units are units of measurement for calculating quantities and physical units for internal display and internal conversion purposes.

There is no default configuration, but SAP delivers a set of time units, which are actually a subset of the standard set of capacity units.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Independent Settings → Define Capacity Units.

You can define new capacity units or edit existing ones.

To define a new capacity unit: ...


2. In the Demand Unit column, select a value from the dropdown box..


You can edit an existing capacity unit by overwriting it: ...

1. Select a capacity unit.

2. In the Demand Unit column, select a value from the dropdown box.




Defining Currency Units Use Here, you can define currency units.

There is no default configuration, but SAP delivers a standard set of currency units.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Independent Settings → Define Currency Units.

You can define new currency units or edit existing ones.

To define a new currency unit: ...


2. In the Crcy column, select a value from the dropdown box.


You can edit an existing currency unit by overwriting it: ...

1. Select a currency unit.

2. In the Crcy column, select a value from the dropdown box.




Defining Period Types Use Here, you define period types.

A period type defines a period derived from the base unit of one month.

For example:

• A period type of 1 defines one month

• A period type of 12 defines 12 months or one year

There is no default configuration, but SAP delivers a set of sample period types.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Independent Settings → Define Period Types.

You can:

• Define period types

• Edit period types

Defining Period Types ...


2. In the Period Type, Period Type Text, and Period Conv. Factor columns, enter a period type, a suitable description, and the period conversion factor.

The period conversion factor is the number of months.


Editing Period Types ...

1. In the Period Type Text, and Period Conv. Factor columns, overwrite the respective values.




Defining Portal Roles Use Here, you define portal roles.

The roles you define here form the basis for the pages you define when defining navigation.

There are four default portal roles:

• Administrator

• Item Manager

• Portfolio Manager

• Resource Manager

You can either use this default configuration or modify it by deleting some default roles and/or adding your own roles.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Independent Settings → Define Portal Roles.

You can:

• Define portal roles

• Edit portal roles

Defining Portal Roles ...


2. In the Role column, enter a role name.

3. In the Portal Role Text column, enter a suitable description.


Editing Portal Roles

To change a portal role name: ...

1. Go to the Portal Role Text column and overwrite the description.




Process and Service Settings Purpose This process describes how to define process and service settings.

Process Flow Go to the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Process and Service Settings and follow the instructions in the steps below: ...

1. Defining Object Search [Page 32]

2. Defining Services [Page 34]

3. Defining Questionnaires [Page 36]

4. Defining Scoring Models [Page 37]

5. Defining Navigation [Page 38]



Defining Object Search Use Here, you can define object search by making the necessary settings to enable searching for objects such as business partners or portfolio items. For each object type, one search help is maintained in the backend SAP system. Here, you can maintain the search help name for each object type as well as the key field IDs and names needed for display in the frontend application. Some object types may need two key field IDs and names. SAP provides a standard object search configuration, but you can also modify this to suit your requirements. If you want to do this, you can copy the search help maintained for an object type, modify it and enter the new search help name. If the search help you modify is using a Business Add-In, you need to modify the code accordingly. For each object type, you maintain values in the fields of the columns listed in the following table:

Column Description

Search Help Name This column contains the search help names.

Short Text This column contains a short description of each search help.

Key Field No. 1 This column contains the ID of the first key field.

Name Field No. 1 This column contains the name of the first object field.

Key Field No. 2 This column contains the ID of the second key field (if necessary).

Name Field No. 2 This column contains the name of the second object field (if necessary).

ConcatName • If the box in this column is checked, the name of the first field and the name of the second field name are concatenated into the name of the first field

• If the box in this column is not checked, the two names are displayed separately

Procedure You can:

• Add search helps for more object types

• Edit search help for existing object types

To add search helps for more object types: ...


2. In the Object Type column, choose F4 and select an object type from the list of object types.

3. In the Search Help Name column, choose F4, enter some search criteria, and select a search help from the list of search helps.

4. In the Short Text column, enter a suitable description for the search help.

5. In the Key Field No 1 column, enter the ID of the first key field.

6. In the Name Field No 1 column, enter the name of the first object field.



7. In the Key Field No 2 column, enter the ID of the second key field (if required).

8. In the Name Field No 2 column, enter the name of the second object field (if required).

9. In the ConcatName column, check the box if you want to concatenate the name of the first field and the name of the second field into the name of the first field.




Defining Services Use Here, you define services and link them to any number of object types.

• Services are actions that you can be assigned to specific fields

• Object types are standard xRPM objects such as portfolio, portfolio item, bucket, decision point, review

There is no default configuration, but SAP delivers ten services:

• Standard input

• SAP generated

• Derived field

• ID generation

• Object link

• Questionnaire

• Scoring model

• Bucket selector

• Advanced search (people search)

• Icon enabled

Each service is linked to the relevant view and edit components in the frontend application.

Is there a standard set of object types ?

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Process and Service Settings → Define Services.

You can:

• Define services

• Edit services

Defining Services ...


2. In the Service column, enter a service.

3. In the Service Name column, enter a suitable description.

4. In the View Component column, enter the name of the relevant display component in the frontend application.

5. In the Edit Component column, enter the name of the relevant edit component in the frontend application.

6. Select the service and double-click on Link service to object Type.

7. In the Object Type column, select a value from the dropdown box.



8. In the Name column, enter a suitable description.

9. In the Service column, select a value from the dropdown box.

10. In the Service Name column, enter a suitable description.


Editing Services You can edit service names, object names, view components, and edit components by overwriting the existing text.




Defining Questionnaires Use Here, you can define questionnaires and link them to question groups, questions, and options.

A questionnaire is a service that contains question groups with multiple questions and options. The multiple questions result in a single score. Areas where questionnaires are used include a portfolio review, association to a phase, and scoring models. They are really services on portfolio item attributes.

Questionnaires are created in the system by a Portfolio Manager within their specific bucket of authority. A questionnaire is created within the context of a bucket and is directly associated with a portfolio item attribute

There is no default configuration, but SAP delivers a sample set of questionnaires.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Process and Service Settings → Define Questionnaires.

You can:

• Define questionnaires

• Edit questionnaires

Defining Questionnaires ...


2. In the Questnnr ID and Name columns, enter a questionnaire ID and a suitable description, and choose Save.

3. Select the questionnaire and double-click on Question Groups.

4. Enter question groups

5. In the Questnnr ID, QuestionGrp ID and Name columns, enter the questionnaire ID, question group ID and a suitable description for the question group, and choose Save.

6. For each question group, select it and double-click on Questions.

7. Enter the questions

8. In the Questnnr ID, QuestionGrp ID, Question ID and Name columns, enter the questionnaire ID, question group ID, question ID and a suitable description for the question, and choose Save.

9. For each question, select it and double-click on Options.

10. Enter the options.

11. In the Questnnr ID, QuestionGrp ID, Question ID, Option ID, and Name columns, enter the questionnaire ID, question group ID, question ID, option ID and a suitable description for the option, and choose Save.

Editing Questionnaires

You edit the descriptions of questionnaires, question groups, questions, and options by overwriting the text.



Defining Scoring Models Use Here, you can define scoring models by specifying weighted attributes (fields) and assigning ranges to each attribute.

Scoring models enable users to compare portfolio items against each other based on a specific set of criteria. Each scoring model is defined by a set of attributes (fields), and each attribute has a specific weighting. Depending on the type of attribute, you can also define a range of values:

• For currency fields, you can specify currency ranges

• For numeric fields, you can specify numeric ranges

• For text fields, you can specify text ranges

There is no default configuration, but SAP delivers a sample set of scoring models.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Process and Service Settings → Define Scoring Models.

You can:

• Define scoring models

• Edit scoring models

Defining Scoring Models ...


2. In the Scoring Model and Name columns, enter a scoring model and a suitable description.

3. Select the scoring model and double-click on Scoring Model Attributes.

4. In the Field Name column, select a field from the dropdown box.

5. In the Weighting column, assign a weighting between 1 and 100.

6. Depending on the type of the scoring model attribute (field), define one or more ranges and enter a score for each range:

For a currency field, select the attribute and double-click on Ranges – Currency

For a numeric field, select the attribute and double-click on Ranges – Numeric

For a text field, select the attribute and double-click on Ranges – Text


Editing Scoring Models

You can edit the scoring model name, scoring model attribute weighting, ranges, and range scores by overwriting the text .



Defining Navigation Use Here, you define the navigation that determines how users can move around in the frontend application by defining links. You can also assign each link to a link group and map each link group to an object context (portfolio type ?).

Each link or navigation step is defined by a link ID, which includes information that determines how the link is identified, how it behaves, and where it points. You configure each link in the fields of the following columns:

• Description

This field contains the link text that is displayed in the frontend application.

• Tooltip

This field contains the text that is displayed in the link tooltip.

• Link Type

This field indicates whether the link points to a view or an action.

• Abs./Rel.

This flag indicates whether the path to the portal page ID specified in the Portal Page ID column is the full (absolute) path or a relative path.

• Portal Page ID

This is the ID of the portal page to which the link points.

A link group is a logical grouping of each of the links defined above. Examples of link groups include Portfolio Management, Item Management, and Administration

You can also map each link group to one or more portfolio types.

SAP delivers a complete default configuration, but you can add or modify the standard setup.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Process and Service Settings → Define Navigation.

You can:

• Define navigation links

• Edit navigation links

Defining Navigation Links ...


2. In the Link ID, Description, and Tooltip columns, enter a link ID, description, and tooltip for the link.

3. In the Link Type column, select a link type from the dropdown box.

4. In the Abs./Rel. column, check the box to indicate whether the specified path to the portal page ID is the full (absolute) or a relative path:

If the path is the full (absolute) path, check the box



If the path is a relative path, do not check the box

5. In the Portal Page ID column, enter the full (absolute) or relative path of the portal page ID to which the link points, as indicated in the above box.

6. Choose Save.

Editing Navigation Links

You can edit the entries for any link ID, link group or object context by overwriting the texts or changing the selections.




Global Field Settings Purpose This process describes how to define global field settings.

Process Flow Go to the SAP xRPM Implementation Guide (IMG), navigate to Global Customizing → Global Field Settings and follow the instructions in the steps below:

• Checking Object Types and Supported Structures [Page 41]

• Checking SAP Field Configuration [Page 42]

• Defining Custom Field Configuration [Page 43]



Checking Object Types and Supported Structures Use Here, you can check the object types and supported structure types.

Supported object types include ADM, BUPA, CPO, CPR, EPO, FPO, FPR, GTO, GTR, RBH, RIH, RPH, RVO, STO, and STR.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Global Field Settings → Check Object Types and Supported Structures.



Checking SAP Field Configuration Use Here, you can check the default SAP field and user interface (UI) configurations for specific object types.

This is the default configuration delivered by SAP.

You cannot change these default settings, but you can define your own custom field and UI configuration [Page 43].

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Global Field Settings → Check SAP Field Configuration.



Defining Custom Field Configuration Use Here, you can customize the default field and UI configuration delivered by SAP for specific object. types.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Global Field Settings → Define Custom Field Configuration.



Portfolio Dependent Settings Purpose This process describes how to define portfolio dependent settings.

Process Flow Go to the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Portfolio Dependent Settings and follow the instructions in the steps below: ...

1. Defining Portfolio Types [Page 45]



Defining Portfolio Types Use Here, you define portfolio types and link them to financial categories and capacity categories.

A portfolio type identifies a group of portfolios that follow the same strategy; it is thus is a required attribute of a portfolio definition. You link each portfolio type to the relevant financial categories and capacity categories. These assignments then cover all portfolio objects in a given portfolio.

What you define here determines the display of portfolio data in the frontend application.

There is no default configuration, but SAP delivers a single default portfolio type ADM.

Prerequisites You must first define financial categories and capacity categories [Page 25].

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing → Portfolio Dependent Settings → Define Portfolio Types.

You can:

• Define portfolio types

• Edit portfolio types

Defining Portfolio Types ...


2. In the Portfolio Type and Portfolio Type Text columns, enter a portfolio type and a suitable description.

3. Select the portfolio type and double-click on Link Portfolio Type to Financial Category.


5. In the Financial Category column, select a financial category from the dropdown box.

6. In the Category Text column, enter a suitable description for the financial category.

7. Double-click on Link Portfolio Type to Capacity Category.

8. In the Capacity Category column, select a capacity category from the dropdown box.

9. In the Category Text column, enter a suitable description for the capacity category.


Editing Portfolio Types

You can:

• Edit a portfolio type description

• Edit financial categories attached to a portfolio type

• Edit capacity categories attached to a portfolio type



Editing a Portfolio Type Description

To edit a portfolio type description, overwrite the existing text.

Editing Financial Categories Attached to a Portfolio Type

• To edit the financial categories attached to a portfolio type, select the portfolio type and double-click on Link Portfolio Type to Financial Category

• To add a new financial category to the portfolio type, choose New Entries, select a financial category from the dropdown box and enter a suitable description

• To edit an existing financial category, overwrite the existing financial category name

Editing Capacity Categories Attached to a Portfolio Type

• To edit the capacity categories attached to a portfolio type, select the portfolio type and double-click on Link Portfolio Type to Capacity Category

• To add a new capacity category to the portfolio type, choose New Entries, select a capacity category from the dropdown box and enter a suitable description

• To edit an existing capacity category, overwrite the existing capacity category name




Project Settings Purpose This process describes how to define project settings.

Process Flow Go to SAP xRPM Implementation Guide (IMG), choose Global Customizing → Project Settings and follow the instructions in the steps below: ...

1. Defining Project Categories [Page 48]

2. Defining Areas [Page 50]

3. Defining Locations [Page 51]

4. Defining Project Alerts [Page 52]



Defining Project Categories Use In this step, you define project categories.

A project category is an area of project activity such as a business area, division, or line of business. Examples of project categories in pharmaceutical R&D include oncology, dermatology, and cardiology.

You can either accept the project categories delivered by SAP or create new ones.

For each project category, you can define the following elements:

Element Description Example

Project subcategory A sub-unit of a project category. Example:

Pharmaceutical R&D:

Project category = oncology

Project sub-category = chemotherapy.

Project type A category by which projects are grouped.

Project types allow you to flag projects as test projects. Test projects are effectively dummy projects, so they have no impact on the capacity data in the system.

Technology type A category by which projects are grouped.

Examples of technology types in a hardware R&D organization would be base, key, pacing, and embryonic.

Project phase and alert object

These elements allow you to correlate alert status with project phases.

Suppose the project phases are Design, Build, and Implement.

You can use the alert object to map a key performance indicator in the Project Dashboard to the project phase indicator (that is, map staffing status to Design, schedule status to Build, and risk status to Implement).

• In the Design phase, this means that if the staffing status shows yellow, the Design phase indicator also shows yellow.

• In the Implement phase, this means that if the risk status shows green, the Risk phase indicator also shows green.

You can specify stages of projects as phases.



Examples of project phases for a pharmaceutical R&D organization could be Discovery, Pre-Clinical I, Pre-Clinical II, and Clinical Trial.

Procedure To create a project category: ...

1. In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Project Settings → Define Project Categories.


3. Enter values in the columns Category, Project Category Text and Specific Name for "Category".

To define the elements of a project category, select the project category and enter settings as follows:

Define Project Subcategory ...

1. Double-click Project Subcategory.

2. Enter values for Project Subcategory and Subcategory Text.

Define Project Type ...

1. Double-click Project Type.

2. Enter values for Project Type and Project Type Text.

3. If a project type is inactive for a specific activity, check the appropriate box.

Define Technology Type ...

1. Double-click Technology Type.

2. Enter values for Project Technology Type and Technology Type Text.

Define Phase Definition with Alert Object ...

1. Double-click Phase Definition with Alert Object.

2. Enter values for Project Phase and Project Phase Text.

3. In the Alert Object column, select an alert object from the dropdown box.



Defining Areas Use In this step, you can define areas for your projects.

An area is a geographical location. When you define an area, it is linked to a physical location [Page 51].

The geographical location information is transferred to the SAP Business Information Warehouse (BW), so that users can run detailed reports based on project physical locations and summarized reports based on project geographical locations.

Procedure ...

In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Project Settings → Define Areas.



Defining Locations Use In this step, you can define locations.

A location defines the physical location of a project. Locations can be anything from rooms to buildings to cities, depending on the size of your company.

When you define a location, it is linked to a geographical area [Page 50].

Procedure ...

In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Project Settings → Define Locations.



Defining Project Alerts Use In this step, you define project alerts to define the status of a project according to:

• Budget

• Priority

• Risk

• Schedule

• Staffing

Procedure Configure the project alerts as required.

To do this: ...

1. In the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Project Settings → Define Project Alerts

2. In turn, double-click on Budget Groups, Priority Groups, Risk Groups, Schedule Groups, and Staffing Groups turn and make the following settings:

a. Enter appropriate percentage values for upper and lower limits.

b. Select the alert icons you wish to use.

At present, you should use only the red, yellow and green LEDs.

c. Select the status colors you wish to use.

Example Here is an example configuration for budget status:

Budget Status Group

Budget Status Group Text

Upper Limit

Lower Limit

+ + + Status Color

01 Critical Over budget 999 50 Red LED; stop; errors

Red LED; stop; error

Red default

02 Over Budget 49 20 Yellow LED; caution

Yellow LED; caution

Yellow default

03 On Budget 19 19 Green LED; go; ok

Green LED; go; ok

Green default

04 Under Budget 20- 49- Yellow LED; caution

Yellow LED; caution

Yellow default

05 Critical Under Budget 50- 999- Red LED; stop: errors

Red LED; stop: errors

Red default

Value Determination You can determine values for each project alert as follows:

• Budget



The budget status is based on the ratio of actual cost YTD (year-to-date) to planned cost YTD. This data is transferred to SAP xRPM via the SAP FI/CO interfacing process and is displayed on the Project Details screen. The value of actual cost YTD is the sum of all actual costs posted in SAP FI/CO on the project cost collectors of the project for the current year. The formula is:

For planned cost YTD > actual cost YTD (under-budget projects):

budget ratio = (actual cost + planned cost) / actual cost * 100

For planned cost YTD <= actual cost YTD (over-budget/on-budget projects):

budget ratio = (actual cost - planned cost) / planned cost * 100

• Priority

The priority is derived directly from the following priority groups and is displayed in the Project Dashboard: Very High High Medium Low

• Risk

The risk status is based on the probability of technical/commercial success and is displayed in the Project Dashboard. The formula is: (100 # ((Probability of Technical Success + Probability of Commercial Success) / 2))

• Schedule

The schedule status is based on the ratio of Completed Tasks to Date to All tasks Tasks to be Completed TD. Each task is weighted by the number of planned hours it takes to complete and the percentage completion of the task.

• Staffing

The staffing status of a project is based on the ratio of Resource Supply to all Roles to Demand of all Roles. Roles that need to be staffed within the next 365 days are considered in this calculation. Each role is weighted by the number of days remaining to staff the role and by criticality of the role.



Base System Interfaces Purpose This process describes how to configure SAP and non-SAP base systems to work with SAP xRPM.

Process Flow • For details about the settings you need to make for each supported base system, see

Application Object Settings [Page 55]

• For details about how to integrate the various supported base systems, see the following sections according to your requirements:

...

SAP Product Lifecycle Management - Project System Integration [Page 66]

SAP cProjects Integration [Page 70]

SAP xApp Product Definition Integration [Page 72]

Microsoft Project Integration [Page 77]

SAP Human Capital Management Integration [Page 84]

SAP Financial and Controlling Integration [Page 112]



Application Object Settings Purpose This process describes how to make application object settings for base system interfaces.

You can connect the SAP xRPM system to various SAP and non-SAP backend systems to extract application-specific fields and link SAP xRPM system objects to backend system objects.

For each business object supported by SAP xRPM, there is one preconfigured business object type associated with the SAP xRPM object link type. You can use this link to capture project data and return it to the backend system when requested.

Process Flow ...

1. Defining RFC Connections [Page 56]

2. Defining Logical Ports [Page 58]

3. Defining Logical Systems [Page 59]

4. Defining the Web Server Alias [Page 60]

5. Defining Object Link Type Groupings [Page 61]

6. Defining Object Link Types [Page 62]

7. Assigning Base System Applications to Application Areas [Page 63]

8. Assigning Object Link Type Groupings to Applications [Page 64]

9. Defining Field Mapping [Page 65]



Defining RFC Connections Use Here you can define the parameters for remote function call (RFC) destinations pointing to the various base project systems. The values of these parameters and the type of connection vary for each application.

This configuration step is required for:

• SAP Product Lifecycle Management – Project System (PLM PS) integration

• SAP cProjects integration

• SAP xApp Product Definition (xPD) integration

• Microsoft Project integration

The name of the RFC destination should be the same as the logical system name.

You can assign the following types of RFC destination:

• R/2 connections

• R/3 connections

• Internal connections

• Logical destinations

• CMC connections

• SNA/CPI-C connections

• TCP/IP connections

• ABAP driver connections

Prerequisites No RFC destinations are assigned in the standard system.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Application Object Settings → Create RFC Connections.

2. Select one of the RFC destination types and choose Create.

3. Enter the parameters required for that type (see example below).

Processing RFCs with Errors If errors occur in RFCs, they are processed individually. The system schedules a background job for each RFC that results in an error. The background job keeps restarting the RFC until the RFC has been processed successfully. If the connection to the receiver system is broken, a large number of background jobs may be created. This means considerable load on the sending system.

To reduce the number of background jobs created and thus improve system performance, you should always process errors collectively in productive operation. That way, failed RFCs are not immediately resubmitted, but collected together in a periodically scheduled background job and



restarted as a packet. This helps to reduce the number of background jobs created. You can do this both for R/3 connections and TCP/IP connections.

To set up collective error processing: ...

1. Change the RFC destination

2. Choose Edit → tRFC options.

3. In the field Suppress background job if conn error field, enter X.

Perform the error handling as follows: ...

1. In ALE Administration choose Services → Communication Transactional RFC → Display incorrect calls.

2. Choose Edit → Execute LUW.

You should schedule a periodic background job that regularly executes this function.

Practice handling errors in remote function calls before the function is used productively.

Example For an R/3 connection, you could enter the following parameters:

Parameter Value

RFC destination S11BSP001

Connection type 3 (required for R/3 connections)

Target host bspserver01

System number 11

User, password, language, and target client As required.

The SAP* user cannot be used for remote function calls to the target system.

To connect to R/2 Systems:

Use an R/2 destination to read the users with passwords.

The actual communication uses CPI-C.

Select Unencrypted Password.

The maintenance of the RFC destination is not part of the automatic Change and Transport System. Therefore, the setting has to be made manually on all systems.



Defining Logical Ports Use Here, you can define the logical ports, which point to the RFC destinations previously configured in Defining RFC Connections [Page 56].



• Microsoft Project Server integration

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Define Logical Ports.

2. In the Proxy Class field, enter the proxy class.

For xPD, the proxy class is /RPM/CO_WSX_RPMINTEGRATION_V

For Microsoft Project, the proxy class is CO_DPR_CMAIN_SOAP_PORT

3. In the Logical Port field, enter the logical port name.

4. In the Description field, enter a suitable description for the logical port.

5. Choose Create.

6. On the Call Parameters tab, select HTTP Destination and, using the F4 help, select the RFC destination configured above.

7. Choose Save.



Defining Logical Systems Use Here, you can define the logical system names of the base project systems, which appear in the user interface of the frontend application. These logical systems point to the RFC destinations previously configured in Defining RFC Connections [Page 56].






• SAP Human Capital Management (HCM) integration

• SAP Financial and Controlling (FI-CO) integration

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Define Logical Systems.

2. Choose Edit → New Entries.

3. In the Log.System column, enter a name for the logical system that you want to create.

4. In the Name column, enter a suitable description of the logical system.

If you want to change this entry:

a. Select the appropriate line.

b. Choose Edit → Change field contents.

c. Enter the new text.

d. Choose Replace.




Defining the Web Server Alias Use Here, you can define the Web server alias. This is the place where you can link the logical ports and logical systems previously configured in Defining Logical Ports [Page 58] and Defining Logical Systems [Page 59].

The name of the Web server alias that you enter here must be the same as the Web server name that you enter in the step Defining Object Link Types [Page 62].






Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Define the Web Server Alias.


3. Enter the Web server alias and Web server address in the appropriate columns.

For SAP xPD, enter the following parameters and values:

Parameter Name Parameter Value

PROXYLOGICALPORT Name of logical port created in Defining Logical Ports [Page 58].

LOGICALDESTINATION Name of logical system created in Defining Logical Systems [Page 59].

For Microsoft Project, enter the following parameters and values:

Parameter Name Parameter Value

MSPLOGONPAGE /PROJECTSERVER/LGNPSAU.ASP

PROXYLOGICALPORT Name of logical port created in Defining Logical Ports [Page 58].

LOGICALDESTINATION Name of logical system created in Defining Logical Systems [Page 59].




Defining Object Link Type Groupings Use In this step, you can assign activity groups to object type groups.


• SAP Product Lifecycle Management - Project System (PLM PS) integration





Procedure For each activity group in the Group column: ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Application Object Settings → Define Object Link Type Groupings.

2. If you want to change the description of the activity type group, overwrite the text in the Name column.

3. In the Defines cProjects Project Header column, -------------.

4. In the Belongs to Object Type Grp column, select an object type group from the dropdown box.




Defining Object Link Types Use Here, you can define the object links for each business object type. This configuration step is required for:





Procedure For each business object type, perform the following steps: ...

1. In the Active column, activate the individual object links as required.

2. Specify the relevant integration settings to link to the base systems you are using.

To do this, select a business object type and double-click on Settings for Integration Processes.

3. Specify the relevant applications and logical systems.

To do this, select a business object type and double-click on Portfolio Add-On to Object Link Types.



Assigning Base System Applications to Application Areas Use In this step, you can assign each base system application to an application area.







Supported applications include:

Application Description

MSPPS Microsoft Project

MSPS3 Microsoft Project Server 2003

SAPCM SAP Content Management

SAPCO SAP Financial and Controlling

SAPCP SAP cProjects

SAPCR SAP Collaboration Room

SAPPD SAP xApp Product Definition (xPD)

SAPPS SAP Product Lifecycle Management – Project System (PLM PS)

SAPRPM SAP xApp Resource and Portfolio Management (xRPM)

Procedure For each application in the Appl. column, perform the following steps : ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Application Object Settings → Assign Base System Applications to Application Areas.

2. If you want to change the description, overwrite the text in the Description column.

3. In the Application Area column, select a base system from the dropdown box.




Assigning Object Link Type Groupings to Applications Use In this step, you assign object link type groupings to applications.







Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Application Object Settings → Assign Object Link Type Groupings to Applications.

For each application in the Appl. column, select an object link type grouping from the dropdown box in the Group column. ...



Defining Field Mapping Use Here, you can define the field mapping between base system applications and SAP xRPM. This is divided into four steps: ...

1. Map base system object fields to SAP cProjects fields

2. Map SAP cProjects fields to base system fields

3. Map base system object fields to SAP xRPM portfolio item fields

4. Map portfolio item fields to base system fields

Step 1 defines which fields should be transferred to SAP cProjects and how they should be transferred. It is further grouped with respect to main objects and sub objects.

• Main Object determines which base system data is transferred to SAP cProjects

• Sub Object determines which object of a particular base system is transferred

This configuration step is required for all SAP and non-SAP project systems.

Procedure ...

Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → Application Object Settings and perform the following activities:

a. Import to cProjects: Map Base System Object Fields to SAP cProjects Fields

b. Export from cProjects: Map SAP cProjects Fields to Base System Fields

c. Import to xRPM: Map Base System Object Fields to Portfolio Item Fields

d. Export from xRPM Portfolio Item: Map Item Fields to Base System Fields

In each case, select a main object link type grouping (Main Object) and a sub-object link type grouping (Sub Object). and double-click on Field Mapping. ...

...



SAP Product Lifecycle Management - Project System Integration Purpose This process describes how to integrate SAP Product Lifecycle Management – Project System (PLM PS) with SAP xRPM.

To create an SAP PLM PS project in SAP xRPM, users typically:

1. Create a project proposal in the SAP xRPM frontend application.

2. Maintain the project structure in the backend SAP PLM PS system.

3. Upload the project structure to SAP xRPM using the Project Upload facility in the SAP xRPM frontend application.

After the initial project upload, they can continue to perform daily project management with SAP PLM PS and may even change the project structure. They can synchronize the project structure in SAP xRPM by updating the project structure according to changes made in SAP PLM PS.

The handling of SAP PLM PS project structure elements varies:

• WBS elements, network headers, network activities, and network activity elements are all updated as tasks in SAP xRPM

• Milestones are updated as tasks with a milestone flag

The information uploaded to SAP xRPM includes details such as task description, planned start date, planned end date, actual start date, actual end date, location, priority and task status. At project level, SAP xRPM data has higher priority than SAP PLM PS data. Information is transferred only if the corresponding fields are initial in SAP xRPM.

During the upload process, objects in the SAP PLM PS and SAP FI-CO systems are linked to corresponding objects in the SAP xRPM system:

• Business object links are created for the SAP PLM PS application to link projects and tasks in SAP xRPM to SAP PLM PS project structure elements.

• Business object links for the application SAP FI-CO to link cost objects in SAP xRPM to SAP FI-CO objects such as WBS elements, network header and network activities.

These objects are attached to SAP xRPM tasks.

Later, the SAP xRPM FI integration evaluates the business object links for the application SAP FI-CO module, collects the costs posted to these costs collector, and transfers them to SAP xRPM.

The customizing for the object link type of the application ’SAP PLM PS application’ will be discussed below.

Since the orders attached to SAP PLM PS structures are not returned by the SAP PLM PS standard BAPI interface, the business object link of the SAP FI-CO module for orders is not created automatically during project upload/synchronization. Users have to maintain these manually using the Object Link Management facility in the SAP xRPM frontend application.

For SAP system releases through 4.6C, the SAP PLM PS standard BAPI interface does not provide the actual start and finish dates for network activities and network activity elements, so this information cannot be transferred to SAP xRPM.



Process Flow • To configure SAP xRPM to work with SAP PLM PS, you must:

...

a. Define RFC connections [Page 56]

b. Define logical systems [Page 59]

c. Define object link type groupings [Page 61]

d. Define object link types [Page 62]

e. Assign base system applications to application areas [Page 63]

f. Assign object link type groupings to applications [Page 64]

g. Define field mapping [Page 65]

• To distribute data from SAP PLM PS to SAP xRPM, see Data Distribution from SAP PLM PS to SAP xRPM [Page 68]



Data Distribution from SAP PLM PS to SAP xRPM Purpose This process describes the main steps that are necessary to distribute data from the SAP Product Lifecycle Management – Project System (PLM PS) to the SAP xRPM system.

Process Flow Uploading Work Centers From SAP PLM PS [Page 69]



Uploading Work Centers From SAP PLM PS Use In this step, you can upload work centers from SAP Product Lifecycle Management - Project System (PLM PS) to SAP xRPM. You can do this from SAP PLM PS by running the report RPM_WRKCNTR_UPLOAD, which transfers work centers to SAP xRPM and uses them to create team master data. The team name is generated using a combination of plant and work center, because the work center ID is only unique within a plant and can be used again in a different plant. The resources assigned to the work center are used to create the resources assigned to teams in SAP xRPM. The employee IDs of resources in SAP PLM PS are used to search for business partners in SAP xRPM with identical employee IDs. If a match is found, the business partner is added to the team. If the SAP PLM PS work center is created using organization units, the employees in the organization unit are derived during the transfer of the work center and used as the basis for creating teams. If new employees are added to the organization after you have run the report, these employees are not included in SAP xRPM system unless you run the program again. For this reason, you should run the program regularly (for example, weekly).

Prerequisites You must create the RFC destination to the target SAP xRPM system. You can do this in the transaction SM59.

Procedure In SAP PLM PS, go to transaction SE38 and run the report RPM_WRKCNTR_UPLOAD.

The program selection screen consists of two parts: • Selection of the work centers.

This is based on the logical database CRC, so you can use any combination of these fields.

• Selection of the logical system to transfer the data.

This is required to call the RFC function in SAP xRPM to create teams.

When you run the report, the output lists teams created, together with the appropriate success or error messages.



SAP cProjects Integration Purpose This process describes how to integrate SAP cProjects with SAP xRPM.

Process Flow ...

1. Define RFC connections [Page 56]

In this case, perform the following steps: ...

a. Choose Base System Interfaces → Application Object Settings → Create RFC Connections.

b. Select ABAP Connections (connection type 3) or HTTP Connections to ABAP System (connection type H) and choose Create.

c. On the RFC Destination screen, enter the RFC destination name and a suitable description.

d. On the Technical Settings tab, enter the following information:

If you are creating a connection type 3:

In the Target host field, enter the project server name or the IP address

In the System No. field, enter the system number

Select Save as IP Address If you are creating a connection type H:

• In the Target host field, enter the project server name or the IP address

• In the Service No. field, enter the port number of the server where the service is available

• In the Path prefix field, enter the path pointing to the WSDL file

• In the Proxy user field, enter the proxy user

• In the Proxy password field, enter the proxy password

a. On the Logon/Security tab, activate SSL in either anonymous or default mode (client).

If you activate SSL, you must change the service to the port number for which SSL is configured in IIS.

b. On the Special Options tab, do the following: In the HTTP Version field, set the HTTP version to HTTP 1.1

Set Compression to Inactive

Set Compressed response to No

Set Accept cookies to Yes

a. Save your configuration settings and check the connection by choosing Test Connection.

A valid connection should return a status code of 200.

2. Define logical ports [Page 58]

3. Define logical systems [Page 59]



4. Define the Web server alias [Page 60]

5. Define object link type groupings [Page 61]

6. Define object link types [Page 62]

7. Assign base system applications to application areas [Page 63]

8. Assign object link type groupings to applications [Page 64]

9. Define field mapping [Page 65]

...



SAP xApp Product Definition Integration Purpose This process describes how to integrate SAP xApp Product Definition (xPD) with SAP xRPM.

Integrating SAP xPD with SAP xRPM enables users to upload xPD concepts to SAP xRPM as valid portfolio items.

This documentation describes how to configure SAP xRPM to work with SAP xPD.

For information about how to configure SAP xPD to work with SAP xRPM, see the documentation Configuration Content for xPD on SAP Service Marketplace at http://service.sap.com/instguides → SAP xApps.

SAP xPD – xRPM Mapping SAP xPD generates a 36-character GUID, which is stored in SAP xRPM as the object key.

SAP xRPM generates a new ID for each new SAP xPD concept uploaded to SAP xRPM.

The standard solution provides the following:

• Default mapping

You can modify the default mapping by implementing your own code in the Business Add-In (BAdI) RPM_XPD_CUST_FIELDS

• Project category and subcategory verification:

If the SAP xPD values are null or are not maintained, the first record maintained in SAP xRPM is used.

• Currency default is USD

• Project unit default is HRS

• Geographical location and physical location defaults are the project manager's default locations

• Project phase default is the first phase

• Project approval status is the first record from the To be approved status group

Process Flow To configure SAP xRPM to work with SAP xPD, you must:

• Make the necessary configuration settings

• Perform the necessary mapping steps:

Map the concept template and process template of the xPD concept to an xRPM portfolio item type for a particular logical system of xPD

Map the phases of the process template to decision points

Add the new xPD concept attributes to the concept custom structure CI_RPM_TS_PD_CONCEPT_ATT and the portfolio item attributes to the portfolio item custom structure CI_RPM_ITEM_ATT in the customizing client



Map the metric ID and value type ID

Map the concept attributes to the portfolio item

Map the components mapped for metrics to some component of the portfolio item

Configuration Settings 1. Defining RFC Connections [Page 56]



b. Select HTTP Connections to External Server (connection type G) and choose Create.




In the Service No. field, enter the port number of the server where the service is available

In the Path prefix field, enter the path pointing to the WSDL file

e. On the Logon/Security tab, activate SSL in either anonymous or default mode (client).


f. On the Special Options tab, do the following:

In the HTTP Version field, set the HTTP version to HTTP 1.1




g. Save your configuration settings and check the connection by choosing Test Connection.










Mapping Steps ...



1. Map templates to item types and decision points [Page 75]

2. Map metrics and value types [Page 76]



Mapping Templates to Item Types and Decision Points Use Here, you can:

• Map SAP xPD concept and process templates to SAP xRPM portfolio item types

• Map phases of SAP xPD process templates to SAP xRPM decision points

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP xApp Product Definition Integration → Map Templates to Item Types and Decision Points.

2. Map portfolio item types to concept templates and process templates:

a. Create a portfolio item type.

b. Select the xPD concept template to be mapped from xPD.

c. Select the xPD process template to be mapped from xPD.

d. Assign the concept template and process template combination to the portfolio item type.

e. Copy the standard field mapping to the portfolio item type.

f. If you need to map other process templates of the same concept template, repeat steps 1 to 5.

3. Map the phases of process templates to decision points.

a. Select the portfolio item type and mapped concept template + process template

b. Select decision point to be mapped

c. Select the xPD phase to be mapped from those phases which have a decision action as a step.

d. Assign the decision point to the selected phase

e. Repeat steps 2-4 if needed



Mapping Metrics and Value Types Use Here, you can map the metrics and value types of SAP xPD concepts, which you want to upload to SAP xRPM portfolio items.

Prerequisites Before mapping, you must add the component name to the structure.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP xApp Product Definition Integration → Map Metrics and Value Types.

2. Go to the customizing client of the system and add the entries, to which the metric ID and value type ID of the xPD concept need to be mapped, to the structure CI_RPM_TS_PD_CONCEPT_ATT.

3. Perform the mapping:

a. Choose New Entries.

b. In the Logical system column, select a logical system from the dropdown box.

c. In the PD Metric ID and PD Value Type ID columns, enter the metric ID and the value type ID of the xPD concept.

d. In the RPM Field Name column, select the component you added to the structure CI_RPM_TS_PD_CONCEPT_ATT from the dropdown box.

e. Save your changes.



Microsoft Project Integration Purpose This process describes how to integrate Microsoft Project with SAP xRPM.

You can use either of the following:

• Microsoft Project Client

In this case, you can synchronize your project plans (.mpp files) with SAP xRPM.

To be able to do this, you must install Microsoft Project Client on your local machine. You can then upload data from .mpp files to Project and Portfolio Management (SAP xRPM) and download date from SAP xRPM to .mpp files any number of times.

Supported versions include Microsoft Project 2002 or higher.

• Microsoft Project Server 2003

In this case, you can synchronize your project plans in SAP xRPM with project plans stored on Microsoft Project Server.

Since the integration between SAP xRPM and Microsoft Project Server is designed to work asynchronously, only one system should be active at any time. This helps guarantee data consistency in both systems.

Both upload from and download to Microsoft Project Server 2003 are supported.

You can upload project data from Microsoft Project Server to SAP xRPM any number of times

You can only download project data from SAP xRPM to Microsoft Project Server once

Business Rules

Uploading Projects from Microsoft Project to SAP xRPM

The project data uploaded from Microsoft Project to SAP xRPM depends on what the user selects in the frontend application. They can upload any (all, none or various combinations) of the following project data from Microsoft Project Client or Microsoft Project Server:

• Tasks

Users can upload tasks alone by checking Tasks in the frontend application. All tasks in Microsoft Project are then uploaded to SAP xRPM, together with the task hierarchy.

The date format for start dates and end dates in SAP xRPM is YYYYMMDD,

Dates in other formats are converted. Any time information maintained in Microsoft Project is ignored.

The value in the Duration field expresses either hours or any unit you otherwise configure.

The value of the work unit maintained in SAP xRPM is expressed in minutes or any equivalent unit you configure.

• Role resources

Resources in Microsoft Project Client are uploaded as resources assigned to a particular role in SAP xRPM. You can manage role data in Microsoft Project using the enterprise text



fields. The enterprise field selected for role information must be mapped to partner role data in SAP xRPM.

If users select Role Resources in the frontend application, Tasks is automatically selected too. This means that if role resource data is uploaded, then task data is also uploaded.

Uploading resources in Microsoft Project to resources of a particular role in SAP xRPM is controlled by the business partner for the resource. This means that each employee ID in Microsoft Project must have a corresponding business partner created in SAP xRPM. If this is not the case, then resources are not transferred.

Resources in Microsoft Project can be assigned to one role in SAP xRPM. If there is more than one role assigned to a resource in Microsoft Project Client, the latest role to be assigned is considered as the current role.

If no role data is maintained in Microsoft Project, a role called UNARES is created in SAP xRPM and all resources that do not have a corresponding role are assigned to that role

Role start dates and end dates are determined by the start dates and end dates of the resources assigned to that role. The earliest start date and latest end date of all resources become the start date and end date of the role.

The date format for start dates and end dates in SAP xRPM is YYYYMMDD, so dates in other formats are converted accordingly. Any time information maintained in Microsoft Project is ignored.

The work effort for the role in SAP xRPM is determined by the accumulated work effort of all resources assigned to the role

The value of the work unit maintained in SAP xRPM is expressed in minutes or any equivalent unit you configure. The unit you configure for 60 seconds is taken as the unit for work.

• Assignments

If users select Assignments in the frontend application, Role Resources is automatically selected too. However, the assignments cannot be uploaded, because changing assignments affects both role resources and tasks. The assignments are made with respect to a particular task in a role. The resources assigned for a particular task in Microsoft Project are retrieved and the corresponding role for the resource is assigned to the task.

For example, if three resources are assigned to a task in Microsoft Project and they belong to two roles, then that particular task will be assigned to two roles. The resources assigned to a role can be easily retrieved at any time.

Roles are assigned to a task and resources are assigned to roles. Assignments specify the roles that are allowed for a task.

To summarize, the following upload options are supported:

Tasks Role Resources

Assignments

1 X

2 X

3 X X



Downloading Projects from SAP xRPM to Microsoft Project

• Download to Microsoft Project Server 2003

When users download projects from SAP xRPM to Microsoft Project Server 2003, they can also download the project resources, but not the roles. To be able to download roles, you must use the Business Add-In (BAdI) provided for the purpose. Only a single download is supported. The names of the downloaded resources are a combination of employee name and employee ID. If an SAP xRPM project resource does not have a valid employee ID, that resource is not downloaded to Microsoft Project Server 2003. Also, if a template is chosen during download, no resources are downloaded.

• Download to Microsoft Project Client

User can download projects to Microsoft Project Client any number of times. A new .mpp file is created after each download. Only the project data and resources are downloaded. Also, resources must have a valid employee ID associated with a business partner.

Data Mapping

Project Data When you upload a project to SAP xRPM, the following project fields are updated:

Microsoft Project Field Description SAP xRPM Field

FINISH_DATE Project End Date FINISH_DATE_FIX

NAME Project Name/Description DESCRIPTION

START_DATE Project Start Date START_DATE_FIX

Task Data Most task data is simply a 1:1 field mapping between Microsoft Project and SAP xRPM. However, you may need to read additional fields.


ACTUAL_WORK Actual Work Effort of Task ACTUAL_WRK_EFFORT_EXT

DURATION Duration DURATION

FINISH Task End Date ACTUAL_FINISH

MILESTONE Milestone MILESTONE

NAME Task Name/Description DESCRIPTION

PERCENT_COMPLETE Task Complete Percentage COMPLETION

REMAINING_WORK Remaining Work Effort of Task

REM_WRK_EFFORT_EXT

START Task Start Date ACTUAL_START

WORK Work Effort Require for Task ???

Resource and Role Data

From Microsoft Project Assignments


FINISH Project End Date END_DATE



START Project Start Date BEG_DATE

From Microsoft Project Resources


WORK Work Effort WORK_EFFORT

From Microsoft Project Extended Attributes


205521569 (Enterprise Field)

Partner Role PARTNER_ROLE

Activities To enable users to utilize SAP xRPM customer fields required for the task and resource objects in all their projects, you must maintain them in the Enterprise Global template views.

To do this: ...

1. Choose Tools → Enterprise Option → Open Enterprise Global.

2. Choose Tools → Customize → Enterprise Fields.

3. Select the Custom Fields tab.

4. For the fields used in the Resource Sheet:

a. Choose Resource.

b. Select Enterprise Text 28 and choose Rename.

c. Enter the new name (that is, role ID) and choose OK.

5. Save the Enterprise Global sheet and close it.

6. Add the fields to the various sheets:

a. Select a whole column by clicking at the top where the column title is displayed.

b. Right click and choose Insert Column.

c. In the dropdown list box, select the required column and choose OK.

As mentioned above, you should do this to add the fields to the respective sheets/view




Configuring Microsoft Project Server 2003 Use This process describes how to integrate Microsoft Project Server 2003 with SAP xRPM.

This involves:

• Microsoft Project Server 2003 configuration

• SAP xRPM configuration

Procedure Microsoft Project Server 2003 Configuration On the Microsoft Project Server 2003 side, you must:

• Configure Microsoft Internet Information Server (IIS)

• Configure HTTPS / SSL for IIS

• Configure Project Data Services (PDS) extender

Access to projects on Microsoft Project Server 2003 is based on the roles defined there for users wanting to access those projects.

Configuring Microsoft Internet Information Server (IIS)

IIS configuration is needed to handle:

• Very large XML requests or responses

For POST operations to a .asp page, Microsoft IIS has default limits on the buffer size that depend on the IIS version:

The default limit in Microsoft IIS 4.0 is 2 MB

The default limit in Microsoft IIS 5.0 is 128 KB

This limit was reduced to 128 KB as a security measure.

The default limit in Microsoft IIS 6.0 is 256 KB

For further information, go to Microsoft Developer Network at http://msdn.microsoft.com/library/en-us/pjsdk/html/pdsUsingSOAP.asp

• Anonymous logon to the SAP system

For further information, see the relevant IIS documentation.

Configuring HTTPS / SSL for IIS

For further information about configuring IIS for HTTPS / SSL, go to http://support.microsoft.com/default.aspx?scid=kb;EN-US;290625

Configuring Project Data Services (PDS) Extender

If you install Microsoft Project Server 2003, you must also install the PDS extender and register it on the system on which the Microsoft Project Server is installed

To do this, download zip files from SAP Service Marketplace at

http://service.sap.com/xapps -> SAP xApps -> SAP xRPM -> Product Details -> Interfaces



and follow instructions in the readme.txt file.

SAP xRPM Configuration To integrate Microsoft Project Server 2003 with SAP xRPM, you must: ...




b. Select HTTP Connections to External Server (connection type G) and choose Create.




In the Service No. field, enter the port number of the server where the service is available

In the Path prefix field, enter the path pointing to the WSDL file

e. On the Logon/Security tab, activate SSL in either anonymous or default mode (client).


f. On the Special Options tab, do the following:

In the HTTP Version field, set the HTTP version to HTTP 1.1




g. Save your configuration settings and check the connection by choosing Test Connection.










When you have performed all the above configuration steps, users can:

• Create roles in SAP xRPM



• Assign resources to roles in SAP xRPM

• Log on with a valid user name and password authenticated by Microsoft Project Server 2003

• Select a project from SAP xRPM to be downloaded to Microsoft Project Server 2003

In this case, a new project is created in Microsoft Project Server 2003 based on the details of the project selected for download from SAP xRPM.

• Create or change task details and task assignment details in Microsoft Project Server 2003

• Upload project data from Microsoft Project Server 2003 to SAP xRPM along with the associated tasks, resources, roles, and task assignments



SAP Human Capital Management Integration Purpose This process describes how to integrate SAP Human Capital Management (HCM) with SAP xRPM.

The integration scenario provides the functionality for distributing SAP HCM data to the SAP xRPM System. The distributed data is the basis for the SAP xRPM resource pool and is used for the resource management functionality offered by SAP xRPM.

The method used to distribute SAP HCM data to the SAP xRPM System is SAP Application Link Enabling (ALE).

The integration scenario distributes three key SAP HCM objects:

• Organizational structure

• Qualifications catalog

• Employee master data

Organizational Structure SAP xRPM uses a basic organizational structure. The minimum requirements are the basic organizational unit hierarchy and the related positions. SAP xRPM uses this structure to determine employee - line manager relationships.

Additional organizational structure objects that assist in resource management (for example, cost centers) may also be included in the distribution scenario.

Qualifications Catalog The SAP qualifications catalog is used to maintain qualifications profiles for employees. To take full advantage of SAP xRPM resource management functionality, SAP recommends you to distribute your organization’s complete qualifications catalog, including proficiency scales.

Employee Master Data Since SAP xRPM is not an SAP HCM System, it does not contain any employee master data management. Therefore, basic employee master data is distributed to SAP xRPM to generate the resource pool used for project staffing. Each employee dataset from the SAP HCM System is converted to SAP business partner information. Each employee’s personnel number is stored with the business partner to link back to the SAP HCM employee master data.

The following SAP HR infotype data used in the employee distribution scenario:

Infotype Description Purpose

0000 Actions Used to select only active employees.

0001 Organizational assignment Organizational assignment, position.

0002 Personal data Name, birth date, social security number, …

0006 Addresses Employee addresses.

0105 Communications System user ID, e-mail address, phone numbers, …

1001 Relationships Employee qualifications profiles.



Process Flow To configure xRPM to work with SAP HCM, you must: ... ...




See also the following steps: ...

1. Common System Configuration and SAP HCM ALE Setup [Page 86]

2. SAP HCM System ALE Setup [Page 87]

3. SAP xRPM System ALE Setup for SAP HCM [Page 91]

4. SAP xRPM System Customizing for SAP HCM [Page 97]

5. Data Distribution from SAP HCM to SAP xRPM [Page 106]



Common System Configuration and SAP HCM ALE Setup Use In this step, you make the necessary settings for Application Link Enabling (ALE) to facilitate the distribution of data between the SAP Human Capital Management (HCM) system and the SAP xRPM system.

Procedure ...

You must perform the following steps in the SAP HCM system and the SAP xRPM system. The order is not critical.

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG).

2. Verify/maintain logical systems:

a. Choose Sending and Receiving Systems → Logical Systems → Define Logical System.

b. Choose Sending and Receiving Systems → Logical Systems → Assign Client to Logical System.

3. Maintain RFC destinations:

a. Choose Sending and Receiving Systems → System in Network → Define Target Systems for RFC Calls.



SAP HCM System ALE Setup Purpose This process describes the Application Link Enabling (ALE) setup in the SAP Human Capital Management (HCM) system.

Process Flow ...

1. Maintain the distribution model [Page 115]

2. Distribute the customizing data [Page 89]



Maintaining the Distribution Model Use In this step, you create and distribute the distribution model to the SAP xRPM System.

Procedure ...

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG) and choose Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views.

2. Create a new model view.

To do this, choose Create model view.

You can use an existing model, but it may be easier to distribute a new model to the target systems. Since the model view is time-dependent, set the start date to the beginning of the calendar year or earlier and leave the end date at the system high date (that is, 31.12.9999).

3. Add a message type.

To do this, choose Add message type and enter the following values:

Message Type: Either RPMFIF

Sender: <Logical system of the SAP FI-CO system>

Receiver: <Logical system of the SAP xRPM system>

4. Save your model view.

5. Generate partner profiles.

a. Select the model view you created and choose Environment → Generate Partner Profiles.

b. Execute the report for generation of partner profiles.

The generation log shows the generation status of Partners, Ports, Outbound parameters.

6. Distribute the model view.

a. Select the model view you created and choose Edit → Model View → Distribute.

b. Select the SAP xRPM target system (if not already selected) and choose Continue.

Result You should now see the model view in the SAP xRPM system.



Distributing Customizing Data Use In this step, you can distribute the customizing entries.

There are two ways you can do this:

• Distribute customizing entries via Application Link Enabling (ALE) This is the most automated distribution method for customizing data. However, the SAP xRPM system must be located in the SAP HCM system transport landscape, because the distribution is handled via customizing transports. If you want to use this method, contact your system administrator to determine whether the option is available.

• Distribute customizing entries via Cross-System Viewer This is a semi-automated distribution method for customizing data that uses the Cross-System Viewer to synchronize customizing data across different systems.

Procedure Maintain Distribution Groups ...

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG) and choose Modeling and Implementing Business Processes → Synchronization of Customizing Data → Modeling and Executing Distribution Maintain Distribution Groups.

2. Create a new distribution group.

3. Choose Assign customizing objects and assign the following customizing object to the distribution group:

Type Object Object Key Transport Object List Description

C VC_T77SK

Maintain the Distribution Model ...

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG) and choose Modeling and Implementing Business Processes → Synchronization of Customizing Data → Modeling and Executing the Distribution → Model Distribution.

2. Modify the distribution model created in Maintaining the Distribution Model [External].

For SAP HCM releases ≤ 4.5B:

• Add message type CONDAT

• Create filter and add VC_T77SK to the object list.

For SAP HCM releases ≥ 4.6B:

• Add message type CONDA2

• Create filter and add the distribution group created above to the filter

3. Save your changes, select the model view and choose Edit Model View Distribute.



4. Select the SAP xRPM target system (if not already selected) and choose Continue.

You should now see the model view in the SAP xRPM system.

Distribute the Distribution Group ...

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG), choose Modeling and Implementing Business Processes → Synchronization of Customizing Data → Modeling and Executing the Distribution → Distribute Distribution Group.

2. Select the distribution group you created above and choose Distribute Distribution Group.

3. Specify the SAP xRPM logical system and execute the report.



SAP xRPM System ALE Setup for SAP HCM

Purpose This process describes the Application Link Enabling (ALE) setup for SAP Human Capital Management (HCM) in the SAP xRPM System.

Process Flow ...

1. Checking Supported Message Types and IDoc Types [Page 92]

2. Mapping Message Types [Page 93]

3. Mapping IDoc Types [Page 94]

4. Changing Inbound Parameter of Partner Profile [Page 95]

5. Setting up SAP HCM Integration with SAP cProjects [Page 96]



Checking Supported Message Types and IDoc Types Use In this step, you can check the message types and IDoc types supported by SAP xRPM.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP HCM System ALE Setup → Check Supported Message Types and IDoc Types.

Example Message Type Basic Type Release

HRMD_A HRMD_A01 3.1G

HRMD_A HRMD_A02 4.0A



HRMD_A HRMD_A05 4.6C

HRMD_A HRMD_A06 610

HRMD_ABA HRMD_ABA01 4.6C

HRMD_ABA HRMD_ABA02 5.0A

HRMD_ABA HRMD_ABA03 610

HRMD_ABA HRMD_ABA04 620



Mapping Message Types Use In this step, you map the SAP Human Capital Management (HCM) message type to the SAP xRPM message type.

The message type used up to and including SAP HCM 4.6C is HRMD_A. Since this message type is unknown to the SAP xRPM System, you must map it to a known message type. For SAP xRPM, this message type is HRMD_ABA.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System ALE Setup → Map Message Types.

2. Under Logical msg. (short), enter the SAP HCM message type HRMD_A.

3. Under Message type, enter the SAP xRPM message type HRMD_ABA. ... ... Under Logical msg. (short), enter the SAP HR R/3 message type HRMD_A Under Message type, enter the xRPM message type HRMD_ABA.

For information about supported message types, see Supported Message Types and IDoc Types [Page 92].



Mapping IDoc Types Use In this step, you map the iDoc types supported by the SAP Human Capital Management (HCM) System to the IDoc types supported by the SAP xRPM System.

Since each SAP HCM release supports different IDoc types, the value you enter depends on the IDoc type supported by the release of your SAP R/3 HCM System.

Procedure 1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces →

SAP Human Capital Management Integration → SAP xRPM System ALE Setup → Map IDoc Types.

2. Under Basic type (short), enter the SAP HCM IDoc type HRMD_A05.

3. Under Basic type, enter the SAP xRPM IDoc type HRMD_ABA04. ...

For information about supported IDoc types, see Supported Message Types and IDoc Types [Page 92].



Changing Inbound Parameter of Partner Profile Use In this step, you change the inbound parameter of the partner profile.

Procedure For SAP Human Capital Management (HCM) releases up to and including 4.6C:

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System ALE Setup for SAP HCM → Change Inbound Parameter of Partner Profile.

2. Under Partner Type LS, select the SAP HCM logical system.

If the logical system is not displayed in the list, create an entry.

3. In the Inbound Parmtrs section, choose Create inbound parameters.

4. In the Message type field, enter HRMD_ABA.

5. On the Inbound options tab, go to the Process code field and enter HRMD or the process code you created in the previous step if you used another name.

6. For testing purposes, you can set the parameter Processing by function module to Trigger by background program.

This holds all incoming IDocs in the SAP xRPM system for manual processing. After testing, you can change this parameter back to Trigger immediately.

For SAP Human Capital Management (HCM) releases from 4.7: ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System ALE Setup for SAP HCM → Change Inbound Parameter of Partner Profile.

2. In the Inbound Parmtrs section, select the message type HRMD_ABA.

3. For testing purposes, you can set the parameter Processing by function module to Trigger by background program.

This holds all incoming IDocs in the SAP xRPM System for manual processing. After testing, you can change this parameter back to Trigger immediately.



Setting up SAP HCM Integration with SAP cProjects Use In this step, you integrate the SAP HCM application components from the ERP system with the business partners in SAP cProjects. This means that the business partner master records with the role employee are distributed for your employees from the existing SAP HCM master data to SAP cProjects. This takes place from the ERP system via Application Link Enabling (ALE).

Since business partners are not integrated with the SAP HCM application components from the ERP system in the standard system, SAP HCM master data is not distributed in SAP cProjects. For this reason, you must create new business partner master records for your employees with the business partner role employee in the standard system.

When you have implemented the SAP HCM application components in the ERP system, you should integrate the business partners with the SAP HCM application components. In this case, you cannot create any business partner master records with the business partner role employee in SAP cProjects.

Procedure To integrate business partners with SAP HCM application components: ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System ALE Setup for SAP HCM → Set up Integration of HR.

2. Perform the activity.

The HR: Set Up Central Person: Overview screen appears.

3. Set the value of the group HRALX with the semantic abbreviation HRAC to X.

In the SAP cProjects standard system, this field is blank.

4. Set the value of the group PLOGI with the semantic abbreviation PLOGI to Active Plan Version.

5. Save the data.

6. Adjust the ALE distribution model of your SAP HCM system.

If you want to use SAP cProjects with employee master data from the SAP HCM application components, proceed as follows:

• For Release 4.6C and higher

Use the message type HRMD_ABA.

Use this message type in the same way as the HRMD_A message type.

• For releases before 4.6C

Use the message type HRMD_A.

In this case, you must set up your own port for the BBP/CRM connection in the SAP HCM system. Enter version 2 (IDoc record types, version 3.0/3.1) for this port.

Use the filter in the distribution system to ensure that only the infotypes 0000, 0001, 0002, 0006, 0009, and 0105 (and no other employee data) are distributed in SAP cProjects.



SAP xRPM System Customizing for SAP HCM Purpose This process describes the necessary SAP xRPM customizing steps for SAP Human Capital Management (HCM).

Process Flow ...

1. Setting Up Business Partners [Page 98]

2. Qualifications Catalog [Page 99]

3. Employee Data Configuration [Page 103]



Setting Up Business Partners This process describes how to set up business partners for SAP xRPM.

In particular, you need to define the following:

• Number ranges

Check that the required number ranges have been defined.

To do this, go to transaction BUCF.

• Address types

Check that the required address types have been defined.

To do this, go to transaction BUC1.

• Name formats

Check that the required name formats have been defined for each country for which you maintain employee data.

The default entries for SAP xRPM are DE (Germany) and US (USA).

The name format is derived from the SAP Human Capital Management (HCM) personal data infotype (IT0002) field Name Format (KNZNM).

To maintain this format in the SAP HCM system, go to the SAP Reference IMG and choose Personnel Management → Personnel Administration → Personal Data → Name Format.

The default name format is 00.

• Authorizations

Check that the user profiles have the required authorizations for business partner maintenance.

To do this, go to transaction BP.

The authorization objects checked for business partner maintenance are:

B_BUPA*

B_BUPR*

For further information about setting up business partners, see the SAP Business Partner Implementation Guide (IMG).



Qualifications Catalog Purpose This process describes how to transport customizing tables containing the scales that define proficiencies to the SAP xRPM System.

There are three ways you can do this: ...

• Distributing Data to SAP xRPM by ALE Customizing [Page 100]

• Distributing Data to SAP xRPM by Client Comparison [Page 101]

• Distributing Data to SAP xRPM by Direct Entry [Page 102]



Distributing Data to SAP xRPM by ALE Customizing Use In this step, you transport the required customizing tables to the SAP xRPM System.

These tables specify the scales used to define qualification proficiencies.

This is one of three methods you can use to create these scales.

The other methods are:

• Client Comparison [Page 101]

• Direct Entry [Page 102]

If you have used one of the other methods, you do not need to execute this step.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System Customizing for SAP HCM → Qualifications Catalog → Distribute Data to SAP xRPM System by ALE Customizing.

There are two stages to this step: ...

a. Generate an ALE request to transfer data (transaction BDXE).

b. Import the data into the SAP xRPM system (transaction BDXD).



Distributing Data to SAP xRPM by Client Comparison Use In this step, you transport the required customizing tables to the SAP xRPM System.



The other methods are

• ALE Customizing Distribution [Page 100]

• Direct Entry [Page 102]


Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System Customizing for SAP HCM → Qualifications Catalog → Distribute Data to SAP xRPM System by Client Comparison.

2. Choose New comparison.

3. Select the source SAP HCM System and choose Total Comparison.

4. Select the view cluster VC_T77SK and choose Edit → Interact Copy.

5. Select each node in turn, select all entries not in the SAP xRPM System and copy them.



Distributing Data to SAP xRPM by Direct Entry Use In this step, you transport the required customizing tables to the SAP xRPM System.



The other methods are

• ALE Customizing Distribution [Page 100]

• Client Comparison [Page 101]


Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System Customizing for SAP HCM → Qualifications Catalog → Distribute Data to SAP xRPM System by Direct Entry.

2. Enter the data manually.



Employee Data Configuration Purpose This process describes employee data configuration.

Since the SAP xRPM System stores qualifications profile information for each business partner, you must:

• Define permitted relationships to allow the business partner to hold a qualifications profile

• Configure the selected qualifications profile of a business partner

Process Flow ...

1. Defining Permitted Relationships [Page 104]

2. Assigning Subprofiles to Business Partners [Page 105]



Defining Permitted Relationships Use In this step, you define permitted relationships in order to allow each business partner to hold a qualifications profile.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System Customizing for SAP HCM → Employee Data Configuration → Define Permitted Relationships.

2. Select Links.

3. Select Relat'ship * and double-click Allowed Relationships.


5. Enter allowed relationships as specified below.

Object Object Type Text A/B Rel Relationship Name

RelObjType Not maint.

BP Business partner A 032 Fulfills Q X

Q Qualification B 032 Is fulfilled by BP X

BP Business partner A 038 Has potential for Q X

Q Qualification B 038 Is a potential of BP X

BP Business partner A 042 Interests and preferences

Q X

Q Qualification B 042 Interests and preferences

BP X

BP Business partner A 043 Dislikes Q X

Q Qualification B 043 Is a dislike of BP X



Assigning Subprofiles to Business Partners Use In this step, you maintain the qualifications profile of business partners.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → SAP xRPM System Customizing for SAP HCM → Employee Data Configuration → Assign Subprofiles to Business Partners.

2. Double-click Header.

3. Select entry BP and double-click Views.

4. Select view PD and double-click Header assignment.

5. Select BP and double-click Subprofile assignment.

6. Choose New Entries and enter information as specified below:

No Sort Sequence Active Name

1 1 X Qualifications

2 2 X Potentials

3 3 X Preferences

4 4 X Dislikes



Data Distribution from SAP HCM to SAP xRPM Purpose This process describes the main steps for distributing data from the SAP Human Capital Management (HCM) System to the SAP xRPM System.

Process Flow ...

1. Creating Evaluation Paths [Page 107]

2. Checking iDoc Status [Page 109]

3. Checking Inbound Processing [Page 110]

4. Mapping Employee Personnel Areas to Project Physical Locations [Page 111]



Creating Evaluation Paths Use In this step, you create or change evaluation paths.

Evaluation paths determine which of those objects related to the base object are selected for Application Link Enabling (ALE) distribution of SAP Human Capital Management (HCM) data.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → Data Distribution From SAP HCM to SAP xRPM → Create Evaluation Paths.

2. Either create an evaluation path and define the individual relationships or select an existing evaluation path and change the individual relationships.

• To create an evaluation path, choose New Entries and enter an evaluation path and description

• To define or maintain the individual relationships, select an evaluation path and enter the individual relationships

Example If you want to distribute a company's organizational structure with related positions and jobs (with qualifications): ...

1. Create a new evaluation path:

Evaluation Path Evaluation Path Text O-O-S-C Jobs per organizational unit

2. Specify the individual relationships:

No Obj. Type

A/B Relat’ship Relationship Name Priority Rel. Obj. Type

Skip

10 O B 003 Incorporates * S

20 O B 002 Is line supervisor of * O

30 S B 007 Is described by * C

If you want to distribute a company's complete qualifications catalog: ...


EvalPath Evaluation Path Text

QCAT_BAS Qualifications catalog (Basis: qual. groups and direct quals)


No. Object type

A/B Relat'ship Relationship Name Priority Rel.Obj. Type

Skip

10 QK B 030 Is a generalization of * QK

20 QK B 030 Is a generalization of * Q



If you want to distribute an employee’s related qualifications profile and positions: ...


EvalPath Evaluation Path Text

P-Q-S Employee qualifications profile and position


No. Object Type

A/B Relat’ship Relationship Name Priority Rel.Obj. Type

Skip

10 P B 008 Holder * S

20 P A 032 Fulfills * Q

30 P A 038 Has potential for * Q

40 P A 042 Interests and Preferences

* Q

50 P A 043 Dislikes * Q



Checking iDoc Status Use In this step, you can view all iDocs and their respective status after they have been transported from the SAP Human Capital Management (HCM) system to the SAP xRPM system.

You can do this in either the SAP HCM system or the SAP xRPM system.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → Data Distribution From SAP HCM to SAP xRPM → Check iDoc Status.

2. Check the status of the iDocs in the SAP HCM system.

Each iDoc transported to the SAP xRPM system should have the status value 3 (Data passed to port OK).

If there is an error, check the asynchronous RFC log.

3. Check the status of the iDocs in the SAP xRPM system.

If the Inbound Processing option is set to Trigger immediately, each IDoc should have the status value 53 (Application document posted).



Checking Inbound Processing Use In this step, you check the inbound processing options in the SAP xRPM system.

If the Inbound processing option has already been set to Trigger by background program, you do not have to perform this step.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → Data Distribution From SAP HCM to SAP xRPM → Check Inbound Processing.

2. Select the relevant iDocs for processing and choose Execute.

This should set a new iDoc status.



Mapping Personnel Areas to Locations Use In this step, you map the personnel areas / subareas of your employees to project locations.

Prerequisites You must have already defined the locations [Page 51].

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Human Capital Management Integration → Data Distribution From SAP HCM to SAP xRPM → Map Personnel Areas to Locations.


3. In the Personnel area and PSubarea columns, enter the personnel areas and subareas of your employees.

4. In the RPM Locat. column, map each of these personnel areas and subareas to the location by selecting a value from the dropdown list box.

Example The location of project A is Palo Alto.

If the employee is based out of Palo Alto and you want to assign that employee with personnel area / personnel subarea 3000 / 001 to project A, the values in the table would look as follows:

Personnel area PSubarea RPM Locat. 3000 001 Palo Alto



SAP Financial and Controlling Integration Purpose This process describes how to integrate SAP Financial and Controlling (FI-CO) with SAP xRPM.

Since SAP xRPM is a project consolidation system, it does not perform project budget or cost management. These tasks are managed by SAP FI-CO, which transfers project budget and cost information to SAP xRPM via Application Link Enabling (ALE). After the transfer, the project budget and cost information is updated in SAP xRPM.

For each SAP xRPM project, users can assign SAP R/3 cost collection objects such as internal orders or WBS elements in the backend SAP FI-CO system using the Object Link Management facility in the SAP xRPM frontend application. These cost collection objects manage project costs and budgets in the backend systems.

Before transferring budget and cost information from SAP FI-CO to SAP xRPM, you must customize the business objects and the ALE interface. If you want to include costs from the SAP Cross-Application Time Sheet (CA-TS), you must activate one business object link for SAP FI-CO and one business object link for SAP CA-TS for the same cost object. You can either assign cost objects to projects manually or generate assignments when uploading from the SAP Product Lifecycle Management – Project System (PLM PS).

Process Flow To configure SAP xRPM to work with SAP FI-CO, you must: ... ...







See also the following steps: ...

• Common System Configuration and SAP FI-CO ALE Setup [Page 113]

• SAP FI-CO System ALE Setup [Page 114]

• SAP xRPM System ALE Setup for SAP FI-CO [Page 116]

• SAP xRPM System Customizing for SAP FI-CO [Page 119]

• Data Distribution from SAP FI-CO to SAP xRPM [Page 122]



Common System Configuration and SAP FI-CO ALE Setup Use In this step, you make the necessary settings for Application Link Enabling (ALE) to facilitate the distribution of data between the SAP Financial and Controlling (FI-CO) system and the SAP xRPM system.

Procedure ...

You must perform the following steps in the SAP FI-CO system and the SAP xRPM system. The order is not critical.

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG).

2. Verify / maintain logical systems:

a. Choose Sending and Receiving Systems → Logical Systems → Define Logical System.

b. Choose Sending and Receiving Systems → Logical Systems → Assign Client to Logical System.

3. Maintain RFC destinations:

a. Choose Sending and Receiving Systems → System in Network → Define Target Systems for RFC Calls.



SAP FI-CO System ALE Setup Purpose This process describes the Application Link Enabling (ALE) setup in the SAP Financial and Controlling (FI-CO) system.

Process Flow ...

1. Maintaining the Distribution Model [Page 115]



Maintaining the Distribution Model Use In this step, you create and distribute the distribution model to the SAP xRPM System.

Procedure ...

1. Go to the Application Link Enabling (ALE) Implementation Guide (IMG) and choose Modeling and Implementing Business Processes → Maintain Distribution Model and Distribute Views.

2. Create a new model view.

To do this, choose Create model view.

You can use an existing model, but it may be easier to distribute a new model to the target systems. Since the model view is time-dependent, set the start date to the beginning of the calendar year or earlier and leave the end date at the system high date (that is, 31.12.9999).

3. Add a message type.

To do this, choose Add message type and enter the following values:

Message Type: Either RPMFIF

Sender: <Logical system of the SAP FI-CO system>

Receiver: <Logical system of the SAP xRPM system>

4. Save your model view.

5. Generate partner profiles.

a. Select the model view you created and choose Environment → Generate Partner Profiles.

b. Execute the report for generation of partner profiles.

The generation log shows the generation status of Partners, Ports, Outbound parameters.

6. Distribute the model view.

a. Select the model view you created and choose Edit → Model View → Distribute.

b. Select the SAP xRPM target system (if not already selected) and choose Continue.

Result You should now see the model view in the SAP xRPM system.



SAP xRPM System ALE Setup for SAP FI-CO Purpose This process describes the Application Link Enabling (ALE) setup for SAP Financial and Controlling (FI-CO) in the SAP xRPM system.

Process Flow ...

1. Checking Inbound Process Code Settings [Page 117]

2. Checking Inbound Parameter of Partner Profile [Page 118]



Checking Inbound Process Code Settings Use In this step, you check the customizing settings for the inbound process code.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Financial and Controlling Integration → SAP xRPM System ALE Setup for SAP FI-CO → Check Inbound Process Code Settings.

2. Select the inbound process code RPMF.

3. Double-click Logical message.

The message type should be RPMFIF.

4. Go back to the first screen and select the inbound process code RPMF again.

5. Choose Details.

The customizing settings for the inbound process code should be: Identification IDOC_INPUT_RPMFIDATA

Option ALE Processing with ALE Service

Processing Type Processing by function module

6. On the right of the Identification field, choose ALE table and check the settings in the following group boxes:

Module (inbound)

Function module IDOC_INPUT_RPMFIDATA

Maximum number of repeats 1

iDoc Packet

Object type IDPKRPMFIF

End event MASSINPUTFINISHED

iDoc

Object type IDOCRPMFIF

Start event INPUTERROROCCURRED

End event INPUTFINISHED



Changing Inbound Parameter of Partner Profile Use In this step, you change the inbound parameter of the partner profile.

Procedure ...

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Financial and Controlling Integration → SAP xRPM System ALE Setup for SAP FI-CO → Change Inbound Parameter of Partner Profile.

2. Under Partner Type LS, select the SAP FI-CO logical system.

3. In the Inbound Parameters section, choose Create inbound parameters.

4. In the Message type field, enter RPMFIF.

5. On the Inbound options tab, go to the Process code field and enter RPMF or the process code you created in the pervious step if you used another name.



SAP xRPM System Customizing for SAP FI-CO Purpose This process describes the necessary SAP xRPM customizing steps for SAP Financial and Controlling (FI-CO).

Process Flow ...

1. Customizing the Organization Type [Page 120]

2. Customizing Value Types [Page 121]



Customizing the Organization Type Use In this step, you can customize the organization type used by the SAP Financial and Controlling (FI-CO) system.

When importing data from the SAP FI-CO system, the SAP xRPM system validates some organizational and technical parameters used in the transfer.

These parameters include:

Parameter Description

Organization unit type The organization unit type used is COA (controlling area).

Currency You maintain the currency used for project costs/budgets in the SAP xRPM system.

Value type • The value types used are:

• Plan Cost 01

• Actual Cost 04

• Budgets 41

• Plan Time PT

• Actual Time AT

Period type The period types used are:

• Monthly M

• Twice monthly M2

• Quarterly QT

• Half Yearly HY

• Yearly Y

• Total Value T

For each value type transferred from SAP FI-CO to SAP xRPM, a certain period type is used.

Procedure ...

Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Financial and Controlling Integration → SAP xRPM System Customizing for SAP FI-CO → Customize Organization Type.



Customizing Value Types Use In this step, you can view the standard value types used in the transfer of financial data from the SAP Financial and Controlling (FI-CO) system to the SAP xRPM system.

You can also create your own value types for individual analysis purposes

Procedure To create a value type:

1. Go to the SAP xRPM Implementation Guide (IMG) and choose Base System Interfaces → SAP Financial and Controlling Integration → SAP xRPM System Customizing for SAP FI-CO → Customize Value Types.


3. Enter the value type, specify the transfer period type and indicate whether the value refers to a quantity.

You can, for example, group the values in the totals table in the SAP FI-CO according to cost object/cost elements.

4. To transfer these values, implement the user exit in the report RPM_FIN01.

You can also use these values to fill your own project / task attributes.

To do this, use the BAdIs in the update program RPM_UPDFI01.

The standard program allows you to transfer plan/actual work time stored as quantity information from the FI-CO total table to SAP xRPM. For further information, see Data Distribution from SAP FI-CO to SAP xRPM [Page 122].



Data Distribution from SAP FI-CO to SAP xRPM Purpose This process describes the main steps for distributing data from SAP Financial and Controlling (FI-CO) to SAP xRPM.

To perform the daily transport of cost and budgets data, you can use the report RPM_FIN02, which you can scheduled as a background job. The link between the cost objects in the SAP FI-CO system and the project structure elements in the SAP xRPM system must be maintained in the SAP xRPM frontend application or generated by SAP PLM PS upload.

You can transfer the quantity information stored under some FI-CO cost elements to the SAP xRPM system. For example, you can transfer planned/actual work time with the value type actual/plan time. To do this, perform the following steps in the SAP FI-CO system: ...

1. Enter the cost elements or cost element intervals under the value type AT in the customizing view V_RPM_VALTYPC.

2. Maintain the conversion factor between the quantity unit used for these cost elements in the SAP R/3 FI-CO system and the time unit used in the SAP xRPM system in the view RPM_TIMCV.

You enter the logical system of the SAP xRPM system (that is, the RFC destination) on the selection screen in the field Destination System.

• If the parameter Actual Costs/Budgets is set to X, only actual cost and budget data is transferred

• If the parameter Actual Costs/Budgets is initial, other types of data such as planned costs is also transferred

If you have more than one controlling area in your SAP FI-CO system for which you want to transfer costs to SAP xRPM, you can start this program separately.

The test options allow you to simulate the transfer using one project and one task. In this case, you have to enter the SAP xRPM project name or ID and the task name or ID. Cost and budget data is transferred in controlling area currency.

Process Flow ...

1. Checking IDoc Status [Page 123]

2. Checking Inbound Processing [Page 124]

3. Updating Project Cost and Budget in SAP xRPM [Page 125]



Checking IDoc Status Use

In this step, you can view all IDocs and their respective status after they have been transported from the SAP Financial and Controlling (FI-CO) System to the SAP xRPM System.

You can do this in either the SAP FI-CO System or the SAP xRPM System.

Procedure ...

1. In the SAP xRPM Implementation Guide (IMG), choose Base System Interfaces → SAP R/3 Financial and Controlling (FI-CO) System → Data Distribution From SAP FI-CO to SAP xRPM → Check IDoc Status.

2. Check the status of the IDocs in the SAP FI-CO System.

Each IDoc transported to the SAP xRPM System should have the status value 3 (Data passed to port OK).

If there is an error, check the asynchronous RFC log.

3. Check the status of the IDocs in the SAP xRPM System.

If the Inbound Processing option is set to Trigger by background program, each IDoc should have the status value 64 (IDoc ready to be transferred to application).

If the Inbound Processing option is set to Trigger immediately, each IDoc should have the status value 53 (Application document posted).

If the IDoc status is 52 (Application document not fully posted ), this is usually okay.

In most cases, this is due to extra data that has been transferred from the SAP HCM System but cannot be created in the SAP xRPM System due to missing data. Refining the data distribution scenario should eliminate the problem.

You should examine IDocs with errors at the point where the error occurs. In some cases, you may only need to perform more customizing. In other cases, data could be corrupt.



Checking Inbound Processing Use In this step, you check the inbound processing options in the SAP xRPM System.

If the Inbound processing option has already been set to Trigger by background program, you do not have to perform this step.

Procedure ...

1. In the SAP xRPM Implementation Guide (IMG), choose Base System Interfaces → SAP R/3 Financial and Controlling (FI-CO) System → Data Distribution From SAP FI-CO System to SAP xRPM System → Check Inbound Processing.

2. Select the relevant IDocs for processing and choose Execute.

This should set a new IDoc status.



Updating Project Cost and Budget in SAP xRPM Use In this step, you can update the project cost and budget in SAP xRPM.

When you have transferred the project cost and budget from the SAP Financial and Controlling (FI-CO) systems, you must review the IDoc status to check that the transfer to the SAP xRPM System was successful.

Procedure ...

Run the report RPM_FIN01.

• If the data transfer was unsuccessful, investigate the errors and perform the transfer again

• If everything is OK, schedule the report RPM_UPDFI01 to update the costs and budgets of the SAP xRPM projects/tasks.

You can run this report in simulation mode. You can also update the costs and budgets of a single project by entering the SAP xRPM project ID.

At present, financial data is transferred only for projects with the execution status 001 (Not Started) and 003 (In Progress).

There are also two BAdI methods of the BAdI definition that allow you to modify the attributes. The BAdI definition is RPM_FI_PROJ_UPDATE and its interface is IF_EX_RPM_FI_PROJ_UPDATE. For further information, see the SAP xRPM Implementation Guide (IMG).



User Management Purpose This process describes how to configure roles and users.

Process Flow ...

• Creating SAP xRPM Roles [Page 127]

• Creating SAP xRPM Users [Page 128]



Creating SAP xRPM Roles Use In this step, you can create roles with defined activities for users.

SAP delivers the following predefined roles for SAP xRPM:

Role Description

SAP_RPM_CONTENTREVIEWER Content Reviewer

SAP_RPM_EXECUTIVE Project Executive

SAP_RPM_PROJECTAPPROVER Project Approver

SAP_RPM_PROJECTMANAGER Project Manager

SAP_RPM_PROJECTMEMBER Project Member

SAP_RPM_PROJECTOFFICE Project Office

SAP_RPM_PROJECTPROPOSER Project Proposer

SAP_RPM_PROJECTREVIEWER Project Reviewer

SAP_RPM_RESOURCEMANAGER Resource Manager

SAP_XRPM_ADMINISTRATOR xRPM 4.0 Administrator

SAP_XRPM_USER xRPM 4.0 User

You can either accept the above predefined roles or create your own.

Procedure To create your own roles, go to the SAP xRPM Implementation Guide (IMG) and choose User Management → Create SAP xRPM Roles.



Creating SAP xRPM Users Use In this step, you can create users and maintain user authorizations in the SAP xRPM system.

Since business partners are created using employee information from the underlying SAP Human Capital Management (HCM) system, the names required for creating users in the SAP xRPM system are derived from there. However, some user names may not be maintained in the SAP HCM system, so you need to create these additional users in the SAP xRPM system or assign them as business partners to existing users.

You can perform the following activities: • Assign business partners to existing users

• Preselect business partners

• Changing user attributes

• Delimit SAP xRPM users

Procedure To create SAP xRPM users, go to the SAP xRPM Implementation Guide (IMG) and choose User Management → Create SAP xRPM Users.

Assigning Business Partners to Existing Users 1. Under Preparation, choose Assignment of Business Partners to Existing Users.

2. Enter a user or search generically and choose Execute.

3. Choose Assign Business Partner.

4. Select an employee by double-clicking.

5. Change the validity date if necessary and choose Create.

Preselecting Business Partners ...

1. Under User / Authorization Assignment, choose Preselect Business Partners.

2. Enter relevant search criteria and choose Execute.

Changing User Attributes Here, you can determine attributes or set up authorization assignments for SAP xRPM users.

Choose Change user attributes/key date.

• In the Password field, INIT appears as the default, but you can change this.

• In the User group field, the entry RPMUSER is fixed and cannot be changed,

This is because it is important to differentiate users authorized for SAP xRPM from other users such as system administrators or online SAP GUI users.

• In the Role field, the role SAP_RPM_PROJECTMEMBER appears as the default.

For more information on the entries that you can make in this screen, choose Information.

Delimiting SAP xRPM Users ...



1. Choose Delimit RPM Users.

2. Enter a user name or search generically.

3. Choose Change.

4. On the Roles tab, you can delimit the user's validity period.



Utilities This section describes utilities for configuring SAP xRPM. ...

• Displaying Project Data [External]

• Employee Overview [Page 132]

• Updating Project Dashboard Data [Page 134]



Displaying Project Data Use This utility enables you to display an overview of project data stored in SAP xRPM applications.

You can display both existing data and archived data content. Other project-related data in the project hierarchy (for example, tasks, roles, and resources) is also displayed.

• The report provides fast access to data that is generated by the SAP xRPM backend system and leveraged by the SAP xRPM application. Data is organized and selected via either a project, project template, or archived project display and selection. The components of project, task, role, resource, relation and object link are supported for display.

• The project organizational hierarchy is visible within the display. Tasks are the most common component to be organized in a hierarchy. You can see the hierarchy either in the project tree display of tasks or by looking at the common data attributes of the task; these attributes indicate the hierarchy position of the object.

• Archived data content can also be retrieved and displayed. This confirms that critical data content has been properly archived. Display of archived data is visible temporarily in project form as the archive data chosen for display is not reloaded into the active project storage of the SAP xRPM system.

• Certain SAP xRPM project data components reference related data. This referenced data and tables of the selected object are displayed in a secondary screen wherever possible. Examples of related data that can be displayed here include availability characteristics of the role or resource and business partner details. Additionally, components such as the object link present additional interpreted data that can be derived from customization in addition to the common display data.

Procedure ...

Go to the SAP xRPM Implementation Guide (IMG) and choose Utilities → Display Project Data. This activity starts the transaction RPMDATA.

Only authorized project data is returned to the user.

Multiple project selection and display is only available within the project or project template display.



Employee Overview Use This utility enables you to display a list of employees according to specific selection criteria.

The primary selection criteria for running this report are:

• Employee Number

• Business Partner Number

• Central Person Number

• User Name

• Team ID

• Key Date

If you enter a key date, the report displays everything valid as of that date

If you enter no key date, the current system date is used

Display options for the report include:

• Employee Overview (default)

• Consistency Check

• Team Overview

You can also filter output further by selecting one of the following options:

• Skills

• Terms

• Location

• Availability

• All Employee Data (default)

The report output depends on the display option you select.

Employee Overview If you select the Employee Overview option (default) with the filter option All Employee Data, the report output includes employee number, business partner number, central person number, expert ID, team ID, user name, and name.

Also included are the following icons indicating the existence (green check mark) or absence (red cross) of:

• Users

• Skills

• Location

• Terms

• Availability

• Projects



• Project Managers

If you select the Employee Overview option (default) with a different filter option (Skills, Terms, Location, Availability), the report output is modified accordingly.

Selecting Location produces report output that includes a column called Consistent Dates for checking date consistency:

• If the dates are inconsistent (red cross) or no data is maintained (null), you can choose Maintain location to correct the data or create a new record

• If there are multiple records, the dates must be continuous and the dates must always end with a high date (31.12.9999)

Consistency Check Report output for the Consistency Check option includes:

• Begin Date

• End Date

• Employee Number

• Business Partner Number

• Central Person

• Expert ID

• Team ID

• User Name

One employee should be attached to one business partner. Each business partner must have one central person, expert ID, and user ID .

If you do not enter a business partner or a range of business partners, the report displays a selection of all business partners.

Team Overview Report output for the Team Overview option includes:

• Team ID

• Team Description

• Employee ID

Procedure Either go to the SAP xRPM Implementation Guide (IMG) and choose Utilities → Employee Overview or start transaction SE38. and run the report RPM_EMPLOYEE_DATA.



Updating Project Dashboard Data Use This utility enables you to add Project Dashboard data to the database whenever changes are made.

To do this, you run the report RPM_PROJECT_SAVE_DERIVED_DATA.

• If you are installing SAP xRPM for the first time, you should run the report anyway

• If you already have an instance of SAP xRPM, you can run the report to add existing project data

Updating Project Dashboard data in this way improves performance.

Procedure Go to the SAP xRPM Implementation Guide (IMG) and choose Utilities → Update Project Dashboard Data or perform the following steps: ...

1. Start transaction SE38, and run the report RPM_PROJECT_SAVE_DERIVED_DATA.

2. Enter appropriate values for project ID.

To account for all existing projects, leave the From and To fields blank.

To ensure a consistent Project Dashboard display, schedule this report as a daily background job.



Business Add-Ins Business Add-Ins (BAdIs) enable you to add your own code for processing data according to your own requirements. To implement your own code with BAdIs, use transaction SE19. Before adding code to the implementation methods, you should activate the new implementations.

Currently available BAdIs include:

BAdI Description

RPM_BUPA_CUST_FIELDS BUPA customer fields

RPM_CALC_BUPA_BPFTE Calculate the business partner availability

RPM_CALC_STAFF_ICON calculate the staffing icon

RPM_CREATEUSR_NAME Generates user names

RPM_HR_IN_IF001 Customer exit for inbound time processing

RPM_HR_IN_IF002

RPM_HR_IN_IF003

RPM_HR_IN_IF004

RPM_HR_IN_IF005

RPM_HR_IN_IF006

RPM_INTEGRATION_OPTS get and set the project integration options

/RPM/OBJECT_SERVICES Object support services

/RPM/PERSON_CUST_FLD Resource customer fields

RPM_PROCESS_DATA Inbound processing of time data by customer

Exception Handling If you want to create exceptions, you must create your own exception handling class, which should be a subclass of the CX_ROOT class. You raise these exceptions in the BAdI methods. If warning messages occur when performing a syntax check in the methods, you can ignore them. The exception class definition should be loaded. Before you deactivate a BAdI implementation, remember to comment out all the exceptions raised in your methods to avoid any error in the pool class. When you activate the BAdI, you can uncomment them.

Example To see an example implementation, see the BAdI RPM_CREATE_NAME, which is delivered with the standard release includes sample code for name generation.



Customer Includes Customer includes are added to the structures, so that you can add your own attributes for any SAP xRPM object. To add your own fields: ...

1. Click on the CI_* include.

This creates a new structure called CI_*.

2. Add the fields to the structure.

Fields of data type string are not supported.

The fields added to the CI_* structures are automatically included in the relevant iViews available in the Business Package for Projects, Portfolio Management and Design Collaboration (PPMDC).

In general, there are two different types of CI_* include:

• Fields that are added to the database

These are input fields in the relevant iViews.

• Derived fields that are filled by implementing Business Add-Ins (BAdIs)

These are display-only fields in the relevant iViews.

The enhancement category for the CI_* include structures should have the enhancement category Cannot be enhanced.

All customer fields are part of database tables (direct or indirect), so decide carefully whether to add or delete fields to or from the CI_* structures.

To implement your own processing with BAdIs, use transaction SE19. Before adding code to the implementation methods, activate the new implementations.

configuration content for sap xrpm 4.0 sp0 (from sdn)

Documents