SRM 7 Process Controlled WF - beyond simple Complete and Approve requirements

[Ramki Maley]

Hello Mark,

You can always make a copy of the standard workflow and modify! If that 
is not an option...

- Worktiem longtext to include detail about the current 'approval area', 
e.g. being able to include the total value of items in specific approval 
step.*- You can always redefine the text and long description of any 
standard task and in your case, include any information that is 
available through BUS2121 or its sub-type. *

- Escalation on deadline to adjust approvers to include next level 
up.***-**In order to add agents to a step, you will need to re-execute 
the rules for the workitem (there is a WAPI for that!). Your agent BAdI 
should therefore needs to determine if deadline has occurred or not. A 
you know, deadline escalation notification in SRM PCWF is done through 
the alert framework. Please check if you can trigger the redo rule WAPI 
through an alert BAdI. Agents can also be added using the standard 
methods behind the add approver functionality.
*
  - Post approval steps such as a simple 1 choice decision to confirm & 
log that off-system actions have occured.*- Are you talking about 
off-line approval from the email notification? You may need to look for 
enhancements in the off-line approval program and implement a custom 
workflow/task. Since this is an off-system action, the new step cannot 
be immediate anyway.*

  - Parallel workitem that exists for the duration of the approval 
process that allows possible rejection of the cart (specific requirement 
where approval is not required, but rejection is possible). This could 
maybe be a POWL type report that allowed process influence.*- Yes, POWL 
report is an option. You can also to implement a custom workflow for this...
*

Cheers,
Ramki.


On 3/31/14, 2:52 AM, Mark Pyc wrote:
> G'day Wuggers,
> I have previously configured SRM 7 PCW for a client who was willing to 
> conform to the what the solution offered. Once you get your head 
> around the BRF construct and the various BAdI's it's really quite 
> simple to flexibly design a multilevel approval with whatever logic 
> you want for agent determination. Lovely!
> As soon as I wanted to add any other functionality, I found the level 
> of configuration available very limiting. I now have a client who has 
> predefined requirements that haven't considered the default offering. 
> I'm curious if anyone has successfully delivered any functionality 
> beyond the clearly documented capabilities. For example:
>  - Worktiem longtext to include detail about the current 'approval 
> area', e.g. being able to include the total value of items in specific 
> approval step.
>  - Escalation on deadline to adjust approvers to include next level up.
>  - Post approval steps such as a simple 1 choice decision to confirm & 
> log that off-system actions have occured.
>  - Parallel workitem that exists for the duration of the approval 
> process that allows possible rejection of the cart (specific 
> requirement where approval is not required, but rejection is 
> possible). This could maybe be a POWL type report that allowed process 
> influence.
> These are just examples, I'd love to hear of solutions for these or 
> any other 'funny' requirement beyond the basic sequential process the 
> solution is designed to deliver.
> Many thanks,
> Mark
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140331/b5f3f20c/attachment.htm