To save custom fields in MM01

Hi All,
I have created a new fields in MM01 transaction and iam trying to save the data. These fields are appended to the MARA table using append structure. Iam not able to save the data entered in these new fields to MARA table. Do I need to add these fields to any other structure to save?
Thanks,
Swarna Munukoti.
Edited by: Swarna Munukoti on Jun 17, 2010 12:51 PM

To fill the new field for old records
- Use the search tool, there is a wiki at sdn on this subject : [How to append MARA & call BAPI_MATERIAL_SAVEDATA |http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=71368708]
To fill the field during MM01/MM02 transactions
- Read the old [Note 44410 - Integrating cust.-specific fields in matl master|https://service.sap.com/sap/support/notes/44410] and all related notes
Regards,
Raymond

Similar Messages

Additional custom field on mm01/mm02 screen

hi all,
I need to create an additional custom field on mm01/mm02 screen.
value entered in this field will be updated in the database.
Kindly give pointer to the user exit/ screen where i can create the custom field.
thanks in advance

Hi Manish,
Do the following process step by step as specified in the following link.[http://www.****************/Tutorials/ExitsBADIs/MM/MM01.htm]
But in this link while you are at the 11th step
select your required view.
and do the rest as usual.
This is at the configuration level u can add your customer fields.
I dont think there are any exits available that can fulfill your requirement as the same requirement is fulfilled at the customization level.
Thanks.

New custom field in MM01 - don't save value

Hello,
I create a custom append structure in mara ZBAR with the custom field ZBARCODE.
I followed the gudelines:
Implement screen exit for MM01/MM02/MM03 HOT
By Vijayanand Poreddy
Now the field is visible but it isn't saved in MARA when I save the value in MM01; I don't like the solution of ID SAP to save the value in the exit indicated in the guide, because the field is in MARA not in a custom table.
How I can save the value?? I tried also to update the view v_130F with the new field but the value isn't saved...
Any suggestion?

resolved myself:
PROCESS BEFORE OUTPUT.
*                      Verarbeitung vor der Ausgabe
*MS17092009 Non eliminare modules standard.
MODULE set_propriety.
MODULE INIT_SUB.
MODULE GET_DATEN_SUB.
PROCESS AFTER INPUT.
*                      Verarbeitung nach der Eingabe
MODULE GET_DATEN_SUB.
CHAIN.
      FIELD MARA-ZBARCODE.
ENDCHAIN.
MODULE SET_DATEN_SUB.
FIELD MARA-ZBARCODE MODULE BARCODE_0001 ON INPUT.

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 MM01

Hi All,
My project have identified a requirement for adding a custom field in Material Master (MARA/MM01). Could anyone provide info on this?
Regards,
Sathyajith
[email protected]

You have to work on two enhancement.
1. Table Enhancement... use APPEND for transparant tables. Goto SE11 .
2. U can use following User Exit .
MGA00001
MGA00002
MGA00003
OR
3. Following BADI.
BADI_Material_Check
Hope this has helped u. If so reward.
Darshan

Custom fields in MM01

Hi
I want to add one custom field in SAP material master table MARA also would like to display this field in MM01/MM02/MM03 screen.
Appreciate your expert comments.
Regards,
Ashwin

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

Save custom fields value in EKKO through ME21N

Hello Friends,
putting a new inputfield in the header of ME21N - PO transaction must be inserted within existing tabstrib "Additional Data".
This the new requirement.
I have used the enhancement "MM06E005". I have only implemented and activated the USEREXIT without writing
any code in any Function Module.
Additionally I have added through the screen painter (Function Pool MEGUI) into screen 1229 the customer
ZFIELD (Textinputfield).
I can see this field in the transaction ME21N, ME22N, ME23N but if I enter any value and save it. This Field has only 0000000 in the EKKO instaed of the entered value by me.
In the other transaction like ME21 ME22 ME23 this problem is not existing. I can save the enterd date without any problem.
I have already implemented the structure CI_EKKODB too. There is the zcustom field added.
I need your help for in how to save the data in EKKO with me21n.
Kindly Regards
Marco

Dear Marco,
Dont use User Exit for this . Use the BADI's .If uses the USer Exit it will create u some probs at later stage.
There are 2 BADI's available for this.
1) ME_PROCESS_PO_CUST.
2) ME_GUI_PO_CUST.
1) ME_PROCESS_PO_CUST.This BADI is for Validating the PO at various Level. Methods for this BADI is
1.Open.
2.Initialize.
3.Process Header.
4.Process Item.
5.Check.
6.Post.
Etc.
So u can Validate the Entire PO ..
2. ME_GUI_PO_CUST.
Adding the Customer Own Screen to Enjoy Purchase Order.
The Process is that Just Create a Function Group with the Screen with Screen Which u want to Add to the Header Level.
Through this BADI u can add N Number of Screen to PO.
In the First Method of this BADI just Add the Screen. For Better Understanding goto the Sample Coding of Both BADI's.
With Regards,
Sumodh.P

Unable to update MARA table custom field in Material master

Hi all,
I have added one custom field in MM01,Basic View 2.
For that i have apended that field in MARA table and created one subscreen for that.
This field is visible in MM02/MM01/MM03 in basic data view 2 .
The issue is that we are not able to save values in MARA table which we entered in this field.
I cheked earliar in SDN but couldn't get the proper solution.
i cheked the below available forum discussion link but couldn't get th proper solution.
In material master How to add a new field on Basic data 1 view
Regards,
Amit

Hi,
please trye this :
Please make sure u implemented: methods PUT_DATA_TO_SCREEN and GET_DATA_FROM_SCREEN as they are required for data transport. These methods are called from within the program of the application at PBO or PAI .
See below example code:
PBO:
MODULE initialize OUTPUT.
CLEAR: sflight, ok_code.
IF exit IS INITIAL.
CALL METHOD cl_exithandler=>get_instance
CHANGING
instance = exit.
ENDIF.
CALL METHOD cl_exithandler=>set_instance_for_subscreen
EXPORTING
instance = exit.
ENDMODULE.
The factory method is used to create an instance of the adapter class. You then declare the instance using the public static method SET_INSTANCE_FOR_SUBSCREEN to allow the data for display on the screen to be used in the function group of the user or in the module pool.
MODULE data_for_subscreen OUTPUT.
program = sy-repid.
dynpro = sy-dynnr.
CALL METHOD cl_exithandler=>get_prog_and_dynp_for_subscr
EXPORTING
exit_name = 'BADI_SCREEN'
calling_program = program
calling_dynpro = dynpro
subscreen_area = 'SUB'
IMPORTING
called_program = program
called_dynpro = dynpro.
CALL METHOD exit->put_data_to_screen
EXPORTING
flight = sflight
EXCEPTIONS
reserved = 01.
ENDMODULE.
PAI:
MODULE user_command_0200 INPUT.
CASE save_ok.
WHEN 'BACK'.
SET SCREEN 100.
WHEN 'SAVE'.
PERFORM save_flights.
WHEN '+EXT'.
CALL METHOD exit->get_data_from_screen
IMPORTING
flight = sflight
EXCEPTIONS
reserved = 01.
ENDCASE.
ENDMODULE.
The method GET_PROG_AND_DYNP_FOR_SUBSCR and the input/output parameters specified above are used to determine the name of the customer program and the name of the subscreen. The method PUT_DATA_TO_SCREEN which is called at PBO as well as the method GET_DATA_FROM_SCREEN which is called at PAI are used to transport the data to be displayed.
These methods are implemented by the user:
When you define a screen enhancement, you are strongly recommended to provide sample code for the methods PUT_DATA_TO_SCREEN and GET_DATA_FROM_SCREEN. This code is automatically copied when you create an implementation and can be added to if required. The user of the BAdI definition should not be responsible for the data transport.
regards,
..Pradeep

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

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

Project Server 2013 not saving custom field data

Hello all,
I have a Project Server 2013 deployment with several Project-level custom fields.
One of them, never saves the info typed in. All others work just fine but this one does not like to save anything. There's no error in queues or the ULS.
I'm so lost with it. Any thoughts?
Rene Alvarez

An update on this issue.
I could isolate it to the project plan template. If I use my custom fields with an EPT without a plan template, I have no problem.
So the problem is the template right? Well, I did the following:
Create a blank template and attach it to the EPT. Result: all Ok.
Create a template with 10 tasks (task name only) and attach it to the EPT. Result: all Ok.
Create a template with my full 135 tasks (task name only) and attach it to the EPT. Result: all Ok.
Create a template with the 135 tasks (task name and WBS) and attach it to the EPT. Result: all Ok.
Create a template with the 135 tasks (task name, WBS and milestones) and attach it to the EPT. Result: FAIL. Cannot save custom fields again.
A user noticed something. If he opens a problematic project in Project Pro, and publish it again (no changes) then the project accepts data in the custom fields.
Rene Alvarez

Adding new custom field in already existing custom tab for MM01

Hello Guru,
I have a requirement that add a custom field in already existing custom view of MM01. I did the following steps :
1. I have cerated a new field in MARA using APPEND structure.
2. I have found the function group(Y_FE_MARA) that already there other subscreens, so that I have added another subscreen in that function group and created a field from MARA in the screen.
3. in SPRO went for the path Logistics General->Material Master->Configuring the Material->Define Structure of Data screens for Each Screen sequence
In the 3rd step, I have choosen already existing screen sequence(Y1) and went for Data Screens and choosen for Custom tab and double click on subscreens and then I have added the program as SAPLY_FE_MARA and subscreen number(011) and saved it.
After all the above steps, I have run MM02/MM03 then the field is not getting displayed in the screen of custom view.
Did I miss any steps here? Please suggest me if I did something wrong.
Thanks and Regards,
Muralikrishna Peravali

Hi Raymond,
Thank you for the reply. As per the note some one already implemented the Screen Enhancement with 2 custom views. I need to add the field in any one of existing custom view. So for this I have created a Subscreen in copied function group of MGD1(Y_FE_MARA). But in the function group already 10 Subscreens were created. Is this is the problem? or else copy the FG MGD1 into another FG and create the subscreen will be feasible to my scenario?
Please suggest me.
Thanks and Regards,
Muralikrishna Peravali

Get the custom fields data at the time of save

Hi,
We have added few fields in the ICWC for the complaint screen.
At the time of save i am trigering a BADI.
I would like to check the data that is entered in those fields of complaint screen.
Is there any FM which can be used to get the data from the buffer ?
I have the header GUID available to me .
Thanks.
R

Hi,
Let me elaborate a bit.
Users would create the complaints in the ICWC.We have addeded few custom fields in the complaint screen.
CRMT_CUSTOMER_H_WRKT is extended with the custom fields.
At the save i am trigerring the Partner Determination BAdi.
Here i have the complaint guid at run time.
I would like to check the data entered in the custom field in the complaint screen. Based on this i would like to determine one more partner.
My question is how can i get the custom field data in the complaint screen in this BAdi.
The FM: CRM_ORDER_READ is not returning this data.Is there any FM to get this ?
Thanks.
R.

Required BADI to add custom fields in the Basic Data screen in MM01

Hi,
      I got a requirement like this. I have to add 3 custom fields and one button in the standard transaction i.e., MM01, MM02, MM03. There is one field like producu heirarchy in the Basic Data in that field i will enter some values i want to display the description of those values in the corresponding field for that i need to create 4 custom field. We can create this by breaking the Developer Access Key but instead of that can i get any BADI to add the our custom code to display those fields. I want to add those fields in Basic Data View in the transaction MM01, MM02, MM03. I serached in SPRO but i couldn't find the respective BADI.
Pls suggest if any BADI is there for this.
Thanks in advance.

Hi,
The list of BADI's are as under
WRF_DISCONT_PARAMS_I                    BAdI: Parameters in Fashion Discontinuation
WRF_DISCONT_FACT_E                      BAdI: Follow-Up Actions in Discontinuation
WRF_DISCONT_CHECKS_I                    BAdI: Scope of Check in Material Reorganization
MG_MASS_NEWSEG                          User-Specific Fields & Segments in Mass Maintenance
MATGRP_SKU_UPD                          BAdI for Article Hierarchy Connection
CDT_CHECK_MATERIAL                      Checks for Existence of a Material in a CDT
BADI_MM_MATNR                           Modification-Free Archiving Enhancement of MM_MATNR
BADI_MAT_F_SPEC_SEL                     BAdI for Material Special Field Selection
BADI_MATNR_CHECK_PVS                    Check Material for Use in iPPE
BADI_MATERIAL_REF                       Addition of customer-defined default data for material
BADI_MATERIAL_OD                        Integration of New Objects in Material or Article Maste
BADI_MATERIAL_CHECK                     Enhanced Checks for Material Master Tables
BADI_GTIN_VARIANT                       User Exit for Customer-Specific GTIN Variant Check
BADI_EAN_SYSTEMATIC                     BAdI for Internal Control of EAN Logic
Regards,
Surinder

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

To save custom fields in MM01

Similar Messages

Maybe you are looking for