Table of Contents

Search

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

Developer Mapping Guide

Developer Mapping Guide

System Parameter Conversion

System Parameter Conversion

You can import a PowerCenter mapping or mapplet that contains some system-defined parameters. The import process imports the parameters if they match the system-defined parameters that are valid in the Model repository.
The import process creates the parameter bindings between the system-defined parameters and the reusable transformations that reference the parameters.
If a PowerCenter mapping has a system-defined parameter that does not have an equivalent system-defined parameter in the Model repository, the conversion does not fail. The import process copies the mapping property with the parameter name as the property value. However, the imported mapping is not valid. You can create a user-defined parameter to replace the property value or you can change the mapping logic.
You can import the following system-defined parameters:
  • $PMMappingName
  • $PMIntegrationServiceName
  • $PMRepositoryUserName
  • $SESSSTARTTIME
  • $SYSDATE
You cannot import the following PowerCenter system-defined parameters:
  • $PMFolderName
  • $PMRepositoryServiceName
  • $PMSessionName
  • $PMSessionRunMode
  • $PMTAB_ALL_DATA_TYPES@TableName
  • $PMTGT_ALL_DATA_TYPES@TableName
  • $PMWorkflowName
  • $PMWorkflowRunId
  • $PMWorkflowRunInstanceName

0 COMMENTS

We’d like to hear from you!