Material Master - Same Description - Message No

Hi,
When i create the material master with the same description which has been created earlier, system does not give message "Material with the same description exists". I have seen in 4.7, but currently I am working on ECC 6.0.
So, some one can help me in providing the Message Class and No since i was not able to find the message class and no.
Note: Internal Number assignment have been configured for the material type.
Thanks in advance.
Regards,
Elanchezhian. K.C.

Hi,
It seems this message is not there in ECC6.0
Please check if you can add this functionality through user exit
EXIT_SAPLMGMU_001
BR
Diwakar

Similar Messages

Create material master get error message

Hello Guys,
I get the error message as below when i create material master . can you help me?
error message
nternal error in FORM/FUNCTION ckms_buffer_write in position 19 with RC 0
Message no. C+099
Procedure
Please inform your system administrator.
Thanks and best regards,
Alengao

Debug the program with help of ABAPer and check it.
Also pls check these NOTES,
414204, 933809, 390655,0001096890
0001126497
0001164684
0001230454
Edited by: Afshad Irani on Aug 12, 2010 3:12 PM

Duplication of material master by description

Hello All,
I have one requirement. System should not allow me to create the material with the same description twice.
e.g. I have created a material AB01 Desc- Crankshaft. Now when I'm trying to create AB02 Desc- Crankshaft, system should restrict me. How to achieve this? Is there any enhancement or exit?
Thanks in advance,
Piyush

Hi Piyush,
As per standard SAP system, description does not matter. System only recognize/understand generated code. So it is not possible to stop it just description is matching.If you want to create the same then make some changes in its description.
Hope this will resolve your issue.
T & R,
Brijesh

Error MM335 when trying to change profit center on material master record

We are trying to change the profit center that is assigned on the u201CSales: general/plantu201D tab in the material master (same as what shows on the u201CCosting1u201D tab of the material master).
The following error message appears: u201CYou want to change the profit center but there are still material stocks u2013 Message no. MM335.u201D
Our SAP version is SAP ECC 5.0 with support pack 19.
This particular material that we are trying to change only exists within one plant and one storage location in SAP.
I have done the following in order to try and resolve this issue:
1. Removed all inventory from the inventory management and warehouse management side for the material.
2. Closed all open purchase orders and process orders for the material.
3. Looked at the MD04 screen to verify there are no outstanding documents for this material.
I also searched for OSS notes and found note #1249513 which was applied to our sandbox environment. This note did not fix our problem.
I had a developer to debug the code that is being triggered upon making a profit center change. Two important pieces of information he found is that the SAP code is:
1. Looking to see if the u2018New G/Lu2019 is turned on and u2018profit centeru2019 is active in the new G/L.
2. Looking to see if previous period stock exists for the material.
The code is then setting a flag which causes the error message to appear.
I have found other comments in the forum stating to change the error to a warning for message MM335. I believe this is not the correct solution; as this would allow a change to a profit center even if stock exists, open orders exist, etc. I also know we could trick the system by temporarily changing the message to a warning and sending that through to production, changing the material master and following up with a transport to change the message back to an error. This would work, but we want a final resolution to this problem.
I believe that 2 OSS notes that were included in our latest support pack upgrade has caused this problem. Those notes are: 1057674 and 1106510.
I plan on opening a note with SAP, but was wondering if any users have experienced this same problem after a recent support pack upgrade.
Regards,
JH

Following is additional information regarding this problem. We were able to successfully change the profit center on some of our materials by making sure there was no stock in previous period and current period (and no open sales orders, purchase orders, etc.).
- JH

How to udate material master from contrat when there is a change in me32k

Planned delivery time is maintained in MRP 2 view of material master. Whenever contract is created for the material, the procurement team changes the planned delivery time in contract. This leads to inconsistency between the two values.
It is required that whenever planned delivery time for a material is changed in contract, the same value should get updated in MRP 2 view in material master.
Moderator message: "spec dumping", please work yourself first on your requirement.
Edited by: Thomas Zloch on Sep 7, 2011 11:00 AM

Try adding a trigger that will add records to a table that can be checked by the ODBC application whenever it runs. Of course, the trigger could also call a stored procedure that called some external code as well.
HTH

Custom - Material Master Update using an IDOC (Message Type - MATMAS_BAPI)

Hello everyone,
I was writing a functional specs. Basically, I want to update the material master MM02 using an IDOC (MATMAS_BAPI01 - Basic Type & MATMAS_BAPI - Message Type). This is currently working.
To my understanding, this currently uses function module - BAPI_IDOC_INPUT1 to update the material master after the IDOC is posted to SAP ECC from XI system.
Now I want to add one small validation logic before it actually updates the material master (MM02).
I looked around and found one exit - EXIT_SAPLMV02_002 in enhancement MGV00001. I was almost sure that this EXIT can be used to write the custom validation code before, actual MM02 updation.
However while trying to establish a link between this EXIT and BAPI_IDOC_INPUT1, I found that EXIT_SAPLMV02_002 is actually a part of another function module - IDOC_INPUT_MATMAS01 and not BAPI_IDOC_INPUT1. I am stuck here if adding the custom logic in the exit really going to work.
a bit of googling and I found from WE30 that the purpose of both these function modules are actually different. While BAPI_IDOC_INPUT1 actually create & updates the material master (also plant specific master data which is my need), IDOC_INPUT_MATMAS01 is just for maintenence of few fields in MM02 (may be custom fields).
Can anyone point out if my thing is in right direction?
Also please offer any solution where shall I put the Custom Logic in the EXIT or the some variants of
BAPI_IDOC_INPUT1.
A less technical explanation would be appreciated as I come from a functional background and invloved in this for writing the func specs. I want to make it sure that what I write is not useless and makes some sense.
Thanks in advance,
Arunesh

Hi Lalit,
Did some head breaking with the function module - BAPI_IDOC_INPUT1 to check whether it is calling the EXIT_SAPLMV02_002 internally. Couldn't get anywhere.
On question of another EXIT in BAPI_IDOC_INPUT1, I don't see any. I am not very proficient in ABAP code, I must say though.
I found the list of exits from google, almost same list everywhere.
http://www.sapfans.com/forums/viewtopic.php?f=21&t=296637
here I got the EXIT, I am talking about.
Any other way to find either the EXIT or link the above?
-- Arunesh

Material Master Extension to all the plants of same type

Hi
In the given scenario, we have almost 200 plants where same materials are required , now when we create material master using Tcode MM01 we want to extend this material master to all the plants of same type in one go .Is it possible , if yes , how to go about it ?? please help, this is the specific customer requirment .
ans will be rewarded
rgds
mojib

Hi,
Just go through the code
report ZMM_FERT_CREATE_EXT_PLANT
       no standard page heading line-size 255.
*include bdcrecx1.
DATA : it_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE,
       it_bdcmsgcoll LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
data : p_filex type string .
types: BEGIN OF t_mm01,
        matnr(018),
        MAKTX(040),
        mtart(004),
        matkl(009),
        WGBEZ(020),
        bklas(004),
        vprsv(001),
        werks(004),
        vkorg(004),
        vtweg(002),
        sktof(001),
        versg(001),
        kondm(002),
        ktgrm(002),
        meins(003),
        gewei(003),
        j_1ichid(012),
        j_1isubind(001),
        j_1icapind(001),
        j_1igrxref(001),
        tragr(004),
        ladgr(004),
        mtvfp(002),
        xchpf(001),
        mtpos_mara(004),
        mtpos(004),
        ekgrp(003),
        BWTTY(010),
        meins1(003),
        meins2(003),
        meins3(003),
        sales_txt(040),
        purc_txt(040),
        mbrsh(001),
        verpr(015),
        peinh(006),
        stprs(015),
        brgew(017),
        ntgew(017),
        j_1ivalass(018),
        umrez1(006),
        umren1(006),
        umrez2(006),
        umren2(006),
        umrez3(006),
        umren3(006),
        lgort(004),
        TAXKM1(001),
        TAXKM2(001),
        HERKL(003),
        HERKR(003),
        J_1IMOOM(018),
      end of t_mm01.
DATA : it_mm01 type table of t_mm01 with header line initial size 0.
*Selection Screen                                              *
SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE text-001.
            PARAMETERS: p_file like IBIPPARMS-PATH obligatory.
SELECTION-SCREEN:END OF BLOCK B.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file .
PERFORM get_filename.
*START-OF-SELECTION
START-OF-SELECTION.
   PERFORM upload_data.
   PERFORM fill_data.
*&      Form upload_data
*       text
* --> p1        text
* <-- p2        text
form upload_data .
p_filex = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename                      = p_filex
    FILETYPE                      = 'ASC'
    HAS_FIELD_SEPARATOR           = '#'
*   HEADER_LENGTH                 = 0
*   READ_BY_LINE                  = 'X'
*   DAT_MODE                      = ' '
*   CODEPAGE                      = ' '
*   IGNORE_CERR                   = ABAP_TRUE
*   REPLACEMENT                   = '#'
*   CHECK_BOM                     = ' '
*   NO_AUTH_CHECK                 = ' '
* IMPORTING
*   FILELENGTH                    =
*   HEADER                        =
tables
    data_tab                      = it_mm01
EXCEPTIONS
   FILE_OPEN_ERROR               = 1
   FILE_READ_ERROR               = 2
   NO_BATCH                      = 3
   GUI_REFUSE_FILETRANSFER       = 4
   INVALID_TYPE                  = 5
   NO_AUTHORITY                  = 6
   UNKNOWN_ERROR                 = 7
   BAD_DATA_FORMAT               = 8
   HEADER_NOT_ALLOWED            = 9
   SEPARATOR_NOT_ALLOWED         = 10
   HEADER_TOO_LONG               = 11
   UNKNOWN_DP_ERROR              = 12
   ACCESS_DENIED                 = 13
   DP_OUT_OF_MEMORY              = 14
   DISK_FULL                     = 15
   DP_TIMEOUT                    = 16
   OTHERS                        = 17
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.                    " upload_data
*&      Form get_filename
*       text
* --> p1        text
* <-- p2        text
form get_filename .
CALL FUNCTION 'F4_FILENAME'
               EXPORTING
                 PROGRAM_NAME        = SYST-CPROG
                 DYNPRO_NUMBER       = SYST-DYNNR
*                 FIELD_NAME          = p_file
               IMPORTING
                 FILE_NAME           = p_file .
               if sy-subrc NE 0 .
                  write : / 'Enter File Name'.
               endif.
endform.                    " get_filename
*&      Form fill_data
*       text
* --> p1        text
* <-- p2        text
form fill_data .
*perform open_group.
loop at it_mm01.
clear it_bdcdata.
refresh it_bdcdata.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MTART'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-MATNR'
                               it_mm01-matnr.
*                              '116100'.
perform bdc_field       using 'RMMG1-MBRSH'
                              'C'.
perform bdc_field       using 'RMMG1-MTART'
                              'FERT'.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(16)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(03)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(05)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(06)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(07)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(09)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(10)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(13)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(16)'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '0080'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-VTWEG'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-WERKS'
                               it_mm01-werks.
*                              '9010'.
perform bdc_field       using 'RMMG1-LGORT'
                               it_mm01-lgort.
*                              'F901'.
perform bdc_field       using 'RMMG1-VKORG'
                               it_mm01-vkorg.
*                              '1000'.
perform bdc_field       using 'RMMG1-VTWEG'
                               it_mm01-vtweg.
*                              '03'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MVKE-MTPOS'.
perform bdc_field       using 'MVKE-VERSG'
                                it_mm01-versg.
*                              '1'.
perform bdc_field       using 'MVKE-KONDM'
                                it_mm01-kondm.
*                              '03'.
perform bdc_field       using 'MVKE-KTGRM'
                               it_mm01-ktgrm.
*                              '01'.
perform bdc_field       using 'MVKE-MTPOS'
                                it_mm01-mtpos.
*                              'NORM'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-MTVFP'
                               it_mm01-mtvfp.
*                              '01'.
perform bdc_field       using 'MARC-XCHPF'
                               it_mm01-xchpf.
*                              'X'.
perform bdc_field       using 'BDC_CURSOR'
                              'MARC-LADGR'.
perform bdc_field       using 'MARC-LADGR'
                               it_mm01-ladgr.
*                              '0003'.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-HERKL'
                               it_mm01-HERKL.
*                              'IN'.
perform bdc_field       using 'MARC-HERKR'
                               it_mm01-HERKR.
*                              '01'.
perform bdc_field       using 'BDC_CURSOR'
                              'J_1IASSVAL-J_1IVALASS'.
perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                it_mm01-J_1ISUBIND .
*                              'X'.
perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                                it_mm01-J_1ICAPIND.
*                              'F'.
perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                 it_mm01-J_1IGRXREF .
*                              '2'.
if it_mm01-J_1IVALASS <> '0'.
perform bdc_field       using 'J_1IASSVAL-J_1IVALASS'
                                it_mm01-J_1IVALASS.
*                              '0'.
endif.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MARC-EKGRP'.
perform bdc_field       using 'MARC-EKGRP'
                               it_mm01-ekgrp.
*                              '002'.
perform bdc_field       using 'MARC-XCHPF'
                               it_mm01-xchpf.
*                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'MAKT-MAKTX'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-STEUC'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'MARC-HERKL'
                                it_mm01-HERKL.
*                              'IN'.
perform bdc_field       using 'MARC-HERKR'
                               it_mm01-HERKR.
*                              '01'.
perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                it_mm01-J_1ISUBIND.
*                              'X'.
perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                               it_mm01-J_1ICAPIND.
*                              'F'.
perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                it_mm01-J_1IGRXREF.
*                              '2'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'MAKT-MAKTX'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-XCHPF'
                                it_mm01-xchpf.
*                              'X'.
*perform bdc_field       using 'MARA-IPRKZ'
*                              'D'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MBEW-STPRS'.
perform bdc_field       using 'MBEW-BKLAS'
                                it_mm01-bklas.
*                              '7930'.
perform bdc_field       using 'MBEW-VPRSV'
                                it_mm01-vprsv.
*                              'S'.
perform bdc_field       using 'MBEW-PEINH'
                                it_mm01-peinh.
*                              '1'.
perform bdc_field       using 'MBEW-VERPR'
                                it_mm01-verpr.
*                              '273.75'.
perform bdc_field       using 'MBEW-STPRS'
                               it_mm01-stprs.
*                              '207'.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
CALL TRANSACTION 'MM01' USING it_bdcdata
                                MODE 'A'
                                UPDATE 'A'
                                MESSAGES INTO it_bdcmsgcoll.
CLEAR it_mm01.
endloop.
*perform bdc_transaction using 'MM01'.
*perform close_group.
endform.                    " fill_data
*&      Form bdc_dynpro
*       text
*      -->P_0297   text
*      -->P_0298   text
form bdc_dynpro USING prog scr.
CLEAR it_bdcdata.
it_bdcdata-program = prog.
it_bdcdata-dynpro = scr.
it_bdcdata-dynbegin = 'X'.
APPEND it_bdcdata.
endform.                    " bdc_dynpro
*&      Form bdc_field
*       text
*      -->P_0687   text
*      -->P_IT_MM01_VPRSV text
form bdc_field USING fnam fval.
CLEAR it_bdcdata.
it_bdcdata-fnam = fnam.
it_bdcdata-fval = fval.
APPEND it_bdcdata.
endform.                    " bdc_field
Regards,
Madhu.

Spanish language description for material master

HI SAP Gurus,
can anybody please clairfy this thing for me. we have a material despcription in english in the material master. If we add ES language in the additional data screen what should be the description. Does the system pick automatically? Or the users have to provide it? Or can it be the same as english description with the just the language key as ES.
For example
EN - Seal cap
ES - Seal Cap
please clarify this
thanks
Anusha

Hi Anusha,
SAP provides option to maintain description in diff. languages so people from diff. places can read the description in their language.
There is nothing stopping you from maintaining the description in english for all lang. keys, but i am sure it would make very little sense.
So if you wish to maintain in spanish language, login in using spanish & then maintain the description.
Hope the above clarifies.
If helpful award points
Regards,
Vivek

Material Description to be overwritten in PR/PO from material master

Hi,
when we create a PO/PR from ME51n and ME21n the material description field is mandatory hence inspite of making setting as display only in SPRO the inital screen will except any description and will save it.
Is there any thing else by which the description data can be overwritten from material master so that even if the user enters any xyz description the system overwrites it from the material master.
Regards,
Reena

Hi,
You can very well achieve it by making the field "Material description" a "Display" field in the IMG path: Maintain screen layout at document level
However, you have to use the right "Field selection key" to make the screen changes. For eg. for NB purchase order, the field selection key would be NBF and not ME21N.
The field selection key that is applicable for the document type can be found in "Define Document types" img activity.
I have checked this and it works perfectly fine for both PR & PO.
Once you enter the material number in PR (or PO), the material description is brought from material master and then the field is greyed out. (thought initially the matl. description field looks editable).
<< Moderator message - Point begging removed >>
Cheers.
Prabhu S
Edited by: Rob Burbank on Nov 24, 2011 10:24 AM

Need additional Description of Material apart from Material Master

Dear All,
One of our customer wants to maintain an additional Material Description, apart from the description maintained in the Material Master.
In the material Master, they are maintaining "Manufacturer Part Number" as a description.
In the Customer-Material Info record, they are maintaining "Customer's Part No".
Both are getting printing in the Invoice output.
Apart from these they need to maintain some other decription of material. Where we can maintain this?
For example, in the Material Master, they are maintaining "Manufacturer Part Number", something like "RM20010V". The same is not acceptable for Excise clearace officers. They asked them to maintain the clear description of the material.
Please suggest.
Regards,
Mullairaja

they need to maintain some other decription of material
Go to MM01 / MM02 and click "Select views" so that you can see a field SALES TEXT. You can maintain here and fetch the same to your sale order / billing.
thanks
G. Lakshmipathi

Message ME095 No short text is mantained, update material master

Hi,
While creatin a Preq in ME51N I'm Getting an error message if I log on in Spanish saying there is no short text for that material in Language ES; mantain material master and the error message is ME095 but I'm sure that I already mantaines correctly in MM02 this material, and I don't get this error if create the Preq logged in English.
Any ideas?
Thanks

Hi,.
GO to MM02 -> Basic view --> additional data --> desctription language .
set the EN & enter.
Save. After that error won't come for this.
SAM
Edited by: Saminathan Gopalan on Jul 28, 2010 10:04 AM

Material Master description change

Hi All,
I have a PO created for a material and the PO is released at all levels. Now i change the description of the material using MM02. Now if i check in the PO it is not showing the new description in the short text field.
I made changes to the Vendor name and i see the New name coming up in the PO when i open the PO
Question:
WIll the new description of the material gets displayed on the already existing PO for that material or this new description gets appended only for the Purchase orders which are created after the description change
Please let me know
regards
Pavan

Hi,
PO created before Changes hence they are not comming in old documents.
We cna corelate with following example -
E.g.
u have original docuement (Matrial Master)
u have taken a Xerox copy of that ( Created PO )
now
u have changed the origional document (Material Master)
Changes will never reflect in Xerox Copy unless u get the new xerox or u need to change it manually
but yes u can one thing change it manually-
Remove the line item system will ask u about enter material number then add the same material number u will get the new desription
regards,
sujit

VK11 Material Description Does Not Came from Material Master

Hi Gurus,
Good day. Please kindly help advice where does the material description in VK11 came from as it displays a different description not equal to material master.
Thank you in advance.
Regards,
Rellie

Dear Rellie,
It should show the same as mentioned in MM01. Plz check again d MM03 as description for a matieral wil always b picked from Mat. Master only across SAP.
If still ny specific issue then share otherwise plz close d thread.
regards

MG144 Error Messages while creating Material Master

Hi,
When creating Material Master getting Error for structure field is required. Message Number MG144.
Pls suggest.
Regards,
VR

Go through this note 45998
Or check, which field is required field and try to maintain or just make the optional entry in customizing

Error Message no. MM214 while creating material master

Hi folks!!
While creating material master, when i fill the MRP controller field and press enter, I get the message...
The MRP controller 391 does not exist for plant
Message no. MM214
I have checked, the MRP controller is availble in Master Data for MRP Controller. And we have already created many material master with this MRP Controller.
What could be the possible cause for this error. Please help.
Best regards

Hi Qamar,
Please go thru the bellow threads,
Assignement of MRP controller to Plant
MRP CONTROLLER
MRP Controller
Re: MRP controller extension from plant 1 to plant 2
Thanks,
Swamy H P

Material Master - Same Description - Message No

Similar Messages

Maybe you are looking for