MM17 Mass Update Tool for Material Master.

Hi Gurus,
We have an appended material master field which was earlier added to the material master.
Now we want to add it as an update field into MM17 Mass Update Tool. But don't know how to do it. Please help.
Thanks in advance.

Hi ,
We are not still able to add that field as 'material updation field' in the field pool. Yes it is a Z field, and the concerned table name is MARC.
The SAP version is 4.6 C. We tried to find SAP Note and found one 576160. But it may not work. Could you please advice further ?
We want to add that field into the field pool which appears on clicking the "Select fields" tab.

Similar Messages

  • Could sap do mass craete/update for material master classification?

    Hi Expert,
      Now we craeted new classifcaiton for material master. It need be assigned to related many parts. May I query Could sap do mass craete/update for material master classification? How to do this ? 
    Thanks
    Alice

    Hi,
    Another option is using LSMW, please refer to below thread for more details:
    Classification view in MM01 with LSMW
    cheers,

  • BAPI for Material master update

    Hello,
    I need to upload and change data to the classification screen of Material master (MM01/02). I am thinking of using BAPI_CHARACT_CREATE and BAPI_CHARACT_CHANGE. Can we use BAPI_MATERIAL_SAVEDATA to upload and change characteristic data for material master(MM01/02)?
    Can anybody provide me some sample code for mass upload and mass change of characteristic data to material master?
    Thanks in advance
    Rajesh.

    Hi Rajesh,
    You can use standard SAP program <b>RCCLBI03</b> to do mass upload.
    Please check the program documentation for more information.
    Also you can take a look this BAPI/FM.
    <b>BAPI_OBJCL_CREATE
    BAPI_OBJCL_CHANGE
    CLVF_INSERT_AUSP
    CLVF_UPDATE_AUSP
    CLVF_VB_INSERT_CLASSIFICATION</b>
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Problem with mass IDoc for Material Master

    Hi All,
    Can anyone suggest a solution to work with mass IDocs for Material master?
    We have DEBMDM and CREMDM as mass capable IDocs for Customer and Vendor. How do we get mass Material Master IDocs from R/3 in a single XML file?
    Also the standard Material repository supplied with SAP MDM 5.5 SP3 doesn't have any XSD definition for MATMDM. Can anyone throw some light on this problem?
    Regards
    Pooja

    Hello Pooja:
    The standard way to do it is to generate a single file containing multiple idocs (And for the sake of performance, I suggest you stick to this technique).
    In the case of material master, everything is straight forward. In the case of customer and vendor master, when data flows from R/3 to MDM no idoc conversion needs to be performed by XI.
    However, for the case of customer and vendor master, when data flows from MDM to R/3, XI needs to separate the data in CREMDM to CREMAS and ADRMAS in order for R/3 to be able to process the idocs; as well as separate the data in DEBMDM to DEBMAS and ADRMAS.
    The good thing is that you do not need to worry about all this mappings and conversions in XI. The only thing you need to do in XI is to import the standard business content for SAP MDM 5.5 into XI.
    Hope this helps.
    Regards,
    Jorge.

  • Exit for Material Master UPdate

    Hi Friends,
    could anyone let me know any user exit for Material Master UPdate.
    Thanks in Advance
    Regards

    hi
    good
    MGA00001            Material Master (Industry): Checks and Enhancements
    MGA00002            Material Master (Industry): Number Assignment
    MGA00003            Material Master (Industry and Retail): Number Display
    thanks
    mrutyun^

  • Most use ful t code for Material Master changing

    Dear All,
    Can any one give me most useful T-codes for create, change and display material master.
    I have one T-code which is very useful for material master it is "MM50". With help of this tcode you can see material extend detail and also you can delete mass material with help of this tcode.
    So please use it and also give me other this type of tcodes.
    Regards,
    Mahesh Wagh

    Hi,
    MM17, LSMW, MM50 --- These are the 3 main transactions which is used frequently to Mass change the  Material master.
    There is one more option is there using BDC Upload.
    Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.
    The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.
    Transaction -- SHDB will be used to record the change material master. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.
    For a BDC upload you need to write a program which created BDC sessions.
    hope you got it. Take a help of  ABAPer for this BDC Upload.
    rgds
    Chidanand

  • 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

  • SRM and MDM for material master in SRM contracts for multiple R/3

    Dear all,
    my question is:
    We are implementing SRM 4.0 in classic scenario with multiple R/3 back-end and we want to set-up Global Outline Agreements in SRM in a multi-backend environment where the Material Master are not harmonized.
    We heard that MDM and COntent Integraton can be a solution.
    Then detailled question is:
    Can we have 2 material numbers (e.g. ABC and XYZ) in 2 different R/3 systems refering the same product.
    Have the mapping done in MDM (Content Integrator?) to a third material number:123
    Replicating the material master 123 to SRM from MDM(?)
    Create global Outline Agreements in SRM for Material Master 123.
    Distribute the GOA as Outline Agreement to R/3 system 1 with the translation to ABC and to R/3 system 2 with the translation XYZ, all of that during the distribution step (or another).
    Have the call-offs quantities correct on 123 in SRM and BW?
    IF yes, how is it working, do you have some documentation discribing the scenario and the config steps to do?
    Thanks in avance

    Hello RD,
    That's a good question.
    You are on the right way. MDM is the tool for you.
    But..
    Content Integrator (CI) was first developped for Shell, to address the need of cross-referencing of material/supplier/category IDs, for:
    - reporting purpose (actual Spend Analysis)
    - mapping purpose (send of XML PO)
    CI was later "fusionned" into the new MDM (1.0) solution.
    So now, you can not order CI without MDM (even if some SRM slides still present CI).
    But mapping API where developped for all inboud/outbound interfaces in SRM, for materials only (good luck for you).
    You will find everywhere this piece of code:
      Call ECI
        CALL FUNCTION 'BBP_PRODUCT_MAP'
          TABLES
            it_input          = lt_mapping_in
            et_output         = lt_mapping_out
          EXCEPTIONS
            logsys_not_found  = 1
            driver_not_found  = 2
            product_not_found = 3
            internal_error    = 4
            OTHERS            = 5.
    So it is ok, you have the mapping call, but I don't know if all the rest of the process was really "finalized" (call of API mapping in CI, via XI). I personnaly never used it, but I assume it should work.
    I my opinion your process is supported by SAP:
    - Extract materials from both R/3 and consolidate them as a single product in MDM.
    - Distribute this product into SRM.
    - Maintain contracts on those products.
    - Distribute them to R/3 (The ECI call is also used during contract distribution).
    - Call offs corrects in SRM and BW
    For MDM documentation, look at netweaver area of service.sap.com.
    For MDM/SRM integration, look at SRM 4.0 spend analysis:
    https://websmp206.sap-ag.de/~sapdownload/011000358700004424262004E/GlobalSpendOverview.ppt
    For SRM contract distribution, call-offs, BW, look at SRM in details in service.sap.com/srm/SRM4.0:
    https://websmp206.sap-ag.de/~sapdownload/011000358700001966382004E/contracten.ppt
    For SRM5.0, see online help on help.sap.com.
    Rgds
    Christophe

  • Uploading sales text and Purchase order text for material master

    Hi,
      I have created, material master with LSMW  byt not updated SALES TEXT and Purchase order text with LSMW  now i want to uplaod the sales and po text for material master can you give some link or ref. code to upload the text i have near 1000 items for which i want to uplaod text  when i have done the recording with SHDB  i have not found filed in recording.
    regards,
      zafar

    Hi,
    I have made the code in se38
    as below but still it is not working
    REPORT  ZTEST_TEXT.
      data: headerl like thead occurs 0 with header line.
      data itab3 like tline occurs 0 with header line.
    headerl-tdobject = 'MATERIAL'.
    headerl-tdname = '00000000000LSMW123'.          "(Material : 000000000300000560, Sorg : 0001, Dist channel: 01)
    headerl-tdid  = 'BEST'.
    headerl-tdspras = 'E'.
    append headerl.
    move '*' to itab3-tdformat.
    move 'Testing PO text' to itab3-tdline.
    append itab3.
    call function 'SAVE_TEXT'
      exporting
        header                = headerl
      insert                = ' '
       savemode_direct       = ' '
      tables
        lines                 = itab3
    exceptions
       id                    = 1
       language              = 2
       name                  = 3
       object                = 4
       others                = 5.
       IF SY-SUBRC = 0.
         CALL FUNCTION 'COMMIT_TEXT'
           EXPORTING
                OBJECT   = headerl-tdobject
                NAME     = headerl-tdname.
       ENDIF.
       break-point.
    regards,
    zafar

  • How is the Consumption tab will update in the material master?

    Hi Friends,
    How is the Consumption tab will update in the material master?
    what are the customization required if consumption tab wants update with respective the qty?
    Regards,
    Hari Shankar

    Hi Friends ,
    I am very thankful to u all for your quick response,
    I have tested the two materials with two movement types of 601 and 954.
    when i did the 601 movement type the consumption tab in the material master has updated automatically even though  i haven't maintained forecasting tab, but where as for the movement type 954 the consumption tab is not updated even though i have maintained forecasting tab view in the material master.
    Is the consumption view will update based on the Material movement types?
    where is the control parameter for updating consumption tab?
    could you pls help me regarding this?
    Regards,
    Hari Shankar.

  • 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

  • Updating values in material master table

    Hi,
    I have a requirement where in which if the user wants to change the value of some fields of a particular record in the o/p,then he checks the checkbox of that record and click on the change button.Then the control goes to the update screen.There are many fields present in the update screen and also checkboxes were present beside each field.The user can change the values of the fields here and click on th execute button.Then only the checked field values should get updated in the material master table.
    Can anyone tell me how only the checked field values can be updated in the material master table

    are you attempting to program the standard transaction MM17 all over again?

  • Need to create a Store Business document type for material master and store a sharepoint link

    Hello,
    I need to create a Store business document type for material master and store a URL link . How do I do that?( or is there any functionality to upload a document for a  store business document that it will automatically saves to sharepoint?)
    Thanks,
    Ran.

    >
    dhayes12 wrote:
    > A)  When I do the (Material Backflush) MFBF for the 04 type, the Inspection Lot gets created OK.  I then can go into QA32 and assign the correct Inspection Plat by clicking the Inspection Lot button.
    >
    > B)  When I do the MIGO via the Purchase Order (type Z01), it will not create the Lot if I have the Multiple Specs selected in the QM Material Master MM02.  If, I turn off the Multiple Specs in the QM Material Master and create a new PO and MIGO, it will create the Lot, however, it automatically assigns the lot to the wrong Inspection Plan (2nd Plan see above)  I need to be able to select the plan like I can with the 04 type.
    >
    > Is their some setting that can be changed in Config or somewhere that acts the same way as example A above?
    For case A, create insp plan with usage "1- production" If you have one IP with this usage for given material then system will assign Plan to lot automatically. In your case for second plan update usage as 1.
    For case B, system should assign 1st plan make sure for both plan udage is correct. for 1st plan usage should be 5 while 2nd plan usage should be 1. Now if your 1st have status 4 and key date before lot date then system will assign plan auto.
    Thanks!!!

  • Search Group for Material Master

    Hi,
    Can any one tell me how to configure a new search group for Material master.
    For eg. I would like to search a material on the basis of Material type/Plant.
    Thanks & Regards
    Merwyn

    Hi
    Please try by adding the Fields material type in the transaction OMSH,
    SPRO -> IMG-> Logistics - General-> Material Master-> Tools-> Maintain Search Helps
    Read the Documentation of the Customzing before procedding futher.
    Thanks & Regards
    Kishore

  • User Exit or BADI for Material master

    When save in MM1 or MM02,  we need a user exit or Badi to <u><b>get ECM data</b></u> (which is saved in AENR or AEOI table). Please help for this.

    Hi Krishna,
    Enhancement/ Business Add-in            Description
    Enhancement
    MGA00001                                Material Master (Industry): Checks and Enhancements
    MGA00002                                Material Master (Industry): Number Assignment
    MGA00003                                Material Master (Industry and Retail): Number Display
    Business Add-in
    MG_MASS_NEWSEG                          User-Specific Fields & Segments in Mass Maintenance
    MATGRP_SKU_UPD
    CDT_CHECK_MATERIAL                      Checks for Existence of a Material in a CDT
    BADI_MM_MATNR
    BADI_MAT_F_SPEC_SEL                     BAdI for Material Special Field Selection
    BADI_MATNR_CHECK_PVS
    BADI_MATERIAL_REF                       Addition of customer-defined default data for material
    BADI_MATERIAL_OD
    BADI_MATERIAL_CHECK                     Enhanced checks for material master table
    BADI_GTIN_VARIANT
    BADI_EAN_SYSTEMATIC
    o.of Exits:          3
    o.of BADis:         11
    These ar ethe avilable exits and badis.
    Rgds,
    P.Naganjana Reddy

Maybe you are looking for