Putaway tasks are not getting generated for one dock-checklist

Resolving The Problem

Putaway Process:
On Receiving:
1.The O/L Rcpt Upd' field in the receiving rule has the following options, 'Y' the receipts are updated online and the putaway tasks are generated in background. 'B' both the receipts and the put away tasks are generated online. 'N' the receipts and putaway task generation is done in background.
2. If any of the Auto Generate Putaway flags are set to 'Y' in the receiving rule then a record is inserted into the receipt_upd_queue table with the record_type as '02' and processed_flag as 'N'.

working of whbu010 -
This background job generates tasks, so that the received items can be putaway to their respective locations. Records are created in the task_list table each record has a corresponding task_id, which is generated by the sequence SEQ_TASK_ID. If two step putaway is defined in receiving rules, then two records are inserted in task_list and movement table for every item that is to be moved.
Once records in this table are processed and tasks are generated the processed_flag is updated to 'Y' if successful or 'E' in case of an error.



CHECKLIST:

1. Compare the configuration set ups of the location where the putaway move is getting generated while for the one where the move is not getting generated
2. Check if for the problem dock , the problem exists for totes and pallets or is restricted to loose SKUs
3. Try receiving a different SKU at the problem dock to see if error persists
4. Once the receiving is done, see if a record for the received sku gets inserted in the receipt_upd_queue ( This will happen if auto-putaway is turned on in 09011)
Processed flag for these records should be N, check if there are any records in Y or E status.
5.For the whbu010 to be used for creating putaway tasks the flag 'O/L Rcpt upd should be set to Y.
6. Verify that the putaway rule is configured for all diversion types and collation types that are being received at our problem dock.


Basic Background config checks to do:
1. Get the apropriate location selection rule form 09010 depending on the collation(Sku, pallet, case) and the diversion(normal, quality_insp etc) and the putaway rule got from (01018-dock set up)
2.Get the candidate location for putaway by decoding the location sel sequence using 09001, 09304
3.Check the avail capacity in location set up 09253 for problem location
If the location size type if infinite then this should be set to 100%
4. Verify that the "Freeze for putaway" flag is set to N in 09253
5. Get the receiving rule as follows:
RCD type 2 in 09753 for function used for receiving
Get field value for Parm type1= 'RCP' and Parmtype2= <RcdType2> in 09289
This is the receiving rule
6. In receiving rules check flag setting for "rules for closing receipt " section. Verify is there is autoputaway selected for different collations.(09011)
2. If the location selected by the location selection rule happens to be a staging location then the putaway tasks are not generated, the record in receipt_upd_queue is set to E status