Developer Mapping Guide > Import From PowerCenter > Transformation Conversion

Transformation Conversion

The import process converts PowerCenter transformations based on compatibility. Some transformations are not compatible with the Model repository. Others import with restrictions.

The following table describes the PowerCenter transformations that import with restrictions or that fail to import:

PowerCenter Transformation	Import Action
Aggregator	Imports with restrictions.
Data Masking	Fails to import.
External Procedure	Fails to import.
HTTP	Fails to import.
Identity Resolution	Fails to import.
Java	Imports with restrictions.
Joiner	Imports with restrictions.
Lookup	Imports with restrictions.
Normalizer	Imports with restrictions.
Rank	Imports with restrictions.
Sequence Generator	Imports with restrictions.
Sorter	Imports with restrictions.
Source Qualifier	Imports with restrictions. A source and Source Qualifier transformation import completely as one data object.
Stored Procedure	Fails to import.
Transaction Control	Fails to import.
SQL	Imports with restrictions.
Union	Imports with restrictions.
Unstructured Data	Fails to import.
XML Parser	Fails to import.
XML Generator	Fails to import.

Transformation Property Restrictions

Some PowerCenter transformations import with restrictions based on transformation properties.

The import process might take one of the following actions based on compatibility of certain transformation properties:

•Ignore. Ignores the transformation property and imports the object.
•Convert internally. Imports the object with the transformation property but the Developer tool does not display the property.
•Fail import. Fails the object import and the mapping is not valid.

Aggregator Transformation

The following table describes the import action for Aggregator transformation properties:

Transformation Property	Import Action
Transformation Scope	Ignore.

Java Transformation

In a Java transformation, the ports must be input ports or output ports. The import fails if the Java transformation has both input ports and output ports.

The following table describes the import action for Java transformation properties:

Transformation Property	Import Action
Class Name	Ignore.
Function Identifier	Ignore.
Generate Transaction	Ignore.
Inputs Must Block	Ignore.
Is Partitionable	Ignore.
Language	Ignore.
Module Identifier	Ignore.
Output Is Deterministic	Ignore.
Output Is Repeatable	Ignore.
Requires Single Thread Per Partition	Ignore.
Runtime Location	Ignore.
Update Strategy Transformation	Ignore.

Joiner Transformation

The following table describes the import action for Joiner transformation properties:

Transformation Property	Import Action
Null Ordering in Master	Convert internally.
Null Ordering in Detail	Convert internally.
Transformation Scope	Convert internally.

Lookup Transformation

The following table describes the import action for Lookup transformation properties:

Transformation Property	Import Action
Cache File Name Prefix	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Lookup Cache Initialize	Ignore.
Lookup Cache Directory Name	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Lookup Caching Enabled	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Lookup Data Cache Size	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Lookup Index Cache Size	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Lookup Source is Static	Ignore.
Lookup Sql Override	Ignore if converted as a stand-alone transformation, and imports to Custom SQL Query when converted within a mapping.
Lookup Source Filter	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Pre-build Lookup Cache	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Re-cache from Lookup Source	Ignore if converted as a stand-alone transformation, and imports when converted within a mapping.
Recache if Stale	Ignore.
Subsecond Precision	Ignore.
Synchronize Dynamic Cache	Ignore.

Normalizer Transformation

When you import a Normalizer transformation into the Developer tool, the Normalizer transformation imports with one input group and at least one output group.

If you import a Normalizer transformation that is not part of a mapping, the Developer tool places all the input ports in the input group of the Normalizer transformation. The Developer tool creates a default output group based on the Normalizer transformation rules for the output ports. If there are no output ports in the Normalizer transformation to import, the Developer tool creates a default output group in the imported Normalizer transformation.

When the Normalizer transformation is part of a mapping, the Developer tool might create multiple output groups based on links to the downstream transformation or targets in the mapping. For more information about the rules and guidelines about links from the multi-group transformation to the target, see the Developer Transformation Guide.

When you import a mapping that contains a reusable Normalizer transformation, the Developer tool imports the transformation as reusable. The Developer tool also replaces the reusable Normalizer transformation instances in the mapping with non-reusable transformation instances. The Developer tool generates new links from the non-reusable Normalizer transformation to the downstream transformations and target.

In PowerCenter, the Normalizer transformation has at least one generated key port. In the Developer tool, the Normalizer transformation does not contain a generated key port. When you import a Normalizer transformation from PowerCenter, the Developer tool ignores the generated key port.

The following table describes the import action for Normalizer transformation properties:

Transformation Property	Import Action
Reset	Ignore.
Restart	Ignore.

Rank Transformation

The following table describes the import action for Rank transformation properties:

Transformation Property	Import Action
Transformation Scope	Ignore.

Sequence Generator Transformation

In PowerCenter, the Sequence Generator transformation has two ports, CURRVAL and NEXTVAL. In the Developer tool, the Sequence Generator transformation has only one port, NEXTVAL. When you import a Sequence Generator transformation in a mapping, the Developer tool creates an Expression transformation to set the values for the CURRVAL port and pass them to the downstream transformation.

For example, you have a mapping in PowerCenter with a Sequence Generator, an Aggregator, and an Expression transformation. The source data passes to the Expression transformation followed by the Aggregator transformation and to the target. The Sequence Generator transformation adds a sequence number to each row with the CURRVAL port.

The following image shows the PowerCenter mapping with a Sequence Generator transformation, Aggregator transformation, and an Expression transformation:

The mapping contains a flat file source, source qualifier, Expression transformation, Aggregator transformation, and a target data object. The data flows from the flat file source to the source qualifier. From the source qualifier, the data passes to the Expression transformation. From the Expression transformation, the data passes to the Aggregator transformation and then to the target. There is a Sequence Generator transformation that has two ports, NEXTVAL and CURRVAL. The data from both these ports passes to the Aggregator transformation and to the target.

The following image shows the mapping imported into the Developer tool:

The mapping contains a source qualifier, two Expression transformations, a Sequence Generator transformation, an Aggregator transformation, and a target data object. The data flows from the Source Qualifier transformation through the Expression transformation to the Sequence Generator transformation. The Sequence Generator transformation has several ports. The data from the NEXTVAL port in the Sequence Generator transformation passes to an Expression transformation to set the CURRVAL. The data from both the NEXTVAL and the CURRVAL ports passes to the Aggregator transformation. The remaining ports in the Sequence Generator transformation passes directly to the Aggregator transformation. The Aggregator transformation passes all the ports to the target.

When you import the mapping, the Developer tool passes the NEXTVAL data from the Sequence Generator transformation to an Expression transformation to set the CURRVAL value.

The Developer tool imports a reusable Sequence Generator transformation in the mapping as a non-reusable transformation with a reusable sequence data object. When you import a reusable Sequence Generator transformation that is not part of the mapping, the Developer tool creates a reusable sequence data object.

The following table describes the import action for Sequence Generator transformation properties:

Transformation Property	Import Action
Current Value	Ignore.
Number of Cached Values	Ignore.

Sorter Transformation

The following table describes the import action for Sorter transformation properties:

Transformation Property	Import Action
Transformation Scope	Ignore.

Source Qualifier Transformation

The following table describes the import action for Source Qualifier transformation properties:

Transformation Property	Import Action
Number of Sorted Ports	Ignore.

SQL Transformation

The following table describes the import action for SQL transformation properties:

Transformation Property	Import Action
Auto Commit	Ignore.
Class Name	Ignore.
Connection Type	Fail import if set to dynamic connection object or full dynamic connect information.
Database Type	Fail import for Sybase, Informix, or Teradata.
Function Identifier	Ignore.
Generate Transaction	Ignore.
Inputs must Block	Ignore.
Is Partitionable	Ignore.
Language	Ignore.
Maximum Connection Pool	Ignore.
Module Identifier	Ignore.
Output is Deterministic	Ignore.
Output is Repeatable	Ignore.
Requires single Thread Per Partition	Ignore.
Runtime Location	Ignore.
SQL Mode	Fail import for script mode.
Transformation Scope	Ignore.
Treat DB Connection Failure as Fatal	Convert internally.
Update Strategy Transformation	Ignore.
Use Connection Pool	Ignore.

Union Transformation

The following table describes the import action for Union transformation properties:

Transformation Property	Import Action
Class Name	Ignore.
Function Identifier	Ignore.
Generate Transaction	Ignore.
Inputs Must Block	Ignore.
Is Partitionable	Ignore.
Language	Ignore.
Module Identifier	Ignore.
Output Is Deterministic	Ignore.
Output Is Repeatable	Ignore.
Requires Single Thread Per Partition	Ignore.
Runtime Location	Ignore.
Transformation Scope	Ignore.
Update Strategy Transformation	Ignore.