EBP 3.5: Approval of Shopping cart: More approvers, different approver finding strategy

[Pyc, Mark]

G'day Christian,
 
Just finished doing something similar this morning also on 3.5.
 
A) Approver Determination occurs within the container element AGENT_001. The
Bus.obj on which this is based is a direct subtype of AAGENT which has a
method CREATE. If you want to use different agent determination you need to
create a direct subtype to AAGENT and redefine the CREATE method. I also
redefined the attributes NOTES and AGENTS because all the other subtypes did
it. ( Basically I subtyped AAGENT and copied the entire code behind
ASBMANOFSL and replaced my generated code before making extra changes)
 
B) "The workflow isn't started via the event being raised, however the event
linkage is considered - i.e. start conditions still have an impact". -
misquote of Practical Workflow for SAP; Dart et.al.
 
C) No idea.
 
Have fun,
Mark
 
-----Original Message-----
From: Christian Baessler [mailto:Christian.Baessler at gmx.net]
Sent: Wednesday, February 05, 2003 15:04
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP 3.5: Approval of Shopping cart: More approvers, different
approver finding strategy
 
 
Hi,
 
we are implementing EBP 3.5 and would like to change the approver strategy
and add more levels of approvers.
 
More or less: the G/L account and cost-center combination determines which
path should be used,
the amount determines the number of levels.
 
My questions:
 
a) where does the approver determination take place ? In the transaction ?
Does anybody know if there's a user exit or at which place in the code to
change the logic ? (in case the transcation is called)
 
b) How is the Workflow called, e.g. WS10000129 for one step approval. If I
switch on the event monitor, I never get an entry in there. It seems to me
that the event linkage is not used ???
 
c) The nice litte Java Applet for the approver-preview and history: what FM
does it call in the background ?
 
 
Thanks
Christian
 
 
"This transmission is strictly confidential and intended solely for the
addressee. It may contain information which is covered by legal,
professional or other privilege. If you are not the intended addressee, you
must not disclose, copy or take any action in reliance on this transmission.
If you have received this transmission in error, please notify us as soon as
possible."