Material records describe the items your team buys, makes or sells. Bills of material describe component relationships that help explain how a supply issue can affect production.
Before you start
Your workspace needs the relevant material, bill-of-material and component data. Missing relationships can prevent a useful downstream view.
Choose the object that holds the business record before applying search or filters.
Read material and component context
Open Records → Material Masters or the item object used by your workspace.
Find the material by identifier and inspect its units, planning fields and relevant relationships.
Open the related Bills of Material and inspect the parent item and component lines.
Follow the components to their suppliers, stock or order context where those relationships are available.
Use Terrain or a task to investigate a shortage with the affected material and production context attached.
Check the result
You can identify the material and the component relationship relevant to the work. Confirm quantities and units before using the relationship to judge supply coverage.
Keep units and versions clear
A component requirement can depend on quantity, unit and the applicable bill of material. Check your source system’s current record rather than inferring a production requirement from a similarly named item.
A supplied item can add supplier-specific context for a material, including the lead time that should be verified with that supplier.
Connect to planning carefully
Planning views depend on configured inputs and which demand and supply records count. A bill-of-material relationship alone does not establish that every relevant requirement has been synced.
If something does not look right
What you see | What to check |
The component is missing | Check BOM line sync and the material relationship. |
Supply coverage looks wrong | Review units, demand source, site scope and inventory planning inputs. |
Should I edit a BOM to fix a display issue?
Should I edit a BOM to fix a display issue?
Confirm source ownership and mapping first. A display or relationship problem may need an integration correction rather than a production master-data change.
Continue your work
Open the relevant area in Cartograph to continue with your workspace data.