Calculating BOM Missing Number

(1) Share

Report

Posted on by FAC.Ansel

1,632

Has anyone else seen this error message? And what did you do? I have tried searching the web and used the debugger and I'm at a standstill on what is missing. It seems like something is just off.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi Ansel, Could you possibly provide some additional Information on your BOM especially the item number 8340-001? Possibly post a screen-print of the BOM and let us know how your BOM and the items included are setup from a costing perspective (Standard costing, moving average, FIFO, LIFO). Maybe you simply forgot setting up a cost price. I think every additional Information helps. Thanks, Ludwig

Was this reply helpful? Yes No
Suggested answer

FAC.Ansel 1,632 on at

Like (1)

Report

I found the issue and hopefully this will help someone in the future when you get the very vague error message "Missing Number".

The reason I got this message is that there was a Phantom Subassembly on the BOM that had a route attached to it. In AX, you must put the route on the top level assembly and leave the Phantom Blank. After removing the Route, the cost rolled as it should.

Was this reply helpful? Yes No
Suggested answer

Svend Torp Larsen 2 on at

Like (0)

Report

I have seen it in D3FO / AX7. The reason was a Released product without neither setup time nor runtime in the Route.

It was in combination with a Phantom route in the structure, but the issue was noy the Phantom Route, but the top level route.

It was able to calculate a price in a Planned Cost version, but not in a Standard Cost costing version.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

We have seen this issue in our live system because of which the entire business was stuck as the BOM calculation was not happening.

After doing the root cause analysis of this incident, we identified that there were some set of items which were changed from being Item type "Item" to "Phantom" and there was no route specified on some of them.

After clearly defining the route on all such items, BOM calculation was successful.

Was this reply helpful? Yes No
jconerp1 on at

Like (0)

Report

A phantom should not require a route - if this is really the issue then Microsoft needs to fix this as that would be a bug.

Was this reply helpful? Yes No
Aparisi82 2,188 on at

Like (0)

Report

@fac.ansel Thank you very much for this.. You let me save days of troubleshooting

Was this reply helpful? Yes No