Material Master Data (US)
Overview
Every record in this material master is generated. Nothing in it was extracted from a real manufacturer's system: no real material, part, manufacturer, plant, price or stock position is represented, and any resemblance to a real record is coincidental. What is reproduced is the shape and the behaviour of a material master a US automotive manufacturer actually holds. The master carries 250,000 materials: raw material, semi-finished and finished product, spare parts, production resources and tools, packaging, operating supplies, trading goods, service and non-stock material, across powertrain, body, chassis, electronics and interior, and across the robotic manufacturing equipment the plants themselves run on. Every material is classified by type, group and class, and every code carries its description on the same row, so the file explains itself with no lookup table and no join. The header row also carries the material's primary manufacturer part number with the manufacturer it belongs to, and its primary barcode with the type that says which structure the barcode carries, because those two are what anyone opening a material master looks for first and neither should be a join away; manufacturer part numbers sit on the externally procured material and barcodes only on material whose base unit is the each, both of them partial the way a real master is partial, and the identifier table beneath holds the rest, where a material may have several part numbers from several manufacturers and a barcode for each packaging level. Classification runs to commodity depth: each material carries its UNSPSC code and title and its segment, plus a 6-digit HS subheading and a 10-digit US HTS line, and each taxonomy ships as a codeset table of its own, keyed on the code itself so that materials reference it by a declared foreign key rather than by convention, with the full path on every row and a count of the materials underneath it. The UNSPSC families are the same code space the vendor master ALLVMS702 classifies suppliers in, so a buyer holding both products can go from a material to the vendors approved to supply its commodity family. The unit of measure conversion table and the depth of the bill of material are the reasons to buy it. Each material keeps separate base, purchase, stock issue and sales units, and every alternative unit is stated as an exact numerator and denominator against the base unit, covering eaches, dozens, gross, litres, gallons, drums, bags, cases and pallets, so conversion logic can be exercised on real packaging ladders instead of a single factor. The bill of material has genuine depth: a superior equipment relationship threads every part from a complete assembly down to the fastener, and a parent explodes through several levels of child structure rather than one flat list. It is built to exercise what a material master is bought to exercise: unit conversion arithmetic, BOM explosion and where-used, split valuation, phantom assemblies, plant-specific make or buy, and status-aware filtering.
Row Counts by Table
Counted from the files that ship, not estimated.
| Table | Rows |
|---|---|
| materials | 250,000 |
| material_plants | 370,000 |
| material_valuations | 350,500 |
| material_uom_conversions | 570,000 |
| material_identifiers | 230,000 |
| bom_headers | 39,260 |
| bom_items | 345,340 |
| material_sales_orgs | 108,000 |
| unspsc_codes | 368 |
| hs_codes | 145 |
Table Relationships
One parent record and seven child tables, each joined back on the same key.
Schema
Every table ships with typed columns, referential integrity, and documentation.
| Column | Type | Description |
|---|---|---|
| material_id | varchar(16) | Material number. Primary key of materials, and the foreign key every child table joins on. Ten digits, zero padded. |
| material_description | varchar(96) | Short text a planner or buyer reads to recognise the material: noun, then modifier, then specification. |
| material_type | varchar(16) | Controls the number range, stock behaviour and valuation. ROH raw material, HALB semi-finished, FERT finished product, ERSA spare part, FHMI production resource or tool, VERP packaging, HIBE operating supplies, HAWA trading goods, DIEN service, NLAG non-stock, UNBW non-valuated. |
| material_type_description | varchar(40) | What the material type code means in words, for example ROH is "Raw Material". |
| material_group | varchar(16) | Automotive commodity group, and the one classification value entered by hand: class, scope, domain and UNSPSC segment are all derived from it. The vendor master ships a column of the same name over an entirely different vocabulary, so the two do not join. |
| material_group_description | varchar(64) | What the material group code means, for example PWT-1010 is "Engine Block and Head Components". |
| material_class | varchar(16) | Derived from the group: the engineering class it belongs to, one level of aggregation up. |
+51 more columns in materials. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| material_id | varchar(16) | Material this plant view belongs to. Half of the primary key, and the foreign key to materials. |
| plant | varchar(16) | Plant the view is maintained for. The other half of the primary key: a material extended to three plants has three rows here. |
| plant_name | varchar(40) | Name and location of the plant the code identifies. |
| plant_material_status | varchar(16) | Whether the material may be used at this plant: active, blocked or phase_out. It is set per plant and may differ from the company-wide material_status. |
| procurement_type | varchar(16) | How this plant obtains the material. E made in house, F bought in, X both. |
| procurement_type_description | varchar(56) | What the procurement type code means, for example E is "In-house production". |
| special_procurement_type_code | varchar(8) | A qualifier on top of the procurement type. 10 consignment, 20 subcontracting, 30 planned stock transfer, 40 direct stock transfer, 50 phantom assembly. Empty on most rows, where the plain procurement type is the whole story. |
+22 more columns in material_plants. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| material_id | varchar(16) | Material this valuation segment belongs to. Part of the primary key. |
| valuation_area | varchar(16) | Where the stock is valued, which in this dataset is the plant. Part of the primary key. |
| valuation_area_name | varchar(40) | Name and location of the valuation area. |
| valuation_type | varchar(16) | Which stock the segment values. STD where there is no split, or DOM and IMP where domestic and imported stock are valued apart. Never empty. |
| valuation_type_description | varchar(40) | What the valuation type means, for example IMP is "Imported stock". |
| valuation_category | varchar(16) | H where the material is split valuated by procurement origin. Empty where it is not. |
| valuation_category_description | varchar(48) | What the valuation category means and what the stock is split by. |
+14 more columns in material_valuations. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| material_id | varchar(16) | Material the conversion belongs to. Part of the primary key. |
| alt_uom | varchar(16) | The alternate unit this row defines. Part of the primary key, and never empty: every material has one row where it equals the base unit. |
| alt_uom_description | varchar(16) | The alternate unit code in words, for example DOZ is "Dozen". |
| alt_uom_dimension | varchar(16) | What the alternate unit measures. It may differ from the base dimension, as a bag does over a base unit of mass, and that is deliberate. |
| base_uom | varchar(16) | The material base unit, repeated on every row so the conversion reads without joining materials. |
| base_uom_description | varchar(16) | The base unit code in words. |
| base_uom_dimension | varchar(16) | What the base unit measures. |
+5 more columns in material_uom_conversions. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| identifier_id | varchar(16) | Primary key. One row per identifier, so a material with a part number and two barcodes has three rows here. |
| material_id | varchar(16) | Material the identifier belongs to. |
| identifier_type | varchar(16) | What the row identifies the material by: MPN a manufacturer part number, GTIN13 and GTIN14 barcodes, QR a scannable code, OEM_PART an original equipment part number. |
| identifier_type_description | varchar(88) | What the identifier type is and who issues it. |
| identifier_value | varchar(56) | The identifier itself. Barcodes carry a valid GS1 check digit so validation logic can be exercised, and a prefix GS1 reserves for restricted circulation, so they are synthetic and must never be used to identify goods in a trading system. |
| identifier_uom | varchar(16) | Packaging level the code applies to, for example the case or the pallet. Populated for barcodes and QR codes, empty for part numbers. |
| identifier_uom_description | varchar(16) | The packaging unit code in words. |
+6 more columns in material_identifiers. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| bom_id | varchar(16) | Primary key. One bill of material per material, plant and alternative. |
| material_id | varchar(16) | The material this bill of material produces, or the equipment it is maintained against. |
| material_description | varchar(88) | Description of the header material, copied so the header reads without a join. |
| plant | varchar(16) | Plant the bill of material is valid at. A material may be structured differently at each plant. |
| plant_name | varchar(40) | Name and location of the plant. |
| bom_alternative | varchar(8) | Which production route this is, numbered from 01. A material with two routes at one plant has two headers. |
| bom_usage_code | varchar(8) | What the structure is for. 1 production, 2 engineering and design, 3 universal, 5 costing, 6 plant maintenance. Only 1 and 3 mean the plant makes the material. |
+14 more columns in bom_headers. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| bom_item_id | varchar(16) | Primary key. One row per component position on one bill of material. |
| bom_id | varchar(16) | The bill of material header this component belongs to. |
| parent_material_id | varchar(16) | The material being built. Carried here as well as on the header so a where-used query needs one join rather than two. |
| parent_bom_level | integer | Level of the parent material in the structure. |
| item_number | varchar(8) | Position of the component within the structure, numbered in tens so a later insertion has somewhere to go. |
| component_material_id | varchar(16) | The material consumed. Always a real material, and always one with a plant view at this header plant. |
| component_description | varchar(88) | Description of the component, copied so the item reads without a join. |
+13 more columns in bom_items. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| material_id | varchar(16) | Material this sales view belongs to. Part of the primary key. |
| sales_org | varchar(16) | Sales organisation that may sell the material. Part of the primary key. |
| sales_org_name | varchar(24) | Name of the sales organisation. |
| distribution_channel_code | varchar(8) | Route to market this view applies to. Part of the primary key, and a code rather than a number despite being all digits. |
| distribution_channel_name | varchar(32) | What the channel code means, for example 10 is direct supply to a vehicle manufacturer. |
| delivering_plant | varchar(16) | Plant that ships the material by default for this sales organisation and channel. |
| delivering_plant_name | varchar(40) | Name and location of the delivering plant. |
+13 more columns in material_sales_orgs. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| code | varchar(16) | The UNSPSC code, 8 digits at every level, zero padded below the level it names. Primary key, and what materials.unspsc_code and materials.unspsc_segment_code reference. |
| level_number | varchar(8) | Depth of the row, 1 for a segment through 4 for a commodity. |
| level_name | varchar(16) | What the level is called: segment, family, class or commodity. |
| title | varchar(120) | Official UNSPSC title of the code. |
| parent_code | varchar(16) | The code one level up, and a foreign key into this same table. Empty on a segment, which is the termination case for a recursive walk. |
| segment_code | varchar(16) | Segment this row sits under, 2 significant digits. The whole path is carried on the row so it reads without a recursive query. |
| segment_title | varchar(120) | UNSPSC title of the segment. |
+9 more columns in unspsc_codes. The full schema ships with the download.
| Column | Type | Description |
|---|---|---|
| code | varchar(8) | The Harmonized System code: 2 digits for a chapter, 4 for a heading, 6 for a subheading. Primary key, and what materials.hs_code references. |
| level_number | varchar(8) | Depth of the row, 1 for a chapter, 2 for a heading, 3 for a subheading. |
| level_name | varchar(16) | What the level is called: chapter, heading or subheading. |
| title | varchar(136) | Official Harmonized System title of the code. |
| parent_code | varchar(8) | The code one level up, and a foreign key into this same table. Empty on a chapter. |
| chapter_code | varchar(8) | Chapter this row sits under, the first 2 digits. |
| chapter_title | varchar(112) | Harmonized System title of the chapter. |
+7 more columns in hs_codes. The full schema ships with the download.
Sample Data
A snapshot of real rows from the dataset (values are fully synthetic).
| material_id | material_description | material_type | material_type_description | material_group | material_group_description | manufacturer_part_number | manufacturer_name | barcode_gtin | barcode_type | unspsc_code | unspsc_title | hs_code | base_uom | material_status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0000100001 | SCARA Robot | FHMI | Production Resource or Tool | ROB-6010 | Industrial Robots and Manipulators | VAN-91460-A0 | Vandale Metalcraft LLC | 23153200 | Robotics | 847950 | EA | obsolete | ||
| 0000100002 | Calliper Bracket, Front Axle, 278 mm | FERT | Finished Product | CHS-3040 | Brake Discs, Drums and Callipers | 25171700 | Braking systems and components | 870830 | EA | active | ||||
| 0000100003 | Headlamp Assembly, 48V, 32 Pin, Rev C | FERT | Finished Product | ELE-4060 | Lighting Modules and Lamps | 25172907 | Vehicle headlight | 851220 | EA | active |
Version History
| v1.0.1 | 2026-08-17 | Moves the QR payload host off the reserved .example TLD. GS1 Digital Link URIs now resolve to id.datlyne.com, the publisher's own domain, rather than a suffix that announces itself as a placeholder in every scan. The GTIN-14 payloads and their check digits are unchanged, so a scanner reads exactly what it read before. No other column, row or value differs. |
Related Datasets
Automotive Manufacturing Sales (EU)
ManufacturingA European automotive sales dataset across the electric transition: 12 brands, 112 models, 20 markets, four channels and five customer segments, monthly from 2016 to mid 2026, in which eight legacy European brands peak, crash, and lose a fifth of the market to battery electric entrants while their net debt climbs.
EV Battery Passport Degradation and Circularity Analytics Set (EU)
ManufacturingEU EV battery passport data linking materials, manufacturing, vehicle use, degradation, safety, second life, recycling and circular recovery.
Heavy Equipment BOM Structure (WW)
ManufacturingA heavy-equipment service parts catalogue with real bill-of-materials mechanics: six machine families, 39 variants, trees four to six levels deep with materialised paths, over a million item rows across 124,337 parts, serial-number effectivity, supersession chains with one documented loop, and a derived where-used table that reconciles exactly.