Open Forum

Expand all | Collapse all

Optimize Lanham's "Outbound Warehouse Request"

  • 1.  Optimize Lanham's "Outbound Warehouse Request"

    TOP CONTRIBUTOR
    Posted 12 days ago

    Hi,
    We're using Lanham's "Outbound Warehouse Request"  with a large warehouse, barcoding, hundreds of skus, and bins with lot tracking and expiration dates.
    However, a pick, of about 20 orders (which can vary in size) takes around 10-20 minutes and deadlocks NAV and sometimes it deadlocks meaning the pick selected must start over.
    Have pickers and our new 2.2 Insight Works handhelds and packers just hanging out waiting for picks to be created.

    Recently made to code changes to the program to not look at all reservation entries each time:

    CU 7312 TableData Whse. Item Tracking Line=rimd

    CU 50098
    BinContent.SETCURRENTKEY("Location Code","Item No.","Variant Code","Bin Type Code"); //J.74

    ...

    EXIT(NOT BinContent.ISEMPTY); //J.74

    I saw another post on making it a job queue though there's some concern about losing orders.

    I guess does anyone have anything they've discovered to optimize this? Speed it up and/or "go around" it in a cool way?

    #NAV2017

    ------------------------------
    Andrea Riviezzo
    IT Manager - NAV
    Charlotte's Web, Inc.
    Louisville CO
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: Optimize Lanham's "Outbound Warehouse Request"

    TOP CONTRIBUTOR
    Posted 8 days ago
    If anyone else struggles with this let me know, we've spent a lot of time in the code over the past week and found things both native NAV and within Lanham to switch around. We got pick time down to about 1 minute or less.
    Still looking for other optimization tricks, if you know any hit me up. :)

    ------------------------------
    Andrea Riviezzo
    IT Manager - NAV
    Charlotte's Web, Inc.
    Louisville CO
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 3.  RE: Optimize Lanham's "Outbound Warehouse Request"

    SILVER CONTRIBUTOR
    Posted 8 days ago

    We use Lanham OWR as well and have found it to be a valuable tool. There are places that I have modified to reduce locking / io which has helped a great deal.
    I don't like the Bin.Empty boolean, so I only maintain it for our "RESERVE" bins. In Codeunit 7301, function InsertWhseEntry, I have put an IF statement to only update Bin.Empty for our Bin."Bin Type Code" of "RESERVE". I don't care that our SHIP, RECEIVE, or PICK Homes have a BIN Code of Empty. It's the Bin Content you care about anyway. the CALCSUMS("Qty. (Base)) slows the system down.

    In our system, we always have a number of locks in the Warehouse Request table. My only thought on this is that the Warehouse Request table is so small, there are a lot of records in a Page. If lock escalation locks a page, then a larger number of rows are locked. Just my 2 cents.



    ------------------------------
    Joseph Flynn
    Sr. Dynamics NAV Developer
    Gold Star Foods INC
    Ontario CA
    ------------------------------

    Academy - Online Interactive Learning from Experts


If you've found this thread useful, dive deeper into User Group community content by role