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

Bad Record Exception Configuration View

Bad Record Exception Configuration View

The
Configuration
view specifies the upper and lower thresholds that the transformation uses to identify good records and bad records. The
Configuration
view also identifies the target tables for the records with scores that are above or below the thresholds.
The following figure shows the Exception transformation
Configuration
view:
The Configuration view has the Manual Review Thresholds fields at the top of the view. The Lower Threshold Value is 10. The Upper Threshold value is 90. The Data Routing Options are in the left column. The Good records are set for Standard Output. The Bad Records are set for the Bad Records table. The Reject records are not configured for any tables.
You can configure the following properties in the
Configuration
view:
Lower Threshold
The lower limit for the bad record score range. The transformation identifies records with scores that are below the lower threshold as rejected records.
Upper Threshold
The upper limit for the bad record score range. The transformation identifies records with scores that are greater than or equal to the upper threshold as good records.
Data Routing Options
The types of output records. In the default configuration, the transformation writes good records to the Standard Output and writes bad records to the Bad Records table. By default, the transformation does not write the rejected records to a database table.
Standard Output
The types of record that the transformation writes to the standard output ports. Default is Good Records.
Bad Record Table
The types of record that the transformation writes to the bad record output ports. Default is Bad Records.
Create separate output group for rejected records
Creates a separate output group for the rejected records. The option is clear by default.
Generate bad records table
Creates a database table to contain the bad record data. When you select the option, the Exception transformation creates the database table, adds a data object to the Model repository, and adds an instance of the object to the mapping canvas. You can generate the bad records table for an Exception transformation instance in a mapping. When you generate the bad records table, the Developer tool also creates an issues table to store descriptive metadata about the records.
The Developer tool adds a 12-character suffix to each column name in the bad record tables. If you use an Oracle database, the source column name can contain no more than 18 characters.

0 COMMENTS

We’d like to hear from you!