Skip to Content
0

Avoid recalculation of release strategy in PReq

Dec 14, 2016 at 01:33 PM

71

avatar image
Former Member

Dear experts,

My client would like the system not to recalculate the release strategy (and require new release) when a PReq item is merely deleted. Our current setting for the release indicator is changeability = 4, i.e. new release in case of new release strategy or value change. We are satisfied with this setting and wouldn't like to change it.

However it makes the system to require new release of an ancient requisition that was approved and delivered five years ago! Only because the recalculation of the release strategy gave new value than the one that was determined from the beginning.

We would like the system not to recalculate the release strategy at all in this case. Do you know if there's such option? User exit?

TIA

Raf

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Jürgen L
Jan 01, 2017 at 10:06 AM
0

Only changes trigger a recalculation. What is the reason that you changed a 5 year old requisition?

Share
10 |10000 characters needed characters left characters exceeded
PRASOON AK Jan 02, 2017 at 05:46 AM
0

Hi,

New release will trigger only if the new value is greater / different from the old released value - this is the standard design. If you need a date validation before re-triggering, you may check the feasibility with the enhancement MEREQ001 with exit EXIT_SAPLMEREQ_005.

However, the validation of date before re-triggering release is not logical, since addition of any line item or increase in quantity in old PR will make the PR open again and the user can continue with purchasing activities. This may be widely misused.

Regards,

AKPT

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Feb 15, 2017 at 09:04 AM
0

Thank you guys for the replies. I am sorry I haven't seen them. The mail notifications apparently doesn't work after SCN has been migrated to the new platform.

Jürgen, the "change" was closing of some not fully ordered items - the user has been cleaning old PReq's.

Anyhow, we have solved the issue by introducing a custom characteristic in the release strategy called "finished". The user exit ZXM06U31 populates the field if all PReq items are either deleted or closed or fully ordered. As the result, the PReq becomes not subject to any release strategy as soon as it is "finished". It is however still possible to see which strategy the PReq had before the closing and who approved it in the change log.

I just wondered how others are tackling this problem. I think it is irrational to require new release of a fully ordered PReq if a user closes one of its items. :-)

BR

Raf

Share
10 |10000 characters needed characters left characters exceeded