The Normalizer is an active transformation. It is used to convert a single row into multiple rows. When the Normalizer transformation receives a row that contains multiple-occurring data, it returns a row for each instance of the multiple-occurring data.
If in a single row, there is repeating data in multiple columns, then it can be split into multiple rows. Sometimes we have data in multiple occurring columns.
For example, a relational source includes four fields with flat sales data. We can configure a Normalizer transformation to generate a separate output row for each flat.
When the Normalizer returns multiple rows from an incoming row, it returns duplicate data for single-occurring incoming columns.
The Normalizer transformation receives a row that contains multiple-occurring columns and returns a row for each instance of the multiple-occurring data. The transformation processes multiple-occurring columns or multiple-occurring groups of columns in each source row.
Here are the following properties of Normalizer transformation in the Properties panel, such as:
We need the appropriate license to use the Normalizer transformation.
The Normalizer transformation parses multiple-occurring columns from COBOL sources, relational tables, or other sources. It can process multiple record types from a COBOL source that contains a REDEFINES clause.
Normalizer Transformation Types
Here are the two types of Normalizer transformation, such as:
We create the following table that represents the student marks records of different classes, such as:
Step 1: Create the source table "stud_source" and target table "stud_target" using the script and import them in Informatica.
Step 2: Create a mapping having source stud_source and target table stud_target.
Step 3: From the transformation menu create a new transformation
Step 4: The transformation will be created, then click on the Done button.
Step 5: Double click on the normalizer transformation, then
Columns will be generated in the transformation. We will see 4 number of marks column as we set the number of occurrences to 4.
Step 6: Then in the mapping
Save the mapping and execute it after creating session and workflow. The class score column is repeating in four columns. For each class score of the student, a separate row will be created by using the Normalizer transformation.
The output of the above mapping will look like the following:
The source data had repeating columns, namely class7, class 8, class 9, and class 10. We have rearranged the data to fit into a single column of class, and for one source record, four records are created in the target by using Normalizer.
In this way, we can normalize data and create multiple records for a single source of data.