Determining PO Rel Code to allow Reset on Non-Significant Change

Mark Pyc mark.pyc at gmail.com
Fri Aug 18 06:48:38 EDT 2006


G'day all,

Just posting an answer back to my own question. This really wasn't that
difficult in the end, I just needed some more complex config set up to look
at.

Table EKKO contains:
Release Goup - FRGGR
Release Strategy - FRGSX
Release Status - FRGKE

Table T16FS is also keyed on FRGGR and FRGSX and contains eight Release Code
fields (FRGC1 - FRGC8).

The field EKKO-FRGKE is 8 characters long and will contain an X per release
code. So if the first release code has been effected the field will be
'X       '. If two release codes had been effected (not that we have more
than 1) it would be 'XX     '.

So to determine the release code you read the field from T16FS corresponding
to the number of Xs in EKKO-FRGKE.

Have fun,
Mark



On 8/9/06, Mark Pyc <mark.pyc at gmail.com> wrote:
>
>  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/20060818/f5e43380/attachment.htm


More information about the SAP-WUG mailing list