Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

Suggested Naming Conventions The following naming conventions appear throughout the Informatica documentation and client tools.

Informatica recommends using the following naming convention when you design mappings and create sessions. Transformations Table A-1 lists the naming convention you should use for all transformations Transformation Aggregator Application Source #ualifier Custom $%pression $%ternal 'rocedure (ilter *oiner )oo,up .# Source #ualifier Normali/er +an, +outer Se0uence !enerator Sorter Stored 'rocedure Transaction Control 1pdate Strategy Naming Convention A!!"TransformationName AS#"TransformationName CT"TransformationName $&'"TransformationName $&T"TransformationName (I)"TransformationName *N+"TransformationName )-'"TransformationName S#".#"TransformationName N+."TransformationName +N-"TransformationName +T+"TransformationName S$#"TransformationName S+T"TransformationName S'"TransformationName TC"TransformationName 1'2"TransformationName

&.) !enerator &.) 'arser &.) Source #ualifier

&!"TransformationName &'"TransformationName &S#"TransformationName

Targets The naming convention for targets is T"TargetName. .appings The naming convention for mappings is m".appingName. .applets The naming convention for mapplets is mplt".appletName Sessions The naming convention for sessions is s".appingName 3or,lets The naming convention for session is wl"3or,letName 3or,flows The naming convention for wor,flows is wf"3or,flowName

You might also like