SRM BBP_WFL_SECURITY Level Value and System Action

[Griffiths, Mark]

Hi Jerry,

For the BADI workflow to get the sort of behaviour you are describing
you need security setting LOW - this will raise the 'change and notify'
event, cancel the approval subflow and then inform the shopper via the
subflow WS10400051.  The approval process will subsequently restart.

The MEDIUM setting does not work very effectively with the BADI workflow
as it only re-triggers the workflow if your start conditions evaluate a
new workflow process (applicable to the 0, 1, 2 step workflows not a
dynamic workflow like the BADI process).

Regards,


Mark



-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of martinek
Sent: Saturday, July 07, 2007 6:26 PM
To: SAP Workflow Users' Group
Subject: Re: SRM BBP_WFL_SECURITY Level Value and System Action

Hi Susan,

Thanks for the reply and suggestions. 

At this point I'm not sure whether I've selected the correct approach to
implementing my requirement.

My requirement is to send the cart back to the shopper when certain
types of changes are made during approval or continue with the next
approval process when an allowed change is made during approval process.


The allowed changes scenario seems to work when the level is set to 4.
I'm not able to get the system to send the cart back to the shopper when
the disallowed changes are made during approval. 

Do I need to include all of the allowed fields in the start conditions?
What else is required to get the cart to go back to the shopper?

Thanks,
Jerry

----- Original Message -----
From: Susan Keohan <keohan at ll.mit.edu>
Date: Saturday, July 7, 2007 6:57 am
Subject: Re: SRM BBP_WFL_SECURITY Level Value and System Action

> Hi Jerry,
> 
> We did not implement the BADI workflows, so I don't know how much 
> help I 
> can be, however, we did implement the WFL_SECUR_BADI and we use it 
> to 
> control whether a user can change a Cart or not.  The only levels 
> we use 
>  are 1 (none) and 4 (no restart of wf, all changes allowed).  All 
> of 
> this BADI and WFL_SECUR stuff is down deep in the guts of the 
> dialog 
> transactions, so try looking in the code, particularly in Function 
> GroupBBP_PDH_WFL.
> 
> Sorry I am not much help on your specific question, but I've felt 
> your pain!
> Cheers,
> Sue
> 
> martinek wrote:
> > Hi,
> > 
> > Can someone please explain the meaning or expected system action 
> when  BBP_WFL_SECURITY = 2 in the shopping cart WS14000133 
> approval scenario in SRM 5.0.
> > 
> > I&#65533;ve activated BADI BBP_WFL_SECUR_BADI method
Set_Security_Level 
> and implemented our own business rules for overriding the default 
> approval levels but I&#65533;m not getting the desired results.
> > 
> > When the value is set to 2, does the system restart the approval 
> process by restarting the approval steps without sending it back 
> to the shopper or does it first send it back to the shopper for 
> approval? If it doesn&#65533;t send it back, how can you get the
system 
> to stop the current workflow and send it back to the shopper in 
> order to first review and then restart? Can it be done via this BADI?
> > 
> > Regards,
> > Jerry Martinek
> > 
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> -- 
> Susan R. Keohan
> SAP Workflow Developer
> MIT Lincoln Laboratory
> 244 Wood Street
> LI-200
> Lexington, MA. 02420
> 781-981-3561
> keohan at ll.mit.edu
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug