Parent member values in Fact tables

Hello,
I want to understand something, as far as I know, we can only send data to base level members, right ?
Then how come we find rows of data that have parent member values in the Fact tables ? (assuming we do not play manually with the database of course), I thought that this can be due to an import with the data manager, can this be right ?

nilanjan chatterjee wrote:
Hi,
>
> The data for the parent members should be available in the SQL tables.
> For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
>
> Hope this helps.
I guess you meant should not, right ?

Similar Messages

  • Multiple fact tables, aggregation and model problems

    Hi,
    I am developing a OLAP Application with 2 dimensions (product,location) and a few measures (sales_qty, sales_value, sale_price, cost_price, promotion_price, average_market_price, etc). I also have a BiBean Crosstab to explore the data.
    I'm having the following problems:
    - The measures are in different fact tables.
    When using cwm2_olap_table_map.Map_FactTbl_Measure, I can only map the measures from the first fact table, the others return "Exact fetch returns more than the request number of rows".
    - The 'price_' measures shouldn't aggregate to higher levels of the dimension hierarchies. I have changed the default aggregation plan, but in the crosstab data is still shown in the higher levels. Is there any way to show N/A in levels that I don't want to aggregate?
    - How can I add a calculated field that is the result of a complex set of business rules (with IF/THEN/ELSE statements and calls to existing oracle functions) and precalculate it during batch?
    Thanks,
    Ricardo

    Keith, thanks for the quick answer!
    Some questions regarding your comments:
    1) The measures are in different fact tables
    - My application will show all the measures in the same report. My question is, will performance be affected by creating separate cubes or creating one cube? I believe that if I don't use an AW, it shouldn't, but I will have an AW. Performance is the main reason why I'm using Oracle OLAP. I need fast access to measures in different fact tables in one report. Those measures will be used in complex calculated fields, and probably in 'what if' analysis.
    2) When using cwm2_olap_table_map.Map_FactTbl_Measure, I can only map the measures from the first fact table, the others return "Exact fetch returns more than the request number of rows".
    Here is the complete script I am using to create the cube:
    execute cwm2_olap_cube.Create_Cube('OLAP','CUBE_REL_3','CUBE_REL_3','MY_CUBE','MY_CUBE');
    execute cwm2_olap_cube.add_dimension_to_cube('OLAP', 'CUBE_REL_3','OLAP', 'DIM_STORE');
    execute cwm2_olap_cube.add_dimension_to_cube('OLAP', 'CUBE_REL_3','OLAP', 'DIM_ITEM');
    -- MEASURES - FACT TABLE 1 (F_SALES)
    execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','SALES_MARGIN', 'Sales Margin','Sales Margin', 'Sales Margin');
    execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','SALES_QTY','Sales Quantity','Sales Quantity','Sales Quantity');
    execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','SALES_VALUE', 'Sales Value','Sales Value', 'Sales Value');
    -- MEASURES - FACT TABLE 2 (F_PVP_MIN_MAX)
    execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','PVP_MIN','pvp min','pvp min','pvp min');
    execute cwm2_olap_measure.create_measure('OLAP', 'CUBE_REL_3','PVP_MAX', 'pvp max','pvp max', 'pvp max');
    -- FACT TABLE 1 MAPPINGS
    execute cwm2_olap_table_map.Map_FactTbl_LevelKey('OLAP','CUBE_REL_3','OLAP','f_sales','LOWESTLEVEL','DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
    execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','SALES_MARGIN','OLAP','f_sales','SALES_MARGIN', 'DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
    execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','SALES_QTY', 'OLAP', 'f_sales', 'SALES_QTY','DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
    execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','SALES_VALUE', 'OLAP', 'f_sales', 'SALES_VALUE','DIM:OLAP.DIM_STORE/HIER:STORE/LVL:L0/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L0/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L0/COL:COD_ITEM;');
    -- FACT TABLE 2 MAPPINGS
    execute cwm2_olap_table_map.Map_FactTbl_LevelKey('OLAP','CUBE_REL_3','OLAP','f_pvp_min_max','LOWESTLEVEL','DIM:OLAP.DIM_STORE/HIER:STORE_HIER1/LVL:L1/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L4/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L4/COL:COD_ITEM;');
    execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','PVP_MIN','OLAP','f_pvp_min_max','PVP_MIN', 'DIM:OLAP.DIM_STORE/HIER:STORE_HIER1/LVL:L1/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L4/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L4/COL:COD_ITEM;');
    execute cwm2_olap_table_map.Map_FactTbl_Measure('OLAP', 'CUBE_REL_3','PVP_MAX', 'OLAP', 'f_pvp_min_max', 'PVP_MAX','DIM:OLAP.DIM_STORE/HIER:STORE_HIER1/LVL:L1/COL:COD_STORE;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER1/LVL:L4/COL:COD_ITEM;DIM:OLAP.DIM_ITEM/HIER:ITEM_HIER2/LVL:L4/COL:COD_ITEM;');
    -- CUBE VALIDATE
    execute CWM2_OLAP_VALIDATE.Validate_Cube('OLAP','CUBE_REL_3');
    The error is in the cwm2_olap_table_map.Map_FactTbl_Measure command for the first measure of the second fact table. Am I doing something wrong?
    Regarding issues 3) and 4), I will follow your sugestions. I'll get back to you on this later.
    Once again, thanks for the help, it is being most helpful.
    Ricardo Sá

  • Few dimension values used in FACT tables.

    Hello all,
    We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
    Thanks and Regards,
    Upendra

    nilanjan chatterjee wrote:
    Hi,
    >
    > The data for the parent members should be available in the SQL tables.
    > For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
    >
    > Hope this helps.
    I guess you meant should not, right ?

  • EVDRE- Child member values not rolling up to Parent

    Dear Freinds,
    I am using 4 Hierarchy in Account DIM.  I am facing a problem that for second hierarchy child member values not summing up to Parent.
    Dimentioned processed sucessfully.
    Thanks ! in advance.

    Have you recently implemented EHP1?
    If so there is a common issue with the hierarchy tables - refer to OSS note 1139396
    Hope this helps

  • Fact table with datetime measure showing #value error while browsing the cube

    Hi All,
    I have a cube with a fact table having datetime measure.
    when I browse the cube, I am able to see the data for all measures except  for the measure with the datetime as datatype.
    Thanks in advance.

    Hi jarugulalaks,
    Actually this forum is to discuss:
    Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
    To make this issue clearly, would you mind letting us know more information about this issue? Whether it is the VS IDE issue? Which language are you using? Which kind of app are you developing? Maybe you could share us a screen shot about it.
    But like this case posted by you here:
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/bc2d30b8-a60d-4f0f-a273-b7cf0f5aaed5/value-error-for-datetime-measure-in-ssas?forum=visualstudiogeneral#bc2d30b8-a60d-4f0f-a273-b7cf0f5aaed5
    If it is the SSAS issue, please post this issue to the SSAS forum for dedicated support.
    Best Regards,
    Jack
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Essbase answers - None of the fact tables are compatible with the query request "member"

    Hi,
    I have modelled an Essbase database into the repository.
    If I pull the measure, period and year dimension in and filter on the year (member) and display the year (member) along with the period (alias) and measure it errors with =>
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request Fiscal Year.Fiscal Year Code. (HY000)
    However, all other things being equal if I change the year displayed to the alias then it works.
    Anyone tell me why??
    Is there a limitation that Essbase brings through that you cannot view what you filter on?
    thanks,
    Robert.

    Hi
    i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
    Gl Balances : D1
    Code Commbination: F1
    Gl Sets Of Books : F2
    I have checked the joins in physical and BMM layer..all are fine..

  • Lookup on values (parent member) of other model

    Hi everybody,
    I have to get a value from one model within my application to save it in another model.
    I tried to use the Lookup functionility of BPC but this doesn't work. I'm allways getting Zeros when I run the script.
    Here is the code I used:
    *LOOKUP MODELA
    *DIM DATASRC = DS.TOTAL //Parent member
    *DIM COMPANY = CO.2000 //Basemember
    *DIM CURRENCY = USD //Basemember
    *DIM MAC: A_ACCOUNT = A.N001  //Parent member
    *ENDLOOKUP
    *LOOKUP MODELB
    *DIM MBC: COMPANY = CO.2000 //Basemember
    *DIM MBC: CURRENCY = USD //Basemember
    *DIM MBC: DATASRC = DS.TOTAL //Parent member
    *DIM MBC: B_ACCOUNT = B.N001 //Parent member
    *DIM MBC: RANK = RA.N001 //Parent member
    *DIM MBC: NATIONALITY = NA.N001 //Parent member
    *ENDLOOKUP
    *SELECT(%CPTLF%,ID,CATEGORY,RUN_LOGIC = Y AND CALC = N)
    *SELECT(%CPTPC%,ID,PROFIT_CENTRE,CALC = N)
    *SELECT(%CPTFC%,ID,TIME,ACT_FOR = F AND LEVEL = MONTH AND CALC = N)
    *XDIM_MEMBERSET A_ACCOUNT = A.1M406 //Specific Account
    *XDIM_MEMBERSET PROFIT_CENTRE = %CPTPC%
    *XDIM_MEMBERSET CATEGORY = %CPTLF%
    *XDIM_MEMBERSET TIME = %CPTFC%
    *XDIM_MEMBERSET COMPANY = CO.NA
    *XDIM_MEMBERSET CURRENCY = USD
    *XDIM_MEMBERSET DATASRC = CALC
    *WHEN A_ACCOUNT
    *IS A.1M406
    *BEGIN
    *REC(FACTOR = -(LOOKUP(MAC)+LOOKUP(MBC)),
    DATASRC = CALC,A_ACCOUNT = A.10002,COMPANY = CO.2000)
    *END
    *ENDWHEN
    When I run this script out of Model A everything seems to be working. But the Problem is that the lookup values for Model B are allways Zero. The strange thing is that this code worked last year correctly. This year the script doesn't calculates correctly. The difference is that we did a patch Level upgrade.
    Regards
    Derk

    Hi Derk,
    Now it's clear!
    First of all - you script is executed in OPERATIONS - then first LOOKUP is better to replace with tuples! Like:
    *LOOKUP MANNING
    *DIM CPT: COMPANY = CO.2700
    *DIM CPT: CURRENCY = USD
    *DIM CPT: DATASRC = DS.TOTAL
    *DIM CPT: MA_ACCOUNT = MA.N001
    *DIM CPT: RANK = RA.N001
    *DIM CPT: NATIONALITY = NA.N001
    *ENDLOOKUP
    *SELECT(%CPTLF%,ID,CATEGORY,RUN_LOGIC = Y AND CALC = N)
    *SELECT(%CPTPC%,ID,PROFIT_CENTRE,CALC = N)
    *SELECT(%CPTFC%,ID,TIME,ACT_FOR = F AND LEVEL = MONTH AND CALC = N)
    *XDIM_MEMBERSET OP_ACCOUNT = OP.1M406 //Cost Pass Thru Income Type
    *XDIM_MEMBERSET PROFIT_CENTRE = %CPTPC%
    *XDIM_MEMBERSET CATEGORY = %CPTLF%
    *XDIM_MEMBERSET TIME = %CPTFC%
    *XDIM_MEMBERSET COMPANY = CO.NA
    *XDIM_MEMBERSET CURRENCY = USD
    *XDIM_MEMBERSET DATASRC = CALC
    *WHEN OP_ACCOUNT
    *IS *    //already scoped to OP.1M406
    *REC(FACTOR = -(([OP_ACCOUNT].[OP.N006],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N011],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N014],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N034],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N035],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+LOOKUP(CPT)),DATASRC = CALC,OP_ACCOUNT = OP.10002,COMPANY = CO.2700)
    *ENDWHEN
    Also it's necessary to understand which values can be missing in the cube... then different logic may be required!
    Vadim

  • Fact table is joining with Other table having values for measures

    I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
    How should be the physical join between them and the logical join.
    Earlier we had those VALUES in Fact1 only
    Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
    We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
    How we have to proceed now..!! Please help us!!?

    I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
    How should be the physical join between them and the logical join.
    Earlier we had those VALUES in Fact1 only
    Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
    We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
    How we have to proceed now..!! Please help us!!?

  • Dimension values without data in a fact table

    I have an ODS system and a Data warehouse system
    I have a Sales fact table in the ODS system and I have these fields:
    SALES
    ID_CUSTOMER (PK),
    ID_MODEL (PK),
    ID_TIME (PK),
    SALES,
    QUANT_ART,
    COST
    Then in some records in the fields ID_Time or ID_Model or ID_Customer I don’t have values (NULL) because in the transactional systems these record don’t have values (NULL).
    The users want to generate aggregate reports with the Sales table...
    The question is:
    I have to put a “dummy” value in the dimensions Customer, Model and Time (for example “0”) and put this value in the fact table if the dimensions fields have NULL values????
    Or I have to leave the NULL values?
    What is the best choice? Why?

    There's often some specific reason why these values don't exist, such as the record being a manual adjustment to sales (for example a journal voucher). In these cases it can be helpful to have a flag column to indicate this, so that when a user comes across a bunch of sales with a Store Name of "Unknown" or "Not Applicable" they can also look at the reason for this unusual entry.

  • Pulling values from Variables for my Fact Table

    Hi All,
    The Load_Date in my Fact table is currently, current_timestamp-1, as the data is one day old when it is being loaded. I want to get that date from a variable because if I need to rerun with an earlier date like 20 or 30 days before the current date, I do not want to touch the mapping instead modify the variable and run the package. Please advise on how to do this?
    Thanks for your time and help.

    As Bhabani said, create a project variable with the code you would like to run to generate the earlier date. For example, "select current_timestamp - 30". Then, add this variable to the Package before the Interface, setting it to refresh. In the Interface, change the mapping from what it is now (current_timestamp - 1) to the variable (#VARIABLE_NAME). The variable will now be refreshed and the value added to the mapping.
    If you want to change it to "current_timestamp - 20", just update the variable.
    Regards,
    Michael Rainey

  • Restricting the Prompt Values based on Fact table data

    Hi,
    We need dashboard prompts in OBIEE reports that will fetch data from dimension tables. Our all dimensions are conformed dimension having joined with multiple fact tables.
    Because prompts are showing data from dimension table, it is showing all dimension data and few data might not present in the particular fact table that we have used in the report.
    For Example:
    We have one Calendar dimension table that has 20 years data that means all dates. Now we have two fact tables Fact1 and Fact2.
    In Fact1 we have records related to only 2007 Years data. And In Fact2 We have 2008 years data.
    Now We are creating two separate reports in two separate page in one dashboard where the prompt is same. That is Calendar date prompt.
    So In report1, The prompt will be Calendare and Result will be from Fact1. But as the calendar prompt from Calendar dimension, it showing all 20 years data though only 2007 years data is valie.
    Similarly for Report2, It is showing all calendar dates in the prompt where Fact2 is having 2008 year data.
    I want to show only 2007 years dates in the prompt for Report1 and 2008 years dates for Report2. That means I want to restrict prompt values based on the fact.
    It will be great if someone can suggest on this.
    Regards,
    SS

    Hi, I have a similar problem.
    I have two dimensions: time and customer.
    The two dimensions are joined into two Fact Table (Order, Forecast).
    I created a dashboard prompt with two selections: the first is the Year (time dimension) and the second is the Region (customer dimension) with the option "cosntraint."
    When I select a Year, not all Regions are shown, but only those that are present in one of two fact table for the year chosen. Which fact table?
    What criteria will limit the values of the Region?
    Thanks

  • Why Negative values are entering in to fact table.

    Dear All,
    After Data File uploaded. The Fact table is showing Negative values.
    Can any body give solution.
    And in DataManager->Financial Process>FX Restatament (Is running Succussfully)
    But Currency is not getting translated.
    Please help.
    Thanks,
    Satish.

    The reason the values are negative may be caused by 2 items.  The first is the default method by which BPC store information; BPC is designed to store values based on the natural sign.  So, if a Revenue account is positive in the Data File, and the Property "ACCTTYPE" is INC, the value is stored as a negative number.  When an expense value is loaded to an account with "EXP", the value is stored as a positive.  LEQ are Negative and AST are positive. (CREDITS and DEBITS storage)
    BPC then uses tables and measures to report the account based on type correctly in the Excel interface. This is how  BPC is designed. 
    There is also the CREDITPOSITIVE = YES / NO that is part of the Data Transformation instructions, and if this is setup incorrectly, you may store the reverse signs from the data file that is loaded. So this may need to be reviewed as well.
    As for the FXTranslation, I assume you have rates in the RATE cube to use in the translation process. You will need to verify that the RATETYPE property is filled in for the accounts you wish to translate? DId you process the FX script logic and the RATE script logic prior to running FX.
    Hope this helps.
    Edited by: Petar Daniel on Dec 10, 2008 2:20 PM

  • Measures values are twice as big compare to corresponding fact table

    The version used is SQL Server 2012
    We have a CustomerAddressKey in fact tables with many partitions and Regular Dimension Usage between fact table and CustomerAddress dimension. As we do not process all partitions every day sometimes we encounter the issue when users see the old address for
    a particular player.
    We have played with 2 approaches: Referenced Dimension Usage and modification of CustomerAddress view when only current (latest) address is available.
    After we build and process Referenced Dimension Usage version using CustomerAddress as Reference Dimension  and Customer as Intermediate dimension and CustomerAddressKey and CurrentCustomerAddressKey.
    Everything is OK besides that the measures value for any slice is twice as big as corresponding fact table value.
    What did we do wrong?
    serguei russky

    There are a couple of ways that data can get duplicated in SSAS
    One is incorrectly running multiple ProcessAdd operations. ProcessAdd always appends data. So if you run it twice with the same set of rows you end up with duplicate fact rows in your cube. The way to fix this is to run a ProcessFull on the affected partition/s.
    The other common thing that can duplicate data is issues with your data and / or schema. The following is just psuedo code, the join conditions should be the same as you've specified in your DSV. If you run these two styles of SQL queries over your raw data
    and they return different amounts then you probably have a problem with the way you have populated the data in your reference dimension table.
    SELECT SUM( <measure column> )
    FROM <fact table>
    SELECT SUM( <measure column> )
    FROM <fact table>
    INNER JOIN <reference dim>
    ON ...
    INNER JOIN <CustomerAddress dimesion>
    ON ...
    http://darren.gosbell.com - please mark correct answers

  • Hierarchy Table - Parent/Child Value Pairs w/o Node Name

    Hi,
      Has any body worked with below senario to create a Hierarchy table through Import Manager. If so how did you do it? I followed and sucessfull with some senario's by refering the blog "MDM Import Manager: handling multiple formats of source data for hierarchy" by pandey but not with this one. This scenair is actually from help.sap.com
    Parent           Category
               Printers
    Printers      Laser
    Printers      Inkjet
    Inkjet           B&W
    Inkjet           Color
    Printers      Dot Matrix
    Dot Matrix      300 DPI
    Dot Matrix      600 DPI
    Dot Matrix      1200 DPI
    Edited by: SDN POWERED on Jun 7, 2009 8:59 PM

    Hi SDN Powered,
    For Hierarchy Table - Parent/Child Value Pairs w/o Node Name just do as follows:
    1) In the Source Hierarchy tree, select the Parent and Child field nodes which you want to use to build hierarchy.
    2) Right-click on one of the nodes and choose Create Hierarchy Field from the context menu, or choose Source > Create Hierarchy Field from the main menu.
    3) MDM opens the Create Hierarchy Field dialog box. This dialog box contains 4 feilds, viz Hierarchy Field Name, Parent Field, Child Field, and Node Name Field. In the Hierarchy Field Name, type the name for the new field.In the Parent Field, Child Field. For Parent/Child Value Pairs w/o Node Name , set the Node Name Field to None.
    4) Click OK to close the Create Hierarchy Field dialog box. The MDM Import Manager creates Hierarchy using the values you have provided.
    I hope I am able to solve your problem.
    Thanks & Regards
    Dilmit Chadha

  • Measure value in intermediate fact table

    Hi I have a schenario where i have a measure in intermediate fact table ( in a many to many relation ship ) and i am not able to handle this.
    I have file summary fact that has file details - names , spaceGB , share details , cost per GB, Total cost of file ( SpaceGB * Cost per GB)
    Share dim that has regular relationship. 
    We have another mapping table (fact) that gives many to many relationship between Shares and Cost Center and there is a allocation percentage associates with a share across different costcenters
    Share        Costcenter          Allocation%
    Share 1     CostCeneter1      50%
    Share 1     CostCeneter2     50%
    everything works fine as long as i dont show allocation % how do i handle allocation % to get cost center cost.

    Hi Vin444,
    According to your description, there is a measure in intermediate fact table which you are not able to handle this in database level, now what you want is showing intermediate fact table measure value, rithg?
    As pey my understanding, you can join the tables based on the intermediate fact table on datasource view. A named query is a SQL expression represented as a table. In a named query, you can specify an SQL expression to select rows and columns returned from
    one or more tables in one or more data sources. So in your scenario, you can join the tables using named query instead of database level.
    http://msdn.microsoft.com/en-IN/library/ms175683.aspx
    http://msdn.microsoft.com/en-IN/library/ms174778.aspx
    If I have anything misunderstood, please point it out.
    Regards,
    Charlie Liao
    TechNet Community Support

Maybe you are looking for