Informatica Etl Naming Conventions

Informatica ETL Naming Conventions These standards should be followed on all new development and rework of existing development objects. Any existing objects (i.e. Production) should only be modified if the opportunity presents itself (i.e. changes to mappings, workflows, etc.). (Note: The list includes new or changed standards (noted with the entry being shaded) as a result of the PowerMart version upgrade to PowerCenter 7.1.3)

Repository Objects

Naming Convention

Mapping Name

Workflow Names

m_<meaningful name> (Examples: m_RefreshSIQREPL, m_PERSON) s_<mapping name> (Example: s_m_PERSON) Folder names for new users will be their department followed by their username. Existing users’ folder names are typically their group followed by their user name. Folder Names may also be based on project, subject area, and promotion group. <session_name>.log OR <workflow_name>.log <session_name>.bad Do not make any distinction here - Informatica color-codes the sources and targets, so it's easy to tell. We do try to prefix these with a folder name, so that when shortcuts or global objects are created we can tell where they originally reside. wflw_<meaningful name>

Workflow Objects

Naming Convention

Worklet Names Command Line Names Event Names Decision Names Control Names Email Names Assignment Names Timer Names

wklt_<meaningful name> cmd_<meaningful name> evtw_<meaningful name> for a wait event evtr_<meaningful name> for a raise event dcsn_<meaningful name> cntrl_<meaningful_name> email_<meaningful_name> asgmnt_<meaningful_name> tmr_<meaningful_name>

Transformation Objects

Naming Convention

Advanced External Procedure Transformation Aggregator Transformation

aep_<procedure name> agg_<meaningful name> that leverages the expression or a name that describes the processing being done.

Session Name Folder Name

Log Files Bad Files Source-name & Target-name

/opt/pdfcoke/conversion/tmp/scratch4/24389251.doc

Expression Transformation Filter Transformation Joiner Transformation Lookup Transformation Mapplet Normalizer Transformation Rank Transformation Source Qualifier Transformation Update Strategy Transformation Stored Procedure Transformation Sequence Generator Transformation Router Transformation Sorter Transformation Custom Transformation Transaction Control Transformation XML Source Qualifier Transformation Application Source Qualifier Transformation MidStream XML Parser Transformation MidStream XML Generator Transformation Union Transformation

exp_< meaningful name > that leverages the expression or a name that describes the processing being done. fil_< meaningful name > that describes the processing being done. jnr_<SourceTable/FileName1_SourceTable/FileN ame2> lkp_ mplt_< meaningful name > nrm_< source name > rnk_< meaningful name > that describes the processing being done. sq_<meaningful name> upd_<meaningful name> sp_<procedure name> (Ex_ProcedureName External Procedure Transform can also be used) seq_<meaningful name> rtr_<meaningful name> srt_<meaningful name> cust_<meaningful name> that leverages the expression or name that describes the processing being done. trctrl_<meaningful name> that leverages the expression or name that describes the processing being done. XMLsq_<meaningful name> Appsq_<meaningful name> XMLprse_<meaningful name> that leverages the expression or name that describes the processing being done. XMLgen_<meaningful name> that leverages the expression or name that describes the processing being done. un_<meaningful name> that leverages the expression or name that describes the processing being done.

Guidelines for naming ports and variables (Not all teams will use these variables in the same way so below are some basic guidelines for naming them).

Ports and Variables

Naming Standards

Input Ports Output Ports Variable Ports

Prefixed with: in_fieldname Prefixed with out_fieldname Prefixed with v_function

/opt/pdfcoke/conversion/tmp/scratch4/24389251.doc