Error #40 Divide check or numeric overflow when posting 1

[seants]

Help!

I got error when posting invoices.

Error #40: Divide check or numeric overflow
Program: SOWUAE
Line: 12180

Any idea what's going on with my MAS200 3.71 system?

Thanks,

 

[BigLouie]

* The error message should provide a key (for example, 00075860000000004). This key is from the Sales Order History Line Detail File (SO_04), and represents the order number and line sequence number. If the error did not provide a key, click 'Debug' on the error window and perform the following:
1. Type "? SO_04$(1,17)" (without quotes) and press ENTER.
2. Note the returned key from SO_04.
3. Type "BYE" (without quotes) and press ENTER to close 'Debug' window.

Then

1. Open Library Master / Repair / Data File Display and Maintenance (DFDM).
2. Select SO_04xxx (xxx = company code).
3. In the 'Key' field, type the 17 digit number from the error message or 'Debug' step above and press ENTER.
4. Click the 'Edit' button. Enter the Field number as "10" (without quotes) and press ENTER. In the 'Change' field, the number must be one or greater. This field is the sales unit of measure conversion factor which must be greater than zero. Enter "1" (without quotes) in the 'Change Data' field.
5. Perform the following steps only if the record is an inventory item. Skip the following steps if the key was a "/C" comment line.
6. Still in DFDM, select IM1xxx at the 'File Name' field (xxx = company code). Press ENTER.
7. Click 'Keyscan', and select the item number that was corrected above.
8. Click 'Edit'. In the 'Field number', type "5" (without quotes). Press ENTER.
9. In the 'Change' field, the number must be 1 or greater. This field is the sales unit of measure conversion factor which must be greater than zero. Enter a "1" (without quotes) in the 'Change Data' field, and click 'OK'.
10. Close DFDM, and start the update again.

 

[BigLouie]

Divide check or numeric overflow is almost always caused by a lack of a value in the unit of measure conversion factor field.

 

[seants]

BigLouie,

That did the tricks. I will double check UM section.
Thanks again and appreciate your help.

Happy holiday!

 

[sharkscott]

Just had someone in the office get this exact error. I am waiting for clearance from the boss to try it out and see if it works. If it worked for the last guy I think it will for me too.

I'll Let you know

sharkscott

 

[BigLouie]

As I said before, divide check or numeric overflow is almost always (like 99%) caused by a lack of value in the unit of measure field.

 

[sharkscott]

Come to find out that the problem was a lot more complex than I thought. I had to call our manufacturer rep and have him take remote control of the program through the administrator login.

Needless to say he did more in two minutes than I did in two hours, oh well. I look like the hero, go figure.

The info here that I used did fix the specific issue I was aware of but it was just the first of a few that we had to take care of.

 

[seants]

Update:

I found out most of our EDI imported SOs having the same issue when posting and it happened on the common line manually add next to the item line after import.
We are using True Commerce EDI solution and we are not experiencing any other issue.

 

[seants]

BigLouie:

Most of my issue happened on this point "/C" comment line, I need to change field 10 from 0 to 1 instead to pass invoice posting.

> 5. Perform the following steps only if the record is an
> inventory item. Skip the following steps if the key was a
> "/C" comment line.

 

[seants]

Update:

Found this from Sage support web site:

Correct LastLine Sequence number in Sales Order/Quote History Header file when importing through Visual Integrator

Date: 3/1/2006
Product Line: MAS 90 and MAS 200
Application: Visual Integrator
Application Level: 3.71
Number: VI3030-T
Symptom

After importing sales orders via Visual Integrator, the lines in Sales Order/Quote History (SO_04) are incorrect when deleting an item and adding another item in Sales Order Entry (SO2). If a Kit item is deleted and re-added to explode the components, only the new Parent and Component items are listed. All other lines, including the original Kit item are deleted from the order.

OR

LastLine Sequence number in Sales Order/Quote History Header file is not being set correctly when importing through Visual Integrator. When importing to Sales Order Entry, the Last Line Sequence number is set to zero. When entering the sales order manually, the line is set to the total number of lines. If additional lines are added to the sale order after the import, the original lines are overwritten in Sales Order/Quote History.

Resolution

The following program will correct the problem.

SOWVIP

To install the correction, run the Download file below.

VI3030_t.exe