Sage 100

Kits not exploding properly! I imported items and kits into a test company made from production. Tested the explosion and PO Generation from Sales Order. Everything works right. Use the same spreadsheets to import into production. Now the first line of the kits are not populating when exploding the item on the sales order. Looked everywhere and can't seem to find any rhyme or reason. Any thoughts? Other than me doing work is very dangerous (for my clients that is)...

Are you importing from .xls(x) or .csv? VI is more reliable with CSV.

I know it seems unrealted, but it Explode Sub Assembly checked in BOM Options? Check or uncheck Maybe it will re-write a table?

Used csv, but the Kits look fine in Kit maintenance. Just on Sales Order not getting first line in the kit. In Product LIne Maintenance we have all product lines set to Prompt under Explode Kit Items.

Are you importing ""Y"" into the Explode field in the VI job?

If you enter a kit manually does it explode properly on sales orders?

I did a test where i removed the line 1 item and added it back (now has reference line 3) and it did not add. Also I think the Y in the VI job is for the Print Detail - Select this check box to print sales kit component items in detail on a sales order or invoice. Clear this check box to print only the sales kit item code and description without any component item detail. They do not want to show the detail on the sales order.

Are you doing inventory kits or BOM kits?

Kits only. No manufacturing, and the kits are typically two items to 2 different vendors. Very simple. It works perfectly in test. I can setup a dummy item in production to test from scratch, but I date to litter their system.

No, I mean are these inventory kits or the BOM module kits?

Inventory Kits - No BOM. It appears that the default vendor ID was changed in the production company so the import passed, but the vendor did not populate as the primary vendor. Therefore the PO was not being generated without a primary vendor. Interestingly, since they failed on import of the vendor alias codes, that load was rerun during go live with the correct vendor ID. A simple updateof the primary vendor fixed the problem.

@GaryFeldman Thank you for the update!