All -
I'm trying to run down an error, and I can't figure out how to get around it.
My user has made a Warehouse Adjustment using the Warehouse Item Journal (they were supposed to use the Whse. Phys. Invt. Journal), and they are now trying to run the "Calculate Warehouse Adjustment" function from the item journal to create the corresponding adjustment there.
When they go to post the adjustment, they are getting the following error message:
---------------------------
Microsoft Dynamics NAV
---------------------------
You must specify Expiration Date in Tracking Specification Entry No.='1'.
---------------------------
OK
---------------------------
When you go to Line -> Item Tracking Lines, the Expiration date shows up for the lot in question, so I've managed to track it back to the Reservation Entry Line, which does not have an expiration date filled in.
Does anyone have any clues on why the expiration wouldn't be filled in on the Reservation Entry, but is filled in on the Item Tracking Line? Does anyone know of a bug in the Warehouse Item Journal that causes this?
Comments
I have copied my live system to a test server, and just posted an adjustment from the Warehouse Item Journal. I adjusted out the full quantity of one lot from one bin. When I look in Warehouse Entries at this adjustment, it shows the adjustment out of the bin with an expiration date filled in, but the corresponding adjustment into our Adjustment Bin (called ADJUST) does not have the expiration date filled in. I don't know why this would be the case.
The whole Item Tracking business still needs some work. There are quite a bit of reservation entry errors in version 5 as well.
Nonetheless, please report your bug to Microsoft so they can hopefully address it in the next release. [-o<
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
http://www.BiloBeauty.com
http://www.autismspeaks.org
I've hit the exact same problem using NAV 5.01, did you get a fix for this from microsoft?
thanks
It's ugly. One of our developers ended up having to write a report to "fix" the issue after the fact. I don't like it, but without some guidance from Microsoft, we have been unsuccessful in finding and eliminating the cause.
We finally logged this with MS and got a fix to be implemented in code unit 6500 which resolved the issue for us so it might be worth trying this.
RESOLUTION
Change CodeUnit6500
PROCEDURE SumUpItemTracking@15(VAR T337@1000 : Record 337;VAR TempHandlingSpecification@1007 : TEMPORARY Record 336;SumPerLine@1006 : Boolean;SumPerLotSN@1008 : Boolean) @1003 : Boolean; VAR
NextEntryNo@1004 : Integer;
EntriesExist@1001 : Boolean; //New Line
ExpDate@1002 : Date; //New Line
BEGIN
.........
TempHandlingSpecification."Buffer Value1" += // Late Binding TempHandlingSpecification."Qty. to Handle (Base)"; ExpDate := ExistingExpirationDate(T337."Item No.",T337."Variant Code",T337."Lot No.",T337."Serial No.",FALSE,EntriesExist); //New Line IF EntriesExist THEN //New Line TempHandlingSpecification."Expiration Date" := ExpDate; //New Line
TempHandlingSpecification.INSERT;
END;
END;
UNTIL T337.NEXT = 0;
hope this helps.
However if I post an Item Journal Line (pos. adjmt), the expiration date is once again blank in warehouse entries...
As I understand,the issue is this
1. Positive Adjustment on Warehouse Journal with lot and expiration date goes in correct.
2. Negative Adjustment on Warehouse journal with lot and expiration date -> expiration date is blank in warehouse entries.
This is correct as the negative adjustment is applied against the positive one.
While doing Item journal posting you will find a similar case, Navision only posts expiration date on positive entries and while posting negative entries it verifies the expiration date from the positive entry.
The error that you are facing here is there because you are trying to post negative adjustment without the positive one.
You're point being?
I really dont get it.
I have checked Nav 2009Sp1 and am not getting this issue.
Are you using advanced warehousing?
On Item tracking code card are Lot Warehouse tracking and Man. Expir. date Entry reqd. ticked?
If your answer is yes to the above questions in that case then for Standard Warehousing Location - White - Expiration date gets posted to warehouse entry.
No, I'm using the location silver.
No becuase the item calculates the Expir. date from Expiration Calculation field on the item, at least I expect it will...
If you are not using Warehouse Tracking on Lot Tracking card then the entries posted in warehouse entry will not be
lot wise and hence it is not logical to post expiration date (Which is lot wise) in warehouse entry. This date will reflect in the ILE which is lot wise.
I think nav is working fine in Nav2009SP1
I am using lot tracking but I'm not using manual exp date.
On Item tracking code card is Lot Warehouse tracking ticked? - > If Yes
Then this works , I am sure just checked in Nav 2009 SP1 for Silver Location.
So I made a new Item, expiration date calc = 6M.
I choose the Item Tracking Code for this Item where everything is ticked on the "Lot No." tabpane.
Location Silver is only ticked for "Bin Mandatory".
I create a new Lot No. for this new item.
I create a positive adjmt item journal line for this new item on location silver, I set the Item tracking for this line to the new Lot No. I created.
I post the item jnl line.
Exp. date ILE -> today + 6M -> CORRECT
Exp. date WHE -> blank.. ???
Did the lot no. get posted in whse. entry?
Also try making 3 new lots for the item you just created.
Make a positive adjustment for the item on location silver,set the Item tracking for this line to the 3 new Lot No.created
Post the item jnl.
Ex:
Item Jnl -> Item1 30 PCS
Tracking -> Lot1 10 PCS
Lot2 10 PCS
Lot3 10 PCS
Check the ledgers you should get 3 ILE and 3 Whse entry and all entries should have lot no. and expiration date.
If you get 3 whse entries and no expiration date then there is some localization here that is making my db post entries correctly.
Has anyone succeeded in resolving this?..If yes, please help. My version is NAV 2009SP1. I have tried adding the code mentioned in this post. But it didn't work.
Any help is higly appreciated.
Thanks,
Manjusree