Delete material view transaction MM06

Hi gurus
For error has been opened costing1 and costin2 material view for a material.
Is there any way to delete only two material views?
I have used transaction MM06 but deletes the material at plant level. Using transaction MM74 the modification should
have to be effected but i don't know to use MM74.
Can you help me?
Thanks in advance

it is not possible to delete views, deletion is only possible at organisation level. Costing is just a part of plant organisation, the fields are stored in table MARC.
if the material was not in use, then you can archive the plant level only with SARA (object MM_MATNR) after you have flagged the plant level for deletion in MM06.
then you can recreate the plant level without the unwanted views.
For archiving of individual org levels, you may have to implement an OSS note

Similar Messages

Is a Full refresh of Materialized views transactional ?

Hello all,
We have materialized views in production, and we would like confirmation that the full refresh of a MV is not transactional, i.e.:
- some mv "mv1" on table t1, which contains data
- we launch a full refresh of mv1
- the refresh operation fails (for instance, snapshot too old)
--> what will be the content of MV1 in this scenario? Will it be empty or not?
Kind regards

In 9.2 and below the default was to TRUNCATE and INSERT. Therefore, if the Refresh fails, then you are left with 0 rows in the MV till you issue another refresh.
In 10.2 the behaviour has changed because ATOMIC_REFRESH now defaults to TRUE. This causes a DELETE and INSERT. If the Refresh fails, it is rolled-back and the pre-refresh image of the rows is available in the MV. The 10.2 behaviour can be changed to the 9.2 behaviour by setting ATOMIC_REFRESH to FALSE.
A TRUNCATE and INSERT refresh is much faster and generates less Redo. However, it leaves you vulnerable -- users querying the MV while the Refresh is running will see zero rows. If the Refresh fails, they will continue to see zero Rows.
The 10.2 behaviour now makes it safer to use the MV while it is being refreshed. A consistent view of the data is always available. This is at the cost of performance and disk space requirements for Undo and Redo/ArchiveLog for the Refresh.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Deleting Query Views transaction code?

How can an administrator delete unwanted Query Views in BW 3.5? What transaction code is used to manage Query Views in the BW system?
Thanks,
Brien

Hello Brian,
Use this to delete views:
TRY.
CALL METHOD CL_RSZ_WWW_DB_INTERFACE=>DELETE_VIEW
EXPORTING
I_VIEWID = 'your_view_id'
I_OBJVERS = RS_C_OBJVERS-ACTIVE.
CATCH CX_RSZ_DB_WRITE_ERROR .
ENDTRY.
Kind Regards,
Alican
Message was edited by: Alican Polat

Material view deletion

Hi
i have to delete some material master views for my material.
i have already tried to delete it by using MM06 tcode but its not helping me out. is there any other method by which i can achieve this?
thanks in anticipation

Dear,
First, flag the desired view tab for deletion using MM06, but still the view available during viewing the material. A message will be displayed when viewing or changing the material but the tab will still be visible. To totally remove the tab execute MM74 for archiving the desired tab deletion for this material only. Make sure you do not copy other materials or storage location..
Try this and I hope it will solve the issue.
Regards,
Syed Hussain.

ORA-00600: internal error when delete master rows in a materialized view

I have a materialized view in 11g2 on Redhat 5, defined asCREATE MATERIALIZED VIEW mv_idty
PARALLEL BUILD IMMEDIATE REFRESH FAST ON COMMIT ENABLE QUERY REWRITE AS
select IDTY_NAME_FIRST,IDTY_NAME_MIDDLE,IDTY_NAME_LAST,IDTY_NAME_SUFFIX,IDTY_SSN,
IDTY_DR_LIC_NUM,IDTY_DR_LIC_STA,x.person_id,i.rowid i_rowid,x.rowid x_rowid
from idty i,person_x_idty x where x.idty_id=i.idty_id; I deleted a few rows from the master tables and get error13:58:48 SQL> delete idty where idty_id like 'test_row%' ;
7 rows deleted.
13:58:52 SQL> commit;
commit
ERROR at line 1:
ORA-12008: error in materialized view refresh path
ORA-00600: internal error code, arguments: [kkzfrfajv_markdml-1], [], [], [], [], [], [], [], [], [], [], [] I have other materialized views and they all delete master OK. This is the simplest one but causes problem. HELP!
Edited by: user13148231 on Aug 11, 2010 5:45 PM

Checked note 743766.1. It is not 100% relevant as it is about import, but the query is usefulselect sowner, vname, mowner, master from sys.snap_reftime$It reveals the materialized view some how based on other schema.
Recreate the materialized view. problem solved.

Oracle Materialized View | Deletion of Records, Oracle Materialized View

One question reg Materialized views.
If as part of housekeeping of the Source database we delete some records (older records), will the materialized view also be updated with the deletion?
I believe the answer is yes. In that case can we ensure that this delete does not happen?
Is there anyway we can prevent MView refresh from deleting the records that is once inserted even if we delete the same records in source DB?

This is a common scenario, particularly with materialised views that summarise detail data where you want to keep the summary but not the detail, and it is addressed in the documentation.
The technique is to make the MV refresh on demand, delete the data from the detail tables, and use the CONSIDER_FRESH procedure to prevent the changes propagating to the MV. You'll probably find it in the docs by searching on DBMS_MView.Consider_Fresh. There are a few warnings to note I think.

Materialized view rows deletion

Hi all,
I have a question!
If the rows in master table are deleted on which a materialized view exist on a remote site, then the corresponding rows from materialized view will also be deleted on refresh?
Appreciate your help
IM

Great, so it means the total number of rows in master table and total number of rows in materialized view will remain same on refresh.
Thanks!
Edited by: user6885664 on Feb 26, 2012 8:29 PM

Materialized view long transaction time

I am using Oracle DB 11g R2 and created a materialized view log WITH SEQUENCE. I need to find out the exact date/time the transaction was made. I see that my MV log has the 'XID$$' column (NUMBER 22), but not sure how to determine the date/time from that. Is there another view/table I can join to get me that info? I see some have 'XID' column but they are RAW(8).
Thanks
Edited by: bobmagan on Feb 27, 2013 11:57 AM

- CDC is at least as performant as materialized view logs. If you do asynchronous CDC, it performs better since you're not burdening the source transactions with the overhead of synchronously maintaining the materialized view logs.
- CDC is at least as effective as materialized view logs. Since CDC is designed to publish changes to custom consumers where materialized view logs are designed to be used by Oracle to refresh a materialized view, it strikes me as a much safer solution. If someone comes along and creates a materialized view that starts using your materialized view log, for example, a solution that involves custom code to manipulate the materialized view is almost certainly going to fail.
- CDC isn't an extra cost option so there shouldn't be a cost difference
That leaves the question of simplicity. I'll certainly grant you that a materialized view log solution may appear simpler. But a lot of that simplicity advantage disappears over time. The fact that we're talking about doing things like querying relatively obscure data dictionary tables like all_summap, for example, is added complexity that a CDC-based solution doesn't need. But over time, I'd much rather maintain a CDC-based solution rather than hooking in to materialized view logs. If someone wants to build a materialized view and Oracle happens to be able to use the materialized view log you've created for your own CDC, the custom solution will stop working. Over time, Oracle introduces more and more functionality that allows the ROWID of a row to change (shrinking a table, flashback, etc.). If you're using CDC, Oracle will take care of making sure that all those things are presented to you correctly. If you're rolling your own solution, you have to test and ensure that your code handles all those cases correctly. When Oracle makes a change in some future release that you hadn't considered, you've got to notice the potential problem, code the fix, and test it. Most places are probably going to miss something and only discover that there is a problem when they do something like shrink a table and then find that their custom solution doesn't handle that gracefully.
Justin

Delete material master view

Hi All...
The work scheduling view was created due to the BDC program. This view is not required. Can anyone suggest how to delete this particular view keeping the rest as-it-is.
FYI.. the maintainence status of the screen is A.
Thanks in advance...
SriB

hi
i think u want to delete the views from bdc program
check this link and take help of abaper
http://help-abap.blogspot.com/2008/09/mm02-bdc-select-specific-material.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d62292b3-0301-0010-df98-aaac31cd4a41
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d62292b3-0301-0010-df98-aaac31cd4a41
regards
kunal

Materialized Views: how can I find the number of updates, inserts, delete

We are using Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod.
In a materialized view, with fast incremental refresh, done after every 5 minutes automatically, I want to store in a logging table the number of rows inserted,updated and deleted in the materialized view by that refresh.
One option is to create a job that should read the materialized view log table just before the refresh and store the required information in the logging table. But this information may not be accurate.
Is there any other way to collect this information for each refresh?

Use auditing, or an before insert/update/delete trigger, that updates a counter
I hate myself for giving this advice, because it will bring you problems, with the MV update/refresh speed, table lock contention on the log-table....
Be carefull !!
Why not use auditing on the source table and why does anyone wants to know the number of changes??
Regards
FJFranken

Permeant delete material from systeam

hi gurus
plz help me how to delete materail from the systeam.i want delate a material permentaly also names& stock.

Hi,
to delete material use t-code MM06.
and if you want that material should not be used for any transaction then go-to MM03 enter material no. select 'Basic Data View 'in that there is a field called 'X-plant matl status'
choose a valid value and just opposite to this field there is a field called 'Valid from' enter todays date in that field then from today your material will be blocked.
otherwise if you want to delete a view from the material use t-code MM50 and if you want to delete all the materials from your client use t-code MMDE and to archive the material use t-code MM71
below mention link will help you in understanding the archiving process.
http://help.sap.com/saphelp_erp2005/helpdata/en/8d/3e59bc462a11d189000000e8323d3a/content.htm
Regards,
Archit

Create a materialized view :-

How do I create a materialized view on a view ,so that it will refresh automatically on every commit in base table where the view having more that 9 function ?

Read Materialized View Refresh for complete information.
For a Jist:
Refresh Mode Description
ON COMMIT
Refresh occurs automatically when a transaction that modified one of the materialized view's detail tables commits. This can be specified as long as the materialized view is fast refreshable (in other words, not complex). The ON COMMIT privilege is necessary to use this mode.
ON DEMAND
Refresh occurs when a user manually executes one of the available refresh procedures contained in the DBMS_MVIEW package (REFRESH, REFRESH_ALL_MVIEWS, REFRESH_DEPENDENT).
When a materialized view is maintained using the ON COMMIT method, the time required to complete the commit may be slightly longer than usual. This is because the refresh operation is performed as part of the commit process. Therefore this method may not be suitable if many users are concurrently changing the tables upon which the materialized view is based.
If you anticipate performing insert, update or delete operations on tables referenced by a materialized view concurrently with the refresh of that materialized view, and that materialized view includes joins and aggregation, Oracle recommends you use ON COMMIT fast refresh rather than ON DEMAND fast refresh.
If you think the materialized view did not refresh, check the alert log or trace file.
If a materialized view fails during refresh at COMMIT time, you must explicitly invoke the refresh procedure using the DBMS_MVIEW package after addressing the errors specified in the trace files. Until this is done, the materialized view will no longer be refreshed automatically at commit time.

MATERIALIZED view on two tables with Fast Refresh

i Wanted to create MV on two tables with Fast refresh on commit.
I followed below steps
create materialized view log on t1 WITH PRIMARY KEY, rowid;
create materialized view log on t2 WITH PRIMARY KEY, rowid;
CREATE MATERIALIZED VIEW ETL_ENTITY_DIVISION_ASSO_MV
REFRESH fast ON commit
ENABLE QUERY REWRITE
AS
select A.ROWID B.ROWID,a.c1, DECODE(a.c1,'aaa','xxx','aaa') c2
from t1 A
join t2 b
on AB.c1= CD.c2;
i am getting below error.
Error report:
SQL Error: ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
12054. 00000 - "cannot set the ON COMMIT refresh attribute for the materialized view"
*Cause: The materialized view did not satisfy conditions for refresh at
commit time.
*Action: Specify only valid options.
Basically i want to take record in MV by joinig two tables and if both of the base tables will updated then record should reflect in materialised view.
Please do the needfull.

does the table support PCT? the other restrictions on joins look to be ok in your statement.
maybe try creating first with on demand instead of commit to see does it create.
http://docs.oracle.com/cd/B19306_01/server.102/b14223/basicmv.htm
>
Materialized Views Containing Only Joins
Some materialized views contain only joins and no aggregates, such as in Example 8-4, where a materialized view is created that joins the sales table to the times and customers tables. The advantage of creating this type of materialized view is that expensive joins will be precalculated.
Fast refresh for a materialized view containing only joins is possible after any type of DML to the base tables (direct-path or conventional INSERT, UPDATE, or DELETE).
A materialized view containing only joins can be defined to be refreshed ON COMMIT or ON DEMAND. If it is ON COMMIT, the refresh is performed at commit time of the transaction that does DML on the materialized view's detail table.
If you specify REFRESH FAST, Oracle performs further verification of the query definition to ensure that fast refresh can be performed if any of the detail tables change. These additional checks are:
A materialized view log must be present for each detail table unless the table supports PCT. Also, when a materialized view log is required, the ROWID column must be present in each materialized view log.
The rowids of all the detail tables must appear in the SELECT list of the materialized view query definition.
If some of these restrictions are not met, you can create the materialized view as REFRESH FORCE to take advantage of fast refresh when it is possible. If one of the tables did not meet all of the criteria, but the other tables did, the materialized view would still be fast refreshable with respect to the other tables for which all the criteria are met.

SQL Loader or Materialized view

Can we achive the following SQL Loader ?
If yes can someone point me out some ling
Requirement:
We need to create a Reporting DB to use for Reporting and a Transactional DB will be in separate Host. Basically we need to pull data from a set of tables from Transactional DB and move to Reporting DB schema at proper intervals.
We might have to get data from different column from different tables and store it in a single table/multiple tables in Reporting DB
If as part of housekeeping of the Source database we delete some records (older records), In that case we have to ensure that this delete does not happen in reporting DB

Materialized view will be the best option for this. You can schedule jobs for refreshing the Materialized view at some interval. If you use sqlloader you need to do some coding.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmview.htm#REPLN003
Edited by: sac on Nov 16, 2009 10:58 AM

Materialized View UNION different tables 10g.

I am trying to create a materialized view from 2 different tables. According the documentation for 10G it should be available.
Here is my script.
DROP MATERIALIZED VIEW PERSON_MV_T16;
CREATE MATERIALIZED VIEW PERSON_MV_T16 refresh complete on demand
AS
SELECT
CAST(P.MARKER AS VARCHAR2(4)) AS MARKER,
P.ROWID P_ROW_ID,
CAST(P.ACTIVE_IND_DT AS DATE) AS ACTIVE_IND_DT
FROM PERSON_ORGS_APEX_MV P
UNION
SELECT
CAST(P.MARKER AS VARCHAR2(4)) AS MARKER,
P.ROWID P_ROW_ID,
CAST(P.ACTIVE_IND_DT AS DATE) AS ACTIVE_IND_DT
FROM PERSON_ORGS_APVX_MV P
delete from mv_capabilities_table;
begin
dbms_mview.explain_mview('PEOPLE.PERSON_MV_T16');
end;
select *
from mv_capabilities_table where capability_name not like '%PCT%' and capability_name = 'REFRESH_FAST_AFTER_INSERT';
I get the following error.
CAPABILITY_NAME = REFRESH_FAST_AFTER_INSERT
POSSIBLE = N
MSGTEXT = tables must be identical across the UNION operator
I wrapped them in CAST operations just to be sure they are the same type and size.

As far as I'm aware, you can create MV in standard and also there is no limitation that I'm aware off
Standard and Enterprise Edition
A. Basic replication (MV replication)
\- transaction based
- row-level
- asynchronous from master table to MV (Materialized View)
- DML replication only
- database 7 / 8.0 / 8i / 9i / 10g
Variants:
1. Read-only MV replication
2. Updateable MV replication:
2.1 asynchronous from MV to master
2.2 synchronous from MV to master
3. Writeable MV replication
Enterprise Edition only
B. Multimaster replication
\- transaction based
- row-level or procedural
- asynchronous or synchronous
- DML and DDL replication
- database 7 / 8.0 / 8i / 9i / 10g
- Enterprise Edition only
Variants:
1. row-level asynchronous replication
2. row-level synchronous replication
3. procedural asynchronous replication
4. procedural synchronous replication
C. Streams replication
(Standard Edition 10g can execute Apply process)
\- (redo) log based
- row-level
- asynchronous
- DML and DDL replication
- database 9i / 10g (10g has Down Streams Capture)

Delete material view transaction MM06

Similar Messages

Maybe you are looking for