Knowledge Management

Question:
Hello,
I would like to know whether is it possible to create Release Strategy in both PR and PO. Currently, we have done in PR only.
Any assistance is much appreciated. Thank you
Answer:
Hi,
Yes, definitely it is possible to create both PR and PO in the same Class Type 032.
Cheers,
HT
Answer:
Hello Ha Trans,
That means I may create two different class type of 032 if both PR and PO have different set of characteristics. Doesn't this impact any user-exits?
Thank you
Answer:
Hi,
In fact, there is only one Class Type 032 that you can use for both PR and PO Release Strategy. The difference is that the Release Characterisitics will be validated from different table CEBAN (for PR Release) and CEKKO (for PO Release). In respect of User Exit, the only one that we are implementing is EXIT_SAPMM06E_012 which includes ZXM06U43 where you can set the validation of MRP Controller for PO Release Strategy if this CEKKO-DISPO is used as part of your Release Characteristics. In respect of other standard User Exits that are currently used in PR/PO Release Procedure, I will get back to you in the afternoon after my further checking in the system.
Cheers,
HT
Answer:
Hello Ha Trans,
Sorry for my wrong stmt ... Yeep there's only one class type 032, what I meant is create two class with the same class type 032. So one refer to PR release mainly from table CEBAN and second refer to PO release which refer to CEKKO.
As far for the user exit, any changes needs to be done? Currently, I never touch any user exit yet because I don't know how to use it.
Thanks again.
Answer:
Hi,
In fact, the User Exit will only be applied subject to how you are going to define your Release Characteristics and if the standard SAP feature can meet your specific business requirements (for instance, the MRP controller is included in your PO Release Strategy and since this field is not seen in PO table, it is true that the User Exit should be applied). As the result, let me know your own settings and your specific requirements and I will get back to you if the User Exits shall be implemented.
Cheers,
HT
Answer:
Hello Ha Trans,
Currently I don't see the need to do PO release. But there's a requirement where the procurement wants contract to create up front and only then requestor create PR whenever they request it. I think this is not possible because we recommend the procurement themselves to create the release order(in po screen). So there's a probability where they will ask the requestor to create a release order themselves and submit for approval also.
I hope there's no need to add the po release. Will let you know if we need to do that in future. May I know your email id so I can liase straight with you incase there's a need to do so.
Thank you
Answer:
Hi,
You can contact me directly via ha.tran@holcim.com
.
Cheers,
HT
Answer:
Hi,
Further to my previous posting, during the individual release for purchase requisitions, the user exit is called in Function Module ME_REL_STRATEGIE_EBAN whereas in the overall release, it is called the Function Module ME_REL_GENERAL_STRATEGY_EBAN. (Enhancement M06B0002, EXIT_SAPLEBND_001, ZXM06U13).
During the release for purchase orders, the user exit in Function Module ME_REL_STRATEGIE_EKKO is called.
Cheers,
HT
Answer:
Hi HT,
Sorry to interrupt. I have a question in PO Release Strategy, if you don't mind.
If a PO has been released, and then there is a changes in qty / price which reduce this PO amount.
Is there any way to trigger this PO release strategy again ?
Or I have to use user exit ? If yes, which user exit I have to use ?
Rgds,
SEAT
Answer:
Hi Seat,
If a PO has been released, and then there is a changes in qty / price which reduce this PO amount.
In fact, if any change in the PO which results in value decrease will not activate a check of release strategy to be performed. For further reference, check in OSS Note 365604.
Is there any way to trigger this PO release strategy again ?
Or I have to use user exit ? If yes, which user exit I have to use ?
I would think that you have to use the User Exit to trigger it. The related User Exit in Function Module ME_REL_STRATEGIE_EKKO is called. However, in Release > 3.1X in program MM06EF0S_STRATEGIE_CEKKO (Enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).
Cheers,
HT