Addine New Dimension In An Existing Cube

Hi fellows,
Im not an expert so need you feedback.
I am supporting a cube that was built a decade ago using Essbase 6.5. It has 7 dimensions (3 dense, 4 sparse). With the new reporting requirement, I need to add a new dimension to be called "BaseTimePeriod" that seems like a Time dimension but will show the "Constant Dollar" amount calcuation for difference Scenarios.
Since the cube has been there for so long, and the expert that has pioneered that cube is no longer in the company. All of our reports uses API being called in MS Excel to retrieve data from the cube and format it the way the users wanted it to be. As well as 75% of our data are user input using the Essbase Excel Add-in, "lock/send" commands.
My problem now is that, since I need to introduce another dimension for the "Constant Dollar" calculation, is there any way that if I add a new dimension the existing process of uploading data by the users as well as retrieving data through Excel API will not be affected?
I tried to add new dimension in the R&D server that we have when I try to retrieve historical data from the cube in the Excel since there is "BaseTimePeriod" dimension before, the Excel report layout gets affected and inserts a new row placing "BaseTimePeriod" in that cell since this not yet there before. And when I try to upload data through Excel Add-in "lock/send" action, it did allow me unless I put a member from the "BaseTimePeriod" to complete the dimension member combination.
My questions now are:
1) How can I add a new dimension without impact from the historical data?
2) Is there any way to place a default value for the new dimension for the historical data so it would complete the dimension member combination, so whenever I retrieve and upload data there will be no problem?
Any insights related to this questions is highly appreciated. Thanks!
obelisk

I tried to add new dimension in the R&D server that
we have when I try to retrieve historical data from
the cube in the Excel since there is "BaseTimePeriod"
dimension before, the Excel report layout gets
affected and inserts a new row placing
"BaseTimePeriod" in that cell since this not yet
there before. And when I try to upload data through
Excel Add-in "lock/send" action, it did allow me
unless I put a member from the "BaseTimePeriod" to
complete the dimension member combination.Essbase must have all (non-attribute) dimensions represented for any data operation to happen. If you think about it, each cell of data represents the intersection of exactly 1 member from each dimension and, behind the scenes, the storage mechanisms are focused on optimizing those relationships. Thus, you can see how the BaseTimePeriod member got added to your retrieve as Essbase didn't know which member from BaseTimePeriod you wanted and made the assumption that you wanted the dimension level member. If you place that dimension level member into your retrieve range (along side any of the other "page" (i.e. filter) fields, the retrieve will not insert a row. The insertion of the row can be extremely hazardous as it pushes the other rows down by one; your end users may be making decisions that effect the existence of your company based on formulas reading those cells and, effectively, the formulas may be referencing data from the wrong row..
My questions now are:
1) How can I add a new dimension without impact from
the historical data?Although my forte is not cube design (I work mostly with frontends to Essbase), most situations I have seen when this happens the historical data is assigned a distinct member within the new dimension (assuming you aren't going to go back and reload the data from the sources and map the data based on the new dimension's values in the dataset.
2) Is there any way to place a default value for the
new dimension for the historical data so it would
complete the dimension member combination, so
whenever I retrieve and upload data there will be no
problem?As stated above, put a member from the dimension, most likely the dimension member itself, into the existing Excel templates.
Good Luck!
Tim Tow
Applied OLAP, Inc

Similar Messages

Problem while adding a new dimension in a existing cube with data in BW3.5

Hi,
We are trying to create a new dimension with new characteristics in a existing cube. But while activating we are getting error that "InfoCube contains data; intentional changes not permitted". Can we add a new dimension in a existing cube with data in BW3.5? If it is not possible then we can take the backup and delete the data from cube and then change the cube. But my question is that, when we will transport the cube with changes to quality then will it transport successfully or same procedure needs to be done there as well.
Regards,
Saikat

hi,
Adding new infoobject /dimension to the cube containing data in 3.5 is not possible.
easier solution is create a new cube similar to old and add the new dimension and proceed.
else you have to drop data and transport.
Ramesh

Adding New Dimension In An Existing Cube (Block)

Hi fellows,
Im not an expert so need you feedback.
I am supporting a cube that was built a decade ago using Essbase 6.5. It has 7 dimensions (3 dense, 4 sparse). With the new reporting requirement, I need to add a new dimension to be called "BaseTimePeriod" that seems like a Time dimension but will show the "Constant Dollar" amount calcuation for difference Scenarios.
Since the cube has been there for so long, and the expert that has pioneered that cube is no longer in the company. All of our reports uses API being called in MS Excel to retrieve data from the cube and format it the way the users wanted it to be. As well as 75% of our data are user input using the Essbase Excel Add-in, "lock/send" commands.
My problem now is that, since I need to introduce another dimension for the "Constant Dollar" calculation, is there any way that if I add a new dimension the existing process of uploading data by the users as well as retrieving data through Excel API will not be affected?
I tried to add new dimension in the R&D server that we have when I try to retrieve historical data from the cube in the Excel since there is "BaseTimePeriod" dimension before, the Excel report layout gets affected and inserts a new row placing "BaseTimePeriod" in that cell since this not yet there before. And when I try to upload data through Excel Add-in "lock/send" action, it did allow me unless I put a member from the "BaseTimePeriod" to complete the dimension member combination.
My questions now are:
1) How can I add a new dimension without impact from the historical data?
2) Is there any way to place a default value for the new dimension for the historical data so it would complete the dimension member combination, so whenever I retrieve and upload data there will be no problem?
Any insights related to this questions is highly appreciated. Thanks!
obelisk

If you add the new dimension to a cube that already has data, you should get a prompt when you save the outline to associate the existing data with a member from the new dimension. You will then go into a dense restructure which could take a while, depending on the size of your database. Another option would be to export your data in column format and load it into a relational table in something like SQL or Access, you can then add the new dimension to the export in the relational tool, export it back out to a text file and use a load rule to reload it.
As far as the lock & send and existing reports, in most cases, adding a new dim will result in all of those needing to be updated. This is why we try not to add new dims to existing cubes, especially ones that have been around a while.
Another thing to consider is the impact of adding a new dim. I don't know the size of your existing database, but you are going to increase it by adding a new dim and things like consolidation time and retrievals can be impacted, so you need to test all of this.
You should evaluate why you need a new dim and determine if you can achieve the same result without adding a new dim. While a new dim might be the preference in a new cube design, when dealing with something that has been around a while you might want to be creative and somewhat more compromising if it is the lesser of two evils. If everyone is committed to a rebuild then go ahead and rebuild especially if it's been around a while, there are probably other things that can stand to be cleaned up as well, but if nobody wants to deal with that, then look to see if you can get their without adding a new dim, perhaps a new roll up in a existing dim or an attribute dim. A more thorough explanation of what the business case is would help to provide an alternate solution.

How to cretae new dimension in an existing cube in BI7

HI BI Gurus
Could you please let me know that is it possible to add a new Dimension in a BI 7 infocube using the Remodelling tool . The cube name is 0TCT_C21 and the dim table is /BI0/D0TCT_C212 . I want to redefine the existing Dim table and want to remove the char
Process Instance (SID) (0TCTINSTSID) and want to create another new dim whic will be a line Item dim and will ad dthe char as Line item char . because the DIm/Fact ratio is 96% in the cube . The chars are in the existing dimension is BW System,Process Chain ID,Process Chain LOG ID,Process Type,Process Variant,Object Version .
Please let me know your view and also is it possible to chage the dimension and add new dimension ?
Regards
Saptarshi

Hi
This is not possible through remodelling. Please see this http://help.sap.com/erp2005_ehp_04/helpdata/EN/9b/0bc041f123c717e10000000a155106/frameset.htm.
For your requirement , you will have to delete the data and make changes to the existing flow. But you should take care of all the issues that might come up with this changes.
Cheers
Chanda

Urgent New Dimension to be added

Hi All,
i have to add new dimension to the existing cube using EIS 7.1.2 and SQL server 2005
IncludeInReport
Member Names
NoCloseClaims
CloseClaims
IncludeInReport itself is a column and it is having only 0's and 1's.
and they had given specifications as
The “NoCloseClaims” member is 0 and matches all records where the “IncludeInReport” column = 0;
and the “CloseClaims” member is 1 and matches all records where the “IncludeInReport” column = 1.
please let me know how to create these members in EIS and fulfil these two conditions.
Is it possible to create members under IncludeInReport?
Thanks in advance
prathap

Asad,
The other way could be to use the BuPaController to find the values like ROLES, GROUPS etc. from Customizing.
Use the code below to access the ROLE for a BP.
DATA: lv_bupacontroller TYPE REF TO cl_crm_ic_bupacontroller_impl.
DATA: ls_profile TYPE crmc_ic_bpident.
lv_bupacontroller ?= get_custom_controller( 'BuPaController' ).
CHECK lv_bupacontroller IS BOUND.
ls_profile = lv_bupacontroller->get_profile( ).
The field <b>ls_profile-BPROLE_CREATE</b> has the role which you want.
Cheers,
Ankur

Adding a New Dimension to a CUBE

Hello
Being in new at Oracle OLAP...
If I need to add a new dimension, SHOULD I RECREATE the cube entirely again??
Is not there any other way??
Regards

Each cell in a cube is referenced by a dimension. Think of it as pointers to cells in a multi-dimensional array.
So when you add or remove a dimension, what should happen to all those cells.
In a way you are breaking the cube.
Since cube data is loaded from a table, you can always re-load your cube after adding or removing a dimension.
Dimensions are not added/removed frequently, once the design is finalized. You may add a new hierarchy to existing dimensions, which is done more frequently compared to adding a dimension. After adding a new hierarchy, you just have to re-aggregate cube data and not re-load from relational source.
Cubes are created for reporting, and can be deleted/recreated or truncated - monthly, quarterly or yearly - for various reasons.
Your source transactional detailed data should be in one (or more) fact tables and should never be deleted.
Is there any "operational" concern in a Production environment, because of which you are asking this question?
One trick could be: to create the new cube (with more dimensions or less dimensions than the original cube) and then COPY DATA from original cube into that new cube.
But it may take the same amount of time as re-loading the new cube from the relational source.

New Dimension to a Cube

Hi,
We've a cube already in production (with huge amount of data). Now we have to add few more 'new' characteristics to this cube.
My question is, can I create new Dimension and add characteristics to this without deleting data?
As the characteristics are new, we don't have to care about reloading the cube as data for these new characteristics don't exist.
Can it be done? Any thoughts?
Regards,
Vikrant.

Hello,
If you had a new characteristic to an existing dimension you don't have to delete data. I already done that procedure many times.
This can help you too:
From this weblog:
Remodeling in NW BI 2004s
"In BW 3.5 version, if data is present in an infoprovider, we can add an infoobject to it, but we cannot delete or replace an existing infoobject in it, unless all infoprovider data is deleted.
This problem has been overcome in BI 2004s version, where the concept of 'Remodeling' can be used to change the structure of an infoprovider even while it holds data."
Ok, so, in version BW3.X and BI7 you can add a new characteristic to an existing dimension, but you have more options in BI7. If you want to had a new dimension you have to delete all data.
Regards,
Jorge Diogo

Error VLD-0370 add a new dimension to a cube

Hello together!
I have a little Problem with my OWB 11.2.0.3 on a new machine. We run OWB 11.2.0.3 on different machines, but on our new machine I have a little problem with ROLAP -Dimensions. I imported my Rolap Dimensions an Cubes from a other machine, all works fine (validate, deploy) but when I genereate a new ROLAP - Dimension the wizzard, vallidation ok, and add it to the cube. I get VLD-0370 error.
VLD-0370: Für Cube CUB_MEMBER_TRANSACTION_R, Dimension TEST_DIM ist die Referenz nicht an Spalten einer Tabelle oder aktualisierbaren View gebunden.
Eine Cube-Dimensionsreferenz muss an Spalten einer Tabelle oder einer aktualisierbaren View gebunden werden.
It must be something like this:
VLD-0370:For CUB_MEMBER_TRANSACTION_R Cube, Dimension TEST_DIM the reference is not bound to columns in a table or updatable view.
A cube dimension reference must be bound to columns of a table or updatable view.
I cannot create a new dimension ans add it to the cube on the new machine. Don't know why. All locations are fine.
A problem is, I don't find a list or something like that for the VLD-xxxx with hints what to to like the ORA-xxxx.
Thanks a lot from Berlin
Michael

Hi Michael,
The cube has a table related, you have added the dimension to the cube, but the table needs a new column with a foreign key to the table-dimension. When you are modifying an existing cube this is not automatic, you have to add the column and foreign key manually.
Regards
ANA GH

How to add a new dimension in ASO cube without losing all data

Hi,
I have an ASO cube with 18 dimensions and I want to add a new one (regular). When I add this new dimension it asked me that the all data has to cleared before the restructure can take place. If I click yes then I would lose all data regardless of the fact if I have a level0 export or not. Because when I tried to reload the export back into the cube it gave me an error cause all the dimensions were not present in the export. Does anyone know how would I be able to accomplish this task?
Thanks
fikes

You can try this work around solution.
1) Export Lev0 data
2) Clear the cube
3) Add new dimension Regular.
4) Add a default member Reg00 in the new dimension and save.
5) Open the Lev0 data in a text editor, Insert "Reg00" in the begining of the file and Enter.
6) Lev0 file will have first record "Reg00" and the remaining export file will be from the second record.
7) Load the modified file with out rule file.
You can verify that all your history data will be loaded w.r.to the Reg00 of the New dimension Regular.

Does it affects existing SSAS Database if i deploy new one with the changes on existing cube solution file

Hello,
Somehow we lost the solution file for workingcube in prod and i have imported from the prod server and created new solution file.
While importing from server, I have renamed the database name and solution name. I need to do some changes in this cube and deploy it as a new one on the same server (testing purpose). What my question is if i deploy this 'test' cube on the same server(Prod),
does it affect existing cube on Prod since it was imported from that server Database.
Thanks,
KK

The name of the solution is not overly important. What you need to check are the deployment properties. Right click on the project in the solution explorer, and check the settings for the target server and target database name under the deployment section.
As long as your deployment target database name is different to the one that is already deployed it will not affect the existing one in any way. However for insurance I would recommend also taking a backup of the production database. That way if anything
does go wrong you can always just restore the back up.
http://darren.gosbell.com - please mark correct answers

Combining relation facts with dimensions from an Essbase cube

Hi!
I am having trouble combining relational measures (from EBS) with dimensions from an Essbase cube. The dimensions that we want to use for reporting (drilling etc) are in an Essbase cube and the facts are in EBS.
I have managed to import both the EBS tables and the cube into OBIEE (11.1.15) and I have created a business model on the cube. For the cube I converted the accounts dimension to a value based dimension, other than that it was basically just drag and drop.
In this business model I created a new logical table with an LTS consisting of three tables from the relational database.
The relational data has an account key that conforms to the member key of the accounts dimension in the Essbase cube. So in the accounts dimension (in the BMM layer) I mapped the relational column to correct column (that is already mapped to the cube) - this column now has two sources; the relational table and the cube. This account key is also available in the LTS of my fact table.
The content levels for the LTS in the fact table have all been set to detail level for the accounts dimension.
So far I am able to report on the data from the fact table (only relational data) and I can combine this report with account key from the account dimension (because this column is mapped to the relational source as well as the cube). But if expand the report with a column (from the accounts dimension) that is mapped only to the cube (the alias column that contains the description of the accounts key), I get an error (NQSError 14025 - see below).
Seeing as how I have modeled that the facts are connected to the dimension through the common accounts key, I cannot understand why OBIEE doesn't seem to understand which other columns - from the same dimension - to fetch.
If this had been in a relational database I could have done this very easily with SQL; something along the lines of select * from relational_fact, dim_accounts where relational_fact.account_key=dim_accounts.account_key.
Error message:
[nQSError: 14025] No fact table exists at the requested level of detail
Edit:
Regards
Mogens
Edited by: user13050224 on Jun 19, 2012 6:40 AM

Avneet gave you the beginnings of one way, but left out that a couple of things. First, you would want to do the export of level zero only. Second, the export needs to be in column format and third, you need to make sure the load rule you use is set to be additive otherwise the last row will overwrite the previouse values.
A couple of other wats I can think of doing this
Create a replicated partition that maps the 3 non used dimensiosn to null (Pick the member at the top of the dimension in your mapping area)
Create a report script to extract the data putting the three dimensions in the page so they don't show up.
Use the custom defined function jexport in a calc script to get what you want

Read existing cubes with Java OLAP API

Hi,
i am new to the Oracle OLAP API and i have a question for which a do not find the answer in the documentation..
I need to access all existing cubes in a database, get the names, the corresponding dimensions etc.
There is no problem in reading the dimensions their hierarchies, the measures an so on. But i found no method or class to read out the information about cubes (names, dimension).
The only thing i found in the documentation to get a cube was over a MtmMeasureMap, but when i call this method i get the exception: Not supported by server version ORAOLAP10.2.0.1.0
Any hints?
Thanks

In current releases, the OLAP API is primarily a query API. Queries can include measures from multiple cubes, so there is no real purpose for a cube object. Therefore there is no Cube class in the Mdm logical metadata package.
Cubes are useful in OLAP mappings, and there is an MtmCube class in the Mtm mapping metadata package. It is possible to navigate between Mdm and Mtm objects. The code that follows prints out the names of all of the cubes and the names of their dimensions.
I don't understand the "Not supported by server version" error that you got. This sample code works for me in 10.1.0.4, and I expect it would work in 10.2, too.
Geof
MdmMetadataProvider mdp; // given
Hashtable cubes = new Hashtable();
MdmSchema rootSchema = mdp.getRootSchema();
Iterator subSchemas = rootSchema.getSubSchemas().iterator();
collectCubes(rootSchema, cubes);
while (subSchemas.hasNext())
collectCubes((MdmSchema) subSchemas.next(), cubes);
// enumerate cubes
Enumeration cubeList = cubes.keys();
while (cubeList.hasMoreElements())
MtmCube cube = (MtmCube) cubes.get(cubeList.nextElement());
System.out.print(cube.getName() + ": ");
Iterator dimensionMaps = cube.getDimensionMaps().iterator();
boolean first = true;
while (dimensionMaps.hasNext())
MtmDimensionMap dimensionMap = (MtmDimensionMap) dimensionMaps.next();
MdmDimension dimension = (MdmDimension) dimensionMap.getMdmSource();
if (first)
first = false;
else
System.out.print(", ");
System.out.print(dimension.getName());
System.out.println();
void collectCubes(MdmSchema schema, Hashtable cubes)
Iterator measures = schema.getMeasures().iterator();
while (measures.hasNext())
MdmMeasure measure = (MdmMeasure) measures.next();
MtmMeasureMap measureMap = measure.getMeasureMap();
MtmCube cube = measureMap.getCube();
// See if we have already visited this cube for another measure
String id = cube.getID();
if (null == cubes.get(id))
cubes.put(id, cube);
}

Create a new dimension in business layer from Data source: text file on the web

Hi,
I have a text data source which is published every few hours that is accessible from a certain URL. I follow the instruction given in this http://scn.sap.com/docs/DOC-43144 - where it shows in great detail how to create the connection, data foundation as well as business layer to create a universe for this type of data.
All is well - I can use this universe in my WEBI doc and display the data.
However, in order for me to merge the data from this universe with another universe, I need to create new dimension based on the data from the text file. The new dimension value is simply the first 4 characters of the Subject found in the text file. The "Subject" dimension is of variant type: varchar.
Following the guide mentioned earlier, the connection is using SAP BO OpenConnectivity driver. And this driver limits severely the SQL statement that I can use to extract a substring of another string. Here's the screenshot of the SQl expression that I can use with this driver
After hours of searching, I cannot find any other connection driver for a text file that's published on a certain URL. The BO OpenConnection driver is the best that I could find.
So here are my problems
1. one of my data source is a text file published on a web
2. the only connection I can create does not allow me to create new dimension in the universe to create an important column "subject ID"
3. I can create the column in webi as a variable. But when I do so, I cannot merge it with existing dimension (webi not allowing to merge these 2 types). And without the merge, the flat file universe with my database universe can't be combined.
I'm using WEBI Rich client version 4.1 SP3 Patch 1. Build 14.1.3.1300
Is there any other idea that you can suggest without requiring to change the extracted data?
Thanks.
With warm regards

Hi Bala,
Were you able to find out a solution for the problem with uploading values for a variable from a text file on the web? I am confronted with the same request from users.
Thanks,
BQ

Encounter error after adding an attribute to a new dimension in AWM.

After I added an attribute to a new dimension, I encountered the error as below.
I also cannot read the metadata from Jdeveloper after I create a cube using AWM.
Please kindly help!!
BI Beans Diagnostics(v1.0.2.0) 2005/9/15
===============================================================================
JDEV_ORACLE_HOME .......................... = C:\jdev1012_base
JAVA_HOME ................................. = c:\j2sdk1.4.2_02
JDeveloper version ........................ = 10.1.2.0.0.1811
BI Beans release description .............. = BI Beans 10.1.2 Production Release
BI Beans component number ................. = 10.1.2.52.0
BI Beans internal version ................. = 3.2.1.0.13
Connect to database ....................... = Successful
JDBC driver version ....................... = 10.1.0.3.0
JDBC JAR file location .................... = C:\jdev1012_base\jdbc\lib
Database version .......................... = 10.2.0.1.0
OLAP Catalog version ...................... = 10.2.0.1.0
OLAP AW Engine version .................... = 10.2.0.1.0
OLAP API Server version ................... = 10.2.0.1.0
BI Beans Catalog version .................. = N/A; not installed in BI_TEST
OLAP API JAR file version ................. = "10.1.0.2.0"
OLAP API JAR file location ................ = C:\jdev1012_base\jdev\lib\ext
Load OLAP API metadata .................... = Successful
java.lang.NullPointerException
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.setDimAttributes(MDMMetadataDriverImpl_92.java:1733)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.getChildren(MDMMetadataDriverImpl_92.java:197)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.addChildren(MDMMetadataDriverImpl_92.java:2687)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.fillOlapObjectModel(MDMMetadataDriverImpl_92.java:2571)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92$LoadOlapObjectModel.run(MDMMetadataDriverImpl_92.java:3013)

I would post this on the OLAP forum as they should be able to help you diagnose this problem. The OLAP forum can be found at the following link:
OLAP
There is not much detail in your log, but I suspect that your OLAP mappings are incomplete or the maintenance of your dimension to load the new attribute data somehow failed. I would check the OLAP AWM build logs for more information.
Thanks
Keith
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Beans http://www.oracle.com/technology/products/bib/index.html
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Creating A new dimension for a characteristic versus adding in the same dim

Hi Guys,
I have a scenario where I have 0Material in a line item dimension in the cube.
Have to add 0Mat_plant which is compounded to 0plant as we need MRP controller
as one of the Nav attributes. 0Plant is also available in the cube.
There are two options of doing this:
1) Either add it to the 0Material dimension removing the line item property.
2) Or create a new dimension for 0MAt_plant and make it as line item dimension
considering the large volume of material information.
Which is a better option and why.
Please advise.
Many Thanks and Regards,
KAte

Hi Kate,
I'd recommend to have a new dimension as line itemdimension for 0MAT_PLANT, just for performance purposes (almost logarithmic access of data instead of full table scan)
The Plant Segments in R/3 usually have a lot more records than the general material master has (max: number of plants * number of materials).
Adding the object to 0material means that you have to unassign the line item flag. Usually this leads to increasing load- and queryruntimes.
hth
cheers
sven

Addine New Dimension In An Existing Cube

Similar Messages

Maybe you are looking for