Recording MM03

calling of  MM03 transaction From Report pgm giving the Material as I/P
but while recording MM03 and and after executing the small icon(service for objects) that appear on the side of heading is not appearing .since that icon is needed for attachement .Kindly help.
Thanks in Advance.

Hi Mr:Nagaraju,
In SHDB before start your recording, select the check box for <b>Not a Batch input session</b>  in <b>recording parameters</b>. Now start recording, your required icon will be available for recording
Regards,
Antony Thomas
reward points if find helpful.

Similar Messages

  • Regarding recording issue in MM03

    Hi All,
    I am trying to record MM03 transaction in SHDB.
    Please find below the sequence of screens:
    MM03 -> Basic data -> System Menu -> Services for object -> Create External Document.
    Now, the problem is when i am entering the system menu in SHDB, it is showing the Serivces for object menu item disabled. However, when i go into the same through MM03, it is allowing us to create the external document.
    We have got all the authorizations in the system.
    Any pointers to this will be highly appreciated.
    Thanks and regards,
    Mayukh.

    Hi !
    aaahhh - not I've got really what you're doing...
    Using the "System" menu, you're trying is a function that's not specific to the transaction you've called. It's using the "GOS" (=Generic Object Service).
    (It's the ICON in the "whit line" above the buttons ... please try that !)
    Maby they are genereally not possible in your system ??
    You should ask one of your BASIS experts for that.
    As I remeber the system needs a "content-server" defined for using the GOS ....
    In our system it's definitely working for the MM02.
    Regards
    rainer
    Some reward points would be nice if that helped a bit.

  • Doubt on bdc's

    i was trying my first bdc program. i wanted to record mm03 transaction.
    so i went to tcode SHDB, pressed new recording, gave a recording name and t-code mm03 and
    started recording. it asked for material number, i just entered one and pressed back to stop recording.
    i saved it. then i selected my recording name and pressed on function module to see the code generated.
    is this how u do it. does all BDC programs work just by starting with SHDB or its not needed. should a BDC
    be written in se38 or se37.
    can any bdc program be written without ever recording.

    Example:
    data:  begin of bdcdata occurs 10.
            include structure bdcdata.
    data:  end of bdcdata.
    form post_goods_issue  tables   p_processing_protocol
                           structure ws_processing_protocol
                           using    p_temp_vbeln.
      clear bdcdata. refresh bdcdata.
      perform bdc_dynpro using 'SAPMV50A'      "Change Outbound Delivery
                               '4004'.
      perform bdc_field using 'LIKP-VBELN'     "Delivery number
                               p_temp_vbeln.
      perform bdc_field using 'BDC_OKCODE'
                               '=WABU_T'.      "PGI button
      perform bdc_dynpro using 'SAPMSSY0'      "Log screen
                                '0120'.
      perform bdc_field using 'BDC_OKCODE'     "Back
                                 '=BACK'.
      perform bdc_dynpro using 'SAPMV50A'      "Change Outbound Delivery
                                  '4004'.
      perform bdc_field using 'BDC_OKCODE'     "Back
                              '/EBACKE_T'.
      clear attempts.
      do.
        clear msgtab. refresh msgtab.
        bdcmode = 'N'.
        call transaction 'VL02N' using bdcdata mode bdcmode update 'S'
        messages into msgtab.
           Start new screen                                              *
    form bdc_dynpro using program dynpro .
      clear bdcdata.
      bdcdata-program  = program.
      bdcdata-dynpro   = dynpro.
      bdcdata-dynbegin = 'X'.
      append bdcdata.
    endform.                    "bdc_dynpro
           Insert field
    form bdc_field using fnam fval.
      clear bdcdata.
      write fnam to bdcdata-fnam .
      write fval to  bdcdata-fval.
      append bdcdata.
    endform.                    "bdc_field

  • WRONG BATCH DETERMINATION - SALES ORDER AND DELIVERY

    Dear Experts,
    We have setup Batch Management in our company. The system do the automatic batch determination, but there is a problem.
    If there is an expired batch on unrestricted stock, the system will take it.
    I've have checked the selection criteria on the batch search strategy and there is the ">= 30 d" value in the LOBM_RLZ characteristic
    But it simply let the expired batch pass.
    Do I am missing something?
    Please Help
    Javier Sandoval Vera
    Ecuador

    Fields in the Material Master Record  (MM03) please check the mateirl master                                                                               
    In the material master record, the following fields are relevant for the shelf life expiration date check:                                              
    o  minimum remaining shelf life                                                
    o  Total shelf life                                                            
        -  If you do not enter a total shelf life, you directly enter the shelf life expiration date with the goods movements.                     
        -  If you enter a total shelf life, you enter the production date with the goods movements. The system automatically calculates the shelf life expiration date on the basis of the production date plus shelf      
           life.

  • Open a Particular view in MM03

    Hi all
    I want to open the MRP4 view of MM03 (directly) by passing the value of Material plant & Storage loc to the tcode.
    I have tried using the BAPI -> MATERIAL_MAINTAIN_DIALOUGE, but it opens the MRP1 view
    any pointers will be helpful.
    Regards
    Ravish

    Hi.
    You can try a simple batch-input in mode N. Do a recording in SM35 and create the batch-input.
      PERFORM bdc_dynpro TABLES my_bdc USING 'SAPLMGMM'   '0060'.
      PERFORM bdc_field TABLES my_bdc USING 'RMMG1-MATNR' '91'.
      PERFORM bdc_field TABLES my_bdc USING 'BDC_OKCODE'  '/00'.
      PERFORM bdc_dynpro TABLES my_bdc USING 'SAPLMGMM'   '0070'.
      PERFORM bdc_field TABLES my_bdc USING 'MSICHTAUSW-KZSEL(15)' 'X'.
      PERFORM bdc_field TABLES my_bdc USING 'BDC_OKCODE'  '=ENTR'.
      PERFORM bdc_dynpro TABLES my_bdc USING 'SAPLMGMM'   '0080'.
      PERFORM bdc_field TABLES my_bdc USING 'RMMG1-WERKS' '1001'.
      PERFORM bdc_field TABLES my_bdc USING 'BDC_OKCODE'  '=ENTR'.
        CALL TRANSACTION 'MM03'
            USING my_bdc
            MODE 'E' UPDATE 'S'.
    FORMS ---
    FORM BDC_DYNPRO ------------------------------------------------------
    Creates a dynpro line: program - screen no
    <->  PT_BDCDATA
    -->  PW_PROGRAM   Program name
    -->  PW_DYNPRO    Screen number
    CHANGES: SY-TABIX
    form bdc_dynpro tables pt_bdcdata structure bdcdata
                     using pw_program pw_dynpro.
      clear pt_bdcdata.
      pt_bdcdata-program = pw_program.
      pt_bdcdata-dynpro  = pw_dynpro.
      pt_bdcdata-dynbegin = 'X'.
      append pt_bdcdata.
    endform.                                                   " BDC_DYNPRO
    FORM BDC_FIELD -------------------------------------------------------
    Creates a field line: field name + value
    <->  PT_BDCDATA
    -->  PW_FNAM      Field name
    -->  PW_FVAL      Field value
    CHANGES: SY-TABIX
    form bdc_field tables pt_bdcdata structure bdcdata
                    using pw_fnam pw_fval.
      clear pt_bdcdata.
      pt_bdcdata-fnam = pw_fnam.
      pt_bdcdata-fval = pw_fval.
      append pt_bdcdata.
    endform.                                                    " BDC_FIELD
    Reward if it helps,
    Regards,
    George

  • Collection of Error Messages of un-uploaded records while running RFBIBL00

    Hello all,
    I prepare an LSMW program to populate GL items data using standard program RFBIBL00 with Direct Input method.
    For instance, I have converted 10 records, among which 5 are valid; 5 get denied due to some reasons. Where exactly can I find the log of records which got denied due to xyz reason with message.
    Thanks in advance.

    please check this
    check all perform bdcfield correct or not....
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'RMMG1-MATNR'
    wa_final-matnr.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
    'X'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'BDC_CURSOR'
    'MARA-BISMT'.
    perform bdc_field using 'MARA-BISMT'
    wa_final-bismt.
    perform bdc_dynpro using 'SAPLSPO1' '0300'.
    perform bdc_field using 'BDC_OKCODE'
    '=YES'.
    perform bdc_transaction using 'MM02'.
    perform bdc_dynpro using 'SAPLMGMM' '0060'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_dynpro using 'SAPLMGMM' '0070'.
    perform bdc_field using 'BDC_CURSOR'
    'MSICHTAUSW-DYTXT(01)'.
    perform bdc_field using 'BDC_OKCODE'
    '=ENTR'.
    perform bdc_dynpro using 'SAPLMGMM' '4004'.
    perform bdc_field using 'BDC_OKCODE'
    '/00'.
    perform bdc_field using 'BDC_CURSOR'
    'RMMG1-MATNR'.
    perform bdc_dynpro using 'SAPLSPO1' '0300'.
    perform bdc_field using 'BDC_OKCODE'
    '=YES'.
    perform bdc_transaction using 'MM03'.

  • Problem in custom fields in mm02/mm03

    Hi folks,
    i want to add the custom fields in mm01.iam able to add and update database.but iam facing problem in when iam checking the particular material in mm02/mm03.the custom field data is not correctly.for every material the last custom field data is showing. in database it is updating correctly but in mm02/mm03 it is displaying incorrectly.
    By the following code i can able to display the data in mm02/mm03.but my problem is the last created custom field(model) data is showing for all the materials when iam checking in mm02/mm03.
    here my custom field is "MODEL"
    for eg matnr-10 model -xx.
    matnr-20 model-yy.
    if iam checking in mm02/mm03 for matnr-10 model-yy it is displaying.in database it is updating correctly.
    can u please tell me how can i write a code to select the custom data(model data) for that particular material.
    Module get_data.
    if sy-tcode = 'MM02'.
    select single model into mara-model from mara
    where matnr = mara-matnr.
    elseif sy-tcode = 'MM03'.
    select single model into mara-model from mara
    where matnr = mara-matnr.
    loop at screen.
    if screen-name = 'MARA-MODEL'.
    screen-input = 0.
    modify screen.
    ENDIF.
    endloop.
    endmodule.
    Thanks in advance,
    Neelu.

    Just read the OSS note mentioned earlier.
    Symptom
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
    Solution
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
    Regards

  • SQVI - Material to Document Info Record

    I am trying to create a query that gives me
    Material Number <b>(I tried MARA and MARC but MARA wont join and MARC produces no data when ran)</b>Document Type (DRAW-DOKAR)
    Document Number (DRAW-DOKNR)
    Document Status (TDWST-STABK)
    Once I have these I can create a report that shows me all materials that are not at a release status. I know 90% of the tables I need but when I create a join using the Document Info Record (DRAW) and any of the material master records MARA, MARC, MAKT, MEBW I end up with a join that doesn't work or a join that doesn't have a similar key to run.
    Any ideas?

    When you go into MM03 and look at any material and then go to the additional
    data tab and then select document data that gives you the documents associated with a part. If you then double click on any document that gives you the document status.
    I am trying to create a report that gives me all open production orders - the parts on that production order (which I can do) and then for every part to see which have documents that are on a certain status.
    Example you may be creating an assembly and the drawing on the document went from a 2 hole gidget to a three hole gidget. Well - production people don't know that the document has been re-issued and is being reviewed. This way they can run a report that shows them which parts on the Production Order are currently in review so they should not waste time a money on an assembly if the design is being tweaked.
    Because you can get to the document status from the material master there must be a link. I don't know where that is. I tried MARA, MARC, MKPF and MSEG and nothing links with the document. But there must be something that triggers that the document is attached to certain part.
    I just need to know what table that is......

  • Error material not maintained by purchasing when creating info record

    Hi Expert,
    I have an issue when creating info record, error says "Material ******* not maintained by purchasing". I've checked in MM03 purchasing view, all has been maintained and at the bottom there is message says "No plant-specific data exist". Accounting view also maintained. I've also checked in MARC table for this material and plant. It existed. I cannot see anything wrong on the material master setup but not sure why am i having this error...
    Please help.
    Thanks,

    Hi,
    Error says "Material ******* not maintained by purchasing" & you checked purchasing view has been maintained.
    OK. Just cross check following optionS
    Option-1: You creating info- record for material with combination of plant & vendor....check did the material have purchasing view for same  plant-the info-record you are creating!
    Option-2: If no purchasing view for material with same plant , just extend in t.code MM50 for E     Purchasing
    Option-3: Check the material for same plant, did Procurement type F (External procurement) is there
    Option-4: Check Profit Center in Plantdata/ sto-2 view of material.
    Regards,
    Biju K

  • Is there any field on waste packaging information in MM03

    Please help me in finding any field on waste packaging information in MM03. If it is there please let me know in which view we can find it, if not let me know where else i can find information on Waste packaging.

    Hi Vinod,
    If i got you right,  you need the information on Packing material in material master, if this is the case then go to
    Material Master - Basic data1- Packaging Material Data here you get to see
    1) )Material group packing material -  here grouping of materials which require same kind of packing is done.
    2)  Reference material for material packing - here material number is given which is to be packed with the similar packing and there should be a material master record for the reference material.
    3) Product composition - if you check ithis tab then composition gets  printed on packing      
    For example - say you have two material X(glass bottles) and y( glass jars) since these two are one of a kind they require same kind of packing.
    hope this will help you
    Thanks
    Abdul

  • Document Info record history, evaluation needed

    Hello
    i have attached a document 4711  to a notification A or any other object. I save this document info record. it is available. Now i go into the notification again and delte this allocation.
    Now the someone wants to know which documents have been attached to the notification at whhat point in time ?
    Is there any evaluation existing which pases this information in a efficient way. The issue is that I only know the Object it has been allocated to and not the DMS object.
    Any idea how to solve this?
    Stephan Bantlin

    Hi Stephan,
    from DMS point of view I can only recommend you to use the 'Display Changes' functions for a document info record in menu "Environment". This will show all the changes for the selected document info record. The report behind this functionality is called MCDOKABL.
    The same functionality is also available in object transactions like MM03 for example.
    Best regards,
    Christoph

  • Enhancement in MM03

    Hi,
    In MRP view - General Data of MM03 i want to add a field just below ABC indicator.
    Please tell me how i should do this as this is the first assignment i am doing on enhancements.
    Regards,
    Darpana.

    Hi,
        Go to transaction SE51. Give program name and screen no you want to modify. Select Layout Editor radio button and  in change mode, Click On Dictionary Program fields window icon. If you need a custom variable on screen, give variable name and click on Get from Program.Select record and click OK..save and activate it.But you need access key for this.
    I think it may solve your problem.
    regards,
      JP

  • Net weight in unit of measure (MM03)

    Hi,
    I have to extract all the units of measure for an article and i was wondering where does this field (Net weight) come from.
    I think it's calculated but how ?
    Allready have some other fields from MARM and find the net weight in mara but as i have many lines of untis of measure, the mara net weight does not apply to all.
    Thanks

    Thank you again for your time.
    I'm trying to extract all datas from that screen so the access to the screen is MM03 or MM02 (i checked and they both have same datas) if that was your concern.
    I see those two fields (Number of Lower-Level Units of Measure (SMEINH-AZSUB) and Lower-Level Unit of Measure in a Packing Hierarchy (SMEINH-MESUB), at the end of both records under Number and LUn as you can see in that screen copy
    http://img354.imageshack.us/img354/3219/sanstitredx2.jpg
    i found a fm (BAPI_MATERIAL_GETALL) that returns the weight for every record so the weight is not a problem anymore for my report. Even if i don't understand why i can change some lines and can not others.
    But i really can't find those two last column
    Edited by: Alan Ford on Jul 10, 2008 2:27 PM

  • Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

    Good day to all of you!
    I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
    In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
    I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
    MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
    1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
    2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
    PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
    All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
    Any help, pls?
    Good day and thank you!

    Hi Alex,
    In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
    http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
    and
    Just read the OSS note mentioned earlier.
    Symptom
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001 
    Solution
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F): 
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
    check this link. It may helps you to solve your issue.
    Thanks
    Sravan

  • Search result problem in material master (MM03)

    When I use either of the default text searches provided in MM03 (Advanced Search for Material Using Search Engine or Quick Search for Material using Search Engine), I get correct results from the search.   However, the first column in the results table, Material code, is blank for all the records.  All the other searches work correctly, but these two don't return the Material code, which is obviously required for this to be an effective search. 
    This seems like a bug.  Anyone else seen this?

    ABAP team said it was an SAP problem and they needed to send a fix.  Started a call with SAP and they're saying it's something we did in configuring it.  I never configured it.  Wouldn't know where to go.
    Is there configuration for the Advanced Search Engine?

Maybe you are looking for