on 09-16-2009 12:19 PM
Hi there,
I have a scenario where if I create a shopping cart above my spending limit it will go into the approver's inbox, that is fine.
Now if I change the total value of the shopping cart to be within my spending limit the original workflow should be "logically deleted" and a "no step approval workflow" should be triggered.
I see when the SC workflow triggers it also branches with a "wait for events", so that if it changes etc it will get caught here.
When I change the SC it does not do anything, the value of the cart changes but it still sits in the approvers inbox and the "no step approval workflow" does not trigger.
We are busy upgrading to SRM 5.0, it worked perfectly in the SRM 3.0 system we had.
Any ideas what would cause the "change event" not to fire?
Thanks for the help
Lynton
Hi Lynton,
First make sure that the event gets triggered at all (use the event log SWELS)
Tthen check if the correct workflow is triggered
And then check the workflow log to see if nothing else is causing this.
If this doesn't yield anything go search OSS for messages with a similar problem.
Kind regards, Rob Dielemans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check the personalization value for BBP_WFL_SECURITY.
http://help.sap.com/saphelp_srm50/helpdata/en/37/830b3b7e7ef74de10000000a114084/frameset.htm
Regards,
Masa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Masa,
You are the man!! That solved it.....I have implemented the BBP_WFL_SECUR_BADI and for whatever reason I set the security level to 4 when it should have been 2.
4 "High" (workflow is never restarted when changes are made)
3 "Medium" (WF restarted conditionally when changes are made)
2 "Low" (workflow is always restarted when changes are made)
1 "None" (changes to the object are not allowed)
0 "Not defined"
Thanks for the help
Lynton
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.