Thanks a Lot.
It's good to know I found someone from Nepali community who has DW knowledge and willing to help.
You are right, Employee in Dimension rather than a fact table, I should have given better example.

This is What I am trying to do. I have Relational DB in Sql with about 200 tables, I need to do the financial analytic so I am trying to Build a data mart in SQL'05 from my RDMBS. So I can use the Oracle Business Intelligence on data mart to run the trends over time period and transactions such as payments, reserves etc to create some financial reports etc. At this moment, I am little knowledgeable on DW concepts as of yet.

Please Suggest how to create a star schema from this example below:

1) DimClaim (Its as 1 to Many rel to DimUnits and  also to DimDiary)
2) DimEmployee (DimEmployee Many to One -->DimClaim)
3) DimDiary (DimDiary Many to One-->DimClaim
3) DimUnit (DimUnit Many to One ->DimClaim)
4) FactPayments
5) FactReserve
6) FactRefunds
etc
FactPayments, FactReserve,FactRefunds has Many to One->DimUnit

As explained above:
All Fact tables are joined to DimUnit in Many-1.(All the transactions are at Unit level)
DimUnit is Joined to DimClaim in Many-1
DimEmployee,DimDiary are Joined to DimClaim in Many-1

After I build a Schema using above relationship,
If I say "Give me particular's Employee's Total Payment", I get error and it says that Employee is not linked with payments.
(However it is defiened in my joins because,
*Employee is Linked with DimClaim
*DimClaim is linked with DimUnit and
* DimUnit is linked with FactPayments)
All the data warehousing resources i see, there is a not single example that gives concpt of this, would you please help and suggest where to start to learn DW. MSDN?
Thanks