[Easy to fly] a picking list single warehouse "Fly" caused by thinking

[Abstract] Our company at the beginning of the month before the 10th financial statements, so before the 10th to do the completion of this month. The PMC Manager received a response from the warehouse clerk. 30408011003 material on the account how there are so many, the last time the material was sent out. The
can also supply a picking list: 5403-20150707032. It's not a leak. Re-count the existing inventory. Results after running, the inventory ledger is still unable to find the picking list, what causes it?
whether the inventory transaction details are not written.
The warehouse number is missing further query corresponding picking the body alone, and sure enough also lost. How did you lose it? There is no discussion here.

Financial said: Today's report has been submitted to the leader. It's impossible to re-run the cost ...
Background query in July There are three picking list single lost, 2012 there are 6. Let's do it in the July through the other repositories.
So how do you prevent such exceptions from happening later? Workaround: At the end of the month check the picking list single warehouse is missing.
Sql:select TE001 Picking list, TE002 picking order, TE003 line number, TE004 product number, TE005 quantity, TE008 Warehouse from mocte inner join MOCTC on te001=tc001 and T e002=tc002 WHERE te008= "and tc003> ' 20150801 '
Set parameters:

Set Send parameters:

Effect:

Oak said you can set not allow blank AH. Implementation: Pre-control much better, set a custom screen to prohibit blank. The

issue is a temporary paragraph, but does this affect the cost of work orders? Reckoned is the cost of work orders is low, because this is put only low cannot high. The
needs logic to support its own idea: the picking list alone does not have a cost field, which is written to maintain inventory transaction details when the product number of the monthly document cost combined quantity calculation amount. At the end of the month, the weighted average unit cost is calculated, the picking list affects the cost code assignment is n, re-assigns the value to maintain the transaction details;
When the cost is collected: The work order associated picking list is associated with maintaining inventory transaction details. (assuming that the correlation condition requires a warehouse, it is not possible to grab the secondary picking list cost)
theory is theory: Need data to support my idea.
Maintain work order cost vs Maintain inventory transaction details

Material cost: 6645.

Export Comparison:

Sure enough, the cost of picking list for this lost warehouse is not collected into the ticket cost.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

[Easy to fly] a picking list single warehouse "Fly" caused by thinking