Informatica Naming Standards V2 0

7/29/2019 Informatica Naming Standards V2 0

1/8

First Indian Corporation

Page 1 of 8

First Indian Corporation Private Limited

INFORMATICA

Naming Standards

Version 2.0

Created by

Swapna Bondada

September 2009


2/8


Version History

Version No. Release Date Released By Description of Changes

1.0 09/15/2009 Swapna Bondada Initial Draft

2.0 10/05/2009 Swapna Bondada Added db connection & parameterstandards

Page 2 of 8


3/8


TABLE OF CONTENTS

1 Introduction.......................................................................................................................41.1 Purpose.......................................................................................................................4

2 Naming Conventions........................................................................................................42.1 ETL Naming Conventions.........................................................................................4

2.1.1 Repository Objects..............................................................................................42.1.2 Files.....................................................................................................................52.1.3 Transformation Objects......................................................................................62.1.4 Workflow Tasks..................................................................................................72.1.5 DB connections...................................................................................................7

2.1.6 Mapping Parameters & Variables.......................................................................7

Page 3 of 8


4/8


1 Introduction

1.1 Purpose

The purpose of this document is to define the ETL naming standards and guidelines thatshould 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 ObjectsNaming Convention

1. Mapping m___< MiscInformation>_

ETL Step can be -

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_Load3. Load data to final table

m_MLS_KDP_Load

Page 4 of 8


5/8


2. Mapplet mplt_ _

3. Session s_ Example: s_MLS_KDP_Load_Ins is without m_

If more than one session has to be created for a mapping, thens_

4. Worklet wl_ Example: wl_MLS_Load

5. Workflow wf__Example: wf_MLS_DAILY_Load

6. SourceFolderName

For Flat File SourcesFlat_File_Example:Flat_File_KDP

For Data Base Sources

7. Folders _Common Ex: MLS_Commoncontains a common objects- reusable sources, targets,transformations. Shortcuts need to be created in the main folderand used. Ex: MLS

This folder will contain all the mappings , sessions, workflows ofproduct/project.Folder specific to the developers should be in the followingformat - Ex: boswapna

2.1.2 Files

Files File NomenclatureAll Files will be delimited (ex: Pipe | ). (If and only if required,they should be optionally enclosed by , if there is a chance of thedelimiter (pipe) itself coming in the data value.)

Source Files src___.dat

e.g.: src_mls_kdp_extract.datSplit Source Files src____ins.dat

src____upd.dat

e.g.: src_ mls_kdp_data_upd.dat

Page 5 of 8


6/8


Target Files tgt____upd.dattgt____ins.dat

e.g.:tgt_mls_kdp_data_ins.datLookup Files lkp___.datTemp Files tmp___.dat

2.1.3 Transformation Objects

Sr.No.Transformation Object Naming Convention (in CAPS)

1. Aggregator AGG_TransformationName - a name thatdescribes the processing being done.

2. Application Source Qualifier ASQ_ TransformationName

3. Expression EXP_ TransformationName - a name that

describes the processing being done.4. Custom

(Replaces Advanced External Procedure)

CT_TransformationName

5. External Procedure EXT_ ProcedureName

6. Filter FIL_TransformationName - a name thatdescribes the processing being done.

7. Joiner JNR_ SourceTable/FileName1_SourceTable/FileName2

8. Lookup LKP_ LookupTable (or File) Name(and/or the reason for lookup),

optionally enclosed by

if override is present9. MQ Source Qualifier SQ_MQ_

10. Normalizer NRM_ TransformationName - a name thatdescribes the processing being done.

11. Rank RNK_ TransformationName - a name thatdescribes the processing being done.

12. Router RTR_

13. Sequence Generator SEQ_

14. Sorter SRT_

15. Stored Procedure SP_16. Source Qualifier SQ_

17. Transaction Control TC_ TransformationName

18. UnionTransformation UN_ TransformationName

19. Update Strategy UPD_

20. XML Generator XG_ TransformationName

Page 6 of 8


7/8


21. XML Parser XP_ TransformationName

22. XML Source Qualifier XSQ_

2.1.4 Workflow Tasks

Sr.No.Workflow Object Naming Convention

1. Command CMD_

2. Email Email_

3. Decision DEC_

4. Assignment ASG_

5. Timer TMR_

6. Control CTL_

7. Event Wait Evt_Wait_

8. Event Raise Evt_Raise_

9. Session Configuration SCfg_

10. Scheduler Sch_

2.1.5 DB connections

Sr.No.Connection Object Naming Convention

1. Relational db__

2.

2.1.6 Mapping Parameters & Variables

Sr.No.Connection Object Naming Convention

1. Mapping Parameter $$MP_< meaningful name>

2. Mapping Variable $$MV_

Comments:

Every Mapping, Session and Workflow should contain the respective comments on thehigh level business rules or functionality being implemented during that phase.

Page 7 of 8


8/8


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

Page 8 of 8

Documents

Informatica Naming Standards V2 0