Hello everyone,
I have a question (or rather a complain) about CRM Actions. To be honest this might be more suitable for the general Netweaver forum (since the application component in question is BC-SRV-GBT-PPF), but I think I might get a better response here since PPF Actions are so widely used in CRM!
My problem stems from the way the system handles the Scheduling Conditions and Action Merging customization. I'll give a scenario:
- I want my Action to only ever execute 1 time successfully, on Save of the CRM document.
- Therefore, in customizing of the definition, I have Action Merging = Set Highest Number of Processed Actions, then in the Action Merging tab, I have 1 Unprocessed Action for Each Action Definition and Max. 1 Successful Action.
- I have also set the Action to be Scheduled Automatically, Processed On Save, Not changeable or executable in dialog and not in the toolbox.
- I then code a scheduling condition BADI implementation, create a condition record for the action, and specify the BADI implementation as the Scheduling Condition.
- There is no Start Condition assigned.
The above setup works fine, until after the first Successful execution of the Action.
Now, since I've setup the Action to be executed only 1 time, I would expect that after this has happened, nothing associated to this Action will be "carried out", including its Scheduling Condition. But that is not the case.
The system will always execute the code in the Scheduling Condition regardless of the Merge settings. Only after it has run the Scheduling Condition and found that the condition has been met, the it will check the total number of triggers already fired for the Action, then it will not execute the Action because it then realizes the Merge limit has been reached.
I find this highly inefficient because why would the system even execute the Scheduling Condition if the end-result is always going to be the same, ie. the merge limit has been reached, so it won't be executed?
I also tried setting Action Merging = Max. 1 Action for Each Action Definition, which should be the most definitive way of saying "I want only 1 Action trigger ever!", but the behaviour is the same. Merging is only considered after Action Determination (ie. Scheduling Conditions) has been evaluated!
Wondering if anyone else thinks the same?
Kind regards,
Justin.