Multiline container deadline monitoring

[former_member663978]

If a document is having three-line items with three different cost centers and in the first step it will create the three different work items and send to three approvers. None of them have touched the document then all will reach the deadline, once it reaches the deadline we are obsoleting that work item. Then creating the new user decision step to send those work items to escalation users ideally that step has to trigger only once, but that step is creating how many work items reaches to deadline.

Any help on this is much appreciated.

Thank you,

Shushma

[keohanster]

I prefer to stay within the SAP Community lane, so here is some SCN docu about deadline monitoring...

https://wiki.scn.sap.com/wiki/display/ABAP/Deadline+Monitoring

Regards,

Sue

[p244500]

Hi ,

You can achieve this using dead line monitoring. kindly look at tutorial about dead line monitoring.

With deadline monitoring you can cancel the workflow you can escalate to next level as well.

[bpawanchand]

Hi Shushma,

Looks like the work items are created dynamically based on the multiline container element which you might have configured the dynamic parallel processing with a multi-line container element.

1. As soon as the latest end reached, I would basically just trigger emails and set a flag in the workflow container which helps me to identify that the deadline was reached. Following, I would validate this flag to just trigger the work item to the escalated user. Since you do not have a situation where you need to loop the missed deadline user again.
2. Otherwise, check the logic which is trying to trigger again all the work items.
3. One more option would be to make use of the end condition. Please find below, where it clearly explains that if any one of the parallel work items is executed then this end condition is evaluated, so you define a flag in the workflow container and validate if this flag is set which automatically end the other work items.

If you can provide more info about the design of the workflow then it gives more clarity on what can be done to solve the issue.

Regards

Pavan