02-25-2013 6:28 PM
Hi Friends,
Please help, depending of some conditions, I need clear the field HERKL (Ctry of Origin) and VERDL (Dispatch Ctry) on Migo Transaction, these information come from de Purchase Order automatically. I found these user exit V50EPROP->EXIT_SAPLV50E_004 that works fine for me21n and me22n, but not in Migo, and
V50EPROP->EXIT_SAPLV50E_005, V50EPROP->EXIT_SAPLV50E_006 works fine for Migo but don't allow modify the fields, just checks.
Regards,
02-25-2013 7:35 PM
Hi,
You can modify with field symbols...but not recommended.
Following code may help..
DATA l_dynprog(50) VALUE '(SAPLMEPO)POT[]'. -->here SAPLMEPO is the program and POT is the internal table you have to find the internal table for the fields which you wnat to change you can find call stack in the debug
* Internal table for EKPO
DATA iekpo LIKE bekpo OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS <f1> TYPE ANY .
ASSIGN (l_dynprog) TO <f1>.
if sy-subrc = 0.
iekpo[] = <f1>.
02-25-2013 7:35 PM
Hi,
You can modify with field symbols...but not recommended.
Following code may help..
DATA l_dynprog(50) VALUE '(SAPLMEPO)POT[]'. -->here SAPLMEPO is the program and POT is the internal table you have to find the internal table for the fields which you wnat to change you can find call stack in the debug
* Internal table for EKPO
DATA iekpo LIKE bekpo OCCURS 0 WITH HEADER LINE.
FIELD-SYMBOLS <f1> TYPE ANY .
ASSIGN (l_dynprog) TO <f1>.
if sy-subrc = 0.
iekpo[] = <f1>.
02-26-2013 9:56 PM
Thanks Sukumar,
I couldn't, additionaly I Tried with other options too, like BADIS, and enhacement point, but it's very forced and inestable get to these fields, I'm going to explain the risks for cancel the case.
Regards,