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

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

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

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

'Requested Start' tab does not work.

Hi everybody,
By filling out the 'Requested Start' tab, I set 2 minutes delay in one of my workflow steps, but after the workflow gets started it stops at the step forever with 'Warting' status.
I've tried the same thing in the same way but on another R3 system. On the other system, the workflow runs smoothly.The step can start on time.
So here comes the question: What configurations can bring this difference between these two R3 system?
Thanks in advance.
Regards,
Minghao

Hi,
The evaluation of deadlines ( like requested start, latest end etc..) is done by 'Scheduled Backgorund Job for Missed Deadlines'. It looks like this is not active in your case.
Check SWU3 under 'Maintain Runtime Environment', if it is not active make it active by executing it. Check the prerequisites for the same. The user doing this customization should belong to SUPER user group. Otherwise, i have seen cases where these gets deactivated automatically with unknown reasons.
Hope this helps you !!
Regards
Krishna Mohan

Testing With Requested Start Deadline Monitoring - can't wait for deadline.

Hi'
In my workflow, I have a background task with a Requested Start 14 days after workitem creation.
This works fine, but for testing purposes, I would like to 'push' this background task earlier (rather than wait 14 days to continue my test).
Do you know any tool which will allow me to execute the workitem before the deadline is reached?
Regards,
Karin.
Message was edited by:
Karin Lund

Depending on little bit of the SAP version, you should be able to go to the specific work item in change mode. There you have a functionality, where you can change the deadline of an item. Just change it to 5 minutes from now and then just wait. Remember that the job that is checking if deadlines have been exceeded is running probably in every 5 minutes. So actually the waiting time for you can be more than 5 minutes.
Regards,
Karri

Requested End Deadline monitoring for Background Activity Step

Hi All,
Workflow for MSS Position change has been implemented in the system.
When a request was created thru Portal the Workflow was triggered but it got stuck.
I found that in a background activity step there is a requested end deadline monitoring which was reached.
Since it is a background activity there is no agent assigned, then what could be the reason that the deadline was reached ?
Can anyone tell me when is the Requested End deadline triggered ?
Regards,
Radhika.

Hello,
Yes, if it's workitem creation time + 1 minute then it means the deadline (any deadline - Latest End, Requested End, Requested Start etc, they're all the same, they just have different names) gets triggered.
What happens next depends on how that deadline has been defined - it may just send a message to someone and do nothing else (ie it leaves the background process running). Or it may be a modeled deadline set up to end the process. Have a look in the Requested End tab to see what it does.
regards
Rick Bakker
Hanabi Technology

I have a Power MAC G5 dual 2ghz that has a peculiar problem. The monitor will not report until the machine is stopped and started 5 or 6 times. Once booted it will restart without problem if done so from the apple menu. Swapped out all hardware

My Power MAC G5 has a peculiar problem. The monitor fails to report until the machine is started and shut down 5 or 6 times. Once it has booted it can be restarted without incident from the Apple menu. I have swapped out all of the hardware. Monitor, Memmory,Video Card and reset the PRAM. After resetting the PRAM it booted on the first attempt and I thought it was solved. But the next day it was back to starting and stopping until the Monitor came on. Does anyone have a suggestion? Thanks

It could be a bad PRAM battery corrupting your PRAM. Typically when I have monitor issues on startup it is a bad PRAM battery.
Texas Mac Man's PRAM, battery, PMU tutorial - https://sites.google.com/site/macpram/mac-pram-nvram-cuda-pmu-battery-tutorial
Apple's PRAM reset directions - http://docs.info.apple.com/article.html?artnum=2238
If you have a digital multimeter you can check the condition of your present battery. It should read at least 3.2V if it is the 3.6V half-AA battery type. A new battery provides 3.67 Volts DC. A bad battery provides under 3.2 Volts DC. Ideally this should be measured while the battery is under load; added recommendation from Hans777:
>I have recently found out that an exhausted battery will still indicate >3.6 V with a high internal resistance VM.
>
>Checking incircuit: powercord disconnected press PMU reset button for >about 5 sec before measuring.
>
>Checking outside: load the battery with a 1500 Ohm resistor when measuring.
Alternatively, test the battery while it is still in the computer.
If the battery is more than 5 years old, especially if you totally disconnect the computer from the power regularly, or have left it unplugged for several months at one time, it is likely the battery is dead.
Sometimes you have to do a more intensive reset of hardware management:
[Resetting Cuda/PMU on Power Mac G5, Power Mac G4, Power Macintosh G3|http://support.apple.com/kb/HT1939]
[How to reset the SMU on a Power Mac G5 (Late 2004) or Power Mac G5 (Late 2005)|http://support.apple.com/kb/HT1436]
[iMac G5: How to Reset the SMU|http://support.apple.com/kb/HT1767]

Problem in Workflow during activity step with "Requested start" time.

Hi,
I am working on SAP workflow.
In my workflow there is a activity step (wait step) where the workflow should wait before going to step after that wait step. To achieve this, I have used requested start as +10 min with WIS workitem creation. After 10 min, the workflow should proceed to further step but my workflow does not go further.
It was working good I tested couple of days back but now it doesn't. Can someone please help ?
Thanks.
Regards,
Rajesh.

Please check the settings in SWU3. Most probably the settings is not correct. You will get a lot of discussion from this forum if you search with SWU3.
Thanks
Arghadip

Using 'Expression' in Requested Start Does not work

I need a workflow to send an email 90 days before a Qualifications End Date. Using BUS7019 with 90- Days in the Requested Start, the date populates perfectly. I look at the work item and the Requested Start deadline looks good. However, the date comes and goes and the work item continues to wait. During testing I was using a container item to set the time as well. At first I thought that might be the problem. So I tried it without a time, which sets it to 00:00:01. So I started the worflow and waited until the next day. Current date 09/16/09 09:00:00, work item with Requested Start 09/16/09 00:00:01 and it is still in Wait status. If I set the Latest Start, the work item fires off immediately, so I know the workflow itself works.
I checked SWAA and it is set to check every 3 min. I ran SWU_OBUF just to be safe.
In the past I have used "work item creation" to set the date and have not had a problem. I recall someone telling me that there is a bug when using "Expressions". Is this true or am I missing something? Is there an OSS note for this?

go to the workflow log of the workitem, click extras-->technical data and then the tab Deadline Data.
Make sure that this information is there.
If it isn't then you need to make sure that the expression has the correct time data and correct format.
If this is there, then check in the job logs if the deadline monitoring job is working correctly.
If this is also working, you should search OSS for a solution or create a new message when you don't find any.
Kind regards, Rob Dielemans

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

Workflow Deadline monitoring

Hi,
Is it possible to re-trigger deadline monitoring more than once, so that if a PO approver has not released a PO within 24 hours, they will receive a reminder every 12 hours until this task

hi..
I hope that you are using an activity step to send workitem to PO approver to approve the PO..
After that step you do as below,
1. Create a loop which loops until your condition (PO approver approves the PO) is met..
2. Insite loop place an activity step with BOR as selfitem and method as sendtaskdescription (This is used to send mail remainders to approver)
3. In that activity step add a requested start deadline of 12 hrs so that mail is sent every 12 hrs..
4. Note that here you are not inserting you actual activity step that you send to PO approver inside loop. So you need not worry that workitem is send repeatedly to him. Only activity step to send remainder mails is inside loop.
Hope this helps..
Cheers,
Bharath
Edited by: bharath padmanabhan on Jul 11, 2011 6:20 PM

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

Execute Background Work Item using Deadline Monitoring

Hi All,
I want to execute a Background Task using Requested Start. The status of Work Item is Waiting. But it is not executing after Deadline reaches and in graphic log it displays no agent. As per my knowledge Background work item is executed by Workflow system itself.

Hi Bikash
check if the deadline monitoring job is running or not. SM37-> Check for job SWWDHEX
if not then schedule it from SWU3.
This is the job which actually picks up the waiting items (waiting for deadlines).
regards,
Modak

Problem in Deadline monitoring-Requested Start

Similar Messages

Maybe you are looking for