Answered

Phantom BOMs only plan when explicitly called

(0) Share

Report

Posted on by FAC.Ansel

1,632

When running planning, the demand is only planning down to the Phantom and then stops. So, I have to run a separate MRP run that explicitly calls out the items that are marked as phantom, then they continue to plan. This is providing very bizarre results. If I run planning for the item specifically (update master planning from net requirements), then the plan looks correct. But if I run planning for everything, then I don't get the demand from the phantoms.

My question then, is there a setting on the item/BOM/parameters that controls how the phantoms are planned? Does anyone else have this issue or have you seen an issue when using MRP with Phantoms? From my research, most complaints are that Phantoms create planned orders, but in my case, I'm not getting these planned orders and I want them.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

FAC.Ansel 1,632 on at

Like (0)

Report

To add to this....

It appears that it is not a Phantom issue, as I have found that 1 Phantom will plan as desired but another one only shows the demand and does not generate supply. If I run the planning run on this item, it creates the planned production orders but does not do this when run as a whole. BOM Levels?

Was this reply helpful? Yes No
Guy Terry 28,924 Moderator on at

Like (0)

Report

Are you expecting Master Planning to plan production orders for your phantom BOM lines?

Was this reply helpful? Yes No
FAC.Ansel 1,632 on at

Like (0)

Report

Yes, I would expect to see Planned Production orders (dynamic) in net requirements to drive the material below the phantom.

Here is an example. These are 2 different item numbers that should be planning the same way.

The one on the left shows the demand but did not create any planned production orders. The one on the right has both demand and planned production orders:

Was this reply helpful? Yes No
Suggested answer

FAC.Ansel 1,632 on at

Like (0)

Report

After a lot of digging, research, testing, and retesting, I found the issue and solution.

The problem was with the BOM Level on the items. After running the BOM recalculation, I still calculated the same wrong levels and continued to have the same issues. In a test environment, I manually updated the BOM level in the inventtable and ran scheduling and got the desired results. It appears that the recalculation considers the Production BOM's which in this case had been used in a circulatory way. So, I commented out the section of code in Class BOMLevelCalc/loadDependencies under "Get Data from ProdBOM". Then ran the recalculation. This time the levels were correct and the master scheduling run exploded the BOM's as expected.

Was this reply helpful? Yes No
Douglas Noel 3,905 on at

Like (0)

Report

Thank you for the post.

Think this will help other a lot.

Great.

Douglas

Was this reply helpful? Yes No