Part I: Version 9.6.1 > New Features (9.6.1) > Informatica Transformations
  

Informatica Transformations

This section describes new transformation features in version 9.6.1.

Address Validator Transformation

This section describes new features to the Address Validator transformation that you create in the Developer tool.

Modes

You can configure the Address Validator transformation to run in the following modes:
Address Code Lookup Mode
When you select address code lookup mode, the Data Integration Service reads an identification code and returns the corresponding address elements from the reference data. The identification code can refer to a locality, street, or mailbox. For example, you can enter the choumei aza code for a Japanese address and retrieve the complete address as output.
Interactive Mode
When you select interactive mode, address validation reads a partial address and returns all addresses from the reference data that match the input elements. Select interactive mode to add data to an incomplete address. You can enter the partial address on a single input port.
You also can enter a partial address on a single input port when you configure the transformation to run in suggestion list mode.

Ports

You can select the following ports for the Address Validator transformation:
Count
Output port that indicates the number of addresses in the address reference data sets that match the data in the input address.
Count Overflow
Output port that indicates whether the reference data contains addresses that address validation does not return to the transformation.
Gmina Code PL
Output port returns the identification code for the municipality or commune to which a Polish address belongs.
Institute of Geography and Statistics Code
Output port that contains a seven-digit identification code for the city or state to which a Brazilian address belongs.
Locality Identifier DE
Input and output ports that contain the identification code for a German locality.
National Address Database Identifier ZA
Input and output port that contains a seven-digit identification code for the street in a South African address.
National Institute of Statistics and Economic Studies Code
Input and output port that identifies the administrative regions to which a French address belongs. The National Institute of Statistics and Economic Studies code is also called the INSEE code.
New Choumei Aza Code JP
Output port that returns a unique delivery point code for a Japanese mailbox.
Official Municipality Key DE
Input and output ports that contain an identification code for a German municipality.
Postal Address Code AT
Output port that contains building-level post code data for an Austrian address.
Postal Address Code RS
Output port that returns a street-level post code for a Serbian address.
Postal Code Extension
Output port that contains a two-digit suffix for the post code of a Swiss address.
Street Identifier DE
Input and output ports that contain a street-level identification code for a German address.
Supplementary status ports
Output ports that indicate if address validation can return supplementary data for an address.
The transformation includes supplementary status ports for Austria, Brazil, France, Germany, Poland, South Africa, and Switzerland.
TERYT Locality Identifier PL
Output port that contains the identification code for the locality to which a Polish address belongs.
TERYT Street Identifier PL
Output port that contains the identification code for the street in a Polish address.
Unique Delivery Point Reference Number GB
Output port that returns a unique delivery point code for a United Kingdom mailbox.
For more information, see the Informatica 9.6.1 Address Validator Port Reference and the Informatica 9.6.1 Developer Transformation Guide.

Properties

You can configure the following advanced properties for the Address Validator transformation:
Alias Locality
The property determines whether address validation replaces a valid location alias with the official location name.
Matching Extended Archive
The property determines whether address validation returns a unique delivery point code for an out-of-date Japanese address.

Data Processor Transformation

This section describes new features to the Data Processor transformation that you create in the Developer tool.

File Input for Streamer

A Data Processor transformation Streamer can use a file as input. Previously, the streamer only used a buffer as input.
For more information, see the Informatica Data Transformation 9.6.1 User Guide.

Generate Data Transformation with AVRO or XML

You can auto-generate a Data Processor transformation with AVRO input and any format output, or Avro output and any format input, with the New Transformation wizard. Use an Avro schema file or sample file to define the AVRO file specification. You can also generate a transformation with both Avro input format and output format. In this case, use separate Avro schema files or sample files to define both the input and the output.
When you add a Data Processor transformation that reads Avro input to a mapping, you also add a complex file reader to pass the Avro input to the transformation. For a mapping with a Data Processor transformation that generates Avro output, you pass the output to a complex file writer.
You can also auto-generate a Data Processor transformation with XML input, output, or both, with the New Transformation wizard. Use an .xsd schema file or a sample file to define the expected XML hierarchy.
For more information, see the Informatica Data Transformation 9.6.1 User Guide.

Generate Schema from Sample File

When you add a sample file to define a hierarchy with the New Transformation wizard or the Schema wizard, the wizard creates an .xsd schema file to define the hierarchy. The wizard creates the schema in the Model repository. You can use the schema with other transformations.
For more information, see the Informatica Data Transformation 9.6.1 User Guide.

Relational Mapping Keys

Keys in a relational mapping can be of type xs:string and xs:integer.
For more information, see the Informatica Data Transformation 9.6.1 User Guide.

Unread XMap Elements

You can select to track XMap input elements that you do not map to output elements. The transformation reports unmapped elements to the Default Handler output port named XMap_Unread_Input_Values .
For more information, see the Informatica Data Transformation 9.6.1 User Guide.

Match Transformation

This section describes new features to the Match transformation that you create in the Developer tool.
You can specify whether the transformation updates a current identity index data store with index data from a mapping data source. Use the Persistence Method option to set the update policy. Set a policy to update the data store with any index data from the data source that the data store does not contain. Alternatively, set a policy that does not update the data store with index data. By default, the transformation updates the data store.
For more information, see the Informatica 9.6.1 Developer Transformation Guide.

SQL Transformation

This section describes new features of the SQL transformation that you create in the Developer tool.
You can use the SQL transformation to invoke stored procedures from a Sybase database.
For more information, see the Informatica 9.6.1 Developer Transformation Guide.