Originally posted by: swatiroi

Hi,

We could successfully store the NACHA message into DB using WTX NACHA pack.

Although it’s very powerful tool but the most painful part is checking and understanding the data audit trace file in case of errors/issues.

It shows errors in the form of a offset and the component number. We found it troublesome to check the exact cause of the failed transformation,
especially in case of very large input data file.

Are there any pointers to make the audit logs more readable so that at least we know what field are causing the issue/problem?

Also we found some differences in the std. NACHA format suggested and the one supported by the WTX NACHA pack like -
i) the file end record is mandatory for the data file without which it just flags the error message as
"one or more inputs are invalid".
ii) Also we found some fields are optional in the std. NACHA format but as per WTX NACHA pack, it
requires values of those fields - example is the Julian date field in the File Header record.

Has anyone used NACHA business pack? Is it possible to share/throw some light/inputs related to above issues?

Thanks in advance.

-Swati
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange