Technical Data
Runtime Technology |
Java iView |
Technical Name |
com.sap.pct.cprxrpm.cust_config_iview |
Available for Portal(Release) |
Enterprise Portal 7.0 (SP4) |
Data Source |
sap.com/xapps~cprxrpm~ui~ptn~config ConfigApp |
Languages |
Available in the business package languages |
Support |
EP-PCT-RPM |
This iView gives you central access to xRPM pattern configuration for the portfolio administrator. The custom configuration screen allows you to configure charts and patterns which you can then see in other contexts in the reporting cockpit.
You navigate to this iView by choosing Portfolio Management → Administration. Choose Custom Configuration.
You can configure the following patterns:
· Dashboard Pattern
· Charting Pattern (for charts and tables)
· Cockpit Pattern
You can configure the patterns with the following data sources:
● Rpm_Item_Getlist-Et_Items
● Rpm_Questionnaire_Getlist-Et_Qnnr_Hdr
● Rpm_Portfolio_Getlist-Et_Attributes
● Rpm_Review_Getlist-Et_Reviews
● Rpm_Person_Getlist-Et_Bupa
● Rpm_Bucket_Getlist-Et_Attributes
● Rpm_Decision_Point_Getlist-Et_Schedule_Chart
● Rpm_Collection_Getlist-Et_Collection
● Rpm_Item_Version_Hdr_Getlist-Et_Item_Version_Hdr
● Rpm_Fin_Category_Get_Chart-Et_Fin_Plan
● Rpm_Fin_Group_Get_Chart-Et_Fin_Plan
● Rpm_Cap_Category_Get_Chart-Et_Cap_Plan
● Rpm_Cap_Group_Get_Chart-Et_Cap_Plan
● Rpm_WhatIf_Getlist-Et_WhatIf
● Rpm_Substitution_Display-Et_Substitutes
● Rpm_Team_Md_Get_List-Et_Teams
● Dependency_Getlist-Dependency_Predecessor
● Dependency_Getlist-Dependency_Successor
This allows the administrator to configure runtime instances for these patterns and store the corresponding configuration metadata in the J2EE runtime repository.
Additionally, you can do the following:
● Save specific configuration instances
● Preview specific configuration instances
● Load existing configuration instances per data source and per pattern
● Delete specific configuration instances
You find the reporting cockpits in the portfolio management context as follows:
· At portfolio level: Click Reporting Cockpit.
· At collection level:Click Collections and click one of the collections to select. Click Reporting Cockpit.
· At review level: Navigate to item level, click Reviews, select a review, then click Reporting Cockpit.
· At bucket level: Click Portfolio Structure of Buckets, select one bucket, then click Reporting Cockpit.
Configurations are bound to a data source. A data source represents a RFC function module return table – for example data source Rpm_Item_Getlist-Et_Items represents the return list of RFC function /RPM/ITEM_GETLIST.
Different data sources contain different fields (for example, an item has different attributes than a portfolio), hence all chart configurations, all dashboard configurations, and all cockpit configurations are bound to a data source.
Pattern |
Configurations |
Dashboard Pattern |
The dashboard configuration screen allows you to create new and modify existing dashboard configurations. A dashboard configuration defines how the result of a specific query is rendered in a dashboard pattern instance. For every dashboard visible to the user, a pattern instance has to be configured, for ex. the visual component Portfolio Dashboard has its own configuration PortList. |
Charting Pattern |
The chart configuration screen allows you to display and modify existing chart configurations and to create new chart configurations. A chart configuration defines how the result of a specific query (the data returned by a specific data source) is used to render a chart. |
Cockpit Pattern |
The cockpit configuration screen allows you to display and modify existing cockpit configurations and to create new cockpit configurations. A cockpit configuration defines how the result of a specific query (the data returned by a specific data source) is used to render one or more charts and or dashboards. Cockpit configurations are also bound to a data source, so within a cockpit configuration only chart and dashboard configurations from the corresponding data source can be used. |
Pattern |
Integration |
Dashboard Pattern |
The dashboard configuration is integrated into the pattern configuration. After a configuration has been saved, it can be selected in the cockpit configuration screen, where existing chart and dashboard configurations can be combined into one cockpit configuration. The reporting cockpit for portfolios, buckets and reviews renders for each of the charts or dashboards as defined in the used cockpit configuration all items within that portfolio, bucket or review respectively. Each of these dashboards is rendered as defined in the corresponding dashboard configuration. |
Charting Pattern |
The chart configuration is integrated into the pattern configuration. After a configuration has been saved it can be selected in the cockpit configuration screen, where several chart and dashboard configurations can be combined to one cockpit configuration. The reporting cockpit for portfolios, buckets and reviews renders for each of the charts or dashboards as defined in the used cockpit configuration all items within that portfolio, bucket or review respectively. Each of these charts is rendered as defined in the corresponding chart configuration. |
Cockpit Pattern |
The cockpit pattern is integrated into the pattern configuration. To assign any chart or dashboard configurations to a pattern, the pattern configurations must first have been created. The reporting cockpit for portfolios, buckets and reviews renders for each of the charts or dashboards (as defined in the user cockpit configuration. See below) all items within that portfolio, bucket or review respectively. |
Dashboard Pattern |
· The iView must be connected to the backend system. · The dashboard configuration has to be set in the iView properties. |
Charting Pattern |
To render charts, the J2EE has to be linked to a running IGS via HTTP. The IGS URL is set up in the J2EE Administration ● Cluster ¡ Server ¡ Services ¡ Configuration Adapter ■ webdynpro ■ sap.com ■ tc~wd~dispwda ■ Propertysheet.default ■ IGSUrl |
Cockpit Pattern |
Create chart and dashboard configurations as needed for your cockpit. |