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

Similar Messages

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

Addtional field display in search help for plant in MM01/MM02/MM03

Hi Experts,
my requirment is that when see search values of ( F4) plant field in MM01/MM02/MM03 t.codes only avilable plant and name1 values . i need to display name2 values also. How i can search help of plant field should be enhanced.
Regards
Jaya

Hi,
You need to:
1/ append ALV grid structure PLM_ALV_116 with field (in SE11)
2/ in form WERKS_LISTE in include LMATEFLI you need to implement following modyfication selecting NAME2 for all the plants which are to be shown:
FORM werks_liste.
* convert into ALV list
DATA: c_structure_name TYPE tabname VALUE 'PLM_ALV_116'.
DATA: status_set TYPE slis_formname VALUE 'ALV_PF_STATUS1' .
DATA: et_list TYPE TABLE OF gs_list_type_06 .
DATA: l_et_list LIKE LINE OF et_list .
DATA: l_seqwerk LIKE LINE OF seqwerk .
* Prapering data to be display
* SET TITLEBAR 'TIT' WITH text-003. Note 821186
G_titlebar = text-003.
LOOP AT seqwerk INTO l_seqwerk .
    MOVE-CORRESPONDING l_seqwerk TO l_et_list .
    APPEND l_et_list TO et_list .
ENDLOOP .
"-------->INSERT
SELECT name2 FROM t001W
    INTO CORRESPONDING-FIELDS OF TABLE et_list
    FOR ALL ENTRIES IN et_list
    WHERE werks EQ et_list-werks.
"<--------
* Praper fields for ALV Disply
PERFORM alv_list_fieldcat_create
        USING lt_fieldcat c_structure_name .
* Diplay ALV list
PERFORM alv_list_display TABLES et_list[]
                           USING c_structure_name
                                  status_set
                                  space.
ENDFORM.                    "WERKS_LISTE
Regards,
Marcin

Make field MDMA-DISGR (MRP Group, MRP Area) mandatory in material master

We are using MRP Area (Storage location) and I want to make MRO Group (MDMA-DISGR) mandatory. It is not in the list of fields (IMG > Logistics) to where field selection for material masters is set.
Am I missing something -- or can this field not be made mandatory?
Thanks

Hi
MRP group(MARC-DISGR) is maintained under selection group 51 (Transaction code - OMSR)
You can miantain the selection in Tcode OMS9 based on the filed refernce key using for the material type.
i am not sure is this you are looking for.
Thanks & Regards
Kishore

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

Custom Field in Work Area of SOCO

Hi,
I have to add custom fields in 'CARRY OUT SOURCING-WORK AREA' frame. Is there any standard structure available for this? i know there are standard structures available for shopping cart and others, but i am not sure whether any structure is available to add custom field in 'CARRY OUT SOURCING-WORK AREA' frame. Please help me in finding out the exact Include structure, which is relevant for my requirement. Also let me know if i have to implement a BADI for this.
Thanks in Advance,
Suresh

Hi Suresh,
It seems that we are looking for the same answer but i haven't found yet the exact BADI to work with it...
Here there is some approach:
In the BBP_SCREENVARIANT BADI there's a method called GET_SCREENVARIANT_SOCO where you can modify the standard screen call from the 0300 dynpro to a 0301 or whatever number dynpro you want to, but the problem it's that i don't know where to generate this new screen and the logic to retrieve the information to fill the new fields that i need....
So i wish this helps you a lil' bit and if you get something please let me know, i get also a post:
Can we hide the 'Create Contract' button in SOCO ?
If you can post any help there i will reward points...
BR
Gerardo.

Add custom fields in header of FI documents using FI_HEADER_SUB_1300IM

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

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

Add Custom fields in Report Incident Screen in EHSM

Hello experts,
I want to add custom fields like Notification No. and division in Report Incident screen in EHSM.
I have added two fields.
Business Object: EHHSS_INCIDENT
Node: BASIC_INFO_ALL
Structure: INCL_EEW_EHHSS_INC_BINFA_D (added two fields using append structure)
Now how can i link with my screen and how to fetch notification data (standard F4 help)?
and when i save data, where it will save?
Can you guide me with proper steps for it as i am new in it.
Thanks in advance.

Hi Jayvin,
To add the above fields on the screen, open the component configuration of the required screen.
Enhance the same and add the fields from the respective Node.
You did not worry about saving the data, once the fields are placed on the screen it will get save on click of save/ on event of save.
Regards,
Sanket.

How we can add custom field in standard report 2kee.

Hi,
How we can add custom field in standard report 2kee.
I need one extra field to add in 2kee report for the same is there any customization req.
Regards
Ravi

Ravi,
Which extra field do you want to add or see? Without specifying the field, it is difficult for one to tell you precisely whether you need a custom field or just change the layout to get the standard one.
There are so many fields which exists but are not displayed when you execute 2KEE. You need to change the layout selections to your preference.
Nonetheless, if the field you want to add does not already exist, then yes you can do customization. Is there a customization requirement? No. But remember, you are making changes to SAP Standard program which will no longer be supported by SAP should in the case an issue arise in the future related to this very program.
Have your abaper add the said field in the program or why not just create a query to pull the report?
Elias
Edited by: Elias Akorli on Sep 18, 2009 9:02 PM

Add Customized fields in FICA document

Dear all,
We are having a requirement in which we need to add customized fields in FICA document and need to post them .Can anyone please tell me how to meet this requirement
susmita
Edited by: susmitha harini on Aug 11, 2010 12:46 PM

Hi Susmita
You can add the fields to the customer includes
CI_FKKOP
CI_FKKKO
To create/update the customer fields in automated processes you can use the standard SAP BAPI:
BAPI_CTRACDOCUMENT_CREATE
BAPI_CTRACDOCUMENT_CHANGE
Check out the import table EXTENSIONIN with structure BAPIPAREX.
To add the fields to the standard SAP transactions, have a look in IMG under
Financial Accounting
Contract Accounts Receivable and Payable
    Basic Functions
      Posting and Documents
        Document
          Screen Preparations
Yep
Jürgen
Edited by: sattlerj on Aug 12, 2010 8:45 PM
Edited by: sattlerj on Aug 12, 2010 8:49 PM - Added EXTENSIONIN

Enhance Standard Info Structure SAP_CRM_ACT to add custom fields in CRM Activity archive Search

Hi All,
We have a requirement where we need to enhance CRM UI archive search with custom fields for CRM activity Object CRM_ACT_ON. As per my analysis Standard Archive Search for activity Uses info structure SAP_CRM_ACT for searching archived data.
But when we are trying to add custom fields into above field catalog, it is treated as modification. But Modification is not allowed in our landscape.
Standard infostructure is harcoded in SAP standard method ARCHIVING_READ of class CL_CRM_REPORT_ACC_DYNAMIC which is called as part of the process. So we are not able to go ahead with custom info structure.
Can you please le me know if there are any alternative way to meet above requirement or I have missed any steps.
Thanks & Regards,
Sujit

Hello Thomas,
Maybe this link can help.
add new field to search criteria and result.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0747ac2-ffd9-2910-de9a-8a3dc44da8b4?QuickLink=index&overridelayout=true&12966506314316
Search Options - Knowledge Management - SAP Library
regards,
Grace

USER EXIT or BADI to add custom fields in QI06 Output

Hi Gurus,
I have tried to find out Suitable User Exit / BADI to add custom fields in QI06 ( Collective Maintenance Display) output. but in vain..
We found USer Exits -QLIB0001/QLIB0002 .
Badi- QB_PLAN_SELECTION_P, QB_Q_INFO_RECORD,QB_QM_SYSTEM_COMPARE,ALV_SWITCH_GRID_LIST
which are not useful.
So need your Suggestions / help in finding out suitable exit/ BADI.
Thanks in Advance,
Lalit.

Hi,
You can use the function module SXV_GET_CLIF_BY_NAME to find more BADI. Set a break point and run QI06 until the end.
I hope this helps you
Regards
Eduardo

Add custom fields in ML81n line item level

Hi All,
We have a requirement to add custom field in ML81N. I have found an enhancement SRVDET and table CI_ESLLDB to add the custom field. But my problem is, I cant find the screen where can I add that custom field. Does anybody knows this?
Appreciate your inputs.
Thanks in advance.

Dear,
Below mentioned enhancment will create a new tab strip in the detail screen of service entry
SRVDET              User screen on tab strip of service detail screen
Create one project in CMOD, then assign the enhancement
Calling screen No. Area     Called screen   No. Short Text
SAPLMLSP        0220 SUSCUSER SAPLXMLU        0299
New field should be added in the include structure CI_ESLLDB
Desgin these new fields in screen 0299 of program SAPLXMLU.
Put your code in FM
EXIT_SAPLMLSP_040              Transfer of Data to Detail User Screen
EXIT_SAPLMLSP_041              Adoption of Data from User Screen
Regards
Dillip

Add custom fields in EL09/EL35 transaction

Hi,
I need to add custom fileds in these transactions in order to specify particular client information I have to extract in the output of meter reading order.
How can I accomplish this need?
Do I need to define a custom transaction or do I have to implement some customizing-badi,... I didn't find anything useful in my researches.
Can you help me please?
Thanks,
Gabriele

Hi Gabriele,
When we are generating meter reading orders, entries are made in tables EABL & EABLG. You can add custom fields in these tables using enhancement EDMMR001.
Based on your rules / logic, you can update these custom fields from user exit - EXIT_SAPLEL01_010.
Now, when you are downloading meter reading orders, you can access these values.
Alternatively, if you can derive these additional values in run time, you can place your logic in Meter Read Order Download Print Workbench program.
Hope this helps.
Regards,
Avinash

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

Similar Messages

Maybe you are looking for