Personal Insights
Overcoming hurdles during the new setup of SAP PPM
Hello Friends. This time I would like to present how to overcome some of the common issues when setting up SAP PPM newly in an on-premise system. Most of the time, I normally look into my repository of learnings to fix these. I thought that it will help many beginners if they have this information handy. That’s the rationale behind this blog post.
Specifically, I addressed 4 topics below. By resolving these, a consultant can get up to speed. Consequently, he can continue to configure the PPM solution and cross verify the corresponding behaviour.
1. URL link for SAP PPM:
To start with, a consultant needs the URL to access the PPM application. Most commonly the URL for SAP PPM will be
https://<host>:<port>/ui2/nwbc/~roletest/SAP_BPR_PPM/?sap-client=<client> OR http://<host>:<port>/ui2/nwbc/~roletest/SAP_BPR_PPM/?sap-client=<client>
The details of <host> & <port> can obtained by getting the details from the transaction code SMICM
2. Service not reached
When the PPM application is opened, it may throw an error saying, “Service cannot be reached”.
This is because the services are not activated in the transaction SICF. Depending on the version of SAP PPM you can refer to the respective configuration content. For example, the configuration content for SAP PPM in S/4HANA 2020 is available in the OSS Note “2941609 – SAP Portfolio and Project Management in SAP S/4HANA 2020: Configuration Content”. For quick reference, most of the services are listed below. However, the list may keep changing according to the version on SAP PPM.
| Area | Host | Path | Services |
| Portfolio Management | |||
| DEFAULT_HOST | /sap/ | ||
| rpm_file | |||
| DEFAULT_HOST | /sap/public/ | ||
| PPM* | |||
| DEFAULT_HOST | /sap/bc/webdynpro/sap/ | ||
| rpm_bucket_details | |||
| rpm_decision_points_details | |||
| rpm_initiative_details | |||
| rpm_initiative_t_details | |||
| rpm_item_dependency | |||
| rpm_item_details | |||
| rpm_item_temp_details | |||
| rpm_portfolio_details | |||
| RPM_QNNR_DETAILS | |||
| rpm_review_details | |||
| RPM_SMODEL_SCORE_BOARD | |||
| RPM_USER_SETTING | |||
|
rpm_whatif_scenario RPM_COLLECTION_DETAILS |
|||
| inm_dfm_links | |||
| inm_m_metrics_app | |||
| inm_resource_bp_detail_create | |||
| inm_team | |||
| inm_workcenter_app | |||
| inm_resource_pool_fpm | |||
| inm_resource_detail | |||
| inm_timeline_mon_app | |||
| inm_kfm_app | |||
| inm_kfm_sel_app | |||
| DEFAULT_HOST | /sap/bc/webdynpro/rpm/ | ||
| classification_dash | |||
| document_app | |||
| document_t | |||
| fin_cap_planning | |||
| item_dependency | |||
| km_doc_integration | |||
| obj_link_dashboard | |||
| res_mng_details | |||
| transfer_demand | |||
| ui_changedoc_app | |||
| ui_multiple_update | |||
| ui_substitute | |||
| version_header | |||
| wda_dashboard_cust | |||
| res_workcenter_app | |||
| ui_res_dashboard | |||
| print_fact_sheet | |||
| ui_factsheet_app | |||
| wda_list_item_ovp | |||
| Project Management | |||
| DEFAULT_HOST | /sap/ | ||
| cprojects_easy | |||
| cprojects_file | |||
| DEFAULT_HOST | /sap/bc/ | ||
| nwbc* | |||
| DEFAULT_HOST | /sap/bc/webdynpro/ | ||
| bcv* | |||
| plmu* | |||
| DEFAULT_HOST | /sap/bc/webdynpro/sap/ | ||
| abp_launchpad* | |||
| apb_lpd* | |||
| ap_inm_transfer | |||
| cprojects | |||
| cprojects_auth_admin_fpm | |||
| cprojects_doc | |||
| cprojects_fpm | |||
| cprojects_mpmon | |||
| cprojects_settings_fpm | |||
| cprojects_search_fpm | |||
| cprojects_search_global | |||
| cprojects_search_service | |||
| cprojects_search_rpm | |||
| cprojects_services | |||
| cprojects_vacant_roles_fpm | |||
| cprojects_replace_user_bp_fpm | |||
| DEFAULT_HOST | /sap/public/ | ||
| PPM* |
3. 500 Internal Server Error:
When the PPM application is opened, it may throw an error saying, “500 Internal server error”.
This is due to the missing configuration related to Navigation. These configurations can be copied from client 000 using the transaction code /RPM/CUST_COPY. The tables to be copied are the following
- INM_NAV_CTX INM Navigation Context
- INM_NAV_CTX_W INM Navigation Context Workcenter
- INM_NAV_INF_W INM Navigation Information
Select the tables and click on the relevant button to copy the settings from the delivery client (usually 000) to the current client.
You will get a result showing many entries copied as shown below.
After refreshing the browser, we will be able to see the dashboard as shown below.
4. Opening / Editing the PPM object from the Dashboard
It may be possible to create objects. But it is not possible to open this object and look into it or edit it. Because there is no clickable link to open the object. The sample screen of the Portfolio Dashboard is shown below.
This happens because the dashboard customizing is empty. This can be copied from the delivery client 000 using the transaction “/RPM/CUST_COPY”. After invoking the transaction choose the table, and click the relevant button to copy as shown below
After importing the table entries from delivery client 000, it must be possible to get a clickable link to open and navigate to the object as shown below.
Conclusion
Now that we have overcome the initial roadblocks, it is possible to play with the configuration and cross verify the behaviour of the system and finally delivering the solution that is designed to be delivered.
For additional information, please refer to the following.
- OSS Note “2941609 – SAP Portfolio and Project Management in SAP S/4HANA 2020: Configuration Content”
- SAP Portfolio and Project Management – SAP Help Portal – on S/4HANA
- SAP Portfolio and Project Management for SAP S/4HANA – SAP Help Portal – Suite on HANA
- SAP Portfolio and Project Management – SAP Help Portal – PPM 6.1
- Community Page: SAP Enterprise Portfolio and Project Management
You may also like to read my other blogs here
Good One Manju..Very useful
Another great article Manju.
It was a pleasure collaborating and working with you.
Keep going.
Very good article, Manju