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?

Similar Messages

  • When i click the star icon on the toolbar it does not add the site to my bookmarks,how can i solve this problem

    i dont seem able to add a web site to my bookmarks,i click the star
    icon+the site is not added to my bookmarks how do i do this?

    If you revisit a site that you tried to bookmark, is the star yellow?
    If the star is yellow, the site has been bookmarked. Clicking on the star once saves the bookmark in the "Unsorted bookmarks" folder which is not visible in the bookmarks menu, clicking on the star a second time allows you to edit the bookmark so you can move it to the folder of your choice. See the [[bookmarks]] article for further details.
    If the site is not being bookmarked at all, see the [[bookmarks not saved]] article for details of how to resole this issue.

  • Star schema in Physical Layer

    Recently, i came across a question from one of colleague. The discussion went as follows:
    He asked me what is star schema and where can you define it? Physical layer or BMM layer?
    I explained about star schema and answered his rest of the doubt that, we define it in BMM layer.
    His immediate question is why can't we define it in Physical layer? Since BMM layer allows to build dimensional models, so, we have to build it in that layer itself is my reply. But, later in the evening, when i started thinking on my way to home, i started thinking about his doubt.
    Here, what am curious to know is since we can join tables in Physical layer too, why can't we define star in Physical layer? and why only in BMM? and what are the difference in the Joins that we made in Physical layer to that of BMM layer?
    I tired getting answers for these in documents and in some other online resources, but, am not succeed. So, am approaching this forum in anticipation. Can anyof you help us understanding these concepts better.

    In OBIEE Server Administration Guide it is written for logical fk join:
    Logical foreign key joins might be needed if the Oracle BI Server is to be used as an ODBC data
    source for certain third-party query and reporting tools. Typically, you should not create logical
    foreign keys. This capability is in the Administration Tool to provide compatibility with previous
    releases.
    And logical complex join:
    The use of logical complex joins is recommended over logical key and foreign key joins.
    And physical complex join:
    In the physical layer of the repository, complex joins are joins over nonforeign key and primary key
    columns. When you create a complex join in the physical layer, you can specify expressions and the
    specific columns on which to create the join. When you create a complex join in the business model
    layer, you do not specify expressions.
    I agree, that always are some special cases, but in general it should be clear when to use which joins.
    So, you should read chapters 4,5 one more time this administration guide [OBIEE server administration guide|http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf]

  • Trouble adding new Essbase dimension to physical layer

    I'm using OBIEE 10.1.3.4.2 and have created a repository where I imported an Essbase cube. That's all been fine. I recently added another layer to one of the dimensions in my cube - had Division and Market and then added System below Market. I opened the Admin tool and added the new layer/column to the physical layer. Dragged the cube to the BM&M and then the Presentation layers. When I go into Answers and begin drilling down once I select a Market the System column says organization instead of displaying valid System names.
    I also created a new repository and imported the cube and everything drills down just fine. I then compared both repositories and they look identical.
    Does anyone have a better approach to updating the physical layer when working with Essbase? I really don't want to create the whole thing from scratch as I am also including other sources.
    Thanks,
    Brad

    Follwoing links will be helpful for the same:-
    http://hekatonkheires.blogspot.com/2009/10/obiee-101341-essbase-931-udml-for-cube.html
    http://hekatonkheires.blogspot.com/2010/01/obiee-101341-essbase-931-udml-for-cube.html
    If interested you also check this link for OBIEE 11g
    http://www.rittmanmead.com/2011/06/incremental-essbase-metadata-imports-now-possible-with-obiee-11g/

  • Star schema of Datawarehouse

    Hi,
    I'm working with BI Apps (OBIEE) uploaded on PeopleSoft HCM 9.1 source system. I'm using pre built ETL task to load the pre designed Datawarehouse.I want to know where can I found the Datawarehouse star schema description?

    What you are looking for the DMR (Datawarehouse Model Reference) Doc. I believe they have this on Metalink for the BI Apps releases. This provides the physcial star schemas and details on the DW tables. Here is the metalink note:
    Oracle Business Analytics Warehouse Data Model Reference Version 7.9.6, 7.9.6.1 and 7.9.6.2 [ID 819373.1
    If this was helpful, please mark the response as correct.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Need help with an extended star schema.

    I have the following data in spreadsheet form and I need to transpose this into an extended star schema in order to prdouce my characteristics and key figures, however I'm having a little trouble understanding where to include the Product Group in the star schema and also what to do with the Sales Doc (Invoice Number) in the sales information spreadsheet. 
    I need to summarise the data into the following also:
    1.     Total quantity and revenue for each Channel and product group
    2.     Total quantity and revenue for each Channel and product group (July 2009 to September 2009)
    3.      Total Quantity and Revenue for iphone sales
    So my question in short is what would the star schema look like?  I'm hoping somebody can help me over this hurdle.
    The following are the details from the spreadsheet:
    Product Details (Attributes)
    File Name:  Product_Details.csv
    Structure     FieldName     Length     Description
         ProdID     5     Uniquely identifies a product
         PG_Group     20     Identifies products in specific groups (Navigational field)
    Sample Data
    ProdID,PG_Group
    PDS01,COMPUTER
    PDS02,COMPUTER
    PDS03,COMPUTER
    PDS04,ACCESSORIES
    PDS05,ACCESSORIES
    PDS06,ACCESSORIES
    PDS07,ACCESSORIES
    PDS08,HARDWARE
    Product Description (Text)
    File Name:  Product.csv
    Structure     FieldName     Length     Description
         ProdID     5     Uniquely identifies a product
         Prod_Desc     Medium Text     Represents the product description
    (Navigational field)
         Language     2     Represents the language descriptor
    Sample Data
    ProdID,Prod_Desc,Language
    PDS01,Notebook Speedy I,EN
    PDS02,Notebook Speedy II,EN
    PDS03,PC Thinkbox I,EN
    PDS04,USB Adaptor,EN
    PDS05,iPhones PX2,EN
    PDS06, Stereo Kit,EN
    PDS07,Camera Connector,EN
    PDS08,USB Storage,EN
    Transactional Data
    Sales information
    File Name:  Sales.txt
    Structure     FieldName     Length     Description
         Product     5     Uniquely identifies a product
         Sales Doc     4     Sales Document number (Invoice Number)
         Calendar Year     8     YYYYMMDD format
         Channel     1     Represents the distribution channel the product was sold by
         Quantity     4     Numeric value indicating the number of each product sold on a specific sales document
         Unit     2     Refers the unit specified by the quantity
         Revenue     8     Refers the sales amount of a specific product on a specific sales document
         Currency     3     Relates the revenue currency type
    Sample Data
    Product;Sales Doc ,Calendar Day,Channel,Quantity,Unit;Revenue,Currency
    ZD_PROD,0DOC_NUMBER,0CALDAY,ZD_CHAN,ZD_QTY,0UNIT,ZD_REV,0CURRENCY
    PDS07,7389,20090705,A,95,EA,151905,USD
    PDS08,7389,20090705,A,115,EA,264385,USD
    PDS02,7473,20090706,B,55,EA,3580445,USD
    PDS01,7472,20090706,C,110,EA,604989,USD
    PDS02,7472,20090706,C,43,EA,2799257,USD
    PDS03,7472,20090706,C,75,EA,4507425,USD
    PDS04,7472,20090706,A,339,EA,301032,USD
    PDS06,7472,20090706,A,120,EA,47976,USD
    PDS01,7473,20090718,D,55,EA,3024945,USD
    PDS02,6845,20090806,B,30,EA,195297,USD
    PDS07,6877,20090807,C,800,EA,12792,USD
    PDS08,6877,20090807,C,250,EA,57475,USD
    PDS03,6912,20090812,C,250,EA,1502475,USD
    PDS04,6900,20090812,B,70,EA,6216,USD
    PDS01,6899,20090812,C,12,EA,659988,USD
    PDS04,6899,20090812,D,55,EA,4884,USD
    PDS04,7479,20090815,C,80,EA,7104,USD
    PDS05,7479,20090815,C,300,EA,70497,USD
    PDS05,6809,20090818,A,1000,EA,234990,USD
    PDS06,6809,20090818,A,130,EA,51974,USD
    PDS03,6831,20090822,C,15,EA,901485,USD
    PDS04,6831,20090822,C,500,EA,4440,USD
    PDS03,6830,20090822,C,125,EA,7512375,USD
    PDS06,6830,20090822,C,400,EA,15992,USD
    PDS04,6841,20090825,C,53,EA,47064,USD
    PDS05,6841,20090825,C,350,EA,822465,USD
    Distribution Channel
    Channel (text)
    File Name:  Channel.csv
    Structure     FieldName     Length     Description
         ChanID     1     Uniquely identifies a specific distribution channel
         Chan_Desc     Medium
    Text     Full name of each distribution channel
    (Navigational field)
    Sample Data
    ChanID, Chan_Desc
    A,Phone
    B,Fax
    C,Internet
    D,Other
    Star Schema Model:

    Potentially the issue may be the combination of actual distance and the presence of any Wi-Fi interference at the location of the AirPort Express that may be the culprit here. The bottom line is you would want the Express to be within a 25+ dB range of the Extreme to be sure that it can consistently stay connected to it.
    For more details on proper base station placement, check out the following AirPort User tip. Please post back your results.

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

  • Map cloned star schema in same BMM Layer.

    I have an ID of a group of companies and STAR SCHEMA related to billing with 8 dimensions. This STAR SCHEMA is loaded exclusively with data coming in EBS.
    But, due to the acquisition of another company, today I have the need to load data coming from a legacy system.
    To create no impact on existing and ETLs conflict of some code, we decided to clone all the star schema tables and load data from legacy.
    To not generate any inconvenience to users, we want these facts and dimensions (which have identical structures) arranged so that they appear unique.
    Example:
    fact_billing_holding
      - dimension_day
      - dimension_organization
      - dimension_vendor
      - dimension_consumer
      - dimension_transaction_type
    fact_billing_legacy
      - dimension_day_legacy
      - dimension_organization_legacy
      - dimension_vendor_legacy
      - dimension_consumer_legacy
      - dimension_transaction_type_legacy
    But you should see structure like this:
    fact_billing_holding
      - dimension_day
      - dimension_organization
      - dimension_vendor
      - dimension_consumer
      - dimension_transaction_type
    How can I implement this solution / problem?

    Hi Vjbez1!
    All facts and dimensions are identical! But all tables in this schema are duplicated and with different data.
    The data is organized like:
    dimension_organization
      - dky_organization - name_organization
                1               Company X
                2               Company Y
    dimension_organization_legacy
      - dky_organization - name_organization
               1               Company Z
    fact_billing_holding
      - dky_day - dky_organization - dky_vendor - dky_consumer - dky_transaction_type - qtd_items
         20130101        1                1            1                 1                 50
         20130101        2                1            1                 1                 70
         20130102        1                1            1                 1                 14
         20130102        2                1            1                 1                 88
         20130103        1                1            1                 1                 22
         20130103        2                1            1                 1                 10
    fact_billing_legacy
      - dky_day - dky_organization - dky_vendor - dky_consumer - dky_transaction_type - qtd_items
         20130101        1              71           31                 12                88
         20130102        1              71           31                 12                70
         20130103        1              71           31                 12                92
    In my analysis I want to see like this:
    Organization | Total
    Company X    | 86
    Company Y    | 168
    Company Z    | 250
    Fernando.

  • How to make snow flake schema to star in Business layer

    i have snow flake data model.
    anybody tell me how can i convert that snow flake to star by doing the adding multiple sources to a dimention.
    how to do the joins with 2 dimention tables in the business layer

    Hi
    we can do that for example we have dimension table that connected with another dimension table in physical layer
    solution- create one new dimension table in bmm layer and drag the columns from two dimension table which in physical layer and give the join condition it ll work,...
    Regards
    prabhu haridass

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

  • Use of complex join in BMM and Physical Join in Physical layer ?

    Hi All ,
    Why we need to use complex join in BMM layer not the Physical Join ?
    Why we need to use Physical Join in Physical layer not Complex join ?
    thanks in advance

    Hi,
    A physical join is at the physical layer and defines the join between two physical tables.
    Logical joins live at the BMM (logical) layer and define a join between two logical tables.
    The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join,
    you just tell it that there is a relationship between these two logical entities.
    when the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
    thanks,
    pramod.

  • Update physical layer - new database schema

    Can the physical layer be updated with new database schema? (Has a new table column) If so, how?
    userQHN

    Hi,
    If you import table which has changes you will get it ,if there is any new columns added.
    Regards,
    Somu

  • Joining tables across databases in OBIEE Physical Layer

    I was facing this problem of joining tables across databases in Physical layer of OBIEE admin tool.
    I had a requirement to combine two tables from 2 different databases A and B respectively. I had created one database object (OBIEE Object) in the physical layer and I had created two connection pools under that pointing to the required databases. I was able to view the data (right click on the table object --> popup menu option "View Data" ) though I had to go through the "Select connection Pool" window and select the required connection pool. I was able to join the tables and was able to complete the star schema in BMM and bring them up to the presentation layer. Conistency check was also successful. Everything went fine so far.
    But when I started building the report, I started getting error whenever I chose the table which was supposed to be queried by using the second connection pool. The error message was something like "table or view does not exist at OCI call OCIStmtExecute". I assume that this was happening because the systm was not able to understand which connection pool to choose (because there were two pools defined under one database object) and by default the server was choosing the first one. If anybody is having a different opinion or definite information about this, kindly update with your reply.
    I could resolve this problem after creating a separate database object with a separate connection pool defined under it, which points to the second database. Imported the required table under this database object. (Infact it was reverse. When I re-imported the table, OBIEE Admin tool, by default created its own database object and the connection pool separately for the imported table).
    Once this was done then I went ahead as usual by joining the tables across these two different database objects and modelling was already done (ofcourse with a little more tweaking since the mapping had to be redone between BMM and Physical layers). Now I could build the report in the reporting layer without encountering any error.
    Appreciate and welcome any further additions/updations/corrections regarding this issue(?).
    -MMishra.
    Edited by: user13483341 on Nov 29, 2011 8:20 AM
    Edited by: user13483341 on Nov 29, 2011 8:20 AM
    Edited by: user13483341 on Nov 29, 2011 8:24 AM

    Hi Deepak, Thanks for your reply.
    Appreciate if you can help me with another thread "possibility of multi-currency in OBIA 7.9.6.2 financial anlytics".
    - MMishra.

  • Aliases in physical layer

    we have created aliases for all the tables.we have joined the alias tables, way it is in the data model.
    now do i need to drag all the tables and aliases from physical layer to business layer?
    now we already join the alias tables and do in need to join the physical tables again?
    can you explain elabarately....is there any reason of using the aliases for all the tables?
    what is the benifit of creating aliases for all the tables.

    Once you created your alias tables, it is a best practice to use this for the joins. Thus, there is no need to join your original physical tables.
    Alias have a lot of advantages like:
    1. reusing the same physical table more than once to create an alias and create a completely new join
    2. you can setup multiple alias tables with different keys or joins
    3. used to convert the ER schemas to dimensional schemas in designing star/snowflake schema

  • Trunccolumn value while importing data to physical layer in RPD

    Hi All,
    While importing data from database, I want to trunc few column values so that I can put complex join, but I am not getting any link to do so.
    Can anyone suggest me that if on database, if two tables are linked by outer join, than how can I restore the same join state in Physical layer while maintaining star schema.
    Thanks in advance.

    Hi,
    I am using version 10.1.3.4.0
    This query is a select type physical table in a physical layer of the RPD
    select distinct project_no,project_name from cw_vertical_d where project_no = VALUEOF(NQ_SESSION."Project_Number")
    NQ_SESSION."Project_Number" is a session non system variable.I am trying to set this variable through a dashboard prompt ( as a request variable ).
    So when a user selects any value in the dashboard prompt then this session non system variable "Project_Number" should be set and then BI Server should fire a query with this value to pick the data from database.
    But this report is failing with "*[nQSError: 23006] The session variable, NQ_SESSION."Project_Number", has no value definition*" error.
    Don't know what is causing this?
    Regards,
    Vikas

Maybe you are looking for

  • Fixing cosmetic differences between Reader 8 and 9

    When Reader 9 starts up, by default it clicks the Highlight Fields toggle button. In Reader 8, this was unchecked by default. In general, this is a good thing. It makes it much more obvious to end-users which documents are fillable/editable PDFs, and

  • OSB 11g: Can I create an Alert Destination to call another webservice?

    Hi All, We would like to send Alert message via SMS to speified person. As we have already a web service to send SMS, can we just create an Alert Destination to call this web service to do that? Thanks for your help! Edited by: FrankieHuang on May 2,

  • Convert PDF in Image

    i need convert a pdf in a image (gif, jpeg,ect) to cut in sub-image...or how i can to cut in subimage a PDF without convert the PDF in a image (gif, jpeg,ect) Thanks

  • Different Calculations based on Hierarchy Level

    Hi Experts, I have a requirement to do different calculations of results based on the hierarchy level. For example: Level A - (total of maximums)              Level B.1 - (maximum)              Level B.2 - (maximum)                     Level C I need

  • INTERFACE : Purchase Requisition Create

    Scenario :- User giving the relevant data from a third party software. Then this software pass the data to  sap system and the Purchase Requisition is created . Then the Purchase Requisition Number is send back to the Third party software. Steps take