Error creating a material in MM01

Dear,
While creating a material in MM01 the following error is appearing
"The Value 770190.60 is not allowed for the field control code".
MM01 -- Mat. No, Ind. Type, Finished Product, ENTER.
Selecting Views - BASIS DATA 1, BASIS DATA 2, & SALES : General / Plant Data, ENTER.
Entering PLANT, SALES ORG. & Dist. Channel, ENTER.
This Shows a message
" Material Already exists & will be extended".
Enter.
Save.
Then this error message is appearing
"The Value 770190.60 is not allowed for the field control code".
What will be the cause & solution of this error.

Dear,
While creating a material in MM01 the following error is appearing
"The Value 770190.60 is not allowed for the field control code".
MM01 -- Mat. No, Ind. Type, Finished Product, ENTER.
Selecting Views - BASIS DATA 1, BASIS DATA 2, & SALES : General / Plant Data, ENTER.
Entering PLANT, SALES ORG. & Dist. Channel, ENTER.
This Shows a message
" Material Already exists & will be extended".
Enter.
Save.
Then this error message is appearing
"The Value 770190.60 is not allowed for the field control code".
What will be the cause & solution of this error.
This no. is seen in the error message only & we are not entering this value in MM01.
When i am looking at the Chapter ID (2nd option) through J1ID then this value can be seen.
But when i am at MM01 - Foreign Trade : Export Data - I find nothing mentioned in it.
The material is already created in Location 1 & now we are creating this material again in Location 2 in same plant.
The error message number is MG-142.
We are not copying material from 1 Plant to another but from 1 Loc to 2nd Loc.
Its not a new material but is already exists
say in Plant 5000 & Loc. RP01 & now we are creating it again in Plant 5000 & Loc SP01 & here we are receiving this error of Value xyz which can be seen in J1ID.
Thanks.

Similar Messages

  • [urgent ]runtime error  occured while creating the material using mm01

    hai
    am configure the ale program now . the problem is occured during the creating the material using mm01.
    am using client 000 (sending system). and i want to send the material to the client 400(receiving system)
    while am  save the created material using t-code mm01 in client 000 . it depicts the error as
    syntax error in program SAPLC140. 
    plz resolve this problem.
    regards
    surender

    Hi,
        In MM01 transaction code u have a problem..normally u will go to mm01 screen to create the material..i thought the same error will occur...so call basis to rectify this problem..
    Thank u,
    Manjula Devi.D

  • Error while creating a material master (mm01)

    hi,
    I'm getting this error message when I'm creating a material master in a specific plant/sloc. I'm probably guessing its in config. I really need some help here.
    "Tables TCURM and T001W inconsistent; notify your system administrator" .
    could any one  draw some light on this.
    thanks regards,
    chinta

    HI,
    Before creation of plant 1st check in t.code:OMSA and see your plant assigned to field reference.
    Check in t.code: OMSY, see your company code entry & active for material management.
    Also check your plant is active for your material type in t.code: OMS2 with quantity & value updating.
    ###Check assignment of plant to company code in t.code: OX18 and see activation of your valuation are in t.code: OX14
    Just cross check all material master customisation , refer link with t.codes:
    Re: Material Master
    Regards,
    Biju K

  • Creating Material Master IDoc when creating a Material

    Hi Guys,
        My requirement is to trigger an IDOC at the time when I am creating a material using MM01 transaction. The Changepointer is active and when i am tring to send materials using BD10 it's showing that the IDOC is created which certifies that the config is OK. but when I am creating a material and saving it ..the same process is not triggering an Idoc.
    Can anyone help me out ...where I am missing out.
    Thanks
    Debasis Roy Chowdhury

    Hi Debasis,
    Activating pointers for the message type do not  trigger Idoc, we need to manually or scheduled the program to create the idoc against  pointers.You need to run BD21 transaction or  schedule RBDMIDOC .
    Go through this [Idoc Triggers|Automatic Trigger of Idoc Sending to PI on Material Master Create/Change;.There is a good discussions.
    Regards,
    Madhu.
    Edited by: madhurao123 on Feb 2, 2012 9:40 PM
    Edited by: madhurao123 on Feb 2, 2012 9:43 PM

  • How to see different views created for material

    hello sap gurus
    How to see, under which all views the material has been created?
    Points will be given
    Thanks in advance
    Vijay

    Hi
    The no of views to be opened when you create a material in MM01 depends on the Material type
    BY changing the material types the views can be changed
    IMG->logistics general>Material Master>Basic settings>Material types-->Define attributes of material types
    Here only the settings is done
    Raja

  • When am creating the material using the transaction MM01 getting the error

    Hi all,
      Could you please help me to solve this issue, When I am creating the material using the transaction MM01, am receiving the error message "Express document "Update was terminated" received from author "XXXXXXXX", I checked the in SM13 found error message showing in Z_LGPLA_BIN_POSTING.
    Regards,
    Muralikrsihna.

    ST22 Error is : SAPSQL_ARRAY_INSERT_DUPREC, below is full error message
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "Z_LGPLA_BIN_POSTING" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    Regards,
    Muralikrishna

  • Error when I create the New material Master (MM01) for New Plant.

    Dear experts,
    I got the error when I create the New material Master (MM01) for New Plant.
    Error:  Valuation Area 2800 Not yet productive with Material Ledger.
    So Pl send me the solution asap.
    Venkata Raju Khottari

    Hi,
    Have u assinged Plant to Company code?
    If u say no, use T.code OX18.
    Regards,
    Murali
    Assign points if it is useful.

  • Error while creating a material using Bapi_material_savedata

    Hi,
    there is an error encountered while creating a material using BAPI_MATERIAL_SAVEDATA..
    The Error description is " Material description is not transfered " even after supplying the Material description and other mandatory field information like industrial sector, material type ,basic view indicator,Base UOM,Base UOM ISO code.
    Please let me know the solution, if you know.

    Hi,
    Please search the SCN for the answers
    https://www.sdn.sap.com/irj/scn/advancedsearch?query=errorinBAPI_MATERIAL_SAVEDATA+&cat=sdn_all

  • Recieving ORA-01722 invalid number error while creating a materialized view

    Hi,
    I am receiving a ORA-01722 invalid number error while creating a materialized view. when run the select statement of the view i don't get any error, but when i use the same select statement to create a materialized view i receive this error. Could any please help in resolving this error. Here is the code i am using to create a materialized view.
    CREATE MATERIALIZED VIEW MV_EBS_CH_CLOSED
    REFRESH FORCE ON DEMAND
    AS
    SELECT DISTINCT kr.request_id, org.org_unit_name,
    ebs_ch_ticket_type (kr.request_id) ticket_type,
    DECODE
    (kr.status_code,
    'CLOSED_SUCCESS', kr.last_update_date,
    'IN_PROGRESS', (SELECT MAX (start_time)
    FROM ebs_ch_datastore ecd1
    WHERE kr.request_id = ecd1.request_id
    AND workflow_step_name =
    'Final BA Review and Deployment Exit Criteria')
    ) closed_date,
    substr(krhd.visible_parameter12,1,10) siebel_start_date,
    kr.creation_date itg_start_date
    FROM kcrt_requests kr,
    kcrt_request_types krt,
    kcrt_req_header_details krhd, kcrt_request_details krd1,
    (SELECT koum.user_id user_id,
    DECODE (koup.org_unit_name,
    'IT Implementations', 'CHS - Service Management BA',
    koup.org_unit_name
    ) org_unit_name
    FROM krsc_org_unit_members koum, krsc_org_units koup
    WHERE 1 = 1
    AND 'Y' = koup.enabled_flag
    AND koum.org_unit_id = koup.org_unit_id
    AND EXISTS (
    SELECT 'X'
    FROM krsc_org_units kouc
    WHERE koup.org_unit_id = kouc.org_unit_id
    START WITH kouc.parent_org_unit_id =
    ANY (SELECT org_unit_id
    FROM krsc_org_units krsc_org_units1
    WHERE 'Clearinghouse' =
    org_unit_name)
    CONNECT BY kouc.parent_org_unit_id =
    PRIOR kouc.org_unit_id)
    UNION
    SELECT kou.manager_id user_id,
    DECODE
    (kou.org_unit_name,
    'IT Implementations', 'CHS - Service Management BA',
    kou.org_unit_name
    ) org_unit_name
    FROM krsc_org_units kou
    WHERE 'Y' = kou.enabled_flag
    START WITH kou.parent_org_unit_id =
    (SELECT org_unit_id
    FROM krsc_org_units krsc_org_units2
    WHERE 'Clearinghouse' = org_unit_name)
    CONNECT BY kou.parent_org_unit_id = PRIOR kou.org_unit_id) org
    WHERE krt.request_type_id = kr.request_type_id
    AND krt.request_type_name IN ('Bug Fix', 'IT Enhancement')
    and kr.REQUEST_ID = krd1.request_id
    and krd1.batch_number = 1
    AND kr.request_id = krhd.request_id
    AND org.user_id in (krd1.parameter4, krd1.parameter5, krd1.parameter7)
    AND ( 'CLOSED_SUCCESS' = kr.status_code
    OR 'IN_PROGRESS' = kr.status_code
    AND kr.request_id IN (
    SELECT request_id
    FROM (SELECT DISTINCT request_id,
    MAX
    (start_time)
    closed_date
    FROM ebs_ch_datastore
    WHERE 'Final BA Review and Deployment Exit Criteria' =
    workflow_step_name
    GROUP BY request_id))
    Thanks,
    Shaik Mohiuddin

    This error occurs when you try to create a materialized view , but if you run the sql the results are perfectly fine. Well it happend to me also and to fix this I made sure all the coulmns have the same data type which are used in joins or in where clause.
    use
    where
    to_number(col1)=to_number(col2) and to_number(col3)=to_number(col4)
    hope this helps..

  • ORA-00905: missing keyword error while creating a materialized view

    Hi Gurus,
    I am trying to create a materialized view as :
    1 CREATE MATERIALIZED VIEW AMREG.ClientData
    2 TABLESPACE AMREG_DATA
    3 COMPRESS
    4 PARALLEL
    5 NOLOGGING
    6 BUILD IMMEDIATE
    7 REFRESH COMPLETE
    8 ON DEMAND
    9 DISABLE QUERY REWRITE
    10 REFRESH START WITH TRUNC( SYSDATE + 1 ) + 3/24 NEXT TRUNC( SYSDATE + 1 ) + 3/24
    11 AS
    12 SELECT
    13 CHILD.CLIENT_SGK "Child SGK",
    14 CHILD.CLIENT_NAME "Child Name",
    15 CHILD.ARC_ACCT_CD "Child ARC Acct Code",
    16 ULTIMATE.CLIENT_SGK "Ultimate Parent SGK",
    17 ULTIMATE.CLIENT_NAME "Ultimate Parent Name",
    18 ULTIMATE.ARC_ACCT_CD "Ultimate ARC Acct Code",
    19 HIER.LVL_FROM_ANCESTOR ,
    20 FROM [email protected] CHILD,
    21 [email protected] HIER,
    22 [email protected] ULTIMATE
    23 WHERE HIER.DESCENDANT_CLIENT_SGK = CHILD.CLIENT_SGK
    24* AND ULTIMATE.CLIENT_SGK = HIER.ANCESTOR_CLIENT_SGK;
    SQL> /
    REFRESH START WITH TRUNC( SYSDATE + 1 ) + 3/24 NEXT TRUNC( SYSDATE + 1 ) + 3/24
    ERROR at line 10:
    ORA-00905: missing keyword
    DBLink name is : DNYCPH60.WORLD
    Please guide me on this and help to resolve the issue.

    Ummm how about not posting the same question 4 times in 3 different forums?
    Gints Plivna
    http://www.gplivna.eu

  • Error message while creating configurable material for variant configuration.

    Dear All,
    I want to create configurable material for the purpose of variant configuration. When trying to create configurable material using mm 01 or mm k1, it is displaying an error message that internal number assignment is not possible for the material type configurable materials as well in using external number also. Can anyone specify the steps to be done in creating the configurable material. Thank you all.
    Regards
    Akula Sivaji Kumar Madhu Kiran

    If you want to set these material type to another group (Which has a internal number and external number range), then you can do it.
    In MMNR, Click on the Edit Group.
    Then select the material type and click select element.
    Then mark a tick option in another group and then press Element/Group.
    Then you can see the material type will come under this group.
    Now save your entry, and create a material with this material type.

  • Error while creatting the Material Master IDOC in ERP 2005

    Hello All,
    I am trying to create scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0).
    I am using Auto ID 4.0 on a NW04s system. The backend is a ERP2005 system.
    The scenario requires that I need to create a material in the backend and send it to the NW04s system using IDOCs.
    After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID from the transaction AIDMM. I get a message that IDOC is just being created. But I could not find it in the transaction WE02.
    On debugging I found that the function MARD_GENERIC_READ_MATNR_PLANT resulted in error.
    Thanks for any kind of input.
    Regards,
    Rahul
    Message was edited by:
            Rahul Gavande

    Dear,
    Check ABAPer for file settings.
    - CANNOT_SKIP_ATTRIBUTE_RECORD : The attributes could not be read in the EPS parcel. The file cannot be opened for reading, because it may have been deleted in the meantime.
    - CANNOT_DETERMINE_EPS_PARCEL : The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must download the relevant patch again (for example, Hot Package).
    - CANNOT_DETERMINE_DATA_FILES : The name of a data file could not be determined, because a profile parameter was not correctly configured. Check the settings using the report RSPARAM.
    - CANNOT_DISASSEMBLE_R_DATA_FILE : An R3trans data file could not be unpacked. A possible error source is that the relevant EPS parcel was not found. The data file could not be opened for writing. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data (UNIX).
    - CANNOT_DISASSEMBLE_D_DATA_FILE : An ADO data file could not be unpacked. The reasons are the same as with the message CANNOT_DISASSEMBLE_R_DATA_FILE .
    - CANNOT_CREATE_COFILE : The cofile could not be created from the relevant data file. One possible error source is that <sys>adm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX).
    Check Note: 70752.
    Regards,
    Syed Hussain.

  • Update Termination while creating Material Master MM01

    Hello,
    While creating the Material Master system is throwing the error Update was Terminated.
    Before that we have client copied.
    Can anybody throw some light??
    Regards,
    Kumar Rayudu

    Hi,
    Check the material number ranges are copied ?
    in SPRO>LOGISTICS GENERAL>MAT.MASTER>BASIC SETTING>NUMBER RANGES FOR MAETRIAL TYPES
    BR
    Diwakar

  • Error in number range when creating new material

    Hi All,
    We just recently changed the number range format of our material master. Earlier it was numerical and no it contains alphanumeric data.
    To do the change, in the material type i selected the option "External Number Assignment w/o check".
    Now i deselcted the option and tried to create a material with the old number range, it does not allow me to do so.It gives the error "Number 12345 not defined for Material Type".
    What changes need to be done to allow numerical characters to be accepted?
    Please advice.
    Thanks,
    Savindi

    Hi All,
    The issue seems to be that the number range has not got assigned to an element. When i try to assign an element, i get the following error-
    NR020- The number range interval with number 01 must be internal
    Please advice,
    Thanks,
    Savindi

  • Create Long Text in MM01 for material

    Hi,
    I'm trying to create long text in MM01. After entering industry sector and material type and also the necessary views, i hit EDIT --> Long Text , the create text option is greyed out (inactive)..
    How can i make this work ? Or is there any other field where i can use long text ?
    thank you..

    Our client's material master data for material text is longer than 40 characters.. and it's impossible for them to reduce this to 40 charac.
    So i need to find another field which they can use..
    I wonder if i use po text, can i use it for developed reports, in search helps .. etc.. I'm not sure..
    And also I have no clue about how will i use the long text in EDIT menu..

Maybe you are looking for

  • Detect external Monitor

    My Sprectre X360 does not detect my SyncMaster 2493HM Monitor using an HDMI cableIt does detect a newer Samsung monitor using HDMI

  • Dynamically  Visibilty of Input Field in Interactive PDF Form

    Hi All, I want to bind the visibilty of Input Field dynamically in an Interactive PDF Form. How can I do ? Please give me some solution Regards Manish

  • Lenovo A806 - chinese characters problem

    Hello, i have little problem, when i try to unlock the phone screen (more exactly to slide up the wallpaper) and enter in contacts or message, chinese characters appears and when it's fully slided up, they automated get translated in the languages th

  • Copying Time Machine Backup

    hi i'm transferring Bacckups.backupdb to a new external hardrive - however, when I copy over the file structure is disrupted So on the original drive everything is correct file structure... Backups.backupdb/MyMacbookPro/x14 dated folders after copyin

  • DTR component not fully functional

    Hi all, We recently tried to change the DTR repository properties file, according to SAP NOTE: 1001509. After performing the process mentioned in this note, we noticed this particular repository.properties file has the wrong content (I downloaded the