Extend Material Views

I am trying to add the Warehouse Management view to my material views.
I've gone into SPRO --> Define Attibutes of Material Types and selected/saved the Warehouse Management view, but it still does not show up in my material views.
All help is appreciated.

Hello Cameron...
R u extending the material views for an already maintained MM?
If so,plz go again into MM01 and give the material No: and start creating,here you can select the View of WH.
Prerequisite:You have maintained the views for the material type in OMS2.
See if the WH is asssigned to the plant for which u r creating the Material Master
Hope this Helps
Arshad
Edited by: arshad ahmed on Jul 27, 2009 5:30 PM

Similar Messages

  • Do I need to extend QM view in Material Master

    Hi,
    We never use QM module in our company however, we have a mini project which is ONLY to use QM module's quality notification to perform complains and problem resolution of company product.
    Hence, under above scenario do we need to extend QM view in material master in order to use Quality Notification?
    Regards,
    Tuff

    No. You don't need to extend QM view if you want to use QM notification only. However, you would need to maintain respective master data and that again depends on the process you follow.
    ntn

  • Extend Classification View for Material Master

    Hello, How do I extend classificiation view for Material Master? Is there any BAPI or FM to do that?
    I cant find any place to extend it with BAPI_MATERIAL_SAVEDATA

    Hi,
    Use this FM to create Classfiaction view BAPI_OBJCL_CREATE
    Regards,
    Shan

  • Help for extending material in sales view

    hi there
                  I am extending material to sales view .
    path
    SAP R/3
    Easy Access:
    Logistics> Sales and Distribution-> Master Data-> Products> Material-> trading Goods--> create
    Question: create sales view for trading goods
    Difficulty: the Sap system does not show sales org. 1 view, sales org. 2 view and Sales: general plant view.
    How to create that?
    Please email me if you find some solution
    Thanks
    Nishant
    [email protected]

    Hi, this post does not belong into SAP Solution Manager forum. Regards Andreas

  • MM50 : add new column in the material view

    Dear guru.
    I need to add a new column of material master in the material view of MM50.
    Do you have a solution (exit) in order to solve my problem ?
    Thanks.

    > I need to add a new field in the MM50 transaction not in MM02.
    Der Friend,
    Pls be specific about your query. As you know MM50 is for material view extension which is a std SAP trxn to help extend the views set by standard SAP pack and if you are referring new field as a new view then it is not so easily approachable.
    Shiva

  • How to get a materialized view get to refresh itself after the job is "broken"

    we created a materialized view sometime ago with the following statement:
    create materialized view SXV_PUB_EMPLOYEE_CERT_ALL_M
    refresh complete on demand
    start with to_date('30-08-2009 04:00:00', 'dd-mm-yyyy hh24:mi:ss') next trunc(sysdate) + (28/24)
    as
    select  sxv_emp_cert_all.*
    from    sxv_employee_certification_all sxv_emp_cert_all;
    this week we found out it had not been refresh for about a month
    In dba_jobs the column broken was 'Y', next_date time something like 01-01-4000 and failures 16
    when I ran it manually by executing
    BEGIN DBMS_MVIEW.REFRESH('SXV_PUB_EMPLOYEE_CERT_ALL_M', 'C'); END;
    I found that one of the columns was too small (probably a columns of one of the underlying tables had been extended since the creation of the materialized view)
    After fixing this I ussied yesterday (on 29-8-2013) the statement :
    alter materialized view SXV_PUB_EMPLOYEE_CERT_ALL_M
    refresh complete on demand
    start with to_date('30-08-2009 04:00:00', 'dd-mm-yyyy hh24:mi:ss') next trunc(sysdate) + (28/24)
    after this the table dba_jobs showed me 30-08-2013 04:00:00 as next date
    I was expecting it to run this night at 04:00, but it didn't
    the last_date column value was still from about a month ago, the column broken still shows 'Y'
    and the next date 30-08-2013 04:00:00 (while it should been set to 31-08-2013 01:00:00
    Rrunning
    BEGIN DBMS_MVIEW.REFRESH('SXV_PUB_EMPLOYEE_CERT_ALL_M', 'C'); END;
    gave no errors this time
    and in User_Mview_Analysis the last_refresh_date column showed the date/time I had executed it
    Any idea how to get the job "unbroken" again so that the view refreshes itself every night?
    the database is Oracle Database 10g Release 10.2.0.4.0
    regards,
    Remco

    thanx for all your helpful and correct answers . but eventually I found it myself
    exec dbms_job.broken(<jobnumber>, false);

  • Creation of Materialized View is taking Long Time

    Hi All,
    In the execution of PLSQL script, I am executing the following sequence.
    First step I am creating the materialized view A, and Materialized view B using DB Links. In the same script as a part of second step I am creating one more materialized view with the combination of Materialized view A and Materialized view B and a table with DB links. But creating of this materialized view is taking 15 hours, I am using Refresh is COMPLETE. I am using a separate tablespace for this and it is Auto Extend Clause. Can any body tell me or suggest where exactly I had done the mistake.
    Thanks,

    pujakhetan wrote:
    is this posiible to do fast refresh on above mentioned Materialized view ??
    I dont have much information about restriction which exists for materialized view refresh .then consider to actually Read The Fine Manuals found at http://docs.oracle.com to obtain desired details

  • Issue in Complete Refresh of a Materialized View

    Hello,
    We have an MV in the Datawarehouse that does a FAST REFRESH daily. Every Saturday, a COMPLETE REFRESH is done as part of the normal Database Activities. The Database is Oracle 9i. The MV contains a Join between a Dimension and Fact Table of a Datawarehouse and does a FAST REFRESH using the MV logs.
    However, last Sat, the COMPLETE REFRESH has failed. The DBA tried to run the script twice again but it failed on both occasions with an UNDO TABLESPACE error (ORA-30036). The DBA tried to extend the Tablespace; it did not help either.
    - Could this be linked to Tablespace allocations for the MV? Are there any specific steps that can be followed to resolve this?
    - Can the MV be dropped and re-created?
    Would appreciate a response on the same.
    Many Thanks,
    Ketan

    Hi Ketan,
    I guess this is probably because MV complete refresh performs "delete" from the MV and then insert. If the MV is large, it may fail on undo allocation.
    Please take a look at Re: materialized view refresh time!  Plz Help me! you can see the explanation, metalink note and the solution (how to perform truncate instead of delete).
    HTH
    Liron Amitzi
    Senior DBA consultant
    [www.dbsnaps.com]
    [www.orbiumsoftware.com]

  • ORA-12008: error in materialized view refresh path with ORA-01652

    I have a temp tablespace with 2 tempfiles of 2GB each (total 4GB) but still refresh of materialized view is failing with following error:
    5646690 - BIS Materialized View Refresh Program
    ORA-12008: error in materialized view refresh path
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP1
    I checked and temp ts is completly filled
    SQL> select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;
    TABLESPACE_NAME BYTES_USED BYTES_FREE
    TEMP1 2147483648 0
    TEMP1 2147483648 0
    My question is how do I find out how much space I need for temp tablespace. what 's the best practise to size temp tablespace when running refresh. refresh is done by client who is submitting a request thru ebiz apps so I 'd like to size it correctly without having to keep guessing.
    Thanks so much in advance for any help

    Hello,
    Temp tablespace size depends how much sort by , order by operation your application performing. You can create new temp tablespace and drop old one with bigger file size
    CREATE  TEMPORARY TABLESPACE TEMP02 TEMPFILE '\mypath_to_temp\TEMP02' SIZE 256M REUSE AUTOEXTEND ON NEXT 256M MAXSIZE 8192M EXTENT MANAGEMENT LOCAL;
    ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP02;
    Drop tablespace temp including contents; -- Make sure you delete on temp data files.Here is link for your reading purpose
    http://www.idevelopment.info/data/Oracle/DBA_tips/Tablespaces/TBS_3.shtml
    Regards
    Edited by: OrionNet on Mar 6, 2009 6:15 PM

  • To extend material master in condition that split valuation.

    I want to valuate the material at two different valuation class
    if the material is produced internally  and procured externally.
    So I use split valuation function.
    I created accounting view  using valuation category  at plant level and
    I extended accounting view using valuation type.
    I tried to extend material master for other plant in condition that
    I didnu2019t check batch management in purchasing view
    but I mat error message u201CIndividual batch valuation not possible hereu201D(M3184).
    To extend material master for other plant, Should I check batch management
    in purchasing view ?

    Hi,
    Select the batch management indicator on purchasing view, press F1 button and check technical details. If the field is:
    MARA-XCHPF --> batch management is active at client.
    MARC-XCHPF --> batch management is active at plant level
    Please check SAP online help on batch level:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/25/2838714f7811d18a150000e816ae6e/frameset.htm
    Batch Levels
    Plant level
    The batch number is unique in connection with the plant and material.
    The batch number is only known in the plant in which it was created if the stock is transferred to another plant, the batch is unknown in the recipient plant and the system does not adopt any data. You have to recreate and specify the batch in the receiving plant; that is, the same batch number may have different specifications in several plants.
    Material level:
    The batch number is unique in all plants in connection with the material.
    The same batch number has the same meaning for the material in all plants. One batch number cannot have different specifications in different plants. During stock transfer to another plant, the specification of the batch is known in the destination plant even if the batch is placed into storage in that plant for the first time.
    Client level:
    The batch number is unique in the whole client. A batch number can only be assigned once in the client. You cannot assign the same batch number for different materials.
    The batch number is only unique at the chosen level.
    If your batch maagement is valid at client / material level you defined it once in table MARA and it is valid for all your plants - that's why you get it automatically (if this is the reason in real).
    Regards,
    Csaba
    Edited by: Csaba Szommer on Nov 7, 2009 5:13 PM

  • Materialized view problem

    Hi all,
    while refreshing MV I have the following error any idea why ?
    SQL> exec dbms_mview.refresh('ACCT_STMT_MV','c');
    BEGIN dbms_mview.refresh('ACCT_STMT_MV','c'); END;
    ERROR at line 1:
    ORA-12008: error in materialized view refresh path
    ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDO'
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2430
    ORA-06512: at line 1Regards

    Try:
    ALTER TABLESPACE {YourUndoTS} ADD DATAFILE '...etc...';or
    ALTER DATABASE DATAFILE '{YourUndoDatafile} RESIZE 10240M;

  • Refresh Materialized views

    Hi,
    While I was refresh the materialized view I found below error.
    SQL> exec dbms_mview.refresh(MV1','C');
    BEGIN dbms_mview.refresh('MV1','C'); END;
    ERROR at line 1:
    ORA-12008: error in materialized view refresh path
    ORA-01652: unable to extend temp segment by 1280 in tablespace TEMP
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2251
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2457
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2426
    ORA-06512: at line 1
    I increased 3 gb, again got the smw error
    and the 11gb TEMP tablespace size was full.
    So please advise How to resolve this issue?
    Thank,
    Praveen

    Hello,
    You should check your Temporary Tablespace so as to be sure of which statement is consumming so much
    space. The following query may help you:
    SELECT S.sid || ',' || S.serial# sid_serial, S.username, Q.hash_value, Q.sql_text,
    T.blocks * TBS.block_size / 1024 / 1024 "Mo used", T.tablespace
    FROM v$sort_usage T, v$session S, v$sqlarea Q, dba_tablespaces TBS
    WHERE T.session_addr = S.saddr
    AND T.sqladdr = Q.address
    AND T.tablespace = TBS.tablespace_name
    ORDER BY S.sid;On the other hand, is this refresh worked before or is it a new MV to refresh ?
    Which option did you use to create this MV ?
    Best regards,
    Jean-Valentin

  • How to extend material/customer

    Hello Experts
                         If I want to extend one material for different plant/sales org/storage location then how can i do this . Same for the customer , if i want to extend that customer for other sales areas then how can i do that ?
    Regards-
    Abhi

    Hi,
    You can extend material to different plant and sales organisation by using the T.Code "MM01".
    Enter the material number you want to extend and enter the same under copy from.Press Enter.
    Select the required views and enter new the plant and Sales organisation you want to extend.
    In a similar way,you can extend customer data as well.
    Regards,
    Krishna.

  • How to extend material cross many plants using BAPI?

    Hi.
    when i use BAPI 'BAPI_MATERIAL_SAVEDATA' to extend material cross plants, i can not extent accounting view.
    code as below:
                BAPI_MARC-PLANT = IT_GOUJIAN-WERKS.
                BAPI_MARCX-PLANT = IT_GOUJIAN-WERKS.
                CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
                  EXPORTING
                    headdata            = BAPIMATHEAD
                   CLIENTDATA          = BAPI_MARA
                   CLIENTDATAX         = BAPI_MARAx
                    PLANTDATA           = BAPI_MARc
                    PLANTDATAX          = BAPI_MARcx
                   VALUATIONDATA       = BAPI_MBEW
                   VALUATIONDATAX      = BAPI_MBEWX
                  IMPORTING
                    RETURN              = IT_RETURN.
                 TABLES
                   MATERIALDESCRIPTION = IT_MATERIALDESC.
    i just change the plant data.
    any advice?

    You can extend the material in several plants using
    BAPI_MATERIAL_SAVEDATA
    All you need to do is populate the import parameter
    WA_HEADDATA-MATERIAL
    WA_HEADDATA-IND_SECTOR
    WA_HEADDATA-MATL_TYPE
    and check the views that you want to maintain in the new plant.
    Suppose you want to maintain only Basic view than..
    WA_HEADDATA-BASIC_VIEW = 'X'.
    And based on selected views , you need to populate other
    parameters.
    like I want to maintain basic view in another plant than
    I need to populate the plant data.
    WA_PLANTDATA-PLANT = <PLANT>.
    populate other fields, if required.
    WA_PLANTDATAX-PLANT = <PLANT>.
    populate flags, if required.
    and pass these parameters to the Function module.
    It should work.
    Please reward, if you find the answer useful.

  • Extend Material Master - Sales Org.

    Hi,
    I want to copy the material from one sales org. distribution channel to another sales org. distribution channel. My doubt is I want to use BAPI_MATERIAL_SAVEDATA. But how to use this??
    Because that material is not present in the target sales org. distribution channel, so for that I have to copy all the views except sales view using BAPI_MATERIAL_GETALL then pass to BAPI_MATERIAL_SAVEDATA.
    In this the problem is.. I have to map all the fields between these BAPI. So is there any easy way to do this?
    Can anyone have similar requirement like this which can share??
    Thanks,
    Regards,
    Jhings.
    Edited by: Jhings on Mar 7, 2012 7:26 PM

    Check these threads about the mandatory fields for your requirement:
    BAPI_MATERIAL_SAVEDATA extend for new plant whats necessary
    Extend material using bapi_material_savedata
    About transfer the material data from BAPI_MATERIAL_GETALL to structures to be used on BAPI_MATERIAL_SAVEDATA, i think that MOVE field by field is the better way once there won't many fields to be populated.
    Felipe

Maybe you are looking for