Automatically updating Assembly Order due date when posting warehouse shipment

whizzergo
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?
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?
0
Answers
-
Nobody else has this experience with assembly orders?0
-
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?
0 -
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
0 -
Still have this problem with BC140 (CU11). Got around it by writing a subscriber to Codeunit 5736
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions