Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
mich_vollmer
Contributor

Most customers adapt the ChaRM standard process by renaming the user status after the transaction type is copied to the customer namespace.

There are some steps to be done and things to checked if you want to do that.

The target of this blog is to describe the complete steps involved if you want to insert a new user status. Here you see an example of an existing user status profile with 3 user status where a fourth one is entered. As the user status is set by customized PPF action in ChaRM, some of these PPF actions have to be adapted as well. The overview below shows the change and the affected things to be done. Be aware that here, no backward user status setting is shown. The PPF actions which set the user status back have to be adopted as well. As this is a first version (I have limited time, I would like to share this with you and enhance it later). Be aware that the screenshots do not show this example but just the places where to change or look.

1. Insert the user status in the user status profile itself:

  • Go to transaction SPRO, path SAP Solution Manager->Capabilities(Optional)->Standard Configuration->Transaction Types->StatusAdministration and execute IMG activity 'Define Status Profile for User Status'.
  • select your user status profile (let's say we have 3 user status stat1 (initial status), stat2(process status) and stat3 (final status)
  • you want to enter a new process status before stat2
  • mark the user status which is most similiar to the one you (here stat2) want to create and copy it.

    • enter a status number between stat1 and stat2
    • adapt the description
    • give a status (key)
    • adapt the highest / lowest values (from which user status this status should be reached and which user status should be reached by this status)
    • change the authority code (for setting this user status) -> for that you might have to create one (SPRO ->

2. Adapt the PPF action (PPF action 1) reaching stat4.

    • The description might have to be adapted as it now sets another user status.
    • But technically more important is that the PPF container element is changed to new user status E0004. (to check which E status the new user status has, you can check table TJ30 with your user status profile).
    • Go to IMG, path 'SAP Solution Manager->Capabilities(Optional)->Change Management->Standard Configuration->Transaction Types->Action Profile' and execute activity 'Define Action Profiles and Actions'.
    • Select the Action profile and the relevant action. The change has to be done in area 'Processing Type'.

3. Create the PPF action (PPF action 4) reaching stat2.

  • Copy another PPF action (and subitems) which has the HF_SET_STATUS implementation, meaning which sets a user status. Be aware that all PPF description texts (all languages) are copied with it and have to be adapted.
  • rename the description text and change the container element of the new PPF action like displayed in 2.)
  • Special case 1: Defining the general action setting. In general a HF_SET_STATUS implementation is running when triggered in the UI by the user. It is although possible to let the PPF action run automatically. For the two cases see the two screenshots below:
    • PPF action settings for execution in Dialog

    • PPF action settings for automatic background run

4. Adapt the highest values for stat1 (E0001). It might be, you would like to adapt the values and change the highest value to the status number of the new stat4, so only this one can be reached and not stat2 as before.

5. Adapt the lowest values for stat2 (E0002). It might be, you want to change the lowest value of stat2 E0002 to the user number of stat4, so the user status can go from stat2 only to stat4 and not stat1.

6. Create the PPF condition. A PPF action is only visible or is executed in background if it has a PPF condition (and at runtime the scheduling and start condition are true). So we have to create a PPF condition for the PPF action 4 created which sets stat4. To that go to IMG activity 'Define Conditions' one under the IMG activity to create PPF actions.

You will see a list of descriptions of PPF actions, switch to the technical view, otherwise you get lost :-). Double-click on your PPF action profile, then you see the list of maintained PPF conditions for the PPF actions. You have to create a new one for the PPF action 4, see the screenshot with the 'Create...' button. You see a list of all available PPF actions of the for which you can create PPF conditions. Choose the PPF action 4 and it is available in the list now. Double-click and you can check the tabs 'Schedule Condition' and 'Start Condition'. Because we have copied the PPF action, there might already a start and/or schedule condition assigned.

Be aware if you change anything in these assigned schedule/start condition, the rule is changed for all other PPF conditions where this condition rule is assigned too. That can create a mess, so careful here now.

So we choose first to delete the assignment of the schedule/start condition. Then we create a new one by giving a new name and then define the rule in the rule editor. The rule editor is a complex part, I will maybe write another block there or enhance this one. In the rule

Via a Rule editor you can assign or create a new condition. You can logical rules by clicking yourself your expression and en´tering the value conditions. Check the screenshots for further infos. Just an introduction, otherwise it's too much for explanation here.

You should have something like that for your user status stat4 and your user status profile:

Then save it. You can have as well no scheduling and no starting condition assigned, then the PPF condition is valid everytime.

Then it should work.

If you have feedback, don't hesitate to contact me.

18 Comments