Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Address Validator Transformation
  4. Aggregator Transformation
  5. Association Transformation
  6. Bad Record Exception Transformation
  7. Case Converter Transformation
  8. Classifier Transformation
  9. Cleanse transformation
  10. Comparison Transformation
  11. Custom Transformation
  12. Custom Transformation Functions
  13. Consolidation Transformation
  14. Data Masking Transformation
  15. Data Masking Examples
  16. Decision Transformation
  17. Duplicate Record Exception Transformation
  18. Dynamic Lookup Cache
  19. Expression Transformation
  20. External Procedure Transformation
  21. Filter Transformation
  22. HTTP Transformation
  23. Identity Resolution Transformation
  24. Java Transformation
  25. Java Transformation API Reference
  26. Java Expressions
  27. Java Transformation Example
  28. Joiner Transformation
  29. Key Generator Transformation
  30. Labeler Transformation
  31. Lookup Transformation
  32. Lookup Caches
  33. Match Transformation
  34. Match Transformations in Field Analysis
  35. Match Transformations in Identity Analysis
  36. Merge Transformation
  37. Normalizer Transformation
  38. Parser Transformation
  39. Rank Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. Source Qualifier Transformation
  44. SQL Transformation
  45. Using the SQL Transformation in a Mapping
  46. Stored Procedure Transformation
  47. Standardizer Transformation
  48. Transaction Control Transformation
  49. Union Transformation
  50. Unstructured Data Transformation
  51. Update Strategy Transformation
  52. Weighted Average Transformation
  53. XML Transformations

Transformation Guide

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!