<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff>Ramki,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff>We use user exit EXIT_SAPLEBND_004 to do something similar to this
and it has worked very well.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff>Hope you get this issue resolved.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=629311814-29032007><FONT face=Arial
color=#0000ff>Seth</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Scheinoha,
John<BR><B>Sent:</B> Thursday, March 29, 2007 8:41 AM<BR><B>To:</B>
sap-wug@mit.edu<BR><B>Subject:</B> RE: PR Overall Release<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><FONT face='"Verdana"'><SPAN
class=290294021-28032007><FONT face=Arial color=#0000ff><SPAN class=correction
id="">Ramki</SPAN>,</FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=290294021-28032007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=290294021-28032007><SPAN class=064173113-29032007> We've
talked about adding validation in the user-exit that determines the release
strategy. The logic would be "if a non-MRP requisition is created without
a release strategy being determined, create an error message back to the user
indicating no release strategy can be determined." Our thought is that a
new Purchase Group, Material Group, or some other release characteristic value
is being used that is not in a valid release strategy. Our hope is the the
user will encounter the error and call our business analyst to determine why the
release strategy can not be determined.</SPAN></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=290294021-28032007><SPAN
class=064173113-29032007></SPAN></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=290294021-28032007><SPAN class=064173113-29032007> The use
exit is in the following path: SAPLMEREQ => LMEREQFXX => LMREQF08
=> LMEREQFDD => ME_REQ_GET_RESPONSIBLE_EBAN => LEBNFU16
=></SPAN></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=290294021-28032007><SPAN
class=064173113-29032007>EXIT_SAPLEBNF_001.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff><SPAN class=290294021-28032007><SPAN
class=064173113-29032007></SPAN></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff><SPAN class=290294021-28032007><SPAN
class=064173113-29032007> I hope this
helps,</SPAN></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff><SPAN class=290294021-28032007><SPAN
class=064173113-29032007></SPAN></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff><SPAN class=290294021-28032007><SPAN
class=064173113-29032007>Best Regards,</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial><SPAN class=290294021-28032007><SPAN
class=064173113-29032007><FONT face=Verdana color=#0000ff>John
Scheinoha</FONT></DIV>
<DIV dir=ltr align=left><FONT
color=#0000ff><BR></FONT></DIV></SPAN></SPAN></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of
</B>workflow99@aol.com<BR><B>Sent:</B> Thursday, March 29, 2007 6:55
AM<BR><B>To:</B> sap-wug@mit.edu<BR><B>Subject:</B> Re: PR Overall
Release<BR></FONT><BR></DIV>
<DIV></DIV>
<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 {
FONT-SIZE: 12px; MARGIN: 0px; COLOR: #000; FONT-FAMILY: Tahoma, Verdana, Arial, Sans-Serif; BACKGROUND-COLOR: #fff
}
..AOLPlainTextBody PRE {
FONT-SIZE: 9pt
}
..AOLInlineAttachment {
MARGIN: 10px
}
..AOLAttachmentHeader {
BORDER-RIGHT: #7da8d4 1px solid; BORDER-TOP: #7da8d4 1px solid; BACKGROUND: #f9f9f9; FONT: 11px arial; BORDER-LEFT: #7da8d4 1px solid; BORDER-BOTTOM: #7da8d4 1px solid
}
..AOLAttachmentHeader .Title {
PADDING-RIGHT: 3px; PADDING-LEFT: 3px; BACKGROUND: #b5ddfa; PADDING-BOTTOM: 3px; FONT: 11px arial; PADDING-TOP: 3px
}
..AOLAttachmentHeader .FieldLabel {
PADDING-RIGHT: 10px; PADDING-LEFT: 9px; BACKGROUND: #f9f9f9; PADDING-BOTTOM: 1px; FONT: 11px arial; COLOR: #000000; PADDING-TOP: 1px
}
..AOLAttachmentHeader .FieldValue {
BACKGROUND: #f9f9f9; FONT: 11px arial; COLOR: #000000
}
..AOLAttachmentHeader A {
COLOR: #2864b4; TEXT-DECORATION: none
}
..AOLImage A {
COLOR: #2864b4; TEXT-DECORATION: none
}
..AOLAttachmentHeader A:hover {
COLOR: #2864b4; TEXT-DECORATION: underline
}
..AOLImage A:hover {
COLOR: #2864b4; TEXT-DECORATION: underline
}
..AOLWebSuiteCompose .AOLPicturesFullSizeLink {
OVERFLOW: hidden; WIDTH: 1px; HEIGHT: 1px
}
..AOLWebSuite .AOLPicturesFullSizeLink {
OVERFLOW: hidden; WIDTH: 1px; HEIGHT: 1px
}
BODY {
BORDER-RIGHT: 0px; BORDER-TOP: 0px; FONT-SIZE: 10pt; BORDER-LEFT: 0px; BORDER-BOTTOM: 0px; FONT-FAMILY: "Verdana"; BACKGROUND-COLOR: white
}
..AOLWebSuiteCompose P {
PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
IMG.managedImg {
WIDTH: 0px; HEIGHT: 0px
}
IMG.placeholder {
BORDER-RIGHT: #dadad6 1px solid; BORDER-TOP: #dadad6 1px solid; BACKGROUND: #f4f4f4 no-repeat center center; BORDER-LEFT: #dadad6 1px solid; WIDTH: 275px; BORDER-BOTTOM: #dadad6 1px solid; HEIGHT: 206px
}
</STYLE>
<DIV id=AOLMsgPart_3_ab2243cb-01c6-44b2-a5d3-b82d3328cf8c>
<DIV dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial
color=#0000ff><SPAN class=correction id="">Ramki</SPAN>,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial
color=#0000ff> 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> 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>Good Luck and Best Regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=290294021-28032007><FONT face=Arial
color=#0000ff>John Scheinoha</FONT> </SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma><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>
<HTML><BODY>*Please note my E-Mail Address has changed. Please<br>
update your contact list*<br>
<br><br><br>
<P><hr size=1></P><br>
<P><STRONG><br>
Anadarko Confidentiality Notice: <br>
This electronic transmission and any attached documents or other<br>
writings are intended only for the person or entity to which it is<br>
addressed and may contain information that is privileged,<br>
confidential or otherwise protected from disclosure. If you have<br>
received this communication in error, please immediately notify<br>
sender by return e-mail and destroy the communication. Any<br>
disclosure, copying, distribution or the taking of any action<br>
concerning the contents of this communication or any attachments by<br>
anyone other than the named recipient is strictly prohibited.<br>
</STRONG></P></BODY></HTML>