WS14000133 Deadline Monitoring / Escalation

Hi all,
The requirement is to set up deadline monitoring for WS14000133 (n-step Workflow with BADI) as follows: if the approval is not actioned within x days, escalate the work item to another approver (at a
higher level).
My questions:
1. Is adding the deadline monitoring per above to WS14000133 considered a system modification? If yes, is there a potential upgrade/patch impact?
2. Has anyone tried copying WS14000133 into a custom workflow? If yes, does SRM still call BBP_WFL_APPROV_BADI from the custom copy, and is SRM behaving properly overall?
3. Has anyone tried writing a custom ABAP report to monitor late work items, instead of using embedded Workflow deadline monitoring feature?
4. What has worked for you when implementing deadline monitoring for BADI Workflows in SRM?
Cheers,
Serguei

Hi
I did not work on this deadline monitoring but you can achieve it in wf14000133 .
about deadline monitoring(in workflow)
In workflow builder STEP TYPE as
then click ACTIVITY and select the appropriate step ( 000109) and go to Latest end REFER DATE TIME WORKITEM CREATION. 24 HOURS and etc.
and you can monitor via SWI2_DEAD
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/303617cf-73dd-2a10-c993-cc6303585176.
regards
Muthu

Similar Messages

Deadline monitoring/Escalation - Purchase Requisition Workflow WS20000077

Dear Friends,
I have read some stuff on SDN but still couldnt figure out the soultion.
Its a common problem. We have set a release strategy in Purchase Requisition and are using std workflow WS20000077.
Now the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release.
I have set the deadline monitoring using the workflow wizard for model deadline monitoring. With this, The work item gets deleted from the approvers inbox. Next in the obsolete path I have set a process control which specifies the worklow step as the step in which deadline monitoring was specified.
When I check in SWI1, the work item is set as obsolete but it doesnt go to the next approver for approval.
Your replies will be highly apprecialted.
Thanks & Regards,
Fawaz

Hi
For your Requirment :
"the requirement is that if an approver doesnt approve in 2 days time then the PR will automatically go to the next approver for release."
Please follow the below steps.in copy of WS20000077.
1.For taskTS20000159:Overall release of requisition , go to
Latest END tab: put ACtion as :Modeled , Refer.date/time:Workitem creation , below time : choses: DAY, and on left add 2.
Outcome :Deadline Montoring.
2.Then come to OUTcomes tab of the same task: see there are 3 lines 1.Step executed, 2.Latest end:Deadline Montoring, 3.Processing obsolete:Processing obsolete ,, all are ACTIVE or not , if not, Activate .then all should be Green.
4.next in the OUtcome :Deadline Montoring , use a process control step. to Set missed workitem to obsolete, in Function: chose : set Work item to Obsolute. and Workflow Step : chose then step no for the above task(TS20000159:Overall release of requisition).
5.In "Processing obsolete" path, again call the same task TS20000159. in different activity . and see to the agent assignment.
I think this will slove your problem.
How it works:
1st the PR is send in a WI to the perticular agent by the 1st activity . if the agent do not execute for 2 days. then that WI will set to obsolute . and process flow to" Processing obsolete" path, then agian PR is send to the next agent using the same task but activity created in step 5.
thanks
Kakoli.

Multiple levels escalation for deadline monitoring

Hi all,
We have a business requirement to perform multiple levels escalation in one of the workflow steps. If the approver does not approve the work item(WI) after one day, a mail notification will be sent to the approver. A second mail will be sent again if approver still doesn't approve WI after 48 hours. Then the third/fourth mail will be sent to approver and approver's boss if approver still doesn't approve WI after 72 / 96 hours. The fifth mail will be sent to approver's boss's boss if WI is not approved still after 5 days.
I know how to do simple and modeled deadline monitoring in workflow builder. But I don't know whether our business requirement can be achieved in workflow builder( and this is a step in dynamic parallel processing). Other option I have is to create an ABAP report to go through the table stores workflow run time data and make this report run several times a day in the batch to send mail notification reminder.
Did anybody have a similar business requirement like ours? What's the best way to handle it - build it in workflow builder or write an ABAP report?
Thank you in advance,
Merta

Hi Merta,
We had a similar requirement and this is how I achieved it:
1. Pleace your approval task into a loop (while not approved) and create a container element as the approval flag. This allows you to get out of the loop when the item has been correctly actioned. Also create a DL element to hold your calculated deadline value;
2. Create a method and task to determine the next escalation point based on how many loop passes the instance has had, ie:
Pass 1 - DL = sy-datum + 1 day;
Pass 2 - DL = DL1 + 1 day, and so on.
3. Create a method to determine who should get what. Link this to a condition so you know whether to send a mail or escalate the entire workitem. Create the notification as a send mail within the condition;
4. Change the Deadline parameters in your step to "Refer.date/tim" = Expression and bind the DL element;
5. Set the processing obsolete property to ensure the workitem is killed when a new pass (and therefore and new deadline/agent etc) is started.
See the following:
This one handles the loop/obsolete concept.
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4b97e453d11d189430000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/bc/ecdd5ad24e11d2b494006094b9ea0d/frameset.htm
Regards
Gareth

Select the approval Agent for Modeled Deadline Monitoring for WF WS14000133

I have setup a deadline monitoring for WF WS14000133 using the modeled approach and added the "Send Mail" Test along with a Loop so that the the appover will get an email every day after three days of not approving a shopping cart.
I noticed in task "109 Subworkflow n-step over Value" there is a task container element "&APPROVALAGENTS.ACT_AGENT&" which contains the approver. I am tring to put it in a Workflow container element that I created referencing "WFSYST-AGENT". When I try to setup a binding to import the value from the task container to the workflow container I get the following error:
"Data object 'APPROVALAGENTS' is elementary )component 'ACT_AGENT' does not exist)
Does anyone know how to fix this or does anyone know another way I can get the approval agent to the WF container so that I can send the email to them in the "send email" step?
According to SAP this can be done....this is what they say on help.sap.com:
"Actual agent: Element WIActual_Agent in the task container
If you want to transfer the actual agent of a work item (available under the element ID WIActual_Agent in the task container) to the workflow container for further use, you define an appropriate element in the workflow container to contain this information.
You create this element with a reference to the ABAP Dictionary field WFSYST-AGENT."
http://help.sap.com/saphelp_nw2004s/helpdata/en/c5/e4b06d453d11d189430000e829fbbd/frameset.htm

hi ,
the field actual agent gets will filled once the responsible agent completes / performs an action on it. Hence it is suggested to use some method / rule to get the responsible agent and create one local workflow container variable (table) to fill up the agents instead of manipulating the workflow variables directly.
In this way, you can check if the table of agents and then send accordingly the deadline messages.
Hope this helps.
Best Regards,
Saujanya

Escalation/Deadline monitoring

Hi,
There are three levels of managers (say L1, L2 & L3).
Work item (user decision step) goes to L1. The action that L1 can take is "Escalate to L2". L1 can either go to the transaction and complete the TECO for maintanance order or take the above action in UWL. IF L1 does not take any action in UWL for say 24 hours, workitem goes to L2, which is achieved by deadline monitoring.
Now the complexity is, L1 can go to the maintanance order and at the transaction level, if he selects radio button called escalated from IW32, even then the workflow should capture this action of his at transaction level and end the workitem in L1's inbox and escalate it to L2's inbox.
In a nutshell there should be three ways to escalate to L2
   a) take action from UWL - select 'Escalate to L2" in workitem.
   b) L1 does not take any action for 24 hours - deadline monitoring.
   c) L1 goes to transaction IW32 and select radio button "Escalated"
'a' and 'b' are pretty straight forward. I need to incorporate 'c' into the design.
My thoughts:
1) When L1 goes to IW32 and selects radio button 'Escalated', I will raise an event at the enhancement in the transaction ( will have to look - if I can do that) and put this event in the terminating events of the task. However it is user decision step - I cannot put a terminating event - as it is synchronus object method.
Please give me some inputs.
Thanks,
Sunita

Hi Sunita,
Sorry, last time, i think i misunderstood your requirement.
================
In a nutshell there should be three ways to escalate to L2
a) take action from UWL - select 'Escalate to L2" in workitem.
b) L1 does not take any action for 24 hours - deadline monitoring.
c) L1 goes to transaction IW32 and select radio button "Escalated"
'a' and 'b' are pretty straight forward. I need to incorporate 'c' into the design.
My thoughts:
1) When L1 goes to IW32 and selects radio button 'Escalated', I will raise an event at the enhancement in the transaction ( will have to look - if I can do that) and put this event in the terminating events of the task. However it is user decision step - I cannot put a terminating event - as it is synchronus object method.
===========
Based on the above, i think you require, if you have already sent a witem to L1 and it's there in his Inbox, AND if L1 is NOT USING workflow task to get to IW32 screen to select the "Escalated" button, then you need to cancel witem in L1's inbox and send a witem to user L2.
Is that correct ?
If yes, do the following:
1. in the user exit of IW32, raise the event "Serv.Order Escalated" based on the selection of "Escalated" button
2. Put this as Terminating Event for the User decision step(task) for which L1 already has a witem.
Here, pl note that if you are using the std. user decision TS00008267, it's better idea to copy and make your own custom user decision(Ex:- TS9200XXXX)and then add Terminating event(ex:- BU2088.ESCALATED).
YOU CAN ADD A TERMINATING EVENT, EVEN IF THE METHOD IS SYNCHRONOUS. ONLY THAT IF IF IT'S AN ASYNCHRONOUS METHOD, IT'S A MUST, IF THE METHOD IS SYNCHRONOUS, THEN IT'S OPTIONAL.
3. Then when you use this user decision in your workflow, you will get a new Outcome "Serv.Order Escalated". If the Outcome is not active, go to Outcomes of your User decision task and activate it.
4. In this Outcome branch, put a Process Control step "Cancel workflow(including all Callers). This will take out any witems for the already started worklfow instance. That means, witem in L1's Inbox is gone now.
5. Specify BU2088.ESCALATED also as one of the triggering events for your workflow. This will restart the workflow with a new instance.
6. And, the first step, you can have if the Triggering event of wflow instance is ESCALATED, then choose the path where you send witem to L2. If anyother event is triggering event, then it's the default path, sending witem to user L1.
============
Hope this should solve your problem. i have done just now the same and it's working fine.
Regards,
venu

Deadline monitoring & extended email without customizing a new workflow?

Hi,
I have a Position setup in Partner Profile - Post Processing:Permitted agent, to be notify if processing errors occur on the inbound idoc interface.
My questions are:
1. Besides receiving work item in SAP inbox for the idoc fallout, is there any way to send extended notification Outlook email to the users in that position when processing error occured?
2. How can i setup a deadline monitoring for the work item triggered only by these specific idoc message variant? In SWWA, it does not narrow down by workitem, permitted agent,partner profile etc.
3. If #2 can be fulfill, is it possible for me to trigger a new work item to another user/position? An escalation to next level after due date.
I know this can be done through customizing a workflow, but in my situation, i need to search for a solution in a standard existing SAP way without creating any new workflow, program or object.
Any suggestions?
Thanks.
Regards
Eunice
Edited by: Huwi Yin Puah on Oct 1, 2009 1:08 PM
Edited by: Huwi Yin Puah on Oct 1, 2009 1:10 PM

Huwi,
1# You can send the external notification using Send mail step in the standard workflow it self. I suppose, You can add new steps in Standard Workflow also. Use Send mail step and chose recipient type as "Email Address'. Pass the email Address and it will sent out to MS outlook inbox if all the SCOt Configurations are done.
2# You can activate the deadline monitoring on any activity by
double click on the activity
goto tab Latest End
Select the relevent options
3# For excalation you can set the deadline out come as a "Modeled" outcome. It would provide you an extra wing in your approval task and in that extra wing you can create your own task putting agent as manager's manager.
Hope it helps!
Cheers,
Vikash

Sending deadline monitoring mails....

Hi all,
I have created a workflow to send mail (user decision to approve or reject buttons) to an approver. If he doesnt respond to it till 3 days, a mail should be sent to his higer level person (say supervisor) and this supervisor should approver or reject the notification. If supervisor also doesnt take any action till 5 days a mail should be sent to the higer level person(manager) and manager should approve or reject the notification. This escalation goes on till 5 levels.
any suggestions and solutions would be very helpful.
Regards,
Gautham P

hi gautham,
use modeled deadline monitoring for sending the email to higher level, and activate the processing obsolete option in the outcome tab of the activity so that the as soon as the deadline is missed the task disappears from his inbox. For using the same you go into latest end tab of the activity there you can make the required deadline monitoring, If you want to terminate the workflow automaticallly aftr it has been esclated to the 5th level and the deadline has been missed, you need to define a terminating event and attach the same in the modelled deadline branch of the activity at the 5th level.
Hope it helps.
Cheers
Saurabh Anand.
P.S: Please award point if it helps

Modelled Deadline Monitoring - Solution for the same

Hi All,
I have a requirement where i need to use modelled deadline monitoring. My requirement is that when a work item is sent to a specific group. If that group does not respond to the work item in 3 days i need to send an escalation mail to that group and their superiors. After that i need to send the escalation mail every day till the work item is not executed.. How do i acheive the same using modelled deadline monitoring and do i need to make a user decision for ths task or is it possible to do the same without that.
Awaiting your reply shortly.
Regards,
Lailu Philip.

Hi Philip,
I have an idea. But I dont know how much its is good. After 3 days, mail has to be send to the approver. Then make a one background method, In method write a code to append the workitem number into a custom table.
Now create one zprogram, and read the workitem ID from the custom table. Then find the work item status using table SWWIHEAD. Then write a condition, if the status is ready then send a mail to the user using the FM 'SO_NEW_DOCUMENT_ATT_SEND_API1. This whole logic will be in your zprogram.
Then schedule one job and assign this program to that job. So it will run once per day and find the work items with status ready and it will send the mail to the correcsponding User.
Finally you can delete the corresponding entry at the Ztable from your workflow.
I think It will work.
Thanks.

Modelled Deadline Monitoring

Hi all,
I have developed a custom workflow and i am using modeled deadline monitoring in the same, the escalation happens properly after the deadline is reached, but the workitem is still visible in the previous agent's Inbox i have activated the processing obsolete option in the outcome tab of the workitem i have also checked the configurations in SWU3 and all of them looks to be fine, can anyone please help me on how to make the workitem disappear from the inbox once the deadline has reached.
Thanks
Saurabh Anand
PS: Points will be rewarded to useful replies.

Saurabh,
1. In the 'latest end' path of the work item insert a process control step.
2. In the Control tab of the process control, for 'function' choose 'set work item to obsolete'.
3. In the 'workflow step', enter the step id for which you have made the modeled deadline monitoring.
When the deadline is reached for the work item, it is removed or 'obsolete'-d and workflow continues through the 'processing obsolete' path.
Reward points if useful.

Error in Schedule Background Job for Deadline Monitoring of swu3

While Auto Customization swu3 i am getting error message 'Output device "" not known' in 'Schedule Background Job for Deadline Monitoring'
Please advice what could be cause of it

the earlier problem of background job was solved by changing the output device assigned to user wf-batch .
regarding the transport request :
when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have executed it automatically ...
well thanks all for u r help

Background Scheduling - Deadline Monitoring

Hi Experts,
I have created new maintenance plan , its around 250 for Mechanical and 250 for Electrical
Maintenance plan having strategy like every two month , every three month , every six month etc..
Scheduling period is 3 year
Now scheduling will be done through IP10 one time , but after first call object scheduling will get hold.
I want to make it background scheduling - Deadline Monitoring
Now the requirement is , For Example :
Maintenance plan X have PM plan date is 21.07.2014
Maintenance plan Y have PM plan date is 24.07.2014
Maintenance plan Z have PM plan date is 29.07.2014
As per above example each equipment will have different plan date , background scheduling can be done through IP30 but by the date is concern how can make it possible ?
Please advise each maintenance plan has to be run as per their plan date.
Thanks,
Abhishek

Hi Mr.Jogeshwara,
Nice Document , Its really useful
But my query is each equipment have different plan date , as explained in above example
If Maintenance plan have Cycle Unit 60 day and Plan X date is on 21.07.2014 then 21.07.2014+60day , same as if maintenance plan Y date is 25.07.2014 then 25.07.2014 +60day
Like that
background scheduling needs to be done as per cycle unit
If i will do background scheduling together of both the above maintenance plan X and Y then scheduling will be run exactly after 60 day and order will be generated in advance for Maintenance plan Y.
Hope you understand my query.
Thanks,
Abhishek

Workflow Deadline Monitoring for SC in SRM 7.0

Hi,
I have activated the deadline monitoring for WF_APPR_LATEST_START event for 1 hour. But didnt see any notification to the requestor and the approver. So need help here.
Below is the setting that i have done to activate deadline.
1. In Define event > BUS2121 > WF_APPR_LATEST_START:SC
2. Define Event Schema > BUS2121 > Event scema : SC > WF_APPR_LATEST_START:Message (low priority):APPROVAL_DEADL_NOTIFIC_NEW:1.
Thanks In Advance.

Masa thanks for replying..
They are in place.
I checked the Workitems Log for administrator ... and could see the workitem 'Trigger Event: 'WF_LATEST_START'' fired exactly after one hour the SC was created as set in the config... but no notification is sent to Outlook.
Background Job RSWWDHEX is also running every 5min ... But didnt see any notification.

Problem in deadline monitoring of batches

Dear experts,
Deadline monitoring of batches (transaction QA07) is not working. I tried running this but it did not post stock of a batch whou2019s expiry date was in next 2 days in blocked stock. I had specified the material no, plant, initial run in days (the one that is underu201D batch status change when expiration date is reachedu201D) and also flagged the checkbox for u201CBlock batchu201D. All other fields were left empty. Also QM module is not active. The message was u201CNo entries foundu201D , I confirmed the batch details with u201CMSC2Nu201D , it was in next 2 days and the same is reflected in report u201CMB5Mu201D too.
Please let me know whether QM is required to be active for execution of QA07 or there is some other problem.
thanks in advance

Ok... I'm still confused. Why can't you run the standard deadline mointoring program?
I believe you still need to activate the 09 inspection type but this can be done in mass using QA08. Since your not using inspection intervals, don't maintain the inspection interval field in the QM view.
No config needs to be done, the standard as delivered config in QM should work.
Run the deadline mointoring program (QA07?) but only fill in data in the bottom half for blocking expired batches.
Set the program up to to run nightly with whatever 'window' you desire, i..e block those that expire in 1 day, or 5 days, or ten days.
If you are using batch status management, then the batches will be restricted. If you are not, they will be moved to blocked stock.
Craig

Extended notification and deadline monitoring

We are using extended notification to deliver new and changed workitem by email. Now we want to update some workflow approval tasks to add deadline notification. In SWU3 workflow customizing, we had setup "Schedule Background Job for Deadline Monitoring" to run job RSWFSLSDLEX (previous version is SWWDHEX).
My question: if there is some outstanding workflow task meet the deadline, will the notification email sent out by job RSWFSLSDLEX or extended notification report SWN_SELSEN? Thanks in advance.
Regards,
Donald

Hi,
The deadline monitoring job only creates additional workitems if a deadline is met, the sending of an email job retrieves workitems and sends them as email.
Kind regards, Rob Dielemans

Srm 70 BRF deadline monitoring BUS2201

Dear SDN-ers,
We are using SRM70 process controlled workflow.
In my project we would like to use deadline monitoring on PO approval workitems.
When we check the customising for deadline for events Business object BUS2201 does not contain any usable events for monitoring deadline and sending notifications when the deadline is passed. See also table BBPC_EVENT_DEF.
In the customising for BUS2121 there are events available like WF_APPR_REQUESTED_STARt etc.
Can we create those events for BUS2201 and how can we do this?
Kind regards,
Johan

Hi,
I have not tested but you can add WF_* event in customizing.
SRM -> SRM Server -> Cross-Application Basic Settings -> Event and Event Schema for Alert Management -> Define Events and Define Event Schema.
Regards,
Masa

WS14000133 Deadline Monitoring / Escalation

Similar Messages

Maybe you are looking for