Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Rules and Guidelines for Lookup Transformation Conditions

Rules and Guidelines for Lookup Transformation Conditions

Certain rules and guidelines apply when you enter a condition for a Lookup transformation.
Consider the following rules and guidelines when you enter a condition for a Lookup transformation.
  • The datatypes for the columns in a lookup condition must match.
  • Use one input port for each lookup port in the lookup condition. You can use the same input port in more than one condition in a transformation.
  • If you use a port selector or a dynamic port in a lookup condition, the lookup condition considers all the ports in the expression.
  • You can use a dynamic input port or a port selector as the input port of a lookup condition. The number of generated ports in the input port must be equal to the number of ports in the lookup column.
  • When processing a Lookup transformation with multiple lookup conditions, the Integration Service returns rows that match all the lookup conditions.
  • You can create an expression parameter to parameterize the lookup condition in a nonreusable lookup transformation.
  • To increase lookup performance, enter conditions in the following order:
    • Equal to (=)
    • Less than (<), greater than (>), less than or equal to (<=), greater than or equal to (>=)
    • Not equal to (!=)
  • Use one of the following operators when you create a lookup condition: =, >, <, >=, <=, or !=.
  • The Integration Service processes lookup matches differently based on whether you configure the Lookup transformation with a dynamic lookup cache, static lookup cache, or uncached lookup.
  • The Integration Service matches null values. For example, the Integration Service considers a lookup port and an input port equal if they both have null values.
  • If the columns in a lookup condition are Decimal data types, the precision of each column must belong to the same precision range. Valid precision ranges include:
    • Decimal 0-18
    • Decimal 19-28
    • Decimal 29-38
    • Decimal 39 and over
    For example, if you define the condition
    DecimalA = DecimalB
    where DecimalA has precision 15 and DecimalB has precision 25, the lookup condition is not valid.

0 COMMENTS

We’d like to hear from you!