BOM Common Bill of Materials Upload points the bills of material in one or more target organizations at a source organization’s bills – so the target assemblies share, rather than copy, the source bill. It walks the whole bill structure and commons any referenced sub-assembly and substitute-item bills automatically. It creates common-bill references only; it does not change components or delete anything.
When to use it
- Share a master bill maintained in one organization with other organizations instead of keeping independent copies.
- Point a new organization’s assemblies at existing bills in bulk during a rollout.
- Common many bills at once, including all their sub-assembly and substitute bills, without doing each by hand.
- Common to all sibling organizations, to all organizations below a hierarchy node, or to a specific organization.
- Review, per target organization, which assemblies already have bills or are missing items before committing.
Before you start
- Blitz Report is installed and you are signed in to a Manufacturing or Bills of Material responsibility with access to the target organizations.
- The source and target organizations share the same item master.
- The assembly item, and all of the bill’s component and substitute items, are already defined in the target organization.
Choose a template
| Template | Use it for |
|---|---|
| Common BOM Upload Template (default) | The download lists every bill and target-organization combination with the Create Common Bom column blank, for you to flag the ones to common. |
| Automatic Common BOM Upload Template | The download comes back with Create Common Bom already set to Yes on every combination – you clear or remove the rows you do not want. |
Step 1 – Choose a template, set the parameters and download
In Blitz Report, open BOM Common Bill of Materials Upload, choose your template, and set the parameters:
| Parameter | Purpose |
|---|---|
| Source Organization Code | The organization whose bills will be made common into the targets. |
| Common BOM Scope | Which organizations to common into: All, Hierarchy or Organization. |
| Target Hierarchy / Target Organization | The hierarchy or specific organization, when Scope is Hierarchy or Organization. |
| Assembly / Alternate BOM | Optionally restrict the download to one assembly or alternate. |
| Show Missing BOMS only | Yes shows only combinations not yet defined in the target. |
Run the upload to download and open the Excel file.
Step 2 – Flag the bills to common
Each row is one bill for one target organization. Set Create Common Bom to Yes on the rows you want made common (in the Automatic template these are already set – clear the ones you do not want). The readiness columns – Is Item Defined In Tgt, Is Bom Defined In Tgt and Comp Items Not Defined In Tgt – show, before you upload, whether the target organization is ready.
Step 3 – Validate and Save
Click Validate and Save. This checks the rows and saves the file. Correct anything it flags before continuing.
Step 4 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates the common-bill references (and any sub-assembly bills that also need commoning). When it finishes, a result report opens showing each row as success or error.
What’s produced
- Common-bill references in the target organizations, including any sub-assembly and substitute-item bills that needed commoning.
- A result report listing every row with a status and a message.
Common questions
Does it copy the components into the target organization?
No. It creates a common bill – the target assembly’s bill references the source bill, so changes to the source flow through.
What if I leave Create Common Bom blank?
That row is skipped and reported as no action taken. Only rows flagged Yes are processed.
Why does a row say the bill already exists?
A bill already exists for that assembly and alternate in the target organization, so nothing is changed. The Is Bom Defined In Tgt column shows Yes for these.
What’s the difference between the two templates?
The default template comes back with the flag blank for you to choose; the Automatic template comes back with every row already flagged Yes, so you only remove the ones you do not want.
Does it also common the sub-assemblies?
Yes – it walks the whole bill structure and commons any sub-assembly or substitute-item bill that exists in the source but not yet in the target.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| This API only supports upload of existing BOMs | The row was not produced by the download (for example a row typed in by hand). | Use rows from the generated template; re-download and flag the rows you need. |
| No action taken | Create Common Bom was not set to Yes on that row. | Set Create Common Bom to Yes for the rows you want processed. |
| Item is not defined in the target organization | The assembly item itself is not assigned in the target organization. | Assign the item to the target organization first, then re-run. |
| No action – bill already exists | A bill already exists for that assembly and alternate in the target. | None needed – the bill is already present. |
| Component items are not assigned in the target organization | Some component or substitute item is missing in the target. | Assign the listed items in the target organization, then re-upload. |