Problem creating hierarchy in BMM layer

Hi,
We are trying to create hierarchy for one of the dimension which contains 10 LTSs, each LTS represents Bridge-->Dimension join in physical layer. So, each LTS contains inner join between Bridge and Dimension tables.
We performed the following.
Right click on Dimension and select Create logical dimension--> Dimension with Level-Based hierarchy.
The error is "Admintool is unable to create the structure for the dimension <<Dim name>> "
Can anybody help..
Thanks,
Anilesh

Hi,
Here we have created 10 LTSs for supporting 10 bridge tables. We are joining same dimension table with multiple bridge tables in physical layer. And each bridge is joined with corresponding fact table. when id comes to BMM layer, we created single dimension which contain LTSs for each bridge table, and we joined the dimension to fact.
Thanks,
Anilesh

Similar Messages

Drilldown in answers without creating dimensional hierarchy in BMM layer?

Hello All,
HELP! I have a main report like this:
title: Region EAST (prompted field- user entered: North, South.... )
heading: Departments Total Sales
rows: Meat (01) 500,000.00
Produce (02) 100,000.00
Organic Items(03) 250,000.00
Users wanted to ClLICK on either Meat, Produce or Organic Items field to get the detailed report on that particular dept. and would prefer to Click on the desired field than using department as a prompted field. :(
I did try to use the navigate function on Departments column to get to the detail report, but the results came back with ALL departments. Is it possible to drill down in answers without creating the dimensional hierarchy in BMM layer? If so, please show me how to create the link that would navigate to the detailed report when users CLICK on desired department, ex: Meat (01)? BTW, detailed report may came from different resources (data is in the detailed table...) and I still need to pass the region variable to the detailed report.
I really need a big help on this.
Thanks All in advance!

Hi Matt,
thank you for looking into this problem.
I did use the Navigate function on the 1st report, create a prompted filter on the depatment column (second report) but user can only click on the high lighted Department column header (on the first report) which navigated to the 2nd report and it displayed detail of all departments. Since users cannot click on a particular deptpartment, therefore I cannot pick up the value (01) for Meat department to pass thru the 2nd report. Is the Navigate function just works only when you click on the header column not on the data values in that column? do I need to set any other function to the department column on the 2nd report beside the filter?
thanks for your help!

Problem creating hierarchy based on 2 physical dimension tables

I'm having a problem creating 1 logical dimension with a drill-down hierarchy, based on two separate physical dimension tables. The errors I receive when navigating the drill-down hierarchy is:
"Cannot find logical table source coverage for logical columns" &
"Missing join between logical tables".
I'm using OBIEE 10.1.3.4
Here are the details of what I have setup sofar:
Physical layer:
Dimension table DIM_ORG with columns:
-dimension_key
-org_total_code
-org_total_description
-org_detail_code
-org_detail_description
Dimension table DIM_DEPT with columns:
-dimension_key
-dept_total_code
-dept_total_description
-dept_detail_code
-dept_detail_description
Fact table FACT_SALES with columns:
-fk_org
-fk_dept
-sum_sales
Physical Joins:
FACT_SALES.fk_org = DIM_ORG_dimension_key
FACT_SALES.fl_dept = DIM_DEPT.dimension_key
Business Model & Mapping layer:
I created a logical dimension ORG_DEPT. It contains two logical table sources (DIM_ORG & DIM_DEPT) and the following logical columns:
- All Departments (mapped to dept_total_code)
- Organisation (mapped to org_detail_description)
- Organisation Number (mapped to org_detail_code)
- Department (mapped to dept_detail_description)
- Department Code (mapped to dept_detail_code)
The business logical key is based on the combination of Organisation Number & Department Code
The hierarchy I need is: All Departments -> Organisation -> Department so I created the following hierarchy for ORG_DEPT:
- Total Level containing: All Departments
- Organisation Level containing: Organisation Number (defined as the Logical level key) & Organisation (defined als the Drill level key)
- Detail Department Level containing: Department Code (defined as Logical level key) and Department (defined as Drill level key).
In the LTS of the dimension ORG_DEPT I've set the Content levels for the sources:
DIM_ORG : Organisation Level
DIM_DEPT: Detail Department Level
In the LTS no -inner- joins have been added against related physical tables.
I created a logical fact table SALES (based on the physical fact table) and joined it against the logical dimension table ORG_DEPT.
In the LTS the Content level for ORG_DEPT is set against the Detail Department Level. No - inner- joins have been aded against related physical tables.
When I create a report in Answers to test the hierachy and select only 'All Departments' I get the correct dimension value returned. When I try to drill to the next level I get the following ODBC error:
"Cannot find logical table source coverage for logical columns: [All Departments]. Please check more detailed level keys are mapped correctly".
When I create a report in Answers and select both 'All Departments' and 'Sales' I get the correct result. When I try to drill to the next level I get a different ODBC error:
"Missing join between logical tables DIM_DEPT and DIM_DEPT: There must be at least one physical join link between the underlying physical tables".
Any suggestions are welcome!
Thanks!

Hello Robert,
Your suggestions were known to me but I still wanted to combine the two physical dimension tables in one logical dimension. So I've played around a bit more and found the solution: In my original setup I had two seperate logical table sources (one for each physical dimension table). The solution was to combine the two logical table sources in one logical table source. I achieved that by logical joining the DIM_DEPT table to the FACT_SALES table and subsequently to the DIM_ORG within the 1 LTS and using inner joins.
Then I created the logical table key (a combination of org_detail_code & dept_detail_code). After that I could create the hierarchy with no problem.
Edited by: The_Dutchman on Nov 4, 2011 9:43 PM

Display of yellow colour icon to a table in BMM layer

Hello all,
Please ignore my previous thread. By mistake it went without any description of problem. Sorry for that.
I have two tables org details, emp details
org details having columns like orgname, year, quarter1 results, quarter 2,quarter 3, quarter 4
emp details having columns like org, year, emp in quarter1, quarter2,quarter 3, quarter 4.
Spread sheet as datasource and imported to physical layer....when i drag drop to BMM layer...emp details table icon showing yellow.
But it's not a fact table...those two are normal tables....why is it showing yellow colour icon?
please let me know the concept of how OBI administrator tool decides that the table is fact table or dimension table.
regards
chandra kanth.

By default OBIEE will show yellow colour.Once you create joins in BMM layer then it will show colours accordingly.Table on n side in 1:n join will be shown as yellow(Fact).So create joins in BMM layer.
Regards,
Sandeep

BMM layer creation (Star Schema Physical Layer) - What to add/not add?

Hi All,
I am just looking for any general feedback on the thought/question below.
I am setting out on creating my first BMM layer and trying to determine what I need to do in this layer that will be different and add value from what I already did in the physical layer. My data model is already defined as a star schema within my data mart source. So in the physical layer I have my facts imported along with the dimensions and I have joined them together as needed. Here is what I think I will setup as I move into the BMM layer:
1. I will add heirarchies as needed to enable drill down within my reports
2. I will need to add my calculations/measures to allow for any type of metric to be returned through a request in Answers
3. I do not see a large need to create logical tables (at least not yet) based on multiple physical source tables as my source is already a star schema and dimensionally modeled. For users that also already source a star schema at the physical layer .. do you find that you do a lot of logical table creation/mapping to add functionality or does your BMM look a lot like you Physical Layer?
Other than steps 1 and 2, I am not really sure how much additional manipulation I might do from the Physical to BMM layer since my Physical is already a star schema. Am I missing anything? Obviously everyone's data model and circumstances are different but I wasn't sure if maybe there were some good thoughts on what I might be missing (if anything)?
One last question .. I am not currently planning to use any aliases at the Physical Layer but I do plan to rename the tables at the presentation layer to be more business verbage like. Why are others using aliases?
Thanks in advance for the help.
K

Alastair, thanks for the advice. I'll definitely keep that in mind as I start to build out the BMM.
One question/issue I just ran into as I was wrapping up my Physical Layer mapping. When I check for global consistency, I am getting an error that is complaining that I have multiple joins defined between the same two tables (which I do). This is because I have the following setup:
TBL_A_FACT
F_ID_HIT
F_HIT_DESC
F_ID_MISSED
F_MISSED_DESC
TBL_B_DIM
F_ID
F_DESC
Table A joins to Table B in two ways:
TBL_A_FACT.F_ID_HIT = TBL_B_DIM.F_ID
TBL_A._FACT.F_ID_MISSED = TBL_B_DIM.F_ID
The F_IDs can be either hit or missed on any given fact record and the total distinct set exist in the dimension.
When I define two foreign key joins in the physical layer based on the relationship above and check Global Consistency, I get an error saying that "TBL_A and TBL_B have multiple joins define. Delete duplicate foreign keys if they exist" and it is listed as an error. I guess this makes sense because when the two tables are used in a request OBIEE would need to know how to join them (using the hit or missed field). What is the best approach for handling this..
- Should I define TBL_A twice in the physical layer as:
TBL_A (Alias TBL_A_HIT)
F_ID_HIT
F_ID_HIT_DESC
TBL_A (Alias TBL_A_MISSED)
F_ID_MISSED
F_ID_MISSED_DESC
Or do something like the above in the BMM layer?
Thanks for the help!
K
And then establish the relationships using these separate tables?

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

Problem with BMM layer warning messages.

Hi,
I have modelled with the following tables in BMM layer.
Dimension tables: Regions,Countries,Departments, locations, Employees, jobs, job history
Fact table: HR Facts (measured columns like salary, max salary, min salary, commission)
The model is consistent with the following warnings:
Logical dimension table REGIONS has a source REGIONS that does not join to any fact source.
Logical dimension table DEPARTMENTS has a source DEPARTMENTS that does not join to any fact source.
Logical dimension table COUNTRIES has a source COUNTRIES that does not join to any fact source.
Logical dimension table LOCATIONS has a source LOCATIONS that does not join to any fact source.
and also in the answers section (Presentation services) i could not able to view data, it's giving the following error (when i am trying to display REGION NAME field values)
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: REGIONS.REGION_NAME. Please fix the metadata consistency warnings. (HY000).
I could not able to trace the problem where exactly is to be fixed.
regards
chandra kanth.

Hi,
Thanks for the information. Ideally that works out without any hierarchies. But the problem with which i was facing is somewhat different.
Let me explain the problem scenario exactly:
I have an employee, region tables in physical layer. Employee table has SALARY Column. Region table dont have any
join with Employee table. In BMM layer i have created a fact table "HR Facts" and crated a logical fact column SALARY.
The logical fact table source is Employee table. I have drag dropped Region table into BMM layer and joined with HR
Facts table. While consistency check its given a warining message: Logical dimension table REGIONS has a source
REGIONS that does not join to any fact source.
What is the problem exaclty?
regards
chandra kanth.

Arranging Hierarchy tables in BMM layer

Hi
I have a different structure of dimensions in the database.
Year->Season->Quarter->Month->Week
For every level in Hierarchy I have table i.e, Dim_Year, Dim_Season, Dim_Quarter, Dim_Month, DIm_Week
They are joined in physical layer in as per the hierarchy thats is Dim_Year is joined to DIm_Season by Year_id, Dim_Season is joined to Dim_Qaurter by Season id and so on.
In BMM layer I have to craete an Hierrarchy.
How should i keep these tables
Option1: Pull the all the tables separately
Create comples join between all the dim tables year->Season->Quarter->Month->Week
Create hierarchy from these tables
Option2:
Create a logical tables as Time
Pull all the tables into Time table with different Logical table sources.
Then create a hierarchy from these tables.
This will avoid the comples join in BMM layer
Please suggest which option will lead to less performance issue and which is ideal approach in such scenarios.
Thanks in Advance

Hi,
I am new to OBIEE but still I am suggesting one option....
Drag and drop any one of the Time table (for ex Dim_Year) from physical layer to bmm layer. create a complex join of this table with the other tables in the bmm layer. then simply drag and drop the columns from other tables (Dim_Season, Dim_Quarter, Dim_Month, DIm_Week) from the physical layer one by one on the LTS of Dim_Year.
Hope I haven't given you a funny answer.
Edited by: user9149257 on Mar 8, 2010 9:20 PM

How to create logical fact table in BMM layer ?

Hello,
I have 3 Dimension table - 2 are in one schema and last is another schema. Using this 3 dimension tables, I need to create a logical fact table.
So, my question is whether we can create this fact table by joining these 3 dimension table which are in 2 different schema s ?
Thanks

Fiaz,
you are correct. We can use tables from different subject area to create a report. However, my question was related to rpd design. Sorry, I was not very clear about the queries earlier.
Here is the whole scenario in the physical layer of the rpd
Table name      Databse name      Connection pool name      Schema name
AV          AV_PXRPAM     AVAILABILITY          CRMODDEV
OUTAGE          AV_PXRPAM     AVAILABILITY          CRMODDEV
COMPANY          PXRPAM          PXRPAM_POOL          CRMODDEV
AV and OUTAGE have the joins already. I want to make a join between COMPANY with OUTAGE. And then I want to include a column from each of above tables to the logical fact table in the BMM layer. then I want to do a star schema with the logical fact table to the above 3 tables in the BMM layer.
Thanks

How to create count() measure for certain set of records in BMM Layer

Hello all.
I have a logical table like this one (Table AAA)
Table AAA

--------------------------+
| *Key* | *Name* | 
--------------------------+
| 1-2EMHS9 | AAA |
--------------------------+
| 1-2EMWMO | BBB |
--------------------------+
| NULL | CCC |
--------------------------+
I need to calculate count() of records where Key is not NULL. In this example, this field must return coun() = 2.
I suppose, CASE operator may help me with that, but I do not know for sure how to do this.
Thank you for help,
Alex.

Thank you.
But I must concretise my issue.
I need to calculate number of records (e.g. order_id) that sutisfy appropriate condition (one of columns (e.g. loy_member_id) is set to null).
I created logical column, that returns order_id if condition (loy_member_id is null) is met.
Look at my logical column:
Q Orders (LPM) - must return number of orders where loyalty_member_id is null.
It has an expression:
CASE WHEN NOT "Foxtrot (my) replica"."Sales Orders".LOY_MEMBER_ID IS NULL THEN "Foxtrot (my) replica"."Sales Orders".ORDER_ID ELSE NULL END
So, this returns order_id I need.
But the question is how to count number of order_id's returned by this column on BMM Layer.
When I define my column with next expression:
*COUNT(CASE WHEN NOT "Foxtrot (my) replica"."Sales Orders".LOY_MEMBER_ID IS NULL THEN "Foxtrot (my) replica"."Sales Orders".ORDER_ID ELSE NULL END)*
I receive error:
+[38083] The Attribute 'Q Orders LPM' defines a measure using an obsolete method.+
Thank you,
Alex.
Edited by: Alex B on 3/3/2009 19:59

Create min(date) for Customer in BMM layer

Hi guys,
I need help in creating a first order date for a customer. I want to do this in BMM layer and use directly in reports.
How should i create this?
Any help Appreciated.

I think its you sent me email with samilar Q.
If you are doing in BMM you need to understand the schema
assuming you got fact,day, custmer tables
and these joined as star.
you need to create a metric on fact as min(day.date) and set content tab to customer level
for this you might have to map day dim to fact using fact source properties add day table.
once you done as I said:
just pull mindate metric in answers run it and check physical sql that should be like
select min(date),cust_name from
fact,day,customer
where 2 joins goes
group by cust_name
Hope this helps, if helps mark

Problem while creating hierarchy

I have 3 zones viz., East, Midwest and West. Under each zone I have few cities like Atlanta and New York in East zone.
Now my goal is to create sales representatives for each city.
I've two ways one is I can right click on a city and select Sales rep ID Insert. But when I am doing so I am getting the following screen:
Create Sales representative: Multiple selection.
with 2 columns Sales repr and short description
Under Sales repr there is # and under Short description column there are the words Not assigned.
However the fact is I've entered all the sales representatives names by right clicking on the characteristic Sales Representative name and selecting "maintain master data".
Now my question is why am I not able to view the names of the sales representatives when right click on a city and select Sales rep ID Insert.
However I am able to find the names of all the sales reps when I do it manually i.e.
1. Rt click on a city name and select Insert Characteristic node.
2. Select the info object IO_SREPNM
3. Here I am able to see the list of all the sales reps and also put the sales reps under their respective cities.
But the next problem is arising when I proceed to the next step which is
To save the screen "Maintain Hierarchy 'IO_SREP hierarchy': 'Modified Version'.
I am getting a dump error when I save the screen. The dump error says Error in ABAP application program AND
If I perform a check on the screen i.e. click on the button Hierarchy Consistency Check (Ctrl+F10) then I am getting the error
Screen name: Error log for consistency check of the hierarchy for InfoObject IO_SREP
Node SAM already exists. 
The reason why its giving this error is because there is a rep SAM whose name occurs twice. Now in my data I've Denver city in Midwest region and also in West region. So sales rep SAM's name also comes once in Midwest and West region.
What I want is
How to avoid the dump error when I save the screen? AND1
What should I do to avoid the error Node SAM already exists. 
Please advice.
Thank you.
TR.

Hi San,
Thank you for your suggestion. As per your advice this is what I've done. please go through this and let me know if I am doing it right or where I am going wrong?
Thank you.
As per your suggestion I clicked on
1. InfoObjects under modeling tab.
2. Right clicked on IO_SREP and selected CHANGE option.
3. Clicked on the Hierarchy tab.
4. Selected the check box with hierarchies.
5. Selected the radio button Time-Dependent Hierarchy Structure [Please note that on my screen it appears as Time-Dependent Hierarchy Structure and not as "Hierarcy structure time-dependent".
6. Now I clicked on the Maintain Hierarchies button.
7. A screen called Initial Screen Hierarchy Maintenance has opened.
should I click on the button Maintain Hierarchies because there is also another button called External Chars. In hierarchies.
Because when I clicked on the Maintain Hierarchies button in the screen Initial Screen Hierarchy Maintenance I found a text box called Restriction on hierarchy basic char. With IO_SREP in the box and with an option to select other InfoObjects.
I didnt find any characteristics on the right panel as the screen was not divided into two panels.
But when I clicked on the button External Chars. In Hierearchies a screen called External Characteristics in Hierarchies opened with 2 pannels the left one is Characteristics Template and the right one being External charactereistics. I think this is what you were referring to. So I selected IO_SOFF and IO_SREP from the Characterisitics Template and put it in the External Characteristics window.
8. I hit the continue button and I was back to the screen Change Characteristic IO_SREP: Detail.
9. When I hit the Check All button I got the message Characteristics o.k. and when I hit the Activate button I got the message InfoObject IO_SREP is active.
10. Now I am back to the Administrator Workbench: Modelling screen.
11. I selected IO_SREP and hit the Hierarchies icon. The screen Initial Screen HierarchyMaintenanc opened.
12. I selected IO_SREP and hit the Create Hierarchy button. The Create Hierarchy screen opened.
13. Now I entered the Hierarchy Name as IO_SREP_HIER and short description as IO_SREP hierarchy
14. Now I am in the screen Maintain Hierarchy IO_SREP_HIER: Modified Version.
15. I right clicked on the IO_SREP hierarchy and selected the option Insert Characteristic Node
16. Create Char. Node: Char. Selection Screen opened. I selected the InfoObject IO_SREG and hit the continue button.
17. From the Create Sales region: Multiple selection screen I selected all the three regions East, Midwest and West and hit the continue button.
18. I right clicked on each region and repeated steps 15 and 16 but selected IO_SOFF and entered the appropriate offices for each region.
19. Now I had entered Denver in both Midwest and West region as it was in Midwest before 1.1.2000 and in West from 1.1.2000.
20. Similarly I have also entered the employees in each city office by right clicking on each city and selecting the option Sales representative Insert.
21. Finally when I save it I am getting the dump error. Ive tried so many times till now and always I am getting the same dump error. Is there something wrong with my system or am I going wrong somewhere? Kindly advice.
While creating the hierarchies, I have noted that all the names of the cities and the regions are in yellow triangle whereas the names of the sales reps under each city are in green color triangle. Is it something that yellow color means the hierarchy is not activated and green color means the hierarchy is activated? Please advice.
In the dump error notes under How to correct the error its given as:
The work area used to hold values passed for the work area operation must be at least as wide as the database table you are accessing.
Now can you please explain me how to create this hierarchy without getting a dump error?

Case statement problem for a column in BMM layer

Hi friends.
In physical layer I've a "cardio" column whose data type is INT, and two values comes here either 0 or 1.
I need to replace 1 by 'YES' and 0 by "NO'.
For that I changed the datatype of "Cardio" column to CHAR. and in BMM layer I'm using this formula
CASE WHEN "A Analysis"."C Report"."CARDIO" = '1' THEN 'Yes' ELSE 'No' END
But this is giving me "Invalid Expression" error.
Please help me correct this error.
Help appreciated.

Hi,
Your are probably using the column Cardio as a 'source' and as a 'target'.
So you have to duplicate the cardio column (right mouse click and Duplicate option) in the business model and then apply the formula CASE WHEN "A Analysis"."C Report"."CARDIO" = '1' THEN 'Yes' ELSE 'No' END
That should work. It is not even necessary to change datatype of Cardio, OBI will handle this for you.
Regards
Edited by: wobiee1 on Nov 12, 2008 1:07 PM

Sum Aggregation Error in Physical & BMM Layer in OBIEE 11g with Essbase 11

Hi everyone,
I'm using OBIEE 11g with Essbase 11 as the data source. I'm using Sample Basic database from the Essbase as my data source. If I'm using the hierarchy for the measures (so I don't flatten the measures), and when I changed the aggregation in both physical and BMM layer from Aggregate_External to Sum, I can't create a report at all from the Answers.
Does anyone encounter the same thing? Any ideas/solution about this? Please help.
Thanks a lot!

Hi Deepak,
When I picked the "Basic - measure" alone, I got this error.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 96002] Essbase Error: Unknown Member Basic - measure used in query (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Basic"."Basic - measure" s_1 FROM "Sample Basic".
When I picked the "Gen1,Measures" alone from the measure dimension, I got this error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 46008] Internal error: File server\Query\Optimizer\ServiceInterfaceMgr\SIMDB\Src\SQOIMDXGeneratorGeneric.cpp, line 2610. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Measures"."Gen1,Measures" s_1, SORTKEY("Sample Basic"."Measures"."Gen1,Measures") s_2 FROM "Sample Basic"
But when I queried the dimensions one by one (only single dimension each), no error was shown.
This only happens if I use Sum in the physical and BMM layer. If I use External_Aggregation, these errors do not happen. And if I flatten the measures, these errors also do not happen.

Not able to find logical dimension tab in BMM layer in OBIEE 11G

Hi All,
Recently i ran in to a interested problem. We are using Oracle BI Administration Tool version 11.1.1.6.6, Repository Version:320.
I'm not able to see logical dimension tab to create dimensional hierarchy.
I followed normal method like all versions. Business model -> New Object -> (No logical dimension). I'm able to see logical display folder and logical Table.
I have only client tool on my machine. Please could anyone suggest me How should i resolve this problem.
Any help is appreciated.
Thanks,
Ashwini K.

Hi Srinu,
I joined all dimensions to facts, and i'm sure that i'm trying to create hierarchy for dimension tables. In oracle Administration Tool Repository version : 308, i'm able to see logical dimension tab at BMM-> New Object ->Logical dimension.
Any help

Problem creating hierarchy in BMM layer

Similar Messages

Maybe you are looking for