Share
Report
44Does anybody have experience routing link codes and backwards flushing of sub-assemblies? I may be missing something obvious.
We want to backflush everything all at once when changing the status of the production order to finished and see what operation the sub-assemblies belong to on the job card report (traveler).
You can use the routing link codes to associate the component to the operation, but you cannot auto-magically backflush everything all at once if you have a routing link code for a sub-assembled item at the parent level. Here is a visual example for an item with one sub-assembly:
Below are the components for the parent item number (492020). The highlighted item is the sub-assembly. If I remove the routing link code of 30 from that sub-assembly, I can backflush everything. If I keep the 30 there, BC is looking for the sub-assembly to be done before it will backflush. It will give me the error “Reserved Item 581002 is not on inventory” when I change the status to finished.
Again, this all comes down to the job card report (traveler). The routing link code is what makes the connection between the component and the operation/work center. Without the Routing Link Code, the item does not print on the report as being a needed component for the operation. If I could keep the routing link code there for the sub-assembly and backflush everything all at once, there would not be an issue.
Have I missed something?
Categories:
All responses (
Answers (
