That component is listed twice on the work order components list (once as the part and once as a component). One has a LOP code the other one does not.
The one without the LOP code has 600 (Batch Number GR1234) issued to it , and the one with the LOP code has 205 (Batch Number 2315) issued to it.
This is controlled by control flag: LOP_CODE_ON_COMPONENTS
The LOP code on from the assembly is by default included on the works order components, but this has some side effects which make it unsuitable for some customers.
The advantage of including it is that a component can be on the components list more than once each with a different LOP code.
But this also means that there will be a sub-works order for each LOP code for a given component. Further still if the LOP code on a component is changed the original sub-works order will no longer be valid for the component - it will be updated to zero required and a new sub-works order will be created to replace it.
If this control flag is set to No then it will not be possible to have a component on a works order more than once. All requirements for a particular component will be be added together and included once.
If this control flag is set to Yes it will not be possible to keep an existing sub-works order when the LOP number on the assembly is changed and then the works order is updated.
Upon review it would appear that the stock was allocated to the second (erroneous) instance of the Part Number (P/N), but then the BOM was updated which removed the second instance of the P/N, and the W/O update, which removed the P/N line but also removed the allocated stock.
Same part listed in view components with different figures for quantity issued
There are different stock issued figures from the component list for a manufactured part. For example, upon issuing a quantity of 600pcs of P/N 12345A to W/O 1234.01, we find only 205pcs showing as allocated, even though all records show 600pcs allocated.
J
Written by Jes Foxall-Beckley
Updated over 3 weeks ago