Requirements Management Scenario: Transfer the IT Requirement to a Project

[mich_vollmer]

This blog describes a use case that was an essential topic during my discussions with the DSAG at a time when the Requirements Management process was built.

Transfer a Requirement to a Project

Consider the following case: A business requirement was created by the LoB. It was approved by the business manager and to be evaluated by the IT department.

During validation the solution architect analyzes and concludes that this is a very large requirement. For example, the requirement would include a new software release, which affects multiple systems in the customer's landscape. In short, it is a project.

IT analyzes the requirement and approves its execution. However, further on in the process, the requirement is too complex to be handled solely by filling out a list of scope items in the IT Requirement and creating a list of change documents. The team responsible decides to use ITPPM for project management. They define the tasks and create IT Requirements, Requests for Change, and change documents from the tasks. So now it would be convenient to have a status available that defines that the previous IT Requirement is handled by a project and closes the flow.

In the following section, let's take a look at how you can customize this functionality, which sets the IT Requirement to a Transferred to RfC status and creates a new IT Requirement. At the same time, this new IT Requirement is assigned to the Business Requirement as a follow-up document. I will also show you how to do the Customizing of setting a status Requirement Transferred to Project.

The screenshots always refer to a ZMIR created from a ZMBR.

There are several parts to be customized:

1. In the status profile, create the new status and authorization key for Transfer to Project.
2. Adopt the status of the Business Requirement
3. Create the PPF action and conditions to set the status.
4. Change Request Management Framework Customizing:
   1. Define status attributes
   2. Actions
   3. Consistency checks
   4. Predecessor status
5. ITPPM Integration (optional): Map task status to transaction status
6. Update roles

In the status profile, create the new status and authorization key for Transfer to Project.

First create an authorization key for the new status.

Then maintain the status Transferred to Project (here E0014).

Double-click the newly added status Transferred to Project and maintain the following transaction control.

Adapt the status of the Business Requirement.

Adapt the highest value of the status that is marked.

Create the PPF action and conditions to set the status

For a more detailed description of where to click, please join the SAP Community Network here.

Create the PPF action by copying it from another PPF action, which sets a user status, for example, <transaction type>_CLOSED.

The PPF action here is named ZMIR_TRANSFER_TO_PROJECT.

Apply the Customizing as displayed below:

The PPF action should have a PPF action container element USER_STATUS with the value E0014.

Add the schedule PPF condition for this action as follows:

Change Request Management Framework Customizing

There are some Customizing activities to be done in the Change Request Management Framework settings.

Define status attributes

Customize the new user status.

Actions

If you are using ITPPM integration, customize SET_STA_TASK as well.

Define that the actions are executed as late actions.

Consistency Checks

It checks that the task statuses of the predecessors are not locked before they are set.

Predecessor Status

The IT Requirement reaches the status Transferred to Project and sets the Business Requirement to status Completed.

It might be of advantage to you to introduce a new status on the Business Requirement reflecting the transfer to project.

Map Task Status to Transaction Status

This defines which task status should be set when the IT Requirement reaches the new status.

Update Roles

Be aware that the authorizations might not be complete. In any case, if you use changed standard roles,

you have to check what needs to be adapted. This can be solved by an authorization trace.

The solution architect / requirements manager requires the authorization to set the status Transferred to Project in

the IT Requirement.

This includes the following:

B_USERSTAT with BERSL = 'ZMIR_14', ACTVT = '01', OBTYP = ' ', 'COH', 'COI' and  STSMA = '<transaction type >HEAD'

The solution architect / requirements manager needs the authorization to set the status Completed or another specific status for reflecting the transfer to project.

This includes the following:

B_USERSTAT with BERSL = 'SMBR_10', ACTVT = '01', OBTYP = ' ', 'COH', 'COI' and  STSMA =

'<transaction type >HEAD'

What you get

In the IT Requirement, you are now able to select Transfer to Project when it has the status Submitted for Implementation.

After saving, the status is set to Transferred to Project and the Business Requirement has the status Completed.