Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Looking at the BOM tree structure, how's tree built, in other words, how table records are linked together?
I am trying to retrieve records for all BOM items, child items.
Could you let us know the form name are you referring to.Is it BOMDesigner or something else.
BOMDesigner, for 2009.
Here is a small overview of the BOM related tables:
BOMTable table - a header of the BOM list. It contains a unique BOMId, that will be used by BOM lines to refer to the header.
BOM table - lines of the BOM list. They are using BOMId of the BOMTable record to refer to the header.
BOMVersion table - this table connects an item and a BOM (header). It allows to have many-to-many relations between an InventTable and BOMTable. It means that many items have the same BOM, and many BOMs can be assigned to the same item. However, only one BOMVersion record will be selected and its BOM Id is used on the order line during the order creation and this selection is based on the criteria specified on the BOMVersion record (e.g. order quantity, order date) and the respective data on the order line (sales or production). This table is not mandatory and actually maybe disabled in the configuration key. If it happens, then there will be always 1-to-1 relation between an item and a BOM and it won't be possible to setup automatic selection based on criteria.
These three tables are enough to build the entire BOM structure.
Thanks Sukrut, BOM could have many levels/layers, how's that handle between these 3 tables?
I don't have ax 2009 environment but I think there is table called BOMLevel
There is no table call BOMLevel, or similar.
Thanks a lot! Sukut, finally figured out, I have to use recursive query on BOM and BOMVersion tables to retrieve the BOM tree structure
I'm very interested in the recursive query you implemented to build a BOM tree structure based on BOMTable, BOM, and BOMVersion.
Would you kindly share this query with me?
Sorry, I changed job, don't have the query anymore. But, it's not hard, you should be able to figure out.
Business Applications communities