Determining PO Rel Code to allow Reset on Non-Significant

[Shai Eyal]

Mark,

Sorry it so long but I've been busy.
Anyhow, the reassign the release strategy via the userexit I mentioned
you do not need to use any of the fields you mentioned. The only thing
you need is to increase the total value field (NETGU or something like
that).

Therefore, within the user exit carry the IF statement which represent
your non-significant change.
If it's true, simply set total value = total value * 2.

BTW, the userexit import parameters are CEKKO fields and also EKPO and
EKET (if I recall correctly).
In case there's additional data you wish to check for you
non-significant change then you transfer if via append structure to
CEKKO.

In addition, please pay attention that I_CEKKO holds the new value while
getting the old value require selection from the database.

For now, simply add IF (non-significant change) statement that if it's
true then total_value = total_value * 2.

What is your non-significant change ?

Good luck,

Regards,
Shai Eyal


Message: 1
Date: Wed, 9 Aug 2006 17:51:54 +0100
From: "Mark Pyc" <mark.pyc at gmail.com>
Subject: Re: Determining PO Rel Code to allow Reset on Non-Significant
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<23f0a78a0608090951x171f30eex38dc2904487ae055 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Thanks for the response Shai!

B certainly sounds interesting but I can't seem to figure it out. This
exit seems more to control which documents are controlled by Release
proceedures or not rather than controlling whether a given document is
released or not. From the doco and examples I can find the idea is that
you include one of the user fields (USRC1 for example) in the
classification defintion of the release strategy and within the exit you
can control this field. If the field is set the PO is subject to
Release, otherwise it isn't which isn't the same as resetting the
release code.

There is also a field CEKKO-PDUMMY which is part of a structure defined
as 'PO release for User Exit', but I'm not sure how this is supposed to
be used. Putting an 'X' in it in the exit didn't do much.

I hope I'm just missing the point and this exit can help. Are you able
to provide me any further clarification.

Many thanks,
Mark


On 8/9/06, Shai Eyal <shaie at team.co.il> wrote:
>
> 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
>