EBP 4.0 - n-step Approval WF and the Shopping Cart Approval Prev iew Function

[Dart, Jocelyn]

Jerry, If you search around in the workflow container for which elements are preset to hold the BADI workflow id you should find the missing field pretty quickly.
 
I know at one other site we ended up writing a small program to delete the unwanted deadline notification - rather than attempt to decipher everything that's happening in the SRM workflow programs as it's a little complicated to say the least.
 
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Martinek, Jerry
Sent: Tuesday,13 July 2004 1:11 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP 4.0 - n-step Approval WF and the Shopping Cart Approval Prev iew Function
 
 
Hi Jocelyn,
 
That may explain why the custom workflow isn't behaving as expected.
 
With regards to the deadline monitoring issue, I did report this to OSS and
their response was that the system may be working as designed.
 
Regards,
Jerry Martinek
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Sunday, July 11, 2004 5:06 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP 4.0 - n-step Approval WF and the Shopping Cart Approval
Prev iew Function
 
Hi Jerry,
EBP workflows follow very specific patterns - the BADI workflows even more
so.
If you wish to create a custom copy of the BADI workflow, you should also
place an OSS message
to confirm what you are missing.  There are places where you need to specify
the standard workflow
id in order to correct the applet display - i.e. so the EBP routines know to
treat your
workflow as a BADI workflow.
 
The particular requirements and handling of the BADI workflow also make
deadline monitoring
problematic.  Again this is a question to discuss with the developers via
OSS (Service.sap.com)
rather than via this forum.
Regards,
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Martinek, Jerry
Sent: Saturday,10 July 2004 10:45 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP 4.0 - n-step Approval WF and the Shopping Cart Approval Prev
iew Function
 
 
Hi,
 
 
 
I've created a new custom version of WS14000133 where I've taken the
original WS14000133 and included all of the relevant steps in WS14000134. I
basically replaced the subworkflow with the individual steps. I've had to do
this to trouble shoot some deadline notification problems with the original
WS14000133 workflow.
 
 
 
Having done this I've now run into a new problem in the Shopping Carts
Approval Preview functionality. When I create a new shopping cart and drill
into the Approval Preview, I see three entries in the preview window. The
names assigned to these entries are the individual task step names from the
new workflow. The first is the 'Determine next Approver', the second is 'To
Be Approved By' and the third is 'Determine next Approver'.
 
 
 
There is nothing wrong with the BADI to derive the approver as it's used by
the functioning SAP WS14000133/WS14000134 workflows.
 
 
 
Does anyone have any experience in this area to sched some light as to why
this would be happening?
 
 
 
The deadline notification problem was when I activated deadline monitoring
in TS10008126 which is part of WS14000134, the system generated two deadline
workitems, one for TS10008126 and one for WS14000134. The expectation is
that the system should only generate a deadline workitem for TS10008126 and
not both.
 
 
 
Regards,
 
Jerry Martinek