Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
11K views

Project Explanation

The project involves building a data warehouse to store sales and transaction data from various branches across the US and UK, validating the data, implementing business logic based on transaction codes, loading historical and new delta data on a daily basis. Mappings are used to identify transaction types via code lookups, surrogate keys are generated for dimensions, and SCD Type 2 is used to track changes to customer and account data over time. The team is responsible for development, testing, and providing dependencies to a third party scheduling tool to automate daily loads.

Uploaded by

api-26304852
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
11K views

Project Explanation

The project involves building a data warehouse to store sales and transaction data from various branches across the US and UK, validating the data, implementing business logic based on transaction codes, loading historical and new delta data on a daily basis. Mappings are used to identify transaction types via code lookups, surrogate keys are generated for dimensions, and SCD Type 2 is used to track changes to customer and account data over time. The team is responsible for development, testing, and providing dependencies to a third party scheduling tool to automate daily loads.

Uploaded by

api-26304852
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Project Explanation:

I’m giving generic explanation of the project. Any project either banking or sales or
insurance can use this explanation.

First u have to start with


1) U have to first explain about objective of the project and what is client
expectations
2) u have to start where ur involvement and responsibility of ur job and limitations
of job.
Add some points from post Project Architecture reply like offshore and onsite model
and team structure.. etc.,

Main objective of this project is we are providing a system with all the information
regarding Sales / Transactions (sales if sales domain / transactions if bank domain or
insurance domain) of entire organizations all over the country US / UK ( based on the
client location US/UK/…..). 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. Delta load means
last 24 hrs transactions captured from the source system. In other words u can call it as
Change Data Capture (CDC). This Delta loads are scheduled daily basis. Pick some
points from What is Target Staging Area Post.. Source to Staging mappings, staging to
warehousing.. based on ur comfort level..

Each transaction contains Transaction code.. based on the transaction code u can identify
wheather that transaction belongs to sales, purchase / car insurance, health insurance, /
deposit , loan, payment ( u have to change the words based on the project..) etc., based on
that code business logic will be change.. we validate and calculate the measure and load
to database.

One Mapping explanation :


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 an organization there are lot of transactions will be there but u
have to consider only required transactions for ur project.. the transaction code exists in
the code master table are only transactions u 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 or account dimension to
keep history of the accounts or customers. We are using SCD2 Date method.before telling
this u should know it clearly abt this SCD2 method..careful abt it..
Responsibilities.. pick from Project architecture Post and tell according ur comfortable
level.. we are responsible for only development and testing and scheduling we are using
third party tools..( Control M, AutoSys, Job Tracker, Tivoli or etc..) we simply give the
dependencies between each mapping and run time. Based on that Information scheduling
tool team will schedule the mappings. We won’t schedule in Informatica .. that’s it
Finished…

Please Let me know if u required more explanation regarding any point reply ……

You might also like