The Phantom designation on an Item only carries to new BOM (Formula implied) lines that are created. It does not retroactively update existing BOM or Production BOM lines. This scenario is best handled by an Engineering Change (if live) to rev the changes. BTW, make sure the Item setup is consistent with Phantom (e.g. don’t designate the Item as Purchase in Order Settings). The same advice applies to BOM lines and Production (Batch Order) BOM (Formula) lines. You could create a runnable class. The four main BOM tables are BOMTable (header), BOMVersion (version), BOM (lines), and PRODBOM (Production Order lines). Have a look at BOM and PRODBOM (BOM snapshot used by Production). Pay keen attention to the Production Order Status if looking at PRODBOM (Estimated Status is when the BOM gets exploded). The phantom field is an Enum. If ECM is enabled, it’s possible there is another BOM related table or two. I have not looked into that.
Thanks……Dave
Login
Report
There was a problem reporting this post.
Block Member?
Please confirm you want to block this member.
You will no longer be able to:
See blocked member's posts
Mention this member in posts
Invite this member to groups
Message this member
Add this member as a connection
Please note:
This action will also remove this member from your connections and send a report to the site admin.
Please allow a few minutes for this process to complete.
Report
You have already reported this .
Welcome to our new site!
Here you will find a wealth of information created for people that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!