Determining PO Rel Code to allow Reset on Non-Significant

Shai Eyal shaie at team.co.il
Wed Aug 9 12:04:56 EDT 2006


Dear Mark,

Basicly, your requirement does not concern the workflow - you wish to
reset the release strategy due to non-significant change. For the best
of my knowledge, there are two options:
A. Make this change significant (reduce the %changeable).
B. Use exit EXIT_SAPLEBND_002 to reset the release strategy due to
non-significant change. Reseting the release strategy will trigger event
ReleaseStepCreated and from there you know to carry on.

OK ?


Regards,
Shai Eyal

------------------------------

Message: 5
Date: Wed, 9 Aug 2006 13:55:08 +0100
From: "Mark Pyc" <mark.pyc at gmail.com>
Subject: Determining PO Rel Code to allow Reset on Non-Significant
	Change
To: WUG <sap-wug at mit.edu>
Message-ID:
	<23f0a78a0608090555y5b28a9ffh2eb0df036597fc2c at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

G'day all,

I appreciate this is more of just a coding issue than WF exactly, but
I'll
try all the same. ECC 5.0

How can you determine the Release Code for a PO when a non-significant
change has occured. To be able to call BUS2012.ResetRelease you must be
able
to pass the Release Code, but I can't see how this can easily be
determined.
I'm in fact amazed at how uneasy it seems.

When dealing with Significant Changes the event passes you the Rel Code
so
there is no need to think about it.

When certain non-Significant changes occur to an already released PO,
the
desire is to reset the release and go through approvals. The problem is
finding the needed Release Code.

Many thanks,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060809/c5f86a5b/a
ttachment.htm

------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


End of SAP-WUG Digest, Vol 21, Issue 38
***************************************




More information about the SAP-WUG mailing list