Originally posted by: repanzer
I've always had problems with using the data audit setting in the organizer not being consistent, just like you mention, where it works good for some objects, but not for others.
In that regards, I can only say to keep changing the settings until you get the desired result.
I'm assuming you want the error handling to show the specific element that caused the error. In my shop, we do it manually using the trace file.
Also, I don't believe the restart should or would work if the object does not loop (though I'm not claiming that I know for sure). At least that sounds right, because if it didn't, how could it restart at that object?
Maybe rather then grabbing a field and putting that into the data audit settings, you grab the segment the field is a part of instead.
Also, you can use the IN function in the data audit settings, something I still had issues getting the desired result when using.
For example, you grab the BGM segment and it looks like;
BGM Segment:Message PAYMUL Outbound Partner Set VD96A:PAYMUL
you can alter it to look like;
Segment IN Message PAYMUL Outbound Partner Set VD96A:PAYMUL
Maybe try changing it like that to get the result you want.
Let us know how it goes.
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange