Problem while registering Pick
manjusree
Member Posts: 79
Hi all,
we are facing the following issue with WMS on Navision-4 SP3.
Suppose we are trying to register a pick/put-away document and an error (for eg., required inventory not available) comes in between or the system got hanged. If we try to register again, the system says, registered pick/put-away has been already created. From back end, we can delete it, no problem. But where the issue comes is some items are taken from the respective bins, but not placed anywhere. We need to do a lot of corrections before posting it again. This problem occurs frequently when the pick contains quite a lot of items.
Any kind of customization can solve this?. Any kind of help would be appreciated.
regards,
Manju
we are facing the following issue with WMS on Navision-4 SP3.
Suppose we are trying to register a pick/put-away document and an error (for eg., required inventory not available) comes in between or the system got hanged. If we try to register again, the system says, registered pick/put-away has been already created. From back end, we can delete it, no problem. But where the issue comes is some items are taken from the respective bins, but not placed anywhere. We need to do a lot of corrections before posting it again. This problem occurs frequently when the pick contains quite a lot of items.
Any kind of customization can solve this?. Any kind of help would be appreciated.
regards,
Manju
0
Answers
-
check the code where you are getting error with Debugger0
-
Actually the probelm is whenever the registering process breaks in between, the system is not bringing the pick back to its initial state. Instead, some lines get partially posted. I've not seen such a problem anywhere else in Nav.
Thanks,
Manju0 -
Then there is a COMMIT somewhere in the code, and the posting breaks after that. That is the only way to get a partially posted document.
From experience, this occurs when there are customizations that are implemented AFTER this COMMIT, and something goes wrong with them. Solution is either to move those customizations before the COMMIT, or if this is not possible, make sure ( through some checks before the COMMIT ) that the customization won't break.0 -
Thank u so much. I think thats the problem.
Cheers,
Manju0
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
- 322 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
