Partitioning using a Dimension Key

Hi -
We have a dimension called Partner. We want to partition the facts for every partner using the partner dimension key. The challenge we have is that the dimension key is generated by OWB during run time, so we cannot create the partitions in the MDL. Is there any way to accomplish this?
One workaround is to use the natural key as the surrogate key? Can this be done in OWB?

Currently.... to partition the fact table by a meaningful column (for example a DATE column representing the time dimension ref) can be done with a little work with the downside that you cannot use the cube operator (and the CWM2 code is not correct either, but this is less of a priority..if you are not using it). The map to load the fact table must use the table operator and lookups performed for the dimensions using surrogate key references. This is not so bad a loss for those concerned with orphan handling with fact tables since incorporating orphan checking would result in a double lookup when using the cube operator in OWB 10.2.
To do this:
1. must add a key on the time dimension table for the DATE column.
2. can then change the datatype of the column in the fact table referencing the time dimension table to DATE.
3. then change the foreign key from the fact table to the time dimension table to use the new key on the DATE column.
4. can now sensibly partition the fact table using time periods.
5. The fact mapping will now use the fact table (rather than the cube operator) to load directly into the table.
Cheers
David

Similar Messages

Dimension key 16 missing in dimension table /BIC/DZPP_CP1P

Hi all,
I have a problem with an infocube ZPP_CP1. I am not able to delete nor load any data. It was working fine till some time back.
Below is the outcome of running RSRV check on this cube. I tried to run the error correction in RSRV. But n o use
Please help.
Dimension key 16 missing in dimension table /BIC/DZPP_CP1P
Message no. RSRV018
Diagnosis
The dimension key 16 that appears as field KEY_ZPP_CP1P in the fact table, does not appear as a value of the DIMID field in the dimensions table /BIC/DZPP_CP1P.
There are 17580 fact records that use the dimension key 16.
The facts belonging to dimension key 16 are therefore no longer connected to the master data of the characteristic in dimension.
Note that errors that are reported for the package dimension are not serious (They are thus shown as warnings (yellow) and not errors (red). When deleting transaction data requests, it can arise that the associated entries in the package dimension have already been deleted. As a result, the system terminates when deleting what can be a very large number of fact records. At the moment, we are working on a correction which will delete such data which remains after deletion of the request. Under no circumstances must you do this manually. Also note that data for request 0 cannot generally be deleted.
The test investigates whether all the facts are zero. If this is the case, the system is able to remove the inconsistency by deleting these fact records. If the error cannot be removed, the only way to re-establish a consistent status is to reconstruct the InfoCube. It may be possible for SAP to correct the inconsistency, for which you should create an error message.
Procedure
This inconsistency can occur if you use methods other than those found in BW to delete data from the SAP BW tables (for example, maintaining tables manually, using your own coding or database tools).

Hi Ansel,
There has been no changes in the cube. I am getting this problem in my QA server. So I retransported the cube again from Dev to QA. But did not help me..
Any other ideas??
Regards,
Adarsh

Load fact table with null dimension keys

Dear All,
We have OWB 10g R2 and ROLAP star schema. In our source system some rows don’t have all attributes populated with values (null value), and this empty attributes are dimension (business) keys in star schema. Is it possible to load fact table with such rows (some dimension keys are null) in the OWB mappings? We use cube operator in mappings.
Thanks And Regards
Miran

The dimension should have a row indicating UNKNOWN, this will have a business key outside of the normal range e.g. -999999.
In the mapping the missing business keys can then be NVL'd to -999999.
Cheers
Si

About Surrogate Key and Dimension Key on OWB 10.2

Hi, everyone.
I am using OWB 10.2 and I have a question about Surrogate key and Dimension Key.
I indicated the foreign key as VARCHAR2 type in Fact Table and Dimension Key as VARCHAR2 type is operated as Primary key in Dimension Table. I made Single Level in Dimension Table.
I know that Dimension Key stores the surrogate ID for dimension and is the primary key of the table. Also, Surrogate ID should be only NUMBER type.
So, in this case, Surrogate ID is NUMBER type
Dimension key should be NUMBER type to store the surrogate ID.
But, Dimension key also should operate the primary to relate Foreign key as VARCHAR2 type.
How I can solve this confusing condition?
Please let me know that.
JWS

Hi JWS,
From a SQL point of view it should not be a problem to join a NUMBER field to a VARCHAR2 field because during execution there will be an implicite cast for the NUMBER value to a VARCHAR2 value. See the example below.
SELECT * FROM DUAL
WHERE 1 = '1'From an OWB point of view it is not possible to have a Dimension with an NUMBER value Key that has a relation to a VARCHAR2 value Foreign key in a Fact table. This is caused due to the creation of a Fact table in OWB in which the Foreign keys in it are build from de Dimension tables that refer to them.
You will loose the reference to the Dimension when changing the type of the Foreign Key.
To resolve this issue I would advise you to use a Sequence that generates your Surrogate Key (NUMBER type) for the Dimension table and store it in the Primary Key Column (VARCHAR2 type).
When validating the mapping you will get a warning, but when executing this should give no problems.
Regards,
Ilona

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.

OBIEE - use of chronological Key

Hi all,
can any body explain in detail what is the use of chronological key and why we need to enable the
time dimension at time of creating a time dimension hierarchy.
Thanks
bharath

HI Bharth,
What is the chronological key use?
A. Typically time dimension differs from all other dimensions in one way and that is,
all other dimensions dont care about the order of the values in it.
e.g. in region_dim the values are north, south, west and east. Here nobody wants to see whether north comes first or south comes first. i.e. no order is required here.
in the case of time dimension there needs to be a particular order for all the values present in it.
e.g. 2010 is earliest and 2004 is older. Dec-10 is earliest and jan-10 is older. i.e. the values in the time dimensiion needs to follow a particular sorting order. So the chronological key is the key which tells the obiee that the data is incrementing based on the chronological column.
Here you may get another doubt. i.e. you are having columns like year, half_year, quarter, month, week and day. Here which one should become the chronolgocial key?
Analyse it yourself. If you kept year as chro key then obiee will be confused whether jan-10 is earliest or feb-10 is earliest. Because it knows only that 2010 is earliest and 2009 is older.
So always it should be the lowest level oif the dimension which needs to be the chronological key. In the abouve case it should be date.
You can select either date or date_id(this could be a sequence generator values).
2. what is the use time dimension?
A.If all you want is to achieve drills from Month, Quarter and Year then treat it as a normal dimension and create the levels. But if you want to do calculations like YTD, QTD and MTD then you need to create a time dimension.
http://oraclebizint.wordpress.com/2007/11/05/oracle-bi-ee-101332-understanding-todate-and-ago-achieving-ytd-qtd-and-mtd/
Refer the above link for time dimension.
Hope this help's
Thanks,
Satya

Key Bindings using the arrow keys

Following is some code that allows you to move a component around the screen using the arrow keys. I've noticed a problem and I'm just wondering if its Java or my keyboard.
Lets start with an example that works:
Press the down and right keys. Then press either the up or left key. The image moves proving that it supports 3 keys.
Now for the problem:
Press the up and left keys. Then press either the down or right key. Three things to notice:
a) the direction doesn't change when the third key is pressed
b) no output is displayed, so the ActionListener is not being invoked
c) after a short time, the program starts beeping
Now try rerunning the code after removing the comments that assign the key bindings to the "a, s, d, f" keys. Redo the above test and it works even if all four keys are pressed.
I don't remember this problem when I wrote the code a while ago, but I did recently get a cheap new keyboard so I'm just wondering if the problem is my keyboard or whether its a quirk with Java.
You can download Duke from here:
http://java.sun.com/docs/books/tutorial/uiswing/examples/components/LayeredPaneDemoProject/src/components/images/dukeWaveRed.gif
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class KeyboardNavigationProblem implements ActionListener
     private JComponent component;
     private int deltaX;
     private int deltaY;
     private Timer timer;
     private int keysPressed;
     private InputMap inputMap;
     public KeyboardNavigationProblem(JComponent component, int delay)
          this.component = component;
          this.deltaX = deltaX;
          this.deltaY = deltaY;
          timer = new Timer(delay, this);
          timer.setInitialDelay( 0 );
          inputMap = component.getInputMap(JComponent.WHEN_IN_FOCUSED_WINDOW);
     public void addAction(int keyCode, String description, int deltaX, int deltaY)
          new NavigationAction(keyCode, description, deltaX, deltaY);
     public void updateDeltaX(int delta)
          deltaX += delta;
     public void updateDeltaY(int delta)
          deltaY += delta;
     public void actionPerformed(ActionEvent e)
          int componentWidth = component.getSize().width;
          int componentHeight = component.getSize().height;
          Dimension parentSize = component.getParent().getSize();
          int parentWidth = parentSize.width;
          int parentHeight = parentSize.height;
          // Determine next X position
          int nextX = Math.max(component.getLocation().x + deltaX, 0);
          if ( nextX + componentWidth > parentWidth)
               nextX = parentWidth - componentWidth;
          // Determine next Y position
          int nextY = Math.max(component.getLocation().y + deltaY, 0);
          if ( nextY + componentHeight > parentHeight)
               nextY = parentHeight - componentHeight;
          // Move the component
          component.setLocation(nextX, nextY);
     class NavigationAction extends AbstractAction implements ActionListener
          private int deltaX;
          private int deltaY;
          private KeyStroke pressedKeyStroke;
          private boolean listeningForKeyPressed;
          public NavigationAction(int keyCode, String description, int deltaX, int deltaY)
               super(description);
               this.deltaX = deltaX;
               this.deltaY = deltaY;
               pressedKeyStroke = KeyStroke.getKeyStroke(keyCode, 0, false);
               KeyStroke releasedKeyStroke = KeyStroke.getKeyStroke(keyCode, 0, true);
               inputMap.put(pressedKeyStroke, getValue(Action.NAME));
               inputMap.put(releasedKeyStroke, getValue(Action.NAME));
               component.getActionMap().put(getValue(Action.NAME), this);
               listeningForKeyPressed = true;
          public void actionPerformed(ActionEvent e)
               if (listeningForKeyPressed)
                    updateDeltaX( deltaX );
                    updateDeltaY( deltaY );
                    inputMap.remove(pressedKeyStroke);
                    listeningForKeyPressed = false;
                       if (keysPressed == 0)
                            timer.start();
                 keysPressed++;
               else // listening for key released
                    updateDeltaX( -deltaX );
                    updateDeltaY( -deltaY );
                    inputMap.put(pressedKeyStroke, getValue(Action.NAME));
                    listeningForKeyPressed = true;
                    keysPressed--;
                       if (keysPressed == 0)
                            timer.stop();
               System.out.println(KeyboardNavigationProblem.this.deltaX + " : "
               + KeyboardNavigationProblem.this.deltaY);
     public static void main(String[] args)
          JPanel contentPane = new JPanel();
          contentPane.setLayout( null );
          JLabel duke = new JLabel( new ImageIcon("dukewavered.gif") );
          duke.setSize( duke.getPreferredSize() );
          duke.setLocation(100, 100);
          contentPane.add( duke );
          KeyboardNavigationProblem navigation = new KeyboardNavigationProblem(duke, 100);
          navigation.addAction(KeyEvent.VK_LEFT, "zLeft", -5, 0);
          navigation.addAction(KeyEvent.VK_RIGHT, "zRight", 5, 0);
          navigation.addAction(KeyEvent.VK_UP, "zUp", 0, -5);
          navigation.addAction(KeyEvent.VK_DOWN, "zDown", 0, 5);
//          navigation.addAction(KeyEvent.VK_A, "zLeft", -5, 0);
//          navigation.addAction(KeyEvent.VK_S, "zRight", 5, 0);
//          navigation.addAction(KeyEvent.VK_D, "zUp", 0, -5);
//          navigation.addAction(KeyEvent.VK_F, "zDown", 0, 5);
          JFrame frame = new JFrame();
          frame.setDefaultCloseOperation( JFrame.EXIT_ON_CLOSE );
          frame.setContentPane( contentPane);
          frame.setSize(800, 600);
          frame.setLocationRelativeTo( null );
          frame.setVisible(true);
}

if you hold down left and right (so it doesn't move), down works, but not up.
hold up/down, right works but not left.Yes, the problem only seems to be when the up and left in combination with the right or down key is pressed.
num lock off - use the number pad arrow keys and all works OK Thats interesting, I didn't notice that. Although it just confuses the issue as to what the problem is.
So it appears to me that:
a) left + up + down, and
b) left + up + right
are special key combinations that are intercepted by either the OS or the JVM. Do these key combinations ring a bell to anybody?
I'm use JDK1.4.2 on XP. I wonder if other OS will have the same problem?
Again, this isn't a real, problem, just more of a curiosity. Thanks,

Use of Dimensions in APO DP Planning Object Structures

In APO DP Planning Objct Structures, I know that it's possible to assign Dimensions to characteristics.
The standard help documentation suggests this is 'to improve performance'.
Can anyone give practical guidance about how to assign Dimensions to improve performance?
Thanks,
Bob Austin

the characterisitcs are grouped logically using the Dimensions
the use of dimensions allows data to be stored in a combination of dimension tables and fact tables
the dimention table consists of the dimension number, a primary key characteristics you assign to the dimension
the primary keys from various dimension tables link up at the fact table and to the values stored in it
so you can think of a star schema of tables with the dimension acting as the link
so when you look for a particular value the dimension table is first quesried based on which the fact table the primary key is linked to is looked up
in order to improve performance, make sure you dont assign too many characterisitics to one dimension
try to logically group the characterisitics - geography for eg can be made of state, region (not material type)
you can also try to match the dimension with the selections you will be using in the planning book,
dimension tables could grow as your characteristic values increase so SAP advices you keep an eye on it (i am not sure of how functionally you can help this but i believe basis will be able to help you with allocating space on an oversized table)
there is a document somewhere in sap marketplace that i am not able to find a link... hopefully someone will link it up here

Using time dimension in materialized view

Do anybody has an example of using Time dimension in MVIEW?. The time tablke has no relation with oder object (ex. i will join the time table with sales table, which has no relation with each other.
Thanks in advance
Mehdi

Hi
Check the foreign key on the fact table to see how it is related to the time dimension table.
Cheers
David

I need to use the 'Ins' key for reverting x,y & z axis co-ords

Apple selling X3: The Return. However the problem is that the navigational command 'go to' will only take you to x and z coordinates, the pc users then use the 'Ins' key to flip to y axis for the third dimension navigation point. I have tried looking at keyboard mapping but the new aluminium iMac keyboard is an 'Function Key' nightmare compared to earlier version. Any brave soul wishing to answer this one.

Have to wait for Admin to delete these duplicate message. Sorry peeps!

Error in Restoring the HDD partition using BootCamp assist

This is regarding error in restoring the HDD partition using BootCamp assist. Yesterday I was trying to instal Windows 8.1 Pro on my Mac Mini.
Started had installing windows software using Boot Camp assist using the USB flash drive
Took the back of Windows Support software from Apple store
Did the HDD partitioning for Windows,
Then went ahead to install the windows and automatically machine restarted.
After few minutes started installing Windows... and stuck for more than 3hrs at by displaying the blue screen of Windows installation... and inactive
I had restarted the using start button, and finally I could not able to install Windows.
Then I got black screen with message ' No boot disk, please insert boot the disk and press any key to restart'
I have restarted using start button by holding 'Alt' key
Finally I could able to started machine with OS X
Now I wanted to remove the partition created above, using Boot Camp assist, but it is not able to do it. There is error message ' Error while restoring the hard disk'
Any help, how to remove this partitioning? Also in every restart I need to hold 'Alt' key to boot the machine with OS X.
-Narsimloo Begari

if you've tried and cannot remove the partition with boot camp assistant, you'll have to open disk utility and reformat the partition there - choose mac journaled and then try to combine this partition back into your existing Mac partition

Using a dimension twice

Hi,
I have a fact table which is using one dimension twice (dimension location "from" and "to"). I have problems with the discoverer working on it.
When using the dimension in a matrix report, discoverer is asking which of the two foreign key constraints it should use. Using both is not a good idea, because it forces "from" and "to" to be equal. Using just one workings fine.
I tried to copy the dimension to a new folder and using the other foreign key constraint there, but then the selection of the "to" location depends of the "from" location showing me just the target locations for the selected source. Choosing the "to" location first, I don't have that dependency on the "from" location.
Is there a way to select both dimension "from" and "to" independend?
Regards,
Torsten

LS,
Another alternative is to create 2 views on your location table, for instance v_location_from and v_location_to, and import these into the Business Area instead of the location table itself.
Then in your disco-report you will have 2 different folders to refer to and no longer have a problem with FK's, even if on the database you are accessing the same object more than once.
You could even make a distinction in the view code if it is really a large table, select only from-locations for your from-view and the same for the to-view (if it is possible to make this distinction in the first place, of course).
Hope this helps.
Cheers, Patrick

Want binary_float dimension key

Hi,
I would like to set up a star schema with binary_float dimension keys to make them much smaller than the numeric datatype. When I do, I get validation warnings in the dimensions built in OWB. Can I ignore the warnings and use the smaller binary_float datatypes or am I setting myself up for trouble later in the project. We are running Oracle 10G 10.2.0.4 on HP Unix. We have OLAP installed but I am deploying dimensions and cubes with the "Deploy Data Objects Only" option because of all of the bugs in OWB. The fact table has about 110 million rows and about 100 gig.
Has anyone used OWB with a star schema that uses binary_float surrogate keys?
Thanks
Don K.

I am using the dimension operator in the map that loads the dimension and it seems to create the surrogate key correctly for new rows and merge the data for existing rows. I am have all of the dimensions set to Type 1. For the fact table map, I could not get the dimension objects to work correctly so I am using lookups into the dimension tables to get the surrogate keys. When I tried to use the dimension objects in the lookups it keeps adding an extra column with "_1" for the dimension key. It works correctly when I do the lookup using the dimension table. It seems like everything works okay. I am just worried about the warning message and wondering why OWB forces a number datatype when a float is much smaller.
Thanks
Don

BPC Office Client : No data retrieval when using static dimensions

Hello,
We have used static dimensions to build reports / input schedules, but the data range remains empty when refreshing the workbook after the column - and row key ranges have been filled. There is definitely data in the application for the combination of the current view members and range members chosen. I have put 3 dimensions in the row key range and 4 dimensions in the column key range.
What are the common solutions for this problem ? I don't receive any errors while refreshing the workbook.

Have you checked security member access profiles to know that the user has access to that slice of data?
You might also double-check your data in BW by running the Shared Query Engine test program UJQ_SQE_TEST from transaction SA38 or SE38. Just select your AppSet and Application, along with matching in the filters the static members you've set in your report.
If you still have issue, try to replicate the issue with a delivered template report and confirm no data is shown.
Otherwise, please create a customer [message|http://service.sap.com/message] in the SAP Service Marketplace and report your issue as a potential bug. To expedite a solution it would be helpful if you detail the steps exactly for the Support team to recreate, verify and troubleshoot the problem.
Best regards,
[Jeffrey Holdeman|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/jeffrey+holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

Allowing parallel processing of cube partitions using OWB mapping

Hi All,
Iam using an OWB mapping to load a MOLAP cube partitioned on TIME dimension. I configured the OWB mapping by checking the 'Allow parallel processing' option with the no.of parallel jobs to be 2. I then deployed the mapping.The data loaded using the mapping is spread across multiple partitions.
The server has 4 CPU's and 6 GB RAM.
But, when i kick off the mapping, i can see only one partition being processed at a time in the XML_LOAD_LOG.
If i process the same cube in AWM, using parallel processing, i can see that multiple partitions are processed.
Could you pls suggest if i missed any setting on OWB side.
Thanks
Chakri

Hi,
I have assigned the OLAP_DBA to the user under which the OWB map is running and the job started off.
But, it failed soon with the below error:
***Error Occured in __XML_MAIN_LOADER: Failed to Build(Refresh) XPRO_OLAP_NON_AGG.OLAP_NON_AGG Analytic Workspace. In __XML_VAL_MEASMAPS: In __XML_VAL_MEASMAPS_VAR: Error Validating Measure Mappings. In __XML_FND_PRT_TO_LOAD: In __XML_SET_LOAD_STATUS: In ___XML_LOAD_TEMPPRG:
Here is the log :
Load ID     Record ID     AW     Date     Actual Time     Message Time     Message
3973     13     SYS.AWXML     12/1/2008 8:26     8:12:51     8:26:51     ***Error Occured in __XML_MAIN_LOADER: Failed to Build(Refresh) XPRO_OLAP_NON_AGG.OLAP_NON_AGG Analytic Workspace. In __XML_VAL_MEASMAPS: In __XML_VAL_MEASMAPS_VAR: Error Validating Measure Mappings. In __XML_FND_PRT_TO_LOAD: In __XML_SET_LOAD_STATUS: In ___XML_LOAD_TEMPPRG:
3973     12     XPRO_OLAP_NON_AGG.OLAP_NON_AGG     12/1/2008 8:19     8:12:57     8:19:57     Attached AW XPRO_OLAP_NON_AGG.OLAP_NON_AGG in RW Mode.
3973     11     SYS.AWXML     12/1/2008 8:19     8:12:56     8:19:56     Started Build(Refresh) of XPRO_OLAP_NON_AGG.OLAP_NON_AGG Analytic Workspace.
3973     1     XPRO_OLAP_NON_AGG.OLAP_NON_AGG     12/1/2008 8:19     8:12:55     8:19:55     Job# AWXML$_3973 to Build(Refresh) Analytic Workspace XPRO_OLAP_NON_AGG.OLAP_NON_AGG Submitted to the Queue.
Iam using AWM (10.2.0.3 A with OLAP Patch A) and OWB (10.2.0.3).
Can anyone suggest why the job failed this time ?
Regards
Chakri

Partitioning using a Dimension Key

Similar Messages

Maybe you are looking for