<HTML><BODY>
<div>John,</div>
<div> </div>
<div>I agree with you that <SPAN contentEditable=false style="DISPLAY: inline-block"></SPAN><FONT face=Arial>the release strategy characteristics need to be updated. Also there are other situations like multiple Purchase Groups are used in a PR. A <SPAN class=correction id="">blank</SPAN> value can be maintained for the characteristic to catch this but currently we are not doing it. I am interested in knowing what has been done to catch this No Release Strategy situation as soon as the PR is created and before a PO is generated for it.</FONT></div>
<div> </div>
<div style="CLEAR: both">Best Regards,<br>
<SPAN class=correction id="">Ramki</SPAN> <SPAN class=correction id="">Maley</SPAN>.</div>
<div> </div>
<br>
-----Original Message-----<br>
From: Scheinoha.John@basco.com<br>
To: sap-wug@mit.edu<br>
Sent: Wed, 28 Mar 2007 5:46 PM<br>
Subject: RE: PR Overall Release<br>
<br>
<STYLE>
.AOLPlainTextBody {
margin: 0px;
font-family: Tahoma, Verdana, Arial, Sans-Serif;
font-size: 12px;
color: #000;
background-color: #fff;
}
.AOLPlainTextBody pre {
font-size: 9pt;
}
.AOLInlineAttachment {
margin: 10px;
}
.AOLAttachmentHeader {
font: 11px arial;
border: 1px solid #7DA8D4;
background: #F9F9F9;
}
.AOLAttachmentHeader .Title {
font: 11px arial;
background: #B5DDFA;
padding: 3px 3px 3px 3px;
}
.AOLAttachmentHeader .FieldLabel {
font: 11px arial;
color: #000000;
padding: 1px 10px 1px 9px;
background: #F9F9F9;
}
.AOLAttachmentHeader .FieldValue {
font: 11px arial;
color: #000000;
background: #F9F9F9;
}
.AOLAttachmentHeader a, .AOLImage a {
color: #2864B4;
text-decoration: none;
}
.AOLAttachmentHeader a:hover, .AOLImage a:hover {
color: #2864B4;
text-decoration: underline;
}
.AOLWebSuiteCompose .AOLPicturesFullSizeLink,
.AOLWebSuite .AOLPicturesFullSizeLink {
height: 1px;
width: 1px;
overflow: hidden;
}
body {
background-color: white;
font-family: "Verdana";
font-size: 10pt;
border: 0px;
}
.AOLWebSuiteCompose p {
margin: 0px;
padding: 0px;
}
img.managedImg {
width: 0px;
height: 0px;
}
img.placeholder {
width: 275px;
height: 206px;
background: #F4F4F4 center center no-repeat;
border: 1px solid #DADAD6 !important;
}
</STYLE>
<div id=AOLMsgPart_3_ab2243cb-01c6-44b2-a5d3-b82d3328cf8c>
<div dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial color=#0000ff size=2><SPAN class=correction id="">Ramki</SPAN>,</FONT></SPAN></div>
<div dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </div>
<div dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial color=#0000ff size=2> The release strategy characteristics need to be updated in the Purchase Requisition Release strategy. Otherwise if you have a purchase requisition created with the new purchase group value, there is no release strategy associated with the new Purchase Group value, the system will not create a release strategy, no approval will be generated and the requisition will be approved by default (omission). </FONT></SPAN></div>
<div dir=ltr align=left><SPAN class=290294021-28032007></SPAN> </div>
<div dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial color=#0000ff size=2> Yes I have experienced this situation one too many times.</FONT></SPAN></div>
<div dir=ltr align=left><SPAN class=290294021-28032007></SPAN> </div>
<div dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial color=#0000ff size=2>Good Luck and Best Regards,</FONT></SPAN></div>
<div dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial color=#0000ff size=2>John Scheinoha</FONT> </SPAN></div>
<br>
<div class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> <A href='javascript:parent.ComposeTo("sap-wug-bounces%40mit.edu", "");'>sap-wug-bounces@mit.edu</A> [<A href='javascript:parent.ComposeTo("sap-wug-bounces%40mit.edu", "");'><SPAN class=correction id="">mailto</SPAN>:sap-wug-bounces@mit.edu</A>] <B>On Behalf Of </B><A href='javascript:parent.ComposeTo("workflow99%40aol.com", "");'>workflow99@aol.com</A><br>
<B>Sent:</B> Wednesday, March 28, 2007 4:32 PM<br>
<B>To:</B> <A href='javascript:parent.ComposeTo("sap-wug%40mit.edu", "");'>sap-wug@mit.edu</A><br>
<B>Subject:</B> PR Overall Release<br>
</FONT><br>
</div>
<div></div>
<div><SPAN style="DISPLAY: inline-block"></SPAN>Hi all,</div>
<div> </div>
<div>This is not a pure <SPAN class=correction id=""><SPAN class=correction id="">workflow</SPAN></SPAN> question but on the fringes. Client has PR overall release with classification. The system cannot determine Release Strategy in <SPAN class=correction id="">certain</SPAN> cases (for instance a new purchase group is created but the characteristic values are not updated). The PR then does not need an approval. I hope some of you have faced this situation and would like to hear your experience on how you have dealt with it. </div>
<div> </div>
<div><SPAN class=correction id=""><SPAN class=correction id="">TIA</SPAN></SPAN>.</div>
<div> </div>
<div style="CLEAR: both">Best Regards,<br>
<SPAN class=correction id=""><SPAN class=correction id="">Ramki</SPAN></SPAN> <SPAN class=correction id=""><SPAN class=correction id="">Maley</SPAN></SPAN>.</div>
<div class=AOLPromoFooter>
<HR style="MARGIN-TOP: 10px">
AOL now offers free email to everyone. Find out more about what's free from AOL at <A href="http://pr.atwola.com/promoclk/1615326657x4311227241x4298082137/aol?redir=http://www.aol.com" target=_blank><B>AOL.com</B></A>.<br>
</div>
</div>
<!-- end of AOLMsgPart_3_ab2243cb-01c6-44b2-a5d3-b82d3328cf8c -->
<div class=AOLPlainTextBody id=AOLMsgPart_4_ab2243cb-01c6-44b2-a5d3-b82d3328cf8c><PRE><TT>_______________________________________________
SAP-WUG mailing list
<A href='javascript:parent.ComposeTo("SAP-WUG%40mit.edu", "");'>SAP-WUG@mit.edu</A>
<A href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A>
</TT></PRE></div>
<!-- end of AOLMsgPart_4_ab2243cb-01c6-44b2-a5d3-b82d3328cf8c --></BODY></HTML>