PO Release Strategy User-exit

[Becker, Stephan]

If you know it is only called two times, set a global variable or a memory
ID. Before you set it, you check it, so if it is filled, you know you've
been there before.. if it's called more than twice, you'd have to go through
the call stack to be sure (function module SYSTEM_CALLSTACK), that will most
likely be different in both situations and you can make a call depending on
that..
 
-----Mensaje original-----
De: mpevans at micron.com [mailto:mpevans at micron.com]
Enviado el: 09 January 2004 17:58
Para: SAP-WUG at MITVMA.MIT.EDU
Asunto: PO Release Strategy User-exit
 
SAP has provided a user-exit (exit_saplebnd_002, include zxm06u22)
intended to allow customer to reset the Release Strategy on the PO (and
other documents).  Since our upgrade to 4.7 we have not been able to
make it work reliably.  We had it working in 4.5, but SAP has changed
how the PO behaves.
 
Changing the Release Strategy is simple.  All we do is set the value of
the variable 'e_cekko-usrc1' to the new release strategy and SAP does
the rest.  The issue is that SAP calls the user-exit more than once.
They call it at least two times: Once when you open the PO and Again on
saving the PO.  If you set 'e_cekko-usrc1' to the new Release Strategy
in the first pass through the user-exit SAP does not reset the
user-exit.
 
In order to make this user-exit to work you must be able to detect that
you are going thorough it for the last time and only on that execution
set the value of 'e_cekko-usrc1'.  Has anyone dealt with this situation
and come up with a good way to determine that you on the last execution
of the user-exit?
 
Thanks for your help.
Phil