Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Where to Assign Parameters
  6. Mapping Outputs
  7. Generate a Mapping from an SQL Query
  8. Dynamic Mappings
  9. How to Develop and Run a Dynamic Mapping
  10. Dynamic Mapping Use Cases
  11. Mapping Administration
  12. Export to PowerCenter
  13. Import From PowerCenter
  14. Performance Tuning
  15. Pushdown Optimization
  16. Partitioned Mappings
  17. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Rules and Guidelines for Importing Mappings with Parameters

Rules and Guidelines for Importing Mappings with Parameters

If you import a mapping with parameters, consider the following rules and guidelines:
PowerCenter does not require initial values for parameters.
When you import a PowerCenter parameter with no initial values, the import process assigns a default value for the parameter based on the parameter data type. The default value for a parameter with a String data type is a number sign (#). The default value for a parameter with a Numeric data type is 0. The default value for a parameter with a Date/Time data type is 01/01/70 in the format mm/dd/yy. The default value for an SQL parameter is Empty.
PowerCenter mappings with the
IsExprVar
property are not valid in the Model repository.
Some PowerCenter mapping parameters have the
IsExprVar
property enabled. This property indicates that the PowerCenter Integration Service must expand the parameter before parsing an expression. The
IsExprVar
property is not valid in the Model repository. If you import a mapping with this parameter property enabled, the conversion is successful, but the mapping is not valid.
Parameterized source owner in Netezza and Teradata objects or target table names in Teradata mappings fails to import.
When you import Netezza and Teradata objects that contains a parameterized source owner name property, the import process does not convert the property. The import process also ignores any parameterized target table names in Teradata mappings.

0 COMMENTS

We’d like to hear from you!