<div>Hello Folks </div>
<div>We have been using deadline escalation on our workflows for SC approval for years.</div>
<div> </div>
<div>I have configured the "Latest Start" deadline such that if a WI is not started to process in 7 days it will become obsolete. </div>
<div>The next step in workflow is a container operations which assigns an element "ZFirstagent" from the container to another element called "Deadline" (" Deadline = Zfirstagent").</div>
<div> </div>
<div>Zfirstagent has the userid of the approver who had been initially selected to approver the shopping cart</div>
<div> </div>
<div>I will then call a role resolution function and pass element Deadline to this function call so that I get the next level up for Zfirstagent, a workitem will be assigned to this next level up agent for approval. This was working accurately for the past 8 years. </div>
<div> </div>
<div>Recently I have a noticed a really spooky behaviour. The container operation of " Deadline = Zfirstagent" is assigning a very different value to the element Deadline. This is not the actual contains of the ZFIRSTAGENT, in fact this value in not to be found anywhere in the task container and/or the workflow container. </div>
<div> </div>
<div>We have recently applied support packs to our SRM 5.00 system as attached. The closest note I could find on the subject is <a class="urLnkFunction urVt1" title="Right mouse click to add this SAP Note to your browser favorites" href="https://service.sap.com/sap/support/notes/1325541" alt="Right mouse click to add this SAP Note to your browser favorites"><span class="urTxtH1" id="header_data">Note 1325541 - Deadline monitoring: Agent determination ignores defaul rule</span></a> which is not exactly relevant. </div>
<div> </div>
<div> </div>
<div>Any thoughts or suggestions you may have are welcome.</div>
<div>Thanks</div>
<div>Shalini</div>