I would like to show you, how external collected requirements can be uploaded into SAP Focused Build by using the requirements import function.
This function was designed to bring requirements from one system into another. How this use case works you can find in this blogpost: Requirement Import in Focused Build for SAP Solution Manager
But sometimes we face the situation, that especially in the beginning of projects, a lot of tasks need to run in parallel to meet the expected timelines. So it can happen that the system set up and the collection of the requirements need to run in parallel.
And therefore a opportunity to upload a bunch of requirements into the SAP Solution Manager Focused Build is needed. This can be realised by the requirements import function, but there are some guidelines to follow.
First of all the mandatory SAP Focused Build set up is done. A solution is created and the process documentation is also entered into solution documentation.
Let's assume the following scenario: We got provided by the customer with an excel sheet that contain their requirements. One per line with the following columns:
So first of all starting with the structure and input data.
In the Requirements Management App via the function "export to spreadsheet" an excel file can be downloaded even if there are no requirements. Within this excel you will receive the structure you need for the upload and don't worry - it is not necessary to fill every column!
Prerequisite for this step is an existing solution documentation with at least processes. Within the upload SAP Solution Manager is not able to map the requirement to the respective process just by the process name. Therefore the technical ID is needed.
Prerequisite for this step are existing users including corresponding business partner numbers in the SAP Solution Manger. All fields like owner or business process expert referencing in the backend to business partner numbers and not names. Therefore you need the business partner number for the upload for the fields like owner or business process expert.
The whole list of names and their business partner numbers can be downloaded from transaction BP.
With these 3 steps the structure and input data is set.
The final steps are bringing all together.
Title and description are normally easy to fill into the upload structure. It is important to check, if there tab stops or line breaks especially in the description text because they will cause failure when uploading. One line will be translated into one requirement in the system.
This column is filled out with numeric values from 1 to 4 to reflect the priority.
Based on the name in this column, I use excel formulas to map the corresponding business partner number in the column "Owner BP Number" based on the input data we dowloaded earlier.
The branch the requirements should be imported to, is the Design branch. The value to enter for all requirements is "Design".
In this column the name of your solution needs to be entered.
For this column I use also a formula that maps the process name given by the customer to the input data downloaded from the solution documentation. You need to find the downloaded solution documentation list the line item for the process the requirement is related to. From this line item the value of the column "OCC_ID" needs to be entered into the upload excel structure in the column "Element ID".
This will create the process reference of the requirement when uploading.
I look up the BP number based on the name in the downloaded business partner list and transferring the value to this column.
These are the same numeric values than in the column Priority.
These columns identify the classification. Based on the classification of your requirement you need to entered one of the following values to the columns.
Now your excel with the upload structure is filled with all mandatory informations and usually requested information from customer to upload the requirements.
As a procedure for the upload, I can recommend to upload roundabout 100 lines max in one upload because sometimes there are failures and then it is quite hard to find them even in 100 lines.
To summarise it up: Having already collected requirements before Focused Build is set up or collecting the requirements in parallel to the set up is not a problem. The upload function can be used to bring the requirements into Focused Build without entering them all in manually.
I would appreciate to hear from you thoughts and experiences about this topic in the comments and also please feel to consider subscribing to the Focused Build for SAP Solution Manager to ask or answer questions in our community.
This function was designed to bring requirements from one system into another. How this use case works you can find in this blogpost: Requirement Import in Focused Build for SAP Solution Manager
But sometimes we face the situation, that especially in the beginning of projects, a lot of tasks need to run in parallel to meet the expected timelines. So it can happen that the system set up and the collection of the requirements need to run in parallel.
And therefore a opportunity to upload a bunch of requirements into the SAP Solution Manager Focused Build is needed. This can be realised by the requirements import function, but there are some guidelines to follow.
First of all the mandatory SAP Focused Build set up is done. A solution is created and the process documentation is also entered into solution documentation.
Let's assume the following scenario: We got provided by the customer with an excel sheet that contain their requirements. One per line with the following columns:
- Titel
- Description
- Name of the owner
- Process Name
- Priority
- Classification (Fit, Gap, WRICEF, Non-Functional)
So first of all starting with the structure and input data.
1.) Downloading the excel with the requirements structure
In the Requirements Management App via the function "export to spreadsheet" an excel file can be downloaded even if there are no requirements. Within this excel you will receive the structure you need for the upload and don't worry - it is not necessary to fill every column!
2.) Download the solution documentation structure (optional)
Prerequisite for this step is an existing solution documentation with at least processes. Within the upload SAP Solution Manager is not able to map the requirement to the respective process just by the process name. Therefore the technical ID is needed.
- Open Solution Documentation
- Change to List view
- Ensure that the whole Solution is shown in the list and download the .txt file
- Open the .txt
- Copy the header into your excel file in a new spread
- Copy the data into the excel table
3.) Download Business Partner numbers
Prerequisite for this step are existing users including corresponding business partner numbers in the SAP Solution Manger. All fields like owner or business process expert referencing in the backend to business partner numbers and not names. Therefore you need the business partner number for the upload for the fields like owner or business process expert.
The whole list of names and their business partner numbers can be downloaded from transaction BP.
With these 3 steps the structure and input data is set.
The final steps are bringing all together.
4.) Fill in the column Title and column Description based on the customer provided data
Title and description are normally easy to fill into the upload structure. It is important to check, if there tab stops or line breaks especially in the description text because they will cause failure when uploading. One line will be translated into one requirement in the system.
5.) Fill the column Priority
This column is filled out with numeric values from 1 to 4 to reflect the priority.
6.) Fill the column Owner with the name
Based on the name in this column, I use excel formulas to map the corresponding business partner number in the column "Owner BP Number" based on the input data we dowloaded earlier.
7.) Fill the column Branch
The branch the requirements should be imported to, is the Design branch. The value to enter for all requirements is "Design".
8.) Fill the column Solution
In this column the name of your solution needs to be entered.
9.) Fill the column Element ID
For this column I use also a formula that maps the process name given by the customer to the input data downloaded from the solution documentation. You need to find the downloaded solution documentation list the line item for the process the requirement is related to. From this line item the value of the column "OCC_ID" needs to be entered into the upload excel structure in the column "Element ID".
This will create the process reference of the requirement when uploading.
10.) Fill column Owner BP Number
I look up the BP number based on the name in the downloaded business partner list and transferring the value to this column.
11.) Fill the column Priority ID
These are the same numeric values than in the column Priority.
12.) Fill the last three columns ClassifAttributes - Component name, ClassifAttributes - Classification and ClassifAttributes - Text
These columns identify the classification. Based on the classification of your requirement you need to entered one of the following values to the columns.
ClassifAttributes - Component name | ClassifAttributes - Classification | ClassifAttributes - Text |
/SALM/NON_FUNCTIONAL | N | Non-Functional |
/SALM/WRICEF | 1 | WRICEF |
/SALM/Gap | G | Gap |
/SALM/Fit | F | Fit |
Now your excel with the upload structure is filled with all mandatory informations and usually requested information from customer to upload the requirements.
As a procedure for the upload, I can recommend to upload roundabout 100 lines max in one upload because sometimes there are failures and then it is quite hard to find them even in 100 lines.
To summarise it up: Having already collected requirements before Focused Build is set up or collecting the requirements in parallel to the set up is not a problem. The upload function can be used to bring the requirements into Focused Build without entering them all in manually.
I would appreciate to hear from you thoughts and experiences about this topic in the comments and also please feel to consider subscribing to the Focused Build for SAP Solution Manager to ask or answer questions in our community.
- SAP Managed Tags:
2 Comments
