Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
a Case Study

a Case Study

Ratings: (0)|Views: 26 |Likes:
Published by api-26996193

More info:

Published by: api-26996193 on Oct 14, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

PURPOSE

The purpose of this document is to understand the \u2018Basic transformations\u2019 available in PowerCenter 7.1. These \u2018Transformations\u2019 are vital to development of mappings which carry the information how to extract, transform and load data. This document covers following Transformations based on a running hands-on Case-Study conceiving the use of all these transformations. The Case-Study is divided in parts based on some underlying concept covering one or more transformations at one time. The target definitions developed in one mapping may be used as source definition in another mapping to continue the concept and complete the whole case-study.

The Basic Transformations covered through this document are:
\ue000
FILTER TRANSFORMATION
\ue000
JOINER TRANSFORMATION
\ue000
SORTER TRANSFORMATION
\ue000
EXPRESSION TRANSFORMATION
\ue000
SOURCE QUALIFIER TRANSFORMATION
\ue000
AGGREGATOR TRANSFORMATION
\ue000
LOOKUP TRANSFORMATION
SCENARIO

Conceive a database build around the transactions at a chain of departmental stores. The typical activities at stores include \u2013 maintaining customers information, maintaining employees information and the kind of job they perform, the items information available at the store along with promotion information, the sales and orders, procuring information with manufacturers and distributors.

Thus the database has typically the following table structure:
\ue000
CUSTOMERS
\ue000
EMPLOYEES
\ue000
STORES
\ue000
MANUFACTURERS
\ue000
JOBS
\ue000
DEPARTMENT
\ue000
ITEMS
\ue000
PROMOTIONS
\ue000
ITEMS_IN_PROMOTIONS
\ue000
DISTRIBUTORS
\ue000
ORDERS
Informatica PowerMart / PowerCenter 7 Basic Class \u2013 Hands-on Lab Guide
Lab
PC
PC7
7
1
\ue000
ORDER_ITEMS
PROBLEM STATEMENT

Consider that our objective here is to get the information of the amount of sales done by the chain of departmental stores. Herein we try to know the \u2018Total Cost\u2019 of items sold for each Order (i.e. the amount of transactions done in each order) along with other Order details. The \u2018Order cost\u2019 is the sum of all the \u2018items cost\u2019 in the order with discount adjustments if any. The final target table should reflect the Total Cost against each Order_ID with other Order details. The intermediate target tables can be used as the source for subsequent mappings.

Though in a real scenario, target may be much bigger and will have large number of tables and huge amounts of data in a very organized way to satisfy varied complex queries, we are here safely assuming our final target contains only one table with exactly necessary data to satisfy above query.

Informatica PowerMart / PowerCenter 7 Basic Class \u2013 Hands-on Lab Guide
2
THE SOLUTION ROADMAP

Here our objective is to finally develop a target definition and store the required data in that target to satisfy the above query. For this we will identify the sources required to have the required data and then we pass the data from different source tables though various transformation logic finally loading the data in the target based on the target definition.

We will design four mappings each having one or more transformation logic along
with one target definition.
1.We start by identifying the necessary sources to provide the required data. These
happen to be \u2018Items\u2019 and \u2018Order_Items\u2019 and \u2018Order\u2019 tables in this particular case.
2.We start with Filter transformation wherein all the items which are discontinued

are filtered out in the initial stage itself and subsequently joined with Order_Items using joiner transformation to get Quantity, Price and Discount details for each item. The data is loaded in a target table \u2018TARGET_ITEMS_ORDER\u2019.

3.With using the above target definition as source, the expression transformation is

used to calculate the Item Cost for each item based on Quantity, Price and discount in the all the Orders. The data is loaded in the target table \u2018TARGET_ITEMS_ORDER1\u2019.

4.With this target definition as new source the data is sorted based on the Order_ID

and passed to the Aggregator transformation as sorted input to be grouped by Order_ID. The aggregated sum of Item Costs is taken for each Order_ID. The data is loaded in the Target Table \u2018TARGET_ITEMS_ORDER2\u2019.

5.Finally using the above Target definition as source and using the \u2018Lookup\u2019

transformation we obtain details (from ORDERS table) for each order based on ORDER_ID. We put these details along with the Order costs calculated in above four steps into the final target table \u2018TARGET_ORDER_COST\u2019.

Informatica PowerMart / PowerCenter 7 Basic Class \u2013 Hands-on Lab Guide
3

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->