MIGO - ME23N problem with withdraw quantity

Question

Hello,
We have found out an error when shipping outsourced materials with MIGO.
The problem comes when in a outsourcing material with components provided by us we modify the purchasing document by moving part of the stock of the component from one plant to another and dispatching the stock from only one plant. When doing this stock is not consumed from this plant, but proportionally consumed from both plants.
The given example may clarify the process:
The purchasing document has a purchasing quantity of 4 (header material). For this material to be sent from the sub-contractor to us, 16 units of one component are required (4 each header unit).
In ME23N the component data is changed, modifying the plants and creating a new line as follows. From:
Header (4 u.)
     Component (16 u.)     plant A
To:
Header (4 u.)
     Component (12 u.)      plant A
     Component (4 u.)     plant B
So basically we are moving part of the stock of the component to another plant.
The problem comes when plant B has stock of the component and it is sent to the sub-contractor and plant A has no stock available.
If with MIGO we try to dispatch 1 u. of the header by consuming only the 4 u. of plant B and unmark in MIGO stock from plant A, in MB51 the stock is consumed as it should be (4 u. from plant B), but when checking again in ME23N or RESB table stock is consumed proportionally.
The following process in MIGO
Header (4 u.)     1 dispatched.
     Component (12 u.)     0 dispatched (not marked)
     Component (4 u.)     4 dispatched (marked)
Should give the following result in RESB or ME23N:
Header (4 u.)     1 dispatched.
     Component      Requirement qty 12 u.          Quantity Withdraw 0     Plant A
     Component      Requirement qty 4 u.          Quantity Withdraw 4     Plant B
But we find the following result:
Header (4 u.)     1 dispatched.
     Component      Requirement qty 12 u.          Quantity Withdraw 3     Plant A
     Component      Requirement qty 4 u.          Quantity Withdraw 1     Plant B
And thatu2019s clearly wrong. First because all the quantity withdraw was from Plant B and second because Plant A has no Stock.
We think this might be a code error.
Thank you very much for your advice.
Regards
Edited by: Adolfo Busca on Apr 23, 2009 10:46 AM

Answer 1

Hi, Adolfo
I did a test following your example and got the same result.
Value of field Quantity Withdrawn did increase proportionally when you receive the header item.
In fact, I would rather say it shows the quantity requirement deduction of the component instead of the quantity of component you actually withdrew.
In MD04, you can see the requirement quantity of the component is also consumed proportionally while the available quantity is reduced as you actually withdrew.
With one more test, we can create a PO with Header and Component A & B. When doing GR of header item, we mark Component A and unmark Component B. In ME23N, we can see that Quantity Withdrawn field of Component B still increased. So we may say it just shows the requirement deduction of Component B.
Hope it can help.
Any further result, let's discuss it in more detail.
Wesley