Universe creation- without fact tables

Hi All,
I want to create a universe , but the problem is I don have any fact tables in my database. So in which schema i can create a universe?
I have one Master table with all Primary Key? So i thought of mapping this master table with other Dimansion table?say any advantages/ disadvatages of star Schema?

Hi,
I don't want to talk about adavantages/diadvantages of star schema as if would take time.
My recommendation is that if you cannot change the database schema of your customer you can build a universe on any database schema and use all features that to obtain the best universe you can have:
<ul><li>Create table aliases
<li>Create contexts if needed
<li>Create derived tables to avoid contexts or complex joins
<li>etc
I already had, in the past, to build a universe on schema that contained only a big table and I successfully created a universe and used it.
Didier

Similar Messages

Mutliple fact tables

Hi,
I have a requirement to build a universe having 12 fact tables and 13 dimension tables. Can anyone suggest me how to build the universe whether to go with one universe or multiple universes. Coming to contexts can we have 10 contexts for 12 fact tables. Please provide me the possible solution with the best way to come out.
Regards,
Jc

Hi JC,
Your requirement is quite complex.
Here is my suggestion :
-     Since Universe have 12 fact and 13 dimension table, it will create good number of Loops, Chasm trap.
-     To resolve this, we can use combination of Alias and Context or explicitly Context only.
-     Letu2019s resolve with Context. Since you have 12 facts, have minimum 12 context i.e one context per fact table.
-     First resolve the loops with context. Avoid one context having more than one fact table.
Thanks,
Sushil

Steps to create Universe without using Fact Table

Dear All,
i am confronting with a problem by creating an Universe.
The problem is that we do no have any fact table.
Could you please explain the steps for creating an universe without fatc table?
Thanks
Pat

The first thing to do is identify the tables in your schema that contain measures. These will be your base tables for contexts.
Then identify all the tables that relate to each of your candidate fact tables.
You may identify two related tables, both with facts in, which would give you a fan trap.
Say you have a schema with only three tables and they are related as: T1 -< T2 -< T3
T2 and T3 both have measure columns.
What you would need to do is create an alias of T2 (AT2) and join it to T2.
You would then have two contexts, T1-< T2 , T2-< T3 and T1-<T2, T2- AT2
For objects from T2, derive the dimensions from T2 and the measures from AT2.
Beyond that, it's fairly standard.
If you have a data schema it is going to be much easier for you.

Join fact tables with different grain without upsetting measures?

Say I am a business analyst at a university, and I have two analytical cubes available to me: an Enrollment Cube and an Admissions Cube. The Enrollment Cube has a grain of Student and Semester, whereas the Admission Cube has a grain of Student, Application and Semester (a potential student can have more than one application in a semester). Is there any way for the OLAP developer that makes these cubes to make it so that I can use both cubes' fact tables without messing up their corresponding measures, such that I can create such analyses as the following:
County
Semester
Acceptance Rate (Admission Fact)
Retention Rate (Enrollment Fact)
County A
1
30%
88%
2
60%
87%
3
42%
84%
County B
1
90%
100%

One suggestion is to create a view that joins the 2 fact tables and then create a cube with measures mapped to the view for analysis purposes. However, this would be using the measures of the new cube for the analysis.

Transaction data can be loaded into the Fact table without loading the

Transaction data can be loaded into the Fact table without loading the corresponding master data (Example : Sales analysis transaction data can be loaded without populating any of its dimensions master data)
a. True
b. False

Hi Kutti,
True - You need to select the option in the infopackage - alwyas load even if no master data exists.
Bye
Dinesh

Creation of condition table without copy

During creation of Condition table ( without copying any condition from available tables), Is it possible to see all field catalouges available? and if possible then how can we see all fields available to add desired ones into our table?

Hi,
SPRO >Sales and Distribution->Basic Functions>Pricing>Pricing Control-->Define Condition Tables
In the above menu path you can find out the Field catalog what SAP has given if you want to add new field you can add provided
If you done the Enhancements
Regards,
Prasanna

Fact Tables without Dimension Tables.

Hi,
I am currently working on a project where a data warehouse is being developed using an application database as the source. Since the application database is already normalised, the tables are being loaded in as they are and the consultant involved is creating
data marts for them. I have asked about why he is not creating separate dimension and fact tables as data marts, and he has told me that he will create a fact table with the dimensions as column names without any dimension tables created as you might expect
as per star/snowflake schema.
Is this right, as I always thought you had to have dimension and fact tables, especially if you want to start using SSAS?
Regards,
W.

create a fact table with the dimensions as column names without any dimension tables created as you might expect as per star/snowflake schema.
This is the trouble with denormalization: where is the stopping point?
If the data warehouse is the source for SSAS OLAP cubes, it is better to go with the usual star schema.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Fact table without dimension table

is it possible to build a fact table without any joining dimension table?
I found that in this case an error is issued.
thanks !!

Yes, you can but you must create a fake join with another table.
OBIEE ask always in the Business Model Layer minimum a fact table and a dimension.
In the presentation layer, you drag only the fact table column and it will work.

Alternate fact table without disturbing the existing fact table in EIS

I have a question in EIS, how to load or work with alternate fact table, without disturbing the existing fact table, pls provide me with some procedure and steps
thank u in advance
sunil

Yes you can have multiple models and metaoutlines load one cube. I've done it before. The trick is you ahve one "master" metaoutline that you put all the measures in (even if they are manually added. You use that to build the cube. Then you can have multiple metaoutlines build different measures within the cube. The idea is you have to have them update different intersections or the last one in will be what you get. I have a client that gets sales info from one source, shipment info from a different relational source . in all I have 10 differnt models and metaoutlines that build one cube. you just lump the load statements into one CBS file. It works great (or as great as EIS works). The biggest issue is timing to make sure all the sources are available when the load is going to be doe. Of course you could build different parts at different times.

Two Filter on Two dimensions without constraining the fact table

Hi All,
does anybody know how to avoid the fact constraint when creating a report with two filters on different dimensions?
I have a big fact table with more than 10 Million rows. In the starmodel the is the dimension customer and products. I create a filter on the customer atrribute "Status" and choose the value "Active". Now I add the column "Product Type" from the dimension "Product" to the filter section. When I want to choose a value OBIEE executes a select statement within the fact table. So I have to wait very long to select a value. Is there any way to say OBIEE only to select the dimension table without joining the fact table?
Thank you very much in Advance.
Regards,
Stefan

Hi Stefan,
Generally queries on the dimensions (across dimesions also) always go through a fact. In case, you would like the queries not be through fact table, but just the dimension tables right away, you can set up a separate subject area for them.
You can create a separate subject area based on a dummy fact table to get these prompt values.
Please refer to http://gerardnico.com/wiki/dat/obiee/presentation_service/obiee_parameter_prompt_subject_area for more details on this setup.
Hope this helps.
Thank you,
Dhar

SSAS .abf file without partitions of fact table

Hi All,
I am trying to take a cube .abf file from Dev env. This cube contains patitions for month on one of the fact table. our each env has differnt number of months.
My problem is when i take .abf file from DEV backup it contains only 4 months of data so it as only 4paritions. But SIT conatins 8 months data they are not showing up even after full cube process. i came to know that we must take a fresh .abf file without
processing. How can i take it??
Note: I cannot create partions from SSMS.
Thanks in advance

I am trying to take a cube .abf file from Dev env. This cube contains patitions for month on one of the fact table. our each env has differnt number of months.
My problem is when i take .abf file from DEV backup it contains only 4 months of data so it as only 4paritions. But SIT conatins 8 months data they are not showing up even after full cube process.
Hi shrSan,
If we backup a cube which contains 4 partitions for the measure group, it always got 4 partitions for the measure group when we restore the cube on a new OLAP Server. If we need to filter a fact tabel with more partitions, we should create partitions by
manually on the new OLAP Server.
For more information, please see:
Filtering a Fact Table for Multiple Partitions:
http://technet.microsoft.com/en-us/library/ms175325(v=sql.105).aspx
Partitions (Analysis Services - Multidimensional Data):
http://technet.microsoft.com/en-us/library/ms175688.aspx
If I have something misunderstood, please point out and elaborate your issue with more detail.
Regards,
Elvis Long
TechNet Community Support

How to load data to fact table for the year 2008 without modifying session sql

Hi,
I need to load data to OOTB Financial-General ledger related fact tables using new DAC execution plan for the year 2008 (just for the year 2008 not before or after). without modifying OOTB informataica session SQL. do you know how to do it?
appreciate you for your help. thank you.

Do you know why you are going for new Execution plan instead of using existing?
let me know this will share what I know
thanks for checking
PS: JV its you!!
Message was edited by: SriniVEERAVALLI

Dimension values without data in a fact table

I have an ODS system and a Data warehouse system
I have a Sales fact table in the ODS system and I have these fields:
SALES
ID_CUSTOMER (PK),
ID_MODEL (PK),
ID_TIME (PK),
SALES,
QUANT_ART,
COST
Then in some records in the fields ID_Time or ID_Model or ID_Customer I donât have values (NULL) because in the transactional systems these record donât have values (NULL).
The users want to generate aggregate reports with the Sales table...
The question is:
I have to put a âdummyâ value in the dimensions Customer, Model and Time (for example â0â) and put this value in the fact table if the dimensions fields have NULL values????
Or I have to leave the NULL values?
What is the best choice? Why?

There's often some specific reason why these values don't exist, such as the record being a manual adjustment to sales (for example a journal voucher). In these cases it can be helpful to have a flag column to indicate this, so that when a user comes across a bunch of sales with a Store Name of "Unknown" or "Not Applicable" they can also look at the reason for this unusual entry.

Star schema without a fact table?

Hi,
I'm preparing my warehouse for using with Discoverer and my question is about the star schema.
- Is a star schema directly associated with data warehouse?
- Can I talk about a star schema if a) I do not have a fact table (no summarized values) and b) if I do not have a dimension of time?
The problem is, I'm thinking of usine Discoverer but should I use it if it's not connected to a data warehouse?
As I told, I'd like to modelized my data "like" a star schema but my "center table" will contain only the foreign key of my dimensions; no time dimensions, no aggregate data in the center table (fact table).
Is there another word for the model I'd like to do?
Thank in advance.

Hi,
Is a star schema directly associated with data warehouse?Not really, a star schema is just one where there is one large fact table joined to many smaller dimension tables using key fields. You usually see this in data warehouses.
Can I talk about a star schema if a) I do not have a fact table (no summarized values) and b) if I do not have a dimension of time?A star schema must have a fact table but it doesn't need contain summarised values or a time dimension.
You can use Discoverer with any Oracle database, it doesn't have to be a data warehouse.
Rod West

Display master data without data in the fact table

Characteristic 0PROJECT
Attribute Price
I want to show in the query all the prices including the projects that don't have registers in the fact table.
How do I do this?
Tnks.

I believe you are describing what SAP referes to as the Slow Moving Item scenario. Search SDN using that phrase and you'll get hits on documents and Notes that talk more about this. Here's something from an old How To
Slow Moving Item Scenario
You want to define a query that displays all products that have been purchased only
infrequently or not at all. In other words, the query is also display characteristic values for
which no transaction data or only low values exist for the selected period.
Procedure
In the Administrator Workbench;
1. Create a MultiProvider consisting of a revenue InfoCube, containing the InfoObject
Material (0MATERIAL), and the InfoObject 0MATERIAL. The InfoObject must be set as
an InfoProvider in InfoObject maintenance. In other words, you need to have assigned
the InfoObject to an InfoArea. (also refer to Tab Page: Master Data/texts [Ext.]).
In the BEx Analyzer:
2. Select your MultiProvider in the Query Designer.
3. Define a query that contains the InfoObject 1ROWCOUNT in the columns.
The InfoObject 1ROWCOUNT is contained in all flat InfoProviders, that is, in all
InfoObjects and ODS objects. It counts the number of records in the InfoProvider.
In this scenario, you can see from the row number display whether or nor values
from the InfoProvider InfoObject are really displayed.
4. Save the query and execute it. All values are now displayed, including those for materials
that were not purchased.
If you filter by time (0CALYEAR, for example), values from the InfoProvider
InfoObjects are not displayed since 0CALYEAR is not an attribute of
0MATERIAL. You can see this from the absence of values in the 1ROWCOUNT
column in the query. If you want to restrict by time, you need to proceed as
follows:
Constant Selection for the InfoObject
You need to set the constant selection for the 1ROWCOUNT key figure in order to be able to
set a filter by time in this query.
1. In the Query Designer, via the context menu for 1ROWCOUNT, choose Edit.
2. On the left hand half of the screen, under the data package dimension, select the
characteristic InfoProvider (0INFOPROV) and drag it into the right-hand screen area.
3. From the context menu for the InfoProvider, choose Restrict, and restrict across the
InfoProvider InfoObject.
4. Also from the context menu for the InfoProvider, choose the function Constant Selection.
5. Save the query and execute it. You can now also set a filter for a time characteristic, the
materials display remains as it was.
Displaying Slow Moving Items
SAP Online Help 05.11.02
MultiProviders 3.0B, Support Package 07 10
If you want to display a list of slow moving items, excluding products that are selling well, you
need to proceed as follows:
1. In the Query Designer, via the context menu for 1ROWCOUNT, choose Edit.
2. Via the context menu for InfoProvider, choose the function Display Empty Values. Also
select Constant Selection.
3. Save the query and execute it. The result is that the system displays the materials for
which there was no revenue.
Displaying Products with Small Revenues
If you want to display a list of products that have not been sold or have only been selling
badly, you need to proceed as follows:
1. Set constant selection as described above, but do not select the display empty values
function.
2. In the Query Designer, define a condition for the 0MATERIAL InfoObject. Specify a value
that is to be the upper limit for a bad sale.
3. Save the query and execute it. The result is that the system displays all materials that
have not been sold or have been selling badly.

Universe creation- without fact tables

Similar Messages

Maybe you are looking for