Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Greg Pope]

We are running into an issue when costing items with phantom lines in the BOM. Basically, it appears AX is creating a longer routing with more operations by merging the routing of the parent and the phantom but is getting an error because the new ending operation number does not end with 0.

In the example below the parent has operations 10-100 and the phantom has operations 10-40 but the error references operation 150.

Does anyone know how to address this?

——————————
Greg Pope
Master Scheduler
Paul Reed Smith Guitars
Stevensville MD
——————————

[Archive User]

Did you try to run Route Updating function?
The other thing to avoid issues with numbering I would strongly recommend that Route numbering be unique and not to overlap.
What mean is leave a suitable gap in the main route for the phantom to be placed in and not to cause any sequential issue.

——————————
Marek Chrzanowski, P.Eng., M.Eng.
Inside Consultant
Dynamics AX 2012 R3
Cyclone Mfg
Toronto, ON, Canada
——————————
——————————————-

[Greg Pope]

Hi Marek,

Thanks for the suggestion.

I was able to correct this by removing the routing from the phantom and placing those operations between the operations preceding the backflush operation of the parent.

——————————
Greg Pope
Master Scheduler
Paul Reed Smith Guitars
Stevensville MD
——————————
——————————————-