Exit in MM01/MM02

Hello experts,
I need a exit in the Tcode MM0x to check the number range of the material.
ie) when the user enters a material number in MM02 and press the button Select
views I need to check the material number range is available in a customised table.
Any ideas.
Thanks in Advance.
Vasanth

Hi vasanth,
There are three exits available for MM01 & MM02.
Exit Name           Description
MGA00001            Material Master (Industry): Checks and Enhancements
MGA00002            Material Master (Industry): Number Assignment
MGA00003            Material Master (Industry and Retail): Number Display
Probably, the first exit may be of use to you. Beacuse, The customer exit is in function module MATERIAL_UPDATE_ALL. The function
module checks the data for errors (logical relationships, foreign keys,
fixed domain values, and so on) when the material master is updated.
Use
    o   New fields
        You can make checks possible for new fields of your own. These checks
        must be identical to the checks that you carry out for your new
        fields in online maintenance.
    o   Existing fields
        For existing fields, you can extend and intensify the checks.
    You can also change data for descriptions and general material data
    (MARA). For example, the descriptions can be generated from attributes of
    the material.
Regards,
JLN
P.S. mark points for all helpful answers

Similar Messages

User Exits for MM01 & MM02 transaction

Hi SDN,
Is there any user exit available for Change, create Material so that i can update some materail related data.
Regards,
Rahul

Hi
MGA00001- Material Master (Industry): Checks and Enhancements
                                                                                Func.   EXIT_SAPLMGMU_001
MGA00002- Material Master (Industry): Number Assignment
                                                                                Func.   EXIT_SAPLMG02_001
                                                                                Func.   EXIT_SAPLMG02_002
MGA00003- Material Master (Industry and Retail): Number Display
                                                                                Func.   EXIT_SAPLOMCV_001
                                                                                Func.   EXIT_SAPLOMCV_002
                                                                                Func.   EXIT_SAPLOMCV_901
                                                                                Func.   EXIT_SAPLOMCV_902
Regds
Seema

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

Screen-Exit MM01/MM02/MM03 - Problems when I try to retrieve the data saved

Hi guys,
I created a Screen-Exit in the Accounting View of MM01/MM02/MM03 because I need to insert data into the fields of an Append Structure of the table MBEW, that I created.
So, I can insert the data through an User-Exit. I Export to the Memory the data from my Screen-Exit and I modify the Fields content of MBEW inside of this User-Exit.
I need to select these data and show it, because the selection is not automatic. I don't know if it could be automatic.
Inside of the Screen-Exit there are some tables available, but they are empty and I can't retrieve the data because I don't have
the Material Number nor other data of MBEW. When I run MM02, for example, the User-Exit is not started and so
I can't export the data to the Memory and after that to select the data. This User-Exit is only started when I save the data...
I found not any BADI too...
Please, could someone help me?? How I could solve this question?
Thanks a lot!
Regards,
Marcos Fernando Dotta

Hello Marcos,
Please see OSS note 44410 - Integrating cust. - specific fields in matl master.
Kind Regards,
Rae Ellen Woytowiez
Link: [https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=44410]

User Exit/Field Exit for Field Selection in MM01 & MM02

Dear All,
Please Tell if I want to make Field Purchasing group Mandatory in MM01 & MM02 in Purchasing view only.I dont want the data to be updated in MRP1 view. Please tell me is there any exit for the same.
Regards,
Sandeep

You can customize
via
SPRO>Logistics - General>Material Master>Field Selection>
first from
Assign Fields to Field Selection Groups
you must assign MARC-EKGRP (Purchasing Group)
to a selection Group which will be mandatory.
Then from Maintain Field Selection for Data Screens
you must choose the Material Types which you want to make
Purchasing Group mandatory.
You must check Reqd Entry for the material types you want
Best Regards
Hope will help

User Exit on Material Save in MM01/MM02 (31I)

Hi,
Does anyone know of a user exit that gets triggered upon material save in MM01/MM02 in 31I? I see there is one exit MGA00001, but it is purely for checking the field values in 31I. The same exit has different interface in 46C version and can be used to update the material master data. I need to update the additional EANs (table MEAN) on the material master in 31I version.
Thanks,
Prayarna

HI,
Just execute this report , the input parameter for this report is the transaction code,Enter the transaction code you will get the user exit available for the particular transaction.
If you find my answer suitable pelase reward me with suitable points.
REPORT Z_USEREXIT .
TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
TABLES : tstct.
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'
                   AND object = 'PROG'
                   AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
    SELECT SINGLE * FROM trdir WHERE name = tstc-pgmna.
    IF trdir-subc EQ 'F'.
      SELECT SINGLE * FROM tfdir WHERE pname = tstc-pgmna.
      SELECT SINGLE * FROM enlfdir WHERE funcname =
      tfdir-funcname.
      SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'
                         AND object = 'FUGR'
                         AND obj_name EQ enlfdir-area.
      MOVE : tadir-devclass TO v_devclass.
    ENDIF.
ENDIF.
SELECT * FROM tadir INTO TABLE jtab
                WHERE pgmid = 'R3TR'
                  AND object = 'SMOD'
                  AND devclass = v_devclass.
SELECT SINGLE * FROM tstct WHERE sprsl EQ sy-langu AND
                                   tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
       20(20) p_tcode,
       45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
    WRITE:/(95) sy-uline.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 sy-vline,
           2 'Exit Name',
          21 sy-vline ,
          22 'Description',
          95 sy-vline.
    WRITE:/(95) sy-uline.
    LOOP AT jtab.
      SELECT SINGLE * FROM modsapt
             WHERE sprsl = sy-langu AND
                    name = jtab-obj_name.
      FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
      WRITE:/1 sy-vline,
             2 jtab-obj_name HOTSPOT ON,
            21 sy-vline ,
            22 modsapt-modtext,
            95 sy-vline.
    ENDLOOP.
    WRITE:/(95) sy-uline.
    DESCRIBE TABLE jtab.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No of Exits:' , sy-tfill.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'No User Exit exists'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST   SCREEN.
Regards,
Irfan Hussain

Set cursor in a specific view of transaction MM01/MM02

Hi,
We have to check a condition in the user-exit EXIT_SAPLMGMU_001, for transaction MM01/MM02, and if the condition fails the client wants to set the cursor in a specific field from a specific view. Is it possible? I tried to use the sentence SET CURSOR referenced to a remote program but it doesn't work.
Does anybody knows how to solve this problem?
Thanks in advance
Regards
Maribel

Hi
I hope, you have read the documetation attached with this Standard Enhancement - MGA00001.
EXIT_SAPLMGMU_001
Where Is the Customer Exit - EXIT_SAPLMGMU_001 called?
The customer exit is in function module MATERIAL_UPDATE_ALL. The
function module checks the data for errors (logical relationships,
foreign keys, fixed domain values, and so on) when the material master
is updated.
Use
o New fields
You can make checks possible for new fields of your own. These
checks must be identical to the checks that you carry out for your
new fields in online maintenance.
o Existing fields
For existing fields, you can extend and intensify the checks.
You can also change data for descriptions and general material data
(MARA). For example, the descriptions can be generated from attributes
of the material.
Limitations
You cannot bypass existing checks.
Interface to Application
The respective data of the current logical transaction is contained in
the structures, for example, in structure WMARA for MARA. Nonrelevant
structures are transferred with their initial values.
General material data that can be changed (CMARA) has the structure
MARU. This MARA view contains fewer internal fields than MARA itself. If
WMARA is filled, CMARA is also filled when accessed.
The customer exit contains the exception APPLICATION_ERROR for your
self-defined error situations.
Using the language element MESSAGE .. RAISING APPLICATION_ERROR, you can
terminate the current (logical) transaction and display your message in
the log.
Also, I guess, have you put some code in the Includes available with the EXITS and then activated the Project in CMOD.
<b>Reward points</b>
Regards

Default values for MVKE in MM01/MM02

Hi All,
If user changes any data in MM02/create material in MM01 , then I need to default some values in MVKE table( say MVKE-PRAT2, Standard SAP Field).
I have tried with User exits and badi, but nothing works .
EXIT_SAPLMGMU_001 ZXMG0U02 (cannot change MVKE fields)
BADI_MATERIAL_CHECK(same as the above user exit)
BADI_MATERIAL_REF ( looks to be works only when extending and creation of new material)
Can somebody help to advise , is there any other user exit/method to update the MVKE fields in MM01/MM02.?
Thanks a lot.
Regards
Agrud

There are many Implicit Enhancement points in the PBO modules of SAPLMGMM. You might want to play with one of those, see where MVKE is getting populated/initialized and pre-populate it there.

Set control in MM01/MM02

Hi experts,
Any user exit we can use on Classification tab for MM01/MM02. I would like to set some restriction on user input.
Thanks so much.
Cheers,
Isaac.

For example,
I would like to stop user from entering Model (this is one of the customized classification field) starting from U* (protected field). If the user did select the classification, I will prompt an error message and restrict them from saving the material records.
Thanks.

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

Enhacement in MM01 / MM02

Hi,
I've a requirement to show a new dynpro in MM01 and MM02 in order to extend the material to more than one storage location.
All the code is already done, but a need to find specific point (User Exit o BADI) in which I can place the call to my FM. It'd be great if there was something just after saving the material to the db.
I've tried user exit EXIT_SAPLMGMU_001 but it's not working.
Best Regards!

Hi,
thanks for your response.
My main problem is that I need to execute my abap code just after the material's been created / updated.
The steps are:
1. User enters the MM01 / MM02 transactions
2. User enter data for the material
3. Material is created / updated
4. Check serveral conditions and show custom screen if required.
4.1 Material is extenden / updated in the rest of storage locations.
I need to find the place in which the transactions have already commited its work and I can use BAPI_MATERIAL_SAVEDATA to extend / update the material for the rest of the storage locations.
Thanks in advance!

Service for Object - MM01/MM02/MM03

We have activated u201Carchive linku201D to ECM (IBM FileNet Application Connector for SAP® R/3® (ACSAP R/3) for business object for material master transactions (MM01/MM02/MM03), so the images associated with material master can be stored in FileNet repository.
We will be using the SAP standard u201CService for Objectu201D functionality to store the image via create -> store business document. We want to disable the u201CCreate -> Create Attachmentu201D because we donu2019t want the documents stored on the SAP content repository.   This is possible to do with either through configuration, security or user exit? If yes, please specify how.
Additionally, please provide any security objects which we could utilize to control user from creating/changing /deleting the attached document. Basically, we want some users to display the document but not alter them in any way.
Thanks.

Hi
The authorization objects for attachment to material are as following:
Object Class BC_Z Basis - Central Functions
Authorization Object: S_BDS_DS
Authorizations for Document Set
Authorization Field ACTVT : 30
Authorization Field CLASSNAME:BUS1001
Authorization Field CLASSTYPE:BO
other ACTVT
01     Create or generate
02     Change
03     Display
04     Print, edit messages
05     Lock
06     Delete
24     Archive
25     Reload
30     Determine
70     Administer
78     Assign
82     Supplement
Note: That to be able to attach user should have MM02 authorization..
Best Regards
Hope it helps

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

Change MARA at save MM01/MM02

HI ABAP experts,
i would like to change some fields in MARA when i save at MM01/MM02. Is there any exit or badi where i can do this?
Thx
Hannes
Moderator message: Welcome to SCN. Please always search for available information/documentation and previous discussions of the same topic before posting.
Edited by: Thomas Zloch on Jan 13, 2012

Searching in SDN can help you the best. there are many threads for this. please search

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.

Exit in MM01/MM02

Similar Messages

Maybe you are looking for