EBP 4.0 workflow / org structure

[Stewart, Jim]

Jocelyn, I can't thank you enough for your input!~
 
Alas, (and of course) the client has a very "matrix-like" organization and
needs to determine approvals based on WBS element and evaluation path in an
org structure... and they want the ability to add agents in an ad-hoc
manner.
 
Lots of fun. Thanks again for your good words.
 
Best, Jim
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Dart, Jocelyn
Sent: Wednesday, December 03, 2003 11:35 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP 4.0 workflow / org structure
 
 
Hi Jim,
In short, you are free to work it out the agent using whatever mechanism you
want in the n-step BADI.
 
There are a couple of things to be aware of:
 
1. How you find the users is up to you - completely! E.g you could set up
responsibility rules for your asset/wbs scenarios and call that, or call an
existing rule in the backend system or use an org plan evaluation path or
whatever.
 
2. You need to return a userid in agent format i.e. US followed by the user
id as the agent.
You can return multiple users if you wish.  That means if you want complex
positions that's fine but you still need to return the holders of the
positions, e.g. use function module RH_GET_STRUCTURE with eval path SAP_TAGT
to find the holders of the positions.
 
3. The approval is sequential - i.e. you specify how many steps you want and
which agents are assigned to which steps.
 
4. The BADI example has been simplified to an extreme degree - it really
just shows you the format of the data you need to send out.
 
5. Be aware that the "add approver" function is not supported with n-step
approval (too complex to have both dynamic approval and adhoc approvers in
the approval applet).
 
And of course as in all SRM workflows, the document is sent for approval as
a WHOLE - it is not split into individual items.  So if you are sending
shopping carts for approval based on account assignments, either make sure
it goes to all approvers necessary in turn; or use the BBP_DOC_CHECK_BADI to
implement business rules around what account assignments can be mixed in the
same shopping cart.
 
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Stewart, Jim
Sent: Thursday,4 December 2003 6:26 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP 4.0 workflow / org structure
 
 
Client desires to use n-step dynamic approval workflow for shopping carts
within EBP 4.0 (support pack 2).
 
Question is -- Are there any known issues with "complex" position and
organizational assignments within the org structure, that is, does EBP limit
you to a very strict subset of the Workflow functionality from an
organizational perspective?  (see example)
 
>From what I've seen -- workflow looks to be the same as WebAS6.20 -- but
does EBP support this rich set of features?
 
Example:
 
A user Mary is assigned multiple positions within an organization. Mary is
an asset manager in division 111, and a project controller at the group
level, in group 222.  She will need to receive approval work items depending
upon WBS element which will indicate the organization approvals need to come
from (hence n-step dynamic approval workflow).
 
I hope this is enough information !! :^)
 
Thanks and regards, Jim Stewart
 
________________________________________________
Jim Stewart
SAP EBP Workflow Consultant
o: 858.826.3619
m: 562.212.4312
mailto:frank.j.stewart at saic.com
mailto:jstewart at equitytechgroup.com