Workaround for corrupt XML problem in update outbound advice process at V&S
This document describes the workaround provided to skip the outbound records that give fatal error while upload to Baan
Problem Definition
Some XML records from Fidware for upload of outbound advices to Baan give fatal error in bus component and restart the xmlhandler on BaanERP (like fatal error(s) in component PRD_520_FW_OBC, xmlhandler will be restarted (HRESULT = 0x80020009)). The root cause of the problem is not known yet.
Workaround
A workaround is provided to report error for such records and skip the recovery process for them. In case of this error, the GUID for the input record will be removed from the GUID table at client side so that it will not be picked up for recovery. This will avoid looping of process due to fatal error and recovery.
Components changed
“VNSWMSTransferObjectsFWToBaanOutboundAdviceChangerowResultUpdateOutboundAdvice”
How to install the component
The changed component is delivered in ofa VNSWMS_UpdateOutboundAdvice20031008.ofa. Import this ofa on Broker port 7250 and 7251. Import will replace existing component with new one. The upload outbound advice process will access the new component from next run. Restart the Broker service just to make sure that all references to old component are cleared.