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?

Similar Messages

Dimension table and fact table exists data physically

Hi experts,
can anyone plz tell me weather dimension table and fact table exists data physically or not/

Hi..Sudheer
SAPu2019s BW is based on "Enhanced Star schema" or "Info Cubes" database design.This database design has a central database table, known as u2018Fact Tableu2019 which is surrounded by associated dimension tables.
Fact table is surrounded by dimensional tables. Fact table is usually very large, that means it contains
millions to billions of records.
These dimension tables doesn't contain data it contain references to the pointer tables that point to the master data tables which in turn contain Master data objects such as customer, material and destination country stored in BW as Info objects. An InfoObjects can contain single field definitions such as transaction data or complex Customer Master Data that hold attributes, hierarchy and customer texts that are stored in their own tables.
SID is surrogate ID generated by the system. The SID tables are created when we create a master data IO. In SAP BW star schema, the distinction is made between two self contained areas: Infocube & master data tables/SID tables.
The master data doesn't reside in the satr schema but resides in separate tables which are shared across all the star schemas in SAP BW. A numer ID is generated which connects the dimension tables of the infocube to that of the master data tables.
The dimension tables contain the dim ID and SID of a particular IO. Using this SID the attributes and texts of an master data Io is accessed.
The SID table is connected to the associated master data tables via teh char key.
Fact table(Transaction data,DIM ID)<>Dimention Table(SID and Dim ID)<->Masterdata table(SID,IO)
Thanks,
Abha

Update data automatically in fact table in Data Warehouse

Hi,
I'm working on the creation of a data warehouse that include different data source like SQL Server performance (more than one), Active Directory users, Server performance (more than one), Exchange server mailboxes. The problem is that performance data change
frequently (like CPU and Memory), so my question is how to update data in fact table every 5 seconds automatically with SSIS.
Thank you for any advice

I'm assuming you have already figured out how to capture the data e.g. Powershell, extended events, MDW etc. and just need to know what dimensions or fact tables do you need.
You need to decide how often you are going to capture this data and based on that you will have dimensions with appropriate grain. Don't try to cram everything in the same fact table if it not of the same granularity. Also, separate process usually
have separate fact tables.
In addition to the Date dimension, you will need a Time dimension with a grain of 1 second (or maybe 5 seconds if that is when you get your data) then run the SSIS every 5 seconds to capture and append that data in the fact table.
- Aalamjeet Rangi | (Blog)

What is correct way to join a start/end date driven dimension to a fact table in data foundation?

I have a bad universe or a data design issue.
Several versions of hierarchies reporting store entities in reporting Fact measures.
Example of date driven Hierarchy Dimension:   ORG_KEY
                                                                            START_DATE
                                                                            END_DATE
                                                                            STORE_NUMBER
                                                                            ORG_HIERARCHY
                                                                            CURR_FLG   (Y/N)
Fact table :                                                         ORG_KEY
                                                                             CALENDAR_KEY
                                                                             TRANS_DATE
                                                                             $amount
Calendar Dimension:                                            CALENDAR_KEY
                                                                              DAY_DATE
                                                                               FY_WEEK          (201452)
                                                                                FY_PERIOD      (201412)
                                                                                FY_QUARTER   (201401)
                                                                                 FISCAL_YEAR    (2014)
Users WISH:
Wish for store number and org hierarchy to pull as of the last day of each pull without prompt.    The Store(ORG_KEY) as in the fact table; but the ORG_HIERARCHY and other attributes as of the last day they pull.
Daily (Would be Calendar.Day_Date in Filter) ,
Week to date (would be Max Calendar.Day_Date for (201452) FY_WEEK as entered,
Month to date,
Year to date,
AdHoc queries.
My problem is I see how they could manually pull this in Webi.   I have tried everything I know to join to no avail. I have not gotten @Prompts to work in joins, derived tables, etc. in the data foundation. Wonder what is difference between parameter in Data foundation vs. filter in buisness layer.    None of them worked.
Please help!   ANY ideas would be appreciated.   .

{Note that abbrevations in brackets are just for short form further down the answer}
Join Store Dim (SD) to Transaction Fact (TF) on ORG_KEY=ORG_KEY with 1 to Many cardinality
Create an alias of Calendar Dim and call it Transaction Date (TD)
Join TD to TF on TD.CALENDAR_KEY=TF.CALENDAR_KEY with 1 to Many cardinality
Create a predefined condition in your universe called "Return Yesterday's Transactions" as:
TD.DAY_DATE = trunc(sysdate-1) <-- That assumes Oracle database; use whatever is correct for yesterday for your RDBMS
The above predefined condition when added to your data query will return only yesterday's transactions.
However, if you want to return all the different types of sales, you would need an object for each one. To do that, you'd use a case statement. Again, using Oracle syntax, an example of MTD would be:
SUM(CASE WHEN trunc(TD.DAY_DATE,'yyyymm') = trunc(sysdate,'yyyymm') THEN TF.amount END)
If you have any more questions about how this approach would work please shout.
As an alternative, you could create a time hierarchy and add scope of analysis to your report for it and enable drilling at report level.

Foreign keys in SCD2 dimensions and fact tables in data warehouse

Hello.
I have datawarehouse in snowflake schema. All dimensions are SCD2, the columns are like that:
ID (PK) SID NAME ... START_DATE END_DATE IS_ACTUAL
1 1 XXX 01.01.2000 01.01.2002 0
2 1 YYX 02.01.2002 01.01.2004 1
3 2 SYX 02.01.2002 1
4 3 AYX 02.01.2002 01.01.2004 0
5 3 YYZ 02.01.2004 1
On this table there are relations from other dimension and fact table.
Need I create foreign keys for relation?
And if I do, on what columns? SID (serial ID) is not unique. If I create on ID, I have to get SID and actual row in any query.

>
I have datawarehouse in snowflake schema. All dimensions are SCD2, the columns are like that:
ID (PK) SID NAME ... START_DATE END_DATE IS_ACTUAL
1 1 XXX 01.01.2000 01.01.2002 0
2 1 YYX 02.01.2002 01.01.2004 1
3 2 SYX 02.01.2002 1
4 3 AYX 02.01.2002 01.01.2004 0
5 3 YYZ 02.01.2004 1
On this table there are relations from other dimension and fact table.
Need I create foreign keys for relation?
>
Are you still designing your system? Why did you choose NOT to use a Star schema? Star schema's are simpler and have some performance benefits over snowflakes. Although there may be some data redundancy that is usually not an issue for data warehouse systems since any DML is usually well-managed and normalization is often sacrificed for better performance.
Only YOU can determine what foreign keys you need. Generally you will create foreign keys between any child table and its parent table and those need to be created on a primary key or unique key value.
>
And if I do, on what columns? SID (serial ID) is not unique. If I create on ID, I have to get SID and actual row in any query.
>
I have no idea what that means. There isn't any way to tell from just the DDL for one dimension table that you provided.
It is not clear if you are saying that your fact table will have a direct relationship to the star-flake dimension tables or only link to them through the top-level dimensions.
Some types of snowflakes do nothing more than normalize a dimension table to eliminate redundancy. For those types the dimension table is, in a sense, a 'mini' fact table and the other normalized tables become its children. The fact table only has a relation to the main dimension table; any data needed from the dimensions 'child' tables is obtained by joining them to their 'parent'.
Other snowflake types have the main fact table having relations to one or more of the dimensions 'child' tables. That complicates the maintenance of the fact table since any change to the dimension 'child' table impacts the fact table also. It is not recommended to use that type of snowflake.
See the 'Snowflake Schemas' section of the Data Warehousing Guide
http://docs.oracle.com/cd/B28359_01/server.111/b28313/schemas.htm
>
Snowflake Schemas
The snowflake schema is a more complex data warehouse model than a star schema, and is a type of star schema. It is called a snowflake schema because the diagram of the schema resembles a snowflake.
Snowflake schemas normalize dimensions to eliminate redundancy. That is, the dimension data has been grouped into multiple tables instead of one large table. For example, a product dimension table in a star schema might be normalized into a products table, a product_category table, and a product_manufacturer table in a snowflake schema. While this saves space, it increases the number of dimension tables and requires more foreign key joins. The result is more complex queries and reduced query performance. Figure 19-3 presents a graphical representation of a snowflake schema.

BW 3.5 Fact table with data no corresponding records on P table

Hi Gurus,
I have a weird situation: There is an BW 3.5 SP 16 (I know itu2019s oldu2026) infocube that receive 400,000 records every single day.
They never compressed (at least there is no data on E table), instead they ran a program calling FM u201CRSDRD_SEL_DELETION'u201D every day that takes about 5 hours to run (when it runs without errors).
So I checked Fact table and found 337,564,988 records. If you check the number of records on Infocube Admin it shows 14,018,370 record. I found that the u201Cmissingu201D record are not on P table (there is data on Fact pointing to missing Packages).
I think the Selective deletion messed up the infocube. These record that are missing on P table have to be deleted. I ran an RSRV check on this Infocube on Background and it canceledu2026
So, I want to delete this data from Fact my question is: How to do that with minimum effort without invalidade the information?
Of course I will backup the data to a temp cubeu2026
Well any idea is welcome
Regards,
Alex

Hi Navesh,
First of all thanks to your quick answer.
Well, the arguments of FM are set to del any 0SEM_CRDATE older than 30 days in the past. This characteristic receive SY-DATUM on Act. Rule (transformationu2026) so every package older than 30 days have to be deleted. The weird thing is that it is deleting the P table record and keeping the data on F table.
So You think it would be a nice try to do an selective deletion with the same criteria manually?
This is the code, can you (or someone) take a look?
START-OF-SELECTION.
*Cria Range do período a ser eliminado
PERFORM f_range.
PERFORM f_elima_cubo.
END-OF-SELECTION.
*&      Form F_RANGE
FORM f_range.
v_data_inic = sy-datum - 31.
v_range-sign   = 'I'.
v_range-option = 'LT'.
v_range-low    = v_data_inic.
v_range-keyfl = 'X'.
APPEND v_range TO t_tab_main-t_range.
t_tab_main-iobjnm        = '0SEM_CRDATE'.
INSERT t_tab_main INTO TABLE t_thx_sel.
ENDFORM.                    " F_RANGE
*&      Form F_ELIMA_CUBO
FORM f_elima_cubo.
v_parallel               = '01'.
CALL FUNCTION 'RSDRD_SEL_DELETION'
    EXPORTING
      i_datatarget      = 'IC_LP_B01'
      i_thx_sel         = t_thx_sel
      i_authority_check = c_flag
      i_no_logging      = v_nl
      i_parallel_degree = v_parallel
      i_show_report     = v_sr
    CHANGING
      c_t_msg           = t_msg.
ENDFORM.
Regards,
Alex

Reg: Fact table and Dimension table in Data Warehousing -

Hi Experts,
I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
Fact table contains data that can be aggregate.
Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
Dimension contains data that is use to generate groups and filters.
This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
Any help is much appreciated.
Pardon me if this's not the correct place for this question. My first question in the new forum.
Thanks and Regards,
Ranit Biswas

ranitB wrote:
But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

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

How to create a ROLAP Cube that has two fact tables.

I want to know if it is possible to create a ROLAP Cube with two fact tables.
Suppose that I have these two star schemas:
The first star schema has only a measure and a time dimension. The time dimension has three levels (Year -> Month -> Day)
The second star schema has the same measure of the first schema and a time dimension. In this schema the time dimension has only two levels (Year -> Month). The values of the measure of this schema come from the first schema, this is, the value of the measure for a defined year and month results of the sum of all fact values of the first schema, that have the same year and month.
I want to know if is possible to create a ROLAP cube that can get the information of the two star schemas, according to the level that the user are consulting.
For example, if the user consults the cube with "OracleBI Spreadsheet Add-In", and if the user is consulting the first two levels (Year and Month), then the ROLAP cube would get the information of the second star schema.
But if the user does a drill down in a month to get information of the days, then the ROLAP cube would get the information of the first star schema.
Is it possible to do this?
Regards,
Rui Torres

I'm not exactly sure what you want to do. Sorry if I get this wrong.
You have two fact tables, one with data values at the day, month and year levels and a second fact table with data values at just the month and year levels. If this is the case, in the CWM2 APIs or OWB Paris, you would create a view that joins the two tables together and then map this view to the ROLAP cube.
For CWM2 details, please refer to the Oracle OLAP Reference.

Can't load data to cubes - same error for all DTPs "exception in substep write to fact table"

Hi Experts,
This initial DTP error is:
Data package processing terminated Message no. RSBK229
Error while updating to target <cubename> (type INFOCUBE) Message no. RSBK241
If I drill down to the specific package in the process monitor the error is: "exception in substep write to fact table" .
No more details for why the error is being generated.
SAP BW 307 service pack 8.
I have run the debugger without success, an ABAPer also ran debug mode to get more details on the error without success
We checked teh termination point and the ABAP stack
No error stack is available
No short dumps
I have reactivated the DTP
The data looks fine
The server crashed the day before the DTPs started to fail
One cube is standard content and the other is a Z version of the same cube.
Please let me know if anyone has resolved this issue before and what steps were necessary.

Hello Russell,
We have got the similar situation and we later found that it was a data issue only.
We tried to enable the error stack, but as the data issue was due to a lookup which is bringing the invalid data, its not captured in the error stack and throwing short dump with the message u mentioned.
so my suggestion, just put a break point if there are any lookups and check the data in internal tables if everything is as expected.
Hope this helps.
Thanks,
Venkata Naresh

Load data from dimensions to fact table

Hi,
I have 10 dimension tables and one fact table. now i want to load data in to fact table from dimensions table. how i can do that.
Regards,
joy

To elaborate on "Mallee"'s answer, it's not good practice to load dimensional data into a fact table.
I guess what you mean is how to refer to dimensions when loading a fact table.
Simply refer to dimensions using lookups on the necessary dimensions, the lookup needs to be on the natural key you have that links facts to dimensions. Don't forget to use the dimension's surrogate key though when populating the fact table's foreign key columns pointing at the dimensions.
Hope this helps.
Cheers, Patrick

Best ways to create rpd or reports if we have data in more fact tables

I have fact and dimensional data in one or more different tables. Then each logical table source represents one data segment.Please suggest me some methods or ways like fragmentation through which i can use them in creating rpd and report and main problem here is facts too large contains 25 million records.But adding tables in BMM layer effecting performance so can anyone other ways doing it in database side.
Thanks in advance
Edited by: user2989722 on Dec 3, 2009 3:09 PM

hi,
For the fragmentation you can create on dimension .The procedure is clearly explained in this blog
http://108obiee.blogspot.com/2009/01/fragmentation-in-obiee.html
http://www.rittmanmead.com/2007/06/19/obiee-data-modeling-tips-2-fragmentation/
For the performance point of view you can create a Materialized view (based on columns that your report is using) so that it will hit that particluar view instead of hitting whole table(25million records table) please look into this post
Re: Materialized views in OBIEE
thanks,
saichand.v

How can we delete the data in e-fact table.

how can we delete the data in e-fact table.

hii,
You cannot delete the request individually but you can one of the following:
1. Do a selective deletion from the cube. RSA1 -> Cube -> Contents -> selective deletion.
2. Delete all the data in the cube and then reconstruct only the required request ids. This would work only if you have the PSA available for all the requests.
3. Reverse posting is another possibility.
hope it helps,
partha

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

Attribute key not found when there is no data in Fact table

Hi All,
I have a Dimension and Fact table,Dimension has data but Fact table is empty. The Dimension is MOLAP & Measure group is ROLAP. the relation is built on Key column and named column is some other attribute.
When I execute MDX "select { [Measures].[Avg Sales] -- Average type measure} on columns from my_Cube ", this returns a valule with #Error. error message in cell is "The attribute key cannot be found when processing:
Table: 'FACT, Column: 'ID', Value: '0'. The attribute is 'Name' "
I have processed the Dimension with Full and then Cube is processed with Full. but still same error. Please suggest .
Ram MSBI Developer

Hi Ram ,
Since you mentioned "Value: '0'. The attribute is 'Name' ""
I would recommend to have a look at the Key/Name Column's property regarding to the NullProcessing .
Regards, David .

FAct TABLE LOOKUPs data

Similar Messages

Maybe you are looking for