First Indian Corporation

First Indian Corporation Private Limited

INFORMATICA Naming Standards

Version 2.0

Created by Swapna Bondada

September 2009

Page 1 of 8

First Indian Corporation

Version History
Version No. 1.0 2.0 Release Date 09/15/2009 10/05/2009 Released By Swapna Bondada Swapna Bondada Description of Changes Initial Draft Added db connection & parameter standards

Page 2 of 8

First Indian Corporation

TABLE OF CONTENTS

1 Introduction.......................................................................................................................4 1.1 Purpose.......................................................................................................................4 2 Naming Conventions........................................................................................................4 2.1 ETL Naming Conventions.........................................................................................4 2.1.1 Repository Objects..............................................................................................4 2.1.2 Files.....................................................................................................................5 2.1.3 Transformation Objects......................................................................................6 2.1.4 Workflow Tasks..................................................................................................7 2.1.5 DB connections...................................................................................................7 2.1.6 Mapping Parameters & Variables.......................................................................7

Page 3 of 8

First Indian Corporation

1 Introduction
1.1 Purpose

The purpose of this document is to define the ETL naming standards and guidelines that should be followed for the FACL ETL - Informatica projects. The document intends to set a standard naming convention to be used for mappings, sessions, workflows and other Informatica objects. The intended audiences are developers, Leads, users and testers of FACL ETL projects. The document illustrates the various objects that will be used and provides examples.

2 Naming Conventions
2.1 ETL Naming Conventions
2.1.1 Repository Objects
Sr.N Repository Objectx Objects 1. Mapping

Naming Convention m_<PROJECT/PRODUCT>_<SOURCE>_< Misc Information>_<ETL Step> ETL Step can be - <Refresh/Incr/Ins/Upd/Del/Load/Extract> For eg:1: Extract of data from KDP Source for MLS Project m_MLS_KDP_Extract 2: Transform the data and load them into stage files or tables. m_MLS_KDP_Stage_Load 3. Load data to final table m_MLS_KDP_Load Page 4 of 8

First Indian Corporation

2. 3.

Mapplet Session

mplt_<PROJECT/PRODUCT>_<meaningful name> s_<Mapping Name> Example: s_MLS_KDP_Load_Ins <Mapping name> is without m_ If more than one session has to be created for a mapping, then s_<meaningful name> wl_<meaningful name> Example: wl_MLS_Load wf_<PROJECT/PRODUCT>_<meaningful name> Example: wf_MLS_DAILY_Load For Flat File Sources Flat_File_<source name>
Example: Flat_File_KDP

4. 5. 6.

Worklet Workflow Source Folder Name Folders

7.

For Data Base Sources <source name> <PROJECT/PRODUCT>_Common Ex: MLS_Common contains a common objects- reusable sources, targets, transformations. Shortcuts need to be created in the main folder and used. <PROJECT/PRODUCT> Ex: MLS This folder will contain all the mappings , sessions, workflows of product/project. Folder specific to the developers should be in the following format - <Network Login Name> Ex: boswapna

2.1.2 Files
Files File Nomenclature All Files will be delimited (ex: Pipe | ). (If and only if required, they should be optionally enclosed by , if there is a chance of the delimiter (pipe) itself coming in the data value.) src_<project/product>_<source>_<MeaningfulName>.dat e.g.: src_mls_kdp_extract.dat src_<project/product>_<source>_<MeaningfulName>_ins.dat src_<project/product>_<source>_<MeaningfulName>_upd.dat e.g.: src_ mls_kdp_data_upd.dat

Source Files Split Source Files

Page 5 of 8

First Indian Corporation

Target Files

tgt_<project/product>_<source>_<MeaningfulName>_upd.dat tgt_<project/product>_<source>_<MeaningfulName>_ins.dat e.g.:tgt_mls_kdp_data_ins.dat lkp_<project/product>_<source>_<MeaningfulName>.dat tmp_<project/product>_<source>_<MeaningfulName>.dat

Lookup Files Temp Files

2.1.3 Transformation Objects

Sr.No. 1. 2. 3. 4. 5. 6. 7. 8. Transformation Object Aggregator Application Source Qualifier Expression Custom
(Replaces Advanced External Procedure)

Naming Convention (in CAPS) AGG_TransformationName - a name that describes the processing being done. ASQ_TransformationName EXP_TransformationName - a name that describes the processing being done. CT_TransformationName EXT_ProcedureName FIL_TransformationName - a name that describes the processing being done. JNR_SourceTable/FileName1_SourceTable /FileName2 LKP_LookupTable (or File) <_ov> Name (and/or the reason for lookup), optionally enclosed by <SOURCE> <_ov> if override is present SQ_MQ_<meaningful name> NRM_TransformationName - a name that describes the processing being done. RNK_TransformationName - a name that describes the processing being done. RTR_<meaningful name> SEQ_<meaningful name> SRT_<meaningful name> SP_<StoredPrcedureName/meaningful name> SQ_<table name or meaningful name> TC_TransformationName UN_TransformationName UPD_<meaningful name> XG_TransformationName

External Procedure Filter Joiner Lookup

9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20.

MQ Source Qualifier Normalizer Rank Router Sequence Generator Sorter Stored Procedure Source Qualifier Transaction Control UnionTransformation Update Strategy XML Generator

Page 6 of 8

First Indian Corporation

21. 22.

XML Parser XML Source Qualifier

XP_TransformationName XSQ_<meaningful name>

2.1.4 Workflow Tasks

Sr.No. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Workflow Object Command Email Decision Assignment Timer Control Event Wait Event Raise Session Configuration Scheduler Naming Convention CMD_<meaningful name> Email_<meaningful name> DEC_<meaningful name> ASG_<meaningful name> TMR_<meaningful name> CTL_<meaningful name> Evt_Wait_<meaningful name> Evt_Raise_<meaningful name> SCfg_<meaningful name> Sch_<meaningful name>

2.1.5 DB connections
Sr.No. 1. 2. Connection Object Relational Naming Convention db_<type of database>_<meaningful name>

2.1.6 Mapping Parameters & Variables

Sr.No. 1. 2. Comments: Every Mapping, Session and Workflow should contain the respective comments on the high level business rules or functionality being implemented during that phase. Connection Object Mapping Parameter Mapping Variable Naming Convention $$MP_< meaningful name> $$MV_<meaningful name>

Page 7 of 8

First Indian Corporation

Transformation comments should be provided for detailed understanding of the logic being implemented during that transformation phase.

Page 8 of 8