Product Matching Report Purpose
The QA Report - Product Matching can be used to check whether all your data from a specific BOM import has been mapped to a Makersite dataset, and if so, which one. The report will highlight which datasets are mapped agains which BOM items, and how. You will get a full overview of the data mapping resulting from your BOM import.
Prerequisites
You need to import your BOM before you can run the QA Import Report.
Running QA Product Matching Report
From the home page, go to Makersite Apps > Business > Pivot Manager > QA-Product Matching.
Set the Product to be analyzed in the right-hand menu.
Select the appropriate report options, as explained below.
Click Create. The report should be available after a short while. If you select Run in the background and save, you will get an e-mail with a link to your report once it's ready.
Report options:
Option | Description |
Full Model | When left blank, the report only considers the datasets directly in the imported BOM. When selected, the report will extend the assessment to additional datasets associated with attached IPC files and BOM's. |
Leaves only | Run the report only for BOM leaves, i.e. the items in the BOM without any sub-items. |
None of the above | If none of the above options are ticked, the report will only show the BOM structure as it has been imported. |
Run in the background and save | Send the report to the queue instead of running it immediately on-page. You will get an e-mail with a link to your report when ready. |
Leaves Only in Depth:
This option refers to the lowest level of an imported BOM (a leaf), and will not show any of the levels in-between, for example if a BOM structure has 4 levels, only levels 1 and 4 will be shown, 2 and 3 will be omitted.
Analyzing Product Matching Report
When ready, your report shows the following data:
Part 1:
Part 2:
Please refer to the table below for column explanation:
Column | Description |
Order | Self-explanatory |
Line count | Line in the BOM |
Level | BOM level. Top-level assembly is always level 0, it's sub-assemblies are level 1, and so on. |
Name | Name of the Product Group created upon import |
Amount | Item amount |
MPN/PN/CAS nr | Item identification. Manufacturer Part Number/Part Number/ CAS nr for chemicals |
Calculated weight | Item weight calculated by Makersite |
Part type |
|
Geography | Geography assigned to Process |
Preferred route | Links to the Process responsible for making this item |
Dataset source | Source of imported data |
Mapped dataset type | Type of dataset mapped by Makersite to the source. Public (generally available in Makersite) / Private (uploaded by you or your team) / Premium (from external dataset available via premium plan) |
Mapped dataset source | Where does the mapped data come from? |
Match type | How the connection between imported and mapped data was made |
Mapped dataset | Link to the mapped dataset in Makersite |
Product Category | UNSPSC Product Category assigned on the source dataset |
Mapped Product Category | UNSPSC Product Category assigned on the target dataset |
Weight (%) | Share of item weight in the whole assembly |
Unit / Weight (kg) | Self-explanatory |
Env. impacts available | Yes/No/no data. Should be available if Product Category is assigned and the LCA model has been calculated for the item. |
Price available | Yes/No/no data. Should be available if Product Category is assigned. |
Minimum cost | Minimum item cost calculated by Makersite |
What's Next?
If you find unmapped data, you can go to the product's Compose page, select Resume import, and map the data manually.
If everything looks good, you can proceed with your business (see documentation on LCAs or Compliance).