PR Overall Release

[Stevens, Seth]

Ramki,
 
We use user exit EXIT_SAPLEBND_004 to do something similar to this and
it has worked very well.
 
Hope you get this issue resolved.
 
Thanks,
Seth

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Scheinoha, John
Sent: Thursday, March 29, 2007 8:41 AM
To: sap-wug at mit.edu
Subject: RE: PR Overall Release


Ramki,
 
   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.
 
   The use exit is in the following path:  SAPLMEREQ => LMEREQFXX =>
LMREQF08 => LMEREQFDD => ME_REQ_GET_RESPONSIBLE_EBAN => LEBNFU16 =>
EXIT_SAPLEBNF_001.
 
   I hope this helps,
 
Best Regards,
John Scheinoha



________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of workflow99 at aol.com
Sent: Thursday, March 29, 2007 6:55 AM
To: sap-wug at mit.edu
Subject: Re: PR Overall Release


John,
 
I agree with you that the release strategy characteristics need to be
updated. Also there are other situations like multiple Purchase Groups
are used in a PR. A blank 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.
 
Best Regards,
Ramki Maley.
 
 
-----Original Message-----
From: Scheinoha.John at basco.com
To: sap-wug at mit.edu
Sent: Wed, 28 Mar 2007 5:46 PM
Subject: RE: PR Overall Release


Ramki,
 
   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).  
 
   Yes I have experienced this situation one too many times.
 
Good Luck and Best Regards,
John Scheinoha 

________________________________

From: sap-wug-bounces at mit.edu
<javascript:parent.ComposeTo("sap-wug-bounces%40mit.edu", "");>
[mailto:sap-wug-bounces at mit.edu
<javascript:parent.ComposeTo("sap-wug-bounces%40mit.edu", "");> ] On
Behalf Of workflow99 at aol.com
<javascript:parent.ComposeTo("workflow99%40aol.com", "");> 
Sent: Wednesday, March 28, 2007 4:32 PM
To: sap-wug at mit.edu <javascript:parent.ComposeTo("sap-wug%40mit.edu",
"");> 
Subject: PR Overall Release


Hi all,
 
This is not a pure workflow question but on the fringes. Client has PR
overall release with classification. The system cannot determine Release
Strategy in certain 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. 
 
TIA.
 
Best Regards,
Ramki Maley.
________________________________

AOL now offers free email to everyone. Find out more about what's free
from AOL at AOL.com
<http://pr.atwola.com/promoclk/1615326657x4311227241x4298082137/aol?redi
r=http://www.aol.com> .

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu <javascript:parent.ComposeTo("SAP-WUG%40mit.edu", "");> 
http://mailman.mit.edu/mailman/listinfo/sap-wug




-----------------------------------------
*Please note my E-Mail Address has changed.  Please update your
contact list*

Anadarko Confidentiality Notice:  
This electronic transmission and any attached documents or other
writings are intended only for the person or entity to which it is
addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure.  If you have
received this communication in error, please immediately notify
sender by return e-mail and destroy the communication. Any
disclosure, copying, distribution or the taking of any action
concerning the contents of this communication or any attachments by
anyone other than the named recipient is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070329/5c26fdde/attachment.htm