Work Directives Are Not Deleted Even After Deleting Corresponding Picks, Causing Performance Issues (Doc ID 1307798.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Warehouse Management System - Version 12.0 to 12.0.11.2 [Release 12.0]
Information in this document applies to any platform.
Checked for relevance on 18-Feb-2015

Symptoms

The work directive records are not deleted from WORK_DIRECTIVE table, even after deleting the corresponding pick directives. Hence the WORK_DIRECTIVE table contains a large number of unnecessary records, causing a performance issue with respect to CF picking.
Steps to Reproduce:
1. Create a stock order for an item for 1/2 pallet to a single store. Assign ‘B’ pick process to item and the reserve pallet location.
2. Create a second stock order for the same item for the other 1/2 pallet to same store.
3. Run the wave for the two stock orders.
4. Notice that there is one pick to container for the two B pick records.
5. Also notice that there are two records for this B pick in WORK_DIRECTIVE table.
6. Complete the B pick.
7. Notice that one work directive record remains in WORK_DIRECTIVE table.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms