Sage 100

Don't have a quick response, though I would probably export the entire table into my Excel spreadsheet, fix the missing data, create blank tables and reimport via VI.

However, I would be interested in the migration specifics and whether you contacted Sage and what their response was.  When you mention B of M, are you referring to the BOM module or the material listing in the PM template?  Is this a PM issue or a BOM issue?

When creating a new BOM, the copy from BOM routine will not work unless the Step Numbers are populated on the bill you are trying to copy.  I discovered this same Step Number issue on an upgrade last weekend and one this weekend.  I have an open case with Karen at Sage for a call back on Tuesday.  Unfortunately, you cannot import into an existing BOM detail line because the Sequence Line Number is not available, and any attempted imports will duplicate the line.  I had to export out the entire BOM detail file, reinitialize the file and then do a VI import to assign step 000000 to all bill detail lines.  Fortunately, you can just reimport the entire file and if the bill did not need step numbers it will not import the step number field.  You need to still be careful if any bills did have other step numbers assigned previously.  

I have discovered many issues with PM conversions.  If step 0000 doesn't exist, the conversion copies the first step and duplicates it as step 0000 which results in double labor amounts budgeted.  WIP GL accounts do not populate if more than one is used, departments need to be assigned, can't change work ticket class on existing templates so GL applied accounts are wrong, production run rates don't populate and have to be imported.  Can't change the template in work ticket entry if assigned in BOM, but need to populate the template in inventory if using ScanForce Make to Order since it doesn't pull from BOM.  Work instructions entered into Extended Text on template will create a new record in CI_ExtendedDescription and everytime you edit a work instruction it will create a new record in CI_ExtendedDescription and abandon the key/record.  Thus, you gets lots of abandoned records and need to use the CI purge utility for obsolete extended descriptions.  Work ticket travelers print work instructions twice.  Completed work orders that were not closed before the conversion may post to WIP accounts when closed in 2023 even though no WIP existed.  Just a few more gotcha's to look out for.

Yep, just a "few" gotchas......  Big sigh!!

When creating a new BOM, the copy from BOM routine will not work unless the Step Numbers are populated on the bill you are trying to copy.  I discovered this same Step Number issue on an upgrade last weekend and one this weekend.  I have an open case with Karen at Sage for a call back on Tuesday.  Unfortunately, you cannot import into an existing BOM detail line because the Sequence Line Number is not available, and any attempted imports will duplicate the line.  I had to export out the entire BOM detail file, reinitialize the file and then do a VI import to assign step 000000 to all bill detail lines.  Fortunately, you can just reimport the entire file and if the bill did not need step numbers it will not import the step number field.  You need to still be careful if any bills did have other step numbers assigned previously.  

I have discovered many issues with PM conversions.  If step 0000 doesn't exist, the conversion copies the first step and duplicates it as step 0000 which results in double labor amounts budgeted.  WIP GL accounts do not populate if more than one is used, departments need to be assigned, can't change work ticket class on existing templates so GL applied accounts are wrong, production run rates don't populate and have to be imported.  Can't change the template in work ticket entry if assigned in BOM, but need to populate the template in inventory if using ScanForce Make to Order since it doesn't pull from BOM.  Work instructions entered into Extended Text on template will create a new record in CI_ExtendedDescription and everytime you edit a work instruction it will create a new record in CI_ExtendedDescription and abandon the key/record.  Thus, you gets lots of abandoned records and need to use the CI purge utility for obsolete extended descriptions.  Work ticket travelers print work instructions twice.  Completed work orders that were not closed before the conversion may post to WIP accounts when closed in 2023 even though no WIP existed.  Just a few more gotcha's to look out for.

When creating a new BOM, the copy from BOM routine will not work unless the Step Numbers are populated on the bill you are trying to copy.  I discovered this same Step Number issue on an upgrade last weekend and one this weekend.  I have an open case with Karen at Sage for a call back on Tuesday.  Unfortunately, you cannot import into an existing BOM detail line because the Sequence Line Number is not available, and any attempted imports will duplicate the line.  I had to export out the entire BOM detail file, reinitialize the file and then do a VI import to assign step 000000 to all bill detail lines.  Fortunately, you can just reimport the entire file and if the bill did not need step numbers it will not import the step number field.  You need to still be careful if any bills did have other step numbers assigned previously.  

I have discovered many issues with PM conversions.  If step 0000 doesn't exist, the conversion copies the first step and duplicates it as step 0000 which results in double labor amounts budgeted.  WIP GL accounts do not populate if more than one is used, departments need to be assigned, can't change work ticket class on existing templates so GL applied accounts are wrong, production run rates don't populate and have to be imported.  Can't change the template in work ticket entry if assigned in BOM, but need to populate the template in inventory if using ScanForce Make to Order since it doesn't pull from BOM.  Work instructions entered into Extended Text on template will create a new record in CI_ExtendedDescription and everytime you edit a work instruction it will create a new record in CI_ExtendedDescription and abandon the key/record.  Thus, you gets lots of abandoned records and need to use the CI purge utility for obsolete extended descriptions.  Work ticket travelers print work instructions twice.  Completed work orders that were not closed before the conversion may post to WIP accounts when closed in 2023 even though no WIP existed.  Just a few more gotcha's to look out for.