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 |m_ (Examples: m_RefreshSIQREPL, m_PERSON) |

|Session Name |s_ (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 |.log OR .log |

|Bad Files |.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_ |

|Workflow Objects |Naming Convention |

|Worklet Names |wklt_ |

|Command Line Names |cmd_ |

|Event Names |evtw_ for a wait event |

| |evtr_ for a raise event |

|Decision Names |dcsn_ |

|Control Names |cntrl_ |

|Email Names |email_ |

|Assignment Names |asgmnt_ |

|Timer Names |tmr_ |

|Transformation Objects |Naming Convention |

|Advanced External Procedure Transformation |aep_ |

|Aggregator Transformation |agg_ 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_ |

|Lookup Transformation |lkp_ |

|Mapplet |mplt_< meaningful name > |

|Normalizer Transformation |nrm_< source name > |

|Rank Transformation |rnk_< meaningful name > that describes the processing being done. |

|Source Qualifier Transformation |sq_ |

|Update Strategy Transformation |upd_ |

|Stored Procedure Transformation |sp_ (Ex_ProcedureName - External Procedure Transform can |

| |also be used) |

|Sequence Generator Transformation |seq_ |

|Router Transformation |rtr_ |

|Sorter Transformation |srt_ |

|Custom Transformation |cust_ that leverages the expression or name that |

| |describes the processing being done. |

|Transaction Control Transformation |trctrl_ that leverages the expression or name that |

| |describes the processing being done. |

|XML Source Qualifier Transformation |XMLsq_ |

|Application Source Qualifier Transformation |Appsq_ |

|MidStream XML Parser Transformation |XMLprse_ that leverages the expression or name that |

| |describes the processing being done. |

|MidStream XML Generator Transformation |XMLgen_ that leverages the expression or name that |

| |describes the processing being done. |

|Union Transformation |un_ 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 |Prefixed with: in_fieldname |

|Output Ports |Prefixed with out_fieldname |

|Variable Ports |Prefixed with v_function |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download