We currently use item journal to enter all item consumed in our inventory. Fuels consumed by a vehicle is entered as a negative entry, and we have set up the vehicles in a dimension, so that we can monitor the fuel consumption for each vehicle.
However, we also require additional information like number of kilometers traveled. As a user, I was planning to show and use the "External Document No.’ field to enter the kilometers traveled, since it is saved in the Item Ledger Entry and Value Entry tables.
Based on our license, we can only hide/show fields, but can not ADD fields since it needs a developer license for the new field to be saved.
I also noticed that there fields Run Time, End Time, Starting Time, Ending Time which I think is useful, but since these fields are not in the Item Ledger Entry and Value Entry tables, I’m not sure where to extract the data once the item journal is posted. And, if this will affect other processes.
We are running on Nav 2009 SP1, and we do not use manufacturing module. At this point, I don’t want to request modifications from our partner, since we are looking at upgrading to 2013.
Would you know if there other fields that I can “re-use” for a different purpose and will not affect Nav’s data integrity?
Playing more with this, I was tried to increase the size of this field from code(20) to code(50) in the following tables:
a. G/L Entry
b. Item Ledger Entry
c. Gen. Journal Line
d. Item Journal Line
e. Value Entry
But when I post the item journal, an error comes up “Overflow under type conversion of Code to Code”. This happens if I enter more than 20 characters (the default). entering less than the original size, allows me to post the journal.
It is better not to increase the standard navision fields. with their lengths… if you want to do so you have to use toold to find out the fields references in the entire database with all the application objects and vairables or assignments or transferfields and also parameters passed etc and change all over…
that is a tedious task and also very risky… because the fix can not happen 100 % dependign on the field you choose to increase the length…
if you want you can use tools like object manager to check the references of a particular fields with other DB objects.
I strongly recommend not do such things to the standard navision fields.