Ansicht
Dokumentation

SAP xRPM 2.0: Backend Release Notes ( RELNXAP_RPM_20 )

PERFORM Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Short text

SAP xRPM 2.0: Backend Release Notes

Release Notes for SAP xRPM 2.0 Initial Version

Global Settings

The SAP xRPM global settings have been updated in the following areas:

• Capacity Management

There is a new global setting for hours worked.

• Master Switches

This is a new area that enables you to switch specific components or features on/off.

In SAP xRPM 2.0, there are master switches for:

• Resource Pools

Resource pools are disabled on delivery.

If you intend to use resource pools, you must create them and assign them to resource managers in the frontend application. You can them enable them here by setting the appropriate master switch.

• SAP Expert Finder

SAP Expert Finder is disabled on delivery.

If you intend to use SAP Expert Finder, you must follow the setup steps in the SAP xRPM Implementation Guide (IMG) and then enable it here by setting the appropriate master switch.

For further information, see the section SAP Expert Finder below.

• HR Integration

The global settings for HCM Integration have been updated.

When upgrading from SAP xRPM 1.0 to SAP xRPM 2.0, you should check any settings that you have overridden with your own values.

For further information, see the following steps in the SAP xRPM Implementation Guide (IMG):

• Global Customizing -→ Define Global Settings

• Global Customizing -→ Override Default Global Settings

Portfolio Prioritization

You can now define portfolio prioritization settings, which specify the criteria you want to be available to users in the frontend application for analyzing and prioritizing projects, by editing the table V_RPM_PRIO_OBJ.

There is also a customer exit called CUST_ANALYZE_PROJECTS that enables you to analyze projects based on customer fields.

Project Approval Status / Project Execution Status: Next Status Settings

For each defined project approval status and project execution status, you can now define the next project approval status and the next project execution status .

This provides users in the SAP xRPM frontend application with a list of valid status settings that they can select based on the current status.

If you are upgrading from SAP xRPM 1.0 to SAP xRPM 2.0, you can do either of the following:

• Maintain the next status manually

To do this, go to the SAP xRPM Implelentation Guide (IMG) and choose Global Customizing → Override Defaullt Global Settings.

• Run the conversion program RPM_CONVERT_APST_EXST described in the section Utilities below

SAP Human Capital Management Integration

You can now maintain logical system information for employees in the SAP HCM System. This helps to identify the source system of employees in the case of multiple systems and ensures correct data transfer to the SAP xRPM System.

SAP Exchange Infrastructure (XI) is available as an optional component for integrating the software components in your system landscape, but the existing mechanism of ALE and RFCs is still offered.

For further information about SAP XI, see the SAP XI documentation.

SAP cProjects Integration

You can now use SAP cProjects as your base project system in addition to SAP Product Lifecycle Management - Project System (PLM PS) and Microsoft Project.

When linking the business object types supported by SAP xRPM with the business objects supported by SAP cProjects, you must also define an HTTP connection for each business object type. This enables HTTP calls from the SAP xRPM system to the SAP cProjects system in order to upload project data to SAP xRPM.

For further information, go to the SAP xRPM Implementation Guide (IMG)and see the steps under Base System Interfaces -→ SAP cProjects Integration.

Capacity Management

There is a new global setting for the number of hours worked.

You can also maintain the calendar to suit your requirements by editing the delivered public holiday definitions factory calendar.

Business Partner Administration

If you are upgrading from SAP xRPM 1.0 to SAP xRPM 2.0, you should run the utility RPM_CONVERT_BUPA_LOCATION to convert business partner locations to their new formats.

For further information, see under Utilities below.

For full update of all data, you are also recommended to resynchronize your ALE distribution to the system.

Application Field Mapping

You can now define the mapping of SAP xRPM application fields to support activities in the frontend application.

You can:

• Assign currency fields and numeric fields to the Expected Commercial Value (ECV) Chart displayed under Project Portfolio Analytics

• Assign a linked business object to your customer-specific application fields

This business object supports users by providing an extended search capability to facilitate the entry of values in the referenced customer fields and validating the data entered.

• Link fields to a spreadsheet and, if required, identify the specific cell references.

SAP Expert Finder

SAP Expert Finder is an integral part of the SAP Web Application Server Cross-Application Component (SAP_ABA), which is a required component for the installation of SAP xRPM. However, SAP Expert Finder is now an optional component for SAP xRPM and is therefore shipped as disabled.

If you decide to use SAP Expert Finder with SAP xRPM, you must follow the setup steps described in the SAP xRPM Implementation Guide step SAP xRPM → Basic Settings → Set up SAP Expert Finder and explicitly enable the component by setting the relevant master switch.

For further information, see Global Settings above.

If you are upgrading from SAP xRPM 1.0 to SAP xRPM 2.0, you must also run the following conversion programs to update business partners, roles, and team definitions:

• RPM_CONVERT_BUPA_LOCATION

• RPM_CONVERT_BUPA_ROLE

• RPM_CONVERT_TEAM_MEMBERS

For further information, see Utilities below.

New Utilities

RPM_CONVERT_APST_EXST

This utility sets up project approval status values and project execution status values.

When upgrading from 1.0 to 2.0, this program enables you to populate the new field containing the next status value for all existing project approval and project executions statuses. In each case, the next status defines the next status available for a particular project approval status or project execution status.

You can run this report in simulation mode without updating the database.

To maintain the next status values, you can either run this utility or maintain them manually as described in the SAP xRPM Implementation Guide (IMG) step

For further information, see the report documentation.

RPM_ASSIGN_GLOBAL_ROLE

This utility enables you to assign global roles to project roles.

On the selection screen, you can enter a single project ID, a range of project IDs or leave the selection blank if you want to check gloabl role assignment for all projects.

The report output displays all roles that do not have global roles and you can then assign them accordingly.

For further information, see the report documentation.

RPM_GLOBAL_ROLE_FROM_JOB

This utility enables you to create global roles for jobs transferred from the SAP HCM system to the SAP xRPM system.

On the selection screen, you enter the jobs for which global roles should be created. You can restrict the selection by language and date and even run the report in simulation mode with no database update.

The report output displays a list of all global roles created and indicates where errors have occurred.

For further information, see the report documentation.

RPM_CONVERT_BUPA_LOCATION

This utility converts all SAP xRPM 1.0 business partner locations to their SAP xRPM 2.0 business partner location formats.

For further information, see the report documentation.

RPM_CONVERT_ROLE

This utility converts all SAP xRPM 1.0 role profiles (qualifications, locations, and key terms) to their SAP xRPM 2.0 role profile formats.

For further information, see the report documentation.

RPM_CONVERT_TEAM_MEMBERS

This utility converts all SAP xRPM 1.0 team definitions to their SAP xRPM 2.0 team definition formats.

For further information, see the report documentation.

RPM_ADD_V2_PROJECT_SETTINGS

This utility adds global time breakdown type and allocation/demand units to the projects, which do not have these.

For further information, see the report documentation.

Enhanced Utilities

RPM_CHECK_DB_CONSISTENCY

This database consistency check utility has been enhanced to check the consistency of global roles.

For further information, see the report documentation.

RPM_EMPLOYEE_DATA

This employee overview utility has been enhanced in the following areas:

Date Consistency

When running the utility with the Location filter, you can now check the consistency of dates in the location table, because the report output includes a column called Consistent Dates.

• If the dates are consistent, a green tick is displayed

• If the dates are inconsistent, a red cross is displayed

• If no data is maintained, the value Null is displayed

If dates are inconsistent or no data is maintained, you can choose Maintain location to correct the data or create a new record.

If there are multiple records, the dates must be continuous. Also, dates must always end with a high date ( for example 31.12.9999 ).

Displaying Attributes

When running the report for all employee data, you can now display and edit the default attributes of an employee or business partner (for example , category, subcategory, global role).

To edit the attributes, choose Edit Attributes. You can only edit one Business Partner at a time.

Data Transfer Tool (Transaction RPM_DX)

• Project Upload (RPM_DX_PROJECT)

This program has been enhanced to allow upload of project descriptions and a single comment. Multiple comments per project are not currently supported.

• Project Stakeholders Upload (RPM_DX_PROJECT_STKHLD)

This program enables you to upload multiple project stakeholders using the new stakeholders data transfer program RPM_DX_PROJECT_STKHLD. It complements the standard projects upload program RPM_DX_PROJECT, which only allows a single entry for each stakeholder role type (project manager, resource manager, project approver, and project reviewer) to be transferred.

Release Notes for SAP xRPM 2.0 Support Package 1

Global Settings

There is a new area 0007 (General Default Values) for storing general default settings.

The following default settings apply for the exchange rate type and the destination system for the conversion:

0001	Currency Exchange Rate Type	M
0002	Exchange Rate RFC Destination	No value

The Exchange Rate RFC Destination is the SAP R/3 system where you maintain your exchange rates. SAP xRPM uses this RFC destination to access the exchange rates stored there.

Both the above parameters are used in what-if scenarios where users can select a group of projects and specify their budgets and other financial data to simulate the financial impact. Since the projects they select may have different currencies, the system has to convert the currencies and currency amounts to a single currency and currency amount for the scenario. Users may change the currency used for the simulation as well, so currency conversions are necessary.

You can override the default currency exchange rate type and define your own RFC destination for the conversion.

For further information, see the following steps in the SAP xRPM Implementation Guide (IMG):

• Global Customizing -→ Define Global Settings

• Global Customizing -→ Override Default Global Settings

Scenario Settings

Portfolio Prioritization Scenarios

When defining settings for portfolio prioritization scenarios, you can enter the names of the fields you want to be used as criteria for prioritizing projects.

For further information, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing -→ Scenario Modeling Settings -→ Define Portfolio Prioritization Settings.

What-If Scenarios

You can define the fields you want to be available to users in the frontend application for analyzing what-if scenarios. These fields are used as criteria for simulating the impact of changes on the budget across several projects and/or project proposals.

Possible settings include amount fields from the project database as well as any of your own customer fields.

In Support Package 1, only the project database attributes numeric field and currency field are supported. Derived attributes are not supported.

For further information, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing -→ Scenario Modeling Settings -→ Define What-If Scenario Settings.

Task Settings

You can select the task execution status values available to users in the Task Dashboard for defining the status of tasks.

For further information, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing -→ Task Settings -→ Define Task Execution Status.

Status Icons for Customer Fields

You can assign status icons to your customer fields.

For further information, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing -→ Assign Status Icons to Customer Fields.

Employee Data Integration Using SAP Exchange Infrastructure (XI)

SAP Exchange Infrastructure (XI) supports the implementation of cross-system business processes by integrating both SAP and non-SAP systems located on different platforms.

In xRPM 2.0 SP1, you can use this ability to facilitate the transfer of data between SAP xRPM and several backend applicaton systems.

This enables you to transfer employee personal data between the SAP Human Capital Management (HCM) system and the SAP xRPM system.

Portal Settings

All portal settings have been removed from the SAP xRPM Implementation Guide (IMG). You now configure all iView properties on the frontend after installing the SAP xRPM Business Package.

For further information about configuring the SAP xRPM frontend application, see the documentation Business Package for SAP xRPM 2.0.

User Exits

For what-if scenarios, the Business Add-In RPM_WHATIF_SCENARIO provides users with methods to convert currency amounts of additional data fields individually

New parameters have been added to the user exits for dependencies and portfolio prioritization

For further information, go to the SAP xRPM Implementation Guide (IMG) and choose Global Customizing -→ User Exits for SAP xRPM Core.

Release Notes for SAP xRPM 2.0 Support Package 2

Application Data Integration Using SAP Exchange Infrastructure (XI)

SAP Exchange Infrastructure (XI) supports and simplifies the implementation of cross-system business processes by integrating both SAP and non-SAP systems located on different platforms.

In xRPM 2.0 SP2, you can use SAP XI to facilitate the transfer of data between SAP xRPM and different backend applicaton systems.

You can:

• Transfer employee time data between SAP Human Capital Management (HCM) and SAP xRPM

• Transfer financial data between SAP Financial and Controlling (FI-CO) and SAP xRPM

Microsoft Project Integration

The ability to integrate project data between Microsoft Project and SAP xRPM has been enhanced.

You can now synchronize your project plan with SAP xRPM from the following Microsoft Project versions:

• Microsoft Project Client

• Microsoft Project Server 2002

• Microsoft Project Server 2003

If you want to integrate data between SAP xRPM and Microsoft Project Server 2003, you need to install the Project Data Services (PDS) extender.

For further information, see the SAP xRPM Master Guide at:

http://service.sap.com/instguides
→ SAP xApps → SAP xApp Resource and Program Management → SAP xRPM 2.0.

External ID Generation

You can now generate your own ID values for external IDs attached to SAP xRPM data objects

SAP xRPM objects such as projects, project templates, roles, role templates, tasks, team master data, resource pools, and what-if scenarios contain an ID field for object reference purposes. Until now, users in the frontend application had to assign these ID values themselves and the system checked that each value was unique.

Now, you can generate your own external ID values that override entries by the user or values generated by the system alone by implementing custom code in the Business Add-In (BAdI) RPM_OBJECT_SERVICES. This enables you to define rules to suit your own requirements and apply validation routines to enforce those rules, .

You may, for example, want to have your own number ranges, prefixes or suffixes, or define ID values according to project attributes.

Custom Field Dropdown Values

To determine the dropdown values for custom fields displayed in the SAP xRPM frontend application, you can implement custom code in the Business Add-In (BAdI) RPM_OBJECT_SERVICES.

If you do this, an icon next to these fields indicates to the user that entry help is available through either a dropdown list of values or the selection list supported by business object link management.

If you like, you can also make the displayed values depend on the context. In this way, you can display different dropdown values for different projects, project categories and other project objects, depending on the context variables.

Dependency Status Groups

Dependency status groups enable you to determine the level of risk for project dependencies by setting upper and lower limits in days. You can also assign an appropriate status icon to each dependency status group for display to users in the Project Dashboard and other iViews of the SAP xRPM frontend application.

You can define as many dependency status groups as you like in ascending order of risk starting from 1.

For example, if you define four dependency status groups from 1 to 4, dependency status group 1 would indicate lowest risk, while dependency status group 4 would indicate highest risk.

Mapping SAP PLM PS Objects to SAP xRPM Task Status

You can now map objects project structure elements in the SAP Product Lifecycle Management - Project System (PLM PS) such as WBS elements, networks, network activities, and network activity elements to the task status in SAP xRPM.

This means that when users upload these objects from SAP PLM PS to SAP xRPM in the frontend application, their status in SAP PLM PS is mapped to the status of the relevant SAP xRPM task.

To prevent your SAP xRPM status settings from being overwritten by a project upload, you can use the user exit RPM_PLMPS_INTF to set the SAP xRPM status to the original task status and define your own mapping rules.

Authorization Checking

To extend the standard authorization check based on project category and subcategory, you can define your own authorization rules determining who can create, change, display, and delete projects and project subobjects (for example, tasks, roles, resources, and teams) by implementing custom code in the Business Add-In (BAdI) RPM_PROJ_CUST_FIELDS.

In the standard authorization check, the function module RPM_CHECK_AUTHORIZATION processes the authorization object RPM_PROJ, which allows users to access only projects in specific project categories or project subcategories.

If you supplement the standard authorization check by implementing your own custom code, the results of the standard authorization check are passed to the BAdI method for further processing.

New Utilities

When upgrading from Support Package 1 to Support Package 2, you should run the utilities listed below through transaction SE38.

RPM_CONVERT_CUST_FIELDS_ICON

If you customized any icons for custom fields in Support Package 1, run this utility.

RPM_CONVERT_SP1_WI_SCENARIO

To enhance the what-if scenarios you created in Support Package 1, run this utility to allow the planning of total role demand and resource allocation in simulated projects of what-if scenarios. This is a new feature in Support Package 2.

Release Notes for SAP xRPM 2.0 Support Package 3

Currency Conversion Changes

The currency conversion function module RPM_GET_CURRENCY_EXCHANGERATES now derives the exchange rate type and the RFC destination for determining the exchange rate from the global settings. To find these values, go to the SAP xRPM Implementation Guide (IMG), choose Global Customizing → Global Settings, and look under 0007 (General Default Values).

Object Link Enhancements -R/3 Business Partner Proxy Class

An SAP xRPM proxy class is now deployed to interface with SAP R/3 to retrieve business partners. This proxy class is intended to support SAP xRPM object link functionality and offers search, existence check, and content validation features available for object links. The proxy class is based on the SAP R/3 BAPI function BAPI_BUPA_SEARCH. By default, SAP R/3 business partners with a partner category of Personsmay be addressed by the proxy class.

Customizable Project Info iView Links

SAP delivers several standard links for display in the Project Info iView, depending on the role. If you want to use the standard links, you can now define your own links by either adding them to the existing links or overwriting the existing links as required. You define these links as either navigation links or action links.

FI-CO Integration and IM Integration

A correction has been implemented to settle costs derived from FI/CO. Previously, settled costs were not transferred to SAP xRPM, because they were cancelled out by their corresponding settlements. Settled costs are now transferred.

Unit Handling

Time units are used in SAP xRPM to store and report role demand and resource supply. To facilitate integration with other SAP applications, SAP xRPM now uses time units defined in the standard SAP unit of measurement table T006 instead of the three fxed units used previously: FTE(Full Time Equivalent), DAY(Person Day) and HRS(Hours). This means that you can configure the time unit(s) you want to use. You can continue to display role demand/resource allocation in FTE.

For existing projects, programs have been provided to back up the role demand, resource allocation, and business partner availability, and convert them to a new standard unit. You must run these programs after upgrade to SAP xRPM 2.0 SP3 and before you create new projects or change existing projects. For further information, see SAP Note 758553.

SAP xPD Integration

Integration with SAP xApp Product Definition (xPD) enables users in SAP xPD to upload concepts to SAP xRPM and display them as project proposals.

SAP PLM PS Integration Improvements

SAP Product Lifecycle Management - Project System (PLM PS) integration has been enhanced to provide the following additional functionality:

Upload:

• Support for network activities and network activity elements as SAP xRPM roles

• Support for assigned resources to network activity elements as SAP xRPM resources and their assignment to corresponding SAP xRPM roles (SAP R/3 Enterprise only)

• Support for assigned teams to network activities and network activity elements as SAP xRPM teams and resources (requires SAP Plug-In 2004.1 SP3)

Download:

• Support for the creation of projects in SAP PLM PS (requires SAP Plug-In 2004.1 SP3)

SAP cProjects Integration Improvements

SAP cProjects integration has been enhanced to provide the following additional functionality:

Upload:

• Multiple upload options to support individual uploads of tasks, roles, resources, and resource assignments

Download:

• Support for the creation of projects in SAP cProjects (SAP cProjects 3.1 only)

Microsoft Project Integration Improvements

Microsoft Project Integration has been enhanced to provide the following additional functionality:

Microsfot Project Server 2003:

Download:

• Support for the download of SAP xRPM project resources as resources in the Microsoft Project plan.

What-If Scenario Enhancements

The duration of what-if scenarios is now based on the earliest planned start date and budget years, and the latest planned end date and budget years, of the original projects selected in the scenario.

• The past time frame is calculated by subtracting the value of the global setting for the past time frame from the earliest planned start date

• The future time frame is calculated by adding the value of the global setting for the future time frame to the latest planned end date

The budget tables for the projects and the scenario are updated with the years covered by this period. By default, a year for undistributed budget (year 0000) is also added to the budget for all projects and the scenario budget.

The handling of what-if scenarios has also been adjusted to conform to the unit handling conventions.

Addresses (Business Address Services)   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 32245 Date: 20240523 Time: 053940     sap01-206 ( 438 ms )