Optimizing data grouping on BMM Layer

Hi.
I'm faced with the next task.
*(1)* Business goal
Display number of customers registered and activated by periods. The request in Answers should contain:
*{Period, NumberOfContacts_Registered, NumberOfContacts_Activated}*
*(2)* At Physical Layer I can provide data in two ways:
*2.1.* In single table like {customer_id, registration_date, activation_date..}
*2.2.* In two tables like {customer_id, registration_date..} and {customer_id, activation_date..}
*(3)* The question is about the most effective way of organizing data on BMM Layer.
I'm interested in whether I can organize single logical table to represent desired data in Answers. For example, logical table with columns {customer_id, registration_date, activation_date..} and then define complex join with logical table "Periods".
For now, I had an occasion to define two logical tables - with columns like in Paragraph 2.2. But it seems to be more effective way to do this.
Could anyone give me a piece of advise how to resolve this task more effectively (in preference, with single logical table).
Regards,
Alex.

hi Jeremy,
Use this '01-JAN-08' format in answers filter
Let me know if you have issues
OBIEE will replace with time stamp adds if its a timestamp/datetime data type
Thanks,
Saichand.v

Similar Messages

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

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.

How to determine the logical Keys of logical fact table in BMM layer?

Hello guys
I'd like to know more about how to know what columns of the logical fact table should be used as key in BMM layer. How OBIEE behaving differently when different keys are selected?
In my situation, I have 1 fact table that physically joins to 20 dimensions in physical layer. Therefore, in physical layer, this fact table has about 20 foreign keys but no primary keys..
In the logical layer, this fact table is logically joined to the same group of dimension tables. So in this case, how do I know what columns in logical fact table I should use as keys?
Please advice
Thanks

thanks for the reply...
The interesting thing I notice is that, when I start using fragmentation with the fact tables in its LTS, if not primary key is defined in the logical fact table, then I will be getting errors:
[nQSError: 10058] A general error has occurred. [nQSError: 14023] None of the fact sources for columns are compatible with the detail filter []. (HY000)
When I create the key by choosing random columns from the fact table as the logical key columns, this error goes way and the correct SQL is generated according to the frag..
Because of such behavior, I'd really like to know how logical key really works in BMM layer.

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

Left outer join usage in obiee BMM layer

Hi All,
We lately started using left outer join in our bmm layer , to meet the requirement expectation .
problem : We have two tables Fact A , Dim B . There is an join int_id column to join them . Problem is... in table Dim B , we have 3 millions rows of Int_id and in fact table it is loaded for only data available(1 million rows).
Due to this we are dropping rows in the report ..as it is only getting data where fact.int_id = dim.int_id. So we used left outer join to solve to one particular report .(we know we can do ETl to load dummy int_id and make it null , but it is huge effort ..so we did left outer join)
These days , same kind of reports are in requirement . if i keep on doing same left outer join to meet the requirement in BMM layer ? is there any disadvantages due to this ? any performance degrade due to this ? please throw few lines on left outer join and its usage ?
Thanks,
Sri

Remodel your tables that might be a partition or any other way and follow in BI as per your new model.
Simply: Go for ETL kind of solution

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 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.

What is the use of Multiple source in Logical Table under BMM Layer?

what is the use of Multiple source in Logical Table under BMM Layer?
thanks in advance

Or more generally speaking:
To create a "logical table" consisting of multiple "physical tables"...hence the names. It's the backbone of the whole BI server concept and the way the rpd handles the requests.
I.e.: how would you otherwise proceed for making an analyzable table from SAP, Teradata, Oracle and a flat file with no full change-access to all the data sources?

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

Please Help in Joins and content tab (BMM Layer).

Hi all,
I am a newbie in OBIEE. I am working on a project in our organisation for existing database schema in oracle. We are planning to use OBIEE for reporting purpose.
Here's my problem.......
I have Three dimensions and Two Fact tables in my schema.
out of these one dimension is conformed Dimension.
Product_Reporting_Line, Geography, Policy_Cover_Type are Dimensions and ClaimFact,*PolicyFact* are facts.
Product_Reporting_Line is joined to Claim Fact and Policy_Cover_Type is joined to PolicyFact..
Geography is joined to both Claim Fact and PolicyFact.
Here's how it looks.....
Product_Reporting_Line-----< Claim Fact >-------Geography--------< PolicyFact >-------Policy_Cover_Type
I have a report in which columns from all the tables have to be taken.
In the Fact tables F1 and F2, there are some columns for which aggregation rule is not set (varchar Data for example Claim Number from ClaimFact and Policy Number from PolicyFact).
How should I design BMM layer. I want to know how the content tabs should be set.
Can anybody suggest me how should I do this?
Edited by: LavaRider on Jul 12, 2010 6:12 AM

Hi Kart,
I didn't do it the other way, I did it the the way you suggested me..
I have set the content for the Policy_Fact LTS to the Total level of Product_Reporting_Line dimension.
also I have set the* content* for the ClaimFact LTS to the total level of Policy_Cover_Type.
When I set the level *(Level tab of logical columns properties)* of Measues to the total level then it works....
i.e.
I have set the levels of the logical columns of Policy Fact table to the total level of Product_Reporting_Line and also set the levels of the logical columns of Claim_Fact to the Total level of Policy_Cover_Type.
I want to ask you Do we have to set the content in the LTS as well as in the Level (tab) of the measures?
Thanks for giving your precious time for me, I really appreciate that

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?

Creation of star schema from snowflake schem in BMM layer

hi,
This is my situation.I have "Fact-table" which has Dim 1 .now Dim 1 is joined to Dim2,Dim3
Fact
|
Dim 1
|
| |
Dim 2 Dim 3
Now in Bmm Layer how can i make this snowfalke schema to star schema.I heard about making changes in the Logical Table source.And what will be the look of the presentation layer.
Any help is appricaited Guys.

In physical layer, you have a join between Dim 1 and Dim 2, Dim1 and DIm3, Fact and Dim1. In BMM for Dim1, in the sources, add Dim2 and Dim3. You may add both these dimensions in one single LTS if the data is not duplicate in the tables. In case the data is duplicated add them as seperate LTS in the sources for Dim1. Refer this post for reference -- Logical Table source source query
In BMM you need a join between Dim1 and Fact. Basically your Dim1 is sourced from three different tables which are your dimensions. This would transform your snowflake into star. In your presentation layer you will have all the columns from your dimensions (except for the duplicates, lets say you have column A in both dim1 and dim2, you should map this column in column mapping tab so as to enable BI server to pick the most economical source) and facts.
Hope this clears your question.

Diffence between physical layer and BMM layer

Hi all,
Please let me know the difference between Physical layer design and BMM layer design. Please write your views in your reply instead of links.
regards
chandra kanth.

chandra kanth.,
Use in the layers
The physical layer is the layer of the Logical Business Model where you define the physical data model of your data source. It contains information about the physical data sources.
The most common way to create the schema in the Physical layer is by importing metadata (table, view, …) from databases and other data sources. If you import metadata, many of the properties are configured automatically based on the information gathered during the import process. You can also define other attributes of the physical data source, such as join relationships, that might not exist in the data source metadata.
In the Business Model
In the business model, OBI recommends using complex logical joins instead of foreign key logical joins.
When Complex joins are used in the business layer then they are really acting as placeholders. They allow the OBI Server to decide on which are the best joins define in the Physical Layer to satisfy the request.
In a Dimension, you may have multiple Logical Table sources that all join to one fact table. The OBI Server will then decide the best joins to use to meet the requirements.

AP Payment User Responsbility's Data Group to be assigned for application as Payables or Payments?

Hi,
I am in version R12.1.3 . I have a requirement to create a user who must have access only to create payments in AP module.So when i try to define a responsibility for this payment user
there is a data group to be assigned. In this data group block for application there are 2 options i.e Payables & Payments? What should I select & what is the difference of selection one over the other?
Appreciate your help.
Thanks

Hi,
i did not see any difference .... I performed a test case, where i created a payment using the new responsibility i have created having data group application as Payments, the payment was successful ... Later i have modified the data group for this new responsibility from payments to payables, then the test payment i have made was also successful....
Not sure about its impact, may be i am having responsibilities which has full access, hence i cannot see the difference in my environment ....
Regards,
Ivruksha

Optimizing data grouping on BMM Layer

Similar Messages

Maybe you are looking for