An IT requirement has been created directly or on the basis of a business requirement, and now has to be evaluated by the solution architect or IT requirements manager. The solution architect or IT requirements manager takes into account the capacity of the development team, as well as the cost and feasibility of implementing the requirement.
They also might decide at what point in their IT requirements process they want to assign a change cycle provided they want to assign one at all. For instance, no change cycle is required in case they work with Requirements Management without Change Request Management for the purpose of tracking their requirements. This feature gives them great flexibility in designing their IT requirements process.
An IT requirement has been created and set to Submitted for Validation
.
You have the business role SOLMANPRO
(also see Authorizations).
SAP Solution Manager 7.2 support package 1 and 2: If wished for, you have enabled the flexible management of change cycles in the IT requirement by calling transaction SOLMAN_SETUP
(SAP Solution Manager Configuration). Choose the Requirements Management
scenario and go to Step 10.2 Assign Flexible Change Cycle
.
In the Requirements Management
view, open the IT requirements that have been assigned to you.
Switch to edit mode and change the status of the IT requirement to Being Checked
by choosing .
In the Details
assignment block, specify the change cycle in which the requirement is to be implemented.
In the Solution Documentation
assignment block, add further elements to the IT requirement to specify its relevance.
In the Checklist
assignment block, enter the relevant checklist and assign each task to the business partner who is to carry it out.
Enter any additional data that may be relevant for the IT requirement such as attachments.
Save your entries.
After the checklist has been completed, choose
to submit the requirement to the IT requirements manager for checking.The IT manager chooses Actions
the task bar and decides how to proceed:
User Action | Description |
---|---|
| The status of the IT requirement is reset to |
| The IT requirement is postponed until a date in the future. |
| The IT requirement is approved but must still be committed by both the business department and the IT department. |
| The IT requirement is rejected and the associated business requirement is set to |
| The |
Note
The requirement must still be committed by both the IT department and the business department before it can be implemented.