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 / m_<meaningful name> (Examples: m_RefreshSIQREPL, m_PERSON)
Session Name / s_mapping name> (Example: s_m_PERSON)
Folder Name / 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.
Log Files / session_name.log OR workflow_name.log
Bad Files / session_name.bad
Source-name & Target-name / 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.
Workflow Names / wflw_<meaningful name>
Workflow Objects / Naming Convention
Worklet Names / wklt_<meaningful name>
Command Line Names / cmd_<meaningful name>
Event Names / evtw_<meaningful name> for a wait event
evtr_<meaningful name> for a raise event
Decision Names / dcsn_<meaningful name>
Control Names / cntrl_<meaningful_name>
Email Names / email_<meaningful_name>
Assignment Names / asgmnt_<meaningful_name>
Timer Names / tmr_<meaningful_name>
Transformation Objects / Naming Convention
Advanced External Procedure Transformation / aep_<procedure name
Aggregator Transformation / agg_meaningful name that leverages the expression or a name that describes the processing being done.
Expression Transformation / exp_ meaningful name that leverages the expression or a name that describes the processing being done.
Filter Transformation / fil_< meaningful name that describes the processing being done.
Joiner Transformation / jnr_<SourceTable/FileName1_SourceTable/FileName2
Lookup Transformation / lkp_Lookup Table Name
Mapplet / mplt_< meaningful name >
Normalizer Transformation / nrm_< source name >
Rank Transformation / rnk_< meaningful name that describes the processing being done.
Source Qualifier Transformation / sq_<meaningful name>
Update Strategy Transformation / upd_<meaningful name>
Stored Procedure Transformation / sp_<procedure name (Ex_ProcedureName - External Procedure Transform can also be used)
Sequence Generator Transformation / seq_<meaningful name>
Router Transformation / rtr_<meaningful name>
Sorter Transformation / srt_<meaningful name>
Custom Transformation / cust_<meaningful name> that leverages the expression or name that describes the processing being done.
Transaction Control Transformation / trctrl_<meaningful name> that leverages the expression or name that describes the processing being done.
XML Source Qualifier Transformation / XMLsq_<meaningful name>
Application Source Qualifier Transformation / Appsq_<meaningful name>
MidStream XML Parser Transformation / XMLprse_<meaningful name> that leverages the expression or name that describes the processing being done.
MidStream XML Generator Transformation / XMLgen_<meaningful name> that leverages the expression or name that describes the processing being done.
Union Transformation / 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 StandardsInput Ports / Prefixed with: in_fieldname
Output Ports / Prefixed with out_fieldname
Variable Ports / Prefixed with v_function
E:\Working\AmyPrior\ETL\Documentation\WebDocs\Informatica_ETL_Naming_Conventions.doc