Hello,
i have a dilema. Navision 4.0+ does NOT allow to delete line (item jnl, document, etc) if it has item tracking entered. I can make it to allow it, but what i want is to know WHY? WHY would it not allow it? To p$$$ us off, or..?
please enlighten me..
0
Comments
A logical explaination is that Navision wants you to very the serial numbers and lot numbers you're deleting. Getting serial/lot number mixed up is a terrible thing.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
A common scenario is:
1. Create a PO for 100 cases of lot tracked item.
2. Set lot number. (this creates tracking lines) (actually table 337)
3. Reduce the PO quantity. (error).
You have two purchase orders each with one line to Item XXX. On one PO you have Quantity 100 of Lot No. AAA and Quantity 50 of Lot No. BBB. On second PO you enter Q=20 for Lot No. BBB and Q=100 of Lot No. CCC. For each Lot No. you create Lot No. Informations. After that, you will want to delete the second PO. But in this case, you need to delete Lot No. Informations for Lot CCC but not for BBB because you need that info on first PO. What the system will do???
:-)
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
When you create a PO with 5 serial numbers, and now you want want to modify it to 4 quantities. If you don't delete the proper serial number, how will Navision know which of the 4 serial number (out of the original 5)should be on the PO?
So it makes perfect sense for Navision to prevent you from deleting the line or changing the quantity.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
for the fact that for example you can't post IJL with lots without first inserting it into table tells a LOT about currect code