on 01-22-2007 9:18 AM
Hello Forum Members,
I am new to xRPM4.0 . I have some queries regarding xRPM, those are as follows,
<b> 1. Which technology xRPM4.0 Application is built on ?
2. Is it possible to customize the application if required ? If yes, then how ?
</b>
Thanks and Regards,
Sugata Basu
Hi,
Runtime Technology
Java/Web Dynpro (WAS 6.40 and higher)
Technical Name
com.sap.pct.cprxrpm.cache_admin
Available for Portal(Release)
Enterprise Portal 7.0 (SP4)
Data Source
sap.com/xappscprxrpmcommon CacheAdminApp
Yes you can customize it. May be some ABAP / Basis guy can help on that.
Enjoy SAP....
Dont forget to give point if its useful ans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ketan,
You said it can be customized.Can you please through some more light on that?
The application is built on Webdynpro/Java technology, so will any ABAPer really would be helpful or we must look for some Java specialist for that? What I meant to say is that,customization would be done from ABAP side or we need to manipulate Java Codes or iVIEWs?? Please give me some detail knowledge.
Although your reply has answered me partially so I have awarded you with points.
Sugata
Custom Configuration
Technical Data
Runtime Technology
Java iView
Technical Name
com.sap.pct.cprxrpm.cust_config
Available for Portal(Release)
Enterprise Portal 7.0 (SP4)
Data Source
sap.com/xappscprxrpmuiptnconfig ConfigApp
Languages
Available in the package languages
Support
EP-PCT-RPM
Features
In the Administration context is a Custom Configuration link which opens the Pattern Configuration iView. The Pattern Configuration iView provides central access to xRPM pattern configuration for the Portfolio Administrator. The Pattern Configuration screen allows the user to configure charts and patterns which are then viewable in other contexts. Pattern Configuration exposes the configuration components of the following patterns:
· Dashboard Patterns
· Charting Patterns (for charts and tables)
· Cockpit Configuration
The patterns can be configured with these data sources:
¡ /Rpm/Portfolio_Getlist
¡ /Rpm/Bucket_Getlist
¡ /Rpm/Item_Getlist
¡ /Rpm/Review_Getlist
¡ /Rpm/Qnnr_Get_List
¡ /Rpm/Person_Getlist
¡ /Rpm/Decision_Point_Getlist
This allows the administrator to configure runtime instances for these patterns and store the corresponding configuration metadata in the J2EE runtime repository.
Once the patterns have been selected, and the data sources chosen in the Pattern Configuration screen in the Administration context, then user charts, tables and dashboards will contain data formatted in the manner the user has configured, and they will be viewable via the Reporting Cockpit to one of the Analytics iViews located in the other contexts:
Context
To Access the Analytics iView
Portfolio Management context
At the Portfolio level context, click the Reporting Cockpit link.
For the Item level context, open an Item, then click Reporting Cockpit link.
For the review context, click Reviews link, select a Review, then click Reporting Cockpit link.
For the bucket level context, click Portfolio Structure, select one Bucket, then click Reporting Cockpit link.
Item Management context
Select an item, then click Reviews link, select a Review, then click Reporting Cockpit link.
In addition to allowing the user to select a pattern and a data source, the features on the Pattern Configuration screen also allow the user to:
· Enter and edit configuration data for dashboard configurations
· Enter and edit configuration data for charting configurations
· Enter and edit configuration data for cockpit configuration
· Save specific configuration instances
· Preview specific configuration instances
· Load existing configuration instances per data source and per pattern
· Delete specific configuration instances.
Important
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, and all dashboard configurations, and all cockpit configurations are bound to a Data Source.
Pattern
Configurations
Dashboard Patterns
The dashboard configuration screen allows the user 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, e.g. the visual component Portfolio Dashboard has its own configuration PortList.
Charting Patterns
The chart configuration screen allows the user 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 Configuration
The cockpit configuration screen allows the user 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.
Integration
Pattern
Integration
Dashboard Patterns
The dashboard configuration is integrated into the pattern configuration.
After a configuration has been saved, it can be selected in the cockpit configurator, where existing chart and dashboard configurations can be combined into one cockpit configuration.
The Analytics view 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 Patterns
The chart configuration is integrated into the pattern configuration.
After a configuration has been saved it can be selected in the cockpit configurator, where several chart and dashboard configurations can be combined to one cockpit configuration.
The Analytics view 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 Configuration
The cockpit configuration 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 Analytics view 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.
Prerequisites
Dashboard Patterns
· The iView must be connected to the backend system.
· No special plug-in is required.
· No specific support package/ patch is required.
· The dashboard configuration has to be set in the iView properties.
· No legal requirements are known.
Charting Patterns
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
· tcwddispwda
· Propertysheet.default
IGSUrl
Cockpit Configuration
Create chart and dashboard configurations as needed for your cockpit.
Settings
This application is an administrative tool and requires no high level customization.
Users can follow steps to create new dashboard configurations, new chart configurations and new cockpit configurations.
To create a new dashboard configuration, users take the following steps:
Select a data source
Enter a descriptive table title in Dashboard Header
Enter a value for Width (Note: The width can be entered either in pixel or percentage (e.g. 600px/ 75%)
If no width entry is made, the table width is defaulted to 100%.
Check values for table sorting/ filtering
Select required buttons on the dashboard toolbar.
Add dashboard columns by selecting single/ multiple fields in the table Fields and pressing the button Add as Column(s).
Move added dashboard columns up or down by using buttons Move up/ Move down on the table Dashboard Columns.
Remove no required columns from the table Dashboard Columns by selecting column and pressing button Remove.
Configure each column to be either text, link, or linked icon by checking values for Icon and Link in every selected column.
Press button Preview to view runtime instance of current configuration data.
Enter configuration name in Save as and press button Save.
To create a new chart configuration, users take the following steps:
Pick a chart type, which matches your requirements
Fill out all header fields like Description, Chart Header and so on.
Assign one field to each chart dimension
To assign a field to a chart dimension
Select the chart dimension either via the drop-down list-box or by selecting the corresponding row in table Chart Dimensions
After a chart dimension has been selected a filter is set for row Data Type in table Fields. So only fields are shown with at data type which matches the selected chart dimension. It is not recommended to assign fields with a different data type then the suggested one. Most of the times this would cause a dump when the chart is rendered.
Assign a field to the chart dimension by simply selecting the corresponding row in the Fields table and pressing the Map button.
Save the configuration.
After the configuration has been saved it can be assigned to a cockpit configuration.
The following chart types are currently supported:
Portfolio Chart
Each rendered object is represented by one circle; the position and size of that circle are defined by assigned dimensions.
A vs. B Portfolio Chart
Each rendered object is represented by one circle; the position and size of that circle are defined by assigned dimensions. This chart can be used as a Risk/Reward diagram.
Column Chart
Each rendered object is represented by one column Used to do a simple nominal comparison
Column Sets Chart
Each rendered object is represented by 3 column Used to compare forecast / planned / actual numbers of several objects
Bar Chart
Each rendered object is represented by one bar Used to do a simple nominal comparison
Gantt Chart
In this chart the x-axis represents time. Each rendered object is represented by one bar with its length defined by the assigned start and end time of that object.
Gantt Sets Chart
In this chart the x-axis represents time. Each rendered object is represented by 3 bars with their length defined by the assigned start and end times of that object. Used to compare forecast / planned / actual dates of several objects
To create a new cockpit configuration, users take the following steps:
Fill out all header fields like Description, Cockpit Header and so on.
Add as many tables or charts as you need to your cockpit by pressing the button Add Table/Chart.
You can get a first idea how the cockpit is going to look like from the Cockpit Layout area.
You can arrange the position of each cell (chart or dashboard) within the cockpit by
Changing the number of columns of the cockpit (change the value in field Columns and press button Apply)
Selecting a cell and pressing one of the Move buttons
Changing the column span of a cell (Select a cell, change the value of field Column Span and press button Apply Changes)
Define the content of each cell
Select a cell
Set the cell to be a chart or dashboard via the matching radio button
If the cell is a chart assign a chart configuration
If the cell is a dashboard assign a dashboard configuration
If you have set the header field Place in individual Trays provide a Tray Title
Save the configuration.
After the configuration has been saved it can be assigned to a cockpit configuration.
For technical reasons a cockpit can be previewed only once without restarting. If a user wants to preview it again, the user must save the configuration, restart the iView (by pressing the link Custom Configuration on the left hand navigation panel) and then reload the newly saved configuration. Only then can the user press preview a second time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.