Error for dimension builting

Hi All
wen iam builting the dimension using rule file from sql Server
im getting error like this may i know y im getting this error;
          U011      U011 - ARENDI CONSULTING
\\Record #37 - Incorrect Dimension (ENTITY) For Member U (3308)
U          U012      U012 - z:Merged 01 01 2006 ARIANE INGENIERIE
\\Record #41 - Incorrect Dimension (ENTITY) For Member U (3308)
U          U013      U013 - z:Merged 01 01 2006 ATLANTIDE
\\Record #55 - Incorrect Dimension (ENTITY) For Member U (3308)
U
          U014      U014 - z:Fusionnée 30 04 2008 AXIEM
Thanks

First of all, answer this. Does the member "U" already exist in another dimension?
The error file indicated that the member you were trying to add already exists in another dimension.
Adding a prefix to the load of the dimension that you were trying to add it (and it error'd out) will make it unique in that dimension, thereby eliminating the error.

Similar Messages

Essbase Typical Error for Dim Built

Hi All
Wen Im builting the Dimension Im getting error below records are rejecting but according to that error
in my database i have the parent for that records all the records are loaded for remaining other parents in that level but these r rejecting;
and i m sure there is no duplicates in that ,and i mapped the fields correctly but im not getting ,its very urjent plz can any one help
\\Record #194 - Member required for alias P-R61010 (3311)
     P-R61010     P-R61010 - Payroll saving (DC)
\\Record #194 - Child Member P-R61010 - Payroll saving (DC) with no parent (3331)
     P-R61010     P-R61010 - Payroll saving (DC)
\\Record #196 - Member required for alias P-R61030 (3311)
     P-R61030     P-R61030 - Rents Saving (DC)
Regards
RamNAndu
\\Record #196 - Child Member P-R61030 - Rents Saving (DC) with no parent (3331)
     P-R61030     P-R61030 - Rents Saving (DC)

HI ,
1. Which algorith are you using like generation references, parent -child.
2. As the error reads as 'no parent' available , in you build properties, re confirm the fields ( for both the parent level and also child level) once again.
3. As you are able to build for other dimension ( also the children) , this should also go through , if you rule is a valid one . Do validate your rule for this ( if you are using seperate rule file for this dimension).
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Error while adding landed cost G/L account 5207010003 needs DR assignment for dimension 1; fill in DR-related fields

Error while adding landed cost G/L account 5207010003 needs DR assignment for dimension 1; fill in DR-related fields

Hi Rajesh
Go to System Initilization => General Settings => Cost Accounting => Check the Dimension1 has Block Posting.
Relase the Block and add the Document it will add.
With Regards
Balaji

Universe Designer: Error getting dimensions for cube

-Using Business Objects Edge 3.1 SP2
-SAP BW 7.0 (patch level 21)
This is quite odd behavior that seemed at first an authorization issue, but now I am uncertain.
-Attempting to create a Universe based on a Infocube.
-Universe connection is created with no problem using user 'ABC'
-Using Universe Designer on the BOBJ server, no issues creating the Universe
-Using Universe Designer on a users desktop, the Universe fails to create with error message:
A runtime exception has occurred. (Error getting dimensions for cube $0SD_C03 (catalog $INFOCUBE): Unknown error)
-Change the connection to use user 'DEF', the Universe creates just fine on the desktop
-Behavior is not exclusive to one BW object, happens no matter what 'ABC' tries to access from this desktop
So, at first I am thinking authorizations, but then the universe create would fail on the server as well. If it is environmental, what could possibly affect this behavior.
Any ideas before I submit to SAP Support?
Edited by: Kevin Smolkowicz on May 5, 2010 12:40 PM
Edited by: Kevin Smolkowicz on May 5, 2010 12:41 PM

Oddly enough it was an authorization issue.
When authenticating against the SAP source system from Universe Designer on either the workstation or server, both traces show a missing authorization for RFC_NAME = RASB
This setting is not found in referenced SAPu2019s guides or whitepapers under suggested authorizations for Universe create. What remains unexplained is why using the same credentials from 2 different computers had a different response.

ENT-06972: Error While Displaying BIBEAN for Dimension Dataviewer

Hi, I got the following message out of the blue when trying to view data for a dimension within OWB :-
ENT-06972: Error While Displaying BIBEAN for Dimension Dataviewer
Not only can I not see the data for the new dimension I was creating, but all my other existing dimensions generate the same error. Although I can see the data in the underlying db tables none of my Disco reports work either now !.
I have stopped and started the system to no avail.
Any ideas (while I log an SR) ?
I think the OLAP catalog is somewhat screwed.
thanks
Paul

Before you deploy the dimensions and the cube, ensure that the deployment option is set to Deploy to Catalog Only. Using this option, you can view the loaded data in the dimensions and the cube in the Data Viewer.

Ent-06972 Error When Displaying BIBeans for Dimension Dataviewer

dear all,
I have problem when trying to view data on dimension with dataviewer in OWB 11g. it's no problem when i load small amount of data, but when i load huge amount of data i've got error message "ent-06972 Error When Displaying BIBeans for Dimension Dataviewer ". is it some kind of bug in OWB?

I am also getting the same error, using 11g.

ERROR:- ENT-09671 ERROR WHILE EXTRACTION DIMENSION METADATA FOR DIMENSION

Hello all,
i am working on OWB 10gR2 while i try to validate & Deploy according to the following process it was successful but as i tried to view data from dimension i am getting an error which i have mentioned below
Source Table = CUST_MST
Destination Table = CUSTOMER
Dimension = CUSTOMER
Mapping = CUSTOMER_MAP
Validate Table CUST_MAP.
Validate Table CUSTOMER.
Validate Dimension CUSTOMER.
Validate Mapping CUSTOMER_MAP.
Deploy table CUSTOMER.
Deploy mapping CUSTOMER_MAP.
Deploy dimension CUSTOMER (configured => Deploy All).
Deploy table CUSTOMER.
Deploy sequence <CUSTOMER_SEQ>
Deploy mapping CUSTOMER_MAP.
Deploy dimension CUSTOMER (configured => Deploy All).
Start mapping to load table CUSTOMER.
After this i am getting an error while i tried to view the data in the dimension
ERROR:- ENT-09671 ERROR WHILE EXTRACTION DIMENSION METADATA FOR DIMENSION DATAVIEWER
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA

Not sure if it's valid to have a dimension with 1 hierarchy and 1 level in that hierarchy. The hierarchy may have to have at least 2 levels. If you want the configuration of a dimension with 1 hierarchy and 1 level, CWM2 may want you to omit the hierarchy, thus creating the dimension with only 1 level.

OBIEE Plug-in for AWM error: Missing spread attribute for dimension\

Hi,
While trying to export a cube to OBIEE administrator using the AWM plugin for OBIEE we get the following error for a lot of dimensions.
AWM version is 11.1.0.7.0B on a 11.1.0.7 DB
ERROR: Missing spread attribute for dimension DAY_FLG at level ALL_FLAGS
ERROR: Missing spread attribute for dimension DAY_FLG at level FLAG
ERROR: Validation problems found for dimension DAY_FLG
Dimension DAY_FLG will not have UDML generated
As suggested in other forums I have created a long_desc attribute and selected the "created level attribute in views" option for all the dimensions in the cube, still the error persists.
Please help.
Regards,
Abhishek
Edited by: 866977 on Jun 20, 2011 3:30 AM

Thanks for you response David. But I'm afraid this does not solve the problem. I did it to all the dimensions and the error on day_flg persists. I noticed that an error on one of the other dimensions thougfh has changed. Detailed error below:
ERROR: Missing spread attribute for dimension DAY_FLG at level ALL_FLAGS
To Fix error: In AWM on the attribute panel for the long description attribute of each applicable dimension -
select the check box 'Create level attribute columns in views'
ERROR: Missing spread attribute for dimension DAY_FLG at level FLAG
ERROR: Validation problems found for dimension DAY_FLG
Dimension DAY_FLG will not have UDML generated
ERROR: Missing spread attribute for dimension HOUR at level ALL_HRS
ERROR: Spread Attribute HR_LONG_DESC found but is not visible for level HR
The dimension HOUR will be marked invalid and no UDML will be generated for this dimension or any cube dimensioned by this dimension.
ERROR: Validation problems found for dimension HOUR
Please help

No UDA Found for Dimension XYZ

We are loading metadata into Planning using outline load utility. The command we are using is as follows:
C:\Hyperion\products\Planning\bin\OutlineLoad -f:%scripthome%\EncPassword.txt /A:NFR /U:%Essid% /M /C /-F /I:C:\Data\NFR_Customer_Dim.csv /D:Entity /L:%scripthome%\Logs\Cust_Dim_OTL_Load.Log /X:c:/outlineLoad.exc
The outline load log throws a *"NO UDA defined for dimension xyz" error.* but seems to load the records fine, without rejecting any. Any idea why this is ?
The first part of the log is :
Successfully logged into "NFR" application, Release 11.113, Adapter Interface Version 5, Workforce supported and not enabled, CapEx not supported and not enabled, CSS Version 3
+"Account" dimension properties and information:+
Account, Parent, Alias: Default, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Account Type, Time Balance, Skip Value, Exchange Rate Type, Variance Reporting, Source Plan Type, Plan Type (Sales), Aggregation (Sales), Plan Type (Plan2), Aggregation (Plan2), Plan Type (Plan3), Aggregation (Plan3)
No UDA's defined on "Account"+
+"Periods" dimension properties and information:+
Periods, Parent, Alias: Default, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Type, Start Period, End Period, Aggregation (Sales), Aggregation (Plan2), Aggregation (Plan3)
No UDA's defined on "Periods"+
......... So on and so forth for EACH dimension and then ....
+"Product" dimension properties and information:+
Product, Parent, Alias: Default, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Sales), Aggregation (Plan2), Aggregation (Plan3), InputType
UDA's bound to "Product" dimension: Product_Type
+"InputType" attribute dimension (on base dimension "Product"). Attributes defined on the "InputType" dimension: ProductLine; ProductNumber;+
InputType, Parent, Alias: Default, Operation
Exchange Rates properties:
Table, Description, To Currency, From Currency, Operation, Method, Historical, Beg Balance, Year, Period, Average, Ending
UDA properties:
Dimension, UDA, Operation
Translation input file fields:
Value, Driver Member, Point-of-View, Data Load Cube Name
+[Tue Feb 01 01:30:12 EST 2011]Successfully located and opened input file "C:\Data\NFR_Customer_Dim.csv".+
+[Tue Feb 01 01:30:12 EST 2011]Header record fields: Entity, Parent, Alias: Default, Data Storage+
+[Tue Feb 01 01:30:12 EST 2011]Located and using "Entity" dimension for loading data in "NFR" application.+
+[Tue Feb 01 01:30:14 EST 2011]Load dimension "Entity" has been unlocked successfully.+
+[Tue Feb 01 01:30:14 EST 2011]Performing cube refresh[Tue Feb 01 01:30:36 EST 2011]Cube refresh operation has completed. Please check the Essbase log for status.+
+[Tue Feb 01 01:30:36 EST 2011]Create security filters operation will not be performed.+
+[Tue Feb 01 01:30:36 EST 2011]Examine the Essbase log files for status if Essbase data was loaded.+
+[Tue Feb 01 01:30:36 EST 2011]Planning Outline data store load process finished. *1599 data records were read, 1599 data records were processed, 1599 were successfully loaded, 0 were rejected.*+
\

Do you get the same errors if you load just the first record from the file, if you don't keep increasing the number of records until you find the record that is causing the problem.
Cheers
John
http://john-goodwin.blogspot.com/

Missing most detailed table for dimension tables

Hi ,
I am getting this following error
Business Model Core:
[nQSError: 15003] Missing most detailed table for dimension tables: [Dim - Customer,Dim - Account Hierarchy,Dim - Account Region Hierarchy,Fact - Fins - Period Days Count].
[nQSError: 15001] Could not load navigation space for subject area Core.
I got this error when I tried to configure # of Elapsed Days and # of Cumulative Elapsed Days by following way-
1. Using the Administration Tool, open OracleBIAnalyticsApps.rpd.
Configuration Steps for Controlling Your Data Set
Configuring Oracle Financial Analytics 5-51
The OracleBIAnalyticsApps.rpd file is located at:
ORACLE_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_
obisn\repository
2. In the Business Model and Mapping layer, go the logical table Fact - Fins - Period
Days Count.
3. Under Sources, select the Fact_W_DAY_D_PSFT logical table source.
4. Clear the Disabled option in the General tab and click OK.
5. Open the other two logical table sources, Fact_W_DAY_D_ORA and Fact_W_
DAY_D_PSFT, and select the Disabled option.
6. Add the "Fact - Fins - Period Days Count" and "Dim - Company" logical tables to
the Business Model Diagram. To do so, right-click the objects and select Business
Model Diagram, Selected Tables Only.
7. In the Business Model Diagram, create a new logical join from "Dim - Company"
to "Fact - Fins - Period Days Count." The direction of the foreign key should be
from the "Dim - Company" logical table to the "Fact - Fins - Period Days Count"
table. For example, on a (0,1):N cardinality join, "Dim - Company" will be on the
(0/1) side and "Fact - Fins - Period Days Count" will be on the N side.
8. Under the Fact - Fins - Period Days Count logical table, open the "# of Elapsed
Days" and "# of Cumulative Elapsed Days" metrics, one at a time.
9. Go to the Levels tab. For the Company dimension, the Logical Level is set to All.
Click the X button to remove it. Repeat until the Company dimension does not
have a Logical Level setting.
10. Make sure to check Global Consistency to ensure there are no errors, and then
save the RPD file.
Please help me to resolve.
Thanks,
Soumitro

Could you let me know how you resolved this. I am facing the same.

"Missing most detailed table for dimension tables" eror when I run the Global Consistency check

ERRORS:
Business Model DAC Measures:
[nQSError: 15003] Missing most detailed table for dimension tables: [D_DETAILS,D_EXECUTION_PLAN,D_TASK].
[nQSError: 15001] Could not load navigation space for subject area DAC Measures.
I am also attaching my Business Model layer for easy understanding. I have a fact table and several Dimension table. I got this error only after creating the following hierarchies:
Execution Plan -> Tasks -> Details
Start Date Time Hierarchy
End Date Time Hierarchy
Is there a solution for this problem? Thanks in advance!

Yes ! My Task Hierarchy has 3 dimension tables that form a hierarchy :Execution Plan -> Tasks -> Detail
All the 3 levels in the hierarchy are 3 different dimension tables.

OBIEE Evaluate - "Essbase error : Repeated dimension in MDX query"

Hi,
I'm using OBIEE 11.1.1.6.2 BP1 on top of Essbase.
I have a project dimension in Essbase with three levels - Total Project -> Project Class -> Project. I have created a new logical column in OBIEE to query two levels from project dimension, using evaluate function as below:
Evaluate('%1.Members, %2.Members', "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen2,Project" , "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen4,Project" ).
The above column when used in analysis, works fine, returning "Total Project" and all the projects. It breaks however when any filter is applied on project dimension with the following error:
"[nQSError: 96002] Essbase Error: Repeated dimension [Project] in MDX query".
I donot have any MDX skills and would appreciate if anyone can explain this error and provide any workaround for this. Here's the MDX that fails:
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])
Many Thanks

This issue regarding BIEE
because MDX is wrong
With
set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
select
{} on columns,
{{[_Project0]}} properties GEN_NUMBER on rows
from [ASOCUBE.Planning]
where ([Project].[1000000-Treatment Plant])

'Essbase Error: Repeated dimension [Accounts] in MDX query'

Dear Essbase Gurus,
I have an error in a query passed to my Essbase cube from an OBI front end, but the errors states quite clearly that it is an essbase error:
'Essbase Error: Repeated dimension Accounts in MDX query'
This is the query it generated:
With
set Accounts3 as 'Accounts.Generations(3).members'
set Attribute Calculations2 as '[Attribute Calculations].Generations(2).members'
set Events5 as 'Events.Generations(5).members'
set Month3 as 'Month.Generations(3).members'
set Scenario2 as 'Scenario.Generations(2).members'
set Year2 as 'Year.Generations(2).members'
set Axis1Set as 'crossjoin ({Accounts3},crossjoin ({Attribute Calculations2},crossjoin ({Events5},crossjoin ({Month3},crossjoin ({Scenario2},{Year2})))))'
select
{Measures.Total e-revenue} on columns,
NON EMPTY {Axis1Set} properties ANCESTOR_NAMES, GEN_NUMBER on rows
from Richmond.RichPOC
As an Essbase newbie I'm unfamiliar with mdx and have no idea what this means, any help would be appreciated.
Thanks
Ed
Edited by: Ed Higgins, AltiusConsulting.com on Oct 15, 2008 9:26 AM

Hi garycris,
Thanks for taking a look, I fear you may have hit the nail on the head, as I mention we are reporting on this using OBIEE, so we have imported the cube (BSO) into our OBI repository, OBI flattens the cube to make it look like a star schema it doesn't recognise the Accounts dimension correctly so we have to set it to be of type 'Other' after we have imported it, otherwise none of the figures in the Accounts dimension are actually reported (you can see the members but when included in a query no data is returned).
Another issue we found was that OBIEE appeared to substitute the name 'Measures' for Accounts when building the query, so we made 'Measures' the default alias for the Accounts dimension, to add to the issue I probably should have mentioned that the aggregation rule in OBIEE for this fact column has been set to SUM rather than External_Agg, but Oracle support have previously indicated that this is OK to do. The issue originally arose because we wanted to extend on of our dimensions with additional attributes stored in a SQL database table.
Sorry it is all a bit messy, the whole OBI with Essbase as a source is still relatively new, and it looks like there may be a few things for the mighty O to iron out, I posted this in here because the OBIEE forum has no posts with similar issues, so thanks for your help so far and anything else you can add.
Ed

Quantization Error for NI AT-MIO-16E-2

Hi
I wanted to confirm the value of quantization error for the 12-bit NI AT-MIO-16E-2 DAQ. I can take values between -10 to 10 Volts. So the quanitization error would be:
= +/- 0.5*(20/(2^12)) = +/-2.44e-3
Is this correct? This seems like a high amount of error when voltages are below 0.1V
Also, I want to know if the above DAQ card comes with an anti-aliasing filter, depending on the sampling frequency.
Thank you
Karthik

Hi Karthik,
If you choose your measurement range to be +/-10V, the smallest change that can be detected is 20/2^12 = 4.8mV. So the maximum quantization error would be +/-4.8mV. If you're looking to increase the accuracy, you can change the measurement range to be the smallest possible for your requirements.
There's no anti-aliasing filter built in to the DAQ card, but you can easily implement them on a terminal block (analog) such as the SCB-68 or in software (e.g. Low Pass Filter in LabVIEW).
Analog Input Low Pass Filtering with an SCB-68 Terminal Block:
http://digital.ni.com/public.nsf/websearch/5D82A2990FB1D21386256EEE00018FF0?OpenDocument
Hope this helps!
Thanks,
Lesley Y.
Applications Engineering

Is it possible to ignore "Rigid relationships between attributes cannot be changed" when using ProcessUpdate for Dimension?

As per the title is it possible to ignore "Rigid relationships between attributes cannot be changed" when using ProcessUpdate for Dimension?
We have a case where very rarely an item might have been miscategorised so the brand is manually changed. We want this dimension to be rigid to speed up ProcessUpdate.
We do a ProcessFull each night, so it will get corrected then, but during the hourly updates we would just like to ignore this error if possible?

Hello,
The rigid relationship should be defined when the members will not change over time. Here are some threads regarding rigid relationship for your reference, please see:
Processing OLAP Cube: http://social.technet.microsoft.com/Forums/sqlserver/en-US/17a55593-9543-404e-a579-0a011965585d/processing-olap-cube?forum=sqlanalysisservices
Flexible and rigid relationship: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d8f5443-065d-4485-9385-6f0b5fa417da/flexible-and-rigid-relationship?forum=sqlanalysisservices
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Error for dimension builting

Similar Messages

Maybe you are looking for