LSMW FOR MATERIAL MASTER USING BAPI_MATERIAL_SAVEDATA

Hi Gurus,
Im trying to develop lsmw for material master upload using bapi method.
Object:BUS1001006
BAPI:BAPI_MATERIAL_SAVEDATA
MESSAGE TYPE: MATMAS_BAPI
BASIC TYPE : MATMAS_BAPI01.
I m unable to find parameters to load gross_weight volume and volume unit and also problem loading the custom fields of material master. Any body who has worked on this one, can you please help me.
Thanks
venkat

The BAPI_MATERAIL_SAVEDATA support the gross_weight or the volume via the tables UNITSOFMEASURE and UNITSOFMEASUREX.
eg.
UNIT_OF_WT =KG
ALT_UNIT = PCS
NUMERATOR = 1
DENOMINATR =1
GROSS_WT =1000
All the customer specific field are supported by the EXTENSIONIN and EXTENSIONINX tables.

Similar Messages

  • LSMW FOR MATERIAL MASTER USING BAPI_MATERIAL_SAVEDATA -Adding Custom Fields

    Hi Gurus,
    I'm developing LSMW for Material Master Upload using BAPI method.
    Object:BUS1001006
    BAPI:BAPI_MATERIAL_SAVEDATA
    MESSAGE TYPE: MATMAS_BAPI
    BASIC TYPE : MATMAS_BAPI03.
    There is a requirement to use/map a custom field. Upon research custom field can be added to the parameter EXTENSIONIN and EXTENSIONINX, but I have no Idea on how to do it with LSMW. Please advise what approach is needed.
    Thanks and Regards,
    Jay

    Hi Gurus,
    I got the following code below.
    The custom field won't get updated.... Please advise on what should I do... I've checked different forums and still can't come up with the solution... Please advise..
    REPORT ztest_extend_matmas1.
    STRUCTURE
    TABLES:
    bapimathead, "Headerdata
    bapi_mara, "Clientdata
    bapi_marax, "Clientdatax
    bapi_marc, "Plantdata
    bapi_marcx, "Plantdatax
    bapi_makt, "Material description
    bapiparex, "Extensionstruktur
    bapiparexx,
    bapiret2. "Return messages
    DATA:
    bapi_te_mara LIKE bapi_te_mara,
    bapi_te_marax LIKE bapi_te_marax,
    v_file TYPE string.
    INTERNAL TABLE
    *to store the output data
    DATA:BEGIN OF it_material_number OCCURS 0.
            INCLUDE STRUCTURE bapimatinr.
    DATA:END OF it_material_number.
    *for materialtext
    DATA:BEGIN OF it_materialdesc OCCURS 0.
            INCLUDE STRUCTURE bapi_makt .
    DATA:END OF it_materialdesc.
    *für z-feld
    DATA:BEGIN OF it_bapiparex OCCURS 0.
            INCLUDE STRUCTURE bapiparex.
    DATA:END OF it_bapiparex.
    *für z-feldx
    DATA:BEGIN OF it_bapiparexx OCCURS 0.
            INCLUDE STRUCTURE bapiparexx.
    DATA:END OF it_bapiparexx.
    *to return messages
    DATA:BEGIN OF it_return2 OCCURS 0.
            INCLUDE STRUCTURE bapiret2.
    DATA:END OF it_return2.
    DATA:BEGIN OF it_return OCCURS 0.
            INCLUDE STRUCTURE bapiret1.
    DATA:END OF it_return.
    DATA
    lt_messages      TYPE bapiret2_t.
    PROCESSING
    *bapimathead-material = it_material_number-material.
    bapimathead-material = '100-2520'.
    bapimathead-ind_sector = 'P'.
    bapimathead-matl_type = 'AEM'.
    bapimathead-basic_view = 'X'.
    bapimathead-purchase_view = 'X'.
    bapimathead-inp_fld_check = 'I'.
    *bapimathead-BASIC_VIEW = 'X'.
    *bapimathead-SALES_VIEW = 'X'.
    *bapimathead-PURCHASE_VIEW = 'X'.
    *bapimathead-MRP_VIEW = 'X'.
    *bapimathead-FORECAST_VIEW = 'X'.
    *bapimathead-WORK_SCHED_VIEW = 'X'.
    *bapimathead-PRT_VIEW = 'X'.
    *bapimathead-STORAGE_VIEW = 'X'.
    *bapimathead-WAREHOUSE_VIEW = 'X'.
    bapi_mara-matl_group = '0001'.
    bapi_mara-old_mat_no = '100-251'.
    bapi_mara-base_uom = 'ST'.
    bapi_marax-matl_group = 'X'.
    bapi_marax-old_mat_no = 'X'.
    bapi_marax-base_uom = 'X'.
    bapi_marc-plant = '1000'.
    bapi_marcx-plant = '1000'.
    it_materialdesc-langu = 'EN'.
    it_materialdesc-matl_desc = 'DESC'.
    APPEND it_materialdesc.
    *bapi_te_mara-material = it_material_number-material.
    bapimathead-material = '100-2520'.
    *bapi_te_mara-zzforst = '4148'.
    bapi_te_mara-material = '100-2520'.
    bapi_te_mara-zzmar_field1 = '4148'.
    *bapi_te_marax-material = it_material_number-material.
    bapimathead-material = '100-2520'.
    *bapi_te_marax-zzforst = 'X'.
    bapi_te_marax-material  = '100-2520'.
    bapi_te_marax-zzmar_field1 = 'X'.
    it_bapiparex-structure = 'BAPI_TE_MARA'.
    it_bapiparex-valuepart1 = bapi_te_mara.
    APPEND it_bapiparex.
    it_bapiparexx-structure = 'BAPI_TE_MARAX'.
    it_bapiparexx-valuepart1 = bapi_te_marax.
    APPEND it_bapiparexx.
    CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
      EXPORTING
        headdata            = bapimathead
        clientdata          = bapi_mara
        clientdatax         = bapi_marax
        plantdata           = bapi_marc
        plantdatax          = bapi_marcx
      IMPORTING
        return              = it_return2
      TABLES
        materialdescription = it_materialdesc
        extensionin         = it_bapiparex
        extensioninx        = it_bapiparexx
        returnmessages      = lt_messages.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    THanks and Regards,
    Jay
    Edited by: jhayyy on May 17, 2011 6:54 AM

  • Issue in LSMW for material master using standard input program RMDATIND!!

    Hello guys,
    I have a issue in LSMW for material master.
    I have a custom field in MARA table. which I want to add in my LSMW.
    I added the field in BMMH1 structure. I'm passing the value to this field, But it is not populated in the table when I run it.
    Is there anything else I need to do apart from addition of field in the structure BMMH1.
    Thanks in advance for your help.
    Regards,
    Sumeet....

    see oss note 44410, it gives you a step by step overview.
    https://service.sap.com/sap/support/notes/44410

  • LSMW for material master using Batch input recording method

    Dears,
    I am using Batch input recording method to upload material master data. But while selecting views , I need to scroll to select the vies lets say Plant storage loc view. While scrolling and selecting ,views are not recorded propelry . That is when I run in foreground system selects only basic data and purchasing views but the plant data views are not selected(palnt data views are selected by scrolling while recording).
    How to resolve this issue.
    Pls help
    Regards
    Kamesh

    HI,
    , I need to scroll to select the vies lets say Plant storage loc view. While scrolling and selecting ,views are not recorded propelry
    Don,t scroll use Page down button from key Bord
    like select Basis view and then press page down button from key board ,then you will get next view now select it
    Regards
    Kailas Ugale

  • LSMW for material master upload

    Hi gurus
    i have one problem while uploading material master with LSMW.
    I have murged 2 company codes in one so while creating material master system is asking me tax classification data in sales view for 2 country sales org and distrubition channel. I am using sap std LSMW for material master creation.
    system is giving me error as " tax classification data not maintained completely".
    need your valuable help to solve this problem

    Tax classification data is mandatory field in Sales view of MM01.
    Check out you mapping for the tax classification fields. usually classification value is 0 OR 1.
    You can first test the values in MM01 Sales View with the legacy data you have and this way you will able to find the mandatory fields also and can see the valid values for the fields.
    Remember you may have more than one Tax Classification values depending on the country code.
    For that you can add those many columns in legacy data file and map them.
    Hope it helps.

  • LSMW for  Vendor Master using Batch Input/Direct

    Hi Folk,
    I'm trying to create a LSMW for  Vendor Master using Batch Input/Direct Input and in the step Create Batch Inout Session a error message appears:
    Trans.     1 XK01: Acct already exists; general area not being processed.
    Can somebody help me with this...........

    Hi,
    Check manually create vendor. Check with recording steps means strucutre creadred while you choose BDC recording option. With same data r u able to create vendor.
    Regards
    Md.MahaboobKhan

  • LSMW for Material master data

    Hi,
    Anybody can help me, how to make LSMW for Material master data.
    Thanks in Advance
    Arjun

    pls follow the thread:
    http://help.sap.com/saphelp_46c/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htm
    regards,
    indranil

  • Upload sales text for material master using LSMW direct input method

    Hello Experts,
    I was trying to upload sales text for a material master using LSMW direct input method.
    I followed the following steps for the same
    Tab dlimited Text file format
    MATNR           LONGTEXT                                                     LINE       
    MATERIAL1    LONGTEXT FOR MATERIAL MATERIAL1       1
    Step1 -> Maintain object attributes
    Object -> 0001
    Method-> 0001
    Program name -> /SAPDMC/SAP_LSMW_IMPORT_TEXTS
    Program type -> D
    Step2 -> Maintain Source Structure
    Source structure -> LONG_TEXT            Source structure for long text
    Step 3-> Maintain souce file
    Source Fields
    ZLONG_TEXT             Source structure for long text
                           MATNR                         C(018)    MATNR
                           LTEXT                          C(132)    LTEXT
    Step 4-> Maintain structure relationship
    Structure Relations
    /SAPDMC/LTXTH Long Texts: Header                                           <<<< ZLONG_TEXT Source structure for long text
                  Select Target Structure /SAPDMC/LTXTH .
    /SAPDMC/LTXTL Long Texts: Row                                              <<<< ZLONG_TEXT Source structure for long text
                 Select Target Structure /SAPDMC/LTXTL .
    Step 5-> Maintain Field mapping and conversion rules
    Here i have assigned constan rules to couple of them like
    /SAPDMC/LTXTH                  Long Texts: Header
    Fields
       OBJECT                Texts: Application Object
                                    Rule :   Constant
                                    Code:    /SAPDMC/LTXTH-OBJECT = 'MVKE'.
       NAME                  Name
                                    Source:  ZLONG_TEXT-MATNR (MATNR)
                                    Rule :   Transfer (MOVE)
                                    Code:    /SAPDMC/LTXTH-NAME = ZLONG_TEXT-MATNR.
       ID                         Text ID
                                    Rule :   Constant
                                    Code:    /SAPDMC/LTXTH-ID = '0001'.
       SPRAS                 Language Key
                                    Rule :   Constant
                                    Code:    /SAPDMC/LTXTH-SPRAS = 'E'.
    /SAPDMC/LTXTL                  Long Texts: Row
      Fields
        TEXTFORMAT     Tag column
                                    Rule :   Constant
                                    Code:    /SAPDMC/LTXTL-TEXTFORMAT = '/'.
        TEXTLINE             Text Line
                                    Source:  ZLONG_TEXT-LTEXT (LTEXT)
                                    Rule :   Transfer (MOVE)
                                    Code:    /SAPDMC/LTXTL-TEXTLINE = ZLONG_TEXT-LTEXT.
    Step6 -> Specify file
    Legacy Data          On the PC (Frontend)
                 Data                           D:\Sales_Longtext.txt
    Step7 -> Assign File
    ZLONG_TEXT Source structure for long text
                  Data D:\Sales_Longtext.txt
    Step8 -> Read data
    Output result
    Source Structure             Read      Written        Not Written
    ZLONG_TEXT              1                1              0
    Transactions Read:            1
    Records Read:                   1
    Transactions Written:         1
    Records Written:                 1
    Step 8 -> Display read data
    Field Name                    Field Text Field Value
    MATNR                          MATNR      MATERIA1
    LTEXT                            LTEXT      SALES TEXT FOR Material MATERIAL1
    Step 9 -> Convert data
    File Read:          ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.read
    File Written:       ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
    Transactions Read:                 1
    Records Read:                        1
    Transactions Written:              1
    Records Written:                     2
    Step 10 -> Display converted data
    1 /SAPDMC/LTXTH                   1MVKE      MATERIAL1                                                                   0001E
    2 /SAPDMC/LTXTL                   2/ SALES TEXT FOR Material MATERIAL1
    Step 11 -> Start direct input program
    Output result for the same
    Legacy System Migration Workbench
    Project:                              ZNRD_PRJ1       ORH
    Subproject:                        ZNRD_SUBPRJ2    Upload long text
    Object:                               ZNRD_LTEXT      Long text tru direct input
    File :                                   ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
    Long Texts in Total:                                1
    Successfully Transferred Long Texts:  1
    Non-Transferred Long Texts:                 0
    Now when i check the material master sales view -> sales text it is empty.
    Please help me with the same.
    Regards,
    Ranjith N

    Hello Experts, I was trying to upload sales text for a material master using LSMW direct input method.
    I followed the following steps for the same
    Tab dlimited Text file format
    MATNR             LONGTEXT                                              LINE
    MATERIAL1     LONGTEXT FOR MATERIAL MATERIAL1 1 *************************************************************************************************************
    Step1 -> Maintain object attributes
    Object -> 0001
    Method-> 0001
    Program name -> /SAPDMC/SAP_LSMW_IMPORT_TEXTS
    Program type -> D
    Step2 -> Maintain Source Structure
    Source structure -> LONG_TEXT Source structure for long text
    Step 3-> Maintain souce file Source Fields
    ZLONG_TEXT Source structure for long text
    MATNR C(018) MATNR
    LTEXT C(132) LTEXT
    Step 4-> Maintain structure relationship
    Structure Relations 
    /SAPDMC/LTXTH Long Texts:  Header <<<< ZLONG_TEXT Source structure for long text
    Select Target Structure
    /SAPDMC/LTXTH . /SAPDMC/LTXTL Long Texts: Row <<<< ZLONG_TEXT Source structure for long text
    Select Target Structure /SAPDMC/LTXTL .
    Step 5-> Maintain Field mapping and conversion rules
    Here i have assigned constan rules to couple of them like
    /SAPDMC/LTXTH Long Texts: Header
    Fields
    OBJECT            Texts: Application Object
                             Rule : Constant
                              Code: /SAPDMC/LTXTH-OBJECT = 'MVKE'.
    NAME               Name
                             Source: ZLONG_TEXT-MATNR (MATNR)
                             Rule : Transfer (MOVE)
                             Code: /SAPDMC/LTXTH-NAME = ZLONG_TEXT-MATNR.
    ID                     Text ID
                             Rule : Constant
                             Code: /SAPDMC/LTXTH-ID = '0001'.
    SPRAS             Language Key
                             Rule : Constant
                            Code: /SAPDMC/LTXTH-SPRAS = 'E'.
    /SAPDMC/LTXTL Long Texts: Row
    Fields
    TEXTFORMAT  Tag column 
                             Rule : Constant
                             Code: /SAPDMC/LTXTL-TEXTFORMAT = '/'.
    TEXTLINE          Text Line
                             Source: ZLONG_TEXT-LTEXT (LTEXT)
                             Rule : Transfer (MOVE)
                             Code: /SAPDMC/LTXTL-TEXTLINE = ZLONG_TEXT-LTEXT.
    Step6 -> Specify file Legacy
    Data On the PC (Frontend)
                 Data D:\Sales_Longtext.txt
    Step7 -> Assign File ZLONG_TEXT
    Source structure for long text
              Data D:\Sales_Longtext.txt
    Step8 -> Read data
    Output result
    Source Structure            Read                Written                Not Written
    ZLONG_TEXT                  1                       1                            0
    Transactions Read          1
    Records Read:                1
    Transactions Written:      1
    Records Written:             1
    Step 8 -> Display read data
    Field Name             Field Text                      Field Value
    MATNR                    MATNR                         MATERIA1
    LTEXT                     LTEXT                            SALES TEXT FOR Material MATERIAL1
    Step 9 -> Convert data
    File Read: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.read
    File Written: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
    Transactions Read:    1
    Records Read:           1
    Transactions Written: 1
    Records Written:         2
    tep 10 -> Display converted data
    1 /SAPDMC/LTXTH     1    MVKE        MATERIAL1 0001   E
    2 /SAPDMC/LTXTL     2/   SALES TEXT FOR Material       MATERIAL1
    Step 11 -> Start direct input program
    Output result for the same
    Legacy System Migration Workbench Project:
    ZNRD_PRJ1  ORH
    Subproject:   ZNRD_SUBPRJ2     Upload long text
    Object:          ZNRD_LTEXT          Long text tru direct input
    File :              ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
    Long Texts in Total:                                1
    Successfully Transferred Long Texts:  1
    Non-Transferred Long Texts:                0
    Now when i check the material master sales view -> sales text it is empty. Please help me with the same.
    Regards,
    Ranjith N

  • Error in the LSMW for vendor master using standard batch/direct input

    I am facing the problem in the LSMW for the Vendor master data. The vendor is initially created for the company code 350 by using LSMW. NOw when I try to uploasd the same vendor using the same LSMW for the company code 450 then I get the error in the Bach input creation as follows:
    Batch Input Interface for Vendors
    FB012                    Session 1 : Special character for 'empty field' is /
    FB007                    Session 1 session name VNDR_CREATE_ was opened
    FB104                    Trans. 2 XK01 : Acct already exists; general area not being processed
    FB125                    ... Data in table BLFA1 cannot be processed
    FB016                    ... Last header record ...
    FB014                    ... BLF00-STYPE 1
    FB014                    ... BLF00-TCODE XK01
    FB014                    ... BLF00-LIFNR 300951
    FB014                    ... BLF00-BUKRS 402
    FB014                    ... BLF00-EKORG /
    FB014                    ... BLF00-KTOKK VEND
    FB017                    ... Last data record ...
    FB014                    ... BLFA1-STYPE 2
    FB014                    ... BLFA1-TBNAM BLFA1
    FB014                    ... BLFA1-ANRED /
    FB014                    ... BLFA1-NAME1 SAVOIE AUTOMATISME DEXIS
    This is because when we use XK01 to create the vendor by using the

    Please check this answered link:
    Re: LSMW for Vendor Master
    LSMW Upload vendor master data
    Edited by: Afshad Irani on May 5, 2010 12:42 PM

  • Classification view creation via LSMW for Material master

    Hi,
    We are planning to have an LSMW for creation of material master along with classification view for configurable materials.
    Though we see a flag to indicate classification view  - XEIC1                        Indicator: take Classification view into account
    We do not see a structure where in we can pass all the characteristics and the corresponding values.
    Is this something possible only with BAPIs such as -> BAPI_OBJCL_CREATE after creation of other view for that material.
    Regards,
    HR

    Hi,
    Thanks for the response. This is helpful.
    However, we were intending to use a single LSMW for creation of all views of material master including classification view. Right now we are using Program RMDATIND as direct input method in LSMW.
    Please let me know if there is a way to use single LSMW for creation of all views of material master.
    Thanks
    HR
    Edited by: Hema Rao on Jan 8, 2009 7:58 AM

  • Create Material Master using BAPI_MATERIAL_SAVEDATA - just the basic view

    Hi,
    I want to create new material master ( just the basic view ) using BAPI_MATERIAL_SAVEDATA.
    No error found in the return parameter, but the material was not created.
    Here is my code :
    DATA : ld_headdata LIKE bapimathead,
           lt_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
           lt_return_comit LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
           lt_return_cl LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
           ld_datum(10),
           ld_uzeit(10).
    DATA: ld_matdesc LIKE bapi_makt OCCURS 0 WITH HEADER LINE,
          ld_clientdata  LIKE bapi_mara.
    Regards,
    Hary
    ld_headdata-material = 'MATERIAL-01'.
    ld_headdata-ind_sector  = 'M'.
    ld_headdata-matl_type = 'ERSA'.
    ld_headdata-basic_view = 'X'.
    ld_matdesc-matl_desc = 'TEST MATERIAL'.
    ld_matdesc-langu = sy-langu.
    APPEND ld_matdesc.
    ld_clientdata-base_uom = 'PC'.
    CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
      EXPORTING
        headdata                    = ld_headdata
        clientdata                  = ld_clientdata
       clientdatax                 =
      PLANTDATA                   =
      PLANTDATAX                  =
      FORECASTPARAMETERS          =
      FORECASTPARAMETERSX         =
      PLANNINGDATA                =
      PLANNINGDATAX               =
      STORAGELOCATIONDATA         =
      STORAGELOCATIONDATAX        =
      VALUATIONDATA               =
      VALUATIONDATAX              =
      WAREHOUSENUMBERDATA         =
      WAREHOUSENUMBERDATAX        =
      SALESDATA                   =
      SALESDATAX                  =
      STORAGETYPEDATA             =
      STORAGETYPEDATAX            =
      FLAG_ONLINE                 = ' '
      FLAG_CAD_CALL               = ' '
      NO_DEQUEUE                  = ' '
      NO_ROLLBACK_WORK            = ' '
    IMPORTING
       return                      = lt_return
    TABLES
       materialdescription         = ld_matdesc
      UNITSOFMEASURE              =
      UNITSOFMEASUREX             =
      INTERNATIONALARTNOS         =
      MATERIALLONGTEXT            =
      TAXCLASSIFICATIONS          =
      RETURNMESSAGES              =
      PRTDATA                     =
      PRTDATAX                    =
      EXTENSIONIN                 =
      EXTENSIONINX                =
      NFMCHARGEWEIGHTS            =
      NFMCHARGEWEIGHTSX           =
      NFMSTRUCTURALWEIGHTS        =
      NFMSTRUCTURALWEIGHTSX       =
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      WAIT          =
    IMPORTING
       return        = lt_return_comit

    hi
    Hope it will help you.
    <REMOVED BY MODERATOR>
    REPORT z34332_bdc_create_material .
    data: la_headdata type BAPIMATHEAD,
    la_clientdata type BAPI_MARA,
    la_CLIENTDATAX type BAPI_MARAX,
    la_return type BAPIRET2.
    data: i_materialdescription type table of BAPI_MAKT,
    wa_materialdescription like line of i_materialdescription.
    la_headdata-MATERIAL = '000000000000000004'.
    la_headdata-IND_SECTOR = 'M'.
    la_headdata-MATL_TYPE = 'FERT'.
    la_clientdata-BASE_UOM = 'FT3'.
    la_CLIENTDATAX-BASE_UOM = 'X'.
    la_clientdata-MATL_GROUP = '01'.
    la_CLIENTDATAX-MATL_GROUP = 'X'.
    wa_materialdescription = 'TEST'.
    append wa_materialdescription to i_materialdescription.
    clear: wa_materialdescription.
    CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
    EXPORTING
    headdata = la_headdata
    CLIENTDATA = la_clientdata
    CLIENTDATAX = la_CLIENTDATAX
    * PLANTDATA =
    * PLANTDATAX =
    * FORECASTPARAMETERS =
    * FORECASTPARAMETERSX =
    * PLANNINGDATA =
    * PLANNINGDATAX =
    * STORAGELOCATIONDATA =
    * STORAGELOCATIONDATAX =
    * VALUATIONDATA =
    * VALUATIONDATAX =
    * WAREHOUSENUMBERDATA =
    * WAREHOUSENUMBERDATAX =
    * SALESDATA =
    * SALESDATAX =
    * STORAGETYPEDATA =
    * STORAGETYPEDATAX =
    * FLAG_ONLINE = ' '
    * FLAG_CAD_CALL = ' '
    IMPORTING
    RETURN = la_return
    TABLES
    MATERIALDESCRIPTION = i_materialdescription
    * UNITSOFMEASURE =
    * UNITSOFMEASUREX =
    * INTERNATIONALARTNOS =
    * MATERIALLONGTEXT =
    * TAXCLASSIFICATIONS =
    * RETURNMESSAGES =
    * PRTDATA =
    * PRTDATAX =
    * EXTENSIONIN =
    * EXTENSIONINX =
    write: la_return-TYPE, ',', la_return-MESSAGE.
    clear: la_headdata, la_return, la_clientdata, la_clientdatax.
    Edited by: Alvaro Tejada Galindo on Feb 19, 2008 3:23 PM

  • XI Content for Material Master used by MDM

    Dear all,
    Where can I get the XI content for MDM 5.5 SP4 to receive the master data sent from ERP system?
    As far as I know, ERP sends two IDoc basic types (MATMAS and MDMRECEIPT). But why I cannot find at the URL https://websmp206.sap-ag.de/~sapidb/011000358700004672592006E?
    By the way, is it possible for ERP system to send master data via XI proxy instead of IDoc at the moment?
    Thanks + Best Regards
    Jerome
    null

    Hi Jerome,
    your link is refering to the XI content documentation. To download the XI content, please have a look at SAP <a href="http://service.sap.com/swdc">Software Distribution Center</a>. Follow the menu to "Download" -> "Support Packages and Patches" -> "Entry by Application Group" -> "SAP Netweaver" -> "SAP MDM" -> "SAP MDM 5.5". There you'll find everything you need for your system landscape setup.
    The standard extracors for materials do only support the IDocs in ERP.
    Kind regards
    Michael

  • CREATING MATERIAL MASTER USING BAPI-GROSS_WT VALUE IS NOT SEEN

    HI GUYS,
    I AM  CREATING MATERIAL MASTER USING BAPI_MATERIAL_SAVEDATA.I AM LOADING THE  VALUES FROM A FLAT FILE .
    THE VALUE FOR  GROSS_WT IS NOT SEEN WHEN THE MATERIAL IS CREATED.
    THE BAPI_MARM STRUCTURE HAD THE FILED BRGEW(GROSS_WT).
    I AM ABLE TO LOAD NET WT CORRECTLY BUT AM NOT ABLE TO LOAD GROSS WT.
    ANY SUGGESTIONS AS TO WHY THIS IS HAPPENING AND PROVIDE ME WITH A  SOLUTION.
    THANKS.

    Error: The numeric material number 1000000 was transferred without leading zeros for material: 1000000
    From next timepost only related code to make it look better.
    Use conversion exit for MATNR field.

  • What is the standard program for Material Master upload using LSMW

    Dear All
    I am trying to use the MM upload using DATMIG_INF4. I want to know what are the different standard projects that are used for Material master upload.

    Hi Amol,
    You can load the material master using direct input method  in LSMW ,details of which are as follows:
    Object               0020   Material master
    Method               0000                 
    Program name         RMDATIND             
    Program type         D   Direct input    
    Please revert back in case of any doubt.
    Cheers
    VJ

  • Step by step instruction for Using LSMW Recoding method for Material Master

    Guys,
    Can some one explain step by step procedure for uploading the materials master data to R/3 by using LSMW Recoding method. By the time you reply I will go through the rule of uploading the data..
    Thanks guys,
    Dhanu.

    Hi,
    The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
    The LSM Workbench covers the following steps:
    (1)Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files)
    (2)Convert the data from source format to target format
    (3)Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
    The Steps for LSME are:
    Example: Customer Master upload:
    LSMW to Update Customer Master Records with Transaction Recording
    Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC
    Step 1: Maintain Object attributes
    In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
    Step 2. Maintain Source Structures
    Give a name and a description to the source structure
    Step 3. Maintain Source Fields
    In this step, you need to list what fields are present in the source structure. The easiest way is to click on u2018Table Maintenanceu2019 icon to enter Fieldname, Type and Length for each field
    Step 4: Maintain Structure Relations
    Execute a step to u2018Maintain Structure Relationsu2019. Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
    Step 5: Maintain field mapping and conversion rules
    Field RF02D-D0310 represents that you chose u2018Sales viewu2019 for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of u2018Xu2019.
    If your source file already has the field value, you choose rule u2018Source Fieldu2019.
    Keep cursor on field u2018KUNNRu2019 and click on u2018Assign Source fieldu2019 icon to choose source field CUSTOMER from structure XD02S
    Step 6: Maintain fixed values, translations, user-defined routines
    You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
    Step 7: Specify files
    In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.
    Step 8: Assign files
    Execute step u2018Assign Filesu2019 and the system automatically defaults the filename to the source structure.
    Step 9: Read data
    In this step, LSMW reads the data from the source file (from your PCu2019s local drive). You have the option to read only selected rows and convert data values to Internal format.
    Step 10: Display read data
    This step is optional. If required, you can review the field contents for the rows of data read.
    Step 11: Convert data
    This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
    Step 12: Display Converted data
    Again this is an optional step to view how the source data is converted to internal SAP format
    Step 13: Create batch input session
    Once the source data is converted in an internal format, you can create a batch session to process updates.
    Step 14: Run Batch Input Session
    You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
    Follow the link for material master
    http://www.sap123.com/showthread.php?t=98
    Regards,
    Biju K

Maybe you are looking for