How to change the same item under all the Production BOMs in Business central

(10) Share

Report

Posted on by SC666

209

Hello,

Do we have any methods to change the same item under all the production BOM in business central at once?

We have discontinued products or vender changed from time to time, and we need to update the items under production BOM accordingly. If we manually change the item per BOM, it will be a huge work and hard to keep the BOM up-to-date.

I saw the /Exchange Prod Bom Items/ but it kept showing error. I defined the No series starting at blank and increase by /1/ because some BOM versions are over 4.0.

Question 1: Can system starting the BOM version and increase by what it is now? Eg. my current BOM version is 3.0 after item replace, it will auto save as 4.0 version.

Question 2 : Is my replacement condition correct below? After running why I cannot see the lined under the related BOM was changed?

Any suggestions? Thank you!

Shine

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

Nimsara Jayathilaka. 4,836 on at

Like (6)

Report

Hello

There's not any way to update an item in bulk across all the production BOMs right away. You typically edit BOMs one at a time. When it comes to version control, the system does not automatically bump BOM versions when you replace an item; you must manage that manually, or create a new version with your required numbering.

If you feel answer is helpful verify the answer.

Thanks

Nimsara

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,311 Super User 2025 Season 2 on at

Like (1)

Report

As far as I know, there's no good solution other than customizing it. Using a configuration package makes adding it easy, but removing it is difficult.
Manual updates are best because they record the version number and preserve the BOM history.

Hopefully other experts can give you better advice.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 3,721 on at

Like (1)

Report

Namaste

Problem Statement is genuine , I also tried i recieved the error .

But un-fortunately we dont see any standard solution . Updating Configuration package is also difficult as there are on-validate Triggers activated

Proposed Solution - Customization ( ** Not implemented but can suggest )

1) Create Table to Store Item no , BOM no , Bom Line no , Expected Item, Expected Qty , Expected UOM

2) Create Procedure to update BOM lines based on Primary key - BOM No , BOM line no with Item No, Expected qty , Expected UOM

3) Upload the data in custom table

4) Provide the admin access to run the Report .

Healthy Tips

1) Dont run this report frequently . Prvoide this repot to Admins

2) Ensure you do this activity in sandbox , Do it for one BOM verfiy the trasnactions after update . Verfiy produciton order is it working fine.

3) If you feel correct , implement in production in offline hours

If you feel helpful , please verify the answer .

Regards

Pallavi Phade

Was this reply helpful? Yes No
Verified answer

Ben Baxter 6,559 Super User 2025 Season 2 on at

Like (3)

Report

Shine,

Yes, this is a standard process in BC. You have the process correct, as you would use the "Exchange Production BOM Items" function to replace an existing component in your Production BOMs.

I think you are running into an issue because your Number Series doesn't have a Starting No. (but read on before you make this change)

The issue with the current process is lack of control and some limitations. The "Exchange Production BOM Items" will create a new BOM Version for the existing Production BOM. It will replace the defined Item with the new Item outlined during the process. You do have some settings around quantity relationship between previous Item and replacement Item, and whether you want to Certify that new BOM Version upon creation.

However, it comes with some limitations. The biggest is the Version No. series. Instead of the individual BOM having V1, V2, V3 and another BOM having V1, V2, V3...the Version No. applies to every new BOM Version created. Which means, unless you create a new Number Series for every BOM, you'll have some BOM Versions that start at 5 or V1200, even though it is the first BOM Version for that unique BOM. It would be better logic to increment the previous BOM Version for each BOM by 1, since the Primary Key involves the BOM and the Version Number, but this is sadly not an out-of-the-box option.

Another flaw in the process is BOMs with the same Item listed multiple times, but with different Routing Link Codes. The process doesn't handle this scenario and will throw an error message. The work-around is to Close that BOM, run the process, then re-certify and manually create the BOM version for that BOM.

I would love if Microsoft added some filtering capabilities to this process to better control the BOM updates, but that could be something you discuss with your partner/developer.

I hope this helps clarify the process.

Best Regards,

Ben Baxter

Accent Software Inc

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Sahan Hasitha 2,674 on at

Like (4)

Report

hi

There isn’t a standard solution for handling this issue in Business Central. A configuration package can simplify adding BOM changes but makes removing items difficult. The only reliable approach is customization, which requires additional development effort. Alternatively, manual updates are often preferred, as they automatically record version numbers and preserve full BOM history, ensuring traceability

1 people found this reply helpful.

Was this reply helpful? Yes No