Informatica ETL Naming Conventions

Transformation Naming Standards:

Type of Transform

Naming Convention

Description/Example

Source Definition

[table_name] or
[flat_file_name]

The source definition should carry the same name as the Flat File
or Relational Table that it was imported from. If the source was
created from a shortcut, that should be indicated in the name.

Target Definition

[table_name] or
[flat_file_name]_ACTION

The target definition should carry the same name as the

Relational Table it was imported from. If the target was created
from a shortcut, that should be indicated in the name. Flat File
targets should have _FF at the end of the name. The ACTION
will correspond to the DML being performed on the target INS,
UPD, DEL.

Source Qualifier

sq_[source_name]
sqo_[source_name]

sq_name of Source or sqo_name of Source if SQL override is

used.

Expression

exp_[RelevantDescriptor]

exp_RelevantDescriptionOfTheProcessBeingDone

Update Strategy

upd_[target_name]_ACTION

An update strategy should have a suffix appended to it

corresponding with the particular action (INS, UPD, DEL)

Router

rtr_[RelevantDescriptor]

rtr_ RelevantDescriptionOfTheProcessionBeingDone

Filter

fltr_[RelevantDescriptor]

fltr_ RelevantDescriptionOfTheProcessionBeingDone

Aggregator

agg_[RelevantDescriptor]

agg_ RelevantDescriptionOfTheProcessionBeingDone

Lookup

lkp_[source_name] or
lkp_[RelevantDescriptor] or
lkpo_[RelevantDescriptor]

If one table: lkp_LookupTableName; If multiple tables are joined to

bring back a result: lkp_
RelevantDescriptionOfTheProcessionBeingDone. If SQL override
is used lkpo_...

Sequence
Generator

seq_[RelevantDescriptor]

Typically the description is based upon the target table and the
primary key column that the sequence will be populating.

Stored Procedure

sp_StoredProcedureName

This is used when executing stored procedures from the

database.

External Procedure

ext_ProcedureName

Used for external procedures

Advanced External
Procedure

aep_ProcedureName

Used for advanced external procedures

Joiner

jnr_SourceTable/FileName1_S
ourceTable/FileName2

Used to join disparate source types: Oracle to Flat File for

example.

Normalizer

Nrm_[RelevantDescriptor]

Used to create multiple records from the one record being

processed. For example: nrm_Create_Error_Messages

Rank

rnk_[RelevantDescriptor]

rnk_ RelevantDescriptionOfTheProcessionBeingDone

Mapplet

Mplt_[RelevantDescriptor]

mplt_ RelevantDescriptionOfTheProcessionBeingDone

Sorter
Transformation

srt_[RelevantDescriptor]

srt_ RelevantDescriptionOfTheProcessionBeingDone

Transaction Control

tc_[RelevantDescriptor]

tc_RelevantDescriptionOfControl

Union

un_[RelevantDescriptor]

un_RelevantDescriptionOfUnion

XML Parser

Xmp_[RelevantDescriptor]

xmp_RelevantDescriptionOfXMLParser

XML Generator

Xmg_[RelevantDescriptor]

xmg_RelevantDescriptionOfGenerator

Custom
Transformation

ct_[RelevantDescriptor]

ct_RelevantDescriptionOfCustomTransformation

IDoc Interpreter

int_[RelevantDescriptor]

int_idoc_RelevantDescriptionOfCustomTransformation

Type of Transform
XML Source
Qualifier
Application Source
Qualifier

Naming Convention
XMLsq_[ RelevantDescriptor]

Description/Example

Appsq_<meaningful name>

* Wherever possible, transformations should include the $PMRootDir/<release>/Temp and

$PMRootDir/<release>/Cache directories. Such transformations include but are not limited to:
Transformation
Name

Directory

Sorter

$PMRootDir/<release>/Temp

Joiner

$PMRootDir/<release>/Cache

Aggregator

$PMRootDir/<release>/Cache

Lookup

$PMRootDir/<release>/Cache

Rank

$PMRootDir/<release>/Cache

Informatica Code Object Naming Standards:

Code Object

Naming Convention

Description/Example

Mapping

m_<meaningful name>

The mapping is the main unit of code for Informatica. It will

be important to include load type (incremental or full
refresh). The target is required and the source is typically
used when trying to differentiate among multiple mappings
that affect the same target. Version numbers will not be
used for this implementation.

Session

s_<mapping name>

s_m_MappingName without the version number attached.

The session is the wrapper for the mapping containing all
connection information necessary to extract and load data.

Workflow

Wf_< meaningful name >

The workflow is a job stream that strings all necessary

tasks together to create a data flow from source to target
systems.

Worklets

Wklt_description.

Worklets are objects that represent a set of workflow tasks

that allow you to reuse a set of workflow logic in several
workflows.

Reusable Session

rs_description

This is a session that may be shared among several

workflow and may execute while another instance of the
same session is running.

Cntrl Task

Cntrl_description

You can use the Control takes to stop, abort, or fail the toplevel workflow or the parent workflow based on an input
link condition.

Event Task

Evnt_description

Event-Raise task represents a user-defined event. When

the Informatica Server executes the Event-Raise task, the
Event-Raise task triggers the event. Use the Event-Raise
task with the Event-Wait task to define events.
The Event-Wait task waits for an event to occur. Once the
event triggers, the Informatica Server continues executing
the rest of the workflow.

Code Object

Naming Convention

Description/Example

Decision Task

Dcsn_description

The Decision task allows you to enter a condition that

determines the execution of the workflow, similar to a link
condition.

Command Task

Cmd_description

The Command task allows you to specify one or more shell

commands to run during the workflow. For example, you
can specify shell commands in the Command task to
delete reject files, copy a file, or archive target files.

Email Task

eml_description

The Workflow Manager provides an Email task that allows

you to send email during a workflow. You can create
reusable Email tasks in the Task Developer for any type of
email. Or, you can create non-reusable Email tasks in the
Workflow and Worklet Designer.

Assignment Task

asmt_description

The Assignment task allows you to assign a value to a

user-defined workflow variable.

Timer Task

tm_description

The Timer task allows you to specify the period of time to

wait before the Informatica Server executes the next task
in the workflow. You can choose to start the next task in the
workflow at an exact time and date. You can also choose
to wait a period of time after the start time of another task,
workflow, or worklet before starting the next task.

Port Variable Naming Standards:

Port Type

Naming Convention

Description/Example

Variable

v_ReleventName

Used in expression transformations

Output

o_RelevantName or
out_RelevantName (only set
this for new output ports
created in an expression
transformation)

Used in expression transformations to define the outgoing

port for use in subsequent transformations.

Input

i_Relevant_Name or
in_RelevantName (only set
this for input ports into a
lookup)

Used in lookup and expression transformations to denote

ports that are used within the transformation and do not
carry forward.

Lookup

lk_RelevantName or
lkp_RelevantName (only set
this in transformations for ports
that originated in a lookup
transformation)

Used in expression transformations for unconnected

lookups.

Return

r_RelevantName

Return values are found in lookup transformations and are

typically the column from the source object being
referenced in the lookup code.

User-Defined Session Parameters Naming Standards:

Parameter Type
Database Connection
Source File
Target File
Lookup File
Reject File

Naming Convention
$DBConnectionName
$InputFileName
$OutputFileName
$LookupFileName
$BadFileName