RMG,
From an ETL perspective, we have a process for that. I’m thinking maybe that should also be part of the ETL tool is to perform the validation step as well. Before sending the data to the target system, the data has to be validated first. Validation can pertain to field or file validation. Something like as follows:
Field Validation:
- System must remove all punctuation (dashes, commas, periods, etc.)
- System must remove all unnecessary spaces.
- If field is < 9 digits, auto-filled with leading zeros.
- System must validate that either field1, field2, etc. are populated.
File Validation:
- If more than 20% of the records receive critial errors, the entire file will fail.
As you can see, the list could be lengthy or not based on the partner requirements. I’m usre you could do this in IS/TN but is there a better method or better tool design specifically for data validation. I’m assuming not considering this was brought up.
#webMethods-General#Integration-Server-and-ESB#webMethods#webMethods-Architecture