We have discovered today that items using lot tracking can not be included as part of a BOM. This causes a huge problem so we need to find a solution. We’ve been racking out brains trying to come up with the best answer. Does anyone have a good idea about how this should be “fixed”? At this point I’m open to all suggestions. Thanks.
Hello Mindi, I have an axe to grind with Navision regarding the use of Bins and Lot Nos. with BOMs too. It annoys me that in the standard Navision Financials package, they included Bin Code and Lot No. in the BOM Journal Line table & form, but did not put any code into the posting routines to use them! When i spoke to Navision about this, they siad that the BOM Journal had neve been intended to work with them! (So why include the fields?) When Attain was released, Navision just wimped out and removed the fields from the form… Assuming you are using Navision Financials, you could try this simple solution I did for bins (But the same is true for Lot Nos.). Modify code unit 32 (BOM Jnl.-Post Line) so that the bin code/lot no. is taken from the BOM Journal Line and copied into the Item Journal Line that Navision creates behind the scenes. e.g. ItemJnlLine.“Lot No.” := “Lot No.”; Then do the same from the negative adjustment for the sub-components. This is a bit of a simplistic solution as you need to make sure that all the sub-components have the same lot no., and in some cases this would have to be done using a transfer journal, but hopefully this will give you a starting point! Hope this is of help. -------------------------------- Edward Bloomfield Microsoft Navision Support Consultant Cambridge Online Systems Limited www.cambridgeonline.net
I have created separate Production BOM Header, Line tables in base financials which similar to the BOM Journal line. The header is used to select the parent item, and the BOM component lines are copied to the Production BOM lines. The Production BOM header/lines have the separate capability to specify Location Code, Bin Code, Lot Number etc. Therefore the components do not have to inherit these parameters from the parent item. As Edward suggests, I have cloned the BOM post line function, and modified accordingly.
No unfortunately we are using Attain and the new lot tracking functionality.
I heard that tracking was changing in Attain 3.60…you should investigate before making your decision.
Actually, lot tracking has not changed in 3.60 with assembly BOMs. The Lot No. Information table is not linked to the form; even if it was, it would take a lot of effort (no pun intended) to make it work for components. Allen Beck President Beck Consulting Alameda, CA & Bellevue, WA allen@beckconsulting.com 800-456-8474
Hi Having been aroungd the block several times with Navision over the use of lot and serial numbers in the BOM Journal this simply looks like something they are not going to change. The division seems to be that if you are in a simple kitting environment then the BOM Journal can be utilised, if you after more advanced features, like the item tracking functionality, then you have to go down the production route and use the production BOMs in conjuction with the output and consumption journals. The other alternative is to modify it of course. Sorry, but if you want to carry on the bashing your head against a brick wall routine, please feel free!! Steve
We did out own function filling A Item Journal with Neg. and Pos Adjustment to solv this problem. Per.Bay@navigera.com Product Manager www.navigera.com
I thought I would go down this route but came across a problem when trying to assign serial numbers to the negative adjustments for the BOM components in the Item Tracking lines Window. The cause is that the ItemTrackingLine.Positive must be True when ItemTrackingCode.“SN Specific Tracking”=TRUE and ItemTrackingCode.“SN Specific Tracking” has to be TRUE if costing method for the item is Specific. [?]I thought I had to use costing method=specific for serial numbered products? What is the upshot of using FIFO on a serial numbered product, apart from not being forced to assign serial numbers every time? What would be the upshot of bypassing the ItemTrackingLine.Positive=TRUE test that causes the error in the item tracking line table? Help![xx(] Any thoughts greatly appreciated![:D]
Please ignore previous rambling! Just realised what i was doing too late. Of course you have to pick a specific item for a negative adjustment, not assign a new serial number to it! Stop laughing you lot![:I]
I have a similar problem. We are trying to use items with lot tracking in a BOM. For those who have customize the BOM functionalty, can you kindly give me details on how you did it? Please assist