Item Tracking Code cannot be changed, when item already has Item Ledger Entries. The main reason behind is costing. To better understand this design, it would be good to differentiate between cost application and item application:
– Item Ledger Entry Application: Defines what ILE to use when applying an outbound entry to an inbound.
– Cost Application: Defines where to take the cost from (ie. which ILE’s) for a give outbound entry.
Having this in mind, item tracking code impacts in both ILE and Cost Application. Therefore, changing this is a critical change which need to be thought carefully before applying it.
If we assume this change is allowed, what would happen to those ILE that could later be reopened (ie. an item charge to a purchase, undo receipt/shipment, etc) which have now a different cost or item ledger entry application? If these are reopened ILEs, how should NAV apply costs to these ILE’s? Or, what would happen with costs if lot tracking is changed to a serial tracking?
Saying this, I must agree there could be different solutions to address these scenarios (ie. split the lot costs into serial costs, …). However, I also believe it would be very difficult to find an acceptable solution within the Dynamics NAV community since each of them has a different business process and understanding. I assume, Microsoft development considered the best design option was not to allowed doing this and forcing users to create a new item,
In case this is considered, a workaround would be:
– Not to leave any ILE opened for this item
– To remove all quantities from stock
– Rename the item
– Create a new item (with old item name) and with the correct item tracking code
– To post positive adjustment for the stock against this new item
Dynamics NAV SCM Support Land ... in Madrid 