Extend material by 'BAPI_MATERIAL_SAVEDATA'

Hi,
the code is as below(it is failed):
            BAPIMATHEAD-MATERIAL = it_error-MATNR.
            BAPIMATHEAD-BASIC_VIEW = 'X'.
            BAPI_MARC-PLANT = IT_GOUJIAN-WERKS.
            BAPI_MARCX-PLANT = 'X'.
            CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
              EXPORTING
                headdata   = BAPIMATHEAD
                PLANTDATA = BAPI_MARc
                PLANTDATAX = BAPI_MARcx.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
i just want to extend material created to more plants .
any advice?

Hello,
DATA: BEGIN OF GT_TAR_ORG OCCURS 0,
          WERKS TYPE WERKS,
          WEART TYPE /RB04/OES_YL3_WERKT,
          MTART TYPE MTART,
        END OF GT_TAR_ORG.
LOOP AT GT_TAR_ORG.
    HEADDATA-MATL_TYPE = GT_TAR_ORG-MTART.
    GR_PLANTDATA-PLANT = GT_TAR_ORG-WERKS.
    GR_PLANTDATAX-PLANT = GT_TAR_ORG-WERKS.
    CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
         EXPORTING
              HEADDATA            = HEADDATA
              CLIENTDATA          = GR_CLIENTDATA
              CLIENTDATAX         = GR_CLIENTDATAX
              PLANTDATA           = GR_PLANTDATA
              PLANTDATAX          = GR_PLANTDATAX
         IMPORTING
              RETURN              = GR_RETURN
         TABLES
              MATERIALDESCRIPTION = MATERIALDESCRIPTION
              UNITSOFMEASURE      = UNITSOFMEASURE
              UNITSOFMEASUREX     = UNITSOFMEASUREX
              RETURNMESSAGES      = GT_RETURNMESSAGES
              MATERIALLONGTEXT    = GT_MATERIALLONGTEXT
              EXTENSIONIN         = GT_EXTENSIONIN
              EXTENSIONINX        = GT_EXTENSIONINX.
Append the return messages to the return table.
    APPEND GR_RETURN TO RETURNMESSAGES.
    APPEND LINES OF GT_RETURNMESSAGES TO RETURNMESSAGES.
    RETURN = GR_RETURN.
ENDLOOP.
If the BAPI is unsuccessful the error flag is X.
IF GR_RETURN-TYPE CA 'AEX'.
   GF_ERROR = 'X'.
ENDIF.
LOOP AT GT_RETURNMESSAGES.
    IF GT_RETURNMESSAGES-TYPE CA 'AEX'.
      GF_ERROR = 'X'.
    ENDIF.
ENDLOOP.
Commit only if the updations were successfull
Commit only if the updations were successfull
IF GF_ERROR IS INITIAL.
    COMMIT    WORK AND WAIT.
ELSE.
    ROLLBACK WORK.
ENDIF.
If useful reward.
Regards,
Vasanth

Similar Messages

Extend Material Master - Sales Org.

Hi,
I want to copy the material from one sales org. distribution channel to another sales org. distribution channel. My doubt is I want to use BAPI_MATERIAL_SAVEDATA. But how to use this??
Because that material is not present in the target sales org. distribution channel, so for that I have to copy all the views except sales view using BAPI_MATERIAL_GETALL then pass to BAPI_MATERIAL_SAVEDATA.
In this the problem is.. I have to map all the fields between these BAPI. So is there any easy way to do this?
Can anyone have similar requirement like this which can share??
Thanks,
Regards,
Jhings.
Edited by: Jhings on Mar 7, 2012 7:26 PM

Check these threads about the mandatory fields for your requirement:
BAPI_MATERIAL_SAVEDATA extend for new plant whats necessary
Extend material using bapi_material_savedata
About transfer the material data from BAPI_MATERIAL_GETALL to structures to be used on BAPI_MATERIAL_SAVEDATA, i think that MOVE field by field is the better way once there won't many fields to be populated.
Felipe

How to extend material cross many plants using BAPI?

Hi.
when i use BAPI 'BAPI_MATERIAL_SAVEDATA' to extend material cross plants, i can not extent accounting view.
code as below:
            BAPI_MARC-PLANT = IT_GOUJIAN-WERKS.
            BAPI_MARCX-PLANT = IT_GOUJIAN-WERKS.
            CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
              EXPORTING
                headdata            = BAPIMATHEAD
               CLIENTDATA          = BAPI_MARA
               CLIENTDATAX         = BAPI_MARAx
                PLANTDATA           = BAPI_MARc
                PLANTDATAX          = BAPI_MARcx
               VALUATIONDATA       = BAPI_MBEW
               VALUATIONDATAX      = BAPI_MBEWX
              IMPORTING
                RETURN              = IT_RETURN.
             TABLES
               MATERIALDESCRIPTION = IT_MATERIALDESC.
i just change the plant data.
any advice?

You can extend the material in several plants using
BAPI_MATERIAL_SAVEDATA
All you need to do is populate the import parameter
WA_HEADDATA-MATERIAL
WA_HEADDATA-IND_SECTOR
WA_HEADDATA-MATL_TYPE
and check the views that you want to maintain in the new plant.
Suppose you want to maintain only Basic view than..
WA_HEADDATA-BASIC_VIEW = 'X'.
And based on selected views , you need to populate other
parameters.
like I want to maintain basic view in another plant than
I need to populate the plant data.
WA_PLANTDATA-PLANT = <PLANT>.
populate other fields, if required.
WA_PLANTDATAX-PLANT = <PLANT>.
populate flags, if required.
and pass these parameters to the Function module.
It should work.
Please reward, if you find the answer useful.

Extend material to another plant

hi all,
I want to extend materials to another plant using copy from... Someone knows which BAPI Can I use
to do this?
thanks.
marisol

u can use "BAPI_MATERIAL_SAVEDATA".
Suppose u have to Extend material from 1000 to 1100 plant.
so ur template will be like this:
Material Number,Current_Plant,extend_plant,valuation area ,Type
Using Material Number,Current_Plant , valuation arear , Type and pass it to
BAPI_MATERIAL_GET_DETAIL
u will get all data 4 , BAPI_MATERIAL_SAVEDATA.

Error while creating a material using Bapi_material_savedata

Hi,
there is an error encountered while creating a material using BAPI_MATERIAL_SAVEDATA..
The Error description is " Material description is not transfered " even after supplying the Material description and other mandatory field information like industrial sector, material type ,basic view indicator,Base UOM,Base UOM ISO code.
Please let me know the solution, if you know.

Hi,
Please search the SCN for the answers
https://www.sdn.sap.com/irj/scn/advancedsearch?query=errorinBAPI_MATERIAL_SAVEDATA+&cat=sdn_all

To Extend material to plant using MATERIAL_MAINTAIN_DARK .

I am tryin to extend material into plants using MATERIAL_MAINTAIN_DARK function module.Can someone please check the code below and tell me how i should modify it to work.Is BDC a better option?
DATA: t_amara_ueb LIKE mara_ueb OCCURS 0 WITH HEADER LINE.
DATA: t_amarc_ueb LIKE marc_ueb OCCURS 0 WITH HEADER LINE.
t_amara_ueb-mandt = sy-mandt.
t_amara_ueb-matnr = it_reqdata-material.
t_amara_ueb-tcode = 'MM01'.
t_amara_ueb-tranc = 1.
APPEND t_amara_ueb.
CLEAR t_amara_ueb.
t_amarc_ueb-mandt = sy-mandt.
t_amarc_ueb-matnr = it_reqdata-material.
t_amarc_ueb-werks = it_reqdata-plant.
t_amarc_ueb-tranc = 1.
t_amarc_ueb-KZKRI = 'X'.
APPEND t_amarc_ueb.
CLEAR t_amarc_ueb.
call function 'MATERIAL_MAINTAIN_DARK'
exporting
flag_muss_pruefen = 'X'
p_kz_no_warn = 'N'
kz_prf = space
kz_verw = 'X'
kz_aend = 'X'
kz_dispo = 'X'
tables
   amara_ueb                       = t_amara_ueb
   AMARC_UEB                       = t_AMARC_UEB
EXCEPTIONS
   KSTATUS_EMPTY                   = 1
   TKSTATUS_EMPTY                  = 2
   T130M_ERROR                     = 3
   INTERNAL_ERROR                  = 4
   TOO_MANY_ERRORS                 = 5
   UPDATE_ERROR                    = 6
   OTHERS                          = 7
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
COMMIT WORK.
ENDIF.
Thanks and Regards,
Pratima.

Hi ,
Use the below code.
DATA : lt_mara_ueb TYPE TABLE OF mara_ueb INITIAL SIZE 0,
       lt_marc_ueb TYPE TABLE OF marc_ueb INITIAL SIZE 0,
       lt_errors TYPE TABLE OF merrdat INITIAL SIZE 0.
DATA : wa_mara_ueb TYPE mara_ueb,
       wa_marc_ueb TYPE marc_ueb,
       wa_messtab TYPE merrdat.
DATA : l_mstring(480).
parameters: l_matnr like mara-matnr.
* Set up I_MARA
REFRESH lt_mara_ueb.
wa_mara_ueb-mandt = sy-mandt.
wa_mara_ueb-tcode = 'MM01'.
wa_mara_ueb-matnr = l_matnr.
wa_mara_ueb-tranc = '0000000001'.
APPEND wa_mara_ueb TO lt_mara_ueb.
CLEAR wa_mara_ueb.
SELECT SINGLE * FROM marc INTO CORRESPONDING FIELDS OF wa_marc_ueb
WHERE matnr EQ l_matnr AND werks EQ '01FC'.
IF sy-subrc EQ 0.
    MOVE '01BV' TO wa_marc_ueb-werks.
    wa_marC_ueb-tranc = '0000000001'.
    WA_MARC_UEB-PSTAT = SPACE.
    APPEND wa_marc_ueb TO lt_marc_ueb.
ENDIF.
CALL FUNCTION 'MATERIAL_MAINTAIN_DARK'
    EXPORTING
*   FLAG_MUSS_PRUEFEN               = 'X'
*   SPERRMODUS                      = 'E'
*   MAX_ERRORS                      = 0
      p_kz_no_warn                    = 'N'
      kz_prf                          = 'W'
*   KZ_VERW                         = 'X'
*   KZ_AEND                         = 'X'
*   KZ_DISPO                        = 'X'
*   KZ_TEST                         = ' '
*   NO_DATABASE_UPDATE              = ' '
*   CALL_MODE                       = ' '
*   CALL_MODE2                      = ' '
*   USER                            = SY-UNAME
*   SUPPRESS_ARRAY_READ             = ' '
*   FLG_MASS                        = ' '
* IMPORTING
*   MATNR_LAST                      =
*   NUMBER_ERRORS_TRANSACTION       =
    TABLES
      amara_ueb                       = lt_mara_ueb
*   AMAKT_UEB                       =
      amarc_ueb                       = lt_marc_ueb
*   AMARD_UEB                       =
*   AMFHM_UEB                       =
*   AMARM_UEB                       =
*   AMEA1_UEB                       =
*   AMBEW_UEB                       =
*   ASTEU_UEB                       =
*   ASTMM_UEB                       =
*   AMLGN_UEB                       =
*   AMLGT_UEB                       =
*   AMPGD_UEB                       =
*   AMPOP_UEB                       =
*   AMVEG_UEB                       =
*   AMVEU_UEB                       =
*   AMVKE_UEB                       =
*   ALTX1_UEB                       =
*   AMPRW_UEB                       =
*   AMFIELDRES                      =
*   AMERRDAT                        =
EXCEPTIONS
   KSTATUS_EMPTY                   = 1
   TKSTATUS_EMPTY                  = 2
   T130M_ERROR                     = 3
   INTERNAL_ERROR                  = 4
   TOO_MANY_ERRORS                 = 5
   UPDATE_ERROR                    = 6
   OTHERS                          = 7
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK.
Regards,
Raghav

To extend material master in condition that split valuation.

I want to valuate the material at two different valuation class
if the material is produced internally and procured externally.
So I use split valuation function.
I created accounting view using valuation category at plant level and
I extended accounting view using valuation type.
I tried to extend material master for other plant in condition that
I didnu2019t check batch management in purchasing view
but I mat error message u201CIndividual batch valuation not possible hereu201D(M3184).
To extend material master for other plant, Should I check batch management
in purchasing view ?

Hi,
Select the batch management indicator on purchasing view, press F1 button and check technical details. If the field is:
MARA-XCHPF --> batch management is active at client.
MARC-XCHPF --> batch management is active at plant level
Please check SAP online help on batch level:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/25/2838714f7811d18a150000e816ae6e/frameset.htm
Batch Levels
Plant level
The batch number is unique in connection with the plant and material.
The batch number is only known in the plant in which it was created if the stock is transferred to another plant, the batch is unknown in the recipient plant and the system does not adopt any data. You have to recreate and specify the batch in the receiving plant; that is, the same batch number may have different specifications in several plants.
Material level:
The batch number is unique in all plants in connection with the material.
The same batch number has the same meaning for the material in all plants. One batch number cannot have different specifications in different plants. During stock transfer to another plant, the specification of the batch is known in the destination plant even if the batch is placed into storage in that plant for the first time.
Client level:
The batch number is unique in the whole client. A batch number can only be assigned once in the client. You cannot assign the same batch number for different materials.
The batch number is only unique at the chosen level.
If your batch maagement is valid at client / material level you defined it once in table MARA and it is valid for all your plants - that's why you get it automatically (if this is the reason in real).
Regards,
Csaba
Edited by: Csaba Szommer on Nov 7, 2009 5:13 PM

How to extend material/customer

Hello Experts
If I want to extend one material for different plant/sales org/storage location then how can i do this . Same for the customer , if i want to extend that customer for other sales areas then how can i do that ?
Regards-
Abhi

Hi,
You can extend material to different plant and sales organisation by using the T.Code "MM01".
Enter the material number you want to extend and enter the same under copy from.Press Enter.
Select the required views and enter new the plant and Sales organisation you want to extend.
In a similar way,you can extend customer data as well.
Regards,
Krishna.

How to extend material to new sto loc

Hi All
Let me know how to extend material to new storage location
Tks
Manju

Dear,
You can extend material for new storage location via MMSC.
Ans if you want to extend list of material for storage location you can use MMSC_MASS.
If you want to extend material for plant you can use MM01 - for single material and MM50 - For multiple materials.
Regards,
Mahesh Wagh

Extend material master data from one plant to another plant

hi,
how can i extend material master data from one plant to another plant.
is there any sap standard transaction for this ie. bdc/t-code.
thanks in advance.......
rahul

Hi
If you want to extend the material form one plant to another then below are the possible options.
1) MM01 - Use the material in the reference and fill in copy from and to then press enter to complete the extention.This is recommended only if you want to extend very less records.
2) Use LSMW and record MM01 thru BDC recording available in LSMW and make the template in excel and convert it to .txt tab delimited format to upload more records.LSMW is the perfect tool and is used extensively in all the projects.
3) Get the help from ABAPer to create upload program and include the BDC recording.
There is no standard T code available in SAP becoz data mainatenance in the material master will be based on the industry.
Hope it will help.
Thanks/Karthik

How to extend material master product Hierarchy

Hi,
How to extend material master product Hierarchy
Define Product Hierarchies (SAP Library - Material Master)
In SAP help, the procedure is given, But in procedure we need to change standard structures and data elements.
Need to know, This is only the possibilty?
Need to change structure and data elements by Access key only or there is some other way.
Regards
Sukumar

Hi,
Use t.code:MM01 and in Copy From Field Give Material No ( u wan to copy) and in Next Screen Give Extending Plant & Storage Location and in Copy From Fields give Reference Plant & Storage Location.
For more check the links for material extension.
http://www.copacustomhelp.state.pa.us/infopak/nav/procurement/pr%20master%20data/file1434/index.htm
http://www.copacustomhelp.state.pa.us/infopak/standard/fastpaths/mm01_content.htm
Regards,
Biju K

How to extend material master?

to extend storage location we can use T-code MMSC. similarly to extend material master any T-code or any other procedure is there? please help me

Hi,
Use t.code:MM01 and in Copy From Field Give Material No ( u wan to copy) and in Next Screen Give Extending Plant & Storage Location and in Copy From Fields give Reference Plant & Storage Location.
For more check the links for material extension.
http://www.copacustomhelp.state.pa.us/infopak/nav/procurement/pr%20master%20data/file1434/index.htm
http://www.copacustomhelp.state.pa.us/infopak/standard/fastpaths/mm01_content.htm
Regards,
Biju K

Extending material master for different sales org/plant combination

hi ,
1 ) a material can be sold from one plant by many sales organisations. so we map this scenario in enterprise structure by the config step "assign sales org--dist channel--
plant ". (let's say sales org A and B selling from plant 1 and also sales org A selling from plant 2)
when we have defined the above config step, then why we need to have material master extended for different combination of sales org and plant as in stpe 1 ?. we can just create one material master with one plant and sales org combination and based on config as in step one, we can sell material from any sales org from a plant ?
2) we can extend material master for any combination of sales org/plant .....is it also possible to extend material master to different storage locations !
regds
pamela
Edited by: Pamela79 on Feb 15, 2011 11:02 AM

There are several reasons why you should extend the materails to different sales organizations and plants.
a. The materials are normally valuated at the plant level. So, you can have different valuations at different plants.
b. You can have different quantity stored in different plants. How do you know which plant has what quantity.
c. You can have materail not to be sold from one plant, but you can have the same materail sold from the other, how do you block it? at the plant and materail combination, you can do it.
d. For different sales organizations, you may want the cost and the price to be posted to different GL accounts. You can control it at sales org level of the materail.
e. You may just want the material to be purchased but not sold, then you may not even create a sales org view for the material. But say, in future you will like to only purchase a materail from a plant and consume it for some other purpose but not sales (which u did previously), then you can block it at sales org and dbr level.
So, these are a few reasons. But there could be many. You can have a look at the fields in the material master at sales org level and plant level and you can find it for yourself howmany parameters are there to control...
Hope this helps...
Regards,
Mukund S

Create Material With BAPI_MATERIAL_SAVEDATA

Hi,
I New To SAP I'm Trying To Create Material With BAPI_MATERIAL_SAVEDATA . When I Execute The Code I am Getting Message That ' Bytes Transfered' But When I Checking The MARA Table I Cannot Find The Enteries..
*************************************************************CODE*********************************************************************************
TABLES: bapimathead,
              bapi_mara,
              bapi_marax,
              bapiret2.
TYPES: BEGIN OF lsmw_material_master,
             matnr TYPE mara-matnr,
             mtart TYPE mara-mtart,
             mbrsh TYPE mara-mbrsh,
             maktx TYPE makt-maktx,
             meins TYPE mara-meins,
             END   OF lsmw_material_master.
DATA: it_master        TYPE TABLE OF lsmw_material_master,
            wa_master     TYPE lsmw_material_master,
            it_materialdesc TYPE TABLE OF bapi_makt WITH HEADER LINE,
            it_return            LIKE bapiret2.
SELECTION-SCREEN: BEGIN OF BLOCK a1 WITH FRAME TITLE text-001.
           PARAMETERS: p_file TYPE rlgrap-filename OBLIGATORY.
SELECTION-SCREEN: END OF BLOCK a1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
   DATA: it_tab   TYPE filetable,
             iv_subrc LIKE sy-subrc.
CALL METHOD cl_gui_frontend_services=>file_open_dialog
     EXPORTING
            window_title            = 'Select Source File'
    CHANGING
            file_table              = it_tab
            rc                      = iv_subrc
   IF sy-subrc <> 0.
*             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
   LOOP AT it_tab INTO p_file.
   ENDLOOP.
CALL FUNCTION 'UPLOAD'
    EXPORTING
           filename                    = p_file
           filetype                      = 'DAT'
   TABLES
           data_tab                      = it_master
   IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
LOOP AT it_master INTO wa_master.
     bapimathead-material        = wa_master-matnr.
     bapimathead-ind_sector    = wa_master-mtart.
     bapimathead-matl_type     = wa_master-mbrsh.
     bapimathead-basic_view    = 'X'.
     bapi_mara-base_uom        = wa_master-meins.
     bapi_marax-base_uom       = 'X'.
     it_materialdesc-matl_desc = wa_master-maktx.
     APPEND it_materialdesc.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
   EXPORTING
          headdata                    = bapimathead
          clientdata                    = bapi_mara
          CLIENTDATAX             = bapi_marax
IMPORTING
          return                          = it_return
TABLES
          materialdescription       = it_materialdesc
ENDLOOP.
IF sy-subrc = 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*     EXPORTING
*       WAIT          =
*     IMPORTING
*       RETURN        =
* ELSE.
   WRITE:/ 'Error'.
*   CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
*   IMPORTING
*     RETURN        =
ENDIF.
*************************************************************FILE >>>>>check.text.********************************************************************************
Cooinfl_Fan
E
FERT
FANS
PC
Bathing_Fan
E
FERT
FANS
PC

Please pass following values:
it_materialdesc-matl_desc = wa_master-maktx.
it_materialdesc-langu = 'E'.
it_materialdesc-langu_iso = 'EN'.
     APPEND it_materialdesc.
Regards

Not able to extend material to plant 102

Hi Experts,
I have a problem to extend material.
I am trying to extend material to plant 102, but when I click costing view I am getting error that "Valuation of Material 1288Z in valuation area 102 inconsistent"
Please help me to resolve this
Thanks in Advance,
Regards,
Vineela

Hi Experts,
In the material Master there is no Accounting View 1 and 2.
How can I get these views in material master.
Regards,
Vineela

Extend material by 'BAPI_MATERIAL_SAVEDATA'

Similar Messages

Maybe you are looking for