EBP 4.0 - Modelled Deadines for N-Step Approvals WS14000133

[Dart, Jocelyn]

Hmmm...
Does it make business sense to put a deadline on an adhoc approver? You could also try a simple deadline using SWDD_CONFIG. Test it though - not sure if the SRM inbox handles deadline work items fully.
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Martinek, Jerry
Sent: Thursday,3 June 2004 1:11 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP 4.0 - Modelled Deadines for N-Step Approvals WS14000133
 
 
Hi Jocelyn,
 
Why wouldn't I need to copy the ad hoc subflow? It has an approval step that
I'd want to make sure is executed in the specified time period.
 
Thanks,
Jerry
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Tuesday, June 01, 2004 11:06 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP 4.0 - Modelled Deadines for N-Step Approvals WS14000133
 
 
Jerry,
Even if you copy the main workflows there is no reason to change the ad hoc
subflow. You can just use the standard workflow for ad hoc approvers in your
own workflow. Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Martinek, Jerry
Sent: Wednesday,2 June 2004 2:33 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP 4.0 - Modelled Deadines for N-Step Approvals WS14000133
 
 
 Hi Jocelyn,
 
I was referring to the export parameter EV_TASK_TO_INSERT of function module
BBP_WFL_DIN_APPR_BY_RULE_GET. It contains the name of the anchor task for
the shopping cart business object.
 
I'm not sure why they are initializing it with the name of the 'Approval
Fragment For Anchor' workflow (WS10000271). I'm assuming that it is there
for a reason so if I copy all of the required workflows for the N-Step
shopping cart approval workflow, I'll need to replace WS10000271 with my own
workflow. The required workflows are WS14000133, WS14000134 and WS10000271.
 
The 'Task' container value that you're referring to is used in some checks
within the function module that eventually point you to the BADI for
deriving approvers.
 
Thanks,
Jerry Martinek
 
 
-----Original Message-----
From: Dart, Jocelyn
To: SAP-WUG at MITVMA.MIT.EDU
Sent: 6/1/04 6:16 PM
Subject: Re: EBP 4.0 - Modelled Deadines for N-Step Approvals WS14000133
 
Hi Jerry,
Look for a container element called "TASK" in the subflow.  You'll see this
has an initial value that indicates the workflow id.  This is then passed to
the routine that gets the next approver.  If you want your own custom
workflow you just have to make sure you do the same in your workflow passing
the "official" workflow id in the TASK element. Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Martinek, Jerry
Sent: Wednesday,2 June 2004 8:46 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP 4.0 - Modelled Deadines for N-Step Approvals WS14000133
 
 
Hi,
 
Has anyone implemented modelled deadlines for the N-Step Approvals
WS14000133 workflow?
 
If you have, did you change the SAP workflows (WS14000134/WS10000271) or did
you copy the SAP workflows and then coremod function
BBP_WFL_DIN_APPR_BY_RULE_GET to insert the new name for the 'Approval
Fragment For Anchor' workflow or did you find a different way of doing it.
 
My understanding is that you shouldn't alter SAP workflows so if you have a
need for modelled deadlines, you copy and modify accordingly. The issue is
that the name of the 'Approval Fragment For Anchor' workflow is hardcoded in
the named function module.
 
Thanks,
Jerry Martinek