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

Similar Messages

  • Problem Adding Custom Field to Service Process Screen

    Hi Folks,
    I'm a dinosaur ABAP developer whose been asked to create a custom field to appear on the Business Transaction service process (Support Message) initial selection screen.
    I've created the field and generated the necessary objects via the EEWB transaction.  The client has created a Z* transaction type.
    Could someone please instruct me how to get the custom field onto the Z transaction selection screen? 
    Points rewarded for a successful instructions.
    Cheers,
    Steve

    Hi Stephen,
    If you have overcome this problem and have any documentation that you can share, please send me at [email protected]
    I am having a similar requirement and would be very grateful for your help.
    Thanks & regards,
    Srini

  • Problems with custom fields

    HI all,
    I've worked in several projects with SRM 7.0 and when I add custom fields to SC, PO... I do always the same steps and works fine. But in my new project is not working, the fields are not displayed in portal and I don't know why.
    The step I've followed are:
    SPRO:
    SAP Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) :
    - Configure Customer Fields -> Define Customer Fields on Item Level:
    I've added the fields in the structures: INCL_EEW_PD_ITEM_CSF and INCL_EEW_PD_ITEM_CSF_SC.
    - Configure Field Control -> Configure Control for Fields on Item Level -> Metadata for Fields on Item Level:
    I've added my fields there, with the correct Obj. type and I've checked Enabled and Visible. (I haven't dynamic classes)
    With this the fields must appear in portal, but aren't displayed...
    It's strange because I've even added one of these fields manually in the component /SAPSRM/WDC_DODC_SC_I_BD, adding a label and an input field, and I can see it in the layout but not in portal...
    I've tried also to add some entries in SPRO in "Configure Generic Field Display on User Interface" but still not working...
    I've checked also the component configuration and it seems it's all ok.
    Any idea what's happens ?
    Thanks in advance.

    Hi Ricardo.
    I got the same issue as you described. I try to add a custom field to SOCO in SRM 7.0.
    I followed your instructions as below and those are done:
    "Configure Customer Fields -> Define Customer Fields on Item Level:
    I've added the fields in the structures: INCL_EEW_PD_ITEM_CSF and INCL_EEW_PD_ITEM_CSF_SC.
    - Configure Field Control -> Configure Control for Fields on Item Level -> Metadata for Fields on Item Level:
    I've added my fields there, with the correct Obj. type and I've checked Enabled and Visible. (I haven't dynamic classes)
    With this the fields must appear in portal, but aren't displayed..."
    The issue starts from here:
    "With this the fields must appear in portal, but aren't displayed..."
    How did you solve the problem , what was the customizing issue of you?

  • Add custom fields in header of FI documents using FI_HEADER_SUB_1300IM

    Hi
    We are trying to add a couple of custom fields in header area of FB01 by making a copy of badi FI_HEADER_SUB_1300IM. With this method we are facing a couple of problems
    - The custom fields added in bkpf structure,  only appears in FB01 just in the case we have go before to FB03 or FB02.
    - We don´t reach to save data of these fields in table BKPF.
    can anybody help us with these problems?
    thanks in advance for your help
    I leave here the code we have used in the copy of badi FI_HEADER_SUB_1300IM
    MODULE d1300_pbo OUTPUT.
      IF exit IS INITIAL.
        CALL METHOD cl_exithandler=>get_instance_for_subscreens
          CHANGING
            instance                      = exit
           EXCEPTIONS
    *      NO_REFERENCE                  = 1
    *      NO_INTERFACE_REFERENCE        = 2
    *      NO_EXIT_INTERFACE             = 3
    *      DATA_INCONS_IN_EXIT_MANAGEM   = 4
    *      CLASS_NOT_IMPLEMENT_INTERFACE = 5
             OTHERS                        = 6.
        IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
      ENDIF.
      CALL METHOD exit->get_data_from_screen_pbo
        EXPORTING
          FLT_VAL       = 'ES'
        IMPORTING
          ex_bkpf       = g_bkpf
          ex_x_no_input = g_no_input.
      loop at screen.
       if g_no_input = 'X'.
         screen-input = 0.
         modify screen.
       endif.
      endloop.
    ENDMODULE.   
    **************************+
    FORM put_value .
    * import header data from main screen
      call method exit->get_data_from_screen_pai
        EXPORTING
          FLT_VAL  = 'ES'
        importing
          ex_bkpf  = g_bkpf.
    * set reference fields
    g_bkpf-ZZDPTOAPROBADOR = bkpf-ZZDPTOAPROBADOR.
    g_bkpf-ZZDELAPROBADOR = bkpf-ZZDELAPROBADOR.
    * put data to main screen
      call method exit->put_data_to_screen_pai
        exporting
          im_bkpf  = g_bkpf
          flt_val  = 'ES'.
    ENDFORM.
    Added code tags
    Edited by: Rob Burbank on May 10, 2011 12:17 PM

    SriVarma,
    Cool! I didn't know this BADI!
    Playing around with existing implementations I can see that, BADI_SD_TAB_CUST_H, can definitely enhance the Sales order header with additional tab strip screens. Similarly BADI_SD_TAB_CUST_I can be used to enhance Sales order item screens.
    Here is what I understand from the coding of an existing implementation
    ACTIVATE_TAB_PAGE - takes a module pool program name and a subscreen that you created and adds it as a additional tab page to sales order header screen. You need to pass back f_program and f_dynpro with your program and screen number that you painted
    TRANSFER_DATA_TO_SUBSCREEN - can be used to read and pass data to the fields on the subscreen you created
    TRANSFER_DATA_FROM_SUBSCREEN - can be used to pass back whatever changes done by user to the respective Z variables in VBAK
    PASS_FCODE_TO_SUBSCREEN - Pass the fcode the user selected to your subscreen.
    I would suggest that you create a function group and create screens, functions etc within that and use those in these methods. Refer existing implementations. The global data of the function group can then be used to communicate between all the above methods

  • Custom Field not showing in analytics?

    We have a custom field on the account object called sales stage. It is a simple pick list (our organization does not use the opportunity object). The custom field is not available in analytics. Is there something on the field setup that needs to be flagged? All of our other fields seem to appear just fine. This is so bizzarre!!
    Any help is greatly appreciated.

    Hm. Still no answers.
    We have a similar problem concerning custom fields not available in Answers. It concerns a custom field for an additional tel no. in the user record type. I thought it might have something to do with the fact that it can only be utilized through the other data types, using "owned by user".
    But as you have the same problem, maybe there is a solution... Any idea would be appreciated.

  • Bidding Engine - Customer Fields

    Hi Experts,
    I hope it will be the last question in terms of the bidding engine.
    I have a problem with Customer Fields, if is start the Web GUI in english, I have no problems - every field have a normal description (Field 1: Additional Address 1; Field 2: Additional Address 2). On friday I started it in another language (in this case german), the fiedls now called zcontact1 and zcontact2.
    I started to analyse the HTML Code for this part and find the area.
    It begins with:
    <!-- START:  Customer Fields                           : Template   0100 -->
    <!-- -INCLUDING FUNCTIONS... - -->
    I try to find this template in se80 but I still find the original templates.
    Could anybody help me to solve the problem?
    Best regards and a nice weekend!
    Andi

    Hello Kalandi,
    I think I know what you mean - but I do not find the table, where I can change it. I think about it, to deactivate the fields in general - but it was not me, who added them
    Best regards and a good night!
    Andi

  • 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

  • Custom fields data in mm02/mm03 is not showing

    Hi,
      My requirement is to add custom fields to mm01 and update the database.but at the same time if i check the material in mm02/mm03 the custom field data also should show.
    iam able to update database.my custom fields data is not showing if iam checking in mm02/mm03.
    Please help me how can i do this.
    Thanks in advance,
    Neelima.N

    Hi folks,
      can u please help me out.
    By the following code i can able to display the data in mm02/mm03.but my problem is the last created customer field(model) data is showing for all the materials.
    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 zfield data for that particular material.
    Module get_data.
    if sy-tcode = 'MM02'.
        select single model into mara-model from mara
                  where matnr is not null.
    elseif sy-tcode = 'MM03'.
        select single model into mara-model from mara
                  where matnr is not null.
      loop at screen.
      if screen-name = 'MARA-MODEL'.
       screen-input = 0.
       modify screen.
       ENDIF.
      endloop.
    endmodule.
    Thanks,
    Neelu.
    Edited by: neelima natta on Feb 26, 2009 2:02 PM

  • Error in adding custom fields to mm01/mm02/mm03 trx

    Hello People,
    To add my custom fields in the basic view tab of MM01 transaction, i have performed the following steps:-
    1. Inserted the append structure in MARA table with the required fields.
    2. Copied function group 'MGD1' to 'ZMGD1' and then set the layout of screen '0001' as per my requirement.
    3. Then i made changes in spro as
         SPRO->Logistics-General->Material Master->Configuring the material master->define structure of data screens for each screen sequence and inserted my program name( of function group 'ZMGD1') and screen number(0001) in 21(Std ind.(short) tab pages)->7(Basic Data 1)->8(sequence).
    Now, if i click on SPRO option (view data screen), then i can see my fields added in basic data view...
    but when i execute 'MM01/MM02/MM03' trx  there my added fields do not appear....
    Does anyone know where i am missing out??
    Please suggest...
    Thanks in advance..
    Rgds,
    Abhi

    Here are some notes I have from when I recently added a new screen/subscreen to Material Master transactions.  Hopefully this information will help you.
    This guide should be used in conjunction with OSS note 44410 and IMG notes Logistics->Logistics Material Master->Material->Configure Customized Material Master.
    Online Maintenance.
    1. Add fields to append structure ZAEMARA.
    Use data dictionary maintenance u2013 SE11
    2. Generate table MARA.
    3. Add fields to view MARU and generate.
    Use data dictionary maintenance u2013 SE11.
    4. Create new sub-screen or add new fields to screen SAPLYMM1 9001.
    Use Screen Painter u2013 SE51.
    Change flow logic to add fields to field: statement and to add any validation required. Generate screen.
    If this is the first time additional data has been added to material master it will be necessary to create a new function group and associated programs. See Configure Customised Material Master paragraph Requirements.
    5. If new sub-screen, add to Customer main screen.
    Transaction OMT3.
    Double click on u2018Std industry sequenceu2019.
    Choose customer screen and Details.
    Change the first occurrence of 0001 (blank screen) to new screen number.
    Save.
    Back arrow.
    Click on Transport button and choose required transport.
    6. To include in 'Copy with Reference' processing - MM01, add new MARA fields to table T130F. (in each client)
    Use Transaction SM31. (make a copy of another ZZ field by typing over existing name).
    Add to transport manually:- R3TR TABU T130F + individual keys
    7. Test Material create, change, display.

  • Add custom field in MRP area-MRP 2 in material master(MM01/MM02/MM03)

    Hi
    As per my requirementn we have to add one field in the Material master(MM01/MM02/Mm03). Mentioned path below.
    MM01/MM02)--> MRP1 tab --> in the MRP areas > click on MRP AREAS button>Pop will come with MRP AREA --> double click on entry > MRP area screen will appear> In MRP2 data tab> i've to add a new custom field. Program Name> SAPLMD_MGD1
    Screen --> 0040
    Is there any exit/customization which can be used to do this?
    i was unable to find a exit for the same.
    Thanks,
    Gauri

    Hi Gauri,
    See Note 44410 - Integrating cust.-specific fields in matl master, I think that it will help you
    Regards
    Eduardo

  • Custom field not updating in MARC table by mm01/mm02/mm03

    Hi,
    I have created a sub screen in Plant storage 2 of MM01 tcode with a custom field.  The field is visible in the screen but the value is not getting updated in the MARC table.  We can update the MARA table through the exit of MPA00001 but there is no option for updating the MARC table.  Please let me know if there are any options.

    HI Geeta,
    Chek this
    DATA: H_ZE1MARCM LIKE ZE1MARCM.
    IF F_CUST_SEGMENT-SEGNAM EQ 'ZE1MARCM'.
      H_ZE1MARCM = F_CUST_SEGMENT-SDATA.
      IF H_ZE1MARCM-ZMYFIELD = C_NODATA.
        CLEAR H_ZE1MARCM-ZMYFIELD.
      ELSE.
        IF H_ZE1MARCM-ZMYFIELD IS INITIAL.
          RES_FIELDS-FELDNAME = 'MARC-ZMYFIELD'.
          APPEND RES_FIELDS.
        ENDIF.
      ENDIF.
      F_MARC_UEB-ZMYFIELD = H_ZE1MARCM-ZMYFIELD.
    ENDIF.
    Given By Lars,
    Regards,
    Madhu.

  • Add custom field to MAKT to get a larger descritpion in MM01/MM02/MM03

    Hi, I already know how to add a new field to MARA and show/maintain it at MM01-03 transactions using this procedure (copied from another thread):
    Create the append structure on the MARA table.
    The SAP note 44410 describes how to add the new fields to the screen and how the updating will work.
    1. Make a copy of function group MGD1to ZMGDI as stated inthe Ossnote using program COPYMGDI.
    2. Goto Se38 enter program name SAPLZMGDI Click Display and goto> program-> other object---> enter screen number '0001' and add your fields to the subscreen which should apper on the the general data section of the basic data1 tab for the tcode MM01
    2. Make the changes stated in SAP Note.
    3. After make the changes the functional analyst will need to make some configuration changes.
    4. SPRO -> Logistic General -> Material Master -> Configuring Materal Master -> Define Structure of Data Screens Sequence.
    5. Select SSq = 21 then click on Subscreens select Basic DATA1
    6. Enter in the new screens that were built
    7. Change the row that was create putting in the program (function group program) that was created in step 2.
    But now, I need to add a language dependent description to have larger material description than MAKT-MAKTX. I've added the Z field to the MAKT table, generated the subscreen and copied the PBO and PAI from the screen 1002 (which is saving the MAKTX data). But it doesn't work and I'm not sure what I have to do...

    Solved by myself
    I write here the response because I didn't found it anywhere:
    When you are adding a custom field to MAKT table you have to add it to appending structres SKTEXT and DMAKT too because the standard uses them to read/write the data to MAKT. It's easy to do but hard to find out

  • How to activate the new fields on material master(MM01/MM02/MM03) for existing Materials

    Hi,
    We have a requirement to add  some custom fields as a new tab in additional data option(Descriptions, Unit of measure, etc.) in Basic data of Material master (MM01/MM02/MM03). I have successfully added and these custom fields and they are not part of standard(MARA, MARC) but a custom table and the updates are also done in custom table.
    For new materials, I can see the new tab in additional data screens of basic data view and I could successfully create/change/display using MM01/MM02/MM03. However I cannot see the new tab/fields for existing materials in the system in all 3 tcodes (MM01/MM02/MM03). This is not a main view in material master so that I can extend it by MM01.
    Is there any setting or mass generation program I have top perform so that I can see and maintain these new fields for existing materials. Appreciate any leads or help on this.
    Thanks,
    Harry

    Hello Harry,
    Goto t.code SPRO ---> Display IMG --->  Logistics - General --> Material master --> Configuring the material master --> Create program for customized screens
    Use the above path and create the screen and assign it to the sequence using the below link as reference.
    **************** - Tips - Implementing screen exits for MM01/MM02/MM03
    Regards,
    Thanga

  • Add field to MM01, MM02, MM03

    Hi guru,
    I need to add some fields in MM01,MM02 & MM03  in BASIC DATA 1 tab.
    I want to do this using BAdI.
    The data will go to MARA table.
    Expecting a better solution in brief from U.
    With Thanks
    Sohel

    Hi,
    Forgot to tell u Note No.
    Please Follow Note No : 44410
    You can also try.............
    Note 38299: “Customized material master: concepts”
    Note 44410: “Integrate Customer Specific fields in material master”
    “To extend an existing material master table to include specific customer-specific fields, you can proceed as follows:
    1. Extend the required table in the Dictionary using an append structure
    2. Extend online maintenance in customer-specific material master maintenance.
    a. Define a sub screen with your customer-specific fields in a customer-specific function group created as a copy of standard function group MD1
    b. In configuration, assign this sub screen to a maintenance screen using the “Copy customized material master” function…..(program COPYMGD1 is available)
    3. To update customer-specific fields via data transfer, proceed as follows:
    a. Include the fields in central table T130F
    b. Extend the data structures for data transfer to include the customer-specific fields
    c. Include the customer-specific fields in those tables in which the incorrect data is stored during Direct Input.
    Let me know if you need more information...
    Affable
    Arbind
    Edited by: Arbind Prasad on Jan 25, 2010 10:32 AM

  • Customer fields problem

    Hi experts
    I inserted a customer field in shopping cart item structure INCL_EEW_PD_ITEM_CSF_SC and now I am able to see it in shopping cart creation, the problem is when insert some information in this customer field it is imediately cleared, and I can't find it in table BBP_PDIGP.
    Is it a bug, is there some note to correct it or the badis BBP_CUF_BADI and BBP_CUF_BADI_2 must be used, if yes how the badi must be used?
    Thanks
    Nilson

    Nilson,
    You might want to check OSS notes just-in-case.  Howeveer, when we add fields to EBP, we added then to structure INCL_EEW_PD_ITEM_CSF and INCL_EEW_PD_ITEM_CSF_SC.
    See, if that helps. If not, what version of SRM are you on?
    Regards, Dean.

Maybe you are looking for

  • How To Get PREVIEW on Television while in Timeline?

    I have a datavideo analog convertor I use to watch playback on my television from FCP. When I use Print To Video it will show up fine but I also used to be able to just play through the timeline and view on my TV as well. For some reason that option

  • How to save media files

    hello all, I am creating an application where there is a provision of uploading media files from any location of local drive into user specified path...and also i want to transmit those files as a zip file over network..if it is possible, then how i

  • Application icon don't appear

    I installed Tarantella on remote systems Os- Xp home, win98. and I am unable to see the icons in Tarantella

  • InDesign files copying themsleves

    has anyone out there who stores files on a server ran into this problem? InDesign files that color themselves - usually yellow - and then copy themselves?

  • How does a user activate a menu bar icon?

    Hello everyone, how great is it to assign hotkeys for your application menus.  Yet... for the more interesting users like me, we need to also activate menu bar icon settings, particularly the 'show ink window' in my case.  Respectively iv'e tried eve