Dimension Hierarchy - Measures on top level

Scenario is about 10 Controlling cubes which all share the dimension "project". The "project" dimension is based on a table that looks like:
#CODE: Task-Line (MS NAV Jobs, parts of project) e.g. 1000-13#773000000
#Project e.g. 1000-13 (parent for hierarchy)
All measures are on level of job lines and are aggregated to projects.
Now i want to build a cube with measures on project level, which is the aggregated parent level.
How to solve this?
Best regards,
Wolgang

Hi Wolgang,
According to your description, many cubes share a dimension in your Analysis Service project, now what you want is that create a measure that can be shared for all the cubes, right?
As you can see on the link below
Dimensions are on database level, and the measures are on cube level. So I am afraid you requirement cannot be achieved currently.
If I have anything misunderstand, please point it out. Thank you for your understanding.
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

OBIEE BI Answers: Wrong Aggregation Measures on top level of hierarchy

Hi to all,
I have following problem. I hope to be clear in my English because it's a bit complicated to explain.
I have following fact table:
Drug Id Ordered Quantity
1 9
2 4
1 3
2 2
and following Drug Table:
Drug Brand Id Brand Description Drug Active Ingredient Id Drug Active Ingredient Description
1 Aulin 1 Nimesulide
2 Asprina 2 Acetilsalicilico
In AWM i've defined a Drug Dimension based on following hierarchy: Drug Active Ingredient (parent) - Drug Brand Description (leaf) mapped as:
Drug Active Ingredient = Drug Active Ingredient Id of my Drug Table (LONG DESCRIPTION Attribute=Drug Active Ingredient Description)
Drug Brand Description = Drug Brand Id of my Drug Table (LONG DESCRIPTION Attribute = Drug Brand Description)
Indeed in my cube I've mapped leaf level Drug Brand Description = Drug Id of my fact table. In AWM Drug Dimension is mapped as Sum Aggregation Operator
If I select on Answers Drug Active Ingredient (parent of my hierarchy) and Ordered Quantity I see following result
Drug Active Ingredient Description Ordered Quantity
Acetilsalicilico 24
Nimesulide 12
indeed of correct values
Drug Active Ingredient Description Ordered Quantity
Acetilsalicilico 12
Nimesulide 6
EXACTLY the double!!!!!!! But if I drill down Drug Active Ingredient Description Acetilsalicilico I see correctly:
Drug Active Ingredient Description Drug Brand Description Ordered Quantity
Acetilsalicilico
- Aspirina 12
Total 12
Wrong Aggregation is only on top level of hierarchy. Aggregation on lower level of hierarchy is correct. Maybe Answers sum also Total Row????? Why?????
I'm frustrated. I beg your help, please!!!!!!!!
Giancarlo

Hi,
in NQSConfig.ini I can't find Cache Section. I post all file. Tell me what I must change. I know your patient is quite at limit!!!!!!! But I'm a new user of OBIEE.
# NQSConfig.INI
# Copyright (c) 1997-2006 Oracle Corporation, All rights reserved
# INI file parser rules are:
# If values are in literals, digits or _, they can be
# given as such. If values contain characters other than
# literals, digits or _, values must be given in quotes.
# Repository Section
# Repositories are defined as logical repository name - file name
# pairs. ODBC drivers use logical repository name defined in this
# section.
# All repositories must reside in OracleBI\server\Repository
# directory, where OracleBI is the directory in which the Oracle BI
# Server software is installed.
[ REPOSITORY ]
#Star     =     samplesales.rpd, DEFAULT;
Star = Step3.rpd, DEFAULT;
# Query Result Cache Section
[ CACHE ]
ENABLE     =     YES;
// A comma separated list of <directory maxSize> pair(s)
// e.g. DATA_STORAGE_PATHS = "d:\OracleBIData\nQSCache" 500 MB;
DATA_STORAGE_PATHS     =     "C:\OracleBIData\cache" 500 MB;
MAX_ROWS_PER_CACHE_ENTRY = 100000; // 0 is unlimited size
MAX_CACHE_ENTRY_SIZE = 1 MB;
MAX_CACHE_ENTRIES = 1000;
POPULATE_AGGREGATE_ROLLUP_HITS = NO;
USE_ADVANCED_HIT_DETECTION = NO;
MAX_SUBEXPR_SEARCH_DEPTH = 7;
// Cluster-aware cache
// GLOBAL_CACHE_STORAGE_PATH = "<directory name>" SIZE;
// MAX_GLOBAL_CACHE_ENTRIES = 1000;
// CACHE_POLL_SECONDS = 300;
// CLUSTER_AWARE_CACHE_LOGGING = NO;
# General Section
# Contains general server default parameters, including localization
# and internationalization, temporary space and memory allocation,
# and other default parameters used to determine how data is returned
# from the server to a client.
[ GENERAL ]
// Localization/Internationalization parameters.
LOCALE     =     "Italian";
SORT_ORDER_LOCALE     =     "Italian";
SORT_TYPE = "binary";
// Case sensitivity should be set to match the remote
// target database.
CASE_SENSITIVE_CHARACTER_COMPARISON = OFF ;
// SQLServer65 sorts nulls first, whereas Oracle sorts
// nulls last. This ini file property should conform to
// that of the remote target database, if there is a
// single remote database. Otherwise, choose the order
// that matches the predominant database (i.e. on the
// basis of data volume, frequency of access, sort
// performance, network bandwidth).
NULL_VALUES_SORT_FIRST = OFF;
DATE_TIME_DISPLAY_FORMAT = "yyyy/mm/dd hh:mi:ss" ;
DATE_DISPLAY_FORMAT = "yyyy/mm/dd" ;
TIME_DISPLAY_FORMAT = "hh:mi:ss" ;
// Temporary space, memory, and resource allocation
// parameters.
// You may use KB, MB for memory size.
WORK_DIRECTORY_PATHS     =     "C:\OracleBIData\tmp";
SORT_MEMORY_SIZE = 4 MB ;
SORT_BUFFER_INCREMENT_SIZE = 256 KB ;
VIRTUAL_TABLE_PAGE_SIZE = 128 KB ;
// Analytics Server will return all month and day names as three
// letter abbreviations (e.g., "Jan", "Feb", "Sat", "Sun").
// To use complete names, set the following values to YES.
USE_LONG_MONTH_NAMES = NO;
USE_LONG_DAY_NAMES = NO;
UPPERCASE_USERNAME_FOR_INITBLOCK = NO ; // default is no
// Aggregate Persistence defaults
// The prefix must be between 1 and 8 characters long
// and should not have any special characters ('_' is allowed).
AGGREGATE_PREFIX = "SA_" ;
# Security Section
# Legal value for DEFAULT_PRIVILEGES are:
# NONE READ
[ SECURITY ]
DEFAULT_PRIVILEGES = READ;
PROJECT_INACCESSIBLE_COLUMN_AS_NULL     =     NO;
MINIMUM_PASSWORD_LENGTH     =     0;
#IGNORE_LDAP_PWD_EXPIRY_WARNING = NO; // default is no.
#SSL=NO;
#SSL_CERTIFICATE_FILE="servercert.pem";
#SSL_PRIVATE_KEY_FILE="serverkey.pem";
#SSL_PK_PASSPHRASE_FILE="serverpwd.txt";
#SSL_PK_PASSPHRASE_PROGRAM="sitepwd.exe";
#SSL_VERIFY_PEER=NO;
#SSL_CA_CERTIFICATE_DIR="CACertDIR";
#SSL_CA_CERTIFICATE_FILE="CACertFile";
#SSL_TRUSTED_PEER_DNS="";
#SSL_CERT_VERIFICATION_DEPTH=9;
#SSL_CIPHER_LIST="";
# There are 3 types of authentication. The default is NQS
# You can select only one of them
#----- 1 -----
#AUTHENTICATION_TYPE = NQS; // optional and default
#----- 2 -----
#AUTHENTICATION_TYPE = DATABASE;
# [ DATABASE ]
# DATABASE = "some_data_base";
#----- 3 -----
#AUTHENTICATION_TYPE = BYPASS_NQS;
# Server Section
[ SERVER ]
SERVER_NAME = Oracle_BI_Server ;
READ_ONLY_MODE = NO;     // default is "NO". That is, repositories can be edited online.
MAX_SESSION_LIMIT = 2000 ;
MAX_REQUEST_PER_SESSION_LIMIT = 500 ;
SERVER_THREAD_RANGE = 40-100;
SERVER_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
DB_GATEWAY_THREAD_RANGE = 40-200;
DB_GATEWAY_THREAD_STACK_SIZE = 0; // default is 256 KB, 0 for default
MAX_EXPANDED_SUBQUERY_PREDICATES = 8192; // default is 8192
MAX_QUERY_PLAN_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_INFO_CACHE_ENTRIES = 1024; // default is 1024
MAX_DRILLDOWN_QUERY_CACHE_ENTRIES = 1024; // default is 1024
INIT_BLOCK_CACHE_ENTRIES = 20; // default is 20
CLIENT_MGMT_THREADS_MAX = 5; // default is 5
# The port number specified with RPC_SERVICE_OR_PORT will NOT be considered if
# a port number is specified in SERVER_HOSTNAME_OR_IP_ADDRESSES.
RPC_SERVICE_OR_PORT = 9703; // default is 9703
# If port is not specified with a host name or IP in the following option, the port
# number specified at RPC_SERVICE_OR_PORT will be considered.
# When port number is specified, it will override the one specified with
# RPC_SERVICE_OR_PORT.
SERVER_HOSTNAME_OR_IP_ADDRESSES = "ALLNICS"; # Example: "hostname" or "hostname":port
# or "IP1","IP2":port or
# "hostname":port,"IP":port2.
# Note: When this option is active,
# CLUSTER_PARTICIPANT should be set to NO.
ENABLE_DB_HINTS = YES; // default is yes
PREVENT_DIVIDE_BY_ZERO = YES;
CLUSTER_PARTICIPANT = NO; # If this is set to "YES", comment out
# SERVER_HOSTNAME_OR_IP_ADDRESSES. No specific NIC support
# for the cluster participant yet.
// Following required if CLUSTER_PARTICIPANT = YES
#REPOSITORY_PUBLISHING_DIRECTORY = "<dirname>";
#REQUIRE_PUBLISHING_DIRECTORY = YES; // Don't join cluster if directory not accessible
DISCONNECTED = NO;
AUTOMATIC_RESTART = YES;
# Dynamic Library Section
# The dynamic libraries specified in this section
# are categorized by the CLI they support.
[ DB_DYNAMIC_LIBRARY ]
ODBC200 = nqsdbgatewayodbc;
ODBC350 = nqsdbgatewayodbc35;
OCI7 = nqsdbgatewayoci7;
OCI8 = nqsdbgatewayoci8;
OCI8i = nqsdbgatewayoci8i;
OCI10g = nqsdbgatewayoci10g;
DB2CLI = nqsdbgatewaydb2cli;
DB2CLI35 = nqsdbgatewaydb2cli35;
NQSXML = nqsdbgatewayxml;
XMLA = nqsdbgatewayxmla;
ESSBASE = nqsdbgatewayessbasecapi;
# User Log Section
# The user log NQQuery.log is kept in the server\log directory. It logs
# activity about queries when enabled for a user. Entries can be
# viewed using a text editor or the nQLogViewer executable.
[ USER_LOG ]
USER_LOG_FILE_SIZE = 10 MB; // default size
CODE_PAGE = "UTF8"; // ANSI, UTF8, 1252, etc.
# Usage Tracking Section
# Collect usage statistics on each logical query submitted to the
# server.
[ USAGE_TRACKING ]
ENABLE = NO;
//==============================================================================
// Parameters used for writing data to a flat file (i.e. DIRECT_INSERT = NO).
STORAGE_DIRECTORY = "<full directory path>";
CHECKPOINT_INTERVAL_MINUTES = 5;
FILE_ROLLOVER_INTERVAL_MINUTES = 30;
CODE_PAGE = "ANSI"; // ANSI, UTF8, 1252, etc.
//==============================================================================
DIRECT_INSERT = YES;
//==============================================================================
// Parameters used for inserting data into a table (i.e. DIRECT_INSERT = YES).
PHYSICAL_TABLE_NAME = "<Database>"."<Catalog>"."<Schema>"."<Table>" ; // Or "<Database>"."<Schema>"."<Table>" ;
CONNECTION_POOL = "<Database>"."<Connection Pool>" ;
BUFFER_SIZE = 10 MB ;
BUFFER_TIME_LIMIT_SECONDS = 5 ;
NUM_INSERT_THREADS = 5 ;
MAX_INSERTS_PER_TRANSACTION = 1 ;
//==============================================================================
# Query Optimization Flags
[ OPTIMIZATION_FLAGS ]
STRONG_DATETIME_TYPE_CHECKING = ON ;
# CubeViews Section
[ CUBE_VIEWS ]
DISTINCT_COUNT_SUPPORTED = NO ;
STATISTICAL_FUNCTIONS_SUPPORTED = NO ;
USE_SCHEMA_NAME = YES ;
USE_SCHEMA_NAME_FROM_RPD = YES ;
DEFAULT_SCHEMA_NAME = "ORACLE";
CUBE_VIEWS_SCHEMA_NAME = "ORACLE";
LOG_FAILURES = YES ;
LOG_SUCCESS = NO ;
LOG_FILE_NAME     =     "C:\OracleBI\server\Log\CubeViews.Log";
# MDX Member Name Cache Section
# Cache subsystem for mapping between unique name and caption of
# members for all SAP/BW cubes in the repository.
[ MDX_MEMBER_CACHE ]
// The entry to indicate if the feature is enabled or not, by default it is NO since this only applies to SAP/BW cubes
ENABLE = NO ;
// The path to the location where cache will be persisted, only applied to a single location,
// the number at the end indicates the capacity of the storage. When the feature is enabled,
// administrator needs to replace the "<full directory path>" with a valid path,
// e.g. DATA_STORAGE_PATH = "C:\OracleBI\server\Data\Temp\Cache" 500 MB ;
DATA_STORAGE_PATH     =     "C:\OracleBIData\cache" 500 MB;
// Maximum disk space allowed for each user;
MAX_SIZE_PER_USER = 100 MB ;
// Maximum number of members in a level will be able to be persisted to disk
MAX_MEMBER_PER_LEVEL = 1000 ;
// Maximum size for each individual cache entry size
MAX_CACHE_SIZE = 100 MB ;
# Oracle Dimension Export Section
[ ORA_DIM_EXPORT ]
USE_SCHEMA_NAME_FROM_RPD = YES ; # NO
DEFAULT_SCHEMA_NAME = "ORACLE";
ORA_DIM_SCHEMA_NAME = "ORACLE";
LOGGING = ON ; # OFF, DEBUG
LOG_FILE_NAME     =     "C:\OracleBI\server\Log\OraDimExp.Log";

Derived Hierarchy Permissions - cascading top level permissions to all subseuent levels

I have created a 3-level derived hierarchy in my MDS model.
Level 1 - divisions, Level 2 - groups, Level 3 - targets per year-month
We have divisional users that would use this structure. so when I add a user I set the permissions at the division level and would like those permissions cascaded down to levels 2 & 3 without going thru and setting permissions on each node in level
2 and level 3. Is it possible to do so? If yes, how? If not, then how do I maintain permissions for my users - how can I make sure that if a user enters a new group for a division, then he/she can use it to set targets?
Thanks,
Sonal

The permission will be inherited by the subtree.
https://msdn.microsoft.com/en-us/library/ee633750.aspx
On the Hierarchy Members tab, each hierarchy is represented as a tree structure. When you assign permission to a node in the tree, all children inherit that permission unless permission is explicitly assigned at a lower level.

A Question Related to Dimension Hierarchy

Hi All,
While going through some hierarchies, i found that some columns were associated with the levels in hierarchy but these columns were not part of level keys.
I want to know that what is difference between the result when columns that are not level keys are associated with a logical level and when such columns are not associated with a logical level ?
Does such columns affect the result when selected in BI Answer?
For exp -
Suppose i have below time dimension hierarchy -
Time
->Grand Total Level 0
---> Year Level1
Year (Level Key)
Year Start Date
Year End Date
---> QuarterLevel2
Quarter(Level Key)
Quarter Start Date
Quarter End Date
---> MonthLevel3
Month(Level Key)
Month Start Date
Month End Date
---> Day Level4
Day (Level Key)
Day Start Date
Day End Date
These start date/end date columns are not part of level keys.
The same thing i have observed in other hierarchies too.
I want to know that what would happen, if these columns are not present at these levels?
So When should we associate columns those are not part of level key to levels and when we should not associate ?
Thanks,
Ashish

Hi ,
The non key columns used in each of the levels help in faster retireval for that aggregate level .
If you look closely at these columns you will find these to be unique ,now having said that another point is that these levels are also used for aggreagation
as we all know.
For ex at the month level the key identifies all the unique moths but if data has to be shown for one particualr month then with the start momth date and end month date the retrieval would be still better :)

Parent-Child hierarchy without facts in top-level

Hello folks,
I've got a fact table which looks like:
fact_id | costs | some_id
1 | 5 | 1
2 | 10 | 1
and a hierarchy which looks like:
id | super_id | some_id
1 | null | null
2 | 1 | 1
3 | 1 | 1
In the business logic layer I defined two keys for the dimension talbe (id and some_id) and built the hierarchy on the first (id).
Also I defined a foreign key from the fact table to the dimension on the second.
As you see no facts are assigned to the first entry (= top-level) in the hierarchy (id = 1).
However the children of 1 have got facts.
What I want is to show the costs for the children (which is the sum of 5 and 10) and the total sum for the parent (30).
However when I drag the hierarchy and the costs into an analysis I get no results available, as there are no facts for the top-level.
How can I fix this?
Regards,
Matthias

Hi Dhar,
thanks for your reply!
What you write coincides with what I thought would happen (but didn't).
Hence there must be some error in my rpd file.
I created my hierarchy right-clicking on the dimension table and only setting the mandatory settings (that is the definition of parent/menber keys and the setup for the hierarchy table).
I didn't touch what admin-tool created inside the hierarchy, which is: a "total" level, where "grand total level" is checked, and a "detail" level, where "Supports rollup to higher level of aggregation" is checked.
What other settings in the admin-tool will I have to touch to step forward?
@anton: I'm using OBIEE 11.1.1.5.0
Regads,
Matthias

Naming of top level in a dimension

Hi,
I was wondering if the naming of the top level in a dimension. Earlier I have just named the top levels whatever suited me the best, and haven't had any problems with that. A couple of days ago I came a across an article on Mark Rittmans weblog where it said that Discoverer and BI beans expect a total level.
Should all the top levels be named total_***** ?
What is the consequence of not naming them total_****?
Anyone have any thoughts on this?
Regards Ragnar

Level names can be reused across dimensions. This is common. For example, detail level data is very often shared across levels. When is comes to summary levels, you need decide whether this makes sense. Consider two hierarchies:
Shipping Hierarchy, with levels:
Total Product
Region Shipments
Country Shipments
Warehouse
Item
Product Type hierarchy, with levels:
Total Product
Brand
Group
Item
In the above case, Total Product in each hierarchy should yield the same values because it is the aggregation of all items. So, you might decide that is ok. A different case might not be ok. Consider:
Shipping Hierarchy, with levels:
Total Product
Region Shipments
Country Shipments
Warehouse
Items shipped
Product Type hierarchy, with levels:
Total Product
Brand
Group
Items sold
Since Items Shipped and Items Sold are likely to have different values, the aggregation of each level will yield a different value. In this case, Total Product as the top of each hierarchy doesn't make sense.
A different twist would be (note the display names):
Shipping Hierarchy, with levels:
Total Shipments with 'Total Product' as display name
Region Shipments
Country Shipments
Warehouse
Items shipped
Product Type hierarchy, with levels:
Total Product Types with 'Total Product' as display name
Brand
Group
Items sold
In this case there will be different levels with different values, but the user will see each as 'Total Product'. Only your user community can tell you if this is want they want.

How to create a custom measure for each level of a dimension

Hi all!
Can Anyone please explain me with an example, how to create a custom measure for each level for a dimension? I dont mine if you use
one or more measures.
thanks in advance
hope someone helps me.

For example:I create a dimension for product_dim witch has 4 levels:total, class, family and item:
d_aben18
n1_aben18
n2_aben18
n3_aben18
n4_aben18
herarchy:h_aben18
cube:cubo_aben18
measure:med_aben18
I create this code to fetch the data to the dimension:
TRAP ON CLEANUP
SQL DECLARE c1 CURSOR FOR SELECT-
total_product_id,1,'N1_ABEN18',total_product_dsc,-
class_id,1,'N2_ABEN18',total_product_id,class_dsc,-
family_id,1,'N3_ABEN18', class_id, family_dsc,-
item_id,1,'N4_ABEN18',family_id,item_dsc-
FROM PRODUCT_DIM
"OPEN THE CURSOR
SQL OPEN c1
"FETCH THE DATA
SQL FETCH c1 LOOP INTO-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N1_aben18_LEVELDEF,:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N2_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N3_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N4_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
"SAVE THE CHANGES
UPDATE
COMMIT
CLEANUP:
SQL CLOSE c1
SHOW 'KK2'
Then I create a cube with use compression off, and in rules sum for example.
After, I create a measure and I select Override the aggregation specification for the cube, in rules I put nonadditive and I would like to create aprogram to assign distinct values to each level of the dimension. For example, I put 1, 2 3, and 4 values, but at the end I would like to put count(distinct(values)).
for that I create another program:
VRB D_RETURN DECIMAL
if D_ABEN18_N1_ABEN18_LEVELDEF eq 'N1_ABEN18'
then D_RETURN = 1
if D_ABEN18_N2_ABEN18_LEVELDEF eq 'N2_ABEN18'
then D_RETURN = 2
if D_ABEN18_N3_ABEN18_LEVELDEF eq 'N3_ABEN18'
then D_RETURN = 3
if D_ABEN18_N4_ABEN18_LEVELDEF eq 'N4_ABEN18'
then D_RETURN = 4
else d_return=26
return d_return
"SHOW D_RETURN
cubo_aben18_med_aben18_stored=d_return
but it doesnt work.I dont know how to put to assign or to see what I want.
I report the measure, or I report the program, but then how can I see the values of the measure?
thanks in advance

Total levels on pivot with dimension hierarchy column incorrect

Hi,
I have a pivot table based on a single subject area, based on an Essbase cube.
The problem I have is that some of the totals against the collapsed dimension hierarchy column are incorrect, it is as if they remember the pre-updated state, even though I have bounced the services and turned all caching off.
When I expand the node then the totals appear correctly, but when reverted to the collapsed state it shows nothing again.
I have turned off caching via EM.
I have tried all flavours of totals, default, server complex aggregate et al with the same result for all.
I have double checked the results at source with an identical query in SmartView and the upper level dimension total is populated in its own right, as well as its children carrying totals which do not sum back to zero.
Any suggestions please??
thanks,
Robert.

Can you validate the query hitting to the database and compare the results?
Mark if helps.
Thanks,

Error when Drill down on top level of hierarchy node

Hi Gurus,
The following error occurs when I drill down to a "Actual Line items sub report" using the "top node" of an hierarchy based report .
But, the same drill down works fine when I drill down using the very sub level of the same hierarchy (without any further levels of hierarchies).
System error in program SAPLRRK0 and form NACHLESEN_INIT_NODE-01-
Any help or work around suggestion would be highly appreciated.
Thanks
Ajay

Hi,
Thanks for the start.
But, My Hierarchy is already active.
Any other place to check for?

Changing the dimension hierarchy level keys in RPD online mode caused issue

Hi,
We tried to correct the dimension hierarchy level keys and remove prefered drill path settings in the business model layer in RPD in online mode. However this caused all the reports and dashboards based off of this subject area to show incorrect, and/or restricted data. The physical query generated by the answers requests were also incorrect.
Even restarting the server and presentation services could not resolve the issue. Can someone please help us to understand what could have caused this issue?
Thanks in advance

Hi,
I am not sure why the existing reports throw an error when I change the RPD dimension hierarchy level keys. Does anyone know how I resolve this issue.
This is urgent. Any help will be most appreciated.
Thanks in advance.

Inserting a level in existing dimension hierarchy

hi,
I have to insert a new level in existing dimension hierarchy with out affecting other reports.
Please let me know how to do
Thanks in advance.

I fixed this problem by doing two things. Firstly I deleted
the summary slide at the end of the quiz. This stopped the error
dialog appearing, but the new slides I was trying to insert were
still overwriting an existing question. I then deleted the
questions that were being overwritten, and all subsequent inserted
questions worked correctly. Seems like something got corrupted in
the question slide.
The quiz result summary page gets regenerated so there's no
problem with deleting it if things get corrupted behind the
scenes.

Report totals with dimension hierarchy column on pivot table incorrect

Hi,
I have a pivot table based report that has one dimension column, a dimension hierarchy column and various measures.
The row totals do not match, detail to total, and I have tried both complex server based aggregate and report based aggregation, but neither are giving me the correct answer.
I have also tried adding the column that is the same as the top level as the hierarchy, but hidden, but this does not help.
I have also tried adding the lowest level of detail column, but hidden, but this does not give me the solution I need as all of the figures then appear at detail not aggregated level.
Any ideas please?
thanks,
Robert.

Can you validate the query hitting to the database and compare the results?
Mark if helps.
Thanks,

Dimension Hierarchy Help

Guys,
We have a product hierarchy that goes like this:
Division, department, category, sub category, range, line, option
We have a logical dimension table that has 2 sources. One source table only goes down to the category level and the other contains the whole hierarchy. What we would like it to do is use the summary table until you go below category level. This sodesn't seem to happen. We have checked the log and if you extract Division in answers OBIEE still queries the detail table.
We have tried making the summary table the number one source but it doesn't help. It only works when you extract Division with Fact information.
This is causing us an issue with prompts which are taking too long as they are querying the detail table.
Does anybosy know how we can force OBI to use the summary table at the top levels?
(We have also looked in to forcing OBI to always use the summary table at certain levels but this doesn't work. The summary table links on a category code and the detail table links on a option code. If detailed fact tables tried to join to the summary table it wouldn't work.)
Thanks in advance,
Jim.

Jim,
Can you create an Alias of the product category table in the physical layer, perform joins as usual.
Now add this as an additional source to your existing logical table, but don't associate this logical table source with ANY levels.
The newly added logical table source must be your 1st source within your logical table.
Now check your SQL related to prompt containing all the levels above category.
neilwelling,
If your issue is same as Jim, give it a try.
let me know if this was helpful.
P.S don't forget to "relaod server metadata" & clear your cache for appropriate results.
-bifacts
http://www.obinotes.com
Edited by: bifacts on Oct 29, 2010 11:04 AM
Edited by: bifacts on Oct 29, 2010 11:06 AM

Obiee dimension hierarchy ?

what is purpose of od dimensional hierarchy in obiee ?

Dimension Hierarchy -
If you Introduce formal hierarchies into a business model it establishes levels for data groupings and calculations and provides paths for drilldown
Steps to Create a Dimension Hierarchy - >
Create a dimension object.
Add a parent-level object.
Add child-level objects.
Determine number of elements.
Specify level columns.
Create level keys.
Create a level-based measure.
Create additional level-based measures.
Create share measures.
Create rank measures.
Add measures to Presentation layer.
Test share and rank measures.
kp

Level Based Measure at Month level.

Hi,
I have defined a level based measure at "Month Level".
I am expecting it have aggregate at month level within a year.
But it is showing aggregation of month without regards to the year. For example in data of four years, for month of Aug it shows aggregation of Aug -2010, 2009, 2008 and 2007.
How i can get Monthly aggregation at Month-Year level ?
The time dimension and its hierarchy are based standard OWB time dimension.
Thank you,
~ Ash

What is the month level key column functionality in your time dimension?
it should be in format of yyyymm but not in just mm ..

Dimension Hierarchy - Measures on top level

Similar Messages

Maybe you are looking for