Converting 3 tables to a star schema ??

Hi i was trying to prepare a very small demo for an OLAP system. Anyways I have a simple transaction database for a supposed Book Store anyways the database has the following 3 tables :
Table No:1
Table Name:Main Table
This Table contains the following columns:
Customer Name (PK) | Book Purchase ID (PK) | PRICE
Table No:2
Table Name:Customer Table
This Table contains the following columns:
Customer Name | CELL | ADDRESS
Table No:3
Table Name:BOOKS Table
This Table contains the following columns:
BOOK Name | Book Purchase ID | GENRE
so the above is my transactional database.. LEt me know if i am missing any other detail. Anyways now i want to convert the above to start schema ?? How would i acccomplish that .. I tried to read a couple of tutorials but i was a bit confused... so if you guys could assist me on this i would be really thnakfull.

David_Aldridge wrote:
thinking in general about this, it sounds like what you need is a set of four tables:
Dim_Cust -- stores customer details as a dimension
Dim_Book -- stores book details as a dimension
Dim_Date -- stores dates for transactions
Fct_Book_Sales -- stores the transactions themselves as the purchase of a book for a certain price by a customer on a date.
Use synthetic keys for all but the Dim_Date.Okay i kind of got lost on the way here is wht i know so far regarding the star schema
"A star schema consists of fact tables and dimension tables. Fact tables contain the quantitative or factual data about a business--the information being queried. This information is often numerical, additive measurements and can consist of many columns and millions or billions of rows. Dimension tables are usually smaller and hold descriptive data that reflects the dimensions, or attributes, of a business. SQL queries then use joins between fact and dimension tables and constraints on the data to return selected information."
so from your explaination there are going to be 3 dimension tables
Dim_Cust (Details about the customers) (Customer_ID,Cell No,Address)
Dim_Book(Details about the Books) (Book Name ,ID,Genre)
Dates (I am confused about the dates part)
Fct_Book_Sales (Confused about this part also)
and one last thing What would the fact table look like ??

Similar Messages

How to convert database in 3NF to Star schema

Hi
Can anyone help me out to convert the database in 3NF to Star schema so that it can be used for Business Intelligence.
Our Application will be populating the database in normal 3NF form which may be difficult for the intelligence to generate queries from it. From the documents given, i saw that only star schema containing dimensions table and fact table is simpler to generate reports. Is there any tool that would convert the schema from 3NF to star schema?
Regards
S. Kokila

Hi,
I do not know any tools that would do this for you. You can apply a certain logic to create your dimensions and facts, but decisions will have to be taken along the way.
You need to know the basis of database design for datawarehousing. A few good books and articles are available on the subject.
Bonne lecture!

What happens when i remove Dimension table in extended star schema

*how to integrate the flex builder web dynpro and xcelsius?
i found some scenarios like when the content of the table change the chart will changes for the changed data in the table using flash islands and web dynpro.
my scenario is like this.
when i changed the chart with sliders automatically the content in the table will update to the chart level ? but both table and chart will be in the same dashboard. how can i work out this scenario using flash islands, flex and web dynpro>
thanks in Advance*

Hi Sateesh,
Please go through this URL you will get overall Idea about Extended Star schema with DIM ID's,SID's and Data flow.
http://help.sap.com/saphelp_nw70/helpdata/EN/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
I hope it will help you.
Regards
Suresh B.G.

Relation between different tables in extended star schema

Hi Experts,
I searched all many threads to understand the how Attribute change run is used for
But a small question is going still.
Is attribute change run used for getting consistent data from aggregates or from infocubes.
Attribute change run is used to update the master data .Then what is the use of "activate master data "
in context menu of the master data infoobject.
Somewhere I have read that Attribute change run is used for updating Aggregates but it has got nothing to
do with Infocubes,Is it right ?
Please clarify me
Thanks in advance
Sundar

Hi Sundar,
Is attribute change run used for getting consistent data from aggregates or from infocubes.
The purpose of ACR is to update the changes happened in master data to aggregates not for aggregates.
Attribute change run is used to update the master data .Then what is the use of "activate master data "
in context menu of the master data infoobject.
when you click on activate master data, the data in P or Q or X or Y tables will get activated(if any records with version M will turned to version A)
ACR is used to update the same changes to aggregates
Somewhere I have read that Attribute change run is used for updating Aggregates but it has got nothing to
do with Infocubes,Is it right ?
Yes you are wright.here we have small logic when ACR is running if you start any rollup step it will get fail.
While ACR is running aggregates will get locked
Regards,
Venkatesh

EIS and setup of Star Schema

I want to be able to drill back into our ERP system from Essbase using EIS. It is my understanding that I need to create a Star Schema in order to get EIS to function properly. Is this correct?Another question is when I create the Dimension tables for the Star Schema, is a Parent Child Relationship sufficent or do I need to create a column for each level/generation in the dimension? Do I need this for Dimension build or Drill back reports?Thanks in advance.

EIS does require a star schema. You can find out additional information in the Essbase.com White Papers section - there's a white paper there that should address your questions about tables:http://www.essbase.com/main.asp?webpagekey=428Regards,Kimberley Kent

Snowflake/Star Schema in OBIEE

Hi Gurus,
I would be very glad if you can help me to resolve this problem.
Before posting, I searched the forum there are similar queries(Circular Join) but I do not get the solution.
I have fact and dimension tables builded with star schema which I do not have any problem. But there is a fact table which has dimension to dimension relation between them.
When I tried to connect them which I explained in below I am getting error(Circular join problem) or If I fix the error, In Obiee analysis I am getting another error which says there is no fact table between tables. Let me explain the situation;
I have 4 dimensions table and a fact table;
connection between them;
Sales Dim(1) ---> Fact.A(N)
Date Dim(1) ---> Fact.A(N)
Customer Dim(1) ---->Fact.A(N)
Sales Channels Dim(1) --->Sales Dim(N)
Date Dim(1)---> Sales Dim(N)
Date Dim(1) ---->SalesChannel(N)
I can see that there are bunch of circular join in here :(. I did not understand to use Alias to resolve this problem.
For instance; Dim A--->Fact AC
Dim B --->Fact AC
Dim A---> Dim B
If I create a Alias for Dim A, I can resolve the problem but which of them should I drag to Presentation Layer(at the end both of them same but Dim A used by other fact tables too). If I drag to Dim A nothing will be change or I am totally lost:(
If you do not understand the question I will try to be more clear.
I would be very happy if you can help me.
Thanks in advance.
M.S

Hi M.S,
If I got your issue correctly, then the issue is the join between the 'Date Dim' -> 'Sales Dim' and 'Date Dim' -> 'Channels Dim'. I was just trying to understand the model here, and thinking why do you need a join between these dimensions.
Anyway, a report with Sales and Date dimension can always be resolved through the Fact table. However, if you still want all combinations across this dimension, you can still use a implicit column methodology for this issue. you might want to refer to venkat's blog on this approach here.http://www.rittmanmead.com/2009/08/oracle-bi-ee-10-1-3-4-1-reporting-on-non-transactional-dimension-values-equivalence-of-outer-joins/
Hope this helps.
Thank you,
Dhar

Injecting data into a star schema from a flat staging table

I'm trying to work out a best approach for getting data from a very flat staging table and then loading it into a star schema - I take a row from a table with for example 50 different attributes about a person and then load these into a host of different tables, including linking tables.
One of the attibutes in the staging table will be an instruction to either insert the person and their new data, or update a person and some component of their data or maybe even to terminate a persons records.
I plan to use PL/SQL but I'm not sure on the best approach.
The staging table data will be loaded every 10 minutes and will contain about 300 updates.
I'm not sure if I should just select the staging records into a cursor then insert into the various tables?
Has anyone got any working examples based on a similar experience?
I can provide a working example if required.

The database has some elements that make SQL a tad harder to use?
For example:
CREATE TABLE staging
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL,
dial_number VARCHAR2(30) NULL,
Is_Contactable CHAR(1) NULL);
INSERT INTO staging
(person_id, title, initials, forename, middle_name, surname, dial_number)
VALUES ('12345', 'Mr', 'NULL', 'Joe', NULL, 'Bloggs', '0117512345','Y')
CREATE TABLE person
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKPerson ON Person
(Person_ID ASC);
ALTER TABLE Person
ADD CONSTRAINT XPKPerson PRIMARY KEY (Person_ID);
CREATE TABLE person_comm
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL ,
comm_id NUMBER(10) NOT NULL );
CREATE UNIQUE INDEX XPKPerson_Comm ON Person_Comm
(Person_ID ASC,Comm_Type_ID ASC,Comm_ID ASC);
ALTER TABLE Person_Comm
ADD CONSTRAINT XPKPerson_Comm PRIMARY KEY (Person_ID,Comm_Type_ID,Comm_ID);
CREATE TABLE person_comm_preference
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL
Is_Contactable CHAR(1) NULL);
CREATE UNIQUE INDEX XPKPerson_Comm_Preference ON Person_Comm_Preference
(Person_ID ASC,Comm_Type_ID ASC);
ALTER TABLE Person_Comm_Preference
ADD CONSTRAINT XPKPerson_Comm_Preference PRIMARY KEY (Person_ID,Comm_Type_ID);
CREATE TABLE comm_type
comm_type_id NUMBER(10) NOT NULL ,
NAME VARCHAR2(25) NULL ,
description VARCHAR2(100) NULL ,
comm_table_name VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKComm_Type ON Comm_Type
(Comm_Type_ID ASC);
ALTER TABLE Comm_Type
ADD CONSTRAINT XPKComm_Type PRIMARY KEY (Comm_Type_ID);
insert into comm_type (comm_type_id, NAME, description, comm_table_name) values ('23456','HOME PHONE','Home Phone Number','PHONE');
CREATE TABLE phone
(phone_id NUMBER(10) NOT NULL ,
dial_number VARCHAR2(30) NULL);
Take the record from Staging then update:
'person'
'Person_Comm_Preference' Based on a comm_type of 'HOME_PHONE'
'person_comm' Derived from 'Person' and 'Person_Comm_Preference'
Then update 'Phone' with the number based on a link derived from 'Phone' which is made up of Person_Comm Primary_Key where 'Comm_ID' (part of that composite key)
relates to the Phone table Primary_Key which is Phone_ID.
Does you head hurt as much as mine?

Resolving loops in a star schema with 5 fact tables and 6 dimension tables

Hello
I have a star schema, ie 5 FACT tables and 7 dimension tables, All fact tables share the same dimension tables, some FACT tables share 3 dimesnsions, while other share 5 dimensions.
I did adopt the best practices, and as recommended in the book, I tried to resolve them using Context, as it is the recommended option to Alias in a star schema setting. The contexts are resolved, but I still have loops. I also cleared the Multiple SQL Statement for each context option, but no luck. I need to get this resoved ASAP

Hi Patil,
It is not clear what exactly is the problem. As a starting point you could set the context up so that it only covers the joins from fact to dimension.
Fact A, joins Dim 1, Dim 2, Dim 3, and Dim 4
Fact B, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 5
Fact C, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 6
Fact D, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 7
Fact E, joins Dim 1, Dim 2, Dim 4 and Dim 6
If each of these are contexts are done and just cover the joins from fact to dim then you should be not get loops.
If you could lay out your joins like above then it may be possible to specify the contexts/aliases that should work.
Regards
Alan

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

Star schema cannot be mapped to multiple tables

Hello!
I am mapping dimension in AWM.
When I am drawing lines from the source columns to the target objects "Member". I get the message "star schema cannot be mapped to multiple tables". Sometimes I can workaround the problem by drawing the lines in a different order. But this dose not always work
I have a dimension that have several levels and hierarchy and I always get the message "star schema cannot be mapped to multiple tables" no matter in witch order I draw the lines to "Member".
Why do I get this message and how do I do to solve the problem?
Best regards,
Tina N Mörnstam

Hi Tina:
Is your dimension snowflaked? Are you mapping from more than one source table to the target dimension? Is the hierarchy formed over different tables?
Hazbleydi C. Verástegui

Star Schema tables Creation

If I am creating a BI analytical application from sample Sales Hisotory schema's transactional data, what is the first Step I need to do? Should I create a star schema from the transactional tables? If this is correct, What I tool I need to use to create such tables with data? I believe once this is done I can create dimensions , measures and cubes using OWM11g. Some on please help me. I am very very new to OLAP , But has lots of interest in it
Thanks
George

Hi George,
If you are working with 11g - did you install all the latest patches? I strongly recommend applying all available patches when working with 11g. All the information you need is here - http://www.oracle.com/technology/products/bi/olap/collateral/olap_certification.html
As for your question about the criteria for desgining dimension tables, the best advice I can offer is to work with star or snowflake dimensions. You can also see sample schema designs for both at these links
Also, in case you haven't already seen it, there is a good blog posting on working with different kinds of dimensions/hierarchies here - http://oracleolap.blogspot.com/2008/01/olap-workshop-4-managing-different.html
Finally, you might find this [white paper|http://www.oracle.com/technology/products/warehouse/pdf/Benefits%20of%20a%20multi-dimensional%20model.pdf] useful as you say you are new to OLAP
Let me know how you get on
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Error in database parameter for star schema table in RSRV

Hi Experts,
In RSRV, I executed the following checks in my cube and it is showing me the following error:-
1) Check database parameter for star schema table for InfoCube ZMM_MVAL
564971 units missing from fact table /BIC/FZMM_MVAL; see details
Message no. RSRV134
Diagnosis
In the fact table /BIC/FZMM_MVAL records have been found that contain values other than zero for key figures that have units, but that have no value for the unit of the key figure. Since the value of the unit has to correspond to the value of the key figure, this inidicates an error when the data was loaded. The values of the units have not been loaded into BW correctly. Choose Details to display the incorrect records.
2) Consistency of time dimension of InfoCube ZMM_MVAL
/BIC/FZMM_MVAL PARTITIONED 1878 ( 30 - 50 )
Please advise me on this.
Thanks in Advance.
Aparna

As mentioned in the log, check the Unit KFs in your cube and make sure that unit is populated for all such values.
e.g. if Qty is 5 KG, then unit KF will have 5 and unit info object should have KF.
Regards,
Gaurav

How to join 2 star schemas using a Dimensional table( like Bridge Table)

How to join 2 star schemas using a Dimensional table( like Bridge Table) in OBIEE?

Complex joins and Content levels is all you need, have you tried the forum search?

Why do we need SSIS and star schema of Data Warehouse?

If SSAS in MOLAP mode stores data, what is the application of SSIS and why do we need a Data Warehouse and the ETL process of SSIS?
I have a SQL Server OLTP database. I am using SSIS to transfer my SQL Server data from OLTP database to a Data Warehouse database that contains fact and dimension tables.
After that I want to create cubes using SSAS form Data Warehouse data.
I know that MOLAP stores data. Do I need any Data warehouse with Fact and Dimension tables?
Is not it better to avoid creating Data warehouse and create cubes directly from OLTP database?

Another thing to note is data stored in transactional system may not always be in end user consumable format for ex. we may use bit fields/flags to represent some details in OLTP as storage required ius minimum but presenting them as is would not make any
sense to user as they would not know what each bit value represents. In such cases we apply some transformations and convert data into useful information for users to understand. This is also in the warehouse so that information in warehouse can directly be
used for reporting. Also in many cases the report will merge data from multiple source systems so merging it on the fly in report would be tedious and would have hit on report server. In comparison bringing them onto common layer (warehouse) and prebuilding
aggregates would be benefitial for the report performance.
I think (not sure) we join tables in SSAS queries and calculate aggregations in it.
I think SSAS stores these values and joined tables and we do not need to evaluates those values again and this behavior is like a Data Warehouse.
Is not it?
So if I do not need historical data, Can I avoid creating Data Warehouse?
On the backend SSAS uses queries only to extract the data
B/w I was not explaining on SSAS. I was explaining on what happens inside datawarehouse which is a relational database by itself. SSAS is used to built cube (OLAP structures) on top of datawarehouse. star schema is easier for defining relationships
and buidling aggregations inside SSAS as its simple and requires minimal lookups to be performed. Also data would be held at lowest granularity level which can easily be aggregated to required levels inside OLAP cubes. Cube processing is very resource
intensive and using OLTP system would really have a huge impact on processing performance as its nnot denormalized and also doing tranformation etc on the fly adds up to complexity. Precreating a layer (data warehouse) having data in required format would
make cube processing easier and simpler as it has to just cross join tables and aggregate data based on relationships defined and level needed inside the cube.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Help to design Star Schema facts and dimensions

Hi
I have the following summarized table that I need to convert to the star schema.
I am totally confused how to create the dimensions. Any help to start with this will be highly appreciated.
I am in an urgent need of it.
Month
AccountId
Cust_id
City
State
Zip
Zip4
AccountMonthsOnBooks
APR
APY
AccountType
OriginationChannel
RewardType
BankProductType
BranchId
CycleEndDate
CycleStartDate
DaysInCycle
DaysInStatement
DirectDepositLastUseDate
FlagElectronicBilling
FlagOverdrawnThisMonth
FlagOverdrawnThisCycle
FlagPaidOverdraft
NumberofTimesOverdraft
OnlineBankingEnrolledIndicator
OnlineBankingLastUseDate
WebLoginCount
OpenDate
OverdraftAmount
OverdraftCount
OverdraftLastDate
OverdraftProtectionIndicator
OverDraftProtectionSourceType
PaidOverdraftAmount
PaidOverdraftCount
PopulationClassIndicator
ProductId
RewardAccruedAmount
RewardBalance
RewardCurrency
RewardRedeemedAmount
RewardsDateEnrolled
RewardsExpirationAmount
RewardTypeBank
RiskScore
RiskScorePlugged
StatementEndDate
StatementStartDate
SubProductId
BalanceADBAmount
BalanceADBNonSweepNonZBAAmount
CycleBeginningBalance
CycleEndingBalance
MonthBeginningBalance
MonthEndingBalance
StatementBeginningBalance
StatementEndingBalance
NonSystemCreditTotalAmount
NonSystemCreditTotalCount
NonSystemDebitTotalAmount
NonSystemDebitTotalCount
ACHCreditTotalAmount
ACHCreditTotalCount
ACHDebitTotalAmount
ACHDebitTotalCount
ACHPPDBillPayCreditAmount
ACHPPDBillPayCreditCount
ACHPPDBillPayDebitAmount
ACHPPDBillPayDebitCount
ACHPPDPayrollDirectDepositCreditAmount
ACHPPDPayrollDirectDepositCreditCount
ACHPPDPayrollDirectDepositDebitAmount
ACHPPDPayrollDirectDepositDebitCount
ATMCreditAmount
ATMCreditCount
ATMDebitAmount
ATMDebitCount
ATMOffUsCashDepositAmount
ATMOffUsCashDepositCount
ATMOffUsCashWithdrawalAmount
ATMOffUsCashWithdrawalCount
ATMOffUsCheckDepositAmount
ATMOffUsCheckDepositCount
ATMOffUsTransferCreditAmount
ATMOffUsTransferCreditCount
ATMOffUsTransferDebitAmount
ATMOffUsTransferDebitCount
ATMOnUsCashDepositAmount
ATMOnUsCashDepositCount
ATMOnUsCashWithdrawalAmount
ATMOnUsCashWithdrawalCount
ATMOnUsCheckDepositAmount
ATMOnUsCheckDepositCount
ATMOnUsTransferCreditAmount
ATMOnUsTransferCreditCount
ATMOnUsTransferDebitAmount
ATMOnUsTransferDebitCount
BranchCheckDepositAmount
BranchCheckDepositCount
BranchCheckWithdrawalAmount
BranchCheckWithdrawalCount
BranchCreditTotalAmount
BranchCreditTotalCount
BranchDepositAmount
BranchDepositCount
BranchDebitTotalAmount
BranchDebitTotalCount
BranchMiscellaneousCreditAmount
BranchMiscellaneousCreditCount
BranchMiscellaneousDebitAmount
BranchMiscellaneousDebitCount
BranchWithdrawalAmount
BranchWithdrawalCount
BranchTransferCreditAmount
BranchTransferCreditCount
BranchTransferDebitAmount
BranchTransferDebitCount
ChargeOffDebitAmount
ChargeOffDebitCount
CheckCausingOverdraftCreditAmount
CheckCausingOverdraftCreditCount
CheckCausingOverdraftDebitAmount
CheckCausingOverdraftDebitCount
CheckCreditTotalAmount
CheckCreditTotalCount
CheckDebitTotalAmount
CheckDebitTotalCount
CheckReturnedCreditAmount
CheckReturnedCreditCount
CheckReturnedDebitAmount
CheckReturnedDebitCount
CheckStopPaymentCreditAmount
CheckStopPaymentCreditCount
CheckStopPaymentDebitAmount
CheckStopPaymentDebitCount
CreditTotalAmount
CreditTotalCount
DebitTotalAmount
DebitTotalCount
FeeACHBillPayAmount
FeeACHBillPayCount
FeeAnnualAmortizedAmount
FeeAnnualAmount
FeeAnnualCount
FeeATMOffUsAmount
FeeATMOffUsBalanceInquiryAmount
FeeATMOffUsBalanceInquiryCount
FeeATMOffUsCount
FeeATMOffUsTransferAmount
FeeATMOffUsTransferCount
FeeATMOnUsCheckInquiryAmount
FeeATMOnUsCheckInquiryCount
FeeDormantAmount
FeeDormantCount
FeeEarlyWithdrawalAmount
FeeEarlyWithdrawalCount
FeeForeignTransactionAmount
FeeForeignTransactionCount
FeeMonthlyAmount
FeeMonthlyCount
FeeNSFAmount
FeeNSFCount
FeeODPTransferAmount
FeeODPTransferCount
FeeOtherAmount
FeeOtherCount
FeeOverdraftAmount
FeeExtendedOverdraftAmount
FeeOverdraftCount
FeeExtendedOverdraftCount
FeePOSPINPurchaseAmount
FeePOSPINPurchaseCount
FeeReturnedCheckAmount
FeeReturnedCheckCount
FeeStopPaymentAmount
FeeStopPaymentCount
FeeTotalAmount
FeeTotalATMCreditAmount
FeeTotalATMCreditCount
FeeTotalATMDebitAmount
FeeTotalATMDebitCount
FeeTotalNonPenaltyAmount
FeeTotalNonPenaltyCount
FeeTotalPenaltyAmount
FeeTotalPenaltyCount
FeeWaiverACHBillPayAmount
FeeWaiverAnnualAmount
FeeWaiverATMOffUsAmount
FeeWaiverATMOffUsBalanceInquiryAmount
FeeWaiverDormantAmount
FeeWaiverForeignTransactionAmount
FeeWaiverMonthlyAmount
FeeWaiverNSFAmount
FeeWaiverODPTransferAmount
FeeWaiverOtherAmount
FeeWaiverOverdraftAmount
FeeWaiverExtendedOverdraftAmount
FeeWaiverStopPaymentAmount
FeeWaiverTotalAmount
FeeWaiverTotalNonPenaltyAmount
FeeWaiverTotalPenaltyAmount
FeeWaiverWireTransferAmount
FeeWireTransferAmount
FeeWireTransferCount
FraudTransactionAmount
FraudTransactionCount
InterestPaymentCreditAmount
InterestPaymentDebitAmount
InternetTransferCreditAmount
InternetTransferCreditCount
InternetTransferDebitAmount
InternetTransferDebitCount
ODPTransferCreditAmount
ODPTransferCreditCount
ODPTransferDebitAmount
ODPTransferDebitCount
OtherCreditAmount
OtherCreditCount
OtherCreditReversalAmount
OtherDebitAmount
OtherDebitCount
OtherDebitReversalAmount
OtherTransferCreditAmount
OtherTransferCreditCount
OtherTransferDebitAmount
OtherTransferDebitCount
PhoneTransferCreditAmount
PhoneTransferCreditCount
PhoneTransferDebitAmount
PhoneTransferDebitCount
POSSIGForeignCreditAmount
POSSIGForeignCreditCount
POSSIGForeignDebitAmount
POSSIGForeignDebitCount
POSPINCreditTotalAmount
POSPINCreditTotalCount
POSPINDebitTotalAmount
POSPINDebitTotalCount
POSSIGCreditTotalAmount
POSSIGCreditTotalCount
POSSIGDebitTotalAmount
POSSIGDebitTotalCount
ReversalFeeACHBillPayAmount
ReversalFeeEarlyWithdrawalAmount
ReversalFeeForeignTransactionAmount
ReversalFeeMonthlyAmount
ReversalFeeNSFAmount
ReversalFeeODPTransferAmount
ReversalFeeOtherAmount
ReversalFeeOverdraftAmount
ReversalFeeExtendedOverdraftAmount
ReversalFeePOSPINPurchaseAmount
ReversalFeeReturnedCheckAmount
ReversalFeeStopPaymentAmount
ReversalFeeTotalAmount
ReversalFeeTotalNonPenaltyAmount
ReversalFeeTotalPenaltyAmount
ReversalFeeWireTransferAmount
SubstituteCheckDepositAmount
SubstituteCheckDepositCount
SubstituteCheckWithdrawalAmount
SubstituteCheckWithdrawalCount
SystemCreditTotalAmount
SystemCreditTotalCount
SystemDebitTotalAmount
SystemDebitTotalCount
TargetSweepCreditAmount
TargetSweepCreditCount
TargetSweepDebitAmount
TargetSweepDebitCount
WaiverFeeReturnedCheckCount
WireTransferFedCreditAmount
WireTransferFedCreditCount
WireTransferFedDebitAmount
WireTransferFedDebitCount
WireTransferInternalCreditAmount
WireTransferInternalCreditCount
WireTransferInternalDebitAmount
WireTransferInternalDebitCount
WireTransferInternationalCreditAmount
WireTransferInternationalCreditCount
WireTransferInternationalDebitAmount
WireTransferInternationalDebitCount
ZBACreditAmount
ZBACreditCount
ZBADebitAmount
ZBADebitCount
AllocatedEquityAmount
CapitalCharge
ContraExpenseCreditLossRecoveryAmount
ContraExpenseFraudRecoveryAmount
EquityCreditAmount
ExpenseCorporateTaxAmount
ExpenseCreditLossWriteOffAmount
ExpenseDepositInsuranceAmount
ExpenseFraudWriteOffAmount
ExpenseMarketingAmount
ExpenseNetworkFeesAmount
ExpenseOperatingAmount
ExpenseOriginationAmortizedAmount
ExpenseOtherAmount
ExpenseTotalAmount
RevenueInterchangeTotalAmount
RevenuePINInterchangeAmount
RevenueSIGInterchangeAmount
RevenueInterestAmount
RevenueOtherAmount
RevenueNetIncomeAmount
RevenuePreTaxIncomeAmount
RevenueTotalAmount
StatusCode
ClosedCode
ClosedDate

user13407709 wrote:
I have the following summarized table that I need to convert to the star schema.
I am totally confused how to create the dimensions. Any help to start with this will be highly appreciated. The first step should be to tell whoever gave you this task that you have no idea what you are doing and set their expectations accordingly.
I am in an urgent need of it.Then it would no longer be urgent and you would have the time to read and learn this.
http://download.oracle.com/docs/cd/E11882_01/server.112/e16579/toc.htm

Converting 3 tables to a star schema ??

Similar Messages

Maybe you are looking for