Problem in Deadline monitoring

Hi i am using deadlien monitoringin my workflow, I need certain trasaction to be called if that has come from Dealine moniroting, is there any way i can come to know that this has come from deadline moniroting?

Hello Munish,
For a transaction to be called when a step has missed the deadline monitoring, you can use the modeled deadline monitoring and then insert a step type, execute a method in which the required transaction is called.
Hope this will help.
Regards,
Sam

Similar Messages

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

Problem in Deadline monitoring-Requested Start

Hi All,
We have custom PR workflow in whcih in the case of rejection we are creating the event for the same workflow using SAP_WAPI_CREATE_EVENT.
for this create event step we have an activity where in Requested start is activated on "Work item creation" for 3 minutes.
As a result we are getting 2 workitems genearated for the same PR and same event.
Examaple: Create event step started at say 10.00.00
we have one workitem created st 10.00.00 and another
workitem at 10.06.00.
In SWWA we have given 5 Minutes.
I jus wanted to know how this Requested start is expected to behave? And how can i solve this issue?
if i remove the requested start, does it work properly?

Raj..
You are right..but i dont see any harm in using API FM inside the workflow...
And this has been perfectly working in prod environment for several years..
In sandbox..they have create some new release groups and for which we are facing issue...
Between i have a doubt in Background program of deadline :
In sandbox we hre having like this :
Name           RSWWDHEX
Variant        &0000000000001
Language       EN
And in job log am getting like this " '2' entries have been edited"
But in prod we are having like this
Name           RSWWDHEX
Variant        &0000000000000
And in job log am getting like this " '1' entries have been edited"
So i doubt abt this settings...Can you please check in your Prod environment ane let me know the correct settings.
Language       EN
Edited by: Swaminathan PJ on Dec 31, 2009 12:19 PM

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

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.

Modeled Deadline monitoring is not working

In workflow i have used modeled Deadline monitoring for the task, in modeled branch i put a send mail step
in that branch that is working fine. once the deadline is reached that workitem is not disappearing from users inbox and modeled branch is working fine , what could be the problem please suggest me.

Hi,
Refer below link and fix it
[Link1|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/303617cf-73dd-2a10-c993-cc6303585176] [Link2|https://wiki.sdn.sap.com/wiki/x/EwEqB] [Link3|https://wiki.sdn.sap.com/wiki/x/fQDDAw].
Regards,
Surjith

Possible loop deadline monitoring for a period of time?

Hi All,
Here is our scenario.. We have a task sent to the managers inbox with deadline monitoring on it. If the manager does not action this task, we set this task to obsolete and then we want to send a reminder email every day until the manager performs the required action.
So the problem.. originally this email was to be a task but the loop would not work with the task as it's waiting on action from the user. We changed this task to an email and it looped as expected however the only way I could think to put a wait for a period of time before another email is sent is by actually counting down the time in a method.
However, the problem with this is that wf-batch is locking the worklfow so it can never complete, even if the event to complete the workflow is triggered. wf-batch has it locked so the workflow can never complete, so it loops infinitely.
So my question.. is it possible to repeatedly send notifications to a manager at specifically defined time intervals without locking the workflow?
Below is how the workflow currently looks:
Any guidance on this would be most gratefully received!
Thanks in advance,
Liz.

Hi Liz
in your wait step, do not count down the time.
Instead keep the method as a dummy method with no code.
In the wait step, use the deadline monitoring - Requested Start - set it to current date + 1 day
The step will start 1 day after 'today' , execute nothing in Dummy method and then go on to the mail step
I am sure that the deadline monitoring job is running because "Latest End" of the first task is executed in your system. So the same job will take care of Requested Start of the wait step.
regards,
Modak

Deadline Monitoring for Maintenance Plans

Hi there,
i want to execute the deadline monitoring (IP30) for a maintenance plan in
a function module. Unfortunately I couldn't find a function module for this
purpose.
So I tried to execute RISTRA20 (program connected to IP30) with the
following statement:
SUBMIT ristra20
USING SELECTION-SCREEN '1000'
WITH SELECTION-TABLE rspar_tab
AND RETURN.
Problem with this call is that some dialogue-dynpros are shown - I want the deadline monitoring completely in the background.
Any ideas? Thx in advance..
Regards,
Markus

we have found similar problems in many PM jobs; in some cases there are some Notes pointing to the issue ( and fixing them, too ) ; for this case check Note 984177 and related.

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

Conditional Deadline monitoring.

Hi,
I have one requisition form through which we are raising two types of request Attendence and Absence.
Now for both these types of request we are triggering same workflow.
In this workflow first activity is Approval activity.
Now my question is i want to use Latest End Deadline monitoring in this activity (Approval activity) but only for one request type, say Absence Type, but for Attendence Type i don't want deadline monitoring.
How can i achieve this?
Regards,
Amar

Dear Rick,
Thank You for your help.
It solved my earlier issue, now i am facing another issue.
Scenarion is:
In my Approval Activity, i am using certain conditions within Conditions Tab-> Complete Workitem ( i am cecking REQ_Status = 'A').
That means if this condition satisfy my workitem should get complete.
Now after raising my requisition, initially value for container element REQ_Status is blank (initial), now with the help of function SAP_WAPI_WRITE_CONTAINER i am setting the container element REQ_Status = 'A'.
And then i am executing report RSWWCOND (Job for condition evaluation).
Then according to my knowledge my workitem should get completed, but nothing is happening and my workitem is still in ready status only.
Can you please help me to solve this problem.
Regards,
Amar

Deadline monitoring batch jobs

Hi batch jobs for deadline monitoring are getting hanged for few times. Sometimes it works fine.
I am not getting why it is getting hang out for few times.
If anybody faced this problem, pls share the possibilities.
regards,
Kedar

Hi,
Please check parameters of deadline monitoring especially parameter "Interval for call objects".If its very long in future then possible reason is system is trying to generate calls for this long period and it may that job is not completed with time parameters set by basis administrator.And this may resulting into termination of job.
So try to limit this parameter and also no of maintenace plan if you have a very huge list.Also check with basis person if any such jobs terminated due to very long time they are running
regds,
atul

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

The problem is to monitor two experimental parameters

The problem is to monitor two experimental parameters (pressure and temperature) using USB -6008. These parameters are converted to voltage by proper sensors.
I use the following sequence of commans:
DAQmxBaseCreateTask("T",&taskHandle);
DAQmxBaseCreateAIVoltageChan(taskHandle,"Dev1/ai0","",DAQmx_Val_Diff,-10,10,DAQmx_Val_Volts,NULL);
DAQmxBaseCreateAIVoltageChan(taskHandle,"Dev1/ai1","",DAQmx_Val_Diff,-1,1,DAQmx_Val_Volts,NULL);
DAQmxBaseStartTask(taskHandle);
Then I read the results every 200 msec. To do this I put into the Timer event handler next code:
{ DAQmxBaseReadAnalogF64(taskHandle,1,timeout,0,data,2,&pointsRead,NULL);
data[0] I convert to pressure;
data[1] I convert to temperature;
The program works, but I am not satisfied because of noise. The origin of the noise is electric interference of power network. I know that the best way to reduce electrical interference is to integrate a signal over period of the power network (20 msec in Russia). All high sensitivity digital voltmeters do this integration. The idea is to make, for example, 40 measurements with SampleRate=2000 , ( 0.5 msec * 40 = 20 msec) instead of single measurement. Then calculate the sum of pressure readouts and the sum of temperature readouts. This procedure should be repeated every 200 msec using the Timer event handler.
Therefore I added before DAQmxBaseStartTask(taskHandle);
DAQmxBaseCfgSampClkTiming (taskHandle, source, sampleRate, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, 40);
and modified Timer event handler:
{ DAQmxBaseReadAnalogF64(taskHandle,40,timeout,0,data,80,&pointsRead,NULL);
data[0] … data[39] I convert to pressure;
data[40] … data[79] I convert to temperature;
Testing of the program showed: the program can make only one cycle of measurement. All times I call the DAQmxBaseReadAnalogF64 the results were the same. It looks like USB-6008 make one cycle of measurement (probably at DAQmxBaseStartTask) and puts the results to the buffer. And the DAQmxBaseReadAnalogF64 just read the buffer but can not initiate new measurements.
How the program can initiate new cycle of measurements? Could anybody to help me?

Dear Micaela,
Thank you for advice. I will change driver to the DAQmx . But it will take time to download 460 M.
Therefore I continued with the old driver.
I changed DAQmxBaseCfgSampClkTiming to DAQmx_Val_ContSamps and immediately faced with another problem. The device began to acquire data continuously, and when I call DAQmxBaseReadAnalogF64 in the timer handler, I got the date that does not correspond to the current time. The data corresponds to the experimental parameters which were 5 minutes ago. I was very surprised until I realized that this huge delay exits!
To fix this problem I tried to add DAQmxBaseStartTask and DAQmxBaseStopTask to the timer handler.
     DAQmxBaseStartTask(taskHandle);
     DAQmxBaseReadAnalogF64(taskHandle,40,timeout,0,data,80,&pointsRead,NULL);
     DAQmxBaseStopTask(taskHandle);
    data[0] … data[39] I convert to pressure;
     data[40] … data[79] I convert to temperature;
The program did not work. Even did not respond to any action.

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

Similar Messages

Maybe you are looking for