Automatically updating Assembly Order due date when posting warehouse shipment

whizzergowhizzergo Member Posts: 22
We currently use NAV 2016 without WMS functionality but a significant part of our business relates to ATO orders.

We have found the the assembly order due date defaults to the sales order shipment date when the assembly order is first created. However, unlike standard sales order lines' shipment date, the assembly order due date is not able to 'force update' when posting shipment of the completed ATO item from a warehouse shipment line with a different shipping date.

This results in an error:

Shipment date must be equal to 'xx/xx/xx' in sales line: Document Type=Order, Document No.=SOxxxxxx, Line No.=xxxxx. Current value is 'xx/xx/xx'

The only work around is to reopen the sales order and manually the sales order header shipping date, then accept all warnings regarding reservations and line updates. This will force update the assembly order header due date.

The question therefore is whether anybody is aware of how to 'force' this update of the assembly order due date when posting the warehouse shipment?



Answers

  • whizzergowhizzergo Member Posts: 22
    Nobody else has this experience with assembly orders?
  • whizzergowhizzergo Member Posts: 22
    This appears to be a bug in codeunit 5763. The AsmHeader record doesn't initialise and the record isn't found using the GET function. Therefore the due date isn't udpated.

    Can anyone with more skills than I prescribe a solution here?

    j9qdfy6bjx1p.png
  • ipr13ipr13 Member Posts: 8
    Hi Whizzergo,

    It's been a year or so since you have this problem. What was your approach then? Did you modify the codeunit or just go with the workaround?

    I have similar problem now (in 2019) and considering to modify the codeunit as it seems doesn't affect the core process and obviously there is a bug in this code.

    Seems NAV didn't consider that difference between Assembly Header Due Date and SalesLine Shipment date & WhseShipment Shipment date could occur. So, the error came when NAV comparing between due date and shipment date


    h4jld6y22z6o.png


  • chrisdfchrisdf Member Posts: 82
    Still have this problem with BC140 (CU11). Got around it by writing a subscriber to Codeunit 5736







Sign In or Register to comment.