Error While Uploading Material Master Through Bdc Call Transaction

Hi Sap Gurus,
I am doing Bdc call Transaction for Material Master Uploading.
But After Entering data for 4-5 screen i got a error_
Field Mara-iprkz doesn,t exit in the screen saplmgmm 4000
Field Mara-prctr doesn,t exit in the screen saplmgmm 4000
Field Mbew-stprs doesn,t exit in the screen saplmgmm 4000
Field Marc-mtvfe doesn,t exit in the screen saplmgmm 4000
Enter Valuation class.
This is my Programme....................................
<removed by moderator>
Thanks in advance.
Arindam
Moderator message: please post only relevant code parts, your post must be less than 5000 characters to preserve formatting.
Edited by: Thomas Zloch on Apr 16, 2011 9:29 PM

Sorry for my obvious answer, but you should ask a more precise question.
Your errors are that you try to enter fields but they don't exist, so it sounds logic.
And the error "Enter Valuation class." means that the field is mandatory. So you must enter it.
Re-record the transaction using SHDB (eventually play with the http://wiki.sdn.sap.com/wiki/display/ABAP/Recordduringplay), run it in A display mode, and correct your program.
Sandra
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'MVKE-SKTOF'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'MARC-PRCTR'
                              wa_mara-prctr."'MUMBAI'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'MARA-IPRKZ'
                              'D'.

Similar Messages

  • Error while uploading Customer creation ( XD01) using Call Transaction

    Hi Experts,
    While recording XD01,  i checked on Use Central Address Management checkBox,
    i got two pop-ups,
       1. Postal code 500018 in country IN does not exist.
       2. City Hyderabad in country IN does not exist.
    i accepts those pop-ups by Clicking on Yes Button.
    while executing in All Screen Mode it executes without errors,
    But in No Screen mode i am getting error in address screen and in the messtab i got  MSGV1= 500018 (postal code) and                                                                               
    FLDNAME =   SZA1_D0100-TITLE_MEDI.
    Is there any other way to get the Title in title list box without using Use Central Address Management Check Box,
    without checking Use Central Address Management Check Box, i am not getting the title in the title list box while displaying in XD02.
    Please help me out to solve the problem.
    Thanks & Regards,
    Karthick.

    Hi,
    I solved this problem.
    By changing the configuration Data through the path spro->SAP NetWeaver-> General Settings->set Contries->Set Contry-Specific Checks and click on the Contry code, a screen will display the default checks.  Previously it is configured to a particular location with respect to Pincode , i updated as per my requirement. So the pop-ups are not coming and it workes fine in all Modes(A/N/E) of BDC.
    The Title problem is also solved by revised recording of XD01.
    Then my problem is solved.
    Thanks & Regards,
    Karthick.

  • Light goes off or System crash During Upload data through BDC Call Transaction ..

    Hi Experts ,
                    How do I know how many records had been updated in database while uploading the  flat file through BDC call transaction  ,the system suddenly  crash or light  goes off ..............
    Thanks and Regards .
    Om prakash 

    Hi Prakash,
    i have already told toy to use bapi to get all the error and success messages, through which you don't need to do all the above stuffs, the first method you have shown is based on algorithm , which might not be correct each time, and the second method is handy.
    You can add these code lines in your BDC which will give you all error and success messages
    DATA : BEGIN OF options.
             INCLUDE STRUCTURE ctu_params.
    DATA : END OF options.
    DATA: i_messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE,
           l_message LIKE bapiret2-message.
    DATA: p_mode TYPE c.
    DATA  BEGIN OF it_error OCCURS 1.
    DATA : text(100)  TYPE c.
    DATA  END   OF it_error.
    DATA  BEGIN OF it_success OCCURS 1.
    DATA:  text(100) TYPE c.
    DATA  END   OF it_success.
    START-OF-SELECTION.
      PERFORM upload_data.
    *   Report for success
       PERFORM  success_text.
    *   Report for Error
       PERFORM  error_text.
    END-OF-SELECTION.
    CALL TRANSACTION 'your transaction code' USING bdcdata
                                 OPTIONS FROM options
                                 MESSAGES INTO i_messtab.
         IF SY-SUBRC NE 0.
           CALL FUNCTION 'BAPI_MESSAGE_GETDETAIL'
             EXPORTING
               id         = sy-msgid
               number     = sy-msgno
               language   = sy-langu
               textformat = 'ASC'
               message_v1 = sy-msgv1
               message_v2 = sy-msgv2
               message_v3 = sy-msgv3
               message_v4 = sy-msgv4
             IMPORTING
               message    = l_message.
           CONCATENATE l_message '-' wa_input-newko wa_input-wrbtr wa_input-budat INTO it_error-text
           SEPARATED BY ' '.
           APPEND it_error.
         ELSE.
           CONCATENATE 'DATA UPLOADED SUCCESSFULLY :' wa_input-newko  wa_input-wrbtr wa_input-budat
           INTO it_success-text SEPARATED BY ' '.
           APPEND it_success.
         ENDIF.
         REFRESH bdcdata.
         CLEAR: wa_input,l_message.
    ENDLOOP.
    ***ENDLOOP.
    endform.
                        " UPLOAD_DATA
    FORM success_text .
       LOOP AT it_success.
         AT FIRST.
           WRITE :/10  'Following records successfully uploaded'.
           ULINE.
         ENDAT.
         WRITE :/10  it_success-text.
       ENDLOOP.
    ENDFORM.
    FORM error_text .
       LOOP AT it_error.
         AT FIRST.
           WRITE :/10  'Following records  are not uploaded'.
           ULINE.
         ENDAT.
         WRITE :/10  it_error-text.
       ENDLOOP.
    ENDFORM.

  • Error While Uploading GL Master Data in LSMW

    Hello Experts,
    I am running into error while uploading GL master data in LSMW, I created recording through FS00, then I mapped the fields, it all went good till 13th step, but last step got stuck(Run Batch Input Session), when I am running batch input session, system is showing this message "Function Code cannot be selected"
    Your help would be highly appreciated.
    Regards
    Muhammad Yousuf Ali
    SAP FI Consultant

    Hi,
    first can you pls check your Hierarchy mode setting in FS00 -  before executing Batch input session -
    Open FS00 - go to settings - and Do not display navigation tree select radio button and save it
    then Now Run fresh LSMW - your issue will resolve
    Mahesh

  • Error while uploading HR master data from inQuality server

    Hi, Expert. While uploading of MAster data from Developement to Quality by BDC. When program starts for Tcode PA40, selecting Hiring Action, it is goining to the Action Screen. Here while taking the position from HR template, it gives error as Position is not in Table T428B. Payroll area on the date (Date of original hiring, of the person) it is taking DM as defalt in place of our created Area and terminating. When i am trying entering the data manually, it is giving same error for Position. I am not able to upload the data. Kindly help me by suggesting me the correct sequence and steps for uploading the data. Correct answer will be provided with STARSSSSSS **. Regds Punit.

    Have all your configurations been transported to Quality?
    Have you created the positions before initiating BDC for Hiring?
    Check Feature ABKRS in Quality. Is this same as in Development?
    Is your BDC running OK in Development?
    Regards,

  • Getting error while uploading gl master data using LSMW batch input data

    Hi Experts,
    I am getting error while uploading the GL master data through lsmw using batch input recording.
    After completion of all steps at the time of running batch input session error i am getting is "maintain EN language discription"
    and Pls tell me is it possible to upload transactional data using lsmw? if yes pls explaing briefly.

    Hello,
    Kindly post in the FI forum to get a better response.
    Regarding the issue you might check whether the correct column is being picked up where you have maintained the description.
    Kind Regards // Shaubhik

  • Runtime error while creating material master data

    hello sir,
    i am facing one prolem while creating MATERIAL MASTER DATA.
    AFTER GIVING ALL REQUIRED INFORMATION WHEN I AM GOING TO SAVE THE DOCUMENT ITS SHOWING ABAP RUNTIME ERROR.
    MESSAGE TYPE: - MDS_KEYMAP.
    MESSAGE CLASS: 001.
    PLEASE TELL ME WHAT TO DO?
    REGARDS..

    SIR THANK YOU FOR YOUR REPLY.
    I ALREADY DONE THAT DUMP ANALYSIS.
    SO PLEASE KINDLY GIVE ME IN DETAILS ABOUT THAT SOLUTION...

  • Error during BAPI while uploading Material data through MM01

    Hi all,
    i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
    but in the debugger all the value is being stored.
    REPORT  ZFINISHED_MAT.
    Data: Begin of legacy_data occurs 0,
         MATNR LIKE MARA-MATNR,
         MBRSH LIKE MARA-MBRSH,            "Industry Sector
         MTART LIKE MARA-MTART,            "Matl Type
         WERKS LIKE MARD-WERKS,            "Plant
         LGORT LIKE MARD-LGORT,            "Storage location
         VKORG LIKE MVKE-VKORG,
         VTWEG LIKE MVKE-VTWEG,
         MAKTX LIKE MAKT-MAKTX,             "Matl Desc.
         MEINS LIKE MARA-MEINS,             "Base UOM
         MATKL LIKE MARA-MATKL,             "Matl.Grp
    *     BISMT LIKE MARA-BISMT,
         SPART LIKE MARA-SPART,             "Division
    *     BRGEW LIKE MARA-BRGEW,             "Gross weight
         GROES LIKE MARA-GROES,
         FERTH LIKE MARA-FERTH,
         ZEINR LIKE MARA-ZEINR,
         TAXKM1 LIKE MLAN-TAXM1,
         TAXKM2 LIKE MLAN-TAXM2,
         TAXKM3 LIKE MLAN-TAXM3,
         TAXKM4 LIKE MLAN-TAXM4,
         KTGRM LIKE MVKE-KTGRM,
    *     GEWEI LIKE MARA-GEWEI,             "Weight unit
    *     NTGEW LIKE MARA-NTGEW,             "Net weight
    *     KLART LIKE RMCLF-KLART,
         MTVFP LIKE MARC-MTVFP,             "Availibility Check
    *     XGCHP LIKE MARA-XGCHP,
         XCHPF LIKE MARA-XCHPF,             "Batch Management
         TRAGR LIKE MARA-TRAGR,
         LADGR TYPE MARC-LADGR,
         VPRSV LIKE MBEW-VPRSV,            "Price Control
         VERPR LIKE MBEW-VERPR,
    *     SPRAS LIKE MAKT-SPRAS,
      END OF LEGACY_DATA.
    DATA: BEGIN OF IT_MAKT OCCURS 0.
    INCLUDE STRUCTURE BAPI_MAKT.
    DATA: END OF IT_MAKT.
    *--- BAPI structures
    DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
    BAPI_MAKT LIKE BAPI_MAKT, " Material Description
    BAPI_MARA1 LIKE BAPI_MARA, " Client Data
    BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
    BAPI_MARD1 LIKE BAPI_MARD,
    BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
    BAPI_MARC1 LIKE BAPI_MARC, " Plant View
    BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
    BAPI_MVKE1 LIKE BAPI_MVKE,
    BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
    BAPI_MLAN1 LIKE BAPI_MLAN,
    BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
    BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
    BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
    BAPI_RETURN LIKE BAPIRET2. " Return Parameter
    *              $PARAMETERS DECLARATION$
    SELECTION-SCREEN BEGIN OF BLOCK B11
                              WITH FRAME TITLE TEXT-001.
    PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN ULINE.
    SELECTION-SCREEN END OF BLOCK B11 .
    *              $DATA DECLARATION$
    *DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
    DATA : IT_EXCEL TYPE STANDARD TABLE OF  ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
            IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
    DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
    DATA : L_MSTRING(480).
    DATA :L_SUBRC LIKE SY-SUBRC.
    DATA: V_FILE TYPE STRING.
    *              $AT-SELECTON SCREEN DECLARATION$
    AT SELECTION-SCREEN ON P_FILE.
      IF P_FILE IS INITIAL.
        MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
      ENDIF.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
      CALL FUNCTION 'F4_FILENAME'
       EXPORTING
         PROGRAM_NAME        = SYST-CPROG
    *   DYNPRO_NUMBER       = SYST-DYNNR
         FIELD_NAME          = 'P_FILE'
       IMPORTING
         FILE_NAME           = P_FILE
    start-of-selection.
    perform data_fetch_to_xls.
    perform insertion.
    *&      Form  data_fetch_to_xls
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM data_fetch_to_xls .
    CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
        EXPORTING
          FILENAME                = P_FILE
          I_BEGIN_COL             = 1
          I_BEGIN_ROW             = 2
          I_END_COL               = 25
          I_END_ROW               = 2
        TABLES
          INTERN                  = IT_EXCEL
        EXCEPTIONS
          INCONSISTENT_PARAMETERS = 1
          UPLOAD_OLE              = 2
          OTHERS                  = 3.
      IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
               /'RETURN CODE : ', SY-SUBRC.
      ELSE.
    *************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
        IF NOT IT_EXCEL[] IS INITIAL.
          CLEAR LEGACY_DATA.
          REFRESH LEGACY_DATA[].
          LOOP AT IT_EXCEL.
            IT_EXCEL_DUMMY = IT_EXCEL.
            AT NEW COL.
              CASE IT_EXCEL_DUMMY-COL.
                WHEN 1.
                  LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
                WHEN 2.
                  LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
                WHEN 3.
                  LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
                WHEN 4.
                  LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
                WHEN 5.
                  LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
                WHEN 6.
                  LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
                 WHEN 7.
                  LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
                WHEN 8.
                  LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
                WHEN 9.
                  LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
                WHEN 10.
                  LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
                WHEN 11.
                  LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
                WHEN 12.
                  LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
                WHEN 13.
                  LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
                WHEN 14.
                  LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
                 WHEN 15.
                  LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
                 WHEN 16.
                  LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
                 WHEN 17.
                  LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
                 WHEN 18.
                  LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
                 WHEN 19.
                  LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
                WHEN 20.
                  LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
                 WHEN 21.
                  LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
                WHEN 22.
                  LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
                WHEN 23.
                  LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
                WHEN 24.
                  LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
                WHEN 25.
                  LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
                  APPEND LEGACY_DATA.
                  CLEAR LEGACY_DATA.
              ENDCASE.
            ENDAT.
            AT END OF ROW.
            ENDAT.
          ENDLOOP.
        ENDIF.
      ENDIF.
    ENDFORM.                    " data_fetch_to_xls
    *&      Form  insertion
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM insertion .
    LOOP AT legacy_data.
    * Header
    BAPI_HEAD-MATERIAL = legacy_data-MATNR.
    BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
    BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
    BAPI_HEAD-BASIC_VIEW = 'X'.
    BAPI_HEAD-SALES_VIEW = 'X'.
    BAPI_HEAD-STORAGE_VIEW = 'X'.
    *BAPI_HEAD-PURCHASE_VIEW = 'X'.
    BAPI_HEAD-ACCOUNT_VIEW = 'X'.
    * Material Description
    REFRESH IT_MAKT.
    *IT_MAKT-LANGU = legacy_data-SPRAS.
    IT_MAKT-MATL_DESC = legacy_data-MAKTX.
    APPEND IT_MAKT.
    BAPI_MARD1-PLANT = legacy_data-WERKS.
    BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
    BAPI_MARDX1-PLANT = legacy_data-WERKS.
    BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
    ** Client Data - Basic
    BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
    *bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
    BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
    BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
    BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
    BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
    BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
    *BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
    BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
    BAPI_MARA1-DIVISION = legacy_data-SPART.
    BAPI_MARAX-MATL_GROUP = 'X'.
    *BAPI_MARAX-OLD_MAT_NO = 'X'.
    BAPI_MARAX-BASE_UOM = 'X'.
    BAPI_MARAX-PROD_MEMO = 'X'.
    BAPI_MARAX-SIZE_DIM = 'X'.
    BAPI_MARAX-DOCUMENT = 'X'.
    BAPI_MARAX-BATCH_MGMT = 'X'.
    *BAPI_MARAX-UNIT_OF_WT = 'X'.
    BAPI_MARAX-TRANS_GRP = 'X'.
    BAPI_MARAX-DIVISION = 'X'.
    *SALES
    BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
    BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
    *BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
    BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
    BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
    BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
    *BAPI_MVKEX1-DELYG_PLNT = 'X'.
    BAPI_MVKEX1-ACCT_ASSGT = 'X'.
    ** Plant - Purchasing
    BAPI_MARC1-PLANT = legacy_data-WERKS.
    BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
    BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
    *BAPI_MARC1-MRP_GROUP =  legacy_data-disgr.
    BAPI_MARCX-PLANT = legacy_data-WERKS.
    BAPI_MARCX-LOADINGGRP = 'X'.
    BAPI_MARCX-AVAILCHECK = 'X'.
    *BAPI_MARCX-MRP_GROUP =  'X'.
    * Accounting
    BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
    BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
    BAPI_MBEW1-STD_PRICE =  legacy_data-VERPR.
    *BAPI_MBEW1-VAL_CLASS =  legacy_data-BKLAS.
    *BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
    *BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
    BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
    BAPI_MBEWX-PRICE_CTRL = 'X'.
    BAPI_MBEWX-STD_PRICE =  'X'.
    *BAPI_MBEWX-VAL_CLASS =  'X'.
    * TAX JURISDICTION CODE
    BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
    BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
    BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
    BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
    BAPI_MLAN1-TAXCLASS_1 = 'X'.
    BAPI_MLAN1-TAXCLASS_2 = 'X'.
    BAPI_MLAN1-TAXCLASS_3 = 'X'.
    BAPI_MLAN1-TAXCLASS_4 = 'X'.
    *--- BAPI to create material
    call function 'BAPI_MATERIAL_SAVEDATA'
    exporting
    HEADDATA = BAPI_HEAD
    CLIENTDATA = BAPI_MARA1
    CLIENTDATAX = BAPI_MARAX
    *PLANTDATA = BAPI_MARC1
    *PLANTDATAX = BAPI_MARCX
    * FORECASTPARAMETERS =
    * FORECASTPARAMETERSX =
    * PLANNINGDATA =
    * PLANNINGDATAX =
    * STORAGELOCATIONDATA =
    * STORAGELOCATIONDATAX =
    VALUATIONDATA = BAPI_MBEW1
    VALUATIONDATAX = BAPI_MBEWX
    * WAREHOUSENUMBERDATA =
    * WAREHOUSENUMBERDATAX =
    * SALESDATA = BAPI_MVKE1
    * SALESDATAX = BAPI_MVKEX
    * STORAGETYPEDATA =
    * STORAGETYPEDATAX =
    IMPORTING
    RETURN = BAPI_RETURN
    TABLES
    MATERIALDESCRIPTION = IT_MAKT
    * UNITSOFMEASURE =
    * UNITSOFMEASUREX =
    * INTERNATIONALARTNOS =
    * MATERIALLONGTEXT =
    * TAXCLASSIFICATIONS =
    * RETURNMESSAGES =
    * PRTDATA =
    * PRTDATAX =
    * EXTENSIONIN =
    * EXTENSIONINX =
    IF BAPI_RETURN-TYPE = 'E'.
    WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
    ELSEIF BAPI_RETURN-TYPE = 'S'.
    WRITE: 'Successfully created material' ,legacy_data-maTNR.
    ENDIF.
    ENDLOOP.
    ENDFORM.                    " insertion
    The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
    suggestion will be vry helpful,
    Kind Regards,
    Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

    Hi Prasenjit,
    Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
    Regards,
    Suruchi

  • Long text problem while uploading Inspection plan through BDC.

    Hi,
    I am facing some problem while uploading the inspection plan. There are few MICs for which we are having long text, while uploading the inspection plan through BDC - some other long text is getting copied into the MIC's long text. After checking I came to know that in function module, read_text - some text which is stored in ABAP memory is getting copied into the inspection plan.
    I am working in SAP release 4.7. I have checked with SAP notes: 97419, but it is also not satisfying.
    Waiting for quick solution.
    Thanks in advance.
    Fahié

    Hi a®s,
    Thanks a lot for your kind reply.
    My requirement is I want to maintain long text for few MICs (which are not having long texts at MIC level) in inspection plan (QP01).
    When I am trying to manually assign the MIC's to inspection plan (QP01), long text is copied whereas I am not clicking the long text icon in (QP01). Long text is not maintained in MIC level, still some long text is copied to this MIC. This was also happening while uploading the inspection plan thro' BDC.
    I believe what you have mentioned about function module SAVE_TEXT cannot be used here since long text is already copied before we pass the long text. Also if we pass some long text, still apart from the long text what we have passed there is some other long text copied (extra long text).
    Waiting for quick solution.
    Thanks in advance.
    Fahié

  • Exchange rate error while Uploading material in MB1C; MovType 561

    Hi Experts,
    I am trying to upload material in MB1C (movement type 561). When I am saving, system is giving following error.
    My company code currency, material master currency is EUR but still following error is occuring.
    "Enter rate EUR /  rate type M for 01.10.2010 in the system settings
    Message no. SG105
    Diagnosis
    For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
    Procedure
    Add the missing entry in the currency conversion table.
    Execute function
    You can then continue to process the commercial transaction."
    Do I need to maintain exchange rate inOB08 for EUR to EUR conversion? Or is there any other setting?
    Regards
    Anand

    Hi,
    No need to maintain conversion between EUR to EUR.
    We'll take one currency as standard for conversions.
    In our case for every currency we have to maintain conversion for USD
    EUR to USD
    USD to EUR
    INR to USD
    USD to INR
    May be you have to maintain like above.
    Rgds
    Murali. N

  • Error while loading material master data

    I am loading delta data for material master and its giving me the following error:
    "Programs not generated for InfoSource 0MATERIAL_ATTR and source system".
    How to resolve this error?
    Need ur help urgently.
    Thanks

    Hi,
    While loading attributes U have to select the transfer structure of the 0MATERIAL_ATTR then activate it..now proceed if it is already replicated in to BW system... other wise first do that..then go ahead....Similar to Text also...
    Regards
    Siddhu

  • Error while sending Material Master IDOC to Auto ID 2.1

    Hello All,
    I am using Auto ID 2.1 with SP1 on NW04.
    Integration server is XI 3.0 with corresponding XI Content for Auto ID.
    The backend is ERP2004.
    I am using the config guide for Auto ID 2.1.
    After completing the configuration, I tried sending the Material Master IDOC to Auto ID.
    IDOC gets created successfully. XI says the message transfer is successfully.
    In the log of Auto ID. I am getting the following error while importing the Material Master product:
    Product ID AUTOIDAII_MAT has an invalid format
    Internal error in /AIN/DM_PROD_COMMIT
    Message no. COM_PRODUCT897
    The description says that it may be a program error.
    Or the program expects some variable to be filled which has not occured.
    Any idea what could be the error. Or where should I try looking for to get more detail info.
    Do some one knows what should be the patch levels for the different components in all three servers for Auto ID 2.1 SP1.
    Thanks for any kind of input.
    Regards,
    Arundeep Singh

    HI Arundeep,
    use the following
    1) XI 3.0 SP level 12
    2) AII 2.1 SP2
    3) check in rfid outbound configuration guide for any customising for product to be done in AII
    regards,
    ashit singh

  • DTW error while uploading UDO master

    Dear All,
                     When am trying to upload a UDO master through DTW, it is giving me an Unknown error 1005! 65171.wat could be the reason for it.
    Regards,
    Shyam sundar.A

    Dear Shyam,
    All 65171 errors are related to data format mismatch. You need to try by only few columns first and add one column at a time to test.
    Thanks,
    Gordon

  • Error while creating material master

    hi,
    I'm getting this error message when I'm creating a material master in a specific plant/sloc. I'm probably guessing its in config. I really need some help here.
    "Tables TCURM and T001W inconsistent; notify your system administrator" .
    could any one  draw some light on this.
    thanks regards,
    chinta

    this is not application server specific problem.
    Suggest you to go to [Logistic/MM forum|SAP ERP - Logistics Materials Management (SAP MM);.
    regards,
    Vincent

  • ERROR -WHILE LOADING MATERIAL MASTER FROM A FLAT FILE

    HI GUYS ,
    I AM TRYING TO CREATE MATERIAL MASTER FROM A FROM FLAT FILE
    IAM GETTIGN AN ERROR MESSAGE
    'YOU HAVE NOT FULLY MAINTAINED THE DESCRIPTIONS'
    REQUIRE HELP ON THIS
    THANKS

    Hello Nishant
    All the inputs that are required to create a material in dialog (MM01) should be mandatory as well if you are going for LSMW or BAPI. Obviously your material requires a description (which will end up in MAKT). If you have this description in your flat file then there are additional (perhaps language-dependent) descriptions required.
    You could try to use BAPI_MATERIAL_SAVEDATA in your test environment to find out the minimum input that is required to create a material in R/3.
    You may also have a look at thread what are the parameters have to pass to bapi material creation?
    Regards
      Uwe

Maybe you are looking for