I am trying to bring drawing BOMs into Job Entry. I keep getting an error message, and Epicor will not allow me to bring in the drawings.
IceBLException: Attempted to divide by zero. at Erp.internal.mr.cpmethod.
These are just drawings and subassemblies. I cannot figure out what this error message means, or how I can fix it. Does anyone know.
Post the full error message along with the full steps you made to get there.
image is below. I tried to bring in drawing BOM 465529 and the subassemblies. I get an error message. I do not know how to correct it and our epicor “consultant” has no clue.
Is this on every job or only some of them?
Just this one. There are already drawings in the job, so it’s puzzling. I did not get the error message when I entered those. It is only this group of drawings. I have never seen this error message before.
My first thought was that this could be a BPM, but i don’t see anything in the error that points to a BPM. so… if this is not a BPM, then it is a bug that definitely needs to be reported and fixed through a call to Support.
thank you. It is very frustrating.
There’s probably an issue in this specific MOM/BOM. Some qty per field set to zero or whatnot. Div0 errors are not common and usually boil down to a user plugging in a zero where they shouldn’t and the system not catching it.
I’ve seen this usually when Either a Qty/Parent field is incorrect as 0.00 or a Prod Std is incorrect as 0.00.
Thank you for your input. This has been in the hands of Epicor for three days now and they have no idea. Which is frightening.
Exit the system monitor to reduce noise, and then post a full trace.
We may be able to see what’s going on.
Start the trace and clear it right after you open the form.
When the error message is off, grab it and post it.
I found 2 customer support cases with a similar error and this is what they found:
For one customer:
They had been changing the op codes on several operations which did not have an op-standard linked and caused the production standard field to be set to 0. Once I set a value here I no longer got the error message.
For the other:
Notice that this error is caused by a subassembly, Rev , Operation 10 is having 0 cycle/hours Try to edit the Operation to 1 cycle /hours and see if this resolves the issue.
Hope these are the same solutions for your issue also.
it worked. I found that three of my subassemblies had 0 hours for fabrication. I put in the hours and was able to bring the entire drawing package into the job.
thank you so much.
That’s why we love this forum, users helping users.
Meanwhile Jane is still waiting for Epicor Support 
No comment 
Lol Aeron just gave you answer here. Maybe it is just faster than in Service now 
You would THINK that Epicor would know what their own error messages mean. But alas they do not. Clueless.
It is system message. Program just does not expect to have it here. Correct way would be to check if this value is 0 before deletion. Not sure how easy it is to implement here.
