on 10-11-2008 7:10 AM
HELLO ABAP GURUS,
CAN U PLZ SOLVE MY PROBLEM.
I'M TRING TO CONVERT LEGACY DATA TO SAP FOR TCODE MM01
IN MM01 ALL THE FIELDS I'M ABLE TO ENTER BUT DURING ENTERING DATA OF EAN(IN BASIC DATA 1) SYSTEM SHOWING WARNING MESSAGE TO SKIP THIS WARNING WE HAVE TO PRESS ENTER KEY THEN ONLY IT IS PROCESSING.
MAIN PROBLEM IS THAT I WANT TO GIVE ONE EXTRA ENTER AFTER EXECUTING THE FOLLOWING CODE
perform bdc_dynpro using 'SAPLMGMM' '4004' 'X'.
perform bdc_field using 'BDC_OKCODE' '/00'.
perform bdc_field using 'MAKT-MAKTX' matdesc.
perform bdc_field using 'BDC_CURSOR' 'MARA-MTPOS_MARA'.
perform bdc_field using 'MARA-MEINS' wa_valid-MEINS.
perform bdc_field using 'MARA-MATKL' wa_valid-MATKL.
perform bdc_field using 'MARA-BISMT' wa_valid-BISMT.
perform bdc_field using 'MARA-SPART' wa_valid-SPART.
perform bdc_field using 'MARA-PRDHA' wa_valid-PRDHA.
perform bdc_field using 'MARA-MTPOS_MARA' wa_valid-MTPOS_MARA.
perform bdc_field using 'MARA-BRGEW' wa_valid-BRGEW.
perform bdc_field using 'MARA-GEWEI' wa_valid-GEWEI.
perform bdc_field using 'MARA-NTGEW' wa_valid-NTGEW.
perform bdc_field using 'MARA-VOLUM' wa_valid-VOLUM.
perform bdc_field using 'MARA-VOLEH' wa_valid-VOLEH.
*perform bdc_field using 'MARA-EAN11' wa_valid-EAN11.
perform bdc_field using 'MARA-NUMTP' wa_valid-NUMTP.
AFTER THIS CODE I WANT TO GIVE A CODE TO PRESS ENTER CAN U PLZ TELL ME.
*perform bdc_field using 'BDC_OKCODE' '=ENTR'. THIS CODE IS NOT WORKING
IN SHDB I RECORDED PROPERLY BUT WARNING MSGES SHDB NOT RECORDING
THE EAN WILL BE DETERMINED INTERNALLY ON THE BASIS OF THE EAN CATEGORY
AND ASSIGNING EAN/UPC NO INTERNALLY ON THE BASIS OF EAN CATEGORY
thanks in advance,
manoj
Hi
I totally agree with Aditya. For a transaction complicated like MM01, BDC is never recommended..using BAPI's is the best option.
You can try with this BAPI: BAPI_MATERIAL_SAVEDATA
The documentation of the BAPI can be seen in SE37.
Regards,
VIshwa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Manoj,
Your issue is the ideal example of why BDCs must be avoided when uploading master or transaction data, because even if you can bypass this warning message, some future configuration changes in SPRO might result in a new information of warning message being raised in MM01 and that will again fail the BDC.
Hence as a solution, please consider using a BAPI e.g. BAPI_MATERIAL_SAVEREPLICA is perfect for your requirement and there is detailed documentation on this to help you code on it.
Adopting this method will make your transfer program maintenance and bug free.
Hope this helps.
Regards,
Adi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.