Ansicht
Dokumentation

/IAM/VC_STPRF - Define User Status Profiles

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

In this Customizing activity, you create status profiles in which you can specify conditions for when a user status or a delivered system status is set.

You have created the user status actions under Define User Status Actions.

1. Create a status profile.
2. Select the status profile and under Fields choose the status fields that you want this profile to include.
3. Under Actions, define under which conditions an action is to be executed. To do this, first choose which type of action you want to store a condition for.

• If you want to define a condition for the user status you defined, under Target Action Type choose the option User Status Action. In this case, the User Status Action field is ready for input so you can select your user status action.

• In some cases it is also necessary to define conditions for delivered BO actions. If, for example, you want to specify that an issue or a change request must not be completed, you must select the BO action COMPLETEPROCESS as the target action.

To define a condition, select the row with the action for which the condition must be fulfilled and choose Conditions. You can specify which statuses allow or prohibit the target action. Here, in addition to the user statuses you define yourself, you can also include delivered lifecycle statuses such as New or In Process. To do this, select the value Field LCYCLE_CD under Status Field.

Note: For BO actions, you can only set prohibitions.

1. When you have finished defining the status profile, you can start a Simulation using the pushbutton in the respective row on the Status Profile screen and check whether the status changes function as required.

Note: Note that only the user status is simulated automatically. You must manually select the lifecycle status that may be set with a user status. In addition, you must set the initial lifecycle status manually directly after the simulation is started. For example, for the application MOC, the initial change request status is 01 (In Preparation); for QIM it is the issue status 60 (New).

1. To use the status profile, you must assign it in Customizing to an issue type or activity type (in the application QIM) or to a change request type or activity type (in the application MOC).
2. To allow the user status actions to be executed on the user interface, you must include the respective pushbuttons or dropdown lists in your Web Dynpro application via Web Dynpro Customizing or configuration. To do this, you must enter the action using an FPM event parameter.

TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3209 Date: 20240423 Time: 190411     sap01-206 ( 64 ms )