Thanks Isaac. I need to evaluate this as this condition only appears to affect older contracts/projects that are no longer active. If you do not mind I have a followup question on this procedure. As part of my routine it creates a series of budget records. I was setting
SET @I_PABUnitCost = 99999999999.99000 and
SET @I_PAFUnitCost = 99999999999.99000.
For some peculiar reason I had a very small set of records where the import would crash with this message:
"Arithmetic overflow error converting numeric to data type numeric"
Changing both to
SET @I_PABUnitCost = 99999999.99000 and
SET @I_PAFUnitCost = 99999999.99000.
eliminates this message. Both fields in the PA01301 table defined as numeric(19,5). Why would most records be fine but a few would not? It appeared to have something to do with the customer number.