on 12-28-2012 12:46 AM
Hi Experts,
We have a requirement of Shopping cart spending limit approval but without maintaining the SLAPPROVER attribute.
Approvers should be determined from organization
structure based on the spend limit in the same way as standard does but
SLAPPROVER attribute is not going to be maintained for the requisitioner or to
any manager. From the determined approvers, Manager with lower Approval limit
should be identified as the Approver.
Is the spending limit approval is possible without maintaining the SLAPPROVER attribute?
If yes, then how?
Thanks,
Sangeeta
Hi,
Although what i would be saying is similar to SLAPPROVER, the other way is to maintain the spend and approval limit is in SU01 of the user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sangeeta,
If you want to use the standard WFL(AC) or Badis(PC) for spending limit, then the usage of SLAPPROVER is a must.
But you can always create a own table and at Badi determine the approver based on your own criteria's.
Cheers,
Melina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.