table of facts with different granularity

Similar Questions

• Combine data sources with different granularity in the same fact table?

  I have two operating tables 'Incident (157 columns)' and 'unit (70 Colums) '. For all the "incidents" happening there could be one or more records in the table of the 'unit '.
  
  As part of my design of data mart, I have merged the tables in one "makes the incident (227 columns)" and insert records from two tables with a join condition between them [incident. IN_NUM = Unit.IN_NUM].
  
  Is this correct, is my question? or am I mix data sources with different granularity in the same fact table. Appreciate your help.
  
  Best regards
  Bees

  Bees,
  Are the measures of the 'Incident', repeated during an incident given, in more than one record in the table of the unit? If so, then the sum (indicent.measure) will give an incorrect result?

  What is there to merge physically tables set outside OBIEE? With OBIEE you might have a table of 'facts' logic to present the user with report, which from tables separated units and Incidents and would stop the occurrence of incorrect aggregations. A common piece of modeling in the same way would be arrested in OBIEE headers and lines of command, quite common to have a logical fact 'orders' which contained the two header orders and order line, this translates into the Incidents-> relationship of units.

  To do what I mentioned, is relatively simple, you need a "Dim - Incident" at two levels, unit, mapp and Incident unique identifiers as keys to level and then use these levels to define the content of the levels correctly in your 2 tables logic sources logic "done", IE the LTS Incidents at incident level LTS units as level of units.

  Hope this helps, let us know if you get stuck.
  See you soon
  Alastair

• Table of facts with 2 keys of time, measures showing together in the same report

  Hello
  
  I use OBI EE and I have the following scenario: a fact table hold information about the inquiries. An investigation may or may not generate a date. So in my table of facts, I have two date columns: date of application information and appointments for date (and not the date of the appointment itself, but when it was actually booked).
  
  This raises a few questions. First question is: I only have a FK logic at the time table, how to create two LFKs for these 2 dates? Should I create a logical table time in MDB, as well as from another dimension of time?
  
  Second question is how to display two data items in the same report. For example, in a report summary per month I want to see the number of demands and appointment reserved for each month. They will most probably different numbers and refer to different lines in the database. What is the best way to this model in the MDB?
  
  For example, in October, there are 10 questions, 8 of them were converted into appointments as well as 3 requests for information made in September. Thus, the report is expected to show for October: number of inquiries: 10, number of nominations: 11 (October 8 + 3 from September)
  
  Sorry if this is a basic question, but I couldn't find examples of this scenario.
  
  Thank you
  Luis

  Hi Luis,.

  I think you have the same problem as 'The phantom', three days ago. I guess that my solution also works for you:
  How to create a common hieracrhy calendar?

  Kind regards
  Stijn

• Answers OBIEE 10G - 2 facts with different dimensions

  For example

  fact 1: sales.

  Of dimensions: Branch, time, product

  fact 2: promotions:

  Of dimensions: business, time, promotional code

  These two facts and related dimensions are in Star patterns.

  Only two made run OK.

  What I want:

  Branch, time, promotional code, Sales, promotions

  In SQL, it would be something like (pseudocode):

  Select t1.*, code t2.promotion, t2.promotions

  Of

  (

  Select the branch, the time, the sales

  Branch, the time, the sales

  where - joins and filters

  ) t1

  left outer join

  (

  Select the branch, promotions, promotional code

  direction, time, promotional code, promotions

  where - joins and filters

  ) t2

  On t1.branch = t2.branch

  and t1. time = t2.time

  I don't know what is doable in OBIEE, or should I use SQL?

  Try to create a fact in MDB with 2 LTS: sales and Promotions and set the level-based measures.

  The two facts sharing the dimensions of the branch and time (consistent dims), OBIEE will join the facts with these columns.

• the analysis of a word table of ms with different numbers of columns for each row

  I'm reading in a MS Word table that contains 20 lines, each with a different number of columns.  I have to iterate over each line then I iterate on each column of the row and read his text.  I don't know a way to find out how to stop an iteration on the columns.  Is a property or a method which tells you the number of columns in a specific line for a table in MS Word?

  ID says:

  I'm reading in a MS Word table that contains 20 lines, each with a different number of columns.  I have to iterate over each line then I iterate on each column of the row and read his text.  I don't know a way to find out how to stop an iteration on the columns.  Is a property or a method which tells you the number of columns in a specific line for a table in MS Word?

  For each row, use the count property of cells. Since there a number of subject lines is the number of columns.

  Ben64

• Tables of Images with different heights, causing the removal of Menu

  OK, I posted this issue in the Council of LabVIEW before I realized that it was associated with Vision.  I made some progress, narrowing of the cause, so I thought it would be best to start a new post here.  Here is the original post:

  http://forums.NI.com/T5/LabVIEW/blank-pop-up-menus/m-p/3281194#M958610

  I'm running into a problem with all of my menus of LabVIEW to shutter when I create arrays of images where the heights do not match.  I have attached a vi I created to illustrate the issue.  In this document, I take a starting image and then extract subsets of it.  Because I don't know how much I'll have to check out until the moment of execution, I'm subpictures in an array.  What I've discovered, is that if the heights of subpictures don't match, I get a weird bug that causes all the menus in LabVIEW empty.  This includes all right click pop up in the façade, block, or Project Explorer diagram and drop-down selections as for enums and ring controls.  It also includes the file menu at the top of the window.

  Rerun this vi with subpictures equivalent height or no subpictures corrects hidden menus.  In addition, running IMAQ Dispose (with Boolean true of images) corrects the problem.

  I'm relatively new to the Vision, so I don't know if I'm missing something basic, but please let me know what you think.  Is there a better way to do this?

  Thank you

  Tim

  Hi Tim,.

  Thanks for reporting this problem. I have reported as a bug.

  I recommend using a Cluster or the KING for manual zoom toolbar. If you want to use an array, each element of the array must maintain the same amount of zoom. (Similar to each LED in a table must have the same color.)

  Sorry you came across this bug.

  Kind regards

• Join the Grains with different facts

  Hello
  
  We have a requirement where we have two facts with different grains
  
  DEPT_FACT - contains (Dept_Id, Dept_Name, recipes)
  EMP_FACT - contains (Emp_Id, Dept_Name, Is_Current_Employee)
  
  Some examples of data
  
  DEPT_FACT
  ========
  1 Sales_Dept 100 000
  Manufacturing_Dept 2 200 000
  
  EMP_FACT
  ========
  Sales_Dept 100 Y
  200 Sales_Dept Y
  Sales_Dept 300 N
  Manufacturing_Dept 400 N
  500 Manufacturing_Dept Y
  Manufacturing_Dept 600 N
  
  Our requirement is to create an OBIEE report that shows the * "' recipes / number of current employees in Department BY Department" * "
  
  The above example should demonstrate
  Sales_Dept = > $ 50,000 (100 000 / 2 current employees)
  Sales_Dept = > $ 200,000 (200 000 / 1 current employee)
  
  Any suggestions on how this can be done?

  Hello

  Try this code in your fx

  Recipes/case when current_employee = 'y' then count end (emp_id by department_name)

  Concerning

  NGO

• 'For' loop with a different number of iterations. Second, the auto-indexation of the tables with different sizes is done. It can affect the performance of the Vi?

  Hello

  I have a loop 'for' which can take different number of iterations according to the number of measures that the user wants to do.

  Inside this loop, I'm auto-indexation four different 1 d arrays. This means that the size of the tables will be different in the different phases of the execution of the program (the size will equal the number of measures).

  My question is: the auto-indexation of the tables with different sizes will affect the performance of the program? I think it slows down my Vi...

  Thank you very much.

  My first thought is that the compiler to the LabVIEW actually removes the Matlab node because the outputs are not used.  Once you son upward, LabVIEW must then call Matlab and wait for it to run.  I know from experience, the call of Matlab to run the script is SLOW.  I also recommend to do the math in native LabVIEW.

• Reg: With the help of several tables of facts in the RPD!

  Hi all
  
  Can I get help with the following scenario?
  
  We use OBIEE 11 g.
  We have a report that uses 1 single fact table to retrieve data and it must be hell a lot of time to display the data in the report.
  
  My question is is there a way to show the performance of the report if divide us the data in table 1 to 2 fact tables and the report uses them 2 made tables.
  Are there other ways of finalization of the report for better performance.
  
  Thanks for the help in advance!
  
  Ajay.

  Hi Ajay,

  Follow these steps for tuning;
  1. try to adjust the SQL query generated first by the report, and then make the necessary changes. (Put index on the column that is required so that your query is scanning the index instead of the whole table)

  2. you can try to create the agg fact table and use agg navigation to improve performance. (This is to reduce the data set on which sql is triggered)

  3. you can try to create partitions on the table of FACTS in the comic book, and so held the partitions are queried according to the filters.

  4. in the last if all the foregoing does not resolve your query, you can try to divide the FACT table in two or more depending on your decision and then use fragmentation content in the MDB of the RPD layer if it will strike appropriate tables depending on whether you declare.

  Mark Correct/utile so this can help.

  Good luck
  Kashi

• Two tables with different values of basic on an analysis filter

  Hi guys,.
  
  Let assume that I have an analysis with columns: group_id and sales.
  On this basis I would like to create two tables: table1 where group_id = 1 and table2 where group_id = 2.
  
  OBIEE is able to do?
  
  Kind regards
  Slavi

  Hi Slavi,

  You can do it in a single analysis, but you have to have the column with group_id twice.

  Bring, group_id_1, group_id_2 (same column), sale

  Now in table 1.

  bring group_id_1, sales

  Then in the selection steps for group_id_1-> select members-> Action choose keep only-> choose the value of the filter 1

  This will filter the table 1 with group_id 1

  In table2 group_id_2 porter, sales

  Then do the same step for group_id_2 with the value 2.

  You now have two reports with different filter in the same report.

  If you want you can keep the same name column for the two columns group_id, I just kept group_id_1, group_id_2 for easy reference.

• Dimension table is associated with N number of fact tables

  Salvation by the Expert,
  
  In the case of a fact table star schema is associated with the N dimension tables, it is possible to join a table of size N with the number of tables of facts... Please let my know your suggestion...
  
  
  Thank you to
  
  Harish

  Hello

  Yes, it's quite possible. A dimension can join the many fact table. For ex: temporal dimension and w_employee_d are classic examples of this behavior.

  Kind regards
  Sandeep

• How to model in the tables of aggregate SPR with different years of data

  Can someone let me know how to accomplish the following in OBIEE?
  
  I want to create a table of logical facts with multiple sources of logical table. I have a global table that only stores the data of the current year. OBIEE, if a user creates a report using data from the current year, I hit the global table of the query. However, my facts database table stores data annually. If a user creates a report using data from previous periods, I want the application to hit the base of facts table.
  
  And if you're curious, that the aggregate contains only data of the current year as the ETL needs to do a full charge every night because of the complexity. The high volume of data and the amount of time it takes to complete this comprehensive way we only have time to fill in the data of the current year.
  
  Thanks in advance.

  Hello

  See Fragmentation in the link below

  http://108obiee.blogspot.com/2009/01/fragmentation-in-OBIEE.html

  Kind regards
  Sandeep

• Impossible to use two af:tables with different colors (skins)?

  Im trying to configure the Siebel self-service application and customize the counting. I have a few problems, because I need to show two af:tables on the same page, but with different colors. One with black background and white text (header and body) and the other with white background and black text. I tried to use styleClass: are, but the css settings defined for the table of the af are the substitution of those mentioned in the style sheets.
  
  Anyone with an idea how to solve this problem?
  
  Thank you
  / Jon-Erik

  Hello

  If the styleClass name is table1 then the skin selector would be something like

  .Table1 af | table

  mul afTable.af: table

  I don't see how this can be overloaded. If you hypothesis is that the style class reference must be to a definition of CSS on the page, then indeed, it does not. The styleClass name is an identifier of type named for the skin component and is used to describe more the component skin

  Frank

• Problem with populating a table of facts, of dimension tables

  My goal is there are 5 dimensional tables created
  
  Student-> primary key s_id, upn(unique pupil no), name
  Rank-> key primary g_id, grade, exam_level, values
  Object-> key primary sb_id, subjectid, subname
  School-> key primary sc_id, schoolno, school_name
  year-> y_id primary key, year (like 2008)
  
  S_ID g_id sb_id, sc_id, y_id are sequences
  

  select * from student;
  S_ID UPN FNAME COMMONNAME GENDER DOB
  ==============================
  9062 1027 MELISSA ANNE       f  13-OCT-81
  
  ...
  
  9000 rows selected

  select * from grade;
        G_ID GRADE      E_LEVEL         VALUE
  ---------- ---------- ---------- ----------
          73 A          a                 120
          74 B          a                 100
          75 C          a                  80
          76 D          a                  60
          77 E          a                  40
          78 F          a                  20
          79 U          a                   0
          80 X          a                   0
  ...
  18 rows selected

  It's basically the dimensional point of view
  
  According to the given specifications, now need to create a table of facts like facts_table that contains all the primary keys of tables IMG as foreign keys in it.
  
  The problem is when I say, I'll look at an example of smaller that the reality of dimension tables 5 let say there are 2 student dim tables, rank with s_id, g_id as the p key.

  create materialized view facts_table(s_id,g_id)
  as
  select  s.s_id,g.g_id
  from   (select distinct s_id from student)s
  ,         (select distinct g_id from grade)g

  The result is a massive duplication as there is no join between two tables. But basically there is no common things between the two tables to join, how to solve?
  
  Think of it as when I do for 5 tables the amount of duplication being involved, why there is not enough tablespace.
  
  I was hoping that if there is no other way then don't create a fact table with just a column at the start
  

  create materialized view facts_table(s_id)
  as
  select s_id
  from student;

  then

  alter materialized view facts_table add column g_id number;

  Then fill this column g_id fetching all the grade table g_id values using some sort of loop, although we shouldn't use pl/sql, I don't know if it works?
  
  All of the suggestions.

  TROPPER,

  Your information, I have tried this test see if it works for you

  DROP TABLE fact_1 CASCADE CONSTRAINTS;
  
  CREATE TABLE fact_1 (
     s_id NUMBER NOT NULL,
     sc_id NUMBER NOT NULL,
     g_id NUMBER NOT NULL
  )
  LOGGING
  NOCOMPRESS
  NOCACHE
  NOPARALLEL
  MONITORING;
  
  ALTER TABLE student_1
   DROP PRIMARY KEY CASCADE;
  DROP TABLE student_1 CASCADE CONSTRAINTS;
  
  CREATE TABLE student_1 (
     s_id NUMBER NOT NULL,
     student_id NUMBER,
     studentname VARCHAR2 (40 BYTE)
  )
  LOGGING
  NOCOMPRESS
  NOCACHE
  NOPARALLEL
  MONITORING;
  
  ALTER TABLE school
   DROP PRIMARY KEY CASCADE;
  DROP TABLE school CASCADE CONSTRAINTS;
  
  CREATE TABLE school (
     sc_id NUMBER NOT NULL,
     school VARCHAR2 (40 BYTE),
     schoolname VARCHAR2 (100 BYTE)
  )
  LOGGING
  NOCOMPRESS
  NOCACHE
  NOPARALLEL
  MONITORING;
  
  ALTER TABLE grade
   DROP PRIMARY KEY CASCADE;
  DROP TABLE grade CASCADE CONSTRAINTS;
  
  CREATE TABLE grade (
     g_id NUMBER NOT NULL,
     e_level VARCHAR2 (40 BYTE)
  )
  LOGGING
  NOCOMPRESS
  NOCACHE
  NOPARALLEL
  MONITORING;
  
  CREATE UNIQUE INDEX fact_1_u01
     ON fact_1 (s_id)
     LOGGING
     NOPARALLEL;
  
  CREATE UNIQUE INDEX fact_1_u02
     ON fact_1 (sc_id)
     LOGGING
     NOPARALLEL;
  
  CREATE UNIQUE INDEX fact_1_u03
     ON fact_1 (g_id)
     LOGGING
     NOPARALLEL;
  
  CREATE UNIQUE INDEX grade_pk
     ON grade (g_id)
     LOGGING
     NOPARALLEL;
  
  CREATE UNIQUE INDEX school_pk
     ON school (sc_id)
     LOGGING
     NOPARALLEL;
  
  CREATE UNIQUE INDEX student_1_pk
     ON student_1 (s_id)
     LOGGING
     NOPARALLEL;
  
  ALTER TABLE fact_1 ADD (
    CONSTRAINT fact_1_u01
   UNIQUE (s_id),
    CONSTRAINT fact_1_u02
   UNIQUE (sc_id),
    CONSTRAINT fact_1_u03
   UNIQUE (g_id));
  ALTER TABLE student_1 ADD (
    CONSTRAINT student_1_pk
   PRIMARY KEY
   (s_id));
  ALTER TABLE school ADD (
    CONSTRAINT school_pk
   PRIMARY KEY
   (sc_id));
  ALTER TABLE grade ADD (
    CONSTRAINT grade_pk
   PRIMARY KEY
   (g_id));
  ALTER TABLE fact_1 ADD (
    CONSTRAINT fact_1_r01
   FOREIGN KEY (s_id)
   REFERENCES student_1 (s_id),
    CONSTRAINT fact_1_r02
   FOREIGN KEY (sc_id)
   REFERENCES school (sc_id),
    CONSTRAINT fact_1_r03
   FOREIGN KEY (g_id)
   REFERENCES grade (g_id));
  ALTER TABLE fact_1 ADD (
    CONSTRAINT fact_1_r02
   FOREIGN KEY (sc_id)
   REFERENCES school (sc_id),
    CONSTRAINT fact_1_r03
   FOREIGN KEY (g_id)
   REFERENCES grade (g_id),
    CONSTRAINT fact_1_r01
   FOREIGN KEY (s_id)
   REFERENCES student_1 (s_id));
  
   -- This should be the sequence you will loading data
  
  INSERT INTO student_1
  VALUES (3, 1, 'Tropper A');
  
  INSERT INTO school
  VALUES (3, 'new school', 'new school name');
  
  INSERT INTO grade
  VALUES (4, 'a');
  
  INSERT INTO fact_1
  VALUES (3, 4, 4);
  
  commitl
  

  Concerning

• Problem: two tables of facts and a dimension in accordance with

  Hello world!
  
  I need solve this situation:
  
  I have two fact tables, say F1 and F2, which are both linked to D1, my dimension in line
  I just need to select fields of D1, but I know that, when querying, OBIEE links to a table of facts anyway... How is it chooses the fact table? In other words, if I want to only fields D1, not the system also queries of F1 or F2? What is a random choice?
  
  Is there a way to "force" this choice, saying the system for example to choose only from F1?
  
  Is there a work around to resolve this situation? Remember, I only need fields D1.
  
  Thank you!!

  The solution to your problem is "column name".
  Go to the layer of presentation and double click on your domain. Then you will see name column option. Click on set. give the corresponding column actually it (in your column of fact give deal F1)

  References: http://oracle-bi.siebelunleashed.com/articles/implicit-fact-column/
  Thank you
  GSR

  Published by: GSR on 20 March 2012 15:22