2 Dimensions to 3 Dimensions

How do I take a circle and make it into a cylinder or a square into a cube?

Well you could make a 3D pie chart with a 100% entry.
An odd question though as Pages is not really a 3D application.
Try:
http://www.freeforum101.com/iworktipsntrick/viewtopic.php?t=71&mforum=iworktipsn trick
instead
Peter

Similar Messages

How to further restrict the task profile 'dimension' to selected dimensions

Hi All,
We have a dimension which we require users to maintain their own master data. We have used the secondary admin task profile which provides default access to the task 'dimension'. THis allows that user access to the BPC Admin console and also to the dimension to maintain dimension members. However, we wish to limit their access to only certain defined dimensions & not give them access to all dimensions. I have tested using this task profile together with a member access profile to limit the secure dimensions for an application, however my understanding is that member access profiles will not restrict access once a user has logged into the BPC Admin Client...i.e the member access profile restricts the ability to read/write to 'facts'/sign data from a BPC front end tool, EG excel.
Any ideas much appreciated as to how to acheive this,
Glen

Hi,
As you said for maintaining dimension members, you had to assign a task to the task profile. However, assigning this task will allow the user to modify any of the dimensions.
You cannot give authorization to allow only selected dimensions. BPC doesnt have this feature. Either the user can modify all the dimensions or none of them.
Hope this helps.

Difference between Dimension Id and Dimension Key

I am reading the third chapter of Rittman's OBIEE book on design of Repository.
It says while building the BMM, don't drag the dimension Id columns from physical layer to logical layer as the BI Server takes care of the join for you but make sure you drag across the dimension key columns as you will need these later on to create your logical table keys.
Can someone enlighten me on what is the difference between a dimension id and dimension key (may be with an example).
Thanks.

Besides the theory says that a fact table can reference any level of a dimension, I couldn't do it with OWB. I don't know if there is a specific way to do that, but I only could assign a dimension detail level to a fact table.
The ID's can have different values when I use a hierarchy in a dimension. OWB generates automatically negative ID's for the more summarized levels.
For example, a product dimension with 2 levels: category and detail. If the product has 4 categories and 20 products (detail level), the table has 4 rows for categories with negative id's. Each row has a category and the fields specific for detail level are empty. The table will have other 20 rows for the detail level, with all fields filled, and all id's positive. The table will have 24 rows in the end.

Mini dimensions and "single dimension" query

Hi everyone,
I thought it is about time to bother you with a question. :)
I have a question about mini dimensions. In BI Apps mini dimensions are used within the dimensions like the Service Request Dimension. This dimension has two logical table sources: W_SRVREQ_D and W_SRVREQ_MD. Each logical table has a separate physical join on the fact table, i.e. the fact tables has a separate foreign key for each table.
The Service Request hierarchy is built up by the following levels: All > SR Attributes > Service Request Detail. The mini-dimension table W_SRVREQ_MD is set on logical level "SR attributes" and W_SRVREQ_D is on logical level "SR Detail".
"Status" is a column which is mapped to both tables and this column is on logical level SR Attributes. When I use Status and a measure from the fact table, the BI Server will hit the mini-dimension, because it is on a higher logical level. So far, so good.
But when I create a request which only contains the column Status, the BI Server chooses the more detailed dimension table W_SRVREQ_D, instead of W_SRVREQ_MD. I'm a suprised by this, because I would expect the BI Server to use the mini dimension table.
This can be a performance problem when a user wants to see all values from a column, for example when creating a filter. I know I can solve this with caching the dimension values, but hey.. you don't use mini dimensions for nothing! ;)
Adding an implict fact doesn't solve the problem. The implicit fact is only used when you combine multiple columns from different dimensions. I've also checked the number of elements per level, but these are also set correctly.
For now I don't see a solution to change this behaviour. Can anyone confirm and explain this behaviour? Does anyone have an idea how to force the BI Server to use the mini dimension table on a "single dimension" query? Thanks!
Regards,
Stijn

Stijn,
Did you ever get an answer to this?
In addition to the scenario that you mentioned (report on Status alone) another common case is a dashboard prompt that has a drop down list box for Status. I would hope that the BI server would choose the mini-dimension instead of a distinct query on the primary dimension (service request).
A possible solution is to add an LTS of a List of values table (LOV) that filters out only the statuses, but the problem there is that a query will result in LOV values that are not in use, whereas if the mini-dimension were used it would only result in actual statuses.
Thanks,
David

How to copy data for certain member from one dimension to another dimension

Dear ,
I want to copy data for certain member ("511102") from one dimension to another combinations of dimensions ,
I have the following combinations for "511102" :
_("Budget2012","FY12","Working.V01","SAR","BegBalance","1011","G_10","custom Grades")_
I want to copy "511102" to "salary"
-salary have the following dimensions :
_("Budget2012","FY12","Working.V01","SAR","BegBalance","General group","All grades","General Employees")_
, I don't know if I could do it by datacopy of cross dimensional , But I don't HOW >>>
Thanks in advance

FIX("Budget2012","FY12","Working.V01","SAR","BegBalance","General group","All grades","General Employees")
"salary"="511102"->"1011"->"G_10"->"custom Grades";
ENDFIX
or
FIX("Budget2012","FY12","Working.V01","SAR","BegBalance")
DATACOPY "511102"->"1011"->"G_10"->"custom Grades" to "salary"->"General group"->"All grades"->"General Employees";
ENDFIX
Key thing in datacopy is to place the dimensions in cross dimension in the same order. Both sides (before and after "TO") should have equal number of dimension members specified.
Cheers,
Alp

Merged Dimensions / Extended Merged Dimensions

Hi friends,
Can you please help me out in this topics Merged Dimensions / Extended Merged Dimensions any articles or any documents with scenarious.
Thanks in advance.

Hi,
Please check the below link for info on the same.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/209c4ed9-9f3e-2e10-628e-b0df41969938&overridelayout=true
Regards,
Raghu

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.

Time Dimensions and Logical dimension "..that not join to any fact source"

Hi Guys,
I get the following error on the ANSWERS front end:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: ToDate(SPECIFICG:[DAggr(RFACT.SPECIFIC [ ] by [ EFact.NO [ ] , Year.ID [ ] ] )], [Level Years]). Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT EFact.NO saw_0, Fact.YTD_E saw_1, EFact.MTD_E saw_2 FROM "E#1" ORDER BY saw_0
The consistency manager shows no errors and the tables are physically joined up via foreign key i.e.
fact year monthday
data - date - date
year month
day
[see screen print|www.metallon.org/test/foreign.jpg]
I would be thankfull for any suggestions!

Hello wildmight.
I followed this tutorial:
http://www.rittmanmead.com/2007/04/30/obi-ee-time-dimensions-and-time-series-calculations/
Why should this layout not work?
Do you have a better idea?
When you say "it has to be one table" do you mean
that quartermonthday and year need to be ONE?
I just rememered that Oracle Hyperion Planning has to have
time and months seperated.
Hello mod100.
What do you mean hierachy over the time dimension?
Is it not obvious from the screen print that I have a hierachy
i.e. yeartotal - years and
quarters - months- days.
I read that by default the LEVELS are set to the lowerst. so thats fine. I set them by myself to the lowest as well but the ERROR is still the same.
no, I have not set the levels as in
http://obiee-tips.blogspot.com/2009/10/logical-levels.html

User cannot view dimensions within EPMA Dimension Library in Shared Library

Greetings,
I presume this must be a security issue, but user cannot view his dimensions in the shared library in EPMA. He can, however view view his application, update the local dimensions, and push to Essbase.
If this is a security issue, what assignment should I provision to enable the user to see these shared dims. Many thanks.

Give that user the rights of
Dimension Editor found under Foundation Service --> Shared Service --> EPMA Administrator and then try again.
Thanks.
HyperEPM

Dimension tables versus dimension Objects

Hi,
We are trying to model a Data Warehouse and I am a little confused about the way the word dimension is used to describe a table and also an object in Oracle.
Our situation is that we will be pulling data from the source system into a staging area made up of materialised views. We thought we would then build dimension tables and fact tables as per Ralph Kimball's definition, but we stumbled across the 'CREATE DIMENSION' command in Oracle that seems to contain so much more than just columns.
Could someone clarify this for me?
Thanks,
Mike

You create dimensions in Oracle just like in any other rdbms using create table statement.
The create dimension statement is optional and is used to optimize certain queries (query rewrite, star transform etc - you can find more about it in oracle warehouse docs).
If you create a dimension using the OEM wizard then create dimension statements are executed as well. In addition, if OLAP option is installed then statements from an OLAP PL/SQL package are executed as well. These statements are only of importance if you plan to use the OLAP feature. Unfortunately, you have only one shot to capture these statements - there is no way to re-create them after the dimension is created. There is no equivalent of 'Show DDL' option available for 'regular' tables. For this reason, OEM is problematic as a tool in designing dimensions: You can tweak them to your heart's content but then when the time comes to deploy them somewhere else - you are stuck. OWB is a little better: it has 'Show DDL' option but that displays only the CREATE DIMENSION statements and not the OLAP package statements. You can get the latter by exporting OWB model to an OLAP bridge however the OWB model does not contain all that is required for OLAP so you end-up with generated defaults.

Limiting Dimension Values to Dimension Values used on Specfic Day

If I have a dimension with thousands of values. And within my cube, on a given day only a few of those dimension values are actually used. How can I limit the scope of my dimension values to be only the values that exist on that given day?

You can check OLAP DML Programs chapter (chapter 4 in 11g doc set) in Oracle OLAP DML Reference document. It's part of the standard olap documentation.
Also regd the parameterization question:
The code as pasted below is already parameterized. By parameterization, do you mean something other than passing value from front-end to the back-end (database)?
Typically the front end report/query will refer to a series of time dimension values -- say, 16-Jul-2012 to 22-Jul-2012 for time. The report would reference a measure with a formula referring to an olap dml program. This program is called repeatedly for each cell and the appropriate dimension member values are passed as input to the program.
argument _tm time <-- implies that the program accepts time dimension value (corresponding to a single cell) as input and works off the same in its calculation.
limit time to _tm <-- usually this is done within a tempstat context to make such changes temporary for calculation w/o affecting external time dimension status. This allows the program to set the context of calculation to current cell (say 18-Jul-2012)
"hence what follows for the rest of the program acts on the restricted status in order to calculate the current cell's value corresponding to time dimension value = 18-Jul-2012.
That's also why the same program can return a different value for each cell (different return value for 18-Jul-2012 compared to return value for 21-Jul-2012) although it's being looped over dimension status implicitly.
HTH
Shankar

Dimension Design - Single Dimension with Multiple Hierarchies

Morning,
the purpose of this discussion is to understand how we should design a specific dimension with 3 levels and multiple hierarchies for optimal performance.
We have an institution dimension with the following characteristics:
Characteristics
Dimension: Institution
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
Hierarchies:
1. Some of the hierarchies have 3 levels and others have only 2 levels (Skip Level)
2. ALL the hierarchies have a TB level and an Institution level
3. None of the hierarchies have the same leafs
4. Some of the hierarchies leafs can overlap
Design:
We are considering two approaches for the institution dimension levels:
a)
Levels:
Hierarchy 1 TB Level
Hierarchy 1 PG Level
Hierarchy 1 Inst Level
Hierarchy 2 TB Level
Hierarchy 2 Inst Level
Hierarchy 3 TB Level
Hierarchy 3 Inst Level
Note:
This approach is working and the resulting dimension and cubes are used by OBIEE, but some of the OBIEE analysis takes a long time (more than a minute) to return the results.
At this point, we are not sure whether this approach will result in an optimal design from a performance perspective and are looking at restructuring the dimension to represent only the three conceptual levels as indicated below.
b)
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
The rest of the dimension i.e. hierarchies, attributes and mappings are defined in the same way.
The cube associated with this dimension have approximately 80 million records.
Please advise on any best practices or design considerations that we need to take into account.
Thanks

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

No business key column is identified on existing dimension - Slow chg dimension

Hi,
I m working to insert/update my Dimension table (in datamart) using SSIS "Kimball Method SCD component " tool.
I have different columns as PK in source and identity column as PK in Dimension table.
I also have Unique Index on the columns in dimension which are PK in source table yet I m getting error from the tool that "no business key column is identified on existing dimension"
Any suggestions?
Thanks,

Business key needs to be defined in the component tool itself.
Double click the component and it will open a wizard kind dialog box.
The first tab is "Existing Dimension Input Column Definitions".
In this tab, the grid has a column "SCD Column Type" which looks like label field but if you click it twice, it turns into dropdown list and from here, you can define Business key for your dimension table.
HTH

Replace dimension with renamed dimension

Hi
We have the following situation. We are currently in the development stage and use Essbase. We have already developed a set of reports but now some the names and aliases of our dimensions need to be changed. In one case, the name of the dimension is changed from "ACCOUNT" to "Account".
However, the reports do not seem to pick up the change. They keep referring to ACCOUNT and error out because they cannot find this dimension anymore. Any suggestions on how to deal with this issue?
yours
Arie

First, is this FR or WA. WA does have a renamer utility that can be quite cumbersome to work with, but if you export the WA report and open up in a text editor, you can do a search and replace on your dimension member.
The same goes with FR, depending on how many objects you have in your report you might have to do a trial and error, but doing an export of the report and doing a search and replaces usually works for me. Any further issues might require a little rework of your reports in there respective design client.
Hope this helps.

Expand Dimension using another dimension Property

Hi guys,
My template has Product in the Rows (User Defined) and Time in the Collums.
The Entity dimension is changed at the context, but I want Currency to show the value of the property "Currency" of Entity dimension.
I've tryed to do this putting Currency at the collum, and trying to filter it by Dimension Property, but I didnt succeed.
Any thoughts?
Thanks in advance.
Adriano Frossard

Hi Adriano,
Simply put currency in the page axis and in the EPMOlapMemberO formula use formula to get a property of entity. Read here: Static report in BPC NW 10
Vadim

Joining a dimension with another dimension

I have a customer dimension, which had the registration date as an attribute. I want to join to this column in the date dimenion so that I can do rollups and drilldowns. Couple of questions:
- Is this design violating the star schema model?
- How do I accomplish this in OWB, if I have customer and date modeled as dimensions?
Appreciate your help.

Hi,
Yes it would be a violation of a pure Kimball design star schema, but my question is do you have a pure customer dimension, or do you have a customer dimension and should there possible also be a fact table with customer related measures(facts) so you can do the slicing and dicing?
When dealing with designing your datamodel or changes to the datamodel, always try to stay true to the architecture you chose at the start. Keep going back to the rules that came with the design decisions. So if you chose star schema, try stick to that and with each change, review the change against the rules for star schema design. In my opinion you may deviate, but in those cases always do that for the right reasons and document the rationale for that in the design.
grts,
Ed

2 Dimensions to 3 Dimensions

Similar Messages

Maybe you are looking for