Cube Materialized View not getting created

Hi
I have a cube which has 8 dimensions. Only one of the dimensions has a level based hierarchy and the rest are value based.
I have not created levels for value based hierarchies.
So the materialized view compataility screen tells me that I need to have levels in these value based hierarchies so that I can create a materialized view.
How can I get around or solve this issue ?

If you are querying the base tables, then creating a materialized view (cube or table based) and relying on query rewrite will usually make things faster. In this case you would need to include a GROUP BY in your SQL queries, and I don't know how you would do that with value hierarchies.
If, instead, you are querying the generated cube views, then creating a cube materialized view will make absolutely no difference to query times. This is the recommended approach, and is the best way to integate with clients such as OBIEE and Simba.

Similar Messages

Materialized View not getting refreshed

Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
I am having a situation here..there a materialized view named mv_empdept,the base table of this MV is located on a remote database.Therefore the MV creation scripti contains a DB link.
Please find the script below.
Select Deptno,dept_name,empno,ename,DOB,Job
from [email protected];
The refresh mode of this MV is set as FAST,and the refresh cycle is scheduled through Oracle Job.
The job does get triggerd but from the log we found this error.
The error message is:ORA-12008: error in materialized view refresh path
ORA-01461: can bind a LONG value only for insert into a LONG column.
I even checked at the source Db and found that there is no mismatch as far datatype and datalength is concerned.
Strangely when i do a manual Complete refresh of the same MV the data does gets populated in mv_empdept snapshot.
Can anybody explain me the why the data is not getting populated in FAST refresh mode.
Your help is highly appreciated.
---Vineet

Read the following...
http://download.oracle.com/docs/cd/B10500_01/server.920/a96567/repmview.htm
and analyze the restrictions of Fast Refresh in your situation.

View not getting created in endeca 3.1

Hi ALl,
I am trying to create a new view in endeca 3.1 but I am getting below error:
"Could not execute view config service request. This usually happens when an invalid view config service request is made, or when a read only Oracle Endeca Server receives a view config service request. Error message: OES-000183: Dependency 'EPC' is missing"
The view definition is
DEFINE Events AS
SELECT "EVENT_TYPE" AS "EVENT_TYPE",
"BUSINESS_STEP" AS "BUSINESS_STEP",
"DISPOSITION" AS "DISPOSITION",
"ACTION" AS "ACTION",
"BUSINESS_LOCATION" AS "BUSINESS_LOCATION",
LOCATION AS "LOCATION",
LOCATION_DESCRIPTION AS "LOCATION_DESCRIPTION",
LOCATION_TYPE AS "LOCATION_TYPE",
"EVENT_TIME" AS "EVENT_TIME",
"RECORD_TIME" AS "RECORD_TIME",
"TOP_LEVEL_EPC_CODE" AS "TOP_LEVEL_EPC_CODE",
Count(EVENT_ID) AS "CODE_COUNTS",
"EVENT_ID" AS "EVENT_ID"
FROM EPC Code
GROUP BY EVENT_ID
Can someone please let me know how to resolve this issue.
Thanks,
Amrit

I believe that as of 3.1 that if you are grouping the results of a view, then all of your view attributes need to have an aggregation function. That may be your problem.
If you are simply copying the value of an attribute from the base view to your custom view, without needing to do any real aggregation, then you would use the ARB function.
This is mentioned in Guidelines for using EQL to define a view, which includes an example.

Material Master MRP View not be created till Basiv View is created

Hello All,
I need an information where i would like to know if an MRP view in a Material master can be restricted without the creation of the Basic View. Basically an MRP view is getting created even though the Basic View of material master is not there and it needs to be stopped.
Thanks for your inputs.
Ismail

Dear Syed ,
If you want to prevent end users update other material master views , you can apply the concept of SAP note 545380 - FAQ: Authorizations material master , with this you will not more problem with this kind of problem.
Hope this can help you.
Please let me know if my thinking about your question is correct.
best regards,
Carlos Moçatto

Material type not getting displayed in the cube........

Hi,
In my infocube material type for one of the material is not getting displayed.
When I check in the content of the cube for this material all the fileds are getting displayed except material type.
However it is present in the material master data from which it is put into the update rules to populate in the cube.
Its getting displayed for some other materials , so we cant say that mapping is wrong or problem with update rules.
Can some body let me know what could be the reason.
Thanks,
Jeetu

Hi Jeetu,
can you check in your cube if you have for one material, entries with AND entries without the MATL_TYPE? If this is the case then you were loading transactional data before having the corresponding material master data.
You should adapt your scenario:
- first do not use the standard attribute derivation during your URules: performance is very bad.
- implement a start routine filling an internal table with your material and MATL_TYPE for all entries of material in your datapackage.
- implement an update routine on the MATL_TYPE with a READ on this internal table an raise an ABORT = 4 if the MATL_TYPE is initial or the material in not found.
Now to fix your situation you'll have to reload your cube or alternatively just reload your missing MATL_TYPE MATERIAL from your cube itself and selective delete those which are empty.
hope this helps...
Olivier.

Very high parse times for query rewrite using cube materialized views

We recently upgraded to version 11.2.0.2 (both AWM and Oracle database server). We are using cube materialized views with query rewrite enabled. Some observations of changes that took place when we rebuilt all the dimensions and cubes in this version:
1. Queries against the base tables take about 35 seconds to parse. Then they execute in a tenth of a second. Even simple queries that just get a sum of the amount from the fact table (which is joined to all the dimensions) takes that long to parse. Once parsed, the queries fly.
2. I noticed that the materialized views used to use grouping sets in the group by clause in version 11.2.0.1, but now they use group by rollup, rollup, rollup...
If we disable query rewrite on the MV or for my session, parse times drop to less than a second. Ideas?

There does appear to be a slow down in parse times between 11.1.0.7 and 11.2. We are still investigating this, but in the meantime here is a way to force the code in 11.2 to generate a GROUPING SETS clause instead of the new ROLLUP syntax.
The trick is to create a dummy hierarchy containing only the leaf level. This is necessary for all dimensions that currently have a single hierarchy. As a simple example I created a dimension, PROD, with three levels, A, B, and C, in a single hierarchy. I then created a one dimensional cube, PC. Here is the SELECT statement for the MV in 11.2. Note the ROLLUP clause in the GROUP BY.
SELECT
GROUPING_ID(T3."CLASS_ID", T3."FAMILY_ID", T3."ITEM_ID") SYS_GID,
(CASE GROUPING_ID(T3."CLASS_ID", T3."FAMILY_ID", T3."ITEM_ID")
   WHEN 3
   THEN TO_CHAR(('A_' || T3."CLASS_ID") )
   WHEN 1
   THEN TO_CHAR(('B_' || T3."FAMILY_ID") )
   ELSE TO_CHAR(('C_' || T3."ITEM_ID") ) END)     "PROD",
T3."CLASS_ID" "D1_PROD_A_ID",
T3."FAMILY_ID" "D1_PROD_B_ID",
T3."ITEM_ID" "D1_PROD_C_ID",
SUM(T2."UNIT_PRICE")     "PRICE",
COUNT(T2."UNIT_PRICE") "COUNT_PRICE",
COUNT(*) "SYS_COUNT"
FROM
GLOBAL."PRICE_AND_COST_FACT" T2,
GLOBAL."PRODUCT_DIM" T3
WHERE
(T3."ITEM_ID" = T2."ITEM_ID")
GROUP BY
(T3."CLASS_ID") ,
ROLLUP ((T3."FAMILY_ID") , (T3."ITEM_ID") )Next I modified the dimension to add a new hierarchy, DUMMY, containing just the leaf level, C. Once I have mapped the new level and re-enabled MVs, I get the following formulation.
SELECT
GROUPING_ID(T3."CLASS_ID", T3."FAMILY_ID", T3."ITEM_ID") SYS_GID,
(CASE GROUPING_ID(T3."CLASS_ID", T3."FAMILY_ID", T3."ITEM_ID")
   WHEN 3
   THEN ('A_' || T3."CLASS_ID")
   WHEN 1
   THEN ('B_' || T3."FAMILY_ID")
   WHEN 0
   THEN ('C_' || T3."ITEM_ID")
   ELSE NULL END) "PROD",
T3."CLASS_ID" "D1_PROD_A_ID",
T3."FAMILY_ID" "D1_PROD_B_ID",
T3."ITEM_ID" "D1_PROD_C_ID",
SUM(T2."UNIT_PRICE")     "PRICE",
COUNT(T2."UNIT_PRICE") "COUNT_PRICE",
COUNT(*) "SYS_COUNT"
FROM
GLOBAL."PRICE_AND_COST_FACT" T2,
GLOBAL."PRODUCT_DIM" T3
WHERE
(T3."ITEM_ID" = T2."ITEM_ID")
GROUP BY
GROUPING SETS ((T3."CLASS_ID") , (T3."FAMILY_ID", T3."CLASS_ID") , (T3."ITEM_ID", T3."FAMILY_ID", T3."CLASS_ID") )This puts things back the way they were in 11.1.0.7 when the GROUPING SETS clause was used in all cases. Note that the two queries are logically equivalent.

Accounting doucment not get created for Credit Memo

Hi
When creating a cancellation doucment(vf11) for credit memo accounting document not get created.While I go for analysis then it is determining the G/L account.But not getting created the accounting doucment.
When i select "Release to accounting" then it is giving a message like this:
"Automatic clearing of billing document 951
and canc. doc. 90000572 not poss." as informatiion first
and then later it is throwing an error message that "maintain correct number range"
While for the same material or earlier cancellation happened and accounting doucment get created.
Please help me out;How would i get this solved?
Thanks in advance

Hi,
You may also check for Number Range - Maintainance & Assignment.
T. Code: SNRO
Table/ View: RV_BELEG
Here, Mantain Number Range.
To Assign,
T. Code: SM30
T.Code: Bill_Num (or select if different in your case)
Assign No. range to your combination of Sales OrgDist.ChannelBill Type i.e. for Cancelled Billing Doc. Type
To Maintain Number Range for Accounting Documents,
T. Code: FBN1
Best Regards,
Amit

Production version is not getting created using ALE-IDOC

Hi all,
Am using BD10 to transfer the material from sending to receving system.All the views are geting sent successfuly accept the production version tab data of MRP4 view.The segment is available in the standard IDOC.But prodction TAB is not getting created at receving system .Please help to resolve this issue.
Thank you.

Hi Sanu,
BD10 Send Material..
the reason might be Production tab is not created is the segment is not a mandatory..
and the data is not populating for that fields.
if the segment is not madatorty and data is not available for the fields in the segment ..the prodction TAB will not be created ..
Regards,
Prabhudas

Integration with EWM-Inspection lot not getting created

Hi,
Inspection lot not getting created after GR is done.
The scenario is Storage location is connected to external warehouse management,so after the GR is done in the legacy system via interface it is updated in ECC.so while checking the material document inpection lot is not created.
Can anyone please tell me the necesaary check points and integeration steps between WM and QM in this case .
Thanks in advance.......

Hi,
Since you didn't say much, I assume you are creating stock into ECC via LSMW using 561 movement. Now to get inspection lot for these batches/ docs, you need to activate inspection type 05.
Go to material master QM view, assign and activate inspection type 05.
Additionally, create a respective inspection plan/ task list for the material(s) to carry out RR and get the consistent inspection lots.
ntn

Integration with QM-Inspection lot not getting creating

Hi ,
Inspection lot is not getting created after GR is posted.
Scenario:Storage location is connected to external warehouse management.
Can anyone please explain the necessary check points and Integration steps needed to be followed for inspection lot creation.

Hi,
Since you didn't say much, I assume you are creating stock into ECC via LSMW using 561 movement. Now to get inspection lot for these batches/ docs, you need to activate inspection type 05.
Go to material master QM view, assign and activate inspection type 05.
Additionally, create a respective inspection plan/ task list for the material(s) to carry out RR and get the consistent inspection lots.
ntn

Material cost not getting displayed in CN41N

Hi Gurus,
When we execute CN41N, Materials assigned to the Network activity are visible but the cost of each material is not getting displayed against it (under Proj. Cost Plan Column) and it is appearing as '0' whereas, it is appearing as an accumulated cost against the activity. I checked SAP notes for this problem, though I could see some notes which are very close to the problem but all are for Release 600 whereas we are using 604 (ECC 6.0). Have anyone encountered such problems or whether the cost will not appear against Material in CN41N.
Awaiting your valuable suggestions.
thanks in advance.
Vinodh

I have seen planned cost of material against material itself in structure report like CN41, CN41N under following conditions:-
1. Valuated Project Stock
2. Material is created using Reservation for WBS or PR+Res for WBS Procurement indicators.
3. Costing relevancy box ticked for material
4. Statistical Cost element exists for Inventory account.
I have not seen planned cost for non-stock item or material with res for network in project. This is purely based on my experience and I dont have any notes or help document to validate my statement.

Order by in MATERIALIZED VIEW not work successfully with first column (ID)

Dears,
I am trying to create a Materialized View as below:
CREATE MATERIALIZED VIEW HR.MV_EMP
PCTFREE 10
MAXTRANS 255
TABLESPACE users
STORAGE (
INITIAL 65536
MINEXTENTS 1
MAXEXTENTS 2147483645
BUILD IMMEDIATE
REFRESH ON DEMAND
AS
SELECT *
FROM employees
where rownum < 5000 order by employee_id desc ;But while querying the MATERIALIZED VIEW, it did not work successfully as the data did not appear in the accurate order.
I tried to create the same MATERIALIZED VIEW but order by another column (Column Date), it worked successfully and the data appeared in the accurate order.
It means that MATERIALIZED VIEW not work successfully with the first column (id).
Can you please help me in this ?
Thanks & regards,,

A few pointers :
1. As has been pointed out, the ROWNUM has been incorrectly placed. ROWNUM values are assigned as rows are fetched from the source before the ORDER BY. You need to ORDER BY first (in a SubQuery) and then ROWNUM afterwards (outside the SubQuery).
2. I wonder why you want only the last 5000 EMPLOYEE_IDs. What if Employee_ID 1 is still an active employee (he is the founder, first employee and CEO ?). There could be very many "low" EMPLOYEE_IDs that are still active.
3. Logically I would expect some filter other than the ROWNUM ... ORDER BY to be used to select candidate rows. Then, an ORDER BY in the CREATE query would be unnecessary.
4. When querying the Materialized View you must explicitly ORDER BY (irrespective of whether you did or did not do an ORDER BY in the CREATE ...)
5. How do you expect to refresh the MV ? Will it always be a COMPLETE Refresh ? Remember that your "5000 employees" filter would likely exclude older employees at the next refresh. If you use some other filter, it should be consistent across all refreshs.
Hemant K Chitale

Material Document not getting posted.

Hi Guys:
Material document is not getting created when i try post the inventory difference using transaction LI21 ( Clearing of differences in Inventory Management ).
we are using WM , so physical inventory is carried out at Bin Level.
Did I miss anything in the config setting?
Thanks
Sweth.

Hi Jurgen:
do you have a pick or putaway quantity in this quant in storage type 999 ?
Yes , in the available quantity I could see the -ve quant ( Goods Issue/Pick) and + Quant (Goods Receipt/Putaway)
is the quant locked?
Quant is showing with unlocked logo.
is somebody else in change mode in that quant?
Nope
is this the only item in your inventory document?
yes
have you tried to execute LI21 in background?
I don't how to do that ,
do you require to enter a reason for the difference?
I didn't see that question Popped Up.
Thanks for the help.
Sweth

Transfer Requirement not getting created

Hi All,
My query as below;
Production order is created using KANBAN (Control Cycle/Supply Area is defined) using classic KANBAN.
WM is in place and all the setting related to TR/TO creation for WM movement type 103 is in place.
When i am trying to receive this Production after completion it is not creating the TR/TO, while as material document is getting generated and shows the stock directly in interim storage type 901 without creating TR and TO.
Further i checked there is indicator in Production order i.e "Kanban indicator" that gets checked automatically when Production order is created using KANBAN Processs and if i remove that indicator forcefully, TR and TO is getting created normally.
Please provide some inputs where can be the problem and how TR and TO can be created normally eventhough KANBAN indicator is checked in Production order and where i can found the setting related to "KANBAN INDICATOR".
Appreciate your help.

Hi Maddy
Thanks very much for your response.
1. When you use KANBAN, you define separate KANBAN storage location, which is different from WM-managed replenishment storage locations, and separate KANBAN interim storage area with storage bin.
Yes different storage location is defined which is not WM-managed in supply area.
As you said Control Cycle is defined, see if the interface is properly defined for both of these Sloc.
Where i can check whether interface is properly defined or not.
2. See if you have defined the KANBAN replenishment strategy with Control type Transfer Requirements from a Storage Location which is being controlled by WM in the Customizing for Production under KANBAN > Replenishment Strategies > Define Stock Transfer Strategies
Actually for a material two strategies are defined like;
1) In-house Production strategies-0003-
supply area is defined with storage location which is IM managed.
And when this order is completed and i am trying to receive this in WM SLOC (usally whatever SLOC we have defined in supply area it proposes that SLOC at the time of receipt but i am changing this manually to WM managed SLOC) using transaction MIGO, it is directly taking the stock to 901 interim storage type and in total the stock increases but the problem is when TR is not getting created i am not able to take this to the storage bin as per strategies defined.
2) Stock Transfer Strategies-This is working fine and in that TR/TO is working fine.
3. For TO to get created automatically by the system from the transfer requirement, see if an indicator Automatic TO creation in the replenishment strategy is set or not. Yes this is set for stock transfer strategies but i didn't find option to check the TO creation automatically for in-house production strategy
4. Also, check that you have set up a suitable replenishment movement type for KANBAN in the Customizing for Warehouse Management under Activities > Transfers > Define Movement Types (i.e.standard is 350 for KANBAN replenishment)-Yes this is also defined correctly.
Appreciate your more inputs on this.

BP ID not getting created

Hi Friends,
While i am creating org unit through PPOMA_BBP,Business partner id not getting created/assigned to the Org unit automatically
I have checked teh number range for Business partner,it exist..
Can you pls tell me what could be the reason for the issue...
Thanks,
San..

Hi,
Check following entry activated.
Transaktion SM30, View T77S0
Regards
Konstantin

Cube Materialized View not getting created

Similar Messages

Maybe you are looking for