Developer Mapping Guide

10.2.1
- 10.5.4
- 10.5
- 10.4.1
- 10.4.0
- 10.2.2

Back Next

Export Restrictions

When you export a Model repository object to PowerCenter, some Model repository objects might not get exported to the PowerCenter repository. You cannot export a mapping or mapplet that contains any object that is not valid in PowerCenter.

You cannot export the following objects to PowerCenter:

Objects with long names: PowerCenter users cannot import a mapping, mapplet, or object within a mapping or mapplet if the object name exceeds 80 characters.
Mappings or mapplets that contain a dynamic port: You cannot export a mapping or mapplet that contains dynamic ports.
Mappings or mapplets that contain a Decision transformation that uses a system parameter: You cannot export a mapping or mapplet that contain a Decision transformation if the transformation script includes a system parameter. The export operation cannot convert the system parameter to a value that PowerCenter can use. Before you export a mapping or mapplet with a Decision transformation that uses a system parameter, replace the parameter with an appropriate value.
Mappings or mapplets that return mapping outputs: PowerCenter users cannot import a mapping or mapplet if the mapping or mapplet returns mapping output.
Mappings or mapplets that contain a Joiner transformation with certain join conditions: You cannot export mappings and mapplets that contain a Joiner transformation with a join condition that is not valid in PowerCenter. In PowerCenter, a user defines join conditions based on equality between the master and the detail sources. In the Developer tool, you can define other join conditions. For example, you can define a join condition based on the equality or the inequality between the master and the detail sources. You can define a join condition that contains transformation expressions. You can also define a join condition, such as 1 = 1, that causes the Joiner transformation to perform a cross-join.
These types of join conditions are not valid in PowerCenter. Therefore, you cannot export mappings or mapplets that contain Joiner transformations with these types of join conditions to PowerCenter.
Mappings or mapplets that contain a Lookup transformation with renamed ports: The PowerCenter Integration Service queries the lookup source based on the lookup ports in the transformation and a lookup condition. Therefore, the port names in the Lookup transformation must match the column names in the lookup source.
Mappings or mapplets that contain a Lookup transformation with certain custom SQL queries: The Developer tool uses different rules than PowerCenter to validate SQL query syntax in a Lookup transformation. A custom SQL query written in the Developer tool that uses the AS keyword or calculated fields is not valid in PowerCenter. You cannot export mappings or mapplets to PowerCenter that contain a Lookup transformation with an SQL query that uses the AS keyword or calculated fields.
Mappings or mapplets that contain sources that are not available in PowerCenter: If you export a mapping or mapplet that includes sources that are not available in PowerCenter, the mapping or mapplet fails to export.
You cannot export a mapping or mapplet with the following sources:
Complex file data object
DataSift
Web Content - Kapow Katalyst
Mappings or mapplets that contain data warehouse sources or targets: You cannot export a mapping or mapplet to PowerCenter that contains Greenplum, Netezza, or Teradata PT objects.
Mapplets that concatenate ports: The export process fails if you export a mapplet that contains a multigroup Input transformation and the ports in different input groups connect to the same downstream transformation.
Nested mapplets with unconnected Lookup transformations: The export process fails if you export any type of mapping or mapplet that contains another mapplet with an unconnected Lookup transformation.
Mappings with an SAP source: When you export a mapping with an SAP source, the Developer tool exports the mapping without the SAP source. When you import the mapping into the PowerCenter repository, the PowerCenter Client imports the mapping without the source. The output window displays a message indicating the mapping is not valid. You must manually create the SAP source in PowerCenter and add it to the mapping.
Mappings with Timestamp with Time Zone or Timestamp with Local Time Zone: When you import a mapping that contains data of the Timestamp with Time Zone or Timestamp with Local Time Zone data type from the Developer tool, the PowerCenter client fails to convert the mapping.

Rename Saved Search

Table of Contents

Developer Mapping Guide

Developer Mapping Guide

Export Restrictions

Export Restrictions