Difference between revisions of "Information Systems:Reserved Stock"
m (Text replacement - "DFU" to "Information Systems:DFU") |
|||
| Line 30: | Line 30: | ||
TOTAL 24.000 |
TOTAL 24.000 |
||
| − | Use [[DFU]] on file WH1LOP in library UP1480BFVA to make corrections. In the above report, the two locations with negative reserve have to be fixed. Location Z2 A214 shows a zero onhand, so that record should be deleted. H1 L437 has an onhand, so that record must be updated. Clear 'Quantity reserved for pick'. If, when you look at this query again in a day or so, the reserved quantities don't change, they should be corrected the same way. |
+ | Use [[Information Systems:DFU]] on file WH1LOP in library UP1480BFVA to make corrections. In the above report, the two locations with negative reserve have to be fixed. Location Z2 A214 shows a zero onhand, so that record should be deleted. H1 L437 has an onhand, so that record must be updated. Clear 'Quantity reserved for pick'. If, when you look at this query again in a day or so, the reserved quantities don't change, they should be corrected the same way. |
Revision as of 15:34, 17 June 2016
When a sales order is dropped for picking, the items on it are reserved, so that we do not accept orders for more than we have in stock. The quantity available to sell is onhand less reserved. Items are also reserved, or unavailable to sell, if there is a location move in process, the location is to be counted, or they have just come in on a shipment that has not yet been closed. (For these last two, the stock isn't in reserved; flags are set to make the location unavailable.)
This ‘reserved’ amount can become incorrect; sometimes when the transaction is cancelled. If it is wrong, we will not accept orders for stock that is actually available.
There is a query that will check for this. (Currently, I am running this once a week, on Fridays.) From a command line in ASW, key in -
RUNQRY HELDERRORS and press enter.
This query is able to exclude items that have status 30 orders (pick lists) against them, but not counting, replenishment, receiving, and picking. So it is best to run this in the morning, and refresh every few minutes. If there are no errors in the reserved amount, when the time comes when all activities have completed but picking has not yet started, no items will be listed.
If there a few items that won’t clear, you have no way of telling if there is activity causing the difference, or if there really is a problem. So make note of the items and quantities (print screen), and see if they are still on the list next time you run this. In this case, I run it again on Monday.
Negative reserved quantities are an error, and need to be cleared as stock will not be correctly reserved for orders that drop for picking.
Display Report
Query . . . : SHEILA1/HELDERRORS Report width . . . . . : 127
Position to line . . . . . Shift to column . . . . . .
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+...10....+...11.
Whs Loc Loc ID Item First Oldest Quantity in reserved on P L Qty on P O Held
zon put away reception location for pick bal
date date Y/N
MAI N2 D509 00423699 20150302 20151014 18.000 4.000 8.000 N
MAI Z2 A214 02050466 20151026 20151026 .000 37.000- N
MAI RX V510 02150886 20140722 20151110 165.000 10.000 360.000 N
MAI N1 F608 02159895 20150323 20151020 13.000 1.000 N
MAI H1 L437 02337277 20141121 20151026 3.000 1.000- N
MAI Z3 SUPL 02468403 20150622 20151027 123.000 47.000 48.000 N
FINAL TOTALS
TOTAL 24.000
Use Information Systems:DFU on file WH1LOP in library UP1480BFVA to make corrections. In the above report, the two locations with negative reserve have to be fixed. Location Z2 A214 shows a zero onhand, so that record should be deleted. H1 L437 has an onhand, so that record must be updated. Clear 'Quantity reserved for pick'. If, when you look at this query again in a day or so, the reserved quantities don't change, they should be corrected the same way.