Hi I want to find where one Serial Number is currently. Some Locations has bin Mandatory. where is information about it. In one table or more than one table
From the item ledger entries navigate to the warehouse ledger entries. These can be considered a strange beast and it is the structure of the bins and serial number information that causes issues here, but if you have a look here you can see the serial number and bin on the same line, it is then just understanding this information.
The art of teaching is clarity and the art of learning is to listen
You can't really link it - linking by Document No. and Item No. is not reliable enough and there isn't anything else.
Forget about linking. Simply look at that item ledger entry of the serial no that has remaining quantity. If it's a non-bin warehouse, throw the location code on the report. If it's a bin warehouse, forget the item ledger entry and just throw the last (by entry no.) warehouse entry of the serial no. there.
But I have a general suggestion. Standard Serial or Lot tracking in Navision simply sucks if used with Bins. It's very badly designed. I never used serial tracking, but I used lot tracking a lot (it's almost the same, serial is easier as quantity is always 1), and what I did is I created a new table called Stock By Bin and Lot and which is similar to Bin Contents: it's key is Location, Bin, Item No, Lot no, and has a quantity flowfield for summing up warehouse entries by these four fields. (I could have just extended the standard Bin Contents but it was cleaner this way). When a wareouse entry is posted, in the registering codeunit I create the entry into this table if it does not exist. And that's it. From that on that table is *the* inventory table. It's used for everything, stock reports, picking lists, physical inventory, or just throw on the form and have the users filter it any way they want. Very useful. Should be standard. You should do this, with the only difference of having the serial no. instead of the lot no. It requires a bit of work but saves a lot more future work.
Comments
Filter the lines on Sr. no you want to find and remaining Qty >0.
and check the location.
Senior Consultan
SETRANGE("Posting Date",FromDate,StatusDate);
....
IF "Item Ledger Entry"."Serial No." <= ' ' THEN
CurrReport.SKIP;
CalcRemainingQty;
IF RemainingQty = 0 THEN
CurrReport.SKIP;
GetLastLocation;
where I must link to the Warehouse entry
Forget about linking. Simply look at that item ledger entry of the serial no that has remaining quantity. If it's a non-bin warehouse, throw the location code on the report. If it's a bin warehouse, forget the item ledger entry and just throw the last (by entry no.) warehouse entry of the serial no. there.
But I have a general suggestion. Standard Serial or Lot tracking in Navision simply sucks if used with Bins. It's very badly designed. I never used serial tracking, but I used lot tracking a lot (it's almost the same, serial is easier as quantity is always 1), and what I did is I created a new table called Stock By Bin and Lot and which is similar to Bin Contents: it's key is Location, Bin, Item No, Lot no, and has a quantity flowfield for summing up warehouse entries by these four fields. (I could have just extended the standard Bin Contents but it was cleaner this way). When a wareouse entry is posted, in the registering codeunit I create the entry into this table if it does not exist. And that's it. From that on that table is *the* inventory table. It's used for everything, stock reports, picking lists, physical inventory, or just throw on the form and have the users filter it any way they want. Very useful. Should be standard. You should do this, with the only difference of having the serial no. instead of the lot no. It requires a bit of work but saves a lot more future work.