Time Related Dimension(table) in communication data model

Hi,
The most common and important thing for a communication data model to me is time metrics.
Things like mean up time, or mean down time are common KPIs we are tracking.
To make this model efficient, we need to create a time dimension can precisely and efficiently to calculate the mean.
How do we create such time dimension with common year, quarter, month, date, and time, while with UTC to local conversion?

Not sure i follow your question.
Can you give some example of the KPIs you mentioned - Mean up time and Mean down time with examples -- as detailed as possible (fact data details)?
On the face of it, it looks like these KPIs should be Calculated Measures involving Time expressions on date columns (date datatype =day+time infomation present in source columns) but nothing in it which needs a customized time dimension. Maybe not out of the box but very much doable in analytical layer (either using olap or relational rpd). So it should be do-able without needing any changes to the default time dimension available with OCDM.
HTH

Similar Messages

  • Unable to join 3 fact tables in obiee data model.

    Hi,
    I am unable to join the 3 fact tables in obiee rpd. If I join with 2 fact tables I got the data in repors, Once I add the one more fact table and join with related dimensions, I am getting nodata error. I am following all joins keys as per datamodel, I am able to see the data in database. anyone pls give me the solution. Thanks in advance.
    Edited by: 1007582 on May 23, 2013 2:17 AM

    Can you please give some more detail as in what you have model in RPD;
    For example, if There are 3 Fact table F1, F2, F3 and two Dimesion Confirmed_D1, Non_Conf_D2. Confirmed_D1 is joined to all three fact tables and Non_Conf_D2 is joined to F2.
    Now to implement this model we have to set the logical content level in BMM layer for Non_Conf_D2 in F1 & F2 to Total*. After this only we can report on Confirmed_D1, Non_Conf_D2, F1, F2, F3 whithout any error.
    Sometime join with multiple table can also result in No Data, since the join conditions filters out the result data.
    Please mark helpful or correct.
    Regards,
    Kashinath

  • Can I add more tables into existing Data Modeler

    My Data Modeler has been generated by SQL Developer, it contains 68 tables. Later I would like to add more tables into my current model. Is there any way I can add more tables into my current model without creating a new one from the scratch? Thanks for your help.
    Kevin

    Hi Kevin,
    you can add new tables using File>Import functionality - you can import from database or DDL scripts.
    Working in SQL Developer you can drag tables from SQL Dev browser and drop them on relational diagram. If Ctrl key is pressed while dropping then subordinate tables also will be added to the model.
    Here you can find tutorials http://apex.oracle.com/pls/apex/f?p=44785:2:0:FORCE_QUERY::2,RIR,CIR:P2_TAGS:Data%20Modeler
    Philip

  • Can anyone describe how to cut and paste table columns in Data Modeler?

    A number of times I have tried using the copy and paste columns functionality in Data Modeler, but in all circumstances when I've copied a set of columns from a table (by highlighting the column set and pressing the copy columns button), opened a new table, and pressed the paste columns at the end button, nothing has happened. is there some unintuitive thing that I need to do?

    Ok, thanks.
    I see I left "Copy" out of the first reply I sent.
    1. Create a table or tables, say tables A and B.
    2. Expand the table which has the columns you want to copy, say table A, in the browser
    3. Shift (or ctrl) select the columns and select COPY from the context menu.
    4. Click in the table you want to copy to, say table B, in the diagram and right-click to use the context menu , select paste
    or select the table B in the browser and right-click, select paste.
    Are you using the copy in the menu?
    There was a bug in our Early Adopter that required you continued to hold the keys, but this has been addressed - you can read this thread to see how things were handled there: Re: Data Model: set of columns

  • What kind of real time problems and issues arise in Data Modelling

    Hellooo experts,
    I am not a BW expertise, so just want to gather some knowledge on Problems and issues related to DATA MODELLING, if any body have a document or a link can you please snd it to [email protected] or reply to this post. I promise to reward you for proper answers hope this is the way i say thanks for your help.
    kishore

    hi kishore,
    The first and most important problem is to understand <b>Clients requirement</b>. Clients even some time not aware of how to utilize efficiency of BW, as they are very much use to with traditional SAP R/3 reporting. So most of time we have to suggest options to client.
    If we come to technical aspect, than identifying <b>Key Figures and Characterstics</b> is the most important task. And how you map that to <b>available infoobjects</b>. Attributes also plays major roles, like which attributes is better to use as navigational one and which as exclusive attribute.
    Their is long list for data modelling issues, its better you refer either <b>Mastering BIW</b> book by Mac'Donalds. And SAP Help Library is also having good material.
    regards,
    kamaljeet

  • If I have PowerPivot Connection with 8 tables in the data model, can I extract the Command Text for each with VBA?

    I have a data model with a single PowerPivot connection to an Oracle database. This model had eight tables in it which all use the same "Existing Connection".  I can get the Query from the first Table connection using Command Text, however,
    I do not know how to get the CommandText of each of the additional tables associated with the same connection. 
    With wsConnList
    .Cells(lngRow, 1).Value = wbTarget.Connections("Conn").Name
    .Cells(lngRow, 2).Value = wbTarget.Connections("Conn").OLEDBConnection.CommandText
    End With
    Thanks, Barbara

    Any suggestions for the amazing Barbara on this topic?
    Barbara, you can also ask the BI Advisors if we're not having luck here.
    Thanks!
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Definitions of time-related fields of usage tracking data

    Hi all,
    After reading the related documentations on usage tracking, I'm still confused about the true meaning of the following fields:
    COMPILE_TIME_SEC The time in seconds required to compile the query.
    C UM_DB_TIME_SEC The total amount of time in seconds that the Oracle BI Server waited for back-end physical databases on behalf of a logical query.
    TOTAL_TIME_SEC The time in seconds that the Oracle BI Server spent working on the query while the client waited for responses to its query requests.
    START_TS The date and time the logical query was submitted.
    END_TS The date and time the logical query finished. The start and end timestamps also reflect any time the query spent waiting for resources to become available.
    My questions are:
    1. Is TOTAL_TIME_SEC = C U M_DB_TIME_SEC + COMPILE_TIME_SEC? Why are there cases where C U M_DB_TIME_SEC > TOTAL_TIME_SEC ?
    2. I've logged cases where (END_TS - START_TS) > TOTAL_TIME_SEC. Why would this happen?
    Could someone clarify the meaning of these fields for me please? Thanks very much!!
    =================
    I have logged the following data with usage tracking, posting here as examples:
    1.
    compile_time_sec = 0
    c um_db_time_sec = 23
    total_time_sec = 12
    start_ts = 18-AUG-09 (14:15:47)
    end_ts = 18-AUG-09 (14:16:00)
    end_ts - start_ts (in sec) = 13
    cache_ind_flg = N
    num_cache_hits = 0
    num_cache_inserted = 1
    2.
    compile_time_sec = 0
    c um_db_time_sec = 125
    total_time_sec = 110
    start_ts = 21-AUG-09 (15:45:37)
    end_ts = 21-AUG-09 (16:47:35)
    end_ts - start_ts (in sec) = 3718
    cache_ind_flg = N
    num_cache_hits = 0
    num_cache_inserted = 0
    3.
    compile_time_sec = 0
    c um_db_time_sec = 1252
    total_time_sec = 932
    start_ts = 24-AUG-09 (17:23:40)
    end_ts = 24-AUG-09 (17:49:27)
    end_ts - start_ts (in sec) = 1547
    cache_ind_flg = N
    num_cache_hits = 0
    num_cache_inserted = 0

    Check out DOC ID 973090.1 in metalink.

  • M:N relationships within a dimension: Standard process vs. BI Data model

    Hi,
    I just completed a review of the u201CMulti-Dimensional Modeling with BIu201D from this link:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84 and I have a quick question here:
    On page 36 of this link, the author noted that
    u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
    i.e. my understanding is that, based on Standard Process it is NOT possible to place two characteristics in M:N relationships in the SAME dimension but with BI Data Model, this, the author points out  is possible
    u201Cdue to the usage of surrogate keys (DIM-IDs) in the dimension tables allowing the same material several times in the dimension tableu201D  i.e. although material is the unique key of the dimension.
    1.
    What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
    2.
    It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
    What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
    3.
    Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
    u201CIf you can avoid compounding - do it!
    Compound attributes always mean there is an overhead with respect to:
    Reporting - you will always have to qualify the compound attributes within a query
    Performance
    Compounding always implies a heritage of source systems and just because it makes sense within the
    source systems does not necessarily mean that it will also make sense in data warehousing.u201D
    Thanks

    Hi Amanda.......
    In a dimension table, any number of semantically related dimension attributes are stored in a hierarchy (parent-child relationship as a 1:N relationship). If an M:N relationship exists between dimension attributes, they are normally stored in different dimension tables.
    I checked the document.........
    On page 36 of this link, the author noted that
    u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
    1.
    What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
    Here the first thing that I want to tell u is that............the diagram shown here is Classic Start Schema............since Extended Star Schema will never store Master data in Dimension tables.........it stores Masterdata in seperate Master data tables..........and nowadays..............Classic Star schema is obsolet.......Dimension table will only store Dimension id and SID......
    Now the Standard process is that..........anything which is Describing a master data..........can be added as an Attribute of that master data.......
    Suppose........Employee is the Masterdata.then Ph no can be one of the Attribute of this master data......
    So this the Standard Process.........but this cannot be followed every time.........why........already explained.....
    2.
    It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
    What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
    Bcoz ..........we use compounding Characteris tic to define the Master data uniquely.........and we load compounding Characteristic seoerately...which is independent of the Master data........ie......compounding Characteristic there is a seperate master data tables...........so ..........problem resolved......
    3.
    Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
    u201CIf you can avoid compounding - do it!
    Compound attributes always mean there is an overhead with respect to:
    Reporting - you will always have to qualify the compound attributes within a query
    Performance
    Compounding always implies a heritage of source systems and just because it makes sense within the
    source systems does not necessarily mean that it will also make sense in data warehousing.u201D
    For Compounding Characteristic............u hav to laod the Coumpoundede master data seperately..which is a overhead...........moreover while query execution......two tables will be accessd..which may result a performance issue.......Performance can be affected when compounded characteristics are used extensively, particularly when a large number of characteristics are included in a compounding. In most cases, the need to compound is discovered during data modeling.
    Regards,
    Debjani.........

  • Tabular data model: Query keeps timing out when attempting to Edit Table Properties

    Tabular data model (SSDT)
    Problem: I have a table in tabular data model using a SQL Query for a data source. The query in question requires about 3 minutes to regenerate. When I open Edit Table Properties for this data source the query times out and I get an error (see below): "
    Failed to retrieve data from udvTrainJobReportsData. Reason: Query timeout expired"
    This seems to happen anytime I use a query that takes longer than a couple of minutes to regenerate. Anyone have an idea on how to get around this. Is there a timeout setting somewhere in tabular data model that can be increased?
    Thanks...

    Hi ManikantM,
    According to your description, you query keeps time out when edit table properties. Right?
    In this scenario, this error is thrown when connection or query execution exceeds the time out value. Please try to import this table and then increase the connection time out seconds.
    We can increase to ExternalCommandTimeout in Analysis Server Properties. Please refer to link below:
    http://aniruddhathengadi.blogspot.in/2012/07/ole-db-error-ole-db-or-odbc-error-query.html
    Please also refer to a similar thread below:
    https://social.technet.microsoft.com/Forums/office/en-US/3f83a26b-71c6-462e-8b90-2ce2ce0b9465/powerpivots-2010-query-keeps-timing-out-when-attempting-to-edit-table-properties?forum=excel
    Best Regards,
    Simon Hou
    TechNet Community Support

  • Tables in SQL DEVELOPER DATA MODELER seem to be read only and have a chain symbol in the upper left

    I have a bunch of tables in my data model.  I have three relational models defined in this file.  In one of the models, all the tables seem to be read only.  They all have a chain in the upper left hand corner of their box.
    I am not using version control, so that are not checked in or anything like that.
    How do I unlock these objects?  Why to they appear to be locked?
    Thanks

    It looks like you've linked tables across multiple models or designs.
    Does this look about right?

  • Powerpivot Error on Refresh -- "We couldn't get data from the data model..."

    I'm using Excel 2013 and Windows 8.1.  I have a spreadsheet I've been using for over a year, and I've just started getting this error message when I try to refresh the data.
    "We couldn't get data from the Data Model.  Here's the error message we got:
    The 'attributeRelationship' with 'AttributeID' - 'PuttDistCat9' doesn't exist in the collection"
    Any idea how I can fix this problem?  I haven't changed anything related to that particular attribute.  All the data is contained in separate sheets in the workbook, so there are no external sources of data.
    Thanks.
    Jean

    Thanks for all the suggestions.
    I found a slightly older version of the spreadsheet that still refreshes properly, so I don't think I have any issues with the version of Excel or Power Query.  (I've had this same error before, and I believe I applied the hotfix at that time.)
    I think this problem started after I updated a number of the date filters in the pivot tables.  I haven't made any changes to the data model, and the only updates I've made were to add data (which I do all the time), and to change the date filters on
    the pivot tables.
    As suggested, I added a new pivot table querying one table (the table with the attribute that shows up in the error message), and it worked fine.  I can also refresh this pivot table.
    Then I tried adding a pivot table which went against several tables in the data model (including the table in question).  The pivot table seemed to return that data properly.  However, when I tried to refresh it, I got the same error message ("we
    couldn't get data from the data model..."). 
    Dany also suggested running the queries one at a time to see which one is in error.  Without checking all the pivot tables, it appears that any which use the table "HolePlayedStrokes" generate the error (this is the table with the attribute
    mentioned in the error message).  Pivot Tables without that particular table seem to refresh OK.  Unfortunately, that is the main table in my data model, so most of the pivot tables use it.
    Any other suggestions?  I'd be happy to send a copy of the spreadsheet.
    Thanks for all the help.
    Jean

  • Multiple Fact Tables and Dimension Tables

    I have been having some problems trying to model the data from Oracle E-Business Suite maintenance. I will try to give the best description of how the data is held in the tables. The structure is such that a work order can have multiple operations and an operation can have multiple resources as well. I believe the problem comes in the fact that an operation doesn't necessarily need to have a resource. I could not attach an image so I have written out an example below. I am not saying this is right or that it works, but just to give you an idea of what I am thinking. The full dimension would be Organization -> WorkOrder -> Operation -> Resource. Now, the fact tables all hold factual data for the three different levels, with the facts being at each corresponding level. This causes an obvious problem in combining the tables into one large fact table through the ETL process.
    Can anyone tell me if they think this can be done? Am I way off? I am sure that there is a solution as there always is but I have been killing myself trying to figure this one out. I currently have the entire solution in different Business Models. I would like however to be able to compare facts from multiple areas such as the Work Order level and the Resource level.
    Any help is greatly appreciated. I realize that the solution may also require additional work on the ETL side so I am open to any and all suggestions.
    Thank you in advance for anyones time. :)
    Dimension Tables
    WorkOrder_D
    Operation_D
    Resource_D
    Organization_D
    Fact Tables
    WorkOrder_F
    Operation_F
    Resource_F
    Joins
    WorkOrder_D -> Operation_D
    Operation_D -> Resource_D
    WorkOrder_D -> WorkOrder_F
    Operation_D -> Operation_F
    Resource_D -> Resource_F
    Organization_D -> WorkOrder_D
    Organization_D -> Operation_D
    Organization_D -> Resource_D

    Hi,
    Currently the dimension table is taken as a simple logical table in rpd as it does not have have any levels or hierarchy.
    Its a flat dimension. Can you guide me how can I implement a flat dimension in OBIEE? Because this dimension is taken as simple logical table
    I am not able to set appropriate level for fac tables. This dimension does not appear in the list of dimensions.

  • Data Modeler - Naming Conventions

    I was using Oracle Designer for several year.
    This product could drive you crazy because sometimes, but the strength was in my opinion the datamodelling part.
    It saved you a lot of time because you kept stuck to the logical model generated your relational model and had all scripts satisfying all naming conventions you needed.
    In Data Modeler i really miss the naming conventions and can't understand some parts, sometimes somebody here can help me if i have overseen something or it is just not implemented.
    Naming conventions as example:
    We work with surrogate keys.
    Two well known tables - Employees (abbreviation EMP), Departments (abbreviation DEP)
    They have one relation 1:N one department has many employees
    In Designer i would define the EMPLOYEE entity, would set the table-abbreviation, the attributes and the primary key.
    The same with DEPARTMENT. I would design it WITHOUT any column for the foreign key constraint.
    Then i would create a relation between this two tables.
    Last step is to generate the relational model.
    a) Designer automatically adds ID as surrogate key on every table (you could configure that, it was dependent on a domain)
    b) it automatically adds the table abbreviation as prefix on every column (even here it's configurable)
    c) it automatically adds the a foreign key column in the child table with the prefix of the master table (f.e. EMP_DEP_ID or DEP_ID if you prefer not to prefix every column... what i do)
    It was really easy to get your scripts.
    Things i don't understand in Data Modeler:
    In a logical model you should design entities, attributes and relations and don't mess around with FK-columns.
    Is there any support for surrogate keys? I don't wanna add an ID manually with every table.
    In Data Modeler an additional COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
    Data Modeler to prefix it automatically. The name can just be changed in the Relational View afterward.
    P.S.
    Surrogate Keys.... There are some pros and cons for/against this out there. I have seen a lot of Oracle Projects and in all except one i always had a surrogate key column. It really makes life
    easier. In the one no-surrogate-key-project we began to add surrogate keys after a while...

    COLUMN(!) is added with every Foreign key relation, i could live with that, but there is no way to tell
    Data Modeler to prefix it automaticallyLook at "General options>Naming Standard>templates" - you can define template for FK columns/attributes and then apply them for whole relational/logical model using "Apply Naming .." functionality from pop-up menu in the browser. For Logical model (FK attributes) - you also need to clear related setting at "General options>Logical>Keep as the name of originating attribute".
    Templates are also used when objects are created, thus when new FK is created, then templates are used to generate name for foreign key and FK columns. Well you have to define table and column abbreviation in order to get them used in generated names - Re: Data Modeler: Naming
    There is no support for surrogate keys in current release.
    Philip

  • Fact columns in dimension table

    In OBIEE, Can we use a fact column in related dimension table in case this column is just an description column? Yup I know that use fact columns in fact and dimension in dimension.. But what exactly will be issue if we do this? I observed it in one model.. No data connection was there to test..

    Hi Hari,
    Why can't you create two tables in BMM one is as FACt and DIM and place all description columns in dim and measures in fact?
    this way you would achieve Star Schema in BMM
    http://www.varanasisaichand.com/2012/04/fact-and-dimension-from-single-source.html  (2nd approach)
    thanks,
    Saichand

  • Data Model won't open

    I have created a PowerPivot data model using Excel 2013.  It runs fine on my computer (the one where I built it), but will not open in other computers.  All computers have the same 64 bit version of PowerPivot 2013 and run on Windows 8.
    The primary data model table contains about 170,000 rows, 20 raw data columns, 2 calculated columns, 30 calculated fields (measures), and there are also a couple of small linked-back data tables with relationships to the primary
    table.  The data model takes approximately 5 minutes to refresh using my computer when I click 'Update All' (pertains to linked-back tables) on the PowerPivot ribbon in Excel.  99% of that 5 minutes is spent reading the data.  However the
    refresh time is not really my concern, as the data model will not open at all on any other computer.
    It might be worth mentioning that my data model utilizes the 'stdev.p' function (new to PowerPivot 2013).  However, I would not expect this to matter since all computers I am trying to run on have PowerPivot 2013.

    User, are you still looking for the answer?
    Thanks!
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

Maybe you are looking for