Dumpp Error while creating material MM01

Hi,
While creating the material (mm01) i am getting dump error not allowing to save, 
Message type: MESSAGE_TYPE_X_TEXT
I checked the PPO setting it is active for BP type.
Pls tell me how to solve this issue.
Thanks

Dear Rakesh,
Go to Tr. code. ST22 and analysis the  cause
From initial its seems  thatthere is a Text Field which  might be mandatory and  due to that syestem giving dump, Chek wth  ur abaper

Similar Messages

  • Error while creating material

    I got an error while creating material "Material does not exist or not activated". Can anybody help me.
    BR//
    Irf

    hi
    I think you have posted your question in wrong place.
    Can you please make your question more clear.
    regards!
    ramesh
    Edited by: Ramesh kumar.p on Feb 22, 2010 12:48 PM
    Edited by: Ramesh kumar.p on Feb 22, 2010 12:50 PM

  • Imp of division while creating  Material mm01

    hi guys
                While creating material (mm01) there is option of puting  Div ,and if  v put com div  insted of actual div in material ,Now  while creating  sales order  if v put same material it gives option of various sales area .and we can choos any division along with com div also .
    now my question is when 1 product is assigned or related to 1 division only then wht use of creating com division, wht is d purpose ,
    while creating material specific div we shd  put insted of com div
    plse explain me  if i am wrong 
    and  wht use  of creating  com div here
    thnx
    point ll be rewarded if ans is helpful

    The common division is ideally used for all the products where you do not need to restrict the same to any Sales areas.
    If you want a product to be funcuanally operating in all the sales areas of your comapny code then you assign the same to the Common DIv.
    regards,
    Amlan

  • Error While Creating Materialized View

    Hello,
    I am getting error ORA-22818: subquery expressions not allowed here while creating materialized view. I am using Oracle9i Enterprise Edition Release 9.2.0.1.0. Below pasted is my SQL Script.
    Any help is highly appreciable.
    Thanks
    *********SQL************
    select distinct(id),NAME,(select count(GRADE) from employees where
    nationality like '%US%'and id=a.organization_id and grade=a.grade
    group by ID,GRADE) US,(select count(GRADE) from employees where
    nationality not like '%US%' and organization_id=a.organization_id and grade=a.grade
    group by ORGANIZATION_ID,GRADE) NON_US,grade from employees a
    where grade is not null
    group by GRADE,ID,name
    order by to_number(grade) desc

    Hi,
    This is a documented restriction on MVs. You cannot have a scalar express (i.e a select statement) in the select list.
    You can get round this by joining your select count(grade).. expression in as an inline view in your FROM clause. Or you can create a normal view without the scalar expression, create your MV as a select from this view, then re-define your view to contain the query you want.
    Hope that helps,
    Rod West

  • Screen sequence error while creating material.

    Respected Gurus,
    While creating material, i am getting the following error:
    The data screen descriptions are missing for screen sequence EH
    (Message no. MM329)
    Looks like screen set up issue.
    How do I solve this??
    Please help.
    Jaideep

    Jaideep,
    Check in other logon language like EN or DE.
    You might want to check with basis consultant if all text's are migrated into your logon language.
    If the screens are not standard, texts might only exist in developer logon language.
    Close message if solved.
    regards,
    Edgar

  • Runtime error while creating material master data

    hello sir,
    i am facing one prolem while creating MATERIAL MASTER DATA.
    AFTER GIVING ALL REQUIRED INFORMATION WHEN I AM GOING TO SAVE THE DOCUMENT ITS SHOWING ABAP RUNTIME ERROR.
    MESSAGE TYPE: - MDS_KEYMAP.
    MESSAGE CLASS: 001.
    PLEASE TELL ME WHAT TO DO?
    REGARDS..

    SIR THANK YOU FOR YOUR REPLY.
    I ALREADY DONE THAT DUMP ANALYSIS.
    SO PLEASE KINDLY GIVE ME IN DETAILS ABOUT THAT SOLUTION...

  • Error while creating Materialized View step 3 of 6 using wizard

    have oracle 9i Rel 1 on Windows 2000 server. Master Site has been setup. Database links are created at Materialized view site. But while creating Materialized View Group using wizard there is following error on step 3 of 6.
    Statement:----------------
    /*OracleOEM*/ SELECT 1 FROM SYS.dba_constraints@masterdbname WHERE OWNER='username' and table_name='tabname' AND constraint_type='P'
    Stack Trace:----------------
    ORA-00942: table or view does not exist.
    ORA-02063: preceding line from masterdbname.
    All parameters for replication are correct.
    Please help me early.
    Thanks

    Hello,
    In the masterdbname, logging as sys user, you must grant select permission on sys.dba_constraints view to mvadmin_dbname user (where dbname is the replicated database name).
    Regards,

  • Error while creating Materialized View step 3 of 6

    I have oracle 9i Rel 1 on Windows 2000 server. Master Site has been setup. Database links are created at Materialized view site. But while creating Materialized View Group there is following error on step 3 of 6.
    Statement:----------------
    /*OracleOEM*/ SELECT 1 FROM SYS.dba_constraints@masterdbname WHERE OWNER='username' and table_name='tabname' AND constraint_type='P'
    Stack Trace:----------------
    ORA-00942: table or view does not exist.
    ORA-02063: preceding line from masterdbname.
    All parameters for replication are correct.
    Please help me early.
    Thanks

    Hello,
    In the masterdbname, logging as sys user, you must grant select permission on sys.dba_constraints view to mvadmin_dbname user (where dbname is the replicated database name).
    Regards,

  • Error while creating material thru MM01

    when i try to create material with accounting and costing views , i am not able to save the material
    i get an error message saying
    " no cost estimate number could be assigned"
    the explanation in help for this is
    "If you create accounting data or costing data for a material for the first time, a so-called cost estimate number for the material is assigned by the system.
    However, no such number could be assigned for this material."
    any ideas on solving this problem
    Regards
    Mangesh

    Hi Mangesh,
    Is the material you are dealing with related to REM?
    Can you also type in the error message number.
    Regards,
    Prasobh

  • Error while creating material cost estimate

    Hello All
    I am creating material cost estimate of FG whose components are SF & ROH-2. While creating cost estimate system gives an error message which states: :
    *No cost element segment exists for 40103110 on 01.09.2009
    Message no. CK048
    Diagnosis
    The consumption account found by automatic account determination for material STD-PRICE-SF does not exist for the date 01.09.2009 specified.
    Procedure
    Check the cost element segment's validity period
    Check cost element
    Or, if you have authorization, create a cost element which did not exist previously.
    Create primary cost element*
    Please provide your valuable inputs regarding this error message. Looking forward to your inputs & feedback.
    Regards,
    J K Tharwani

    Dear Jitendra,
    Its Seem primary cost element you mentioned is not defined for 09 period.For this go to KA06,gIve that cost element number and the Valid from  date as 01.09.2009 and valid to date as 30.09.2009, press enter it will take u inside the T.C,feed the relevant data and save.
    Now again take the costing run.This time system should not throw the error.
    Check and Revert back.
    Thanks and Regards,
    Jitendra DIlip Chauhan.

  • Error while creating materialized view which using database link

    Helo!
    I'm getting error "ORA-00942: table or view does not exist" when I want to create materialized view.
    Details:
    1. On destination database I create a database link:
    CREATE DATABASE LINK SDATABASE
    CONNECT TO MYUSER
    IDENTIFIED BY MYUSERPASS
    USING 'ORCL';
    => Command "SELECT * FROM TABLE1@SDATABASE" returns data normally!
    2. On source database I create MATERIALIZED VIEW LOG:
    CREATE MATERIALIZED VIEW LOG
    ON TABLE1
    WITH PRIMARY KEY
    INCLUDING NEW VALUES;
    3. Now, when I want to create MATERIALIZED VIEW on destination database:
    CREATE MATERIALIZED VIEW TABLE1
    REFRESH FAST
    START WITH SYSDATE
    NEXT SYSDATE + 1/1440
    WITH PRIMARY KEY
    AS SELECT * FROM TABLE1@SDATABASE;
    ...I get error "ORA-00942: table or view does not exist"!
    How is that possible if command "SELECT * FROM TABLE1@SDATABASE" returns data normally?
    Thanks,
    Voranc

    And, I'm using Oracle 10g.
    Voranc

  • Error while creating material using MMS1

    Hi All ,
             I am trying to create material (Material type - DIEN) using MMS1.... but its giving error as "The field Component 1 is defined as a required field; it does not contain an entry" .
            Pls suggest / advice on how to correct this error ....
    Thanks ,
    Mridul .

    hi,
    i believe some finctional consultant having knowledge in MM module can easily help u out on this.
    reg,
    nj

  • Batch management error while creating material

    Hi All,
    My client does not want to have qty updating and only value udating for his all materials. we are managing thro by removing qty updating tick for plants.
    Now issue is while craeting material master for semi finished material and while activating batch management tick we are getting below error. While selecting display error icon message read as follows
    " Batch management may not be defined for value-only materials."
    Need all of your help to fix this
    Thanks
    A.Gururajan

    Batches are used to manage stocks not only at material level, you do Batch managment because you require more details for the stock.
    Value-only materials are just the oposite of this:
    Represents a group of articles whose inventory is to be managed on a value basis, but not on an article basis.
    So value-only articles with batch managment does not make any sense.

  • Error while creating Materialized View in AWM

    Hello,
    I am using Oracle 11g with Analytic WorkSpace Manager 11.1.0.6.0A
    I am trying to create materialized view on my Cube..
    The Cube has 5 Dimensions out of which Four are having two levels i.e.,
    TotalA-->DimensionA
    TotalB-->DimensionB...and so on
    And one time Dimension having 4 levels
    TotalTime-->YEAR-->QUARTER-->MONTH
    When i try to create the materialized view, i get an error saying that
    "Your metadata changes have been saved, with the following errors
    CREATE MATERIALIZED VIEW "ENT.CB$TIME_TIME_HIER"
    ORA-02267:column type incompatible with referenced column type"
    When i googled regarding this error, it says to change the datatype of the column..
    But which column's data type is to be changed..Please throw some light regarding this...
    Awaiting for reply..

    My query is as follows:
    SELECT
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.level_name='ALL_MODE' AND m.LONG_DESCRIPTION = 'Type1')then 1 else 0 end)) as Cumm_Type1Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.level_name='ALL_MODE' AND m.LONG_DESCRIPTION = 'Type2')then 1 else 0 end)) as Cumm_Type2Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LONG_DESCRIPTION='product1'AND l.level_name='ALL_MODE'AND m.LONG_DESCRIPTION = 'Type1' )then 1 else 0 end)) as Cumm_product1_Type1Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LONG_DESCRIPTION='product1'AND l.level_name='ALL_MODE'AND m.LONG_DESCRIPTION = 'Type2')then 1 else 0 end)) as Cumm_product1_Type2Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.LONG_DESCRIPTION='Mode1'AND m.LONG_DESCRIPTION = 'Type1')then 1 else 0 end)) as Cumm_Mode1_Type1Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.LONG_DESCRIPTION='Mode1'AND m.LONG_DESCRIPTION = 'Type2')then 1 else 0 end)) as Cumm_Mode1_Type2Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.LONG_DESCRIPTION='Mode2'AND m.LONG_DESCRIPTION = 'Type1')then 1 else 0 end)) as Cumm_CLRING_Type1Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.LONG_DESCRIPTION='Mode2'AND m.LONG_DESCRIPTION = 'Type2')then 1 else 0 end)) as Cumm_Mode2_Type2Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.LONG_DESCRIPTION='Mode3'AND m.LONG_DESCRIPTION = 'Type1')then 1 else 0 end)) as Cumm_TRSFER_Type1Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.LONG_DESCRIPTION='Mode3'AND m.LONG_DESCRIPTION = 'Type2')then 1 else 0 end)) as Cumm_Mode3_Type2Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.level_name='ALL_MODE' AND m.level_name = 'ALL_TYPE')then 1 else 0 end)) as Cumm_Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.long_description='Mode3' AND m.level_name = 'ALL_TYPE')then 1 else 0 end)) as Cumm_Mode3_Txn_Amount,
    sum(cd.SALESAMT *(case when (k.LEVEL_NAME = 'ALL_product' AND l.long_description='Mode2' AND m.level_name = 'ALL_TYPE')then 1 else 0 end)) as Cumm_Mode2_Txn_Amount,
    sum(cd.SALESAMT *(case when (k.long_description = 'product1' AND l.level_name='ALL_MODE' AND m.level_name = 'ALL_TYPE')then 1 else 0 end)) as Cumm_product1_Txn_Amount,
    sum(cd.SALESAMT *(case when (k.long_description = 'product1' AND l.long_description='Mode1' AND m.LONG_DESCRIPTION = 'Type1')then 1 else 0 end)) as Cumm_product1Mode1Type1_Txn_Amount,
    sum(cd.SALESAMT *(case when (k.long_description = 'product1' AND l.long_description='Mode1' AND m.LONG_DESCRIPTION = 'Type2')then 1 else 0 end)) as Cumm_product1_Mode1_Type2_Txn_Amount,
    sum(cd.SALESAMT *(case when (k.long_description = 'product1' AND l.long_description='Mode1' AND m.level_name = 'ALL_TYPE')then 1 else 0 end)) as Cumm_product1_Mode1_Total_Txn_Amount
    /* From dimension views and cube view */
    FROM CUSTOMER_ID_CUSTOMER_ID_HIE_VIEW b,
    TIME_TIME_HIER_VIEW j,
    product_product_HIER_VIEW k,
    MODE_MODE_HIER_VIEW l,
    TYPE_TYPE_HIER_VIEW m,
    CUBETEST_VIEW cd
    /* Create level filters */
    WHERE b.level_name = 'CUSTOMER_ID'
    AND b.LONG_DESCRIPTION='xyz'
    AND j.LEVEL_NAME='MONTH'
    AND j.END_DATE between to_date('2007-10-31','YYYY-MM-DD') and to_date('2007-10-31','YYYY-MM-DD')
    /* Join dimension views to cube view */
    AND b.DIM_KEY=cd.ACCOUNT_ID
    AND j.DIM_KEY=cd.TIME
    AND k.DIM_KEY=cd.product
    AND l.DIM_KEY=cd.MODE
    AND m.DIM_KEY=cd.TYPE
    ORDER BY j.end_date,
    k.level_name,
    l.level_name,
    m.level_name;

  • Error while creating Materialized Views

    I tried creating Materialized views with set operator, and Oracle throws up an error message
    ORA-30370: set operators are not supported in this context
    The script,
    CREATE MATERIALIZED VIEW ORADBA2.MV_GP_AGG_00055_MMR1
    PCTFREE 0 TABLESPACE GPMTSPOC
    STORAGE (INITIAL 128K NEXT 128K MAXEXTENTS UNLIMITED)
    BUILD IMMEDIATE
    REFRESH COMPLETE
    ENABLE QUERY REWRITE
    AS
    SELECT * FROM tb_gp_agg_00055r1_01
    WHERE srce_sys_cd = 15
    UNION ALL
    SELECT * FROM tb_gp_agg_00055r1_02
    WHERE srce_sys_cd = 15
    UNION ALL
    SELECT * FROM tb_gp_agg_00055r1_03
    WHERE srce_sys_cd = 15;
    Will Oracle support UNION clause in Materialized Views?? Any work arounds ?? Thanks.
    null

    SET operators cannot be used in MATERIALIZED VIEWS.
    A workaround is that you create a table AS SELECT using the SET operators and then create the materialized view from that table.
    But then you'll not be able to take advantage of QUERY REWRITE AND AUTOMATIC REFRESH.
    But if you would still like to have the materialized view then this will work!!

Maybe you are looking for