Storing degenerate dimension info in an OWB 10gR2 cube

Hi,
I'm looking to store "degenerate dimension" information in an OWB 10gR2 cube. Typically in a DW, I'd just add a column to the fact table to hold the information. However, in OWB 10gR2, I don't see any way to add a column to a "cube" object - everything appears to either have to be a dimension surrogate key, or a measure.
Not sure the best way to proceed. We've coded all our ETL using the standard cube objects and letting OWB do all the surrogate key lookup, etc. automagically for us, so I'd hate to be forced to go back to manually loading the fact tables. Is there an easier way?
Thanks,
Scott

Hi Scott,
The problems I've run into with dimensions and cubes are:
Dimensions abort if there are many roles - about 4 is the limit. This is very bad for the time dimension which should have 100s of aliases. Unfortunately I can't use the Time dimension wizard because we require ISO-Weeks. My workaround is to create several Time dimensions manually and assign 4 roles to each.
Naming - when I create several time dimensions with 4 roles each (see above), in the BI layer, the foreign keys in cubes are always named something like time_dim, time_dim_1, etc rather than named for role names. I have to manually rename them in tables and then when I deploy BI objects, manually rename them again in Discoverer Administrator.
Redeploying just about anything is broken. Table upgrade plans are invalid (even after running the grant scripts that support recommended), Redeploying BI objects runs successfully but if you read the job output, it does nothing since the objects already exist - again, the upgrade option does nothing.
Column ordering is random when deploying objects so I've taken to sorting alphabetically for our BI objects. Not ideal by any means.
As for the time savings with lookups, I don't save nearly that much. Due to many composite keys in our source systems, I assign surrogate keys in our staging area. These become the "business keys" in our DW layer and consequently I end up doing lookups against the staging MAP tables - really no more or less difficult than looking up dimension keys. That is more a design choice than anything and may just be my "Kimball" habits dying hard.
I'm encouraged to hear that you are having success. I chose to utilize the Dimensions and Cubes and so far am sticking with it. I'm hoping that there will be patches and/or point releases to OWB soon!

Similar Messages

  • Degenerate dimensions

    Hello friends ,
    I need some clarifications regarding the creations of the Degenerate Dimension(fact generated ) Creations in a Cube .
    1. How many degenerate dimensions can we create on a SSAS Cube .What is the possible limit . can we have more than 150  degenerate dimensions in a SSAS Cube ..?
    2. What are the drawbacks/disadvantages of a De Generate dimensions.?
    3. if the degenerate dimensions is followed . what will be affect on the calculations  as well performance wise.
    Please help in these 2 points

    Hi Rakesh,
         Degenerate dimensions have same granularity as Fact Table. To be simple these types of dimensions are used to display the textual information to the client that resides in the Fact tables. This explains that getting any sort of information
    from these dimensions (Browsing) is painfully slow.It is recommended to hide these dimensions from user and only use it in actions- Drillthrough (Or other). I am able to create only one Degenerate dimension per measure group.
    Regards,
    Venkata
    Venkata Koppula

  • OWB 10gR2 - some enhancement requests

    Hi, I've been working with OWB 10gR2 for approximately a week now, and I've come across a few (minor) bugs, as well as a list of enhancements that I think would make the tool better. I'd like to surface these in this forum so they can be either disagreed with or have workarounds suggested, as well as getting this list in front of Oracle. Also I'm new to the tool, so maybe there are ways to accomplish what I want.
    p.s. as a side note - please don't take these as criticisms of the tool. I'm actually very impressed with OWB 10gR2, but just want to surface some ideas that I think would make the tool better.
    Thanks,
    Scott
    ---Bugs:
    1.     If I enter a quote character in one of the business description fields (i.e. for a cube or dimension), it causes the DDL scripts to blow up. It probably mentions the list of valid characters in the users guide somewhere - but if a character isn't legal, it should be flagged when I try to enter it originally – not when deploying
    2.     I can enter illegal strings in an expression operator that fail validation there, but the whole map still passes validation. For instance, I put in an expression (for a varchar2 field) using a single quote at the start, but mistakenly with a double quote at the end. I didn’t bother to validate this within the expression. The whole map validated fine, but (of course) blew up with the illegal syntax when generating the code.
    3.     I get the following error when trying to browse a cube (ROLAP, not MOLAP) through OWB, but I'm able to pull the cube up fine using either the excel add-in or biBeans: CubeDV_OLAPSchemaConnectionException_ENT_06952???
    ---Enhancement Requests:
    1.     Add a “deploy” button in control center next to the to “default actions” and “reset actions” buttons
    2.     Allow an option to have dimensions and cube defaults set to either “deploy all”, “deploy data only”, “deploy catalog only”, “deploy aggregations” (for cubes). Also, why is the default set to “deploy data only”? Does deploying the CMW2 metadata involve huge performance impacts or something? It seems like the CMW2 is almost “free” – so it should be turned on by default. Its a pain to use the dimension wizard, but then have to go in to each dimension afterwards to set this option.
    3.     When using “configure” on dims and cubes in control center, the first time the “configuration properties” dialog pops up, everything is fine. However, when you try to configure the 2nd object, the “background focus” switches from control center back to design center. This makes navigation very slow if you have lots of items to change. I've noticed this behavior in a few other places as well.
    4.     Some dialogs do not have maximize buttons (i.e. dimension wizard dialogs), and default to a very small size. It is possible to have size of dialogs dynamically scaled to screen resolutions, and attempt to size columns so they fit properly. Or better yet, have each dialog remember how large it was last time, and automatically open up to that size?
    5.     When generating the “autobind” relational table while creating a dimension, it seems to be “randomizing” the order of the attributes within a level (although it does sort the “top level” attributes first, followed by lower level attributes), at least when using the dimension wizard. It would be nice if the attributes in the relational table came out sorted in the same order as they are specified in the attributes tab.
    6.     When using a “unmapped” display set– there doesn’t seem to be a way to refresh the set (i.e. remove the items that have since been mapped) unless you select “all” and then “unmapped” again. Would be nice if you could simply choose “unmapped” again and have it refresh the object
    7.     While doing a mapping, right click on canvas allows option to “generate”. Would be nice to also add the “validate” option to this menu
    8.     Validating mappings takes a decent amount of time – would be nice if a “busy” icon was displayed to let user know that OWB hasn’t locked up.
    9.     default size of “job details” dialog is too small, and even if I maximize I still have to go through and manually adjust the size of each pane. Similar to enhancement #4
    10.     Horizontal size of operators in mapping seems to be determined by the length of the operator name, instead of tying directly to the icon. Looks strange. Very minor
    11.     When displaying dimension objects in a mapping:
    a.     For the “surrogate key” columns – add an icon to indicate this attribute is a surrogate key. Likewise, since its not legal to map anything to this column, remove the little “arrow” next to it (the one that turns gray when something is mapped to a column), or perhaps don't even show this column at all.
    b.     For the “business key” columns – add some type of icon to show which attributes represent the business natural key (or make color different, etc.)
    12.     Similar to #11, for the cube operator in a mapping:
    a.     For the “surrogate key” columns – if they can’t be mapped to, then don’t show them
    b.     For the “business key” columns – add some type of icon to show which attributes represent the business natural key
    c.     Separate the “measure” columns from the dimension columns
    13.     For the “Aggregation” operator – can you move the “<None>” default operator to the top of the list. At the bottom, it means you always have to scroll to use the most common operations (which are at the top of the list), i.e. sum and avg, etc.
    14.     In the log on prompt, if I choose SQL*Net connection, every time I start it up it defaults to the details being shown (even when I chose no detail last time), with cursor in the “host” box. I should be able to have the details hidden, and this dialog should ALWAYS default to having the active cursor in the password box on startup
    15.     When printing in a mapping, the “page setup” print dialog is very slow. Also, the “print setup” dialog shows margins, but you can’t adjust them. It would be nice if this could be changed here
    16.     Add a “print preview” icon to all of the toolbars. Printer icon is there, print preview should also be.
    17.     In the dimension attributes, we need a way to tag an attribute as being the “insert record” date or the “update record” date. The corresponding MERGE SQL should be updated to use these attributes.
    18.     It would be nice if the mapping canvas defaulted to an unlimited size…i.e. when I want to add new operators and the screen is already full, I either need to shrink the zoom factor down to the point where I can’t read the icons anymore, or I have to pick up the new operator and “drag” at the bottom / right side until it scrolls enough to drop it where I want. If the canvas had an unlimited size, I could simple use the scroll bars to scroll to where I want.
    19.     Scroll wheel functionality to zoom in / out (and have it zoom in around the currently selected object)
    20.     Option to have operations automatically resize when longer attribute names are added to them (can workaround by mimimizing and then maximizing, but would be better to have the operators automatically adjust size to fit)
    21.     Ability to sort output attributes in an operator (just like table column sort functionality). If I create a new operator, it would be nice to group it with related operators instead of always having it at bottom.
    22.     re: column sort functionality – drag and drop instead of up/down arrows would be nice
    23.     It would be nice if, when adding output attributes to (for example) the expression operator, it would choose the default data type the same way the dimension attribute wizard works (i.e. if it sees “ind” in name, automatically choose char(1)
    24.     Change the “zoom in” button so that it zooms in on the currently selected operator – i.e. if I click on a particular table and then hit the zoom in button, it should keep the table I selected centered
    25.     When in a mapping, clicking on a line should highlight the attributes on both the source and target operators (to allow easier visual ID of where data is coming from / going to)
    26.     AWM has a feature where table attributes can be sorted so that mappings between them don't have "crossed" lines. Similar functionality in OWB would be very appreciated. It may be harder to automate this, but even manual drag and drop of attributes within an operator would be nice.

    if you could copy/paste this whole thing into the submission form (see feedback option under the numbers menu). The more people that request these features, the more likely we are to see them in an update or the next version.
    Jason

  • Error When Loading a Degenerate Dimension

    Hi,
    I have received the link > http://blogs.oracle.com/warehousebuilder/entry/owb_11gr2_degenerate_dimensions#comments
    from you to create a degenerate dimesion .
    I have create a DIM_DD_LOAN with two attribue loan_no_business with idenitifier business and a description then I deploy the table related to this dim is called DIL_DD_LOAN_TAB but I got this error
    ORA-37162: OLAP error
    XOQ-02102: cannot find object "BANK_STG.DIM_DD_LOAN"
    XOQ-02106: invalid property "Dimension" with value "BANK_STG.DIM_DD_LOAN" for object "BANK_STG.CUBE_PAID_LOAN.DIM_DD_LOAN" in XML document
    XOQ-02106: invalid property "ConsistentSolve" with value "SOLVE ( SUM OVER DIM_BANKS HIERARCHIES (STANDARD), SUM OVER DIM_BRANCHES HIERARCHIES (STANDARD), SUM OVER DIM_CUSTOMERS HIERARCHIES (STANDARD), SUM OVER DIM_REQUESTS HIERARCHIES (STANDARD), SUM OVER DIM_CURRENCIES HIERARCHIES (STANDARD), SUM OVER DIM_BONDS HIERARCHIES (STANDARD), SUM OVER DIM_COLLATERALLS HIERARCHIES (STANDARD), SUM OVER DIM_CONTRACTS HIERARCHIES (STANDARD), SUM OVER DIM_OWNERSHIPS HIERARCHIES (STANDARD), SUM OVER DIM_SEGMENTS HIERARCHIES (STANDARD), SUM OVER DIM_USAGE_CODES HIERARCHIES (STANDARD), SUM OVER DIM_LOAN_DIVISIONS HIERARCHIES (STANDARD), SUM OVER DIM_LOAN_PURPOSES HIERARCHIES (STANDARD), SUM OVER DIM_NOMINALS HIERARCHIES (STANDARD), SUM OVER DIM_LOCATIONS HIERARCHIES (STANDARD), SUM OVER DIM_DATES HIERARCHIES (STANDARD), SUM OVER DIM_DD_LOAN)" for object "BANK_STG.CUBE_PAID_LOAN" in XML document
    XOQ-02005: The Dimension "BANK_STG.DIM_DD_LOAN" referenced from object "BANK_STG.CUBE_PAID_LOAN" is not found.
    XOQ-02100: cannot parse server XML string
    ORA-06512: at "SYS.DBMS_CUBE", line 433
    ORA-06512: at "SYS.DBMS_CUBE", line 465
    ORA-06512: at "SYS.DBMS_CUBE", line 523
    ORA-06512: at "SYS.DBMS_CUBE", line 486
    ORA-06512: at "SYS.DBMS_CUBE", line 475
    ORA-06512: at "BANK_STG.OWB$XMLCLOB_TAT_BANK_STG_DW", line 513
    ORA-06512: at line 3
    can you help me??
    REgards,
    Sahar

    The degenerate dimension best practice I mention in the blog will not work for cube MVs, the cube MV will expect a dimension defined in the AW for any dimension defined in the cube. So if you followed the blog post to the word, you did not deploy the dimension so when the cube is deployed it is looking for the dimension object (which does not exist). If you did deploy it, then you would have to maintain the dimension...and it would not be degenerate.

  • Loading a degenerate dimension

    Hi,
    I have source data which is used to load both a SCD2 dimension and fact table. Since, the dimension is derived from the fact data and is not a measure we can call it as a degenerate dimension.
    Ex:
    Source Row -- A,B,C,D,E
    Fact data - A,B,C
    Degenerate dimension data - D,E
    I have to load the SCD2 degenerate dimension with D,E and maintain the dimension surrogate in Fact table.
    So,
    Degenerate dimension - 111,D,E
    Fact - 201 ,A,B,C,111
    111 is the dimension surrogate
    201 is the fact sequence no.
    How do i identify A,B,C,D,E belong to a single row in the source data , so that i can maintain the dimension surrogate key with Fact records.
    Is there a way OWB 10g R2 can handle this, or we have to join the dimension row with the source row based on D,E and get 111,A,B,C as output.
    Any suggestion or document on how to load a degenerate dimension and fact would be highly appreciated ?
    Thanks and Regards,
    Chakri

    Hi Chakri
    Which version are you using? With pre 11gR2 you will probably have to load the cube using the (fact) table operator rather than the cube operator.
    Cheers
    David

  • OWB 10gR2 License

    Hi All,
    We have installed the Oracle 10g2 enterprise database which has core ETL features for OWB 10gR2. We have not purchased the ETL option for OWB. Can we use Dimesions and Cubes as target table ?? Are Cubes and Dimensions only available with ETL option purchase ??
    Thanks,
    Sam.

    What are you doing with a dimension when you can only specify SCD1. nothing
    To me it's a joke that Oracle says that it's possible to use dimensions when you need the ETL option to be able to use SCD2. Most dimension's I have seen the last years have been defined as SCD2 and not SCD1. So what does it help to define a dimension if you can't use it afterwards in the mappings.
    Message was edited by:
    Maurice Muller

  • OWB 10gR2: How to disable not licensed features/options

    Hi,
    Is it possible in OWB 10gR2 to disable the features of the "Oracle Warehouse Builder Data Quality Option" and "Oracle Warehouse Builder Enterprise ETL Option"?
    If no is there any other way to prevent developers of using not licensed features/options?
    Regards
    Maurice

    Hi Borkur,
    An additional problem related to these options is that there are not explained at all in the user documentation. So as you say it's not easy at all to know for a developer which features he can use.
    For example it's still not clear for me, didn't get any feedback from Oracle Sales, if it is allowed to define a dimension without any licensing.
    Also I think that's a shame that Oracle Sales defines a new licensing model (for product which was already delayed by over 18 months) once the product has been developed. If Sales would have defined the new licensing a the begging of the development it would have been possible to implement it so that you can disable these features and also they would have documented it in the user/installation manuals.
    Maurice

  • OWB 10gR2 "Experts" - does documentation exist?

    Do any sources of information on OWB 10gR2 experts exist anywhere? The users guide has almost nothing about them, and the API / scripting reference doesn't mention them. I'm specifically looking on how to write experts to streamline tasks such as copying expression operators from one map to another.
    There seems to be a huge amount of power in these, but without docs we really won't be able to harnass it.
    Any help is appreciated!!!
    Thx,
    Scott

    Hi Scott.
    Hummm.... I've tried google (owb+experts), found some info in:
    http://www.nicholasgoodman.com/bt/blog/2004/11/17/owb10g-paris-experts/
    It's not a technical resource, though.
    Regards,
    Marcos

  • Logical Key for Degenerate Dimension

    Hi Gurus,
    Need some help on the degenerate dimensions in the BMM layer.
    I have one fact table with dimension attributes and I would like to move the attributes into separate logical table and treat it as dimension.
    Now my newly created dimension has the Fact LTS and I would like to assign a logical key to the newly created table and then create the logical dimension.
    Can anyone provide some inputs on we can assign the logical key to the column?
    Thanks

    Hi Srini,
    Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
    So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
    Please let me know if I am not clear.
    Thanks

  • Unable to use XML functions in OWB 10gR2.

    Hi,
    I am trying to use XMLELEMENT ,XMLATTRIBUTES and XMLFOREST function for loading into a XML file using OWB 10Gr2.
    During deployment it is erroring out with an error 'identifier 'XMLELEMENT' must be declared'.
    Please suggest some workaround or possible reason for this problem.
    Reagrds,
    PHD
    Edited by: user1662077 on May 21, 2009 5:17 AM

    Hi Navneet,
    I have followed these steps,But beyond that there is some thing which we want to achive.
    We want the xml file to have a proper format like
    "<?xml version="1.0" encoding="UTF-8"?>
    <Header recTyp ='01' RTA='IN200200' ISIN='IN2000020220' recDate ='20090202' stmtDate='20090202' stmtTime='232020'
    totNSDLPos='100' totTrnstPos='0' TotUnlckPos='10' TotLckPos='100' totPldgPos='0' totFrzPos='9' totIdtPos='9'
    NSDLTotFrzPos='1' totDtlRec='2'/>
    <Details recTyp='02' dpId='IN300118'>
    <BenDtl benAcctNum='12345678' type='01' subtype='02' status='01'>
    <FirstHldr name='op' fatherName='' PAN='HUFSOSFNKS'>
    <Address type='1' pinCode='400097' phoneNum='28490520' faxNum='9999999999'>
    <Part type='1'>
    </Part>
    <Part type='2'>
    </Part>
    <Part type='3'>
    </Part>
    <Part type='4'>
    </Part>
    </Address>
    </FirstHldr>.........."
    On the oracle blogs it was suggested that this can be achived by using XML function in the expression operator.
    But while using them,OWB is not recongnising these XML function.
    Regards,
    PHD

  • OWB 10gR2 : How to configure ctl and log locations for Sql*Loader mappings?

    Hi all,
    I'm using OWB 10gR2 to load data in tables with Sql*Loader mappings.
    In my project I have a datafile module and an Oracle module.
    When creating an sql*loader mapping in the oracle module, there is two properties for this mappings that I want to modify. The first is Control File Location and the second is Log File Location. Values for those properties are equal to the data file module location. When trying to change those values I can only chose "Use module configuration location".
    Somebody knows how to configure those properties with different locations as the one of the flat file module?
    What I want to do is to store the data file in one directory, and control file and log file in other directories.
    Thank you for your help.
    Bernard

    Hi,
    You're right, my problem is that the dropdown only show the location associated with the flat file location even if I have other file locations created in the design repository.
    The good news is that I have found the solution to solve the problem :
    1) Edit the file module and in tab "Data locations", add the locations you want to use for control file and log file.
    2) Open configuration window of the mapping and then the dropdown for properties Control File Location and Log File Location show new locations
    I have tested my mapping after changing those properties and it's working.
    Bernard

  • SQL08 Need example of creating AND using a Fact (degenerate) dimension

    Can someone post a link to some examples of setting up and using a Fact (degenerate) dimension.  Ive got the SSAS 2008R2 Adventureworks DW project setup and I see a few Fact dimensions in there, but id like some descriptions to go along with this or
    something similar.
    My scenario:
    Orders - attributes include :  Order#, OrderStartDate, SalesPerson, BusinessType, MarketType
    OrderTransactions - attributes include:  OrderKey , TransactionAmount, TransactionType, TransactionDate, AccountKey
    Description:
    Its more or less the typical Order > Order Detail type scenario, with the addition of Orders have some additional attributes.
    So I want to be able to measure on for example:
    Order counts - broken down by BusinessType and MarketType , and then within a date range
    Revenue - which will be totals of transaction amounts, again grouped by BusinessType and MarketType, but also be able to drill down to see the related Order#

    Hi Shiftbit,
    According to your description, you need some examples about create and use degenerate dimensions, right?
    Degenerate dimensions, also called fact dimensions, are standard dimensions that are constructed from attribute columns in fact tables instead of from attribute columns in dimension tables. Here is document that describes how to create and use degenerate
    dimensions step by step, please refer to the links below.
    https://msdn.microsoft.com/en-us/library/ms167409(v=sql.100).aspx
    http://www.jamesserra.com/archive/2011/11/degenerate-dimensions/
    Regards,
    Charlie Liao
    TechNet Community Support

  • Reporting on Degenerate Dimension without using aggregation

    Hi Gurus,
    I have 2 fact tables F1 and F2 and a conformed dimension D. Both the fact tables contains degenerate dimensions.
    So I have created degenerated dimesnion in BMM layer DDF1 and DDF2 corresponding to F1 and F2 resp.
    I want to generate report using DDF1, DDF2 and D without using any column from F1 or F2(basically I dont need any aggregation in my reports, but more than 1 fact table is used).
    But I receive error while trying to implement this. I have created the dimensions and defined content mappings for the fact tables.
    I had followed the steps given at [http://www.rittmanmead.com/2010/01/oracle-bi-ee-10-1-3-4-1-modeling-degenerate-dimensions-fact-attributes/]
    Does this type of reporting without using aggregation possible in OBIEE?
    Thanks in advance.

    If you want it in pivot view it is not possible for ad-hoc to give it to end-users without measure columns.
    You can do this in table view for only dimension columns wihtout measures easily possible.
    If you want the look of pivot and same as results of pivot in your table view then you follow this blog
    http://gerardnico.com/wiki/dat/obiee/table_to_pivot
    UPDATE POST
    the rittman blog mentioned follow that properly every step is given correctly,according to me your doing mistake at degenerate dimensions or conformed dimensions...that is why the error is throwing on the fact column that you are using.Please setup once again each and every step correctly you will achieve it.
    Cheers,
    KK
    Edited by: Kranthi on Feb 8, 2011 3:06 AM

  • Oracle11g degenerate dimension usage

    HI,
    The context of my sales cube is as follows,
    Dimensions: product,region,time
    Degenerate dimension: order_number (which is huge list)
    Measure: amount,quantity
    Using oracle11g analytic workspace manager, I can create the dimension, measure and cube.
    Will somebody please guide me to configure order_number dimension as degenerate dimension. This would be the dimension which reside in fact with no mapping to source and no aggregates across this dimension.
    I should be able get results for queries like, " List all the order numbers for the product A under Region B and where quantity sold > 100K"
    Plz ask for any clarifications..
    Thanks in advance,
    -- Vinay

    Hi,
    Refer this link:
    http://books.google.co.in/books?id=VEGxVL2L0K0C&pg=PT62&lpg=PT62&dq=WhatisDegenerateDimensionandslowlychangingdimensionin+BW&source=bl&ots=1CyWv5TSRG&sig=07JISYkbaHUTSwmz4DH8tiH5HUE&hl=en&ei=9WYvS9fHG4-gkQWmkdCCBA&sa=X&oi=book_result&ct=result&resnum=9&ved=0CCEQ6AEwCA#v=onepage&q=What%20is%20Degenerate%20Dimension%20and%20slowly%20changing%20dimension%20in%20BW&f=false
    It gives the contents of the book SAP BW certification: a business information warehouse study guide By Catherine M. Roze.
    The contents give you an idea of all the types of dimensions like :
    Degenerate
    Partitioning
    Categorical
    Slowly changing
    Reserved
    Hope this helps.
    Thanks,
    Rahul

  • Degenerate Dimension

    While performing modeling in BMM layer I am hitting an issue.
    I have two fact tables Revenue and Charges. Both has Sales Order Number as common column (Sales Order Number) is available in both the fact tables.
    Now I want to create a report across both the fact tables.
    The approach I am taking is to first create common degenerate dimension from both the fact tables (Sales order Number column is mapped to both the fact tables.
    But when I try to create a dimension hierarchy by right clicking on degenerate dimension it throws an error saying 'AdminTool is unable to created a structure for dimension'. I believe this is because Sales Order Number is not unique in any of the fact tables.
    Desired model should be able to use Sales Order Number across both fact tables.
    Thank you,
    DP.
    Edited by: BIDeveloper on Nov 22, 2010 4:53 PM

    DP,
    As you mentioned "Sales Order Number" as degenerate dimension it is confined to a fact table (a standard definition).
    Thus dimensional hierarchy cannot be created on facts.
    Mandatory conditions for creating a dimensional hierarchy:
    1. The logical table cannot be a logical fact table.
    2. The logical table on which a dimensional hierarchy is bieng created should not have a hierarchy already created.
    mark posts promptly.
    J
    -bifacts
    http://www.obinotes.com

Maybe you are looking for