Professional Documents
Culture Documents
Informatica Banking Project
Informatica Banking Project
Client Introduction:
Main objective of this project is we are providing a system with all the information
regarding Transactions of entire banks all over the country. We will get the daily transaction
data from all branches at the end of the day. We have to validate the transactions and
implement the business logic based on the transactions type or transaction code. We have
to load all historical data into DWH and once finished historical data. We have to load Delta
Loads.
Each transaction contains Transaction code. Based on the transaction code we can
identify whether that transaction belongs to withdraw, deposit, loan, payment… based on that
code business logic will be change. We validate and calculate the measure and load to
database.
In Informatica mapping, we first lookup all the transaction codes with code master
table to identify the transaction type to implement the correct logic and filter the unnecessary
transactions. Because in BANK there are lot of transactions will be there but we have to
consider only required transactions for the project. The transaction code exists in the code
master table are only transactions we have to consider and other transactions load into one
table called Wrap table and invalid records( transaction code missing, null, spaces) to Error
table. For each dimension table we are creating surrogate key and load into DWH tables.
SCD2 Mapping:
We are implementing SCD2 mapping for customer dimension to keep history of the customers.
We are using SCD2 Date method.
Architecture of Project:
SCD2 Mapping:
We are implementing SCD2 mapping for customer dimension to keep history of the customers.
We are using SCD2 Date method.
Architecture of Project:
Design:
High Level Design Document, Based on the Technical specs. Developers has to create
the HLD, it will have the Informatica flow chart. What are the transformations required for
that mapping. HLD will cover only 75% of requirement.
UTP:
Development:
UAT - User Accept Testing. Client will do the UAT. This is last phase of the ETL project.
Production:
50% offshore 50% onsite
Work will be distributed between offshore and onsite based on the run time of the Loading.
Mapping bugs needs to fix by Development team. Development team will support for warranty
period based on agreement days.
In ETL projects Three Repositories. For each repository access permissions and location will be
different.
Development: E1
Testing: E2
Production: E3
In ETL projects Three Repositories. For each repository access permissions and location will be
different.
Development: E1
Testing: E2
Production: E3
Dimensions:
Mapping explanation:
o Analysis
o Requirement Gathering
o Design
o Development
o Testing
Production -
Analysis and Requirement Gathering:
HLD: Unit Test Plan. Write the test cases based on the requirement.
Testing:
Employee
Customer
Agent
Transaction
Date
http://informatica-
kareem.blogspot.in/2012/08/informatica-project.html
https://www.scribd.com/doc/48634480/informatica-project