Show TOC

Function documentationUser Status

 

You can add your own customer-specific user status to the applications for creating and processing issues and activities, which can be set in addition to the delivered lifecycle statuses. You can thus extend control of the processing sequence defined by the delivered lifecycle statuses by including your own user statuses.

Example Example

You can query board approval when processing an activity. The activity can be completed only if the user status Approved by Board is set.

End of the example.

The user status is set by the execution of a user status action. This can be, for example, a user selecting a respective entry in a selection list.

When you define user status actions, you can store conditions that must be fulfilled before a user status or also a lifecycle status can be set.

For reporting purposes, you can also show the user status in the worklist.

Features

You have various options for defining a user status.

  • The recommended option is the use of the up to five delivered user status fields that are assigned to the business objects /IAM/ISSUE and /IAM/ACTIVITY. You specify the meaning of these status fields in Customizing for QIM under Start of the navigation path Environment Next navigation step User Statuses End of the navigation path. There, you define the individual user statuses, the actions for setting the statuses, and status profiles that you can assign to an issue type or activity type. For more information about the procedure, see the documentation for the relevant Customizing activities.

  • You can implement a user status using Web Dynpro configuration and by changes in the Business Object Processing Framework (BOPF). For more information about this procedure, see Defining User Statuses Using Configuration and BOPF.

Recommendation Recommendation

We recommend that you define the user statuses in Customizing because this does not require programming effort. In addition, no customer-specific Web Dynpro configuration is necessary because the delivered status fields are already included in the delivered Web Dynpro configurations. Selection lists for the status fields are displayed as soon as a status profile is assigned to the respective issue type or activity type. Also, in the standard system, the first delivered user status field is available in the worklist as a selection criterion. You can include the other delivered fields in the worklist yourself (see SAP Note 1865206Information published on SAP site).

End of the recommendation.

Activities

To define user status fields in Customizing, proceed as follows:

  1. In Customizing for QIM under Start of the navigation path Environment Next navigation step User Statuses End of the navigation path, you define the user statuses and the user status actions, and store the conditions for executing the user status actions in a status profile.

  2. In Customizing for QIM, you assign the status profile to an issue type or an activity type.

Result

When you create an issue or an activity with the respective issue or activity type, a selection list is available automatically that is named after the user status field text and includes the assigned and possible user status actions.

Note Note

To trigger a workflow following a status change, use the workflow event ID USERSTATUSCHANGE in the event linkage. For more information about workflow in SAP QIM, see Customizing under Start of the navigation path Environment Next navigation step Activate Workflow End of the navigation path.

End of the note.