FM WRF_MATERIAL_MAINTAINDATA_RT  /  BAPI_MATERIAL_MAINTAINDATA_RT

Hi,
<subject length restrictions SAP apply> ...Class CL_MATERIAL_MAINTAINDATA_ALE
I try to populate an MVKE extension thru function exit_sapl1001_003 but I do not get there. We have an active MVKE APPEND structure.
Is it posible that I can not populate the extension fields without touching the MVKE fields?
experienced retailer pls. reply.
TIA,
Clemens

Yes, I can not populate the extension fields without touching the MVKE fields - and even worse: Not without poulating base MARA fields.
I remember further that a note came up fixing locking issues...
Regards,
Clemens

Similar Messages

  • BAPI_MATERIAL_MAINTAINDATA_RT ---Article with purchasing view

    Hi,
    I am using BAPI_MATERIAL_MAINTAINDATA_RT  to create Article. I am able to create article using Basic view, Log. DC view etc.
    There is no purchasing view in HEADDATA. Also  fields like Purchase organization, net price etc are not present in any structure.How to create an Article  with purchasing view using this BAPI.
    Please help me in this regard.
    Regards,
    Kiran.

    Hi,
    I had the same problem with this bapi. To activate the purchasing view
    I used WRF_MATERIAL_MAINTAINDATA_RT to create the materials.
    You must put attention how works the mm41 and fill the segments in this
    that you need.
    *& Report  ZTEST_BAPI_EXTENDEDUPDATE
    REPORT  ztest_bapi_extendedupdate.
    DATA: headdata TYPE bapie1mathead.
    DATA: return TYPE STANDARD TABLE OF bapireturn1.
    DATA: lwareturn TYPE bapireturn1.
    DATA: organizational_level TYPE wrfscreenvalues.
    DATA: clientdata  TYPE STANDARD TABLE OF bapie1marart WITH HEADER LINE.
    DATA: clientdatax TYPE STANDARD TABLE OF bapie1marartx WITH HEADER LINE.
    DATA: addnlclientdata TYPE STANDARD TABLE OF bapie1maw1rt  WITH HEADER LINE.
    DATA: addnlclientdatax  TYPE STANDARD TABLE OF bapie1maw1rtx WITH HEADER LINE.
    DATA: unitsofmeasure  TYPE STANDARD TABLE OF bapie1marmrt  WITH HEADER LINE.
    DATA: unitsofmeasurex TYPE STANDARD TABLE OF bapie1marmrtx WITH HEADER LINE.
    DATA: salesdata  TYPE STANDARD TABLE OF bapie1mvkert WITH HEADER LINE.
    DATA: salesdatax  TYPE STANDARD TABLE OF bapie1mvkertx WITH HEADER LINE.
    DATA: inforecordgeneral  TYPE STANDARD TABLE OF bapieina WITH HEADER LINE.
    DATA: inforecordpurchorg  TYPE STANDARD TABLE OF wrfbapieine WITH HEADER LINE.
    headdata-material = '000000000000400121'.
    headdata-matl_type = 'ZMES'.
    headdata-matl_group = '101210501'.
    headdata-matl_cat = '00'.
    headdata-ref_matl = '000000000000448590'.
    headdata-basic_view = 'X'.
    headdata-list_view  = 'X'.
    headdata-sales_view = 'X'.
    headdata-logdc_view = 'X'.
    headdata-pos_view = 'X'.
    organizational_level-material = headdata-material.
    organizational_level-matl_type = headdata-matl_type.
    organizational_level-matl_group = headdata-matl_group.
    organizational_level-matl_cat = headdata-matl_cat.
    organizational_level-ref_matl = headdata-ref_matl.
    organizational_level-purch_org = 'SPC1'.
    organizational_level-vendor = '20400353'.
    organizational_level-info_type = '0'.
    *organizational_level-plant = ''.
    *  Llena clientdata
    clientdata-material  = headdata-material.
    clientdata-base_uom  = 'ST'.
    APPEND clientdata.
    clientdatax-material  = headdata-material.
    clientdatax-base_uom  = 'X'.
    APPEND clientdatax.
    addnlclientdata-material    = headdata-material.
    addnlclientdata-sales_unit  = ''.
    addnlclientdata-li_proc_st  = 'B1'.
    addnlclientdata-li_proc_dc  = 'B1'.
    addnlclientdata-list_st_fr  = sy-datum.
    addnlclientdata-list_st_to  = '99991231'.
    addnlclientdata-list_dc_fr  = sy-datum.
    addnlclientdata-list_dc_to  = '99991231'.
    addnlclientdata-sell_st_fr  = sy-datum.
    addnlclientdata-sell_st_to  = '99991231'.
    addnlclientdata-sell_dc_fr  = sy-datum.
    addnlclientdata-sell_dc_to  = '99991231'.
    APPEND addnlclientdata.
    addnlclientdatax-material    = headdata-material.
    addnlclientdatax-sales_unit  = 'X'.
    addnlclientdatax-li_proc_st  = 'X'.
    addnlclientdatax-li_proc_dc  = 'X'.
    addnlclientdatax-list_st_fr  = 'X'.
    addnlclientdatax-list_st_to  = 'X'.
    addnlclientdatax-list_dc_fr  = 'X'.
    addnlclientdatax-list_dc_to  = 'X'.
    addnlclientdatax-sell_st_fr  = 'X'.
    addnlclientdatax-sell_st_to  = 'X'.
    addnlclientdatax-sell_dc_fr  = 'X'.
    addnlclientdatax-sell_dc_to  = 'X'.
    APPEND addnlclientdatax.
    unitsofmeasure-material   = headdata-material.
    unitsofmeasure-alt_unit   = 'ST'.
    unitsofmeasure-ean_upc    = '7702111342224'.
    APPEND unitsofmeasure.
    unitsofmeasurex-material   = headdata-material.
    unitsofmeasurex-alt_unit   = 'X'.
    unitsofmeasurex-ean_upc    = 'X'.
    APPEND unitsofmeasurex.
    "inforecordgeneral-info_rec ='5300002556'.
    inforecordgeneral-material = headdata-material.
    inforecordgeneral-mat_grp = headdata-matl_group.
    inforecordgeneral-vendor = organizational_level-vendor.
    inforecordgeneral-po_unit = 'ST'.
    *inforecordgeneral-base_uom = clientdata-base_uom.
    APPEND inforecordgeneral.
    inforecordpurchorg-material = headdata-material.
    inforecordpurchorg-vendor = organizational_level-vendor.
    "inforecordpurchorg-info_rec = '5300002556'.
    inforecordpurchorg-purch_org = organizational_level-purch_org.
    inforecordpurchorg-info_type = '0'.
    inforecordpurchorg-pur_group = 'GC1'.
    inforecordpurchorg-currency = 'MXN'.
    APPEND inforecordpurchorg.
    BREAK-POINT.
    CALL FUNCTION 'WRF_MATERIAL_MAINTAINDATA_RT'
      EXPORTING
        headdata             = headdata
        organizational_level = organizational_level
        badi_callmode        = '99'
      TABLES
        return               = return[]
        clientdata           = clientdata[]
        clientdatax          = clientdatax[]
        addnlclientdata      = addnlclientdata[]
        addnlclientdatax     = addnlclientdatax[]
        unitsofmeasure       = unitsofmeasure[]
        unitsofmeasurex      = unitsofmeasurex[]
    *    plantdata             = plantdata[]
    *    plantdatax            = plantdatax[]
    *    salesdata             = salesdata[]
    *    salesdatax            = salesdatax[]
        inforecord_general    = inforecordgeneral
        inforecord_purchorg   = inforecordpurchorg
    BREAK-POINT.
    READ TABLE return INTO lwareturn WITH KEY type = 'E'.
    IF sy-subrc NE 0.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
    ENDIF.

  • IS-Retail: BAPI_MATERIAL_MAINTAINDATA_RT

    Hello guys,
    still using BAPI_MATERIAL_MAINTAINDATA_RT.
    If I create a new article, the FM does not load all field values from the reference material (that should be used by default - Transaction WG24). Some fields that are not loaded are:
    - MARA-RAUBE
    - MARA-IPRKZ
    - MARA-SPART
    - MARA-MTPOS_MARA
    ecc..
    The fields in the structures like CLIENTDATAX are alle empty.
    Does anyone know why not all attributes of the reference material are used for the creation of a new material?
    Thank you,
    Manuel

    Hi Manuel,
    the reference handling for such fields is not easy.
    Please look at transaction OMSR in details for this field.
    Here at least the flag KZCPY must be enabled to activate teh copy function from
    a reference article.
    Further this field MUSt be visible and ready fro input.
    and finnally, go to SE80 inf unction group MGWL.
    Here for the fields the logical subroutines
    Referenz_before
    referenz_***
    ref_***_after
    will be called
    If you look at referenz_before, you can see that
    wmara-spart = t023-spart.  will be referenced by mechandise category and not by ref. article. So this is hard coded.
    If this will not help, please open an CSN message with an example. Our support guys will help you within some seconds.
    Regards
    Björn

  • How to use BAPI_MATERIAL_MAINTAINDATA_RT function module in SAP Reatil?

    Hi,
    I am facing aproblem with BAPI_MATERIAL_MAINTAINDATA_RT function module when i send Article Master data from one SAP Server where all Article Master Data is maintained to another SAP Server where all Transaction Data is maintained.
    how can i use the above Function Module to create or change Articles in Remote Server ( Transactional Data Server) by specifying Destination when calling Function Module so that it can create or change in Remote Server i.e what are the neccessary parameters passed to this function modules.

    thanks

  • Create new article:  BAPI_MATERIAL_MAINTAINDATA_RT

    Hi all,
    When i try to create a new article by using BAPI_MATERIAL_MAINTAINDATA_RT i am getting the follow success message M3801 ("Material & changed") but article is not created. After sending the BAPI_MATERIAL_MAINTAINDATA_RT and returning without an error I call a BAPI_TRANSACTION_COMMIT. How can I resolve this? Thanks in advance.
    Best Regards
    Gabriel.

    Hi,
    Thanks in advance. If i create an article using BAPI_MATERIAL_SAVEDATA then there is not using transaction MM43...
    Best Regards
    Gabriel

  • BAPI_MATERIAL_MAINTAINDATA_RT update gross weight for generic article

    Hi, I want to update the gross weight (MARM-BRGEW) for a generic article and it's variants. Sometimes, the new gross weight is not propagate to all the article related variants when I'm using BAPI BAPI_MATERIAL_MAINTAINDATA_RT ??
    In the structure headdata, I just pass the article number and flag the basic_view. I used 2 internal table for the unit of measures (bapie1marmrt, bapie1marmrtx).
    Example of my source code:
      st_headdata-material   = st_marm-matnr.
      st_headdata-matl_cat   = st_marm-attyp. (01 for generic)
      st_headdata-ref_matl   = st_marm-matnr.
      st_headdata-basic_view = 'X'.
      st_bapimarm-material   = st_marm-matnr.
      st_bapimarm-alt_unit   = st_marm-meinh.
      st_bapimarm-numerator  = st_marm-umrez.
      st_bapimarm-denominatr = st_marm-umren.
      st_bapimarm-gross_wt   = pa_brgew.
      st_bapimarm-unit_of_wt = st_marm-gewei.
      st_bapimarmx-material   = st_marm-matnr.
      st_bapimarmx-alt_unit   = st_marm-meinh.
      st_bapimarmx-numerator  = 'X'.
      st_bapimarmx-denominatr = 'X'.
      st_bapimarmx-gross_wt   = 'X'.
      st_bapimarmx-unit_of_wt = 'X'.
      APPEND: st_bapimarm   TO tp_bapimarm,
              st_bapimarmx  TO tp_bapimarmx.
      CALL FUNCTION 'BAPI_MATERIAL_MAINTAINDATA_RT'
        EXPORTING
          headdata        = st_headdata
        IMPORTING
          return          = st_return
        TABLES
          unitsofmeasure  = tp_bapimarm
          unitsofmeasurex = tp_bapimarmx.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    Let's say my article has 3 unit of mesasure which are EA, PAK, CAR. The base unit of measure of the articles (generic + variants) are EA.
    MARM example BEFORE calling the bapi
    MATNR           MEINH   UMREZ   UMREN  BRGEW
    A011125             KAR     48     1      33
    A011125A10090     KAR     48     1      33
    A011125A10091     KAR     48     1      33
    A011125A10092     KAR     48     1      33
    A011125A10093     KAR     48     1      33
    A011125B10590     KAR     48     1      33
    A011125B10591     KAR     48     1      33
    A011125B10592     KAR     48     1      33
    A011125B10593     KAR     48     1      33
    A011125W10090     KAR     48     1      33
    A011125W10091     KAR     48     1      33
    A011125W10092     KAR     48     1      33
    A011125W10093     KAR     48     1      33
    MARM after calling the BAPI with a new BRGEW of 34
    MATNR           MEINH   UMREZ   UMREN  BRGEW
    A011125             KAR     48     1      34
    A011125A10090     KAR     48     1      34
    A011125A10091     KAR     48     1      34
    A011125A10092     KAR     48     1      34
    A011125A10093     KAR     48     1      33
    A011125B10590     KAR     48     1      34
    A011125B10591     KAR     48     1      33
    A011125B10592     KAR     48     1      33
    A011125B10593     KAR     48     1      34
    A011125W10090     KAR     48     1      34
    A011125W10091     KAR     48     1      33
    A011125W10092     KAR     48     1      34
    A011125W10093     KAR     48     1      34
    I don't think that a locking problem....

    Please open a customer message with the detail data, so I will have a look at your system.
    But I remember that there should be a note for that
    Regards
    B

  • BAPI_MATERIAL_MAINTAINDATA_RT for MARA 'Z' fields

    Hi ,
    I need to populate 'ZZ' fields which are appended to 'MARA' table using the BAPI function 'BAPI_MATERIAL_MAINTAINDATA_RT'. I see there are two parameters for custom fields. They are 'clientext' and 'clientextx'. I need to populate 40 custom fields which are appended to the MARA table. Say for example if I want to populate two custom fields. One is 'ZCOLOR' the value of which is black , the second one is 'ZFABRIC' , the value of which is 'COTTON'. If I want to populate this info using  'clientext' and 'clientextx' , how to do it. Please let me know if you guys have sample code.
    Thanks
    JC

    Hello Gurus,
    I recently used the Function Module EXIT_SAPL1001_003 mentioned above. And I found that in Unicode system there might be offset issues when assigning the value of a structure directly to another one if either of them had non-character like components (refer to this ABAP Keyword Documentation).
    So I changed the SAP sample code for this function module a little.
    * Sample code
    *   INCLUDE LXMGVF07                                                   *
    * Example2: Customer-specific data contains also numerical data types  *
    * Customer structure ZMARC has the following definition:               *
    *   Field name  Data type  Length                                      *
    *   ZZCUS1      CHAR       10                                          *
    *  ZZCUS2      DEC        3     -> numerical!!!!                      *
    *   ZZCUS3      CHAR       5                                           *
    DATA: error_occured LIKE sy-datar.
    DATA: BEGIN OF h_clientext_c,      "Customer data in CHAR format
             function  LIKE bapie1marcextrt-function,  "Key field
             material  LIKE bapie1marcextrt-material,  "Key field
             zzsccj1        LIKE zsmm_bcxx-zzsccj1,
             zzpzwh         LIKE zsmm_bcxx-zzpzwh,
             zzjx           LIKE zsmm_bcxx-zzjx,
             zztssp         LIKE zsmm_bcxx-zztssp,
             zzybsp         LIKE zsmm_bcxx-zzybsp,
             zzpp           LIKE zsmm_bcxx-zzpp,
             zzsccj2         LIKE zsmm_bcxx-zzsccj2,
             zzzgxj(14)     TYPE c, "CURR 11, DEC 2
             zzzgxj_waers   LIKE zsmm_bcxx-zzzgxj_waers,
             zzzgxj_peinh   LIKE zsmm_bcxx-zzzgxj_peinh,
             zzzgxj_bprme   LIKE zsmm_bcxx-zzzgxj_bprme,
             zzzdxj(14)     TYPE c, "CURR 11, DEC 2
             zzzdxj_waers   LIKE zsmm_bcxx-zzzdxj_waers,
             zzzdxj_peinh   LIKE zsmm_bcxx-zzzdxj_peinh,
             zzzdxj_bprme   LIKE zsmm_bcxx-zzzdxj_bprme,
             zzjmdsj(14)    TYPE c, "CURR 11, DEC 2
             zzjmdsj_waers  LIKE zsmm_bcxx-zzjmdsj_waers,
             zzjmdsj_peinh  LIKE zsmm_bcxx-zzjmdsj_peinh,
             zzjmdsj_bprme  LIKE zsmm_bcxx-zzjmdsj_bprme,
             zzypbx         LIKE zsmm_bcxx-zzypbx,
             zzgg           LIKE zsmm_bcxx-zzgg,
             zzbqdw         LIKE zsmm_bcxx-zzbqdw,
             zztym           LIKE zsmm_bcxx-zztym,
           END   OF h_clientext_c.
    DATA: BEGIN OF h_clientext,      "Customer data in actual format
             function  LIKE bapie1marcextrt-function,  "Key field
             material  LIKE bapie1marcextrt-material.  "Key field
             INCLUDE STRUCTURE zsmm_bcxx.
    DATA: END   OF h_clientext.
    DATA: BEGIN OF h_clientextx,     "Customer update information
             function  LIKE bapie1marcextrtx-function,  "Key field
             material  LIKE bapie1marcextrtx-material,  "Key field
             zzsccj1        TYPE c,
             zzpzwh         TYPE c,
             zzjx           TYPE c,
             zztssp         TYPE c,
             zzybsp         TYPE c,
             zzpp           TYPE c,
             zzsccj2         TYPE c,
             zzzgxj         TYPE c,
             zzzgxj_waers   TYPE c,
             zzzgxj_peinh   TYPE c,
             zzzgxj_bprme   TYPE c,
             zzzdxj         TYPE c,
             zzzdxj_waers   TYPE c,
             zzzdxj_peinh   TYPE c,
             zzzdxj_bprme   TYPE c,
             zzjmdsj        TYPE c,
             zzjmdsj_waers  TYPE c,
             zzjmdsj_peinh  TYPE c,
             zzjmdsj_bprme  TYPE c,
             zzypbx         TYPE c,
             zzgg           TYPE c,
             zzbqdw         TYPE c,
             zztym           TYPE c,
           END   OF h_clientextx.
    CASE parameter_name.
       WHEN c_parnam_clientext.
    * Copy from unstructured BAPI format to structured CHAR format
         h_clientext_c-zzsccj1 = f_clientext-field1+0(40).
         h_clientext_c-zzpzwh = f_clientext-field1+40(25).
         h_clientext_c-zzjx = f_clientext-field1+65(10).
         h_clientext_c-zztssp = f_clientext-field1+75(10).
         h_clientext_c-zzybsp = f_clientext-field1+85(2).
         h_clientext_c-zzpp = f_clientext-field1+87(10).
         h_clientext_c-zzsccj2 = f_clientext-field1+97(10).
         h_clientext_c-zzzgxj = f_clientext-field1+107(14).
         h_clientext_c-zzzgxj_waers = f_clientext-field1+121(5).
         h_clientext_c-zzzgxj_peinh = f_clientext-field1+126(5).
         h_clientext_c-zzzgxj_bprme = f_clientext-field1+131(3).
         h_clientext_c-zzzdxj = f_clientext-field1+134(14).
         h_clientext_c-zzzdxj_waers = f_clientext-field1+148(5).
         h_clientext_c-zzzdxj_peinh = f_clientext-field1+153(5).
         h_clientext_c-zzzdxj_bprme = f_clientext-field1+158(3).
         h_clientext_c-zzjmdsj = f_clientext-field1+161(14).
         h_clientext_c-zzjmdsj_waers = f_clientext-field1+175(5).
         h_clientext_c-zzjmdsj_peinh = f_clientext-field1+180(5).
         h_clientext_c-zzjmdsj_bprme = f_clientext-field1+188(3).
         h_clientext_c-zzypbx = f_clientext-field1+191(1).
         h_clientext_c-zzgg = f_clientext-field1+192(12).
         h_clientext_c-zzbqdw = f_clientext-field1+204(3).
         CONCATENATE f_clientext-field1+207(22)
                     f_clientext-field2+0(18)
                     INTO h_clientext_c-zztym.
    * Copy from structured CHAR format to actual format
         MOVE-CORRESPONDING h_clientext_c TO h_clientext.
         h_clientextx  = f_clientextx.
         IF NOT h_clientextx-zzsccj1 IS INITIAL
         OR NOT f_headdata-all_fields IS INITIAL.
    * Corresponding data field is relevant for update
           IF h_clientext-zzsccj1 IS INITIAL.
             t_res_fields-feldname = 'MARA-ZZSCCJ1'.
             APPEND t_res_fields.
           ENDIF.
         ELSE.
           CLEAR h_clientext-zzsccj1.
         ENDIF.
         f_mara_ueb-zzsccj1 = h_clientext-zzsccj1.
         IF NOT h_clientextx-zzpzwh IS INITIAL
         OR NOT f_headdata-all_fields IS INITIAL.
    * Corresponding data field is relevant for update
           IF h_clientext-zzpzwh IS INITIAL.
             t_res_fields-feldname = 'MARA-ZZPZWH'.
             APPEND t_res_fields.
           ENDIF.
         ELSE.
           CLEAR h_clientext-zzpzwh.
         ENDIF.
         f_mara_ueb-zzpzwh = h_clientext-zzpzwh.
    ENDCASE.
    * Example for raising an exception if an application error occurred
         IF NOT error_occured IS INITIAL.
           MESSAGE e544(mg) WITH parameter_name RAISING application_error.
         ENDIF.
    消息编辑者为：Arwen Liu

  • BAPI_MATERIAL_MAINTAINDATA_RT problem

    Hi experts.
    I am trying to change some material parameters. It's MARC-MINBE and MARC-MABST.
    For this I am using BAPI_MATERIAL_MAINTAINDATA_RT with appropriate parameters.
    Unfortunatelly there is an error message: 537.
    In SLG1 I have some messages:
    - The field MARA-BRAND_ID/BAPIE1MARART-BRAND_ID is defined as a required field; it does not contain an entry
    - The field MARA-BSTAT/BAPIE1MARART-CREATION_STATUS is defined as a required field; it does not contain an entry     
    - The field MARA-FASHGRD/BAPIE1MARART-FASHION_GRADE is defined as a required field; it does not contain an entry     
    I've got 15 of messages like that.
    Code is as follow:
    REPORT ztest.
    PARAMETER: p_matnr LIKE mara-matnr DEFAULT '116'.
    DATA: wa_head LIKE bapie1mathead,
                wa_return LIKE bapireturn1.
    TYPES: BEGIN OF t_plantdata.
            INCLUDE STRUCTURE bapie1marcrt.
    TYPES: END OF t_plantdata.
    DATA: wa_plantdata TYPE t_plantdata,
          it_plantdata TYPE TABLE OF t_plantdata.
    TYPES: BEGIN OF t_plantdatax.
            INCLUDE STRUCTURE bapie1marcrtx.
    TYPES: END OF t_plantdatax.
    DATA: wa_plantdatax TYPE t_plantdatax,
          it_plantdatax TYPE TABLE OF t_plantdatax.
    MOVE: p_matnr TO wa_head-material,
    'X' TO wa_head-basic_view.
    MOVE: p_matnr TO wa_plantdata-material.
    MOVE '1204' TO wa_plantdata-plant.
    MOVE '1.0' TO wa_plantdata-reorder_pt.
    *MOVE '2' TO wa_plantdata-max_stock.
    APPEND wa_plantdata TO it_plantdata.
    CLEAR wa_plantdata.
    MOVE: p_matnr TO wa_plantdatax-material.
    MOVE: '1204' TO  wa_plantdatax-plant.
    MOVE: 'X' TO wa_plantdatax-reorder_pt.
    *MOVE: 'X' TO wa_plantdatax-max_stock .
    APPEND wa_plantdatax TO it_plantdatax.
    CLEAR wa_plantdatax.
    CALL FUNCTION 'BAPI_MATERIAL_MAINTAINDATA_RT'
      EXPORTING
        headdata   = wa_head
      IMPORTING
        return     = wa_return
      TABLES
        plantdata  = it_plantdata
        plantdatax = it_plantdatax.
    IF wa_return-type EQ 'E'.
      WRITE:/ 'Error in updating the Material'.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      WRITE:/ 'Updating the Material is Successful'.
    ENDIF.
    BTW: Problem is only on ECC 6.0. On 4.6C there is no problem like that, data are being updated...
    Really gratefull for help.
    Daniel.

    This is a list of those parameters:
    bapie1marart-brand_id
    bapie1marart-creation_status
    bapie1marart-fashion_grade
    bapie1marart-fiber_code_1
    bapie1marart-fiber_code_2,
    bapie1marart-fiber_code_3,
    bapie1marart-fiber_code_4,
    bapie1marart-fiber_code_5,
    bapie1marart-fiber_part_1,
    bapie1marart-fiber_part_2,
    bapie1marart-fiber_part_3,
    bapie1marart-fiber_part_4,
    bapie1marart-fiber_part_5,
    bapie1marart-free_char_value
    Question whether all of them are necessary ? Where can I take a look for them ?
    Thanks.

  • BAPI_MATERIAL_MAINTAINDATA_RT ZZFIELDS

    Hello,
    I am updating mara, marc append structure  zfields using BAPI_MATERIAL_MAINTAINDATA_RT.
    I am using function value as 004. Value is not getting updated to material master.
    function = '004'
    material = matnr value
    plant = plant value
    field1 = value of z field.
    Please help me in using field1 to update z fields.
    Thanks

    Hi all,
    I have the same requirement MM46 custom field ( with out ALE ) which would updates MARA - custom field value.
    First step -  Created custom field ( MARA-ZZXXX ) by using OMS9 trasaction for MM46 mass maintenance screen.
    Second step -  Created CMOD Z project.
    In this step I got some confusion about writing the code for my Z field, Here I have found 2 include programs under EXIT_SAPL1001_003 exit
    1.  INCLUDE LXMGVF07  -  In this include program I tried to create enhancement ( to write the code for my Z field  by using  WHEN C_PARNAM_CLIENTEXT ), but program is not allowing me to create enhancement / to change the include program. 
    System is giving " Changes to LXMGVF07 are forbidden by SAP"
    2. If you double click on EXIT_SAPL1001_003 exit , here I have found INCLUDE ZXMGVU07.
        In this include program I put break point, but this break point is not getting triggering / stopping.
    Please help me on this

  • BAPI_MATERIAL_MAINTAINDATA_RT-Purchasing View

    Hi all,
    I have to upload the data for MM41 transaction.
    In the 'BAPI_MATERIAL_MAINTAINDATA_RT' purchasing view is not available. i have to select all views how can i do? Plz help.
    Regards
    Priyaranjan

    Hi all,
    I have to upload the data for MM41 transaction.
    In the 'BAPI_MATERIAL_MAINTAINDATA_RT' purchasing view is not available. i have to select all views how can i do? Plz help.
    Regards
    Priyaranjan

  • BAPI_MATERIAL_MAINTAINDATA_RT gives error KM701, but manual entry succeeds

    I have written a program which creates a new material using function module BAPI_MATERIAL_MAINTAINDATA_RT. I get the following error:
    KM701 Profit center K100/12345 does not exist
    However, I can add the same profit center (12345) to the article in transaction MM42 without problems.
    I'm using the same user ID for the BAPI call (via RFC) and manual entry via MM42.

    you probably forgot the leading zeros for the profit center.

  • BAPI_MATERIAL_MAINTAINDATA_RT  dump

    Hi Guru',
    I  am  using function module  BAPI_MATERIAL_MAINTAINDATA_RT  to list  a article at plant level.
    I declared  the  RETURN  table  as  BAPIRETURN1 . But while excuting the program I am getting fallowing error.
    "RETURN" is the correct type, its length is incorrect.
    I tried in all ways .  But still I am getting this problem .
    Will u please any body solve my problem.
    Thanks in advance,
    Santhosh.V

    Hi Santosh,
    The return parameter of the BAPI 'BAPI_MATERIAL_MAINTAINDATA_RT' is an export parameter. It is not a table parameter.
    Hence, declare it as following:
    DATA: wa_return TYPE BAPIRETURN1.
    Regards,
    Pranav.

  • BAPI_MATERIAL_MAINTAINDATA_RT reorder point & Forecast parameters

    Hi
    I use  BAPI_MATERIAL_MAINTAINDATA_RT for change reorder point and only this, but after run i see that the forecast parameters changed too.
    example code
    head-material = matnr.
    head-logst_view = 'X'.
    plant-material = matnr.
    plant-plant = werks.
    plant-reorder_pt = value.
    plantx-material = matnr.
    plantx-plant = werks.
    plantx-reorder_pt = 'X'.
    CALL function 'BAPI_MATERIAL_MAINTAINDATA_RT'
      EXPORTING
         headdata = head
      Importing
         return = return
    TABLES
       plantdata = plant
       plantdatax = plantx.
    I try to select/deselect auto_reset (reset forecast model automatically) but nothing was changed.
    Do you know what is wrong whit this??
    Best Regards
    Szymon Glapiak
    Edited by: Szymon Glapiak on Nov 4, 2008 6:20 PM

    Hi,
    You might need to check for an OSS Note for this BAPI.
    For detailed Desc of BAPI, Refer to http://abap.wikiprog.com/wiki/BAPI_MATERIAL_MAINTAINDATA_RT
    Or you can also use WE60 for IDOC ARTMAS01, the segment definition will help you to understand the BAPI parameters.

  • BAPI_MATERIAL_MAINTAINDATA_RT cannot set value to zero

    I am trying to use this bapi to set a custom Marc field to zero but I cannot. I can set it to anything but zero. Any help would be GREATLY appreciated.
    Here's a sample of my code:
    headdata-function = '004'.
    headdata-material = gv_matnr.
    headdata-no_appl_log = 'X'.
    plantdata-function = '004'.
    plantdata-material = gv_matnr.
    plantdata-plant = gv_werks.
    plantdata-round_val = marc-bstrf.
    APPEND tbapie1marcrt.
    plantdatax-function = '004'.
    plantdatax-material = gv_matnr.
    plantdatax-plant = gv_werks.
    plantdatax-round_val = 'X'.
    APPEND plantdatax.
    plantdataextrt-function = '004'.
    plantdataextrt-material = gv_matnr.
    plantdataextrt-plant = gv_werks.
    plantdataextrt-field1 = 'ZZFIELD'.
    plantdataextrt-field2 = '0'.
    APPEND plantdataextrt.
    plantdataextrtx-function = '004'.
    plantdataextrtx-material = gv_matnr.
    plantdataextrtx-plant = gv_werks.
    plantdataextrtx-field1 = 'ZZFIELD'.
    plantdataextrtx-field2 = 'X'.
    APPEND plantdataextrtx.
    CALL FUNCTION 'BAPI_MATERIAL_MAINTAINDATA_RT'
    EXPORTING
    headdata = headdata
    IMPORTING
    return = return1
    TABLES
    plantdata = plantdata
    plantdatax = plantdatax
    plantext = plantdataextrt
    plantextx = plantdataextrtx.

    I found the solution. Main EAN goes in MARM but when I had tried it and it failed it was actually because I forgot to set this field in X structure.
    Thanks.

  • BAPI_MATERIAL_MAINTAINDATA_RT - no way to set MAIN EAN?

    Hi,
    I'm using BAPI_MATERIAL_MAINTAINDATA_RT to create new materials. Everything was going fine until I added an EAN to the material, when it started giving the following error:
    M3-535: First specify the main EAN for the unit PC
    What this error says makes sense. But in structure MARM (parameter INTERNATIONALARTNOS) of this BAPI the field "main EAN" (HPEAN) is not available. So, how can I set it if it is not available?
    I do see that in structure VENDOREAN has field main ean but I tried to set it and still nothing happened. Besides, I believe it doesnt make sense to set it from here since we don't need vendor data in order to add EANs to an article.
    Having debugged I found the data flowing from INTERNATIONALARTNOS structure to internal table MEAN_ME_TAB which has a structure similar to MEAN and then the place where this internal table the existence of a main EAN is tested. Of course it always fails, since there is no way to fill that field from the BAPI.
    Unless I'm missing something, I don't see how I can set the main EAN from the BAPI.
    Please help.
    Regards,
    Nuno

    I found the solution. Main EAN goes in MARM but when I had tried it and it failed it was actually because I forgot to set this field in X structure.
    Thanks.

Maybe you are looking for