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

Parameter Hierarchy

Parameter Hierarchy

The parameter hierarchy defines the levels where you can create user-defined parameters.
The hierarchy occurs in the following order:
Workflow parameters Mapping parameters Mapplet parameters Logical data objects Transformation/data object parameters
A parameter assigned to an object at a higher level in the hierarchy can replace parameters assigned to lower levels in the hierarchy. You can use the hierarchy to override parameters in the following ways:
  • Override parameters assigned to low-level objects in the hierarchy by assigning parameters to high-level objects in the hierarchy.
  • Bind low-level object parameters to high-level object parameters to use the default values of the high-level object parameters in the run-time mapping or workflow.
For example, you can add a reusable transformation to a mapping. To replace parameters in the reusable transformation, you can create mapping parameters to override the transformation parameters. Or, you can expose the transformation parameters as mapping parameters to bind the transformation parameters to mapping parameters. The transformation uses the default mapping parameter values at run time.

0 COMMENTS

We’d like to hear from you!