OBIEE 10g: Problem on fact table mapping

Hi to everyone,
i have this situation:
1) i have 2 fact tables in phisical model (FHRCTR and HCTOT) this two table is the same in the FK columns.
2) the structure is: FHRCTR[month_fk, transaction_type, measure A], HCTOT[month_fk, measure B]. 'transaction_type' is an attribute of the table not dimension.
3) i have created a logical fact table with this two tables for source.
4) each field of logical table is mapped on the corrispetive field on the both phisical table, except for 'transaction_type' column having as source only FHRCTR table.
5) i've created a report with follow colums: month_fk, transaction_type, measure_A, measure_B
The problem is: if i create the report with the columns in point 5, the measure_B returns null values and the measure_A have a correct value.
Insteed if i create a report without 'transaction_type' column the value of Measure_B and Measure_A are correct.
I remind you that: 'transaction_type' in the logical fact table is mapped only on the FHRCTR table because on HCTOT it doesn't exist.
Can you help me to solve this issue?
Thanks

832596 wrote:
Can you help me to solve this issue?
ThanksI guess when you set some aggregation rule for 'transaction_type' in a repository then all will be ok (for examplу - min). But you'll get results that you don't expect.

Similar Messages

FACT table Mapping

I could not find a clear documentation on how to create a mapping to load CUBE
after creating dimensions. I am using 10.1.0.2 version.
I have two dimensions and one FACT table
DIM1
D1_sk
other attributes
DIM2
D2_SK
other attributes
FACT
D1_sk
D2_sk
measure attributes
In previous forums I came across to use a lookup on dimensions
to load the FACT table.
But what would be my source to perform a lookup on Dimensions ?
because My dimensions are the source for the FACT TABLE.
Can I Join the DIMENSIONS to load the FACT TABLE?
can any one suggest the right approach to creat a FACT table mapping.
Thanks in advance.

Hi,
If you can tell what you are tying to achieve we can give some suggestions. You can use the same sources which you have used to load Dimensions, to load Fact table.
Mahesh

OBIEE: incorrect selection of fact table when generating SQL

I have 2 dimension tables ("DimA" and "DimB") connected with one fact table ("Fact1").
Also (only) "DimB" is connected with another fact table "Fact2".
When I want to make a report with one attribute ("Attribute_A") from "DimA" and another one ("Attribute_B") from "DimB", I receive a error like this:
"State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact2) does not contain mapping for [DimA.Attribute_A]. (HY000)"
Remember that is not supposed "DimA" to be connected with "Fact2", only with "Fact1".
The only factor that I see that can be a problem is the fact that in Presentation Catalog was defined a implicit column from tact table "Fact2".

Hi,
While I don't know the need to generate a report based on 2 dimensions only, I mean you are trying to generate a report between 2 dimensions. Dimensions are not joined together in OBIEE. OBIEE will try to pull any fact and try to obtain the relationship between the two dimensions. In your case it is taking Fact2.
One way could be if u just pull in some measure from Fact1, then u should be able to get the report.
Else u can try setting content level for DimA in fact 2 to grand total level. This can be done even though dimA and Fact2 are not joined. Although I am not sure whether this will work.

Problem: two fact tables and one conformed dimension

Hi everyone!
I need to solve this situation:
I have two fact tables, let's say F1 and F2, that are both linked to D1, my conformed dimension
I just need to select fields from D1 but I know that, when querying, OBIEE links it to a fact table anyway..how does it choose the fact table? That is, if I only want fields from D1, does the system queries also from F1 or F2? Is it a random choice?
Is there a way to "force" this choice, telling the system for example to choose only from F1?
Is there a workaround to solve this situation? Remember, I only need fields from D1.
Thanks!!

The solution of your problem is "Implict Fact Column"
Go to presentation layer and double click on your subject area. then you will see Implict fact column option. click on set. give corresponding fact column there( in your case give F1 fact column)
references: http://oracle-bi.siebelunleashed.com/articles/implicit-fact-column/
Thanks
GSR
Edited by: GSR on Mar 20, 2012 3:22 PM

Calc problem with fact table measure used as part of bridge table model

Hi all,
I'm experiencing problems with the calculation of a fact table measure ever since I've used it as part of a calculation in a bridge table relationship.
In a fact table, PROJECT_FACT, I had a column (PROJECT_COST) whose default aggregate was SUM. Whenever PROJECT_COST was used with any dimension, the proper aggregation was done at the proper levels. But, not any longer. One of the relationships PROJECT_FACT has is with a dimension, called PROJECT.
PROJECT_FACT contains details of employees and each day they worked on a PROJECT_ID. So for a particular day, employee, Joe, might have a PROJECT_COST of $80 for PROJECT_ID 123, on the next day, Joe might have $40 in PROJECT_COST for the same project.
Dimension table, PROJECT, contains details of the project.
A new feature was added to the software - multiple customers can now be charged for a PROJECT, where as before, only one customer was charged.
This percentage charge break-down is in a new table - PROJECT_BRIDGE. PROJECT_BRIDGE has the PROJECT_ID, CUSTOMER_ID, BILL_PCT. BILL_PCT will always add up to 1.
So, the bridge table might look like...
PROJECT_ID CUSTOMER_ID BILL_PCT
123          100     .20
123          200     .30
123          300     .50
456 400 1.00
678 400 1.00
Where for project 123, is a breakdown for multiple customers (.20, .30. .50).
Let's say in PROJECT_FACT, if you were to sum up all PROJECT_COST for PROJECT_ID = 123, you get $1000.
Here are the steps I followed:
- In the Physical layer, PROJECT_FACT has a 1:M with PROJECT_BRIDGE as does PROJECT to PROJECT_BRIDGE (a 1:M).
PROJECT_FACT ===> PROJECT_BRIDGE <=== PROJECT
- In the Logical layer, PROJECT has a 1:M with PROJECT_FACT.
PROJECT ===> PROJECT_FACT
- The fact logical table source is mapped to the bridge table, PROJECT_BRIDGE, so now it has multiple tables it maps to (PROJECT_FACT & PROJECT_BRIDGE). They are set for an INNER join.
- I created a calculation measure, MULT_CUST_COST, using physical columns, that calculates the sum of the PROJECT_COST X the percentage amount in the bridge table. It looks like: SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT)
- I brought MULT_CUST_COST into the Presentation layer.
We still want the old PROJECT_COST around until it get's phased out, so it's in the Presentation layer as well.
Let's say I had a request with only PROJECT_ID, MULT_CUST_COST (the new calculation), and PROJECT_COST (the original). I'd expect:
PROJECT_ID MULT_CUST_COST PROJECT_COST
123          $1000     $1000
I am getting this for MULT_CUST_COST, however, for PROJECT_COST, it's tripling the value (possibly because there are 3 percent amounts?)...
PROJECT_ID MULT_CUST_COST PROJECT_COST
123          $1000 (correct)      $3000 (incorrect, it's been tripled)
If I were to look at the SQL, it would have:
          SELECT SUM(PROJECT_COST),
SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT),
               PROJECT_ID
          FROM ...
          GROUP BY PROJECT_ID
PROJECT_COST used to work correctly before modeling a bridge table.
Any ideas on what I did wrong?
Thanks!

Hi
Phew, what a long question!
If I understand correctly I think the problem lies with your old cost measure, or rather combining that with you new one in the same request. If you think about it, your query as explained above will bring back 3 rows from the database which is why your old cost measure is being multiplied. I suspect that if you took it out of the query, your bridge table would be working properly for the new measure alone?
I would consider migrating your historic data into the bridge table model so that you have a single type of query. For the historic data each would have a single row in the bridge with a 1.0 BILL_PCT.
Best of luck,
Paul
http://total-bi.com

Fact table mapping/loading

I am new to OWB and trying to use OWB 9.0.4 to create a star schema on a oracle 9.2 DB. Using OWB client, I successfuly created dims and a fact table on the target DB. But I got stuck with how to use OWB to map the fact table with dims and source tables, and using OWB to generate SQL loading scripts which contains PL/SQL statement shown below:
insert into "fact_table" ("fact_count") ( select count(*) from target_table where dim1='dime_value1' and dim2='dim2_value2');
here dim1 and dim2 are the dims assocated with the fact table and they are also mapped to the corresponding target table columns.

Frank,
source table -> aggregator -> target
As input into the aggregator, you specify dim1, dim2 and any numeric value. If you do not have one, use a numeric constant such as 1. In the aggregator, you specify dim1, dim2 as the group by clause (operator properties). You then add a numeric output attribute (edit function), and go to the attribute properties. As a function, specify count from the numeric input attribute.
That would load your measure.
Cube function is not currently supported in the mapping editor, but you could include that in a materialized view that is based on the table.
Mark.

Problems with Fact Table in an Infocube

In IC 0CCA_C11 we've seen almost a 50% increase in the row count on the F fact table from about 100 million rows to about 150 million rows. However we are very certain that we really havent had that much growth.
We have a process chain that does a full load of 12 million rows to the cube and then deletes the previous full load. Because this PC is conflicting with a more important PC that loads to the cube, we've been cancelling the step in the PC and manually deleting the previous request out of the cube via the IC "Manage" screen.
Is it possible that what we've been doing has been leaving rows in the cube that we thought were deleted?
If so, is there an Analysis and Repair function in RSRV that will get rid of all these extra rows?
There's no way this cube could have truly grown by 50 million rows in 2 weeks!

Wardell,
Check the data in RSA3 for the extractor that you use to bring data .
You must be using the data source 0CO_OM_CCA_09. Check the data and reconcile and you will get it.
Let me know if you need anything else.
Thanks
Ravi Thothadri
[email protected]

10g - merge 2 fact tables

hi, experts,
there are 2 tables
columns in A:
CK1
CK2
CK3
X varchar
Y varchar
Z varchar
FA1 double
FA2 double
FA3 double
columns in B:
CK1
CK2
CK3
FB1 double
FB2 double
FB3 double
CK1,CK2 and CK3 are the common keys of TABLE A and TABLE B.
if there is a table/pivot table having columns : CK1,CK2,CK3, X,Y,Z, FA1,FA2,FA3,FB1,FB2,FB3
I found that all FB1,FB2,FB3 are showing null.
how to solve?

i used to work on a very primitive tool called INFORMATICA POWER ANALYZER ( 10 YEARS BACK- 2001/2002 ) and OBIEE is a re incarnation of that tool. I think this feature is avaiable in OBIEE 11g ( pulling columns from different subject areas via implicit common DIMENSION tables )
Cheers

Integrating google maps in obiee 10g

i am using IE and after filling the boxes in narrative view in preview it is showing "retrieving view"...
but even after long time it displays nothing...
do help me.
any help is appreciated.

HI,
Refer the below links.
http://wentari.blogspot.in/2011/03/obiee-10g-and-google-chart-api-maps.html#!/2011/03/obiee-10g-and-google-chart-api-maps.html
http://www.peakindicators.com/index.php/knowledge-base/68-mapping-capabliity-with-oracle-bi-ee-faqs
Hope this help's
Thanks,
Satya

Business Model with 2 fact tables

Hi there
I am trying to get a simple business model working , 2 fact tables, 1 dimension, similar to this example :
http://www.rittmanmead.com/2008/08/resolving-fan-traps-and-circular-joins-using-obiee/
However I keep getting this: [nQSError: 14025] No fact table exists at the requested level of detail:
the tables are:
Incident (dimension)
PK Sequence
Incident Detail (fact table 1)
PK Sequence
FK Problem #
Order (fact table 2)
PK Sequence
FK HDNum
I cant figure out why this doesnt work like the rittman mead example? do they need to have the same column name?
Thanks
Tim

It says the model doesnt contains a fact table.Fact table will have foreignkeys and Measure columns.That link shows the circular joins between tables.There fact table is not there.
See this link for fact and dimensions
http://www.geekinterview.com/question_details/66773

Counting fact table records within brackets

Hi,
I have a star schema setup in OBIEE, consisting of a fact table of transaction records, linked to a customer dimension and a time dimension via PK-FK relations.
One of the requirements is to count the number of customers based on how many transactions they have done per time period. I imagine solving this by creating logical colums such as "# customers (1-10 transactions)", "# customers (11-20 transactions)", etc. The counting should be based on the current level of drill-down in the time dimension.
Any advice on how to approach this would be greatly appreciated
best regards
M

Thanks for you reply, it brought me a lot closer to a solution. So far i've been able to create a bracket attribute on the customer dimension (via Answers and then into Administrator, as advised). I've verified this against the database, and it categorizes each customer correctly.
The remaining challenge is that I want to see the count within each category on an aggregate bracket level rather than per customer. Using one attribute ("customer bracket") which can take on one of several values (e.g. "0", "1-10", "11-20", etc.) i'm not sure how to accomplish this.
As a workaround i tried creating one column in Answers for each bracket, taking on the value 1 for records falling within that bin, and 0 for all other records. Treating the column as numeric, and adding a sub total (sum), i get the answers i want for each bin. The problem here however, is that one line (value 0 or 1) is shown for each customer record, which makes the report useless for most practical intents and purposes as thousands of records are shown.
Any thoughts on which method i should go ahead with, and how?
regards
M

Load data in a fact table

Hello,
I have implemented SCD2 dimension and mapping executing works fine.
Now I have question about loading data in a fact table.
How do I need to use OWB (maybe JOINER operator - Join condition - between dimensions and source table) in case of:
- update on source table
- delete on source table
I think the most simple is insert on source table. It is probably to_char(source_transaction_date,'dd.mm.yyyy') = to_char(sysdate,'dd.mm.yyyy'), if I load once a day..
What is the procedure for fact table mapping to handle updates and deletes on source table?
Regards

Some discussions in previous forums should help you
http://forums.sdn.sap.com/thread.jspa?threadID=2019448
http://forums.sdn.sap.com/thread.jspa?threadID=1908902
In the SAP tutorial, you can see a sample example of making fact tables.
http://help.sap.com/businessobject/product_guides/boexir32SP1/en/xi321_ds_tutorial_en.pdf
Arun

Dynamic fact table choice

Hi Experts,
Is there any way to model the following in obiee:
I have multiple fact tables:
Fact_ABC
Fact_BCD
Fact_DEF
and depending on the value that the user selects on the dimension table (dim_types) the BI server has to pick the corresponding the fact table.
If the users selects the value ABC from the dimension the fact that should be used is Fact_ABC and the same for the other values.
Any idea??
Regards

hi,
Ok,we can do this using fragmentation as our friends said
http://obieetalk.com/fragmentation-obiee
Can I ask what's the reason of that question? is it performance related?Not sure,its based on the data that u have and tables that ur using ,because if u observe the query it is firing while using fragmentation in above example you will came to know about.That's why i asked no.of tables
thanks,
Saichand.v

FAct TABLE LOOKUPs data

Hi,
Please help me out in loading the fact tables
I had used lookup on DIM table to get my SUK and if I use union transformation to get the out put from each lookup and then loading the data with some condition the data in my fact is not loading in a proper format.
The union transformation is splitting the out put in to different records
Please do inform me about which transformation should be used to get the data from lookup tables.
Or please do inform me the approach to load the fact table in SSIS.
I’m basically INFORMATICA resource and I’m implementing in terms of INFORMATICA

Hi, glad to see your reply. I am encountering almost the same problem, loading fact table,
My Dataflow is like:
Source Component -->LKP1(get Dim1 SUK) -->LKP2(get Dim2 SUK) -->LKn(getDimn SUK) ...-->Destination Component(load to fact table database), while i have tough difficulties:
[FactoryLookup [352]] Error: Row yielded no match during lookup.
[FactoryLookup [352]] Error: The "component "FactoryLookup" (352)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Output" (354)" specifies failure on error. An error occurred on the specified object of the specified
component.
[DTS.Pipeline] Error: The ProcessInput method on component "FactoryLookup" (352) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will
cause the Data Flow task to stop running.
[DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0xC0209029.
Could you please help me? How to fix them?

Textual Data in Fact Table

Hi
I would like to understand what can be the probable issues which I may face in OBIEE 11g if my fact table has non- numeric data (textual data) like type or rejection reason in the fact table.
I am new to the team and the data warehouse consist of textual data in fact table. I am not very much sure whether this approach is correct(unless I am missing latest trend)
Can anybody explain me with example on what can be the issues which we can face with textual data in fact table
Regards
Sameer

You need to explain your requirement a bit more. Why you want to add type or rejection reason in fact table.
In general you should avoid adding textual data in fact.
Fact tables are only supposed to store keys and measures. It can hold textual data in case of degenerate dimension ( i.e if the number of records are same in dimension as well as fact ).
Type or Rejection reason are going to have much less records. You can create a new dimension for them having probably 20 or 30 records.
Disadvantages of adding textual data in fact is, once the fact has millions of records the fact table updates are going to take huge time and also your reports will take long time.
If you have a rejection reason dimension with some 20 records, you can use rejection reason in prompts.
But if the same rejection reason is coming from fact table your prompts performance is going to be very slow since it has to fetch 20 distinct records from millions of records.
Consider these before adding textual data in facts.
Thanks
Edited by: Maqsood Hussain on Dec 5, 2012 9:40 PM

OBIEE 10g: Problem on fact table mapping

Similar Messages

Maybe you are looking for