04-08-2015 10:40 PM
Hi Experts,
I’m using CL_EX_ME_PROCESS_PO_CUST to do some validations and set EKPO- ELIKZ with X if true.
This is working fine from ME21N but it doesn’t seems to be working from ME59N, I see in the debugger that the value is set with an X even at the end of the POST Method.
My scenario in ME21N and ME59N is to set EKPO- ELIKZ when I converting from a Purchase Requisition.
So my question is:
What can be happening that its working ok in ME21N and not in ME59N?
Im not very familiar with ME59N, do I have to set any of the ME59N selection screen parameter beside Purchase Requisition #?
Thanks in advance!
04-09-2015 8:07 AM
I hope you are not modifying the demo class provided with the BAdI,n but you actually create a new implementation with SE19?
Do you use same order type in ME59N and ME21N, there can be a difference in their Customizing (status fields) ?
Regards,
Raymond
04-09-2015 8:07 AM
I hope you are not modifying the demo class provided with the BAdI,n but you actually create a new implementation with SE19?
Do you use same order type in ME59N and ME21N, there can be a difference in their Customizing (status fields) ?
Regards,
Raymond
04-09-2015 2:12 PM
Hi Raymond,
Yes, of course I create an implementation of the Badi.
Where can I see the Customizing status fields?
Thanks.
Nico.-
04-09-2015 3:59 PM
SPRO : Purchasing, Purchase Order, Define Document Types and Define Screen Layout at Document Level.
Regards,
Raymond
04-09-2015 4:52 PM
ME21 ME21N is there in those SPRO path you send, but I couldn't find ME59N.
I set a break point at process_input_filter and field ekpo-elikz got a dot (.) so I guess its editable.
ME21N and ME59N both creates a ZNB PO, but through ME59N it does not set Delivery Complete with an X as its doing inME21N
Any hint?
Thanks a lot!
Nico.-
04-10-2015 7:20 AM
What is your version, I found an old note 632096 - ME59N Change of shipping data via BAdI ME_PROCESS_PO_CUST , where modifications by the BAdI were dropped, but it's an old note?
NB: in recent version the BAdi is even used to correct the difference between ME21n and ME59n, see 1758500 - T-code ME59N - PO item numbers are not sequential for an example.
Regards,
Raymond
04-09-2015 10:14 AM
Hello Nicolas,
Did you try by placing the watchpoint on the field EKPO- ELIKZ.
There might be another user exit or some enhancement which is making the EKPO- ELIKZ as blank after you set X in your BADI implementation.
Regards,
TP
04-10-2021 11:12 AM