web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Phantom Lines Not Expl...
Microsoft Dynamics AX (Archived)

Phantom Lines Not Exploding Consistently

(0) ShareShare
ReportReport
Posted on by Community Member

Hello,

In Dynamics AX 2012, we use phantom BOMs quite frequently. We seem to have the same settings for the same phantom line in different products, but when a production order is firmed from a master plan order from two different products, one may explode the phantom BOM correctly into the production BOM, but the other will not.

Does anyone know what could cause a phantom BOM not to explode properly?

Thank you,

Stephen M.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    This will probably not answer your question fully, but perhaps it will get you one step closer.

    In class ReqTransPoMarkFirm, I found the following code in method createProdBOM.

    It appears in addition to being typed as Phantom on the Bill of material line itself, the coverage must be "derived directly" and the Released product must be of type Item (not Service).  The "derived directly" is probably what causes the seemingly random behavior in your question.

            if (   reqTransBOM.bomType == BOMType::Phantom
            && reqTransBOM.IsDerivedDirectly
            && inventTable.ItemType == ItemType::Item)
        {
            if (!bom.BOMMap::itemBOMId(_prodTable.bomDate,reqTransBOM.Qty,reqTransBOM.inventDim()))
            {
                throw error(strFmt("@SYS112833",_prodTable.ItemId,reqTransBOM.ItemId,reqTransBOM.inventDim().InventSiteId));
            }

            // expand phantom

            reqTransDerived = reqTransBOM.reqTransDirectlyDerived(true);
            if (reqTransDerived.RecId)
            {
  • Community Member Profile Picture
    Community Member on at

    Thank you for the quick response, Brandon!

    I have checked a few Master Plan orders and production orders based on what you suggested, and I have found that when a phantom is pulled in to a Master Plan Order properly, it generates an MPO for the Phantom component with the checkbox "Directly Derived" checked.

    However, this same Phantom component as a line on a different BOM does not even populate into the Derived Requirements for a Master Plan Order for that BOM.

    I believe this means that the Phantom component itself may be set up correctly and the issue may be with individual items. I am unsure of this, however. It also seems to be related to the passage of time. The same item which generates an MPO that omits a Phantom line, when run a week or so later (according to our scheduler) will no longer omit that Phantom line, even though no changes have been made to any of the involved items or BOM lines.

    I have tried changing the Master Plan schedule for the item but that does not seem to have an effect.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Brandon,

    We were able to determine the cause of the issue. It would appear that when a Master Plan Order is cut by the AX system for a demand that is a certain distance in the future (e.g. 35 days) and the Coverage Group for a Phantom component within the standard BOM for that item is set to a shorter span than that (e.g. 15 days), then the AX system does not create a directly derived Master Plan Order for the Phantom component before the main Master Plan Order is firmed. Because of this, when the main Master Plan Order is firmed, the Phantom component's derived requirements are not exploded into the main Master Plan Order's production BOM.

    It appears that we can resolve the issue by increasing the span of the Coverage Group for the Phantom component (because our Phantom components will always be Phantom, our plan is to just set the Coverage Group for 90 days, the longest Coverage Group span that we have).

    Thank you for your assistance!

  • Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    Excellent to hear!  So IsDerivedDirectly was the culprit after all?

    Please mark as answered if you think this thread might help others in the future.

    Thanks!

  • Community Member Profile Picture
    Community Member on at

    Brandon, IsDerivedDirectly is the culprit in the sense that the main Master Plan Order, when firmed, looks for all of the directly derived Master Plan Orders in order to populate its production BOM.

    If there is no directly derived Master Plan Order (perhaps because there are no Phantom lines, or because the Phantom components in the standard BOM lines do not have an appropriate Coverage Group time frame compared to the main item), then there are no directly derived requirements for the production BOM to pull in when it is firmed.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans