SRM 4.0 Item-Based Approval Question
Dart, Jocelyn
jocelyn.dart at sap.com
Tue Nov 15 18:15:33 EST 2005
RE: Jocelyn - I haven't dealt a whole lot with Business Objects, but in
the past I've always done my programming at the attribute level. For
ad-hoc approval functionality to work, do I HAVE TO call my function
from the Create method?
Yes.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com <http://www.sap.com/>
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Seko, Ryan
Sent: Wednesday, 16 November 2005 6:57 AM
To: SAP Workflow Users' Group
Subject: RE: SRM 4.0 Item-Based Approval Question
Jocelyn & Koen,
Thanks for your advice (Koen - I've included your direct response to me
for the rest of the group to see, hope you don't mind).
Jocelyn - I haven't dealt a whole lot with Business Objects, but in the
past I've always done my programming at the attribute level. For ad-hoc
approval functionality to work, do I HAVE TO call my function from the
Create method?
Koen - Although we are currently using the org plan for parts of our
approvals, I'm planning to switch everything to a custom table because
it's getting too cumbersome to maintain the org plan. Depending on the
situation, sometimes we need to look up the approver based on the whole
cost center and other times, only the first 3 digits (greatly reducing
the number of approval entries). I've also looked into responsibilty
rules, but that also looked like a maintenance nightmare. A custom
table just seems like it would be the most efficient, but I'm always
open suggestions!
Ryan
________________________________________________________________________
___________________________
Hi Ryan,
1.The setup of who has to approve what in a shopping basket needs to be
done in the BADI. SAP recommends not to change the workflows, which is
also my recommendation. If you fill the tables correctly in the BADI it
is possible to send one item to different approvers.
2. In standard SRM there are attributes available in the organisational
model to fill the cost center so why use a custom table. The advantage
is that all maintenance is done in the organzational model and that you
directly see who is responsible for what. Getting the costcenter out of
a custom table or out of the org model is just some programming (
example
function: RH_OM_ATTRIBUTES_READ ).
3. For the ad-hoc approver, I did the following: setting the workflows
and task as general. And it worked.
Regards,
Koen Durnez
dk.Advice bvba
Belgium
+32(0)497.46.89
www.dkadvice.com <outbind://101/www.dkadvice.com>
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Thursday, November 10, 2005 3:25 PM
To: SAP Workflow Users' Group
Subject: RE: SRM 4.0 Item-Based Approval Question
Re assigning approvers at the split account assignment level - its not
intended for this and SAP AG don't guarantee it will work.
However I have played around with it and it did seem to be possible -
certainly the "everyone approves" scenario worked fine - but we were not
able to complete testing of this functionality and did not go live with
it.
You can copy and modify the item-based workflows - but you have to know
what you are doing. Go very gently.
You are absolutely required to use an ad hoc agent object based on
AAGENT *unless* you are using the BADI workflows - if you don't you will
lose some significant parts of the approval preview/approval tab
displays. You can call your function module or an object attribute
from the Create method of your ad hoc agent object.
Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T +61 412 390 267
M + 61 412 390 267
E jocelyn.dart at sap.com
http://www.sap.com <http://www.sap.com/>
The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents.
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated.
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Seko, Ryan
Sent: Friday, 11 November 2005 6:18 AM
To: SAP Workflow Users' Group
Subject: SRM 4.0 Item-Based Approval Question
Hi All,
My company will soon be upgrading from SRM 2.0 (EBP 3.5) to SRM 4.0 and
I'm planning to redesign our custom shopping cart approval process at
the same time. Our main approval is based on cost center with the
possibility of up to three more approvals after that. Currently, we use
dynamic parallel processing to send the entire shopping cart to all cost
center approvers (including items with multiple account assigments). It
looks like SAP's Item-Based Approval might work for us, but one concern
I have is if it can handle items with multiple account assignments.
Does anyone know if the Badi can be programmed to have a single item
sent to multiple approvers? From everything I've read, it appears
everything has to be done through the Badi since the item-based and
n-level workflows can't be copied then modified like past standard
workflows. Is that correct?
While I'm at it, I'll throw this one out too (in case I don't use the
item-based approval). I have a function to look up the cost center
approver(s) from a custom table. Is it more efficient to call this
function from a object attribute or from a rule within the workflow?
>From reading the "Practical Workflow" book it appears I would have to
add the attribute to a subtype of AAGENT to maintain ad-hoc approver
functionality. Would I lose that functionality if my function is called
from a workflow rule?
Thanks for your help,
Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051116/e58fe7e4/attachment.htm
More information about the SAP-WUG
mailing list