Skip to main content
Solved

BOM ID not acting as expected in import scenario

  • May 5, 2025
  • 7 replies
  • 140 views

Forum|alt.badge.img

H, working on importing some BOM’s into the Bill of Material screen.  I believe I have the hard part working, it’s creating the BOM as expected with multiple operations and/or materials listed under the operations.  My issue is with the BOM ID field.  I want the system to auto-generate the BOM ID field.  The AMBOM numbering sequence is NOT set to manual.  If I hand enter a BOM and hit Save, it creates the BOM ID using the numbering sequence BUT my import scenario when run, creates the BOM using the BOM ID from my spreadsheet.  From previous experience in other screens, I’ve seen the value in the spreadsheet, is kind of ignored by Acumatica and it will just generate the next number from the sequence for example when importing AP Bills and I want to use the auto seq for the reference number.  

My initial import scenario, was mapping the inventory ID as the BOM ID.  Thinking again, that the BOM ID value itself in the spreadsheet is immaterial and just used for grouping when auto numbering is active and it actually worked in that I have say 8 rows pertaining to the BOM and it put all the rows into the same BOM correctly.  It’s just that the BOM ID didn’t get auto numbered.  Maybe it’s just the way this screen acts?  It’s going to be a pain if I have to prep the BOM IDs in the spreadsheet before hand!  Any suggestions or answers would be appreciated.  Thanks!

Best answer by rskieresz88

@valentynbeznosiuk  thank you for your research into this.  Your suggestions did help a bit, but I still was having some issues and errors when trying to create more than one BOM.  I did play around with unchecking the cancel box on the import scenario and it was changing things, but I still wasn’t able to get it to the point of it correctly assigning the ID and recognizing the change to create the next BOM.  I probably didn’t try all the combinations I could of with this and maybe your suggestion could of worked in the end with more trial and error on my part, but I made the decision to just manually populate the BOM ID field on the spreadsheet based on their numbering scheme.  As I said from the start, the scenario itself was working fine when the BOM ID assignment was taken out of the mix.  So I did that, changed the numbering sequence to manual and imported the about 200 BOMs from the spreadsheet with no issues whatsoever.  

This isn’t the last load of BOMs I’ll be doing as part of this implementation, so I may revisit this or play around with it a bit more to try to get it to work as wanted but I’m good for now.  Thanks everyone again. 

7 replies

riglesias
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Employee
  • May 5, 2025

Hello ​@rskieresz88 

If you manually create a record under Bill of Material screen does the value for BOM ID field is auto-numbered?
 


Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • May 5, 2025

@riglesias  Yes, if I manually enter a BOM and hit Save it auto assigns the ID using the numbering sequence.   I’ve even done a test using just 1 line/row for the BOM, thinking maybe the multiple lines is part of the issue, but even with just 1 line, it does the same thing, it doesn’t auto-assign but uses the BOMID field from the spreadsheet instead.


riglesias
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Employee
  • May 5, 2025

Hi ​@rskieresz88 
Could you share a screenshot of the scenario mapping, or export the scenario to XML and attach the file here?


valentynbeznosiuk
Jr Varsity I
Forum|alt.badge.img+3

Hi ​@rskieresz88 

 Try to put into the BOM ID field instead of populating value from the file, to put ='<NEW>' or any other New Number Symbol value from the related Numbering Sequence

 


Forum|alt.badge.img+2

@riglesias If you are migrating BOMs, it's better to create and assign BOM numbers manually in your Excel sheet and then load them using an import scenario, instead of letting the system generate the numbers. This approach makes it easier to track which BOMs were imported successfully and to analyze any errors that occur during the import process.


valentynbeznosiuk
Jr Varsity I
Forum|alt.badge.img+3

@rskieresz88 I’ve spent some more time playing with it, and my previous suggestion is not stable in most cases, so I was looking for another way, and such a combination as a result gives ignoring numbers from spreadshit using a numbering sequence instead. Pay attention: line with <Action:Cancel> should be disabled

 


Forum|alt.badge.img
  • Author
  • Jr Varsity II
  • Answer
  • May 6, 2025

@valentynbeznosiuk  thank you for your research into this.  Your suggestions did help a bit, but I still was having some issues and errors when trying to create more than one BOM.  I did play around with unchecking the cancel box on the import scenario and it was changing things, but I still wasn’t able to get it to the point of it correctly assigning the ID and recognizing the change to create the next BOM.  I probably didn’t try all the combinations I could of with this and maybe your suggestion could of worked in the end with more trial and error on my part, but I made the decision to just manually populate the BOM ID field on the spreadsheet based on their numbering scheme.  As I said from the start, the scenario itself was working fine when the BOM ID assignment was taken out of the mix.  So I did that, changed the numbering sequence to manual and imported the about 200 BOMs from the spreadsheet with no issues whatsoever.  

This isn’t the last load of BOMs I’ll be doing as part of this implementation, so I may revisit this or play around with it a bit more to try to get it to work as wanted but I’m good for now.  Thanks everyone again.