Mm01 customised subscreen

Hi i had created a customised subscreen 1002 and program name saplzzmgd1.
after creating this i had gone to spro and select logistics general,in this i selected material master, and then expanded configuring material master, and then executed this Define Structure of Data Screens for Each Screen Sequence, then in that i had select 21 Std ind.(short) tab pages and then clicked on datascreens, then i had selected the 21, 16, Purchase Order Text and then clicked on subscreens
their i had changed the program name from saplmgd1 to saplzzmgd1. and saved it.
the issue is when i execute the transaction code mm01 or mm02 and click on tab purchase order text it is not displaying my screen instead it is displaying standard screen.
i had done debugging , here i had found out that it is not call my program or screen. can you please help me out how to proceed further.
Thanks in advance. points will be awarded

Hi,
It is quite some years since I did this, but I think I used program SAPLMGD1 and created screens in the 99xx range as a copy of exixting subscreens. I believe this range is defined as customer range, thus this change not beeing a modification.

Similar Messages

Problem with customised subscreen in ME21N

I am using BadI ME_GUI_PO_CUST & ME_PROCESS_PO_CUST to add a customized subscreen in the header. But the subscreen is only visible with ME23N & ME22N not with ME21N . I am new to BadI, so help is needed.
I have used the following code:
In BadI ME_GUI_PO_CUST with interface IF_EX_ME_GUI_PO_CUST~SUBSCRIBE the code i ve written .. the following code ..
DATA: ls_subscriber LIKE LINE OF re_subscribers.
* we want to add a customer subscreen on the item detail tab
CHECK im_application = 'PO'.
CHECK im_element = 'HEADER'.
* each line in re_subscribers generates a subscreen. We add one
* subscreen in this example
CLEAR re_subscribers[].
* the name is a unique identifier for the subscreen and defined in this
* class definition
ls_subscriber-name = subscreen1.
* the dynpro number to use
ls_subscriber-dynpro = '0002'.
* the program where the dynpro can be found
* "Created in a module pool program in SE80 to hold the subscreen in
*the tcode me21n, me22n, me23n*
ls_subscriber-program = 'ZME_GUI_PO_CUST_SCREEN'.
* each subscreen needs his own DDIC-Structure
ls_subscriber-struct_name = 'CI_EKKODB'.
* a label can be defined
ls_subscriber-label = text-001.
* the position within the tabstrib can be defined
ls_subscriber-position = 13.
* the height of the screen can be defined here. Currently we support two
* screen sizes:
* value <= 7 a sevel line subscreen
* value > 7 a 16 line subscreen
ls_subscriber-height = 7.
APPEND ls_subscriber TO re_subscribers.
In IF_EX_ME_GUI_PO_CUST~MAP_DYNPRO_FIELDS i ve changed the follwoing .......
type-pools : MMMFD.
FIELD-SYMBOLS: <mapping> LIKE LINE OF ch_mapping.
LOOP AT ch_mapping ASSIGNING <mapping>.
CASE <mapping>-fieldname.
WHEN 'ZZPAYMENT'. <mapping>-metafield = mmmfd_cust_03.
ENDCASE.
ENDLOOP.
In the badi ME_PROCESS_PO_CUST, their is a method called FIELDSELECTION_HEADER
method IF_EX_ME_PROCESS_PO_CUST~FIELDSELECTION_HEADER .
DATA: l_persistent TYPE mmpur_bool.
FIELD-SYMBOLS: <fs> LIKE LINE OF ch_fieldselection.
* if the item is already on the database, we disallow to change field
* badi_bsgru
l_persistent = im_item->is_persistent( ).
IF l_persistent EQ mmpur_yes.
READ TABLE ch_fieldselection ASSIGNING <fs> WITH TABLE KEY metafield = mmmfd_cust_03.
IF sy-subrc IS INITIAL.
* <fs>-fieldstatus = '*'. " Display <-- this one was as per the sample code given.
<fs>-fieldstatus = '+'. " Input <-- this i added to make the field mandatory.
ENDIF.
ENDIF.
I have figured out the issue but do not the idea to fix the issue. I have put a break-point in the badi ME_PROCESS_PO_CUST, having the method called FIELDSELECTION_HEADER & run the tcode ME21N. In the line l_persistent = im_item->is_persisten & IF l_persistent EQ mmpur_yes and found out that the value of mmpur_yes equal to 'X', l_persistent is blank.
Suggestion is widely accepted.
Thanks & regards
Feluda

Try like this.
method IF_EX_ME_PROCESS_PO_CUST~FIELDSELECTION_HEADER .
DATA: l_persistent TYPE mmpur_bool.
FIELD-SYMBOLS: <fs> LIKE LINE OF ch_fieldselection.
* if the item is already on the database, we disallow to change field
* badi_bsgru
l_persistent = im_item->is_persistent( ).
IF l_persistent EQ mmpur_yes.
READ TABLE ch_fieldselection ASSIGNING <fs> WITH TABLE KEY metafield = mmmfd_cust_03.
IF sy-subrc IS INITIAL.
* <fs>-fieldstatus = '*'. " Display <-- this one was as per the sample code given.
<fs>-fieldstatus = '+'. " Input <-- this i added to make the field mandatory.
ENDIF.
ELSE.
READ TABLE ch_fieldselection ASSIGNING <fs> WITH TABLE KEY metafield = mmmfd_cust_03.
IF sy-subrc IS INITIAL.
<fs>-fieldstatus = '*'. " Display <-- this one was as per the sample code given.
ENDIF.
ENDIF.
Let me know if you still have the problem.
Thanks,
Jyothi

Needs to be added one subscreen in MM01

Hi All,
I need to create one sub screen and needs to be added it into MM01 along with basic data1, basic data1 and so on. And also it should come in table view of MM01. Anybody can help me on this?
KUMAR.

Hi,
Follow the following steps:
Tcode SPRO: Configuring the Material Master -> Assign Secondary Screens
and Configuring the Material Master -> Create Program for Customized SubScreens.
Hope this Helps
Anirban M.

Control is passed from subscreen to main program in MM01

Hi All,
In MM01, in additional data tab ,we have a subscreen.
This subscreen has following fields
sales org,distribution channel,division and zzpublisher,zzMedia.
sales org,distribution channel,division are within chain, end chain and we have a module to make these field mandatory based on data enetered in zzmedia.Ex:zzmedia 45
similary zzpublisher sould be mandatory based on data entered on zzmedia(zzMedia =55.
) .This field is not within chain endchain.
When we enter zzmedia 45, sales org ,dist channe and division are working correctly.
whereas when we enter zzmedia =55 ,zzpublisher is becoming mandatory but at the same time I am getting standard popup i.e Do you want to save the data,
YES No Cancel..
Can you let me know how to avoid calling the popup when we require to make zzpublisher madatory.
note:all the module written to make fields mandatory are in PAI

Let's see... if you call the subscreen9030 after 9020 PBO, then in the 9020 PAI you call it again, and the PBO for 9030 initializes the data, didn't you just wipe out what you have entered?

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.

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

Customised tab in Purchase order header transaction

Hi all,
I have implemented ME_GUI_PO_CUST BADI for adding a tab in PO header and activated.I have put break-points and found it's not triggering.I have gone through previous forums,but couldn't find any reason.Please help.
pls find below code I used in my BADI:
DATA: ls_subscriber LIKE LINE OF re_subscribers.
     name type mepo_name.
we want to add a customer subscreen on the Header tab.
CHECK im_application = 'PO'.
CHECK im_element = 'HEADER'.
each line in re_subscribers generates a subscreen. We add one subscreen in this example
CLEAR re_subscribers[].
the name is a unique identifier for the subscreen and defined in this class definition
ls_subscriber-name = 'Transporter'.
the dynpro number to use
ls_subscriber-dynpro = '1001'.
the program where the dynpro can be found
ls_subscriber-program = 'SAPLZTRANSP'.
each subscreen needs his own DDIC-Structure
ls_subscriber-struct_name = 'ZTRANSP'.
a label can be defined
ls_subscriber-label = 'Transporter'.
the position within the tabstrib can be defined
ls_subscriber-position = 11.
the height of the screen can be defined here. Currently we suport two screen sizes:
value <= 7 a sevel line subscreen
value > 7 a 16 line subscreen
ls_subscriber-height = 5.
APPEND ls_subscriber TO re_subscribers.
Thank you.
Edited by: Jaya on Feb 8, 2010 10:05 AM

Hi all,
I am able to see the customised tab in ME23n but not in ME21N and ME22N.Any thing else shall I add in the code for this?
following is the code I did for BADI ME_GUI_PO_CUST
method IF_EX_ME_GUI_PO_CUST~SUBSCRIBE.
DATA: ls_subscriber LIKE LINE OF re_subscribers.
*--FIRST SCREEN POPULATION
CHECK im_application = 'PO'.
CHECK im_element     = 'HEADER'.
CLEAR re_subscribers[].
ls_subscriber-name = subscreen1.
*--the dynpro number to use
ls_subscriber-dynpro = '1001'.
*--the program where the dynpro can be found
ls_subscriber-program = 'SAPLZTRANSP'.
*--each subscreen needs itsown DDIC-Structure
ls_subscriber-struct_name = 'ZTRANSP'.
*--a label can be defined
ls_subscriber-label = 'Transporter'.
*--the position within the tabstrib can be defined
ls_subscriber-position = 7.
ls_subscriber-height = 7.
APPEND ls_subscriber TO re_subscribers.
endmethod.
method IF_EX_ME_GUI_PO_CUST~MAP_DYNPRO_FIELDS.
type-pools MMMFD.
*constants above 90000000 for the metafield.
FIELD-SYMBOLS: <mapping> LIKE LINE OF ch_mapping.
LOOP AT ch_mapping ASSIGNING <mapping>.
    CASE <mapping>-fieldname.
      WHEN 'ZLIFNR'.      <mapping>-metafield = mmmfd_cust_08.
      WHEN 'ZNAME1'.      <mapping>-metafield = mmmfd_cust_09.
     ENDCASE.
ENDLOOP.
endmethod.
Edited by: Jaya on Mar 8, 2010 12:55 PM

Custom sub-screen creation in 'MRP 4' tab of MM01

Hi All,
I have to add custom sub-screens in u2018Accounting 2u2019, u2018MRP 2u2019 and u2018MRP 4u2019 tabs of the Material Master transaction (MM01).
I could successfully add a sub-screen in u2018Accounting 2u2019, u2018MRP 2u2019 tabs by using SPRO (Logistics -> Material master -> Configuring the material master -> Define structure of data screens).
However, I could not able to add incase of u2018MRP 4u2019 tab, as Standard SAP has already used all the existing 6 sub-screens. If I try further to create any, I get the error u201CInsertion not possible since maximum number of sub-screens reached u201C.
Please help me out in this scenario.
Thanks in advance!

Screen number changed from 4000 to 4004 in SPRO, which allows to create a maximum of 10 subscreens.

Vendor master field customisation

Hi all,
I have added a new field to the LFM1 table and want to include the field in the XK01 transaction screen. However, there exists no screen exit for the XK01 transaction and as it stands, it needs to be done though customisation. Could anyone guide me through SPRO and help me include the field in the screen?
Regards,
Kumod.

Hi Kumod
As you need to add a new field to the XK01 transaction you have to go with screen exits by defining a subscreen area in the sap standard screen.
Define one subscreen and have a requitred field on that subscreen and call this subscreen in the PBO event using the statement Call Customer-Screen <Number> <Area> then the new field will appear on the screen and u have to write some coding to get the vaslue that entered in that field in the PAI event and some more coding has to be done.
bye bye

Adding new field in MM01/MM02/MM03

Hi All,
I have a requirement to add a checkbox in MM01 costing2 tab page. I have done the basic configurations like adding a new field in MARC with Append Structure, creating Function group (for subscreen) in SPRO and assigning the same to the respective screen (2902) for Costing2 tab page.
I am facing a problem that when i check the newly created checkbox in Costing2 tab page while creating new material. Once the material is successfully created, it is not reflecting in the MARC table for the same created Material,
can anybody guide me to meet the desired requirement.
Note : while running MM02 TCode the respective value to the newly created checkbox should retrieved from database table and if any change made to that should also be reflected back to MARC.
Kindly help me in this regard
Regards
Babu

USE set parameter id in the standard EXIT

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

Restricting the material types in MM01

Dear experts,
Our client is using few materila types like-HIBE,NLAG,ROH
We have upgraded from 4.6B to ECC6. Now many other material types have come .
While creating material in MM01,selecting the required material type among the many is inconvient.
1)One way of removing the unnecessary mat types is deleting others in OMS2,
The other way of restricting is --
2) I can enter the authorisation group in OMS2 for the required material types and i can assign to M_MATE_MAR object in the required role, but it is not working
Do i need to create authorisation group in any customisation for entering in the OMS2, because what i entered in OMS2 is not displaying in PFCG of the authorisation object under authorisation group.I have checked in SM30 also ,the same authorisation groups under T134 table are updated. Even though,mat types are not restricted in MM01 under material type field.
Please suggest any other way of restricting the display of material types in Material type field of MM01 instead of deleting unwanted the material types in OMS2 transaction
Regards,
Dayanand

You can use the material type specific transactionsminstead of MM01, remove the authorizations of MM01 transaction and add the required material type creation transactions
example - Goor Matreials create(special)
HIBE,NLAG,ROH
MMB1                 Create Semifinished Product(HALB)
MMF1                 Create Finished Product(FERT)
MMG1                 Create Returnable Packaging
MMH1                 Create Trading Goods
MMI1                 Create Operating Supplies(HIBE)
MMK1                 Create Configurable Material(KMAT)
MML1                 Create Empties
MMN1                 Create Non-Stock Material
MMP1                 Create Maintenance Assembly
MMR1                 Create Raw Material(ROH)
MMS1                 Create Service
MMU1                 Create Non-Valuated Material
MMV1                 Create Packaging
MMVH                 Create Centrally: Decentral.Shipping
MMW1                 Create Competitor Product

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

Screen Enhancement in MM01

Hi All,
We are using the AFS SAP ECC 5.0 system. My requirement is to add the LAENG (Length), BREIT (Width) and HOEHE (Height) fields to the table control in AFS Weights & Volumes TabStrip in Additional Data of MM01/MM02/MM03 Transactions and we need to update these values in /AFS/MARM table.
I have done the IMG activities specified for the changing the screen sequence of Material Master. I have created the Function Group ZJ3AB using the IMG activity Create Program For Customized Subscreens under Logistics General  Material Master  Configuring the Material Master. I have copied the Subscreens SAPLJ3AB 1002 and 2501 to my custom Function Group ZJ3AB and modified the table control. I have assigned these SubScreens to the Screen Sequence using the IMG activity Define Structure of Data Screen for Each Screen Sequence. I am able to see my custom sub screen. But when I change the data in the table control the data is not getting saved in the /AFS/MARM table and the system is giving a status message No Changes Made.
There is an internal table XJ_3AMARM which holds the table control data. This table is declared as the global field in the function group ZJ3AB. It is getting populated in the PAI of my custom screen. The system is calling the function modules J_3A_VERBUCHER_AUFRUF and J_3A_AFS_MAT_VERBUCHER for updating the data to the /AFS/MARM table. These function modules are reading the data from the internal table XJ_3AMARM to update the /AFS/MARM table. XJ_3AMARM internal table is blank when these function modules are triggered.
Please suggest me in updating the data.
Thanks & Regards,
Prasad.

Hi,
BADI BADI_MATERIAL_REF
Check this document for BADI implementations -
http://help.sap.com/saphelp_47x200/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
Regards

Screen exit for MM01 to add additional fields to basic data tab .

Hi All ,
We are working on the SAP version ECC 5.0 . Our requirement is to add additional fields to the general data section of the basic data1 tab for the tcode MM01 . I have gone through many previous queries in SDN but not able to figure out what exactly the process should be . All I could figure out is to start the process from appending the structure to MARA for the additional fields . Then follow the steps in the SPRO .
Define Structure of Data Screens for Each Screen Sequence
Assign Secondary Screens
Maintain Order of Main and Additional Screens
Assign Screen Sequences to User/Material Type/Transaction/In
Define How Maintenance Statuses Are Determined in Data Trans
Create Program for Customized Subscreens
I am not able to comprehend what we are trying to do in these steps .
Can anyone explain me in detail what we are trying to do in the whole process ?
Thanks ,
Varun .

Hi varun,
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.
Thanks and regards,
Pavankumar

Mm01 customised subscreen

Similar Messages

Maybe you are looking for