Transformations in Informatica


Informatica Transformations are repository objects that can read, alter, and pass data to defined target structures such as tables, files, or any other required targets. A transformation is essentially a set of rules that specify the data flow and how the data is put into the targets. Informatica PowerCenter includes a number of transformations, each of which serves a specific purpose. Let’s discuss what Informatica transformations are in this blog. For a better understanding of Informatica, join Informatica Training in Chennai with certification and placement support. It may be helpful for your career enhancement.

Various Informatica Transformations

Informatica Transformations are primarily divided into two groups. The first is based on the transformations’ connectedness (linking in mapping), while the second is based on the change in the total number of rows between the source and target. Let’s start with the Informatica transformations that are based on connectivity.

Types of transformations in Informatica based on connectivity

  • Connected Transformations.
  • Unconnected Transformations.

Connected transformations in Informatica are transformations that are linked to one or more other transformations.

When a transformation is run for each input row and it is anticipated to return a value, connected transformations are employed.

Unconnected transformations are transformations that are not connected to any other transformations. Their functionality is accessed by invoking them from within other transformations, such as the Expression transformation. The mapping pipeline does not include these changes.

When the functionality of unconnected transformations is only required under particular conditions, they are utilized. Learn more about Informatica by joining an Informatica Course in Chennai with certifications.

Types of Informatica transformations based on the change in the number of rows

  • Active Transformations
  • Passive Transformations

Active Transformations in Informatica

  • Change the number of rows that the transformation passes through: The filter transformation, for example, is active since it removes rows that do not satisfy the filter requirement.
  • Change the transaction boundary: A transaction boundary is a line that separates all transactions that occur before or after a commit call. For example, during a transactional activity, the user feels that a commit is required after specific transactions and uses the commit command to create a savepoint, changing the default transaction boundary. By default, the transaction boundary runs from the beginning of the file to the end of the file, or EOF.
  • Change the row type attribute: A record type that represents a table row is the row type attribute. The record can either save a whole row of data from a database or retrieve data from a pointer or pointer variable.

Passive Transformation in Informatica

  • A passive transition is one that meets all of these criteria.
  • There are no new rows formed or current rows eliminated in the passive transformation.
  • If passive transformations do not modify the number of rows, you may be asking why they are employed. They’re commonly used to update variables, execute an external method from a shared library, and specify maplets’ input and output. A maplet is a collection of simple mapping transformations.
  • There is no rule that a transformation utilized as a passive transformation cannot be used as an active transformation later. Similarly, depending on the situation, an unconnected transformation can be employed as a connected transformation. The brilliance of Informatica transformations is that they can create any feasible combination between these categories.

Difference Between Connected and Unconnected Lookup 

  • An unconnected lookup takes values from another transformation’s lookup expression, but a connected lookup receives values directly from the mapping pipeline. A pipeline in Informatica is made up of sources, transformations, and targets that are all connected together.
  • Because they have several return ports, connected lookups return numerous columns from the same row, whereas unconnected lookups only have one return port and return one column from each row. For example, if we use a connected lookup on an employee database with a specific department id as a parameter, we can get all of the information about the employees in that department, such as their names, employee ID numbers, addresses, and so on, whereas, with an unconnected lookup, we can only get one attribute of the employee, such as their name or employee ID number, or any other attribute specified by the user.
  • An unconnected lookup caches only the lookup output and conditions, whereas a connected lookup caches all lookup columns.
  • User-defined default values are supported by connected lookup, but not supported by unconnected lookup. You can alter the default value of those columns to NULL in the lookup expressions, for example, if you want to modify all values of a given column to NULL after lookup. In the event of an unconnected search, however, this feature is not available.

Attention Reader! Join Informatica Training in Bangalore with certification and placement support for your career enhancement.


I hope that this blog helps you to get some valuable information about Informatica. If you want training in Informatica to enhance your career, then join FITA Academy because it provides you with certifications and placement support for your career enhancement. It also provides you with training from real-time working experts.

If you are interested in Designing then read this blog, Importance Of UI UX Design, it may be helpful to enhance your career as a UI UX designer.

Leave a Reply

Your email address will not be published.

    Quick Enquiry