Introduction
As part of the latest Service Pack (SP12) of Focused Build for SAP Solution Manager, we are delivering the latest version of solution readiness Dashboard built using the standard SAP Fiori Elements. This blog is part of the blogs series for the new “New Solution Readiness Dashboard.” In this blog, we will understand the pre-requisite settings that needs to be performed for the new dashboard to work effectively.
Steps to configure the solution readiness dasboard
There are couple of reports that needs to be executed as default step in the Solman set up.
Solman Setup- Manual Activity for Dashboard configuration
1. Switch Version History Deletion on/off
With this report, the version history deletion can be activated. The extraction layer for the solution readiness dashboard stores an entry for each change that is made on documents like Requirements, Work Packages, Work Items, Project tasks etc. But currently, only the historical data of work packages and Work items are used in the Progress by card of the dashboard, displaying the progress of work packages and work items through different status over a period.
By switching the version deletion flag on, the versions of all transaction types (except for Work Packages and Work Items) are deleted during a run of report /SALM/DATA_EXTRACTION_PPMITSM retaining only the latest version. Only for Work packages and Work items, the version history is continued to be maintained.
This reduces the number of entries in the tables /SALM/ITREQ, /SALM/PROJECT, and /SALM/PROJECTTSK in turn avoiding unnecessary entries in extraction and improving performance.
2. Progress by Details
To display a progress of status of Work Packages and Work Items in certain cards of solution readiness dashboard, there was a need to introduce a new field 'Extarction Date To' in the extraction table for the dashboards. On executing this report, ‘ext_date_to’ field in the extraction table /SALM/ITREQ is populated.
This report is required to be executed only ones as an initial migration and for the new entries this field is filled during a run of report /SALM/DATA_EXTRACTION_PPMITSM.
3. Measures and Dimensions Report
When we configure the dashboard, as part of Solman set up, it is particularly important to run this report as it generates the dimensions and measures for each of the detail pages. Once we execute this report, the default measures and dimensions are set. And once the OData services for each detail page are refreshed, all the meta data properties are displayed and dashboard.
4. Extraction Job
As part of the new solution readiness dashboard, there is a new report SALM/SRD_FILL_CACHE_ALP introduced to fill the cache layer of the dashboard. This report updates the existing Cache table /SALM/INDX as well as the new ALP (Analytical List Page) tables to display the data in detail pages of the cards.
There is selection check box 'Full Extraction'. If this is selected, all the cache and ALP tables are cleared and reloaded again from extraction layer. When this is unchecked, only the delta changes are copied. The trigger refresh option on the dashboard does the delta fetch from extraction layer to the cache layer using this report with 'Full Extraction' unchecked.
Earlier extraction report with report: /SALM/FILL_SRD_CACHE must stop, and new extraction job needs to schedule with the new report SALM/SRD_FILL_CACHE_ALP. No change about /SALM/DATA_EXTRACTION_PPMITSM is needed.
5. Status Group Customizing
The new customizing for status groups in Solution readiness dashboard is accessible from SPRO in the below path:
Status Group Customizing
The default status groups are delivered as part of a BC Set and this is also integrated as part of initial Solman set up of release SP12.
In the customizing, the Status Group and Process Type Mapping step displays the different status groups per transaction type. The sequence column helps in re-arranging the order of the status group on the dashboard. In the below example, I have considered requirements(S1BR). It has 3 status groups -To be scoped, in progress and realized with sequence 2, 3 and 1, respectively. Then when we see on the requirement card the same sequence is visible.
Sequence of the status groups -1
Now if we change the sequence to ‘To be scoped – 1', ‘Realized - 2’ ‘In progress –3', the requirement card reflects the new sequence after refreshing the browser.
Sequence of the status groups -2
Another interesting feature is that we can create new status groups (Only for work package and Work item) and we arrange the individual statuses in each group in the Define User Status Mapping section as shown below:
Statuses in each status group
Please feel free to provide feedback either directly here in the comment section or, in case of questions, you can submit them here. You are also encouraged to follow SAP Solution Manager tag here and Focused Build for SAP Solution Manager tag here.
Important Links and Resources
- Usage Rights
- SP12 delta presentation to get an overview of the changes and read the highlights blog
- Read how SAP Activate and Focused Build with SAP Solution Manager is working together
- ALM Community page
- SAP Managed Tags:
