SRM BAdi-n step for Shopping Carts

[Susan R. Keohan]

Hi Natasha,

Thanks so much for all the info.   Our current process does not call for ad-hoc approvers, but I am 
still hoping to take advantage of this functionality.

Am I correct that the value in BBP_WFL_SECURITY (currently set to 'not defined') would be the key to 
allowing/prohibiting changes to Shopping Carts, all using the same task ?  Just re-stating in my own 
words what I thought you said...

Have you used Events to cause the recalculation of agents for active tasks ? This could solve a lot 
of our problems, where the Shopping Cart changes during the approval process, and the wrong 
approvers still have the 'old' approval task...(Ginger Gatling delivered a great presentation on 
this topic at the recent TechEd in Boston).

Many thanks,
Sue

Baunach, Natasha R wrote:

> Hi Sue,
> 
> I have implemented BBP_WFL_APPROV_BADI in our SRM 4.0 sandbox with
> different level of approvals and certain line items going to different
> approvers.  Hopefully, I can answer some of your questions.
> 
> 1. Yes, approval index must be incremented by 1.  You can still have
> your ad-hoc approval steps between pre-defined approval steps assuming
> that you allow for ad-hoc approvers (you can disable this functionality
> via BADI 'Allow Changes to Approvers' BBP_CHNG_AGNT_ALLOW.
> 
> 2. It is the same task that is used for approvals in all shopping cart
> approval workflows available in SRM 4.0.  The task is TS10008126.
> Whether or not an approver can change the cart during approval process
> is determined by the settings at the role level.  Go to transaction
> PFCG, input your role, hit display.  Then go to Personalization tab and
> look for personalization object key 'BBP_WFL_SECURITY'.  During runtime,
> this default can be overwritten in the BADI 'Authorization to Change
> During Approval' BBP_WFL_SECUR_BADI.  So basically, if your approvers at
> different levels have different roles, you should be able to control
> change ability via this setting at the role level.  If it is more
> complicated than that, then you will need to place your more complicated
> logic in the BADI.  
> 
> BTW, I think that you can also use a different BADI to allow only
> certain fields to be changed.  It could be applicable only to CUF's.  I
> have this requirement and will be looking into it shortly -- if a user
> has finance approver profile, only allow them to change GL account
> assignment and nothing else; no changes are allowed for other approver.
> 
> I hope this helps.  
> 
> Natasha
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
> Of Susan R. Keohan
> Sent: Tuesday, November 01, 2005 6:56 AM
> To: SAP Workflow Users' Group
> Subject: SRM BAdi-n step for Shopping Carts
> 
> Hi all,
> 
> I am trying to embark on the implementation of BBP_WFL_APPROV_BADI (SRM
> 4.0).  Have looked at all 
> the notes, docu, sample implementations, etc.
> 1) The docu for this BAdi says 'Note that there must be absolutely no
> gaps in the approval steps and 
> that approvers must be defined for every step.'  I assume this means
> that the ApprovalIndex must be 
> incremented from 0 by 1 with no gaps in it.  Am I correct ?  Or does
> this mean that there can be no 
> intervening steps *between* approval steps ?
> 
> 2) Is it possible to pass an approver an approval task, which also
> allows them to change the cart ? 
>    But other approvers (different approval levels) can only approve or
> reject?  Can I determine 
> which tasks the approvers can get and set that in the BAdi ?
> 
> Obviously, I am an SRM novice and a BAdi novice as well, so any help is
> greatly appreciated.
> Happy WF-ing,
> Sue

-- 
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