<div>Didn't realise halloween + SPs do a number on workflows ;-)</div>
<div> </div>
<div>One more piece of information I forgot to mention, this problem only occurs in our production environment. I could not repeat it in our test environments even though they are all on the same level of support packs. </div>
<div> </div>
<div>It almost seems like a container index issue if there would have been such a thing. </div>
<div> </div>
<div>Again any help is welcome.</div>
<div>Shalini<br><br></div>
<div class="gmail_quote">On Tue, Nov 3, 2009 at 12:27 PM, Mike Pokraka <span dir="ltr"><<a href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">That'll teach ya to apply support packs around Halloween! :-)<br>
<div>
<div></div>
<div class="h5"><br>On Tue, November 3, 2009 4:20 pm, Shalini Sabnani wrote:<br>> Hello Folks<br>> We have been using deadline escalation on our workflows for SC approval<br>> for<br>> years.<br>><br>> I have configured the "Latest Start" deadline such that if a WI is not<br>
> started to process in 7 days it will become obsolete.<br>> The next step in workflow is a container operations which assigns an<br>> element<br>> "ZFirstagent" from the container to another element called "Deadline" ("<br>
> Deadline = Zfirstagent").<br>><br>> Zfirstagent has the userid of the approver who had been initially selected<br>> to approver the shopping cart<br>><br>> I will then call a role resolution function and pass element Deadline to<br>
> this function call so that I get the next level up for Zfirstagent, a<br>> workitem will be assigned to this next level up agent for approval. This<br>> was<br>> working accurately for the past 8 years.<br>><br>
> Recently I have a noticed a really spooky behaviour. The container<br>> operation<br>> of " Deadline = Zfirstagent" is assigning a very different value to the<br>> element Deadline. This is not the actual contains of the ZFIRSTAGENT, in<br>
> fact this value in not to be found anywhere in the task container and/or<br>> the<br>> workflow container.<br>><br>> We have recently applied support packs to our SRM 5.00 system as attached.<br>> The closest note I could find on the subject is Note 1325541 - Deadline<br>
> monitoring: Agent determination ignores defaul<br></div></div>> rule<<a href="https://service.sap.com/sap/support/notes/1325541" target="_blank">https://service.sap.com/sap/support/notes/1325541</a>> which<br>
<div class="im">> is not exactly relevant.<br>><br>><br>> Any thoughts or suggestions you may have are welcome.<br>> Thanks<br>> Shalini<br></div>> _______________________________________________<br>
> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</blockquote></div><br>