SAP BLOG Release Strategy reset when change made to delivery schedule

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
1,851
Tepki puanı
7
Puanları
6

Problem​


Release scheduling agreement from tcode ME35L from all release indicator after that whenever we add/change in schedule lines from Me38 then system through a message “Release already effected will be cancelled” at the time of saving the scheduling agreement .

Cause​


When the scheduling agreement is released, the system stores the value at which the PO was released in field EKKO-RLWRT (Total value at time of Release). This is the total net price of each item in the scheduling agreement at the time of the release. So whenever in the future there is a modification of the Schedule agreement and the release strategy allows a change (i.e changeable indicator 4 or 6). The system calculates the net price of each of the items again if there are time dependent conditions. This price is then compared with the value at which the document was earlier released. If the change is more than the tolerance limit the release strategy is reset even though only the delivery lines are changed.Also If you are using userexit EXIT_SAPLEBND_002 for modifying any release characteristic value then release will be reset if there is a change in any characteristic value and system finds a new release strategy valid for these parameters.



Symptom​

  1. Release strategy reset in transaction ME38.
  2. Release strategy canceled when delivery schedule is created or maintained (additional lines added).
  3. You want to update a scheduling agreement (SA) item price condition with t-code MEKL or MEK2. This increases the whole document’s price, hence if the current condition period’s such condition is being changed (on MEKL pay attention onto the validity) then the release strategy of the SA is reset. But if you change the condition’s value for a future date then the price change not goes into the SA automatically with MEKL / MEK2 transaction’s process due to the price not valid today yet. Then the release strategy not reset at that moment. And if you add new schedule lines with ME38 later, on the day from where the new price valid (what we just entered in MEKL previously) then ME38 will be show in change log as release strategy reset transaction.



Solution​


you can check if user exit EXIT_SAPLEBND_002 activated or not & also You can use RM06ENP1 program to update EKKO-RLWRT value .



Steps​

  1. Run Se38 – Program RM06ENP1 –Execute



sap-prog.png




2. Enter Scheduling Agreement Number & execute .(system update the value in EKKO_RLWRT)

sap-prog1-1.png


Conclusion


This blog can be used for SAP ECC .This is a standard feature of SAP but as per your business requirement you can change/modify this feature & achieve your requirement .This will not affect other objects after implementing .



FAQ Release Strategy


Q1 : Why is the release strategy not reset?

Answer : A reset of the release strategy only takes place if the changeability of the release indicator is set to ‘4’ in case of a purchase requisition and ‘4’ or ‘6’ in case of another purchasing document (purchase order, request for quotation, contract, scheduling agreement), the document is still subject to the previous release strategy,the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order, CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release (V_161S-TLFAE), the release strategy is reset when the value of the document is higher than the percentage you have specified and if the document is still subject to the previous release strategy.



Q2 : Why is the release strategy not determined?

Answer : Please check the following points :

You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.

For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

If you use a release user exit to derive the communication structure the following statements must be in the code (see note 371667):

E_CEBAN = I_CEBAN (EXIT_SAPLEBND_001 and EXIT_SAPBELND_004)

E_CEKKO = I_CEKKO (EXIT_SAPLEBND_002)

Okumaya devam et...
 
Üst