Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Allow Phantom Material Decision During Work Order Planning - "Phantom Toggle"

When generating a work order from a BOM with phantoms, there may be pre-existing stock to fulfil the order for the item that is phantomed. 

Allowing the BOM to control the phantom requires a planner to accept the phantoming on the BOM as created when creating a work order, as it is the pattern for the work order.  To resolve cases where there is existing stock on a phantomed item, the planner must create a Deconstruct order  to "mask" the phantom usage, or de-phantom the BOM, regenerate the work order and then un-change the bom to it's original state. This assumes their role allows this. 

In environments where there low run, high mix, and demand is lumpy, there could be different stocking strategies (pre stock vs build in place phantoms) over time that need to modulate to the meet production.  The BOM structures may not be able to anticipate future conditions beyond knowing that a phantom is needed.    Ideally, the phantom decision process can be deferred until closer to production timing.

Note 1: Keep BOMs as they are today. 

Note 2: Provide the work order tool a selectable flag in Production Details, perhaps only for lines defined as phantoms by the BOM, allowing a phantom to be the assembly, or a toggle allowing the materials to be consumed as a phantom (exploded child components) or as the item (not exploded, behave as "Regular" materials).  

Note 3: Other idea allowing ANY assembly to be phantomed during planning enhances the value of the Critical Materials tool dramatically,  This allows the Critical Materials tool to present the planner with a "blowdown" similar to MPR.  Currently, the critical materials tool "masks" visibility (by intent) to 1 level, but when phantoms are present, the tools allows visibility to the second level (or third if phantoms are nested).  

Note 4:  Conceptually, this turns the BOM phantom strategy into something more suggestive and allows deferring structure decision until later in the process.

Note 5: If this were adopted, it could be a setting (allows Phantom Toggle from Work Order during Planning).

Note 6: This would only work on orders that were "Planned" (not released, InProcess)

This idea takes the burden off of manufacturing engineers to anticipate all future conditions and also alleviates the planner of time consumptive work arounds to manage actual stocking conditions.    The strategy for stocking may change as the lifecycle of a product changes and giving the tool this proposed flexibility would make it more efficient. 


  • Sean Adams
  • Feb 8 2019
  • Gathering Feedback
  • Attach files
  • Rebekah Helton commented
    April 11, 2019 18:25

    Agree with all of this! In particular, the circumstance that sometimes subassemblies are made at the time of the parent assembly and in the same ratio as the parent assembly (a true phantom) and sometimes they are not. For example, the subassemblies may sometimes be pre-manufactured to stock if a higher demand for those subassemblies across their parents might be needed, and therefore the phantom process might not be required. Or, often the subassembly process might often be done at the same time as the parent, but other times the subassembly might be made in greater quantity than what's what's directly required by the parent ("we need to build 15 of these to build this parent item, but we'll do 10 more to have extra on the shelf").