PO Release strategy reset when value of price or quantity changed

[former_member192050]

Hi Experts,

We have a Requirement of resetting the release strategy when ever the value changes both in the price or quantity in any level.

Example :

               price value now 5000 INR and limit is 15000 INR.

               now the value changes to 6000 INR and it should be reset and same as reduces.

               and release group should be triggered as per the limit

For the quantity also same.

Thanks & Regards

Sathish

[former_member196651]

Hi Sathish,

In my case, I was taking the header total value in my consideration. In that what I had done was, when the PO got approved for the first time, I will save the total value to a Z table. After that, when ever there was changes, I will compare the current value with value from Z table to find deviation.

One thing that you can do. After coming to the exit, you can find the total by multiplying the MENGE * NETPR and add these. I think this will solve your issue.

Regards,

Abijith

[former_member196651]

Hi Sathish,

We faced the same issue during an implementation. What we had done was, we made use of the exit M06E0004. This exit will be triggered before the system finalizes the release strategy. From here you will be able to fill an additional flag, which can be used for release strategy selection.

I will explain step by step what we had done. When the release strategy is defined by the MM Funtionals, they will define classification based on some fields like PO Type, PUR. Grp. etc. Here we will be able to place an additional indicator. This is done by appending a field in the communication structure CEKKO. This field can be used by MM Functionals while defining classification for each release strategies.

1) Ask the MM Functional to create a release strategies with field that we are adding to CEKKO. So if A1 is a release strategy that triggers for change from 5000 to 6000 where the additional field is set as ' ', then create a dummy release strategy for this as DA where the additional field is checked for 'X' which needs to be triggered for change for negative deviation from 5000.

2) Add a field into CEEKO through append structure.

3) Now create a project in CMOD for exit M06E0004 for which the import parameter is CEKKO.

4) Here you will have to find a logic to find the deviation that happened to the PO.

5) If the deviation is negative, then set the field that we had added to the CEEKO structure as 'X'.

6) Ask MM Functional to trigger the release strategy, based on the field.

This solution worked for me.

Regards,

Abijith

[former_member192050]

hi Abijith,

in the exit M06E0004,

i worte a code for changing in the price value like below.

but when ever the quantity changes it is not triggering properly as i expected.

E_CEKKO = I_CEKKO .

DATA : wa_bekpo type BEKPO,
        wa_ekpo TYPE ekpo,
        WA_CEKKO TYPE CEKKO,
        w_reset(1) TYPE c .

if sy-tcode eq 'ME22N' OR sy-tcode eq 'ME22' or sy-tcode eq 'ME29N'.
WA_CEKKO = I_CEKKO .
IMPORT WA_CEKKO = WA_CEKKO FROM MEMORY ID 'ZREL_COST'.
IF SY-SUBRC NE 0.
   EXPORT WA_CEKKO = WA_CEKKO TO MEMORY ID 'ZREL_COST'.
ENDIF.
ENDIF.


if ( sy-tcode eq 'ME22N' OR sy-tcode eq 'ME22' OR sy-tcode eq 'ME29N')
   and sy-ucomm eq 'MESAVE' or sy-ucomm eq 'MECHECKDOC'.

*Import/Export the origninal values.

*Check if the limit is passed.
LOOP AT it_bekpo INTO wa_bekpo .

SELECT SINGLE NETWR FROM ekpo INTO wa_ekpo-netwr WHERE ebeln eq wa_bekpo-ebeln and ebelp eq wa_bekpo-ebelp.
   SELECT SINGLE menge FROM ekpo INTO wa_ekpo-menge WHERE ebeln eq wa_bekpo-ebeln and ebelp eq wa_bekpo-ebelp.
IF SY-SUBRC EQ 0.
IF wa_bekpo-netwr < wa_ekpo-netwr or wa_bekpo-netwr > wa_ekpo-netwr.
     w_reset = 'X'.
   endif.
ENDIF.

ENDLOOP.

*IF limit passed - reset the value to high limit beyond tolerance.
IF w_reset = 'X'.
   clear wa_cekko-gnetw.
E_CEKKO-GNETW = WA_CEKKO-GNETW + ( wa_ekpo-menge * wa_ekpo-netwr ).
ENDIF.
*
endif.

[former_member196651]

Hi Sathish,

There is a point to remember. The system will reset the release strategies when the approved value changes from 5000 to 6000. But if this happens in the  reverse way, like approved value changes from 5000 to 4000, then the release strategies will not reset. The system will think in a more logical way that, the users approved for 5000. So there is no need  for resetting the release strategies when it gets reduced. We were facing this problem. I don't know whether this is a standard behavior or not.

Regards,

Abijith

[former_member192050]

Hi Abijith,

Thanks for ur Reply

SAP standard Functionality behaves like that only but our client want above functionality when there is even a small change in the price or quantity it should be reset. 

[Former Member]

Hi Satish,

Please go through the link it might be helpful..

YoursR@J

[Former Member]

Hi Sathish,

SPRO - MM - Purchasing - Purchase Order - Release Procedure - Define Release Strategy - Release Indicator - Changable (set as 6).

Regards,

Manish Jain