Table of Contents


  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. B2B transformation
  7. Aggregator transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence Generator transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation



Disabling incoming fields

Disabling incoming fields

You can disable incoming fields to connect only the generated sequence in the output fields, NEXTVAL and CURRVAL, to one or more downstream transformations. When you disable incoming fields, you cannot connect the Sequence Generator transformation to upstream transformations.
When you disable incoming fields, at least one field from another transformation must be connected to the downstream transformation along with the Sequence Generator fields. For example, if the mapping contains a Sequence Generator transformation and a Source transformation and the Sequence Generator transformation is connected to a Target transformation, you must connect at least one field from the Source transformation to the Target transformation.
The following image shows a mapping where incoming fields are disabled in the Sequence Generator transformation:
The mapping canvas shows the Source transformation and the Sequence Generator transformation connected to the Target transformation.
You cannot disable incoming fields in advanced mode.


We’d like to hear from you!
MAX IICS - June 19, 2022

By default Sequence Generator is passive in nature...but If I Disable Incoming Field In sequence Generator then what is nature of Sequence generator either Active or Passive? How it will behave?

Informatica Documentation Team - June 20, 2022


We are working to resolve your query. We will get back to you shortly.

Informatica Documentation Team - June 27, 2022

Hi MAX IICS, The Sequence Generator (SG) transformation is always passive. The Disable Incoming Fields option was added to make the transformation behave the same way in elastic and non-elastic mappings. In a non-elastic mapping, you can add a SG that either does or does not contain incoming fields, but in an elastic mapping, you can only add a SG that contains incoming fields. This option was added to make it clear whether or not the SG contains incoming fields.