Description:

This problem only occurs in any interfaces that imports data into additional information fields. It is important to know what the data looks like in the source database before creating additional data info fields. Look at the actual values. If a "Bit" field is in the source, you might see "FALSE" in the source data instead of a one (1) or a zero (0). If you create the additional info field as "NUMBER" and try to import "FALSE" into the field, you will get the following Symptom.  

Symptoms:

QCEXCEED_YN was created as "NUMBER", the following messages appeared in the log file (must set verbosity to nine - 9):

16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo():  Error Handler dump BEGIN --------------------------
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo():  WHEN_KEY = QCEXCEED_YN, WHEN_VALUE = False
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo():  WHEN_FACILID = OPSVSS, WHEN_VARID = 1629, WHEN_DATESTAMP = 1/29/2011
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo(): Connection Error (0) # -2147217887 - 'Multiple-step operation generated errors. Check each status value. ' occured
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo(): HASH_DUMP :  [LAB_CERT] 241325920
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo(): HASH_DUMP :  [LOD] 2
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo(): HASH_DUMP :  [QCEXCEED_YN] False
16:28:45 : CommonFacilityWriter.WriteToHachWIMSainfo():  Error Handler dump END   --------------------------
16:28:45 : CommonFacilityWriter.WriteToHachWIMS() : WriteToHachWIMSainfo returned failure during write of Additional Info Fields

After reviewing the log file shown above, we see the value for QCEXCEED_YN is "False", not a "NUMBER".

Resolution:

The additional info field MUST be NVARCHAR in this case. Add a new field to the additional data info table that is an NVARCHAR type, and map that to the interface additional info field.