RAMP UP EXERCISE

Version – 0.1
 DOCUMENT RELEASE NOTICE

The Technical System Design document is released for use in Franklin Resources. This document
contains the system design in layperson’s understandable form.
The intended users of this document are the system designer, developer, and all the project personnel
who are working in this project.
This document is subject to Franklin Templeton Technologies’ (FTT’s) document control and revision
procedures.
Comments, suggestions, and queries related to this document should be addressed to the Project
Manager using the feedback form.
For Internal Use Only
This document is the confidential and proprietary product of Franklin Templeton. Any unauthorized
use, reproduction, or transfer of this manual is strictly prohibited. Copyright © 2004 Franklin
Resources, Inc. (Subject to limited distribution and restricted disclosure only.) All rights Reserved.
Trademark Acknowledgments:
Any and all products or brand names mentioned in this book are trade names, service marks,
trademarks, or registered trademarks of their respective owners.

Prepared/Updated By Garima Gilani Date 12.05.10

Reviewed By Date mm.dd.yy
Approved By Date mm.dd.yy
 REVISION HISTORY

Version Affected
Ref Release Created/ Reviewed Description of the Sections in
(Releas Date Revised by by Revision the
ed) Document
0.1 Garima Rishi Initial Version
 Table of Contents
1.0 INTRODUCTION______________________________________________________5
2.0 Purpose___________________________________________________________5
3.0 Definitions, Acronyms, and Abbreviations_____________________________5
3.1 Acronyms______________________________________________________________5
3.2 Naming Conventions_____________________________________________________5
4.0 ETL (Informatica) Related Objects____________________________________5
5.0 ETL (Informatica) Transformations And Reusable Components (Mapplet)_6
6.0 Database Related Objects___________________________________________7
7.0 Programming Standards____________________________________________8
7.1 Coding standards_______________________________________________________8
7.2 Software Development Tools_____________________________________________8
8.0 ETL LOGIC (Ramp up Exercise)______________________________________10
8.1 Feed to Target Load____________________________________________________10
8.2 WEB MODEL__________________________________________________________10
8.3 PROCESSING STEPS:____________________________________________________11
8.4 SAMPLE FEED:________________________________________________________11
8.5 INTERFACE DOC_______________________________________________________12
8.6 MAPPING DOCUMENT :_________________________________________________12
Approval Log___________________________________________________________14
1.0 INTRODUCTION

This document details out the design approach as well as the designed components for the
Ramp Up Exercise. The document will serve as the single source of information for all the
designed components along with the implementation level details.

2.0 Purpose

The purpose of the document is to capture the technical design details corresponding to
following requirements for the Exercise:

1. Load Financial Advisor data into GID transaction tables.

2. Load the area specific to a given financial Advisor, along with its respective
channel and divisions.

3.0 Definitions, Acronyms, and Abbreviations

3.1 ACRONYMS
Acronym Full Name
GID Global Integrated Data store
ETL Extract Transform Load
SDS System Design Specification
TSD Technical Specification Design
FTT Franklin Templeton Technologies

3.2 NAMING CONVENTIONS

Give the naming conventions that one should follow in the naming the programs, files,
modules etc

4.0 ETL (Informatica) Related Objects

Object Type Object Sub Type Naming Convention Adopted

Folders Folder name GID_ prefix
Shared folder ( For mappings) GID_SH_ prefix
 Load folder GID_LOAD_ Source-system-abbrev

Load input feed to stage load m_source_system_target table_”STG”

Load
Mappings Load Stage to target m_source_system_target table

Functionality is like refreshing a m_source_system_ target table _functionality

matiew, snap shot table
Mapping used for initial load for m_source_system_ target table _”initial”_”stg”
staging
Other
Mapping used for initial load for m_source_system_ target table _”initial”_”tgt
mappings
target
Adhoc: End the mapping name with keyword “adhoc”

Example: m_RIVA_DLR_adhoc
Sessions Sessions Use the same naming convention as mappings but
prefix with s_ instead of m_

Workflows Workflows Use the same naming convention as mappings but

prefix with wf_ instead of m_

5.0 ETL (Informatica) Transformations And Reusable Components

(Mapplet)

Object Name Naming Convention Adopted

Lookups Named as LKP_<<Lookup table name >>

Example: LKP_ERROR_DESC
Source Named as SQ_<<name of the driver source table >>
Qualifier
Example: SQ_SALESOFF
Expression Named as EXP_<<Main functionality >>

Example: EXP_TRIM ( trims white space in the source field data)

Named as EXP_<<Main functionality >>

Example: EXP_TRIM ( trims white space in the source field data)

Router Named as RTR_<<Main functionality >>

Example: RTR_DATA_REJ ( filters data to reject /Target table based upon filtering
conditions)
Stored Named as Procedure name”_PRC”
Procedure
Example GID_GETSEQ_PRC
Mapplets Named as “mplt” + table name and functionality implemented

Example mplt_SH_RELS_INS_UPD ( Mapplet for Insert/update logic on table

GID_SH_RELS
Update Named as UPD_<<target table name >>
Strategy
Example: UPD_DLR
Filter Named as FTR_<<Main functionality >>

Example: FTR_TXN_TYPE_U ( filters data for dealer taxation type = ‘D”)

Rank Named as RNK_<<column name >>

Example: RNK_ DELR_REF_NUMBER ( ranks the records based on ascending order of

 DELR_REF_NUMBER column values)
Aggregate Named as AGG_+<<function and column name >>

Example: AGG_MAX_AMNT_INVESTED (aggregation to achieve max value of column

amnt_invested)

6.0 Database Related Objects

Object Type Naming Convention Adopted

Prefix with “GID_3PTY_”
Stored
Procedure
Prefix with “GID_3PTY_MSG” if used for middleware calls
End with “PRC”
Example GID_3PTY_CREAT_INDEX_PRC
Prefix with “GID_3PTY_”

Prefix with “GID_3PTY_MSG” if used for middleware calls

Stored Functions
End with “FUNC”

Example GID_3PTY_CREAT_INDEX_FUNC
For Specification

Prefix with “GID_3PTY_”

Prefix with “GID_3PTY_MSG” if used for middleware calls
End with “Pks”
Stored Package
For Body

Prefix with “GID_3PTY_”

Prefix with “GID_3PTY_MSG” if used for middleware calls
End with “Pkb”
Views Prefix with “GID_3PTY_”
End with “_VW”
Example GID_3PTY_DEALER_VW
Materialized Prefix with “MV_”
Views
Sequences Table abbreviation and “_SEQ” as suffix
Indexes Prefix with GID_3PTY_IX_Table_abbriviation_column abbreviation(to
make it unique)
End with _FK for Foreign key index
End with _UK for Unique key index

Example GID_3PTY_IX_DELR_NM
Table Trigger Prefix with
GID_3PTY_Table_abbriviation_function( insert/update/delete)
End with “_TRG”

Example GID_3PTY_DEALR_INS_TRG

In addition to the above naming standards, the following conventions have to be

followed throughout:
  All the Path names and the file names will be stored in the parameter files.
 All parameters in one file for the mappings contained in a single folder (not
separate files for each); however, single parameter may be used during initial
development phase.

7.0 Programming Standards

7.1 Coding standards
 All Mappings /Sessions /Workflows to have proper comments
 All Complex Transformations used in each mapping to have proper
comments
 All DB and ETL related objects to adhere to naming convention described in
sections above
 All lookup which have heavy cache size and CPU requirements would be
pushed in Source qualifier
 Minimize database specific function calls in Informatica

 Make use of all performance enhancement features available in Informatica
tool example push down optimization

7.2 Software Development Tools

All the Informatica development will be done on the Informatica development server
(SACSUN59), which has Informatica 8.6 setup.
8.0 ETL LOGIC (Ramp up Exercise)

8.1 Feed to Target Load

1. Dumping up of the data from feed (financial_advisor.txt) into the target table , with
lookup transformations in order to get the Area , Channel and respective divisions
2. Expression transformation used for hard coding the values needed and specifying
the date for the creation or updation of the FA’s data
3. Further details of the transformation described in the mapping document.

8.2 WEB MODEL

GID_3PTY_FA GID_3PTY_FA_AREA

PK Fa_id
First_name
Last_name
City PK Area_id
Place Area
Email FK Channel_id
FK1 Area_id Territory
FACreationDate

FALastUpdateDate

GID_3PTY_CHANNEL GID_3PTY_DIVISION
PK Division_Id
PK Channel_Id
Retail_Territory Division
Retirement_territory
FK Division_Id

GID_3PTY_TARGET_LOAD
 PK fa_id
Status_date
First_name 8.3 PROCESSING STEPS:
Middle_name
1. Loading of data from feed
Last_name
(financial_advisor.txt) into the
Company_Name target table
GID_3PTY_TARGET_LOAD.
Addr_1 2. Lookup on table GID_3PTY_FA ,
Addr_2 in order to get the area_id ,
area_id in turn will retrieve the
State channel_id from
City gid_3PTY_FA_AREA
3. Lookup on
Zip GID_3PTY_CHANNEL will give
the division_id based on the
Email
channel_id
Phone 4. Lookup on
GID_3PTY_DIVISION will give
FA_Title_CD the division name based on the
FA_Desc division_id found.

Retail_territory
8.4 SAMPLE FEED:
Retirement_Territory
Territory Attached financial_advisor.txt feed
Area to be used as source.
It contains all the information of a
Division financial advisor that is to be loaded in
the target table.
FA_Last_Update_Date
FA_Creation_Date

financial_Advisor.zip

8.5 INTERFACE DOC

Attached is the interface doc

Explains in detail the columns along with their precisions, data type and delimiter to be
used.
Interface_doc.zip
 APPROVAL LOG
Project Name: ____________________________________________________________
Program Manager: ____________________________________________________________
Business Project Manager:______________________________________________________
Technical Project Manager:_____________________________________________________
The Technical System Design Document for the above-noted project has been reviewed and
approved with the appropriate signature(s) below.
Approved
Not approved

The Technical System Design Document for the above-noted project has been reviewed but
not approved for the following reason(s):
_____________________________________________________
_____________________________________________________

_______________________________________________________________________ ___________________________
Technical Project Manager or Designee Signature Date